Description of problem: The version of mesa in mga is 8.0.2. Bug fix release 8.0.3 is available. Release notes: http://www.mesa3d.org/relnotes-8.0.3.html Version-Release number of selected component (if applicable): Version 8.0.2 to be updated to version 8.0.3
Please commiter, note that we have 8.0.2-2.mga2 in core, and 8.0-1.mga2.tainted in tainted so we need anyway an update for fix that ihmo
CC: (none) => anssi.hannula, dmorganec, fundawang, mageia, pterjan, thierry.vignaud, tmb
Yes I noticed there is conflicting versions of mesa and mesa-tainted. And I second an update to this new 8.0.3 version. thanks Simon/Lemonzest
CC: (none) => lemonzest
CC: (none) => hhielscher
Summary: Update request: Bug fix release of mesa available => Update request: Bug fix release of mesa available (fix for different version tainted/core)
8.0.4 is out now
Keywords: (none) => Junior_job
Why is mesa in tainted? Do we have a list of IP-issues?
Just look at its description, it's explained. It's mainly about compressed textures which use S3TC format which is patented. Hence it's not done in mesa but in txc-dxtn library which in tainted. The tainted build of mesa just pull this library in order to enable support for compressed textures.
Tainted has float buffer support, s3tc seems to be in the non-tainted build (using it with lib64xtc and its working fine), float textures are a requirement for opengl 3.0 + and is patented :(
So there is a need for a tainted version. At least for the next 20 years. But still those two versions should be of the same version. Is there any reason for them not to be of the same version?
No. The one who updated it last forgot to do it. Anyway, anybody can push the mesa-8.0.4 into */update_testing
there is also a CVE-2012-2864 being discussed upstream: http://www.mail-archive.com/mesa-dev@lists.freedesktop.org/msg25207.html https://bugzilla.redhat.com/show_bug.cgi?id=851006
Keywords: Junior_job => (none)Component: RPM Packages => SecuritySummary: Update request: Bug fix release of mesa available (fix for different version tainted/core) => Update request: Bug fix release of mesa available (fix for different version tainted/core), CVE-2012-2864 fix pending...
I need update for my tainted mesa version to Mageia 2 x86_64, because some features chromium-browser don't work with the core version.
CC: (none) => frateraec
I've uploaded 8.0.4 to both core & tainted's updates_testing
Blocks: (none) => 7381
I installed 8.0.4 tainted for test! Mageia 2 x86_64
Blocks: 7381 => (none)
This bug is a mix of several different issues. The update for Mageia 2 is now in Bug 7381. We'll leave this bug for the issues in Cauldron.
CC: (none) => luigiwalserVersion: 2 => CauldronSummary: Update request: Bug fix release of mesa available (fix for different version tainted/core), CVE-2012-2864 fix pending... => Mesa: fix for different version tainted/core, CVE-2012-2864 fix pending...
(In reply to comment #13) > This bug is a mix of several different issues. > > The update for Mageia 2 is now in Bug 7381. > > We'll leave this bug for the issues in Cauldron. This one has _nothing_ what so ever to do with Cauldron, it ia a Mga2 only issue (including the CVE), was tracked and will be resolved with the mesa update goining out...
Version: Cauldron => 2Depends on: (none) => 7381
(In reply to comment #14) > (In reply to comment #13) > > This bug is a mix of several different issues. > > > > The update for Mageia 2 is now in Bug 7381. > > > > We'll leave this bug for the issues in Cauldron. > > This one has _nothing_ what so ever to do with Cauldron, > it ia a Mga2 only issue (including the CVE), was tracked > and will be resolved with the mesa update goining out... Just goes to show how confusing this bug is. I thought it said the core/tainted version mismatch also affected Cauldron. I don't believe the CVE is fixed in Cauldron, but if you don't want a bug for that, then this is just a duplicate now. *** This bug has been marked as a duplicate of bug 7381 ***
Status: NEW => RESOLVEDDepends on: 7381 => (none)Resolution: (none) => DUPLICATE
(In reply to comment #15) > Just goes to show how confusing this bug is. I thought it said the > core/tainted version mismatch also affected Cauldron. Well, a cauldron only mismatch is usually detected pretty fast, and will simply be re-submitted when needed... > I don't believe the CVE > is fixed in Cauldron, but if you don't want a bug for that, then this is just a > duplicate now. > It's fixed in the current snapshot waiting to be built: mesa-9.0.0-0.git20120906.1.mga3