ma, 2006-09-11 kello 00:17 +0200, Bill Allombert kirjoitti: > > 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 ?
Not explicitly. > 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. If you want that to happen, write the code. I'm not going to write the code to automatically track package name changes. It's complicated enough that I don't even particularly want it included in piuparts at all. > Currently I am performing "random upgrade": I install a random set of > sarge packages and try to upgrade them. Piuparts is not suitable for this. You want a new tool that is suitable for upgrade testing of systems, not a tool for testing whether individual packages can be installed, upgraded, and removed. -- Every time I say /quit I die a little. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
