Discussion:
[ANNOUNCE] systemd 212
(too old to reply)
Kay Sievers
2014-03-25 23:28:59 UTC
Permalink
Many bugfixes, and a number of new features:

http://www.freedesktop.org/software/systemd/systemd-212.tar.xz

CHANGES WITH 212:

* When restoring the screen brightness at boot, stay away from
the darkest setting or from the lowest 5% of the available
range, depending on which is the larger value of both. This
should effectively protect the user from rebooting into a
black screen, should the brightness have been set to minimum
by accident.

* sd-login gained a new sd_machine_get_class() call to
determine the class ("vm" or "container") of a machine
registered with machined.

* sd-login gained new calls
sd_peer_get_{session,owner_uid,unit,user_unit,slice,machine_name}(),
to query the identity of the peer of a local AF_UNIX
connection. They operate similar to their sd_pid_get_xyz()
counterparts.

* PID 1 will now maintain a system-wide system state engine
with the states "starting", "running", "degraded",
"maintenance", "stopping". These states are bound to system
startup, normal runtime, runtime with at least one failed
service, rescue/emergency mode and system shutdown. This
state is shown in the "systemctl status" output when no unit
name is passed. It is useful to determine system state, in
particularly when doing so for many systems or containers at
once.

* A new command "list-machines" has been added to "systemctl"
that lists all local OS containers and shows their system
state (see above), if systemd runs inside of them.

* systemctl gained a new "-r" switch to recursively enumerate
units on all local containers, when used with the
"list-unit" command (which is the default one that is
executed when no parameters are specified).

* The GPT automatic partition discovery logic will now honour
two GPT partition flags: one may be set on a partition to
cause it to be mounted read-only, and the other may be set
on a partition to ignore it during automatic discovery.

* Two new GPT type UUIDs have been added for automatic root
partition discovery, for 32bit and 64bit ARM. This is not
particularly useful for discovering the root directory on
these architectures during bare-metal boots (since UEFI is
not common there), but still very useful to allow booting of
ARM disk images in nspawn with the -i option.

* MAC addresses of interfaces created with nspawn's
--network-interface= switch will now be generated from the
machine name, and thus be stable between multiple invocations
of the container.

* logind will now automatically remove all IPC objects owned
by a user if she or he fully logs out. This makes sure that
users who are logged out cannot continue to consume IPC
resources. This covers SysV memory, semaphores and message
queues as well as POSIX shared memory and message
queues. Traditionally SysV and POSIX IPC had no life-cycle
limits, with this functionality this is corrected. This may
be turned off using the RemoveIPC= switch of logind.conf.

* The systemd-machine-id-setup and tmpfiles tools gained a
--root= switch to operate on a specific root directory,
instead of /.

* journald can now forward logged messages to the TTYs of all
logged in users ("wall"). This is the default for all
emergency messages now.

* A new tool systemd-journal-remote has been added to stream
journal log messages across the network.

* /sys/fs/cgroup/ is now mounted read-only after all cgroup
controller trees are mounted into it. Note that the
directories mounted beneath it are not read-only. This is a
security measure and is particularly useful because glibc
actually includes a search logic to pick any tmpfs it can
find to implement shm_open() if /dev/shm is not available
(which it might very well be in namespaced setups).

* machinectl gained a new "poweroff" command to cleanly power
down a local OS container.

* The PrivateDevices= unit file setting will now also drop the
CAP_MKNOD capability from the capability bound set, and
imply DevicePolicy=closed.

* PrivateDevices=, PrivateNetwork= and PrivateTmp= is now used
comprehensively on all long-running systemd services where
this is appropriate.

* systemd-udevd will now run in a disassociated mount
namespace. To mount directories from udev rules make sure to
pull in mount units via SYSTEMD_WANTS properties.

* The kdbus support gained support for uploading policy into
the kernel. sd-bus gained support for creating "monitoring"
connections that can eavesdrop into all bus communication
for debugging purposes.

* Timestamps may now be specified in seconds since the UNIX
epoch Jan 1st, 1970 by specifying "@" followed by the value
in seconds.

