[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problem testing with piuparts

On Wed, Nov 24, 2010 at 4:20 PM, Holger Levsen <holger@layer-acht.org> wrote:
>>> /var/lib/python-support/python2.4/.path
>> >> Can you recommend any best practices or helper scripts?
>> > a.) file a bug against the dependend package
>> Is it python-support?
> In this case I probably wouldn't file a bug as it involves python-2.4 and that
> is gone from sid and squeeze.

I still need it to ensure build can succeed on lenny with python-2.5
(I don't use sid or squeeze, because my server is too stable and too
"productive" to be disturbed out of trac/trac-bitten scope).

>> --no-symlinks with -I pysupport and -I ssl helped. Thanks. But it runs
>> only installation and purging test. How to make it run upgrade test
>> also?
> Quoting the manpage:
> If you want to test that a package installs properly in the stable (currently
> lenny) Debian release, then can be upgraded to the testing (currently
> squeeze) and unstable (sid) versions, and then uninstalled without problems,
> you would give the following command:
> piuparts -a -d lenny -d squeeze -d sid foo

But I don't want to test upgrade between Debian releases. I want to
test upgrade from previous package version (in lenny-backports) to
newer package version I've just biult.

>> Trying to backport latest trac-bitten 0.6b3 to install on development
>> machine, which is running lenny.
> Ah.
> I dont bother filing bugs in lenny anymore (unless severe ones). If you can
> reproduce it in sid, great! (Then I'd file..)

This suxx, of course, but backports are here to handle exactly that,
aren't they?

>> Please, CC.
> Done, please don't cc: me :)

Usually "Reply to all" button is enough. ;)
anatoly t.

Reply to: