Bug#1059184: polkitd: Upgrade of polkitd 0.105-33 123-3 fails

Control: tags -1 + moreinfo On Thu, 21 Dec 2023 at 00:33:47 +0100, thah...@t-online.de wrote: > Updating an older machine which wasn't used for quite a while > caused errors in updating polkitd ... > + command -v systemd-sysusers > + systemd-sysusers polkitd.conf > Failed to check if group

Bug#1059228: build system hard-codes -std=c++11

Source: s2geometry Version: 0.10.0-6 Severity: normal s2geometry's CMakeLists.txt includes # s2geometry needs to use the same C++ standard that absl used to avoid # undefined symbol errors since ABSL_HAVE_STD_STRING_VIEW etc will # end up defined differently. There is

Bug#1058706: mariadb-server-core: mariadbd fails to start on fresh install on armel

Yes, this NAS unit also has 512M of RAM. Unfortunately, setting "innodb_flush_method=fsync" did not work. However, setting "innodb_use_native_aio=OFF" did work, but only after deleting the corrupted InnoDB files in /var/lib/mysql. On Thu, Dec 21, 2023 at 09:25:20AM +0200, Tuukka Pasanen

Bug#1058522: (no subject)

On 2023-12-21, at 11:21:48 +, Jeremy Sowden wrote: > On 2023-12-21, at 11:10:28 +0500, Lev Lamberov wrote: > > Since I cannot reproduce the bug, I'm downgrading the severity of > > this bug report. > > I cloned the git repo, ran `gbp buildpackage --git-pbuilder` and > reproduced it (log

Bug#1059227: Firmware Missing from recent live builds (I think due to usr transition)

package: live-build version: 1:20230502 I noticed that in recent weekly builds, many firmware packages are missing from the live desktop images. I believe that the problem is in this file https://salsa.debian.org/live-team/live-build/-/blob/master/functions/firmwarelists.sh. Its logic depends

Bug#1058937: /usr-move: Do we support upgrades without apt?

Hi, On 21/12/2023 09:41, Helmut Grohne wrote: Is it ok to call upgrade scenarios failures that cannot be reproduced using apt unsupported until we no longer deal with aliasing? I incline towards "no"; if an upgrade has failed part-way (as does happen), people may then reasonably use dpkg

Bug#1058937: /usr-move: Do we support upgrades without apt?

On Thu, Dec 21, 2023 at 11:19:48AM -0300, Antonio Terceiro wrote: > On Thu, Dec 21, 2023 at 10:41:57AM +0100, Helmut Grohne wrote: > > Is it ok to call upgrade scenarios failures that cannot be reproduced > > using apt unsupported until we no longer deal with aliasing? > > I think so, yes. I

Bug#1057591: octave-vibes: FTBFS: fatal: caught signal Segmentation fault -- stopping myself...

Le jeudi 21 décembre 2023 à 08:49 +0100, Rafael Laboissière a écrit : > * Santiago Vila [2023-12-20 22:03]: > > > El 20/12/23 a las 21:08, Rafael Laboissière escribió: > > > > HOME := $(shell mktemp -d) > > > > > > > > so that the same directory is never used twice between consecutive > > > >

Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386

On Thu, 21 Dec 2023 at 14:57, Paul Gevers wrote: > The Release Team considers packages that are out-of-sync between testing > and unstable for more than 30 days as having a Release Critical bug in > testing [1]. Your package src:meson has been trying to migrate for 31 > days [2]. Hence, I am

Bug#1058937: /usr-move: Do we support upgrades without apt?

On Thu, Dec 21, 2023 at 10:41:57AM +0100, Helmut Grohne wrote: > ## Upgrading using dpkg directly? > > We already have quite a number of packages that use Conflicts to prevent > file loss in upgrades in a very similar way to #1058937 (Ben's > libnfsidmap1 bug) even in released versions of Debian.

Bug#1058096: Test suite issues with new version of python3-antlr4 (Was: python3-antlr4: FTBFS: AttributeError: 'TestIntervalSet' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

On Thu, 21 Dec 2023 14:30:34 +0100 Andreas Tille wrote: > Control: tags -1 pending > > Hi, > > I intended to fix bug #1058096. Since I realised there is a new > upstream version I was considering an upgrade which I pushed to Salsa. > Unfortunately there are other test suite errors as you can see

