[Fwd: Some of your Debian packages might need attention] - Current Package Statuses
>Dear Debian Games Team,
The following possible problem(s) were detected in the package(s)
you maintain in Debian:
=== a7xpg:
= This package has not been able to migrate from unstable
to testing for 33 days.
See <http://release.debian.org/migration/testing.pl?package=a7xpg>
Not built on ARM, should it?
=== adanaxisgpl:
= This package has 1 bug(s) that should be fixed for the next Debian release:
- #463389 <http://bugs.debian.org/463389>
Missing dependency on adanaxisgpl-data
This is a Release-Critical bug!
New release in svn and on mentors fixes this.
=== ceferino:
= This package has not been able to migrate from unstable
to testing for 59 days.
See <http://release.debian.org/migration/testing.pl?package=ceferino>
Not built on mips, mipsel.
=== chromium:
= This package has 1 bug(s) that should be fixed for the next Debian release:
- #459056 <http://bugs.debian.org/459056>
chromium: FTBFS with dash: ./configure: 22: source: not found
Bug part of a release goal: switch /bin/sh to dash
= This package has not been in testing for 509 days.
If things don't change, it won't be part of lenny!
See <http://release.debian.org/migration/testing.pl?package=chromium>
Waiting on chromium-data, see below.
=== chromium-data:
= This package has 1 bug(s) that should be fixed for the next Debian release:
- #385115 <http://bugs.debian.org/385115>
chromium-data: Unclear license for some files
This is a Release-Critical bug!
= This package has not been in testing for 509 days.
If things don't change, it won't be part of lenny!
See <http://release.debian.org/migration/testing.pl?package=chromium-data>
Licensing issues. Is anyone working on this? Definitely not my area of expertise.
=== fretsonfire:
= A newer upstream version exists for this package (or your watch file
is broken):
upstream: 1.2.512 Debian: 1.2.451.dfsg-2
512 is in SVN. Is it going to get uploaded?
=== gfpoken:
= This package has 1 bug(s) that should be fixed for the next Debian release:
- #460042 <http://bugs.debian.org/460042>
gfpoken: gimp script fails on alpha
This is a Release-Critical bug!
= This package has not been able to migrate from unstable
to testing for 85 days.
See <http://release.debian.org/migration/testing.pl?package=gfpoken>
I think Bas is working heavily on this package?
=== gnome-chess:
= This package has 1 bug(s) that should be fixed for the next Debian release:
- #424339 <http://bugs.debian.org/424339>
gnome-chess: FTBFS if built twice in a row
Bug part of a release goal: double compilation support
= This package has not been in testing for 9 days.
If things don't change, it won't be part of lenny!
See <http://release.debian.org/migration/testing.pl?package=gnome-chess>
Fixed. Too new for testing.
=== gunroar:
= This package has not been able to migrate from unstable
to testing for 33 days.
See <http://release.debian.org/migration/testing.pl?package=gunroar>
Not yet built on ARM.
=== jugglemaster:
= This package has not been in testing for 13 days.
If things don't change, it won't be part of lenny!
See <http://release.debian.org/migration/testing.pl?package=jugglemaster>
Not yet built on mipsel.
=== kball:
= A newer upstream version exists for this package (or your watch file
is broken):
upstream: _16dec2004 Debian: 0.0.20041216-4
Fixed in SVN. Is someone going to upload this?
=== kraptor:
= A newer upstream version exists for this package (or your watch file
is broken):
upstream: _jan_26_2003 Debian: 0.0.20040403-4
Upstream naming is hosed. Would take some significant upstream version mangling.
=== late:
= This package has 1 bug(s) that should be fixed for the next Debian release:
- #424494 <http://bugs.debian.org/424494>
late: FTBFS if built twice in a row
Bug part of a release goal: double compilation support
Three bugs fixed in SVN. I've put a new upload on mentors: http://mentors.debian.net/debian/pool/main/l/late/late_0.1.0-11.dsc
=== lordsawar:
= A newer upstream version exists for this package (or your watch file
is broken):
upstream: 0.0.7 Debian: 0.0.4-1
Already in the archive. False positive? (Probably hasn't hit testing yet, too new).
=== moaggedit:
= This package has 1 bug(s) that should be fixed for the next Debian release:
- #424575 <http://bugs.debian.org/424575>
moaggedit: FTBFS if built twice in a row
Bug part of a release goal: double compilation support
Fixed in SVN and new package on mentors: http://mentors.debian.net/debian/pool/main/m/moaggedit/moaggedit_0.5-4.dsc
=== neverball:
= This package has 1 bug(s) that should be fixed for the next Debian release:
- #459114 <http://bugs.debian.org/459114>
neverball: FTBFS with dash: find: debian/never{ball-common,ball-data,putt}/usr/share/games: No such file or directory
Bug part of a release goal: switch /bin/sh to dash
Should already be fixed in the repository.. False positive??
=== nikwi:
= A newer upstream version exists for this package (or your watch file
is broken):
upstream: src Debian: 0.0.20060823-1
Upstream tarball naming blows. No idea how you would do this. Probably should drop the watch file?
=== ogre:
= This package has not been able to migrate from unstable
to testing for 155 days.
= A newer upstream version exists for this package (or your watch file
is broken):
upstream: 1-4-6 Debian: 1.4.5-3
See <http://release.debian.org/migration/testing.pl?package=ogre>
Someone is working heavily on this aren't they?
=== openarena-data:
= This package has 1 bug(s) that should be fixed for the next Debian release:
- #448921 <http://bugs.debian.org/448921>
openarena-data recommends unmet openarena (>= 0.7.1) | openarena-server (>= 0.7.1)
Bug part of a release goal: no unmet recommends
There is supposedly a new 0.7.1 upstream of openarena. Is someone working on this??
=== pokerth:
= This package has not been able to migrate from unstable
to testing for 45 days.
See <http://release.debian.org/migration/testing.pl?package=pokerth>
Someone is working on this.
=== qonk:
= A newer upstream version exists for this package (or your watch file
is broken):
upstream: 0.3.1 Debian: 0.3.0-2
Just about ready to upload. I'm working on the gcc-4.3 patch and I'd like to fix the bitstream font issue.
=== rrootage:
= This package has not been able to migrate from unstable
to testing for 135 days.
= A newer upstream version exists for this package (or your watch file
is broken):
upstream: x86-bin-0.23a Debian: 0.23a-6
See <http://release.debian.org/migration/testing.pl?package=rrootage>
Watch file fixed in SVN.
=== scorched3d:
= A newer upstream version exists for this package (or your watch file
is broken):
upstream: 41.3 Debian: 41.2dfsg-1
Already in SVN.
=== torus-trooper:
= This package has not been in testing for 28 days.
If things don't change, it won't be part of lenny!
See <http://release.debian.org/migration/testing.pl?package=torus-trooper>
Not yet built on arm.
=== ultrastar-ng:
= A newer upstream version exists for this package (or your watch file
is broken):
upstream: 0.2.1 Debian: 0.1.4-2
In SVN.
=== val-and-rick:
= This package has not been able to migrate from unstable
to testing for 33 days.
See <http://release.debian.org/migration/testing.pl?package=val-and-rick>
Not yet built on ARM.
=== vegastrike:
= This package has 1 bug(s) that should be fixed for the next Debian release:
- #449475 <http://bugs.debian.org/449475>
src/cmd/collide/prapid.* cannot be distributed
This is a Release-Critical bug!
= This package has not been in testing for 979 days.
If things don't change, it won't be part of lenny!
See <http://release.debian.org/migration/testing.pl?package=vegastrike>
Is anyone working on this anymore?
=== warzone2100:
= This package has 1 bug(s) that should be fixed for the next Debian release:
- #458275 <http://bugs.debian.org/458275>
warzone2100: SVN snapshots should not migrate to testing
This is a Release-Critical bug!
= This package has not been in testing for 188 days.
If things don't change, it won't be part of lenny!
See <http://release.debian.org/migration/testing.pl?package=warzone2100>
Dunno about this one.
<snip>
If anyone could review/sponsor/upload any of the ones on mentors, I would appreciate it!!
Thanks,
Barry deFreese
Reply to: