mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #4539] List of deprecated profiles #2696
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#2696
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 @ghost on GitHub (Sep 13, 2021).
Original GitHub issue: https://github.com/netblue30/firejail/issues/4539
I'm creating this issue, to keep track of the profiles that would need deleting in the future. I remind you, they are 1000+ profiles and we need to note down what is on it's way out. Propose suspect profiles.
profiles with support for old versions
@kmk3 commented on GitHub (Sep 14, 2021):
@pirate486743186 commented on Sep 13:
What would be the "need" to delete profiles?
If the idea is about avoiding having >1000 files per directory (because of
GitHub file listing), how about moving certain profiles to an archive directory
instead (e.g.: "etc-archive")?
Why do you consider that to be the case? The latest commit is from July and it
still works.
These still exist in the AUR at least:
While rtv is likely to break (as suggested by the main author on
https://github.com/michael-lazar/rtv/issues/696) or to already be broken,
it's not like RSS is a moving target, so newsbeuter will probably keep working.
@ghost commented on GitHub (Sep 14, 2021):
you'll leave in profiles that are useless? You need to remove the dead stuff. I'm a bit surprised by the casual attitude regarding the profiles
These are not to be deleted immediately. Maybe i should detail the reasons in the list...
youtube-dl has many red flags. Yes exactly, last commit was 1 of July, but this is a fast moving project, that's incredibly long. A partial workaround was found for age restricted videos in youtube, that's still not implemented. Also, youtube-dl is not just about youtube, it has downloaders for many other sites, you can't just see how it performs with youtube. If you are interested, yt-dlp seams to be the new youtube-dl. It's 90% certain at this point that youtube-dl is dead.
newsbeuter is not "really" abandoned, it just changed name. No one "maintains" it, because they maintain newsboat. newsbeuter will just accumulate bitrot until it can't compile. Arch is all bleeding edge, can you still install newsbeuter? It was removed from debian. The only users must be from old versions of distributions that are still maintained.
rtv still works, until reddit changes their API or is left behind by python. Presumably a fork will succeed by then and we'll recycle the profile.
@crocket commented on GitHub (Sep 16, 2021):
youtube-dl.profile doesn't need to be deleted so quickly.
@ghost commented on GitHub (Sep 16, 2021):
i'm not saying immediately. It will become almost useless very fast though.
you want to use yt-dlp.
@kmk3 commented on GitHub (Sep 16, 2021):
@pirate486743186 commented on Sep 14:
Useless to whom? If a program still works and still has users, it by
definition has a use, and so does its profile.
Again, what would be the "need" to remove anything?
I see that you added redirects on some of the mentioned profiles, such as:
If you're worried about maintenance, we can just undo the redirects so that the
original programs don't affect and don't get affected by their forks. This
would also make it easier to update fork profiles if they require
major/frequent changes. And so the original profiles would mostly only get
updated by mass search/replace commits, which maintenance-burden-wise is not
too different from them being deleted.
Note: If a profile redirect starts being a nuisance, doing the above would
likely be helpful regardless of a project's maintenance status.
I could say the same. It takes effort to write a profile, especially one that
is a good combination of secure, usable and generic and it's hard to tell how
many users any given profile might have.
A timeframe would help clarify things. It's not clear if the suggestion is to
remove a profile a day or years after you consider a program to be "dead".
I agree that due to it depending on ever-changing web-based APIs, it requires
more constant care than not. Though I can't remember the last time that it
failed on me due to YouTube API changes (other than for the age-restricted
videos). IME it has been more solid in that regard than other YouTube
frontends at least.
How come? If we're still talking about "useless" programs: In a given program,
if half of its functionality stops working and you don't notice it (because you
never used such functionality), does the program stop being useful?
I have planned on trying yt-dlp, though I'm not sure if I'll bother while
youtube-dl still works. youtube-dl is integrated with other software (like
mpv), so I'd have to change config files and scripts and retest, which I have
no interest in doing at the moment. Note also that options were removed and
that many defaults have changed (all of which may have to be evaluated), so it
is not a 100% drop-in replacement.
See also the following comment on a related issue:
@dirkf commented on Sep 14:
I'd wager that most users will only notice that anything changed (or didn't
change fast enough) in youtube-dl if/when it actually stops working for
YouTube. Other than that, I'd expect at least one of the following to happen
before making such a claim:
While the UI is similar, newsboat has a massive additional dependency
(rust/cargo), so it's hardly the same project packaging-wise. To me it might
as well have been a complete rewrite considering that. Also, the maintainer of
newsboat considers it to be a fork.
I tested newsbeuter-git and all it takes is adding
-DTRUE=1 -DFALSE=0toCFLAGS, as json-c for some reason had macros for true and false. It also works
fine. Note that the latest commit is from 2017-09-20, so it still works after
being unchanged for almost 4 years. I guess the dependencies were nicely
chosen. Anyway, that was an interesting exercise; I'll send a patch to the AUR
maintainer later.
Which by definition would mean that the profile is still useful. Also, why
would the age of a distribution matter profile-wise if it's still maintained
and if firejail still works on it? Right on the README.md firejail has
instructions for Ubuntu 18.04, for example.
@dirkf commented on GitHub (Sep 16, 2021):
Indeed.
Ubuntu 16.04 is in ESM support until 2024. 18.04 (ESM to 2028) is some bleeding edge OS in comparison.
@crocket commented on GitHub (Sep 16, 2021):
I can't relate to ubuntu's bleding edge. I use gentoo linux. I also used to use artix linux which is a derivative of arch linux.
Arch linux is the bleeding edge. Gentoo linux is a little behind because of stabilization process.
Gentoo linux package stabilization process is a good tradeoff between bleeding edge and stability. On gentoo linux, you can choose either the bleeding edge or a stable version for each package. Other distributions force you to be on the bleeding edge or stable versions for every package.
@ghost commented on GitHub (Sep 17, 2021):
install yt-dlp, then make a symbolic link to it named youtube-dl in your path. A few things changed, for example the download filename format ("--compat-options filename" will give you the old one). So test things a bit, then take your time to change the configurations.
They are 1000+ profiles, you need to note down somewhere what is on it's way out. Stop freaking out.
@rusty-snake commented on GitHub (Oct 30, 2022):
I don't think we need to track this in an issue.