This is an example of the error I receive when trying to do an update via
YaST, YaST2, or zypper. Basically, curl is broken. With out it functioning
normally, I can’t use openSUSE’s update mechanism to fix my system. Need to
find a way to manually fix / upgrade curl.
Any ideas?
TIA
There was an error in the repository initialization.
‘Updates-for-openSUSE-11.4-11.4-0’: |] Valid metadata not found at
specified URL(s)
History:
> just for my own education i wonder if you would explain how that output
> might impact the ability to solve this DNS problem…
the weird part is that when I move the laptop to a different location, curl
now resolves download.opensuse.org correctly & I receive updates … so
maybe it was DNS.
interestingly, Midori works at home when Firefox doesn’t; but at the second
location, both work.
Harv wrote:
> interestingly, Midori works at home when Firefox doesn’t; but at the
> second location, both work.
>
Can you check in Firefox if it is set to use the system settings for the
proxy? If yes can you check which settings in the kde control center are
used for the proxy?
I am not familiar with Midori (I know that it is a browser but that’s it) so
I ask: Is there a similar setting in Midori which differs from that?
This should give a hint what the problem might be if one works always and
the other sometimes not.
I had to change myself once the setting in the kde control center to “Direct
connection” instead of “automatic detection” to make some applications work,
so it is possible you have something similar here.
–
PC: oS 11.3 64 bit | Intel Core2 Quad Q8300@2.50GHz | KDE 4.6.2 | GeForce
9600 GT | 4GB Ram
Eee PC 1201n: oS 11.4 64 bit | Intel Atom 330@1.60GHz | KDE 4.6.0 | nVidia
ION | 3GB Ram
I just saw this and I noticed that Curl does not properly resolve DNS addresses using secondary DNS in YAST2 if the primary DNS is down. Firefox however does correctly resolve using secondary DNS. This probably is a CURL bug. My stupid corporate VPN resets the DNS in resolv.conf . . . and doesn’t set it back
When I tried to update an openSuSe 13.1 server I faced the resolving problem reported in the present thread.
I was connecting to the server from another pc on the LAN, through an ssh shell.
I was also trying to update that server by syncing repository definitions on another openSuSe pc (exporting and importing to a definitions file).
What I had overlooked was that before, on that server, and through yast (ncurses) I had changed some network definitions on it, namely, I had set up the server to have a static ip address, but I did not set the DNS servers addresses for that connection.
So… I googled… and I ended up in here. After setting its DNS settings all was ok.