-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
{tvheadend,antennas}: drop #336395
{tvheadend,antennas}: drop #336395
Conversation
c85b218
to
8083972
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
An entry in the release notes should be added about the removal of these two services and packages
8083972
to
5f2b4c1
Compare
Good point about the release notes! Added. |
Please Renee otherwise come fine to merge |
5f2b4c1
to
a565cfe
Compare
I use both. I would like to mantain them, but the tvheadend 4.3-unstable version. |
Sorry for the late response, for tvheadend i have no strong desire or time to maintain it |
Thank you for the response all the same! I’m currently waiting on a reply to #332259 (comment) in the other PR from @oneingan that I hope will let us figure out a sustainable path forward for the package and module. I’ll probably merge this in a few days if I don’t hear back so that it’s not blocking FFmpeg 4 clean‐ups; the package and module can always be re‐added a later date once we figure out maintenance and what to do with them. |
Sorry for the late response. I have no interest in maintaining tvheadend or antennas, as I only know the basics of nix. But I do need these two packages for my server, so examples of how I can continue to use them even if the packages are no longer available would be very helpful. Edit: If it matters, I use the git version of tvheadend by using an overlay. |
Thanks for the response, @Gooxey. Overlaying your own package should continue to work even after this PR, although you’d have to copy the NixOS module into your configuration if you use that. I packaged the Git version in #332259; if you managed to recreate that with an overlay I’d say you’re qualified to maintain it, but obviously there’s no obligation to :) Honestly, I would be happy to just merge the update I wrote and leave the package without a maintainer for now, which I assume would make things easier for you in general, but I need someone who knows the software well enough to explain what the backwards incompatibility compared to 4.2 is and how difficult migration would be for users. If you can comment on that it’d be very helpful, as the upstream warnings about “no direct upgrade path from v4.2 to v4.3/v4.4” and the comment in #168620 saying “Updating to latest master (aka v4.3) will break configs of most people using v4.2” concern me that it would break as many people’s setups as just removing it for being unmaintained would. |
Leaving the package without a maintainer seems like the best solution. Maybe someone will start maintaining it in the future. But in the meantime, other people who need this package, or at least the module, will not have the unnecessary problems that would be caused by removing both packages. As for TVHeadend, I have never had anything to do with it and only know that it has something to do with TV channels. I just upgraded an old server from Ubuntu to NixOS. But maybe you could add some kind of switch that would allow you to use either the legacy v4.2 or the latest supported version. In theory, this would satisfy both parties, unless I am forgetting something. |
Keeping 4.2 gives us the problems of having to maintain an old end‐of‐life version of FFmpeg indefinitely when every other working source package in Nixpkgs has been migrated off it. It’s also already taken up limited maintainer resources from the rest of the tree multiple times as changes in other packages have caused it to break and need fixing by people who, like me, have no particular relevant interest or expertise in it. So while I don’t have any inherent objection to leaving the package abandoned for now, we do need to get it off 4.2, and unfortunately it seems like nobody knows enough about Tvheadend to be able to tell us what compatibility risks that would entail or help us mitigate them. That’s unfortunate, but these kinds of issues are why keeping unmaintained packages around is a liability. I’ve already spent more time on this package than almost any other involved in the mass FFmpeg migration and I’m not sure a resolution is in sight. Hopefully @oneingan will reply to #332259 (comment) soon; otherwise I think the best way forward is to drop the packages for now and revive them when someone who can maintain them steps up. |
Merging per #332259 (comment). Hopefully we’ll have 4.3 packaged soon! |
Picked up the dropped package config for Tvheadend from NixOS/nixpkgs#332259 and its service config from NixOS/nixpkgs#336395, passed into giants-deep config.
Description of changes
See #332259.
tvheadend
is stuck on an unmaintained version that depends on FFmpeg 4; upstream recommend that users install the 4.3 development version, which will soon become the 4.4 stable release, but that version is backwards‐incompatible with current configurations, and it seems that nobody is willing to maintain the package and service. Since we have no way of making a decision here and the package and service are effectively unmaintained and headed for permanent bitrot, let’s be honest with our users and drop the code. Hopefully someone will step up to maintain it.I have also removed
antennas
, as it is intended solely for use withtvheadend
.@bachp @Gooxey I see that you have both done work on the
antennas
module, so I assume that you aretvheadend
users. Would you be willing to take up the mantle oftvheadend
maintenance and help us decide what to do about 4.3/4.4? I didn’t notice theantennas
module before now, so I didn’t think to ping you on the original PR, but I’d be very happy to close this in favour of #332259 if we can get the package maintained again and get it on a current version.Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.