Post by badð½sectorPost by R Daneel OlivawPost by badð½sectorPost by Carlos E.R.Post by badð½sector*zypper dup* often locks up one download or
another but the problem arises VIRTUALLY ALWAYS
ONLY while downloading from a packman repo and
not other repos. I've found a few workarounds
but am beginning to wonder what the underlying
real cause and what the associated permanent fix
might be. How no other repos are affected?
Different server network. Obviously :-)
is THIS a clue? And even if it be one, again
how come only on the packman repo?
---------------------------------
^C
Trying to exit gracefully...
Segmentation fault (core dumped)
---------------------------------
NB. Many times there is no exit, graceful or ugly,
only a total hang!
Especially when observed only or mostly in association
with specific software then a segfault is a result of memory
mismanagment by that software (or did I miss sometyhing?).
My guess is that http://packman.links2linux.org/mirrors has the
answer. Which mirror are you using? I'm set up for the gwdg one (with
https) and that seems to work just fine, I was using an Austrian one a
couple of years ago but it went offline without warning and I think
I've been using the current one ever since.
Retrieving: Mesa-libGL1-32bit-24.0.3-1699.375.pm.2.x86_64 (Packman
Essentials Repository) (95/96), 210.4 KiB
Retrieving: Mesa-libGL1-32bit-24.0.3-1699.375.pm.2.x86_64.rpm
................<52%>===============[| (1.6 KiB/s)]
Have you tried to download that file directly?
http://ftp.halifax.rwth-aachen.de/packman/suse/openSUSE_Tumbleweed/Essentials/x86_64/Mesa-libGL1-32bit-24.0.3-1699.375.pm.2.x86_64.rpm
***@Telcontar:~/tmp/A> wget http://ftp.halifax.rwth-aachen.de/packman/suse/openSUSE_Tumbleweed/Essentials/x86_64/Mesa-libGL1-32bit-24.0.3-1699.375.pm.2.x86_64.rpm
--2024-04-16 18:02:00-- http://ftp.halifax.rwth-aachen.de/packman/suse/openSUSE_Tumbleweed/Essentials/x86_64/Mesa-libGL1-32bit-24.0.3-1699.375.pm.2.x86_64.rpm
Resolving ftp.halifax.rwth-aachen.de (ftp.halifax.rwth-aachen.de)... 137.226.34.46, 2a00:8a60:e012:a00::21
Connecting to ftp.halifax.rwth-aachen.de (ftp.halifax.rwth-aachen.de)|137.226.34.46|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 215472 (210K) [application/x-redhat-package-manager]
Saving to: ‘Mesa-libGL1-32bit-24.0.3-1699.375.pm.2.x86_64.rpm’
Mesa-libGL1-32bit-24.0.3-169 100%[=============================================>] 210,42K --.-KB/s in 0,1s
2024-04-16 18:02:01 (1,42 MB/s) - ‘Mesa-libGL1-32bit-24.0.3-1699.375.pm.2.x86_64.rpm’ saved [215472/215472]
***@Telcontar:~/tmp/A>
It downloads here instantly, so you selected a bad mirror. Choose another one.
You can also download it manually, and put in the appropriate directory. In my machine, that would be:
/var/cache/zypp/packages/Ext_Packman/Essentials/x86_64/
Post by badð½sectorhttp://ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/Essentials
the mirros page shows just: http:// no https:// and if I try to edit
it to https in Yast it gets written as http only
Use the ones actually on the page. If there are no https, then there are no https.
Post by badð½sectorBUT if I truncate to just FTP
ftp.gwdg.de/pub/linux/misc/packman/suse/openSUSE_Tumbleweed/Essentials
With no protocol? You are asking the software to crash.
For ftp it would be:
ftp://ftp.gwdg.de/pub/linux/misc/packman/
Post by badð½sector# zypper dup
Loading repository data...
Reading installed packages...
Segmentation fault (core dumped)
(segfault=badly written software)
Or badly updated machine :-)
Post by badð½sector2nd attemp after reboot works ok
So my question remains: WHAT is CAUSING this, swinging repos is NOT the
answer it's just a workaround. I'd like to find THE cause and fix THAT
(i.e. help getting it fixed).
--
Cheers, Carlos.