Hello,
recently siduction has simplified its repo structure. The siduction "base" repo was moved to "extra".
Sorry, for the inconvenience.
Some months ago Debian also has replaced the redirector http.debian.net by httpredir.debian.org.
So it's a good opportunity to check your sources, because ... almost everything changed.
This output was created with siduction 2015-1 dev-release [with non-free content not disabled]:
root@sidbox:~# inxi -r
Repos:
Active apt sources in file /etc/apt/sources.list.d/debian.list
deb http://httpredir.debian.org/debian/ unstable main contrib non-free
Active apt sources in file /etc/apt/sources.list.d/extra.list
deb http://ftp.spline.de/pub/siduction/extra unstable main
Active apt sources in file /etc/apt/sources.list.d/fixes.list
deb http://ftp.spline.de/pub/siduction/fixes unstable main contrib non-free
Contrib and non-free archives do exist in the extra repo, so users might later add those.
At the moment for the old xserver 17.3 there is fglrx-driver and nvidia-driver in debian.
greetings
musca
So this means that "base" and "user" repos are gone/integrated in "extra" and "fixes"?
would it be possible for one of the team members to update the list of currently available repositories also here? --> http://packages.siduction.org/
Where can I find the archive signing key as I get this error:
Reading package lists... Done
W: GPG error: http://packages.siduction.org/base unstable InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 15CBD88045C45076
W: The repository 'http://packages.siduction.org/base unstable InRelease' is not signed.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: There is no public key available for the following key IDs:
15CBD88045C45076
Thanks
you could try pipers "old fashioned" solution in
http://forum.siduction.org/index.php?topic=3381.msg29023#msg29023
Quote from: wannek3 on 2016/01/31, 11:24:37
you could try pipers "old fashioned" solution in
http://forum.siduction.org/index.php?topic=3381.msg29023#msg29023 (http://forum.siduction.org/index.php?topic=3381.msg29023#msg29023)
That didn't work, but had to add the extras repo as that was where the archive key package was. Ideally the archive key should be in the base repo as probably not everyone has the extras repo enabled.
Haven't tried yet, haven't had errors, but just
apt-key add Release.key
or
apt key add Release.key
might work
Quote from: piper on 2016/01/31, 16:50:30
Haven't tried yet, haven't had errors, but just
apt-key add Release.key
or
apt key add Release.key
might work
Thanks piper for the tip
As I reed the first post, first line, base repo is gone or did I understood it wrong?
greets ayla
its not used any longer - some ancient kernels are in, we have dont removed it yet to prevent bugs
Quote from: melmarker on 2016/02/01, 04:10:57
its not used any longer - some ancient kernels are in, we have dont removed it yet to prevent bugs
Same applies for "user" repo?
i think the user repo will stay - until now it was used only several times by users - and thats the reason why the user repo isn't activated in an standard installation.
Hello absolut,
Alf introduced me into the editing team (I won't regret, no?) and finally we updated the announced sources.
Last call: please update all ftp:// links to http:// in your sources.
download/mirrors (english) (http://forum.siduction.org/index.php?page=8) and download/mirrors (german) (http://forum.siduction.org/index.php?page=7)
http://packages.siduction.org/ (english only)
For testers we have hid a tiny easter egg at the liquorix mirror. Feedback welcomed.
greetings
musca
hi musca!
thanks a lot for updating the packages lists. it is now consistent with current ISOs and will not be causing confusion anymore among potential / actual users ... (i hope) :-)
best
absolut
[deleted - error was on my router]
QuoteHas there been a change of sources?
No, but you have a problem with dns!
Could not resolve 'httpredir.debian.org'
Could not resolve 'ftp.spline.de'
Could not resolve 'ftp.spline.de'
Liegt wohl eher am ftp-Server und nicht am lokalen Rechner.
Quote from: samoht on 2016/02/17, 16:18:30
Liegt wohl eher am ftp-Server und nicht am lokalen Rechner.
httpredir.debian.org is not a ftp-server!
... on my computer:
# LANG=C apt update
Ign:1 http://ftp.spline.de/pub/siduction/extra unstable InRelease
Ign:2 http://ftp.spline.de/pub/siduction/fixes unstable InRelease
Err:3 http://ftp.spline.de/pub/siduction/extra unstable Release
Unable to connect to ftp.spline.de:http:
Err:4 http://ftp.spline.de/pub/siduction/fixes unstable Release
Unable to connect to ftp.spline.de:http:
Hit:5 http://download.virtualbox.org/virtualbox/debian jessie InRelease
Hit:6 http://repository.spotify.com stable InRelease
Hit:7 http://mirror.sinavps.ch/debian testing InRelease
Hit:9 http://debian.ethz.ch/debian experimental InRelease
Hit:8 http://ftp.nl.debian.org/debian unstable InRelease
Hit:10 https://deb.opera.com/opera-developer stable InRelease
Hit:11 http://incoming.debian.org/debian-buildd buildd-unstable InRelease
Reading package lists... Done
E: The repository 'http://ftp.spline.de/pub/siduction/extra unstable Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure( manpage for repository creation and user configuration details.
E: The repository 'http://ftp.spline.de/pub/siduction/fixes unstable Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure( manpage for repository creation and user configuration details.
Certainly no local router problem.
Update1:
Not accessible by mobile network.
Update2:
spline server accessible again.
try the ones listed at http://packages.siduction.org/ (http://packages.siduction.org/)
works for me...
greetings,
mork
Had to change my sources from ftp to http as recommended in the package lists, everything worked great after that. :)