Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 59059

Summary: gstreamer ebuild changes from stable to ~ on hourly basis
Product: Gentoo Linux Reporter: Sebastian <sebastian_ml>
Component: New packagesAssignee: Gentoo Linux Gnome Desktop Team <gnome>
Status: RESOLVED DUPLICATE    
Severity: normal CC: scandium
Priority: High    
Version: unspecified   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Sebastian 2004-08-01 03:24:33 UTC
Hello,

yesterday I emerge rsynced and emerge -uD world showed gnome 2.6.2. Great. Installed it right away. Early in the morning I rsynced again, and it wanted to uninstall the gstreamer it emerged some hours ago. Ok. Today, after rsync, it wants to reinstall it? What's happening? Why does it seem that gstreamer-0.8.3-r3 is stable and in a minute it's ~x86?

Greets

Sebastian 

emerge -uD world -pv

These are the packages that I would merge, in order:

Calculating world dependencies ...done!
[ebuild     UD] media-libs/gstreamer-0.8.1 [0.8.3-r1] -debug -debug -debug  1,149 kB
[ebuild     UD] media-libs/gst-plugins-0.8.1 [0.8.2] +alsa -debug -debug -debug -debug -esd -oss  1,767 kB

Total size of downloads: 2,917 kB


Reproducible: Always
Steps to Reproduce:
1.
2.
3.




emerge info
Portage 2.0.50-r9 (default-x86-2004.0, gcc-3.3.3, glibc-2.3.3.20040420-r0,
2.6.7-gentoo-r11)
=================================================================
System uname: 2.6.7-gentoo-r11 i686 Intel(R) Pentium(R) M processor 1400MHz
Gentoo Base System version 1.4.16
distcc 2.13 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled]
Autoconf: sys-devel/autoconf-2.59-r4
Automake: sys-devel/automake-1.8.3
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CFLAGS="-O3 -march=pentium3 -mmmx -msse -msse2 -mfpmath=sse -fomit-frame-pointer
-pipe"
CHOST="i686-pc-linux-gnu"
COMPILER="gcc3"
CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config
/usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config
/usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/
/usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/
/usr/share/texmf/xdvi/ /var/qmail/control"CONFIG_PROTECT_MASK="/etc/gconf
/etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=pentium3 -mmmx -msse -msse2 -mfpmath=sse
-fomit-frame-pointer -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs ccache distcc sandbox"
GENTOO_MIRRORS="ftp://mirrors.sec.informatik.tu-darmstadt.de/gentoo/
http://mirrors.sec.informatik.tu-darmstadt.de/gentoo/
http://128.213.5.34/gentoo/ http://gentoo.mirror.sdv.fr"
MAKEOPTS="-j5"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY=""
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="berkdb gdbm mmx ncurses nls pam perl pwdb python readline sse ssl tcpd x86
zlib"

blood root #
Comment 1 Paul Kronenwetter 2004-08-01 08:11:44 UTC
My first thought would be to be sure you're using the same portage mirror on each sync.  It's possible, though less likely with the new timestamp feature in portage, that the mirror you happened to hit sometimes was out-of-sync.

Just a thought.
Comment 2 Rainer Größlinger (RETIRED) gentoo-dev 2004-08-01 09:26:32 UTC
It's also possible that the newly stabled gnome requires >0.8.1 but you still have something else installed (like nautilus-media IIRC) that depends on =0.x.x, that would create a circular dependency.

I have seen this problem on another box, too, so I think it'S a circular dep, I havn't checked yet, though.
Comment 3 Sebastian 2004-08-01 09:33:40 UTC
For 24 hours? And only gstreamer affected? Sounds a bit strange to me...

Sebastian
Comment 4 Spider (RETIRED) gentoo-dev 2004-08-01 09:43:13 UTC
Basically it was an issue with only parts of gst-plugins-*  that went stable in the first run, this caused the "old" dependencies to want old version of gst-plugins and gstreamer.


Does this still persist?

*** This bug has been marked as a duplicate of 59052 ***
Comment 5 Paul Kronenwetter 2004-08-01 12:55:28 UTC
My weirdness agrees with the description of bug #59052.