[GH-ISSUE #7025] build: 0.9.78: release tag is in the wrong commit (version 0.9.79) #3458

Open
opened 2026-05-05 10:00:37 -06:00 by gitea-mirror · 1 comment
Owner

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:

git clone https://github.com/netblue30/firejail.git
cd firejail
git checkout tags/0.9.78 -b build-0.9.78
./configure && make deb

Method 2 recommended by Github Copilot fails:

wget https://github.com/netblue30/firejail/archive/refs/tags/0.9.78.tar.gz
tar xzf 0.9.78.tar.gz
cd firejail-0.9.78
./configure && make deb

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:

user@devuan:~/Downloads/firejail$ git describe --tags --exact-match || echo "Not on an exact tag"
0.9.78
user@devuan:~/Downloads/firejail$ grep 0.9.78 configure
user@devuan:~/Downloads/firejail$ grep 0.9.79 configure
# Generated by GNU Autoconf 2.72 for firejail 0.9.79.
PACKAGE_VERSION='0.9.79'
PACKAGE_STRING='firejail 0.9.79'
'configure' configures firejail 0.9.79 to adapt to many kinds of systems.
     short | recursive ) echo "Configuration of firejail 0.9.79:";;
firejail configure 0.9.79
It was created by firejail $as_me 0.9.79, which was
This file was extended by firejail $as_me 0.9.79, which was
firejail config.status 0.9.79

Thanks in advance.

Relates to:

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 [](https://github.com/netblue30/firejail), 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: ```sh git clone https://github.com/netblue30/firejail.git cd firejail git checkout tags/0.9.78 -b build-0.9.78 ./configure && make deb ``` Method 2 recommended by Github Copilot fails: ```sh wget https://github.com/netblue30/firejail/archive/refs/tags/0.9.78.tar.gz tar xzf 0.9.78.tar.gz cd firejail-0.9.78 ./configure && make deb ``` 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: ```console user@devuan:~/Downloads/firejail$ git describe --tags --exact-match || echo "Not on an exact tag" 0.9.78 user@devuan:~/Downloads/firejail$ grep 0.9.78 configure user@devuan:~/Downloads/firejail$ grep 0.9.79 configure # Generated by GNU Autoconf 2.72 for firejail 0.9.79. PACKAGE_VERSION='0.9.79' PACKAGE_STRING='firejail 0.9.79' 'configure' configures firejail 0.9.79 to adapt to many kinds of systems. short | recursive ) echo "Configuration of firejail 0.9.79:";; firejail configure 0.9.79 It was created by firejail $as_me 0.9.79, which was This file was extended by firejail $as_me 0.9.79, which was firejail config.status 0.9.79 ``` Thanks in advance. Relates to: * #6841
gitea-mirror added the
bug
packaging
labels 2026-05-05 10:00:37 -06:00
Author
Owner

@kmk3 commented on GitHub (Jan 13, 2026):

Hello, thanks for the report.

This is the original/correct commit for the release:

But the 0.9.78 release tag currently points a few commits ahead of where it
should:

Changes:

We 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:

git clone https://github.com/netblue30/firejail.git
cd firejail
git checkout 196de37df4f98061341476f8fa9f84b369d06a7a -b build-0.9.78
./configure && make deb
<!-- gh-comment-id:3741461309 --> @kmk3 commented on GitHub (Jan 13, 2026): Hello, thanks for the report. This is the original/correct commit for the release: * https://github.com/netblue30/firejail/commit/196de37df4f98061341476f8fa9f84b369d06a7a But the 0.9.78 release tag currently points a few commits ahead of where it should: * https://github.com/netblue30/firejail/commit/35d61001e06494c5523cfed3dd679b6ad4082be5 Changes: * https://github.com/netblue30/firejail/compare/196de37df4f98061341476f8fa9f84b369d06a7a...35d61001e06494c5523cfed3dd679b6ad4082be5 We are in the process of fixing that; see the following for details: * <https://github.com/netblue30/firejail/discussions/6841#discussioncomment-15480734> 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: ```sh git clone https://github.com/netblue30/firejail.git cd firejail git checkout 196de37df4f98061341476f8fa9f84b369d06a7a -b build-0.9.78 ./configure && make deb ```
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#3458
No description provided.