|
[Original]
[Print]
[Top]
|
I'm having a bit of a difficulty with gst-plugins. Every time I do an
emerge update, it will either upgrade from gst-plugins-0.8.8-r2 to
0.8.10 or downgrade from 0.8.10 to 0.8.8-r2.
Both packages are needed by different utilities that both are part of
gnome.
If I try putting [media-libs/gst-plugins-0.8.10 in
/etc/portage/package.mask, emerge complains that it's needed by
media-libs/gst-plugins-pango-0.8.8-r1
If I try putting ]=media-libs/gst-plugins-0.8.10 in package.mask, I get
the same complaint for gst-plugins-oss-0.8.10
Adding it to package.provided has no effect -- emerge still wants to
install the one I don't currently have and delete the other.
Anyone know a solution here, except waiting for a new gst-plugins-pango
or never do an rsync again?
--
*Art
|
|
|
[Original]
[Print]
[Top]
|
|
[Original]
[Print]
[Top]
|
Arthur Hagen wrote:
Anyone know a solution here, except waiting for a new
gst-plugins-pango or never do an rsync again?
Choose whether you want the *same* version 0.8.8* or 0.8.10 for all 3
packages. Then, emerge your decided versions, and portage should be
happy.
|
|
[Original]
[Print]
[Top]
|
|
[Original]
[Print]
[Top]
|
Arthur Hagen wrote:
Sorry, no, doesn't work.
All of the packages that directly use gst-plugins or gst-plugins-* are
deep dependencies, so if I remove them and install a specific version,
the wanted version gets reinstalled on the next emerge --update
--deep, and the problem is back.
If you want to go with 0.8.10, then note that
/usr/portage/media-plugins/gst-plugins-pango/gst-plugins-pango-0.8.10.ebuild
is marked unstable, so add it to package.keywords. Otherwise, you will
see the behaviour you describe.
When there's a temporary discrepancy in package dependencies,
the solution is to tell portage (via the files in /etc/portage) which
versions you want. Check the ebuild files in /usr/portage to see what
portage is reasoning.
|
|
|
[Original]
[Print]
[Top]
|
|
[Original]
[Print]
[Top]
|
Paul Bredbury [i@hate-spam.com] wrote:
Arthur Hagen wrote:
Anyone know a solution here, except waiting for a new
gst-plugins-pango or never do an rsync again?
Choose whether you want the *same* version 0.8.8* or 0.8.10 for all 3
packages. Then, emerge your decided versions, and portage should be
happy.
Sorry, no, doesn't work.
All of the packages that directly use gst-plugins or gst-plugins-* are
deep dependencies, so if I remove them and install a specific version,
the wanted version gets reinstalled on the next emerge --update --deep,
and the problem is back.
If I emerge gst-plugins-0.8.10, the next invocation of
"emerge --update --deep world" will switch to 0.8.8-r2, and the next
emerge after that will switch to 0.8.10, and so on, back and forth on
alternating emerges.
Is there an easy way to nest a dependency tree backwards? I've tried
with qdepends -r, but that doesn't seem to work for deep dependencies.
Regards,
--
*Art
|
|
|
[Original]
[Print]
[Top]
|
|
[Original]
[Print]
[Top]
|
Arthur Hagen wrote:
So far, I can't see any stable solutions until either
gst-plugins-pango-0.8.10 is marked stable or gnome and everything
depending on the latest stable gnome is rolled back to a previous
version (which obviously isn't desirable either).
I'd suggest you open a bug against
media-plugins/gst-plugins-pango-0.8.10, mentioning the mask conflict.
Since it's stable on ia64 and sparc with "Zarro Boogs" on bugzilla, the
maintainer is probably just waiting for a tiny trickle of feedback for
the other arches.
|
|
[Original]
[Print]
[Top]
|
|
[Original]
[Print]
[Top]
|
Paul Bredbury [i@hate-spam.com] wrote:
If you want to go with 0.8.10, then note that
/usr/portage/media-plugins/gst-plugins-pango/gst-plugins-pango-
0.8.10.ebuild is marked unstable, so add it to package.keywords.
Otherwise, you will see the behaviour you describe.
I don't want anything marked unstable.
When there's a temporary discrepancy in package dependencies,
the solution is to tell portage (via the files in /etc/portage) which
versions you want.
I've already tried that, as per the first post in this thread. The
problem is that you can't just tell which packages you want if parent
packages depend on specific versions.
Check the ebuild files in /usr/portage to see what portage is
reasoning.
From what I can tell, gnome-2.10.2 is the culprit, in that it requires
two packages that can't coexist on a stable system:
gnome-base/gnome-2.10.2 ]=media-video/totem-1.0.4
gnome-base/gnome-2.10.2 ]=media-libs/gst-plugins-0.8.10
media-video/totem-1.0.4 ]=media-plugins/gst-plugins-pango.0.8.8
In my opinion, gnome-2.10.2 should not have been marked as stable, since
it requires ]=gst-plugins-0.8.10 while gst-plugins-pango doesn't exist
in a stable 0.8.10 version.
Ideally, portage *should* have caught this, instead of playing ping pong
between two versions. See http://bugs.gentoo.org/show_bug.cgi?id=13632
So far, I can't see any stable solutions until either
gst-plugins-pango-0.8.10 is marked stable or gnome and everything
depending on the latest stable gnome is rolled back to a previous
version (which obviously isn't desirable either).
Regards,
--
*Art
|
|
|
[Original]
[Print]
[Top]
|
|
[Original]
[Print]
[Top]
|
Arthur Hagen [art@broomstick.com] wrote:
In my opinion, gnome-2.10.2 should not have been marked as stable, since
it requires ]=gst-plugins-0.8.10 while gst-plugins-pango doesn't exist
in a stable 0.8.10 version.
I agree. I have this problem but with gst-plugins-faad. There are quite
a few gst-plugins still at 0.8.8 so quite a few people could be
experiencing this.
It's been a few days now and there are no bugs against gst-plugins-faad
so I'm going report it against that package in a hope that something
gets done (if the password ever arrives that is).
--
Andy.
|
|
[Original]
[Print]
[Top]
|
|
[Original]
[Print]
[Top]
|
Paul Bredbury [i@hate-spam.com] wrote:
I'd suggest you open a bug against
media-plugins/gst-plugins-pango-0.8.10, mentioning the mask conflict.
Since it's stable on ia64 and sparc with "Zarro Boogs" on bugzilla,
the maintainer is probably just waiting for a tiny trickle of
feedback for the other arches.
Checking, I found a bug filed already.
Still, the gnome maintainers should probably be more careful in not
marking gnome as stable until all dependent subsystems are also stable,
at least until the known portage bug that allows the ping-pong behaviour
has been fixed (which hopefully would have prevented gnome-2.10.2 from
being installed at all while required subsystems need different
versions).
Regards,
--
*Art
|
|
|
[Original]
[Print]
[Top]
|
|
[Original]
[Print]
[Top]
|
In alt.os.linux.gentoo, Paul Bredbury uttered the immortal words:
I'd suggest you open a bug against
media-plugins/gst-plugins-pango-0.8.10, mentioning the mask conflict.
I've done that for gst-plugins-faad (see my other post). It would probably
be a good idea to file a bug for gst-plugins-pango too just to shake the
tree a little.
--
Andy.
|
|
[Original]
[Print]
[Top]
|
|
The content of this page is collected from Linux Forum, All copyrights and other associated rights are reserved by the original authors of the articles.