| Summary: | When package installing URPMI should update related packages | ||
|---|---|---|---|
| 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, andrey.bondrov, denis.silakov |
| Version: | Fresh | Flags: | v.potapov:
qa_verified+
alex.burmashev: published+ |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Platform: | --- | ROSA Vulnerability identifier: | |
| RPM Package: | ISO-related: | ||
| Bad POT generating: | Upstream: | ||
|
Description
Vladimir Potapov
2013-03-13 12:26:46 MSK
Uh, no. This would allow to avoid issues such as the one from the bug you've quoted, but will significantly decrease urpmi flexibility. Urpmi is a command-line tool intended for experienced users, and developers do need a way to install packages without updating the whole set of dependent packages. Because in many cases such updates are not really necessary and will only take time. Normally users should use some higher-level tools. Currently we use rpmdrake, but it is quite an ugly program and we are not going to improve it in future. Instead, a new Software Center will be introduced in future ROSA versions; let's hope it will be smarter and easier-to-use for end users. (In reply to comment #1) > Uh, no. This would allow to avoid issues such as the one from the bug you've > quoted, but will significantly decrease urpmi flexibility. The feature just must be optional and turned on by default (with possibility to disable via urpmi system config or key --no-suggested-updates). On the latest TC meeting we've come to agreement to try to implement some improvements in this area. Advisory: When updating some package, urpmi by default now tries to update all packages on which the current one depends. That is, if you invoke 'urpmi foo' and foo requires 'bar', urpmi will look for bar updates and install them, even if 'bar' is already installed and formally satisfy 'foo' requirement. Behavior of urpmi can be regulated using '--force-req-update' and '--no-force-req-update' options (either in command line or in urpmi.cfg). Rpmdrake now has appropriate option enabled by default. Build lists: (perl-URPM) https://abf.rosalinux.ru/build_lists/1055659 https://abf.rosalinux.ru/build_lists/1055660 (urpmi) https://abf.rosalinux.ru/build_lists/1055657 https://abf.rosalinux.ru/build_lists/1055658 (rpmdrake) https://abf.rosalinux.ru/build_lists/1055662 https://abf.rosalinux.ru/build_lists/1055661 perl-URPM should be published first. These changes were tested for some time by developers. We've fixed some issues and there were no claiming during the last week. Considering the case with audiofile (bug #1763) - Audiofile requires 'libaudiofile.so.1', but it doesn't specify particular version of the library package. So if user has old audiofile and libaudiofile installed, he is able to update audiofile only. But newer audiofile (0.3.6 in that case) doesn't work with old library (0.3.4). With new urpmi, libaudiofile will be updated automatically. perl-URPM-4.43-8-rosa2012.1 urpmi-6.71-9-rosa2012.1 rpmdrake-5.26.12-15-rosa2012.1 ********************** Advisory ************************* When updating some package, urpmi by default now tries to update all packages on which the current one depends. That is, if you invoke 'urpmi foo' and foo requires 'bar', urpmi will look for bar updates and install them, even if 'bar' is already installed and formally satisfy 'foo' requirement. Behavior of urpmi can be regulated using '--force-req-update' and '--no-force-req-update' options (either in command line or in urpmi.cfg). Rpmdrake now has appropriate option enabled by default. ******************************************************* QA Verified |