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

Am 29.01.2017 um 22:07 schrieb Luca Capello: > Hi there, > > On Fri, 27 Jan 2017 23:08:08 +0100, Nicolas Braud-Santoni wrote: >> On Sun, Dec 25, 2016 at 03:29:39PM +0100, Luca Capello wrote: >>> >>> sorry for the late reply, the package was rejected: >>> >>> >>>

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

Hi there, On Fri, 27 Jan 2017 23:08:08 +0100, Nicolas Braud-Santoni wrote: > On Sun, Dec 25, 2016 at 03:29:39PM +0100, Luca Capello wrote: > > > > sorry for the late reply, the package was rejected: > > > > > >

Bug#852883: systemd: FTBFS: Test failures

Am 29.01.2017 um 17:47 schrieb Lucas Nussbaum: > On 29/01/17 at 17:28 +0100, Michael Biebl wrote: >> Am 29.01.2017 um 17:10 schrieb Lucas Nussbaum: >> >>> Yes, tzdata is no longer build-essential, and is not installed in the >>> chroot. >> >> [..] >> >>> Actually, I did a rebuild specifically for

Bug#852883: systemd: FTBFS: Test failures

On 29/01/17 at 17:28 +0100, Michael Biebl wrote: > Am 29.01.2017 um 17:10 schrieb Lucas Nussbaum: > > > Yes, tzdata is no longer build-essential, and is not installed in the > > chroot. > > [..] > > > Actually, I did a rebuild specifically for that some time ago (to file > > all bugs in that

init-system-helpers 1.47 MIGRATED to testing

FYI: The status of the init-system-helpers source package in Debian's testing distribution has changed. Previous version: 1.46 Current version: 1.47 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

Bug#852883: systemd: FTBFS: Test failures

Am 29.01.2017 um 17:10 schrieb Lucas Nussbaum: > Yes, tzdata is no longer build-essential, and is not installed in the > chroot. [..] > Actually, I did a rebuild specifically for that some time ago (to file > all bugs in that category). I assume that something changed on the > systemd side,

Bug#852883: systemd: FTBFS: Test failures

On 29/01/17 at 17:00 +0100, Michael Biebl wrote: > Hi Lucas > > Am 29.01.2017 um 08:15 schrieb Lucas Nussbaum: > > On 28/01/17 at 10:40 +0100, Michael Biebl wrote: > >> The package built fine on the buildds just a couple of days ago. Do you > >> have an idea how the aws build environment

Bug#853078: udev: fails to start under systemd due to partial upgrade (seccomp error)

Package: udev Version: 232-14 Severity: important Am 29.01.2017 um 15:09 schrieb Michael Biebl: > Am 29.01.2017 um 11:53 schrieb Teemu Ikonen: >> Package: udev >> Version: 232-14 >> Followup-For: Bug #852811 >> >> I got same behaviour from udev as Christian on i386 (Apple MacBook2,1). >>

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

Dear powerpc porters, it would be great if you could look at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852811 From a cursory glance it seems that seccomp support is broken on ppc64. Your input would be appreciated. Am 27.01.2017 um 16:21 schrieb Michael Biebl: > Am 27.01.2017 um 15:54

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

Am 27.01.2017 um 15:27 schrieb Christian Marillat: > 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: >> >>>

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

Am 29.01.2017 um 11:53 schrieb Teemu Ikonen: > Package: udev > Version: 232-14 > Followup-For: Bug #852811 > > I got same behaviour from udev as Christian on i386 (Apple MacBook2,1). > Commenting out the lines mentioned above in systemd-udevd.service made > udev start. > > The problem was

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

Package: udev Version: 232-14 Followup-For: Bug #852811 I got same behaviour from udev as Christian on i386 (Apple MacBook2,1). Commenting out the lines mentioned above in systemd-udevd.service made udev start. The problem was version mismatch with udev (232-14) and systemd (232-8). systemd