Home_greyopenFATE - openSUSE feature tracking > #306116
Dashboard | Search | Sign up | Login

Please login or register to be able to edit or vote this feature.

Better lock handling in zypper

Feature state

openSUSE-11.2
Rejected Information
openSUSE-11.3
Rejected Information

Description

Currently only two states in locking of packages are available (keep package as is/do not care about package) but I think it would be much more better to have a possibility lock only some parameters of package...
For example you have a 64bit machine, but you want keep some package always in i586 version, but you still wanna version updates in this case there should be a possibility to lock only this parameter. Of course there is a lot of options what else can be locked, for example version of package, meaning that you can't change package version, but release number can change...

References

http://en.opensuse.org/Libzypp/Locksfile

Discussion


icons/user_comment.png F. L. wrote: (9 years ago)

I can see marginal value in an x86 vs x64 lock as 64 bits become more popular.

upping to desirable.

icons/user_comment.png R. U. wrote: (8 years ago)

I hate zyppers locking behavior. If you just want to reasure your upgrades by a quick search, here a case study: I upgrade my openSUSE factory. For it is much I do not useĀ  verbose to keep oversight:

"zypper ref && zypper dup"

Now I am unsure about an arch change (a vlc library becomes i686 from pm but I want to stick with videolan.org), therefore on another console I do:

"zypper se -s vlc"

Not possible - zypper search exits, it does not like the locked database, why ?

icons/user_comment.png J. K. wrote: (8 years ago)

This request is about package locks, not zypper process locks. However, we are seeking to improve the inter-process locks as well, see e.g. http://lists.opensuse.org/zypp-devel/2008-03/msg00075.html , i'm not sure if there's another FATE entry for this. And yes, we hate the global zypp lock, too :O)

icons/user_comment.png J. K. wrote: (8 years ago)

BTW, see here for a workaround (but use it with caution!!): http://en.opensuse.org/Zypper/Troubleshooting#Ignore_still_running_zypper

icons/user_comment.png R. U. wrote: (8 years ago)

Thank you for the hint.

Why not following suggestion as standard behavior of zypper:

1. for all normal users "export ZYPP_READONLY_HACK=1"

2. only make sure this isn't exported back to root through sudo

icons/user_comment.png J. K. wrote: (8 years ago)

There already is a possibility to lock by quite a range of parameters. See 'man locks' or http://en.opensuse.org/Libzypp/Locksfile . The locks file contains queries editable by hand.

Zypper provides an interface (the *lock* commands) to manipulate just simple package/type queries. If we want to extend this interface, we need to define what exactly we want to achieve (which package attributes to enable, etc). It is surely not reasonable to handle all cases, and a simple generic interface is almost the same as editing the locks file manually.

Where i see room for improvement (except for supporting additional package attributes) is visualisation of the manually added special queries in the 'locks' command (it should show them somehow, show the results of specified query, etc).

Last change: 6 years ago
Voting
Score: 17
  • Negative: 0
  • Neutral: 2
  • Positive: 17
Tags
Feature Export
Application-xmlXML   Text-x-logPlaintext   PrinterPrint