Re:Systemd 248 RC3: systemd-oomd is now considered fully sup...
by iio7 on Saturday March 13, 2021 @07:03PM
(#26451403)
Could they maybe start handling the 1400+ bugs that has been a part of systemd for such a long time (some unresolved since 2015) rather than keep adding and adding and adding and adding code!
[ Parent
| on HN ]
Re:Systemd 248 RC3: systemd-oomd is now considered fully sup...
by jabiko on Saturday March 13, 2021 @07:16PM
(#26451499)
There are a lot of open issues but you are a bit unfair in calling them bugs.
If you filter out the RFEs (Requests For Enhancement) you find 617 issues. If you filter for only issues labeled as a bug you get 97 results.
Re:Systemd 248 RC3: systemd-oomd is now considered fully sup...
by stonogo on Saturday March 13, 2021 @07:47PM
(#26451673)
OK, but they don't always label bugs that way (example: systemd/#5616) and the bugs that are labeled can get pretty old (systemd/#3700). Furthermore a lot of RFEs are really just disguised bug reports (systemd/#5917 is just an RFE rephrasing of system/#3700).
In my experience, unless you can get Red Hat to care about patching a specific bug, you can rely on opened bugs to stay open.
Re:Systemd 248 RC3: systemd-oomd is now considered fully sup...
by viraptor on Saturday March 13, 2021 @08:47PM
(#26452025)
I didn't dig into others, but:
> don't always label bugs that way (example: systemd/#5616)
Nobody figured out if that issue is in logind or X yet. They did not close it so it's not like they say it can't possibly be on systemd side. (typical Lennart comments aside)
Re:Systemd 248 RC3: systemd-oomd is now considered fully sup...
by zokier on Sunday March 14, 2021 @08:15AM
(#26454686)
People add features they need, and fix bugs that impact them. Scratching your own itch is the fundamental principle in open source. I recommend you to do the same.
Re:Systemd 248 RC3: systemd-oomd is now considered fully sup...
by jbverschoor on Saturday March 13, 2021 @07:09PM
(#26451444)
Feel free to contribute to open source projects!