After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 166460 - [packaging] gstreamer-deps yum repository for FC3 incompatible with Fedora Extras
[packaging] gstreamer-deps yum repository for FC3 incompatible with Fedora Ex...
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: packages
0.8.8
Other Linux
: Normal normal
: NONE
Assigned To: Thomas Vander Stichele
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-02-06 16:14 UTC by D. D. Brierton
Modified: 2005-09-17 15:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description D. D. Brierton 2005-02-06 16:14:03 UTC
Distribution/Version: Fedora Core 3

yum is subscribed to the following repositories:

Fedora Core
Fedora Core updates released
Fedora Extras
Livna Stable
Livna Testing
Livna Unstable
gstreamer
gstreamer-deps

Attempting yum update fails. Yum wants to update liboil to 0.3 from Extras, but
swfdec from gstreamer-deps requires liboil 0.2:

Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package liboil.i386 0:0.3.0-1 set to be updated
--> Running transaction check
--> Processing Dependency: liboil-0.2.so.0 for package: swfdec
--> Finished Dependency Resolution
Error: missing dep: liboil-0.2.so.0 for pkg swfdec

$ rpm -q swfdec
swfdec-0.3.1-0.lvn.1.3

Why is the swfdec misleadingly named *.lvn.*.rpm? Very confusing. It makes it
look like it's a Livna package.

Anyway, now Fedora Extras is official I expect most FC3 users will stop using
the old fedora.us FC2 repository and move over to the offical Fedora Extras. I
guess you maybe can't repackage until Livna rebuild against Fedora Extras
instead of against fedora.us. But I thought you should know about the
incompatability.
Comment 1 Thomas Vander Stichele 2005-09-17 15:38:14 UTC
this has been fixed.  reopen if still a problem.