package libwildmidi-config 0.2.3.4-2.1 failed to install/upgrade: Versuche, »/etc/wildmidi/wildmidi.cfg« zu überschreiben, welches auch in Paket libwildmidi0 0.2.2-3~ppa1~lucid1 ist

Bug #1041765 reported by Tomas Pospisek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wildmidi (Ubuntu)
New
Undecided
Unassigned

Bug Description

During an upgrade 10.04 -> 12.04.1 libwildmidi-config is trying to overwrite files which belong to libwildmidi0

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: libwildmidi-config 0.2.3.4-2.1
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
Date: Sat Aug 25 23:48:41 2012
Dependencies:

DpkgTerminalLog:
 Entpacke libwildmidi-config (aus .../libwildmidi-config_0.2.3.4-2.1_all.deb) ...
 dpkg: Fehler beim Bearbeiten von /var/cache/apt/archives/libwildmidi-config_0.2.3.4-2.1_all.deb (--unpack):
  Versuche, »/etc/wildmidi/wildmidi.cfg« zu überschreiben, welches auch in Paket libwildmidi0 0.2.2-3~ppa1~lucid1 ist
ErrorMessage: Versuche, »/etc/wildmidi/wildmidi.cfg« zu überschreiben, welches auch in Paket libwildmidi0 0.2.2-3~ppa1~lucid1 ist
PackageArchitecture: all
SourcePackage: wildmidi
Title: package libwildmidi-config 0.2.3.4-2.1 failed to install/upgrade: Versuche, »/etc/wildmidi/wildmidi.cfg« zu überschreiben, welches auch in Paket libwildmidi0 0.2.2-3~ppa1~lucid1 ist
UpgradeStatus: Upgraded to precise on 2012-08-25 (0 days ago)

Revision history for this message
Tomas Pospisek (tpo-deb) wrote :
Revision history for this message
Emmet Hikory (persia) wrote :

Thanks for catching this. The Breaks and Replaces need to be extended. I'll test a patch right away.

Revision history for this message
Emmet Hikory (persia) wrote :

Unfortunately, I'm having trouble reproducing the error: while I believe that the issue is that libwildmidi-config should both Breaks and Replaces libwildmidi0 as well as libwildmidi1, I haven't been able to reproduce it, and the PPA versioning makes me wonder if there is something different about the original installed package.

If anyone is able to reproduce this in a lucid->precise upgrade using standard packages, please share the procedure used for reproduction. Alternately, if it is possible to identify the PPA from which the problematic package was produced, I may be able to work with the PPA owner to resolve the issue.

Changed in wildmidi (Ubuntu):
status: New → Incomplete
Revision history for this message
Tomas Pospisek (tpo-deb) wrote :

I'm guessing the package came from this repository here http://ppa.launchpad.net/lucid-bleed/ppa/ubuntu

Since this is not a mainline package feel free to change the bug status as you think best.

Changed in wildmidi (Ubuntu):
status: Incomplete → New
Revision history for this message
Tomas Pospisek (tpo-deb) wrote :

I meant to say:

Since this is not a mainline repository feel free to change the bug status as you think best.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.