Bug#991060: reopen for bullseye

2022-12-04 Thread Stéphane Glondu
Hi, Le 04/12/2022 à 20:51, Santiago Vila a écrit : Please, let us fix this for stable. I would gladly backport the fix from unstable but since the fix was included in a new upstream release I'm in doubt about what would have to be done and would definitely need help. Did you try the

Processed: Re: simbody: FTBFS on ppc64el, mips64el

2022-12-04 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1024526 [src:simbody] simbody: FTBFS on ppc64el, mips64el Severity set to 'important' from 'serious' -- 1024526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024526 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1024526: simbody: FTBFS on ppc64el, mips64el

2022-12-04 Thread Andrius Merkys
Control: severity -1 important The upstream says this is a bug in optimization, but they do not have access to these architectures. For now I have RMed the binaries of ppc64el and mips64el, thus the package should be allowed to migrate to testing without them for the time being. Andrius

Bug#1012572: android-platform-frameworks-base: FTBFS with protobuf 3.20.1+

2022-12-04 Thread Mattia Rizzolo
Hello Roger, On Fri, Jun 10, 2022 at 09:48:06PM +0900, Roger Shimizu wrote: > I tried your patch by installing protobuf in experimental > and confirmed it builds well, and all tests are also OK. > Will upload after protobuf 3.20 (or later) hits unstable. > Thanks for your support! You uploaded

Bug#993065: marked as done (gnome-shell-extension-xrdesktop: Please update for gnome-shell 43)

2022-12-04 Thread Debian Bug Tracking System
Your message dated Mon, 05 Dec 2022 04:42:25 + with message-id and subject line Bug#1018208: Removed package(s) from unstable has caused the Debian Bug report #993065, regarding gnome-shell-extension-xrdesktop: Please update for gnome-shell 43 to be marked as done. This means that you claim

Bug#1019098: marked as done (src:tbb: do not migrate. this source is deprecated in favor of src:onetbb)

2022-12-04 Thread Debian Bug Tracking System
Your message dated Mon, 05 Dec 2022 04:40:55 + with message-id and subject line Bug#1014990: Removed package(s) from unstable has caused the Debian Bug report #1019098, regarding src:tbb: do not migrate. this source is deprecated in favor of src:onetbb to be marked as done. This means that

Bug#1024515: Acknowledgement (mariadb-10.6: FTBFS on s390x: test main.order_by_innodb failed with type 'ref')

2022-12-04 Thread Otto Kekäläinen
I did a re-run today and surprisingly it passed: main.order_by_innodb 'innodb'w2 [ pass ] 84 https://buildd.debian.org/status/fetch.php?pkg=mariadb-10.6=s390x=1%3A10.6.11-1=1670206361=0 Maybe the issue is sporadic? But also the first day I saw this I re-ran the build and it did

Bug#1020087: marked as done (guile-ssh: FTBFS: dh_auto_test: error: cd debian/build/guile-3.0 && make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2)

2022-12-04 Thread Debian Bug Tracking System
Your message dated Mon, 05 Dec 2022 03:04:05 + with message-id and subject line Bug#1020087: fixed in guile-ssh 0.16.0-1 has caused the Debian Bug report #1020087, regarding guile-ssh: FTBFS: dh_auto_test: error: cd debian/build/guile-3.0 && make -j1 check "TESTSUITEFLAGS=-j1 --verbose"

Processed: bug 1023804 is forwarded to https://github.com/mnauw/git-remote-hg/issues/53

2022-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1023804 https://github.com/mnauw/git-remote-hg/issues/53 Bug #1023804 [src:git-remote-hg] git-remote-hg: autopkgtest needs update for new version of git: transport 'file' not allowed Set Bug forwarded-to-address to

Processed: tagging 1023801 ...

2022-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1023801 + fixed-upstream patch Bug #1023801 [src:check-manifest] check-manifest: autopkgtest needs update for new version of git: transport 'file' not allowed Added tag(s) patch and fixed-upstream. > forwarded 1023801 >

Bug#1019635: marked as done (ruby-mail: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "Can not decode an entire message, try calling #decoded on the various fiel

2022-12-04 Thread Debian Bug Tracking System
Your message dated Mon, 05 Dec 2022 01:06:18 + with message-id and subject line Bug#1019635: fixed in ruby-mail 2.7.1+dfsg1-2 has caused the Debian Bug report #1019635, regarding ruby-mail: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: expected NoMethodError with "Can not decode

Processed: libssh-dev: DSA support is disabled by default

2022-12-04 Thread Debian Bug Tracking System
Processing control commands: > block 1020087 by -1 Bug #1020087 [src:guile-ssh] guile-ssh: FTBFS: dh_auto_test: error: cd debian/build/guile-3.0 && make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2 1020087 was not blocked by any bugs. 1020087 was not blocking any

Bug#1025027: marked as done (python-cffi: (autopkgtest) needs update for python3.11: Aborted)

2022-12-04 Thread Debian Bug Tracking System
Your message dated Mon, 05 Dec 2022 00:21:15 + with message-id and subject line Bug#1025027: fixed in python-cffi 1.15.1-4 has caused the Debian Bug report #1025027, regarding python-cffi: (autopkgtest) needs update for python3.11: Aborted to be marked as done. This means that you claim that

Processed: Bug#1019635 marked as pending in ruby-mail

2022-12-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1019635 [src:ruby-mail] ruby-mail: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed:expected NoMethodError with "Can not decode an entire message, try calling #decoded on the various fields and body or parts if it is a multipart

Bug#1019635: marked as pending in ruby-mail

2022-12-04 Thread Antonio Terceiro
Control: tag -1 pending Hello, Bug #1019635 in ruby-mail 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#1016332: librsb: FTBFS: gmake[3]: *** [Makefile:920: qtests] Error 1

2022-12-04 Thread Michele Martone
suggestion 2: sed 's/..LATEX./false/g' -i rsbtest/Makefile.am I suggest to use 1, and if you confirm it works, I'd also use it upstream. Is it effective? Ciao, Michele On 20221204@22:45, Rafael Laboissière wrote: > Control: forwarded -1 michelemart...@users.sourceforge.net > Control: t

Processed: Bug#1025027 marked as pending in python-cffi

2022-12-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1025027 [src:python-cffi] python-cffi: (autopkgtest) needs update for python3.11: Aborted Added tag(s) pending. -- 1025027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025027 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1025027: marked as pending in python-cffi

2022-12-04 Thread Stefano Rivera
Control: tag -1 pending Hello, Bug #1025027 in python-cffi 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#1025454: afl: Downloads software during build

2022-12-04 Thread Kurt Roeckx
Source: aflplusplus Version: 4.04c-1 Severity: serious Hi, On the buildds, we get: # -/usr/bin/make -C utils/plot_ui /usr/bin/make -C frida_mode make[3]: Entering directory '/<>/frida_mode' mkdir -p /<>/frida_mode/build/ mkdir -p /<>/frida_mode/build/frida/ wget -qO

Bug#1025313: marked as done (nip2: FTBFS with fftw3 (3.3.10-1))

2022-12-04 Thread Debian Bug Tracking System
Your message dated Sun, 04 Dec 2022 22:39:17 + with message-id and subject line Bug#1025313: fixed in nip2 8.7.1-4 has caused the Debian Bug report #1025313, regarding nip2: FTBFS with fftw3 (3.3.10-1) to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: your mail

2022-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 528062 upstream Bug #528062 [apache2] apache2: mod_userdir is broken with respect to suexec support. patch included Added tag(s) upstream. > tags 967010 buster Bug #967010 [apache2] apache2: last debian 10.4 , last apache avail from repo

Processed: nghttp2: missing build-dependency on tzdata

2022-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 981600 nghttp2: missing build-depends on tzdata Bug #981600 [src:nghttp2] nghttp2: util_localtime_date test fails in arch-only build Changed Bug title to 'nghttp2: missing build-depends on tzdata' from 'nghttp2: util_localtime_date test

Processed: Re: Bug#1016332: librsb: FTBFS: gmake[3]: *** [Makefile:920: qtests] Error 1

2022-12-04 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 michelemart...@users.sourceforge.net Bug #1016332 [src:librsb] librsb: FTBFS: gmake[3]: *** [Makefile:920: qtests] Error 1 Set Bug forwarded-to-address to 'michelemart...@users.sourceforge.net'. > tags -1 unreproducible Bug #1016332 [src:librsb]

Bug#1016332: librsb: FTBFS: gmake[3]: *** [Makefile:920: qtests] Error 1

2022-12-04 Thread Rafael Laboissière
Control: forwarded -1 michelemart...@users.sourceforge.net Control: tags -1 unreproducible Hi Michele, There is a bug report filed against the librsb package (Bug#1016332 [1]) that has severity level "serious". This is blocking the package entering testing and, therefore, librsb will be

Bug#1022526: marked as done (python-ssdeep: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command)

2022-12-04 Thread Debian Bug Tracking System
Your message dated Sun, 04 Dec 2022 21:22:01 + with message-id and subject line Bug#1022526: fixed in python-ssdeep 3.4.1-1 has caused the Debian Bug report #1022526, regarding python-ssdeep: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command to be marked as

Bug#1025317: marked as done (vips: FTBFS with fftw3 (3.3.10-1))

2022-12-04 Thread Debian Bug Tracking System
Your message dated Sun, 04 Dec 2022 20:46:34 + with message-id and subject line Bug#1025317: fixed in vips 8.13.3-2 has caused the Debian Bug report #1025317, regarding vips: FTBFS with fftw3 (3.3.10-1) to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: unarchive for bullseye

2022-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 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

Processed: unarchive for bullseye

2022-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 997580 Bug #997580 {Done: Markus Koschany } [src:libpicocontainer1-java] libpicocontainer1-java: FTBFS: dh_auto_test: error: /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven/boot/plexus-classworlds-2.x.jar

Processed: unarchive again for bullseye

2022-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 997222 Bug #997222 {Done: Håvard Flaget Aasen } [src:libexplain] libexplain: FTBFS: libexplain/iocontrol/siocadddlci.c:51:12: error: invalid application of ‘sizeof’ to incomplete type ‘struct dlci_add’ Unarchived Bug 997222 > End of

Processed: jruby,jruby-openssl: both ship /usr/share/jruby/lib/ruby/stdlib/*openssl*

2022-12-04 Thread Debian Bug Tracking System
Processing control commands: > found -1 9.3.9.0+ds-1 Bug #1025442 [jruby,jruby-openssl] jruby,jruby-openssl: both ship /usr/share/jruby/lib/ruby/stdlib/*openssl* There is no source info for the package 'jruby-openssl' at version '9.3.9.0+ds-1' with architecture '' Marked as found in versions

Bug#1025442: jruby,jruby-openssl: both ship /usr/share/jruby/lib/ruby/stdlib/*openssl*

2022-12-04 Thread Andreas Beckmann
Package: jruby,jruby-openssl Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: found -1 9.3.9.0+ds-1 Control: found -1 0.9.21-4 Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without

Processed: reopen for bullseye

2022-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 991060 Bug #991060 {Done: Stéphane Glondu } [src:mlpost] mlpost FTBFS with imagemagick with the #987504 change 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need

Bug#991060: reopen for bullseye

2022-12-04 Thread Santiago Vila
reopen 991060 found 991060 0.8.1-8 fixed 991060 0.9-1 thanks Hi. Please, let us fix this for stable. I would gladly backport the fix from unstable but since the fix was included in a new upstream release I'm in doubt about what would have to be done and would definitely need help. Thanks.

Bug#1024453: marked as done (mediathek: fails to start with openjdk 17)

2022-12-04 Thread Debian Bug Tracking System
Your message dated Sun, 4 Dec 2022 20:46:42 +0100 with message-id and subject line Re: Bug#1024453: mediathek: fails to start with openjdk 17 has caused the Debian Bug report #1024453, regarding mediathek: fails to start with openjdk 17 to be marked as done. This means that you claim that the

Bug#1024987: marked as done (sweethome3d: Fail to start)

2022-12-04 Thread Debian Bug Tracking System
Your message dated Sun, 4 Dec 2022 20:46:42 +0100 with message-id and subject line Re: Bug#1024453: mediathek: fails to start with openjdk 17 has caused the Debian Bug report #1024453, regarding sweethome3d: Fail to start to be marked as done. This means that you claim that the problem has been

Bug#1025440: FTBFS: fails to compile with Java errors

2022-12-04 Thread Hans Joachim Desserud
Source: starjava-ttools Version: 3.4.7-2 Severity: serious Tags: ftbfs Dear Maintainer, starjava-ttools fails to build from source, see https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/starjava-ttools.html for detailed log output. The main errors seem to be com.sun.*

Processed: jbigkit: diff for NMU version 2.1-6.1

2022-12-04 Thread Debian Bug Tracking System
Processing control commands: > tags 1023710 + patch Bug #1023710 [src:jbigkit] jbigkit: autopkgtest failure: unittests-Makefile: No such file or directory Added tag(s) patch. > tags 1023710 + pending Bug #1023710 [src:jbigkit] jbigkit: autopkgtest failure: unittests-Makefile: No such file or

Bug#1023710: jbigkit: diff for NMU version 2.1-6.1

2022-12-04 Thread Jochen Sprickerhof
Control: tags 1023710 + patch Control: tags 1023710 + pending Dear maintainer, I've prepared an NMU for jbigkit (versioned as 2.1-6.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. Regards. diff -Nru jbigkit-2.1/debian/changelog

Processed: Adding ibus-cangjie and keyman to the "Affects" list

2022-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1025312 + src:ibus-cangjie src:keyman Bug #1025312 [libgl1-mesa-dri] libgl1-mesa-dri: multiple packages FTBFS and have autopkgtest regressions running test programs under Xvfb Bug #1025324 [libgl1-mesa-dri] libc6: Xserver with nouveau

Bug#1025377: marked as done (texstudio: Switch to libqtermwidget5-1-dev)

2022-12-04 Thread Debian Bug Tracking System
Your message dated Sun, 04 Dec 2022 17:53:46 + with message-id and subject line Bug#1025377: fixed in texstudio 4.3.1+ds-2 has caused the Debian Bug report #1025377, regarding texstudio: Switch to libqtermwidget5-1-dev to be marked as done. This means that you claim that the problem has been

Processed: tagging 1002353, tagging 1023986

2022-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1002353 + pending Bug #1002353 [src:parso] parso: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.10 3.9" returned exit code 13 Added tag(s) pending. > tags 1023986 + pending Bug #1023986 [python3-parso]

Bug#1009482: marked as done (sphinxcontrib-autoprogram: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.10 returned exit code 13)

2022-12-04 Thread Debian Bug Tracking System
Your message dated Sun, 4 Dec 2022 19:38:23 +0200 with message-id and subject line Fixed in 0.1.7-3 has caused the Debian Bug report #1009482, regarding sphinxcontrib-autoprogram: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.10 returned exit code 13 to be marked as done.

Bug#1012382: pktanon: autopkgtest fails on s390x with: wrong pcap file version: should be 2.4

2022-12-04 Thread Sascha Steinbiss
forwarded 1012382 https://github.com/KIT-Telematics/pktanon/issues/8 tags 1012382 upstream thanks Hi, Your package has an autopkgtest, great. However, it fails on s390x. I have attached the relevant piece of the log [1]. I'd like to note that s390x is big-endian. Maybe the check for the

Bug#1019638: marked as done (ruby-memory-profiler: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.)

2022-12-04 Thread Debian Bug Tracking System
Your message dated Sun, 04 Dec 2022 17:20:43 + with message-id and subject line Bug#1019638: fixed in ruby-memory-profiler 0.9.14-4.1 has caused the Debian Bug report #1019638, regarding ruby-memory-profiler: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed. to be marked as done. This means

Bug#997145: marked as done (autoconf2.69: FTBFS: autoconf.texi:9: unknown command `setcontentsaftertitlepage')

2022-12-04 Thread Debian Bug Tracking System
Your message dated Sun, 04 Dec 2022 17:19:14 + with message-id and subject line Bug#997145: fixed in autoconf2.69 2.69-3.1 has caused the Debian Bug report #997145, regarding autoconf2.69: FTBFS: autoconf.texi:9: unknown command `setcontentsaftertitlepage' to be marked as done. This means

Processed: Re: Bug#1012382: pktanon: autopkgtest fails on s390x with: wrong pcap file version: should be 2.4

2022-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 1012382 https://github.com/KIT-Telematics/pktanon/issues/8 Bug #1012382 [src:pktanon] pktanon: autopkgtest fails on s390x with: wrong pcap file version: should be 2.4 Set Bug forwarded-to-address to

Processed: golang-github-go-chef-chef: diff for NMU version 0.0.1+git20161023.60.deb8c38-1.2

2022-12-04 Thread Debian Bug Tracking System
Processing control commands: > tags 848055 + pending Bug #848055 [src:golang-github-go-chef-chef] golang-github-go-chef-chef: FTBFS randomly (failing tests) Added tag(s) pending. -- 848055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848055 Debian Bug Tracking System Contact

Bug#848055: golang-github-go-chef-chef: diff for NMU version 0.0.1+git20161023.60.deb8c38-1.2

2022-12-04 Thread Adrian Bunk
Control: tags 848055 + pending Dear maintainer, I've prepared an NMU for golang-github-go-chef-chef (versioned as 0.0.1+git20161023.60.deb8c38-1.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru

Processed: tagging 1022343

2022-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1022343 + fixed Bug #1022343 {Done: Abou Al Montacir } [src:view3dscene] view3dscene: FTBFS: view3dscene.lpr(63,17) Fatal: Can't find unit CastleCubeMaps used by view3dscene Added tag(s) fixed. > thanks Stopping processing here. Please

Bug#932345: marked as done (profile-sync-daemon: Debian specific error "I require modinfo but it's not installed")

2022-12-04 Thread Debian Bug Tracking System
Your message dated Sun, 04 Dec 2022 16:20:23 + with message-id and subject line Bug#932345: fixed in profile-sync-daemon 6.34-1.2 has caused the Debian Bug report #932345, regarding profile-sync-daemon: Debian specific error "I require modinfo but it's not installed" to be marked as done.

Bug#1023330: marked as done (ghostscript 10.0.0~dfsg-6: x11 support missing, thus 'gv 1:3.7.4-2+b1' is failing)

2022-12-04 Thread Debian Bug Tracking System
Your message dated Sun, 04 Dec 2022 15:20:50 + with message-id and subject line Bug#1023330: fixed in ghostscript 10.0.0~dfsg-8 has caused the Debian Bug report #1023330, regarding ghostscript 10.0.0~dfsg-6: x11 support missing, thus 'gv 1:3.7.4-2+b1' is failing to be marked as done. This

Processed: reassign 1024318 to ghostscript, severity of 1023330 is grave, forcibly merging 1023330 1024318

2022-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1024318 ghostscript 10.0.0~dfsg-6 Bug #1024318 [gv] gv: x11 output driver not found Bug reassigned from package 'gv' to 'ghostscript'. No longer marked as found in versions gv/1:3.7.4-2. Ignoring request to alter fixed versions of bug

Processed: tagging 1024327, tagging 1024318

2022-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1024327 + sid bookworm Bug #1024327 [gv] gv hangs on any file Added tag(s) bookworm and sid. > tags 1024318 + sid bookworm Bug #1024318 [gv] gv: x11 output driver not found Added tag(s) sid and bookworm. > thanks Stopping processing here.

Bug#1025296: closing 1025296

2022-12-04 Thread Sebastian Ramacher
close 1025296 thanks clementine was part of the protobuf transition. A binNMU fixed this issue. Cheers

Processed: closing 1025296

2022-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1025296 Bug #1025296 [clementine] clementine: Core dump at startup, libprotobuf version mismatch Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1025296:

Processed: reassign 1024987 to java-wrappers, forcibly merging 1024453 1024987, affects 1024453

2022-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1024987 java-wrappers 0.3 Bug #1024987 [sweethome3d] sweethome3d: Fail to start Bug reassigned from package 'sweethome3d' to 'java-wrappers'. No longer marked as found in versions sweethome3d/7.0.2+dfsg-1. Ignoring request to alter fixed

Processed: tagging 1024453

2022-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1024453 - bullseye Bug #1024453 [java-wrappers] mediathek: fails to start with openjdk 17 Removed tag(s) bullseye. > thanks Stopping processing here. Please contact me if you need assistance. -- 1024453:

Processed: block 1011567 with 1012103

2022-12-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1011567 with 1012103 Bug #1011567 [android-framework-23] android-framework-23: FTBFS with OpenJDK 17 due to com.sun.javadoc removal 1011567 was not blocked by any bugs. 1011567 was not blocking any bugs. Added blocking bug(s) of 1011567:

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

2022-12-04 Thread Sebastiaan Couwenberg
On 12/2/22 16:39, Sebastiaan Couwenberg wrote: The test target still fails because it uses xvfb which is broken by the recent update of mesa (#1025312). A work around for the xvfb failure is to set LIBGL_ALWAYS_SOFTWARE=1 in the environment. The updated debdiff that also implemented this is

Bug#1025315: marked as done (pyxplot: FTBFS with fftw3 (3.3.10-1))

2022-12-04 Thread Debian Bug Tracking System
Your message dated Sun, 04 Dec 2022 12:04:58 + with message-id and subject line Bug#1025315: fixed in pyxplot 0.9.2-13 has caused the Debian Bug report #1025315, regarding pyxplot: FTBFS with fftw3 (3.3.10-1) to be marked as done. This means that you claim that the problem has been dealt

Bug#938322: fixed in qtwebengine-opensource-src 5.15.11+dfsg-1

2022-12-04 Thread Dmitry Shachnev
Hi Bastian! On Sun, Dec 04, 2022 at 12:15:04AM +0100, Bastian Germann wrote: > On Sun, 27 Nov 2022 10:00:56 + Debian FTP Masters > wrote: > >* Use Python 3 instead of Python 2 for building (closes: #938322). > > - Update build-dependency. > > - Add python3.patch, inspired by

Processed: Re: Bug#1023156: haskell-gi-gtk FTBFS on armel

2022-12-04 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #1023156 [src:haskell-gi-gtk] haskell-gi-gtk FTBFS on armel Severity set to 'important' from 'serious' -- 1023156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023156 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#1023156: haskell-gi-gtk FTBFS on armel

2022-12-04 Thread Ilias Tsitsimpis
Control: severity -1 important On Tue, Nov 01, 2022 at 10:17AM, Scott Talbert wrote: > On Sun, 30 Oct 2022, Adrian Bunk wrote: > > > haskell-gi-gtk has only once ever been built successfully on armel. > > Unless someone has a better suggestion, my short-term Plan B would be > > that I request

Bug#1025366: Note that the bug is also present in 7.0.2

2022-12-04 Thread Eric Valette
Already fixed there same ways but did not report the bug hoping it will be soon fixed. -- eric

Bug#1025406: tpm2-pytss: FTBFS in sid

2022-12-04 Thread Gianfranco Costamagna
Hello Sadly, also with that patch, the tests fails due to a missing json file in the system. Not sure if tpm2-tss should install it, or we should disable such tests. See e.g. https://launchpadlibrarian.net/637540124/buildlog_ubuntu-lunar-amd64.tpm2-pytss_1.2.0-2ubuntu1_BUILDING.txt.gz E

Bug#1025408: python-certbot-dns-standalone: FTBFS (Depending on old python3-acme-abi-1)

2022-12-04 Thread Gianfranco Costamagna
Source: python-certbot-dns-standalone Version: 1.0.3-2 Severity: serious Hello, your package FTBFS now that newer python3-acme abi is in sid. dpkg-source: warning: cannot verify inline signature for ./python-certbot-dns-standalone_1.0.3-2.dsc: no acceptable signature found dpkg-source: info:

Processed: Re: tpm2-pytss: FTBFS in sid

2022-12-04 Thread Debian Bug Tracking System
Processing control commands: > tags -1 patch Bug #1025406 [src:tpm2-pytss] tpm2-pytss: FTBFS in sid Added tag(s) patch. -- 1025406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025406 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1025406: tpm2-pytss: FTBFS in sid

2022-12-04 Thread Gianfranco Costamagna
control: tags -1 patch It turns out its not installing libpython3.11-dev because you depend on python3-dev instead of python3-all-dev. See e.g. https://launchpad.net/ubuntu/+source/tpm2-pytss/1.2.0-2ubuntu1 and the patch diff -Nru tpm2-pytss-1.2.0/debian/changelog

Bug#1024154: marked as done (llvm-toolchain-14: FTBFS: testsuite hangs on i386, x32)

2022-12-04 Thread Debian Bug Tracking System
Your message dated Sun, 04 Dec 2022 08:34:19 + with message-id and subject line Bug#1024154: fixed in llvm-toolchain-14 1:14.0.6-9 has caused the Debian Bug report #1024154, regarding llvm-toolchain-14: FTBFS: testsuite hangs on i386, x32 to be marked as done. This means that you claim that

Bug#1025406: tpm2-pytss: FTBFS in sid

2022-12-04 Thread Gianfranco Costamagna
Source: tpm2-pytss Version: 1.2.0-2 Severity: serious Hello, your package not FTBFS with a clean sid environment. Following the failure W: cgroups are not available on the host, not using them. I: pbuilder: network access will be disabled during build I: Current time: Sun Dec 4 09:06:09 CET

Bug#1023978: scikit-learn: FTBFS with Python 3.11 as a supported version

2022-12-04 Thread Paul Wise
Control: tags -1 + fixed-upstream patch Control: forwarded -1 https://github.com/scikit-learn/scikit-learn/commit/63f92d4adb61aed58d656544cc6caa9d68cb6065 On Sun, 13 Nov 2022 12:26:18 + Graham Inggs wrote: > scikit-learn FTBFS with Python 3.11 as a supported version. I noticed that

Processed: Re: scikit-learn: FTBFS with Python 3.11 as a supported version

2022-12-04 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + fixed-upstream patch Bug #1023978 [src:scikit-learn] scikit-learn: FTBFS with Python 3.11 as a supported version Added tag(s) patch and fixed-upstream. > forwarded -1 >