Bug#1058096: Test suite issues with new version of python3-antlr4 (Was: python3-antlr4: FTBFS: AttributeError: 'TestIntervalSet' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?)

Control: tags -1 pending Hi, I intended to fix bug #1058096. Since I realised there is a new upstream version I was considering an upgrade which I pushed to Salsa. Unfortunately there are other test suite errors as you can see in Salsa CI[1]:

Bug#1058034: webkit2gtk: 2.43 fails to build on riscv64

On Thu, Dec 21, 2023 at 07:03:31AM -0500, Jeremy Bícha wrote: > > Jeremy, can you give this one a try? > The build is still in progress which seems like a good sign that it > will succeed. > > https://launchpad.net/~jbicha/+archive/ubuntu/arch2/+build/27578344 Ok, I wanted to upload 2.43.3 to

Bug#1059146: pandoc produces html5 that gives lintian errors

On Wed, 20 Dec 2023 14:35:09 +0100 Andreas =?UTF-8?B?UsO2bm5xdWlzdA==?= wrote: > Package: pandoc > Version: 3.0.1+ds-3 > Severity: normal > > Dear Maintainer, > > Pandoc produces html5 that gives lintian errors - for example: > > E: allegro5-doc: privacy-breach-uses-embedded-file You may use

Bug#1056460: python-bytecode's autopkg tests fail with Python 3.12 (armhf)

severity 1056460 important thanks On Wed, Nov 22, 2023 at 02:29:47PM +0100, Matthias Klose wrote: > Package: src:python-bytecode > Version: 0.15.1-1 > Severity: important > Tags: sid trixie > User: debian-pyt...@lists.debian.org > Usertags: python3.12 > > python-bytecode's autopkg tests fail

Bug#1059226: release.debian.org: Help doris migrate to testing

Package: release.debian.org Severity: normal X-Debbugs-Cc: pkg-grass-de...@lists.alioth.debian.org doris (5.0.3~beta+dfsg-17) is not migrating to testing, the excuses suggest this is due to superficial autopkgtests: https://qa.debian.org/excuses.php?package=doris Should this really block

Bug#1059225: [INTL:sv] Swedish strings for apt-listchanges debconf

package: apt-listchanges severity: wishlist tags: patch l10n Please consider to add this file to translation of debconf. -- brother# Translation of apt-listchanges debconf template to Swedish # Copyright (C) 2023 Martin Bagge # This file is distributed under the same license as the

Bug#1058318: flask-login: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

I don't see any other errors in the log except for the ast.Str deprecation warnings, and they all come from python-werkezug and not this package. Reassiging the bug. Upstream has already fixed this in in 2.3.5, by the way: https://github.com/pallets/werkzeug/issues/2704 I can see that 3.0.1

Bug#1059224: [INTL:sv] Swedish strings for xsp debconf

package: xsp severity: wishlist tags: patch l10n Please consider to add this file to translation of debconf. -- brother# Translation of xsp debconf template to Swedish # Copyright (C) 2023 Martin Bagge # This file is distributed under the same license as the xsp package. # # Martin Bagge ,

Bug#1017039: (no subject)

Hi Thomas, understood. Thank you for your elaboration and maintaining dracut in Debian! Cheers, Patrick

Bug#1059223: src:meson: fails to migrate to testing for too long: fails autopkgtest on arm64 and i386

Source: meson Version: 1.2.3-1 Severity: serious Control: close -1 1.3.0-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as

Bug#1059222: src:pv: fails to migrate to testing for too long: FTBFS on armhf

Source: pv Version: 1.8.0-3 Severity: serious Control: close -1 1.8.5-1 Tags: sid trixie ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as

Bug#1059221: outdated package description - mkosi is no longer legacy-free (and that's okay)

Package: mkosi Severity: low Dear maintainer, as for the headline, I know "create legacy-free OS images" was the original branding of the project. mkosi know supports legacy BIOS booting. I see you already updated the package description to reflect that. Images are no longer

Bug#1059220: src:restic: fails to migrate to testing for too long: new Build-Depends is no migration candidate

Source: restic Version: 0.16.0-1 Severity: serious Control: close -1 0.16.2-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as

Bug#1058750:

