Le 07/01/2016 16:33, Gustav Degreef a écrit :

On 01/07/2016 01:18 PM, jdd wrote:

...

Le 07/01/2016 12:00, Gustav Degreef a écrit :

...

Hello,

I have been unable to update (via zypper, YOU or apper) since some time. It behaved normally after the initial install for some weeks.

I suspect a broken update of libzyp or similar

may be download the zypper rpm and install it by hand?

Thanks, but would that explain why Apper and YOU are failing and why I can't add any repos via Yast? Gustav.

...

jdd

yes, any of then probably use the libzypp backend may be the one click will work?? https://software.opensuse.org/package/libzypp you may be able to find the rmp in the same place jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Gustav Degreef wrote:

On 01/07/2016 01:23 PM, Per Jessen wrote:

...

Gustav Degreef wrote:

...

linux:/home/user # zypper patch Download (curl) error for 'http://download.opensuse.org/update/leap/42.1/non-oss/repodata/repomd.xml': Error code: Connection failed Error message: Failed to connect to download.opensuse.org port 80: Network is unreachable

Abort, retry, ignore? [a/r/i/? shows all options] (a): a ABORT request: Aborting requested by user linux:/home/user # zypper ref Download (curl) error for 'http://download.opensuse.org/distribution/leap/42.1/repo/non-oss/content': Error code: Connection failed Error message: Failed to connect to download.opensuse.org port 80: Network is unreachable Can you ping download.opensuse.org? ping6 download.opensuse.org ?

ping works fine on the first url, with the second the response is "unknown host"

Okay, sounds like your ipv4 network connectivity is fine. "Network is unreachable" suggests that you have no route to "download.opensuse.org". What does "ip route get 195.135.221.134" say? -- Per Jessen, Zürich (2.7°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Gustav Degreef wrote:

On 01/07/2016 05:03 PM, Per Jessen wrote:

...

Gustav Degreef wrote:

...

On 01/07/2016 01:23 PM, Per Jessen wrote:

...

Gustav Degreef wrote:

...

linux:/home/user # zypper patch Download (curl) error for 'http://download.opensuse.org/update/leap/42.1/non-oss/repodata/repomd.xml': Error code: Connection failed Error message: Failed to connect to download.opensuse.org port 80: Network is unreachable

Abort, retry, ignore? [a/r/i/? shows all options] (a): a ABORT request: Aborting requested by user linux:/home/user # zypper ref Download (curl) error for 'http://download.opensuse.org/distribution/leap/42.1/repo/non-oss/content': Error code: Connection failed Error message: Failed to connect to download.opensuse.org port 80: Network is unreachable Can you ping download.opensuse.org? ping6 download.opensuse.org ?

ping works fine on the first url, with the second the response is "unknown host" Okay, sounds like your ipv4 network connectivity is fine. "Network is unreachable" suggests that you have no route to "download.opensuse.org".

What does "ip route get 195.135.221.134" say?

The result is:

user@linux:~> ip route get 195.135.221.134 195.135.221.134 via 192.168.1.1 dev eth0 src 192.168.1.33 cache Gustav

That looks fine - your machine is 1.33, your router is 1.1. It sounds like "Network is unreachable" is caused by your "zypper ref" trying to use the IPv6 address of "download.opensuse.org". Do you still get this error? What does "host download.opensuse.org" say? On a systems with no IPv6 connectivity, you ought to see the IPv4 address listed first. /Per -- Per Jessen, Zürich (5.6°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Gustav Degreef wrote:

On 01/08/2016 02:54 PM, Per Jessen wrote:

...

Gustav Degreef wrote:

That looks fine - your machine is 1.33, your router is 1.1. It sounds like "Network is unreachable" is caused by your "zypper ref" trying to use the IPv6 address of "download.opensuse.org". Do you still get this error?

What does "host download.opensuse.org" say? On a systems with no IPv6 connectivity, you ought to see the IPv4 address listed first.

/Per Thanks Per. The results now are:

user@linux:~> host download.opensuse.org download.opensuse.org has address 195.135.221.134 download.opensuse.org has IPv6 address 2001:67c:2178:8::13 ;; connection timed out; no servers could be reached

The last line is a little odd, not sure where that would be from. Otherwise fine.

user@linux:~> ping6 download.opensuse.org PING download.opensuse.org(ftp.opensuse.org) 56 data bytes From fe80::1 icmp_seq=1 Destination unreachable: No route

Hmm, let us see your network config, please: "ip addr" -- Per Jessen, Zürich (5.4°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Gustav Degreef wrote:

On 01/08/2016 03:32 PM, Per Jessen wrote:

...

Hmm, let us see your network config, please: "ip addr"

I really appreciate the help. However, this being a public list, I would like to retain some privacy. What part can I delete from the output to do that? Gustav.

Well, as your IP-network seems to be 192.168.0.0, it's private anyway. Feel free to redact any public addresses though. -- Per Jessen, Zürich (4.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Gustav Degreef wrote:

On 01/08/2016 03:32 PM, Per Jessen wrote:

...

Gustav Degreef wrote:

...

On 01/08/2016 02:54 PM, Per Jessen wrote:

...

Gustav Degreef wrote:

That looks fine - your machine is 1.33, your router is 1.1. It sounds like "Network is unreachable" is caused by your "zypper ref" trying to use the IPv6 address of "download.opensuse.org". Do you still get this error?

What does "host download.opensuse.org" say? On a systems with no IPv6 connectivity, you ought to see the IPv4 address listed first.

/Per Thanks Per. The results now are: user@linux:~> host download.opensuse.org download.opensuse.org has address 195.135.221.134 download.opensuse.org has IPv6 address 2001:67c:2178:8::13 ;; connection timed out; no servers could be reached The last line is a little odd, not sure where that would be from. Otherwise fine.

...

user@linux:~> ping6 download.opensuse.org PING download.opensuse.org(ftp.opensuse.org) 56 data bytes From fe80::1 icmp_seq=1 Destination unreachable: No route Hmm, let us see your network config, please: "ip addr"

It is odd that you should have an IPv6 address (fe80::1) saying "no route". Judging by your "ip addr" output, you only have link-local addresses, but I wonder if you might have an IPv6 route, default fe80::1. What does "ip -6 route show" say? -- Per Jessen, Zürich (7.2°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Gustav Degreef wrote:

On 01/09/2016 05:15 PM, Per Jessen wrote:

...

Gustav Degreef wrote:

...

On 01/08/2016 03:32 PM, Per Jessen wrote:

...

Gustav Degreef wrote:

...

On 01/08/2016 02:54 PM, Per Jessen wrote:

...

Gustav Degreef wrote:

That looks fine - your machine is 1.33, your router is 1.1. It sounds like "Network is unreachable" is caused by your "zypper ref" trying to use the IPv6 address of "download.opensuse.org". Do you still get this error?

What does "host download.opensuse.org" say? On a systems with no IPv6 connectivity, you ought to see the IPv4 address listed first.

/Per Thanks Per. The results now are: user@linux:~> host download.opensuse.org download.opensuse.org has address 195.135.221.134 download.opensuse.org has IPv6 address 2001:67c:2178:8::13 ;; connection timed out; no servers could be reached The last line is a little odd, not sure where that would be from. Otherwise fine.

...

user@linux:~> ping6 download.opensuse.org PING download.opensuse.org(ftp.opensuse.org) 56 data bytes From fe80::1 icmp_seq=1 Destination unreachable: No route Hmm, let us see your network config, please: "ip addr" It is odd that you should have an IPv6 address (fe80::1) saying "no route". Judging by your "ip addr" output, you only have link-local addresses, but I wonder if you might have an IPv6 route, default fe80::1. What does "ip -6 route show" say?

fe80::/64 dev eth0 proto kernel metric 256 pref medium default via fe80::1 dev eth0 proto static metric 100 pref medium

Okay, there is your problem. When zypper tries to access "download.opensuse.org", it will attempt to use IPv6, because you appear to have IPv6 connectivity. When the first packet is routed to fe80::1, it is returned with "Network is unreachable" because your router doesn't actually have any IPv6 connectivity. It's probably easily fixed by changing to dhcp4 only for your network interfaces. This is done with YaST. -- Per Jessen, Zürich (5.6°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sun, 10 Jan 2016 14:11, Gustav Degreef wrote:

On 01/10/2016 09:41 AM, Per Jessen wrote:

...

Gustav Degreef wrote:

...

On 01/09/2016 05:15 PM, Per Jessen wrote:

...

Gustav Degreef wrote:

...

On 01/08/2016 03:32 PM, Per Jessen wrote:

...

Gustav Degreef wrote: > On 01/08/2016 02:54 PM, Per Jessen wrote: >> Gustav Degreef wrote: >> >> That looks fine - your machine is 1.33, your router is 1.1. It >> sounds like "Network is unreachable" is caused by your "zypper >> ref" trying to >> use the IPv6 address of "download.opensuse.org". Do you still >> get this error? >> >> What does "host download.opensuse.org" say? On a systems with no >> IPv6 connectivity, you ought to see the IPv4 address listed >> first. >> > Thanks Per. The results now are: > user@linux:~> host download.opensuse.org > download.opensuse.org has address 195.135.221.134 > download.opensuse.org has IPv6 address 2001:67c:2178:8::13 > ;; connection timed out; no servers could be reached The last line is a little odd, not sure where that would be from. Otherwise fine.

> user@linux:~> ping6 download.opensuse.org > PING download.opensuse.org(ftp.opensuse.org) 56 data bytes > From fe80::1 icmp_seq=1 Destination unreachable: No route Hmm, let us see your network config, please: "ip addr" It is odd that you should have an IPv6 address (fe80::1) saying "no route". Judging by your "ip addr" output, you only have link-local addresses, but I wonder if you might have an IPv6 route, default fe80::1. What does "ip -6 route show" say?

fe80::/64 dev eth0 proto kernel metric 256 pref medium default via fe80::1 dev eth0 proto static metric 100 pref medium

Okay, there is your problem. When zypper tries to access "download.opensuse.org", it will attempt to use IPv6, because you appear to have IPv6 connectivity. When the first packet is routed to fe80::1, it is returned with "Network is unreachable" because your router doesn't actually have any IPv6 connectivity. It's probably easily fixed by changing to dhcp4 only for your network interfaces. This is done with YaST.

Thanks Per. I went to Yast > Network Config > General options. There I unchecheked the enable Ipv6 and then as instructed by Yast rebooted. But it had NO effect. Problem is unchanged. It's really puzzling. Gustav.

Shorted from above: Wah!-Comp-wants-to-use-IPv6-but-I-have-only-IPv4-no-connect-at-all Hmm, have you ever heard of "/etc/gai.conf" ? Nifty file to configure just HOW that damn glibc orders the get-address-info stuff. Esp. a line of: [code] precedence ::ffff:0:0/96 100 [/code] helps in such troubles. Most times it is already there, but commented out. May need a reboot, but most often not. - Yamaban. -- Live: Shit happens, then you die. The trick is to make sure it's your shit that happens. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sun, 10 Jan 2016 14:50, Per Jessen wrote:

Yamaban wrote:

...

Shorted from above: Wah!-Comp-wants-to-use-IPv6-but-I-have-only-IPv4-no-connect-at-all

Yup.

...

Hmm, have you ever heard of "/etc/gai.conf" ? Nifty file to configure just HOW that damn glibc orders the get-address-info stuff.

Yes, but there really should be no need to fiddle with that. The problem is that Gustav's router hands out an IPv6 route although it has no IPv6 connectivity. The correct way to fix the problem would be to change the router setup, but the easy way is to just dhcp4 instead of both -4 and -6.

Sorry, but: "Snort" NOT possible with wicked. (except if you mong the system, aka: replacing /usr/lib/wicked/bin/wickedd-dhcp6 or force disabling wickedd-dhcp6.service) Just TRY to remove or disable dhcp v6 on Leap 42.1, it laughs at you. Yes, I'm frustrated by that behavior, but that is the "Party-Line" from the SUSE desicion-making-staff above. - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Per Jessen wrote:

Yamaban wrote:

...

On Sun, 10 Jan 2016 14:50, Per Jessen wrote:

...

Yamaban wrote:

...

Shorted from above: Wah!-Comp-wants-to-use-IPv6-but-I-have-only-IPv4-no-connect-at-all

Yup.

...

Hmm, have you ever heard of "/etc/gai.conf" ? Nifty file to configure just HOW that damn glibc orders the get-address-info stuff.

Yes, but there really should be no need to fiddle with that. The problem is that Gustav's router hands out an IPv6 route although it has no IPv6 connectivity. The correct way to fix the problem would be to change the router setup, but the easy way is to just dhcp4 instead of both -4 and -6.

Sorry, but: "Snort" NOT possible with wicked. (except if you mong the system, aka: replacing /usr/lib/wicked/bin/wickedd-dhcp6 or force disabling wickedd-dhcp6.service)

Just TRY to remove or disable dhcp v6 on Leap 42.1, it laughs at you.

Hmm, it seems to be possible, just as it used to be - if it doesn't work, time for bugzilla.

With BOOTPROTO=dhcp, I get an ipv4 and an ipv6 address assigned (from the dhcp servers). With BOOTPROTO=dhcp4, I get an ipv4 and no ipv6 address assigned (from the dhcp servers). I have not tried with dhcp6 only. With BOOTPROTO=dhcp4, ipv6 privacy addresses are still assigned due to router advertisements. I guess it might make sense not to even run wickedd-dhcp6. For Gustav's case though, 'fe80::1' as a default route is handed out by dhcp. Seems to work just fine. *SNORT* -- Per Jessen, Zürich (5.8°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 01/11/2016 08:24 AM, Per Jessen wrote:

Per Jessen wrote:

...

With BOOTPROTO=dhcp, I get an ipv4 and an ipv6 address assigned (from the dhcp servers). With BOOTPROTO=dhcp4, I get an ipv4 and no ipv6 address assigned (from the dhcp servers). I have not tried with dhcp6 only. Just tried it, works fine.

I think changing both interfaces to dhcp4 should solve the problem for Gustav.

I tried to edit the interfaces in Yast Network Devices. However, because I am using networkmanager (or wicked, not sure), the interfaces can not be edited unless I select to configure with ifup (I can not remember the last time I had to do that). So I went to /etc/sysconfig/network and found only ifcfg-wlan0 and ifcfg-template, none for eth0. I edited the wlan0 file and changed BOOTPROTO=dhcp to BOOTPROTO=dhcp4, rebooted and it had no effect. I read the ifcfg-template file. If I understand correctly, this is used when configuring the network with ifup. So perhaps that is why it did not work. As I mentioned in a previous post on this thread, I edited the file /etc/gai.conf but with no effect. I can try my hand at configuring the netwrok devices with ifup and configuring my network connections via ifup, but as a regular user who is also visually impaired, tis is getting extremely frustrating. I am having periodic and regular kernel panics on 13.2 because I can not get the intel graphics working right on it, so that is why I installed Leap. On Leap that problem is solved, but I can not migrage my day to day desktop to it because of this problem. Leap has been the most frustrating release since 6.3 - for me. Thanks for everyone's help, particularly Per who has approached this very systematically, Gustav. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 01/11/2016 02:54 PM, Per Jessen wrote:

Gustav Degreef wrote:

...

On 01/11/2016 08:24 AM, Per Jessen wrote:

...

Per Jessen wrote:

...

With BOOTPROTO=dhcp, I get an ipv4 and an ipv6 address assigned (from the dhcp servers). With BOOTPROTO=dhcp4, I get an ipv4 and no ipv6 address assigned (from the dhcp servers). I have not tried with dhcp6 only. Just tried it, works fine.

I think changing both interfaces to dhcp4 should solve the problem for Gustav. I tried to edit the interfaces in Yast Network Devices. However, because I am using networkmanager (or wicked, not sure), the interfaces can not be edited unless I select to configure with ifup (I can not remember the last time I had to do that). Ah. I'm sorry, I hadn't thought of the NetworkManager option. I don't really know NM very well, but presumably it has the same options somewhere? In the network manager GUI there is an option to edit the interface settings. There are two tabs, one ipv4 and one ipv6. It's not intuitive for me, can't figure out how to set what is needed. Gustav.

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

* Gustav Degreef [01-11-16 09:44]:

...

On 01/11/2016 02:54 PM, Per Jessen wrote:

...

Gustav Degreef wrote:

...

On 01/11/2016 08:24 AM, Per Jessen wrote:

...

Per Jessen wrote:

...

With BOOTPROTO=dhcp, I get an ipv4 and an ipv6 address assigned (from the dhcp servers). With BOOTPROTO=dhcp4, I get an ipv4 and no ipv6 address assigned (from the dhcp servers). I have not tried with dhcp6 only. Just tried it, works fine.

I think changing both interfaces to dhcp4 should solve the problem for Gustav. I tried to edit the interfaces in Yast Network Devices. However, because I am using networkmanager (or wicked, not sure), the interfaces can not be edited unless I select to configure with ifup (I can not remember the last time I had to do that). Ah. I'm sorry, I hadn't thought of the NetworkManager option. I don't really know NM very well, but presumably it has the same options somewhere? In the network manager GUI there is an option to edit the interface settings. There are two tabs, one ipv4 and one ipv6. It's not intuitive for me, can't figure out how to set what is needed. Gustav. Not familiar with Nm but wicked will not (I cannot make it) work on my new toshiba laptop. Looking at the ipv6 tab, I suggest changing "method" from automatic to ignored>

ps: Experiment, you can always change it back. I changed both my wireless and wired connections as you suggested. Restarted the network. Apper now no longer told me the system was offline, zypper ref refreshed all the repos except packman. I then was able to update the system via YOU. It looked great, but then I tried another zypper ref and all repos were unreachable! And Apper again said

On 01/11/2016 04:06 PM, Patrick Shanahan wrote: the network was offline, etc. I did not try experimenting yet, I'll do that tomorrow. But this temporary fix is the same as occurred when I initially managed to reinstall libzypp. VERY ODD! Thanks, Gustav. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Gustav Degreef wrote:

On 01/10/2016 09:41 AM, Per Jessen wrote:

...

Gustav Degreef wrote:

...

fe80::/64 dev eth0 proto kernel metric 256 pref medium default via fe80::1 dev eth0 proto static metric 100 pref medium

Okay, there is your problem. When zypper tries to access "download.opensuse.org", it will attempt to use IPv6, because you appear to have IPv6 connectivity. When the first packet is routed to fe80::1, it is returned with "Network is unreachable" because your router doesn't actually have any IPv6 connectivity. It's probably easily fixed by changing to dhcp4 only for your network interfaces. This is done with YaST.

Thanks Per. I went to Yast > Network Config > General options. There I unchecheked the enable Ipv6 and then as instructed by Yast rebooted. But it had NO effect. Problem is unchanged. It's really puzzling. Gustav.

You probably have to reboot to change that option - the dhcp change I suggested doesn't require a reboot. -- Per Jessen, Zürich (5.9°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Gustav Degreef wrote:

On 01/10/2016 02:48 PM, Per Jessen wrote:

...

Gustav Degreef wrote:

...

On 01/10/2016 09:41 AM, Per Jessen wrote:

...

Gustav Degreef wrote:

...

fe80::/64 dev eth0 proto kernel metric 256 pref medium default via fe80::1 dev eth0 proto static metric 100 pref medium

Okay, there is your problem. When zypper tries to access "download.opensuse.org", it will attempt to use IPv6, because you appear to have IPv6 connectivity. When the first packet is routed to fe80::1, it is returned with "Network is unreachable" because your router doesn't actually have any IPv6 connectivity. It's probably easily fixed by changing to dhcp4 only for your network interfaces. This is done with YaST.

Thanks Per. I went to Yast > Network Config > General options. There I unchecheked the enable Ipv6 and then as instructed by Yast rebooted. But it had NO effect. Problem is unchanged. It's really puzzling. Gustav. You probably have to reboot to change that option - the dhcp change I suggested doesn't require a reboot.

Then I misunderstood what you were saying to do? Sorry, can you please explain more? Gustav.

You go into YaST, "Network Settings" - for each network interface, you can change which kind of DHCP it should use - v4, v6 or both. The default is to use both. You can do the same by editing /etc/sysconfig/network/ifcfg-xxxx directly and changing BOORPROTO to dhcp/dhcp4/dhcp6 and restarting the interface. -- Per Jessen, Zürich (6.4°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 01/07/2016 10:42 PM, Darryl Gregorash wrote: snip

Then, fire up Yast/Software Management and search for everything that depends on libzypp. Everything that is installed (here there are 8 packages, default installation) likely needs to be /forcibly/ refreshed.

Snip I think I understood most of your suggestion. However, the above is not clear to me. I found these 7 packages that depend on libzypp. Do I forcibly remove all and re-install all of them? PackageKit-backend-zypp btrfsmaintenance libyui-ncurses-pkg7 libyui-qt-pkg7 libzypp snapper-zypp-plugin yast2-pkg-bindings zypper Thanks, Gustav -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 08/01/16 08:00 AM, Gustav Degreef wrote:

...

On 01/07/2016 10:42 PM, Darryl Gregorash wrote:

snip

...

Then, fire up Yast/Software Management and search for everything that depends on libzypp. Everything that is installed (here there are 8 packages, default installation) likely needs to be /forcibly/ refreshed. Snip

I think I understood most of your suggestion. However, the above is not clear to me. I found these 7 packages that depend on libzypp. Do I forcibly remove all and re-install all of them? No, you don't need to remove them. On the yast menu bar, click Packages/All in this list/Update unconditionally.

That will re-install any packages already installed, but will not add any new ones.

PS, since this might be just a libzypp problem, you can probably update just that one package. Hopefully that would be enough. The result was very strange! I reinstalled libzypp as indicated - as

On 01/08/2016 04:22 PM, Darryl Gregorash wrote: the first step. Then I was able to refresh all the repositories (which had been failing). After that I did "zypper patch" and it completed successfully without errors. So far so good. I then tried "zypper up" and but got the same failures to connect to the packman repo as before! I then tried to reinstall the remaining 7 packages (dependencies of libzypp) via yast. But that failed with the error that the system could not connect to any of the repoertories. The following is a sample error message (from zypper - at that same time point): linux-tz21:/home/rada # zypper ref Download (curl) error for 'http://download.opensuse.org/distribution/leap/42.1/repo/non-oss/content': Error code: Connection failed Error message: Failed to connect to download.opensuse.org port 80: Network is unreachable Abort, retry, ignore? [a/r/i/? shows all options] (a): There is no particular repo failing, all of them fail. Packman seems to fail most often, but when trying to update the libzypp dependencies all of the repos are unreachable. I've never had anything like this happen in all the years of using suse! Thanks for the help, Gustav. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org