[Bug 772353] New: zypper -n interactive with packagekit
https://bugzilla.novell.com/show_bug.cgi?id=772353 https://bugzilla.novell.com/show_bug.cgi?id=772353#c0 Summary: zypper -n interactive with packagekit Classification: openSUSE Product: openSUSE 12.2 Version: Factory Platform: All OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: gs@suse.com ReportedBy: bwiedemann@suse.com QAContact: qa-bugs@suse.de Found By: System Test Blocker: --- In automated openQA tests I noticed that zypper -n patch will still interactively ask "Tell PackageKit to quit? [yes/no] (no): " if packagekit is blocking it When calling zypper -n in scripts, the expectation is usually that when it returns, it has done its work, so forcing the termination of packagekit in this case would be the right thing. Or at least provide some --force-quit-packagekit option -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=772353 https://bugzilla.novell.com/show_bug.cgi?id=772353#c Gabriele Mohr <gs@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=772353 https://bugzilla.novell.com/show_bug.cgi?id=772353#c1 Gabriele Mohr <gs@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |ma@suse.com --- Comment #1 from Gabriele Mohr <gs@suse.com> 2012-10-18 13:19:59 UTC --- I have tested on 12.2. 'zypper' in non-interactive mode doesn't ask "Tell PackageKit to quit?" but terminates immediately. The function read_bool_answer() returns the default answer when running in non-interactive mode and this is set to "false", see Zypper.cc, line 2565 bool reply = read_bool_answer(PROMPT_PACKAGEKIT_QUIT, _("Tell PackageKit to quit?"), false); In my opinion we shouldn't set the default answer to "true" and with it change the behaviour of zypper in non-interactive mode. Trying to stop 'packagekit' may fail for various reasons and 'zypper' wouldn't stop at all. I talked to Bernhard and we found a possible solution. Let the behaviour like it is and return an extra error code. This code can be used in scripts to call 'zypper -n ...' again. In think this is better than adding an additional option like --non-interactive-stop-packagekit'. Michel, what's your opinion? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=772353 https://bugzilla.novell.com/show_bug.cgi?id=772353#c2 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|ma@suse.com | --- Comment #2 from Michael Andres <ma@suse.com> 2012-10-18 15:37:36 CEST --- (In reply to comment #1)
I talked to Bernhard and we found a possible solution. Let the behaviour like it is and return an extra error code. This code can be used in scripts to call 'zypper -n ...' again.
In think this is better than adding an additional option like --non-interactive-stop-packagekit'.
yes -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=772353 https://bugzilla.novell.com/show_bug.cgi?id=772353#c3 Gabriele Mohr <gs@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |bwiedemann@suse.com --- Comment #3 from Gabriele Mohr <gs@suse.com> 2012-10-23 10:09:37 UTC --- Bernhard, is it necessary to distinguish between libzypp locked by packagekit and locked by another application, e.g. yast? I would return ZYPPER_EXIT_ZYPP_LOCKED (7) for both. Locked is locked and one can try to call 'zypper' several times then. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=772353 https://bugzilla.novell.com/show_bug.cgi?id=772353#c4 Gabriele Mohr <gs@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED InfoProvider|bwiedemann@suse.com | Resolution| |FIXED --- Comment #4 from Gabriele Mohr <gs@suse.com> 2012-10-24 08:23:50 UTC --- 'zypper' now returns ZYPPER_EXIT_ZYPP_LOCKED (7) if libzypp is locked by another application, the man page is adapted (I have created the pull request on github). -- Configure bugmail: https://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