tes== #debian IRC notes for bookworm→trixie release                      ==
== gobby:Teams/IRC/Releases/bookworm-trixie                           ==
== https://gobby.debian.org/export/Teams/IRC/Releases/bookworm-trixie ==

== symlink factoids

no sources.list is <reply>see trixie sources.list
no installation guide is <reply> see trixie installation guide
no release notes is <reply> see trixie release notes
no installer firmware is <reply>see installer firmware trixie
no errata is <reply> see errata trixie

== Factoids with "stable" in key (check for "bookworm", "bullseye" in the value):
==  https://ircbots.debian.net/factoids/search.php?q=stable&term=key

no stable-updates is <reply> see trixie-updates
stable =~ s/Bookworm (12.x)/Trixie (13.x)/
stable sources.list =~ s/bullseye->bookworm/bookworm->trixie/
stable sources.list =~ s/bookworm/trixie/
stable sources.list =~ s/bookworm/trixie/
no stable->testing is <reply>see trixie->forky
no oldstable->stable is <reply>see bookworm->trixie
no oldstable is <reply>see bookworm
no oldstable-security is <reply>see bookworm-security
no oldstable-updates is <reply>see bookworm-updates
no oldoldstable is <reply>see bullseye
no oldoldstable-security is <reply>see bullseye-security
no oldoldstable security is <reply>see oldoldstable-security
bullseye-security =~ s/You should also have a line for <stable-updates>. //
no stable/updates is <reply>see trixie/updates
install oldstable =~ s/bullseye/bookworm/
install stable  =~ s/bookworm/trixie/
security =~ s/bookworm/trixie/
bullseye =~ s/oldstable/oldoldstable/
buster =~ s/<buster->bullseye>/<buster->bullseye>, <elts>/
stretch =~ s/<jessie->stretch>/<stretch->buster>, <elts>/
elts is also jessie-elts ended 2025-06-30.
stable kernel =~ s/bookworm/trixie/

#no buster/bullseye mix is <reply>see oldstable/stable mix
bullseye/bookworm mix =~ s,stable/testing,oldstable/stable,
bookworm/trixie mix is <reply>see oldstable/stable mix
trixie/forky mix is <reply>see stable/testing mix
no trixie/sid mix is <reply>see mixing stable and unstable

no trixie release notes is <reply>The release notes for Debian 13 (Trixie) are at https://www.debian.org/releases/trixie/release-notes/index . See also <bookworm->trixie>, <trixie install guide>

no install trixie is <reply>There are a myriad of different ways to install Debian.  See https://www.debian.org/releases/trixie/debian-installer for a list of images and ask me about <netinst>.  See also <install guide> and <d-i> for detailed instructions.  (If you've never installed Debian before, you should read the install guide.)  Alternatively, ask about full VM <cloud images>.

trixie install guide is <reply> The Installation Guide for Debian 13 "Trixie" can be found at https://www.debian.org/releases/trixie/installmanual . See also <errata> and <trixie release notes>.

== Factoids with "trixie" in key (check for "testing" in the value):
==  https://ircbots.debian.net/factoids/search.php?q=trixie&term=key

no trixie/sid mix is <reply>see mixing stable and unstable
trixie->sid is <reply> see stable->unstable
no trixie/sid is <reply> If /etc/debian_version says "trixie/sid", then you have an out-of-date trixie installation. Try upgrading it to the current trixie release and check to see if you have any <not available> packages that are actually from some (outdated) sid. Ask me about <testing/unstable>.
no why trixie/sid is <reply>see trixie/sid
testing/unstable =~ s,trixie/sid,forky/sid,
testing =~ s/<trixie>/<forky>/
no trixie-backports is <reply>Some packages intended for Forky (which will be Debian 14) but recompiled for use with Trixie (Debian 13) can be found in the trixie-backports repository. See https://backports.debian.org/Instructions/ . Ask me about <bdo>, <backports>.

== Factoids with "bookworm" in the value (check for "stable" in the value)
==    https://ircbots.debian.net/factoids/search.php?q=bookworm&term=value

