Re: [systemd-devel] pre-release warnings?

2015-05-26 Thread Alexander E. Patrakov

26.05.2015 21:52, Martin Pitt wrote:

Lennart Poettering [2015-05-26 18:36 +0200]:

That said, I think even better would be to maybe make the support for
this generic in systemctl: instead of explicitly invoking chkconfig or
update-rcd, maybe we can just make systemctl invoke some fixed binary
/usr/lib/systemd/systemd-sysv-compat or so with a fixed set of
parameters. The distros could then make that a tool (maybe just a
shell script) that invokes chkconfig or update-rc.d This would then
allow us to remove any chkconfig-specific code from systemd, and would
allow all distros to plug-in the tool of their choice without having
to patch upstream. What do you think?


That sounds great. If chkconfig and update-r.cd are/were the only two
contenders then #ifdef sounds easier, but I don't know about other
distros like e. g. Gentoo.


With my Gentoo user hat on: Gentoo needs no support here. Their 
initscripts are based on OpenRC, which is not SysV-compatible enough for 
the fall back to the initscript logic to make sense at all (e.g., 
their initscripts have #!/sbin/runscript in the beginning, have no LSB 
header, and produce an error message if run in the system booted by 
systemd). In fact, they explicitly disable SysV compatibility in systemd:


# disable sysv compatibility
--with-sysvinit-path=
--with-sysvrcnd-path=

--
Alexander E. Patrakov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


[systemd-devel] pre-release warnings? [was: 220 tarball erroneously ships keyboard-keys-from-name.gperf]

2015-05-26 Thread Martin Pitt
Hello all,

Dimitri John Ledkov [2015-05-26 15:12 +0100]:
 Or will there be a v220.1 release shortly with releasy fix-ups?

Can we perhaps flip that around? I did a make dist/port our
patches/build packackages/run our tests round on May 11, but that was
before most of the recent hiccups landed in master. I'd rather love
to do that once I know that a release is around the corner, but as we
don't currently have release is imminent warnings none of the
packagers can do this as a pre-release exercise.

So Lennart: WDYT about announcing your intent to do a stable release
on the ML, and then us packagers can do a make dist, test an actual
tarball, and thus find all these little tarball errors, udev
regressions and what not before the official release is cut?

At least for me, the biggest part of updating to a new release is to
rebase our ~ 50 patches; doing that against a near-release tarball
will be the same amount of work; running automatic tests is negligible
human effort, and running manual tests doesn't take that long for me
(that's the point which might vastly differ for other packagers -- but
then again, testing pre-release tarballs means that not much will
change any more until the real release, so the second time testing
will be faster).

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] pre-release warnings? [was: 220 tarball erroneously ships keyboard-keys-from-name.gperf]

2015-05-26 Thread Lennart Poettering
On Tue, 26.05.15 16:26, Martin Pitt (martin.p...@ubuntu.com) wrote:

 Hello all,
 
 Dimitri John Ledkov [2015-05-26 15:12 +0100]:
  Or will there be a v220.1 release shortly with releasy fix-ups?
 
 Can we perhaps flip that around? I did a make dist/port our
 patches/build packackages/run our tests round on May 11, but that was
 before most of the recent hiccups landed in master. I'd rather love
 to do that once I know that a release is around the corner, but as we
 don't currently have release is imminent warnings none of the
 packagers can do this as a pre-release exercise.
 
 So Lennart: WDYT about announcing your intent to do a stable release
 on the ML, and then us packagers can do a make dist, test an actual
 tarball, and thus find all these little tarball errors, udev
 regressions and what not before the official release is cut?

Well, I had been trying to stabilize things since 3 weeks before the
release, I did mention it on IRC back then. I didn't announce this on
the ML though, but I figure I could do that too, for the next cycle...

I tend to ping some people before the release, who I know have
independent test suites or care for last-minute fixes... 

 At least for me, the biggest part of updating to a new release is to
 rebase our ~ 50 patches; doing that against a near-release tarball
 will be the same amount of work; running automatic tests is negligible
 human effort, and running manual tests doesn't take that long for me
 (that's the point which might vastly differ for other packagers -- but
 then again, testing pre-release tarballs means that not much will
 change any more until the real release, so the second time testing
 will be faster).

50 non-backport patches? That sounds like a lot...

Lennart

-- 
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] pre-release warnings? [was: 220 tarball erroneously ships keyboard-keys-from-name.gperf]

2015-05-26 Thread Martin Pitt
Lennart Poettering [2015-05-26 16:43 +0200]:
 Well, I had been trying to stabilize things since 3 weeks before the
 release

Ah, that's roughly when I did my last build packages from upstream
trunk test, and indeed it looked fairly well back then.

 I didn't announce this on the ML though, but I figure I could do
 that too, for the next cycle...

That would be nice. Let's give it a try and see how it goes? From your
end it's just an extra mail when you are ready to release (and maybe
giving packagers two days or so), and from our end it's just moving
all the heavy-lifting around a bit.

 50 non-backport patches? That sounds like a lot...

It's not that bad, most of them are trivial, like tweaking tmpfiles.d
or some extra historic udev rules. We have quite a bunch of patches to
get rid of Fedora/RedHat-isms and replace them with Debianisms, and
then there's a lot for having a non-merged /usr (which Debian didn't
do yet). Aside from two or three which keep breaking most of them just
tag along, but there's always enough noise to break completely
automatically building packages from git master. Anyway, this is
completely tangential.. :-)

Thanks,

Martin

-- 
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel


Re: [systemd-devel] pre-release warnings? [was: 220 tarball erroneously ships keyboard-keys-from-name.gperf]

2015-05-26 Thread Lennart Poettering
BOn Tue, 26.05.15 16:58, Martin Pitt (martin.p...@ubuntu.com) wrote:

  50 non-backport patches? That sounds like a lot...
 
 It's not that bad, most of them are trivial, like tweaking tmpfiles.d
 or some extra historic udev rules. We have quite a bunch of patches to
 get rid of Fedora/RedHat-isms and replace them with Debianisms, and
 then there's a lot for having a non-merged /usr (which Debian didn't
 do yet). Aside from two or three which keep breaking most of them just
 tag along, but there's always enough noise to break completely
 automatically building packages from git master. Anyway, this is
 completely tangential.. :-)

But note that upstream is supposed to be non-redhat centric, and is
supposed to support non-merged /usr. If it's really about that, I#d be
inetersted to know what these patches are about, and maybe we can move
some upstream.

Lennart

-- 
Lennart Poettering, Red Hat
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel