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

Packages not entering testing due to version inconsistencies between arches

Dear all,

There are a number of source packages whose current versions cannot
propagate into testing because they have previously been compiled on
arches that the maintainer cannot or does not want to support, and has
asked via the BTS to have removed.  Some of these bugs have been around
for months.  Some of the packages, if they could enter testing, would
fix RC bugs in sarge.  Is there anything we (i.e. anyone not an FTP
master) can do to help, other than point out the specific packages
affected?  Thanks should go to Jeroen van Wolffelaar for already
retitling and tagging most of the bugs against ftp.debian.org.

Below is a list by maintainer of affected source packages.  This list
may be a few days out-of-date.  Full disclosure: I maintain cernlib, one
of the source packages held up by this problem, and feel it's important
that the current version propagate into sarge.

Does anyone else think it would be reasonable for some script to run
over the archive and remove binary packages from unstable that are (a)
out-of-date, and (b) no longer intended to be built for that arch by the
maintainer (determined via the arch list in debian/control)?  This would
reduce workload on the FTP masters and prevent inconsistent versioning
in sid due to packages built for unwanted arches.

Format of this list:
- First field is source package name;
- Second field is the bug number(s) against ftp.d.o;
- Third and fourth fields are the version in testing, and the most
  recent version in unstable.  If the package is not in testing, then
  the third field is the earliest version present in unstable if there
  are out-of-sync arches;
- Remaining fields are any RC bugs closed between the two version
  numbers listed, plus those that would be "fixed" by removal of the
  unwanted arches.

Alberto Gonzalez Iniesta <agi@agi.as>
  xmbmon 256796 2.04-3 2.05-1 252282
Amaya Rodrigo Sastre <amaya@debian.org>
  lirc 260565,267323 0.6.6-7 0.6.6-12 243195 259978
Aurelian Jarno <aurel32@debian.org>
  i2c-old 270481 1:2.7.0-10 1:2.7.0-15 274618
  lm-sensors-old 270482 1:2.7.0-11 1:2.7.0-13 274620
Colin Watson <cjwatson@debian.org>
  trn4 276956 4.0-test76-8 4.0-test76-9 none
Debian Mono Group <pkg-mono-group@lists.alioth.debian.org>
  mcs 268061 0.30.2-1 1.0.2-1 none
  mono 269523 1.0-3 1.0.2-1 256755 257412 262023 272846 259680
  # this has other problems; see the email I sent to bug #269523.
Debian QA Group <packages@qa.debian.org>
  lush 267494 1.0+cvs.2004.02.02 1.0+cvs.2004.05.16 243501
Dirk Eddelbuettel <edd@debian.org>
  octave2.0 271648 2.0.17-7 2.0.17-9 none
Ian Lynagh (wibble) <igloo@debian.org>
  ghc6 276608 6.2.1-4 6.2.2-2 277585
Kevin B. McCarty <kmccarty@princeton.edu>
  cernlib 255970 2004.01.20-1 2004.01.20-8 none
Mark Purcell <msp@debian.org>
  linuxvideostudio 241019 0.1.4-3 0.1.7-1 none
Martin Buck <mbuck@debian.org>
  xview 271313 167054
Mike Furr <mfurr@debian.org>
  vegastrike 233942 0.3.1-5 0.4.1-12 246299
Peter Eisentraut <peter_e@gmx.net>
  postgresql-plruby 271019 0.4.2-1 0.4.2-2 none
Sergio Rua <srua@debian.org>
  partimage 276329 0.6.4-7 0.6.4-10 268248 259523
Stephen Stafford <bagpuss@debian.org>
  distributed-net 177134,258401 2.8015.46-10 2.9008.490-2 162891 251760
Sven Luther <luther@debian.org>
  unicorn 267730,270530 0.8.7-1 0.8.7-1.1 none
Volker Ossenkopf <ossk@ph1.uni-koeln.de>
  workman 271313 1.3.4-16 1.3.4-17 none


Kevin B. McCarty <kmccarty@princeton.edu>   Physics Department
WWW: http://www.princeton.edu/~kmccarty/    Princeton University
GPG public key ID: 4F83C751                 Princeton, NJ 08544

Reply to: