Re: Debian installer - mirror does not support trixie
On Wed, 15 Oct 2025 23:18:19 +0200
Grześ Andruszkiewicz <gandrusz@gmail.com> wrote:
> This was my first choice, same error 😐
Hmmm…. In that case, please show us (copy and paste, please) your
/etc/apt/sources.list, or, if you have modernized your sources,
/etc/apt/sources.list.d/debian.sources. Then please run (as root) "apt
update", then "apt upgrade", and copy and paste (unwrapped, if
possible) the session into your reply. e.g.:
root@tiassa:~# apt update
Get:1 http://security.debian.org/debian-security trixie-security InRelease [43.4 kB]
Hit:2 http://deb.debian.org/debian trixie InRelease
Get:3 http://deb.debian.org/debian trixie-updates InRelease [47.3 kB]
Get:4 http://security.debian.org/debian-security trixie-security/main amd64 Packages [53.8 kB]
Ign:5 https://repo.vivaldi.com/stable/deb stable InRelease
Hit:6 https://repo.vivaldi.com/stable/deb stable Release
Fetched 145 kB in 1s (189 kB/s)
1 package can be upgraded. Run 'apt list --upgradable' to see it.
root@tiassa:~# apt upgrade
Upgrading:
firefox-esr
Summary:
Upgrading: 1, Installing: 0, Removing: 0, Not Upgrading: 0
Download size: 71.7 MB
Space needed: 355 kB / 183 GB available
Continue? [Y/n] y
Get:1 http://security.debian.org/debian-security trixie-security/main amd64 firefox-esr amd64 140.4.0esr-1~deb13u1 [71.7 MB]
Fetched 71.7 MB in 12s (6,163 kB/s)
Reading changelogs... Done
(Reading database ... 162969 files and directories currently installed.)
Preparing to unpack .../firefox-esr_140.4.0esr-1~deb13u1_amd64.deb ...
Leaving 'diversion of /usr/bin/firefox to /usr/bin/firefox.real by firefox-esr'
Unpacking firefox-esr (140.4.0esr-1~deb13u1) over (140.3.1esr-1~deb13u1) ...
Setting up firefox-esr (140.4.0esr-1~deb13u1) ...
Processing triggers for hicolor-icon-theme (0.18-2) ...
Processing triggers for man-db (2.13.1-1) ...
Processing triggers for mailcap (3.74) ...
Processing triggers for desktop-file-utils (0.28-1) ...
Scanning processes...
Scanning processor microcode...
Scanning linux images...
Running kernel seems to be up-to-date.
The processor microcode seems to be up-to-date.
No services need to be restarted.
No containers need to be restarted.
No user sessions are running outdated binaries.
No VM guests are running outdated hypervisor (qemu) binaries on this host.
root@tiassa:~#
Thanks
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
Reply to: