Hi Thomas and everybody, > On 11/28/2015 03:08 PM, Charles Plessy wrote: > > > > In the case of cloud images, wouldn't that problem be solved by pinning the > > backports suite at a low priority, and pinning the installed backports > > (cloud-init, etc.) at a higher priority ?
Le Sat, Nov 28, 2015 at 09:23:31PM +0100, Thomas Goirand a écrit : > > Even with such pinning, the problem you mentioned would remain, no? Not the same, but still a problem. If stable-backports is pinned to -1, packages will not be installed even if they are not in the base suite, but there will be no updates. Then, if a package, (for instance cloud-init) is installed and pinned at 100 while the whole suite is at -1, it is possible to update it, unless it depends on other backports. So in the worse case scenario, important updates can not be applied. There may be one more solution, which would be to ship a package in jessie-backports, that would drop a file in /etc/apt/preferences.d, that would ensure that everything cloud-related is pinned appropriately. I am quite sure this is not the way to go. > On 11/28/2015 03:08 PM, Charles Plessy wrote: > > > > More in general, it seems to me that the best solution to allow enabling > > backports by default would be to change APT's behaviour so that > > installation of > > new packages from the backports suite always require that the suite is > > explicitely selected. Does somebody know if this has already been discussed > > somewhere ? Le Sat, Nov 28, 2015 at 09:23:31PM +0100, Thomas Goirand a écrit : > > I'd also would like this feature to be added to APT (with a possible > option for it). I started a discussion on the debian-backports mailing list. Let's see how it goes. <https://lists.debian.org/debian-backports/2015/11/msg00067.html> Have a nice day, -- Charles Plessy Debian Med packaging team, http://www.debian.org/devel/debian-med Tsurumi, Kanagawa, Japan