* Native tcpwrap support in systemd has been removed. tcpwrap
is old code, not really maintained anymore and has serious
shortcomings, and better options such as firewalls
exist. For setups that require tcpwrap usage, please
consider invoking your socket-activated service via tcpd,
like on traditional inetd.

* A new system.conf configuration option
DefaultTimerAccuracySec= has been added that controls the
default AccuracySec= setting of .timer units.

* Timer units gained a new WakeSystem= switch. If enabled
timers configured this way will cause the system to resume
from system suspend (if the system supports that, which most
do these days).

* Timer units gained a new Persistent= switch. If enabled
timers configured this way will save to disk when they have
been last triggered. This information is then used on next
reboot to possible execute overdue timer events, that
couldn't take place because the system was powered off. This
enables simple anacron-like behaviour for timer units.

* systemctl's "list-timers" will now also list the time a
timer unit was last triggered in addition to the next time
it will be triggered.

* systemd-networkd will now assign predictable IPv4LL
addresses to its local interfaces.

Contributions from: Brandon Philips, Daniel Buch, Daniel Mack,
Dave Reisner, David Herrmann, Gerd Hoffmann, Greg
Kroah-Hartman, Hendrik Brueckner, Jason St. John, Josh
Triplett, Kay Sievers, Lennart Poettering, Marc-Antoine
Perennou, Michael Marineau, Michael Olbrich, Miklos Vajna,
Patrik Flykt, poma, Sebastian Thorarensen, Thomas Bächler,
Thomas Hindoe Paaboel Andersen, Tomasz Torcz, Tom Gundersen,
Umut Tezduyar Lindskog, Wieland Hoffmann, Zbigniew
Jędrzejewski-Szmek

-- Berlin, 2014-03-25
Stephan Raue
2014-03-26 00:45:45 UTC
Permalink
Hi,

systemd-212 breaks if we run autoreconf before configuring and building
with:

autoreconf: running:
/home/stephan/projects/openelec-master/build.OpenELEC-Generic.x86_64-devel/toolchain/bin/automake
--add-missing --copy --force-missing
Makefile.am:36: warning: user target '.PRECIOUS' defined here ...
/home/stephan/projects/openelec-master/build.OpenELEC-Generic.x86_64-devel/toolchain/share/automake-1.14/am/configure.am:
... overrides Automake target '.PRECIOUS' defined here
docs/gtk-doc.make:270: error: HAVE_GTK_DOC does not appear in AM_CONDITIONAL
docs/gudev/Makefile.am:98: 'docs/gtk-doc.make' included from here
docs/gtk-doc.make:270: error: HAVE_GTK_DOC does not appear in AM_CONDITIONAL
docs/libudev/Makefile.am:92: 'docs/gtk-doc.make' included from here
autoreconf:
/home/stephan/projects/openelec-master/build.OpenELEC-Generic.x86_64-devel/toolchain/bin/automake
failed with exit status: 1


even if there is no change in docs/gtk-doc.make between 211 and 212 the
files differs in the tarball. using this patch:
https://github.com/OpenELEC/OpenELEC.tv/blob/ae1cb224141c8e7b179619285333fc0dc741b0ac/packages/sysutils/systemd/patches/systemd-212-GTK_DOC.patch

fixes the problem here. (note, we dont build with gtk support and dont
have any gtk devel packages installed)

greetings

