Well, for what it's worth, Backports and Testing both contain Orca 3.43.11 with the only difference in version number being Backports has an extra string at the end to indicate it is a Backport. Also, Debian Unstable currently contains the same version of Orca as Testing. For the moment, Bookworm points at Debian Testing and the only difference between putting bookworm in your sources versus Testing is that Bookworm will switch to Stable automatically upon release. Testing versus Backports is mostly a question of upgrading everything versus only upgrading key components, and ingeneral, I believe the biggest difference a backport build and a testing build in most cases is that the backport will be built against stable libaries that aren't backported. That said, short of building from Git, if you want the newest Orca Debian offers, you want Debian Experimental, which currently has a .44.0 package of Orca. And while the packages in Experimental are often too bleeding edge even for Debian Unstable, it's arguably less risky to add Experimental to your sources.list than Unstable as while Unstable is a full distro and packages will automatically be upgrade to to their unstable versions by a apt upgrade unless you've set a default release in your apt settings to prevent it, Experimental only contains a small fraction of the packages offered by Debian and upgrades to an experimental version are always manual(Aptitude won't even mark packages with an experimental upgrade as upgradeable, you have to manually check a package's list of available versions to know when an experimental upgrade is available)... that said, I did test the Debian Experimental build of Orca earlier this week and it broke Seamonkey's accessibility completely... another thing that makes Experimental less risky compared to Unstable is that I could downgrade to the version I was using previously pretty much as soon as I realized there was a serious issue... A broken version manages to slip into unstable or testing, you have little choice but downgrade to a version likely older than the last working version. Sorry I can't really give you a definite answer, but there really isn't one and hopefully this helps you make an informed decision. For what it's worth, While I've only recently switched to Vanilla Debian after about a decade of using Knoppix, I've been sourcing >95% of my packages from Debian Testing with occasional dips into unstable and, in the last year, experimental for over a decade with little issue(though, part of what pushed me to switching to Vanilla Debian was an issue where upgrading to the Testing version of libc-bin, a core library nearly everything depends on broke my Knoppix install forcing a prolonged stint sourcing stuff from Debian Stable). On 5/26/23, Linux for blind general discussion <blinux-list@xxxxxxxxxx> wrote: > So, had to set up a Debian laptop for someone, and the first question I > got asked is ....yes but how do I update all the accessible stuf? > > So here's my question. What is the most accepted way to do this, is it > by backports, or switching to testing? It's a Debian 11 system, and by > default it ships with Gnome 3.38 and thus Orca 3.38. > > So, is there a preferred way to keep things up to date then? I've seen > some people online say use backports. I've seen others say oh, go with > testing, it hasn't ever let me down, and still others say oh, wait for > Bookworm, and yet more say oh switch your sources.list to Bookworm > > > So which is it? I'm not sure what the consensus is. > > > And related question, Is there an easy way to buil Orca from git? I know > about Una, so is it on there, if so it'd make my life a lot easier. Una > is, for those who aren't aware, like paru or yay for Debian. I didn't > know Debian had an AUR until I stumbled across Una. > > > Jace > _______________________________________________ > Blinux-list mailing list > Blinux-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/blinux-list > > _______________________________________________ Blinux-list mailing list Blinux-list@xxxxxxxxxx https://listman.redhat.com/mailman/listinfo/blinux-list