Ferenc Wágner: > Package: release.debian.org > Severity: normal > User: release.debian....@packages.debian.org > Usertags: unblock > > Dear Release Team, > > Please advise about the situation with Pacemaker. > > At the moment pacemaker_2.0.1~rc5-1 is 6 days old in unstable (it was > uploaded on the day following its release) and now that it finally built > on all architectures (it triggered a linker bug on amd64) I expect it to > migrate to testing this week, well before the full freeze. > > However, Pacemaker 2.0.1 final was released today and includes a single > code change only, with the following commit message (the change itself > is the deletion of lines at the end of the debdiff below): > > High: libcrmcommon: complete interrupted live migrations correctly > > 8435966 (2.0.0) got the sense of compare_version() wrong when > attempting to remove the old behavior for recording partial live > migrations, instead re-introducing it. > > This causes a regression in behavior when a transition containing a > live migration is aborted after the migrate_to has been initiated > but before the migrate_from has been initiated. In that case, it > would schedule a full start on the destination node rather than a > migrate_from. > > I think we should release buster with Pacemaker 2.0.1, thus with this > fix and the small documentation fixes also bundled with it. The added > include directives just make previously indirect includes explicit, and > our build doesn't use the abi-check script, so that change is a no-op. > Full debdiff from 2.0.1~rc5-1 (which is on its way to testing): > > [...] > > Even if I uploaded 2.0.1-1 now, it would miss the freeze date by a day, > kicking out 2.0.1~rc5-1 as well, which would be quite a shame, > considering that it's almost as good as the final, and definitely better > than 2.0.1~rc4-1 currently in testing. Could you please provide a way > for 2.0.1-1 final (not uploaded yet) to reach buster? > > Thanks, > Feri. > > unblock pacemaker/2.0.1-1 >
Hi Feri, Thanks for filing the report. Please let the current version of pacemaker as it is and then ping us on this bug once it have. Thanks, ~Niels