This happens not only with siduction , (have debian on arm with same problem also from today , not for spline )
Does somebody have a solution ?
On siduction , same problem for spline,vivaldi and eid.belgium[size=78%]:[/size]
[/size]
Failed to fetch http://ftp.spline.de/pub/siduction/fixes/dists/unstable/InRelease Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)The repository 'http://ftp.spline.de/pub/siduction/fixes unstable InRelease' is no longer signed.Updating from such a repository can't be done securely, and is therefore disabled by default.See apt-secure(8) manpage for repository creation and user configuration details.Failed to fetch http://repo.vivaldi.com/stable/deb/dists/stable/InRelease Clearsigned file isn't valid, got 'NOSPLIT' (does the network require authentication?)The repository 'http://repo.vivaldi.com/stable/deb stable InRelease' is no longer signed.
Use a different mirror. Spline runs into problems occasionally. Stuttgart is very reliable (if you live in our parts) Both problems seem to be signature related.
Please read all before posting answer :
THIS HAPPENS NOT ONLY WITH SPLINE , but ALSO forothers REPOS e.g: EID belgium, vivaldi browser, and also on a little server' with ARM processor (NO SIDUCTION REPO)
Relax dude before you blow some hemorrhoids
If your not using siduction repo's I shouldn't be helping, but for shits & giggles post the WHOLE output of
inxi -r
The second answer is not neter than the first , you are moderator ?? Can you sit on your hemorrhoids?
Case closed for me II will look elsewhere.
And I unsubscribe for mail answer
HAHAHA! Obviously a localized problem as I have never seen this output. I'm suspecting a network issue.
Ha ha -- good job @piper -- I think you've done us a favor.
don@n5110:~$ ping www.spline.de
PING www.spline.de(vm-staticweb.spline.inf.fu-berlin.de (2001:470:51c5:babe::71:1)) 56 data bytes
64 bytes from vm-staticweb.spline.inf.fu-berlin.de (2001:470:51c5:babe::71:1): icmp_seq=1 ttl=46 time=149 ms
I have never seen such a message, either.
google search -> 1st entry is an example, where the original issue was a network issue.
https://askubuntu.com/questions/899009/sudo-apt-update-always-giving-clearsigned-file-isnt-valid-got-nosplit-does
therefore the question: is that just a local network issue?