[Debian-ha-maintainers] Bug#981088: pacemaker: crm shell can't be executed due to a library error

[Thorsten Rehm]

Hi Markus,

thanks for the hint about holding and pinning packages. We're aware of
that and did exactly the pinning variant for the pacemaker packages,
after the broken release ;-)
In my opinion the crmsh package should be more strict with the
pacemaker-cli-utils package, if this is a possible option. There is
always an alternative for crmsh, the pcs package. Maybe that's the
reason why the pacemaker package is not so strict with the cli
package.
But that is beyond my knowledge.

Thank you for the support and the update of the package to the current version.

Best regards,
Thorsten

On Thu, 28 Jan 2021 at 18:50, Markus Koschany <apo at debian.org> wrote:
>
> Hello Thorsten,
>
> Am Donnerstag, den 28.01.2021, 14:52 +0100 schrieb Thorsten Rehm:
> > Hi Markus,
> >
> > thank you for your reply.
> > I've installed a fresh Debian Stretch and I think I know why I had
> > such a problem. I believe it's a dependency problem, but I let you
> > decide, if this is the case.
> > We're always installing the packages "pacemaker" and "crmsh" on our
> > systems. As you know, the latter one has a dependency to the
> > "pacemaker-cli-utils" package:
>
> [...]
>
> Indeed the problem could have been avoided if either the pacemaker-cli-utils
> dependency of crmsh or the Recommends: pacemaker-cli-utils in pacemaker was
> more strict. However the general issue here is that you instruct apt to install
> specific packages instead of upgrading the existing ones. If your policy
> forbids upgrades then I suggest to mark packages you don't want to upgrade as
> "on hold" or use apt pinning to change the priority of your packages. Then you
> could still use the upgrade command for the remaining packages. I recommend to
> install security updates though unless you are absolutely sure your
> systems/configurations are not affected. I leave it to the maintainer of
> pacemaker if he wants to tighten the Recommends of pacemaker-cli-utils in the
> future.
>
> Regards,
>
> Markus