On Thu, Apr 19, 2018 at 11:26:20AM -0400, Greg Wooledge wrote: > > According to http://packages.debian.org/pacemaker there is also a > backport of the stretch version of the package in the jessie-backports > repository. So perhaps there is some way to convince the jessie upgrade > to use the jessie-backports version of this package rather than removing > it. But that's beyond my experience. >
I totally forgot about backports. Generally, including backports repositories of the upgrade target (i.e., the suite being upgraded to) is not a good idea. However, this situation would qualify as extenuating circumstances. Plus, someone who manages a HA cluster almost certainly has the skills to deal with the occasional minor hiccup assocaited with mixing backports into an upgrade. The only thing I would say is use apt "pinning" to prioritize the backports repository lower than the other repositories so you don't accidentally get backports for *everything* that has a backport available. Regards, -Roberto -- Roberto C. Sánchez
