Bug#764982: Backports removed from sources.list ;-(
control reopen -1
stop
On Sun, Apr 19, 2015 at 05:44:12PM +0200, Paul van der Vlis wrote:
> Hello,
>
> I saw backports has been removed as default setting from sources.list in
> Jessie RC3. I am very disappointed by this last minute change, without
> much discussion so far I know. I did not know about this bug.
BR reopened for futher discussion.
from the changelog:
| Changes:
| apt-setup (1:0.97) unstable; urgency=medium
| .
| * Stop enabling backports by default (Closes: #764982). Rationale:
| - Packages in the base suite are preferred to the ones in the
| backports suite so one needs to specifically ask for the version
| from backports.
| - That isn't true for packages which are only available in the
| backports suite.
| This means one could possibly install such packages without even
| noticing they're not fetched from the base suite; and that seems
| a dangerous default.
That "danger" is installing an old package.
That "danger" only occures when there is NO new package.
A "bigger danger", a bigger disadvantage,
is NOT getting the package installed.
(not getting a package installed that _is available_ in backports )
The "danger" is no danger, the "bigger danger" is.
> In my opinion it's very good when backports is default in sources.list.
Typical use cases for having backports enabled:
* Package became available after the release ( this will happen more and more )
* Package was too late for the freeze ( that has happend allready )
About the
| This means one could possibly install such packages without even
| noticing they're not fetched from the base suite; and that seems
| a dangerous default.
There is much doubt in 'could possibly' and 'seems a dangerous default'
Please go beyond the doubt and install available packages.
And let us find out which packages are missing in the base suite.
Groeten
Geert Stappers
--
Leven en laten leven
Reply to: