Re: [systemd-devel] [PATCH] travis: Add a travis.yml for doing CI after commits
On Wed, Aug 14, 2013 at 02:48:07PM -0700, David Strauss wrote: The CI I maintain [1] for systemd is certainly one alternative that continues to be in production. I'd like to get more test automation going, but it's not like TravisCI was running any tests beyond a successful build. I plan to continue maintaining the Jenkins CI, if Please take a look at the .travis.yml file. It executes make check and make distcheck. Maybe on your jenkins setup you try these two commands as well and check how far you get? holger ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] travis: Add a travis.yml for doing CI after commits
On Wed, Aug 14, 2013 at 11:15:35PM +0200, Kay Sievers wrote: I temporarily switched it off now. thanks for the heads up. Maybe someone has an idea, or an alternative. If David starts to execute make check make distcheck there is probably nothing travis-ci provides that David's setup doesn't. As an alternative I can play catch-up and provide/build additional deps. holger ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH 0/3] Z-Shell fixes
On Wed, Aug 14, 2013 at 10:09:13PM -0500, William Giokas wrote: Just a redo of the three un-merged patches on the ml at the moment. Nothing really different, just rebased. William Giokas (3): zsh_completion: Allow specifying multiple arguments -- Just rebased. zsh_completion: machinectl properties can be stacked zsh_completion: Remove ctls function from _systemd Makefile.am | 1 + shell-completion/zsh/_machinectl | 2 +- shell-completion/zsh/_systemctl | 16 +++- shell-completion/zsh/_systemd | 174 -- shell-completion/zsh/_systemd-delta | 15 +++ shell-completion/zsh/_systemd-inhibit | 8 +- 6 files changed, 118 insertions(+), 98 deletions(-) create mode 100644 shell-completion/zsh/_systemd-delta Applied, thanks. Zbyszek ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [RFC] Integrating an early-boot service in a blocking way?
Hi, the debian-live people have approached me and want to experiment with systemd. One of the things they need to have is running a service called live-config.service, but the issue is that it needs to run in early boot, even before udev. We thought of maybe creating a custom target, but it would need to run before basic.target and I don’t see a good way of doing that. Do you have any ideas on how to solve this (and making live-config work in a different way does not count :))? Thanks! -- Best regards, Michael ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] Please pass 'fsck.mode=force' on the kernel command line rather than creating /forcefsck on the root file system
Please pass 'fsck.mode=force' on the kernel command line rather than creating /forcefsck on the root file system please drop this deprectaion, it is disturbing and useless if you want a forced fsck for *whatever* reason you do *not* want to edit the grub-config and need to remove it after pass to prevent on the next boot a unintented fsck nor do you want to struggle with the boot-menu on remote-machines this warning is pointless and useless signature.asc Description: OpenPGP digital signature ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Please pass 'fsck.mode=force' on the kernel command line rather than creating /forcefsck on the root file system
On Thu, Aug 15, 2013 at 11:04 PM, Reindl Harald h.rei...@thelounge.net wrote: Please pass 'fsck.mode=force' on the kernel command line rather than creating /forcefsck on the root file system please drop this deprectaion, it is disturbing and useless it is afaik just a step towards read-only / if you want a forced fsck for *whatever* reason you do *not* want to edit the grub-config and need to remove it after pass to prevent on the next boot a unintented fsck nor do you want to struggle with the boot-menu on remote-machines this warning is pointless and useless ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Please pass 'fsck.mode=force' on the kernel command line rather than creating /forcefsck on the root file system
On 16 Aug 2013 05:05, Reindl Harald h.rei...@thelounge.net wrote: Please pass 'fsck.mode=force' on the kernel command line rather than creating /forcefsck on the root file system please drop this deprectaion, it is disturbing and useless if you want a forced fsck for *whatever* reason you do *not* want to edit the grub-config and need to remove it after pass to prevent on the next boot a unintented fsck nor do you want to struggle with the boot-menu on remote-machines this warning is pointless and useless If there is a need to fsck, then writing to the root fs is probably the last thing you want to do, which is why we don't want to promote this mechanism. Tom ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
