Add Debian

[4nd3r]

Fixes #685.

Signed-off-by: Ander Punnar ander@kvlt.ee

[4nd3r]

Wait with merge a bit, need to sort out few build failures:
https://github.com/4nd3r/libdigidocpp/actions

Weird that they showed up now, didn't happen before 🤷

Will rebase later.

[4nd3r]

Looks better now:
https://github.com/4nd3r/libdigidocpp/actions/runs/16972276007

Did few additional small changes:

• For the sake of consistency, use codenames for both.
• Adjusted the version string.
• Use standard /etc/os-release instead of lsb_release.

If codenames for Ubuntšik are not fine, then I'll revert back to numbers.

Sadly, there's no better way to define the strategy matrix, because the previously proposed approach didn't behave correctly for Debian arches.

[metsma]

I think the Debian build job shouldn’t run on every commit — it duplicates the Ubuntu job (same toolchains, packages, etc.), slows down development, and wastes GitHub resources. The Debian build would be more useful as a release/nightly check rather than a per-commit CI step.

Could you please update the workflow so that the Debian build only runs:
• on tagged releases (or published GitHub releases),
• on nightly schedule (cron),
• and optionally via manual dispatch?

That way we still verify Debian builds regularly, but without slowing down day-to-day development.

[4nd3r]

It's not possible to have per-job triggers.

Moved to separate workflow with suggested triggers.

[metsma]

Based your changes, maybe something like this metsma@f4df5b1

[4nd3r]

Personally I dislike pipeline templating used this way, and stuffing everything into one single file. YAML-based engineering in itself is already hacks built on top of hacks. But if that gets the work done, then sure, let's have it.

[metsma]

I agree this is not optimal. But duplicating build similar instructions across different yaml files is also pain.
Maybe investigate https://docs.github.com/en/actions/tutorials/create-actions/create-a-composite-action this solution?

[4nd3r]

I solved my "problem" on my own and I'm not going to continue working on this PR.

Feel free to use this in any way you see fit.