package installation failure because of oxide codecs

Bug #1399597 reported by Timo Jyrinki
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apt (Ubuntu)
New
Undecided
Unassigned
oxide-qt (Ubuntu)
Confirmed
Medium
Unassigned
ubuntu-touch-meta (Ubuntu)
Fix Released
Critical
Unassigned
unity-scope-click (Ubuntu)
Invalid
High
Unassigned

Bug Description

The last packaging change upload (https://code.launchpad.net/~bzoltan/oxide/packaging.vivid-improved-conflicts/+merge/243515) broke autopkgtests of many packages that try to install Oxide during preparation of the environment.

See for example https://jenkins.qa.ubuntu.com/job/vivid-adt-qtcreator-plugin-ubuntu/lastBuild/ARCH=amd64,label=adt/console

This prevents migration of several packages.

---
Unpacking oxideqt-codecs:amd64 (1.3.5-0ubuntu4) ...
dpkg: considering removing oxideqt-codecs:amd64 in favour of oxideqt-codecs-extra:amd64 ...
dpkg: oxideqt-codecs:amd64 is not properly installed; ignoring any dependencies on it
dpkg: yes, will remove oxideqt-codecs:amd64 in favour of oxideqt-codecs-extra:amd64
---
Setting up oxideqt-codecs-extra:amd64 (1.3.5-0ubuntu4) ...
dpkg: error processing package oxideqt-codecs (--configure):
 no package named `oxideqt-codecs' is installed, cannot configure
---
Errors were encountered while processing:
 oxideqt-codecs
E: Sub-process /usr/bin/dpkg returned an error code (1)

Because of this it'll be reverted until a better solution is offered.

Related branches

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote : Re: The last oxide upload breaks autopkgtests with a package installation failure

https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-003/+packages has the revert, but also if a fix is found it can be done there.

description: updated
summary: - The last oxide upload breaks autopkgtests
+ The last oxide upload breaks autopkgtests with a package installation
+ failure
description: updated
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Dependency chain:
qtcreator-plugin-ubuntu -> ubuntu-sdk -> ubuntu-sdk-libs -> oxideqt-codecs-extra. oxideqtcodecs-extra conflicts with oxideqt-codecs (and it already did before the upload, now it's just arch specific).

Is it apt getting confused with the complex dependencies and conflicts? Or is something specifically depending on oxideqt-codecs while the ubuntu-sdk-libs requires oxideqt-codecs-extra?

I can't reproduce the actual problem seen on the autopkgtest runners locally.

Revision history for this message
Olivier Tilloy (osomon) wrote :

Is it expected that ubuntu-sdk-libs depends on oxideqt-codecs-extra? Couldn’t it just depend on liboxideqt-qmlplugin?

Revision history for this message
Zoltan Balogh (bzoltan) wrote :

In my view (could be wrong thou) the problem is when a package has both

    oxideqt-codecs-extras

and

    oxideqt-codecs | oxideqt-codecs-extras

packages in the dependency tree. As the apt first selects the packages to install, but the codecs unselects the already selected extras packages ...but the setup phase of the apt does not know about this change of the "plans"

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Ok, we have a new proposal / idea. It's building now in landing-003 with version number 1.3.5-0ubuntu6. Please land it during US Friday if ok, since it'd then unblock (hopefully) everything that is currently in the vivid-proposed pocket.

Debdiff from the current vivid archive version (causing this bug) attached.

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Adding a possible apt task, it shouldn't try to configure a package that was already removed.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package oxide-qt - 1.3.5-0ubuntu6

---------------
oxide-qt (1.3.5-0ubuntu6) vivid; urgency=medium

  * Use the new conflict arrangement still, but change the dependency
    order of Oxide's own codecs packages to prefer the -extras.
    This should hopefully solve the problem when setting up the
    autopkgtest environment with packages that have a hard depedency
    on the -extras package. (LP: #1399597)
 -- Timo Jyrinki <email address hidden> Fri, 05 Dec 2014 13:39:34 +0000

Changed in oxide-qt (Ubuntu):
status: New → Fix Released
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

This needs reverting. It will result in -extras being pulled in to the desktop seed, which is not acceptable

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

:( The ubuntu6 was approved by a core-dev on IRC. I originally asked people to get this sorted out during US timezone Friday, but it didn't get forward and more landings were stuck in -proposed.

I filed bug #1400275 as the continuation bug. Please add in there why desktop shouldn't depend on the oxideqt-codecs-extra package, since I see they are both in main.

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Reopened, suggested fix at bug #1400275 again brings this problem back.

Changed in oxide-qt (Ubuntu):
status: Fix Released → Confirmed
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

Marking this as critical as it prevents packages in http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html from migrating to vivid-release (unity-scope-click autopkgtest regressions).

Changed in oxide-qt (Ubuntu):
importance: Undecided → Critical
Changed in ubuntu-touch-meta (Ubuntu):
importance: Undecided → Critical
Changed in unity-scope-click (Ubuntu):
importance: Undecided → Critical
Changed in ubuntu-touch-meta (Ubuntu):
status: New → Invalid
Changed in ubuntu-touch-meta (Ubuntu):
status: Invalid → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntu-touch-meta - 1.207

---------------
ubuntu-touch-meta (1.207) vivid; urgency=medium

  * Refreshed dependencies
  * Added oxideqt-codecs-extra to touch
  * Removed oxideqt-codecs-extra from sdk-libs (LP: #1399597)
 -- Colin Watson <email address hidden> Thu, 18 Dec 2014 10:57:34 +0000

Changed in ubuntu-touch-meta (Ubuntu):
status: New → Fix Released
Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote : Re: unity-scope-click autopkgtests with a package installation failure because of oxide codecs

This was now fixed by moving oxideqt-codecs-extra from sdk to touch meta package.

Remaining issues:
- unity-scope-click should query the available frameworks manually (or via click if a feature arrives) instead of depending on ubuntu-sdk-libs directly
- oxide-qt could optionally have an alternatives system to managing the codecs packages instead of conflicting, to prevent possible similar future issues

summary: - The last oxide upload breaks autopkgtests with a package installation
- failure
+ unity-scope-click autopkgtests with a package installation failure
+ because of oxide codecs
Changed in oxide-qt (Ubuntu):
importance: Critical → Medium
Changed in unity-scope-click (Ubuntu):
importance: Critical → High
Revision history for this message
Colin Watson (cjwatson) wrote :

Note that unity-scope-click already does query frameworks dynamically (it would be nice if it used the API call that's been available in libclick for some time, but it isn't necessary to do that for the purposes of this bug). I think it should just drop the dependency, since it's not unity-scope-click's business to specify this, it should depend on the context in which that package is being installed.

Revision history for this message
Timo Jyrinki (timo-jyrinki) wrote :

All three cases summarized in bug #1400275 work now:
- vivid target SDK works as intended
- autopkgtests work
- correct codecs package is on the desktop (and also correct one on touch)

However, it was just pointed out this current setup generates a very similar problem during image building, with same symptoms that the autopkgtests originally had:

https://launchpadlibrarian.net/192991440/buildlog_ubuntu_vivid_armhf_ubuntu-touch_FAILEDTOBUILD.txt.gz

summary: - unity-scope-click autopkgtests with a package installation failure
- because of oxide codecs
+ package installation failure because of oxide codecs
Revision history for this message
dobey (dobey) wrote :

Is there some other way to depend on the frameworks files actually being installed on the system, without a dep on ubuntu-sdk-libs? The dep was added because the frameworks files being present on disk are necessary for the scope to work correctly, as otherwise it will appear the scope is completely broken, and we'll get bug reports about the scope not showing any available apps when it gets installed in certain contexts.

I see no valid reason why ubuntu-sdk-libs should be removed as a dependency. It should never be uninstallable, and it provides files which are vital to the functionality of the click store scope. By definition, the dependency is correct.

dobey (dobey)
Changed in unity-scope-click (Ubuntu):
status: New → Invalid
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.