Red Hat Bugzilla – Bug 975909
rpm fails when there are dir<->symlink replacements and the package gets split into sub-packages
Last modified: 2015-06-29 21:22:51 EDT
Description of problem:
RPM cannot replace a symlink with a directory or vice-versa. To work around this, you must use a %pretrans script in the specfile. In RPM 4.11 (see bug 447156), RPM was changed to detect and report such invalid operations as file conflicts (before this, it would just fail later). These conflicts do not occur in RPM when the proper %pretrans script is used to fix up the symlinks and directories.
Unfortunately, yum now fails in transaction test (it does not execute pretrans?). So packages that need to replace symlinks with directories cannot be upgraded in Fedora 19.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. On Fedora 19, install golang-1.1-2 from koji: http://kojipkgs.fedoraproject.org//packages/golang/1.1/2.fc19/x86_64/golang-1.1-2.fc19.x86_64.rpm
2. yum upgrade golang
Transaction check error
(pages of output)
This might require a revert of this behavior in rpm?
Although yum's the one with symptoms, the problem is on rpm side in these cases.
Okay, the issue is caused by heuristics in rpm 4.11.x which decide when to let dir<->symlink replacement conflicts through in test-transactions: the heuristics fail to catch the case when package gets split into sub-packages. This can be triggered by rpm too with 'rpm -Uvh --test'.
The heuristics need to be fixed to allow for package splits, but the conflict detection itself is not going away.
Err, spoke too soon. The issue is not specific to rpm 4.11 at all, it happens with older rpm versions (4.9.x and 4.10.x tested) as well if you run with 'rpm -Uvh --test', which is what yum does before doing the actual transaction.
So AFAICS the golang update is broken for all Fedora versions.
Ok. I will try eliminating the subpackages as a workaround. Do you think I could keep them in rawhide?
This happens even when I eliminate the subpackage:
/usr/share/golang/src/pkg/unicode/digit.go conflicts between attempted installs of golang-1.1.1-4.fc19.x86_64 and golang-1.1.1-4.fc19.x86_64
Self-conflicts are entirely possible through directory symlinks, but rpm versions prior to 4.10 didn't notice them.
golang-1.1.1-4.fc18 has been submitted as an update for Fedora 18.
golang-1.1.1-4.fc17 has been submitted as an update for Fedora 17.
golang-1.1.1-4.fc19 has been submitted as an update for Fedora 19.
A golang update could not address an rpm bug :) Switching component...
Sorry, I had the wrong bug in https://admin.fedoraproject.org/updates !
Also, I think I have worked around this, so if it is not a valid bug anymore, please close.
I still have this problem, and I cannot work around as in the aforementioned golang. I have an update that is giving a conflict on itself for a symlink that should disappear.
# yum --enablerepo=temp update
Loaded plugins: langpacks, refresh-packagekit
--> Running transaction check
---> Package guacamole.noarch 0:0.8.1-2.fc19 will be updated
---> Package guacamole.noarch 0:0.8.2-1.fc19 will be obsoleting
---> Package guacamole-common.noarch 0:0.8.0-5.fc19 will be obsoleted
---> Package guacamole-common-js.noarch 0:0.7.1-3.fc19 will be obsoleted
---> Package guacamole-ext.noarch 0:0.8.0-4.fc19 will be obsoleted
---> Package guacd.x86_64 0:0.7.0-7.fc19 will be updated
---> Package guacd.x86_64 0:0.8.2-1.fc19 will be an update
---> Package libguac.x86_64 0:0.7.0-5.fc19 will be updated
---> Package libguac.x86_64 0:0.8.2-1.fc19 will be an update
---> Package libguac-client-rdp.x86_64 0:0.7.4-3.fc19 will be updated
---> Package libguac-client-rdp.x86_64 0:0.8.2-1.fc19 will be an update
---> Package libguac-client-ssh.x86_64 0:0.8.0-3.fc19 will be updated
---> Package libguac-client-ssh.x86_64 0:0.8.2-1.fc19 will be an update
---> Package libguac-client-vnc.x86_64 0:0.7.2-3.fc19 will be updated
---> Package libguac-client-vnc.x86_64 0:0.8.2-1.fc19 will be an update
--> Finished Dependency Resolution
Package Arch Version Repository Size
guacamole noarch 0.8.2-1.fc19 temp 1.2 M
replacing guacamole-common.noarch 0.8.0-5.fc19
replacing guacamole-common-js.noarch 0.7.1-3.fc19
replacing guacamole-ext.noarch 0.8.0-4.fc19
guacd x86_64 0.8.2-1.fc19 temp 13 k
libguac-client-rdp x86_64 0.8.2-1.fc19 temp 30 k
libguac-client-ssh x86_64 0.8.2-1.fc19 temp 23 k
libguac-client-vnc x86_64 0.8.2-1.fc19 temp 9.6 k
Updating for dependencies:
libguac x86_64 0.8.2-1.fc19 temp 30 k
Install 1 Package
Upgrade 4 Packages (+1 Dependent package)
Total download size: 1.3 M
Is this ok [y/d/N]: y
No Presto metadata available for temp
Total 53 MB/s | 1.3 MB 00:00
Running transaction check
Running transaction test
Transaction check error:
file /usr/share/tomcat/webapps/guacamole/guacamole-common-js from install of guacamole-0.8.2-1.fc19.noarch conflicts with file from package guacamole-0.8.1-2.fc19.noarch
The file "/usr/share/tomcat/webapps/guacamole/guacamole-common-js" was a symlink in guacamole-0.8.1-2.fc19.noarch, now it's a folder since the other guacamole-common-js is now contained in guacamole-0.8.2-1.fc19.noarch.
How to deal with such situation?
What are the "%pretrans" hacks mentioned?
I'm bumping the priority as this is preventing me to push updates to Fedora.
Well, I've looked to all bugs referenced and this is happening since 2008!
There are many workarounds floating in packages, like this one:
Is this the intended way to deal with the problem?
Bumped distribution to f20, as it happens there as well...
This should be fixed in rpm >= 4.12, there was an issue where a %pretrans-removed symlink was still considered in fingerprinting, causing a bogus conflict to be reported:
If you can test your particular case with the rawhide rpm, that'd be appreciated.
Thanks, I will try to test it this week. Need some time to set up a Rawhide system between one meeting and the other.
(In reply to Panu Matilainen from comment #15)
> This should be fixed in rpm >= 4.12, there was an issue where a
> %pretrans-removed symlink was still considered in fingerprinting, causing a
> bogus conflict to be reported:
> If you can test your particular case with the rawhide rpm, that'd be
The latest rawhide build is rpm-4.11.2-1.fc21 I believe. This build does not yet let me update a symlink with a directory using yum. rpm -Uvh works, but yum install fails (similar to rpm -Uvh --test). See bug 1054396 for details as to how to reproduce. RPM from rawhide does not fix the problem for me.
(In reply to Severin Gehwolf from comment #17)
> (In reply to Panu Matilainen from comment #15)
> > This should be fixed in rpm >= 4.12, there was an issue where a
> > %pretrans-removed symlink was still considered in fingerprinting, causing a
> > bogus conflict to be reported:
> > http://rpm.org/gitweb?p=rpm.git;a=commitdiff;
> > h=bcba176fbf0d2cae4d0ee01c0f1b19dde181fc59
> > If you can test your particular case with the rawhide rpm, that'd be
> > appreciated.
> The latest rawhide build is rpm-4.11.2-1.fc21 I believe. This build does not
> yet let me update a symlink with a directory using yum. rpm -Uvh works, but
> yum install fails (similar to rpm -Uvh --test). See bug 1054396 for details
> as to how to reproduce. RPM from rawhide does not fix the problem for me.
Panu backported the fix to 4.11.2:
but I can confirm that with 4.11.2-2.fc20, "yum upgrade" behaves differently to "rpm -U", and the problem I described here:
still exists when using "yum upgrade" (though not with "rpm -U").
I found bug 1076552 and discovered that a fix for that bug is now in rawhide. The latest build is 4.11.2-4.fc21 (http://koji.fedoraproject.org/koji/buildinfo?buildID=507188).
With 4.11.2-4.fc21 the problem does seem to be fixed, and old files are not left behind when upgrading the 'test' package using "yum upgrade".
Panu, do you think the bug 1076552 fix will make its way into F20? Unless I am mistaken, the solution for replacing a symlink to a directory with a directory, documented here:
leaves behind old files.
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 20 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.