Text only | Text with Images

Siduction Forum

Siduction Forum => Upgrade Warnings => Topic started by: micspabo on 2025/03/04, 20:56:24

Title: [Solved] Siduction Repository Timeout
Post by: micspabo on 2025/03/04, 20:56:24
I am located in the north of germany and <https://packages.siduction.org/> is actually timing out here.  :(

Code Select

Ign:18 https://packages.siduction.org/extra unstable InRelease                                                               
Ign:19 https://packages.siduction.org/fixes unstable InRelease
Ign:18 https://packages.siduction.org/extra unstable InRelease
Ign:19 https://packages.siduction.org/fixes unstable InRelease
Ign:18 https://packages.siduction.org/extra unstable InRelease
Ign:19 https://packages.siduction.org/fixes unstable InRelease
Err:18 https://packages.siduction.org/extra unstable InRelease
  Could not connect to packages.siduction.org:443 (31.214.144.87), connection timed out
  Unable to connect to packages.siduction.org:https:
Err:19 https://packages.siduction.org/fixes unstable InRelease
  Unable to connect to packages.siduction.org:https:
Fetched 74,9 MB in 37s (2.008 kB/s)
11 packages can be upgraded. Run 'apt list --upgradable' to see them.
Warning: Failed to fetch https://packages.siduction.org/extra/dists/unstable/InRelease  Unable to connect to packages.siduction.org:https:
Warning: Failed to fetch https://packages.siduction.org/fixes/dists/unstable/InRelease  Unable to connect to packages.siduction.org:https:
Warning: Some index files failed to download. They have been ignored, or old ones used instead.
Title: Re: Siduction Repository Timeout
Post by: michaa7 on 2025/03/04, 22:00:21
the same here
Title: Re: Siduction Repository Timeout
Post by: micspabo on 2025/03/04, 22:49:47
Not so patient users could use one of the following mirrors until the repo is accessible again.
Found them via https://forum.siduction.org/index.php?action=search2;params=eJwtjs0KgzAQhF-l9NLLHMzfbnwa0SSgRY1sbUshD98owhyGbwZm-vjp15BieZSm3Msgh2MNreE8qAFpkAIZkAMRyMIxHME5cJUFG7AC12YL18JWEYyHIagWilFzBntwC9_AK3gNb-Bt3XuN-duFvGxz2lNdPtB7eKawd3mdfxfJslcnaU7n2Qt1cZKKY3qFg6RewnjWtnxbJpEsf86sQzU.;start=30 (https://forum.siduction.org/index.php?action=search2;params=eJwtjs0KgzAQhF-l9NLLHMzfbnwa0SSgRY1sbUshD98owhyGbwZm-vjp15BieZSm3Msgh2MNreE8qAFpkAIZkAMRyMIxHME5cJUFG7AC12YL18JWEYyHIagWilFzBntwC9_AK3gNb-Bt3XuN-duFvGxz2lNdPtB7eKawd3mdfxfJslcnaU7n2Qt1cZKKY3qFg6RewnjWtnxbJpEsf86sQzU.;start=30)
Title: Re: Siduction Repository Timeout
Post by: devil on 2025/03/04, 23:25:18
We are in the process of moving to a new server infrastructure, since the hoster moves to a new location. I was told, the old one gets cut off on March 15. Right now, it is unclear to me why it obviously is not online any more. Will investigate, please be patient.
Title: Re: Siduction Repository Timeout
Post by: vinzv on 2025/03/05, 00:18:53
Quote from: micspabo on 2025/03/04, 22:49:47
Not so patient users could use one of the following mirrors until the repo is accessible again.

  • https://siduction.mirror.garr.it/...
  • https://ftp.belnet.be/mirror/siduction/...
  • https://mirror.math.princeton.edu/pub/siduction/...
Found them via https://forum.siduction.org/index.php?action=search2;params=eJwtjs0KgzAQhF-l9NLLHMzfbnwa0SSgRY1sbUshD98owhyGbwZm-vjp15BieZSm3Msgh2MNreE8qAFpkAIZkAMRyMIxHME5cJUFG7AC12YL18JWEYyHIagWilFzBntwC9_AK3gNb-Bt3XuN-duFvGxz2lNdPtB7eKawd3mdfxfJslcnaU7n2Qt1cZKKY3qFg6RewnjWtnxbJpEsf86sQzU.;start=30 (https://forum.siduction.org/index.php?action=search2;params=eJwtjs0KgzAQhF-l9NLLHMzfbnwa0SSgRY1sbUshD98owhyGbwZm-vjp15BieZSm3Msgh2MNreE8qAFpkAIZkAMRyMIxHME5cJUFG7AC12YL18JWEYyHIagWilFzBntwC9_AK3gNb-Bt3XuN-duFvGxz2lNdPtB7eKawd3mdfxfJslcnaU7n2Qt1cZKKY3qFg6RewnjWtnxbJpEsf86sQzU.;start=30)

