Processed: tagging 1023327, tagging 1023328

Processing commands for cont...@bugs.debian.org: > tags 1023327 + ftbfs Bug #1023327 [notepadqq] notepadqq: Fail to build with rollup 3 Added tag(s) ftbfs. > tags 1023328 + ftbfs Bug #1023328 [janus] janus: Fail to build with rollup 3 Added tag(s) ftbfs. > thanks Stopping processing here. Please

Processed: severity of 1023327 is serious, severity of 1023328 is serious

Processing commands for cont...@bugs.debian.org: > severity 1023327 serious Bug #1023327 [notepadqq] notepadqq: Fail to build with rollup 3 Severity set to 'serious' from 'important' > severity 1023328 serious Bug #1023328 [janus] janus: Fail to build with rollup 3 Severity set to 'serious' from

Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

On 2022-11-02 14:24:51 +0200, Eli Zaretskii wrote: > Signal 1 is SIGHUP, AFAIU. Why should Emacs receive SIGHUP in the > middle of GC, I have no idea. Maybe ask the user what was he doing at > that time. E.g., could that be a remote Emacs session? No, it is on my local machine. On 2022-11-02

Bug#999280: empire-lafe: diff for NMU version 1.1-1.1

No need to delay. Total possible impact one way or another would be really low, and they can rebuild if they need to. I haven't used it in a decade, and am surprised my deadline hacks have survived all this time. I don't currently have a known working build system. -Dtake On Wed, Nov 2,

Bug#1023284: libevent: FTBFS with glibc 2.36

Nicolas Mora, le mer. 02 nov. 2022 19:14:51 -0400, a ecrit: > If I understand correctly, removing the symbols evutil_secure_rng_add_bytes > from the symbols files is enough to fix this bug? It will make the package build again. But possibly some binaries in Debian are using that symbol, that'd

Bug#1023317: Bug#1023318 / Bug#1023317: {screen,zsh}: re-adds /usr/bin/{screen,zsh} to /etc/shells on upgrade

Hi Helmut, thanks for these bug reports and making us aware of this type of issue. Some more hints about how this all is meant to work and why it actually works would have been appreciated, though: Helmut Grohne wrote: > When upgrading or reinstalling screen, it adds /usr/bin/screen to >

Bug#1023373: bibledit:

Source: bibledit Version: 5.0.988-3 Severity: serious Control: affects -1 bibledit-cloud This is a follow-up on #1017083. Aside from the embedded quill still not being built from source, quill/source/docs/_includes/analytics.html is clearly a non-source file that applies Google Analytics, which

Processed: bibledit:

Processing control commands: > affects -1 bibledit-cloud Bug #1023373 [src:bibledit] bibledit: Added indication that 1023373 affects bibledit-cloud -- 1023373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: icmpush: diff for NMU version 2.2-6.2

Processing control commands: > tags 999158 + patch Bug #999158 [src:icmpush] icmpush: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999158 + pending Bug #999158 [src:icmpush] icmpush: missing required debian/rules targets build-arch and/or

Bug#999158: icmpush: diff for NMU version 2.2-6.2

Control: tags 999158 + patch Control: tags 999158 + pending Dear maintainer, I've prepared an NMU for icmpush (versioned as 2.2-6.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u icmpush-2.2/debian/changelog icmpush-2.2/debian/changelog

Bug#1023284: libevent: FTBFS with glibc 2.36

Hello, If I understand correctly, removing the symbols evutil_secure_rng_add_bytes from the symbols files is enough to fix this bug? If no objection, I'll upload the fixed package tomorrow.

Processed: icheck: diff for NMU version 0.9.7-6.4

Processing control commands: > tags 999090 + patch Bug #999090 [src:icheck] icheck: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999090 + pending Bug #999090 [src:icheck] icheck: missing required debian/rules targets build-arch and/or

Bug#999090: icheck: diff for NMU version 0.9.7-6.4

Control: tags 999090 + patch Control: tags 999090 + pending Dear maintainer, I've prepared an NMU for icheck (versioned as 0.9.7-6.4) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u icheck-0.9.7/debian/changelog

Processed: grpn: diff for NMU version 1.4.1-1.1

Processing control commands: > tags 999170 + patch Bug #999170 [src:grpn] grpn: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999170 + pending Bug #999170 [src:grpn] grpn: missing required debian/rules targets build-arch and/or build-indep Added

Bug#999170: grpn: diff for NMU version 1.4.1-1.1

Control: tags 999170 + patch Control: tags 999170 + pending Dear maintainer, I've prepared an NMU for grpn (versioned as 1.4.1-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru grpn-1.4.1/debian/changelog grpn-1.4.1/debian/changelog

Processed: gpsim-doc: diff for NMU version 0.22.0-2.2

Processing control commands: > tags 999299 + patch Bug #999299 [src:gpsim-doc] gpsim-doc: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999299 + pending Bug #999299 [src:gpsim-doc] gpsim-doc: missing required debian/rules targets build-arch

Bug#999299: gpsim-doc: diff for NMU version 0.22.0-2.2

Control: tags 999299 + patch Control: tags 999299 + pending Dear maintainer, I've prepared an NMU for gpsim-doc (versioned as 0.22.0-2.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u gpsim-doc-0.22.0/debian/changelog

Processed: gnuboy: diff for NMU version 1.0.3-7.2

Processing control commands: > tags 998967 + patch Bug #998967 [src:gnuboy] gnuboy: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 998967 + pending Bug #998967 [src:gnuboy] gnuboy: missing required debian/rules targets build-arch and/or

Bug#998967: gnuboy: diff for NMU version 1.0.3-7.2

Control: tags 998967 + patch Control: tags 998967 + pending Dear maintainer, I've prepared an NMU for gnuboy (versioned as 1.0.3-7.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u gnuboy-1.0.3/debian/changelog

Processed: g3data: diff for NMU version 1:1.5.3-3.1

Processing control commands: > tags 999267 + patch Bug #999267 [src:g3data] g3data: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999267 + pending Bug #999267 [src:g3data] g3data: missing required debian/rules targets build-arch and/or

Bug#999267: g3data: diff for NMU version 1:1.5.3-3.1

Control: tags 999267 + patch Control: tags 999267 + pending Dear maintainer, I've prepared an NMU for g3data (versioned as 1:1.5.3-3.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u g3data-1.5.3/debian/changelog

Processed: floatbg: diff for NMU version 1.0-28.1

Processing control commands: > tags 999330 + patch Bug #999330 [src:floatbg] floatbg: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999330 + pending Bug #999330 [src:floatbg] floatbg: missing required debian/rules targets build-arch and/or

Bug#999330: floatbg: diff for NMU version 1.0-28.1

Control: tags 999330 + patch Control: tags 999330 + pending Dear maintainer, I've prepared an NMU for floatbg (versioned as 1.0-28.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u floatbg-1.0/debian/rules floatbg-1.0/debian/rules ---

Bug#998942: farpd: diff for NMU version 0.2-11.1

Control: tags 998942 + patch Control: tags 998942 + pending Dear maintainer, I've prepared an NMU for farpd (versioned as 0.2-11.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u farpd-0.2/debian/rules farpd-0.2/debian/rules ---

Processed: farpd: diff for NMU version 0.2-11.1

Processing control commands: > tags 998942 + patch Bug #998942 [src:farpd] farpd: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 998942 + pending Bug #998942 [src:farpd] farpd: missing required debian/rules targets build-arch and/or build-indep

Bug#1020456: marked as done (cypari2 FTBFS with PARI 2.15.0)

Your message dated Wed, 02 Nov 2022 22:20:59 + with message-id and subject line Bug#1020456: fixed in cypari2 2.1.2-3 has caused the Debian Bug report #1020456, regarding cypari2 FTBFS with PARI 2.15.0 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: closing 1022385

