Is this an appropriate forum for zypper questions?

Brian Reichert

7 Dec 2020 7 Dec '20

19:17

I have a mounting set of questions about zypper, which don't seem to be addressed by any online docs I've read so far. I don't know if this is an appropriate forum, and am happy for any pointers to a better one. My issues are under SLES 12, but I find those forums relatively unresponsive. I'm assuming that SLES's version of 'zypper' isn't critically different than other SuSE-related distributions, so hopefully this is a good alternative. One such question: One on SLES 12 host, I sucessfully installed 'createrepo' with zypper, and retained the RPM package. I've copied it to another SLES 12 host, and am attempting to install it via 'zypper': localhost:~ # zypper --no-gpg-checks --no-remote install -y - /home/prior_release_RPM/createrepo-0.10.3-2.8.x86_64.rpm ... Reading installed packages... Resolving package dependencies... 2 Problems: Problem: createrepo-0.10.3-2.8.x86_64 requires /bin/sh, but this requirement cannot be provided Problem: This request will break your system! Solution 1: Following actions will be done: keep bash-4.3-83.23.1.x86_64 ... Solution 2: do not install createrepo-0.10.3-2.8.x86_64 Solution 3: break createrepo-0.10.3-2.8.x86_64 by ignoring some of its dependencies What is zypper trying to convey here? The local RPM database is quite aware of the presense of the 'bash' package, and what it provides: localhost:~ # rpm -q --whatprovides /bin/sh bash-4.3-83.23.1.x86_64 'zypper' seems to, as well: localhost:~ # zypper --no-remote info --provides bash ... Provides : [6] bash = 4.3-83.23.1 bash(x86-64) = 4.3-83.23.1 config(bash) = 4.3-83.23.1 /bin/sh /bin/bash /usr/bin/sh Some details of my environment; let me know if any others would be helpful: localhost:~ # cat /etc/issue Welcome to SUSE Linux Enterprise Server 12 SP5 (x86_64) - Kernel \r (\l). localhost:~ # rpm -q zypper rpm zypper-1.13.57-21.32.1.x86_64 rpm-4.11.2-16.21.1.x86_64 -- Brian Reichert BSD admin/developer at large

Show replies by date

Carlos E. R.

8 Dec 8 Dec

01:38

On 07/12/2020 20.17, Brian Reichert wrote:

...

I have a mounting set of questions about zypper, which don't seem to be addressed by any online docs I've read so far.

I don't know if this is an appropriate forum, and am happy for any pointers to a better one.

Of course it is.

...

My issues are under SLES 12, but I find those forums relatively unresponsive.

Well, that's a problem, because this is an openSUSE forum. I know verly little about SLES, so I can only answer assuming that it is sufficiently similar to Leap. But SLES 12 is old, around 2014.

...

I'm assuming that SLES's version of 'zypper' isn't critically different than other SuSE-related distributions, so hopefully this is a good alternative.

On SLES there must be some method of verification that you are a client to be able to download updates. There is nothing like that on Leap - that's an important difference.

...

One such question:

One on SLES 12 host, I sucessfully installed 'createrepo' with zypper, and retained the RPM package.

I've copied it to another SLES 12 host, and am attempting to install it via 'zypper':

localhost:~ # zypper --no-gpg-checks --no-remote install -y - /home/prior_release_RPM/createrepo-0.10.3-2.8.x86_64.rpm ... Reading installed packages... Resolving package dependencies... 2 Problems: Problem: createrepo-0.10.3-2.8.x86_64 requires /bin/sh, but this requirement cannot be provided Problem: This request will break your system! Solution 1: Following actions will be done: keep bash-4.3-83.23.1.x86_64 ... Solution 2: do not install createrepo-0.10.3-2.8.x86_64 Solution 3: break createrepo-0.10.3-2.8.x86_64 by ignoring some of its dependencies

What is zypper trying to convey here? The local RPM database is quite aware of the presense of the 'bash' package, and what it provides:

Sorry, I have never seen anything similar. But normally, I would install a lone rpm using the "rpm" command. Or I would add a local disk repository with YaST. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)

Tomas Kuchta

05:41

Zypper works the same in SLES and openSuSE. You need subscription to update SLES, probably not 12.0 anymore .... On Mon, Dec 7, 2020, 17:38 Carlos E. R. wrote:

...

On 07/12/2020 20.17, Brian Reichert wrote:

...
I have a mounting set of questions about zypper, which don't seem to be addressed by any online docs I've read so far.

I don't know if this is an appropriate forum, and am happy for any pointers to a better one.

Of course it is.

...
My issues are under SLES 12, but I find those forums relatively unresponsive.

Well, that's a problem, because this is an openSUSE forum. I know verly little about SLES, so I can only answer assuming that it is sufficiently similar to Leap.

But SLES 12 is old, around 2014.

...
I'm assuming that SLES's version of 'zypper' isn't critically different than other SuSE-related distributions, so hopefully this is a good alternative.

On SLES there must be some method of verification that you are a client to be able to download updates. There is nothing like that on Leap - that's an important difference.

...
One such question:

One on SLES 12 host, I sucessfully installed 'createrepo' with zypper, and retained the RPM package.

I've copied it to another SLES 12 host, and am attempting to install it via 'zypper':

localhost:~ # zypper --no-gpg-checks --no-remote install -y -

/home/prior_release_RPM/createrepo-0.10.3-2.8.x86_64.rpm

...
... Reading installed packages... Resolving package dependencies... 2 Problems: Problem: createrepo-0.10.3-2.8.x86_64 requires /bin/sh, but this requirement cannot be provided Problem: This request will break your system! Solution 1: Following actions will be done: keep bash-4.3-83.23.1.x86_64 ... Solution 2: do not install createrepo-0.10.3-2.8.x86_64 Solution 3: break createrepo-0.10.3-2.8.x86_64 by ignoring some of its dependencies

What is zypper trying to convey here? The local RPM database is quite aware of the presense of the 'bash' package, and what it provides: .

