[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#926203: marked as done (unblock: pacemaker/2.0.1-2)

Your message dated Tue, 02 Apr 2019 05:42:00 +0000
with message-id <cb9a84ce-27d0-9628-f016-27a712b065b5@thykier.net>
and subject line Re: Bug#926203: unblock: pacemaker/2.0.1-2
has caused the Debian Bug report #926203,
regarding unblock: pacemaker/2.0.1-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
926203: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926203
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock

Please unblock package pacemaker

Dear Release Team,

As reported in #925354, the newly reintroduced pacemaker-dev package
missed Breaks+Replaces against some long-obsolete packages from wheezy,
leading to file conflicts in certain situations.  The version already in
unstable fixes this bug, please unblock it.

Thanks,
Feri.

diff -Nru pacemaker-2.0.1/debian/changelog pacemaker-2.0.1/debian/changelog
--- pacemaker-2.0.1/debian/changelog	2019-03-04 21:34:46.000000000 +0100
+++ pacemaker-2.0.1/debian/changelog	2019-04-01 13:39:28.000000000 +0200
@@ -1,3 +1,19 @@
+pacemaker (2.0.1-2) unstable; urgency=medium
+
+  * [d8939cc] Avoid file conflicts with leftover packages from wheezy.
+    Pacemaker-dev in wheezy was a metapackage pulling in several -dev
+    packages.  It is removed during the jessie dist-upgrade due to
+    dependency problems, and jessie does not have pacemaker at all, so these
+    obsolete -dev packages are left behind, unless replaced by the
+    renamed -dev packages from jessie-backports or later from stretch, both
+    of which requires manual action.  Lacking that, a manual install of the
+    reintroduced pacemaker-dev from buster will try to overwrite headers
+    from those obsolete -dev packages causing file conflicts, because the
+    old Breaks+Replaces relations weren't carried over from the stretch
+    packages. (Closes: #925354)
+
+ -- Ferenc Wágner <wferi@debian.org>  Mon, 01 Apr 2019 13:39:28 +0200
+
 pacemaker (2.0.1-1) unstable; urgency=medium
 
   * [7d6ff2e] New upstream release (2.0.1)
diff -Nru pacemaker-2.0.1/debian/control pacemaker-2.0.1/debian/control
--- pacemaker-2.0.1/debian/control	2019-03-04 21:30:38.000000000 +0100
+++ pacemaker-2.0.1/debian/control	2019-03-29 09:06:28.000000000 +0100
@@ -332,6 +332,10 @@
  liblrmd-dev (<< 2),
  libpengine-dev (<< 2),
  libstonithd-dev (<< 2),
+# header ghosts from wheezy, where pacemaker-dev used to exist:
+ libcrmcluster1-dev,
+ libcrmcommon2-dev,
+ libpengine3-dev,
 Replaces:
  libcib-dev (<< 2),
  libcrmcluster-dev (<< 2),
@@ -340,6 +344,10 @@
  liblrmd-dev (<< 2),
  libpengine-dev (<< 2),
  libstonithd-dev (<< 2),
+# header ghosts from wheezy, where pacemaker-dev used to exist:
+ libcrmcluster1-dev,
+ libcrmcommon2-dev,
+ libpengine3-dev,
 Description: cluster resource manager development
  ${S:X-Common-Description}
  .

unblock pacemaker/2.0.1-2

--- End Message ---
--- Begin Message --- 
Ferenc Wágner:
> Package: release.debian.org
> Severity: normal
> User: release.debian.org@packages.debian.org
> Usertags: unblock
> 
> Please unblock package pacemaker
> 
> Dear Release Team,
> 
> As reported in #925354, the newly reintroduced pacemaker-dev package
> missed Breaks+Replaces against some long-obsolete packages from wheezy,
> leading to file conflicts in certain situations.  The version already in
> unstable fixes this bug, please unblock it.
> 
> Thanks,
> Feri.
> 
> [...]
> 
> unblock pacemaker/2.0.1-2
> 

Unblocked, thanks.
~Niels

--- End Message ---
Reply to: