Bug#784859: Workaround considered annoying at best
Control: clone -1 -2 Control: retitle -2 Unsuitable for stable without proper maintenance Control: block -2 by 766449 Hi, On Fri, Sep 18, 2015 at 01:08:53PM +0200, Andreas Beckmann wrote: > On 2015-09-18 11:36, "David Prévot" wrote: > At least this "workaround" seems to have worked in the past. Again, as previously pointed on this bug report, an upgrade to a newer upstream version of its dependency (e.g., for security reason) in stable will make this package uninstallable for no good reason. > I don't mind doing rebuild-only QA uploads (since arch:all cannot be > binNMUed), but I don't care about (or even use) ampache at all. Then please don’t: keeping an outdated and unmaintained version of some PHP scripts without anyone caring if it actually works or is secure is not a service to our users. > Please retitle the bug according to your wishes, right now it just calls > for a rebuild. It definitely doesn’t and there is more than a title in a bug report. Anyway, cloning to expose the other problem pointed in this bug report. Regards David signature.asc Description: PGP signature
Processed: Re: Bug#784859: Workaround considered annoying at best
Processing control commands: > clone -1 -2 Bug #784859 [ampache-common] Uninstallable in Sid: too strict version constraints Bug 784859 cloned as bug 801116 > retitle -2 Unsuitable for stable without proper maintenance Bug #801116 [ampache-common] Uninstallable in Sid: too strict version constraints Changed Bug title to 'Unsuitable for stable without proper maintenance' from 'Uninstallable in Sid: too strict version constraints' > block -2 by 766449 Bug #801116 [ampache-common] Unsuitable for stable without proper maintenance 801116 was not blocked by any bugs. 801116 was not blocking any bugs. Added blocking bug(s) of 801116: 766449 -- 784859: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=784859 801116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801116 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#784859: Workaround considered annoying at best
Hi, > On Wed, 16 Sep 2015 10:23:24 -0400 David =?UTF-8?Q?Pr=C3=A9vot?= >wrote: >> unarchive 784859 >> # Rebuilding is a workaround, it does *not* address the problem. >> reopen 784859 > > AFAICT rebuilding with an updated toolchain actually got rid of the > strict versioning (without changing something in the package itself): > > Package: ampache Youre not even looking at the right package, and no: Package: ampache-common Source: ampache Version: 3.6-rzb2752+dfsg-6 [ ] Depends: fonts-freefont-ttf (<< 20120503.0~), fonts-freefont-ttf (>= 20120503), libjs-prototype (<< 1.7.1.0~), libjs-prototype (>= 1.7.1), libphp-phpmailer (<< 5.2.10+dfsg.0~), libphp-phpmailer (>= 5.2.10+dfsg), libphp-snoopy (<< 2.0.0.0~), libphp-snoopy (>= 2.0.0), php-getid3 (<< 1.9.9+dfsg.0~), php-getid3 (>= 1.9.9+dfsg), php-gettext (<< 1.0.11.0~), php-gettext (>= 1.0.11) The next transition of any of these dependencies will be blocked by this unmaintained and out of date ampache package. Keeping it in the archive as is is considered harmful. Regards David
Bug#784859: Workaround considered annoying at best
On 2015-09-18 11:36, "David Prévot" wrote: >> Package: ampache > > You’re not even looking at the right package, and no: > > Package: ampache-common Oops ... right, that tells a different story. At least this "workaround" seems to have worked in the past. I don't mind doing rebuild-only QA uploads (since arch:all cannot be binNMUed), but I don't care about (or even use) ampache at all. > The next transition of any of these dependencies will be blocked by this > unmaintained and out of date ampache package. Keeping it in the archive as > is is considered harmful. Please retitle the bug according to your wishes, right now it just calls for a rebuild. Andreas