https://bugzilla.redhat.com/show_bug.cgi?id=1554943#c13
how can it be that the most important component after the kernel is left over moths with bugs which easily lead to data loss? F26 is in 4 weeks EOL and F27 suffers it's half lifetime from an issue leading to unclean unmounts and journal-replay
Fedora has a major problem: systemd bugs are repeatly not fixed even when there are upstream patches available in the whole lifecycle of the distribution and again: this is not acceptable for one of the most important packages
https://bugzilla.redhat.com/show_bug.cgi?id=1500916
This should be reported to FESCo, not the Council. Can you open the ticket here: https://pagure.io/fesco/ please?
done: https://pagure.io/fesco/issue/1887 - i was pointed from the project leader here, but anyways
-------- Weitergeleitete Nachricht -------- Betreff: Re: systemd: where make an official complaint about a maintainer? Datum: Thu, 3 May 2018 10:23:53 -0400 Von: Matthew Miller mattdm@mattdm.org An: Reindl Harald h.reindl@thelounge.net
The appropriate place for such a complaint would be in the Fedora Council issue tracker. https://pagure.io/Fedora-Council/tickets/
I would suggest other avenues of escalation first, however ? perhaps the https://fedoraproject.org/wiki/Fedora_Program_Management/Prioritized_bugs_and_issues process. Or, consider submitting a pull request to the F27 package.
Particularly, I would not ascribe malice or effrontery to something which can easily be explained by "this person has a lot of work they're doing, and could use help".
On Thu, May 03, 2018 at 02:32:23PM +0200, Reindl Harald wrote:
Hi since you are the project leader and bugzilla don't help i see no other way than contact you directly - in 4 weeks F26 is out of maintainance and F27 has a serious bug in systemd which could have been fixed last year long before my report
Hi
since you are the project leader and bugzilla don't help i see no other way than contact you directly - in 4 weeks F26 is out of maintainance and F27 has a serious bug in systemd which could have been fixed last year long before my report
Metadata Update from @jwboyer: - Issue assigned to jwboyer
Thank you. I'd like to give the engineering committee time to look at the issue first. If nothing happens to help the problem, we can continue discussion here. We'll leave this open for now.
@jwboyer how did the engineering conversation go?
it was closed as invalid. The FESCo ticket quickly devolved into arguments.
Metadata Update from @bcotton: - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.