Processing commands for cont...@bugs.debian.org: > close 1022385 3.0.6-1 Bug #1022385 [src:pcb-rnd] pcb-rnd: FTBFS: diff: out.copper_p2.svg: No such file or directory The source 'pcb-rnd' and version '3.0.6-1' do not appear to match any binary packages Marked as fixed in versions

Bug#1017711: emacs-gtk: terminated with signal SIGABRT, 137 MB coredump

Hello Vincent, Upstream says there isn't enough information in the backtrace to say anything helpful about this. Could you take a look at and consider supplying more information over there, please? Also, are you able to reproduce this with 'emacs -q' (not -Q)?

Bug#1023365: prusa-slicer: Wrong wxWidgets Version linked during debian Build resulting in instant SIGSEGV on launch (due to lacking wxWidgets 3.2 support)

Package: prusa-slicer Version: 2.5.0+dfsg-2 Severity: grave Justification: renders package unusable X-Debbugs-Cc: t...@beamnet.de, t...@debian.org, onit...@gmail.com The wrong wxWidgets Version is linked during the build. Normally debian/rules specifies WX_STABLE=1 which should result in the

Bug#999280: empire-lafe: diff for NMU version 1.1-1.1

Control: tags 999280 + patch Control: tags 999280 + pending Dear maintainer, I've prepared an NMU for empire-lafe (versioned as 1.1-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u empire-lafe-1.1/debian/changelog

Processed: empire-lafe: diff for NMU version 1.1-1.1

Processing control commands: > tags 999280 + patch Bug #999280 [src:empire-lafe] empire-lafe: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999280 + pending Bug #999280 [src:empire-lafe] empire-lafe: missing required debian/rules targets

Bug#1023361: jupyter-core: CVE-2022-39286: Execution with Unnecessary Privileges in JupyterApp

Source: jupyter-core Version: 4.11.1-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for jupyter-core. CVE-2022-39286[0]: | Jupyter Core is a package for the core common functionality of Jupyter |

Bug#1016070: marked as done (sbuild: autopkgtest fails with "No space left on device")

Your message dated Wed, 02 Nov 2022 21:06:14 + with message-id and subject line Bug#1016070: fixed in sbuild 0.84.0 has caused the Debian Bug report #1016070, regarding sbuild: autopkgtest fails with "No space left on device" to be marked as done. This means that you claim that the problem

Processed: dsh: diff for NMU version 0.25.10-1.5

Processing control commands: > tags 999207 + patch Bug #999207 [src:dsh] dsh: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999207 + pending Bug #999207 [src:dsh] dsh: missing required debian/rules targets build-arch and/or build-indep Added

Bug#999207: dsh: diff for NMU version 0.25.10-1.5

Control: tags 999207 + patch Control: tags 999207 + pending Dear maintainer, I've prepared an NMU for dsh (versioned as 0.25.10-1.5) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u dsh-0.25.10/debian/changelog dsh-0.25.10/debian/changelog

Processed: dircproxy: diff for NMU version 1.0.5-6.1

Processing control commands: > tags 999031 + patch Bug #999031 [src:dircproxy] dircproxy: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999031 + pending Bug #999031 [src:dircproxy] dircproxy: missing required debian/rules targets build-arch

Bug#999031: dircproxy: diff for NMU version 1.0.5-6.1

Control: tags 999031 + patch Control: tags 999031 + pending Dear maintainer, I've prepared an NMU for dircproxy (versioned as 1.0.5-6.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u dircproxy-1.0.5/debian/changelog

Processed: deps: diff for NMU version 0.13-4.2

Processing control commands: > tags 999186 + patch Bug #999186 [src:deps] deps: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999186 + pending Bug #999186 [src:deps] deps: missing required debian/rules targets build-arch and/or build-indep Added

Bug#999186: deps: diff for NMU version 0.13-4.2

Control: tags 999186 + patch Control: tags 999186 + pending Dear maintainer, I've prepared an NMU for deps (versioned as 0.13-4.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u deps-0.13/debian/changelog deps-0.13/debian/changelog ---