Stephan
Post by Kay Sievers
http://www.freedesktop.org/software/systemd/systemd-212.tar.xz
* When restoring the screen brightness at boot, stay away from
the darkest setting or from the lowest 5% of the available
range, depending on which is the larger value of both. This
should effectively protect the user from rebooting into a
black screen, should the brightness have been set to minimum
by accident.
* sd-login gained a new sd_machine_get_class() call to
determine the class ("vm" or "container") of a machine
registered with machined.
* sd-login gained new calls
sd_peer_get_{session,owner_uid,unit,user_unit,slice,machine_name}(),
to query the identity of the peer of a local AF_UNIX
connection. They operate similar to their sd_pid_get_xyz()
counterparts.
* PID 1 will now maintain a system-wide system state engine
with the states "starting", "running", "degraded",
"maintenance", "stopping". These states are bound to system
startup, normal runtime, runtime with at least one failed
service, rescue/emergency mode and system shutdown. This
state is shown in the "systemctl status" output when no unit
name is passed. It is useful to determine system state, in
particularly when doing so for many systems or containers at
once.
* A new command "list-machines" has been added to "systemctl"
that lists all local OS containers and shows their system
state (see above), if systemd runs inside of them.
* systemctl gained a new "-r" switch to recursively enumerate
units on all local containers, when used with the
"list-unit" command (which is the default one that is
executed when no parameters are specified).
* The GPT automatic partition discovery logic will now honour
two GPT partition flags: one may be set on a partition to
cause it to be mounted read-only, and the other may be set
on a partition to ignore it during automatic discovery.
* Two new GPT type UUIDs have been added for automatic root
partition discovery, for 32bit and 64bit ARM. This is not
particularly useful for discovering the root directory on
these architectures during bare-metal boots (since UEFI is
not common there), but still very useful to allow booting of
ARM disk images in nspawn with the -i option.
* MAC addresses of interfaces created with nspawn's
--network-interface= switch will now be generated from the
machine name, and thus be stable between multiple invocations
of the container.
* logind will now automatically remove all IPC objects owned
by a user if she or he fully logs out. This makes sure that
users who are logged out cannot continue to consume IPC
resources. This covers SysV memory, semaphores and message
queues as well as POSIX shared memory and message
queues. Traditionally SysV and POSIX IPC had no life-cycle
limits, with this functionality this is corrected. This may
be turned off using the RemoveIPC= switch of logind.conf.
* The systemd-machine-id-setup and tmpfiles tools gained a
--root= switch to operate on a specific root directory,
instead of /.
* journald can now forward logged messages to the TTYs of all
logged in users ("wall"). This is the default for all
emergency messages now.
* A new tool systemd-journal-remote has been added to stream
journal log messages across the network.
* /sys/fs/cgroup/ is now mounted read-only after all cgroup
controller trees are mounted into it. Note that the
directories mounted beneath it are not read-only. This is a
security measure and is particularly useful because glibc
actually includes a search logic to pick any tmpfs it can
find to implement shm_open() if /dev/shm is not available
(which it might very well be in namespaced setups).
* machinectl gained a new "poweroff" command to cleanly power
down a local OS container.
* The PrivateDevices= unit file setting will now also drop the
CAP_MKNOD capability from the capability bound set, and
imply DevicePolicy=closed.
* PrivateDevices=, PrivateNetwork= and PrivateTmp= is now used
comprehensively on all long-running systemd services where
this is appropriate.
* systemd-udevd will now run in a disassociated mount
namespace. To mount directories from udev rules make sure to
pull in mount units via SYSTEMD_WANTS properties.
* The kdbus support gained support for uploading policy into
the kernel. sd-bus gained support for creating "monitoring"
connections that can eavesdrop into all bus communication
for debugging purposes.
* Timestamps may now be specified in seconds since the UNIX
in seconds.
* Native tcpwrap support in systemd has been removed. tcpwrap
is old code, not really maintained anymore and has serious
shortcomings, and better options such as firewalls
exist. For setups that require tcpwrap usage, please
consider invoking your socket-activated service via tcpd,
like on traditional inetd.
* A new system.conf configuration option
DefaultTimerAccuracySec= has been added that controls the
default AccuracySec= setting of .timer units.
* Timer units gained a new WakeSystem= switch. If enabled
timers configured this way will cause the system to resume
from system suspend (if the system supports that, which most
do these days).
* Timer units gained a new Persistent= switch. If enabled
timers configured this way will save to disk when they have
been last triggered. This information is then used on next
reboot to possible execute overdue timer events, that
couldn't take place because the system was powered off. This
enables simple anacron-like behaviour for timer units.
* systemctl's "list-timers" will now also list the time a
timer unit was last triggered in addition to the next time
it will be triggered.
* systemd-networkd will now assign predictable IPv4LL
addresses to its local interfaces.
Contributions from: Brandon Philips, Daniel Buch, Daniel Mack,
Dave Reisner, David Herrmann, Gerd Hoffmann, Greg
Kroah-Hartman, Hendrik Brueckner, Jason St. John, Josh
Triplett, Kay Sievers, Lennart Poettering, Marc-Antoine
Perennou, Michael Marineau, Michael Olbrich, Miklos Vajna,
Patrik Flykt, poma, Sebastian Thorarensen, Thomas Bächler,
Thomas Hindoe Paaboel Andersen, Tomasz Torcz, Tom Gundersen,
Umut Tezduyar Lindskog, Wieland Hoffmann, Zbigniew
Jędrzejewski-Szmek
-- Berlin, 2014-03-25
_______________________________________________
systemd-devel mailing list
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Kay Sievers
2014-03-26 01:16:26 UTC
Permalink
Post by Stephan Raue
systemd-212 breaks if we run autoreconf before configuring and building
/home/stephan/projects/openelec-master/build.OpenELEC-Generic.x86_64-devel/toolchain/bin/automake
--add-missing --copy --force-missing
Makefile.am:36: warning: user target '.PRECIOUS' defined here ...
... overrides Automake target '.PRECIOUS' defined here
docs/gtk-doc.make:270: error: HAVE_GTK_DOC does not appear in AM_CONDITIONAL
docs/gudev/Makefile.am:98: 'docs/gtk-doc.make' included from here
docs/gtk-doc.make:270: error: HAVE_GTK_DOC does not appear in AM_CONDITIONAL
docs/libudev/Makefile.am:92: 'docs/gtk-doc.make' included from here
/home/stephan/projects/openelec-master/build.OpenELEC-Generic.x86_64-devel/toolchain/bin/automake
failed with exit status: 1
Have you tried passing --disable-gtk-doc to configure? Check ./configure --help.
Post by Stephan Raue
even if there is no change in docs/gtk-doc.make between 211 and 212 the
https://github.com/OpenELEC/OpenELEC.tv/blob/ae1cb224141c8e7b179619285333fc0dc741b0ac/packages/sysutils/systemd/patches/systemd-212-GTK_DOC.patch
This file in not in git, and cannot be patched upstream, it is added
by gtk-doc itself.
Post by Stephan Raue
fixes the problem here. (note, we dont build with gtk support and dont have
any gtk devel packages installed)
It's just a common html doc generator, used for libudev's and gudev's
docs, there is no gtk code in systemd.

http://www.freedesktop.org/software/systemd/libudev/index.html

Kay
Stephan Raue
2014-03-26 01:37:21 UTC
Permalink
Post by Kay Sievers
Post by Stephan Raue
systemd-212 breaks if we run autoreconf before configuring and building
/home/stephan/projects/openelec-master/build.OpenELEC-Generic.x86_64-devel/toolchain/bin/automake
--add-missing --copy --force-missing
Makefile.am:36: warning: user target '.PRECIOUS' defined here ...
... overrides Automake target '.PRECIOUS' defined here
docs/gtk-doc.make:270: error: HAVE_GTK_DOC does not appear in AM_CONDITIONAL
docs/gudev/Makefile.am:98: 'docs/gtk-doc.make' included from here
docs/gtk-doc.make:270: error: HAVE_GTK_DOC does not appear in AM_CONDITIONAL
docs/libudev/Makefile.am:92: 'docs/gtk-doc.make' included from here
/home/stephan/projects/openelec-master/build.OpenELEC-Generic.x86_64-devel/toolchain/bin/automake
failed with exit status: 1
Have you tried passing --disable-gtk-doc to configure? Check ./configure --help.
yes we are building with --disable-gtk-doc
see:
https://github.com/OpenELEC/OpenELEC.tv/blob/master/packages/sysutils/systemd/package.mk#L41

but the problem is not at configure time, we do a autoreconf before
configuring for every package
Post by Kay Sievers
Post by Stephan Raue
even if there is no change in docs/gtk-doc.make between 211 and 212 the
https://github.com/OpenELEC/OpenELEC.tv/blob/ae1cb224141c8e7b179619285333fc0dc741b0ac/packages/sysutils/systemd/patches/systemd-212-GTK_DOC.patch
This file in not in git, and cannot be patched upstream, it is added
by gtk-doc itself.
yes but its part of the tarball, and it seems to be wrong (HAVE_GTK_DOC
vs. ENABLE_GTK_DOC) - at least if we compare the file from 211 with the
one from 212.
Kay Sievers
2014-03-26 01:40:21 UTC
Permalink
Post by Stephan Raue
Post by Kay Sievers
Post by Stephan Raue
systemd-212 breaks if we run autoreconf before configuring and building
/home/stephan/projects/openelec-master/build.OpenELEC-Generic.x86_64-devel/toolchain/bin/automake
--add-missing --copy --force-missing
Makefile.am:36: warning: user target '.PRECIOUS' defined here ...
... overrides Automake target '.PRECIOUS' defined here
docs/gtk-doc.make:270: error: HAVE_GTK_DOC does not appear in AM_CONDITIONAL
docs/gudev/Makefile.am:98: 'docs/gtk-doc.make' included from here
docs/gtk-doc.make:270: error: HAVE_GTK_DOC does not appear in AM_CONDITIONAL
docs/libudev/Makefile.am:92: 'docs/gtk-doc.make' included from here
/home/stephan/projects/openelec-master/build.OpenELEC-Generic.x86_64-devel/toolchain/bin/automake
failed with exit status: 1
Have you tried passing --disable-gtk-doc to configure? Check ./configure --help.
yes we are building with --disable-gtk-doc
https://github.com/OpenELEC/OpenELEC.tv/blob/master/packages/sysutils/systemd/package.mk#L41
but the problem is not at configure time, we do a autoreconf before
configuring for every package
Post by Kay Sievers
Post by Stephan Raue
even if there is no change in docs/gtk-doc.make between 211 and 212 the
https://github.com/OpenELEC/OpenELEC.tv/blob/ae1cb224141c8e7b179619285333fc0dc741b0ac/packages/sysutils/systemd/patches/systemd-212-GTK_DOC.patch
This file in not in git, and cannot be patched upstream, it is added
by gtk-doc itself.
yes but its part of the tarball, and it seems to be wrong (HAVE_GTK_DOC vs.
ENABLE_GTK_DOC) - at least if we compare the file from 211 with the one from
212.
It might be a change in upstream gtk-doc, I don't know, I built the
tarball with:
gtk-doc-1.20-1.fc21.noarch
installed, maybe something has change there, we need to find out ...

Kay
Kay Sievers
2014-03-26 02:12:28 UTC
Permalink
Post by Kay Sievers
Post by Stephan Raue
Post by Kay Sievers
Post by Stephan Raue
systemd-212 breaks if we run autoreconf before configuring and building
/home/stephan/projects/openelec-master/build.OpenELEC-Generic.x86_64-devel/toolchain/bin/automake
--add-missing --copy --force-missing
Makefile.am:36: warning: user target '.PRECIOUS' defined here ...
... overrides Automake target '.PRECIOUS' defined here
docs/gtk-doc.make:270: error: HAVE_GTK_DOC does not appear in AM_CONDITIONAL
docs/gudev/Makefile.am:98: 'docs/gtk-doc.make' included from here
docs/gtk-doc.make:270: error: HAVE_GTK_DOC does not appear in AM_CONDITIONAL
docs/libudev/Makefile.am:92: 'docs/gtk-doc.make' included from here
/home/stephan/projects/openelec-master/build.OpenELEC-Generic.x86_64-devel/toolchain/bin/automake
failed with exit status: 1
Have you tried passing --disable-gtk-doc to configure? Check ./configure --help.
yes we are building with --disable-gtk-doc
https://github.com/OpenELEC/OpenELEC.tv/blob/master/packages/sysutils/systemd/package.mk#L41
but the problem is not at configure time, we do a autoreconf before
configuring for every package
Post by Kay Sievers
Post by Stephan Raue
even if there is no change in docs/gtk-doc.make between 211 and 212 the
https://github.com/OpenELEC/OpenELEC.tv/blob/ae1cb224141c8e7b179619285333fc0dc741b0ac/packages/sysutils/systemd/patches/systemd-212-GTK_DOC.patch
This file in not in git, and cannot be patched upstream, it is added
by gtk-doc itself.
yes but its part of the tarball, and it seems to be wrong (HAVE_GTK_DOC vs.
ENABLE_GTK_DOC) - at least if we compare the file from 211 with the one from
212.
It might be a change in upstream gtk-doc, I don't know, I built the
gtk-doc-1.20-1.fc21.noarch
installed, maybe something has change there, we need to find out ...
Hmm, *seems* to work fine here with the tarball and without gtk-doc installed:

