Your message dated Thu, 25 Jun 2020 10:00:16 +
with message-id
and subject line Bug#942861: fixed in linux 5.7.6-1
has caused the Debian Bug report #942861,
regarding linux-image-amd64: missing-copyright-file
/usr/share/doc/linux-image-amd64/copyright
to be marked as done.
This means that yo
Your message dated Thu, 25 Jun 2020 10:00:16 +
with message-id
and subject line Bug#942861: fixed in linux 5.7.6-1
has caused the Debian Bug report #942861,
regarding linux-image-amd64:amd64: missing-copyright-file
/usr/share/doc/linux-image-amd64/copyright
to be marked as done.
This means t
Your message dated Thu, 25 Jun 2020 10:00:16 +
with message-id
and subject line Bug#954294: fixed in linux 5.7.6-1
has caused the Debian Bug report #954294,
regarding linux: __X32_SYSCALL_BIT being defined as UL constant breaks userspace
to be marked as done.
This means that you claim that th
Your message dated Thu, 25 Jun 2020 10:00:16 +
with message-id
and subject line Bug#959781: fixed in linux 5.7.6-1
has caused the Debian Bug report #959781,
regarding linux-image-5.6.0-1-rt-amd64: please enable CONFIG_STAGING_EXFAT_FS
to be marked as done.
This means that you claim that the p
Your message dated Thu, 25 Jun 2020 10:00:16 +
with message-id
and subject line Bug#961823: fixed in linux 5.7.6-1
has caused the Debian Bug report #961823,
regarding linux-source-5.6: Please enable hwmon for nvme drives in the kernel
config (CONFIG_NVME_HWMON)
to be marked as done.
This mea
Your message dated Thu, 25 Jun 2020 10:00:16 +
with message-id
and subject line Bug#961299: fixed in linux 5.7.6-1
has caused the Debian Bug report #961299,
regarding FTBFS: debhelper compatibility level 12 breaks linux kernel build on
hppa/parisc
to be marked as done.
This means that you cl
Your message dated Thu, 25 Jun 2020 10:00:16 +
with message-id
and subject line Bug#961823: fixed in linux 5.7.6-1
has caused the Debian Bug report #961823,
regarding linux: please enable CONFIG_NVME_HWMON
to be marked as done.
This means that you claim that the problem has been dealt with.
I
Your message dated Thu, 25 Jun 2020 10:00:16 +
with message-id
and subject line Bug#961328: fixed in linux 5.7.6-1
has caused the Debian Bug report #961328,
regarding src:linux enable OF and SERIAL_OF_PLATFORM for Loongson-3
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 25 Jun 2020 10:00:16 +
with message-id
and subject line Bug#962254: fixed in linux 5.7.6-1
has caused the Debian Bug report #962254,
regarding NFSv4.2: umask not applied on filesystem without ACL support
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 25 Jun 2020 10:00:16 +
with message-id
and subject line Bug#961823: fixed in linux 5.7.6-1
has caused the Debian Bug report #961823,
regarding Please set CONFIG_NVME_HWMON=y
to be marked as done.
This means that you claim that the problem has been dealt with.
If this i
Your message dated Thu, 25 Jun 2020 10:00:16 +
with message-id
and subject line Bug#962254: fixed in linux 5.7.6-1
has caused the Debian Bug report #962254,
regarding NFSv4.2: umask not applied on filesystem without ACL support
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 25 Jun 2020 10:00:16 +
with message-id
and subject line Bug#961516: fixed in linux 5.7.6-1
has caused the Debian Bug report #961516,
regarding linux: please enable VBOXSF_FS on amd64 and i386
to be marked as done.
This means that you claim that the problem has been dea
Package: src:linux
Version: 5.6.14-2
Severity: important
Dear Maintainer,
I just updated an Apple PowerBook G4 from debian 8 (latest officially
released version for powerpc) to unstable.
The latest running kernel il 3.16 while the new 5.6.0 does not boot the
machine. While booting, the last lines
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 24 Jun 2020 20:56:57 +0200
Source: linux
Architecture: source
Version: 5.7.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
Closes: 942861 954294 959781
On Wed, Jun 24, 2020 at 05:39:38PM +0100, Steve McIntyre wrote:
>On Wed, Jun 24, 2020 at 05:57:42PM +0200, Salvatore Bonaccorso wrote:
>>Control: found -1 4.19.118-1
>>Control: tags -1 + upstream
>>
>>>
>>> As I can reproduce this quite easily, I'm happy to help with whatever
>>> debugging might b
Package: src:linux
Followup-For: Bug #949020
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Just confirming that this issue is still present, causing a terrible
user experience when upgrading from Buster to Bullseye on a Lenovo
laptop. Verified on a 4th Gen Thinkpad X1 Carbon.
Setting intel_iom
Michael Biebl dixit:
>Is this workaround permanent or will systemd FTBFS again in the future?
I’ve just verified that the upstream-merged fix, appearing in
linux-libc-dev 5.7.6-1 in sid, fixes this permanently.
bye,
//mirabilos
--
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://ww
Am 25.06.20 um 17:49 schrieb Thorsten Glaser:
> Michael Biebl dixit:
>
>> Is this workaround permanent or will systemd FTBFS again in the future?
>
> I’ve just verified that the upstream-merged fix, appearing in
> linux-libc-dev 5.7.6-1 in sid, fixes this permanently.
>
Great, thanks Thorsten.
package src:linux
found 963689 5.7.6-1
thanks
I just found a new kernel in sid. This new 5.7 kernel has the same
problem as the previous 5.6.0-2
Bye,
Giuseppe
Processing commands for cont...@bugs.debian.org:
> package src:linux
Limiting to bugs with field 'package' containing at least one of 'src:linux'
Limit currently set to 'package':'src:linux'
> found 963689 5.7.6-1
Bug #963689 [src:linux] linux-image-5.6.0-2-powerpc: stuck at 'pmac32_cpufreq'
whe
linux-signed-amd64_5.7.6+1_source.changes uploaded successfully to localhost
along with the files:
linux-signed-amd64_5.7.6+1.dsc
linux-signed-amd64_5.7.6+1.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Mapping sid to unstable.
binary:linux-image-5.7.0-1-amd64 is NEW.
binary:linux-image-5.7.0-1-cloud-amd64 is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes a
linux-signed-arm64_5.7.6+1_source.changes uploaded successfully to localhost
along with the files:
linux-signed-arm64_5.7.6+1.dsc
linux-signed-arm64_5.7.6+1.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 24 Jun 2020 20:56:57 +0200
Source: linux-signed-amd64
Architecture: source
Version: 5.7.6+1
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
Changes:
linux-signe
Mapping sid to unstable.
binary:linux-image-5.7.0-1-arm64 is NEW.
binary:linux-image-5.7.0-1-cloud-arm64 is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes a
linux-signed-i386_5.7.6+1_source.changes uploaded successfully to localhost
along with the files:
linux-signed-i386_5.7.6+1.dsc
linux-signed-i386_5.7.6+1.tar.xz
Greetings,
Your Debian queue daemon (running on host usper.debian.org)
Mapping sid to unstable.
binary:linux-image-5.7.0-1-686 is NEW.
binary:linux-image-5.7.0-1-686-pae is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a good
OpenPGP signature and file hashes are val
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 24 Jun 2020 20:56:57 +0200
Source: linux-signed-arm64
Architecture: source
Version: 5.7.6+1
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
Changes:
linux-signe
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 24 Jun 2020 20:56:57 +0200
Source: linux-signed-i386
Architecture: source
Version: 5.7.6+1
Distribution: sid
Urgency: medium
Maintainer: Debian Kernel Team
Changed-By: Salvatore Bonaccorso
Changes:
linux-signed
OK, so I've just bisected down the stable 4.19.y branch from 4.19.98
to 4.19.118. What I've found is:
e58f543fc7c0926f31a49619c1a3648e49e8d233 is the first bad commit
commit e58f543fc7c0926f31a49619c1a3648e49e8d233
Author: Jann Horn
Date: Thu Sep 13 18:12:09 2018 +0200
apparmor: don't try
30 matches
Mail list logo