Processed: cappuccino: diff for NMU version 0.5.1-10.1

Processing control commands: > tags 999145 + patch Bug #999145 [src:cappuccino] cappuccino: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999145 + pending Bug #999145 [src:cappuccino] cappuccino: missing required debian/rules targets build-arch

Bug#999145: cappuccino: diff for NMU version 0.5.1-10.1

Control: tags 999145 + patch Control: tags 999145 + pending Dear maintainer, I've prepared an NMU for cappuccino (versioned as 0.5.1-10.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -u cappuccino-0.5.1/debian/changelog

Bug#1020995: marked as done (opengv: binary-all FTBFS)

Your message dated Wed, 02 Nov 2022 20:35:14 + with message-id and subject line Bug#1020995: fixed in opengv 1.0+1git91f4b1-6 has caused the Debian Bug report #1020995, regarding opengv: binary-all FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1023357: python3-morse-simulator: depends on non-existing python3 (< 3.9)

Package: python3-morse-simulator Version: 1.4-6+b1 Severity: serious Hi, python3-morse-simulator depends on python3 (< 3.9) which is only satisfiable in oldstable or older. -Ralf.

Bug#1023356: libdune-pdelab-dev: unsatisfiable dependency on libdune-common-2.7.0

Package: libdune-pdelab-dev Version: 2.7~20200605-2 Severity: serious Hi, this package depends on libdune-common-2.7.0 which does not exist in sid. -Ralf.

Bug#1023355: limereg: depends on non-existing libboost-program-options1.67.0

Package: limereg Version: 1.4.1-4+b1 Severity: serious Hi, limereg depends on libboost-program-options1.67.0 which only exists in oldstable. -Ralf.

Bug#1019995: marked as done (supercollider: FTBFS: sndfile.h:356:33: error: conflicting declaration ‘typedef struct sf_private_tag SNDFILE’)

Your message dated Wed, 02 Nov 2022 19:14:24 + with message-id and subject line Bug#1019995: fixed in supercollider 1:3.12.2+repack-1 has caused the Debian Bug report #1019995, regarding supercollider: FTBFS: sndfile.h:356:33: error: conflicting declaration ‘typedef struct sf_private_tag

Bug#1022991: marked as done (libc6: broken y2038 support in fstatat on mips64el)

Your message dated Wed, 02 Nov 2022 19:06:24 + with message-id and subject line Bug#1022991: fixed in glibc 2.36-4 has caused the Debian Bug report #1022991, regarding libc6: broken y2038 support in fstatat on mips64el to be marked as done. This means that you claim that the problem has been

Processed: Bug#1022991 marked as pending in glibc

Processing control commands: > tag -1 pending Bug #1022991 [libc6] libc6: broken y2038 support in fstatat on mips64el Added tag(s) pending. -- 1022991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022991 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1022991: marked as pending in glibc

Control: tag -1 pending Hello, Bug #1022991 in glibc 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#1007984: netpbm-free ready to upload

Hi Andreas, Am Thu, Oct 06, 2022 at 07:09:13PM +0200 schrieb Andreas Metzler: > > I noticed you added some missing information to d/copyright > > of netpbm-free. Thanks a lot for doing so. Do you think it > > is time for another upload? > > I invested a couple of hours but sadly it is not a

Processed: closing 1022458

Processing commands for cont...@bugs.debian.org: > close 1022458 2.1.0-3 Bug #1022458 [src:pgl-ddl-deploy] pgl-ddl-deploy: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked as fixed in versions pgl-ddl-deploy/2.1.0-3. Bug #1022458

Processed: Re: Bug#1023348: Null dereference in dentry_unlink_inode / kswapd

Processing control commands: > severity -1 normal Bug #1023348 [src:linux] Null dereference in dentry_unlink_inode / kswapd Severity set to 'normal' from 'critical' -- 1023348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023348 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1023348: Null dereference in dentry_unlink_inode / kswapd

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'),

Bug#998933: marked as done (cgilib: missing required debian/rules targets build-arch and/or build-indep)

Your message dated Wed, 02 Nov 2022 18:19:16 + with message-id and subject line Bug#998933: fixed in cgilib 0.6-2 has caused the Debian Bug report #998933, regarding cgilib: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim

Bug#1023224: [Pkg-swan-devel] Bug#1023224: strongswan: autopkgtest regression: depends on no longer built strongswan-scepclient

Hi Yves-Alexis, On 02-11-2022 17:27, Yves-Alexis Perez wrote: I'm not sure why the test is failing then and what I should have done differently. Could you give me some pointers here? https://sources.debian.org/src/strongswan/5.9.8-1/debian/tests/control/ line 2 says that the *first* two

Bug#1022478: closing 1022478

close 1022478 1.4.2-2 thanks

Processed: closing 1022522

Processing commands for cont...@bugs.debian.org: > close 1022522 1:2.0.10-5 Bug #1022522 {Done: Christoph Berg } [src:postgresql-pllua] postgresql-pllua: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Ignoring request to alter fixed versions

Bug#1022522: closing 1022522

close 1022522 1:2.0.10-5 thanks

Processed: closing 1022478

Processing commands for cont...@bugs.debian.org: > close 1022478 1.4.2-2 Bug #1022478 {Done: Christoph Berg } [src:pg-cron] pg-cron: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Ignoring request to alter fixed versions of bug #1022478 to

Processed: closing 1022522

Processing commands for cont...@bugs.debian.org: > close 1022522 1:2.0.10-5 Bug #1022522 [src:postgresql-pllua] postgresql-pllua: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked as fixed in versions postgresql-pllua/1:2.0.10-5. Bug

Processed: closing 1022478

Processing commands for cont...@bugs.debian.org: > close 1022478 1.4.2-2 Bug #1022478 [src:pg-cron] pg-cron: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked as fixed in versions pg-cron/1.4.2-2. Bug #1022478 [src:pg-cron] pg-cron:

Processed: found 1022957 in 0.0.0+git.2021.03.30.1a3320dab9-2

Processing commands for cont...@bugs.debian.org: > found 1022957 0.0.0+git.2021.03.30.1a3320dab9-2 Bug #1022957 [nex] nex: /usr/bin/nex is already provided by the nvi package Marked as found in versions golang-github-blynn-nex/0.0.0+git.2021.03.30.1a3320dab9-2. > thanks Stopping processing here.

Bug#1023348: amended syslog snippet

I missed the first three lines of the syslog snippet containing the BUG event, inlined here: Oct 31 16:27:48 gonzo kernel: BUG: kernel NULL pointer dereference, address: 0028 Oct 31 16:27:48 gonzo kernel: #PF: supervisor write access in kernel mode Oct 31 16:27:48 gonzo kernel: #PF:

Bug#1023348: Null dereference in dentry_unlink_inode / kswapd

Package: src:linux Version: 5.10.4-1 Severity: critical Tags: upstream X-Debbugs-Cc: nat...@acmeaom.com Apologies if this isn't the right venue for this, doing my best here. Attachment descriptions b1 - syslog from BUG event b2 - syslog from 12+ hours later preceding total system hang b3 -

Bug#998933: cgilib: diff for NMU version 0.6-1.2

Hi Andreas! On Wed, Nov 02, 2022 at 02:50:12PM +0100, Andreas Beckmann wrote: [...] > cgilib is orphaned, so you should rather do a QA upload ;-) > Heheh, sorry for that, and thanks for the info :D The Maintainer field has not been changed, and I prepared a series of NMUs against the same

Bug#1023224: [Pkg-swan-devel] Bug#1023224: strongswan: autopkgtest regression: depends on no longer built strongswan-scepclient

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2022-10-31 at 21:01 +0100, Paul Gevers wrote: > With a recent upload of strongswan the autopkgtest of strongswan fails > in testing when that autopkgtest is run with the binary packages of > strongswan from unstable. It passes when run

