github-starred/firejail

Fork 0

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

[GH-ISSUE #2341] LTS build out of mainline sources #1561

New issue

Closed

opened 2026-05-05 08:13:25 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 08:13:25 -06:00

Owner

Originally created by @reinerh on GitHub (Jan 14, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2341

A Debian user asked me to provide the LTS version in Debian.
But I think that most users are probably more interested in the mainline version.

Would it be possible to build a LTS version out of the mainline sources (i.e. drop all the features that are not available in LTS at build time)?
Or are they too much differing?
In this way an additional binary package for the LTS version could be built.

Originally created by @reinerh on GitHub (Jan 14, 2019). Original GitHub issue: https://github.com/netblue30/firejail/issues/2341 A Debian user asked me to provide the LTS version in Debian. But I think that most users are probably more interested in the mainline version. Would it be possible to build a LTS version out of the mainline sources (i.e. drop all the features that are not available in LTS at build time)? Or are they too much differing? In this way an additional binary package for the LTS version could be built.

gitea-mirror

2026-05-05 08:13:25 -06:00

closed this issue
added the
enhancement
label

gitea-mirror commented

2026-05-05 08:13:28 -06:00

Author

Owner

@netblue30 commented on GitHub (Jan 20, 2019):

That was the original plan, but something went wrong. The mistake was to go (@startx2017 and I) on a different branch instead of staying on mainline. We had problems keeping the branch in sync with mainline, so at some point we deleted it and started again without any plans to merge it back to mainline.

For the next LTS release we'll go mainline-based as you describe. Most of the code is already in mainline, we can have the sync ready by the end of this year. For debian buster you'll be able to release the regular and the LTS versions in two different packages from the same source code.

@netblue30 commented on GitHub (Jan 20, 2019): That was the original plan, but something went wrong. The mistake was to go (@startx2017 and I) on a different branch instead of staying on mainline. We had problems keeping the branch in sync with mainline, so at some point we deleted it and started again without any plans to merge it back to mainline. For the next LTS release we'll go mainline-based as you describe. Most of the code is already in mainline, we can have the sync ready by the end of this year. For debian buster you'll be able to release the regular and the LTS versions in two different packages from the same source code.

gitea-mirror commented

2026-05-05 08:13:29 -06:00

Author

Owner

@SkewedZeppelin commented on GitHub (Jan 20, 2019):

@netblue30 I saw a lot of the features you were completely stripping out. Wouldn't it be easier to make those all configurable at build time with make flags? Allowing LTS to essentially just be a build variant with less attack surface?

@SkewedZeppelin commented on GitHub (Jan 20, 2019): @netblue30 I saw a lot of the features you were completely stripping out. Wouldn't it be easier to make those all configurable at build time with make flags? Allowing LTS to essentially just be a build variant with less attack surface?

gitea-mirror commented

2026-05-05 08:13:30 -06:00

Author

Owner

@reinerh commented on GitHub (Jan 20, 2019):

For the next LTS release we'll go mainline-based as you describe. Most of the code is already in mainline, we can have the sync ready by the end of this year. For debian buster you'll be able to release the regular and the LTS versions in two different packages from the same source code.

Debian Buster will be released in a few months, with a soft freeze starting in a few weeks.
So buster will probably only ship with the mainline version then.
But thanks for planning to having both releases in the same branch. That will be very useful in the future.

@reinerh commented on GitHub (Jan 20, 2019): > For the next LTS release we'll go mainline-based as you describe. Most of the code is already in mainline, we can have the sync ready by the end of this year. For debian buster you'll be able to release the regular and the LTS versions in two different packages from the same source code. Debian Buster will be released in a few months, with a [soft freeze](https://release.debian.org/buster/freeze_policy.html) starting in a few weeks. So buster will probably only ship with the mainline version then. But thanks for planning to having both releases in the same branch. That will be very useful in the future.

gitea-mirror commented

2026-05-05 08:13:31 -06:00

Author

Owner

@netblue30 commented on GitHub (Jan 20, 2019):

configurable at build time with make flags

Yes, everything will be configured at build time - some of them are already in.

Allowing LTS to essentially just be a build variant with less attack surface?

yes

Debian soft freeze on 2019-02-12 - Then I'll have full mainline releases by the end of this month in both firejail and firetools.

@netblue30 commented on GitHub (Jan 20, 2019): > configurable at build time with make flags Yes, everything will be configured at build time - some of them are already in. > Allowing LTS to essentially just be a build variant with less attack surface? yes Debian soft freeze on 2019-02-12 - Then I'll have full mainline releases by the end of this month in both firejail and firetools.

gitea-mirror commented

2026-05-05 08:13:32 -06:00

Author

Owner

@reinerh commented on GitHub (Jan 21, 2019):

Debian soft freeze on 2019-02-12 - Then I'll have full mainline releases by the end of this month in both firejail and firetools.

Thanks!
I've just uploaded the release candidate to experimental.

@reinerh commented on GitHub (Jan 21, 2019): > Debian soft freeze on 2019-02-12 - Then I'll have full mainline releases by the end of this month in both firejail and firetools. Thanks! I've just uploaded the release candidate to experimental.

gitea-mirror commented

2026-05-05 08:13:33 -06:00

Author

Owner

@netblue30 commented on GitHub (Jan 22, 2019):

Thanks! I'll have new releases for both firejail and firetools out this weekend.

@netblue30 commented on GitHub (Jan 22, 2019): Thanks! I'll have new releases for both firejail and firetools out this weekend.

gitea-mirror referenced this issue

2026-05-05 10:12:21 -06:00

[PR #1561] [MERGED] fix usage of STEAM_RUNTIME_PREFER_HOST_LIBRARIES=1 in steam.profile #4022

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

No description provided.

Rows
Columns