Hi Michael.
Yes, Trixie is now installed on the Roon Server. I used the script.
I use other services (not many) and they all work just fine.
Torben
PS: Netdata will not work
Well they do need testers, so well done to you.
I think I am already running on the 6.12 kernel for the last six months or so, but I will probably (maybe) be lazy and wait for the DietPi full update for a change.
But I keep looking at new mini PCs to replace my Nuc 10i5, not that I really need to in truth 
Funnily enough I actually turned off Netdata the other day as I was not happy with some of its information collection, compared to what ps and top were telling me. It seemed to be showing the systemd services using much more memory than they actually were
Not sure what you mean by that? The full image? Or? The full image has been released. But I prefer the script version.
Blog post:
Torben
Sorry I meant the DietPi dietpi-update version.
I saw and read a bit about trixie being released (and some minor issues with some software) but it has not come to any of my other devices yet, assuming due to some software incompatibility.
I have broken too many Linux distros over the last 30 years by forcing updates (and installing incompatible software) that were not meant to be installed on them 
1 Like
As I have commented before, on anything but the simplest of systems (of which my Roon Server is not one), I am generally governed by two mantraās:
- KISS (Keep It Simple, St***d)
- If it aināt broke, donāt fix it.
I shall not be updating my Roon Server machine to Trixie for some time. Bookworm will continue to get support for a year or two yet and so, for me, there is no imperative to upgrade. Iām not one of those that has to be on the bleeding edge all of the time.
Yes, I updated my RPi endpoint Dietpi installations to Trixie but this was because they are extremely easy to re-image back to Bookworm if necessary having just 4 or so dietpi packages to install and no custom configuration and it gives me some experience of the upgrade process and running Trixie so I know what to expect later when I do eventually upgrade the more complex and the more critical Roon Server computer. Even then, I did one RPi device at a time and confirmed all was as it should be before moving on to the next one. Note: All four of my RPis are RPi 4B devices - 1 with 8G DRAM, and 3 with 2GB DRAM.
2 Likes
@Wade_Oram @Michael_Harris - The SQ is better with Trixie LOL LOL 
Just kidding
So far no problems with Trixie. Letās hope it stays that way 
Torben
2 Likes
You get bonus points for saying it out loud as well 
2 Likes
Please donāt go there! Some things are beyond a joke.
Sometimes, you just have to instill an idea and others will take it up and run with it as a fact and before you know it, there is a whole community of believers who will argue the case at the slightest opportunity.
2 Likes
Wade this is not a fun free area, and while I understand Torben was clearly joking and marked it up as such.
People will believe what they want regardless of what we write, but that does not preclude some of us enjoying a bit of humor while we play with our hobby
1 Like
@Michael_Harris I think you took me more seriously than I intended.
My post above was also firmly tongue in cheek - although as with much humour, there is always an element of truth.
1 Like
Ah sorry @Wade_Oram your tongue wasnāt far enough through your cheek 
Humour is such a Trixie thing to get right 
1 Like
oh man did you have to say that 
1 Like
1 Like
If you are using early-access builds there are some nice improvements in the upcomming v9.17 version:
- DietPi-Software | Roon Server: A new dialogue and related dietpi.txt setting
SOFTWARE_ROONSERVER_EARLYACCESSallows to select and switch between stable and early access builds. Information about the Roon Early Access Program can be found here: https://help.roonlabs.com/portal/en/kb/articles/roon-early-access-program. Many thanks to @Wade_Oram for suggesting this enhancement: Roon Server Early Access on DietPi X86
Torben
2 Likes
You give me more credit than I deserve.
I didnāt suggest the change. That was @MichaIng.
I only asked the question that highlighted the issue.
2 Likes
Indeed the wording was not accurate 
: changelog: accuracy :) Ā· MichaIng/DietPi@f21710d Ā· GitHub
I tend to take good questions as ideas/suggestions, sadly do not always find the time to implement them any time soon. But that we walked through the steps to switch back and forth between early access and stable builds helped to make this implementation quick and simple.
2 Likes
Do you think it is worth to keep Netdata support by switching to their own repository?
It has a closed source web UI and according to Debian a lot of features moved into their cloud service, which requires an account, with limited free plan (max 5 nodes). Has anyone tried this yet?
I certainly find Netdata quite useful on Bookworm but I have not yet migrated to Trixie so I have had no need to try the Netdata repository version.
I am not keen on the idea needing a subscription to a cloud service. I canāt see the benefit to me of such a move. However, a 5 node limit would not be major concern to me at present.
The problem for me, is that I have, to date, found no alternative to Netdata for monitoring and graphing aspects of the system over extended periods of time. The recent feedback that I raised about an apparent memery leak associated with the scheduled Roon database backups was a case in point:
Without Netdata (or some equivalent tool), I cound not have noticed the correlation between the time of the Roon backup and the increase in memory utilisation.
So. Back to your question. For me, I guess it depends on the extent that you need to modify the install script to fit the Dietpi way of doing things. If simply running the Netdata supplied install script results in a functional installation with, for example, the ability to ensure that log data and the Netdata database are written to suitable locations, then I guess that there is no real need for explicit support in dietpi-software.