[Idea] Softwareinventory support for opkg/apk

[Megachip]

Your idea

Now, where It is possible to do an remote inventory via ssh, it would be cool if glpi-agent support opkg and apk.

[g-bougard]

Hi @Megachip

it should not be difficult to implement dedicated modules under: lib/GLPI/Agent/Task/Inventory/Generic/Softwares

Can you provide for each each command output showing how this could be handled ?
For each package, we will have typically to provide:

NAME
ARCH
VERSION
FILESIZE
COMMENTS
FROM will be "opkg" or "apk"
SYSTEM_CATEGORY
INSTALLDATE
PUBLISHER

So we need a command providing datas easy to parse providing the required one. I think NAME, ARCH and VERSION at least are mandatory.

[Megachip]

I'm using opkg list-installed | while read pkg x; do opkg info $pkg; done mini-script to output all data. Can you share full outputs telling which device is behind so I can use them in unittest ? Or if you find not working cases or special cases that can help, can you share at least them (a full output would be better anyway) ?

do you need all these Information? File Attached

For the full output, does the following work ? apk list | while read pkg; do apk info $pkg; apk info $pkg -v; done, if yes, can you share it ?

empty output.
[output.zip](https://github.com/user-attachments/files/19754361/output.zip) works
find both files attached.

Strange thing, alpine seems to have dpkg installed (whyever) ... I'll guess thats not the case for all distros, which are using apk ;)

[g-bougard]

I don't see any attached file.

About apk, sorry, I made a mistake in the syntax. Here is what I would like you test: apk list | while read pkg x; do apk info $pkg; apk info $pkg -v; done (a x was missing in while read pkg x;)

[Megachip]

I don't see any attached file.

Strange. Will attach it again, if its noch working, I'll send it on another way.
Did you tried to copy the URL? ;)

About apk, sorry, I made a mistake in the syntax. Here is what I would like you test: apk list | while read pkg x; do apk info $pkg; apk info $pkg -v; done (a x was missing in while read pkg x;)

Still -q is required (but seems that information also got lost)

apk list -q | while read pkg x; do apk info $pkg; apk info $pkg -v; done
apk list -q | while read pkg; do apk info $pkg; apk info $pkg -v; done
both working and producing the same output ... what's the usage of x? (

output.zip

[g-bougard]

Did you tried to copy the URL? ;)

Yes I tried, but it says "Not found". Try it. ;-)
This time it is there.

both working and producing the same output ... what's the usage of x? (

This is a shell syntax to parse lines. In the case of apk list, it means for the first line you provided before: pkg=acl-libs-2.3.2-r1 & x=x86_64 {acl} (LGPL-2.1-or-later AND GPL-2.0-or-later) [installed] (the rest of the line).
But so I understand apk info acl-libs-2.3.2-r1 is not understood by apk command. Does apk info acl-libs-2.3.2-r1.x86_64 work ?
Originally, I didn't use -q as the option is not documented, as I said before. My concern here is to use the most possible generic code. I just support apk list -q could just fail on another system if -q option is not supported.

[g-bougard]

Looking at apk output, I think the best command could be: apk list | while read pkg arch x; do echo $pkg $arch; name=$(echo $pkg| sed -e 's/-[0-9].*$//'); apk info $name -v; done
I should than extract version from "pkg" assuming version starts at the first number after an hyphen. Having arch is also useful and it seems only apk list gives it. apk info $pkg -v is easier to parse. But the question is now is sed command supported by the system (it should be as busybox is installed)... or do you know a better way to catch all required data (including version and arch) ?

Also did you try the Opkg module I gave before ?

[Megachip]

Also did you try the Opkg module I gave before ?

I did: glpi-agent --remote=ssh://xxx --logger=stderr --tasks remoteinventory -f --debug --debug --var=data/
But seems not filling the software part. Is there a way to just running the remote software inventory?
Cause Inventory take some time: Remote inventory task run in 20360 seconds

Looking at apk output, I think the best command could be: apk list | while read pkg arch x; do echo $pkg $arch; name=$(echo $pkg| sed -e 's/-[0-9].*$//'); apk info $name -v; done

apk.zip

[Megachip]

Looking at apk output, I think the best command could be: apk list | while read pkg arch x; do echo $pkg $arch; name=$(echo $pkg| sed -e 's/-[0-9].*$//'); apk info $name -v; done

we should use apk list --installed ^^ Also it seems like output (of v3) differ a bit.
apk.zip

[g-bougard]

I checked quickly that new output, I see few weird things:

• for the first, I see:

