Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mkdeb.sh.in: stop enabling apparmor #5176

Merged
merged 1 commit into from
Jun 6, 2022

Conversation

kmk3
Copy link
Collaborator

@kmk3 kmk3 commented Jun 5, 2022

Since make deb-apparmor already exists, use that for now instead of
changing what make deb does.

This fixes CI.

Added on commit 494b26d ("adding --enable-apparmor by default for make
deb - most Debian-based distros have apparmor enabled by default",
2022-06-03).

Kind of relates to #5154.

Since `make deb-apparmor` already exists, use that for now instead of
changing what `make deb` does.

This fixes CI.

Added on commit 494b26d ("adding --enable-apparmor by default for make
deb - most Debian-based distros have apparmor enabled by default",
2022-06-03).

Kind of relates to netblue30#5154.
@kmk3 kmk3 requested review from reinerh and netblue30 June 5, 2022 17:32
@kmk3
Copy link
Collaborator Author

kmk3 commented Jun 5, 2022

Note: I think it would be nice to add --enable-apparmor to mkdeb.sh.in and to
then remove make deb-apparmor, as it would make things simpler. I thought
about doing that on #5154, but I wasn't too sure about it and I wanted to avoid
making any breaking changes in that PR.

Since the upcoming release is near and since it is meant to be about important
bugfixes, I think it would be better to leave this change for later, to
minimize breaking changes and also because it would probably require some
reorganization in .gitlab-ci.yml to make it work without it looking confusing.

@netblue30
Copy link
Owner

Fixed!

@netblue30 netblue30 merged commit 4a9f73b into netblue30:master Jun 6, 2022
@kmk3 kmk3 deleted the build-mkdeb-undo-apparmor branch June 6, 2022 19:22
kmk3 added a commit that referenced this pull request Jun 18, 2022
This amends commit 9a0fbbd ("mkdeb.sh.in: pass remaining arguments to
./configure", 2022-05-13) / PR #5154.

See also #5176.
kmk3 added a commit to kmk3/firejail that referenced this pull request Dec 21, 2022
This reverts commit 8229944.

The idea is to later enable building the .deb package with AppArmor by
default with `make deb` and to then remove `make deb-apparmor` (though
note that some ci changes might also be needed in tandem[1]).  This
could potentially allow building a .deb package for all firejail
versions (including past and future ones) with just `make deb`.

Also, note that other options can be added/removed to the default `deb`
target (besides AppArmor-related ones), so ideally there would be only a
single `deb` target with all the desired options applied.

So instead of releasing a version without `make deb` and then
potentially adding it back and removing `make deb-apparmor`, just leave
the targets as is (considering the current release, 0.9.70) for now.

[1] netblue30#5176 (comment)
kmk3 added a commit to kmk3/firejail that referenced this pull request Feb 17, 2023
The official .deb package is always built with apparmor support, so use
`--enable-apparmor` in mkdeb.sh and remove the "deb-apparmor" target in
order to reduce redundancy.

Note that custom configure options may be specified by calling
./mkdeb.sh directly.

For example, to build the .deb package without apparmor support, instead
of running `make deb`, the following commands can be used:

    make dist
    ./mkdeb.sh --disable-apparmor

Also, change the `build_apparmor` GitLab CI job into
`build_no_apparmor`, which is intended to check that building without
apparmor still works.

Note: This commit makes the resulting .deb package not have an
"-apparmor" suffix (see `EXTRA_VERSION` in mkdeb.sh), to avoid
redundancy (as having apparmor support becomes the default).

Misc: This is a follow-up to netblue30#5654.

Relates to netblue30#5154 netblue30#5176 netblue30#5547.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done (RELNOTES N/A)
Development

Successfully merging this pull request may close these issues.

3 participants