It seems that createrepo.rpm needs newer bash and because it cannot install it (because no-remote or because it isn't in your repos) it presents with difficult choices. You have bunch of options to try depending on your circumstances: 1. Let zypper use repos, hoping that it will find what it needs. 2. Get older version of createrepo.rpm which will be happy with what you have. 3. Keep the bash you have and install createrepo anyway, hoping for the best. .... 7. Upgrade to recent SLES or open SuSe Leap (15.2 is current) .... Hope that helps, Tomas

Andrei Borzenkov

06:13

07.12.2020 22:17, Brian Reichert пишет:

...

I have a mounting set of questions about zypper, which don't seem to be addressed by any online docs I've read so far.

I don't know if this is an appropriate forum, and am happy for any pointers to a better one.

My issues are under SLES 12, but I find those forums relatively unresponsive. I'm assuming that SLES's version of 'zypper' isn't critically different than other SuSE-related distributions, so hopefully this is a good alternative.

One such question:

One on SLES 12 host, I sucessfully installed 'createrepo' with zypper, and retained the RPM package.

I've copied it to another SLES 12 host, and am attempting to install it via 'zypper':

localhost:~ # zypper --no-gpg-checks --no-remote install -y - /home/prior_release_RPM/createrepo-0.10.3-2.8.x86_64.rpm ... Reading installed packages... Resolving package dependencies... 2 Problems: Problem: createrepo-0.10.3-2.8.x86_64 requires /bin/sh, but this requirement cannot be provided Problem: This request will break your system! Solution 1: Following actions will be done: keep bash-4.3-83.23.1.x86_64 ... Solution 2: do not install createrepo-0.10.3-2.8.x86_64 Solution 3: break createrepo-0.10.3-2.8.x86_64 by ignoring some of its dependencies

What is zypper trying to convey here? The local RPM database is quite aware of the presense of the 'bash' package, and what it provides:

localhost:~ # rpm -q --whatprovides /bin/sh bash-4.3-83.23.1.x86_64

If you read carefully - zypper offers to "keep" bash which means something causes bash removal for proper resolution. Unfortunately zypper is notoriously bad at presenting explanation *why* it has problems. It only shows how it is going to resolve them. Trying verbose output or checking logs may help. If you create solver test case (see zypper manual) and make it available someone with sufficient knowledge and time may look into it. What happens if you use rpm to install this package? If there are some unresolved dependencies rpm will fail right away and it may hint at root cause.

...

'zypper' seems to, as well:

localhost:~ # zypper --no-remote info --provides bash ... Provides : [6] bash = 4.3-83.23.1 bash(x86-64) = 4.3-83.23.1 config(bash) = 4.3-83.23.1 /bin/sh /bin/bash /usr/bin/sh

Some details of my environment; let me know if any others would be helpful:

localhost:~ # cat /etc/issue

Welcome to SUSE Linux Enterprise Server 12 SP5 (x86_64) - Kernel \r (\l).

localhost:~ # rpm -q zypper rpm zypper-1.13.57-21.32.1.x86_64 rpm-4.11.2-16.21.1.x86_64

Isgleas, Francisco

10:25

On Mon, Dec 7, 2020 at 8:17 PM Brian Reichert wrote:

...

localhost:~ # zypper --no-gpg-checks --no-remote install -y - /home/prior_release_RPM/createrepo-0.10.3-2.8.x86_64.rpm

Reading that line, it looks like you are trying to uninstall that package by adding that '-' alone: From 'man zypper': "In the install command, you can also specify packages you wish to remove by prepending their names by a - or ! character." If you are trying to install that package, try removing that dash, Hth Francisco

Brian Reichert

17:54

On Tue, Dec 08, 2020 at 11:25:44AM +0100, Isgleas, Francisco wrote:

...

On Mon, Dec 7, 2020 at 8:17 PM Brian Reichert wrote:

...
localhost:~ # zypper --no-gpg-checks --no-remote install -y - /home/prior_release_RPM/createrepo-0.10.3-2.8.x86_64.rpm

Reading that line, it looks like you are trying to uninstall that package by adding that '-' alone:

From 'man zypper': "In the install command, you can also specify packages you wish to

remove by prepending their names by a - or ! character."

If you are trying to install that package, try removing that dash,

Indeed, removing that dash does allow the package to be installed. The manpage, on the topic of install says: - you can also specify packages you wish to remove by prepending their names by a - or ! character. - that if you choose to use - with the first package you specify, you need to write -- before it to prevent its interpretation as a command option I did intend to use the '--', so your suggestion revealed a typo in my invocation. Note that my dash did not prepend a name, it was separated by a space, and hence was not part of a package name. I actually have no idea how zypper interpreted this incorrect use. Thanks for the second set of eyes!

...

Hth Francisco

...

_______________________________________________ openSUSE Support mailing list -- support@lists.opensuse.org To unsubscribe, email support-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/support@lists.opensuse.org

-- Brian Reichert BSD admin/developer at large

Andrei Borzenkov

18:26

08.12.2020 20:54, Brian Reichert пишет:

...

On Tue, Dec 08, 2020 at 11:25:44AM +0100, Isgleas, Francisco wrote:

...
On Mon, Dec 7, 2020 at 8:17 PM Brian Reichert wrote:

...
localhost:~ # zypper --no-gpg-checks --no-remote install -y - /home/prior_release_RPM/createrepo-0.10.3-2.8.x86_64.rpm

Reading that line, it looks like you are trying to uninstall that package by adding that '-' alone:

From 'man zypper': "In the install command, you can also specify packages you wish to

remove by prepending their names by a - or ! character."

If you are trying to install that package, try removing that dash,

Indeed, removing that dash does allow the package to be installed.

The manpage, on the topic of install says:

- you can also specify packages you wish to remove by prepending their names by a - or ! character.

- that if you choose to use - with the first package you specify, you need to write -- before it to prevent its interpretation as a command option

I did intend to use the '--', so your suggestion revealed a typo in my invocation.

Note that my dash did not prepend a name, it was separated by a space, and hence was not part of a package name.

I actually have no idea how zypper interpreted this incorrect use.

Thanks for the second set of eyes!

Yes, really good catch. zypper install - attempts to remove everything. I would expect simply usage error. Care to open bug report?

Brian Reichert

9 Dec 9 Dec

22:50

On Tue, Dec 08, 2020 at 09:26:38PM +0300, Andrei Borzenkov wrote:

...

Yes, really good catch.

zypper install -

attempts to remove everything. I would expect simply usage error. Care to open bug report?

With who? I really don't understand the SUSE ecosystem...

...

_______________________________________________ openSUSE Support mailing list -- support@lists.opensuse.org To unsubscribe, email support-leave@lists.opensuse.org List Netiquette: https://en.opensuse.org/openSUSE:Mailing_list_netiquette List Archives: https://lists.opensuse.org/archives/list/support@lists.opensuse.org

-- Brian Reichert BSD admin/developer at large

Carlos E. R.

22:54

On 09/12/2020 23.50, Brian Reichert wrote:

...

On Tue, Dec 08, 2020 at 09:26:38PM +0300, Andrei Borzenkov wrote:

...
Yes, really good catch.

zypper install -

attempts to remove everything. I would expect simply usage error. Care to open bug report?

With who? I really don't understand the SUSE ecosystem...

openSUSE bugzilla. https://en.opensuse.org/openSUSE:Submitting_bug_reports But if what you have is SLES, I have no idea where. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)

1247

Age (days ago)

1249

Last active (days ago)

List overview

Download

8 comments

5 participants

participants (5)

Andrei Borzenkov
Brian Reichert
Carlos E. R.
Isgleas, Francisco
Tomas Kuchta

Is this an appropriate forum for zypper questions?

tags

participants (5)