apk-mbedtls-3.0.0_pre20250208-r2 mips_24kc
apk-mbedtls: apk package manager (mbedtls)
apk-mbedtls: https://gitlab.alpinelinux.org/alpine/apk-tools.git
apk-mbedtls: 212 KiB
apk-mbedtls: apk package manager (mbedtls)
apk-mbedtls: https://gitlab.alpinelinux.org/alpine/apk-tools.git
apk-mbedtls: 212 KiB

Here there's 2 times the same data after the line with version and arch and this the same for most of the other packages.
Is there really 2 packages or do you run 2 times the command where you should not as I only run "apk info" one time in my mini-script ?

• for wpa-supplicant, this is different, I see the duplicated data, but also many other packages... So does apk list --installed wpa-supplicant really report that output ? If yes, can you explain what is really installed. Actually, I still don't see how to proceed with apk.

wpa-supplicant-2025.02.09~c8c7d56a-r1 mips_24kc
wpa-supplicant: WPA Supplicant (built-in full)
wpa-supplicant: https://w1.fi/wpa_supplicant/
wpa-supplicant: 800 KiB
wpa-supplicant: WPA Supplicant (built-in full)
wpa-supplicant: https://w1.fi/wpa_supplicant/
wpa-supplicant: 800 KiB
wpa-supplicant-basic: WPA Supplicant (11r, 11w)
wpa-supplicant-basic: https://w1.fi/wpa_supplicant/
wpa-supplicant-basic: 544 KiB
wpa-supplicant-mbedtls: WPA Supplicant (mbedTLS full)
wpa-supplicant-mbedtls: https://w1.fi/wpa_supplicant/
wpa-supplicant-mbedtls: 1124 KiB
wpa-supplicant-mesh-mbedtls: WPA Supplicant (mbedTLS, 11s, SAE)
wpa-supplicant-mesh-mbedtls: https://w1.fi/wpa_supplicant/
wpa-supplicant-mesh-mbedtls: 1060 KiB
wpa-supplicant-mesh-openssl: WPA Supplicant (OpenSSL, 11s, SAE)
wpa-supplicant-mesh-openssl: https://w1.fi/wpa_supplicant/
wpa-supplicant-mesh-openssl: 1124 KiB
wpa-supplicant-mesh-wolfssl: WPA Supplicant (wolfSSL, 11s, SAE)
wpa-supplicant-mesh-wolfssl: https://w1.fi/wpa_supplicant/
wpa-supplicant-mesh-wolfssl: 1124 KiB
wpa-supplicant-mini: WPA Supplicant (minimal)
wpa-supplicant-mini: https://w1.fi/wpa_supplicant/
wpa-supplicant-mini: 480 KiB
wpa-supplicant-openssl: WPA Supplicant (OpenSSL full)
wpa-supplicant-openssl: https://w1.fi/wpa_supplicant/
wpa-supplicant-openssl: 1124 KiB
wpa-supplicant-p2p: WPA Supplicant (Wi-Fi P2P support)
wpa-supplicant-p2p: https://w1.fi/wpa_supplicant/
wpa-supplicant-p2p: 1188 KiB
wpa-supplicant-wolfssl: WPA Supplicant (wolfSSL full)
wpa-supplicant-wolfssl: https://w1.fi/wpa_supplicant/
wpa-supplicant-wolfssl: 1124 KiB
wpad: This package contains a full featured IEEE 802.1x/WPA/EAP/RADIUS Authenticator and Supplicant
wpad: https://w1.fi/
wpad: 1440 KiB
wpad-basic: This package contains a basic IEEE 802.1x/WPA Authenticator and Supplicant with WPA-PSK, 802.11r and 802.11w support.
wpad-basic: https://w1.fi/
wpad-basic: 892 KiB
wpad-basic-mbedtls: This package contains a basic IEEE 802.1x/WPA Authenticator and Supplicant with WPA-PSK, SAE (WPA3-Personal), 802.11r and 802.11w support.
wpad-basic-mbedtls: https://w1.fi/
wpad-basic-mbedtls: 960 KiB
wpad-basic-openssl: This package contains a basic IEEE 802.1x/WPA Authenticator and Supplicant with WPA-PSK, SAE (WPA3-Personal), 802.11r and 802.11w support.
wpad-basic-openssl: https://w1.fi/
wpad-basic-openssl: 960 KiB
wpad-basic-wolfssl: This package contains a basic IEEE 802.1x/WPA Authenticator and Supplicant with WPA-PSK, SAE (WPA3-Personal), 802.11r and 802.11w support.
wpad-basic-wolfssl: https://w1.fi/
wpad-basic-wolfssl: 960 KiB
wpad-mbedtls: This package contains a full featured IEEE 802.1x/WPA/EAP/RADIUS Authenticator and Supplicant
wpad-mbedtls: https://w1.fi/
wpad-mbedtls: 1440 KiB
wpad-mesh-mbedtls: This package contains a minimal IEEE 802.1x/WPA Authenticator and Supplicant (with 802.11s mesh and SAE support).
wpad-mesh-mbedtls: https://w1.fi/
wpad-mesh-mbedtls: 1440 KiB
wpad-mesh-openssl: This package contains a minimal IEEE 802.1x/WPA Authenticator and Supplicant (with 802.11s mesh and SAE support).
wpad-mesh-openssl: https://w1.fi/
wpad-mesh-openssl: 1440 KiB
wpad-mesh-wolfssl: This package contains a minimal IEEE 802.1x/WPA Authenticator and Supplicant (with 802.11s mesh and SAE support).
wpad-mesh-wolfssl: https://w1.fi/
wpad-mesh-wolfssl: 1440 KiB
wpad-mini: This package contains a minimal IEEE 802.1x/WPA Authenticator and Supplicant (WPA-PSK only).
wpad-mini: https://w1.fi/
wpad-mini: 828 KiB
wpad-openssl: This package contains a full featured IEEE 802.1x/WPA/EAP/RADIUS Authenticator and Supplicant
wpad-openssl: https://w1.fi/
wpad-openssl: 1504 KiB
wpad-wolfssl: This package contains a full featured IEEE 802.1x/WPA/EAP/RADIUS Authenticator and Supplicant
wpad-wolfssl: https://w1.fi/
wpad-wolfssl: 1504 KiB

