tags 763197 + patch
thanks
With the help of the old udev checks I came up with this which
properly detects my systemd and kernel incompatibilities.
It is not detecting the UEFI things though.
How about applying it?
-Mikko
diff -rup systemd-215-orig/debian/systemd.preinst
Your message dated Sat, 11 Oct 2014 10:08:52 +0200
with message-id 3169424.eqA7oPNOLs@antec
and subject line Re: Bug#764714: systemd-cron: indention error in
systemd-crontab-generator tab instead of spaces
has caused the Debian Bug report #764714,
regarding systemd-cron: indention error in
Hi,
Michael Scherer wrote (11 Oct 2014 05:51:39 GMT) :
Unfortunately, it seems the error code of aa_change_onexec is not propagated,
which is a bug ( my fault, will correct upstream ). In the mean time, I guess
we will have to use strace and/or gdb to get it and see what is going on.
I
On 11 October 2014 18:09, Michael Biebl bi...@debian.org wrote:
Am 11.10.2014 um 18:57 schrieb Dimitri John Ledkov:
Can someone from systemd experts say whether or not
systemd-udev-trigger is run before local-fs target?
That's not quite how it works.
local-fs.target is a dynamic target which
Hi,
could you please remove your local service file again, add
systemd.log_level=debug to the kernel command line, enable verbose udev
debug logging via /etc/udev/udev.conf and then after a reboot, attach
the output of
journalctl -alb
Please also attach your /etc/fstab and mention which mounts
Am 11.10.2014 um 21:17 schrieb Michael Biebl:
Please also attach your /etc/fstab and mention which mounts are btrfs
volumes which are not mounted.
nvm, I just noticed that you already did provide that file in the mean time.
--
Why is it that all of the instruments seeking intelligent life
Am 11.10.2014 um 21:53 schrieb Sebastian Oswald:
On Thu, 09 Oct 2014 19:28:48 +0200 Ansgar Burchardt ans...@debian.org
wrote:
Hi,
Sebastian Oswald sebast...@rostwald.de writes:
When trying to upgrade systemd-packages from 208-8 systemd isn't
selected for upgrade, resulting in KDE and X11 to
On Sat, Oct 11, 2014 at 10:12:44AM +0200, intrigeri wrote:
Hi,
Michael Scherer wrote (11 Oct 2014 05:51:39 GMT) :
Unfortunately, it seems the error code of aa_change_onexec is not
propagated,
which is a bug ( my fault, will correct upstream ). In the mean time, I
guess
we will
On 11 October 2014 20:14, Michael Biebl bi...@debian.org wrote:
Am 11.10.2014 um 20:58 schrieb Dimitri John Ledkov:
So what needs doing? Because to mount btrfs /dev/sdb,
systemd-udev-trigger is needed to generate block add event and
thus execute btrfs scan, in the initramfs-less case.
And ate
So, investigating the problem.
The issue is that :
ReadOnlyDirectories = /
make aa_change_onexec fail with
Oct 11 23:22:25 test-debian systemd[1985]: Failed at step APPARMOR spawning
/usr/bin/tor: Read-only file system
( once there is proper reporting ). I suspect the issue is upstream,
Am 12.10.2014 um 00:45 schrieb Dimitri John Ledkov:
On 11 October 2014 20:14, Michael Biebl bi...@debian.org wrote:
Actually that dump is very confusing for me to read, but it does have
timestamps for udev-trigger 2 seconds before data-gentoo, data and
home mount.
Then yeah, we need a log of
On Sun, Oct 12, 2014 at 02:23:22AM +0200, Michael scherer wrote:
On Sun, Oct 12, 2014 at 01:40:29AM +0200, Michael scherer wrote:
So, investigating the problem.
The issue is that :
ReadOnlyDirectories = /
make aa_change_onexec fail with
Oct 11 23:22:25 test-debian
So yeah, putting apparmor code before namespace code is the proper fix. I am
gonna send it
upstream, and then up to you to decide either to backport/adapt, or to just
work
around with /proc being rw.
Patch sent upstream :
13 matches
Mail list logo
