tillkamppeter
commented
10 months ago Thank you very much for your work.
I will look through it and find solutions for foomatic-db and HPLIP.
HPLIP perhaps needs only deeper investigation of the GitLab repository from Debian which is the base for it. Note that HPLIP itself (upstream, at HP) has no public GIT repo and so the current Snap automation does not work directly with it. Also the HPLIP developers at HP do not deliver a high coding quality and do not accept the patches created by distro package maintainers and community. Therefore the distro packages have many patches (~80) and with this it is better to base the Snaps on the Debian package of HPLIP.
For foomatic-rip I actually did not have really a release policy (rolling release, version number = date) as it is no code, only data. I will now look into whether I can make it trigger the Snap automation with each commit or each day with has at least one commit. Probably I will add a GIT workflow to it which creates a tag on each day it gets a commit, so that this triggers Snap automation (and any other packager's or admin's upstream release observation system).
rudra-iitm
Integrated the GitHub workflow auto-update.yml located in .github/workflows/ from the https://github.com/ubuntu/desktop-snaps repository. This leverages the GitHub action for automating updates to the snapcraft.yaml file.
Modified the snapcraft.yaml file to enable the update automation for the individual parts.
It's currently not feasible to automate updates for foomatic-db releases due to the absence of official releases for foomatic-db. Additionally, excluded hplip from the update process since the script couldn't retrieve source-tag and source-branch information for this repository.