Bug#824532: Bug#848327: [Pkg-auth-maintainers] Bug#848327: RFS: libu2f-host/1.1.3-1

On 25/12/16 15:29, Luca Capello wrote: On Fri, 16 Dec 2016 11:58:51 +0100, Nicolas Braud-Santoni wrote: This updates brings: - - a fix for #846358, so that rules for the right udev version are installed; - - as per #846359 and #824532, this creates a new binary package, libu2f-common, containi

Bug#852461: systemd: Creating scopes with systemd-run unreliable

Am 27. Januar 2017 21:16:52 MEZ schrieb Michael Gebetsroither : >On 2017-01-27 20:50, Michael Biebl wrote: > >>> The error sent from systemd back to systemd-run seems to be: >>> "Unit run-24908.scope already exists." >> >> >> Could you check if you have many scope units in /run which could slo

Bug#824532: [Pkg-auth-maintainers] Bug#848327: RFS: libu2f-host/1.1.3-1

Hi, On Sun, Dec 25, 2016 at 03:29:39PM +0100, Luca Capello wrote: > > sorry for the late reply, the package was rejected: > > > Sorry for the even-more-late reply, I was ill the last few months

Bug#852461: systemd: Creating scopes with systemd-run unreliable

On 2017-01-27 20:50, Michael Biebl wrote: >> The error sent from systemd back to systemd-run seems to be: >> "Unit run-24908.scope already exists." > > > Could you check if you have many scope units in /run which could slow down > systemd # find /run/systemd/system/ -type f -iname '*.scope' |w

Bug#852461: systemd: Creating scopes with systemd-run unreliable

Am 27. Januar 2017 18:56:31 MEZ schrieb Michael Gebetsroither : >On 2017-01-24 20:20, Michael Biebl wrote: >Hi Michael, > >>> The creation of scopes with systemd-run --scope is unreliable. >>> It seems to depend on system "load" or some other factors affected >>> by system "load". >>> On product

Bug#852461: systemd: Creating scopes with systemd-run unreliable

On 2017-01-24 20:20, Michael Biebl wrote: Hi Michael, >> The creation of scopes with systemd-run --scope is unreliable. >> It seems to depend on system "load" or some other factors affected >> by system "load". >> On production systems we've seen an error rate of up to 20%. > >> % for i in `seq 5

systemd 232-14 MIGRATED to testing

FYI: The status of the systemd source package in Debian's testing distribution has changed. Previous version: 232-8 Current version: 232-14 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive la

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

Am 27.01.2017 um 16:30 schrieb Christian Marillat: > On 27 janv. 2017 16:21, Michael Biebl wrote: > >> Christian, I think it's best if you approach the ppc64 porters about >> this. We need their input regarding seccomp support on that architecture. > > Well the kernel is a ppc64 but the archite

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

On 27 janv. 2017 16:21, Michael Biebl wrote: > Am 27.01.2017 um 15:54 schrieb Christian Marillat: >> #MemoryDenyWriteExecute=yes >> #RestrictRealtime=yes >> #RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 >> >> But I see others problems after a reboot : > > There are quite a few ser

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

Am 27.01.2017 um 15:54 schrieb Christian Marillat: > #MemoryDenyWriteExecute=yes > #RestrictRealtime=yes > #RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 > > But I see others problems after a reboot : There are quite a few services which use seccomp features to restrict the service.

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

On 27 janv. 2017 15:48, Felipe Sateler wrote: > On 27 January 2017 at 11:44, Michael Biebl wrote: >> Am 27.01.2017 um 15:40 schrieb Christian Marillat: >>> On 27 janv. 2017 15:26, Michael Biebl wrote: [...] >>> | Jan 27 15:38:52 fabian.marillat.net systemd[1]: systemd-udevd.service: >>> Main

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

On 27 janv. 2017 15:48, Felipe Sateler wrote: > On 27 January 2017 at 11:44, Michael Biebl wrote: >> Am 27.01.2017 um 15:40 schrieb Christian Marillat: >>> On 27 janv. 2017 15:26, Michael Biebl wrote: [...] >>> | Jan 27 15:38:52 fabian.marillat.net systemd[1]: systemd-udevd.service: >>> Main

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

On 27 janv. 2017 15:44, Michael Biebl wrote: > Am 27.01.2017 um 15:40 schrieb Christian Marillat: >> On 27 janv. 2017 15:26, Michael Biebl wrote: [...] >> Still the same : > > The error code is different. > >> | Jan 27 15:38:52 fabian.marillat.net systemd[1]: systemd-udevd.service: >> Main pr

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

