possible Bug: tbcleanup deletes all database entries
Joe Marcus Clarke
marcus at marcuscom.com
Sat Sep 13 03:29:35 EDT 2008
On Fri, 2008-09-12 at 15:04 +0200, Frank Wall wrote:
> 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
> 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 :-)
The message is wrong, but the result is correct. tbcleanup is really
designed to be run AFTER a package build but before running tc addPort
and starting a new package build. What this phase of tbcleanup does is
remove database entries for ports which do not have packages built.
That is, build 7.0-STANDARD did not have a recent package built for
shells/zsh, so that database entry gets pruned.
If you run tbcleanup before running the tinderbuild, you'll need to
re-run addPort to re-populate the database.
PGP Key : http://www.marcuscom.com/pgp.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 195 bytes
Desc: This is a digitally signed message part
More information about the tinderbox-list