[SOLVED] synaptic and muon are giving me a strange not-error message that i can't figure out

[przxqgl]

synaptic and muon are both giving me a strange "not-error" message, that says:

Could not download all repository indexes:
The repository may no longer be available or could not be contacted because of network problems. If available, an older version of the failed index will be used. Otherwise, the repository will be ignored. Check your network connection and ensure the repository address is correct in 'Repositories' under 'Settings'...

then it says the part i can't figure out:

Repository 'http://ddebs.ubuntu.com bionic-updates Release' changed its 'Suite' value from 'bionic-proposed' to 'bionic-updates'
Repository 'http://ddebs.ubuntu.com bionic-updates Release' changed its 'Codename' value from 'bionic-proposed' to 'bionic-updates'

i can see nowhere in synaptic or muon where it is possible to change the "Suite" value, or the "Codename" value...

can someone help me figure this out? i'm afraid i'm not getting important updates.

[claydoh]

then it says the part i can't figure out:

Repository 'http://ddebs.ubuntu.com bionic-updates Release' changed its 'Suite' value from 'bionic-proposed' to 'bionic-updates'
Repository 'http://ddebs.ubuntu.com bionic-updates Release' changed its 'Codename' value from 'bionic-proposed' to 'bionic-updates'

i can see nowhere in synaptic or muon where it is possible to change the "Suite" value, or the "Codename" value...

can someone help me figure this out? i'm afraid i'm not getting important updates.

I believe that some of the repos had some parts re-named, or some naming was corrected, I can't find which. Nothing to worry about, to be sure, and I have not found the reason why.
To 'fix' it, you will need to run

sudo apt update

to get a 'yes/no' prompt to accept the changes. (note, if you run the old-fashioned apt-get, you won't get the prompt)

This should take care of this, as well as the 'Could not download all repository indexes' message, I think. But if not, there will be more useful info on the specific cause, and we can go from there if necessary.



What 'Suite" and 'Codename' are referring to are just the names for the different Ubuntu repositories. 'bionic-updates' is pretty obvious, and one of the important ones, though 'bionic-proposed' is not, and not normally used as a default. I think there was a screw up somewhere but have not found out why.

[przxqgl]

thanks, that fixed it...

i wonder why the fix is to run the command-line, and completely hide it on the GUI, except for the not-error message? i wonder why the not-error message tells me to go somewhere and do something that i can't do with the GUI? 😕

[claydoh]

The very rare instance of this happening is something the gui programs simply have not had to deal with, is my guess.

This is the first time I have ever personally come across this in using debian based distros since 2005.

[deanr]

This is the first time I have ever personally come across this in using debian based distros since 2005.

That's encouraging

[przxqgl]

note, if you run the old-fashioned apt-get, you won't get the prompt.

i just noticed this...

when did apt-get become "old-fashioned"?

is there a syntax difference between the way apt-get is used and the way apt is used?

are there reasons to use apt rather than apt-get other than not getting the prompt?

is there a plan to deprecate apt-get at some point?

i've had apt-get in my "notebook of interesting and useful linux commands" ever since kubuntu 3.x... should i just remove the -get part of the command, or what?

[claydoh]

apt-get has been superseded by apt for some time now ( it has been around since 2014, and Ubuntu included it starting with 16.04), though apt-get is still around for compatibility purposes, and probably will be for a while to come.
There are differences in the syntax, which you can see looking at the man page for it.

apt update and apt full-upgrade being the most notable differences.

Much more info here
https://itsfoss.com/apt-vs-apt-get-difference/

[chimak111]

To 'fix' it, you will need to run

sudo apt update

to get a 'yes/no' prompt to accept the changes. (note, if you run the old-fashioned apt-get, you won't get the prompt)

It appears it is possible with apt-get if one uses apt-get --allow-releaseinfo-change.

man apt-get has

Allow the update command to continue downloading data from a repository which changed its information of the release contained in the repository indicating e.g a new major release. APT will fail at the update command for such repositories until the change is confirmed to ensure the user is prepared for the change. See also apt-secure(8) for details on the concept and configuration.

Debian is promoting the use of apt for interactive use but not for scripts as evidenced by

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

[przxqgl]

apt-get has been superseded by apt for some time now ( it has been around since 2014, and Ubuntu included it starting with 16.04)...

bleh...

sorta gives you an idea about how conscious i have been about my computer for the past few years...

thanks for the updated info... now all i gotta do is remember to use it.

[jglen490]

Less typing ... that's how I remember it