|
Bugzilla – Full Text Bug Listing |
| Summary: | Get rid of package locks in package manager | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.2 | Reporter: | Pascal Bleser <pascal.bleser> |
| Component: | YaST2 | Assignee: | Klaus Kämpf <kkaempf> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | martin.schlander |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Pascal Bleser
2007-04-14 22:43:52 UTC
I agree that this is a big problem. A lot of times when you update things or remove things, you get the conflict dialog telling you to unlock packages before you can proceed. I have also experienced problems because of locked packages when using zypper. I'm not sure if zypper even offers a way to unlock locked packages. The feature to update packages in sw_single using "Package" > "All Packages" > "Update if a newer version is available" seems to disregard the locks anyway. If packages weren't locked automagically then this feature could perphaps respect the locks that people actually enable themselves. I see no benefit from the automatic locking, only problems. Getting rid of it for good would be nice, imho. Oh, right, I meant the "automatically locked packages" in YaST2, not the "taboo locks" that are explicitly set by users. Package locks are there to protect 3rd party packages from being removed/replaced/upgraded without the users notice. There are a lot of packages in the suse distribution which are built with more conservative settings than those coming from 3rd party repositories. Replacing them without warning would also cause user complaints. The current implementation has room for improvement, we are well aware of this. I would welcome an open discussion on opensuse-factory on how to - protect 3rd party packages - lock installed packages (protect them from being removed/upgraded) - lock uninstalled packages (protect them from being installed) Hi Klaus (In reply to comment #3) > Package locks are there to protect 3rd party packages from being > removed/replaced/upgraded without the users notice. Could you give some insight about how exactly YaST2 decides it automatically sets a lock on a package (or not) ? Are packages not built by SUSE automatically locked ? If so, how does it detect the former ? by the key it was signed with, the %{VENDOR}, ... ? > There are a lot of packages in the suse distribution which are built with more > conservative settings than those coming from 3rd party repositories. Replacing > them without warning would also cause user complaints. Yes in some scenarios (e.g. SLES or possibly SLED) and no in others. The typical SUSE user at home would most probably want to install certain packages from at least one or two well-known repositories (especially the one starting with P), e.g. wrt full multimedia support. That conservative behaviour is actually quite annoying in those use cases. > The current implementation has room for improvement, we are well aware of this. Mmmmyeah.. but it has been like that for ages (and an annoyance to many for ages ;)). > I would welcome an open discussion on opensuse-factory on how to > - protect 3rd party packages > - lock installed packages (protect them from being removed/upgraded) > - lock uninstalled packages (protect them from being installed) That's a good idea, indeed. Let's move the discussion there and summarize the results here, if there are any. To be discussed on opensuse-factory. Will be tracked as a feature (FATE ##302135) later. Revisit in preparation of Code11 Fixed in 10.3, further improvements in progress. |