Fedora 17 Update Problem

[Magickman]

I am having a small problem with Apper and Yum, and Updates in general. If I use only the official Fedora repos, I have no updates. But if I engage the rpmfusion repos, Apper cannot install the updates called for. RPMFusion was working fine when I used Easylife to install java, media codecs, and media players, it went exceptionally fast too. What gives? Anyone know?

[glennzo]

What errors are you getting? Something to do with gvfs?

[DBelton]

Are you getting a lot of dependency problems with rpmfusion packages?

like this?


Packages skipped because of dependency problems:
avidemux-2.5.6-6.fc17.x86_64 from rpmfusion-free
avidemux-cli-2.5.6-6.fc17.x86_64 from rpmfusion-free
avidemux-gtk-2.5.6-6.fc17.x86_64 from rpmfusion-free
avidemux-libs-2.5.6-6.fc17.x86_64 from rpmfusion-free
avidemux-qt-2.5.6-6.fc17.x86_64 from rpmfusion-free
ffmpeg-0.10.2-1.fc17.x86_64 from rpmfusion-free
ffmpeg-devel-0.10.2-1.fc17.x86_64 from rpmfusion-free
ffmpeg-libs-0.10.2-1.fc17.x86_64 from rpmfusion-free
gstreamer-ffmpeg-0.10.13-2.fc17.x86_64 from rpmfusion-free
gstreamer-plugins-ugly-0.10.18-7.fc17.x86_64 from rpmfusion-free
gstreamer-plugins-ugly-devel-docs-0.10.18-7.fc17.noarch from rpmfusion-free
libquicktime-1.2.3-6.fc17.x86_64 from rpmfusion-free
live555-0-0.36.2012.02.04.fc17.x86_64 from rpmfusion-free
mencoder-1.0-0.135.20120205svn.fc17.x86_64 from rpmfusion-free
mplayer-1.0-0.135.20120205svn.fc17.x86_64 from rpmfusion-free
mplayer-common-1.0-0.135.20120205svn.fc17.x86_64 from rpmfusion-free
mplayer-gui-1.0-0.135.20120205svn.fc17.x86_64 from rpmfusion-free
mplayer-tools-1.0-0.135.20120205svn.fc17.x86_64 from rpmfusion-free
phonon-backend-vlc-0.5.0-2.fc17.x86_64 from rpmfusion-free
vlc-2.0.0-5.fc17.x86_64 from rpmfusion-free
vlc-core-2.0.0-5.fc17.x86_64 from rpmfusion-free
vlc-devel-2.0.0-5.fc17.x86_64 from rpmfusion-free
vlc-extras-2.0.0-5.fc17.x86_64 from rpmfusion-free
vlc-plugin-jack-2.0.0-5.fc17.x86_64 from rpmfusion-free
x264-libs-0.120-3.20120303.fc17.x86_64 from rpmfusion-free
xine-lib-extras-freeworld-1.1.20.1-2.fc17.x86_64 from rpmfusion-free


