|
Bugzilla – Full Text Bug Listing |
| Summary: | repository priorities ignored by package management apps | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.0 | Reporter: | Jochem Kossen <jkossen> |
| Component: | libzypp | Assignee: | Michael Schröder <mls> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P4 - Low | CC: | dmacvicar, forgotten_hovWKlcOPJ, forgotten_zOWss6Gs9u, lslezak, support |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | x86 | ||
| OS: | openSUSE 11.0 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
screenshot of PackageKit showing updates
screenshot of yast showing updates y2logs + resolver test case |
||
|
Description
Jochem Kossen
2008-07-12 12:01:13 UTC
Created attachment 227447 [details]
screenshot of PackageKit showing updates
Created attachment 227448 [details]
screenshot of yast showing updates
Please attach y2logs and resolver test case. If you are in doubt follow: http://en.opensuse.org/Bugs/YaST Thanks! Created attachment 228548 [details]
y2logs + resolver test case
Note I reported something similar, but more KDE centric, at bug #402770. I thing it NEEDS a fix. Repository priorities were implemented in libzypp, but just a single command uses them. - zypper lu -t package ignores them - zypper dup ignores them - kde updater applet, with both libzypp and packagekit backends, ignores them - YaST QT PM ignores them - gnome updater aplet ignores them - YaST GTK PM ignores them Only zypper up -t package looks at repository priorites! Well, for me, 'zypper up' and 'zypper dup' seem to handle priorities correctly (check the terminal output in the original bug text, they both don't want to update anything, which is correct). Gnome updater applet does not, and Yast GTK PM does not. They both want to update the system with packages from the packman repository, which has the lowest priority of all activated repositories: 130 (higher number thus lower priority), thus should not be used. "zypper up" only updates patches, no packages, and "zypper up -t package" works correctly. But zypper dup doesn't gives you problems just because the "don't change vendor" rule. Create a "/etc/zypp/vendors.d/packman" file with content: ---Start file content (do not include) [main] vendors=http://packman,packman,videolan ---End file Put videolan repo with a lower priority than packman. Be sure to have "vlc" or "libffmpeg0" package installed from packman... and "zypper dup" will try to change your packman package with a videolan one. Between, yes... "don't change vendor" rule is also ignored by updater applets and YaST PM. I think that rule isn't documented anywhere, but it's my understanding that is supposed to be applied. So we have three behaviors: - zypper lu -t package... the one used by all the GUI apps (or something very similar). Only looks at package version, ignores vendor (bad) and repo priority (bad). - zypper up -t package... doesn't changes vendor (good) and honours repo priorities (good). "The Good One (TM)". - zypper dup. It doesn't changes vendor (good), but doesn't honours repo priorities (bad). *** Bug 416082 has been marked as a duplicate of this bug. *** This bug seems to be fixed in openSUSE 11.1. Repository-priorities and dont-change-vendor-rule works here in Yast Packagemanagement. Yes, even if YaST sw_single module still does some things in its own instead of through libzypp (locks and vendor are ignored...), the priorities seem to be handled correctly everywhere now. Any problem with closing the bug? No, lets close it then. |