How can I access individual packages that make up the images that are available for download e.g. at https://www.armbian.com/lenovo-x13s/ ? I see only "full image" downloads and no link to information on what was used to build these images. I poked around the dists named "bookworm something" on apt.armbian.com looking for the kernel used, but didn't find any obvious match (no 6.3 kernel version, no kernel that has "x13s" in the package name, ...).

 

Likewise, there is no x13s listed in https://github.com/armbian/build/tree/master/config/sources/families

From a quick look (I don't know about this device in particular) it seems like it supports UEFI and therefore generic ARM64 UEFI target applies.

https://github.com/armbian/build/blob/main/config/boards/thinkpad-x13s.wip

OK, thank you, please excuse my relative n00bness in armbian matters, but where do I find the .deb packages that make up the image? E.g. if I want to install the same kernel than this image on a Debian install, for that I need the .deb package. To see what is in there source-wise, I'd need e.g. the .dsc file and the files referred therein. If I want to see what version of userspace tool protection-domain-mapper it uses and/or install it, likewise I need to get the .deb file and the .dsc file.

 

I mean according to the documentation at https://docs.armbian.com/User-Guide_Getting-Started/#how-to-update-firmware-and-packages, after the image is installed, the way to upgrade to newer versions of everything (within a major release like bookworm or jammy, not across them) is a Debian-standard apt update and upgrade. So all this must be in some APT repository somewhere?

Edited August 9, 20233 yr by lmamane

42 minutes ago, lmamane said:

please excuse my relative n00bness in armbian matters, but where do I find the .deb packages that make up the image?

 

43 minutes ago, lmamane said:

if I want to install the same kernel than this image on a Debian install, for that I need the .deb package.

 

Image is not made by installing .deb package. You need to use https://github.com/armbian/build and you will receive no support. As build target is not supported. You should also find that in the documentation. Not just your rights.

 

46 minutes ago, lmamane said:

To see what is in there source-wise, I'd need e.g. the .dsc file and the files referred therein.

 

This world is not as simple and organised as x86 Debian world you must be coming from ... sources are on Git. We don't hide anything, just support is extremely limited.

 

49 minutes ago, lmamane said:

is a Debian-standard apt update and upgrade. So all this must be in some APT repository somewhere?

Next cycle perhaps.
https://docs.armbian.com/Process_Release-Model/#release-cycle

1 hour ago, Igor said:

Image is not made by installing .deb package.

I was under the impression that once installed, it is __upgraded__ by installing .deb packages, else how would "apt update && apt upgrade" do the upgrade? Or is that bit of the documentation only valid for released / supported / ... targets and not for this one?

55 minutes ago, lmamane said:

only valid for released / supported / ... targets and not for this one?

 

Exactly. You can get first hand information only if you will be investing your time to help us: https://www.armbian.com/participate/ If you will be asking from users perspective, "access denied" comes by default. We are not Lenovo employees or contractors.