Dear Debian Games Team, The following possible problem(s) were detected in the package(s) you maintain in Debian:
=== attal: = A newer upstream version exists for this package (or your watch file is broken): upstream: 1.0-rc1 Debian: 1.0~rc1+cvs20080318-1 === attal-themes: = A newer upstream version exists for this package (or your watch file is broken): upstream: 1.0-rc1 Debian: 1.0~rc1+cvs20080318-1 === boson: = This package has 1 bug(s) that should be fixed for the next Debian release: - #471153 <http://bugs.debian.org/471153> boson: FTBFS with python2.5 on amd64 Bug part of a release goal: python2.5 support = This package has not been in testing for 25 days. If things don't change, it won't be part of lenny! See <http://release.debian.org/migration/testing.pl?package=boson> === chromium: = This package has 2 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 - #467123 <http://bugs.debian.org/467123> chromium: contains code which is not modifiable This is a Release-Critical bug! = This package has not been in testing for 565 days. If things don't change, it won't be part of lenny! See <http://release.debian.org/migration/testing.pl?package=chromium> === 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 565 days. If things don't change, it won't be part of lenny! See <http://release.debian.org/migration/testing.pl?package=chromium-data> === clanlib: = This package has 1 bug(s) that should be fixed for the next Debian release: - #372272 <http://bugs.debian.org/372272> clanlib: FTBFS: bashisms in build scripts Bug part of a release goal: switch /bin/sh to dash = This package has not been in testing for 11 days. If things don't change, it won't be part of lenny! See <http://release.debian.org/migration/testing.pl?package=clanlib> === droidbattles: = A newer upstream version exists for this package (or your watch file is broken): upstream: 1.0.7 Debian: 1.0.6-6 === enet: = A newer upstream version exists for this package (or your watch file is broken): upstream: 1.2 Debian: 1.1-2 === 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 === 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 65 days. If things don't change, it won't be part of lenny! See <http://release.debian.org/migration/testing.pl?package=gnome-chess> === kball: = A newer upstream version exists for this package (or your watch file is broken): upstream: _16dec2004 Debian: 0.0.20041216-4 === kraptor: = A newer upstream version exists for this package (or your watch file is broken): upstream: _jan_26_2003 Debian: 0.0.20040403-4 === 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 === lordsawar: = This package has not been able to migrate from unstable to testing for 58 days. = A newer upstream version exists for this package (or your watch file is broken): upstream: 0.0.9 Debian: 0.0.8-1 See <http://release.debian.org/migration/testing.pl?package=lordsawar> === 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 === ogre: = This package has not been able to migrate from unstable to testing for 211 days. = A newer upstream version exists for this package (or your watch file is broken): upstream: 1-4-7 Debian: 1.4.6.dfsg1-1 See <http://release.debian.org/migration/testing.pl?package=ogre> === 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 === scorched3d: = A newer upstream version exists for this package (or your watch file is broken): upstream: 41.3 Debian: 41.2dfsg-1 === stormbaancoureur: = A newer upstream version exists for this package (or your watch file is broken): upstream: 2.1.3 Debian: 2.1.1-1 === 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 === vegastrike: = This package has 2 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! - #473300 <http://bugs.debian.org/473300> vegastrike: Cannot start: libboost_python-gcc41-1_34_1.so.1.34.1 not found This is a Release-Critical bug! = This package has not been in testing for 1035 days. If things don't change, it won't be part of lenny! See <http://release.debian.org/migration/testing.pl?package=vegastrike> === warzone2100: = This package has 1 bug(s) that should be fixed for the next Debian release: - #458275 <http://bugs.debian.org/458275> beta releases should not migrate to testing This is a Release-Critical bug! = This package has not been in testing for 244 days. If things don't change, it won't be part of lenny! See <http://release.debian.org/migration/testing.pl?package=warzone2100> This is an automated mail. These mails are sent monthly. For more information about these mails, refer to http://wiki.debian.org/qa.debian.org/DdpoByMail We are sorry if this mail was useless for you. If you think it was avoidable (that we can detect easily that the problems weren't actually problems), please reply to it and let us know. If you don't want to receive this type of mail any more, you can reply to this mail and use one of the following commands at the beginning of the mail: - unsubscribe <email> You will no longer receive any mail for any package - ignore <package> <email> You will no longer receive information about that package in those mails. So if that package is the only one with problems, you won't receive anything. - ignore <bug> <email> You will no longer receive information about this bug. All commands are manually processed, but you will receive confirmation. The commands are just here so that we know precisely what you want. A more detailed status of your packages is available from the DDPO. See: http://qa.debian.org/[EMAIL PROTECTED] Don't hesitate to reply to this mail if you have questions. The wiki page will be updated with useful information. -- DDPOMail, run by Lucas Nussbaum _______________________________________________ Pkg-games-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/pkg-games-devel