dmm =~ s/<dmm bookworm>/<dmm trixie>/
dmm =~ s/<dmm bullseye>/<dmm bookworm>/
contrib =~ s/bullseye|bookworm|trixie|sid/bookworm|trixie|forky|sid/
no branch is What release (version) of Debian you are using: bullseye/oldoldstable, bookworm/oldstable, trixie/stable, forky/testing, sid/unstable.  Ask me about <version>.
backports.debian.org =~ s/bookworm/trixie/
backports.debian.org =~ s/bullseye/bookworm/
bdo kernel =~ s/bookworm/trixie/
bdo kernel =~ s/bookworm/trixie/
dbgsym =~ s/bookworm/trixie/
debgen =~ s/bookworm/trixie/
debgen =~ s/bullseye/bookworm/

###########

== Factoids with "testing" in key (check for "trixie" in the value):
==  https://ircbots.debian.net/factoids/search.php?q=testing&term=key

testing sources.list =~ s/trixie/forky/
testing sources.list =~ s/trixie/forky/
testing =~ s,bookworm->trixie,trixie->forky,
testing =~ s/<trixie>/<forky>/
testing-security =~ s/trixie/forky/

== Factoids with "bookworm" in the value
==    https://ircbots.debian.net/factoids/search.php?q=bookworm&term=value

upgrade =~ s/bullseye->bookworm/bookworm->trixie/

# XXX too long! # dmm trixie is <reply>If you really need deb-multimedia.org (are you sure your information isn't 15 years out of date?), then (as root): printf 'Types: deb\nURIs: https://www.deb-multimedia.org\nSuites: trixie\nComponents: main non-free\nSigned-By: /usr/share/keyrings/deb-multimedia-keyring.pgp\nEnabled: yes\n' > /etc/apt/sources.list.d/dmo.source; apt update && apt install deb-multimedia-keyring && apt update.  For an alternative way to load Marillat's archive key, ask me about <apt-key 1F41B907>. See <why not dmm>.

firefox trixie is <reply>Debian 13 "Trixie" contains the extended support release (ESR) version Firefox 128 (package firefox-esr) at the time of this writing. Like previous releases, trixie will track the ESR release until a new ESR becomes needed for security updates. Ask me about <firefox-esr> <trixie-security>.

introduction =~ s/trixie/forky/
introduction =~ s/bookworm/trixie/


== ALL CHANGES ABOVE APPLIED AS OF 2025-08-10

== Factoids with "sid" in the value
==    https://ircbots.debian.net/factoids/search.php?q=sid&term=value

forky/sid is <reply>Debian doesn't distinguish if a system runs testing or unstable. "forky/sid" means a system is either tracking testing or unstable (or a mix). If you want the list of releases your system really tracks, ask me about <tracked suites>. Also ask about <list repositories>, <not available>. See also /usr/share/doc/base-files/FAQ ("Questions about /etc/issue and /etc/debian_version").
no, trixie/sid is <reply>If /etc/debian_version says "trixie/sid", then you have an out-of-date trixie installation. Try upgrading it to the current trixie release and check to see if you have any <not available> packages that are actually from some (outdated) sid. Ask me about <testing/unstable>.

== Create the new testing
==   (a few days after the release!)
== Conventions:
==   - create a factoid for each release that judd will know about;
==     this one will be the main factoid and others will symlink to it

#forky/updates is <reply>Sorry "forky/updates" doesn't exist, just like it didn't exist for bookworm or trixie. The repository was renamed; ask me about <forky-security> instead.
#forky/security is <reply>see forky-security
forky security is <reply>see forky-security
forky-security is <reply>see testing-security
forky-proposed-updates is <reply> see testing-proposed-updates
forky-updates is <reply> forky-updates is not used while forky is the testing release. Once stable, it will provide updates to some packages (from <proposed-updates>) prior to a <point release>. Not to be confused with <forky-security> which is for <security> updates (and also not normally used for 'testing'!).
forky-debug is <reply>The "forky-debug" archive contains the automatically generated packages with debugging symbols for packages for binary packages in the forky release. Ask me about <dbgsym>.
forky-backports is <reply>see testing-backports
forky backports is <reply>see forky-backports

forky/sid mix is <reply>see tum
forky/sid is <reply>see testing/unstable
why forky/sid is <reply>see testing/unstable

# TODO replace with deb822?? no forky sources.list is <reply>A suitable /etc/apt/sources.list for "forky" has three lines: "deb https://deb.debian.org/debian/ forky main" "deb https://deb.debian.org/debian-security forky-security main" "deb https://deb.debian.org/debian/ forky-updates main".  Note that trixie does not yet have security support and is a <moving target>. See <deb-src> <contrib> <non-free> <forky-updates> and "man sources.list"."

