Bug 147273
Summary: | yum architecture dependent behaviour - conflicting files missed or not | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Michal Jaegermann <michal> |
Component: | rpm | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED WONTFIX | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | jbj, katzj |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-08-27 03:29:09 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Michal Jaegermann
2005-02-06 00:12:07 UTC
yum doesn't look at files for conflicts. That's something rpm does in the transaction check. If it doesn't report them then yum won't complain. This isn't an issue yum can really affect. Refiling as rpm Conflicts is conflicts, even if comments. Agreed that conflicts are confilcts but the real question was why a reaction of yum to these changes with a machine architecture. 'reaction of yum'? I don't understand what you mean there. I mean exactly what was written in the original report. Let's try again... With tetex and texinfo packages installed on i386 and x86_64 installations a yum update with the same versions of packages ended up with a conflict reported on x86_64 but NOT reported on x86. This discrepancy left me scratching my head as corresponding texi2pdf scripts were not architecture dependent (not very surprising). are the files different in the x86_64 and not in the i386 version? Your report isn't very clear as how to replicate the problem. Could you please describe what you do to cause it to occur? thanks. > are the files different in the x86_64 and not in the i386 version? Of course not. The files in questions are scripts, so there was nothing to compile, and all packages were build from the same sources. In case of doubts I did check (at the time I wrote the original report) that these scripts were indeed the same before and after updates. > Could you please describe what you do to cause it to occur? Well, I run basically 'yum update' and on one installation I was greeted with a conflict notification and on another, in what it looked like the same situation, everything was happily updated. I forced an update using rpm where I had to. I am afraid that from times of the original report versions of yum, rpm and packages in question changed few times so this is not something which is reproducible on demand. |