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

Re: Lots debian packages (wine, zapping, gst-plugins0.8, Qcad, etc.) can't enter to Sarge because of arts :(

On Fri, 17 Sep 2004, AKL. Mantas Kriauciunas wrote:
There is a pretty big problem with arts (core sound system of KDE) -
many debian packages (wine, zapping, gst-plugins0.8, Qcad, zinf and lots
of kde packages) can't enter to Sarge because of arts :(

The problem is, that arts in unstable is at version 1.3.0 and has release
critical bug  #269132, named "arts 1.3 completely untested against kde 3.2"
and lots of packages, which don't need exactly this version (works fine
with version from testing) can't enter to Sarge, because they are compiled
with arts 1.3.0

Sounds like the problem is with the packages whose preferred versions are not in testing.

The best solution would be if the packages in testing were compiled using
testing dev libraries (like libartsc0-dev), but current Debian politics
doesn't allow this, so there always are lots of problems in situations like
this (especially in the middle of the release cycle)

I don't know what you mean. All packages in testing, including the dev packages, are derived from sources in the pool flagged as being in "testing"... no?

So, I found 2 temporary solutions:
1. Allow to enter arts 1.3.0 into Sarge (look at the bugreport for more
info - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=269132 )
2. Downgrade arts in unstable to 1.2.3 and recompile all packages in
unstable, which depends on arts.

How about introducing arts-future_1.3.0 into unstable and creating wine-newer, zapping-newer, etc. which depend on it, then let them migrate into testing. QA is satisfied and only the affected packages need to make an effort. If having two versions of wine, etc. in Sarge is no good then maybe some games can be played via proposed-updates or manual intervention to drop the older versions and rename the newer ones.

- Bruce

Reply to: