Bug#1025000: python-qtawesome: Includes non-source Font Awesome 5

On Fri, Dec 09, 2022 at 08:49:10AM +0200, Andrius Merkys wrote: > Hi Bastian, > > On Mon, 28 Nov 2022 16:16:19 +0100 Bastian Germann wrote: > > This package contains three font files > > /usr/share/python-qtawesome/fonts/fontawesome5-*-webfont.ttf > > which are licensed freely but are not built

Bug#1021846: [programmer11...@programist.ru: Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem]

Daniel Axtens on Sat, 2022/12/03 01:41: > Please try the following: > > diff --git a/grub-core/fs/f2fs.c b/grub-core/fs/f2fs.c > index df6beb544cbd..855e24618c2b 100644 > --- a/grub-core/fs/f2fs.c > +++ b/grub-core/fs/f2fs.c > @@ -650,7 +650,7 @@ get_blkaddr_from_nat_journal (struct

Processed: Bug#1025242 marked as pending in fastapi

Processing control commands: > tag -1 pending Bug #1025242 [src:fastapi] fastapi: FTBFS with python3.11 Added tag(s) pending. -- 1025242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025242 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1025242: marked as pending in fastapi

Control: tag -1 pending Hello, Bug #1025242 in fastapi reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1025000: python-qtawesome: Includes non-source Font Awesome 5

Hi Bastian, On Mon, 28 Nov 2022 16:16:19 +0100 Bastian Germann wrote: This package contains three font files /usr/share/python-qtawesome/fonts/fontawesome5-*-webfont.ttf which are licensed freely but are not built from source and cannot be built from source (missing build system). #902981

Processed: reopening 1025661

Processing commands for cont...@bugs.debian.org: > # not actually fixed yet > reopen 1025661 Bug #1025661 {Done: Sylvestre Ledru } [src:rust-plotters] rust-plotters: invalid Uploaders field: missing comma between Jelmer Vernooij and Blair Noctis 'reopen' may be inappropriate when a bug has been

Bug#1024854: marked as done (aiotask-context: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine')

Your message dated Fri, 09 Dec 2022 04:34:21 + with message-id and subject line Bug#1024854: fixed in aiotask-context 0.6.1-3 has caused the Debian Bug report #1024854, regarding aiotask-context: (autopkgtest) needs update for python3.11: module 'asyncio' has no attribute 'coroutine' to be

Bug#1023697: Keep out of testing

Hi, On Fri, Nov 25, 2022 at 4:27 AM Bastian Germann wrote: > > It would be great to address the CVEs with patches on 4.6.0+p1-0+deb11u1. A proposed update for the 11.6 point release of bullseye, which is scheduled for next weekend, was filed with the release team. [1] They were also contacted

Bug#1024898: mozc: FTBFS on armel

Hi Nobuhiro, On 2022-12-09 01:52, Nobuhiro Iwamatsu wrote: Thanks for your help! 2022年12月9日(金) 9:03 Gunnar Hjalmarsson : Under the assumption that it's better to have mozc without the armel arch in testing than seeing mozc go away (see ), I'm about to do an

Bug#1024898: mozc: FTBFS on armel

Hi, Thanks for your help! 2022年12月9日(金) 9:03 Gunnar Hjalmarsson : > > On 2022-12-01 11:28, Gunnar Hjalmarsson wrote: > > How important is it that mozc is available on armel? Would it be an > > option to drop the armel support in bookworm? > > Under the assumption that it's better to have mozc

Bug#1024898: marked as done (mozc: FTBFS on armel)

Your message dated Fri, 09 Dec 2022 00:34:42 + with message-id and subject line Bug#1024898: fixed in mozc 2.28.4715.102+dfsg-2.1 has caused the Debian Bug report #1024898, regarding mozc: FTBFS on armel to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1024829: marked as done (src:mozc: fails to migrate to testing for too long: unresolved RC bug and FTBFS on armel)

Your message dated Fri, 09 Dec 2022 00:34:42 + with message-id and subject line Bug#1024829: fixed in mozc 2.28.4715.102+dfsg-2.1 has caused the Debian Bug report #1024829, regarding src:mozc: fails to migrate to testing for too long: unresolved RC bug and FTBFS on armel to be marked as

Bug#1023525: marked as done (Empty candidate window in x11 sessions)

Your message dated Fri, 09 Dec 2022 00:34:42 + with message-id and subject line Bug#1023525: fixed in mozc 2.28.4715.102+dfsg-2.1 has caused the Debian Bug report #1023525, regarding Empty candidate window in x11 sessions to be marked as done. This means that you claim that the problem has

Bug#1024898: mozc: FTBFS on armel

On 2022-12-01 11:28, Gunnar Hjalmarsson wrote: How important is it that mozc is available on armel? Would it be an option to drop the armel support in bookworm? Under the assumption that it's better to have mozc without the armel arch in testing than seeing mozc go away (see

Bug#1002353: marked as done (parso: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13)

Your message dated Thu, 08 Dec 2022 23:35:21 + with message-id and subject line Bug#1002353: fixed in parso 0.8.3-1 has caused the Debian Bug report #1002353, regarding parso: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13 to

Bug#1023986: marked as done (parso: too old to parse Python 3.11)

Your message dated Thu, 08 Dec 2022 23:35:21 + with message-id and subject line Bug#1023986: fixed in parso 0.8.3-1 has caused the Debian Bug report #1023986, regarding parso: too old to parse Python 3.11 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1012382: marked as done (pktanon: autopkgtest fails on s390x with: wrong pcap file version: should be 2.4)

Your message dated Thu, 8 Dec 2022 23:28:02 +0100 with message-id <04f3abe2-62b1-7c65-f5e4-fb38aacb7...@debian.org> and subject line Re: Bug#1012382: pktanon: autopkgtest fails on s390x with: wrong pcap file version: should be 2.4 has caused the Debian Bug report #1012382, regarding pktanon:

Bug#999143: dns-browse NMU to fix RC bugs.

Hi all, I plan to fix #999143 and #965494 by NMU. Please see the debdiff as attachment. My plan is I'll wait for 10 days to see if anyone stops me. And I'll upload to the delay/10 queue. The following changes are made: * Non-maintainer upload. * Port to DebSrc3.0 (quilt) * debian/rules:

Bug#1024224: marked as done (openscap-utils: FTBFS with libproc2)

Your message dated Thu, 08 Dec 2022 21:37:09 + with message-id and subject line Bug#1024224: fixed in openscap 1.3.6+dfsg-5 has caused the Debian Bug report #1024224, regarding openscap-utils: FTBFS with libproc2 to be marked as done. This means that you claim that the problem has been dealt

Bug#1024632: [Pkg-erlang-devel] Bug#1024632: erlang: CVE-2022-37026 Client Authentication Bypass

Sergei, Markus, On Wed, Nov 30, 2022 at 04:25:17PM +0300, Sergei Golovan wrote: > Hi Markus, > > On Wed, Nov 30, 2022 at 4:15 PM Markus Koschany wrote: > > > > Hello, > > > > I have prepared a security update for Bullseye which fixes CVE-2022-37026. > > Sergei could you review the update

Bug#1025213: i915g

The Gallium dri driver i915 22.3.0 also at my laptop is working and stops the flickering problem. Unfortunately it still is not supported and also has issues. Specially with shaders it is not compatible with classic i915. Less shaders are compiled without errors and also there is no fallback

Processed: libnewuoa breaks libpdb-redo autopkgtest: pdb-redo-example (Failed)

Processing control commands: > found -1 libnewuoa/0.1.2-1 Bug #1025778 [src:libnewuoa, src:libpdb-redo] libnewuoa breaks libpdb-redo autopkgtest: pdb-redo-example (Failed) Marked as found in versions libnewuoa/0.1.2-1. > found -1 libpdb-redo/2.0.3-1 Bug #1025778 [src:libnewuoa, src:libpdb-redo]

Bug#1025778: libnewuoa breaks libpdb-redo autopkgtest: pdb-redo-example (Failed)

Source: libnewuoa, libpdb-redo Control: found -1 libnewuoa/0.1.2-1 Control: found -1 libpdb-redo/2.0.3-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of libnewuoa the autopkgtest of libpdb-redo fails

Bug#1025777: qcustomplot: autopkgtest regression: collect2: error: ld returned 1 exit status

Source: qcustomplot Version: 2.1.0+dfsg1-3 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of qcustomplot the autopkgtest of qcustomplot fails in testing when that autopkgtest is run with the binary packages of qcustomplot from

Bug#1025775: libsdl2 breaks cataclysm-dda autopkgtest: Killing leaked background processes

Source: libsdl2, cataclysm-dda Control: found -1 libsdl2/2.26.0+dfsg-1 Control: found -1 cataclysm-dda/0.F-3-8 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of libsdl2 the autopkgtest of cataclysm-dda

Processed: libsdl2 breaks cataclysm-dda autopkgtest: Killing leaked background processes

Processing control commands: > found -1 libsdl2/2.26.0+dfsg-1 Bug #1025775 [src:libsdl2, src:cataclysm-dda] libsdl2 breaks cataclysm-dda autopkgtest: Killing leaked background processes Marked as found in versions libsdl2/2.26.0+dfsg-1. > found -1 cataclysm-dda/0.F-3-8 Bug #1025775 [src:libsdl2,

Bug#1025722: marked as done (duck fails with 'Can't close(GLOB(0x558bebc05958)) filehandle: 'Is a directory' at /usr/share/duck/lib/checks/patch_files.pm line 101')

Your message dated Thu, 08 Dec 2022 20:38:23 + with message-id and subject line Bug#1025722: fixed in duck 0.14.1 has caused the Debian Bug report #1025722, regarding duck fails with 'Can't close(GLOB(0x558bebc05958)) filehandle: 'Is a directory' at /usr/share/duck/lib/checks/patch_files.pm

Processed: r-cran-tmb: autopkgtest needs update for new version of rmatrix: Please re-install 'TMB' from source

Processing control commands: > affects -1 src:rmatrix Bug #1025772 [src:r-cran-tmb] r-cran-tmb: autopkgtest needs update for new version of rmatrix: Please re-install 'TMB' from source Added indication that 1025772 affects src:rmatrix -- 1025772:

Bug#1025772: r-cran-tmb: autopkgtest needs update for new version of rmatrix: Please re-install 'TMB' from source

Source: r-cran-tmb Version: 1.9.1-2 Severity: serious X-Debbugs-CC: rmat...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:rmatrix Dear maintainer(s), With a recent upload of rmatrix the autopkgtest of r-cran-tmb fails in

Bug#1025722: duck fails with 'Can't close(GLOB(0x558bebc05958)) filehandle: 'Is a directory' at /usr/share/duck/lib/checks/patch_files.pm line 101'

On Thu, Dec 08, 2022 at 12:45:29AM +0100, gregor herrmann wrote: > Package: duck > Version: 0.14.0 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: p...@packages.debian.org > As of today, duck (called in any source package directory) fails with > > Can't

Bug#1025722: duck fails with 'Can't close(GLOB(0x558bebc05958)) filehandle: 'Is a directory' at /usr/share/duck/lib/checks/patch_files.pm line 101'

Hi Gregor, Thanks for catching this. On Thu, 2022-12-08 at 00:45 +0100, gregor herrmann wrote: > As of today, duck (called in any source package directory) fails with > > Can't close(GLOB(0x558bebc05958)) filehandle: 'Is a directory' at > /usr/share/duck/lib/checks/patch_files.pm line 101' > >

Processed: severity of 1024218 is serious, severity of 1024219 is serious, severity of 1024220 is serious ...

Processing commands for cont...@bugs.debian.org: > severity 1024218 serious Bug #1024218 [apitrace] apitrace: FTBFS with libproc2 Severity set to 'serious' from 'important' > severity 1024219 serious Bug #1024219 [src:cpu-x] cpu-x: FTBFS with libproc2 Severity set to 'serious' from 'important' >

Bug#1024637: marked as done (libmartchus-qtforkawesome1: missing Breaks+Replaces: libmartchus-qtforkawesome0.0.3)

Your message dated Thu, 08 Dec 2022 19:51:11 + with message-id and subject line Bug#1024637: fixed in martchus-qtforkawesome 0.1.0-1 has caused the Debian Bug report #1024637, regarding libmartchus-qtforkawesome1: missing Breaks+Replaces: libmartchus-qtforkawesome0.0.3 to be marked as done.

Processed: tagging 995223

Processing commands for cont...@bugs.debian.org: > tags 995223 + bookworm sid Bug #995223 {Done: Matthias Klose } [src:libffi] libffi: autoconf incompatibility causes baseline violation Added tag(s) bookworm and sid. > thanks Stopping processing here. Please contact me if you need assistance.

Bug#1025765: torbrowser-launcher: Failed to download Tor Browser. Get '404'.

Package: torbrowser-launcher Version: 0.3.5-3 Severity: grave Justification: renders package unusable X-Debbugs-Cc: ajv...@gmail.com Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Run torbrowser-lunccher.

Bug#1024431: marked as done (libgccjit0: missing Depends: libc6-dev)

Your message dated Thu, 08 Dec 2022 18:49:53 + with message-id and subject line Bug#1024431: fixed in gcc-12 12.2.0-9.1 has caused the Debian Bug report #1024431, regarding libgccjit0: missing Depends: libc6-dev to be marked as done. This means that you claim that the problem has been dealt

Processed: Fixing in bullseye

Processing commands for cont...@bugs.debian.org: > reopen 1013554 Bug #1013554 {Done: Mathias Gibbens } [src:golang-github-valyala-tcplisten] golang-github-valyala-tcplisten: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/valyala/tcplisten returned exit code 1

Bug#1013554: Fixing in bullseye

reopen 1013554 found 1013554 0.0~git20210309.652d3b4-1 fixed 1013554 0.0~git20210309.652d3b4-2 thanks Hello. Please consider an upload for bullseye, as packages in stable must build in stable. The attached debdiff may help (I've merely applied the patch from bookworm and added a changelog

Bug#1025743: marked as done (libfftw3-dev: Tests fails)

Your message dated Thu, 08 Dec 2022 17:35:02 + with message-id and subject line Bug#1025743: fixed in gsequencer 4.4.3-1 has caused the Debian Bug report #1025743, regarding libfftw3-dev: Tests fails to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1025308: marked as done (gsequencer: FTBFS with fftw3 (3.3.10-1))

Your message dated Thu, 08 Dec 2022 17:35:02 + with message-id and subject line Bug#1025308: fixed in gsequencer 4.4.3-1 has caused the Debian Bug report #1025308, regarding gsequencer: FTBFS with fftw3 (3.3.10-1) to be marked as done. This means that you claim that the problem has been

Bug#1025761: opendrop FTBFS with sundials 6.4.1

Source: opendrop Version: 3.3.1-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=opendrop=3.3.1-3%2Bb3 ... In file included from include/opendrop/younglaplace.hpp:135, from opendrop/fit/younglaplace/.checkpoints/shape.cpp:763:

Processed: fixed 1005747 in 0.19.1+dfsg1-2+deb11u1

Processing commands for cont...@bugs.debian.org: > fixed 1005747 0.19.1+dfsg1-2+deb11u1 Bug #1005747 {Done: Steffen Moeller } [src:freecad] freecad: CVE-2021-45844 - Improper sanitization in the invocation of ODA File Converter Marked as fixed in versions freecad/0.19.1+dfsg1-2+deb11u1. >

Bug#1013508: marked as done (django-testscenarios: FTBFS: ImportError: cannot import name 'reorder_suite' from 'django.test.runner' (/usr/lib/python3/dist-packages/django/test/runner.py))

Your message dated Thu, 08 Dec 2022 17:30:03 + with message-id and subject line Bug#1025643: Removed package(s) from unstable has caused the Debian Bug report #1013508, regarding django-testscenarios: FTBFS: ImportError: cannot import name 'reorder_suite' from 'django.test.runner'

Bug#1013933: Keep xsane out of Debian releases

Please consider reducing the severity of the bug to allow the inclusion of xsane in the next stable release. xsane has no equivalent software available. Its GUI allows you to use advanced features of SANE not available graphically in other GUIs. xsane is usable in the currently packaged

Bug#1024278: libgssglue: autopkgtest failure with pkgconf

Hey Simon, On Thu, Nov 17, 2022 at 12:46:19PM +0100, Sebastian Ramacher wrote: > > I see. If so, it would be good if pkgconf was made consistent with > > pkg-config here, if the intention is to replace it. > > This discussion needs to happen with the pkgconf maintainer / upstream. > But since

Bug#1025757: dyssol FTBFS with sundials 6.4.1

Source: dyssol Version: 1.0.2+ds2-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=dyssol=1.0.2%2Bds2-1%2Bb1 ... /<>/EquationSolvers/DAESolver.cpp: In member function ‘bool CDAESolver::SetModel(CDAEModel*)’: /<>/EquationSolvers/DAESolver.cpp:56:30: error: too few

Processed: Re: Bug#1025739: hmmer2: missing source for configure

Processing control commands: > tags -1 moreinfo Bug #1025739 [src:hmmer2] hmmer2: missing source for configure Added tag(s) moreinfo. -- 1025739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1025739: hmmer2: missing source for configure

Control: tags -1 moreinfo Hi Helmut Am Thu, Dec 08, 2022 at 09:57:56AM +0100 schrieb Helmut Grohne: > The source code for the file configure in the source tarball is missing. > This violates DFSG #2. I agree that this configure script looks auto generated but IMHO it can be considered machine

Bug#1025753: FTBFS: Java compilation error (cannot find symbols)

Source: jruby-openssl Version: 0.9.21-4 Severity: serious Tags: ftbfs Dear Maintainer, jruby-openssl currently fails to build with the following error message: [ERROR] COMPILATION ERROR : [INFO] - [ERROR]

Bug#1022404: raqm: diff for NMU version 0.7.0-4.1

Also, I suggest bumping harbuzz in Build-Depends. I don't know the exact version needed, setting it to 5.2 is probably ok. Thank you, Jeremy Bicha

Bug#1025105: marked as done (python-hypothesis: (autopkgtest) needs update for python3.11: AssertionError)

Your message dated Thu, 08 Dec 2022 15:37:36 + with message-id and subject line Bug#1025105: fixed in python-hypothesis 6.60.0-1 has caused the Debian Bug report #1025105, regarding python-hypothesis: (autopkgtest) needs update for python3.11: AssertionError to be marked as done. This means

Bug#1025285: marked as done (nvidia-graphics-drivers-tesla-470: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675, CVE-2022-34677, CVE-2022-34679, CVE-2022-34680, CVE-2022-34682, CVE-2022-42254, CVE-2022

Your message dated Thu, 08 Dec 2022 15:06:16 + with message-id and subject line Bug#1025285: fixed in nvidia-graphics-drivers-tesla-470 470.161.03-1 has caused the Debian Bug report #1025285, regarding nvidia-graphics-drivers-tesla-470: CVE-2022-34670, CVE-2022-34674, CVE-2022-34675,

Bug#1025309: jamin: FTBFS with fftw3 (3.3.10-1)

On 12/2/22 13:03, Bas Couwenberg wrote: The attached patch resolves the issue by changing the dependency to libfftw3-dev. The patch is applied in git: https://salsa.debian.org/multimedia-team/jamin/-/commit/92a3958d9af04a8b1e3a8f9c6b39ce946976810f Jonas has removed himself from Uploaders

Processed: Bug#1025309 marked as pending in jamin

Processing control commands: > tag -1 pending Bug #1025309 [src:jamin] jamin: FTBFS with fftw3 (3.3.10-1) Added tag(s) pending. -- 1025309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1025309: marked as pending in jamin

Control: tag -1 pending Hello, Bug #1025309 in jamin reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1025746: vienna-rna: FTBFS: Package 'RNAlib2', required by 'virtual:world', not found

Source: vienna-rna Version: 2.4.17+dfsg-2 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) Hi, vienna-rna recently started to FTBFS, this is probably related to a change in the toolchain or a build dependency: ... checking

Processed: Re: Bug#1025743: Acknowledgement (libfftw3-dev: Tests fails)

Processing commands for cont...@bugs.debian.org: > reassign 1025743 gsequencer Bug #1025743 [libfftw3-dev] libfftw3-dev: Tests fails Bug reassigned from package 'libfftw3-dev' to 'gsequencer'. No longer marked as found in versions fftw3/3.3.10-1. Ignoring request to alter fixed versions of bug

Bug#1025743: Acknowledgement (libfftw3-dev: Tests fails)

reassign 1025743 gsequencer thanks On 08 déc. 2022 13:18, "Debian Bug Tracking System" wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress on this Bug here: 1025743: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025743. I did this bug report too

Bug#1025712: marked as done (marble: autopkgtest regression in 22.08.3-{1,2})

Your message dated Thu, 08 Dec 2022 13:20:52 + with message-id and subject line Bug#1025712: fixed in marble 4:22.08.3-3 has caused the Debian Bug report #1025712, regarding marble: autopkgtest regression in 22.08.3-{1,2} to be marked as done. This means that you claim that the problem has

Bug#1025711: marked as done (marble: qtwebengine5-dev build dependency restriction does not work)

Your message dated Thu, 08 Dec 2022 13:20:52 + with message-id and subject line Bug#1025711: fixed in marble 4:22.08.3-3 has caused the Debian Bug report #1025711, regarding marble: qtwebengine5-dev build dependency restriction does not work to be marked as done. This means that you claim

Bug#1025743: libfftw3-dev: Tests fails

Package: libfftw3-dev Version: 3.3.10-1 Severity: serious Dear Maintainer, As tests fails, fftw3 is stuck in unstable. >From >https://ci.debian.net/data/autopkgtest/testing/amd64/g/gsequencer/29127797/log.gz , | autopkgtest: WARNING: package gsequencer is not installed though it should be

Bug#1022386: marked as done (libjs-webrtc-adapter: FTBFS: make[1]: *** [debian/rules:26: out/adapter.js] Error 1)

Your message dated Thu, 08 Dec 2022 12:55:39 + with message-id and subject line Bug#1022386: fixed in libjs-webrtc-adapter 8.2.0~ds-1 has caused the Debian Bug report #1022386, regarding libjs-webrtc-adapter: FTBFS: make[1]: *** [debian/rules:26: out/adapter.js] Error 1 to be marked as done.

Bug#1024577: marked as done (libzypp: FTBFS against libgpgme-dev >= 1.18.0-2)

Your message dated Thu, 08 Dec 2022 12:55:51 + with message-id and subject line Bug#1024577: fixed in libzypp 17.25.7-2.3 has caused the Debian Bug report #1024577, regarding libzypp: FTBFS against libgpgme-dev >= 1.18.0-2 to be marked as done. This means that you claim that the problem has

Bug#1023328: marked as done (janus: Fail to build with rollup 3)

Your message dated Thu, 08 Dec 2022 13:34:02 +0100 with message-id <167050284277.969220.11867191344416924...@auryn.jones.dk> and subject line Re: Bug#1023328: Patch for rollup 3 has caused the Debian Bug report #1023328, regarding janus: Fail to build with rollup 3 to be marked as done. This

Processed: Bug#1022386 marked as pending in libjs-webrtc-adapter

Processing control commands: > tag -1 pending Bug #1022386 [src:libjs-webrtc-adapter] libjs-webrtc-adapter: FTBFS: make[1]: *** [debian/rules:26: out/adapter.js] Error 1 Added tag(s) pending. -- 1022386: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022386 Debian Bug Tracking System

Bug#1022386: marked as pending in libjs-webrtc-adapter

Control: tag -1 pending Hello, Bug #1022386 in libjs-webrtc-adapter reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#1024577: libzypp: diff for NMU version 17.25.7-2.3

Control: tags 1024577 + patch [Replace XX with correct value] Hello Mike, I've prepared an NMU for libzypp (versioned as 17.25.7-2.3) and uploaded it, non-delayed as LowThresholdNmu. Kind regards Andreas diff -Nru libzypp-17.25.7/debian/changelog libzypp-17.25.7/debian/changelog ---

Processed: libzypp: diff for NMU version 17.25.7-2.3

Processing control commands: > tags 1024577 + patch Bug #1024577 [src:libzypp] libzypp: FTBFS against libgpgme-dev >= 1.18.0-2 Added tag(s) patch. -- 1024577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024577 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1025201: marked as done (tkcalendar: (autopkgtest) needs update for two supported python versions: Xvfb failed to start)

Your message dated Thu, 08 Dec 2022 12:06:47 + with message-id and subject line Bug#1025201: fixed in tkcalendar 1.6.1-3 has caused the Debian Bug report #1025201, regarding tkcalendar: (autopkgtest) needs update for two supported python versions: Xvfb failed to start to be marked as done.

Processed: your mail

Processing commands for cont...@bugs.debian.org: > forwarded 1025732 https://github.com/pengutronix/genimage/issues/200 Bug #1025732 {Done: Paul Gevers } [src:genimage] src:genimage: fails to migrate to testing for too long: FTBFS (testsuite fails) on 32 bits systems Set Bug

Bug#1024954: librcsb-core-wrapper: (autopkgtest) needs update for python3.11: initialization of CorePyWrap raised unreported exception

Hi again, On Mon, Nov 28, 2022 at 08:05:35PM +0530, Nilesh Patra wrote: > On Sun, 27 Nov 2022 22:26:31 +0100 Paul Gevers wrote: > > Source: librcsb-core-wrapper > > Version: 1.005-10 > > We are in the transition of adding python3.11 as a supported Python > > version [0]. > > [...] > > [0]

Bug#1025739: hmmer2: missing source for configure

Source: hmmer2 Version: 2.3.2+dfsg-7 Severity: serious Justification: DFSG #2 Hi, The source code for the file configure in the source tarball is missing. This violates DFSG #2. Helmut

Processed: severity of 1025736 is important

Processing commands for cont...@bugs.debian.org: > # riscv64 is not a release architecture, so bugs specific to it are not RC > severity 1025736 important Bug #1025736 [nodejs] nodejs: Always segfaults on riscv64 Severity set to 'important' from 'grave' > thanks Stopping processing here. Please

Bug#1025736: nodejs: Always segfaults on riscv64

Package: nodejs Version: 18.12.1+dfsg-2+0.riscv64.1 Severity: grave Justification: renders package unusable X-Debbugs-Cc: davidventura27+deb...@gmail.com Dear Maintainer, * What led up to the situation? Trying to execute nodejs in any condition under riscv64. * What exactly did you do

Bug#1025380: marked as done (python3-fissix: SyntaxError: Missing parentheses in call to 'print')

Your message dated Thu, 08 Dec 2022 10:50:04 + with message-id and subject line Bug#1025380: fixed in python-fissix 21.6.6-3 has caused the Debian Bug report #1025380, regarding python3-fissix: SyntaxError: Missing parentheses in call to 'print' to be marked as done. This means that you

Bug#1025380: marked as pending in python-fissix

Control: tag -1 pending Hello, Bug #1025380 in python-fissix reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1025380 marked as pending in python-fissix

Processing control commands: > tag -1 pending Bug #1025380 [python3-fissix] python3-fissix: SyntaxError: Missing parentheses in call to 'print' Added tag(s) pending. -- 1025380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025380 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1024443: marked as done (asterisk-modules no longer includes chan_sip which breaks existing configs)

Your message dated Thu, 08 Dec 2022 10:04:27 + with message-id and subject line Bug#1024443: fixed in asterisk 1:20.0.1~dfsg+~cs6.12.40431414-1 has caused the Debian Bug report #1024443, regarding asterisk-modules no longer includes chan_sip which breaks existing configs to be marked as

Bug#1017524: [DRE-maint] Bug#1017524: status?

On 23/11/22 04:48 PM, Cédric Boutillier wrote: > Hi, > > I recently looked at failures in jekyll. > > Jekyll is broken in several ways in unstable due to version constraints > on the dependencies. One can easily relax the > version dependency on mercenary in the gemdeps (no changes needed). > >

Bug#1025733: libxmlada: unsatisfiable buil-dependency on unicode-data

Source: libxmlada Version: 22.0.0-3 Severity: serious Hi, libxmlada build-depends (in Build-Depends-Arch) on unicode-data (>= 14~), unicode-data (<< 15~) but the version of unicode-data in sid is 15.0.0-1. -Ralf.