Bug#773149: marked as done (unblock: x52pro/0.1.1-2.2 (pre-approval))
Your message dated Sat, 10 Jan 2015 13:16:06 +0100
with message-id <20150110121605.GC19033@ugent.be>
and subject line Re: Bug#773149: what to do with x52pro???
has caused the Debian Bug report #773149,
regarding unblock: x52pro/0.1.1-2.2 (pre-approval)
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.)
--
773149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773149
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: what to do with x52pro???
- From: Andreas Beckmann <anbe@debian.org>
- Date: Mon, 15 Dec 2014 02:40:12 +0100
- Message-id: <20141215014012.12335.95443.reportbug@zam581.zam.kfa-juelich.de>
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
x52pro has been neglected after its initial maintainer upload and a
single NMU in 2011.
x52pro | 0.1.1-2.1 | wheezy | source
x52pro | 0.1.1-2.1 | sid | source
It has no rdepends in either wheezy or sid.
It can be installed and removed in wheezy without problems.
It is uninstallable in sid and therefore has been removed from testing.
(#767675)
But here comes the problem: It cannot be removed from jessie or sid if it
was installed in wheezy and thereafter the system was distupgraded.
(#773147)
This is likely caused by the maintainer script calling udevadm which
seems to have changed behavior ...
I would suggest the following:
* reintroduce the packages libx52pro0 and libx52pro-dev as dummy
packages into jessie: no files, no scripts (or only empty scripts if
needed for smooth upgrades - to have the new script succeed after the
old one failed)
* there will be a clear upgrade path, this ensures the bad old scripts
are gone and the dummy packages can be removed from jessie without
problems
* a (new) RC bug will be filed against the (soon to be) crippled
package in sid to keep it out of stretch
If this seems acceptable, I can prepare the dummy packages and send a
debdiff.
Andreas
--- End Message ---
--- Begin Message ---
Hi,
On Thu, Jan 08, 2015 at 02:01:09AM +0100, Andreas Beckmann wrote:
> Uploaded.
Unblocked.
Cheers,
Ivo
--- End Message ---
Reply to: