|
Bugzilla – Full Text Bug Listing |
| Summary: | improve the --force option | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.4 | Reporter: | Jon Nelson <jnelson-suse> |
| Component: | libzypp | Assignee: | Jan Kupec <jkupec> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P4 - Low | CC: | bitdealer, estellnb |
| Version: | Factory | ||
| Target Milestone: | Factory | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Jon Nelson
2009-03-09 13:42:12 UTC
The name of the --force option is really misfortunate as it is in fact --reinstall-the-exact-installed-version. I'll fix this, but later. The new functionality still needs to be defined, though. I'll try to come up with some suggestions. What you suggest might be one of the use cases. 'zypper dup' does excatly what you want: it brings all of your packages back to versions from the configured repositories. (In reply to comment #0) > Also, how does --repo differ from --from: Please, one report per bug. It is more work for you, but it is also the only sane way to handle bugs. Thanx! > -r, --repo <alias|#|URI> Install packages only from the specified > repository. The --repo description is wrong. I'll change it to "Consider only the specified repository, ignore others." or something in that fashion. Would that be more clear? > --from <alias|#|URI> Select packages only from specified repository. This is correct. c#2: yes, but it does it for all packages. We need to be able to do it also per-package. probably 'zypper in -f foo' to reinstall the package with the best available from any repo, and 'zypper in -f -r repo foo' to reinstall from the specified repo. *** Bug 506702 has been marked as a duplicate of this bug. *** Providing an own downgrade option as proposed in Enh/Bug 506701 will better fulfill the needs described here as it is anyway possible to downgrade via 'zypper in' by specifying the version (f.i. zypper in libdrm-2.4.1-1.13). In general 'zypper in' should still be for installing packages as it was not meant as a downgrade utility. *** Bug 547485 has been marked as a duplicate of this bug. *** Agree regarding comment 6. What is the status of this issue? (In reply to comment #6) > Providing an own downgrade option as proposed in Enh/Bug 506701 will better > fulfill the needs described here as it is anyway possible to downgrade via > 'zypper in' by specifying the version (f.i. zypper in libdrm-2.4.1-1.13). The needs which led Jon to filing this report, yes, but the report itself is about 'zypper in --force ...' not working properly (at least i took it that way). So i'm keeping this open until that is resolved. For the downgrade functionality let's use bug 506701. > In > general 'zypper in' should still be for installing packages as it was not meant > as a downgrade utility. Why not? It's 'zypper install what-i-tell-you'. If that what-i-tell-you means in fact downgrade, so be it. (In reply to comment #8) > What is the status of this issue? Regarding the --force option, some improvements have been already done in zypper 1.4.x which is now in openSUSE 11.3. I still need to summarize what works and what still needs fixing. 11.1 -> 11.4 Fixed in 1.5.1
in -f amarok # will request the highest ver. regardles
# of vendor/priority/locks/dep problems
in -f amarok-1.4.2 # will force that version even if it means downgrade
if the requested/highest version is already installed, it will get reinstalled
Note that 'update' does not have the --force option (yet). But in/up with arguments do the same (just the messages differ a bit). So if you want to force something, use 'in --force'.
|