Hi, i must inform you that this bug exists with
linux-image-4.9.0-4-686-pae and 4.9.0-3
-- System Information:
Debian Release: 9.2
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 4.9.0-4-686-pae (SMP w/4 CPU cores)
Hi, i would like to inform you that this bug still exists with
linux-image-4.9.0-4-686-pae and 4.9.0-3
Package: src:linux
Version: 4.13.4-1
Severity: normal
Not running the kernel affected:
a) too many tolerable issues, constant journal spam with wpa_supplicant
and hung threads (will paste the kernel msg dump I had before)
b) issues with email now resolved (hopefully)
Sorry about this, but can't
On Mon, 2017-10-09 at 17:38 +0100, Steve McIntyre wrote:
> On Mon, Oct 09, 2017 at 02:01:15PM +0100, Ben Hutchings wrote:
[...]
> > It also appears to mean that buildds can get anything signed on demand
> > with no human intervention at all, without all the checks that dak does
> > on uploads.
On Mon, Oct 9, 2017 at 17:38:56 +0100, Steve McIntyre wrote:
> On Mon, Oct 09, 2017 at 02:01:15PM +0100, Ben Hutchings wrote:
> >It also makes all these packages unreproducible, which is a policy
> >violation.
>
> Surely *anything* with a signature is going to be unreproducible
> directly, by
On Mon, Oct 09, 2017 at 02:01:15PM +0100, Ben Hutchings wrote:
>On Thu, 2017-10-05 at 14:57 -0300, Helen Koike wrote:
>> Hello all,
>>
>> As you probably already know, Debian doesn't support the Secure Boot
>> chain yet.
>> To support it we need to sign Grub and the Kernel with our key, so we
>>
On Thu, 2017-10-05 at 14:57 -0300, Helen Koike wrote:
> Hello all,
>
> As you probably already know, Debian doesn't support the Secure Boot
> chain yet.
> To support it we need to sign Grub and the Kernel with our key, so we
> are discussing the best infrastructure for this workflow.
>
> The
7 matches
Mail list logo