Now I have some problem again. I can run GNOME Desktop with the variable but animations are not working even if enabled. Also Phosh desktop failing to run with all drivers, except with crocus: ``` libEGL warning: egl: failed to create dri2 screen (phoc:6696): phoc-wlroots-CRITICAL **:

Bug#1059219: gudhi: add build support for loongarch64

Source: gudhi Version: 3.7.1+dfsg-2 Severity: wishlist Tags: patch User: debian-loonga...@lists.debian.org Usertags: loong64 Dear maintainers, We need to add build support for loongarch64 in d/control. Please consider the patch I have attached. The gudhi source package was compiled

Bug#1056279: Bug#1057220: Looks like the systemctl links are gone but not the pm-utils ones

On Mon, Dec 18, 2023 at 10:09:10AM +0100, Marc Haber wrote: > Thanks for the work, I was never able to fully grasp the issue and the > inner workings of the solution, and thank you for allowing me to remain > silent during the process of finding and implementing the solution. I'd like to report

Bug#1059218: Incorrect version information in debconf prompts?

package: xsp thanks While translating the debconf strings for XSP I noticed a strange wording. > You appear to have some ASP.NET 2.0 sites configured in > /etc/mono-server.Support for the 1.0 profile has been removed Found here

Bug#1059217: telegram-purple: add build support for loongarch64

Source: telegram-purple Version: 1.4.3-3 Severity: wishlist Tags: patch User: debian-loonga...@lists.debian.org Usertags: loong64 Dear maintainers, We need to add build support for loongarch64 in d/control, for example, ``` Package: telegram-purple # see #958828; little endian (big: hppa m68k

Bug#1059216: Problem configuring polkitd after upgrade

Package: polkitd Version: 122-3 During upgrading from Debian 11 Bullseye to Debian 12 Bookworm I received an error on polkitd configuration which also blocks other dependencies (network-manager, modemmanager, pkexec, colord, ...) Configurazione di polkitd (122-3)... Creating group 'polkitd'

Bug#1058034: webkit2gtk: 2.43 fails to build on riscv64

On Sun, Dec 17, 2023, 18:37 Alberto Garcia wrote: > On Thu, Dec 14, 2023 at 05:25:45PM +0100, Alberto Garcia wrote: > > Maybe we can try treating the CPU as unknown, as we do with x32: > > Jeremy, can you give this one a try? > The build is still in progress which seems like a good sign that it

Bug#1059215: slinkwatch: add build support for loongarch64

