Bug#1015014: marked as done (libgrokj2k: FTBFS on many architectures)

2022-09-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Sep 2022 22:21:11 + with message-id and subject line Bug#1015014: fixed in libgrokj2k 10.0.2-1 has caused the Debian Bug report #1015014, regarding libgrokj2k: FTBFS on many architectures to be marked as done. This means that you claim that the problem has been

Bug#1019953: flamerobin: FTBFS on arm, i386, mips

2022-09-16 Thread Scott Talbert
Source: flamerobin Version: 0.9.3.12-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) flamerobin 0.9.3.12-1 FTBFS on serveral arches (arm*, i386, mips*). Relevant log snippets: cd /<>/obj-aarch64-linux-gnu && /usr/bin/cmake -E

Bug#937234: trying to remove python2.7 from bookworm

2022-09-16 Thread Paul Gevers
Hi Mike, On Mon, 15 Aug 2022 13:54:27 + Mike Gabriel wrote: in another project context I have a freelancer working on pam-python Py3 transition. Will pick up the threads this week (I returned freshly from VAC yesterday). One month went by, is there any progress to report? Paul

Bug#1014628: src:git-annex: fails to migrate to testing for too long: FTBFS on armel and armhf

2022-09-16 Thread Sean Whitton
Hello, Some time ago Joey suggested uploading something like the attached to try to debug the build failures of 8.20211123 on the 32-bit ARM archs. However, it has not been possible to do this for some months because the Haskell transition is stalled on those architectures. I'm sending this mail

Processed: edb-debugger: diff for NMU version 1.3.0-1.1

2022-09-16 Thread Debian Bug Tracking System
Processing control commands: > tags 1012918 + pending Bug #1012918 [src:edb-debugger] edb-debugger: ftbfs with GCC-12 Added tag(s) pending. -- 1012918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012918 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1012918: edb-debugger: diff for NMU version 1.3.0-1.1

2022-09-16 Thread Adrian Bunk
Control: tags 1012918 + pending Dear maintainer, I've prepared an NMU for edb-debugger (versioned as 1.3.0-1.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru edb-debugger-1.3.0/debian/changelog edb-debugger-1.3.0/debian/changelog ---

Bug#1019724: warning: stray \ before - causes autopkgtest failure

2022-09-16 Thread Paul Gevers
Hi Santiago, On 15-09-2022 09:26, Paul Gevers wrote: I am trying to schedule autopkgtests in unstable on amd64 for all source packages that have one. All results are now in. Only several test failed due this warning: the known dpkg and cjet and the newly found nagios-plugins-contrib,

Processed: block 1000922 with 1019949

2022-09-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1000922 with 1019949 Bug #1000922 [src:llvmlite] llvmlite: Please upgrade to llvm-toolchain-14 1000922 was not blocked by any bugs. 1000922 was blocking: 1000941 1017679 Added blocking bug(s) of 1000922: 1019949 > thanks Stopping processing

Bug#1019949: numba seems to need autopkgtest dependency on python-is-python3

2022-09-16 Thread Adrian Bunk
Source: numba Version: 0.56.2+dfsg-1 Severity: serious https://ci.debian.net/data/autopkgtest/unstable/amd64/n/numba/25838468/log.gz ... == FAIL: test_nonsense_gdb_binary (numba.tests.test_cli.TestGDBCLIInfoBrokenGdbs)

Bug#1019945: python3-numba must depend on python3-llvmlite (>= 0.39)

2022-09-16 Thread Adrian Bunk
Package: python3-numba Version: 0.56.2+dfsg-1 Severity: serious Control: block 1018786 by -1 https://ci.debian.net/data/autopkgtest/testing/amd64/n/numba/26144527/log.gz ... autopkgtest [20:15:06]: test python3-numba: [--- [*] Testing with python3.10: Traceback (most recent

Processed: python3-numba must depend on python3-llvmlite (>= 0.39)

2022-09-16 Thread Debian Bug Tracking System
Processing control commands: > block 1018786 by -1 Bug #1018786 {Done: Diane Trout } [src:numba] numba: autopkgtest needs update for new version of llvmlite: The module `llvmlite.llvmpy` is deprecated 1018786 was not blocked by any bugs. 1018786 was not blocking any bugs. Added blocking bug(s)

Processed: block 1016633 with 1016625

2022-09-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1016633 with 1016625 Bug #1016633 [src:pyhst2] pyhst2: FTBFS: redefinition of 'constexpr const _Tp std::integral_constant<_Tp, __v>::value' 1016633 was not blocked by any bugs. 1016633 was not blocking any bugs. Added blocking bug(s) of

Bug#1016299: mkautodoc: diff for NMU version 0.1.0-3.1

2022-09-16 Thread Adrian Bunk
Control: tags 1016299 + patch Control: tags 1016299 + pending Dear maintainer, I've prepared an NMU for mkautodoc (versioned as 0.1.0-3.1) and uploaded it to DELAYED/14. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru mkautodoc-0.1.0/debian/changelog

Processed: mkautodoc: diff for NMU version 0.1.0-3.1

2022-09-16 Thread Debian Bug Tracking System
Processing control commands: > tags 1016299 + patch Bug #1016299 [src:mkautodoc] mkautodoc: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 returned exit code 13 Added tag(s) patch. > tags 1016299 + pending Bug #1016299 [src:mkautodoc] mkautodoc: FTBFS:

Bug#1016599: mayavi2: vtk[6,7] removal

2022-09-16 Thread Adrian Bunk
On Wed, Aug 03, 2022 at 10:39:53PM +0200, Sebastian Ramacher wrote: > Source: mayavi2 > Version: 4.8.0-1 > Severity: serious > X-Debbugs-Cc: sramac...@debian.org > Tags: sid bookworm > Control: block 1016597 by -1 > User: gl...@debian.org > Usertags: vtk6_vtk7_removal > > Based on #1013156 and

Bug#1019937: elfutils: Missing licenses in d/copyright

2022-09-16 Thread Bastian Germann
Source: elfutils Severity: serious Version: 0.187-2 elfutils' debian/copyright file is missing at least the BSD-2-clause license and the GFDL-NIV-1.3 license. Please find a machine-readable copyright file attached that includes them.Format:

Processed: r-cran-tmb must depend on the exact upstream version of r-cran-matrix it was built with or drop the warning

2022-09-16 Thread Debian Bug Tracking System
Processing control commands: > affects -1 r-cran-glmmtmb src:r-cran-glmmtmb Bug #1019936 [r-cran-tmb] r-cran-tmb must depend on the exact upstream version of r-cran-matrix it was built with or drop the warning Added indication that 1019936 affects r-cran-glmmtmb and src:r-cran-glmmtmb > block

Bug#1019936: r-cran-tmb must depend on the exact upstream version of r-cran-matrix it was built with or drop the warning

2022-09-16 Thread Adrian Bunk
Package: r-cran-tmb Version: 1.9.1-1 Severity: serious Control: affects -1 r-cran-glmmtmb src:r-cran-glmmtmb Control: block 1017626 by -1 > library(TMB) Warning message: In checkMatrixPackageVersion() : Package version inconsistency detected. TMB was built with Matrix version 1.4.1 Current Matrix

Bug#1019708: marked as done (astropy: autopkgtest regression: No warnings of type (,) were emitted)

2022-09-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Sep 2022 15:20:09 + with message-id and subject line Bug#1019708: fixed in astropy 5.1-4 has caused the Debian Bug report #1019708, regarding astropy: autopkgtest regression: No warnings of type (,) were emitted to be marked as done. This means that you claim that

Bug#1019916: marked as done (node-commist embeds a copy of node-leven)

2022-09-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Sep 2022 15:04:28 + with message-id and subject line Bug#1019916: fixed in node-commist 3.1.2+ds-1 has caused the Debian Bug report #1019916, regarding node-commist embeds a copy of node-leven to be marked as done. This means that you claim that the problem has

Processed: Bug#1019708 marked as pending in astropy

