delta/systemd.git - github.com: systemd/systemd.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	semaphore: switch to another keyserver	Evgeny Vereshchagin	2019-09-06	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \|	lxc-create has been failing to download the image today with ``` + sudo lxc-create -n buster-amd64 -t download -- -d debian -r buster -a amd64 Setting up the GPG keyring ERROR: Unable to fetch GPG key from keyserver lxc-create: buster-amd64: lxccontainer.c: create_run_template: 1617 Failed to create container from template lxc-create: buster-amd64: tools/lxc_create.c: main: 327 Failed to create container buster-amd64 ``` Let's try another keyserver.
*	semaphore: switch back to the master branch	Evgeny Vereshchagin	2019-08-24	1	-1/+1
\|
*	tests: pass --werror to meson on Semaphore	Evgeny Vereshchagin	2019-07-25	1	-1/+1
\|
*	semaphore: avoid running autopkgtest with --apt-upgrade	Evgeny Vereshchagin	2019-07-13	1	-13/+3
\| \| \| \| \|	by getting rid of the cache and upgrading images once every time they are built from scratch.
*	semaphore: pass allow-releaseinfo-change to apt-get	Evgeny Vereshchagin	2019-07-07	1	-1/+1
\| \| \| \|	https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929248
*	Merge pull request #12519 from keszybz/man-on-demand	Yu Watanabe	2019-05-21	1	-1/+1
\|\ \| \| \| \|	Build man pages on demand only
\| *	meson: default to -Dman=false to make development quicker	Zbigniew Jędrzejewski-Szmek	2019-05-09	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	This makes the default build much quicker. If people are building systemd for packaging or actual installation, they probably need to set some more options anyway (-Ddns-servers=, -Dntp-servers=), so adding -Dman=true is not a big burden. For CIs configured locally, -Dman=true is added to restore status quo ante.
* \|	semaphore: switch to Debian experimental packaging branch	Martin Pitt	2019-05-17	1	-1/+2
\|/ \| \| \| \| \| \|	Debian unstable is frozen for the Debian 9 release, current development happens in experimental. After the release, this can be switched back to master, and the branch set through the `$BRANCH` env variable in the semaphore config.
*	semaphore: merge semaphore scripts to avoid code duplication (#12365)	Frantisek Sumsal	2019-04-24	3	-104/+111
\|
*	scripts: use 4 space indentation	Zbigniew Jędrzejewski-Szmek	2019-04-12	2	-3/+6
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	We had all kinds of indentation: 2 sp, 3 sp, 4 sp, 8 sp, and mixed. 4 sp was the most common, in particular the majority of scripts under test/ used that. Let's standarize on 4 sp, because many commandlines are long and there's a lot of nesting, and with 8sp indentation less stuff fits. 4 sp also seems to be the default indentation, so this will make it less likely that people will mess up if they don't load the editor config. (I think people often use vi, and vi has no support to load project-wide configuration automatically. We distribute a .vimrc file, but it is not loaded by default, and even the instructions in it seem to discourage its use for security reasons.) Also remove the few vim config lines that were left. We should either have them on all files, or none. Also remove some strange stuff like '#!/bin/env bash', yikes.
*	semaphoreci: caching and more robust creation of container image	Martin Pitt	2019-03-04	1	-20/+37
\| \| \| \| \| \| \| \| \| \| \| \|	lxc-create in semaphore sometimes fails with ERROR: Unable to fetch GPG key from keyserver Which often happens behind proxies. As the default key server is a load balancer, retry a few times. Also, cache the container image between runs, and only recreate it when it is older than a week.
*	semaphoreci: Run subset of autopkgtests in LXC (#11814)	Martin Pitt	2019-03-01	2	-27/+76
\| \| \| \| \| \| \|	Run build/test in LXC for now, as full nested QEMU is too brittle right now: https://github.com/semaphoreci/semaphore/issues/37 But this at least runs some tests. It ensures that systemd generally works in containers, as well as provides some backup results if the main Ubuntu CI is down.
*	semaphore: keep build settings in the repository	Evgeny Vereshchagin	2019-02-09	2	-0/+35
	It should make it easier to tweak them without having access to SemaphoreCI itself (I'm glad I'm an admin there now but it shouldn't be necessary to be an admin to add a couple of kludges :-)). More importantly, changes to the settings will go through review and be tested before they're applied globally potentially breaking Semaphore as it happened two days ago. I'll point Semaphore CI to these scripts once the PR is merged.