mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #7025] build: 0.9.78: release tag is in the wrong commit (version 0.9.79) #3458
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#3458
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 @Wyuld0 on GitHub (Jan 11, 2026).
Original GitHub issue: https://github.com/netblue30/firejail/issues/7025
Dear developers,
According to the home page , the stable version is currently 0.9.78, while the unstable version under development is 0.9.79.
As I am an occasional user of git, to obtain a firejail_0.9.78_amd64.deb package, I first asked for assistance from deepwiki.com, then from Github Copilot, to no avail: whatever method I use, I always get a firejail_0.9.79_1_amd64.deb package, and after installation, firejail --version always shows 0.9.79.
Method 1 recommended by Github Copilot fails:
Method 2 recommended by Github Copilot fails:
I'm just an amateur when it comes to compiling. However, I have a feeling that there is an error in the metadata that is causing this behavior:
Thanks in advance.
Relates to:
@kmk3 commented on GitHub (Jan 13, 2026):
Hello, thanks for the report.
This is the original/correct commit for the release:
196de37df4But the 0.9.78 release tag currently points a few commits ahead of where it
should:
35d61001e0Changes:
196de37df4...35d61001e0We are in the process of fixing that; see the following for details:
Other than a different program version, there are only minor documentation
changes compared to the original commit, so it should be fine to keep using
that build.
You can also manually checkout the correct commit and build from that: