Am 21.05.2015 um 20:45 schrieb martin f krafft:
> Package: systemd
> Version: 215-17
> Severity: wishlist
> File: /bin/systemd-inhibit
>
> Instead of inhibiting while a command spawned is running, please
> find a way to elegantly/efficiently inhibit while another process is
> running (e.g. a syste
Am 23.05.2015 um 20:56 schrieb Rainer Dorsch:
> Am Montag, 18. Mai 2015, 22:21:42 schrieb Michael Biebl:
>> As you can also see, powertop exits with a non-zero return code. Since
>> /etc/rc.local uses "set -e", your script exits at this point and the
>> service
Control: tags -1 moreinfo unreproducible
Am 24.05.2015 um 00:57 schrieb Eduard Bloch:
> Repro steps:
>
> - install apt-cacher-ng from Sid (0.8.3-1). That works fine, runs the
>process with correct uid and parameters.
> - build the package from
>https://alioth.debian.org/anonscm/git/apt-
Control: tags -1 moreinfo
Am 27.05.2015 um 11:49 schrieb Wolfgang Silbermayr:
> When installing the package, then purging and removing it using dpkg, a
> dangling symlink is left on the system:
>
> /etc/systemd/system/multi-user.target.wants/.service ->
> /lib/systemd/system/.service
>
> A snip
Am 27.05.2015 um 23:38 schrieb Niels Thykier:
> reassign 786942 systemd,udev
> retitle 786942 systemd,udev: Long boot-time with systemd-udev-settle
> thanks
>
> Dear systemd maintainers,
>
> I am reassigning this upgrade report to you, in the hopes that you can
> solve it (or point us in the ri
Package: systemd
Version: 220-2
Severity: normal
Since the upgrade to v220, I get
Mai 30 15:06:24 pluto systemd[1]: [/lib/systemd/system/sudo.service:7] Failed
to unescape command line, ignoring: /usr/bin/find /var/lib/sudo -exec
/usr/bin/touch -d @0 '{}' \073
Mai 30 15:06:24 pluto systemd[1]: s
Source: systemd
Version: 220-2
Severity: serious
v219 and v220 has been failing in the test-suite for a while.
The results are somewhat consistent and it's the following three tests
which fail:
FAIL: test-strv
FAIL: test-dhcp6-client
FAIL: test-journal-flush
-- Package-specific info:
-- Syste
Control: severity -1 serious
Am 31.05.2015 um 20:14 schrieb Peter Wu:
> Control: tags -1 +upstream
> Control: forward -1 https://bugs.freedesktop.org/show_bug.cgi?id=90794
>
> Hi,
>
> It is not a sudo issue, but a systemd one. Should it be marked as such
> then?
>
> systemd v220 on Arch Linux t
Hi,
Am 31.05.2015 um 21:26 schrieb Martin Pitt:
> Michael Biebl [2015-05-30 15:53 +0200]:
>> v219 and v220 has been failing in the test-suite for a while.
>> The results are somewhat consistent and it's the following three tests
>> which fail:
>>
>> FAIL
Am 01.06.2015 um 23:13 schrieb Tino:
> Package: systemd
> Version: 215-17
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
>
> systemd doesn't survive two days on my bare minimal headless NAS
> installation. I already purged all unused packages, reinstalled syste
Am 01.06.2015 um 23:56 schrieb Tino:
> I don't know why or when this job was triggered. The uptime of the
> system was about 1.5-2 days until it happened.
> I don't have any custom or modified units. The only change i made with
> systemd is setting the log level to debug.
> I've seen a sefault whil
Hi Joey
Am 02.06.2015 um 02:27 schrieb Joey Hess:
> Package: systemd
> Version: 220-3
> Severity: normal
> File: systemd-networkd
>
> I'm trying to use systemd-networkd with systemd-nspawn --private-network
> --port
> now that a systemd supporting this feature has convenently landed in unstable
Am 02.06.2015 um 02:39 schrieb Michael Biebl:
> Given the recent upstream discussions [1] to switch to nftables, we will
...
> [1]
> http://lists.freedesktop.org/archives/systemd-devel/2015-June/032661.html
That was the wrong link. Here's the correct one:
http://lists.freedeskto
Am 02.06.2015 um 05:19 schrieb Daniel Schepler:
> I had the same testsuite failures reproduced on my machine in an i386
> pbuilder
> chroot. It turned out that the chroot didn't have systemd installed, just
> sysvinit (because it was created some time ago and just upgraded since then).
>
> W
Hi Martin
Am 02.06.2015 um 05:44 schrieb Martin Pitt:
> Control: fixed -1 219-1
> Control: severity -1 important
>
> Hello Tino,
>
> Tino [2015-06-01 23:13 +0200]:
>> This time it segfaulted while adding a job that should restart journald.
>
> This is known to not work. Don't restart journald f
Control: block -1 by 782475
Hi KiBi et al,
Am 02.06.2015 um 18:11 schrieb Cyril Brulebois:
> libudev1-udeb depends on missing libcap2. I suspect the easiest would be
> to drop libcap2 support from the udeb build. An alternative would be to
> try and add a udeb in libcap2. I'd rather have the form
Control: tags -1 moreinfo
hi
Am 02.06.2015 um 19:43 schrieb Arto Jantunen:
> Package: systemd
> Version: 220-1
> Severity: grave
>
> The new upload to unstable broke booting with dracut. The initramfs attempts
> to run /usr/lib/systemd/systemd-fsck to fsck the rootfs. Since on Debian (and
> in t
Control: tags -1 = upstream patch
Am 02.06.2015 um 20:07 schrieb Michael Biebl:
> Am 02.06.2015 um 19:43 schrieb Arto Jantunen:
>> The new upload to unstable broke booting with dracut. The initramfs attempts
>> to run /usr/lib/systemd/systemd-fsck to fsck the rootfs. Since on De
Control: found -1 220-4
Am 02.06.2015 um 08:51 schrieb Debian Bug Tracking System:
>* Fix parsing of escape characters in Exec*= lines. (Closes: #787256)
Looks like this isn't properly fixed yet by
load-fragment-use-UNESCAPE_RELAX-flag-to-parse-exec-.patch
I know get the following error with
Am 02.06.2015 um 11:16 schrieb James Cowgill:
> I tried building systemd on a few different machines and couldn't get it
> to fail on any of them. Then I looked at what packages were installed on
> the buildds. On the machines it fails on, sysvinit-core is installed and
> on mipsel-aql-01 (which pa
Am 04.06.2015 um 14:27 schrieb Mathias Brodala:
> Package: systemd
> Version: 220-4
> Severity: normal
>
> Hi,
>
> I am not able to use "bootctl install" to install the recently added
> systemd bootloader:
>
> # bootctl install --path=/boot/efi
> Created "/boot/efi/EFI/systemd".
> Created "/boot
Am 04.06.2015 um 10:10 schrieb Josselin Mouette:
> How about using only the last 3 bytes of the MAC?
>
> The probability of using, on the same system, *two or more* controllers
> from *different brands* with a collision in the last 3 bytes is
> nonexistent in practice.
>
> The clear benefit would
Am 04.06.2015 um 20:36 schrieb nusenu:
> Package: systemd
> Version: 215-17
>
> when using a multi-instance systemd service file with
> ReadOnlyDirectories the service fails if it is attempted to start on a
> Debian 8 system that has been upgraded from a previous release.
>
> Error message is:
>
Am 04.06.2015 um 23:00 schrieb Michael Biebl:
> Am 04.06.2015 um 20:36 schrieb nusenu:
>> Package: systemd
>> Version: 215-17
>>
>> when using a multi-instance systemd service file with
>> ReadOnlyDirectories the service fails if it is attempted to start on a
Am 04.06.2015 um 23:12 schrieb nusenu:
>> Can you find out what is different between the upgraded and fresh Debian
>> installation?
>
> systemd version is on both (fresh and upgraded) systems 215-17, what
> else should I check?
Eg. diff the list if installed packages you get via dpkg
--get-select
Am 04.06.2015 um 23:16 schrieb nusenu:
>
>> Do you maybe have anything installed on your upgraded system which might
>> interfere with systemd, like cgmanager, lxc, cgroup-bin etc.
>
> upgraded-system# dpkg -l cgmanager lxc cgroup-bin
> dpkg-query: no packages found matching cgmanager
> dpkg-que
Am 04.06.2015 um 23:37 schrieb Michael Biebl:
> Am 04.06.2015 um 23:12 schrieb nusenu:
>>> Can you find out what is different between the upgraded and fresh Debian
>>> installation?
>>
>> systemd version is on both (fresh and upgraded) systems 215-17, what
>>
Am 05.06.2015 um 14:05 schrieb Giuseppe Bilotta:
> Package: systemd
> Version: 220-4
> Severity: normal
>
> In all systems I have, systemd will fail to reboot or poweroff the
> machines if there is an NFS filesystem mounted. This happens because the
> network is brought down _before_ unmounting th
Am 04.06.2015 um 23:13 schrieb Christoph Anton Mitterer:
> So what I'm basically looking for, would be a way to configure, that
> e.g. everytime netfilter-persistent is stopped, fail2ban is either and
> when it's restarted fail2ban is either (obviously in the correct order,
> like stop fail2ban, st
Let me add here, that systemd has created proper dependencies for your
oneforall.mount unit, like After: network-online.target
It's then up to the individual networking software (NetworkManager,
ifupdown, wpasupplicant) to hook correctly into those targets and make
sure they are properly ordered.
Am 05.06.2015 um 17:49 schrieb Marc Haber:
> On Thu, Jun 04, 2015 at 06:05:04PM +0200, Christoph Anton Mitterer wrote:
>> Anyway, can we merge the issues?
>
> Objected. #787731 is a real bug. Just mentioning that the default is a
> bad default does not make it the same issue. The issue here ist th
Hi
Am 04.06.2015 um 16:02 schrieb Marc Haber:
> The documentation in resolved.conf(5) suggests that the compiled-in
> list does only apply if there is no other definition of DNS-Servers.
> This is not the case here, and the fact that systemd-resolved takes
> the definition from /etc/systemd/networ
Control: tags -1 + fixed-upstream confirmed
Control: fixed -1 220-1
Am 05.06.2015 um 21:45 schrieb Michael Biebl:
> Hi
>
> Am 04.06.2015 um 16:02 schrieb Marc Haber:
>> The documentation in resolved.conf(5) suggests that the compiled-in
>> list does only apply if there is n
Control: reassign -1 nvidia-driver
Control: found -1 340.65-2
Am 30.05.2015 um 19:26 schrieb Karl Schmidt:
> Finally SOLVED - the problem was traced back to the nvidia driver
> package I was using (in jessie 340.65+3.16.0+1) - I removed it ( the
> need has been eliminated as nouveau can now suppor
Am 09.09.2014 um 13:37 schrieb Samuel Thibault:
> Package: systemd
> Version: 208-8
> Severity: normal
>
> Hello,
>
> On a wheezy system, I had a serial console configured in /etc/inittab,
> used as a secondary work terminal (i.e. no console=ttyS0 on the kernel
> command line). After an upgrade t
Control: reassign -1 release-notes
Am 07.06.2015 um 08:32 schrieb Samuel Thibault:
> Michael Biebl, le Sun 07 Jun 2015 01:41:59 +0200, a écrit :
>> /etc/inittab is a sysvinit specific config file, which systemd won't
>> read. This is not going to change.
>>
>> If
Am 07.06.2015 um 19:06 schrieb Matthias Klumpp:
> 2015-06-07 18:59 GMT+02:00 Christian Kastner :
>>> [...]
>> http://www.kvr.at/debian/pool/main/libc/libcap2/libcap2_2.24-9.dsc
> Looks fine to me and builds & works fine as well :) - I could sponsor
> the package this evening, if there are no o
Am 07.06.2015 um 23:59 schrieb Christian Kastner:
> On 2015-06-07 23:22, Cyril Brulebois wrote:
>> Christian Kastner (2015-06-07):
>> | @@ -1,4 +1,5 @@
>> | libcap.so.2 libcap2 #MINVER#
>> | + __cap_lookup_name@Base 1:2.24-9
>> | _cap_names@Base 1:2.10
>> | _libcap_strdup@Base 1:2.10
>> More
Am 08.06.2015 um 08:01 schrieb Ludovic Lebègue:
> For a few days now each time the computer boots it forces a file system
> check on two of my disks.
>
> Here is the relevant journalctl entry :
>
> Jun 08 07:48:19 leonardo kernel: input: PS/2 Generic Mouse
> as /devices/platform/i8042/serio1/inp
Am 08.06.2015 um 10:26 schrieb Michael Biebl:
> Am 08.06.2015 um 08:01 schrieb Ludovic Lebègue:
>
>> For a few days now each time the computer boots it forces a file system
>> check on two of my disks.
>>
>> Here is the relevant journalctl entry :
>>
>>
Control: reopen -1
Control: fixed -1 217-1
Am 06.06.2015 um 21:45 schrieb Debian Bug Tracking System:
> Version: 217-1
>
> Am 05.06.2015 um 22:53 schrieb Michael Biebl:
>> > I tested with a minimal configuration under jessie's v215 and could
>> > reproduce the
Hello Thibaut,
Am 17.05.2015 um 15:32 schrieb Thibaut Varène:
>
> On 17 mai 2015, at 14:59, Thibaut Varène wrote:
>
>>
>> On 17 mai 2015, at 14:57, Martin Pitt wrote:
>>>
>>> Thibaut VARENE [2015-05-17 14:41 +0200]:
Just upgraded my system from wheezy to jessie. Boot stopped after initial
Control: -1 forwarded https://github.com/systemd/systemd/pull/91
Am 08.06.2015 um 11:10 schrieb Michael Biebl:
> We do not want to change the upstream behaviour though, so I'll try to
> start a discussion on the upstream mailing list and see what they think.
Prepared a patch and cre
Am 09.06.2015 um 13:14 schrieb Marc Haber:
> On Sat, Jun 06, 2015 at 09:42:37PM +0200, Michael Biebl wrote:
>> This change is imho too invasive for being backported to the stable v215
>> in jessie. The first Debian version carrying that fix is 217-1, so I'm
>> closing it
Am 10.06.2015 um 12:22 schrieb Axel Beckert:
> Hi,
>
> there seem to be a general issue with how .service files should be
> packaged (in /lib/systemd/system/ and not in /etc/systemd/system/):
>
> If a package is shipping a init script as well as a service file (as
> currently strongly recommend),
Am 10.06.2015 um 12:54 schrieb Martin Pitt:
> Michael Biebl [2015-06-10 12:50 +0200]:
>> To address this, we added code do dh_systemd, to mask the service on
>> remove. So even if the package is only removed, but not purged, be
>> remaining sysv init script will not be
Am 10.06.2015 um 15:50 schrieb Patrick Schleizer:
> Hi!
>
> This is what I did on Debian jessie...
>
>> sudo mkdir /etc/systemd/system/network-manager.service.d
>> sudo touch /etc/systemd/system/network-manager.service.d/x.conf
>> sudo systemctl daemon-reload
>
> Now, when running...
>
>> sudo
Control: severity -1 important
Am 09.06.2015 um 12:06 schrieb Ruediger Oberhage:
>* What led up to the situation?
> Booting Debian "Jessie". That dam*d "systemd" erases the "lost+found"
> directory entry in "/tmp", which obviously is in its own partition.
Looking at sysvinit's /lib/init/bootc
Am 10.06.2015 um 13:19 schrieb Axel Beckert:
> Michael Biebl wrote:
>> To address this, we added code do dh_systemd,
..
> After reading the source of
> /usr/share/perl5/Debian/Debhelper/Sequence/systemd.pm, I assume that
>
> dh $@ --with=systemd
>
> suffices.
Am 10.06.2015 um 20:00 schrieb Axel Beckert:
> Michael Biebl wrote:
> Ok. I'll revert the previously committed solution (1) and will likely
> do the next upload without a fix for LP#1462692. I want to make an
> upload of some packaging-only changes soon as there is a new upstrea
Control: tags -1 moreinfo
Am 11.06.2015 um 02:13 schrieb jessie:
> And the output of the systemd-logind.service, as you can see it fires
> `suspend` on the first lid close but never on any after the very first lid
> close, it is very odd, it clearly sees the event:
>
> ```
> -- Logs begin at W
Am 11.06.2015 um 18:44 schrieb Jessica Frazelle:
> systemd-inhibit
> Who: NetworkManager (UID 0/root, PID 693/NetworkManager)
> What: sleep
> Why: NetworkManager needs to turn off networks
> Mode: delay
>
> 1 inhibitors listed.
Ok, that looks fine.
Do you have an external mo
Am 11.06.2015 um 19:06 schrieb Jessica Frazelle:
> No I don't have an external monitor, I also reproduced this on a
> ubuntu 15.04 machine and a machine with a commpletely fresh install of
> debian stretch with gnome.
I guess we need a more verbose debug log then.
Please boot with systemd.log_leve
Am 11.06.2015 um 19:49 schrieb Jessica Frazelle:
> ok confirmed, it was HandleLidSwitchDocked=suspend, it just needed a
> system reboot to register the change i guess restarting logind doesnt
> do that
So logind believes your system is docked, probably because it detected a
second graphics device.
Am 11.06.2015 um 20:04 schrieb Jessica Frazelle:
> attached here
Ok, two things:
If you suspend/resume/suspend within 90secs, systemd will ignore the 2n
suspend request. That's this line:
> Jun 11 10:42:17 debian systemd-logind[706]: Ignoring lid switch
request, system startup or resume too clos
Am 10.06.2015 um 11:37 schrieb Michael Biebl:
> Am 09.06.2015 um 13:14 schrieb Marc Haber:
>> On Sat, Jun 06, 2015 at 09:42:37PM +0200, Michael Biebl wrote:
>>> This change is imho too invasive for being backported to the stable v215
>>> in jessie. The first Debian versi
This is a small test to see, if the email to u...@packages.debian.org
ends up on the pkg-systemd-maintainers m-l.
--
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
___
Hi
On Wed, 03 Dec 2014 13:31:24 +0100 Morel Berenger
wrote:
> Package: udev
> Version: 175-7.2
> Severity: important
>
> Dear Maintainer,
>
> When pluggin a hard-disk with (highly presumably) damaged partition table (or
> logical partition system, not sure exactly), udev starts lot of processe
Am 11.06.2015 um 20:44 schrieb Jessica Frazelle:
>> Can you reboot,run
>> ls -la /sys/class/drm
>> suspend/resume and run again
>> ls -la /sys/class/drm
Ok, let's retry this again:
for i in /sys/class/drm/*/status; do echo $i; cat $i; done
Please run that before and after suspend.
ControL: tags -1 moreinfo unreproducible
Am 13.06.2015 um 15:30 schrieb Martin-Éric Racine:
> Package: systemd
> Version: 215-17+deb8u1
> Severity: important
>
> systemd-logind regularly eats over 20% of system resources. Whenever that
> happens, the whole desktop crawls to a stop and GNOME mark
Am 13.06.2015 um 16:17 schrieb Martin-Éric Racine:
> 2015-06-13 16:34 GMT+03:00 Michael Biebl :
>> ControL: tags -1 moreinfo unreproducible
>>
>> Am 13.06.2015 um 15:30 schrieb Martin-Éric Racine:
>>> Package: systemd
>>> Version: 215-17+deb8u1
>>
Am 13.06.2015 um 16:17 schrieb Martin-Éric Racine:
> Not knowing exactly what processed launched systemd-logind ('ps' shows
> as launched by root as /usr/lib/systemd/systemd-logind, but without a
Is this a typo?
The Debian systemd package only ships /lib/systemd/systemd-logind.
--
Why is it tha
Am 13.06.2015 um 17:19 schrieb Martin-Éric Racine:
> $ sudo strace -t -p 29336 -o systemd-logind.txt
>
> Please find the result attached
So, logind seems to be continuously (re)stating and reading your drm
devices.
Can you run "udevadm monitor" and check the kernel log files if there
are any eve
Am 13.06.2015 um 18:39 schrieb Martin-Éric Racine:
> 2015-06-13 18:42 GMT+03:00 Michael Biebl :
>> Can you run "udevadm monitor"
>
> Endless series of these:
>
> KERNEL[4312.794011] change
> /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0
>
Am 14.06.2015 um 01:23 schrieb Josh Triplett:
> Package: udev
> Version: 220-6
> Severity: normal
>
> I don't know if the bug here lies with udev, udisks2, or some other
> component.
>
> I plugged in a removable USB disk, and its devices showed up as root:disk
> 0660,
> with no ACLs. Normally,
Control: tags -1 moreinfo
On Mon, 8 Jun 2015 17:19:33 +0500
=?UTF-8?B?0JDRhdC80LDQtNGD0LvQuNC9LCDQkNC90LTRgNC10Lkg0JLQu9Cw0LTQuNC80LjRgNC+0LLQuA==?=
=?UTF-8?B?0Yc=?= wrote:
> Package: udev
>
> Good day!
>
> uname -a
> Linux tc-017 3.16.0-4-686-pae #1 SMP Debian 3.16.7-ckt9-3~deb8u1
> (2
Control: reassign -1 debconf
On Thu, 11 Jun 2015 14:22:55 +0200 Mathieu Bridon
wrote:
> Package: udev
> Version: 215-17+deb8u1
> Severity: normal
>
> Dear Maintainer,
>
> I just ran 'apt upgrade' as usual, and there were a few packages to update.
>
> At some point, this appeared in the apt out
Hi
Am 14.06.2015 um 20:42 schrieb Josh Triplett:
> The disk was mounted, but the device file itself was not made
> read/write, so dd'ing a Debian .iso to it required root. Previously,
> that has worked for the logged-in user without requiring root. (I don't
> know how long ago this stopped worki
Am 14.06.2015 um 21:46 schrieb Josh Triplett:
> In any case, it seems unfortunate that users can no longer write an
> image to a USB disk without using root.
You can, using gnome-disks/udisks2. Admittedly, there is no command line
client for that, but with the D-Bus interfaces provided by udisks2,
Hi Michael,
thanks for getting in touch with us.
Am 14.06.2015 um 23:03 schrieb Michael Banck:
> I think after all the fuss over the last year, it might be a good idea
> to (i) outline how the sky has not fallen with systemd-in-jessie, (ii)
> what issues there were/are in jessie, if any, (iii) wh
Am 15.06.2015 um 07:34 schrieb Martin Pitt:
> Hey Josh,
>
> Josh Triplett [2015-06-13 16:23 -0700]:
>> I plugged in a removable USB disk, and its devices showed up as root:disk
>> 0660,
>> with no ACLs. Normally, I'd expect removable USB disks to grant
>> read/write permission to the logged-in u
Am 14.06.2015 um 15:11 schrieb Ansgar Burchardt:
> Hi,
>
> as written earlier[1] I would like to demote the "init" package from
> Priority: required & Essential: yes to Priority: important.
>
> This needs at least a change to the provider of update-rc.d/invoke-rc.d:
> these two programs are calle
Am 16.06.2015 um 06:35 schrieb David Mohr:
> I have a crypto device which I use as a physical volume for LVM. After
> upgrading to systemd 215-17+deb8u1 my system fails to boot, because
> `vgchange -ay` is not run after the crypto device is set up (which
[..]
> Please let me know if I can help to
Am 16.06.2015 um 08:12 schrieb Michael Biebl:
> Am 16.06.2015 um 06:35 schrieb David Mohr:
>> I have a crypto device which I use as a physical volume for LVM. After
>> upgrading to systemd 215-17+deb8u1 my system fails to boot, because
>> `vgchange -ay` is not run after the cr
Am 16.06.2015 um 08:12 schrieb Michael Biebl:
> Am 16.06.2015 um 06:35 schrieb David Mohr:
>> I have a crypto device which I use as a physical volume for LVM. After
>> upgrading to systemd 215-17+deb8u1 my system fails to boot, because
>> `vgchange -ay` is not run after the cr
Please attach your /etc/fstab. Was the USB drive attached when you booted your
system?
Am 16. Juni 2015 09:22:16 MESZ, schrieb Thomas Korimort :
>Package: systemd
>
>Severity: critical
>
>I am using Debian 8.0 Jessie on my RaspBerrry Pi 2. I do regular
>firmware updates with the script of Hexxeh
Separate /usr and no initramfs to mount it?
Am 16. Juni 2015 10:06:07 MESZ, schrieb Eric Valette :
>Package: systemd
>Version: 220-6
>Severity: critical
>Justification: breaks the whole system
>
>After yesterday upgrade to systemd 220.6, my system no longer boot. It
>reports a kernel panic witha
Am 16.06.2015 um 10:42 schrieb eric2.vale...@orange.com:
>
> On 06/16/2015 10:17 AM, Michael Biebl wrote:
>> Separate /usr and no initramfs to mount it?
>
> yes but 220-5 was working. I rather suspect the /tmp change as I do have
> this line in my /etc/fstab
Nope,
Control: forcemerge 785525 -1
[please always CC the bug report]
Am 16.06.2015 um 11:16 schrieb Thomas Korimort:
> Dear Michael,
>
> my fstab is short and consists of just 3 lines. The first two mount the 2
> partitions of the SD card, first partition as /boot/firmware with FAT file
> system and
[please don't use HTML only mails, or better no HTML at all]
Am 16.06.2015 um 11:46 schrieb eric2.vale...@orange.com:
> On 06/16/2015 11:40 AM, Michael Biebl wrote:
>> Am 16.06.2015 um 10:42 schrieberic2.vale...@orange.com:
>>> On 06/16/2015 10:17 AM, Michael Biebl wrote:
[again, please always CC the bug report]
Am 16.06.2015 um 12:38 schrieb Thomas Korimort:
> Thanks. My intention with the USB drive was to keep all the frequently
> changing and voluminous things there. /var is still on the SD card, but
> i decided to not put such essential thing on an unreliable U
Am 16.06.2015 um 13:18 schrieb eric2.vale...@orange.com:
> On 06/16/2015 11:58 AM, Michael Biebl wrote:
>> My suggestion would be, to fix your setup to either use an initramfs
>> like initramfs-tools or dracut, which mounts your /usr partition, or
>> use no separate /usr pa
Am 16.06.2015 um 19:35 schrieb Kees Cook:
> On Tue, Jun 16, 2015 at 11:55:30AM +0200, Martin Pitt wrote:
>> Would you mind moving this into /lib?
>
> Sure, that would be fine by me. I don't see a common way to handle this,
> though. Each package I've looked at does it differently. Can you send a
>
Hi Chris,
thanks for filing this bug report.
Am 18.06.2015 um 13:07 schrieb Chris Vogel:
> Package: udev
> Version: 215-17+deb8u1
> Severity: normal
>
> Dear Maintainer,
>
> copying a Jessie installation from a server with hardware raid to a
> system with software raid /dev/md* I found that the
Control: reassign -1 mdadm
Am 18.06.2015 um 14:18 schrieb Chris Vogel:
>
> Hi Michael,
>
> thanks for the prompt answer!
>
> On 18.06.2015 13:31, Michael Biebl wrote:
>> But mdadm (in jessie) ships it's own initramfs-tools hook
>> /usr/share/initramfs-too
Control: forcemerge 760923 -1
Am 22.06.2015 um 17:08 schrieb Tom LAREDO:
> Package: systemd-sysv
> Version: 215-17+deb8u1
> Severity: normal
>
> Dear Maintainer,
>
> The "halt" command behaviour has changed between Debian Wheezy and Debian
> Jessie. On Wheezy (running sysvinit), when you run "ha
Hi Andrei,
thanks for your bug report.
Am 21.06.2015 um 02:20 schrieb Andrei Karas:
> Package: udev
> Version: 220-7
> Severity: important
>
> With udev 220-7, after reboot network not working.
> Present eth1 and renamed interfaces. Roll back to 215-18 fixed issue.
> After rollback present eth1
Control: forwarded -1 https://github.com/systemd/systemd/issues/340
Am 23.06.2015 um 22:14 schrieb Dylan Thurston:
> Package: udev
> Version: 220-7
> Severity: normal
>
> Dear Maintainer,
>
> Since upgrading to recent udev version (220-x from 215-x), my Kinesis
> Advantage keyboard no longer wor
Am 23.06.2015 um 01:28 schrieb Andrei Karas:
>> We switched to the new persistent interface naming scheme in 220-7.
>>
>> Can you tell use, what interface names you had before the upgrade (via
>>
>> and what you get after the upgrade?
>>
>> What's the ifconfig -a output before and after the upgrade
Am 28.06.2015 um 11:17 schrieb Martin Pitt:
> Indeed, what the heck -- I do get /usr/share/doc/udev/NEWS.Debian.gz
> in the Ubuntu build, but not in the Debian build, but Ubuntu's
> debhelper has no difference wrt. debian/package.NEWS installation.
> It's also the same version.
>
> dh_installchan
Am 28.06.2015 um 11:50 schrieb Michael Biebl:
> Am 28.06.2015 um 11:17 schrieb Martin Pitt:
>
>> Indeed, what the heck -- I do get /usr/share/doc/udev/NEWS.Debian.gz
>> in the Ubuntu build, but not in the Debian build, but Ubuntu's
>> debhelper has no differ
Am 28.06.2015 um 11:50 schrieb Michael Biebl:
> It's very likely the doc-symlinking, which is Debian only, which causes
> udev.README.Debian to not be installed in Debian.
Sorry, meant udev.NEWS of course.
--
Why is it that all of the instruments seeking intelligent life in the
u
[ bringing pkg-systemd-maintainers into the loop here ]
Am 27.06.2015 um 20:14 schrieb Christian Seiler:
> On 06/27/2015 08:02 PM, Jonas Meurer wrote:
>> Am 27.06.2015 um 16:07 schrieb Christian Seiler:
>>> Could you try to do the following:
>>>
>>> 1. create a directory /etc/systemd/system/remote
Control: tags -1 moreinfo
Am 29.06.2015 um 18:32 schrieb Silvério Santos:
> Package: systemd
> Version: 220-7
> Severity: normal
>
> --- Please enter the report below this line. ---
> Shutdown is delayed 120 seconds (according to the message on the screen
> after
> the delay) waiting for autom
Package: usb-modeswitch
Version: 2.2.2+repack0-1
Severity: important
Hi,
according to [1], there is an incompatibility between usb-modeswitch
< 2.2.3 and systemd v221. Now that systemd v221 has landed in unstable,
it would be great if you can update usb-modeswitch accordingly.
Depending on the
Control: tags -1 moreinfo
Am 30.06.2015 um 10:18 schrieb Klaus Ethgen:
> Package: udev
> Version: 220-7
> Severity: critical
>
> After upgrading my system from 215-18 to 220-7 or 221-1, (only udev
> changes), my system is not bootable anymore.
>
> Here is all the informations I have:
> I first u
Control: severity -1 important
(I'm downgrading to non-RC, since sparc is not a release architecture)
Am 30.06.2015 um 09:57 schrieb Meelis Roos:
> Package: systemd
> Version: 221-1
> Severity: critical
> Justification: breaks the whole system
>
> I had trouble with udev 220-7 hanging on sparc b
Control: found -1 220-7
Control: severity -1 important
(downgrading, not a release architecture)
Am 30.06.2015 um 10:04 schrieb Meelis Roos:
> Package: udev
> Version: 221-1
> Severity: critical
> Justification: breaks the whole system
>
> udev 220-7 broke sparc boot with strange messages about
Am 30.06.2015 um 19:50 schrieb Axel Beckert:
> Hi,
>
> Michael Biebl wrote:
>> Am 30.06.2015 um 17:52 schrieb Klaus Ethgen:
>>> # CONFIG_FHANDLE is not set
>>
>> E.g. that one is missing.
>> If you compile your own kernel, you should make sure all requi
Am 30.06.2015 um 20:45 schrieb Klaus Ethgen:
> Am Di den 30. Jun 2015 um 17:38 schrieb Michael Biebl:
>> Am 30.06.2015 um 17:52 schrieb Klaus Ethgen:
>>> # CONFIG_FHANDLE is not set
>
>> E.g. that one is missing.
>> If you compile your own kernel, you should mak
501 - 600 of 2654 matches
Mail list logo
