Sparky 5.8 updating problem

[Midas]

Hi there.

Please excuse the newbie question, but these are my tentative first steps with Sparky. I have Sparky's stable version running off a USB3 pendrive, ATM, and mostly everything works fine.

Not long ago, while performing 'apt update' and 'apt upgrade' in the command console, I started getting the following error.

Code Select Expand

Ign http://security.debian.org testing/updates InRelease
Err http://security.debian.org testing/updates Release                                                                             
  404  Not Found [IP: 151.101.132.204 80]

...

E: The repository 'http://security.debian.org testing/updates Release' no longer has a Release file.
E: Repository 'http://ftp.debian.org/debian testing InRelease' changed its 'Codename' value from 'buster' to 'bullseye'
E: Repository 'http://www.deb-multimedia.org testing InRelease' changed its 'Codename' value from 'buster' to 'bullseye'
E: Failed to download some files
W: Failed to fetch http://ftp.debian.org/debian/dists/testing/InRelease:
W: Failed to fetch http://www.deb-multimedia.org/dists/testing/InRelease:
W: Failed to fetch http://security.debian.org/dists/testing/updates/Release: 404  Not Found [IP: 151.101.132.204 80]
E: Some index files failed to download. They have been ignored, or old ones used instead.

...

I didn't think much of it, taking for granted to I'd need to update my sources list down the line.

Today, I finally got down to do it, but after searching around (mainly here at the forum) I got no clear instructions for that.

More, I found some instructions to update to a more recent release that expressly said that I need to have Debian Security repos for that to work.

So I'm relying on some community tips for the best way to proceed.

All help appreciated and thanks in advance. :)

P.S.: I already looked in '/etc/apt/sources.list.d' and couldn't find the failing repos in the more likely locations. Synaptic does list them, though.

[paxmark1]

Please post output of "inxi -r"  or the actual /etc/... ...

[Midas]

Here you have the full 'inxi -r' output:

Code Select Expand

Repos:     Active apt repos in: /etc/apt/sources.list
           1: deb http://ftp.debian.org/debian/ testing non-free contrib main
           2: deb-src http://ftp.debian.org/debian/ testing non-free contrib main
           3: deb http://security.debian.org/ testing/updates non-free contrib main
           4: deb-src http://security.debian.org/ testing/updates non-free contrib main
           5: deb http://www.deb-multimedia.org/ testing non-free main
           No active apt repos in: /etc/apt/sources.list.d/dropbox.list
           No active apt repos in: /etc/apt/sources.list.d/google.list
           No active apt repos in: /etc/apt/sources.list.d/liquorix.list
           No active apt repos in: /etc/apt/sources.list.d/pipelight.list
           No active apt repos in: /etc/apt/sources.list.d/playonlinux.list
           No active apt repos in: /etc/apt/sources.list.d/sid.list
           Active apt repos in: /etc/apt/sources.list.d/softmaker.list
           1: deb http://shop.softmaker.com/repo/apt/ wheezy non-free
           Active apt repos in: /etc/apt/sources.list.d/sparky-stable.list
           1: deb https://sparkylinux.org/repo/ core main
           2: deb-src https://sparkylinux.org/repo/ core main
           3: deb https://sparkylinux.org/repo/ stable main
           4: deb-src https://sparkylinux.org/repo/ stable main
           No active apt repos in: /etc/apt/sources.list.d/virtualbox.list
           No active apt repos in: /etc/apt/sources.list.d/wine-staging.list

[Midas]

Well, advancing my research of possible solutions I found an answer at unix.stackexchange.com/a/528896 that I'll quote here in case it helps someone else.

Change testing/updates to testing-security in your sources.list to match http://security-cdn.debian.org/debian-security/dists/testing-security/
Then run apt update instead of apt-get update to interactively accept the various changes.

I went ahead and did just that. Had to answer yes to a couple of prompts and download about 46MB of updating info.

Problem is, now I have 583 upgradable packages in queue, many of them for core system files, so I'm unsure if I should proceed.

By the looks of it, it appears as if I switched from the stable to the testing branch.

How do I go back? I haven't upgraded anything yet, but the Eye of Gnome package that was refusing to install on account of missing dependencies did install just fine after this.

[paxmark1]

Good news - You are on a usb.  Possibly because you are trying things out before you put in onto your computer. 

Your /etec/apt/sources.list is clearly in testing.  You have not specified the specific Sparky image that you downloaded and put onto the usb. 

https://sparkylinux.org/download/         

please specify which iso / image you downloaded.  Also - when.       If you run a checksum on it

Hypothesis:  If a Sparky 5.blah iso was downloaded months ago, it would point to testing.  I believe 5.7 amd all other previous versions would be included in the images that would point to testing.   

[Midas]

Your /etec/apt/sources.list is clearly in testing. You have not specified the specific Sparky image that you downloaded and put onto the usb.

https://sparkylinux.org/download/   

please specify which iso / image you downloaded.  Also - when.       If you run a checksum on it

Sorry for that. Although it was a few months ago, Im quite sure it was the SparkyLinux 5.8 Xfce x86_64/amd64 ISO. What I am not so sure about is the procedure followed to install to USB. Does this help?

Code Select Expand

$ uname -a
Linux Sparky 4.19.0-5-amd64 #1 SMP Debian 4.19.37-3 (2019-05-15) x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID: Sparky
Description: SparkyLinux 5.8 (Nibiru)
Release: 5.8
Codename: buster


     

Hypothesis:  If a Sparky 5.blah iso was downloaded months ago, it would point to testing.  I believe 5.7 amd all other previous versions would be included in the images that would point to testing.

Yeah, I recall being mildly puzzled by the fact that despite having downloaded the "Stable" ISO, it was pulling updates from testing repositories. But then again my knowledge is on the slim side of the issue.

You are on a usb.  Possibly because you are trying things out before you put in onto your computer.

I'm on USB because I need a portable OS for casual work on unknown computers and general system rescue and Sparky has been performing remarkably well for that (although it was unable to boot a Lenovo x220) up to this updating conundrum.

Plus, having to work with some legacy hardware, I value the fact that it is able to run from RAM.

But yes, I very much like to know clearly what I'm dealing with before I commit.

[penguin]

H Midas. I have seen your post beofre but I have not get attention ti it. I will give my advice based on my experience.

First. I never have used Sparky as portable OS from USB . You can have/try other OS ( really I like  Antix or MX Linux), but also Porteus , Puppy etc that are build with idea of being or function as portable ( making system persistence ) etc . etc.  If you want to run occasionally why You need to update ? Because as I know that Sparky does not build a personalized USB  from an installed machine - build it without your software (as MX Linux and Antix), if you really need a personalized USB, try Antix or MX Linux ( or use persistence or build personalized USB from and updated Antix , MX Linux):
Second. Sparky was not able to install on Lenovo X220? I do not believe. Maybe you have made something wrong. Lenovo is practically one of the safest machines that one can install Linux(does not matter what kind). Lenovo are practically the most compatible machines to run a Linux Distro. Enter Bios and enable Legacy Mode. Calamares installer does not install Sparky if during install detects hat UEFI is enabled and you have not a small portion of 300 MB ( Fat32) in your partition (that will react as ESP). I have installed Linux in a Lenovo X201i, Lenovo T420, Lenovo T430, Lenovo x60. No problem at all. But also not problem to install Linux on Fujitsu or HP
Lets come now to updating point. If want to update or upgrade Sparky in USB , dor what reasons you need other utilities, google, Play on Linux, or wine in this Sparky USB, when you intend to use it sporadically as safe OS ? Why you have hardened this USB with such kind of utilities ? Anyway. Your upgrade problem comes fro repositories. By my experience with Sparky really there is not (or I did not found) a clearly way described for Sparky repos. I found also that pavroo has updated information how to pass to Old Stable, Stable , Testing but something vital is missing that I have also verified yesterday when I tried to change Sparky 5.8 to testing line.  If one read here

Code Select Expand

https://sparkylinux.org/wiki/doku.php or here

Code Select Expand

https://sparkylinux.org/sparky-2019-08/ some information is missing.
Also if someone download lets say XFCE semi rrolling from

Code Select Expand

https://sparkylinux.org/download/rolling/

I downloaded and checked names of Debian Testing Repo in the Live USB . For names of Debian Repo better use byllseye instead of testing (to be in the safe side)  - See my follow explanations (I repeat:  Pay attention : Debian Repo not Sparky Repo )

Lets make it clear.

I have copied the follow info from pavroo in

Code Select Expand

https://sparkylinux.org/wiki/doku.php/repository_oldstable


Old Stable

Code Select Expand


sudo nano /etc/apt/sources.list.d/sparky-oldstable.list

and paste into the file:

Code Select Expand


deb https://sparkylinux.org/repo oldstable main
deb-src https://sparkylinux.org/repo oldstable main
deb https://sparkylinux.org/repo core main
deb-src https://sparkylinux.org/repo core main

Create a preference file:

Code Select Expand

sudo nano /etc/apt/preferences.d/sparky
and paste into the file:

Code Select Expand

Package: *
Pin: release o=SparkyLinux
Pin-Priority: 1001

Otherwise you can do it automatically by , install 'sparky-apt' and 'sparky4-apt' packages to do so.

Public key (everywhere for all old stable, stable or testing you need Sparky key ).

Download the Sparky's Public Key as a "deb" package from:

https://sparkylinux.org/repo/pool/main/s/sparky-keyring/

Then install it:

sudo dpkg -i /path/to/sparky-keyring_VERSION_all.deb
sudo apt-key add /usr/share/keyrings/sparkylinux.gpg.key

or get the key manually ('wget' has to be installed):

wget -O - https://sparkylinux.org/repo/sparkylinux.gpg.key | sudo apt-key add -

Uppssss....

What is missing in the above mentioned instruction ???

You need to reflect changes also in your Debian repos.

+++++++++++++++++++++++++++++++++++++
For Old Stable Line (Stretch) 

read the above mentioned explanations from https://sparkylinux.org/wiki/doku.php/repository_oldstable
/etc/apt/sources.list.d (needs to have as follow )

create it by sudo nano /etc/apt/sources.list.d (or change names in Repositories - Synaptic)

(follow are my Debian repos but should be similar for you )

Code Select Expand

deb http://ftp.debian.org/debian/ strecth non-free contrib main
deb-src http://ftp.debian.org/debian/ stretch non-free contrib main
deb http://security.debian.org/ stretch/updates non-free contrib main
deb-src http://security.debian.org/ stretch/updates non-free contrib main

(additional/optional)

Code Select Expand

deb http://www.deb-multimedia.org/ stretch main non-free

Code Select Expand

deb https://download.mono-project.com/repo/debian stable-stretch main

++++++++++++++++++++++++++++++++++++++


++++++++++++++++++++++++++++++++++++++
For Stable Line (Buster)

read explanations from  https://sparkylinux.org/wiki/doku.php/repository_stable

Missing information :

/etc/apt/sources.list.d (needs to have as follow )

create it by sudo nano /etc/apt/sources.list.d ( or change names in Repositories - Synaptic)

(my Debian repos but should be similar for you)

Code Select Expand

deb http://ftp.debian.org/debian/ buster non-free contrib main
deb-src http://ftp.debian.org/debian/ buster non-free contrib main
deb http://security.debian.org/ buster/updates non-free contrib main
deb-src http://security.debian.org/ buster/updates non-free contrib main

(additional/optional)

Code Select Expand

deb http://www.deb-multimedia.org/ buster main non-free

Code Select Expand

deb https://download.mono-project.com/repo/debian stable-buster main

++++++++++++++++++++++++++++++++++++++


++++++++++++++++++++++++++++++++++++++
For Rolling Line (Byllseye)

read  explanations from https://sparkylinux.org/wiki/doku.php/repository_testing

The name of Debian Testing is Byllseye (maybe testing can do the job but to be safe, use byllseye instead of it)

Missing Information

/etc/apt/sources.list.d (needs to have as follow )

create it by sudo nano /etc/apt/sources.list.d ( or change names in Repositories - Synaptic)

(follow are my Debian repos but should be similar for you )

Code Select Expand

deb http://security.debian.org/ byllseye/updates non-free contrib main
deb-src http://security.debian.org/ byllseye/updates non-free contrib main

(additional/optional)

Code Select Expand

deb http://www.deb-multimedia.org/ buster main non-free

Code Select Expand

deb https://download.mono-project.com/repo/debian stable-buster main

++++++++++++++++++++++++++++++++++++++

P.S.
For any possible mistake(typo) in the name of repos or any missing pgp key , please check in the internet.

For example, installing of media codecs in Debian 10 as follow :

https://linuxhint.com/install_multimedia_codecs_debian_10/

Or installing of Mono project as follow:

https://www.mono-project.com/download/stable/#download-lin-debian

Or another link to correct your repos

https://unix.stackexchange.com/questions/528751/cannot-update-apt-list-repository-no-longer-has-a-release-file

[paxmark1]

A testing - rolling version is very very probably not what you want for a live usb. 

Quibble.  for the Debian section of etc/apt/sources.list  - either bullseye or testing should yield the same results, until 2021 July ish.  no capital letters in your source.lists. 

So yes, you are/were using a usb.  So what is your usage going to be - and then select the proper tool - iso - type of linux.  And download a recent copy of that.  penguins suggestions for usb installs are tried and tested. 

