| Summary: | ntfs-config error with x32 repo enabled | ||
|---|---|---|---|
| Product: | [ROSA-based products] ROSA Fresh | Reporter: | Vladimir Potapov <v.potapov> |
| Component: | Packages from Main | Assignee: | ROSA Linux Bugs <bugs> |
| Status: | RESOLVED FIXED | QA Contact: | ROSA Linux Bugs <bugs> |
| Severity: | normal | ||
| Priority: | Normal | CC: | alex.burmashev, denis.silakov |
| Version: | Fresh | Flags: | v.potapov:
qa_verified+
alex.burmashev: published+ |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Platform: | --- | ROSA Vulnerability identifier: | |
| RPM Package: | urpmi | ISO-related: | |
| Bad POT generating: | Upstream: | ||
|
Description
Vladimir Potapov
2013-10-23 17:48:14 MSK
Advisory: Fixed perl-URPM to take package architecture into account before reporting that "newer package exists in repository". A typical situation with both 32bit and 64bit repos enabled in the 64bit system is that you add a 32bit container. So you can have foo-2.i586 from container and foo-1.x86-64 from usual repository. If you will try to install 'urpmi foo', it will actually install nothing - first, foo-2 will be rejected since we have 64 bit foo, but foo-1.x86-64 will be rejected since there is a newer foo-2. Moreover, some collisions may arise when resolving dependencies for foo-2 - it seems that the situation described in this bug is from this series. Build lists: https://abf.rosalinux.ru/build_lists/1365417 https://abf.rosalinux.ru/build_lists/1365416 How to test: A recent example is ntfs-config in 64bit system with both 32bit and 64bit repos enabled. Remove ntfs-config if it is installed. Add 32bit container from bug #2952 and try to install 'urpmi ntfs-config'. Expected behavior: urpmi should install 64bit ntfs-config-1.1-4 from usual repositories. If you add 64bit container, urpmi should install ntfs-config-1.1-5 from that container. perl-URPM-4.43-22-rosa2012.1 ******************** Advisory ******************* Fixed perl-URPM to take package architecture into account before reporting that "newer package exists in repository ************************************************* QA Verified |