github-starred/firejail

Fork 0

mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00

[GH-ISSUE #4268] Conflict with jailtest utility #2600

New issue

Closed

opened 2026-05-05 09:16:17 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 09:16:17 -06:00

Owner

Originally created by @reinerh on GitHub (May 10, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/4268

The new jailtest utility conflicts with a utility of the same name included in uml-utilities (Debian), uml_utilities (Fedora, Arch AUR).
They are installed in the same location (/usr/bin/jailtest). This means for packaging, that a Breaks relationship needs to be declared, which means that firejail can not be co-installed with the uml-utilities package. This is very user-unfriendly and should be avoided if possible. As it has not been released yet, avoiding a conflict is still possible.

Is this tool actually needed globally? Or would it be sufficient to have it in a private directory (like /usr/lib/firejail/, where other helper tools like fldd are located)?

If the tool really is supposed to be invoked by users manually, could we think of a different name to avoid a conflict?

Alternatively I'm also considering not shipping it in the Debian package.

Any opinions?

Ping @netblue30

Originally created by @reinerh on GitHub (May 10, 2021). Original GitHub issue: https://github.com/netblue30/firejail/issues/4268 The new `jailtest` utility conflicts with a utility of the same name included in `uml-utilities` (Debian), `uml_utilities` (Fedora, Arch AUR). They are installed in the same location (`/usr/bin/jailtest`). This means for packaging, that a `Breaks` relationship needs to be declared, which means that firejail can not be co-installed with the uml-utilities package. This is very user-unfriendly and should be avoided if possible. As it has not been released yet, avoiding a conflict is still possible. Is this tool actually needed globally? Or would it be sufficient to have it in a private directory (like `/usr/lib/firejail/`, where other helper tools like fldd are located)? If the tool really is supposed to be invoked by users manually, could we think of a different name to avoid a conflict? Alternatively I'm also considering not shipping it in the Debian package. Any opinions? Ping @netblue30

gitea-mirror

2026-05-05 09:16:17 -06:00

closed this issue
added the
help wanted

question_old
labels

gitea-mirror commented

2026-05-05 09:16:20 -06:00

Author

Owner

@ghost commented on GitHub (May 10, 2021):

Is this tool actually needed globally?

Personally I would answer 'yes'. Now that --audit is gone this tool is pretty nice to check running sandboxes.

If the tool really is supposed to be invoked by users manually, could we think of a different name to avoid a conflict?

firejailtest, firetest, jailcheck - just a few ideas (didn't check for any name collisions)...

@ghost commented on GitHub (May 10, 2021): Is this tool actually needed globally? Personally I would answer 'yes'. Now that --audit is gone this tool is pretty nice to check running sandboxes. > If the tool really is supposed to be invoked by users manually, could we think of a different name to avoid a conflict? firejailtest, firetest, jailcheck - just a few ideas (didn't check for any name collisions)...

gitea-mirror commented

2026-05-05 09:16:21 -06:00

Author

Owner

@netblue30 commented on GitHub (May 13, 2021):

Thanks, I'll move it to "jailcheck". How do we check for collisions?

@netblue30 commented on GitHub (May 13, 2021): Thanks, I'll move it to "jailcheck". How do we check for collisions?

gitea-mirror commented

2026-05-05 09:16:21 -06:00

Author

Owner

@kmk3 commented on GitHub (May 13, 2021):

@glitsj16 commented 2 days ago:

firejailtest, firetest, jailcheck - just a few ideas (didn't check for any
name collisions)...

@netblue30 commented 3 hours ago:

Thanks, I'll move it to "jailcheck". How do we check for collisions?

On Arch, it can be done with with pacman -F:

$ pacman -F firejail
community/firejail 0.9.64.4-1
    usr/bin/firejail
    usr/share/bash-completion/completions/firejail
$ pacman -F jailtest firejailtest firetest jailcheck

I doesn't check the AUR though.

And according to the Pacman Rosetta, on Debian this can be done with:

apt-file search

@kmk3 commented on GitHub (May 13, 2021): @glitsj16 commented 2 days ago: > firejailtest, firetest, jailcheck - just a few ideas (didn't check for any > name collisions)... @netblue30 commented 3 hours ago: > Thanks, I'll move it to "jailcheck". How do we check for collisions? On Arch, it can be done with with `pacman -F`: ```console $ pacman -F firejail community/firejail 0.9.64.4-1 usr/bin/firejail usr/share/bash-completion/completions/firejail $ pacman -F jailtest firejailtest firetest jailcheck ``` I doesn't check the AUR though. And according to the [Pacman Rosetta][1], on Debian this can be done with: ```sh apt-file search ``` [1]: https://wiki.archlinux.org/title/Pacman/Rosetta#Querying_specific_packages

gitea-mirror commented

2026-05-05 09:16:21 -06:00

Author

Owner

@rusty-snake commented on GitHub (May 13, 2021):

And for Fedora it is dnf provides <PROGRAM|PATH>.

$ en_US-locale dnf provides jailcheck
Error: No Matches found

@rusty-snake commented on GitHub (May 13, 2021): And for Fedora it is `dnf provides <PROGRAM|PATH>`. ``` $ en_US-locale dnf provides jailcheck Error: No Matches found ```

gitea-mirror commented

2026-05-05 09:16:22 -06:00

Author

Owner

@reinerh commented on GitHub (May 13, 2021):

And according to the Pacman Rosetta, on Debian this can be done with:
apt-file search

Yes, that's correct. There is also no conflict in Debian:

$ apt-file search jailcheck
$

@reinerh commented on GitHub (May 13, 2021): > And according to the [Pacman Rosetta](https://wiki.archlinux.org/title/Pacman/Rosetta#Querying_specific_packages), on Debian this can be done with: > > ```shell > apt-file search > ``` Yes, that's correct. There is also no conflict in Debian: ``` $ apt-file search jailcheck $ ```

gitea-mirror commented

2026-05-05 09:16:22 -06:00

Author

Owner

@netblue30 commented on GitHub (May 18, 2021):

jailcheck all set!

@netblue30 commented on GitHub (May 18, 2021): jailcheck all set!

gitea-mirror referenced this issue

2026-05-05 10:20:07 -06:00

[PR #2600] [MERGED] Seahorse revisited #4438

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#2600

No description provided.

Rows
Columns