(no subject)
-- Somos Wells Fargo Finance Company, tenemos compañía en todo el mundo, como Estados Unidos, Reino Unido, Asia continente, Europa. Ofrecemos préstamo @ tasa de interés del 3% a partir de una serie de mínimo de 10.000,00 euros, dólares y libras a un máximo de 500,000,000.00euro, dólares y libras. ¿necesita un préstamo de Navidad urgentes amablemente aplicar ahora. Nombre completo: país: Cantidad necesaria: duración: número de teléfono móvil nos lleva días sólo 4working que le conceda este préstamo sin ninguna cuota ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#732209: dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied.
Hi, BTW, this only happens with GNOME sessions. With other window managers (e.g. LXDE, Openbox) it does *not*. Therefore, I do not think it's a systemd bug, rather it's related to GNOME. Do you agree to reassign this bug against either the 'gnome-session' or the 'gnome-shell' package? No, I don't agree. I can reproduce it 100% in MATE desktop environment and also in Cinnamon, see [1]. I'm actually thinking of merging that bug report with this one. Please read the comments from Linas Vepstas there, they confirm that it's not a desktop environment or a text editor itself that causes it. Also, systemd had been messing up the ownership of /run/user/1000/dconf/user in the past, see [2]. [1] https://bugs.debian.org/766464 [2] https://bugs.debian.org/731300 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#771707: Unbounded journal~ file accumulation
Control: tag -1 pending Control: notfound -1 217-2 Hey Keith, Moyer, Keith [2014-12-01 19:44 +]: http://cgit.freedesktop.org/systemd/systemd/commit/?id=3bfd4e0c6341b0ef946d2198f089743fa99e0a97 Please consider pulling in this trivial patch. Pulled into master (for unstable/testing), thanks for pointing out! This is already fixed in 217-2 through the v217-stable series. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: tagging 771122
Processing commands for cont...@bugs.debian.org: tags 771122 + pending Bug #771122 [systemd] restarting the journal breaks other services Bug #771947 [systemd] systemd: Desktop services not working after systemd upgrade, until a reboot is done: enabling WiFi in NetworkManager, reboot Added tag(s) pending. Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 771122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771122 771947: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771947 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#771122: restarting the journal breaks other services
Am 04.12.2014 um 15:20 schrieb Martin Pitt: Michael Biebl [2014-11-27 0:17 +0100]: Maybe the least invasive change is, to move the systemd-journald restart into the if dpkg --compare-versions $2 lt-nl 215-3; then fi This is the typical between rock and hard place situation. I agree that we should stop restarting it by default, but we probably have to for upgrades from wheezy. (Proably/hopefully most wheezy users don't run systemd yet, so it shouldn't matter that much ). So I don't know a better solution than the above = 215-3 version guard either; is everyone ok with going that route? It was pointed out, that apparently for network-manager there is a patch available, which works around the issue and better deals with a journald restart. So the most prominent breakage is probably fixed by that. That said, there might be other services, which we don't know of currently, which might be affected and I feal a bit uneasy doing the restart against upstreams recommendation. So I'm leaning towards doing the restart only once during the dist-upgrade (i.e. what Martin committed in the mean time to git) I still want to upload the fix for NM in addition to that. Imho it makes sense to do both. Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758533#44 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#765542: systemd: man systemd refers to obsolete command 'systemctl dump'
Control: tags -1 = upstream confirmed Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=87020 On Wed, 15 Oct 2014 22:39:35 -0400 Dominique Brazziel dbrazz...@snet.net wrote: Package: systemd Version: 215-5+b1 Severity: minor Tags: patch The man page refers to the 'dump' function of systemctl in the SIGUSR2 explanation. The dump function has been moved to 'systemd-analyze dump'. Patch attached to change the wording. Thanks for your report. I have forwarded it upstream. Saludos ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: Re: systemd: man systemd refers to obsolete command 'systemctl dump'
Processing control commands: tags -1 = upstream confirmed Bug #765542 [systemd] systemd: man systemd refers to obsolete command 'systemctl dump' Added tag(s) upstream and confirmed; removed tag(s) patch. forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=87020 Bug #765542 [systemd] systemd: man systemd refers to obsolete command 'systemctl dump' Set Bug forwarded-to-address to 'https://bugs.freedesktop.org/show_bug.cgi?id=87020'. -- 765542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#771122: restarting the journal breaks other services
Michael Biebl [2014-12-04 23:13 +0100]: I still want to upload the fix for NM in addition to that. Imho it makes sense to do both. Yes, absolutely. There might be other reasons why journald restarts, because the admin did it, or there's a crash. This sounds appropriate and safe enough for jessie to me. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#771122: restarting the journal breaks other services
Petr Baudis [2014-12-04 16:16 +0100]: Can't this be handled like a glibc (nss) upgrade is, using a debconf prompt that suggests restarting other services recursively? In theory, anything is possible :-) However, that first assumes that all the affected services actually support that properly; e. g. it's not at all obvious how to start NetworkManager's DHCP client from outside without hardcoding a lot of knowledge about NM's internal package structure. And restarting the entire NetworkManager is too disruptive. TBH I don't think we can aim for this complexity in Jessie; it's very unlikely that we get that right at the first or second shot. Even if infeasible, it would be good to add a debconf prompt to systemd restarts triggered by upgrades if they are known to break stuff; but maybe that's a given? My personal opinion is that the fewer unbreak my machine debconf prompts we have, the better; in many cases like these they are just a poor excuse. It's like we as the developers don't know what to do here, so we pushed this question to the user who will of course have absolutely no clue about it; but we can then shift the blame to the user if stuff breaks. If we can't safely restart the journal, let's just not do it. There are some plans upstream how to make it possible (very far away from easy though), so until then let's just stay at the safe side. Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: Re: Bug#765870: systemd-logind brings system to knees with RAM consumption
Processing control commands: severity -1 important Bug #765870 [systemd] systemd-logind brings system to knees with RAM consumption Severity set to 'important' from 'grave' -- 765870: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#765870: systemd-logind brings system to knees with RAM consumption
Control: severity -1 important John Goerzen [2014-11-29 16:57 -0600]: I have not yet had the chance to migrate this system to boot with systemd. The problem is also not yet resolved. However, the logind processes now consume far less RAM: We haven't heard about this problem from other reporters, John said the problem became a lot smaller wiht the recent versions of systemd-shim, and there is no evidence that this is even a problem when running under systemd. So if you don't mind I downgrade this to important, at least as long as it's moreinfo/unreproducible. Thanks! Margin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#738319: marked as done (systemd: Patch to bootstrap without gobject-introspection or cryptsetup)
Your message dated Fri, 5 Dec 2014 07:31:51 +0100 with message-id 20141205063151.ga32...@piware.de and subject line Re: Bug#738319: systemd: Patch to bootstrap without gobject-introspection or cryptsetup has caused the Debian Bug report #738319, regarding systemd: Patch to bootstrap without gobject-introspection or cryptsetup to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 738319: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: systemd Version: 204-6 Severity: wishlist Tags: patch The attached patch implements a stage1 bootstrap for systemd to resolve a couple Build-Depends cycles: systemd Build-Depends on libcryptsetup-dev, but lvm2 Build-Depends on libudev- dev. systemd Build-Depends on gobject-introspection; gobject-introspection Build- Depends on libcairo2-dev; cairo Build-Depends on libgl1-mesa-dev; and mesa Build-Depends on libudev-dev. -- Daniel Schepler diff -urN systemd-204.old/debian/rules systemd-204/debian/rules --- systemd-204.old/debian/rules 2013-12-31 05:39:51.0 -0800 +++ systemd-204/debian/rules 2014-02-08 21:17:55.109166636 -0800 @@ -5,6 +5,10 @@ DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) +ifneq (,$(findstring stage1,$(DEB_BUILD_PROFILES))) +BOOTSTRAP_DH_FLAGS := -Ngir1.2-gudev-1.0 -Nlibgudev-1.0-0 -Nlibgudev-1.0-dev +endif + CONFFLAGS = \ --with-rootprefix= \ --with-rootlibdir=/lib/$(DEB_HOST_MULTIARCH) \ @@ -12,13 +16,15 @@ --with-sysvrcnd-path=/etc \ --with-firmware-path=/lib/firmware \ --with-debug-shell=/bin/bash \ - --enable-libcryptsetup \ --enable-tcpwrap \ --disable-coredump \ --disable-efi \ --disable-myhostname \ --disable-vconsole \ --disable-silent-rules +ifeq (,$(findstring stage1,$(DEB_BUILD_PROFILES))) +CONFFLAGS += --enable-libcryptsetup +endif CONFFLAGS_deb = \ --enable-selinux \ @@ -80,7 +86,7 @@ rm -rf debian/install/*/etc/kernel/ find debian/install/ -name '*.la' -delete dh_install -pudev-udeb -plibudev1-udeb --sourcedir=debian/install/udeb - dh_install -Nudev-udeb -Nlibudev1-udeb --sourcedir=debian/install/deb + dh_install $(BOOTSTRAP_DH_FLAGS) -Nudev-udeb -Nlibudev1-udeb --sourcedir=debian/install/deb # install some files manually, --sourcedir makes that necessary # udev-udeb install -D --mode=755 debian/extra/udev.startup \ @@ -169,7 +175,9 @@ # files shipped by udev / bash-completion rm debian/systemd/usr/share/bash-completion/completions/udevadm # files systemd by cryptsetup +ifeq (,$(findstring stage1,$(DEB_BUILD_PROFILES))) rm debian/systemd/usr/share/man/man5/crypttab.5 +endif # files shipped by systemd rm debian/udev/lib/udev/rules.d/70-uaccess.rules rm debian/udev/lib/udev/rules.d/73-seat-late.rules @@ -202,4 +210,8 @@ dh_autoreconf debian/rules -- autoreconf %: +ifeq (,$(findstring stage1,$(DEB_BUILD_PROFILES))) dh $@ --with autoreconf,gir,python2 +else + dh $@ --with autoreconf,python2 $(BOOTSTRAP_DH_FLAGS) +endif ---End Message--- ---BeginMessage--- Version: 204-7 Daniel Schepler [2014-02-08 21:29 -0800]: The attached patch implements a stage1 bootstrap for systemd to resolve a couple Build-Depends cycles: This was applied ages ago, but the changelog forgot to close the bug: systemd (204-7) unstable; urgency=low * fix systemctl enable/disable/… error message “Failed to issue method call: No such file or directory” (Closes: #734809) * bug-script: attach instead of paste extra info with reportbug ≥ 6.5.0 (Closes: #722530) * add stage1 bootstrap support to avoid Build-Depends cycles (Thanks Daniel Schepler) * cherry-pick: order remote mounts from mountinfo before remote-fs.target (77009452cfd) (Closes: #719945) Fix CPUShares configuration option (ccd90a976dba) (Closes: #737156) fix reference in systemd-inhibit(1) (07b4b9b) (Closes: #738316) -- Michael Stapelberg stapelb...@debian.org Tue, 11 Feb 2014 23:34:42 +0100 -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)---End Message--- ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#739020: marked as done (run tests during build)
Your message dated Fri, 5 Dec 2014 07:30:03 +0100
with message-id 20141205063003.ga32...@piware.de
and subject line Re: Bug#739020: [Pkg-systemd-maintainers] Bug#739020: run
tests during build
has caused the Debian Bug report #739020,
regarding run tests during build
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
739020: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739020
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: systemd
Version: 204-7
Severity: wishlist
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu ubuntu-patch trusty
Hello,
systemd has some unit tests (with make check). Unfortunately not all
of them work in the rather restricted environment of our buildds, but
most of them do. It would be nice to at least run those, to pick up
regressions on particular architectures. Of course, over time, I
also hope that we can fix those tests upstream to work better during
package build.
The main ingredient is a patch to allow specifying a different path
for /etc/machine-id, as that does not yet usually exist (particularly,
not in buildd chroots). Upstream rejected the patch back then
(https://bugs.freedesktop.org/show_bug.cgi?id=62344), but it's rather
simple, so doesn't hurt too bad for a distro patch.
Are you interested in that for Debian? If so, I'll attach the three
git formatted patches for that (against current packaging git).
Thanks for considering,
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
From d594684c0f4ab6bc79d52b727c916e3e72d2d3be Mon Sep 17 00:00:00 2001
From: Martin Pitt martinp...@gnome.org
Date: Fri, 15 Mar 2013 08:27:43 +0100
Subject: [PATCH 1/3] Add env variable for machine ID path
During package build, in minimal chroots, or other systems which do not already
have an /etc/machine-id we get six test failures. Introduce a
$SYSTEMD_MACHINE_ID_PATH environment variable which can specify a location
other than /etc/machine-id, so that the unit tests are independent from the
environment.
https://bugs.freedesktop.org/show_bug.cgi?id=62344
---
debian/changelog| 8
src/libsystemd-id128/sd-id128.c | 6 +-
2 files changed, 13 insertions(+), 1 deletion(-)
diff --git a/debian/changelog b/debian/changelog
index 0490e3d..bd12491 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,16 @@
systemd (204-8) UNRELEASED; urgency=low
+ [ Michael Stapelberg ]
* move manpages from systemd to libsystemd-*-dev as appropriate
(Closes: #738723)
+ [ Martin Pitt ]
+ * Add env variable for machine ID path. During package build, in minimal
+chroots, or other systems which do not already have an /etc/machine-id we
+get six test failures. Introduce a $SYSTEMD_MACHINE_ID_PATH environment
+variable which can specify a location other than /etc/machine-id, so that
+the unit tests are independent from the environment.
+
-- Michael Stapelberg stapelb...@debian.org Thu, 13 Feb 2014 22:52:45 +0100
systemd (204-7) unstable; urgency=low
diff --git a/src/libsystemd-id128/sd-id128.c b/src/libsystemd-id128/sd-id128.c
index 64ddd09..47351c8 100644
--- a/src/libsystemd-id128/sd-id128.c
+++ b/src/libsystemd-id128/sd-id128.c
@@ -115,6 +115,7 @@ _public_ int sd_id128_get_machine(sd_id128_t *ret) {
ssize_t k;
unsigned j;
sd_id128_t t;
+const char *machine_id_path;
if (!ret)
return -EINVAL;
@@ -124,7 +125,10 @@ _public_ int sd_id128_get_machine(sd_id128_t *ret) {
return 0;
}
-fd = open(/etc/machine-id, O_RDONLY|O_CLOEXEC|O_NOCTTY);
+machine_id_path = getenv(SYSTEMD_MACHINE_ID_PATH);
+if (machine_id_path == NULL)
+machine_id_path = /etc/machine-id;
+fd = open(machine_id_path, O_RDONLY|O_CLOEXEC|O_NOCTTY);
if (fd 0)
return -errno;
--
1.9.rc1
From eace7af7b5a98ac26945e024f01145898f059c39 Mon Sep 17 00:00:00 2001
From: Martin Pitt martin.p...@ubuntu.com
Date: Sat, 15 Feb 2014 00:26:27 +0100
Subject: [PATCH 2/3] debian/rules: Run unit tests during package build.
Don't run them under fakeroot as that hangs some tests, and supply a local
machine id file.
---
debian/changelog | 2 ++
debian/rules | 11 +++
2 files changed, 13 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index bd12491..1722ce3 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -10,6 +10,8 @@ systemd (204-8) UNRELEASED; urgency=low
get
Bug#767410: marked as done (systemd-resolved: doesn't include local search domain from DHCP query into resolv.conf)
Your message dated Fri, 5 Dec 2014 07:33:23 +0100 with message-id 20141205063322.ga...@piware.de and subject line Re: Bug#767410: systemd-resolved: doesn't include local search domain from DHCP query into resolv.conf has caused the Debian Bug report #767410, regarding systemd-resolved: doesn't include local search domain from DHCP query into resolv.conf to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 767410: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767410 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: systemd Version: 215-5 Severity: minor Tags: upstream patch Hi Using systemd-resolved, the local searchdomain provided by the DHCP server is not added to resolv.conf, which disables FQDN completion without domain suffix. e.g.: $ ls -al /etc/resolv.conf lrwxrwxrwx 1 root root 32 Okt 17 20:00 /etc/resolv.conf - /run/systemd/resolve/resolv.conf $ cat /run/systemd/resolve/resolv.conf # This file is managed by systemd-resolved(8). Do not edit. # # Third party programs must not access this file directly, but # only through the symlink at /etc/resolv.conf. To manage # resolv.conf(5) in a different way, replace the symlink by a # static file or a different symlink. nameserver 10.0.0.1 nameserver 8.8.8.8 nameserver 8.8.4.4 # Too many DNS servers configured, the following entries may be ignored nameserver 2001:4860:4860:: nameserver 2001:4860:4860::8844 Domain name without domain suffix: $ nslookup redstone Server: 10.0.0.1 Address:10.0.0.1#53 Non-authoritative answer: *** Can't find redstone: No answer FQDN, with full (local-) domain suffix: $ nslookup redstone.lan Server: 10.0.0.1 Address:10.0.0.1#53 Name: redstone.lan Address: 10.10.7.0 This seems to have been reported upstream under https://bugs.freedesktop.org/show_bug.cgi?id=79671 and probably also https://bugs.freedesktop.org/show_bug.cgi?id=85397 The formal patch that was actually merged upstream http://cgit.freedesktop.org/systemd/systemd/commit/?id=6192b846ca0d15602e94ddb5da4420b7c60d64a5 doesn't apply easily to systemd 215, but the initially suggested patch https://bugs.freedesktop.org/attachment.cgi?id=103315 applies to current (Debian-) systemd HEAD (as of debian/215-5-14-g8178d8d) and is working for me --- old/resolv.conf +++ /etc/resolv.conf @@ -5,6 +5,7 @@ # resolv.conf(5) in a different way, replace the symlink by a # static file or a different symlink. +domain lan nameserver 10.0.0.1 nameserver 8.8.8.8 nameserver 8.8.4.4 $ nslookup redstone Server: 10.0.0.1 Address:10.0.0.1#53 Name: redstone.lan Address: 10.10.7.0 systemd-networkd configuration: $ cat /etc/systemd/network/50-br0.netdev [NetDev] Name=br0 Kind=bridge MACAddress=01:23:45:67:89:AB $ cat /etc/systemd/network/51-eth0.network [Match] Name=eth0 [Network] Bridge=br0 $ cat /etc/systemd/network/60-br0.network [Match] Name=br0 [Network] DHCP=yes Regards Stefan Lippers-Hollmann -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.18-rc2-aptosid-amd64 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-57 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1 ii libblkid1 2.25.2-2 ii libc6 2.19-12 ii libcap2 1:2.24-6 ii libcap2-bin 1:2.24-6 ii libcryptsetup4 2:1.6.6-3 ii libgcrypt20 1.6.2-4 ii libkmod218-3 ii liblzma55.1.1alpha+20120614-2 ii libpam0g1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-5 ii mount 2.25.2-2 ii sysv-rc 2.88dsf-57 ii udev215-5 ii util-linux 2.25.2-2 Versions of packages systemd recommends: ii dbus1.8.8-2 ii libpam-systemd 215-5 Versions of packages systemd suggests: pn systemd-ui none -- no debconf information signature.asc Description: This is a digitally signed message part. ---End Message--- ---BeginMessage--- Version: 217-1 Stefan Lippers-Hollmann [2014-10-30 22:25 +0100]: Using systemd-resolved, the local searchdomain provided by the DHCP server is not added to resolv.conf, which disables FQDN completion without domain suffix. The upstream patch is included in 217, which is now in experimental. Marking fixed version accordingly. Thanks,
Processed: Re: Bug#766598: systemd: help for journalctl --until option is misleading
Processing control commands: notfound -1 217-1 Bug #766598 [systemd] systemd: help for journalctl --until option is misleading Ignoring request to alter found versions of bug #766598 to the same values previously set tag -1 pending Bug #766598 [systemd] systemd: help for journalctl --until option is misleading Added tag(s) pending. -- 766598: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766598 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#734848: [Pkg-systemd-maintainers] Bug#734848: systemd: LSB initscript wrappers should also handle sockets on start/stop
Control: tag -1 -patch As the original patch needs some work, I'm removing the patch tag for now. Thanks for your work! Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#768776: systemd wakes up CIFS/network drives too early
Am 17.11.2014 um 21:59 schrieb dAgeCKo: Le 17/11/2014 14:33, intrigeri a écrit : Hi dAgeCKo, Michael Biebl wrote (09 Nov 2014 17:45:45 GMT) : Please update to the latest version in jessie (i.e. 215-5) Then boot with systemd.log_level=debug on the kernel command line and then include the output of systemd-analyze dump journalctl -al Please also attach your network configuration (e.g. /etc/network/interface, if you use ifupdown) and your /etc/fstab. Ping? Here are joined why you requested. I hope that the provided information could help you. Let me know. Thanks again for the care. Please update ifupdown to 0.7.50 and test if that fixes your problem. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: Re: Bug#734848: [Pkg-systemd-maintainers] Bug#734848: systemd: LSB initscript wrappers should also handle sockets on start/stop
Processing control commands: tag -1 -patch Bug #734848 [systemd] systemd: LSB initscript wrappers should also handle sockets on start/stop Removed tag(s) patch. -- 734848: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=734848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#766598: systemd: help for journalctl --until option is misleading
Control: notfound -1 217-1 Control: tag -1 pending Hello, Santiago Vila [2014-10-24 11:46 +0200]: --since=DATE Start showing entries on or newer than the specified date --until=DATE Stop showing entries on or older than the specified date This is a little bit confusing. This is fixed in experimental, marking affected versions accordingly. This is a zero risk fix for jessie, so I cherry-picked the patch into master for unstable/testing. Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
