Old versions and recomendations

Have some feedback, questions, suggestions, or just fancy a chat? Pop it in here.
Post Reply
dzooky
Posts: 12
Joined: Wed Jun 20, 2018 10:58 pm

Old versions and recomendations

Post by dzooky »

Hi guys
I want to ask why there is still old version of software eg.
Certbot 0.10 and actual is 0.29 (asking because newest support certificates with wildcard)
Grafana 5.1.4 actual is 5.3.4
DP use https://dl.bintray.com/fg2it/deb and official is https://packagecloud.io/grafana/stable/debian/
Probably there is another old version of software.
It is because of stability or what?

It will be helpful to have information somewhere which version will be installed.

Then hint for ReadyMedia

Code: Select all

rm /mnt/dietpi_userdata/.MiniDLNA_Cache/* && systemctl restart minidlna
doesn't work because there are some directories
so you can update manual to

Code: Select all

rm -r /mnt/dietpi_userdata/.MiniDLNA_Cache/* && systemctl restart minidlna
it will be helpful for beginers
User avatar
MichaIng
Site Admin
Posts: 2323
Joined: Sat Nov 18, 2017 6:21 pm

Re: Old versions and recomendations

Post by MichaIng »

It depends on the type of install candidate:
- Much software we pull via APT from Debian repo, so it depends on the version there and Debian is known, that longer time after stable release the major software versions are somehow behind, but well tested and very stable in combination the the remaining Debian system. E.g. CertBot: https://packages.debian.org/de/stretch/certbot
- Some software we pull via their own APT repo or from Git archieve/download link, where always the most current version will be in place. So with these software, everything should be always up to date.
- Some software is only available via official download links, that contain a version string. In these cases we manually need to update the download link by times. Indeed there is a too long time delay until this is done and the install process with the new version is tested before release. Mostly due to lack of man power ;). You are welcome to open PRs to update and test those download links. Here is a list of affected software titles, although not up-to-date: https://github.com/Fourdee/DietPi/issues/1340
- For next DietPi release we will update more download links to always pick the most current packaged release from GitHub via https://api.github.com/repos/<ownser>/<repo>/releases[/latest], which is at least in some cases possible as alternative to the usual download links from release page.

Not all, but some software offer internal update mechanisms. Use them regularly, if available. They should not break anything with the DietPi setup. Of course regularly use G_AGUP && G_AGDUG (non-interactive apt update && apt full-upgrade) to keep all APT packages up-to-date, at least with the downstream versions ;).
Post Reply