Personally I would not mind dup --repo being removed. Nonetheless independently from this updating /etc/zypp/systemCheck, as Jano said, will be a good idea. On the other hand why not keep a functionality which is already implemented and might make sense in some cases. My suggestion for this would be to keep dup but to make it always require the --force option. This will require no additional implementation effort (unless the check I have previously proposed). If --force is not specified alongside with dup --repo a message should prompt the user either to use --from instead or to add the --force option. Jano Kupec schrieb:
Michael Andres wrote:
On Tuesday 04 August 2009 20:45:41 Elmar Stellnberger wrote:
Zypper -dup may choose to remove important user programs if it can not satisfy its dependencies. This is especially the case if zypper wants to switch the arch of certain packages as in Bug 506801 (https://bugzilla.novell.com/show_bug.cgi?id=506801). Where you did a 'zypper dup --repo myrepo', and several packages got deleted because the solver assumes they are orphaned. This happens because --repo currently hides all repos except myrepo from the solver.
Yes, Elmar knows that. I suggested to bring this up on this list because this can happen with any command (even 'zypper rm glibc'). I wonder why we ship the systemCheck with only glibc. Although it's up to the user to edit this file, why not put more stuff there?
A few days ago I wrote about the new Resolver::addUpgradeRepo which is intended to solve this problem. With this call the solver is aware of all repos and should be able to make better decisions.
What bothers me more than the content of /etc/zypp/systemCheck (which is a user config file), is the question whether it is actually worth to keep the old 'zypper dup --repo' behaviour?
It's a shortcut for
disble all repos except myrepo zypper dup enable the repos again
Exactly. In short - load only the specified repos for current operation.
IMO this is not a feature, but just worked around a missing functionality in the solver. Now as the functionality is present, I'd prefer to fix '--repo' instead on introducing a new '--form' option.
I wouldn't consider this as breaking backward compatibility, but fixing a buggy and dangerous behavior.
OK, IMO current --repo makes sense as well (for developers at least, if not users), but since i am apparently the only one who thinks so, i'll be happy to change it to what i proposed to be --from. Starting with dup, and later, as we add necessary API to libzypp also in the other commands.
If anyone wants to keep this feature, please speak up! I vote for keeping it :O)
-- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org