[Megachip]

Here there's 2 times the same data after the line with version and arch and this the same for most of the other packages.
Is there really 2 packages or do you run 2 times the command where you should not as I only run "apk info" one time in my mini-script ?

I used your command without --installed ... this seems to list the package twice (the installed one and the available one - see below)

for wpa-supplicant, this is different, I see the duplicated data, but also many other packages... So does apk list --installed wpa-supplicant really report that output ? If yes, can you explain what is really installed. Actually, I still don't see how to proceed with apk.

apk list --installed wpa-supplicant
wpa-supplicant-2025.02.09~c8c7d56a-r1 mips_24kc {feeds/base/package/network/services/hostapd} (BSD-3-Clause) [installed]

apk list apk*
apk-mbedtls-3.0.0_pre20250208-r2 mips_24kc {feeds/base/package/system/apk} (GPL-2.0-only) [installed]
apk-mbedtls-3.0.0_pre20250208-r2 mips_24kc {feeds/base/package/system/apk} (GPL-2.0-only)
apk-openssl-3.0.0_pre20250208-r2 mips_24kc {feeds/base/package/system/apk} (GPL-2.0-only)

apk list apk*
apk-tools-2.14.6-r3 x86_64 {apk-tools} (GPL-2.0-only) [installed]

[g-bougard]

Hi @Megachip

sorry but something seems wrong in your output or is not coherent with what you're saying. Also I don't understand why you now share output of apk*, I mean I didn't talk about apk package and why with a * ? It makes no sens to use such globbing in inventory context.

Your output of apk list --installed wpa-supplicant is not coherent with what I saw in your file.

If --installed option also show "available" packages... I don't even understand that option.

[Megachip]

sorry but something seems wrong in your output or is not coherent with what you're saying. Also I don't understand why you now share output of apk*, I mean I didn't talk about apk package and why with a * ? It makes no sens to use such globbing in inventory context.

It was just an example to show the different outputs (and behavior) between apk version 2 and 3. I just choosen apk that you see, which apk is installed. A complete output is to long and make no sense here.

So, to sum up: Version 2 list packages once (with an [installed] behind), version 3 list it twice, if it is installed. If not, it is just listed once.

[Megachip]

Your output of apk list --installed wpa-supplicant is not coherent with what I saw in your file.

Could you point out the file? I just run the commands, you requested (which mostly where without --installed , I just pointed out, that it would make more sense in my option to just go through installed packages and not through all available (cause even without inventory tooks half a day sometimes ;)

hope this clarify the situation a bit

[g-bougard]

About apk list --installed wpa-supplicant, I shared the concerned part from your last apk.zip archive, see my previous comment.

You're now speaking about 2 different apk versions with different outputs... Sorry, but you didn't tell that, so I don't see how to implement safely apk support with vague information.

Finally, if it can take half a day to remotely inventory softwares... I don't think this is a good idea to implement it.

Then can I leave you the task to produce a script which generates a coherent software list with apk ? If you need to change the output parsing depending on apk version, try to handle it check apk version.