As summary. While gst-plugin-faad is still at 0.8.8 but my system is calling for gst-plugins version 0.8.10 I get an upgrade/downgrade loop on gst-plugins. Reproducible: Always Steps to Reproduce: 1. emerge -Duav world 2. gst-plugins gets upgraded to 0.8.10 3. emerge -Duav world again 4. gst-plugins gets downgraded to 0.8.8 5. goto 1 and repeat ad infinitum
*** Bug 104259 has been marked as a duplicate of this bug. ***
I'm having the same problem now with gnome 2.12.0. That depends on gst-plugins-0.8.11 but the .0.8.10 plugins (gst-plugins-faad-0.8.10 for example) depends on gst-plugins-0.8.10. Maybe gst-plugins should state it depends on all plugins with the same version number?
*** Bug 112047 has been marked as a duplicate of this bug. ***
*** Bug 113096 has been marked as a duplicate of this bug. ***
Ping! Someone please fix this stuff already, it happening over and over again, now also w/ 0.8.11. :-(
gst-plugins-faad-0.8.11 has been there since Sept 5. The gst-plugins-faad packages have the same stable and ~ versions as gst-plugins. I get no upgrade/downgrade cycle. Nothing in the main portage tree specifically deps on an old version of gst-plugins-faad. I'm convinced there is not problem here. Rhythmbox has a commented out dep on 0.8*, maybe it's dep was updated without a revbump? If so, try re-emerging rhythmbox.
i cant see the bug, sorry
OK, reopen, it's back again with next version bump. Portage does *not* handle the below construct in gst-plugins.eclass. It's too restrictive and is causing dependency resolver to produce weird circular dependencies - i.e., gst-plugins-foo-0.10.1 depends on gst-plugins-foo-0.10.0* <snip> MY_P=gst-plugins-${PV} RDEPEND="=media-libs/${MY_P}*" </snip>
*** Bug 120015 has been marked as a duplicate of this bug. ***
*** Bug 120040 has been marked as a duplicate of this bug. ***
gst-plugins-ogg-0.8.11 is still ~x86 while most of gst-plugins-*-0.8.11 stuff is marked stable, that causes all loop mess for me.
I can add gst-plugins-flac, gst-plugins-cdparanoia, gst-plugins-mad, gst-plugins-vorbis and gst-plugins-gnomevfs to *-0.8.11 ~x86 list
Well, since there are such stupid dependencies, then all the plugins must be commited at the same time with all needed keywords. That said, software that needs dependencies like =0.10.1* is broken by design, and comment #8 about portage not handling such stuff is still valid.
The version bump has been there for a while. Closing this bug.
Same thing happens with 0.8.11/0.8.12. Please reopen.
Er, never mind. I'd forgotten to ~ some plugins =P