[opensuse-factory] new noise from zypper
zypper -v dup is now announcing packages locked which are not installed (most set at installation time to prevent them from being installed via future dep changes or otherwise). Is this intentional? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/19/2015 08:32 PM, Felix Miata wrote:
zypper -v dup is now announcing packages locked which are not installed (most set at installation time to prevent them from being installed via future dep changes or otherwise). Is this intentional?
Yes, it is intentional to report packages which are locked (both installed and not-installed). The reason is that the locks may prevent other packages from being updated, be it due to versioned dependencies or new dependencies introduced in the new version of such packages and users should be aware of such constraints. Jiri -- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.com Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.com -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Jiri Srain composed on 2015-03-20 07:55 (UTC+0100):
Felix Miata wrote:
zypper -v dup is now announcing packages locked which are not installed (most set at installation time to prevent them from being installed via future dep changes or otherwise). Is this intentional?
Yes, it is intentional to report packages which are locked (both installed and not-installed). The reason is that the locks may prevent other packages from being updated, be it due to versioned dependencies or new dependencies introduced in the new version of such packages and users should be aware of such constraints.
On my systems this list amounts to nothing but noise, as there are typically more locks set than the number of rows in a terminal, not unusually more than 40. The current format strings endlessly across the screen down several rows. As I've typically done '# zypper ll' shortly before '# zypper -v dup', the new output tells me nothing I don't already know, and does so in a less useful format. I would find being told what will be (or was) skipped line by line due to locks to be more useful than the current single string dump. Zypper has told us previously what update packages were held back. I don't see how this change amounts to any improvement. Better the output follow the process, allowing holdbacks to be listed for subsequent decision whether to remove any locks and repeat the update/upgrade. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/20/2015, 07:55 AM, Jiri Srain wrote:
On 03/19/2015 08:32 PM, Felix Miata wrote:
zypper -v dup is now announcing packages locked which are not installed (most set at installation time to prevent them from being installed via future dep changes or otherwise). Is this intentional?
Yes, it is intentional to report packages which are locked (both installed and not-installed). The reason is that the locks may prevent other packages from being updated, be it due to versioned dependencies or new dependencies introduced in the new version of such packages and users should be aware of such constraints.
Obvious question: how to turn that off? 1000 lines over serial console is not fun and I know what I am doing -- I don't care about the output at all. $ zypper -v dup -l --no-r|wc -c 94927 The most hitting lock is '*32bit' here. thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/20/2015, 09:17 AM, Jiri Slaby wrote:
On 03/20/2015, 07:55 AM, Jiri Srain wrote:
On 03/19/2015 08:32 PM, Felix Miata wrote:
zypper -v dup is now announcing packages locked which are not installed (most set at installation time to prevent them from being installed via future dep changes or otherwise). Is this intentional?
Yes, it is intentional to report packages which are locked (both installed and not-installed). The reason is that the locks may prevent other packages from being updated, be it due to versioned dependencies or new dependencies introduced in the new version of such packages and users should be aware of such constraints.
Obvious question: how to turn that off? 1000 lines over serial console is not fun and I know what I am doing -- I don't care about the output at all.
If the author of the change wants to make it actually useful, they should report only packages which are locked and: * are installed AND newer/another version is available, OR * are not installed AND is soft/required by an unlocked package thanks, -- js suse labs -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I think it should: - - report *only all* of those, which are affected by a current installation case in some way, no matter if a newer/another version is available; - - have an option to configure it for enable/disable in config (with the default state - enabled) and also for command-line; And then you can just continue to use list locks command as usual to see all of the locks on the system, when needed. 20.03.2015 10:21, Jiri Slaby пишет:
On 03/20/2015, 09:17 AM, Jiri Slaby wrote:
On 03/20/2015, 07:55 AM, Jiri Srain wrote:
On 03/19/2015 08:32 PM, Felix Miata wrote:
zypper -v dup is now announcing packages locked which are not installed (most set at installation time to prevent them from being installed via future dep changes or otherwise). Is this intentional?
Yes, it is intentional to report packages which are locked (both installed and not-installed). The reason is that the locks may prevent other packages from being updated, be it due to versioned dependencies or new dependencies introduced in the new version of such packages and users should be aware of such constraints.
Obvious question: how to turn that off? 1000 lines over serial console is not fun and I know what I am doing -- I don't care about the output at all.
If the author of the change wants to make it actually useful, they should report only packages which are locked and: * are installed AND newer/another version is available, OR * are not installed AND is soft/required by an unlocked package
thanks,
-----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVC+MVAAoJEHRzCo0swmJSw+YQAKn/ZPgs6SWJ7FBojGYPG6RC tl86jhqfuw6yCXRLu9T4lnh4To9bpKtT/09CcV/kaApwt9UpSAuWsN62vwgr2IJb EsNrHCXMOzNYNElnIM/e1B31mwQ+c2SOJYgQ541Z1sYGkppxipBOHRz/b/Wfk0bq dMiVFz3qzDhUEc9DqXvnftzkUCtfGLyZI93j+G1ogQGKS1wMt3giCUeE8W3RhUDJ MWd6dxHMm2dPnpPnIAqzRYA5XKjyYq+WgUpQwmIft2z1X9yVoZFE5VvewnKNnyYD b523OEW9QWZ//iMZGHtwJWtU1O3d49YKUAMAvgTDVD0yW8Y+qnl8/kyCXybBLOOr xt1LgNOEsl93LWk8a8RqHRHrrLoTIs9CMjZatlyvGORjQ/xRVkL+HpBaSsIg8NGx s9kua1ZQe/NoDm1hXtky8YoZR5AMD7YjbCzUmTcOgtVuQi51GIWpQg1snMwHMha+ Z6fWRhVQ/F4LjYGWWW04TrKTDhuA7DPYVcpSlxvs3dul4eMU6URkFTA7Y8iZY23S DgucihBV5N/318N9D/EMbhYz2DsPi/aouXkbTSFB6fr8188MF/MUi0OxU6yrHoV9 XTLvJS/R/QBbTllEnuWTQlEDlQ4RztywqAsOlU0yufuQ7Dgg9x/+rLQChnPTWkgJ w1jo6AkI82Ppk+XoIT/G =yXLU -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 03/20/2015 09:21 AM, Jiri Slaby wrote:
On 03/20/2015, 09:17 AM, Jiri Slaby wrote:
On 03/20/2015, 07:55 AM, Jiri Srain wrote:
On 03/19/2015 08:32 PM, Felix Miata wrote:
zypper -v dup is now announcing packages locked which are not installed (most set at installation time to prevent them from being installed via future dep changes or otherwise). Is this intentional?
Yes, it is intentional to report packages which are locked (both installed and not-installed). The reason is that the locks may prevent other packages from being updated, be it due to versioned dependencies or new dependencies introduced in the new version of such packages and users should be aware of such constraints.
Obvious question: how to turn that off? 1000 lines over serial console is not fun and I know what I am doing -- I don't care about the output at all.
If the author of the change wants to make it actually useful, they should report only packages which are locked and: * are installed AND newer/another version is available, OR * are not installed AND is soft/required by an unlocked package
* are installed AND a non-installed package/version conflicts with them * themselves conflics with an uninstalled package/version I'm not sure that this list is complete... Jiri -- Regards, Jiri Srain Project Manager --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.com Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 Czech Republic http://www.suse.com -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (4)
-
Felix Miata -
Jiri Slaby -
Jiri Srain -
Opensuse user