apt-utils.sh: get base-files package version from GHA

[amazingfate]

Description

I have written a python script running in Github workflow: https://github.com/amazingfate/deb-files-parser, which will generate all versions of base-files from debian and ubuntu in a json file: https://github.com/amazingfate/deb-files-parser/blob/master/base-files.json, and now we can get rid of the unstable packages.debian.org or packages.ubuntu.com.
If this change is fine, we can move the repo amazingfate/deb-files-parser to armbian.

Deprecating: #7286

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

• ./compile.sh BOARD=rock-5b BRANCH=vendor BUILD_MINIMAL=yes DEB_COMPRESS=xz DOWNLOAD_MIRROR=china KERNEL_CONFIGURE=no RELEASE=jammy GITHUB_MIRROR=ghproxy KERNEL_GIT=shallow BUILD_DESKTOP=no ENABLE_EXTENSIONS=mesa-vpu DEBUG=yes. Build log:

--> (19) DEBUG: Calling artifact function [ artifact_armbian-base-files_prepare_version()  ]
--> (20) INFO: Found upstream base-files package filename [ base-files_12ubuntu4.7_arm64.deb ]
--> (20) DEBUG: Found package filename [ base-files_12ubuntu4.7_arm64.deb in url http://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports/pool/main/b/base-files/base-files_12ubuntu4.7_arm64.deb ]
--> (20) INFO: Found base-files upstream package version [ 12ubuntu4.7 ]
--> (20) DEBUG: Found package download url [ http://mirrors.tuna.tsinghua.edu.cn/ubuntu-ports/pool/main/b/base-files/base-files_12ubuntu4.7_arm64.deb ]

Checklist:

Please delete options that are not relevant.

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

[ColorfulRhino]

Cool!

If this change is fine, we can move the repo amazingfate/deb-files-parser to armbian.

Why not include this into the armbian/build repo instead of using a separate repo just for the script? Build could just run the parser on the fly and put the resulting json in the cache directory, what do you think?

[amazingfate]

Cool!

If this change is fine, we can move the repo amazingfate/deb-files-parser to armbian.

Why not include this into the armbian/build repo instead of using a separate repo just for the script? Build could just run the parser on the fly and put the resulting json in the cache directory, what do you think?

The parser script is still querying pkg info from pacakges.debian.org or packages.ubuntu.com, if the site is down, build would still fall if there is no local cache.

[rpardini]

Excellent, @amazingfate -- super thanks. A few nits:

I've reviewed https://github.com/amazingfate/deb-files-parser -- looks fine, only suggestions there would be

1. use pretty-printed JSON for the output file, so when changes do happen, we can get better diffs.
2. when moving that repo to the armbian org, one will possibly need to be explicit about the permissions: (GITHUB_TOKEN behaves slightly weird/different when used in a personal repo or a org repo, and the git push will most probably fail)

And to say the truth I can't follow where https://github.armbian.com/base-files.json is actually coming from in the end -- is it in ghpages in the armbian org? If so, where is the actual repo and GHA workflow that is publishing it there?

[igorpecovnik]

And to say the truth I can't follow where https://github.armbian.com/base-files.json is actually coming from in the end -- is it in ghpages in the armbian org? If so, where is the actual repo and GHA workflow that is publishing it there?

1. https://github.com/armbian/armbian.github.io/blob/main/.github/workflows/generate-base-files-info-json.yml generates JSON and puts it into "data" repository
2. this https://github.com/armbian/armbian.github.io/blob/main/.github/workflows/directory-listing.yml checks if something is pushed to data and generate website with index.

I expanded this to put here some other JSON files that are in use.

And, top level org pages has this (sub)domain: (normally armbian.github.io)

[rpardini]

1. armbian/armbian.github.io@main/.github/workflows/generate-base-files-info-json.yml generates JSON and puts it into "data" repository
2. this armbian/armbian.github.io@main/.github/workflows/directory-listing.yml checks if something is pushed to data and generate website with index.

Nice this makes sense. I will send PRs down there in the future, thanks!

[rpardini]

I've cherry-picked, built a large train, published to repo, everything seems to work fine.