don't want to hijack your thread about Forky, but technically it's about UPDATING and tracking Forky/Testing Repos.  So let me chime in...   In recent years I have switched from Ubuntu (Lubuntu 16.04) to Debian (Bullseye) base...primarily because Debian support window is approximately similar to the Ubuntu support window; with the scales being tipped in Debian's favor from all the users on Debian forums who "sweared & declared" they have been upgrading Debian IN PLACE for years....numerous cycles....with no issues whatsoever.  If it was a few folks, I'd probably discount those stories as outliers, or bravado....but it's not a few....it was a LOT.  They can't all be lying, or exaggerating.  I have upgraded Ubuntu in place several times, but it has ALWAYS resulted in issues.  Sometimes right away...sometimes in coming weeks.  I learned to wait until the first "point release" of Ubuntu, but same results.  I learned it was always best to just re-install Ubuntu fresh.  A PITA, but less work than troubleshooting weird artefacts from upgrades....so I made the move to Debian.    I built a Debian Bullseye VM as a proof of concept and made sure I could install the applications and customizations in Debian that I prefer.  All was good, until Bookworm was on the horizon.  All I had to do was wait another month or so, and I'd get extra support from Bookworm than I would from Bullseye.  Once released, I rebuilt based on Bookworm, which is where I sit today.   But I still had my Bullseye VM.  Inspired by Ray's updates, I figured it was time to give Debian full-upgrades a full-go, LOL!  Made sure Bullseye was fully up-to-date, then switched my sources.list to reflect Bookworm; updated my repos; made a partial upgrade of the underlying OS with no issues; then a full upgrade of all installed packages; purged & autoremoved for cleanup; then re-booted and waited for the results.  NO ISSUES whatsoever!  I tinkered around for a bit and many parts are substantially similar in appearance (i actually kind of like that....suggests that customizations might "stick" and not get overwritten?!).  Verified the new version with lsb_release -a and checked on kernel with uname -a and everything indicated "bookworm".  Feeling pretty good about that outcome, I figured "let's see if we can wreck the system with another update/upgrade to Trixie?!"   Repeated the process, and now my Debian LXQT is on Trixie repos, with no problems observed so far.  I'll continue to monitor Trixie in my VM and see how it performs when some "point releases" hit the repos, but so far, count me impressed and PLEASED.  Updating/upgrading Debian was easy-peasy and seems to be without issue, AS IT SHOULD BE!  (knock on wood)  If it continues on this track, this will be the easiest and most trouble-free update I've ever done.  I can live with this...hell, I'm HAPPY about it!  As far as I'm concerned, Debian for the win?!