Forum › Forums › Official Releases › antiX-19 “Marielle Franco, Hannie Schaft, Manolis Glezos, Grup Yorum, Wobblies” › System Update – Depots changed from “stable” to “oldstable”!?!?
Tagged: repository old-stable
- This topic has 9 replies, 5 voices, and was last updated Feb 4-5:02 pm by Anonymous.
-
AuthorPosts
-
January 29, 2022 at 5:20 pm #76344Member
NNO
Hi everyone,
I happily use antiX Linux antiX-19.3 “Manolis Glezos” on two machines; a notebook for everyday work and a desktop as fallback-machine if the notebook has serious issues. Therefor I update the system on the desktop only every two to three months.
Lateley, the update process on the desktop gives me a hint, that the depots (repositories?) were somewhat changed. The message says:
• Regarding the depot „http://security.debian.org buster/updates InRelease“ the „Suite“-value was changed from „stable“ to „oldstable“.
• Regarding the depot „http://ftp.de.debian.org/debian buster-updates InRelease“ the „Suite“-value was changed from „stable-updates“ to „oldstable-updates“.
• Regarding the depot „http://ftp.de.debian.org/debian buster InRelease“ the „Version“-value was changed from „10.9“ to „10.11“.
• Regarding the depot „http://ftp.de.debian.org/debian buster InRelease“ the „Suite“-value was changed from „stable“ in „oldstable“.In any of these cases I’m advised to explicitly confirm that updates from these depots can be executed. I should read the man-page of „apt-secure(8)“, what I did.
See picture number 01: 20220129-01-repos-values-changed-permission-required.png
Unfortunately I don’t really know what exactly do I have to do and how do I have to do it.
Therefor I tried the advise by Moderator BobC (https://www.antixforum.com/forums/topic/short-essential-how-to-list-for-the-complete-linux-newbie/page/2/#post-60926) and put the following search into Google:
„depot stable oldstable site:https://www.antixforum.com/forums“
and got only one hit: „New mirrors for iso downloads and antiX packages“ under the path Forum › Forums › News › Announcements ›, starting on November 29, 2018 at 5:56 am by Forum Admin anticapitalista. After reading it I concluded that it doesn’t contain the answer regarding my question.
Honestly, I really don’t have a clue yet. I very much would appreciate if anyone could give me a helping hand here.
Many thanks in advance.
Greetings,
NNO
January 29, 2022 at 5:59 pm #76349Member
sybok
::Hi,
antiX is based on Debian which releases different version when ready.
antiX-19 = based on ‘buster’
antiX-21 = based on ‘bullseye’ (released in 2021).When ‘bullseye’ (current Debian stable) was released, the ‘buster’ was “moved” from being stable to *old-stable*.
This is the information you got when running updates.
‘buster’ will get support (updates) for some time, then it would be a good thing to consider to upgrade to antiX-21.You are safe to confirm you agree and proceed with the updates.
Search internet for EOL (End-Of-Life) of Debian ‘buster’.
Search forum for details on ugprade from antiX-19 to antiX-21.January 29, 2022 at 6:18 pm #76350Moderator
caprea
::If you do your updates with
sudo apt-get update
please try
sudo apt update
insteadThis should lead you to a prompt where you can accept the change
Alternatively, if this doesn’t help ,you can try
apt-get update --allow-releaseinfo-changeJanuary 29, 2022 at 6:38 pm #76351MemberNNO
::Hi sybok,
thank you very much for your fast reply with this overview.
Now I understand the background for this change from “stable” to “oldstable”.
I searched for the EOL info regarding Debian “Buster” and fount out this will approximately be in August 2022.
Because antiX 19 is still maintained I would like to stick to it for a little while and only upgrade my desktop from version antiX-19.3 to antiX-19.5.
The next step now is to confirm the “old-stable” repositories. The update-process advised me to read the manpages of apt-secure(8). I did.
The manpage of apt-secure(8) differentiates between signed depots and unsigned depots. I could there only find a hint in the case of unsigned depots. It reads: “You can force that all apt-clients give only a warning if you put the configuration option “Acquire::AllowInsecureRepositories” to “true”. For signed depots I couldn’t find any command to use. And I assume that the “old-stable” repositories are still signed.
To make a long story short: You wrote:
“You are safe to confirm you agree and proceed with the updates.”
I would like to ask: “How can I confirm and proceed with the updates?” Where do I have to put which command(s)?
[Can someone tell me, please, how to end a block-quote?]
You help is much appreciated. Thank you in advance.
Greetings,
NNO
- This reply was modified 1 year, 3 months ago by NNO.
- This reply was modified 1 year, 3 months ago by NNO.
- This reply was modified 1 year, 3 months ago by NNO.
January 29, 2022 at 6:43 pm #76355Moderator
caprea
::“How can I confirm and proceed with the updates?” Where do I have to put which command(s)?Answered in my post above.
January 29, 2022 at 6:45 pm #76356MemberNNO
::Hi caprea,
thank you for your answer, very kind of you.
I usually do the updates with
“sudo apt-get update
sudo apt-get dist-upgrade”.I will try your advice and give feedback.
Can you give me a hint how to use the B-QUOTE (Block-Quote) function correctly, especially how to end a block-quote? – Many thanks in advance.
Time to try your hints.
See you,
NNO
- This reply was modified 1 year, 3 months ago by NNO.
- This reply was modified 1 year, 3 months ago by NNO.
January 29, 2022 at 7:00 pm #76359Moderator
caprea
::Can you give me a hint how to use the B-QUOTE (Block-Quote) function
This is the way I quote here.
Mark the quote with your left mouse, then click on the button in the upper right corner “QUOTE”
Your answer now contains the quote.- This reply was modified 1 year, 3 months ago by caprea.
January 29, 2022 at 7:29 pm #76362MemberNNO
::Hi caprea,
your hint with
sudo apt update
instead of
sudo apt-get update
and “accept the change” at the prompt already brought the solution!
I’m so relieved. Thank you very much in my name and that of my old faithful desktop!
And thank too you for the explanation regarding the use of the Block-Quote-function.
I wish you and sybok a nice week-end.
Best wishes,
NNO
January 30, 2022 at 1:54 am #76380Memberstevesr0
::I am running 19.2 and didn’t recall getting that message. I looked in synaptic which shows that my repositories include both buster, buster backports and oldstable.
Why aren’t all the buster/19 repos listed as oldstable (except for the “local” ones perhaps)?
stevesr0
February 4, 2022 at 5:02 pm #76810Anonymous
::I am running 19.2 and didn’t recall getting that message. I looked in synaptic which shows that my repositories include both buster, buster backports and oldstable.
Why aren’t all the buster/19 repos listed as oldstable (except for the “local” ones perhaps)?
Consider the time (date) your 19.2 /etc/apt/sources.d/*.list files were drafted or were last edited. At that time “oldstable” (never old-stable, with a dash!) would have pointed to (redirected to, server-side) the packages compiled for use with the “stretch” suite. Nowadays however, “oldstable” is redirected to (server-side) packages compiled with the “buster” suite.
The OP screenshot indicates use of some non-debian package repositories (zotero, et al).
On such servers, who can guess which suite a downloadable package was compiled for use with?
(Don’t guess, seek documentation/clarification from the zotero or whichever project site.)read this short wiki page wiki.debian.org/DebianOldStable then post back if you still have remaining questions.
ps:
The questions in this topic, and the associated answers, merit placement in the antixlinuxfan.miraheze.org wiki -
AuthorPosts
- You must be logged in to reply to this topic.
