On Mon, Sep 11, 2006 at 12:48:41AM +0300, Lars Wirzenius wrote: > su, 2006-09-10 kello 21:31 +0200, Bill Allombert kirjoitti: > > After performing sarge to etch upgrade, piuparts try to do 'apt-get > > install $pkg'. I am not sure what is the purpose of this, but it cause > > the following problem: > > If $pkg was renamed, it exists in Sarge but no more in Etch and in this > > case the command fails and so does piuparts. > > Yes, that's what happens. Piuparts does not try to track changes in > package names. This is not a bug as far as I care, so I'm closing the > report.
Is it documented ? > If I have understood correctly, you're trying to test upgrades from > sarge to etch. piuparts.cs.helsinki.fi already does that for individual > packages, when the package name has not changed. For other kinds of > tests, piuparts is probably not the right tool. Well, in my opinion, if you want to test upgrade seriously, you should be able to test at least whether all sarge packages can be upgraded, especially since packages that get renamed have a more fragile upgrade path on average. Currently I am performing "random upgrade": I install a random set of sarge packages and try to upgrade them. Cheers, Bill. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
