I have two systems running bookworm, a laptop at 12.13 and aspecify the desired suite in absolute terms whereas the desktop uses
desktop at 12.11.
I am still able to update the laptop from bookworm repositories but
the desktop refuses, telling me that repositories have changed
"Version" and 'Codename' to various trixie related values.
From this difference in behavior, I speculate that the laptop's /ets/apt/sources.list uses codenames (for example, "bookworm") to
I would like to stay on bookworm for a while and also to keep the
two systems at the same level.
How would I "fix" this so the desktop will update from bookworm?
On Thu, Jan 22, 2026 at 11:03:32 -0800, Bob McGowan wrote:
I am still able to update the laptop from bookworm repositories but the >> desktop refuses, telling me that repositories have changed "Version" and >> 'Codename' to various trixie related values.
Use "apt update" instead of "apt-get update" at least one time.
This should prompt you to confirm that it's OK to update the Version
and Codename values.
I am still able to update the laptop from bookworm repositories but the
desktop refuses, telling me that repositories have changed "Version" and
'Codename' to various trixie related values.
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>I have two systems running bookworm, a laptop at 12.13 and a
desktop at 12.11.</p>
<p>I am still able to update the laptop from bookworm repositories
but the desktop refuses, telling me that repositories have changed
"Version" and 'Codename' to various trixie related values.</p>
<p>I would like to stay on bookworm for a while and also to keep the
two systems at the same level.</p>
<p>How would I "fix" this so the desktop will update from bookworm?</p>
<p>Thanks,</p>
<p>Bob</p>
</body>
</html>
On Thu, Jan 22, 2026 at 11:03:32 -0800, Bob McGowan wrote:
I am still able to update the laptop from bookworm repositories but the >> desktop refuses, telling me that repositories have changed "Version" and >> 'Codename' to various trixie related values.Use "apt update" instead of "apt-get update" at least one time.
This should prompt you to confirm that it's OK to update the Version
and Codename values.
I have two systems running bookworm, a laptop at 12.13 and a desktop at 12.11.
I am still able to update the laptop from bookworm repositories but the desktop refuses, telling me that repositories have changed "Version" and 'Co dename' to various trixie related values.
I would like to stay on bookworm for a while and also to keep the two systems at the same level.
How would I "fix" this so the desktop will update from bookworm?
I have two systems running bookworm, a laptop at 12.13 and a desktop at 12.11.
I am still able to update the laptop from bookworm repositories but the desktop
refuses, telling me that repositories have changed "Version" and 'Codename' to
various trixie related values.
Hi,
On Thu, Jan 22, 2026 at 11:03:32AM -0800, Bob McGowan wrote:
I have two systems running bookworm, a laptop at 12.13 and a desktop at 12.11.At first reading I thought that this would be because you had "stable" instead of "bookworm" in the /etc/apt/sources.list file. However, you
I am still able to update the laptop from bookworm repositories but the desktop
refuses, telling me that repositories have changed "Version" and 'Codename' to
various trixie related values.
have since shown us the contents of that file and confirmed that it does
say "bookworm".
Therefore my next guess is that the message about repositories changing
in fact talks about the next bookworm point release, 12.13, and not
anything to do with trixie (which would be 13.x). Can you confirm the
exact wording of the message please?
If that is the case then the solution is as Andrew Cater mentioned: use
"apt update" and it will prompt you to accept the change to the new
point release of bookworm.
If that's not the case and it really is offering to upgrade you to
trixie then I am at a loss as to how, since you have showed us a
sources.list that is still on bookworm. Possibly there is some other repository below /etc/.apt/sources.list.d/.
Thanks,
Andy
Please provide the output of `cat /etc/apt/sources.list | grep -v '^#' `.[...]
The desktop is down right now so this is not exact, but the "Version"
says 12 -> 13 and "Codename" says trixie.
this is not exact
On 1/23/26 08:08, Bob McGowan wrote:
The desktop is down right now so this is not exact, but the "Version"
says 12 -> 13 and "Codename" says trixie.
Try to visually edit the sources.list file to see its location and if it matches the content of what you have provided on this list.
To me, it looks like you might have multiple sources.list files being used.
Look for ANY files under/etc/apt/sources.list.d/ and
either PASTE them or ATTACH them to your email so we can see their
exact contents.
On 23/01/2026 6:54 pm, Greg Wooledge wrote:
Look for ANY files under/etc/apt/sources.list.d/ and
either PASTE them or ATTACH them to your email so we can see their
exact contents.
It is more straightforward to just execute
apt policy
It reports configured repositories and pinning.
Hi,
On Thu, Jan 22, 2026 at 11:03:32AM -0800, Bob McGowan wrote:
I have two systems running bookworm, a laptop at 12.13 and a desktop at 12.11.At first reading I thought that this would be because you had "stable" instead of "bookworm" in the /etc/apt/sources.list file. However, you
I am still able to update the laptop from bookworm repositories but the desktop
refuses, telling me that repositories have changed "Version" and 'Codename' to
various trixie related values.
have since shown us the contents of that file and confirmed that it does
say "bookworm".
Therefore my next guess is that the message about repositories changing
in fact talks about the next bookworm point release, 12.13, and not
anything to do with trixie (which would be 13.x). Can you confirm the
exact wording of the message please?
If that is the case then the solution is as Andrew Cater mentioned: use
"apt update" and it will prompt you to accept the change to the new
point release of bookworm.
If that's not the case and it really is offering to upgrade you to
trixie then I am at a loss as to how, since you have showed us a
sources.list that is still on bookworm. Possibly there is some other repository below /etc/.apt/sources.list.d/.
Thanks,
Andy
I have two systems running bookworm, a laptop at 12.13 and a desktop at 12.11.
I am still able to update the laptop from bookworm repositories but the desktop refuses, telling me that repositories have changed "Version" and 'Co dename' to various trixie related values.
I would like to stay on bookworm for a while and also to keep the two systems at the same level.
How would I "fix" this so the desktop will update from bookworm?
Hi,
On Thu, Jan 22, 2026 at 11:03:32AM -0800, Bob McGowan wrote:
I have two systems running bookworm, a laptop at 12.13 and a desktop at 12.11.
I am still able to update the laptop from bookworm repositories but the desktop
refuses, telling me that repositories have changed "Version" and 'Codename' to
various trixie related values.
At first reading I thought that this would be because you had "stable" instead of "bookworm" in the /etc/apt/sources.list file. However, you
have since shown us the contents of that file and confirmed that it does
say "bookworm".
Therefore my next guess is that the message about repositories changing
in fact talks about the next bookworm point release, 12.13, and not
anything to do with trixie (which would be 13.x). Can you confirm the
exact wording of the message please?
Thanks,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
It's warning you that 12.11 is now 12.13, I expect.
Just run apt and update it.
On Fri, Jan 23, 2026 at 22:07:41 +0000, Andrew M.A. Cater wrote:
It's warning you that 12.11 is now 12.13, I expect.That's what I thought, too, when I read the first message in this
Just run apt and update it.
thread.
It turns out the OP actually had multiple contradictory sources,
one in /etc/apt/sources.list (bookworm), and one in some file
under /etc/apt/sources.listl.d/ (trixie), neither of which we ever
got to see.
On 1/23/26 02:58 PM, Greg Wooledge wrote:.
It turns out the OP actually had multiple contradictory sources,
one in /etc/apt/sources.list (bookworm), and one in some file
under /etc/apt/sources.listl.d/ (trixie), neither of which we ever
got to see.
Yes, I had files in /etc/apt/sources.list.d that were causing the problem
I'm not sure why or when they were created.
I discovered them this morning and simply moved them out of the way and
my update/upgrade ran flawlessly.
I did not think it necessary to send out copies of these errant files
but if you think that would be helpful I can certainly do so.
Yes, I had files in /etc/apt/sources.list.d that were causing the problem.
I'm not sure why or when they were created.
I discovered them this morning and simply moved them out of the way and my update/upgrade ran flawlessly.
Yes, I had files in /etc/apt/sources.list.d that were causing the problem.
I'm not sure why or when they were created.
I discovered them this morning and simply moved them out of the way and
my update/upgrade ran flawlessly.
On Sat, 24 Jan 2026 at 00:51, Bob McGowan <ramjr0915@gmail.com> wrote:
On 1/23/26 02:58 PM, Greg Wooledge wrote:
It turns out the OP actually had multiple contradictory sources,
one in /etc/apt/sources.list (bookworm), and one in some file
under /etc/apt/sources.listl.d/ (trixie), neither of which we ever
got to see.
Yes, I had files in /etc/apt/sources.list.d that were causing the problem.
I'm not sure why or when they were created.
I discovered them this morning and simply moved them out of the way and
my update/upgrade ran flawlessly.
I did not think it necessary to send out copies of these errant files
but if you think that would be helpful I can certainly do so.
Hi, how could *we* know if it would be helpful or not?
Due to your communication style, we do not yet have any
information from which to formulate a useful answer.
What we know:
- you had some files
- we dont know their names
- we dont know what they contain
- something probably put them there for a reason
- we dont know what put them there
- you disabled them somehow
?\_((???))_/?
It *could* be helpful to *you* if those files were there for a reason,
and "moving them out of the way" without any understanding caused
something else that you care about to break mysteriously in the future.
By not showing us exactly what you are doing, and not sharing the
details, you keep us in the dark, which means that we have less idea
than you do about the answers to your questions.
Hi Bob
Bob wrote:
Yes, I had files in /etc/apt/sources.list.d that were causing the problem. >>
I'm not sure why or when they were created.
I discovered them this morning and simply moved them out of the way and
my update/upgrade ran flawlessly.
Great news!
I am assuming now that running `cat /etc/*release*` returns the correct version.
The process sounded confusing. If you encounter such a situation again, with additional and unwanted files being created unexpectedly, please write back, and effort could be undertaken to identify the possible cause.
I did not think it necessary to send out copies of these errant files but if you think that would be helpful I can certainly do so.
The process sounded confusing. If you encounter such a situation
again, with additional and unwanted files being created unexpectedly,
please write back, and effort could be undertaken to identify the
possible cause.
| Sysop: | Jacob Catayoc |
|---|---|
| Location: | Pasay City, Metro Manila, Philippines |
| Users: | 5 |
| Nodes: | 4 (0 / 4) |
| Uptime: | 19:04:01 |
| Calls: | 117 |
| Calls today: | 117 |
| Files: | 367 |
| D/L today: |
540 files (253M bytes) |
| Messages: | 70,845 |
| Posted today: | 26 |