Lucid to Precise: must Conflicts and Provides/Break older wildmidi to prevent APT loops during upgrade

a real shame this still isn't fixed

This patch should fix the problem (verification pending). Upgrades to quantal and later have to pass through precise so it's sufficient to fix precise only and be done with it for any later release. From the looks of it, oneiric might be affected as well, though.

The attached patch looks correct to me, and I encourage it's application if anyone can verify it fixes the issue (as noted in other reports of this issue, I have been unable to replicate this at all). Note that *only* lucid->precise upgrades are affected, so this change only needs to be applied to precise. The upgrade path lucid->maverick->natty->oneiric->precise is safe, as is anything post-precise, from precise. Unfortunately, as there were no other changes in wildmidi in quantal, it may be required to push a no-op upload to quantal (without this patch) to ensure a forward progression of updates for precise->quantal->raring (development) upgrades. I expect to push a new upstream to raring, which would provide a larger version for upgrade, but if someone wants to verify and fix this before that happens, please also upload a no-change version-bump to raring to preserve the versions of the upgrade path.

This bug was fixed in the package wildmidi - 0.2.3.4-2.1ubuntu1

---------------
wildmidi (0.2.3.4-2.1ubuntu1) raring; urgency=low

  * No change upload to raring to ensure that the version is newer than
    the one SRUed in precise for lp: #924508
 -- Sebastien Bacher <email address hidden> Fri, 30 Nov 2012 16:16:52 +0100

sponsored to precise: http://launchpadlibrarian.net/124515832/wildmidi_0.2.3.4-2.1precise1_source.changes (waiting for review)

We need a no-change upload for quantal too.

Note to those processing quantal's SRU queue: I used the unconventional version "0.2.3.4-2.1quantal1" in order to be between 0.2.3.4-2.1precise1 in precise and 0.2.3.4-2.1ubuntu1 in raring. Neither is really correct; we should have had something involving the Ubuntu version number rather than codename in precise, and something involving "build1" rather than "ubuntu1" in raring. However, it's too late now for raring, and I don't want to go around again on sponsorship for precise just for this.

Hello Martin-Éric, or anyone else affected,

Accepted wildmidi into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/wildmidi/0.2.3.4-2.1precise1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Martin-Éric, or anyone else affected,

Accepted wildmidi into quantal-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/wildmidi/0.2.3.4-2.1quantal1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

The quantal upload is a no-change upload, and is not intended to fix any bugs. It should be tested only for regression potential, as the bug cannot manifest in quantal with any supported transition.

This bug was fixed in the package wildmidi - 0.2.3.4-2.1quantal1

---------------
wildmidi (0.2.3.4-2.1quantal1) quantal; urgency=low

  * No-change upload to ensure that the version is newer than the one SRUed
    in precise for LP: #924508.
 -- Colin Watson <email address hidden> Mon, 07 Jan 2013 13:45:35 +0000

Reverting unexplained status change.

fix verified for precise

This bug was fixed in the package wildmidi - 0.2.3.4-2.1precise1

---------------
wildmidi (0.2.3.4-2.1precise1) precise-proposed; urgency=low

  * properly fix Replaces and Breaks line. Lucid2Precise. LP: #924508
 -- Rolf Leggewie <email address hidden> Sun, 18 Nov 2012 11:53:24 +0100

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.