Dietpi-Software installs microblog.pub instead of build-essential package
Creating a bug report/issue
- [x] I have searched the existing open and closed issues
Required Information
- DietPi version |
cat /boot/dietpi/.version
root@DietPi:~# cat /boot/dietpi/.version
G_DIETPI_VERSION_CORE=9
G_DIETPI_VERSION_SUB=4
G_DIETPI_VERSION_RC=2
G_GITBRANCH='master'
G_GITOWNER='MichaIng'
G_LIVE_PATCH_STATUS[0]='not applicable'
- Distro version |
echo $G_DISTRO_NAME $G_RASPBIAN
bookworm 0
- Kernel version |
uname -a
Linux DietPi 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux
- SBC model |
echo $G_HW_MODEL_NAMEor (EG: RPi3)
RPi 4 Model B (aarch64)
Additional Information (if applicable)
- Software title:
build-essential - Was the software title installed freshly or updated/migrated? Fresh?
- Can this issue be replicated on a fresh installation of DietPi? Yes
Steps to reproduce
- Install DietPi on RPi4 Model B
- Try to install
build-essentialusingdietpi-softwarecommand:dietpi-software install 16
Expected behaviour
- package
build-essentialshould be installed
Actual behaviour
- package
microblog.pubis getting installed instead ofbuild-essential
With DietPi v8.15, build-essential has been removed from dietpi-software, and later the software ID has been reused with microblog.pub: https://dietpi.com/docs/releases/v8_15/#removed-software
Just install it via APT:
apt install build-essential
Or better install those compilers/tools/headers you really need for whatever you want to compile. Above package contains e.g. dpkg-dev for compiling DEB packages, which is rarely needed.
Is the software ID 16 still wrong referenced somewhere?
Appreciate the quick response! I was actually following a guide from 2023 to install RetroPie on my DietPi installation. And it so happened I could not find ID 16 in TUI for dietpi-software, so I proceeded trying to install using CLI method. It's not that the ID 16 for build-essential is referenced in DietPi, but it's still being referenced on the intewebs.
I would not recommend re-using a removed / depricated software ID for another software then. It's confusing for new users who follow an old guide where some parts still apply. If it's removed, the ID should be added to a blacklist and the user should get a warning when trying to use it. Just my 2 cents
ID 16 is first referenced her: https://github.com/MichaIng/DietPi/blob/b13c6731a1d01bb3d9179f26da1cd02dea1a9b28/.meta/dietpi-survey_report#L222 Then removed from the bash array here: https://github.com/MichaIng/DietPi/blob/b13c6731a1d01bb3d9179f26da1cd02dea1a9b28/.meta/dietpi-survey_report#L657 and ID 16 is re-used for another software here: https://github.com/MichaIng/DietPi/blob/b13c6731a1d01bb3d9179f26da1cd02dea1a9b28/.meta/dietpi-survey_report#L664
We'll think about it. Makes sense at least for libraries, build tools/stacks and such.
The survey report script needs to define per DietPi version so that uploads from older DietPi versions are interpreted correctly.
There is btw also dietpi-software list to see which software ID is what, and: https://github.com/MichaIng/DietPi/wiki/DietPi-Software-list
@MichaIng WHy was this closed? In master i still see ID 16 equals to microblog.pub https://github.com/MichaIng/DietPi/blob/26ab3eb43515f326eb19f84a91886723326fefce/.meta/dietpi-survey_report#L452
Of course we won't change the microblog.pub software ID now, which would cause the exact issue you mentioned, but for a more recent and still available, hence more relevant software title. The only consideration is to not reuse software IDs from now on, at least for anything which can be a dependency, like libraries, frameworks, toolchains or so.