Am Thu, 13 Aug 2015 15:18:26 +0200 schrieb forum::für::umläute <zmoel...@umlaeute.mur.at>:
> while i haven't followed the bug that required a fix that breaks > functionality you need, it seems to me that the correct solution would > be to spend time fixing the regression (while at the same time keeping > the fix for the original bug intact). To clarify: This was me, mpg123 upstream, following-up to the announcement of the new release on the mpg123-users list that fixes the regression (1.22.4), precisely because … > and distributions will hopefuly distribute the fixed version (without > the regression), rather than an outdated version. … distributions tend to keep the old base version of packages around and carry patches where it is deemed necessary. In the case of Debian, this affects wheezy (oldstable): mpg123 1.14.4-1 jessie (stable): mpg123 1.20.1-2 stretch (testing): mpg123 1.22.2-1 I suppose stretch will upgrade to 1.22.4 soon-ish, but wheezy and jessie likely want to stay on the 1.14.x and 1.20.x feature series. That's about exactly the range of versions affected by the regression, so I provided a little script to make patching them up easy. It's a 3-line change, but a plain patch would differ subtly between the versions. While my policy is to keep each new mpg123 superior and compatible to the previous version, it is exactly the case of unintended regressions that can creep in that still gives a good argument for not always going with the latest & greatest. Even an actual undisputed improvement in user behaviour might not be wanted when the promise to the user is that things are stable and do not change where it is not required to fix bugs / vulnerabilities. Alrighty then, Thomas
pgpCWMlnKd2QM.pgp
Description: Digitale Signatur von OpenPGP
_______________________________________________ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers