Control: tag -1 upstream fixed-upstream patch
Control: forwarded -1 https://gitlab.freedesktop.org/pixman/pixman/-/issues/96
On 12 Jul 2024 13:38:30 +0900 Mike Hommey wrote:
> Source: pixman
> Version: 0.42.2-1
> Severity: serious
>
> The package fails to build on armhf on current sid/testing wi
On Tue, 26 Mar 2024 01:06:34 +0200 Peter Pentchev wrote:
> Control: tag -1 + confirmed
>
> On Tue, Mar 26, 2024 at 01:29:08AM +0500, Andrey Rakhmatullin wrote:
> > Source: dante
> > Version: 1.4.3+dfsg-1
> > Severity: serious
> > Tags: ftbfs
> >
> > https://buildd.debian.org/status/fetch.php?pkg
On Tue Aug 20, 2024 at 11:45 PM CEST, Cyril Brulebois wrote:
> Emanuele Rocca (2024-08-20):
> > Package: python3-pkg-resources
> > Version: 72.2.0-1
> > Severity: serious
> >
> > Importing pkg_resources fails with the following error:
> >
> > (sid-amd64-sbuild)ema@ariel:~$ python3
> > Python 3
On Tue Aug 20, 2024 at 5:55 PM CEST, Antonio wrote:
> I tried to install the new version of kmod 33+20240816-2 but it seems to
> remove essential packages:
>
> $ sudo apt install kmod
> ...
>
> Upgrading:
> kmod libkmod-dev libkmod2
>
> REMOVING:
> cryptsetup-initramfs initramfs-tools
Control: notfound -1 30+20230519-1
On Mon Aug 19, 2024 at 12:59 PM CEST, Antonio wrote:
> because i did log report after system restore, so it took that version.
> The affected version is 33+20240816-1.
Thanks, updating/fixing the found versions then.
> Il 19/08/24 12:54, Diederik d
On Mon, 19 Aug 2024 09:45:26 +0200 Antonio wrote:
> Package: kmod
> Version: 30+20230519-1
Why did you report it against 30+20230519-1?
Because AFAICT 30+20230519-1 and 32+20240611-1 are fine.
signature.asc
Description: This is a digitally signed message part.
On Mon, 19 Aug 2024 11:41:59 +0200 Christoph Anton Mitterer
wrote:
> On Mon, 2024-08-19 at 05:12 +0200, Marco d'Itri wrote:
> > > With the new version, initramfs generation gives:
> > I know, the plan it to rebuild dracut-install.
>
> Thanks. Then I guess from my side we could also already close
Control: affects -1 dracut initramfs-tools
On Mon, 19 Aug 2024 16:18:44 +1200 Ash Joubert wrote:
> Control: severity -1 critical
>
> This bug is critical because the dracut failure results in a nonbootable
> initrd when followed by "apt-get install -f":
>
> update-initramfs: Generating /boot/i
On Mon Aug 12, 2024 at 1:05 PM CEST, Faidon Liambotis wrote:
> On Sun, Aug 11, 2024 at 12:31:21PM -0400, Reinhard Tartler wrote:
> > But you are right, ultimately this decision is up to the maintainer to make.
>
> Maintainer here :)
>
> For this particular case, I think removing -Werror made sense
On Sun Aug 11, 2024 at 6:31 PM CEST, Reinhard Tartler wrote:
> I'm afraid we'll have to agree to disagree
Agreed
signature.asc
Description: PGP signature
On Mon Aug 12, 2024 at 8:42 AM CEST, Petter Reinholdtsen wrote:
>
> Control: tags -1 + patch
>
> The following debian/patches/1020-ffmpeg-7.patch seem to fix the build:
>
> Description: More fixes for ffmpeg 7.0
> Use class method GetChannels() as a wrapper to get the ffmpeg version
> dependent i
On Sun Aug 11, 2024 at 4:56 PM CEST, Reinhard Tartler wrote:
> On 2024-08-11 08:55, Diederik de Haas wrote:
> > On 03 Aug 2024 11:08:58 -0400 Reinhard Tartler
> > wrote:
> >> I noticed this package is listed as low-NMU. As such, I'm taking the
> >> liberty o
Control: notforwarded -1
Control: tag -1 -fixed-upstream
On Sun Aug 11, 2024 at 3:43 PM CEST, Petter Reinholdtsen wrote:
> [Diederik de Haas]
> >> during a rebuild of the reverse dependencies for the transition to
> >> ffmpeg 7.0, your package failed to build
> >
>
On Sun Aug 11, 2024 at 3:43 PM CEST, Petter Reinholdtsen wrote:
> [Diederik de Haas]
> >> during a rebuild of the reverse dependencies for the transition to
> >> ffmpeg 7.0, your package failed to build
> >
> > Someone made a PR and that got merged upstream.
On 03 Aug 2024 11:08:58 -0400 Reinhard Tartler wrote:
> I noticed this package is listed as low-NMU. As such, I'm taking the
> liberty of uploading the following patch as NMU to sid:
> ...
> new file debian/patches/don-t-fail-on-unknown-gcc-warnings.patch
> @@ -0,0 +1,20 @@
> +From: Reinhard Tar
On dinsdag 23 juli 2024 17:56:34 CEST you wrote:
> > during a rebuild of the reverse dependencies for the transition to
> > ffmpeg 7.0, your package failed to build
>
> In the upstream git repo there are 2 commits on 2024-04-13 which probably do
> fix the FTBFS issue, but don't make it compatible
On Wed, 03 Jul 2024 12:47:52 + Matthias Klose wrote:
> Package: src:wasmedge
> Version: 0.13.5+dfsg-1
> Usertags: ftbfs-gcc-14
>
> The package fails to build in a test rebuild on at least amd64 with
> gcc-14/g++-14, but succeeds to build with gcc-13/g++-13. The
> severity of this report will
Control: found -1 6.3.7-1
On Friday, 26 July 2024 10:49:00 CEST Stefan wrote:
> The complete sentence is:
>
> oldest non-working kernel is 6.3.7 (package linux-image-6.3.0-1-amd64),
> 6.3.5 (latest version of package package linux-image-6.3.0-0-amd64) works.
Excellent, that narrows down the 'sus
Control: tag -1 upstream fixed-upstream patch
On Wed, 03 Jul 2024 12:33:34 + Matthias Klose wrote:
> Package: src:libliftoff
> Version: 0.4.1-1
> Usertags: ftbfs-gcc-14
>
> The package fails to build in a test rebuild on at least amd64 with
> gcc-14/g++-14, but succeeds to build with gcc-13/
Control: found -1 6.9.7-1~bpo12+1
On Wednesday, 24 July 2024 17:24:44 CEST Stefan wrote:
> I ran a few other tests:
>
> 1. tried package "linux-image-6.1.0-22-amd64": works
> 2. tried package "linux-image-6.9.7+bpo-amd64": does not work
Via https://snapshot.debian.org/package/linux-signed-amd64/
On Wednesday, 24 July 2024 13:21:36 CEST Vincent Lefevre wrote:
> On 2024-07-24 10:58:24 +0200, Diederik de Haas wrote:
> > Uninstalling firmware YOU DON'T NEED is a perfectly valid solution.
>
> How can one do that? I mean, get only the Nvidia firmware for my
> part
On Sunday, 21 July 2024 13:13:23 CEST Simon John wrote:
> Realistically we need a fix for whatever happened here and it can't be
> any of:
>
> * remove plymouth or firmware (not practical for desktop)
Plymouth is not the problem. It turns out it's installed on my laptop and I
don't have this p
Control: affects -1 firmware-nvidia-graphics
On Friday, 19 July 2024 17:56:30 CEST Chris Hofstaedtler wrote:
> Control: retitle -1 initramfs-tools: duplicates nvidia firmware files
>
> On Fri, Jul 19, 2024 at 04:43:47PM +0200, Diederik de Haas wrote:
> > > In any case, the u
[ not including debian-release for this ]
On Friday, 19 July 2024 15:54:57 CEST Vincent Lefevre wrote:
> On 2024-07-19 14:32:28 +0200, Diederik de Haas wrote:
> > On Friday, 19 July 2024 13:08:50 CEST Vincent Lefevre wrote:
> > > When upgrading the firmware:
> > >
&
[ adding debian-release to the list for some troubling observations ]
On Friday, 19 July 2024 15:54:57 CEST Vincent Lefevre wrote:
> On 2024-07-19 14:32:28 +0200, Diederik de Haas wrote:
> > On Friday, 19 July 2024 13:08:50 CEST Vincent Lefevre wrote:
> > > When upgr
Control: tag -1 moreinfo
On Friday, 19 July 2024 13:08:50 CEST Vincent Lefevre wrote:
> When upgrading the firmware:
>
> [...]
> Setting up firmware-intel-graphics (20240610-1) ...
> Setting up firmware-iwlwifi (20240610-1) ...
> Setting up firmware-misc-nonfree (20240610-1) ...
> Setting up firm
Control: severity -1 minor
On 18 Jul 2024 09:43:38 +0200 Bastian Venthur wrote:
> Package: plymouth
> Version: 24.004.60-2
> Severity: important
> X-Debbugs-Cc: vent...@debian.org
>
> Dear Maintainer,
>
> trying to update plymouth fails with "No space left on device":
>
> sudo aptitude -u
> Pe
Control: tag -1 -patch
On Friday, 28 June 2024 09:55:24 CEST Michel Dänzer wrote:
> > This is fixed in upstream commit 5ca85d75c05de9df7c3170122dfdb04bc795b43a
> > ("dri: Fix BGR format exclusion"), which I attached for your convenience.
>
> Beware that this commit caused a regression on little e
Control: tag -1 upstream, fixed-upstream patch
Control: forwarded -1 https://gitlab.freedesktop.org/mesa/mesa/-/issues/11360
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/29837
On 14 Jun 2024 13:36:54 +0200 Emilio Pozuelo Monfort wrote:
> Control: reassign -1 mesa 24.1.1-2
> Control:
branch.
Yeah, it was/is a bit confusing, hence my next reply contained:
On 27 May 2024 10:40:24 +0200 Diederik de Haas wrote:
> Forgot to mention that that commit is part of upstream's 3.4.0~rc1,
> but it's unclear to me what is considered upstream now.
The ``debian/wa
On 27 May 2024 10:26:45 +0200 Diederik de Haas wrote:
> Control: tag -1 upstream fixed-upstream patch
>
> On Tue, 21 May 2024 14:57:47 +0200 Andreas Beckmann wrote:
> > Package: dahdi-dkms
> > Version: 1:3.1.0+git20230717~dfsg-5
> > Severity: serious
>
> A
^~~
> | strscpy
>
> cc1: some warnings being treated as errors
But this is.
Attached is the upstream patch for compatibility with 6.8/6.9 kernels added to
``debian/patches``.
>From e032b7936b75400f039ae8dfd40b1fdfdd56f2ce Mon Sep 17 00:00:00 2001
From: Died
Control: found -1 0.4.4-1
Control: tag -1 upstream patch
Control: forwarded -1
https://gitlab.com/ddcci-driver-linux/ddcci-driver-linux/-/commit/7f851f5fb8fbcd7b3a93aaedff90b27124e17a7e
On Saturday, 25 May 2024 10:18:20 CEST Bastian Blank wrote:
> Control: reassign -1 ddcci-dkms/0.4.4-1
Upstream
Control: forcemerge -1 1065184
On Saturday, 13 April 2024 16:32:04 CEST Andreas Metzler wrote:
> > If you agree, please merge these two bugs.
> > FTR: Bug #1065184 is already fixed in git.
>
> FWIW I can cobnfirm that xwayland builds successfully if libtirpc-dev is
> installed.
Thanks, then I'm
Hi,
I saw that this issue was fixed in git, but there hasn't been an upload with
that yet. It seems it's blocking the armhf build of wlroots and therefor its
migration, so could you upload a version with that fix?
Cheers,
Diederik
PS: On Salsa 'upstream-unstable' is set as default branch, wh
Hi,
On Wed, 13 Mar 2024 13:06:09 +0100 Lucas Nussbaum wrote:
> Source: xwayland
> Version: 2:23.2.4-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > /
On Sat, 3 Feb 2024 11:52:03 +0100 Paul Gevers wrote:
> Source: mumble
> Version: 1.3.4-4
> Severity: serious
> Control: close -1 1.5.517-1
> Tags: sid trixie
> User: release.debian@packages.debian.org
> Usertags: out-of-sync
>
> Dear maintainer(s),
>
> The Release Team considers packages tha
Control: tag -1 upstream fixed-upstream
On Tue, 06 Feb 2024 13:45:14 -0800 Elizabeth Loss-Cutler-Hull
wrote:
> Package: vulkan-tools
> Version: 1.3.268.0+dfsg1-1
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
>
> In file includ
On Wed, 2 Aug 2023 16:44:39 +0100 Simon McVittie wrote:
> Control: tags -1 + patch
>
> On Tue, 06 Dec 2022 at 13:22:40 +, Simon McVittie wrote:
> > This package has a Depends and/or Build-Depends on the transitional
> > package policykit-1, which has been separated into polkitd, pkexec and
>
Control: reassign 1058495 src:cage
Control: forcemerge -1 1058495
signature.asc
Description: This is a digitally signed message part.
Control: forcemerge -1 1058495
On dinsdag 16 januari 2024 20:29:22 CET you wrote:
> Source: cage
> Version: 0.1.5-1
> Severity: serious
> Justification: FTBFS
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
It's a known problem, see https://bugs.debian.org/1
Control: severity -1 important
Control: tag -1 moreinfo
On Tuesday, 19 December 2023 13:57:51 CET Vincent Lefevre wrote:
> Another piece of information: this is a regression.
>
> With the 6.1.0-16-amd64 kernel from stable, "journalctl -b -g ga107"
> gives
>
> Dec 19 04:57:07 qaa kernel: nouveau
On Monday, 11 December 2023 12:29:01 CET Salvatore Bonaccorso wrote:
> I cannot test for the regression explicitly myself, but 6.1.67 was
> released with just db46c77f3d51 ("Revert "wifi: cfg80211: fix CQM for
> non-range use""). Would you be in the position of do a test build with
> that commit (o
On Monday, 11 December 2023 13:01:58 CET Grand T wrote:
> Linux 6.6.6 is out and its only change over Linux 6.6.5 released just a few
> days ago is reverting the patch "wifi: cfg80211: fix CQM for non-range
> use." That patch ended up regressing Linux wireless support with deadlocks
> in the IWD wi
Control: tag -1 patch fixed-upstream
If the package is updated to version 3.3 plus a 'backport' of upstream commit
df95c4ee7bf489448a02c1f5053a24c628d637d9, then this bug should be fixed.
signature.asc
Description: This is a digitally signed message part.
On Thursday, 9 November 2023 14:14:23 CET Sebastian Ramacher wrote:
> > FTR: Upstream has an alternative patch for this (and references this bug):
> > https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/f01fdedb69e4accb1d1555106d
> > 8f682ff1f1ddc7
> I am awayre, yes. But a release of 6.1 is expected s
On 31 Oct 2023 23:15:11 + Sebastian Ramacher
wrote:
> https://salsa.debian.org/multimedia-team/ffmpeg/-/commit/
> 5a5de39526bd8ff5f3881cc611968062e076d9fe
>
>
> Workaround build issues with texinfo 7.1
>
> Closes: #105
On Monday, 24 July 2023 11:23:19 CET Salvatore Bonaccorso wrote:
> On Sun, Jul 02, 2023 at 09:14:50PM +, Hervé Werner wrote:
> > I've just faced this issue on the SSD disk as well, so it seems that
> > the probability is just lower on a speedier disk.
>
> Are you able to reliably preoeduce the
Control: notfound -1 20230210-5
Control: found -1 20230515-3
On Thursday, 12 October 2023 18:52:26 CEST Wiktor Janas wrote:
> Package: firmware-amd-graphics
> Version: 20230210-5
>
> firmware-amd-graphics version 20230515-3 (currently in unstable and testing)
> ships an inconsistent snapshot of t
Control: reassign -1 dkms
Control: tag -1 -ftbfs
On Wednesday, 13 September 2023 17:40:28 CEST Michael Cuffaro wrote:
> Error! Bad return status for module build on kernel: 6.1.0-12-amd64 (x86_64)
> Consult /var/lib/dkms/rtl88x2bu/5.13.1/build/make.log for more information.
No idea where you got
On Sat, 12 Aug 2023 19:24:16 +0200 Bastian Germann wrote:
> Source: waybar
> Version: 0.9.20-2
> Severity: serious
>
> The build fails on mips64el due to:
>
> test: waybar
> start time: 15:11:25
> duration: 0.02s
> result: killed by signal 6 SIGABRT
> command: MALLOC_PER
On 07 Aug 2023 00:18:15 +0200 Diederik de Haas wrote:
> Package: wlgreet
> Version: 0.4.1-1
> Severity: grave
> Tags: patch
> Justification: renders package unusable
>
> I'm preparing a MR on Salsa and once I have a bug number for this bug,
> I'll submit it
Package: wlgreet
Version: 0.4.1-1
Severity: grave
Tags: patch
Justification: renders package unusable
If you switch greetd's config to start wlgreet, you get presented a
screen to input your username and the next screen is for the password.
When you then press enter sway is supposed to start and i
On Monday, 3 July 2023 12:27:12 CEST julienbenja...@free.fr wrote:
> invoke DKMS to remove the module from installed kernel versions...
> and it failed with xtrx on 6.3.0-1-amd64.
>
> ```
> 0 upgraded, 0 newly installed, 1 to remove and 42 not upgraded.
> 4 not fully installed or removed.
You ma
On Wednesday, 14 June 2023 11:40:55 CEST Al Sutton wrote:
> Debain 12 has been released with a known bug which causes Android firmware
> builds to fail (https://lkml.org/lkml/2023/3/2/797) which makes bookwork
> unusable for the Android firmware community.
Is this possibly the same issue as report
On Friday, 21 April 2023 17:02:57 CEST Diederik de Haas wrote:
> It's even worse, it looks like I CAN'T uninstall the package (using normal
> tools; will likely try ``dpkg -f`` to brute force it later)
It turns out that ``dpkg --purge raspi-firmware`` with in my case also
``dp
Control: severity -1 critical
On Friday, 21 April 2023 16:53:39 CEST Diederik de Haas wrote:
> While I now do have those files in ``/lib/firmware/brcm/`` it caused various
> error which will only go away if I uninstall this package again.
> And as expected, at least the assumption tha
On Sunday, 2 April 2023 00:24:26 CEST Diederik de Haas wrote:
> 2) The commit that Bjørn identified also contained a "Link:" tag:
> https://lore.kernel.org/r/20230105041059.39366-1-kvija...@amd.com
>
> The best thing to do is to respond to that thread and explain the issue y
Control: tag -1 upstream
On Saturday, 1 April 2023 22:47:35 CEST Guy Durrieu wrote:
> I just finished to build the patched kernel.
Well done!
> After installing it, the system 6.1.0-7 boots again and run fine.
> Thus the source was well identified by Bjørn Mork.
This is great :-)
> I just had
On Saturday, 1 April 2023 17:44:21 CEST Guy Durrieu wrote:
> I am in trouble... I first did "Obtaining the kernel source", and at the
> end I got a /root/linux-source-6.1/ directory.
>
> Then I did "Rebuilding official Debian kernel packages" and
> "Preparation", and then I got among others a
> /
Is it sufficient to apply the patch given by Diederik de Haas ?
I'm guessing you forgot to do the Preparation from 4.2.1
>Le 01/04/2023 à 15:28, Salvatore Bonaccorso a écrit :
>> Hi,
>>
>> On Sat, Apr 01, 2023 at 11:51:38AM +0200, Guy Durrieu wrote:
>>> Hello
to the actual one which is para 4.2.2 and I have
attached a patch which reverts the referenced commit and that .patch file is
what you give as an argument to `bash debian/bin/test-patches`.
If you could try that to see if that indeed fixes the issue, that would be
very helpful.
HTH
>From 2e6223080905caf4c775680201700b2
On Wednesday, 1 March 2023 12:48:49 CET Axel Beckert wrote:
> A patch (without the proper indentation probably wanted for readability)
> which seems to have helped for me:
>
> diff --git a/kernel/postinst.d/z50-raspi-firmware
> b/kernel/postinst.d/z50-raspi-firmware index 1d3ae16..d898847 100755
>
On Tuesday, 28 February 2023 04:13:18 CET Daniel Black wrote:
> Source: linux
> Version: 5.10.0-21-powerpc64le
> Severity: grave
> Justification: causes non-serious data loss
> X-Debbugs-Cc: dan...@mariadb.org
>
> >From https://jira.mariadb.org/browse/MDEV-30728
>
> MariaDB's mtr tests on a numbe
On Thursday, 23 February 2023 04:44:16 CET Stuart Young wrote:
> Just a note that it looks like this patch got picked up in the 22.3.6
> release that just went out.
That's good to know, thanks.
But I don't know if at this stage in the Freeze new upstream releases are
still allowed. I'm pretty con
Control: tag -1 upstream fixed-upstream patch
On Tue, 31 Jan 2023 01:19:54 +0300 Andrey Skvortsov
wrote:
> Here is link to created upstream issue.
> https://gitlab.freedesktop.org/mesa/mesa/-/issues/8198
In https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/21330 this issue
got fixed up
Control: tag -1 -security
Control: severity -1 wishlist
On vrijdag 17 februari 2023 23:47:55 CET you wrote:
> And the final message in this bug is that you run Out Of Memory, so the OOM
> killer does exactly what it needs to do: kill other programs.
It may be annoying, but the system is working a
Control: tag -1 unreproducible
On Wed, 9 Feb 2005 17:12:21 +0100 Mike Hommey wrote:
> On Dec 27, 2004, Vincent Lefevre wrote:
> > Package: xsltproc
> > Version: 1.1.8-5
> >
> > Here xsltproc takes up to 138 MB, making the whole system slow down
> > due to swapping. This problem occurs when gene
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 w
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 ...
I said ALL CAP
> > Le mardi, 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
> > > > ligh
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
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
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
4d07b0bc403403438d9cf
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 w
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, 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 Cubox-
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 sure
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
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.
>
> Relevant
Control: retitle -1 mdadm --examine in chroot without /dev mounted corrupts
host's filesystem
Control: found -1 5.10.127-2
Control: fixed -1 5.18.2-1~bpo11+1
On Tuesday, 2 August 2022 11:03:09 CET Chris Hofstaedtler wrote:
> Control: reassign -1 src:linux
On 10 Feb 2021 14:29:52 +0100 Patrick Ce
Control: tag -1 upstream patch
Control: forwarded -1 https://github.com/GeorgeFilipkin/pulsemixer/pull/71
On Sun, 23 Oct 2022 15:41:02 +0200 Lucas Nussbaum wrote:
> Source: pulsemixer
> Version: 1.5.1-1
> Severity: serious
> Justification: FTBFS
I submitted a patch upstream, but upstream seems k
Control: forcemerge -1 1020066
On woensdag 23 november 2022 18:39:05 CET you wrote:
> > merge -1 1020066
>
> Bug #1019296 [src:tt-rss] tt-rss - build-dependencies unsatisfiable
> Unable to merge bugs because:
signature.asc
Description: This is a digitally signed message part.
Control: found -1 4.9.88-1+deb9u1
Control: notfound -1 4.9.88-1
Hi Salvatore,
On zondag 20 november 2022 16:38:25 CET Salvatore Bonaccorso wrote:
> On Sun, Nov 20, 2022 at 04:26:45PM +0100, Diederik de Haas wrote:
> > Control: notfound -1 4.9.88-1+deb9u1
> > Control: found -1 4.
user debian-rele...@lists.debian.org
usertag 1020066 + bsp-2022-11-nl-tilburg
tag 1020066 + pending
thanks
On Sun, 18 Sep 2022 08:18:31 +0200 Lucas Nussbaum wrote:
> Source: tt-rss
> Version: 21~git20210204.b4cbc79+dfsg-1
> Severity: serious
> Justification: FTBFS
Merged "Relax libjs-prototype b
Control: notfound -1 4.9.88-1+deb9u1
Control: found -1 4.9.88-1
On zondag 20 november 2022 13:55:09 CET Salvatore Bonaccorso wrote:
> Seems the BSP was productive :).
Yeah, once I set up the VM and created the script, it was actually quite easy.
> If you have spare cycles, might you
> check if d
Control: found -1 5.14.9-2
Control: found -1 5.15.5-2
Control: fixed -1 5.15.15-2
Control: fixed -1 5.16.11-1
Control: fixed -1 5.18.16-1
Control: fixed -1 6.0.3-1
On zondag 20 november 2022 12:18:50 CET you wrote:
> Control: found -1 5.14.9-2 5.15.5-2
> Control: fixed -1 5.15.15-2 5.16.11-1 5.18
Control: found -1 5.14.9-2 5.15.5-2
Control: fixed -1 5.15.15-2 5.16.11-1 5.18.16-1 6.0.3-1
On zaterdag 19 november 2022 21:22:46 CET Diederik de Haas wrote:
> found 900821 5.10.70-1
> fixed 900821 5.10.84-1
I continued testing with kernels from backports and updated metadata
accor
user debian-rele...@lists.debian.org
usertag 900821 + bsp-2022-11-nl-tilburg
found 900821 5.10.70-1
fixed 900821 5.10.84-1
thanks
We have/had a BSP in Tilburg today and I went to work on this bug.
With success :-)
I first created a new Bullseye VM with virt-manager using the
debian-11.5.0-amd64-
Control: tag -1 pending
On Wednesday, 9 November 2022 00:27:11 CET Diederik de Haas wrote:
> The /usr/lib/linux-image-6.1.0-0-arm64 does indeed not exist.
Since merging https://salsa.debian.org/kernel-team/linux/-/merge_requests/581
the directory does exist and is populated, thus tagging
On Thursday, 3 November 2022 22:18:53 CET Salvatore Bonaccorso wrote:
> >From the cover letter in the series:
> > The first patch will fix this, and the second will make sure we avoid that
> > situation entirely in the future. This has been tested with 5.19.12.
> > Earlier versions might need a bac
On Tuesday, 1 November 2022 22:36:56 CET Salvatore Bonaccorso wrote:
> Source: linux
> Version: 6.0.6-2
> Severity: serious
> Justification: FTBFS
>
> Documenting the build failures on arm64 and armhf due to ABI changes:
>
> https://buildd.debian.org/status/fetch.php?pkg=linux&arch=arm64&ver=6.0.
On donderdag 3 november 2022 12:37:19 CET you wrote:
> I was able to reproduce this on a RPi 1, found that is was reported upstream
> here:
> https://lore.kernel.org/dri-devel/20220922145448.w3xfywkn5ecak...@pengutronix.de/
>
> and found the patches that were applied upstream in 6.1-rc2 where ther
Control: severity -1 normal
On Wednesday, 2 November 2022 18:16:12 CET nmr wrote:
> Package: src:linux
> Version: 5.10.4-1
This is one of the very first 5.10.x versions! ...
> -- System Information:
> Debian Release: 11.5
> APT prefers stable-security
> APT policy: (500, 'stable-security'),
Control: found -1 5.19.6-1
Control: severity -1 important
Control: tag -1 moreinfo
On 30 Oct 2022 13:24:55 +0100 Jan Huijsmans wrote:
> Package: linux-image-5.19.0-1-arm64
> Severity: critical
> Justification: breaks the whole system
Only affecting RPi3 in certain conditions, thus lowering sever
Control: tag -1 -a11y
On zaterdag 29 oktober 2022 12:33:59 CEST femenia wrote:
> Package: src:linux
> Version: 6.0.3-1
> Severity: grave
> Tags: a11y
I don't see how a11y is relevant here, so removing the tag
signature.asc
Description: This is a digitally signed message part.
On woensdag 26 oktober 2022 12:43:02 CEST Alexis Huxley wrote:
> Following other reports of post-grub kernel hangs on systems with
> amdgpu, I waited for new release of linux-image-5.10.0-19-amd64,
> which came quickly, but it did not solve the problem for me.
>
> Symptoms are: grub loads kernel a
Control: forwarded -1 https://gitlab.freedesktop.org/drm/amd/-/issues/2216
Control: tag -1 patch pending upstream
Control: merge -1 1022042
signature.asc
Description: This is a digitally signed message part.
1 - 100 of 305 matches
Mail list logo