Or go to https://siduction.org/mirrors/

It's "hidden" in the menu under Downloads.  ;)
Title: Re: Siduction Repository Timeout
Post by: micspabo on 2025/03/05, 07:01:35
Quote from: vinzv on 2025/03/05, 00:18:53
It's "hidden" ...  ;)
Looks very much more like that I need a new pair of glasses.  ::) Thanks.
@devil: Thanks, it's online again. Wish you good luck that everything goes according to the plan.
Title: Re: [Solved] Siduction Repository Timeout
Post by: michaa7 on 2025/03/17, 13:48:15
Today again?

QuoteDiese Website ist nicht erreichbar
https://packages.siduction.org/ ist nicht erreichbar.

Title: Re: [Solved] Siduction Repository Timeout
Post by: hendrikL on 2025/03/17, 14:53:19
Quote from: michaa7 on 2025/03/17, 13:48:15
Today again?

QuoteDiese Website ist nicht erreichbar
https://packages.siduction.org/ ist nicht erreichbar.



Yes.

But now, we are moving all the data to a new web server, so everyone has to be patient until all the work is done.
Sorry, this will need it's time!
Title: Re: [Solved] Siduction Repository Timeout
Post by: michaa7 on 2025/03/17, 17:09:44
Thanks. Good to know.

And thanks for your work.

I think we all will be patient.
Title: Re: [Solved] Siduction Repository Timeout
Post by: hendrikL on 2025/03/17, 19:36:03
everything should be ok now.

We moved to the new server.

Code Select

[18:15] <towo`> System:
[18:15] <towo`>   Host: ms-136.premium-rootserver.net Kernel: 6.1.0-31-amd64 arch: x86_64 bits: 64 compiler: gcc
[18:15] <towo`>     v: 12.2.0 Console: pty pts/5 Distro: Debian GNU/Linux 12 (bookworm)
[18:15] <towo`> Machine:
[18:15] <towo`>   Type: Desktop System: Micro (HK) Tech product: Venus Series v: 1.0 serial: <superuser required>
[18:15] <towo`>   Mobo: Shenzhen Meigao Equipment model: AHWSA v: 1.0 serial: <superuser required> UEFI: American
[18:15] <towo`>     Megatrends LLC. v: 1.26 date: 10/14/2024
[18:15] <towo`> CPU:
[18:15] <towo`>   Info: 14-core (6-mt/8-st) model: 12th Gen Intel Core i9-12900H bits: 64 type: MST AMCP
[18:15] <towo`>     arch: Alder Lake rev: 3 cache: L1: 1.2 MiB L2: 11.5 MiB L3: 24 MiB
[18:15] <towo`>   Speed (MHz): avg: 405 high: 493 min/max: 400/4900:5000:3800 cores: 1: 400 2: 400 3: 400 4: 400
[18:15] <towo`>     5: 426 6: 400 7: 400 8: 400 9: 493 10: 400 11: 400 12: 400 13: 400 14: 400 15: 400 16: 400
[18:15] <towo`>     17: 400 18: 400 19: 400 20: 400 bogomips: 116736
[18:15] <towo`>   Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
[18:15] <towo`> Info:
[18:16] <towo`>   Processes: 251 Uptime: 20d 7h 1m Memory: 62.54 GiB used: 2.19 GiB (3.5%) Init: systemd v: 252
[18:16] <towo`>   target: graphical (5) default: graphical Compilers: gcc: 12.2.0 alt: 12 Packages: pm: dpkg
[18:16] <towo`>   pkgs: 833 Shell: Bash v: 5.2.15 running-in: pty pts/5 inxi: 3.3.26


Title: Re: [Solved] Siduction Repository Timeout
Post by: Lanzi on 2025/03/18, 19:05:32
Code Select

Hinweis: Fehlendes Signed-By im Eintrag sources.list(5) für »https://ftp.gwdg.de/pub/linux/siduction/extra«
Hinweis: Fehlendes Signed-By im Eintrag sources.list(5) für »https://ftp.gwdg.de/pub/linux/siduction/fixes«


What do I need to change? Was muss ich noch ergänzen?
Title: Re: [Solved] Siduction Repository Timeout
Post by: der_bud on 2025/03/18, 21:21:18
Quote from: Lanzi on 2025/03/18, 19:05:32
... What do I need to change? Was muss ich noch ergänzen?

Hier bei mir fangen die entsprechenden Zeilen in der siduction.list mit
Code Select
deb [signed-by=/usr/share/keyrings/siduction-archive-keyring.gpg] ... an
Title: Re: [Solved] Siduction Repository Timeout
Post by: Lanzi on 2025/03/18, 21:51:25
Thanks!
Is there any place where I can copy the the new syntax for sources.list.d?
Right now I have the old one for extras.list