!!no forky is <reply>The release following Debian 13 "Trixie" will be Debian 14 "Forky", https://lists.debian.org/debian-devel-announce/2022/10/msg00004.html .  Forky is the googly eyed, pipe-cleaner-handed spork from Toy Story 4 https://en.wikipedia.org/wiki/Forky .  Remember that straight after a stable release, all sorts of mess suddenly lands in "testing" and it is best avoided if you don't like debugging things.
install forky is <reply>see install testing

trixie->forky is <reply>Given trixie has only just released, it is highly recommended that if you don't know enough about Debian to already know how to do this on your own, that you don't even try. The Debian 'testing' release is really messy straight after the release.

!!forky pool is <reply> See <forky pool 1> for bets placed on when forky will release.  To add one, ask me about <forky bet>.
!!forky bet is <reply> To add a bet to the <forky pool>, /msg dpkg forky pool 1 =~ s/!/! yournick=yyyy-mm-dd/ and when "forky pool 1" is full, create "forky pool 2" and update this factoid.
!!forky pool 1 is <reply>! jëlly=2027-09-01


== Additional bits
!!no trixie is <reply>Trixie is the codename for the current <stable> release, Debian 13, released 2025-08-09. Trixie is the dinosaur in Toy Story 3, a blue Triceratops owned by Bonnie; see https://wiki.debian.org/DebianTrixie . Ask me about <install trixie>, <release notes>, <bookworm->trixie>.

!!no trixie installation guide is <reply> The Installation Guide for Debian 13 "Trixie" can be found at https://www.debian.org/releases/trixie/installmanual . See also <errata> and <trixie release notes>.

!!no trixie sources.list is <reply>A suitable /etc/apt/sources.list for "Trixie" has three lines: "deb https://deb.debian.org/debian trixie main" "deb https://deb.debian.org/debian-security trixie-security main" "deb https://deb.debian.org/debian/ trixie-updates main".  See <deb-src> <contrib> <non-free> <trixie-updates> and "man 5 sources.list".

!!updates =~ s/<bookworm-updates>/<trixie-updates>/
!!updates =~ s/<bullseye-updates>/<bookworm-updates>/

errata trixie is <reply>Last minute notes regarding Debian 13 ("Trixie") are listed at https://www.debian.org/releases/trixie/errata .  Known problems in the installer are listed at https://www.debian.org/releases/trixie/debian-installer/#errata

trixie errata is <reply>see errata trixie

!!no bookworm->trixie is <reply>Do read (at least) the upgrading chapter of <release notes> https://deb.li/v8Rv . TL;DR: In /etc/apt/sources.list change "bookworm" to "trixie", remove stable-specific lines like bookworm-backports. apt update && apt upgrade --no-new-pkgs && apt full-upgrade. 3rd party repos like <dmo> cause problems with upgrades.

trixie installer is <reply> see install trixie

no trixie-updates is <reply>trixie-updates is a suite providing updates to solitme packages (from <proposed-updates>) prior to a <point release>. The updates may be important bug fixes or low priority security fixes. All packages from trixie-updates will be included in point releases. https://wiki.debian.org/StableUpdates . Not to be confused with <trixie-security> which is for <security> updates.

no trixie-proposed-updates is <reply> see stable-proposed-updates

#no bookworm/updates is <reply> There is no "bookworm/updates" repository for security updates. To reduce confusion with <bookworm-updates> (which is for other bug fixes), security updates are distributed via the <bookworm-security> repository "deb http://deb.debian.org/debian-security bookworm-security main". Note that you may also need to adjust your Default-Release and pinning settings for apt.

