Andrei Borzenkov wrote:

24.11.2017 12:03, Per Jessen пишет:

...

I'm sure someone has a quick explanation:

a) zypper addrepo 'https://download.opensuse.org/repositories/Virtualization:containers/openSUS...'

This fails:

Download (curl) error for 'https://download.opensuse.org/repositories/Virtualization:containers/openSUS...': Error code: Bad URL Error message: Protocol http not supported or disabled in libcurl

b) zypper addrepo 'https://download.opensuse.org/repositories/Virtualization:/containers/openSU...'

Works fine. (notice the extra slash between 'Virtualization:' and 'container'.

https://forums.opensuse.org/showthread.php/527052-Cached-files-in-home-cache...

Let me quote:

That openSUSE download server still does not support https, is indeed server problem. It does follow 301 redirection, but zypper explicitly restricts redirection to https only in this case. Note that error message says "Protocol http not supported or disabled in libcurl", not https

Thanks for digging that out, Andrei. Okay. I think the final message is - we should not be using https:// URLs for download.o.o. Getting every openSUSE mirror to support https:// is highly unlikely, and getting mirrorbrain to support https is probably even more unlikely. I guess I might wonder why zypper prohibits the redirect from https to http. Firefox doesn't seem to mind. -- Per Jessen, Zürich (10.9°C) http://www.dns24.ch/ - your free DNS host, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

24.11.2017 23:17, Per Jessen пишет:

Per Jessen wrote:

...

Andrei Borzenkov wrote:

...

24.11.2017 12:03, Per Jessen пишет:

...

I'm sure someone has a quick explanation:

a) zypper addrepo 'https://download.opensuse.org/repositories/Virtualization:containers/openSUS...'

This fails:

Download (curl) error for 'https://download.opensuse.org/repositories/Virtualization:containers/openSUS...': Error code: Bad URL Error message: Protocol http not supported or disabled in libcurl

b) zypper addrepo 'https://download.opensuse.org/repositories/Virtualization:/containers/openSU...'

Works fine. (notice the extra slash between 'Virtualization:' and 'container'.

https://forums.opensuse.org/showthread.php/527052-Cached-files-in-home-cache...

Let me quote:

...

That openSUSE download server still does not support https, is indeed server problem. It does follow 301 redirection, but zypper explicitly restricts redirection to https only in this case. Note that error message says "Protocol http not supported or disabled in libcurl", not https

Thanks for digging that out, Andrei.

I was too fast. It doesn't quite explain it though.

Why does a) fail and b) work?

Did you read follow-up posts? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Fri, 24 Nov 2017 21:00:36 +0100 Per Jessen wrote:

Getting every openSUSE mirror to support https:// is highly unlikely

It seems like that should be a priority for 'the-powers-that-be'? Why would 'we' want any mirrors using plain http? Now maybe I'm ignorant and everything is protected by individual signatures on each package or somesuch so the transport is irrelevant, but naive people like me would feel better if https was used. Cheers, Dave -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Fri, 24 Nov 2017 21:54:25 +0100 Per Jessen wrote:

Dave Howorth wrote:

...

On Fri, 24 Nov 2017 21:00:36 +0100 Per Jessen wrote:

...

Getting every openSUSE mirror to support https:// is highly unlikely

It seems like that should be a priority for 'the-powers-that-be'?

Hi Dave

it's simply not likely to happen:

https://progress.opensuse.org/news/40

...

Why would 'we' want any mirrors using plain http?

It is more the other way around - why would a mirror want to offer https:// ?

...

Now maybe I'm ignorant and everything is protected by individual signatures on each package or somesuch so the transport is irrelevant, but naive people like me would feel better if https was used.

Absolutely, which is probably some well-intentioned soul changed links and enabled download.o.o for https. Unfortunately it just won't work. Not in the short term certainly.

Thanks for the reply and pointer,Per, much appreciated. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Hi - I suddenly have hit a problem after reboot and I kinda suspect I may have had a disk drive error of some kind but need some help recovering. I am running OpenSuSE Leap 42.3 and after doing a reboot I discovered a number of services (such as Apache2, OpenSSH, Named, Clamd, and a few others) had failed to start. My detective work (such as it is, I am no expert on this stuff) seems to lead me to believe I may have a corrupt file as a lot of errors in the /var/log/messages file seem to point at "/usr/lib64/libgssapi_krb5.so.2: invalid ELF header" So thinking something must be wrong with this file I thought I would get Yast2 to reinstall it for me, but when I tried to bring up the Software Manager I ran into yet another failure in that it would not load and gave me an error message which unfortunately I cannot copy/paste to show. But I did take a look at y2logs and got the following messages which I think encapsulates the problem and shows it too is having troubles with the same file -