I have been getting those for about a week now :(

[caf4926]

I updated F17 without issue
Not using rpmfusion though

[AndrewSerk]

I have been getting those for about a week now :(

FYI: I just installed those packages on a i686 f17 today without issue.

[caf4926]

For the record
I'm _64 on my eeepc

[DBelton]

FYI: I just installed those packages on a i686 f17 today without issue.


I need to look at my errors more and see what is happening. The updates hit right at the time when they were switching from rawhide to the regular repos, and I think something may have gotten mixed up due to that. I just haven't had a good time to dig into it and see what's going on yet.

[Magickman]

Yeah, happened to me agin with this moring's updates. Dependancy problems, cannot install due to broken packages. I used the command yum --skip-broken update to get the updaes.
I think this will go away when Fedora 17 is a full Release and not in Beta stage. Until then, this is a good workaround.

[j0534ng31]

Yeah, happened to me agin with this moring's updates. Dependancy problems, cannot install due to broken packages.

Me too... Today, I have a bunch of updates pending, but yum cannot find "PackageKit-qt-0.7.4-1.fc17.x86_64 (updates-testing)" :C

--> Resolución de dependencias finalizada
Error: Paquete: apper-0.7.1-3.fc17.x86_64 (@updates-testing)
Necesita: libpackagekit-qt2.so.2()(64bit)
Eliminando: PackageKit-qt-0.7.3-1.fc17.x86_64 (@anaconda-0)
libpackagekit-qt2.so.2()(64bit)
Actualizado por: PackageKit-qt-0.7.4-1.fc17.x86_64 (updates-testing)
No encontrado

One little question... Is there a fast way to change the language for those shell commands? I mean, I would like to post those error messages in plain english, but I don't know if there is a way to do that (appart from translating myself one by one)... :doh:

Thank you.

[Haber_Nir]

wait for the next updates . they probley (like always) fix it with the next updates

[DBelton]

for the PackageKit-qt problem, you can do


yum --exclude=PackageKit* --skip-broken update


That will allow you to get the other updates out there.

[Magickman]

Thanks, that worked like a charm.

[idoitprone]

Umm I think you have the same problem as me

I think you have to clean your yum cache

mmmmm yum cache

yum clean all

then do

yum update

For a couple of weeks I was wondering why was I not getting updates on a beta

[tuxor]

One little question... Is there a fast way to change the language for those shell commands? I mean, I would like to post those error messages in plain english, but I don't know if there is a way to do that (appart from translating myself one by one)... :doh:

Try to put "LANG=C" in front of your command line. If you call the command with sudo, put it in front of the "sudo":

# LANG=C yum update

or

$ LANG=C sudo yum update

And by the way, I don't have any problems with broken dependencies. Maybe there is something wrong with your RPMDB or with your yum installation. idoitprone's suggestion sounds pretty good...

[hadrons123]

I maybe wrong. I did not recieve any update in the last 3 days. I 'm using f17 TC2. yum returns without an update.

[tuxor]

@hadrons123
Fedora's updates-testing repository has been automatically disabled a few days ago for users of F17. And as far as I know, there will be as little updates as possible in the "updates" repository till the final release on May 22. So no wonder you didn't get any updates in the last few days. But I'm using Fedora 17 for two or three weeks now and didn't have a single broken dependency during that time.

In general, I can't understand why so many people are ranting about Fedora 17 being so unstable and unusable. For me, it has been working great for weeks now. And the only thing I really don't like is the wallpaper :C

And concerning new features: There are good reasons to upgrade: xorg-x11-drv-synaptics 1.6 (finally full multi touch and clickpad support for notebook touchpads), qemu 1.0, GIMP 2.8, a dedicated symbol for activated VPN connections in Gnome-Shell and I have my old boot time of 7 seconds (don't know what made the change here though ...).

What I would have loved to have is TexLive 2012: http://fedoraproject.org/wiki/Features/TeXLive But it's okay for now sticking with the extra repository.

[hadrons123]

@hadrons123
Fedora's updates-testing repository has been automatically disabled a few days ago for users of F17. And as far as I know, there will be as little updates as possible in the "updates" repository till the final release on May 22. So no wonder you didn't get any updates in the last few days. But I'm using Fedora 17 for two or three weeks now and didn't have a single broken dependency during that time.

In general, I can't understand why so many people are ranting about Fedora 17 being so unstable and unusable. For me, it has been working great for weeks now. And the only thing I really don't like is the wallpaper :C

And concerning new features: There are good reasons to upgrade: xorg-x11-drv-synaptics 1.6 (finally full multi touch and clickpad support for notebook touchpads), qemu 1.0, GIMP 2.8, a dedicated symbol for activated VPN connections in Gnome-Shell and I have my old boot time of 7 seconds (don't know what made the change here though ...).

What I would have loved to have is TexLive 2012: http://fedoraproject.org/wiki/Features/TeXLive But it's okay for now sticking with the extra repository.

you did not have issue, good for you.

But I had issues with broken dependecies, for many packages and updates, which is so unlike fedora, even for a beta. Don't say we are ranting without a valid reason.

[j0534ng31]

Try to put "LANG=C" in front of your command line. If you call the command with sudo, put it in front of the "sudo":

# LANG=C yum update

or

$ LANG=C sudo yum update

And by the way, I don't have any problems with broken dependencies. Maybe there is something wrong with your RPMDB or with your yum installation. idoitprone's suggestion sounds pretty good...

Thank you! :D

[AlexDudko]

Due to dependency issues I can’t install gcc, for instance.

[tuxor]

gcc is installed on both of my F17 machines (i686 and x86_64). Which packages conflict with gcc?

[AlexDudko]

gcc is installed on both of my F17 machines (i686 and x86_64). Which packages conflict with gcc?

Here's the output:

# yum install gcc
Loaded plugins: langpacks, presto, refresh-packagekit
Resolving Dependencies
--> Running transaction check
---> Package gcc.i686 0:4.7.0-4.fc17 will be installed
--> Processing Dependency: libgomp = 4.7.0-4.fc17 for package: gcc-4.7.0-4.fc17.i686
--> Processing Dependency: cpp = 4.7.0-4.fc17 for package: gcc-4.7.0-4.fc17.i686
--> Processing Dependency: glibc-devel >= 2.2.90-12 for package: gcc-4.7.0-4.fc17.i686
--> Processing Dependency: cloog-ppl >= 0.15 for package: gcc-4.7.0-4.fc17.i686
--> Processing Dependency: libmpc.so.2 for package: gcc-4.7.0-4.fc17.i686
--> Running transaction check
---> Package cloog-ppl.i686 0:0.15.11-3.fc17.1 will be installed
--> Processing Dependency: libppl_c.so.4 for package: cloog-ppl-0.15.11-3.fc17.1.i686
--> Processing Dependency: libppl.so.9 for package: cloog-ppl-0.15.11-3.fc17.1.i686
---> Package cpp.i686 0:4.7.0-4.fc17 will be installed
---> Package gcc.i686 0:4.7.0-4.fc17 will be installed
--> Processing Dependency: libgomp = 4.7.0-4.fc17 for package: gcc-4.7.0-4.fc17.i686
---> Package glibc-devel.i686 0:2.15-35.fc17 will be installed
--> Processing Dependency: glibc-headers = 2.15-35.fc17 for package: glibc-devel-2.15-35.fc17.i686
--> Processing Dependency: glibc-headers for package: glibc-devel-2.15-35.fc17.i686
---> Package libmpc.i686 0:0.9-2.fc17.2 will be installed
--> Running transaction check
---> Package gcc.i686 0:4.7.0-4.fc17 will be installed
--> Processing Dependency: libgomp = 4.7.0-4.fc17 for package: gcc-4.7.0-4.fc17.i686
---> Package glibc-headers.i686 0:2.15-35.fc17 will be installed
---> Package ppl.i686 0:0.11.2-8.fc17 will be installed
--> Processing Dependency: libpwl.so.5 for package: ppl-0.11.2-8.fc17.i686
--> Running transaction check
---> Package gcc.i686 0:4.7.0-4.fc17 will be installed
--> Processing Dependency: libgomp = 4.7.0-4.fc17 for package: gcc-4.7.0-4.fc17.i686
---> Package ppl-pwl.i686 0:0.11.2-8.fc17 will be installed
--> Finished Dependency Resolution
Error: Package: gcc-4.7.0-4.fc17.i686 (fedora)
Requires: libgomp = 4.7.0-4.fc17
Installed: libgomp-4.7.0-5.fc17.i686 (@updates-testing)
libgomp = 4.7.0-5.fc17
Available: libgomp-4.7.0-4.fc17.i686 (fedora)
libgomp = 4.7.0-4.fc17
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest

[tuxor]

This is a very simple problem that sometimes occurs due to the automatic disabling of the updates-testing repository. It doesn't have anything to do with anything specific for Fedora 17.

If you want updates-testing to stay disabled, you probably don't mind having a slightly older version of libgomp from the standard "fedora" repository. Thus you can simply solve your problem by "yum downgrade libgomp".

[AlexDudko]

This is a very simple problem that sometimes occurs due to the automatic disabling of the updates-testing repository. It doesn't have anything to do with anything specific for Fedora 17.

If you want updates-testing to stay disabled, you probably don't mind having a slightly older version of libgomp from the standard "fedora" repository. Thus you can simply solve your problem by "yum downgrade libgomp".

Thank you, I know about this solution. But other packages are dependent on the package from testing repo, and if I downgrade there are other dependency issues. Actually I decided that there are no dependency problems only with pure LXDE, which I'm using at the moment.
Dependency problem started just after I'd tried to install OpenOffice 3.4 several days ago. Since then I ran into a dependency issue every here and there. Now I deleted everything which caused problems and it turned out there was no GUI left. So I installed LXDE (minimal) in terminal and now it seems stable and doesn't cause dependency issues.

---------- Post added at 10:52 PM ---------- Previous post was at 10:30 PM ----------

It seems updates-testing repository was inabled once by default and I have installed quite a number of packages then, after that it was disabled by some update, since then the issue started to appear. I've downgraded all testing packages and now the system seems to work as it should to.

[tuxor]

It seems updates-testing repository was inabled once by default and I have installed quite a number of packages then, after that it was disabled by some update, since then the issue started to appear. I've downgraded all testing packages and now the system seems to work as it should to.

That's what I tried to explain. It's simply a conceptual problem of the direct transit from prerelease to release state without reinstall. There has to be one certain point in time when updates-testing must be disabled when release date comes nearer. And it's a problematic task to decide what to do at this point with packages that were installed from updates-testing before that date.

And as I said, the only sensible solution is to downgrade all packages from updates-testing. This decision has to be left to the user though and the user is an experienced user in most cases, because we are talking about a user who is installing an unstable pre-release operating system. I think, Fedora's way of handling this problem is pretty professional.

If in your case "other packages are dependent on the package from testing repo", the obvious solution will be to reenable updates-testing manually... But you neither did this, nor took the step of downgrading _all_ affected packages. So of course you ran into bigger problems .....

[mschwendt]

It's actually pretty easy to just run yum distro-sync and let Yum figure out which packages need to be downgraded.