On Mon Mar 24, 2025 at 10:10 AM CET, Ilias Tsitsimpis wrote:
> Source: haskell-tldr
>
> I intend to remove this package:
>
> * Seems unmaintained; Last upload ~4 years ago
> * Debian provides tldr-py, a Python client for tldr
> * Will probably stop working at end of year (see [1]).
>
> [1] ht
ut AMD-SEV:
https://www.amd.com/en/developer/sev.html
--
Henrique de Moraes Holschuh
or from a third-party (or
build a new one themselves by replacing the AMD PI / AGESA with updated ones).
--
Henrique de Moraes Holschuh
Hi,
On Thu Feb 27, 2025 at 2:30 PM CET, Johannes Schauer Marin Rodrigues wrote:
> Source: mesa
> Version: 25.0.0-1
> Severity: serious
>
> this is a regression from mesa 24.3.4-3. I'm filing with RC severity because
> this affects not only me but also other users on the BananaPI [1] and by
I have
On Sat Feb 22, 2025 at 11:59 AM CET, Aurelien Jarno wrote:
> Starting with version 6.13.3-1~exp1, the riscv64 kernel is shipped as a
> EFI binary with the payload compressed with zstd (using the EFI_ZBOOT
> config option). In addition to breaking non-EFI systems, this change
Breaks non-EFI systems
Dear maintainer,
Please consider the patch attached, which I have used to fix this package
FTBFS against NumPy 2.
Thank you,
Mateus
Description: Fix FTBFS on NumPy2
Author: Mateus Rodrigues de Morais
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libgetdata/+bug/2098512
Last-Update: 2025
Dear maintainer,
Please consider the patch attached, which I have used to fix this FTBFS
with NumPy 2 on Ubuntu.
Thank you,
Mateus
Description: Fix FTBFS on NumPy2
Author: Mateus Rodrigues de Morais
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/libgetdata/+bug/2098512
Last-Update: 2025
s no patch needed.
I hope someone can find the time to update Alien Arena to 7.71.7 in
Debian. I'm not familiar with the Debian tools and environments to do
this efficiently myself.
Kind regards,
Raoul de Raadt
On Sun Aug 11, 2024 at 10:27 PM CEST, Sebastian Ramacher wrote:
> Source: golang-google-grpc
> Version: 1.64.0-6
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the past)
> X-Debbugs-Cc: sramac...@debian.org
>
> https://buildd.debian.org/stat
Control: tag -1 fixed-upstream
The following commit added support for bootstrap-html (v5):
https://github.com/meetecho/janus-gateway/commit/5cc6c6c1f3cdaf96fc4adf19acff73f0006ccae9
which was the result of the following upstream PR:
https://github.com/meetecho/janus-gateway/pull/3300
and that would
Control: tag -1 fixed-upstream patch
On Mon, 09 Dec 2024 08:42:14 + Victor Seva
wrote:
> forwarded 1089503 https://github.com/sipwise/rtpengine/issues/1882
Upstream fixed it in the following commit
https://github.com/sipwise/rtpengine/commit/6b3f3b9698ed9670fedccd0db5f595d1c0db917e
And als
On Mon, 2 Dec 2024 16:00:18 +0100 Chris Hofstaedtler wrote:
> On Thu, Nov 14, 2024 at 11:11:43AM +0100, Guido Günther wrote:
> > Not in this case. 0.18 is considerably different regarding
> > e.g. rendering, damage tracking, etc. It's not just an API change.
>
> So, whats the plan here now?
>
>
On Wed, 13 Nov 2024 16:41:00 +0100 Emanuele Rocca wrote:
> Source: coccinelle
> Version: 1.2.deb-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
>
> During a rebuild of all packages in sid, coccinelle failed to build on
> arm64 and amd64 with the following error.
>
> [7]
>
Control: tag -1 upstream fixed-upstream
On Mon, 7 Oct 2024 12:27:11 -0400 Louis-Philippe Véronneau
wrote:
> Source: ranger
> Severity: important
>
> Python 3.13 removes a large amount of so called 'dead battery' libraries
> from the standard library.
>
> The following removed libraries were f
On 9/19/24 20:45, Jeremy Bícha wrote:
Could you try plugging in a keyboard and see if that avoids the issue?
Yes, makes no difference.
If you revert to using gjs 1.80.2-1 from Unstable/Testing, does that
avoid the issue?
Also makes no difference.
However, I managed to find a way to workaro
Package: gnome-shell
Version: 47.0-1
Severity: grave
Justification: renders package unusable
Upgrading Gnome-Shell to 47.0 makes GDM crash on boot. I've got almost the
exact same set of packages (& versions) installed on two other machines that
don't exhibit this issue.
Two things are specific
On Mon, 9 Sep 2024 11:20:39 +0100 Colin Watson wrote:
> On Mon, Sep 09, 2024 at 11:15:58AM +0100, Colin Watson wrote:
> > I've prepared an NMU for python-autopage (versioned as 0.4.0-3.1) and
> > uploaded it to DELAYED/2. Please feel free to tell me if I should delay
> > it longer.
>
> This is als
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
Source: jsjac
Followup-For: Bug #1006027
Control: tags -1 ftbfs
I tested this with sbuild and the package builds just fine.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500,
'unstable')
Architec
Source: jsjac
Followup-For: Bug #1006027
Control: tags -1 ftbfs
It does work on my current sid installation. I will check on a brand new
chroot.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500,
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
ebian.org alerts that the upload had reintroduced bugs in Trixie,
when I got your email on this bug report.
I have uploaded 3.20240813.2 a few minutes ago merging in the NMU changes and
hopefully fixing the oversight and closing this bug once again. Sorry about
that!
--
Henrique de Moraes Holschuh
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
Hi all,
I have attached a patch for the MCPP FTBFS reported in #1075263 can
somebody upload the patch to debian?
Cheers,
José
--
José Gutiérrez de la Concha
ZeroC, Inc.
--- a/src/expand.c
+++ b/src/expand.c
@@ -710,7 +710,9 @@
} else {
m_inf->locs.start_col = m_
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:
On Thu, 2024-05-23 at 13:36 +0200, Santiago Vila wrote:
> Arthur: Would be ok for you if I fix this in bullseye via team
> upload?
Please do, thanks.
I only have limited time available at the moment and have quite a big
backlog of issues to pick up so any help is really welcome.
Thanks,
--
--
On Sat, 2024-06-01 at 14:59 +0200, Chris Hofstaedtler wrote:
> thanks for uploading to unstable. However the upload included
> maintainer-built binaries (for Arch: all and amd64). Migration to
> testing of these is forbidden by release team policy.
> Please upload a new version (no further changes
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
, and now is as good a time as any other to stop
shipping libnss-db.
Users can probably use any other NSS module that can use some form of
database backend.
After a while I intend to file an RM bug, too.
Chris
--
Paulo Henrique de Lima Santana (phls)
Belo Horizonte - Brasil
Debian Developer
S
Can this solution be brought too bookworm, either through stable-updates
(preferably) or otherwise backports?
The current package is not useable.
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
It seems this has stalled. Most distros have already released a patched
version of libspf2. While I agree it's unclear whether the currently
available patch fixes this CVE, it does however fix an underflow that
would be relevant to release as a security fix, I think. Libspf2 has
tried to reach
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
Package: python3-certbot-dns-ovh
Version: 2.1.0-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Certbot renewal fails:
> systemctl status certbot
× certbot.service - Let's Encrypt renewal
Loaded: loaded (/etc/systemd/system/certbot.service; static)
Active: fai
e already
done so, and Debian is lagging behind. This is even more serious
considering exim is the default MTA on Debian, while many other distros
opt for postfix.
Kind regards,
Bert Van de Poel
On 18/10/2023 11:56, Salvatore Bonaccorso wrote:
Hi,
On Fri, Oct 13, 2023 at 12:05:19PM +0200, B
Package: systemd
Version: 252.12-1~deb12u1
Severity: serious
Justification: linux system unstable
Dear Maintainer,
When setting the time to 19 Jan 2038 3:14 GMT using "date 011903142038"
the systemd gets high load.
At 7 seconds after 3:14 the date is correct in the kernel but systemd
get
Package: cronie
Version: cron
Severity: serious
Justification: linux system unstable
Dear Maintainer,
When setting the time to 19 Jan 2038 3:14 GMT using "date 011903142038"
the crond gets high load.
Inspection of the cronie code, the meanloop of cron is controlled by a
time value that bec
Package: libspf2-2
Version: 1.2.10-7.1~deb11u1
Severity: critical
Tags: security patch
Justification: root security hole
X-Debbugs-Cc: Debian Security Team
As already outlined on
https://security-tracker.debian.org/tracker/CVE-2023-42118 there's a known
security issue in libspf2 found through
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
Source: python-duniterpy
Version: 1.1.0-3
Severity: serious
X-Debbugs-Cc: mateus.mor...@canonical.com
Dear maintainer,
The current upload of python-duniterpy (1.1.0-3) contains failing
autopkgtests when run against python-libnacl 2.1.0-1, currently in
unstable, and is blocking its migration to te
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
ic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
>From 7fd68f186
Dear,
This work has been done on the account of Trafik Verket
(https://www.trafikverket.se/) If applicable this information can be added.
Thank you, best regards,
Raymond
--
--
Dit e-mailbericht is met AVG-antivirussoftware gecontroleerd op virussen.
www.avg.com
Package: libqt5location5
Version: 5.15.8+dfsg-3
Severity: grave
Tags: bookworm
Justification: renders package unusable
X-Debbugs-Cc: raym...@orphiction.nl
Dear Maintainer,
Tiles are not loaded by qtlocation without this change.
The maintainer already showed that is fix is possible using unstable
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
1 - 100 of 1026 matches
Mail list logo
