libosmesa6 conflicts with libglapi-mesa-lts-*

Status changed to 'Confirmed' because the bug affects multiple users.

After enabling the Hardware Enablement Stack for Trusty shipped with 14.04.2, I am experiencing the same issue, when trying to install build dependencies for various packages, f.e. vtk using "sudo apt-get build-dep vtk"

Nobody you wants the full range of devel packages should go anywhere near 14.04.2 or install the lts-utopic mesa packages on a 14.04 or 14.04.1 install
It's just a decent case of fubar
(- another example - freeglut3-dev

libosmesa6/trusty-updates 10.1.3-0ubuntu0.3 amd64 can't be installed because it depends on libglapi-mesa (= 10.1.3-0ubuntu0.3), but libglapi-mesa-lts-utopic/trusty-updates,trusty-security 10.3.2-0ubuntu1~trusty2 amd64 is 10.3.2-0ubuntu1 not 10.1.3-0ubuntu0.3.

So utopic's libosmesa6 needs to be backported to match the new libglapi-mesa.

Status changed to 'Confirmed' because the bug affects multiple users.

Anyone know of a workaround for this?

"Anyone know of a workaround for this?"
Do a fresh install using the 14.04.1 image from Ubuntu old-releases.
If needing for some reason a newer mesa then use a ppa like xorg-edgers fresh X crack or oibaf

I just run into this bug. It also is present with vivid version of LTS enablement stack.

uploaded a new mesa-lts-vivid to

https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging

seems to work for me, please confirm

I can confirm that the mesa-lts-vivid Timo uploaded to his PPA (10.5.9-2ubuntu1~trusty3~ppa1) includes the corresponding vivid's libosmesa(-dev) packages. I can now install the dependencies needed to build f. e. vtk without any problems (see answer #3). Great to see that this annoying bug is solved!

a bit of background: libosmesa in precise didn't depend on libglapi-mesa which meant it wasn't necessary to provide a renamed one for precise lts stacks..

uploaded mesa-lts-vivid for trusty-proposed

Hello Doug, or anyone else affected,

Accepted mesa-lts-vivid into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa-lts-vivid/10.5.9-2ubuntu1~trusty3 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!

I enabled trusty-proposed and gave the uploaded mesa-lts-vivid (10.5.9-2ubuntu1~trusty3) a try. I can confirm that the corresponding vivid's libosmesa(-dev) packages are now included and that I am able to install the dependencies needed to build f. e. vtk without any problems (see answers #3 and #11). Great to see that this annoying bug is solved!

I'm not sure this is the right way to fix it, since it wouldn't allow packages that depend on libosmesa6 to be installed, because versioned Provides is not supported there... that would need fixing the stock mesa to build libosmesa statically so that it wouldn't depend on libglapi-mesa.

Hello Doug, or anyone else affected,

Accepted mesa into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/10.1.3-0ubuntu0.5 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!

Installed fine in 14.04.3 (using hwe vivid stack), both the lib & -dev packages
Also allowed desmume to install & open

Upgraded to Vivid HWE and enabling the proposed repository fixed the issue for me.

What are you all doing here??, twice released to trusty-proposed under same name? & then after 2nd verification deleted

This bug was fixed in the package mesa - 10.1.3-0ubuntu0.5

---------------
mesa (10.1.3-0ubuntu0.5) trusty; urgency=medium

  * Build osmesa separately and without using shared glapi again.
    (LP: #1424059)

 -- Timo Aaltonen <email address hidden> Thu, 17 Sep 2015 11:35:21 +0300

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