On Wed, Jan 19, 2005 at 04:15:30PM -0700, Joel Aelwyn wrote: > > Sounds like you want --rebuild-all. Unfortunately, this currently only > includes --rebuild-files (which regenerates the Sources and Packages > files). The --rebuild-dbs option does not yet function, but is intended to > rebuild the on-disk DBs (though on further consideration, this may be an > interesting task). Sounds like there also needs to be a --rebuild-<mumble> > option for rebuilding the .source and .package files from which Sources and > Packages are built, if it isn't save to assume that they ever got written. > > In the meanwhile, I think it should be possible to grab *everything* that > got installed for the various packages (changes, dsc, etc), and put then > in the incoming/ area of a new archive, then fire it by hand. This is > effectively re-uploading things, and probably wouldn't work in an archive > that still had old data in it. Even the orig tarball detection in 0.1.10,
Indeed what I did, but it has been a try-and-redo process unfortunately, due to the orig tarball thing mainly. > however, doesn't try to use the .changes file to decide if the orig tarball > should be in the upload or in the archive; instead, it simply requires > that it exist in one (and only one) of the two places. I may fix this for > 0.1.11, now that I think of it... > > I agree that the --rebuild-* options need to be able to handle situations > that are somewhat more pathological than they currently can, but I'm not > (yet) sure just what they need to do or how they should do it yet, so this > bug may not be fixed immediately. > -- That was plain and clear :) Indeed it's a wishlist. Thanks for your speedy returns. -- Francesco P. Lovergine -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
