[Piuparts-devel] running piuparts on a single package which were not modified by the user

[Ivo De Decker]

Hi,

As Andreas requested, I'm redirecting this discussion (triggered by bug
677054) to piuparts-devel.

On Sat, Jan 26, 2013 at 06:57:07PM +0100, Andreas Beckmann wrote:
> On 2013-01-26 17:10, Ivo De Decker wrote:
> > It seems this can be fixed by just keeping the first part of the config file
> > in the preinst. The attached patch fixes the piuparts error.
> > 
> > With this patch, piuparts still reports an error on lenny -> squeeze ->
> > wheezy, but that error seems to be related to the split of the nut package, so
> > I don't know if this is really an error or just a false positive...
> 
> nut 2.6.4-2.3 passes the lenny->squeeze->wheezy distupgrade test. I
> probably have a few more exceptions and excludes active than are shipped
> in the last release (or even committed to the public git).

Well, it would be nice to have some documentation to easily reproduce all the
tests you are running on the archive, even with packages that aren't uploaded
yet. This involves setting up a private repo and some wrapper scripts. I don't
know if such docs exist somewhere? I would be willing to help with that.

Obviously, it would be a great help with that to have all your scripts, even
those that aren't in git (yet).

Currently, it's quite hard for random developers to do the piuparts tests
themselves, especially before upload. If they would just have to run some
script on their binaries (and wait quite some time for all the tests), that
would be one less excuse for not being piuparts-clean :)


Cheers,

Ivo