Hi folks.
Today I decided to upgrade my Sparky 8 testing to Sparky 9 testing.
I have proceeded as per follow: instructions
https://wiki.sparkylinux.org/doku.php/upgrade_8_to_9
Everything gone smoothly ( .... which repo should be activated ? see my second post)
Quote from: penguin on October 25, 2025, 03:55:35 PM[....]
Err:10 https://repo.sparkylinux.org forky Release
404 Not Found [IP: 184.174.34.74 443]
Hit:11 http://deb-multimedia.org forky InRelease
Hit:12 http://deb-multimedia.org trixie InRelease
Error: The repository 'https://repo.sparkylinux.org forky Release' does not have a Release file.
(https://i.imgur.com/IqZHXhe.gif) Well, it is clearly indicating that there is a very obvious error in the SparkyLinux repositories. Which, you should correct.
Here. you can see an image with the repositories correctly configured:
(https://i.ibb.co/xt8qTWFF/image.png)
Quote from: penguin on October 25, 2025, 03:55:35 PM[....] Thanks in advance.
You're welcome !!
Cheers !! (https://i.imgur.com/uZvkZOF.gif)
Quote from: penguin on October 25, 2025, 03:55:35 PM[....]
Hit:11 http://deb-multimedia.org forky InRelease
Hit:12 http://deb-multimedia.org trixie InRelease
And obviously, you should also check and correct dmo (
deb-multimedia):
(https://i.ibb.co/QvYGyB4k/image.png)
(https://i.imgur.com/VeeZyZt.gif)
Strange ....
As per description in the
https://wiki.sparkylinux.org/doku.php/upgrade_8_to_9
there are 2 ways to change the repositories . new way and old way.
When I change repositories as per follow sources:
/etc/apt/sources.list.d/debian.sources (new way)
Types: deb deb-src
URIs: http://deb.debian.org/debian/
Suites: forky
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
Types: deb deb-src
URIs: http://security.debian.org/debian-security/
Suites: forky-security/updates
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
Types: deb deb-src
URIs: http://deb.debian.org/debian/
Suites: forky-updates
Components: main contrib non-free non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
/etc/apt/sources.list.d/sparky.sources (new way)
Types: deb deb-src
URIs: https://repo.sparkylinux.org/
Suites: core
Components: main
Signed-By: /etc/apt/trusted.gpg.d/sparky-repo.asc
Types: deb deb-src
URIs: https://repo.sparkylinux.org/
Suites: tiamat
Components: main
Signed-By: /etc/apt/trusted.gpg.d/sparky-repo.asc
No any update comes up one when I use : sudo apt update
de-activating (the above description repos ) and changing them as per per follow sources :
/etc/apt/sources.list (old way)
deb http://deb.debian.org/debian forky main contrib non-free non-free-firmware
deb-src http://deb.debian.org/debian forky main contrib non-free non-free-firmware
deb http://security.debian.org/debian-security/ forky-security/updates main contrib non-free non-free- firmware
deb-src http://security.debian.org/debian-security/ forky-security/updates main contrib non-free non-free-firmware
deb http://deb.debian.org/debian forky-updates main contrib non-free non-free-firmware
deb-src http://deb.debian.org/debian forky-updates main contrib non-free non-free-firmware
deb http://deb-multimedia.org/ forky main non-free
/etc/apt/sources.list.d/sparky.list (old way
deb [signed-by=/usr/share/keyrings/sparky.gpg.key] https://repo.sparkylinux.org/ core main
deb-src [signed-by=/usr/share/keyrings/sparky.gpg.key] https://repo.sparkylinux.org/ core main
deb [signed-by=/usr/share/keyrings/sparky.gpg.key] https://repo.sparkylinux.org/ forky main
deb-src [signed-by=/usr/share/keyrings/sparky.gpg.key] https://repo.sparkylinux.org/ forky main
the second one gives error saying that ( Err:8 https://repo.sparkylinux.org forky Release
404 Not Found [IP: 184.174.34.74 443]
Error: The repository 'https://repo.sparkylinux.org forky Release' does not have a Release file.).
For that reason I disabled repos in the /etc/apt/sources.list.d/sparky.list
When I use sudo apt update or synaptic the updates are fired up.
Any other has experienced the same ?
May be a couple of issues with the 8-9 instructions. May have been edited incorrectly recently.
There is no mention of /etc/apt/sources.list.d/unofficial-multimedia-packages.sourcesand I believe
deb [signed-by=/usr/share/keyrings/sparky.gpg.key] https://repo.sparkylinux.org/ forky main
deb-src [signed-by=/usr/share/keyrings/sparky.gpg.key] https://repo.sparkylinux.org/ forky mainshould read
deb [signed-by=/usr/share/keyrings/sparky.gpg.key] https://repo.sparkylinux.org/ tiamat main
deb-src [signed-by=/usr/share/keyrings/sparky.gpg.key] https://repo.sparkylinux.org/ tiamat main
Simple way to change to the new format would be to use sudo apt modernize-sources and if update complains add Signed-By: /usr/share/keyrings/deb-multimedia-keyring.pgp to /etc/apt/sources.list.d/unofficial-multimedia-packages.sources
Do NOTE that synaptic does not recognise the new format in its repository lists at this stage.
(https://i.imgur.com/IqZHXhe.gif) It seems to be a typing error:
(https://i.imgur.com/KudZcKi.png)
Because, in
the same news item, written on the main page (2025/08/17) it does appear correctly.
And even in this news, a reference is made
to this wiki article with the wrong data.
Cheers !! (https://i.imgur.com/emjz0.gif)
My question was simple one.
When I update repos in the old way, the sudo apt update gets plenty of updates in the terminal.
Meanwhile when I update repos in the new way sudo apt update shows the message : All packages are up to date.
Why this happen ?
See the follow ...
/etc/apt/sources.list[/] (old way)
deb http://deb.debian.org/debian/ forky main contrib non-free non-free-firmware
deb-src http://deb.debian.org/debian/ forky main contrib non-free non-free-firmware
deb http://security.debian.org/debian-security/ forky-security/updates main contrib non-free non-free-firmware
deb-src http://security.debian.org/debian-security/ forky-security/updates main contrib non-free non-free-firmware
deb http://deb.debian.org/debian/ forky-updates main contrib non-free non-free-firmware
deb-src http://deb.debian.org/debian/ forky-updates main contrib non-free non-free-firmware
# deb http://deb-multimedia.org/ forky main non-free
/etc/apt/sources.list.d/sparky.list (old way)
deb [signed-by=/usr/share/keyrings/sparky.gpg.key] https://repo.sparkylinux.org/ core main
deb-src [signed-by=/usr/share/keyrings/sparky.gpg.key] https://repo.sparkylinux.org/ core main
deb [signed-by=/usr/share/keyrings/sparky.gpg.key] https://repo.sparkylinux.org/ tiamat main
deb-src [signed-by=/usr/share/keyrings/sparky.gpg.key] https://repo.sparkylinux.org/ tiamat main
Notice. Instead of forky the right entry tiamat is entered in the above repos
penguin@penguin:~$ sudo apt update
[sudo] password for penguin:
Hit:1 http://security.debian.org/debian-security forky-security/updates InRelease
Hit:2 http://deb.debian.org/debian forky InRelease
Hit:3 http://deb.debian.org/debian forky-updates InRelease
Hit:4 https://repo.sparkylinux.org core InRelease
Hit:5 https://repo.sparkylinux.org tiamat InRelease
Hit:6 http://dl.google.com/linux/earth/deb stable InRelease
1480 packages can be upgraded. Run 'apt list --upgradable' to see them.
Quote from: penguin on October 27, 2025, 07:17:13 PM[....]
When I update repos in the old way, the sudo apt update gets plenty of updates in the terminal.
Meanwhile when I update repos in the new way sudo apt update shows the message : All packages are up to date.
[....]
(https://i.imgur.com/bDtcOwK.gif) Let's see lad.
Because, it seems to me that you are messing up on your own. Whether you use the old or new format, the result can NOT differ.
It must be the same (since you are using the same repositories).
So, check thoroughly if there are any errors (repository, signatures... etc).
Or use the available option '
sudo apt modernize-sources' that
21grams has told you about in his message.
sudo apt modernize-sources && sudo apt --update dist-upgrade
Finally, check if everything is working as it should be ... (https://i.imgur.com/4GCd6.gif)
Good luck !!
Cheers !! (https://i.imgur.com/VeeZyZt.gif)
Seems that problem was solved.
As per pavroo description in the follow link:
https://wiki.sparkylinux.org/doku.php/upgrade_8_to_9
Change of repos old way
/etc/apt/sources.list (old way)
deb http://deb.debian.org/debian forky main contrib non-free non-free-firmware
deb-src http://deb.debian.org/debian forky main contrib non-free non-free-firmware
deb http://security.debian.org/debian-security/ forky-security/updates main contrib non-free non-free-firmware
deb-src http://security.debian.org/debian-security/ forky-security/updates main contrib non-free non-free-firmware
deb http://deb.debian.org/debian forky-updates main contrib non-free non-free-firmware
deb-src http://deb.debian.org/debian forky-updates main contrib non-free non-free-firmware
deb http://deb-multimedia.org/ forky main non-free
/etc/apt/sources.list.d/sparky.list (old way):
deb [signed-by=/usr/share/keyrings/sparky.gpg.key] https://repo.sparkylinux.org/ core main
deb-src [signed-by=/usr/share/keyrings/sparky.gpg.key] https://repo.sparkylinux.org/ core main
deb [signed-by=/usr/share/keyrings/sparky.gpg.key] https://repo.sparkylinux.org/ tiamat main
deb-src [signed-by=/usr/share/keyrings/sparky.gpg.key] https://repo.sparkylinux.org/ tiamat main
Notice in the above repos > tiamat instead of forky
Changing of repos in the new way
/etc/apt/sources.list.d/debian.sources (new way)
Types: deb deb-src
URIs: http://deb.debian.org/debian/
Suites: forky
Components: main contrib non-free non-free-firmware
Enabled:yes
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
Types: deb deb-src
URIs: http://security.debian.org/debian-security/
Suites: forky-security/updates
Components: main contrib non-free non-free-firmware
Enabled:yes
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
Types: deb deb-src
URIs: http://deb.debian.org/debian/
Suites: forky-updates
Components: main contrib non-free non-free-firmware
Enabled:yes
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
Notice : Enabled:yes is added
/etc/apt/sources.list.d/sparky.sources
Types: deb deb-src
URIs: https://repo.sparkylinux.org/
Suites: core
Components: main
Enabled:yes
Signed-By: /etc/apt/trusted.gpg.d/sparky-repo.asc
Types: deb deb-src
URIs: https://repo.sparkylinux.org/
Suites: tiamat
Components: main
Enabled:yes
Signed-By: /etc/apt/trusted.gpg.d/sparky-repo.asc
Notice : Enabled:yes is added
As per clarification found in the follow link https://wiki.debian.org/SourcesList
Here is an example of a debian.sources for trixie:
Types: deb deb-src
URIs: https://deb.debian.org/debian
Suites: trixie trixie-updates
## If you want access to contrib and non-free components,
## add " contrib non-free" after "non-free-firmware":
Components: main non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
Types: deb deb-src
URIs: https://security.debian.org/debian-security
Suites: trixie-security
Components: main non-free-firmware
Enabled: yes
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
But still changing repos in the new way even with Enabled:yes does not function for Debian Update...
Definitely I will use the old way ....
The Enabled:yes addition to allows you to set Enabled:no disabling that repository. The repository is enabled without it.
Do you see any errors in the terminal when you run sudo apt update after changing to the deb822 format (the new way)?
NOTE: If deciding to manually change to the new format, ensure to rename the old sources.list files to .bak ; using debian command sudo apt modernize-sources does this automagically (without the Enables:yes).
Quote from: 21grams on October 29, 2025, 08:41:08 AMThe Enabled:yes addition to allows you to set Enabled:no disabling that repository. The repository is enabled without it.
Do you see any errors in the terminal when you run sudo apt update after changing to the deb822 format (the new way)?
NOTE: If deciding to manually change to the new format, ensure to rename the old sources.list files to .bak ; using debian command sudo apt modernize-sources does this automagically (without the Enables:yes).
I use Sparky Testing for years. I do not remember, since what time. The latest Sister version (Test) was updated through old format version. When I decided to upgrade to tiamat version, I did not noticed the changing names post (as pavroo suggested). So I have used the way, I described in my 1 post. I have created debian and sparky souce repo files manually , de activating the Synaptic sources(or inserting the # in front of each line)
I do not see any error in the terminal. The difference is that the new way repo files does not catch updates and the old one yes.
Anyway... I will continue to continue Sparky Testing using old repo way.