Your message dated Sun, 16 Jun 2024 22:22:43 +
with message-id
and subject line Bug#1073525: fixed in firmware-free 20240610-1
has caused the Debian Bug report #1073525,
regarding firmware-free: Incomplete source for carl9170-1.fw
to be marked as done.
This means that you claim that the
firmware-free_20240610-1_source.changes uploaded successfully to localhost
along with the files:
firmware-free_20240610-1.dsc
firmware-free_20240610.orig.tar.xz
firmware-free_20240610-1.debian.tar.xz
firmware-free_20240610-1_source.buildinfo
Greetings,
Your Debian queue daemon
Thank you for your contribution to Debian.
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Mon, 17 Jun 2024 00:01:17 +0200
Source: firmware-free
Architecture: source
Version: 20240610-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Kernel Team
Processing commands for cont...@bugs.debian.org:
> retitle 1073525 firmware-free: Incomplete source for carl9170-1.fw
Bug #1073525 [firmware-linux-free] firmware-linux-free uses prebuilt blobs
instead of building from source
Changed Bug title to 'firmware-free: Incomplete source for
Processing control commands:
> clone -1 -2
Bug #890601 [firmware-linux-free] firmware-linux-free uses prebuilt blobs
instead of building from source
Bug 890601 cloned as bug 1073525
1073525 was blocked by: 1050989 994625
1073525 was not blocking any bugs.
Ignoring request to alter blocking bugs
Control: clone -1 -2
Control: severity -1 wishlist
Control: retitle -2 firmware-free: Incomplete source for carl9170-1.fw
On Thu, 2024-06-06 at 21:18 +0200, Bastian Germann wrote:
> Hi Ben,
>
> Am 05.06.24 um 20:59 schrieb Ben Hutchings:
> > Please identify precisely which policy requirement is
Hello !
and should also end up back-ported in 6.9.5:
https://lore.kernel.org/all/20240616133543.1590007-1-osm...@heusipp.de/
Thanks for the notification. So this will end in our next upload based
on at least 6.9.5.
Looks like it just missed 6.9.5. Hopefully it will be in 6.9.6 then.
Processing control commands:
> tags -1 + fixed-upstream
Bug #1071378 [src:linux] linux-image-6.7.12-686-pae: Crash during early boot
Added tag(s) fixed-upstream.
--
1071378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071378
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tags -1 + fixed-upstream
Hi Jörn,
On Sun, Jun 16, 2024 at 03:50:57PM +0200, Jörn Heusipp wrote:
>
> This is fixed in upstream 6.10:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.10-rc3=2a38e4ca302280fdcce370ba2bee79bac16c4587
>
> and should also
On Sun, 16 Jun 2024 17:24:15 +0200 Christian Kastner
wrote:
> FYI, a contributor has submitted a patch to the kernel Bugzilla [1]
and
> it indeed fixed the issue for the packages where I was seeing this.
>
> Let's hope it gets recognized and accepted soon.
>
> Best,
> Christian
>
> [1]:
FYI, a contributor has submitted a patch to the kernel Bugzilla [1] and
it indeed fixed the issue for the packages where I was seeing this.
Let's hope it gets recognized and accepted soon.
Best,
Christian
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=218916
This is fixed in upstream 6.10:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v6.10-rc3=2a38e4ca302280fdcce370ba2bee79bac16c4587
and should also end up back-ported in 6.9.5:
https://lore.kernel.org/all/20240616133543.1590007-1-osm...@heusipp.de/
Regards,
Jörn
On Sunday, 16 June 2024 15:20:05 CEST Leith Bade wrote:
> I need to work out how to submit these fixes to the Linux device tree
> maintainers.
My experience is primarily/only with Rockchip based devices/SoCs and their
upstream development process, but it may help wrt MediaTek's.
- If you think
This weekend I went over the current Linux BPI-R3 Device Tree file in the
linux master branch in order to fix some issues I encountered with the
Ubuntu 6.8 kernel.
I compared everything to the BPI-R3 schematics as well as the MT7986
datasheet and these are the issues I found and fixed in my copy
PS: I am not using Proxmox (here), but the nfsd was running inside
a LXC container. The container couldn't be stopped due to the stuck
service and the whole LXC server had to be restarted.
15 matches
Mail list logo