lmms package asks for older lmms-common, but newer lmms-common is already installed

Bug #1152807 reported by Len Ovens
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lmms (Ubuntu)
Fix Released
Undecided
Unassigned
Precise
Fix Released
Undecided
Israel Dahl

Bug Description

(edited for SRU candidate clarity)

[Impact]
upgrade from lmms 0.4.13 to 0.4.14 fails because it depends on lmms-common (= 0.4.13-0ubuntu1) but lmms-common is already upgraded to 0.4.14-0ubuntu2.

Apt-get upgrade gives this error:

The following packages have unmet dependencies:
 lmms : Depends: lmms-common (= 0.4.13-0ubuntu1) but 0.4.14-0ubuntu2 is installed

[Test case]
From any Ubuntu version prior to 12.10, install lmms, and then attempt a distribution upgrade to the immediately proceeding stable release, e.g.,
  11.10 -> 12.04
  12.04 -> 12.10

[Regression potential]
Low - there is no source code alteration, and everything present in a newer version of lmms-common can accommodate older versions of lmms.

Related branches

Revision history for this message
Len Ovens (len-ovenwerks) wrote :
Revision history for this message
Howard Chan (smartboyhw) wrote :

I will be fixing this bug.

Changed in lmms (Ubuntu):
status: New → Confirmed
assignee: nobody → Howard Chan (smartboyhw)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lmms - 0.4.14-0ubuntu3

---------------
lmms (0.4.14-0ubuntu3) raring; urgency=low

  * Make lmms depend on lmms-common (>= ${source:Version}) instead of
    only = to fix (LP: #1152807)
 -- Howard Chan <email address hidden> Sun, 10 Mar 2013 15:21:43 +0800

Changed in lmms (Ubuntu):
status: Confirmed → Fix Released
Daniel T Chen (crimsun)
description: updated
summary: - lmms packge asks for older lmms-common, but new lmms-common is installed
+ lmms package asks for older lmms-common, but newer lmms-common is
+ already installed
Daniel T Chen (crimsun)
Changed in lmms (Ubuntu Precise):
status: New → In Progress
assignee: nobody → Israel Dahl (israeldahl)
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello Len, or anyone else affected,

Accepted lmms into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/lmms/0.4.10-2ubuntu1.1 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!

Changed in lmms (Ubuntu Precise):
status: In Progress → Fix Committed
tags: added: verification-needed
Revision history for this message
Javier López (javier-lopez) wrote :

I didn't find any issue upgrading lmms from Ubuntu Precise to Ubuntu Quantal, the report tell 'upgrade from lmms 0.4.13 to 0.4.14 fails because it depends on lmms-common (= 0.4.13-0ubuntu1) but lmms-common is already upgraded to 0.4.14-0ubuntu2.0', however, Ubuntu Precise | Quantal have a lower version: 0.4.10

Not sure why a -proposed update was made:

This is the information of my Precise box before the dist update:

$ apt-cache policy lmms
lmms:
  Installed: 0.4.10-2ubuntu1
  Candidate: 0.4.10-2ubuntu1
  Version table:
 *** 0.4.10-2ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ precise/universe i386 Packages
        100 /var/lib/dpkg/status

$ rmadison lmms
      lmms | 0.3.1-1ubuntu2 | hardy/universe | source, amd64, hppa, i386, ia64, lpia, powerpc, sparc
      lmms | 0.4.5-0ubuntu2 | lucid/universe | source, amd64, armel, i386, ia64, powerpc, sparc
      lmms | 0.4.10-1ubuntu3 | oneiric/universe | source, amd64, armel, i386, powerpc
      lmms | 0.4.10-2ubuntu1 | precise/universe | source, amd64, armel, armhf, i386, powerpc
      lmms | 0.4.10-2ubuntu1.1 | precise-proposed/universe | source, amd64, armel, armhf, i386, powerpc
      lmms | 0.4.10-2.3ubuntu1 | quantal/universe | source, amd64, armel, armhf, i386, powerpc
      lmms | 0.4.14-0ubuntu3 | raring/universe | source, amd64, armhf, i386, powerpc
      lmms | 0.4.14-0ubuntu3 | saucy/universe | source, amd64, armhf, i386, powerpc

Then while updating the distro (no errors):

Preparing to replace lmms 0.4.10-2ubuntu1 (using .../lmms_0.4.10-2.3ubuntu1_i386.deb) ...
Unpacking replacement lmms ...
Preparing to replace lmms-common 0.4.10-2ubuntu1 (using .../lmms-common_0.4.10-2.3ubuntu1_all.deb) ...
Unpacking replacement lmms-common

After the upgrade (I used do-release-upgrade to do it):

$ cat /etc/issue
Ubuntu 12.10 \n \l

$ apt-cache policy lmms
lmms:
  Installed: 0.4.10-2.3ubuntu1
  Candidate: 0.4.10-2.3ubuntu1
  Version table:
 *** 0.4.10-2.3ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ quantal/universe i386 Packages
        100 /var/lib/dpkg/status

With no issues, therefore I'm marking this as verification-failed.

tags: added: verification-failed
removed: verification-needed
Israel Dahl (israeldahl)
tags: added: verification-needed
removed: verification-failed
Revision history for this message
Israel Dahl (israeldahl) wrote :

Hi Javier this is an issue regarding some people that had upgraded during the Beta phase of Raring. When we were working to get an updated bug fixed version of lmms in the repos I had gotten 0.4.13 in, but had incorrectly made the .desktop file installed by lmms-common, but later fixed it in 0.4.14 (the version released in Raring). Unfortunately the description of the bug doesn't reflect this. I am sorry. If you think that this is invalid still because there are potentially no more Raring users who haven't upgraded lmms from an earlier Beta (which is most likely the case) mark it accordingly. If this has been verified to not exist anymore I guess the bug should be closed as completed, and not included in the SRU report. I don't think the bug is present in people upgrading from 12.10 to 13.04, either because 13.04 has the correct desktop file (which is what will be in the SRU). 0.4.10 installs, but has no menu/dash/launcher icon because it has no .desktop file, because the lmms.install file is missing the path to install the desktop file.
Thanks so much for your help I appreciate it!

Revision history for this message
Brian Murray (brian-murray) wrote :

I installed lmms from precise-proposed and was able to upgrade to Quantal without a problem so I am setting this to verification-done.

tags: added: verification-done
removed: verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package lmms - 0.4.10-2ubuntu1.1

---------------
lmms (0.4.10-2ubuntu1.1) precise-proposed; urgency=low

  * Backported changes from 13.04's packaging:
    - installed desktop file so that the program is noticeable to users
      (LP: #863366);
    - adjusted versioned dependency on -common so that package upgrades
      can succeed (LP: #1152807).
 -- Daniel T Chen <email address hidden> Thu, 25 Apr 2013 11:16:48 -0400

Changed in lmms (Ubuntu Precise):
status: Fix Committed → Fix Released
Revision history for this message
Colin Watson (cjwatson) wrote : Update Released

The verification of the Stable Release Update for lmms 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.

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.