2018-04-03 21:09:34 <1> bigbang(4728) [Interpreter] bin/y2start:56 Calling YaST client sw_single 2018-04-03 21:09:34 <1> bigbang(4728) [Ruby] yast/wfm.rb:295 Call client /usr/share/YaST2/clients/sw_single.rb 2018-04-03 21:09:34 <3> bigbang(4728) [liby2] Y2PluginComponent.cc(loadPlugin):234 error loading plugin /usr/lib64/YaST2/plugin/libpy2Pkg.so.2: /usr/lib64/libgssapi_krb5.so.2: invalid ELF header 2018-04-03 21:09:34 <3> bigbang(4728) [liby2] Y2PluginComponent.cc(loadPlugin):234 error loading plugin /usr/lib64/YaST2/plugin/libpy2Pkg.so.2: /usr/lib64/libgssapi_krb5.so.2: invalid ELF header 2018-04-03 21:09:34 <3> bigbang(4728) [Interpreter] bin/y2start:56 Loading module 'Pkg' failed 2018-04-03 21:09:34 <3> bigbang(4728) [libycp] Import.cc(import):97 No matching component found 2018-04-03 21:09:34 <3> bigbang(4728) [Ruby] binary/Yast.cc(getNs):67 ruby call: Can't import namespace 'Pkg' 2018-04-03 21:09:34 <2> bigbang(4728) [Ruby] yast/builtins.rb:586 tostring builtin called on wrong type Class 2018-04-03 21:09:34 <3> bigbang(4728) [Ruby] yast/wfm.rb:253 Client call failed with 'component cannot import namespace 'Pkg'' (NameError) and backtrace ["/usr/lib64/ruby/vendor_ruby/2.1.0/yast/yast.rb:178:in `import_pure'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/yast.rb:178:in `import'", "/usr/share/YaST2/clients/sw_single.rb:22:in `main'", "/usr/share/YaST2/clients/sw_single.rb:814:in `'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:300:in `eval'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:300:in `run_client'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:206:in `call_builtin'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:206:in `call_builtin_wrapper'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:195:in `CallFunction'", "/usr/lib/YaST2/bin/y2start:56:in `<main>'"] 2018-04-03 21:09:34 <3> bigbang(4728) [Ruby] yast/wfm.rb:275 Internal error. Please report a bug report with logs. Run save_y2logs to get complete logs. Details: component cannot import namespace 'Pkg' Caller:  /usr/lib64/ruby/vendor_ruby/2.1.0/yast/yast.rb:178:in `import_pure' 2018-04-03 21:09:34 <1> bigbang(4728) [ui] YPushButton.cc(setRole):170 Guessing function key F10 for YPushButton "OK" at 0x7f050c0dfb50 from button role YOKButton

So if I am right in my guess, can some kind guru tell me what I need to do to reinstall this file without using Yast2? I am not an expert on zypper or how to find things in the repos yet so please talk me though this in baby steps. ;-)  (at least with Yast2 I know how to search for a file to find what package needs to be downloaded, but I don't know how to do that with zypper or any other tool. Still learning...) I did make a feeble attempt at it but again ran into this snag -

zypper se -f libgssapi_krb5.so.2 zypper: error while loading shared libraries: /usr/lib64/libgssapi_krb5.so.2: invalid ELF header

So I dunno what to do now...  Thanks in advance...      Marc...

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 04/04/2018 13:41, Patrick Shanahan wrote:

* Marc Chamberlin <> [04-04-18 01:58]:

...

Hi - I suddenly have hit a problem after reboot and I kinda suspect I may have had a disk drive error of some kind but need some help recovering. I am running OpenSuSE Leap 42.3 and after doing a reboot I discovered a number of services (such as Apache2, OpenSSH, Named, Clamd, and a few others) had failed to start. My detective work (such as it is, I am no expert on this stuff) seems to lead me to believe I may have a corrupt file as a lot of errors in the /var/log/messages file seem to point at "/usr/lib64/libgssapi_krb5.so.2: invalid ELF header"

[...]

...

So if I am right in my guess, can some kind guru tell me what I need to do to reinstall this file without using Yast2? I am not an expert on zypper or how to find things in the repos yet so please talk me though this in baby steps. ;-)  (at least with Yast2 I know how to search for a file to find what package needs to be downloaded, but I don't know how to do that with zypper or any other tool. Still learning...)

I did make a feeble attempt at it but again ran into this snag -

...

zypper se -f libgssapi_krb5.so.2 zypper: error while loading shared libraries: /usr/lib64/libgssapi_krb5.so.2: invalid ELF header

zypper ref;zypper -v in --force --no-r krb5

will reinstall *only* krb5 and missing dependencies if any.

If zypper fails because it has to use that library, then there are two possibilities: download the rpm with "wget", then install it with "rpm". If that also fails, the alternative is to boot from a rescue sytem, and use rpm or perhaps zypper to install on another mounted system. I would have to look it up to find the exact command line concoction, so please ask again if going this road. An alternative method is to boot the installation DVD of the same release (42.3) and tell it to "upgrade" the installed 42.3 system (to the same version). This is like shooting a fly with a cannon, but it works. Unless you (Marc) have hard disk errors, which is something I would verify first. Paste here the result of running "smartctl -a /dev/THEDISKDEVICE". Make sure to run the long test if it hasn't been done previously. -- Saludos/Cheers, Carlos E.R. (Minas-Morgul - W10) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org