You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The version detection code from nzbget is broken in nzbget-ng I think, because of changes to autoconfigure.ac or something around that. It thinks the current version is 21.0.0, which I guess is the default it uses when it can't detect the correct version with whatever mechanism it (tries to) use.
I tried to fix it, but couldn't find how to.
I never said I'd be archiving nzbget-ng/nzbget, and certainly won't until I've made sure everything of value and still relevant has made it into nzbgetcom/nzbget. I hate seeing good work being dropped on the floor.
I'm in the process of moving all the issues and discussions in nzbget-ng/nzbget over to nzbgetcom/nzbget as we speak. I'll also be looking at those improvements in nzbget-ng that nzbgetcom hasn't already adopted, and making pull requests. No commitments on when though, due to the same problem I've been transparent about from the get-go - not enough time. I'm not a member of that repo either, so the final say over what is incorporated will be up to the maintainers of that repo.
For all the appreciation I have for hugbug and the large amount of time and effort he put into nzbget, I find it hard to understand why it was abandoned it so abruptly, and almost killing it by doing so. Baffling.
Transitions can be handled gracefully, and that's my goal. nzbget will finally be back in the hands of people who can dedicate enough time to do it justice.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
As this is a fork from the original, Do we know when/if this fork will get "containerised"?
Beta Was this translation helpful? Give feedback.
All reactions