possible Bug: tbcleanup deletes all database entries
Frank Wall
fwall at inotronic.de
Fri Sep 12 09:04:14 EDT 2008
Hi,
today was the first (and maybe last) time I used the tbcleanup feature.
According to the README I expected it to delete "old log files and packages".
In my case this went totally wrong and tinderbox startet deleting ALL ports
from the database! First I did not realize it, because print/ghostscript-gpl-nox11
really doesn't exist anymore, but it found more and more ports...
./tc tbcleanup -p
Removing database entry for nonexistent port devel/autoconf261
Removing database entry for nonexistent port print/ghostscript-gpl-nox11
7.0-STANDARD
Removing database entry for nonexistent port shells/zsh/7.0-STANDARD
Removing database entry for nonexistent port converters/libiconv/7.0-STANDARD
Removing database entry for nonexistent port lang/perl5.8/7.0-STANDARD
[...]
Tinderbox deleted 112 ports from the database before I could stop it.
So my question is: is this a bug or a feature? Since I never used tbcleanup
before this question is serious :-)
Kind regards
Frank Wall
More information about the tinderbox-list
mailing list