|
Bugzilla – Full Text Bug Listing |
| Summary: | cannot add multiple locks (was: Package state "Protected -- Do Not Modify" not saved) | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | Forgotten User b49zM5D78q <forgotten_b49zM5D78q> |
| Component: | YaST2 | Assignee: | E-mail List <zypp-maintainers> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P2 - High | CC: | forgotten_7645792743, gp, lazy.kent, ma, paka, rainer.klute, tgoettlicher |
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | y2log | ||
|
Description
Forgotten User b49zM5D78q
2009-08-06 10:04:45 UTC
I confirm. openSUSE Factory, latest updates installed. I guess it happens in the Qt frontend. Can you confirm that? Not really. Launching yast2 --ncurses sw_single and marking several pre-installed packages as "Lock" (shotcut ALT+'*'), which can be seen as state "-i-" this locked state isn't remembered even for a second call of the ncurses interface. BTW: The packages I tried to lock were installed manually and do not come from an active repository in the repository manager, if this plays a role. Wow, I can reproduce it, but only with some packages :( I've been able to lock the others successfully ... Yes, I got the same effect on one of the tested systems - the Protected state for one package was saved, but for others not. At the moment, I have no idea in which case it is saved and when not. Created attachment 312644 [details]
y2log
Erm, the bug is not ncurses-specific, locking in qt-pkg fails just as well - seems that we have to ask zypp-maintainers for help. From what I've seen in several tests (y2log in comment #6 shows those), no matter how many packages the user tries to lock, only *one* of them ends up in /etc/zypp/locks. E.g the last run of sw_single in the log above tries to lock vim and vim-base, while only vim-base ends up being locked at the end. (needinfo-ing for the time being, can be reassigned later) Hmm, sounds like this is in libzypp, after all, zypper is affected, too (bug 520015). I did not investigate yet, but this might be related to changes in the PoolQuery. Even more, subsequent locks doesn't lock more than the previous package that was left. At the moment, I can lock maximally one package, independently of how often I restart YaST or zypper and retrying locking more packages. (In reply to comment #7) > ... > From what I've seen in several tests (y2log in comment #6 shows those), no > matter how many packages the user tries to lock, only *one* of them ends up in > /etc/zypp/locks. E.g the last run of sw_single in the log above tries to lock > vim and vim-base, while only vim-base ends up being locked at the end. > ... *** Bug 520195 has been marked as a duplicate of this bug. *** (In reply to comment #8) > Hmm, sounds like this is in libzypp, after all, zypper is affected, too (bug > 520015). I did not investigate yet, but this might be related to changes in the > PoolQuery. Yes. Looks like PoolQuery::opertor== broke. I'll fix it. *** This bug has been marked as a duplicate of bug 501850 *** Sorry, this is of not a duplicate of #501850. Reopened. *** Bug 520015 has been marked as a duplicate of this bug. *** zypper-1.2.3-1.1.x86_64 still has the same problem adding more than one lock 11.2/m6 yes, will be fixed in git today fixed in libzypp-6.14.0 *** Bug 535664 has been marked as a duplicate of this bug. *** |