$ autoreconf -v
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal -I m4 ${ACLOCAL_FLAGS}
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not running libtoolize: --install not given
autoreconf: running: /usr/bin/autoconf
autoreconf: running: /usr/bin/autoheader
autoreconf: running: automake --no-force
Makefile.am:36: warning: user target '.PRECIOUS' defined here ...
/usr/share/automake-1.14/am/configure.am: ... overrides Automake
target '.PRECIOUS' defined here
autoreconf: Leaving directory `.'

$ ./configure
...
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for gtk-doc... no
configure: WARNING:
You will not be able to create source packages with 'make dist'
because gtk-doc >= 1.18 is not found.
checking for gtkdoc-check... no
checking for gtkdoc-check... no
checking for gtkdoc-rebase... no
checking for gtkdoc-mkpdf... no
checking whether to build gtk-doc documentation... no
checking for GTKDOC_DEPS... yes
checking for gobject-introspection... yes
checking for strings... strings
checking for gperf... gperf
checking if gcc -std=gnu99 supports flag -pipe in envvar CFLAGS... yes
...

Kay
Stephan Raue
2014-03-26 02:25:39 UTC
Permalink
Post by Kay Sievers
Post by Kay Sievers
Post by Stephan Raue
Post by Kay Sievers
Post by Stephan Raue
systemd-212 breaks if we run autoreconf before configuring and building
/home/stephan/projects/openelec-master/build.OpenELEC-Generic.x86_64-devel/toolchain/bin/automake
--add-missing --copy --force-missing
Makefile.am:36: warning: user target '.PRECIOUS' defined here ...
... overrides Automake target '.PRECIOUS' defined here
docs/gtk-doc.make:270: error: HAVE_GTK_DOC does not appear in AM_CONDITIONAL
docs/gudev/Makefile.am:98: 'docs/gtk-doc.make' included from here
docs/gtk-doc.make:270: error: HAVE_GTK_DOC does not appear in AM_CONDITIONAL
docs/libudev/Makefile.am:92: 'docs/gtk-doc.make' included from here
/home/stephan/projects/openelec-master/build.OpenELEC-Generic.x86_64-devel/toolchain/bin/automake
failed with exit status: 1
Have you tried passing --disable-gtk-doc to configure? Check ./configure --help.
yes we are building with --disable-gtk-doc
https://github.com/OpenELEC/OpenELEC.tv/blob/master/packages/sysutils/systemd/package.mk#L41
but the problem is not at configure time, we do a autoreconf before
configuring for every package
Post by Kay Sievers
Post by Stephan Raue
even if there is no change in docs/gtk-doc.make between 211 and 212 the
https://github.com/OpenELEC/OpenELEC.tv/blob/ae1cb224141c8e7b179619285333fc0dc741b0ac/packages/sysutils/systemd/patches/systemd-212-GTK_DOC.patch
This file in not in git, and cannot be patched upstream, it is added
by gtk-doc itself.
yes but its part of the tarball, and it seems to be wrong (HAVE_GTK_DOC vs.
ENABLE_GTK_DOC) - at least if we compare the file from 211 with the one from
212.
It might be a change in upstream gtk-doc, I don't know, I built the
gtk-doc-1.20-1.fc21.noarch
installed, maybe something has change there, we need to find out ...
$ autoreconf -v
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal -I m4 ${ACLOCAL_FLAGS}
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not running libtoolize: --install not given
autoreconf: running: /usr/bin/autoconf
autoreconf: running: /usr/bin/autoheader
autoreconf: running: automake --no-force
Makefile.am:36: warning: user target '.PRECIOUS' defined here ...
/usr/share/automake-1.14/am/configure.am: ... overrides Automake
target '.PRECIOUS' defined here
autoreconf: Leaving directory `.'
$ ./configure
...
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for gtk-doc... no
You will not be able to create source packages with 'make dist'
because gtk-doc >= 1.18 is not found.
checking for gtkdoc-check... no
checking for gtkdoc-check... no
checking for gtkdoc-rebase... no
checking for gtkdoc-mkpdf... no
checking whether to build gtk-doc documentation... no
checking for GTKDOC_DEPS... yes
checking for gobject-introspection... yes
checking for strings... strings
checking for gperf... gperf
checking if gcc -std=gnu99 supports flag -pipe in envvar CFLAGS... yes
...
Kay
just found the commit in gtk-doc which causes this:

https://git.gnome.org/browse/gtk-doc/commit/?id=cf5a3002fcf4f45331537fd6c4990725827b1f59

to "fix"

http://bugzilla.gnome.org/show_bug.cgi?id=666509

see post #15 there ...

hmmm i will rebuild the whole distro and check if maybe another
gtk-doc.m4 file is used instead the one from the m4 folder...
Colin Walters
2014-03-31 13:07:48 UTC
Permalink
On Tue, Mar 25, 2014 at 8:45 PM, Stephan Raue
Post by Stephan Raue
docs/gtk-doc.make:270: error: HAVE_GTK_DOC does not appear in
AM_CONDITIONAL
You might try:

https://git.gnome.org/browse/gtk-doc-stub

It's used by OpenEmbedded:

https://github.com/openembedded/oe-core/tree/master/meta/recipes-gnome/gtk-doc-stub

And gnome-continuous.
Thomas Bächler
2014-03-28 09:22:44 UTC
Permalink
Post by Kay Sievers
* Timer units gained a new Persistent= switch. If enabled
timers configured this way will save to disk when they have
been last triggered. This information is then used on next
reboot to possible execute overdue timer events, that
couldn't take place because the system was powered off. This
enables simple anacron-like behaviour for timer units.
How do these timers interact with suspending or hibernation? If I
suspend the system and resume after the timer should have elapsed, the
timer won't be restarted. Will it still trigger on resume?

(Use-case: A system that rarely reboots and has a timer set daily at
midnight. The user always suspends the system at 11 and resumes it in
the morning.)

Another question: The documentation says that the timer will trigger
"immediately" when it is started. Is this accurate or is there some
holdoff time?
Lennart Poettering
2014-04-10 23:50:23 UTC
Permalink
Post by Thomas Bächler
Post by Kay Sievers
* Timer units gained a new Persistent= switch. If enabled
timers configured this way will save to disk when they have
been last triggered. This information is then used on next
reboot to possible execute overdue timer events, that
couldn't take place because the system was powered off. This
enables simple anacron-like behaviour for timer units.
How do these timers interact with suspending or hibernation? If I
suspend the system and resume after the timer should have elapsed, the
timer won't be restarted. Will it still trigger on resume?
Timers are dispatched as soon as systemd is scheduled and the current
time is >= the time configured for the timer. If the system is suspended
for a longer time, and thus systemd doesnt get scheduled then the
dispatching is hnce simply delayed until the next resume.
Post by Thomas Bächler
(Use-case: A system that rarely reboots and has a timer set daily at
midnight. The user always suspends the system at 11 and resumes it in
the morning.)
In that case the timer will be dispatched immediately after resume.
Post by Thomas Bächler
Another question: The documentation says that the timer will trigger
"immediately" when it is started. Is this accurate or is there some
holdoff time?
Immediately is correct.

Lennart
--
Lennart Poettering, Red Hat
Continue reading on narkive:
Loading...