2022-09-16 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1019708 [src:astropy] astropy: autopkgtest regression: No warnings of type (,) were emitted Added tag(s) pending. -- 1019708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019708 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1019708: marked as pending in astropy

2022-09-16 Thread Ole Streicher
Control: tag -1 pending Hello, Bug #1019708 in astropy 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#1019930: newt: Several issues with copyright file

2022-09-16 Thread Bastian Germann
Source: newt Severity: serious Version: 0.52.21-5 newt's copyright file does not present the package's copyright in a fashion that is required by the Policy. The copyright holder is not included from README (Red Hat) but from COPYING, which is the GPL's copyright holder. The GPL-2+ license,

Processed: Remove ruby-coffee-script - deprecated upstream

2022-09-16 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 1019924 Bug #1019927 [ruby-coffee-script] Remove ruby-coffee-script - deprecated upstream 1019927 was not blocked by any bugs. 1019927 was not blocking any bugs. Added blocking bug(s) of 1019927: 1019924 -- 1019927:

Bug#1019923: utf8proc: build-depends on unicode-data (< 14.1) but Unstable has 15.0.0-1

2022-09-16 Thread Jeremy Bicha
Source: utf8proc Version: 2.7.0-3 Severity: serious Tags: ftbfs upstream bookworm sid This week, there is a new Unicode 15 release. In Debian, unicode-data has been updated to 15.0.0. utf8proc needs to be updated to building against the current unicode-data in Debian. This issue was detected by

Bug#1019268: marked as done (tumbler-plugins-extra: Update for libgepub 0.7)

2022-09-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Sep 2022 09:42:03 + with message-id and subject line Bug#1019268: fixed in tumbler 4.16.1-1 has caused the Debian Bug report #1019268, regarding tumbler-plugins-extra: Update for libgepub 0.7 to be marked as done. This means that you claim that the problem has been

Bug#1019916: node-commist embeds a copy of node-leven

2022-09-16 Thread Yadd
Source: node-commist Version: 3.1.2-1 Severity: serious Tags: upstream Justification: Code duplication Version 3.1.2 adds a leven.js file. This file is: * undeclared in debian/copyright (not same author) * a copy of node-leven file Please drop it from import and replace it by

Bug#1019914: Useless in Debian

2022-09-16 Thread Katharina Drexel
Package: adldap2 Severity: serious [ Reported by a team member to see the package removed from testing ] adldap2 will be deprecated in favor of LdapRecord (https://github.com/DirectoryTree/LdapRecord), and I don't see a use case any more at the moment. No packages depend on it, so it can be

Bug#1018134: [Debian-on-mobile-maintainers] Bug#1018134: Bug#1018134: chatty: bump severity to serious for ongoing evolution transitions

2022-09-16 Thread Evangelos Ribeiro Tzaras
Hi, On Tue, 2022-09-06 at 08:40 +0200, Guido Günther wrote: > Just so that everybody is on the same page: the next chatty > release switches to libcmatrix and we can then switch to libsoup3 > via > >   https://source.puri.sm/Librem5/libcmatrix/-/merge_requests/18   just a quick update: There

Processed: Re: Bug#1018758: fixed in python-xarray 2022.06.0-7

2022-09-16 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #1018758 {Done: Alastair McKinstry } [dpkg-cross] dpkg-cross leaves a dangling symlink for ld-linux.so for sparc64 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add

Bug#1018758: fixed in python-xarray 2022.06.0-7

2022-09-16 Thread Paul Gevers
Control: reopen -1 python-xarray (2022.06.0-7) unstable; urgency=medium . * Patch test_indexes-big-endian.patch from Graham Inggs. Closes: #1018758 Wrong bug. Paul OpenPGP_signature Description: OpenPGP digital signature

Bug#1019758: marked as done (python-xarray: new autopkgtest regression on s390x)

2022-09-16 Thread Debian Bug Tracking System
Your message dated Fri, 16 Sep 2022 07:58:06 +0200 with message-id and subject line closed wrong bug has caused the Debian Bug report #1019758, regarding python-xarray: new autopkgtest regression on s390x to be marked as done. This means that you claim that the problem has been dealt with. If