no trixie-security is <reply>On Debian 13 "trixie" systems, there are two repositories that you should have in your sources.list aside from your main mirror. You should have an entry for "trixie-security" which is <security> updates (and also "trixie-updates" which is for <stable-updates>. See also <sources.list>. Note that you may also need to adjust your Default-Release and pinning settings for apt.

no release history is <reply>Named after "Toy Story" characters. Buzz 1.1 1996-03-14, Rex 1.2 1996-10-28, Bo 1.3 1997-05-01, Hamm 2.0 1998-07-24, Slink 2.1 1999-03-09, Potato 2.2 2000-08-15, Woody 3.0 2002-07-19, Sarge 3.1 2005-06-06, Etch 4.0 2007-04-08, Lenny 5.0 2009-02-14, Squeeze 6.0 2011-02-06, Wheezy 7 2013-05-04, Jessie 8 2015-04-25, Stretch 9 2017-06-17, Buster 10 2019-07-06, Bullseye 11 2021-08-14, Bookworm 12 2023-06-10. Trixie 13 2025-08-09, Forky! https://deb.li/ilB4R

no release is <reply>Debian 12 "Bookworm" was released on 2023-06-10. It is now considered "stable". Ask me about <install debian>, <bullseye->bookworm> to upgrade from Debian 11 "Bullseye". See https://www.debian.org/releases/ or <release history> for other releases. For updates from the Debian Release Team, see https://release.debian.org/

latest =~ s/'stretch' (9), 'buster' (10), 'bullseye' (11), 'bookworm' (testing), 'sid' (unstable)./'buster' (10), 'bullseye' (11), 'bookworm' (12), 'trixie' (testing), 'sid' (unstable)./

codenames =~ s/and sid/bullseye (12) and sid/

no when will bookworm release is <reply>IT'S OUT!  https://www.debian.org/News/2023/20230610

when will trixie release is <reply>REALLY!!!1!?one! bookworm only just came out and we need to catch our breath first!

no bookworm bet is <reply> see bookworm pool
no bookworm pool is <reply>The pool about when <bullseye> would release was won by Khepra (scorpion2185 is disqualified yet again, this time for betting after the date was announced!). Last place, yet again, was jélly… clearly aiming for the "most improved" award again. Ask me about <bookworm pool 1> to see the bets placed.  See also <trixie pool>.

no oldstable is <reply>OldStable the previous stable version of Debian, as long as it is still supported by the security team. Debian 11 "Bullseye" is oldstable.  It is recommended to upgrade your systems to the current stable release, ask me about <oldstable->stable>. http://wiki.debian.org/DebianOldStable or see <lifespan> <lts>.

bookworm-lts is <reply>It is expected that extended security support for Debian 12 "Bookworm" will be offered by the <LTS> project after the Debian Security Team ceases supporting bookworm in mid 2026, lasting until mid 2028. See https://wiki.debian.org/LTS for more information.


forget oldoldstable security
rename 'oldstable security' 'oldoldstable security'
oldstable security is <reply> see buster security

bobbitt =~ s/Bullseye/Bookworm/

no point release is <reply>Point releases are updates to <stable> and <oldstable>, fixing security & grave bugs. If you track security updates regularly (as you should!) there will often be no updates for you in a point release. Upgrade by referencing a Debian <mirror> in /etc/apt/sources.list, then "apt update && apt full-upgrade". See <10.13> <11.14> (None for bookworm yet). https://wiki.debian.org/DebianReleases/PointReleases.


== TODO
non-free-firmware
firmware images



firmware images bookworm is <reply> see firmware images

installer firmware bookworm is <reply>Debian-Installer is able to load  additional <firmware>, by including it within installation media or supplying on removable media (e.g. USB stick, floppy). See https://www.debian.org/releases/bookworm/amd64/ch06s04 . To include firmware within Debian <netboot> images, see https://wiki.debian.org/DebianInstaller/NetbootFirmware . See also <firmware images>.



=========================================================================
== Notes for whomever makes use of this pad to make changes:

    Don't just copy and paste in large slabs of "forget" or "no" commands -- dpkg will end up ignoring you

    You are limited to 4 or 5 "forget" per day per hostmask -- you can do some on libera.chat and some on oftc. Exceeding this gets you ignored by dpkg for several days. When dpkg says "Stop abusing forget" it means it.

    There is an unknown limit on queries to dpkg in general and exceeding that results in "Too many queries from you, ignoring for 5 minutes." Batch the "rename"s and "no"s into smaller chunks so even if you get ignored, you easily know which ones weren't processed yet.

    Mark the commands that have been applied with #

    If you think of other factoids that need updating, please add them to this document around as a starting point for the Bookworm release editing :)

    A few days after release, check the website for recently changed factoids that have broken xrefs
    	https://ircbots.debian.net/factoids/stats.php?q=recently-changed