Code Select

deb      https://ftp.gwdg.de/pub/linux/siduction/extra unstable main contrib non-free non-free-firmware


If I understand the new concept, I cannot mix the line from "der_Bud" with the old one?

Title: Re: [Solved] Siduction Repository Timeout
Post by: Pip on 2025/03/18, 22:37:29
As devil pointed out in https://forum.siduction.org/index.php?topic=9606.msg76539#msg76539 (https://forum.siduction.org/index.php?topic=9606.msg76539#msg76539), there's a release from Debian to migrate lists. Would that help you?
Title: Re: [Solved] Siduction Repository Timeout
Post by: Lanzi on 2025/03/18, 22:56:33
I did that before. And indeed I have the new sources entry. I was wrong before. I didn't see the .bak - ending. SO ignore my firt posting. My bad!

But, the line from the_Bud does no work. I have this entry:

Code Select

Types: deb
URIs: https://ftp.gwdg.de/pub/linux/siduction/extra/
Suites: unstable
Components: main  contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/siduction-archive-keyring.gpg


The error remains! So is the file in /usr/share/keyrings/ wrong?




Title: Re: [Solved] Siduction Repository Timeout
Post by: michaa7 on 2025/03/19, 01:18:36
do you have the keyrings installed?
Title: Re: [Solved] Siduction Repository Timeout
Post by: hendrikL on 2025/03/19, 09:53:09
Your sources file looks a bit different, look at Components and Signed-By!

Code Select

Types: deb deb-src
URIs: https://packages.siduction.org/extra
Suites: unstable
Components: main
Enabled: yes
Signed-By: /usr/share/siduction-archive-keyring/siduction-archive-keyring.gpg


What is "ls -l /usr/share/keyrings/" telling you?

Title: Re: [Solved] Siduction Repository Timeout
Post by: Pip on 2025/03/19, 10:16:43
Does the output of

Code Select
gpg --list-packets /usr/share/keyrings/siduction-archive-keyring.gpg

give relevant details?
Title: Re: [Solved] Siduction Repository Timeout
Post by: scholle1 on 2025/03/19, 14:32:20
@Lanzi: Sorry, but this can`t work.

Quote from: Lanzi on 2025/03/18, 22:56:33
[...] I have this entry:
Code Select

Types:      deb
URIs:       https://ftp.gwdg.de/pub/linux/siduction/extra/
Suites:     unstable
Components: main contrib non-free non-free-firmware
Signed-By:  /usr/share/keyrings/siduction-archive-keyring.gpg

The following line is missing between "Components" and "Signed-By":
Code Select
Enabled: yes

And then, as hendrikL wrote, check whether all key files are stored in the /usr/share/keyrings/ directory.

In addition:
The file that hendrikL posted is deb deb-src. I assume you don't need deb-src.
Then remove deb-src, or if only deb-src is entered, set the value Enabled to "no".
Title: Re: [Solved] Siduction Repository Timeout
Post by: towo on 2025/03/19, 15:31:42
Code Select
Enabled: yes

Is not needed at all!
Title: Re: [Solved] Siduction Repository Timeout
Post by: Lanzi on 2025/03/19, 17:29:55
Sorry for the delay.

HendrikL had the solution. I changed the entry according to his suggestion.

Thanks to everyone for all the suggestions. Really helpful and good to know that we can reley on each other. Thanks a lot!
Title: Re: [Solved] Siduction Repository Timeout
Post by: der_bud on 2025/03/19, 21:04:01
Just to add extra information and clarify, I shoudn't have shortened the whoe line in my last answer ;)
I still have the old .list style and my siduction.list in full is
Code Select
#siduction extra+fixes
deb [signed-by=/usr/share/keyrings/siduction-archive-keyring.gpg] https://ftp.gwdg.de/pub/linux/siduction/extra unstable main contrib non-free non-free-firmware
deb [signed-by=/usr/share/keyrings/siduction-archive-keyring.gpg] https://packages.siduction.org/fixes  unstable main contrib non-free non-free-firmware

#siduction experimental (kernel etc)
#deb https://packages.siduction.org/extra experimental main contrib non-free

In /usr/share/keyrings are all the debian-$foo-keyrings, signal-keyring, and siduction-archive-keyring.gpg as a link to the location mentioned above:
Code Select
ls -lan /usr/share/keyrings/
...
lrwxrwxrwx   1 0 0       58 16. Sep 2021  siduction-archive-keyring.gpg -> ../siduction-archive-keyring/siduction-archive-keyring.gpg
...So working with links is possible in this case.
Text only | Text with Images