Bug#918677: transition: pacemaker
On 16/01/2019 09:11, Ferenc Wágner wrote:
> Emilio Pozuelo Monfort <pochu@debian.org> writes:
>
>> On 15/01/2019 17:23, wferi@niif.hu wrote:
>>
>>> The uploads are done, but the testing migration of pacemaker and pcs
>>> probably deadlocked due to the autopkgtest of the latter. Unstable pcs
>>> needs unstable pacemaker, so they can only go together, which may need
>>> manual intervention on your part.
>>
>> The way this is normally handled is by adding a Breaks on the new pacemaker
>> against the broken pcs. That way the autopkgtests are run for the new pcs
>> version, and britney migrates the two packages at the same time.
>
> If only we knew in advance... But there's a new Pacemaker pre-release
> I'd like to upload; shall I add that Breaks now or just wait until this
> unwrinkles? I don't know when/if you will intervene or pcs will be
> automatically migrated in two days.
It won't migrate due to that autopkgtest failure. It's a bit weird that pcs
hardcodes the pacemaker SONAME, doesn't depend on it, but then requires it for
the autopkgtests? Or so it seems.
So yeah you can add some breaks on pacemaker. Or add them on the new pcs against
the old pacemaker library? Not sure what's the best solution here.
Emilio
Reply to: