[Bug 549940] New: k3b patch from 11.2 test-updates uninstalls k3b
http://bugzilla.novell.com/show_bug.cgi?id=549940 Summary: k3b patch from 11.2 test-updates uninstalls k3b Classification: openSUSE Product: openSUSE 11.2 Version: RC 1 Platform: Other OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: suse-beta@cboltz.de QAContact: jsrain@novell.com Found By: Beta-Customer Created an attachment (id=324041) --> (http://bugzilla.novell.com/attachment.cgi?id=324041) zypper log and solver testcase 11.2 RC1 + 11.2 test-updates repo # rpm -q k3b k3b-1.66.0.svn1009369-2.3.x86_64 # zypper in -t patch k3b Loading repository data... Reading installed packages... Resolving package dependencies... The following NEW patch is going to be installed: k3b The following package is going to be REMOVED: k3b 1 package to remove. After the operation, 10.4 MiB will be freed. Continue? [y/n/?] (y): n Needless to say that zypper should NOT uninstall k3b. The attached tarball contains the zypper.log and a solver testcase. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=549940 Andreas Jaeger <aj@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |zypp-maintainers@forge.prov |ovo.novell.com |o.novell.com -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=549940 User mls@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=549940#c1 Michael Schröder <mls@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #1 from Michael Schröder <mls@novell.com> 2009-10-27 02:32:10 MDT --- No, that's the correct behavior if the k3b package of the update repository is not installable. You should use 'zypper patch' instead, which doesn't use ForceResolve like 'zypper in' (Hi Jano!). -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=549940 User jkupec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=549940#c2 Ján Kupec <jkupec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jkupec@novell.com --- Comment #2 from Ján Kupec <jkupec@novell.com> 2009-10-27 03:06:09 MDT --- Hi :O) OK, this is obviously weird. Off with forceResolve for patches! (...and continue the discussion for packages in the other bug or ML. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=549940 User jkupec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=549940#c3 Ján Kupec <jkupec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High AssignedTo|zypp-maintainers@forge.prov |jkupec@novell.com |o.novell.com | Summary|k3b patch from 11.2 |'zypper in - t patch k3b' |test-updates uninstalls k3b |from 11.2 test-updates | |uninstalls k3b --- Comment #3 from Ján Kupec <jkupec@novell.com> 2009-10-27 03:12:47 MDT --- reopening to fix this in zypper -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=549940 User jkupec@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=549940#c4 Ján Kupec <jkupec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | --- Comment #4 from Ján Kupec <jkupec@novell.com> 2009-10-27 03:13:02 MDT --- reopening to fix this in zypper -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=549940 http://bugzilla.novell.com/show_bug.cgi?id=549940#c5 Ján Kupec <jkupec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #5 from Ján Kupec <jkupec@novell.com> 2009-11-27 11:54:53 UTC --- fixed in git, to be in zypper 1.2.12 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=549940 http://bugzilla.novell.com/show_bug.cgi?id=549940#c6 Michael Andres <ma@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |ma@novell.com Resolution|FIXED | --- Comment #6 from Michael Andres <ma@novell.com> 2009-11-27 14:14:07 UTC --- Hmm... # zypper in -t package test # grep force_resolution zypper.log 2009-11-27 14:52:15 <1> Fibonacci(26426) [zypper++] solve-commit.cc(set_force_resolution):271 force resolution: true ^^^^ but # zypper in -t package -t pattern test # grep force_resolution zypper.log 2009-11-27 14:53:09 <1> Fibonacci(26530) [zypper++] solve-commit.cc(set_force_resolution):271 force resolution: false ^^^^^ Do you really think it is a good idea to let force_resolution depend on the ammount and sequence of -t arguments? IMO worse than 'always on' is 'perhaps on'. Please consider using force resolve only when deleting, and never when installing. Then you can make up your mind whether to use --force always or never, instead of sometimes. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=549940 http://bugzilla.novell.com/show_bug.cgi?id=549940#c7 Ján Kupec <jkupec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED --- Comment #7 from Ján Kupec <jkupec@novell.com> 2009-11-27 14:40:45 UTC --- It does not depend on the amount, it's "force resolution only when there's only 'package'". I DID CONSIDER NOT USING FORCE-RESOLUTION FOR INSTALL. Many times. I'm starting to get sick of this discussion. You two (Michaels) bring it up from time to time, we exchange some arguments, but we never conclude it. Each time you left my (and not only my, there were also some users agreeing with me) arguments and questions unanswered and later bring it up anew!! grrr :O) I don't care anymore. I'll just change it as you want, and we'll see how people will like it, OK? Apart from that, have a nice weekend :O) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=549940 http://bugzilla.novell.com/show_bug.cgi?id=549940#c8 --- Comment #8 from Michael Andres <ma@novell.com> 2009-11-30 12:23:39 UTC --- Whatever we do, someone will complain. I see lots of bugs where people obviously do no understand why 'in' does it and 'up' does not. They don't seem to recognize (or expect), that a problem reported in 'up' corresponds with a package deleted in 'in'. Zypper should follow easy rules. The easiest rule would have been "per default report problems. Use 'force' to fore a resolution". Zyppers rule is slightly more complex: "zypper 'in' does force, 'up' does not". You are right that my suggestion was not objective, because I'd favor the easiest rule. Sorry for this. But you IMO should consider reverting your change. You should not use different solver options, just because a non-package is, or could be, on the commandline. Stay with the current rule and say: This bug is invalid. You need to use 'zypper in --no-force-resolution -t patch k3b'. Or enable 'zypper patch k3b'. That's pure patch installation. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=549940 http://bugzilla.novell.com/show_bug.cgi?id=549940#c9 --- Comment #9 from Ján Kupec <jkupec@novell.com> 2009-11-30 15:58:19 UTC --- (In reply to comment #8)
Whatever we do, someone will complain.
That's true :O)
I see lots of bugs where people obviously do no understand why 'in' does it and 'up' does not. They don't seem to recognize (or expect), that a problem reported in 'up' corresponds with a package deleted in 'in'.
Hmm.. yes, i agree.
Stay with the current rule and say: This bug is invalid. You need to use 'zypper in --no-force-resolution -t patch k3b'.
What about making it configurable in zypper.conf? [solver] <cut> ## Comma-separated list of commands in which the resolution should be forced ## when solving package dependencies. This means the solver ## will automatically opt to remove problematic packages instead ## of asking the user how to resolve the dependency problem. ## ## This is particularly useful in the 'remove' command, since one ## typically wants to remove the requested package and all the packages ## which depend on it, without being asked. But one may find it convenient ## to force the resolution also in the 'install' command, or perhaps even ## others. ## ## This setting can be overridden ad-hoc by the --force-resolution and ## --no-force-resolution command line options. ## ## Values: remove, install, update, patch, verify ## Default: remove forceResolution = remove, install
Or enable 'zypper patch k3b'. That's pure patch installation.
good idea, too -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=549940 http://bugzilla.novell.com/show_bug.cgi?id=549940#c10 Ján Kupec <jkupec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #10 from Ján Kupec <jkupec@novell.com> 2009-12-01 12:14:15 UTC --- i added the zypper.conf option, to be in zypper-1.2.12 -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=549940 http://bugzilla.novell.com/show_bug.cgi?id=549940#c11 Swamp Workflow Management <swamp@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard| |maint:released:11.2:32913 --- Comment #11 from Swamp Workflow Management <swamp@suse.com> 2010-05-06 15:04:56 UTC --- Update released for: PackageKit, PackageKit-debuginfo, PackageKit-debugsource, PackageKit-devel, PackageKit-doc, PackageKit-lang, libpackagekit-glib12, libpackagekit-glib12-debuginfo, libpackagekit-glib12-devel, libpackagekit-qt12, libpackagekit-qt12-debuginfo, libpackagekit-qt12-devel, libsatsolver, libsatsolver-debugsource, libsatsolver-demo, libsatsolver-demo-debuginfo, libsatsolver-devel, libsatsolver-devel-debuginfo, libzypp, libzypp-bindings, libzypp-debuginfo, libzypp-debugsource, libzypp-devel, perl-satsolver, perl-satsolver-debuginfo, perl-zypp, python-satsolver, python-satsolver-debuginfo, python-zypp, ruby-satsolver, ruby-satsolver-debuginfo, ruby-zypp, ruck, satsolver-tools, satsolver-tools-debuginfo, yast2-ncurses, yast2-ncurses-debuginfo, yast2-ncurses-debugsource, yast2-ncurses-devel, yast2-ncurses-pkg, yast2-ncurses-pkg-debuginfo, yast2-ncurses-pkg-debugsource, yast2-qt-pkg, yast2-qt-pkg-debuginfo, yast2-qt-pkg-debugsource, zypp-testsuite-tools, zypper, zypper-debuginfo, zypper-debugsource Products: openSUSE 11.2 (debug, i586, x86_64) -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com