Hi, On Wed, Aug 30, 2006 at 11:08:29PM -0700, Adeodato Simó wrote: > [...] > That person will normally be the developer responsible for the upload, > but in fact can be any developer that steps up and says "I understand > the issues involved, and I've made sure they'll cause no problem". > > Said that, I'm sure you'll find that at least one of the members of the > release team will be able to allocate some time to perform that task > *together* with the maintainer. If you'd like that, please let us know. Well, AFAICT that change should pose no problem at all, _but_ I'm in paranoid mode because I don't really want to mess anything, now that we are somewhat close to a release. Do you know if there is any easy way to rebuild all those packages with the modified ruby-pkg-tools? I guess I can try that by hand, but I would prefer something more automatic. Perhaps you can help with that, I don't know :-/ As I said, I have a tiny script to collect simple regression data (the generated packages' file list), and I have used that to compare file lists by the previous r-p-t and by the new, proposed r-p-t. Some of the packages couldn't be built, probably because of missing Build-Depends or something, but the ones which built correctly, did so with both versions, I think, and the file list was the same, except for hobix (the fixed package). I didn't really feel like investigating through the enormous output when I first tried (imagine the output of a for loop, with about 20 source packages, building the debs), but if there isn't any other, easier way... Regards, -- Esteban Manchado Velázquez <firstname.lastname@example.org> EuropeSwPatentFree - http://EuropeSwPatentFree.hispalinux.es Help spread it through the Net in signatures, webpages, whatever!
Description: Digital signature