| Summary: | subversion 32/64-bit libs conflict | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Frank Griffin <ftg> |
| Component: | RPM Packages | Assignee: | All Packagers <pkg-bugs> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | subversion | CVE: | |
| Status comment: | |||
The above post was from David Walser. From Charles Edwards: Under standard policy you are correct but subversion has Always been packaged in this manner. The lib is of No use to any other package, if subversion-1.8.14 %arch is not installed the lib can not and will not be used. I have had subversion for years and have never had the i586 lib installed and I have no idea why it happened in Franks case, Unless he had updated at some point from a mirror when i586 had been synced but x86_64 had not. If the intent is to prevent this from reoccurring I would prefer that either an %arch specific require or conflict be added. Here's a weirder take. rpmdrake doesn't say that any ,586 subversion packages are installed. If, instead of --auto-update I specifically urpmi subversion, the 64-bit package updates without errors. The lib64svn0 package still gets the errors. Something must be pulling in libsvn0.
David Walser
2015-10-30 15:39:20 CET
Summary:
32/64 bi versions suddenly conflict =>
subversion 32/64-bit libs conflict There is no registered maintainer for subversion in our maintainers database, so assigning to packagers collectively. Packagers, if one of you is maintaining subversion, please update the maintainers database accordingly. Assignee:
bugsquad =>
pkg-bugs I'm closing as OLD. Status:
NEW =>
RESOLVED |
I have a 64-bit system. Somehow, 32-bit svn got installed on it. A very recent cauldron update (2-3 days ago) causes the following conflict: Installation failed: file /etc/subversion/config from install of lib64svn0-2:1.8.14-3.mga6.x86_64 conflicts with file from package libsvn0-2:1.8.14-2.mga6.i586 file /etc/subversion/servers from install of lib64svn0-2:1.8.14-3.mga6.x86_64 conflicts with file from package libsvn0-2:1.8.14-2.mga6.i586 file /etc/subversion/config from install of libsvn0-2:1.8.14-3.mga6.i586 conflicts with file from package lib64svn0-2:1.8.14-2.mga6.x86_64 file /etc/subversion/servers from install of libsvn0-2:1.8.14-3.mga6.i586 conflicts with file from package lib64svn0-2:1.8.14-2.mga6.x86_64 This raises a several questions. 1) I didn't manually install i586 svn. Why is it there ? 2) The first two messages indicate that i586 is already installed, and the attempt to install a new x86_64 is blocked by the conflict. The last two indicate that x86_64 is already installed and blocking a new i586. If they conflict, how did they both get installed before. 3) What are /etc files doing in a lib package ? A quote from the dev ML: ***************************************************************** Frank Griffin <ftg@...> writes: > I have no idea why/how i586 svn got installed here, but in the last two > days --auto-update bounces the 64-bit version with: > > file /etc/subversion/{servers,config} from install of > lib64svn0-2:1.8.14-3.mga6.x86_64 conflicts with file from package > libsvn0-2:1.8.14-2.mga6.i586 > > Should it ? Those files most likely don't belong in the lib package. Please file a bug. ******************************************************************* I'm not sure if moving them will solve the problem if the i586 and x86_64 packages can be installed side-by-side. They'll conflict no matter where they are. Reproducible: Steps to Reproduce: