[GH-ISSUE #6853] ci: Replicate Debian CI jobs in our GitLab CI #3395

New issue

gitea-mirror · 2026-05-05T09:57:50-06:00

gitea-mirror commented

2026-05-05 09:57:50 -06:00

Originally created by @kmk3 on GitHub (Aug 4, 2025).
Original GitHub issue: https://github.com/netblue30/firejail/issues/6853

Currently Debian packaging issues are mostly only checked at the end of a
release, but it would be nice to have it normally tested as a part of our own
CI so that issues can be caught earlier.

Also, when I last looked at the errors in #6702, they seemed to be very
unusual/specific to that Debian CI environment, so it would be helpful to have
an equivalent job in our CI to make it easier to debug and iterate.

Note: We currently have a debian_ci job in .gitlab-ci.yml, but it does not
produce the same errors as in the official Debian CI.

Relates to:

#6702

Originally created by @kmk3 on GitHub (Aug 4, 2025). Original GitHub issue: https://github.com/netblue30/firejail/issues/6853 Currently Debian packaging issues are mostly only checked at the end of a release, but it would be nice to have it normally tested as a part of our own CI so that issues can be caught earlier. Also, when I last looked at the errors in #6702, they seemed to be very unusual/specific to that Debian CI environment, so it would be helpful to have an equivalent job in our CI to make it easier to debug and iterate. Note: We currently have a `debian_ci` job in .gitlab-ci.yml, but it does not produce the same errors as in the official Debian CI. Relates to: * #6702

gitea-mirror added the

enhancement

packaging

labels 2026-05-05 09:57:50 -06:00

gitea-mirror referenced this issue

2026-05-05 10:25:52 -06:00

[PR #3395] [MERGED] docs: bug_report.md: clarify and ask for more specific information #4748

Sign in to join this conversation.