[Bug 389694] New: zypper: confusing update behaviour on "zypper up zypper"
https://bugzilla.novell.com/show_bug.cgi?id=389694 Summary: zypper: confusing update behaviour on "zypper up zypper" Product: openSUSE 11.0 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: libzypp AssignedTo: jkupec@novell.com ReportedBy: kkaempf@novell.com QAContact: dmacvicar@novell.com CC: mls@novell.com Found By: --- 1. zypper reports "zypper not installed" which is wrong, see rpm -q below 2. zypper installs lots of unrelated packages zypper (resp. sat-solver) should only honor those recommends/supplements which belong to the current transaction
sudo zypper up zypper Reading installed packages... Package 'zypper' is not installed.
The following NEW packages are going to be installed: pacemaker libnet heartbeat-resources heartbeat-core heartbeat Overall download size: 1.6 M. After the operation, additional 7.0 M will be used. Continue? [YES/no]: Downloading package libnet-1.1.2.1-114.x86_64, 241.0 K (1.8 M unpacked) Downloading: libnet-1.1.2.1-114.x86_64.rpm [done] Installing: libnet-1.1.2.1-114 [done] Downloading package heartbeat-core-2.1.3-13.x86_64, 334.0 K (1.2 M unpacked) Downloading: heartbeat-core-2.1.3-13.x86_64.rpm [done] Installing: heartbeat-core-2.1.3-13 [done] Downloading package heartbeat-resources-2.1.3-13.x86_64, 116.0 K (475.0 K unpacked) Downloading: heartbeat-resources-2.1.3-13.x86_64.rpm [done] Installing: heartbeat-resources-2.1.3-13 [done] Downloading package heartbeat-2.1.3-13.x86_64, 373.0 K (1.3 M unpacked) Downloading: heartbeat-2.1.3-13.x86_64.rpm [done] Installing: heartbeat-2.1.3-13 [done] Downloading package pacemaker-0.6.3-8.x86_64, 565.0 K (2.2 M unpacked) Downloading: pacemaker-0.6.3-8.x86_64.rpm [done] Installing: pacemaker-0.6.3-8 [done] kkaempf@heron:~> rpm -q zypper zypper-0.11.1-3 kkaempf@heron:~> -- 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=389694
User kkaempf@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c1
--- Comment #1 from Klaus Kämpf
https://bugzilla.novell.com/show_bug.cgi?id=389694
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c2
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=389694
User schubi@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c3
Stefan Schubert
https://bugzilla.novell.com/show_bug.cgi?id=389694
User kkaempf@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c4
Klaus Kämpf
https://bugzilla.novell.com/show_bug.cgi?id=389694
User mls@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c5
--- Comment #5 from Michael Schröder
https://bugzilla.novell.com/show_bug.cgi?id=389694
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c6
Ján Kupec
comment #1: 2. "zypper (resp. sat-solver) should only honor those recommends/supplements which belong to the current transaction" That would break our new feature installing language depend packages or additional kmp packages if a repo or a new hardware has been installed by the user.
Whooo, may be a cool feature, but also one of the most annoying ones, really. Especially if we don't provide a way to get away with these automatic additional packages!
comment #2: a, see above b, That would be too generally and not understandable for the user while future zypper/UI calls.
Hm. But how to solve this then? zypper in foo wants to install a lot of totaly unrelated recommended packages and there is no way to get away with them other than always using --no-recommends or by letting them to install and them removing them manually one by one.... we _need_ an acceptable solution for this. IMO, b) would be a good solution. Why do you think it would confuse users? You run zypper in, check what it's going to install, you don't like it, you retry with --no-recomends, you like it. Soft locks saved, you won't see the then would-be-selected recommends automatically popping up again. What's wrong with that? -- 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=389694
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c7
Ján Kupec
(In reply to comment #3 from Stefan Schubert)
comment #1: 2. "zypper (resp. sat-solver) should only honor those recommends/supplements which belong to the current transaction" That would break our new feature installing language depend packages or additional kmp packages if a repo or a new hardware has been installed by the user.
Whooo, may be a cool feature, but also one of the most annoying ones, really. Especially if we don't provide a way to get away with these automatic additional packages!
But nevertheless, is the feature supposed to work like this? -- 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=389694
User visnov@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c8
Stanislav Visnovsky
(In reply to comment #3 from Stefan Schubert)
comment #1: 2. "zypper (resp. sat-solver) should only honor those recommends/supplements which belong to the current transaction" That would break our new feature installing language depend packages or additional kmp packages if a repo or a new hardware has been installed by the user.
Whooo, may be a cool feature, but also one of the most annoying ones, really. Especially if we don't provide a way to get away with these automatic additional packages!
comment #2: a, see above b, That would be too generally and not understandable for the user while future zypper/UI calls.
Hm. But how to solve this then? zypper in foo wants to install a lot of totaly unrelated recommended packages and there is no way to get away with them other than always using --no-recommends or by letting them to install and them removing them manually one by one.... we _need_ an acceptable solution for this.
IMO, b) would be a good solution. Why do you think it would confuse users? You run zypper in, check what it's going to install, you don't like it, you retry with --no-recomends, you like it. Soft locks saved, you won't see the then would-be-selected recommends automatically popping up again. What's wrong with that?
This is usability nightmare. The first impression counts and here is the impression 'I told zypper to do one thing and it does another one'. It is even unclear that user should use '--no-recommends'. I agree with comment #4. -- 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=389694
User coolo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c9
--- Comment #9 from Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=389694
User visnov@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c10
--- Comment #10 from Stanislav Visnovsky
https://bugzilla.novell.com/show_bug.cgi?id=389694
User schubi@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c11
Stefan Schubert
https://bugzilla.novell.com/show_bug.cgi?id=389694
User visnov@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c12
--- Comment #12 from Stanislav Visnovsky
https://bugzilla.novell.com/show_bug.cgi?id=389694
User coolo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c13
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=389694
User visnov@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c14
--- Comment #14 from Stanislav Visnovsky
https://bugzilla.novell.com/show_bug.cgi?id=389694
User schubi@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c15
--- Comment #15 from Stefan Schubert
https://bugzilla.novell.com/show_bug.cgi?id=389694
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c16
--- Comment #16 from Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=389694
User mls@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c17
--- Comment #17 from Michael Schröder
https://bugzilla.novell.com/show_bug.cgi?id=389694
User kkaempf@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c18
--- Comment #18 from Klaus Kämpf
https://bugzilla.novell.com/show_bug.cgi?id=389694
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c19
--- Comment #19 from Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=389694
User mls@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c20
--- Comment #20 from Michael Schröder
https://bugzilla.novell.com/show_bug.cgi?id=389694
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c21
--- Comment #21 from Ján Kupec
I meant "--update-softlocks" without any other arguments. It would set the soft locks so that all recommended packages that aren't installed are added.
That wouldn't be too useful, especially after we introduce .zypperrc. What would make sense IMO is to save the softlocks for the recommends for the specific operation, like 'install foo' (those which --no-recommends would ignore during that operation).
Regarding #18: Maybe it doesn't make sense for zypper, but it makes sense for the yast UI.
Sure. Yast users will just deselect what they don't like and the softlocks will be saved (??) for such packages. -- 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=389694
User mls@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c24
--- Comment #24 from Michael Schröder
https://bugzilla.novell.com/show_bug.cgi?id=389694
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c25
Ján Kupec
https://bugzilla.novell.com/show_bug.cgi?id=389694
User coolo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c26
--- Comment #26 from Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=389694
User coolo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c28
Stephan Kulow
https://bugzilla.novell.com/show_bug.cgi?id=389694
User schubi@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c29
Stefan Schubert
https://bugzilla.novell.com/show_bug.cgi?id=389694
User jkupec@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=389694#c30
Ján Kupec
participants (1)
-
bugzilla_noreply@novell.com