Bug#1019804: marked as done (plee-the-bear: Please transition to wxwidgets3.2)

Your message dated Wed, 02 Nov 2022 16:05:30 + with message-id and subject line Bug#1019804: fixed in plee-the-bear 0.6.0-8 has caused the Debian Bug report #1019804, regarding plee-the-bear: Please transition to wxwidgets3.2 to be marked as done. This means that you claim that the problem

Bug#1023341: Fails to add any event due to too new python3-tzlocal

Package: khal Version: 1:0.10.4~ds-4 Severity: grave Hi, Adding a any new events on bookworm fails like (example is copied from the manpage): $ khal new 18:00 Awesome Event /usr/lib/python3/dist-packages/khal/icalendar.py:104: PytzUsageWarning: The localize method is no longer necessary, as

Bug#1022348: marked as done (gpgme1.0: FTBFS: Could not find gpg-error-config. Please install the libgpg-error development package.)

Your message dated Wed, 02 Nov 2022 15:50:31 + with message-id and subject line Bug#1022348: fixed in gpgme1.0 1.18.0-2 has caused the Debian Bug report #1022348, regarding gpgme1.0: FTBFS: Could not find gpg-error-config. Please install the libgpg-error development package. to be marked as

Bug#1020456: cypari2 FTBFS with PARI 2.15.0

On Fri, Oct 28, 2022 at 07:26:09PM +, Tobias Hansen wrote: > Thanks! I will apply the patch once the pari version with the other fixes is > uploaded. Great! I uploaded it today (pari 2.15.1~pre1-1). I hope it will be OK. Cheers, -- Bill. Imagine a large red swirl here.

Bug#1022348: [pkg-gnupg-maint] Bug#1022348: gpgme1.0: FTBFS: Could not find gpg-error-config. Please install the libgpg-error development package.

On Wed 2022-10-26 18:17:11 +0200, Andreas Metzler wrote: > On 2022-10-26 Andreas Metzler wrote: > [...] >> Which has been promptly fixed. Find attached debdiffs for a proposed >> upload. - I can also massage this into a mergew-request or push >> directly to https://salsa.debian.org/debian/gpgme

Bug#1022289: marked as done (libassuan: FTBFS: configure: error: libgpg-error was not found)

Your message dated Wed, 02 Nov 2022 14:49:08 + with message-id and subject line Bug#1022289: fixed in libassuan 2.5.5-5 has caused the Debian Bug report #1022289, regarding libassuan: FTBFS: configure: error: libgpg-error was not found to be marked as done. This means that you claim that the

Bug#998933: cgilib: diff for NMU version 0.6-1.2

Hi Marcos, On Wed, 2 Nov 2022 00:21:56 -0300 Marcos Talau wrote: I've prepared an NMU for cgilib (versioned as 0.6-1.2) and cgilib is orphaned, so you should rather do a QA upload ;-) Andreas

Bug#1022674: marked as done (three.js: Unable to build with rollup 3)

Your message dated Wed, 02 Nov 2022 13:22:24 + with message-id and subject line Bug#1022674: fixed in three.js 111+dfsg1-3 has caused the Debian Bug report #1022674, regarding three.js: Unable to build with rollup 3 to be marked as done. This means that you claim that the problem has been

Processed: bug 1022577 is forwarded to https://github.com/llvm/llvm-project/issues/58514

Processing commands for cont...@bugs.debian.org: > forwarded 1022577 https://github.com/llvm/llvm-project/issues/58514 Bug #1022577 [src:llvm-toolchain-15] llvm-toolchain-15 fails with LLVM ERROR when using mesa Set Bug forwarded-to-address to

Bug#1006022: marked as done (puma: flaky tests)

Your message dated Wed, 02 Nov 2022 12:50:08 + with message-id and subject line Bug#1006022: fixed in puma 5.6.5-2 has caused the Debian Bug report #1006022, regarding puma: flaky tests to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#1021317: salt-master: Fails to start with "zmq.error.ZMQError: Invalid argument"

It can be linked to https://github.com/saltstack/salt/issues/62092. I have the same issue, and python3-zmq on my system is 24.0.1-1.

Bug#1019991: marked as done (ovn: ovn-controller incremental processing FAILED)

Your message dated Wed, 02 Nov 2022 12:37:49 + with message-id and subject line Bug#1019991: fixed in ovn 22.03.1-6 has caused the Debian Bug report #1019991, regarding ovn: ovn-controller incremental processing FAILED to be marked as done. This means that you claim that the problem has been

Processed: Bug#1006022 marked as pending in puma

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

Bug#1006022: marked as pending in puma

Control: tag -1 pending Hello, Bug #1006022 in puma 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#1023325: cron-daemon-common: insufficient Breaks+Replaces against cronie

Package: cron-daemon-common Version: 3.0pl1-150 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package has file conflicts with cronie/experimental. There are Breaks+Replaces: cronie (<< 1.6.1-4), but cronie had a new upload

Bug#1023324: gm2-12-doc: missing Breaks+Replaces: gm2-12 (<< 12.2.0-8)

Package: gm2-12-doc Version: 12.2.0-8 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries

Bug#1023323: cockroachdb-datadriven: missing Breaks+Replaces: golang-github-cockroachdb-datadriven-dev (<< 1.0.2-2)

Package: cockroachdb-datadriven Version: 1.0.2-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to

Processed: severity of 1022674 is serious, severity of 1022630 is serious

Processing commands for cont...@bugs.debian.org: > severity 1022674 serious Bug #1022674 [three.js] three.js: Unable to build with rollup 3 Severity set to 'serious' from 'important' > severity 1022630 serious Bug #1022630 [node-mermaid] node-mermaid: Unable to build with rollup 3 Severity set to

Processed: closing 1022490

Processing commands for cont...@bugs.debian.org: > close 1022490 2.17-1 Bug #1022490 [src:postgresql-hll] postgresql-hll: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'. Marked as fixed in versions postgresql-hll/2.17-1. Bug #1022490

Bug#1022490: closing 1022490

close 1022490 2.17-1 thanks

Bug#1020056:

Hello, Le jeudi 13 octobre 2022, Thomas Braun a écrit : > so I think it should be as easy as adding cppzmq-dev to the build > dependencies. > > $diff -Nur control control.new > --- control 2022-10-13 16:19:07.384578078 +0200 > +++ control.new 2022-10-13 16:19:03.972578004 +0200 > @@ -7,6

Bug#1020073: marked as done (pyfai: FTBFS: distutils.errors.DistutilsError: Command '['/usr/bin/python3.10', '-m', 'pip', '--disable-pip-version-check', 'wheel', '--no-deps', '-w', '/tmp/tmpymrbi1ta',

Your message dated Wed, 02 Nov 2022 11:04:52 + with message-id and subject line Bug#1020073: fixed in pyfai 0.21.3+dfsg1-2 has caused the Debian Bug report #1020073, regarding pyfai: FTBFS: distutils.errors.DistutilsError: Command '['/usr/bin/python3.10', '-m', 'pip',

Bug#1023025: linux-image-6.0.0-2-686: kernel BUG at mm/memory.c:2660!

Package: src:linux Version: 6.0.5-1 Followup-For: Bug #1023025 X-Debbugs-Cc: l...@duck.com Dear Maintainer, Computer boot to a black screen and looks unresponsive from the keyboard and mouse after the update. In recover mode it boots to a black screen with the mouse pointer only, but

Bug#1021846: grub-install is broken since 2.06-3: error: unknown filesystem

Hi! On Thu, Oct 20, 2022 at 06:20:26PM +0100, Steve McIntyre wrote: >On Thu, Oct 20, 2022 at 08:09:15PM +0300, программист некто wrote: >># fsck.f2fs -f /dev/sda1 >>didn't report any errors. > >OK, that's good to know. > >>I can continue testing - rebuild without patches in turn, to reveal patch

Bug#1011532: marked as done (icedtea-web: FTBFS with OpenJDK 17 due to pack200 removal)

Your message dated Wed, 02 Nov 2022 10:19:15 + with message-id and subject line Bug#1011532: fixed in icedtea-web 1.8.8-2 has caused the Debian Bug report #1011532, regarding icedtea-web: FTBFS with OpenJDK 17 due to pack200 removal to be marked as done. This means that you claim that the

Bug#1011532: marked as pending in icedtea-web

Control: tag -1 pending Hello, Bug #1011532 in icedtea-web 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#1011532 marked as pending in icedtea-web

Processing control commands: > tag -1 pending Bug #1011532 [src:icedtea-web] icedtea-web: FTBFS with OpenJDK 17 due to pack200 removal Added tag(s) pending. -- 1011532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011532 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1023318: screen: re-adds /usr/bin/screen to /etc/shells on upgrade

Source: screen Version: 4.9.0-2 Tags: patch Severity: serious Justification: Debian policy 10.7.3 When upgrading or reinstalling screen, it adds /usr/bin/screen to /etc/shells even if one locally removed it there. Such behaviour violates Debian policy section 10.7.3. I propose managing the entry

Bug#1023317: zsh: re-adds /bin/zsh to /etc/shells on upgrade

Package: zsh,zsh-static Version: 5.9-1 Tags: patch Severity: serious Justification: Debian policy 10.7.3 When upgrading or reinstalling zsh or zsh-static, it adds /bin/zsh or /bin/zsh-static respectively to /etc/shells even if one locally removed it there. Such behaviour violates Debian policy

Bug#1023316: 9base: re-adds /bin/rc to /etc/shells on upgrade

Source: 9base Version: 1:6-12 Tags: patch Severity: serious Justification: Debian policy 10.7.3 If I remove /bin/rc from /etc/shells and then upgrade or reinstall 9base, it will re-add itself to /etc/shells. Such behaviour violates Debian policy section 10.7.3. I propose moving to dpkg triggers

Bug#1013259: samba-libs: Possible policy violation (now with unnecessary soname bump libndr.so.2 => libndr.so.3)

On Tuesday, 1 November 2022 11:21:55 CET Michael Tokarev wrote: > 01.11.2022 13:14, Ralph Boehme wrote: > > On 11/1/22 09:15, Michael Tokarev via samba-technical wrote: > >> Control: tag -1 + upstream > >> > >> Original context was at http://bugs.debian.org/1013259 , but whole > >> thing *now*

Bug#1013259: samba-libs: Possible policy violation (now with unnecessary soname bump libndr.so.2 => libndr.so.3)

On Tuesday, 1 November 2022 11:21:55 CET Michael Tokarev via samba-technical wrote: > 01.11.2022 13:14, Ralph Boehme wrote: > > On 11/1/22 09:15, Michael Tokarev via samba-technical wrote: > >> Control: tag -1 + upstream > >> > >> Original context was at http://bugs.debian.org/1013259 , but

Bug#995792: printing text files

Le dimanche, 30 octobre 2022, 00.43:02 h CET Thorsten Alteholz a écrit : > The problem seems to be that it was installed on a system without need > for it. Wouldn't there be a better package than printer-driver-all-enforce > to add a Recommends: for it? Maybe OdyX can shed some light on it? The

Bug#1022411: marked as done (apksigcopier: FTBFS: Unable to create file /sbuild-nonexistent/.cache/pylint/apksigcopier_1.stats: [Errno 2] No such file or directory: '/sbuild-nonexistent/.cache/pylint/

Your message dated Wed, 02 Nov 2022 06:34:08 + with message-id and subject line Bug#1022411: fixed in apksigcopier 1.1.0-1 has caused the Debian Bug report #1022411, regarding apksigcopier: FTBFS: Unable to create file /sbuild-nonexistent/.cache/pylint/apksigcopier_1.stats: [Errno 2] No such

  1   2   >