Bug#1032889: marked as done (itinerary doesn't start at all)

2023-03-23 Thread Debian Bug Tracking System
Your message dated Fri, 24 Mar 2023 00:04:09 + with message-id and subject line Bug#1032889: fixed in itinerary 22.12.3-1 has caused the Debian Bug report #1032889, regarding itinerary doesn't start at all to be marked as done. This means that you claim that the problem has been dealt with.

Processed (with 5 errors): re: Don't include in Bookworm

2023-03-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 103 normal Bug #103 [src:rust-encoding] Don't include in Bookworm Severity set to 'normal' from 'serious' > retitle 103 rust-encoding is unmaintained upstream Bug #103 [src:rust-encoding] Don't include in Bookworm Changed

Bug#1033333: Don't include in Bookworm

2023-03-23 Thread Peter Green
severity 103 normal retitle 103 rust-encoding is unmaintained upstream severity 104 normal retitle 104 rust-boxfnonce is unmaintained upstream severity 105 normal retitle 105 rust-const-cstr is unmaintained upstream (summarising several bugs) there is

Bug#1033369: ruby-riddle: autopkgtest timeouts on 32 bit archs

2023-03-23 Thread Paul Gevers
Source: ruby-riddle Version: 2.4.2-3 Severity: serious User: debian...@lists.debian.org Usertags: timeout Dear maintainer(s), Your package has an autopkgtest, great. However, it fails on 32 bit architectures. What's worse, it fails because it seems to hang and eventually times out due to

Bug#1032989: Liferea 1.14.1-1 segfaults on startup when trying to read gsettings

2023-03-23 Thread Grzegorz Szymaszek
On Thu, Mar 23, 2023 at 07:34:49PM +0100, Paul Gevers wrote: > On 23-03-2023 18:28, Grzegorz Szymaszek wrote: > > Would it be possible for you to run another build? > http://debomatic-amd64.debian.net/distribution#testing/liferea/1.14.1-2/buildlog Thanks! Well, this one does not crash.

Bug#1032989: Liferea 1.14.1-1 segfaults on startup when trying to read gsettings

2023-03-23 Thread Paul Gevers
Hi On 23-03-2023 18:28, Grzegorz Szymaszek wrote: Would it be possible for you to run another build? http://debomatic-amd64.debian.net/distribution#testing/liferea/1.14.1-2/buildlog Paul OpenPGP_signature Description: OpenPGP digital signature

Processed: Re: Bug#1033155: migration test fails when EC key present in test keyrings

2023-03-23 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1033155 [src:gnupg2] migration test fails when EC key present in test keyrings Severity set to 'serious' from 'important' -- 1033155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033155 Debian Bug Tracking System Contact

Bug#1029342: jexec: can't locate java: No such file or directory

2023-03-23 Thread Patrice Duroux
Hi again, This d/patches file was there until openjdk-16 but it's not there anymore in openjdk-17: https://salsa.debian.org/openjdk-team/openjdk/-/blob/openjdk-16/debian/patches/jexec.diff Could this be the reason for this problem? What is its intentional abandonment? Sorry for the noise

Bug#1032989: Liferea 1.14.1-1 segfaults on startup when trying to read gsettings

2023-03-23 Thread Grzegorz Szymaszek
Hi, On Thu, Mar 23, 2023 at 12:41:52PM +0100, Paul Gevers wrote: > I've went ahead and the build is running now here: > http://debomatic-amd64.debian.net/distribution#unstable/liferea/1.14.1-2/buildlog > > Once done, you can pull the liferea-data and liferea deb's from that page > and install

Processed: Re: [Pkg-freeipa-devel] Bug#1031816: tomcatjss: Migrate to Tomcat 10

2023-03-23 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1031816 [src:tomcatjss] tomcatjss: Migrate to Tomcat 10 Severity set to 'serious' from 'important' -- 1031816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1033366: resteasy3.0: should migrate to tomcat10

2023-03-23 Thread Markus Koschany
Source: resteasy3.0 Version: 3.0.26-5 Severity: serious Tags: help X-Debbugs-Cc: a...@debian.org Hello, currently resteasy3.0 depends on libtomcat9-java but should rather depend on libtomcat10-java. The reasoning for this is the fact that we can only support one tomcat package per release for

Processed: Re: i2p: Migrate to Tomcat 10

2023-03-23 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1031817 [src:i2p] i2p: Migrate to Tomcat 10 Severity set to 'serious' from 'important' -- 1031817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1032476: marked as done (apache2: CVE-2023-25690 CVE-2023-27522)

2023-03-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Mar 2023 16:02:08 + with message-id and subject line Bug#1032476: fixed in apache2 2.4.56-1~deb11u1 has caused the Debian Bug report #1032476, regarding apache2: CVE-2023-25690 CVE-2023-27522 to be marked as done. This means that you claim that the problem has been

Processed: Re: Bug#1031943: [pkg-netfilter-team] Bug#1031943: Should we do something?

2023-03-23 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1031943 [ebtables] ebtables: symlink removal removal code in the postinst does not seem to be working Severity set to 'important' from 'serious' -- 1031943: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031943 Debian Bug Tracking

Bug#1031943: [pkg-netfilter-team] Bug#1031943: Should we do something?

2023-03-23 Thread Arturo Borrero Gonzalez
control: severity -1 important On 3/23/23 16:18, Jeremy Sowden wrote: On 2023-03-23, at 15:58:45 +0100, Alberto Molina Coballes wrote: I agree with Arturo, the proposed change should be harmless, but we were not able to reproduce the issue in any of the test performed so I was thinking to

Bug#1031943: [pkg-netfilter-team] Bug#1031943: Should we do something?

2023-03-23 Thread Jeremy Sowden
On 2023-03-23, at 15:58:45 +0100, Alberto Molina Coballes wrote: > I agree with Arturo, the proposed change should be harmless, but we > were not able to reproduce the issue in any of the test performed so I > was thinking to lower the severity and apply the patch but don't ask > to be included in

Bug#1031943: [pkg-netfilter-team] Bug#1031943: Should we do something?

2023-03-23 Thread Alberto Molina Coballes
I agree with Arturo, the proposed change should be harmless, but we were not able to reproduce the issue in any of the test performed so I was thinking to lower the severity and apply the patch but don't ask to be included in bookworm.

Bug#1026639: fixed in rhino 1.7.14-1