Yes, your lenovo should probably host almost any linux distribution easily.  There are occasions that the calamares install will have problems, it is in active development.  If it fails in Sparky (or others) use the advanced installer.  See the wiki.  Sparky should work well.  Download a recent iso, that may have been your biggest problem, using an old iso with the changes in versions. 

The steps outlined by penguin for old stable and stable seem doable and workable. 
 

[penguin]

I run Sparky XFCE.

Yesterday I upgraded a Sparky 4.1 to the new version of Sparky 5.8 in one of my laptops. I remember that the last time that I upgraded Sparky from 4.1 to 5.8 I had no such kind of problems, see as follow:

First pavroo. Correct me if I am wrong. If one would try installing sparky_apt or sparky5_apt he cannot do it without changing firstly repos: from stretch to buster. Please investigate it. If it is true ,so correct Sparky Wiki pages when said .....

Code Select Expand

Otherwise, install 'sparky-apt' and 'sparky5-apt' packages to do so.
The debian repos should be changed before because the libraries needed by packages dwell in the buster repos. After yesterday upgrade I had three problems

1- A start job for Network Manager Waiting Service that was impossible to start (I waited for this service 1:30 min and after that, the system passed this step)
2- A start job is running for hostname service ( I did not changed hostname ) . But this did not allow Sparky to start.
3- A start job is running for uncomplicated firewall . Also this job was impossible to cancel and did not allow Sparky to start.

I do not recall that this problems happens roundly a month ago when I upgraded the last machine.

Because I was not able to stop booting process, I power down system forcibly bu power button and entered/started Sparky in the recover mode ( Advanced Options) and I corrected all problems.

I resolved the first problem by masking Network Manager service as per this link:

Code Select Expand

https://forums.linuxmint.com/viewtopic.php?t=282437

sudo systemctl mask NetworkManager-wait-online.service

The second problem I resolved by disabling UFW ( Uncomplicated Firewall)

and the last one (but as I said I did not changed hostname) as shown in this link:

Code Select Expand

https://stackoverflow.com/questions/48781464/failed-to-start-hostname-service-unit-hostname-service-is-masked

Update the hostname in both /etc/hostname file and /etc/hosts file before running service hostname restart.

On newer systems running systemd (e.g. Ubuntu 16.04), have to use:

sudo hostnamectl set-hostname new-host-name . In here, edit new-host-name with your host name.

And the last one. I found that sparky_aptus was removed during upgrade process and was not installed automatically during upgrade. I installed it manually.

[paxmark1]

It's not the same problem as first poster.  A new post would have probably been better.

For your Debian base programs, Debianistas are saying more and more, don't upgrade re-install.  But Stretch to Buster did not have that many ground breaking things.  XFCE is a good candidate to just go with the apt -full-upgrade. 

I see the LMint guy used systemd-anlayze also. 
2018 is a bit ago.  And the Debian base can vary from LMints Ubuntu base.  I would be looking at the Debian forums for XFCE problems first.  But it does seem reasonable to do that.  "mask" is a one way ticket to dev/null  .   About as close to "kill -9 processblah" as you can get. It is strong

Please post "inxi -r" to get a look at your repositories   Mark up as code.  Also please post the first few items of "systemd-analyze blame"  example follows   Mark up both as code via # button.  Hopefully it has improved.  Example follows of "systemd-analyze blame"
   

Code Select Expand

systemd-analyze blame
          9.407s NetworkManager-wait-online.service
           783ms upower.service
           715ms lvm2-pvscan@8:19.service
           600ms systemd-journal-flush.service
           571ms vboxdrv.service
           571ms systemd-logind.service
           501ms dev-mapper-dbnbuster\x2d\x2dvg\x2droot.device
           421ms udisks2.service


There have been problems for some with the new XFCE, but I believe that is for people using "Sparky6-Bullseye, it just barely failed to get into Sparky5 Buster. 

[penguin]

Thanks @paxmark1.

As I said. I resolved in this way.In the forum folks can find that I have upgraded Sparky 4 to Sparky 5 (means Debian 9 to Debian 10) at least 3 time and I posted my way How To also problems raised during process. Hmmm. But I think that problems raise up comes that still Debian 10 gets so many updates and some maybe create small conflicts. The problem of UFW it is know for Debian 10, but ok. I resolved. I posted for people that would like to upgrade to Debian 10 and hope that this will serve them to be prepared . Also this is a transition phase of Debian 9 to Debian 10 also XFCE from 4.12 to XFCE 4.14.  But still Debian is Debian and Sparky is Sparky. It is so pity that Sparky is not so wide supported by more folks or community. Personally : Sparky deserve much more.