Source: slinkwatch Version: 1.1-5 Severity: wishlist Tags: patch User: debian-loonga...@lists.debian.org Usertags: loong64 Dear maintainers, We need to add build support for loongarch64 in d/control, for example, ``` Package: slinkwatch -Architecture: amd64 arm64 armel armhf i386 mips mips64el

Bug#1056653: Info received (Bug#1056653: Info received (Bug#1039566: Info received (Bug#1039566: "Uncaught exception" on crypto.getRandomValues(new Uint32Array(32)))))

Update: "strings /usr/lib/firefox/UNUSED/libnss3.so | grep NSS_3. | sort --version-sort" gives me 3.79 max, "dpkg-query -l libnss3" says 2:3.96.1-1 So the libraries included in firefox seem to be much older

Bug#1059214: python-skbio: add loong64 support

Source: python-skbio Version: 0.5.9-1 Severity: normal X-Debbugs-Cc: zhan...@loongson.cn Dear Maintainer, Please add loong64 support in debian/control, thanks! -- System Information: Debian Release: trixie/sid APT prefers unreleased APT policy: (500, 'unreleased'), (500, 'unstable')

Bug#1059213: simka: add build support for loongarch64

Source: simka Version: 1.5.3-7 Severity: wishlist Tags: patch User: debian-loonga...@lists.debian.org Usertags: loong64 Dear maintainers, We need to add build support for loongarch64 in d/control. Please consider the patch I have attached. The simka source package was compiled successfully on

Bug#1059210: qmake6

Hi Helmut. Xaos started this Qt6/QMake6 discussion and turned out to be a good testbed for checking debhelper versus Qt6 compatibility. A someone pointed out (sorry cannot find his name browsing on the phone), the generic first thing to try would be to try CMake instead. But I don't want to

Bug#1059212: spaln: add build support for loongarch64

Source: spaln Version: 2.4.13f+dfsg-1 Severity: wishlist Tags: patch User: debian-loonga...@lists.debian.org Usertags: loong64 Dear maintainers, We need to add build support for loongarch64 in d/control. Please consider the patch I have attached. The spaln source package was compiled

Bug#1058522: (no subject)

On 2023-12-21, at 11:10:28 +0500, Lev Lamberov wrote: > Since I cannot reproduce the bug, I'm downgrading the severity of this > bug report. I cloned the git repo, ran `gbp buildpackage --git-pbuilder` and reproduced it (log attached). I'll see if I can work out what's going on. J.

Bug#1058937: /usr-move: Do we support upgrades without apt?

Re: Helmut Grohne > Is it ok to call upgrade scenarios failures that cannot be reproduced > using apt unsupported until we no longer deal with aliasing? > > If the answer is yes here, we'll close #1058937 (Ben's libnfsidmap1 bug) > with no action calling the scenario unsupported. I think we

Bug#1059211: qemu-system-x86: QEMU/KVM guests: Window contents partially not updated

Package: qemu-system-x86 Version: 1:8.2.0+ds-1 Severity: important X-Debbugs-Cc: rz49...@gmx.net Dear Maintainer, after the latest QEMU packages update, I noticed strange redraw issues in VM guests’ X windows. I use XFCE on Debian Bullseye or Sid in all my VM guests. The lightdm logon pad

Bug#1039990: [Pkg-javascript-devel] Bug#1039990: nodejs: CVE-2023-30581 CVE-2023-30588 CVE-2023-30589 CVE-2023-30590

Le jeu. 21 déc. 2023 à 10:54, Moritz Muehlenhoff a écrit : > On Thu, Dec 21, 2023 at 06:43:35AM +0100, Salvatore Bonaccorso wrote: > > Hi, > > > > [CC'ing node-undici uploader] > [CC-ing the good email address for node-undici uploader] > > > >> Ack, let's do that. Could you prepare

Bug#1058937: /usr-move: Do we support upgrades without apt?

Hi, this installment serves a dual purpose. Let me first give an update of the status quo and then pose a consensus question on how we want to deal with a particular problem. I Cc d-release@l.d.o as upgrades are an integral part of releases. I Cc d-ctte@l.d.o for advisory feedback with

Bug#1059210: xaos FTCBFS: invokes the build architecture qmake6

Source: xaos Version: 4.3.1-1 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs xaos fails to cross build from source, because it bypasses the qmake detection required for cross building in debhelper. We've since added --buildsystem=qmake6 that makes this all a lot simpler. I note

Bug#1059209: debhelper: qmake6 buildsystem: add cross compilation support

Package: debhelper Version: 13.11.9 Tags: patch User: debian-cr...@lists.debian.org Usertags: ftcbfs Control: affects -1 + src:xaos Hi Niels, I uploaded my qmake6 buildsystem, but when I did, I forgot that cross build support is needed in there and not inherited from qmake (qt5). So I need

Bug#1057755: Qt WebEngine Security Support In Stable

On Wed, Dec 20, 2023 at 02:06:28PM -0700, Soren Stoutner wrote: > I must admit that I have no personal experience with connecting QML and C++. I don’t have any personal experience with that too. > But it seems to me from the documentation Qt has produced there are several > ways to bridge the

Bug#1059208: dh-ada-library: should strip the unreproducible path from the installed project

Package: dh-ada-library Severity: wishlist https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1030715 shows an example. Such unreproducibilities will affect most packages using the gprinstall tool, so a common solution seems better and the right place for that is dh-ada-library.

Bug#1059207: aseba: add loong64 support

Source: aseba Version: 1.6.99+dfsg-8 Severity: normal X-Debbugs-Cc: zhan...@loongson.cn Dear Maintainer, Add loong64 support diff --git a/debian/control b/debian/control index 1dad46e..b4c3cb4 100644 --- a/debian/control +++ b/debian/control @@ -18,7 +18,7 @@ Vcs-Git:

Bug#1059206: scikit-learn: FTBFS on loong64

Source: scikit-learn Version: 1.2.1+dfsg-1 Severity: wishlist Tags: ftbfs User: debian-loonga...@lists.debian.org Usertags: loong64 Dear maintainers, Compiling the scikit-learn failed for loong64 in the Debian Package Auto-Building environment. The full compilation log can be found at

Bug#1039990: [Pkg-javascript-devel] Bug#1039990: nodejs: CVE-2023-30581 CVE-2023-30588 CVE-2023-30589 CVE-2023-30590

On Thu, Dec 21, 2023 at 06:43:35AM +0100, Salvatore Bonaccorso wrote: > Hi, > > [CC'ing node-undici uploader] > > >> Ack, let's do that. Could you prepare bookworm-security updates > > >> based on 18.17.0 (after it has landed in unstable)? > > > > > nodejs 18.19.0 has landed in testing. > > It

Bug#1056653: Info received (Bug#1039566: Info received (Bug#1039566: "Uncaught exception" on crypto.getRandomValues(new Uint32Array(32))))

Ok, I seem to have it fixed locally. One of the threads in FF ran with much more CPU load, even if no activity was expected. "gdb" on it showed lots of Thread 1 "Isolated Web Co" received signal SIGSYS, Bad system call. 0x7f5c4e636840 in __libc_open64

Bug#1059168: Bug#1059165: src:zlib: fails to migrate to testing for too long: triggers autopkgtest issues

retitle 1059168 flaky autopkgtest user debian...@lists.debian.org usertag 1059168 flaky thanks BCC: control@b.d.o Hi, On 21-12-2023 10:04, Jérémy Lal wrote: Thank you for https://bugs.debian.org/1059168 I noticed "Marked as found in versions

Bug#1059165: [Pkg-javascript-devel] Bug#1059165: src:zlib: fails to migrate to testing for too long: triggers autopkgtest issues

Le jeu. 21 déc. 2023 à 08:59, Paul Gevers a écrit : > Hi, > > On 20-12-2023 23:08, Jérémy Lal wrote: > > I did the one for burp. > > Thanks for that. > > > Dolfin has active maintainers, though. > > I think I need to file a "flaky autopkgtest" bug report against dolfin. Thank you for

Bug#1059205: Add supoort for loong64

Package: python-py2bit Version: 0.3.1-1 Severity: normal X-Debbugs-Cc: liuxi...@loongson.cn Dear Maintainer,   Please add loong64 support, patch file is attached. Thanks diff -ruN python-py2bit-0.3.1-bk/debian/control python-py2bit-0.3.1/debian/control ---

Bug#1056457: [Debichem-devel] Bug#1056457: python-ase's autopkg tests fail with Python 3.12

Hi, On Thu, 21 Dec 2023 08:39:54 +0200 Andrius Merkys wrote: > Is there a way to ignore DeprecationWarnings, but leave them in to the > output? They are quite helpful to see, but not worth failing the build > at the time being. > You're right, deprecation outputs are useful. I've just tried by

Bug#1059204: Upgrade to 'libtorrent-rasterbar2.0' causes qbittorrent to crash

Package: libtorrent-rasterbar2.0 Version: 2.0.9-2+b1 Yesterday (2023-12-20) I have performed an upgrade of all my packages and turned my computer off. Today, I have found that qbittorrent is crashing at startup and can't even produce graphical crash log. After looking into my upgrade history

Bug#1059203: Add support for loong64

Package: opm-common Version: 2023.04+ds-5 Severity: normal X-Debbugs-Cc: liuxi...@loongson.cn Dear Maintainer,   Please add loong64 support, patch file is attached. Thanks diff -ruN opm-common-2023.04+ds-bk/debian/control opm-common-2023.04+ds/debian/control ---

Bug#1056653: Bug#1039566: Info received (Bug#1039566: "Uncaught exception" on crypto.getRandomValues(new Uint32Array(32)))

Another data point: The affected FF process has two defunct "Socket Process"es, the working FF-esr doesn't. 594571 ?Sl14:00 \_ /usr/bin/firefox.real -ProfileManager 594630 ?Z 0:00 | \_ [Socket Process] 594753 ?Z 0:00 |

Bug#1059165: [Pkg-javascript-devel] Bug#1059165: src:zlib: fails to migrate to testing for too long: triggers autopkgtest issues

Hi, On 20-12-2023 23:08, Jérémy Lal wrote: I did the one for burp. Thanks for that. Dolfin has active maintainers, though. I think I need to file a "flaky autopkgtest" bug report against dolfin. Paul OpenPGP_signature.asc Description: OpenPGP digital signature

<    1   2