2023-03-23 Thread Markus Koschany
Hi, Am Donnerstag, dem 23.03.2023 um 15:08 +0100 schrieb Paul Gevers: > Hi, > > On Mon, 13 Feb 2023 14:42:17 + Debian FTP Masters > wrote: > >    * New upstream version 1.7.14. > > - Fix FTBFS with OpenJDK 17. (Closes: #1026639) > > Is it possible to get a targeted fix? This new

Bug#1026639: fixed in rhino 1.7.14-1

2023-03-23 Thread Paul Gevers
Hi, On Mon, 13 Feb 2023 14:42:17 + Debian FTP Masters wrote: * New upstream version 1.7.14. - Fix FTBFS with OpenJDK 17. (Closes: #1026639) Is it possible to get a targeted fix? This new upstream is not reviewable and I seriously doubt it meets the freeze policy [1] 1325

Processed: closing 1031960

2023-03-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1031960 1.03-5~exp Bug #1031960 {Done: Adrian Bunk } [src:cpufetch] cpufetch FTBFS on ppc64/ppc64el Marked as fixed in versions cpufetch/1.03-5~exp. Bug #1031960 {Done: Adrian Bunk } [src:cpufetch] cpufetch FTBFS on ppc64/ppc64el Bug

Processed: closing 1031960

2023-03-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1031960 1.03-4 Bug #1031960 [src:cpufetch] cpufetch FTBFS on ppc64/ppc64el Marked as fixed in versions cpufetch/1.03-4. Bug #1031960 [src:cpufetch] cpufetch FTBFS on ppc64/ppc64el Marked Bug as done > thanks Stopping processing here.

Bug#1033335: Don't include in Bookworm

2023-03-23 Thread Alexander Kjäll
Hi The list-rdeps.sh script in https://salsa.debian.org/rust-team/debcargo-conf/ shows that it's in use: $ ./dev/list-rdeps.sh const-cstr Versions of rust-const-cstr in unstable: librust-const-cstr-dev 0.3.0-1+b1 Versions of rdeps of rust-const-cstr in unstable, that

Processed: Re: Update on packaging corepack

2023-03-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 980316 bookworm-ignore Bug #980316 [yarnpkg] Update yarnpkg to 2.x versions using corepack repo Added tag(s) bookworm-ignore. > tags 958686 bookworm-ignore Bug #958686 [node-yarnpkg] node-yarnpkg: Remove dependency to node-request Added

Processed: Re: Bug#1022760: openrefine: localhost:3333 returns HTTP ERROR 404 Not Found

2023-03-23 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1022760 {Done: Markus Koschany } [openrefine] openrefine: localhost: returns HTTP ERROR 404 Not Found Bug reopened Ignoring request to alter fixed versions of bug #1022760 to the same values previously set > severity -1 serious Bug #1022760

Bug#1032989: Liferea 1.14.1-1 segfaults on startup when trying to read gsettings

2023-03-23 Thread Paul Gevers
Hi, On 23-03-2023 12:21, Paul Gevers wrote: Hi Grzegorz, On 21-03-2023 17:48, Grzegorz Szymaszek wrote: [3]: https://github.com/lwindolf/liferea/issues/1214 This issue identified the broken commit and it was confirmed that revering the commit unbroke liferea for the bug submitter. Are you

Bug#1032989: Liferea 1.14.1-1 segfaults on startup when trying to read gsettings

2023-03-23 Thread Paul Gevers
Hi Grzegorz, On 21-03-2023 17:48, Grzegorz Szymaszek wrote: [3]: https://github.com/lwindolf/liferea/issues/1214 This issue identified the broken commit and it was confirmed that revering the commit unbroke liferea for the bug submitter. Are you in the position to build and test with that

Processed: tagging 1010347

2023-03-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1010347 + pending Bug #1010347 [src:cloudcompare] cloudcompare: CVE-2021-21897 - heap-based buffer overflow loading a DXF file via embedded dxflib Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need

Bug#1032510: packagekit: pkcon what-provides application/x-keepass2 makes PK crash

2023-03-23 Thread Bernhard Übelacker
On Wed, 08 Mar 2023 10:47:25 +0100 Laurent Bigonville wrote: $ pkcon what-provides application/x-keepass2 Getting provides[=] Loading cache [=] Querying

Bug#1031943: Should we do something?

2023-03-23 Thread Arturo Borrero Gonzalez
On Thu, 23 Mar 2023 09:46:05 +0100 Thomas Goirand wrote: Hi, It's been a month since the last entry in this bug, with nobody able to reproduce the bug, and no answer from original submitter. Shall we: - close the bug? - lower severity? - apply the patch? Introducing the proposed change

Bug#985377: marked as done (CVE-2020-13327)

2023-03-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Mar 2023 08:55:25 + with message-id and subject line Bug#985377: fixed in gitlab-ci-multi-runner 14.10.1-1 has caused the Debian Bug report #985377, regarding CVE-2020-13327 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1023116: marked as done (gitlab-ci-multi-runner build-depends on non-existing golang-github-gorilla-context-dev)

2023-03-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Mar 2023 08:55:25 + with message-id and subject line Bug#1023116: fixed in gitlab-ci-multi-runner 14.10.1-1 has caused the Debian Bug report #1023116, regarding gitlab-ci-multi-runner build-depends on non-existing golang-github-gorilla-context-dev to be marked as

Bug#1010452: marked as done (gitlab-ci-multi-runner: FTBFS: test failure)

2023-03-23 Thread Debian Bug Tracking System
Your message dated Thu, 23 Mar 2023 08:55:25 + with message-id and subject line Bug#1010452: fixed in gitlab-ci-multi-runner 14.10.1-1 has caused the Debian Bug report #1010452, regarding gitlab-ci-multi-runner: FTBFS: test failure to be marked as done. This means that you claim that the

Bug#1031943: Should we do something?

2023-03-23 Thread Thomas Goirand
Hi, It's been a month since the last entry in this bug, with nobody able to reproduce the bug, and no answer from original submitter. Shall we: - close the bug? - lower severity? - apply the patch? Cheers, Thomas Goirand (zigo)