There's one package that I can't get upgraded, and it's driving me up the wall because every time I run an update via yum or yumex, I have to remember to exclude it: firefox. Here's the results of my latest try:
Transaction check error: file /usr/lib/firefox/browser/defaults/preferences from install of firefox-22.0-1.fc19.i686 conflicts with file from package firefox-22.0-1.fc17.i686
I tried using swap:
yum swap firefox*.fc17.i686 firefox*fc.19.i686
because the man page said that that was simply a short form of remove/install, but yum interpreted it as an update. Maybe I'll have to download the file and use rpm to do it, but there should[1] be a way to force it via yum.
[1]Well, I think there should be; if you disagree, I'd be willing to discuss it and maybe change my mind if your reason's good enough. Do note, however, that rpm does allow --force.
On 08/01/2013 03:51 PM, Joe Zeff wrote:
Transaction check error: file /usr/lib/firefox/browser/defaults/preferences from install of firefox-22.0-1.fc19.i686 conflicts with file from package firefox-22.0-1.fc17.i686
You have two firefox packages installed. There are multiple ways of fixing this with or without yum.
yum remove firefox-22.0-1.fc17.i686
yum distro-sync
package-cleanup --cleandupes
rpm -e firefox-22.0-1.fc17.i686
Pick one.
On Thu, 01 Aug 2013 13:51:46 -0700 Joe Zeff joe@zeff.us wrote:
There's one package that I can't get upgraded, and it's driving me up the wall because every time I run an update via yum or yumex, I have to remember to exclude it: firefox. Here's the results of my latest try:
Transaction check error: file /usr/lib/firefox/browser/defaults/preferences from install of firefox-22.0-1.fc19.i686 conflicts with file from package firefox-22.0-1.fc17.i686
What happens if you just try to "yum remove firefox" and after that is done do a "yum install firefox"?
Since I remember you saying something about salvaging a half-updated machine, did you
(1) do "yum distro-sync full", (2) make sure that /etc/os-release says Fedora 19, and (3) check that repository definitions under /etc/yum.repos.d/ actually point to Fedora 19 repos?
Also, I vaguely remember that upgrading from F17 to F19 is not exactly a great idea, and that you'd be better off upgrading to F18 first, and only after that upgrade to F19. Though I believe it's now obsolete advice, given that you have already performed the upgrade... ;-)
HTH, :-) Marko
On 08/01/2013 03:11 PM, Michael Cronenworth wrote:
You have two firefox packages installed. There are multiple ways of fixing this with or without yum.
No, I don't. I never did. I had the fc17 version of firefox 22 and couldn't update to the f19 version of firefox 22 because of a file conflict. If I'd had both installed, fixing it would have been far more trivial.
On Thu, 01 Aug 2013 15:30:25 -0700 Joe Zeff joe@zeff.us wrote:
On 08/01/2013 03:14 PM, Marko Vojinovic wrote:
(1) do "yum distro-sync full", (2) make sure that /etc/os-release says Fedora 19, and (3) check that repository definitions under/etc/yum.repos.d/ actually point to Fedora 19 repos?
Asked and answered, several times.
Sorry, I missed the answers. :-)
If all else fails, I'd use "rpm -e firefox" and subsequently "yum install firefox". I know it's not the cleanest and most proper way to deal with it, but I believe that rpm would actually do what it's told to do. After that it would be up to yum to figure out its own database...
HTH, :-) Marko
Joe Zeff writes:
On 08/01/2013 03:11 PM, Michael Cronenworth wrote:
You have two firefox packages installed. There are multiple ways of fixing this with or without yum.
No, I don't. I never did. I had the fc17 version of firefox 22 and couldn't update to the f19 version of firefox 22 because of a file conflict. If I'd had both installed, fixing it would have been far more trivial.
It's some kind of an RPM bug. I ran into this when upgrading from F18 to F19. The solution, on every box, was trivial. yum remove firefox, then yum install it. You'll be able to reinstall firefox just fine.
There is no real conflict. Something in RPM is FUbared.
On 08/01/2013 03:55 PM, Marko Vojinovic wrote:
If all else fails, I'd use "rpm -e firefox" and subsequently "yum install firefox". I know it's not the cleanest and most proper way to deal with it, but I believe that rpm would actually do what it's told to do. After that it would be up to yum to figure out its own database...
Which is what I eventually used, although I added --nodeps, just to be safe.
And, this gave me a chance to test another yum-related program that had been having problems: originally, you could run needs-restarting without root. Later, it would crash if a regular user ran it, because it didn't check to see if it had the access it needed. Now, if you're not root, it complains about not being able to read from a large number of directories in /proc, but I can now confirm that it does end up with the right answer. There's a bugzilla out about this, and two of us are trying to persuade the maintainer that if nothing else, the exit code should reflect the fact that it wasn't run as root. (There are scripts that might run it and interpret the error messages as programs that need to be restarted; having an exit code that tells it that it didn't have root privs can help prevent confusion.)
On 08/01/2013 03:58 PM, Sam Varshavchik wrote:
It's some kind of an RPM bug. I ran into this when upgrading from F18 to F19. The solution, on every box, was trivial. yum remove firefox, then yum install it. You'll be able to reinstall firefox just fine.
And that's what I finally did.
There is no real conflict. Something in RPM is FUbared.
Is it a problem in rpm itself, or that particular package? Is there a bugzilla on this?
Rahul Sundaram writes:
Hi
On Thu, Aug 1, 2013 at 6:58 PM, Sam Varshavchik wrote:
There is no real conflict. Something in RPM is FUbared.
bugzilla # ? Thanks
This can't be an obscure bug, it was fairly obvious that everyone who upgrades is going to run into it. Didn't even bother to write it up, initially, when I ran into it.
Yeah, just searched Bugzilla, and it's been reported already:
https://bugzilla.redhat.com/show_bug.cgi?id=976420
I'm somewhat disappointed, though, there there aren't any DUPEs that have been closed to it.
Given the explanation, and the easy workaround, I'd say don't even bother. Just mark it down as a known issues, and move on to more pressing matters.
Joe Zeff writes:
On 08/01/2013 03:58 PM, Sam Varshavchik wrote:
It's some kind of an RPM bug. I ran into this when upgrading from F18 to F19. The solution, on every box, was trivial. yum remove firefox, then yum install it. You'll be able to reinstall firefox just fine.
And that's what I finally did.
There is no real conflict. Something in RPM is FUbared.
Is it a problem in rpm itself, or that particular package? Is there a bugzilla on this?
I thought that it was an RPM bug, but it's really a package bug, but it's really really something that RPM should handle, but does not, so it should really be an RPM bug.
On Thu, Aug 1, 2013 at 4:33 PM, Sam Varshavchik mrsam@courier-mta.com wrote:
I thought that it was an RPM bug, but it's really a package bug, but it's really really something that RPM should handle, but does not, so it should really be an RPM bug.
It's definitely an RPM bug, just one that is really, really hard to fix. (IIRC it's due to a limitation in cpio, so fixing it would require changing the format files in RPMs are used to something else, which is...quite the undertaking.)
Working around it with %pretrans hackery is much, much easier, so thus it's also a packaging bug if people want it fixed this decade. ;-)
-T.C.
T.C. Hollingsworth writes:
On Thu, Aug 1, 2013 at 4:33 PM, Sam Varshavchik mrsam@courier-mta.com wrote:
I thought that it was an RPM bug, but it's really a package bug, but it's really really something that RPM should handle, but does not, so it should really be an RPM bug.
It's definitely an RPM bug, just one that is really, really hard to fix. (IIRC it's due to a limitation in cpio, so fixing it would require changing the format files in RPMs are used to something else, which is...quite the undertaking.)
I don't see why using the cpio format makes it difficult to fix this. rpm can't be just forking off cpio, and feeding it the payload inside an rpm file. Otherwise there's no way to implement %noclobber.
rpm must be parsing the cpio format manually, and doing extraction by hand, one file at a time, in order to be able to do %noclobber, and a few other things.
Am 01.08.2013 22:51, schrieb Joe Zeff:
There's one package that I can't get upgraded, and it's driving me up the wall because every time I run an update via yum or yumex, I have to remember to exclude it: firefox. Here's the results of my latest try:
Transaction check error: file /usr/lib/firefox/browser/defaults/preferences from install of firefox-22.0-1.fc19.i686 conflicts with file from package firefox-22.0-1.fc17.i686
why not simply "rpm -e --nodeps firefox; yum install firefox" and in doubt "package-cleanup --dupes" and/or "package-cleanup --cleandupes"