On Thursday, 9 February 2023 05:17:24 CET Mathirajan S. Manoharan wrote:
> Package: firmware-brcm80211
> Version: 20221214-5
>
> My system has the following network card
> 02:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43225
> 802.11b/g/n [14e4:4357] (rev 01)
>
> If i
Hi Salvatore,
On Sunday, 5 February 2023 16:17:58 CET Salvatore Bonaccorso wrote:
> > > So I guess we can close this bug here, and the files can be shipped
> > > with a new dedicated source package containing the firmware files,
> > > since the last option of having them merged upstream in
> > >
Control: reassign -1 dkms
On Sunday, 5 February 2023 14:19:43 CET Eric Streit wrote:
> Package: src:linux
> Version: 6.1.8-1
> **
> Paramétrage de linux-image-6.1.0-3-amd64 (6.1.8-1) ...
> I: /initrd.img is now a symlink to boot/initrd.img-6.1.0-3-amd64
>
On Saturday, 4 February 2023 22:12:24 CET Salvatore Bonaccorso wrote:
> > Right, I agree this should be a package of its own. I didn't know
> > raspi-nonfree came from a "coherent" set of firmware sources provided
> > by a single upstream. It is a distorsion that peopleinterested in
> > brcmfmac
On Saturday, 4 February 2023 02:06:02 CET Dr. David Alan Gilbert wrote:
> a) The patch I bisected to is not the root cause of the bug; it just
> triggers a ~9 year old bug in the v4l code - so this patch isn't going
> to get changed.
>
> b) The ~9 year old bug is in a particularly hairy piece of
On 2 January 2023 20:21:04 CET Lisandro Damián Nicanor Pérez Meyer wrote:
> Control: forwarded -1 https://github.com/quassel/quassel-i18n/pull/2
>
> On 29 Dec 2022 at 21:37, Diederik de Haas wrote:
> > On Fri, 13 Mar 2020 10:31:57 -0300 Lisandro Damián Nicanor Pérez Meyer
>
Control: forwarded -1
https://lore.kernel.org/linux-iommu/Y9qSwkLxeMpffZK%2F@gallifrey/
On Wednesday, 1 February 2023 18:46:43 CET Dr. David Alan Gilbert wrote:
> I sent this upstream report:
> https://lore.kernel.org/linux-iommu/Y9qSwkLxeMpffZK%2F@gallifrey/T/#u
Thanks :-) Updated bug
On Wednesday, 1 February 2023 02:52:13 CET Dr. David Alan Gilbert wrote:
> bisected:
> GOOD [37fcacb50be7071d146144a6c5c5bf0194b9a1cf] phy: PHY_FSL_LYNX_28G should
> depend on ARCH_LAYERSCAPE BAD [f5ff79fddf0efecca538046b5cc20fb3ded2ec4f]
> dma-mapping: remove CONFIG_DMA_REMAP GOOD
>
On Tuesday, 31 January 2023 22:27:24 CET Russ Allbery wrote:
> Diederik de Haas writes:
> > I looked a little deeper/further and specifically into
> > `lib/coresight.sh` and that file does contain `echo -n`, which
> > ShellCheck does flag as it's undefined in POSIX. So mayb
Hi Salvatore and Gunnar,
On Tuesday, 31 January 2023 19:17:43 CET Salvatore Bonaccorso wrote:
> > Gunnar indicated that he's willing to remove the files from
> > raspi-firmware,
> > but they still need to be added to firmware-brcm80211, so pretty please?
>
> So I looked at this, and don't think
On Tuesday, 31 January 2023 18:10:57 CET Russ Allbery wrote:
> > I: linux-perf: bash-term-in-posix-shell '. $(dirname
> > $0)/../lib/coresight.sh'
> > [usr/lib/perf-core/tests/shell/coresight/asm_pure_loop.sh:8]
> Yeah, I think it's a false positive in this check (check_line in
>
Package: lintian
Version: 2.116.2
Followup-For: Bug #1016919
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
While inspecting lintian's output wrt (several) kernel builds I did, I
found the following warning, which seems to be a false positive?
I: linux-perf: bash-term-in-posix-shell '.
On 29 January 2023 18:35:14 CET, Julian Gilbey wrote:
>> A (major) libc6 upgrade is not something that will happen on Stable, so this
>> issue may only occur with people running Testing or Unstable.
>
>But it will happen when people upgrade their stable machines to
>bookworm once it is released.
On Tue, 24 Jan 2023 10:22:28 + Julian Gilbey wrote:
> Package: postgresql-15
> Version: 15.1-1+b1
>
> I recently started getting warnings such as the following from my
> postgresql backup script:
>
> WARNING: database "postgres" has a collation version mismatch
> DETAIL: The database was
Control: affects -1 src:directfb
On 3 Feb 2018 15:42:21 +0100 Sebastian Ramacher wrote:
> Package: wnpp
>
> Note that upstream appears to MIA.
https://web.archive.org/web/20170603093935/http://www.directfb.net/ seems to
be the last capture which at least shows a working home page, after that
Hi Stuart!
On Saturday, 28 January 2023 05:18:34 CET Stuart Prescott wrote:
> On 27/01/2023 21:23, Diederik de Haas wrote:
> Your suggestion is entirely sensible and it does no harm to start with
> the updated version as you say. I'm not sure there's any functionality
> in recent com
Control: tag -1 upstream fixed-upstream
On Saturday, 28 January 2023 07:22:11 CET Stuart Read wrote:
> I found this upstream bug report:
> http://lists.infradead.org/pipermail/linux-mediatek/2022-December/054010.ht
> ml
>
> However it is unclear to me if or when the fix will be applied to the
>
Control: tag -1 moreinfo
On 26 Nov 2022 20:31:25 +0100 Klaus Singvogel wrote:
> This issue only happens only with linux-image-6.0.0-0.deb11.2-amd64
> After I booted the old linux-image-5.19.0-0.deb11.2-amd64, the issue does
> not occur.
Does this issue still occur with version 6.0.12-1~bpo11+1
Hi Stuart!
On Friday, 27 January 2023 04:40:47 CET Stuart Prescott wrote:
> On 27/01/2023 09:17, Diederik de Haas wrote:
> > Package: svn-all-fast-export
> > Version: 1.0.18+git20200501-1
> > Severity: wishlist
> >
> > It would be great if the latest version co
Package: svn-all-fast-export
Version: 1.0.18+git20200501-1
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
It would be great if the latest version could be packaged for Debian.
I recently had the need to retrieve a repo from the alioth archive and
convert it to git. And this
On Wednesday, 25 January 2023 23:01:01 CET Diederik de Haas wrote:
> This sounds like a nice solution for the SD card images.
> I myself always use a wired connection, but I saw yesterday that someone
> tried to use d-i for RockPro64 but didn't get any output on screen and then
> tried
On Wednesday, 25 January 2023 20:22:33 CET Cyril Brulebois wrote:
> # SD card images (might also be applicable to the upcoming ChromeOS images)
> ...
> All of this assuming that the end results can be appended as the third
> part of the + + combination!
This sounds like a nice solution for the
Control: tag -1 upstream
Control: forwarded -1
https://gitlab.freedesktop.org/libinput/libinput/-/issues/852
On 25 January 2023 17:52:10 CET, Tobias Klausmann
wrote:
>Also reported to libinput upstream:
>
>https://gitlab.freedesktop.org/libinput/libinput/-/issues/852
Thanks! Updated bug
Control: found -1 5.10.162-1
On Wednesday, 25 January 2023 11:18:35 CET Keyu Tao wrote:
> [ 214.783069] CPU: 0 PID: 372 Comm: kworker/0:4 Kdump: loaded Not tainted
> 5.10.0-21-amd64 #1 Debian 5.10.162-1
signature.asc
Description: This is a digitally signed message part.
Control: reassign -1 dkms
Control: forcemerge 1029063 -1
On Monday, 23 January 2023 14:53:18 CET Stefano Simonucci wrote:
> Building module:
> Cleaning build area...
> make -j8 KERNELRELEASE=6.1.0-1-amd64 all
> KERNEL_SRC=/lib/modules/6.1.0-1-amd64/b uild...(bad exit status: 2)
> Error! Bad
Package: command-not-found
Version: 20.10.1-1
Severity: critical
Justification: Breaks unrelated software
Followup-For: Bug #968757
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 01 Sep 2020 15:59:09 +0800 Paul Wise wrote:
> Control: severity -1 important
>
> Downgrading this because
lace your existing 5.10.0-20-amd64
kernel and there is no (easy) way to see that you would be booting into
your new patched kernel from GRUB.
HTH,
Diederik>From 3ed496982f556d17a87f830acaf5023d4f5d9a9b Mon Sep 17 00:00:00 2001
From: Diederik de Haas
Date: Thu, 19 Jan 2023 18:32:38 +0100
Subject: [PATCH]
On Thursday, 19 January 2023 13:19:32 CET Diederik de Haas wrote:
> It generally takes me a few *seconds* to spot the issue.
One reason for that is that the cause and the solution of the issue tends to
be the same, pretty much every single time.
Namely a new kernel version with which their d
On 19 January 2023 10:32:04 CET, Andreas Beckmann wrote:
>On 17/01/2023 18.27, Diederik de Haas wrote:
>> It seems fine to print (in all caps afaic) that there is an issue.
>
>That tends to get overlooked ... in the middle of a thousand packages being
upgraded ...
Control: tag -1 fixed-upstream
On Wednesday, 18 January 2023 11:35:30 CET only4com wrote:
> Package: linux-image-6.1.0-1-amd64
> Version: 6.1.4-1
>
> After updating the linux image from linux-image-6.0.0-6-amd64 to
> linux-image-6.1.0-1-amd64 Version 6.1.4-1 I cannot mount a samba share from
>
17 janvier 2023, 15.32:37 h CET Diederik de Haas a écrit :
> > > On Monday, 16 January 2023 22:33:05 CET Didier 'OdyX' Raboud wrote:
> > > > This is on 6.1.4-1a~test, patched against the "2nd DisplayPort doesn't
> > > > light up", so feel free to c
On Tuesday, 17 January 2023 18:12:30 CET Andreas Beckmann wrote:
> On Tue, 17 Jan 2023 10:56:33 +0100 Bastian Blank wrote:
> > > Error! Bad return status for module build on kernel: 6.0.0-6-amd64
> > > (x86_64)
> > > Consult /var/lib/dkms/anbox-binder/1/build/make.log for more
> > > information.
Control: tag -1 moreinfo
On Tuesday, 17 January 2023 14:20:19 CET Claire Osborne wrote:
> Booting in recovery mode on 5.10.0.20 also failed
>
> I have fallen back to the previously installed kernel 5.10.19 - with the
> same effect.
>
> Booting in recovery mode on 5.10.0.19 also fails.
What was
Hi OdyX,
On Monday, 16 January 2023 22:33:05 CET Didier 'OdyX' Raboud wrote:
> This is on 6.1.4-1a~test, patched against the "2nd DisplayPort doesn't
> light up", so feel free to close the bug; I'll test if I get the same
> symptoms on an unpatched kernel anyway :-)
If this issue doesn't occur
On dinsdag 17 januari 2023 13:09:57 CET you wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:wlroots package:
>
> #1027682: wlroots: New upstream release (0.16.1)
>
> It has been closed by Debian FTP Masters
> (reply to Guido Günther ).
On Sun, 15 Jan 2023 15:59:13 +0100 vmxevils...@gmail.com wrote:
> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> I am looking for a sponsor for my package "linux":
>
> * Package name : linux
>Version : 6.1.6-1~exp1
>Upstream contact : Salvatore
On Saturday, 14 January 2023 16:30:05 CET Salvatore Bonaccorso wrote:
> On Thu, Jan 12, 2023 at 02:51:05PM +0100, Diederik de Haas wrote:
> > On Thursday, 12 January 2023 12:03:24 CET Sjoerd Simons wrote:
> > > Fwiw there is a general regression with AMDGPU MST on
Source: linux
Version: 6.1.4-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The DeviceTree files (*.dtb) as shipped with the Debian kernel have the
executable bit set, but there is absolutely no need for that.
Lintian rightfully complains about it
Hi Julian,
On Thursday, 12 January 2023 12:11:57 CET Julian wrote:
> The message to linux-nvme finally came through and the thread is here:
> http://lists.infradead.org/pipermail/linux-nvme/2023-January/037384.html
The following paragraph may not be ideally formulated:
"Currently, I am using
On Thursday, 12 January 2023 12:03:24 CET Sjoerd Simons wrote:
> Fwiw there is a general regression with AMDGPU MST on linux 6.1; tracked
> upstream here:
> https://gitlab.freedesktop.org/drm/amd/-/issues/2171
Thanks! About an hour ago the suggested fix was to revert commit
Control: forwarded -1
http://lists.infradead.org/pipermail/linux-nvme/2023-January/037384.html
On Thursday, 12 January 2023 12:11:57 CET Julian wrote:
> The message to linux-nvme finally came through and the thread is here:
>
On Wednesday, 11 January 2023 19:28:25 CET Julian Groß wrote:
> On Mon, 09 Jan 2023 14:09:30 +0100 Diederik de Haas
> wrote:
> > https://wiki.debian.org/DebianKernel/GitBisect describes a procedure
> > to find the exact commit which introduced the issue you reported, but it's
Control: found -1 6.0~rc7-1~exp1
On Wednesday, 11 January 2023 15:04:30 CET Julian wrote:
> 6.0~rc7-1~exp1 is also broken.
>
> I will go through https://wiki.debian.org/DebianKernel/GitBisect and see
> what I can find. Thankfully the documentation is quite comprehensive.
That would be great,
On Wednesday, 11 January 2023 08:33:29 CET Didier 'OdyX' Raboud wrote:
> Package: src:linux
> Version: 6.1.4-1
> Severity: serious
>
> Since booting 6.1.0-1, the 2nd DisplayPort output from my Lenovo Docking
> Station doesn't get any output.
Can you try the previous versions of the 6.1.x series
On Tue, 23 Nov 2021 07:58:32 +0100 Ard Biesheuvel wrote:
> I don't see a reason to revert the default upstream. The feature
> remains deprecated (and in the longer term, the EFI handover protocol
> may be deprecated and removed as well), so the earlier the bootloaders
> adapt, the better it is.
>
Control: forwarded -1
https://lore.kernel.org/all/877f41ovlu@free-electrons.com/
Hi Ben,
On 07 Mar 2017 18:16:45 +0100 Gregory CLEMENT
wrote:
> On lun., févr. 20 2017, Ben Hutchings wrote:
> > On Mon, 2017-02-20 at 17:50 +0100, Thomas Petazzoni wrote:
> >> On Mon, 20 Feb 2017 16:40:25
Control: found -1 6.0.10-1
On Monday, 9 January 2023 13:20:08 CET Julian Groß wrote:
> when running Linux Kernel version 6.0.12 or 6.0.10, my system seemingly
> randomly freezes due to the filesystem being set to read-only due to an
> issue with my nvme controller.
> The issue does *not* appear
Control: tag -1 upstream patch
On Wed, 03 Mar 2021 16:16:49 + Matthias Klose wrote:
> Package: src:qpxtool
> Version: 0.8.1-1
> Usertags: ftbfs-gcc-11
>
> The package fails to build in a test rebuild on at least amd64 with
> gcc-11/g++-11, but succeeds to build with gcc-10/g++-10.
>
>
On Thursday, 5 January 2023 22:16:15 CET Helge Deller wrote:
> But it seems to fail differently for you
> https://salsa.debian.org/diederik/rrdtool/-/jobs/3746600 :
>
> /builds/diederik/rrdtool/debian/output/source_dir/src/rrdtool list
> FAILED: (rc=1) list without parameters displays Usage
>
On Sun, 25 Dec 2022 12:49:27 +0100 Helge Deller wrote:
> Package: rrdtool
> Version: 1.7.2-4
> Tags: hppa, patch, ftbfs
> Severity: important
>
> The command "rrdtool list /some/dir/" fails on 32-bit arches at runtime
> if those are running on huge discs, e.g. see failing "list1" testcase
> on
Package: fwupd
Version: 1.8.9-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
When I check the status of `fwupd.service` I see the (error?) message as
mentioned in the Subject.
It doesn't sound good, although I have no idea if this has any effect on
the workings of `fwupd`. I
Control: tag -1 upstream
Control: severity -1 normal
On Wed, 04 Jan 2023 12:04:52 +0100 xevilstar wrote:
> Package: linux-image-6.2.0-rc2
> Version: 6.2.0-rc2-1
>
> I am testing linux kernel 6.2-rc2
That is great, but you should report any issues you find to the relevant
upstream maintainers.
Package: aerc
Version: 0.13.0-1+b1
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Earlier today the release of version 0.14.0 was announced:
https://lists.sr.ht/~rjarry/aerc-announce/%3C20230104163910.PQQOJR7R3JWE%40ringo%3E
And hereby the request to update the aerc package
On Tuesday, 3 January 2023 22:14:10 CET Santiago Vila wrote:
> --
> From this definition it follows that packages of required priority are not
> necessarily build essential, as it is possible for some them not to be
... for some *of* them
On Wednesday, 4 January 2023 15:38:32 CET Tim Düsterhus wrote:
> Unfortunately the setting `1` allows direct write access to the devices,
> whereas the previous and to my understanding the default setting of `-1`
> only allows read access, making this a safer option.
>
> It appears that aacraid's
On Wednesday, 4 January 2023 16:39:33 CET Renato Gallo wrote:
> 5.10 should be EOL by now
Please refrain from comments like that.
It doesn't help at all and is also plain false.
signature.asc
Description: This is a digitally signed message part.
On Tuesday, 3 January 2023 19:06:41 CET Vagrant Cascadian wrote:
> Looks like some new source of non-determinism was added in 5.0.x, you
> can see bookworm (which does not test build paths) was reproducible
> until 5.0.x started getting tested in bookworm in June of 2022:
>
>
On 14 Apr 2022 15:45:26 -0700 Vagrant Cascadian wrote:
> On 2021-08-08, Sebastian Ramacher wrote:
> > On 2021-03-13 20:05:47 -0800, Vagrant Cascadian wrote:
> >> Source: ffmpeg
> >> Severity: normal
> >> Tags: patch
> >> User: reproducible-bui...@lists.alioth.debian.org
> >>
> >> The build path
On Monday, 2 January 2023 07:03:10 CET Vagrant Cascadian wrote:
> Also wifi related, on first boot, there was no wifi device configured,
> and I did not happen to install anything that pulled in
> network-manager or something similar. I am not sure I even did an
> install using wifi before, so
Source: wlroots
Version: 0.16.0-2
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I just saw that upstream released wlroots 0.16.1 last week.
AFAICT it has some important fixes, so if the package could be upgraded
to that version, that would be appreciated.
Cheers,
Diederik
Package: repo
Version: 2.28-1
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Version 2.31 is available upstream.
Could that be packaged and uploaded to Debian, please?
TIA,
Diederik
- -- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy:
On Saturday, 31 December 2022 01:41:52 CET Vagrant Cascadian wrote:
> On 2022-12-31, Diederik de Haas wrote:
> > Does this mean that u-boot upstream supports the Asus TF101?
> > If so, what is needed to get it enabled in Debian?
>
> It does not look like it is supported up
Package: rrdtool
Version: 1.7.2-4+b7
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I saw on salsa that version 1.8.0 is already there (since 9 months), but
it looks like it never got uploaded to the Debian archive?
Could you do that? In time for the freeze?
TIA,
Diederik
Source: u-boot
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Grepping through the source of u-boot (upstream), I found the following:
arch/arm/include/asm/mach-types.h:#define MACH_TYPE_TF1013640
Does this mean that u-boot upstream supports the Asus TF101?
On Friday, 30 December 2022 17:38:43 CET Jan Mojzis wrote:
> Currently nginx is compiled with the PCRE3 library and all modules
> using PCRE must be compiled with the same version (PCRE3).
>
> I made practical test,
> nginx compiled with PCRE2 and lua compiled with PCRE3 and didn't work.
Ah ok,
On Fri, 11 Nov 2022 15:59:38 +0100 Jan Mojzis wrote:
> currently,
> nginx and all modules distributed with it are compatible with PCRE2.
>
> The last problem is with the libnginx-mod-http-lua module,
> which PCRE2 does not support.
> Issue here:
On Friday, 30 December 2022 14:03:03 CET Matthias Urlichs wrote:
> > Do you have a link to that fix?
>
> https://github.com/gpiozero/gpiozero/pull/929
Thanks
signature.asc
Description: This is a digitally signed message part.
On Friday, 30 December 2022 12:42:53 CET Thorsten Glaser wrote:
> I think I reported the same thing against experimental some time ago,
> but it now is a regression in stable. Building kernel modules shows:
>
> tglase@tglase-edge:~/lnx/master/janz $ make
> make -C
On Friday, 30 December 2022 01:48:53 CET Stefan Pietsch wrote:
> >> Affected is at least linux-image-5.6.0-1-amd64 (5.6.7-1) and
> >> linux-image-5.6.0-2-amd64 (5.6.14-1).>
> > This also affects 5.5.0-rc5-amd64.
> >
> > (https://snapshot.debian.org/archive/debian/20200106T211159Z/pool/main/l/l
>
On Fri, 13 Mar 2020 10:31:57 -0300 Lisandro Damián Nicanor Pérez Meyer
wrote:
> Package: quassel-client
> Version: 1:0.13.1-3
>
> Hi! In the spanish translation there is a typo: it says mesnaje instead of
> mensaje.
>
> I've tried creating a pull request on quassel's github only to be closed
On Thursday, 29 December 2022 04:33:51 CET Rick Thomas wrote:
> Rebooting while watching the serial console output says "U-Boot SPL
> 2016.05-rc2+dfsg0~20160423~1-1 (Apr 24 2016 - 04:24:21)" So the firmware
> does not correspond to what aptitude says.
The main difference with your other
On Thursday, 29 December 2022 00:21:05 CET Vagrant Cascadian wrote:
> debian stable (2021.01*), testing (2022.04*), unstable (2022.10*)
> and experimental (2023.01-rc*)
>
> # arm64
> ...
> rock64-rk3328
I don't recall ever having issues with u-boot on my Rock64's, so for me
2022.04 - 2022.10
Control: affects -1 src:jekyll
On Mon, 26 Dec 2022 17:54:13 +0100 Lucas Nussbaum wrote:
> On 17/12/22 at 14:51 +0100, Diederik de Haas wrote:
> > There is an upstream PR: https://github.com/dtao/safe_yaml/pull/101
> > which tried to address this, but someone who tried it s
Control: reassign -1 src:linux 6.0.3-1~bpo11+1
On Tuesday, 27 December 2022 15:42:31 CET Wolf-Dieter Groll wrote:
> Package: linux-image-amd64
> Version: 6.0.3-1~bpo11+1
Stable backports now has 6.0.12-1~bpo11+1, could you try that too?
signature.asc
Description: This is a digitally signed
On Tuesday, 9 November 2021 01:30:03 CET nerdopolis wrote:
> +++ b/debian/config/kernelarch-x86/config
> @@ -75,6 +75,7 @@ CONFIG_IA32_EMULATION=y
> ## file: arch/x86/Kconfig.cpu
> ##
> # CONFIG_PROCESSOR_SELECT is not set
> +CONFIG_X86_SYSFB=y
It is now in a different location and quoting the
On Thursday, 22 December 2022 22:20:44 CET Kamila Szewczyk wrote:
> [ 297.413358] vboxdrv: loading out-of-tree module taints kernel.
If you're indeed testing this inside VirtualBox, do look whether there's an
update for that (too).
> [ 3025.190695] ACPI Error: No handler for Region [ECSI]
Control: reassign src:linux 5.10.158-2
On Wednesday, 21 December 2022 22:45:12 CET sapcie wrote:
> Package: linux-image-5.10.0-20-amd64
> Version: latest
> Severity: normal
Bug https://bugs.debian.org/1010733 also mentions that same audio device,
although that seems to have failed with
On Wednesday, 21 December 2022 17:11:55 CET Diederik de Haas wrote:
> Given that it worked with 6.0 but no more with 6.1-1~exp1 which I assume is
> a self-built kernel from current master, it seems more likely to be an
> upstream issue/regression.
I just noticed the following part from t
On Wednesday, 21 December 2022 12:47:45 CET Zhang Ning wrote:
> Package: linux-image-arm64
> Version: 6.1-1~exp1
>
> WIFI works well for my Arm64 SBCs (Khadas VIM1 & VIM3), both are Amlogic
> SBC, S905x and A311D, with kernel 6.0 and early versions.
>
> these two boards are well supported by
On 13 Sep 2022 09:00:07 -0300 Antonio Terceiro wrote:
> Source: ruby-safe-yaml
> Version: 1.0.5-2
> Justification: FTBFS
> Usertags: ruby3.1
>
> We are about to start the ruby3.1 transition in unstable. While trying to
> rebuild ruby-safe-yaml with ruby3.1 enabled, the build failed.
>
>
Hi Jonas,
On Tuesday, 13 December 2022 10:55:18 CET Jonas Smedegaard wrote:
> perhaps I can point you to other examples as well
I'd love to have several examples to look at :-)
Especially if you know of one (or more) who write extensive commit messages
explaining the reasons/rational of their
found 1026174 linux/6.0.10-2
signature.asc
Description: This is a digitally signed message part.
On Saturday, 22 May 2021 00:46:55 CET Vagrant Cascadian wrote:
> Package: src:linux
> Version: 5.10.28-1
> File: /boot/vmlinuz-5.10.0-6-armmp-lpae
> Control: block 986767 by -1
>
> The ethernet bridge fails to work on 5.10.x (also tried 5.10.38-1),
> but works fine on 4.19.x from buster. (This
On Thursday, 15 December 2022 11:47:11 CET Diederik de Haas wrote:
> On Thursday, 15 December 2022 10:43:22 CET Adi Kriegisch wrote:
> > after the discussion about the root cause of this issue on the linux-scsi
> > mailing list[1] there was one simple patch submitted to this list[2
On Thursday, 15 December 2022 10:43:22 CET Adi Kriegisch wrote:
> after the discussion about the root cause of this issue on the linux-scsi
> mailing list[1] there was one simple patch submitted to this list[2] that
> just changes the logic of the selection of the dma mask: in case of a 64bit
>
Control: found -1 6.0.12-1
On Thursday, 15 December 2022 10:09:27 CET Bernhard wrote:
> This bug still exist in Daily image from today (2022-12-15).
That's using the 6.0.0-6-armmp kernel.
signature.asc
Description: This is a digitally signed message part.
On Tuesday, 13 December 2022 15:40:04 CET Adi Kriegisch wrote:
> Source: linux
> Version: 5.10.158-1
>
> we just upgraded our xen test cluster's kernel to the latest kernel from
> s-p-u and noticed that network communication is broken. We do have a
> 'classic' setup with bridges in dom0. After
Control: tag -1 -moreinfo
On Wednesday, 1 June 2022 01:27:32 CET Diederik de Haas wrote:
> What's the current status wrt this bug?
Just saw upstream commit 630dc25e43dacfb5af94cd41532e77c47ec1caff which should
become part of 6.1-rc9 and/or 6.1 and it would be interesting to know if that
wo
On Sunday, 11 December 2022 14:16:04 CET Bernhard wrote:
> igc :04:00.0 eno1: PCIe link lost, device now detached
https://lore.kernel.org/all/20221031170535.77be0...@kernel.org/ looks relevant
signature.asc
Description: This is a digitally signed message part.
Control: reassign -1 debbugs 2.6.0
On Sat, 10 Dec 2022 13:56:54 +0500 Akbarkhon Variskhanov
wrote:
> Package: bugs.debian.org
> Severity: minor
> Tags: newcomer patch
> X-Debbugs-Cc: akbarkhon.variskha...@gmail.com
signature.asc
Description: This is a digitally signed message part.
Control: tag -1 moreinfo
On Sunday, 3 July 2022 14:40:36 CET Jean-Marc LACROIX wrote:
> Package: linux-image-5.18.0-2-arm64
> Version: 5.18.5-1
>
> Please find in attached file success story (!) on recent boot for
> target rock64 (pine64) with 64 Go class10 MMC card with Debian 11.3
>
Control: tag -1 =upstream
signature.asc
Description: This is a digitally signed message part.
Control: forwarded -1
https://lore.kernel.org/linux-scsi/y1jkuktjvyrow...@eldamar.lan/
Control: merge -1 1022126
On Thursday, 8 December 2022 15:27:49 CET Dröszler Gábor wrote:
> Package: src:linux
> Version: 5.10.149-2
> Severity: important
>
> Debian Bullseye not boot with XEN,
Control: severity -1 important
Control: forwarded -1
https://lore.kernel.org/linux-scsi/y1jkuktjvyrow...@eldamar.lan/
Control: merge -1 1022126
On Monday, 31 October 2022 13:44:05 CET Taavi Ansper wrote:
> Yes we are using xen virtualization
Merging it with 1022126 then
signature.asc
Control: tag -1 upstream
On Thursday, 8 December 2022 12:48:08 CET Marco Moock wrote:
> > Has it worked properly before with an older kernel? If so, which?
>
> No, it is a general problem.
Tagging the bug accordingly
On Thursday, 8 December 2022 09:39:40 CET Marco Moock wrote:
>My Logitech
On Thursday, 8 December 2022 09:39:40 CET Marco Moock wrote:
> Package: src:linux
> Version: 6.0.10-2
>
>My Logitech Inc. QuickCam Communicate STX USB Webcam 046d:08d7 can't
>use USB 2.0, although the manufacturer says it supports it.
Has it worked properly before with an older kernel?
On Wednesday, 7 December 2022 10:13:00 CET Chris Knadle wrote:
> What I really need is a Debian source package that uses CMake to see an
> example of how to build a package. I'm looking at list of packages that
> reverse depend on cmake, maybe I can find a Debian source package that
>
Control: tag -1 -fixed-upstream
Control: tag -1 moreinfo
On 13 Feb 2019 01:14:36 + Chris Knadle wrote:
> retitle 921617 Mumble echo canceler leaks memory
> forwarded 921617 https://github.com/mumble-voip/mumble/issues/3379
> thanks
The forwarded issue was closed without a fix, so removing
Hi Chris,
On Wednesday, 7 December 2022 10:13:00 CET Chris Knadle wrote:
> > So I'd suggest skipping 1.4 altogether and go straight for 1.5.
> > You _could_ now release a development snapshot (to Experimental?),
> > especially if the package needs to go through NEW and then the update to
> > the
On Wednesday, 7 December 2022 05:57:55 CET Christoph Anton Mitterer wrote:
> A patch has now been posted for dash at:
> https://lore.kernel.org/dash/y47zlpwkqy+ji...@gondor.apana.org.au/
> which is apparently scheduled to be merged into their git.
FTR: a v2 of that patch has been posted:
401 - 500 of 1672 matches
Mail list logo