On 27 January 2017 at 11:44, Michael Biebl wrote: > Am 27.01.2017 um 15:40 schrieb Christian Marillat: >> On 27 janv. 2017 15:26, Michael Biebl wrote: >> >>> Am 27.01.2017 um 15:21 schrieb Debian Bug Tracking System: >> >> [...] >> >>> seccomp is supposed to work on ppc64 [1], but maybe it's not.

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

Am 27.01.2017 um 15:40 schrieb Christian Marillat: > On 27 janv. 2017 15:26, Michael Biebl wrote: > >> Am 27.01.2017 um 15:21 schrieb Debian Bug Tracking System: > > [...] > >> seccomp is supposed to work on ppc64 [1], but maybe it's not. >> >> Christian, could comment out >> RestrictAddressFam

Processed: reopening 852811

Processing commands for cont...@bugs.debian.org: > reopen 852811 Bug #852811 {Done: m...@linux.it (Marco d'Itri)} [udev] udev: Doesn't start after upgrade powerpc Bug reopened Ignoring request to alter fixed versions of bug #852811 to the same values previously set > thanks Stopping processing h

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

On 27 janv. 2017 15:26, Michael Biebl wrote: > Am 27.01.2017 um 15:21 schrieb Debian Bug Tracking System: [...] > seccomp is supposed to work on ppc64 [1], but maybe it's not. > > Christian, could comment out > RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6 > > in systemd-udevd.ser

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

On 27 janv. 2017 15:29, Michael Biebl wrote: [...] > The output of grep SECCOMP /boot/config-$(uname -r) > would be helpful as well. , | $ grep SECCOMP /boot/config-$(uname -r) | CONFIG_HAVE_ARCH_SECCOMP_FILTER=y | CONFIG_SECCOMP_FILTER=y | CONFIG_SECCOMP=y ` Christian __

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

Am 27.01.2017 um 15:26 schrieb Michael Biebl: > Am 27.01.2017 um 15:21 schrieb Debian Bug Tracking System: >>> Maybe the problem is because / is a RAID0 ? >>> >>> Setting up udev (232-14) ... >> No. This is the problem: >> >>> addgroup: The group `input' already exists as a system group. Exiting. >

Bug#852811: udev: Doesn't start after upgrade powerpc

On Fri, 27 Jan 2017 15:16:57 +0100 m...@linux.it (Marco d'Itri) wrote: > On Jan 27, Christian Marillat wrote: > > > Maybe the problem is because / is a RAID0 ? > > > > Setting up udev (232-14) ... > No. This is the problem: > > > addgroup: The group `input' already exists as a system group. Exitin

Bug#852811: udev: Doesn't start after upgrade powerpc

On 27 janv. 2017 15:16, m...@linux.it (Marco d'Itri) wrote: > On Jan 27, Christian Marillat wrote: > >> Maybe the problem is because / is a RAID0 ? >> >> Setting up udev (232-14) ... > No. This is the problem: > >> addgroup: The group `input' already exists as a system group. Exiting. I see als

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

Am 27.01.2017 um 15:21 schrieb Debian Bug Tracking System: >> Maybe the problem is because / is a RAID0 ? >> >> Setting up udev (232-14) ... > No. This is the problem: > >> addgroup: The group `input' already exists as a system group. Exiting. I suspect this to be the problem: Jan 27 14:51:23 fa

Bug#852811: udev: Doesn't start after upgrade powerpc

Package: udev Version: 232-14 Severity: important Dear Maintainer, Maybe the problem is because / is a RAID0 ? Setting up udev (232-14) ... addgroup: The group `input' already exists as a system group. Exiting. Job for systemd-udevd.service failed because the control process exited with error c

Bug#852811: marked as done (udev: Doesn't start after upgrade powerpc)

Your message dated Fri, 27 Jan 2017 15:16:57 +0100 with message-id <20170127141657.dzvo2skczyex6...@bongo.bofh.it> and subject line Re: Bug#852811: udev: Doesn't start after upgrade powerpc has caused the Debian Bug report #852811, regarding udev: Doesn't start after upgrade powerpc to be marked as

Bug#774430: systemd: service makes as not reloadable

Hi, On 26/01/17 21:49, Michael Biebl wrote: > Am 26.01.2017 um 15:44 schrieb Michael Biebl: >> Am 18.01.2017 um 14:31 schrieb James Cowgill: > >>> After debugging a bit I found this commit which seems likely to be the >>> cause. I haven't actually tested 215 with the patch though: >>> https://git

Processed: tagging 847203

Processing commands for cont...@bugs.debian.org: > tags 847203 + fixed-upstream Bug #847203 [systemd] systemd: journalctl zsh completion fails with RC_QUOTES Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 847203: http://bugs.debian.or

Your Personal Letter Dated 27-01-2017

[image: Inline image 1] ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers