[PR #7148] build: remove etc-fixes directory #6340

Open
opened 2026-05-05 10:55:05 -06:00 by gitea-mirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/netblue30/firejail/pull/7148
Author: @kmk3
Created: 4/25/2026
Status: 🔄 Open

Base: masterHead: build-remove-etc-fixes


📝 Commits (1)

  • 90d7bc1 build: remove etc-fixes directory

📊 Changes

11 files changed (+0 additions, -354 deletions)

View changed files

etc-fixes/0.9.38/firefox.profile (+0 -32)
etc-fixes/0.9.52/atom.profile (+0 -31)
etc-fixes/0.9.52/firefox.profile (+0 -99)
etc-fixes/0.9.52/gedit.profile (+0 -44)
etc-fixes/0.9.52/libreoffice.profile (+0 -36)
etc-fixes/0.9.56/brave-browser.profile (+0 -6)
etc-fixes/0.9.56/brave.profile (+0 -24)
etc-fixes/0.9.58/atom.profile (+0 -35)
etc-fixes/0.9.60/atom.profile (+0 -37)
etc-fixes/seccomp-join-bug/README (+0 -10)
etc-fixes/seccomp-join-bug/eecf35c-backports.zip (+0 -0)

📄 Description

This directory contains profiles from older firejail versions with
backported bugfixes.

All of the firejail versions in question are many years old (and
unsupported by us), with the most recent version (0.9.60) being from
2019 and the last backport-related change in etc-fixes appearing to be
from 2020:

Assuming that they are not being updated/maintained (/used) anyway,
these profiles can add noise when using git grep (depending on the
search pattern used) and when trying to update many profiles at once in
general.

Future backports can be done using git branches (such as using one
branch per release), which may be less convenient for updating many
versions at once but would avoid polluting the main tree (and would be a
more common and arguably more reliable method).

So just remove this directory.

Note: This also removes a README file and a binary file:

  • etc-fixes/seccomp-join-bug/README
  • etc-fixes/seccomp-join-bug/eecf35c-backports.zip

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/netblue30/firejail/pull/7148 **Author:** [@kmk3](https://github.com/kmk3) **Created:** 4/25/2026 **Status:** 🔄 Open **Base:** `master` ← **Head:** `build-remove-etc-fixes` --- ### 📝 Commits (1) - [`90d7bc1`](https://github.com/netblue30/firejail/commit/90d7bc11a52cb9e722d3a41d0188f94ed07755f2) build: remove etc-fixes directory ### 📊 Changes **11 files changed** (+0 additions, -354 deletions) <details> <summary>View changed files</summary> ➖ `etc-fixes/0.9.38/firefox.profile` (+0 -32) ➖ `etc-fixes/0.9.52/atom.profile` (+0 -31) ➖ `etc-fixes/0.9.52/firefox.profile` (+0 -99) ➖ `etc-fixes/0.9.52/gedit.profile` (+0 -44) ➖ `etc-fixes/0.9.52/libreoffice.profile` (+0 -36) ➖ `etc-fixes/0.9.56/brave-browser.profile` (+0 -6) ➖ `etc-fixes/0.9.56/brave.profile` (+0 -24) ➖ `etc-fixes/0.9.58/atom.profile` (+0 -35) ➖ `etc-fixes/0.9.60/atom.profile` (+0 -37) ➖ `etc-fixes/seccomp-join-bug/README` (+0 -10) ➖ `etc-fixes/seccomp-join-bug/eecf35c-backports.zip` (+0 -0) </details> ### 📄 Description This directory contains profiles from older firejail versions with backported bugfixes. All of the firejail versions in question are many years old (and unsupported by us), with the most recent version (0.9.60) being from 2019 and the last backport-related change in etc-fixes appearing to be from 2020: * 55906959a ("More fixes for #3464", 2020-06-13) Assuming that they are not being updated/maintained (/used) anyway, these profiles can add noise when using `git grep` (depending on the search pattern used) and when trying to update many profiles at once in general. Future backports can be done using git branches (such as using one branch per release), which may be less convenient for updating many versions at once but would avoid polluting the main tree (and would be a more common and arguably more reliable method). So just remove this directory. Note: This also removes a README file and a binary file: * etc-fixes/seccomp-join-bug/README * etc-fixes/seccomp-join-bug/eecf35c-backports.zip --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
gitea-mirror added the
pull-request
label 2026-05-05 10:55:05 -06:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#6340
No description provided.