systemd: bugreports for missing service-files

Mathieu Bridon bochecha at fedoraproject.org
Mon Jun 20 08:09:22 UTC 2011


On Mon, 2011-06-20 at 09:39 +0200, Reindl Harald wrote:
> 
> Am 20.06.2011 09:11, schrieb drago01:
> > 2011/6/19 Reindl Harald <h.reindl at thelounge.net>:
> >> [...]
> >> i am sorry too that my day has only 24 hours and that i was not aware that this work
> >> was not done from the package-maintainers since i packaged most services with
> >> syetmd-files the last days but not very happy with them because few expierience
> >> and some services are fired too soon after mysqld has started but is not ready
> >> for connections
> > 
> > If that is your problem, you probably should provide a patch to make
> > mysqsld socket activated
> 
> child i had to learn yesterday how to do this - why are these pieces missing

It's missing because no one did it.
 
And in case it isn't explicit enough, it means that the package manager
didn't do it, but that **you** didn't do it either.

(Before someone starts screaming, I know that some people provided
some .service files for a lot of services that maintainers didn't
accept, I was one of them. But what didn't get done in time by anyone
was the testing that was required for the packaging guidelines, so my
point still stands)

> and F15 not suspended from QA

Because Fedora is supposed to be a fast moving target focusing on
innovation, not something that waits months or years before releasing.

Perhaps (as has already been suggested in another one of your threads)
you are mistaking Fedora for something that it's not?

> > which means ordering wont not matter at all (might be faster then to audit
> > every service)
> 
> and the policy says "no change for F15", so F15 is released broken
> and has a policy not to fix it the whole lifetime - WTF?

Fedora 15 is not broken (at least not regarding systemd integration).

Systemd has a pretty decent compatibility with sysv initscripts, so that
services can be migrated each one at their own pace.

> what do you think i am doing the last days except getting the work of package-maintainers
> done

Remember that those package maintainers are mostly volunteers, so you
are not "doing their job", you are "participating to a community
effort", just like them.

Perhaps you should consider becoming a package maintainer yourself? It
only seems natural that you would want to give a hand in maintaining
those packages you care deeply about (or even depend on for your
business).


-- 
Mathieu




More information about the devel mailing list