[Bug 646925] New: Make repo parameter in locks more flexible
https://bugzilla.novell.com/show_bug.cgi?id=646925 https://bugzilla.novell.com/show_bug.cgi?id=646925#c0 Summary: Make repo parameter in locks more flexible Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers@forge.provo.novell.com ReportedBy: cmorve69@yahoo.es QAContact: qa@suse.de Found By: Community User Blocker: --- When adding a lock the repo parameter must be specified exactly. I would like at least the possibility to negate it. I expect a common lock to be repo: !packman type: package match_type: glob case_sensitive: on solvable_name: gstreamer-* install_status: non-installed Now you can make something similar with repo: oss type: package match_type: glob case_sensitive: on solvable_name: gstreamer-* install_status: non-installed and perhaps also repo: dvd type: package match_type: glob case_sensitive: on solvable_name: gstreamer-* install_status: non-installed but this will stop working once you add the multimedia:libs repo. You can add a third lock, but the problem here is that the lock doesn't really means what the user wants. The user doesn't wants to lock the installation of gstreamer packages from oss, he wants to block the installation of gstreamer packages from non-Packman repos. Since I expect the "even when dist-upgrade, I want this package from this repo and never from any other repo" case to be common, could this be added? Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=646925 https://bugzilla.novell.com/show_bug.cgi?id=646925#c1 Duncan Mac-Vicar <dmacvicar@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low Status|NEW |NEEDINFO CC| |dmacvicar@novell.com InfoProvider| |cmorve69@yahoo.es --- Comment #1 from Duncan Mac-Vicar <dmacvicar@novell.com> 2011-05-17 08:30:01 UTC --- If you install the package from packman, and lock it, you have the same effect right? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=646925 https://bugzilla.novell.com/show_bug.cgi?id=646925#c2 Cristian Morales Vega <cmorve69@yahoo.es> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|cmorve69@yahoo.es | --- Comment #2 from Cristian Morales Vega <cmorve69@yahoo.es> 2011-05-17 08:59:07 UTC --- Not really. Once Packman updates its package my installed package is no longer "from Packman" and so not locked, now zypper dup will change my package for the one from the repo with the higher priority. If I forget to use an "install_status: installed" it's even worse. Now I have locked the Packman update package, so that package will be the only option I'm sure will not be selected. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=646925 https://bugzilla.novell.com/show_bug.cgi?id=646925#c3 Cristian Morales Vega <christian.morales.vega@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|libzypp |libzypp Product|openSUSE 11.3 |openSUSE 12.1 --- Comment #3 from Cristian Morales Vega <christian.morales.vega@gmail.com> 2012-05-16 16:43:01 UTC --- Same problem in 12.1 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com