mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #6702] Update Debian package / Ubuntu PPA to 0.9.74 #3340
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#3340
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kmk3 on GitHub (Apr 5, 2025).
Original GitHub issue: https://github.com/netblue30/firejail/issues/6702
Originally assigned to: @reinerh on GitHub.
Currently the latest Debian package and Ubuntu PPA appear to be for version
0.9.72:
Version 0.9.74 was released on 2025-03-25:
Relates to:
@reinerh commented on GitHub (Apr 5, 2025):
It's already packaged in git (https://salsa.debian.org/reiner/firejail), but not yet uploaded due to testing errors: https://salsa.debian.org/reiner/firejail/-/jobs/7331459
@kmk3 commented on GitHub (Apr 5, 2025):
Nice.
I see; I wasn't aware of that repository.
This job seems to produce a lot of testing errors that do not happen in the
GitHub CI.
From my experience with firejail tests in CI, they seem to be rather brittle;
would it make sense to skip them for the upload?
Do you need help with anything?
@reinerh commented on GitHub (Apr 5, 2025):
Yes, they are rather fragile. I've already split them in the past into tests are really fragile and allowed to fail and in a core set of tests that I thought should be always work. But even they are failing partially now. And I can't even reproduce it on my system. I'll probably mark all of them as "fragile". :|
If you are able to reproduce some failures and file tickets or so that would be nice (so they can be fixed in a future version). But I'll probably upload it anyways in the next days.
@krwudtke commented on GitHub (May 12, 2025):
I'm kind of new to this, but it has been over a month, and it appears that the version still hasn't been updated in the PPA. Any news?
@reinerh commented on GitHub (May 12, 2025):
@krwudtke thanks for the reminder. i've now uploaded them to the PPA as well (except for the current development version, which should soon sync from Debian).
@kmk3 commented on GitHub (Aug 4, 2025):
I could not reproduce the errors at all; they seemed to be very specific to
this environment.
So I created #6853, which should make it easier to debug them.
Closing the main issue as resolved.