Bug#991060: reopen for bullseye
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 supplied patch? Cheers, -- Stéphane
Processed: Re: simbody: FTBFS on ppc64el, mips64el
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 problems
Bug#1024526: simbody: FTBFS on ppc64el, mips64el
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+
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 this patch to experimental, however I see no sign of v13 to be uploaded to unstable anytime soon. Can you please apply this same patch also in unstable? -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Bug#993065: marked as done (gnome-shell-extension-xrdesktop: Please update for gnome-shell 43)
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 that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 993065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993065 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-shell-extension-xrdesktop Version: 0.14.0-3 Severity: important git master appears to be compatible with gnome-shell 3.38 and 40. Thanks, Jeremy Bicha --- End Message --- --- Begin Message --- Version: 0.14.0-3+rm Dear submitter, as the package gnome-shell-extension-xrdesktop has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1018208 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1019098: marked as done (src:tbb: do not migrate. this source is deprecated in favor of src:onetbb)
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 you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1019098: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019098 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: tbb Version: 2020.3-2.1 Severity: serious src:tbb: do not migrate. this source is deprecated in favor of src:onetbb. The RM bug of src:tbb is filed at https://bugs.debian.org/1014990 --- End Message --- --- Begin Message --- Version: 2020.3-2.1+rm Dear submitter, as the package tbb has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1014990 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1024515: Acknowledgement (mariadb-10.6: FTBFS on s390x: test main.order_by_innodb failed with type 'ref')
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 not pass, so could also be the test behaviour was dependant on some dependency that updated in the past week?
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)
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" VERBOSE=1 returned exit code 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1020087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: guile-ssh Version: 0.13.1-6 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220917 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[5]: Entering directory '/<>/debian/build/guile-3.0/tests' > PASS: log.scm > FAIL: server.scm > PASS: session.scm > FAIL: client-server.scm > PASS: popen.scm > PASS: shell.scm > PASS: server-client.scm > PASS: sssh-ssshd.scm > FAIL: key.scm > PASS: tunnel.scm > PASS: dist.scm > >Guile-SSH 0.13.1: tests/test-suite.log > > > # TOTAL: 11 > # PASS: 8 > # SKIP: 0 > # XFAIL: 0 > # FAIL: 3 > # XPASS: 0 > # ERROR: 0 > > .. contents:: :depth: 2 > > FAIL: server > > > Starting test server > Group begin: server > Test begin: > test-name: "%make-server" > source-file: "tests/server.scm" > source-line: 35 > source-form: (test-assert "%make-server" (%make-server)) > Test end: > result-kind: pass > actual-value: # > Test begin: > test-name: "server?" > source-file: "tests/server.scm" > source-line: 38 > source-form: (test-assert "server?" (begin (set-log-userdata! "server?") > (let ((server (%make-server)) (x "I'm not a server")) (and (server? server) > (not (server? x)) > Test end: > result-kind: pass > actual-value: #t > Test begin: > test-name: "comparison of servers" > source-file: "tests/server.scm" > source-line: 44 > source-form: (test-assert "comparison of servers" (begin (set-log-userdata! > "comparison of servers") (let ((s1 (%make-server)) (s2 (%make-server))) (and > (equal? s1 s1) (not (equal? s1 s2)) > Test end: > result-kind: pass > actual-value: #t > Test begin: > test-name: "server-set!, valid values" > source-file: "tests/server.scm" > source-line: 50 > source-form: (test-assert "server-set!, valid values" (begin > (set-log-userdata! "server-set!, valid values") (let* ((server > (%make-server)) (topdir (getenv "abs_top_srcdir")) (options (quasiquote > ((bindaddr "127.0.0.1") (bindport 22) (unquote (if (>= %libssh-minor-version > 7) (list (quote hostkey) %rsakey %dsakey) (quote (hostkey "ssh-rsa" > "ssh-dss" (rsakey (unquote %rsakey)) (dsakey (unquote %dsakey)) (banner > "string") (log-verbosity nolog rare protocol packet functions) (blocking-mode > #f #t (log (test-runner-aux-value (test-runner-current))) (res #t)) > (for-each (lambda (opt) (for-each (lambda (val) (catch #t (lambda () > (server-set! server (car opt) val)) (lambda (key . args) (set! res #f) > (format log " opt: ~a, val: ~a, error: ~a~%" (car opt) val args (cdr > opt))) options) res))) > opt: hostkey, val: > /<>/debian/build/guile-3.0/../../../tests/keys/dsakey, error: > (server-set! Unable to set the option (# > hostkey /<>/debian/build/guile-3.0/../../../tests/keys/dsakey) > #f) > Test end: > result-kind: fail > actual-value: #f > Test begin: > test-name: "server-set!, invalid values" > source-file: "tests/server.scm" > source-line: 83 > source-form: (test-assert "server-set!, invalid values" (begin > (set-log-userdata! "server-set!, invalid values") (let ((server > (%make-server)) (options (quote ((bindaddr #f 42) (rsakey #f 42) (dsakey #f > 42) (bindport "I'm not a port" -42) (hostkey "invalid value" 1 (quote > invalid-value)) (banner 12345) (log-verbosity -1 0 1 2 3 4 5) (blocking-mode > 42 "string" (log (test-runner-aux-value (test-runner-current))) (res #t)) > (for-each (lambda (opt) (for-each (lambda (val) (catch #t (lambda () > (server-set! server (car opt) val) (format log " opt: ~a, val: ~a -- passed > mistakenly~%" (car opt) val) (set! res #f)) (lambda (key . args) #t))) (cdr > opt))) options) res))) > Test end: > result-kind: pass > actual-value: #t > Test begin: > test-name: "make-server" > source-file: "tests/server.scm" > source-line: 119 > source-form: (test-assert "make-server" (begin (set-log-userdata!
Processed: bug 1023804 is forwarded to https://github.com/mnauw/git-remote-hg/issues/53
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 'https://github.com/mnauw/git-remote-hg/issues/53'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1023804: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1023801 ...
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 > https://github.com/mgedmin/check-manifest/commit/1ce75c466c218a23082d685d34377cfbbe35f413 > https://github.com/mgedmin/check-manifest/pull/161 Bug #1023801 [src:check-manifest] check-manifest: autopkgtest needs update for new version of git: transport 'file' not allowed Set Bug forwarded-to-address to 'https://github.com/mgedmin/check-manifest/commit/1ce75c466c218a23082d685d34377cfbbe35f413 https://github.com/mgedmin/check-manifest/pull/161'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1023801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023801 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
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
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 an entire message, try calling #decoded on the various fields and body or parts if it is a multipart message.", got #https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019635 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-mail Version: 2.7.1+dfsg1-1.1 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-mail with ruby3.1 enabled, the build failed. Relevant part of the build log (hopefully): >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 > message.", got # #decoded on the various fields and bod...lling #decoded on the various fields > and body or parts if it is a multipart message.' >^> with backtrace: > # /<>/lib/mail/message.rb:1912:in `decoded' > # /<>/spec/mail/message_spec.rb:1525:in `block (4 > levels) in ' > # /<>/spec/mail/message_spec.rb:1525:in `block (3 > levels) in ' > # /<>/spec/mail/message_spec.rb:1525:in `block (3 levels) > in ' > > Finished in 1.49 seconds (files took 0.51284 seconds to load) > 1647 examples, 7 failures, 3 pending > > Failed examples: > > rspec /<>/spec/mail/message_spec.rb:199 # Mail::Message > initialization YAML serialization should serialize the basic information to > YAML > rspec /<>/spec/mail/message_spec.rb:210 # Mail::Message > initialization YAML serialization should deserialize after serializing > rspec /<>/spec/mail/message_spec.rb:216 # Mail::Message > initialization YAML serialization should serialize a Message with a custom > delivery_handler > rspec /<>/spec/mail/message_spec.rb:223 # Mail::Message > initialization YAML serialization should load a serialized delivery handler > rspec /<>/spec/mail/message_spec.rb:229 # Mail::Message > initialization YAML serialization should not deserialize a delivery_handler > that does not exist > rspec /<>/spec/mail/message_spec.rb:237 # Mail::Message > initialization YAML serialization should handle multipart mail > rspec /<>/spec/mail/message_spec.rb:1512 # Mail::Message output > should raise an error and message if you try and call decoded on a multipart > email > > /usr/bin/ruby3.1 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby3.1" failed: The full build log is available from: https://people.debian.org/~terceiro/ruby3.1/17/ruby-mail/ruby-mail_2.7.1+dfsg1-1.1+rebuild1663007790_amd64-2022-09-12T18:36:31Z.build To reproduce this, you need to install ruby-all-dev >= 1:3.0+2. Depending on when you try this, it might mean installing ruby-all-dev from experimental, or if the transition has already started, a normal build on unstable will be enough. If you fail to reproduce, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: ruby-mail Source-Version: 2.7.1+dfsg1-2 Done: Antonio Terceiro We believe that the bug you reported is fixed in the latest version of ruby-mail, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1019...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Terceiro (supplier of updated ruby-mail package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 04 Dec 2022 15:21:19 -0300 Source: ruby-mail Architecture: source Version: 2.7.1+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Antonio
Processed: libssh-dev: DSA support is disabled by default
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 bugs. Added blocking bug(s) of 1020087: 1025455 -- 1020087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020087 1025455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025455 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025027: marked as done (python-cffi: (autopkgtest) needs update for python3.11: Aborted)
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 the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1025027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-cffi Version: 1.15.1-3 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update User: debian-pyt...@lists.debian.org Usertags: python3.11 Control: affects -1 src:python3-defaults Dear maintainer(s), We are in the transition of adding python3.11 as a supported Python version [0]. With a recent upload of python3-defaults the autopkgtest of python-cffi fails in testing when that autopkgtest is run with the binary packages of python3-defaults from unstable. It passes when run with only packages from testing. In tabular form: passfail python3-defaults from testing3.10.6-3 python-cffifrom testing1.15.1-3 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of python3-defaults to testing [1]. https://docs.python.org/3/whatsnew/3.11.html lists what's new in Python3.11, it may help to identify what needs to be updated. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] https://bugs.debian.org/1021984 [1] https://qa.debian.org/excuses.php?package=python3-defaults https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-cffi/28732274/log.gz (0:04:55) = === python3.11-dbg === = test session starts == platform linux -- Python 3.11.0+, pytest-7.1.2, pluggy-1.0.0+repack rootdir: /tmp/autopkgtest-lxc.czowtejq/downtmp/autopkgtest_tmp collected 2019 items c/test_c.py [ 2%] [ 6%] ...s...s [ 10%] . [ 11%] testing/cffi0/test_cdata.py . [ 11%] testing/cffi0/test_ctypes.py ..s...s.s.s [ 13%] ...s.sss..s..s.. [ 17%] ...s [ 18%] testing/cffi0/test_ffi_backend.py ..s... [ 20%] ..ss [ 23%] ...s...s [ 27%] ...s.s...s... [ 29%] testing/cffi0/test_function.py ..s...s.s..ss..sss..ss [ 31%] testing/cffi0/test_model.py . [ 31%] testing/cffi0/test_ownlib.py ..ss...s [ 32%] testing/cffi0/test_parsing.py .s.. [ 34%] testing/cffi0/test_platform.py [ 34%] testing/cffi0/test_unicode_literals.py [ 34%] testing/cffi0/test_verify.py .s.s... [ 36%] [ 40%] ..s...sAborted autopkgtest [23:19:18]: test unittests3 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-cffi Source-Version: 1.15.1-4 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of python-cffi, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated python-cffi package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 04 Dec 2022 19:39:20 -0400 Source: python-cffi Architecture: source Version: 1.15.1-4 Distribution:
Processed: Bug#1019635 marked as pending in ruby-mail
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 message.", got #https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019635 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1019635: marked as pending in ruby-mail
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: https://salsa.debian.org/ruby-team/ruby-mail/-/commit/2460a6e62ef16ff6d73456ca7fb2550523726783 Add patches to fix tests with ruby3.1 Closes: #1019635 (this message was generated automatically) -- Greetings https://bugs.debian.org/1019635
Bug#1016332: librsb: FTBFS: gmake[3]: *** [Makefile:920: qtests] Error 1
Hi Rafael,
latex is not able to compile a rsbtest-generated
file looking like the one I attach.
The problematic line is:
\usepackage[utf8x]{inputenc}
and there are two alternative fixes to be applied before autoreconf:
Patch suggestion 1:
sed 's/utf8x//g' -i rsbtest/rsbtest.cpp
Patch 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: 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 removed from the upcoming bookworm
> release, unless the bug is fixed. This means that octave-sparsersb would
> also be absent from the next Debian release if nothing is done.
>
> I cannot reproduce the bug and I am hereby tagging this bug report
> accordingly. Skimming over the full build log [2], I could not find the
> source of the problem. If you could take a look at this, it will be great.
>
> Best,
>
> Rafael
>
> [1] https://bugs.debian.org/1016332
> [2] http://qa-logs.debian.net/2022/07/28/librsb_1.3.0.1+dfsg-2_unstable.log
>
> * Lucas Nussbaum [2022-07-29 20:37]:
>
> > Source: librsb
> > Version: 1.3.0.1+dfsg-2
> > Severity: serious
> > Justification: FTBFS
> > Tags: bookworm sid ftbfs
> > User: lu...@debian.org
> > Usertags: ftbfs-20220728 ftbfs-bookworm
> >
> > Hi,
> >
> > During a rebuild of all packages in sid, your package failed to build on
> > amd64.
> >
> > [snip]
> >
> > The full build log is available from:
> > http://qa-logs.debian.net/2022/07/28/librsb_1.3.0.1+dfsg-2_unstable.log
> >
> > All bugs filed during this archive rebuild are listed at:
> > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org
> > or:
> > https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220728=lu...@debian.org=1=1=1=1#results
> >
> > A list of current common problems and possible solutions is available at
> > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to
> > contribute!
> >
> > If you reassign this bug to another package, please marking it as
> > 'affects'-ing this package. See
> > https://www.debian.org/Bugs/server-control#affects
> >
> > If you fail to reproduce this, please provide a build log and diff it
> > with mine so that we can identify if something relevant changed in the
> > meantime.
% for f in ; do epstopdf $f; done;
%%%
\documentclass[xcolor=dvipsnames]{beamer}
%rm *.pdf *.aux *.nav *.out *.dvi *.log *.snm *.toc -f && ls && latex slides.tex && pdflatex slides.tex && pdflatex slides.tex && evince slides.pdf
\usepackage{color}
\usepackage{sverb} % for verbinput
\usepackage{hyperref} % for url
\usepackage{epsfig}
\hypersetup{pdfpagemode=fullscreen}
\setbeamertemplate{footline}[page number] % no footline
\setbeamertemplate{footline}[text line{...}] % no footline
\setbeamertemplate{navigation symbols}{}
\usepackage[]{verbatim}
\usepackage[]{ulem}
\usepackage{graphicx}
\usepackage{ucs}
\usepackage[utf8x]{inputenc}
\usepackage{epstopdf}
\usepackage[]{comment}
\usepackage[]{color}
%\logo{\includegraphics[scale=0.20]{logo.png}}
\def\mytitle{librsb autotuning benchmark report\\
Linked to librsb-88e18cc
compiled by "gcc"
with flags "-g -O2 -ffile-prefix-map=/root/librsb=. -fstack-protector-strong -Wformat -Werror=format-security -O3 -std=c99"
supporting up to 128 threads
and hardcoded cache parameters ""
and OpenMP enabled.
Supported types: "double,float,float complex,double complex"
Not using C++ RSB implementation.
Not using C++ wrapper to librsb.
Not linked to the Intel MKL.
\_\_cplusplus: 201703
\_\_GNUC\_\_: 12
\_\_GNUC\_MINOR\_\_: 1
}%
\title{\mytitle}
%\author[{michele DOT martone AT lrz DOT de}]{Michele MARTONE}
%\institute{LRZ\\
%Garching bei Muenchen, Germany
%}
%
%\date[]{Place\\Date}%
%
\def\plotwidth{0.6}
\begin{document}
\section{Title Page}
\frame { \titlepage }
%%%
%%
%%%
\begin{frame}[fragile]
\frametitle{Experiment Setup}
Experiment setup using:
\\ types in: D
\\ files in: A\_underscore.mtx
\\ thread spec in: 0
\\ transpositions in: 78
\\ nrhs in: 1
\\ incx in: 1
\\ incy in: 1
\\ density in: 50
Processed: Bug#1025027 marked as pending in python-cffi
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 problems
Bug#1025027: marked as pending in python-cffi
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: https://salsa.debian.org/python-team/packages/python-cffi/-/commit/06dee85317a78dad380bd514c313d32adfec4b59 Patch: Untrack some objects that triggered assertion failures in 3.11. (Closes: #1024767, #1025027) (this message was generated automatically) -- Greetings https://bugs.debian.org/1025027
Bug#1025454: afl: Downloads software during build
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 /<>/frida_mode/build/frida/frida-gumjs-devkit-15.2.1-linux-x86_64.tar.xz "https://github.com/frida/frida/releases/download/15.2.1/frida-gumjs-devkit-15.2.1-linux-x86_64.tar.xz; || curl -L -o /<>/frida_mode/build/frida/frida-gumjs-devkit-15.2.1-linux-x86_64.tar.xz "https://github.com/frida/frida/releases/download/15.2.1/frida-gumjs-devkit-15.2.1-linux-x86_64.tar.xz; /bin/sh: 1: wget: not found /bin/sh: 1: curl: not found make[3]: *** [GNUmakefile:313: /<>/frida_mode/build/frida/frida-gumjs-devkit-15.2.1-linux-x86_64.tar.xz] Error 127 make[3]: Leaving directory '/<>/frida_mode' make[2]: [GNUmakefile:636: distrib] Error 2 (ignored) cd nyx_mode && ./build_nyx_support.sh = Nyx build script = [*] Performing basic sanity checks... [*] Making sure all Nyx is checked out ./build_nyx_support.sh: line 41: git: command not found make[2]: [GNUmakefile:637: distrib] Error 127 (ignored) cd qemu_mode && sh ./build_qemu_support.sh = QemuAFL build script = [*] Performing basic sanity checks... [+] All checks passed! [*] Making sure qemuafl is checked out [*] cloning qemuafl Trying to clone qemuafl (attempt 1/3) ./build_qemu_support.sh: 84: git: not found Trying to clone qemuafl (attempt 2/3) ./build_qemu_support.sh: 84: git: not found Trying to clone qemuafl (attempt 3/3) ./build_qemu_support.sh: 84: git: not found [-] Not checked out, please install git or check your internet connection. make[2]: [GNUmakefile:638: distrib] Error 1 (ignored) cd unicorn_mode && unset CFLAGS && sh ./build_unicorn_support.sh = UnicornAFL build script = [...] On machines that have more software installed, it will download various things and build them. It makes at least use of software like wget, curl, git, cargo. Packages in Debian should be build only from the source and not download more sources from internet. Kurt
Bug#1025313: marked as done (nip2: FTBFS with fftw3 (3.3.10-1))
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 this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1025313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025313 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nip2 Version: 8.7.1-3 Severity: serious Tags: ftbfs patch Dear Maintainer, Your package FTBFS with fftw3 (3.3.10-1) because it not longer provides fftw3-dev. The attached patch resolves the issue by making libfftw3-dev the first alternative. Kind Regards, Bas diff -Nru nip2-8.7.1/debian/changelog nip2-8.7.1/debian/changelog --- nip2-8.7.1/debian/changelog 2022-05-26 18:28:53.0 +0200 +++ nip2-8.7.1/debian/changelog 2022-12-02 13:09:59.0 +0100 @@ -1,3 +1,10 @@ +nip2 (8.7.1-3.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Build depend on libfftw3-dev, fftw3-dev no longer provided. + + -- Bas Couwenberg Fri, 02 Dec 2022 13:09:59 +0100 + nip2 (8.7.1-3) unstable; urgency=medium * Backport upstream fix for compilation with ICU 68+ (closes: #1011693). diff -Nru nip2-8.7.1/debian/control nip2-8.7.1/debian/control --- nip2-8.7.1/debian/control 2021-01-19 06:42:23.0 +0100 +++ nip2-8.7.1/debian/control 2022-12-02 13:09:59.0 +0100 @@ -1,7 +1,7 @@ Source: nip2 Section: graphics Priority: optional -Build-Depends: debhelper-compat (= 12), libglib2.0-dev, libpango1.0-dev, libatk1.0-dev, libgtk2.0-dev, libvips-dev (>= 8.4), shared-mime-info, gnome-icon-theme, hicolor-icon-theme, flex, bison, intltool, fftw3-dev | libfftw3-dev, libxml2-dev, pkg-config, libjpeg-dev, zlib1g-dev, libpng-dev, libmagickcore-dev, libmagickwand-dev, libfreetype6-dev, libfontconfig1-dev, libice-dev, gettext, libgsl-dev, libgraphviz-dev +Build-Depends: debhelper-compat (= 12), libglib2.0-dev, libpango1.0-dev, libatk1.0-dev, libgtk2.0-dev, libvips-dev (>= 8.4), shared-mime-info, gnome-icon-theme, hicolor-icon-theme, flex, bison, intltool, libfftw3-dev | fftw3-dev, libxml2-dev, pkg-config, libjpeg-dev, zlib1g-dev, libpng-dev, libmagickcore-dev, libmagickwand-dev, libfreetype6-dev, libfontconfig1-dev, libice-dev, gettext, libgsl-dev, libgraphviz-dev Maintainer: Laszlo Boszormenyi (GCS) Standards-Version: 4.5.1 Homepage: https://github.com/libvips/nip2 --- End Message --- --- Begin Message --- Source: nip2 Source-Version: 8.7.1-4 Done: Laszlo Boszormenyi (GCS) We believe that the bug you reported is fixed in the latest version of nip2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Laszlo Boszormenyi (GCS) (supplier of updated nip2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 04 Dec 2022 20:17:50 +0100 Source: nip2 Architecture: source Version: 8.7.1-4 Distribution: unstable Urgency: medium Maintainer: Laszlo Boszormenyi (GCS) Changed-By: Laszlo Boszormenyi (GCS) Closes: 1025313 Changes: nip2 (8.7.1-4) unstable; urgency=medium . * Adjust build dependency to libfftw3-dev (closes: #1025313). * Update Standards-Version to 4.6.1 . Checksums-Sha1: c9768234be93702d6a5ac826a26832c54f4cfe6a 2058 nip2_8.7.1-4.dsc b5dc3438ad6b53671181d97ead7df23bd3f27910 8260 nip2_8.7.1-4.debian.tar.xz Checksums-Sha256: 07c9ccc7d94e896294fad1d3a835faac58026cc3d81add184d2c545c7b3a9cda 2058 nip2_8.7.1-4.dsc 1dced517646c126a5cf0ac06907a2a5ee81c2c38b090a9888dc81c0def3f29d9 8260 nip2_8.7.1-4.debian.tar.xz Files: b4cf52f05b7044eeb4459c399f7d8142 2058 graphics optional nip2_8.7.1-4.dsc 92c715397bbcc537e12da74c67e91c33 8260 graphics optional nip2_8.7.1-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfYh9yLp7u6e4NeO63OMQ54ZMyL8FAmONGnsACgkQ3OMQ54ZM yL+7yhAAuGZvMEPGg8N0UifidH8nMRjhzn0r0N4H3WjrFNBjWGMF3JQCxL4/w0Na ln8g4EDVzFjfHh1jnCxgilnk2EGBRqJbWAWaxyvj+c6QRDpaDfU4NS0SmpZRvfF0 FtprzxpRIVtr66KOdpLaoH5uipNcruYHpfVhN2IQHuzLEOkj8uJtcBD7ZnRj+2jo ir9Oo+sli5INJNZDj3SfCHrQV+Qvh4RKk/g0Co099cjdwjvID3ojSfjYegIMu0on
Processed: your mail
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 hangs on install (and start phase) Added tag(s) buster. > End of message, stopping processing here. Please contact me if you need assistance. -- 528062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=528062 967010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: nghttp2: missing build-dependency on tzdata
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 fails in arch-only build'. > tags 981600 + patch Bug #981600 [src:nghttp2] nghttp2: missing build-depends on tzdata Added tag(s) patch. > severity 981600 serious Bug #981600 [src:nghttp2] nghttp2: missing build-depends on tzdata Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 981600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1016332: librsb: FTBFS: gmake[3]: *** [Makefile:920: qtests] Error 1
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] librsb: FTBFS: gmake[3]: *** [Makefile:920: qtests] Error 1 Added tag(s) unreproducible. -- 1016332: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1016332: librsb: FTBFS: gmake[3]: *** [Makefile:920: qtests] Error 1
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 removed from the upcoming bookworm release, unless the bug is fixed. This means that octave-sparsersb would also be absent from the next Debian release if nothing is done. I cannot reproduce the bug and I am hereby tagging this bug report accordingly. Skimming over the full build log [2], I could not find the source of the problem. If you could take a look at this, it will be great. Best, Rafael [1] https://bugs.debian.org/1016332 [2] http://qa-logs.debian.net/2022/07/28/librsb_1.3.0.1+dfsg-2_unstable.log * Lucas Nussbaum [2022-07-29 20:37]: Source: librsb Version: 1.3.0.1+dfsg-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220728 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. [snip] The full build log is available from: http://qa-logs.debian.net/2022/07/28/librsb_1.3.0.1+dfsg-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220728;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220728=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.
Bug#1022526: marked as done (python-ssdeep: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command)
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 done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1022526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-ssdeep
Version: 3.1+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py config
> /<>/setup.py:7: DeprecationWarning: The distutils package is
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP
> 632 for potential alternatives
> from distutils.command.build import build
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
> Distutils was imported before Setuptools, but importing Setuptools also
> replaces the `distutils` module in `sys.modules`. This may lead to
> undesirable behaviors or errors. To avoid these issues, avoid using distutils
> directly, ensure that setuptools is installed in the traditional way (e.g.
> not an editable install), and/or make sure that setuptools is always imported
> before distutils.
> warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
> Setuptools is replacing distutils.
> warnings.warn("Setuptools is replacing distutils.")
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3 setup.py build
> /<>/setup.py:7: DeprecationWarning: The distutils package is
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP
> 632 for potential alternatives
> from distutils.command.build import build
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning:
> Distutils was imported before Setuptools, but importing Setuptools also
> replaces the `distutils` module in `sys.modules`. This may lead to
> undesirable behaviors or errors. To avoid these issues, avoid using distutils
> directly, ensure that setuptools is installed in the traditional way (e.g.
> not an editable install), and/or make sure that setuptools is always imported
> before distutils.
> warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning:
> Setuptools is replacing distutils.
> warnings.warn("Setuptools is replacing distutils.")
> Traceback (most recent call last):
> File "/<>/setup.py", line 87, in
> setup(
> File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in
> setup
> return distutils.core.setup(**attrs)
> File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line
> 172, in setup
> ok = dist.parse_command_line()
> File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
> 474, in parse_command_line
> args = self._parse_command_opts(parser, args)
> File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1107, in
> _parse_command_opts
> nargs = _Distribution._parse_command_opts(self, parser, args)
> File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line
> 540, in _parse_command_opts
> raise DistutilsClassError(
> distutils.errors.DistutilsClassError: command class '__main__.CFFIBuild'> must subclass Command
> E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1:
> /usr/bin/python3 setup.py build
> dh_auto_build: error: pybuild --build -i python{version} -p 3.10 returned
> exit code 13
> make: *** [debian/rules:5: binary] Error 25
The full build log is available from:
http://qa-logs.debian.net/2022/10/23/python-ssdeep_3.1+dfsg-3_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221023;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221023=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS .
Bug#1025317: marked as done (vips: FTBFS with fftw3 (3.3.10-1))
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 this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1025317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025317
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vips
Version: 8.13.3-1
Severity: serious
Tags: ftbfs patch
Dear Maintainer,
Your package FTBFS with fftw3 (3.3.10-1) because it not longer provides
fftw3-dev.
The attached patch resolves the issue by changing the dependency to
libfftw3-dev.
Kind Regards,
Bas
diff -Nru vips-8.13.3/debian/changelog vips-8.13.3/debian/changelog
--- vips-8.13.3/debian/changelog2022-11-12 07:01:18.0 +0100
+++ vips-8.13.3/debian/changelog2022-12-02 14:09:07.0 +0100
@@ -1,3 +1,10 @@
+vips (8.13.3-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Build depend on libfftw3-dev, fftw3-dev no longer provided.
+
+ -- Bas Couwenberg Fri, 02 Dec 2022 14:09:07 +0100
+
vips (8.13.3-1) unstable; urgency=medium
* New upstream release.
diff -Nru vips-8.13.3/debian/control vips-8.13.3/debian/control
--- vips-8.13.3/debian/control 2022-02-28 22:28:00.0 +0100
+++ vips-8.13.3/debian/control 2022-12-02 14:09:06.0 +0100
@@ -5,7 +5,7 @@
libjpeg-dev, libtiff-dev, libpng-dev (>= 1.2.9), libgif-dev (>= 5.1),
libcgif-dev, librsvg2-dev (>= 2.40.0), libpoppler-glib-dev,
gobject-introspection,
- zlib1g-dev, fftw3-dev | libfftw3-dev, liblcms2-dev, libmagickcore-dev,
+ zlib1g-dev, libfftw3-dev, liblcms2-dev, libmagickcore-dev,
libmagickwand-dev, libfreetype6-dev, libpango1.0-dev, libfontconfig1-dev,
libglib2.0-dev, libice-dev, libimagequant-dev, liborc-0.4-dev, libheif-dev,
libmatio-dev, libexpat1-dev, libcfitsio-dev, libopenslide-dev, libwebp-dev,
@@ -42,7 +42,7 @@
Package: libvips-dev
Section: libdevel
Architecture: any
-Depends: ${misc:Depends}, libvips42 (= ${binary:Version}), gir1.2-vips-8.0 (=
${binary:Version}), libjpeg-dev, libtiff-dev, zlib1g-dev, fftw3-dev |
libfftw3-dev, liblcms2-dev, libpng-dev, libmagickcore-dev, libmagickwand-dev,
libfreetype6-dev, libpango1.0-dev, libfontconfig1-dev, libglib2.0-dev,
libice-dev, gettext, pkg-config, liborc-0.4-dev, libopenexr-dev, libmatio-dev,
libexpat1-dev, libcfitsio-dev, libopenslide-dev, libwebp-dev, libgsf-1-dev,
libgif-dev (>= 5.1), libcgif-dev, libpoppler-glib-dev, librsvg2-dev (>=
2.40.0), libimagequant-dev, libheif-dev
+Depends: ${misc:Depends}, libvips42 (= ${binary:Version}), gir1.2-vips-8.0 (=
${binary:Version}), libjpeg-dev, libtiff-dev, zlib1g-dev, libfftw3-dev,
liblcms2-dev, libpng-dev, libmagickcore-dev, libmagickwand-dev,
libfreetype6-dev, libpango1.0-dev, libfontconfig1-dev, libglib2.0-dev,
libice-dev, gettext, pkg-config, liborc-0.4-dev, libopenexr-dev, libmatio-dev,
libexpat1-dev, libcfitsio-dev, libopenslide-dev, libwebp-dev, libgsf-1-dev,
libgif-dev (>= 5.1), libcgif-dev, libpoppler-glib-dev, librsvg2-dev (>=
2.40.0), libimagequant-dev, libheif-dev
Recommends: libvips-doc, libvips-tools
Suggests: nip2
Description: image processing system good for very large ones (dev)
--- End Message ---
--- Begin Message ---
Source: vips
Source-Version: 8.13.3-2
Done: Laszlo Boszormenyi (GCS)
We believe that the bug you reported is fixed in the latest version of
vips, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1025...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS) (supplier of updated vips package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 04 Dec 2022 20:17:39 +0100
Source: vips
Architecture: source
Version: 8.13.3-2
Distribution: unstable
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS)
Changed-By: Laszlo Boszormenyi (GCS)
Closes: 1025317
Changes:
vips (8.13.3-2) unstable; urgency=medium
.
* Adjust build dependency to libfftw3-dev (closes: #1025317).
* Update Standards-Version to 4.6.1 .
Checksums-Sha1:
a8579fa15453d18360595897d79513b87854bbba 2461
Processed: unarchive for bullseye
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
Unarchived Bug 1013554
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1013554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: unarchive for bullseye
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 -Dmaven.home=/usr/share/maven
-Dmaven.multiModuleProjectDirectory=/<>
-Dclassworlds.conf=/etc/maven/m2-debian.conf
org.codehaus.plexus.classworlds.launcher.Launcher
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode test
returned exit code 1
Unarchived Bug 997580
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
997580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: unarchive again for bullseye
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 message, stopping processing here.
Please contact me if you need assistance.
--
997222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997222
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: jruby,jruby-openssl: both ship /usr/share/jruby/lib/ruby/stdlib/*openssl*
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 jruby/9.3.9.0+ds-1. > found -1 0.9.21-4 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' at version '0.9.21-4' with architecture '' Marked as found in versions jruby-openssl/0.9.21-4. -- 1025442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025442 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025442: jruby,jruby-openssl: both ship /usr/share/jruby/lib/ruby/stdlib/*openssl*
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 declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../jruby-openssl_0.9.21-4_all.deb ... Unpacking jruby-openssl (0.9.21-4) ... dpkg: error processing archive /var/cache/apt/archives/jruby-openssl_0.9.21-4_all.deb (--unpack): trying to overwrite '/usr/share/jruby/lib/ruby/stdlib/jopenssl/load.rb', which is also in package jruby 9.3.9.0+ds-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/jruby-openssl_0.9.21-4_all.deb If jruby-openssl is obsolete, please RM it and add to jruby Breaks+Replaces: jruby-openssl and probably also a (versioned) Provides: jruby-openssl cheers, Andreas jruby=9.3.9.0+ds-1_jruby-openssl=0.9.21-4.log.gz Description: application/gzip
Processed: reopen for bullseye
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 to re-add them.
Bug reopened
No longer marked as fixed in versions 0.9-1.
> found 991060 0.8.1-8
Bug #991060 [src:mlpost] mlpost FTBFS with imagemagick with the #987504 change
Ignoring request to alter found versions of bug #991060 to the same values
previously set
> fixed 991060 0.9-1
Bug #991060 [src:mlpost] mlpost FTBFS with imagemagick with the #987504 change
Marked as fixed in versions mlpost/0.9-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
991060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#991060: reopen for bullseye
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)
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 problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1024453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mediathekview Version: 13.2.1+ds-1 Severity: grave X-Debbugs-Cc: sramac...@debian.org Since the switch to openjre-17 as default, mediathekview nolonger starts: $ mediathekview [warning] /usr/bin/mediathekview: No java runtime was found Cheers -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (650, 'unstable-debug'), (650, 'unstable'), (601, 'testing'), (600, 'experimental-debug'), (600, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages mediathekview depends on: ii default-jre [java9-runtime] 2:1.17-73 ii java-wrappers 0.3 ii libcommons-compress-java1.21-1 ii libcommons-configuration2-java 2.8.0-1 ii libcommons-dbcp2-java 2.9.0-1 ii libcommons-lang3-java 3.12.0-2 ii libcommons-pool2-java 2.11.1-1 ii libcontrolsfx-java 11.0.0-1 ii libguava-java 29.0-6 ii libjackson2-core-java 2.14.0-2 ii libjchart2d-java3.2.2+dfsg2-3 ii libjiconfont-font-awesome-java 4.7.0.1-1 ii libjiconfont-java 1.0.0-2 ii libjiconfont-swing-java 1.0.1-2 ii libjide-oss-java3.7.6+dfsg-2 ii liblog4j2-java 2.17.2-1 ii libmbassador-java 1.3.1-2 ii libmiglayout-java 5.1-3 ii libokhttp-java 3.13.1-3 ii libopenjfx-java 11.0.11+1-1.1 ii libslf4j-java 1.7.32-1 ii libswingx-java 1:1.6.2-4 ii libxz-java 1.9-1 ii openjdk-17-jre [java9-runtime] 17.0.5+8-2 Versions of packages mediathekview recommends: pn flvstreamer ii mpv 0.35.0-2 ii vlc 3.0.18~rc2-1+b1 Versions of packages mediathekview suggests: ii ffmpeg 7:5.1.2-1 -- no debconf information -- Sebastian Ramacher --- End Message --- --- Begin Message --- Version: 0.4 On 2022-11-19 19:31:05 +0100, Sebastian Ramacher wrote: > Control: reassign -1 java-wrappers 0.3 > Control: affects -1 mediathekview > > On 2022-11-19 19:18:14 +0100, Sebastian Ramacher wrote: > > Package: mediathekview > > Version: 13.2.1+ds-1 > > Severity: grave > > X-Debbugs-Cc: sramac...@debian.org > > > > Since the switch to openjre-17 as default, mediathekview nolonger > > starts: > > > > $ mediathekview > > [warning] /usr/bin/mediathekview: No java runtime was found > > This is an issue in java-wrappers. It does not know about version 17. java-wrappers (0.4) unstable; urgency=medium . * Team upload. * Add JDK17-20 (Closes: #1011165) * Switch to debhelper-compat 13 * Add R³ * Add Multi-Arch according to MA hinter * Update Vcs fields * Make d/copyright machine readable * Bump policy version (no changes) Cheers -- Sebastian Ramacher--- End Message ---
Bug#1024987: marked as done (sweethome3d: Fail to start)
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 dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1024453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: sweethome3d Version: 7.0.2+dfsg-1 Severity: grave Dear Maintainer, sweethome3d fail to start. Maybe related to java 17 as sweethome3d was working with java 11 , | $ sweethome3d | [warning] /usr/bin/sweethome3d: No java runtime was found | [warning] /usr/bin/sweethome3d: No JAVA_CMD set for run_java, falling back to JAVA_CMD = java | Java 3D: implicit antialiasing enabled | Exception in thread "J3D-Renderer-1" java.lang.IllegalAccessError: class javax.media.j3d.X11NativeConfigTemplate3D (in unnamed module @0x614635c2) cannot access class sun.awt.X11GraphicsConfig (in module java.desktop) because module java.desktop does not export sun.awt to unnamed module @0x614635c2 | at javax.media.j3d.X11NativeConfigTemplate3D.isGraphicsConfigSupported(X11NativeConfigTemplate3D.java:180) | at javax.media.j3d.NativePipeline.isGraphicsConfigSupported(NativePipeline.java:3341) | at javax.media.j3d.Renderer.doWork(Renderer.java:533) | at javax.media.j3d.J3dThread.run(J3dThread.java:275) ` Christian -- System Information: Debian Release: bookworm/sid APT prefers buildd-unstable APT policy: (500, 'buildd-unstable'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.10 (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages sweethome3d depends on: ii default-jre [java8-runtime] 2:1.17-73 ii icedtea-netx1.8.8-2 ii java-wrappers 0.3 ii libbatik-java 1.16+dfsg-1 ii libfreehep-graphics2d-java 2.4+dfsg-3 ii libfreehep-graphicsbase-java2.4+dfsg-3 ii libfreehep-graphicsio-java 2.4+dfsg-3 ii libfreehep-graphicsio-svg-java 2.4+dfsg-3 ii libitext-java 2.1.7-13 ii libjava3d-java 1.5.2+dfsg-17 ii libsunflow-java 0.07.2.svn396+dfsg-18 ii openjdk-17-jre [java8-runtime] 17.0.5+8-2 Versions of packages sweethome3d recommends: pn sweethome3d-furniture sweethome3d suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 0.4 On 2022-11-19 19:31:05 +0100, Sebastian Ramacher wrote: > Control: reassign -1 java-wrappers 0.3 > Control: affects -1 mediathekview > > On 2022-11-19 19:18:14 +0100, Sebastian Ramacher wrote: > > Package: mediathekview > > Version: 13.2.1+ds-1 > > Severity: grave > > X-Debbugs-Cc: sramac...@debian.org > > > > Since the switch to openjre-17 as default, mediathekview nolonger > > starts: > > > > $ mediathekview > > [warning] /usr/bin/mediathekview: No java runtime was found > > This is an issue in java-wrappers. It does not know about version 17. java-wrappers (0.4) unstable; urgency=medium . * Team upload. * Add JDK17-20 (Closes: #1011165) * Switch to debhelper-compat 13 * Add R³ * Add Multi-Arch according to MA hinter * Update Vcs fields * Make d/copyright machine readable * Bump policy version (no changes) Cheers -- Sebastian Ramacher--- End Message ---
Bug#1025440: FTBFS: fails to compile with Java errors
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.* imports. I've also seen the same build failure when the package got synced to Ubuntu (https://launchpad.net/ubuntu/+source/starjava-ttools/3.4.7-2/+build/24622556) as well as locally on my Sid system. Not sure what might have changed since the package got uploaded in the first place. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-4-amd64 (SMP w/3 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- mvh / best regards Hans Joachim Desserud http://desserud.org
Processed: jbigkit: diff for NMU version 2.1-6.1
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 directory Added tag(s) pending. -- 1023710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1023710: jbigkit: diff for NMU version 2.1-6.1
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 jbigkit-2.1/debian/changelog --- jbigkit-2.1/debian/changelog 2022-10-11 01:46:00.0 +0200 +++ jbigkit-2.1/debian/changelog 2022-12-04 19:16:16.0 +0100 @@ -1,3 +1,10 @@ +jbigkit (2.1-6.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix autopkgtest (Closes: #1023710) + + -- Jochen Sprickerhof Sun, 04 Dec 2022 19:16:16 +0100 + jbigkit (2.1-6) unstable; urgency=medium * Rehome JBIGKit packaging onto salsa.debian.org diff -Nru jbigkit-2.1/debian/tests/run-unit-test jbigkit-2.1/debian/tests/run-unit-test --- jbigkit-2.1/debian/tests/run-unit-test 2022-10-11 01:46:00.0 +0200 +++ jbigkit-2.1/debian/tests/run-unit-test 2022-12-04 19:12:00.0 +0100 @@ -1,4 +1,6 @@ #!/bin/sh +set -e + +cd debian/tests make -f unittests-Makefile -j1 test -exit $? signature.asc Description: PGP signature
Processed: Adding ibus-cangjie and keyman to the "Affects" list
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 not workiing. Added indication that 1025312 affects src:ibus-cangjie and src:keyman Added indication that 1025324 affects src:ibus-cangjie and src:keyman > End of message, stopping processing here. Please contact me if you need assistance. -- 1025312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025312 1025324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025324 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025377: marked as done (texstudio: Switch to libqtermwidget5-1-dev)
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 dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1025377: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025377 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: texstudio Version: 4.3.1+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org Unfortunately, qtermwidget bumpbed SONAME and also changed the name of the -dev package. The new -dev package is called libqtermwidget5-1-dev. Please adopt the package accordingly. Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: texstudio Source-Version: 4.3.1+ds-2 Done: Tom Jampen We believe that the bug you reported is fixed in the latest version of texstudio, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Tom Jampen (supplier of updated texstudio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 04 Dec 2022 18:23:11 +0100 Source: texstudio Architecture: source Version: 4.3.1+ds-2 Distribution: unstable Urgency: medium Maintainer: Tom Jampen Changed-By: Tom Jampen Closes: 1025377 Changes: texstudio (4.3.1+ds-2) unstable; urgency=medium . * Updating build dependency due to the qtermwidget transition (Closes: #1025377). Checksums-Sha1: 0148ea824e01276dc16ace9cd2aebba45023e52c 2136 texstudio_4.3.1+ds-2.dsc 6a982a1efaab986ce5b9ad3d2797b89749d34975 23328 texstudio_4.3.1+ds-2.debian.tar.xz f6ea4a9688ad2a971ca4a24820306ba529129819 17340 texstudio_4.3.1+ds-2_source.buildinfo Checksums-Sha256: ae022535fcd6664f26c9a8d776cf3a6981522c756e42e39f6d265aeb5b2da798 2136 texstudio_4.3.1+ds-2.dsc a292c7a6d22646b5139ef18a4c2fe3dda0ca49cd530689bbf0cdaa033b36b820 23328 texstudio_4.3.1+ds-2.debian.tar.xz 113ee771b5ff822903c5a45ece074744c80bee42ccdc879fe6dafb5a78c91e20 17340 texstudio_4.3.1+ds-2_source.buildinfo Files: a516c603d99d826429e20111e51e3466 2136 editors optional texstudio_4.3.1+ds-2.dsc b903cf1b9c566281974f3fbbb91a3c2c 23328 editors optional texstudio_4.3.1+ds-2.debian.tar.xz 3f96e5ad17023e4e57830e5b8bece81d 17340 editors optional texstudio_4.3.1+ds-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEnpMtHgsxz4UK/Hmebz5hUxY+BXcFAmOM2BkUHHRvbUBjcnlw dG9ncmFwaHkuY2gACgkQbz5hUxY+BXcc+Q//fOpYBqRy5goDe60d6tbvx+ZGmp7D 186UH/qGUhk3fzXLb0AZK+H/WAtvffNCPNoKeRIZDE1jKjvpK3Qa/Z2SXhDYH02Q zxZ14UaQHvRqvva45HlCEQHgiEx8J3ittQcQ84fwM0kSg0cj/87Izz5RzhVNpB2V hFmmsxCbiRGWAJ2dP38ykQH84lZca+Rd//VHF1CpH3iKQyr6CBbDZmtM/k2jQtl6 duij4NFhbKno5pEyFSPCzlH4Hz576slqPXPtBDGpaCZxtzUAB51BMHUyy0feOq5f MrriA9sSmXqkago//H14OZ5AV6xjBXtWE0vCGMWohcOVfE3a8DoraDByt23xnKkm rVmINizzZXTjIAggjklipeKF54t+A0ohcmp4M9MYYpxlN49Lqcx7fb5Q58q0aLDi ZUmWVAxPift7a+yEVb/K3BhJasGIrjniI2FWa8wd7TA9MZdJwXQQ3U9unkM5wPk4 QuwSJdg7WfsFehAnDBI6Vfgl66MxeB+RRPSEzf0copMAH8pOnwHGOtD4G15tu9h/ sQtcr/fvYoEmtLSYqlgYDQYwCSpp2MpApcvnUghpFDGfXtraKE7LvFHQ7nRBWo2t Li+qzU/bt5+SbvOxeOTgGFVo6/cu8rBVgu8WRthBP5QpFeFAx1PlMGHNiNxk5RBQ ZX+35gdbnhZ7tLk= =btHC -END PGP SIGNATURE End Message ---
Processed: tagging 1002353, tagging 1023986
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] parso: too old to parse Python 3.11
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1002353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002353
1023986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023986
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1009482: marked as done (sphinxcontrib-autoprogram: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.10 returned exit code 13)
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.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1009482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sphinxcontrib-autoprogram
Version: 0.1.7-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220412 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with=python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:239: python3.10 setup.py config
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:239: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10/build/sphinxcontrib
> copying sphinxcontrib/__init__.py ->
> /<>/.pybuild/cpython3_3.10/build/sphinxcontrib
> copying sphinxcontrib/autoprogram.py ->
> /<>/.pybuild/cpython3_3.10/build/sphinxcontrib
> running egg_info
> creating sphinxcontrib_autoprogram.egg-info
> writing sphinxcontrib_autoprogram.egg-info/PKG-INFO
> writing dependency_links to
> sphinxcontrib_autoprogram.egg-info/dependency_links.txt
> writing namespace_packages to
> sphinxcontrib_autoprogram.egg-info/namespace_packages.txt
> writing requirements to sphinxcontrib_autoprogram.egg-info/requires.txt
> writing top-level names to sphinxcontrib_autoprogram.egg-info/top_level.txt
> writing manifest file 'sphinxcontrib_autoprogram.egg-info/SOURCES.txt'
> reading manifest file 'sphinxcontrib_autoprogram.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'README'
> warning: no files found matching 'CHANGES.*'
> warning: manifest_maker: MANIFEST.in, line 4: unknown action 'tox.ini'
>
> adding license file 'LICENSE'
> writing manifest file 'sphinxcontrib_autoprogram.egg-info/SOURCES.txt'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:239: python3.10 setup.py test
> running test
> WARNING: Testing via this command is deprecated and will be removed in a
> future version. Users looking for a generic test entry point independent of
> test runner are encouraged to use tox.
> running egg_info
> writing sphinxcontrib_autoprogram.egg-info/PKG-INFO
> writing dependency_links to
> sphinxcontrib_autoprogram.egg-info/dependency_links.txt
> writing namespace_packages to
> sphinxcontrib_autoprogram.egg-info/namespace_packages.txt
> writing requirements to sphinxcontrib_autoprogram.egg-info/requires.txt
> writing top-level names to sphinxcontrib_autoprogram.egg-info/top_level.txt
> reading manifest file 'sphinxcontrib_autoprogram.egg-info/SOURCES.txt'
> reading manifest template 'MANIFEST.in'
> warning: no files found matching 'README'
> warning: no files found matching 'CHANGES.*'
> warning: manifest_maker: MANIFEST.in, line 4: unknown action 'tox.ini'
>
> adding license file 'LICENSE'
> writing manifest file 'sphinxcontrib_autoprogram.egg-info/SOURCES.txt'
> running build_ext
> test_argument_groups (sphinxcontrib.autoprogram.ScannerTestCase) ... FAIL
> test_choices (sphinxcontrib.autoprogram.ScannerTestCase) ... ok
> test_parse_epilog (sphinxcontrib.autoprogram.ScannerTestCase) ... ok
> test_simple_parser (sphinxcontrib.autoprogram.ScannerTestCase) ... ok
> test_subcommands (sphinxcontrib.autoprogram.ScannerTestCase) ... ok
> test_make_rst (sphinxcontrib.autoprogram.AutoprogramDirectiveTestCase) ... ok
> test_import_object (sphinxcontrib.autoprogram.UtilTestCase) ... ok
>
> ==
> FAIL: test_argument_groups (sphinxcontrib.autoprogram.ScannerTestCase)
> --
> Traceback (most recent call last):
> File "/<>/sphinxcontrib/autoprogram.py", line 479, in
> test_argument_groups
> self.assertEqual("optional arguments", group.title)
> AssertionError: 'optional arguments' != 'options'
> - optional arguments
> + options
>
>
> --
> Ran 7 tests in 0.007s
>
> FAILED (failures=1)
> Test failed:
> error: Test
Bug#1012382: pktanon: autopkgtest fails on s390x with: wrong pcap file version: should be 2.4
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 version fails somehow? I assume that pktanon simply isn't portable enough to work on architectures not intended by upstream. I have opened an issue in upstream's GitHub [0] -- but as a previous one [1] regarding ARM issues remained unanswered I assume that portability to some exotic platforms is probably not a high priority. TBH I could live with that as well. Since pktanon does not seem to work reliably on that platform, I am going to remove s390x from the list of supported platforms to allow it to migrate to testing. Cheers Sascha [0] https://github.com/KIT-Telematics/pktanon/issues/8 [1] https://github.com/KIT-Telematics/pktanon/issues/7 OpenPGP_signature Description: OpenPGP digital signature
Bug#1019638: marked as done (ruby-memory-profiler: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed.)
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 that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1019638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-memory-profiler Version: 0.9.14-4 Severity: important Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.1 Hi, We are about to start the ruby3.1 transition in unstable. While trying to rebuild ruby-memory-profiler with ruby3.1 enabled, the build failed. Relevant part of the build log (hopefully): > /usr/bin/ruby3.1 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby3.1 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-memory-profiler/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0 > ruby3.1 -e gem\ \"memory_profiler\" > > ┌──┐ > │ Run tests for ruby3.1 from debian/ruby-tests.rake > │ > └──┘ > > RUBYLIB=. > GEM_PATH=/<>/debian/ruby-memory-profiler/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0 > ruby3.1 -S rake -f debian/ruby-tests.rake > /usr/bin/ruby3.1 -w > /usr/lib/ruby/gems/3.1.0/gems/rake-13.0.6/lib/rake/rake_test_loader.rb > "test/test_helper.rb" "test/test_helpers.rb" "test/test_reporter.rb" > "test/test_reporter_private_start_stop.rb" > "test/test_reporter_public_start_stop.rb" "test/test_results.rb" > "test/test_stat_hash.rb" "test/test_top_n.rb" -v > Run options: -v --seed 49086 > > # Running: > > TestReporterPublicStartStop#test_no_strings_retained_report = 0.02 s = F > TestReporterPublicStartStop#test_anonymous_class_object = 0.02 s = . > TestReporterPublicStartStop#test_yield_block = 0.02 s = . > TestReporterPublicStartStop#test_ignore_file_with_regex = 0.02 s = . > TestReporterPublicStartStop#test_ignore_file_with_string = 0.02 s = . > TestReporterPublicStartStop#test_strings_report = 0.02 s = . > TestReporterPublicStartStop#test_module_double_start = 0.02 s = . > TestReporterPublicStartStop#test_module_stop_with_no_start = 0.00 s = . > TestReporterPublicStartStop#test_mono_output_defaults_to_true_when_not_run_from_tty > = 0.02 s = . > TestReporterPublicStartStop#test_counts = 0.03 s = . > TestReporterPublicStartStop#test_nil_reporting_class = 0.02 s = . > TestReporterPublicStartStop#test_no_color_output = 0.02 s = . > TestReporterPublicStartStop#test_class_tracing_with_value = 0.02 s = . > TestReporterPublicStartStop#test_color_output_defaults_to_true_when_run_from_tty > = 0.02 s = . > TestReporterPublicStartStop#test_allow_files_with_string = 0.02 s = . > TestReporterPublicStartStop#test_basic_object = 0.02 s = . > TestReporterPublicStartStop#test_reports_can_be_reused_with_different_color_options > = 0.02 s = . > TestReporterPublicStartStop#test_non_string_named_class = 0.03 s = . > TestReporterPublicStartStop#test_class_tracing_with_array = 0.03 s = . > TestReporterPublicStartStop#test_color_output = 0.02 s = . > TestReporterPublicStartStop#test_exception_handling = 0.00 s = . > TestReporterPublicStartStop#test_allow_files_with_array = 0.02 s = . > TestReporterPublicStartStop#test_string_reporting_class = 0.02 s = . > TestReporterPrivateStartStop#test_color_output = 0.02 s = . > TestReporterPrivateStartStop#test_strings_report = 0.02 s = . > TestReporterPrivateStartStop#test_allow_files_with_string = 0.02 s = . > TestReporterPrivateStartStop#test_exception_handling = 0.00 s = . >
Bug#997145: marked as done (autoconf2.69: FTBFS: autoconf.texi:9: unknown command `setcontentsaftertitlepage')
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 that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997145
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: autoconf2.69
Version: 2.69-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering directory '/<>/doc'
> Updating ./version.texi
> restore=: && backupdir=".am$$" && \
> am__cwd=`pwd` && CDPATH="${ZSH_VERSION+.}:" && cd . && \
> rm -rf $backupdir && mkdir $backupdir && \
> if (/bin/bash /<>/build-aux/missing --run makeinfo --version)
> >/dev/null 2>&1; then \
> for f in autoconf.info autoconf.info-[0-9] autoconf.info-[0-9][0-9]
> autoconf.i[0-9] autoconf.i[0-9][0-9]; do \
> if test -f $f; then mv $f $backupdir; restore=mv; else :; fi; \
> done; \
> else :; fi && \
> cd "$am__cwd"; \
> if /bin/bash /<>/build-aux/missing --run makeinfo --no-split -I
> . \
> -o autoconf.info autoconf.texi; \
> then \
> rc=0; \
> CDPATH="${ZSH_VERSION+.}:" && cd .; \
> else \
> rc=$?; \
> CDPATH="${ZSH_VERSION+.}:" && cd . && \
> $restore $backupdir/* `echo "./autoconf.info" | sed 's|[^/]*$||'`; \
> fi; \
> rm -rf $backupdir; exit $rc
> autoconf.texi:9: unknown command `setcontentsaftertitlepage'
> make[3]: *** [Makefile:251: autoconf.info] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/autoconf2.69_2.69-3_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: autoconf2.69
Source-Version: 2.69-3.1
Done: Adrian Bunk
We believe that the bug you reported is fixed in the latest version of
autoconf2.69, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Adrian Bunk (supplier of updated autoconf2.69 package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 19 Nov 2022 21:40:11 +0200
Source: autoconf2.69
Architecture: source
Version: 2.69-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian GCC Maintainers
Changed-By: Adrian Bunk
Closes: 997145
Changes:
autoconf2.69 (2.69-3.1) unstable; urgency=medium
.
* Non-maintainer upload.
* Backport upstream fix for FTBFS with recent texinfo.
(Closes: #997145)
Checksums-Sha1:
d01f460bfe741c398a6f2034ee869ae67e7da67d 1802 autoconf2.69_2.69-3.1.dsc
e5a87ec221a900d4ef5bcbfddc0a483c634aa892 11124
autoconf2.69_2.69-3.1.debian.tar.xz
Checksums-Sha256:
226b5d3e8172f6a87400cab2df0e3a8484ef44f19c052cc4edbb778c7d45f43f 1802
autoconf2.69_2.69-3.1.dsc
fe908dbfc5669ff63fccefa9ec1affc11b6c07a6781028baee7ced77f4f0c2fb 11124
autoconf2.69_2.69-3.1.debian.tar.xz
Files:
89532f43d8c0459a407fb37747c20018 1802 devel optional autoconf2.69_2.69-3.1.dsc
debec2f575f264febc624bb88168ba8d 11124 devel optional
autoconf2.69_2.69-3.1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAmN5MrwACgkQiNJCh6LY
mLEXIxAAoV/uiWx0gUVHFiJ3O8fplFD2xIxrLmjp0gsgPyT/P3pHLM8gk7OCiR8C
yqLTes5sPIHmlhuqJ0F7Pxjy+F7TtUVYrxMrc9qF9Q/JY6aHJ6nsyEFQyG6Idgvl
ZrLxHpiwwWyT/dczvl7L9W4nje+aF3yTz9PL7T3xe3C7sVhw9hvTDqicRDFVTQP6
M3VOoIiY4DKRtK9cXgoTrOi6A4ndJnHNhBM2KlWLeSghPZ1yvxSgY7OI3LQB0GTU
1PxpV81ssnucuRAvme7jlF8a3NZXsDVdihcqD9kxKCTga2F8/pPlLcwgZr5NfH6D
rtvEG26tVzw9r09G/SxcpBqAWeqwUKO/3OetSD0YDCmQe3K5VBov/x3SONhHTw1Z
Processed: Re: Bug#1012382: pktanon: autopkgtest fails on s390x with: wrong pcap file version: should be 2.4
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 'https://github.com/KIT-Telematics/pktanon/issues/8'. > tags 1012382 upstream Bug #1012382 [src:pktanon] pktanon: autopkgtest fails on s390x with: wrong pcap file version: should be 2.4 Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 1012382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: golang-github-go-chef-chef: diff for NMU version 0.0.1+git20161023.60.deb8c38-1.2
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 ow...@bugs.debian.org with problems
Bug#848055: golang-github-go-chef-chef: diff for NMU version 0.0.1+git20161023.60.deb8c38-1.2
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 golang-github-go-chef-chef-0.0.1+git20161023.60.deb8c38/debian/changelog golang-github-go-chef-chef-0.0.1+git20161023.60.deb8c38/debian/changelog
--- golang-github-go-chef-chef-0.0.1+git20161023.60.deb8c38/debian/changelog 2021-01-09 17:26:27.0 +0200
+++ golang-github-go-chef-chef-0.0.1+git20161023.60.deb8c38/debian/changelog 2022-12-04 19:02:27.0 +0200
@@ -1,3 +1,10 @@
+golang-github-go-chef-chef (0.0.1+git20161023.60.deb8c38-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add upstream fix for intermittent test failures. (Closes: #848055)
+
+ -- Adrian Bunk Sun, 04 Dec 2022 19:02:27 +0200
+
golang-github-go-chef-chef (0.0.1+git20161023.60.deb8c38-1.1) unstable; urgency=medium
* Non maintainer upload by the Reproducible Builds team.
diff -Nru golang-github-go-chef-chef-0.0.1+git20161023.60.deb8c38/debian/patches/0001-Fix-the-intermittent-failures-in-the-String-tests.patch golang-github-go-chef-chef-0.0.1+git20161023.60.deb8c38/debian/patches/0001-Fix-the-intermittent-failures-in-the-String-tests.patch
--- golang-github-go-chef-chef-0.0.1+git20161023.60.deb8c38/debian/patches/0001-Fix-the-intermittent-failures-in-the-String-tests.patch 1970-01-01 02:00:00.0 +0200
+++ golang-github-go-chef-chef-0.0.1+git20161023.60.deb8c38/debian/patches/0001-Fix-the-intermittent-failures-in-the-String-tests.patch 2022-12-04 19:02:27.0 +0200
@@ -0,0 +1,107 @@
+From b8a5b9cbb7b472eba5c1e2759aa6c288b8251de1 Mon Sep 17 00:00:00 2001
+From: markgibbons
+Date: Sat, 7 Dec 2019 07:10:13 -0800
+Subject: Fix the intermittent failures in the String tests
+
+diff --git a/client_test.go b/client_test.go
+index ad7aff7..7daeeaf 100644
+--- a/client_test.go
b/client_test.go
+@@ -40,15 +40,17 @@ func TestClientsService_List(t *testing.T) {
+ mux.HandleFunc("/clients", func(w http.ResponseWriter, r *http.Request) {
+ fmt.Fprintf(w, `{"client1": "http://localhost/clients/client1;, "client2": "http://localhost/clients/client2"}`)
+ })
+-
+ response, err := client.Clients.List()
+ if err != nil {
+ t.Errorf("Clients.List returned error: %v", err)
+ }
+
++ // The order printed by the String function is not defined
+ want := "client1 => http://localhost/clients/client1\nclient2 => http://localhost/clients/client2\n;
+- if response.String() != want {
+- t.Errorf("Clients.List returned:\n%+v\nwant:\n%+v\n", response.String(), want)
++ want2 := "client2 => http://localhost/clients/client2\nclient1 => http://localhost/clients/client1\n;
++ rstr := response.String()
++ if rstr != want && rstr != want2 {
++ t.Errorf("Clients.List returned:\n%+v\nwant:\n%+v\n", rstr, want)
+ }
+ }
+
+diff --git a/databag_test.go b/databag_test.go
+index 5ea7514..071fc4b 100644
+--- a/databag_test.go
b/databag_test.go
+@@ -157,8 +157,11 @@ func TestDataBagsService_UpdateItem(t *testing.T) {
+
+ func TestDataBagsService_DataBagListResultString(t *testing.T) {
+ e := {"bag1": "http://localhost/data/bag1;, "bag2": "http://localhost/data/bag2"}
++ // The output order is not guarenteed by the String function, check for either order
+ want := "bag1 => http://localhost/data/bag1\nbag2 => http://localhost/data/bag2\n;
+- if e.String() != want {
+- t.Errorf("DataBagListResult.String returned:\n%+v\nwant:\n%+v\n", e.String(), want)
++ want2 := "bag2 => http://localhost/data/bag2\nbag1 => http://localhost/data/bag1\n;
++ ebag := e.String()
++ if ebag != want && ebag != want2 {
++ t.Errorf("DataBagListResult.String returned:\n%+v\nwant:\n%+v\n", ebag, want)
+ }
+ }
+diff --git a/environment_test.go b/environment_test.go
+index 1bb7470..ff1b37a 100644
+--- a/environment_test.go
b/environment_test.go
+@@ -143,16 +143,19 @@ func TestEnvironmentsService_Put(t *testing.T) {
+
+ func TestEnvironmentsService_EnvironmentListResultString(t *testing.T) {
+ e := {"_default": "https://api.opscode.com/organizations/org_name/environments/_default;, "webserver": "https://api.opscode.com/organizations/org_name/environments/webserver"}
++ estr := e.String()
+ want := "_default => https://api.opscode.com/organizations/org_name/environments/_default\nwebserver => https://api.opscode.com/organizations/org_name/environments/webserver\n;
+- if e.String() != want {
+- t.Errorf("EnvironmentResult.String returned:\n%+v\nwant:\n%+v\n", e.String(), want)
++ want2 := "webserver => https://api.opscode.com/organizations/org_name/environments/webserver\n_default => https://api.opscode.com/organizations/org_name/environments/_default\n;
++ if estr != want && estr != want2 {
++ t.Errorf("EnvironmentResult.String returned:\n%+v\nwant:\n%+v\n", estr, want)
+ }
+ }
+
+ func TestEnvironmentsService_EnvironmentCreateResultString(t *testing.T) {
+ e := {"uri":
Processed: tagging 1022343
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 contact me if you need assistance.
--
1022343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#932345: marked as done (profile-sync-daemon: Debian specific error "I require modinfo but it's not installed")
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. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 932345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932345 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: profile-sync-daemon Version: 6.34-1 Severity: normal Dear Maintainer, In in debian modinfo is located: [/usr]/sbin/modinfo Workaround: change 'modinfo ...' to '/sbin/modinfo ...' in /usr/bin/profile-sync-daemon -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable'), (90, 'unstable'), (70, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages profile-sync-daemon depends on: ii init-system-helpers 1.56+nmu1 ii rsync3.1.3-6 profile-sync-daemon recommends no packages. Versions of packages profile-sync-daemon suggests: ii libpam-systemd 241-5 ii systemd-sysv241-5 -- no debconf information --- End Message --- --- Begin Message --- Source: profile-sync-daemon Source-Version: 6.34-1.2 Done: Shengjing Zhu We believe that the bug you reported is fixed in the latest version of profile-sync-daemon, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 932...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Shengjing Zhu (supplier of updated profile-sync-daemon package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 29 Nov 2022 23:45:53 +0800 Source: profile-sync-daemon Architecture: source Version: 6.34-1.2 Distribution: unstable Urgency: medium Maintainer: Jan Luca Naumann Changed-By: Shengjing Zhu Closes: 932345 Changes: profile-sync-daemon (6.34-1.2) unstable; urgency=medium . * Non-maintainer upload. * Add /sbin to PATH. (Closes: #932345) Checksums-Sha1: d3e1d118424a1adc23d7b2e81d30e787d8271045 1379 profile-sync-daemon_6.34-1.2.dsc d739a68e97eaff7b030b99eb24933bee416a6416 3024 profile-sync-daemon_6.34-1.2.debian.tar.xz 4c7243142b09c07f3803cf14bab08f1126b76bb9 profile-sync-daemon_6.34-1.2_amd64.buildinfo Checksums-Sha256: 382f3a5e01583f9131ff591b087d740f410336496dbd2e9bda2ac7a89522a965 1379 profile-sync-daemon_6.34-1.2.dsc 4c49708e2055ae32ea1ffb9654794d05f40f610d633fad1e32b1f8b727066c98 3024 profile-sync-daemon_6.34-1.2.debian.tar.xz ce5e7fe10733dd0a8e2a7462312d7053bbb2d02a60dab5521fac41a07bff66e8 profile-sync-daemon_6.34-1.2_amd64.buildinfo Files: cdddb19d035bb025d3d18fb1b973c30d 1379 utils optional profile-sync-daemon_6.34-1.2.dsc cba473f1e00e67fb96003b89df41de9d 3024 utils optional profile-sync-daemon_6.34-1.2.debian.tar.xz 3571b5b2d32b5eb08ae4da9889b830ad utils optional profile-sync-daemon_6.34-1.2_amd64.buildinfo -BEGIN PGP SIGNATURE- iIYEARYIAC4WIQSRhdT1d2eu7mxV1B5/RPol6lUUywUCY4Yp1hAcemhzakBkZWJp YW4ub3JnAAoJEH9E+iXqVRTLTCkBAMNXW2Q/bdbtoNk1C60EnUuuIngXZz/WYuj/ vKcU00CFAQCE5jN2U1O4wLaB9+E2CUx70x4BE4PVmGArICas6rEMAg== =QeD8 -END PGP SIGNATURE End Message ---
Bug#1023330: marked as done (ghostscript 10.0.0~dfsg-6: x11 support missing, thus 'gv 1:3.7.4-2+b1' is failing)
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 means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1023330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023330 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ghostscript Version: 10.0.0~dfsg-6 Severity: important Dear Maintainer, after upgrade to ghostscript 10, gv (ghostview) is no longer able to render PostScript files, due to missing support for the 'x11' device. Compiling ghostscript-10.0.0.tar.gz from upstream has resolved the problem. ghostscript support for the x11 device seems to be mandatory for 'gv'. Thanks - Jakob. -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'testing'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-2-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ghostscript depends on: ii libc62.35-4 ii libgs10 10.0.0~dfsg-6 ghostscript recommends no packages. Versions of packages ghostscript suggests: ii ghostscript-x 10.0.0~dfsg-6 -- no debconf information --- End Message --- --- Begin Message --- Source: ghostscript Source-Version: 10.0.0~dfsg-8 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of ghostscript, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1023...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated ghostscript package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 04 Dec 2022 16:00:05 +0100 Source: ghostscript Architecture: source Version: 10.0.0~dfsg-8 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sebastian Ramacher Closes: 1023330 Changes: ghostscript (10.0.0~dfsg-8) unstable; urgency=medium . * QA upload * debian/: No longer build with dynamic modules (Closes: #1023330) - X11 support is now part of ghostscript and ghostcript-x is a transitional package. Checksums-Sha1: 104ed979acbd3133b0da4866f525ae7008dc15b7 2757 ghostscript_10.0.0~dfsg-8.dsc 13a9beb22d2e2a5c6fb7d5d474868a6363a4275e 83704 ghostscript_10.0.0~dfsg-8.debian.tar.xz Checksums-Sha256: 595b0898ea921605c77e2513218b58afb9759c257c37383749d1ee04ee113645 2757 ghostscript_10.0.0~dfsg-8.dsc ed432b5b782303d1d45dde430f62e64cf4b8038ded77c7ab40c5a16f07ebeecf 83704 ghostscript_10.0.0~dfsg-8.debian.tar.xz Files: bbb697f687001a070a7d69cc4deac4b5 2757 text optional ghostscript_10.0.0~dfsg-8.dsc f7c67c171ee0c6adec5a547c52640494 83704 text optional ghostscript_10.0.0~dfsg-8.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAmOMuRwACgkQafL8UW6n GZN1DxAAqXY9rfqRrTAplxzzC7yocH1yQz1mJCFTbpaXdS4pEkH8RfMh4Ra0gizf U1RjoWTULy6/cFRmkSYfnq2JdAluxKw9HWaavA2kpfHnZti1Vpd5RaBFb75UOShO sUNV94fDkBm11JfRgUcfn6v1NG80OtF6Sdtw0yUDBvBJNcdWvENfBlCKq/E2Ob9Q Brho6dvKi8HAAw6CyNkZAqUXbTEDFvU49+1Fo/xuNFzrdWGoo0IgxF/1qpNWyDBt hNjmK5qHGXRoMkrLnnA1xMsN8jizig5TVztsqTq/JZRhXxO42D5N+kJbe5MyPPCQ zpkZnRV99w35JaczPm/V0HAJL1zpUBkklbRjUOQS2EYXbUDNMuQIpaxje3udpq1V G6QIPt0i5ouDqVrqnEkBqwgKCb69mX32uPUngOy8UMnk/DM8KyaevP3Gyti20Xmw 30818rrX9GMUapuSA9bBdyKCkIBzwJ7p6RfGsNGe7D25ZPRSzONI2YpLfxqEhYNy A9jcG09q3yB8NU7a0DNwfD5P5gX8zfpJku7A0nr4vG9UFD5u6V3tb0DWX1ckKoyU 0MpIxcL0zr1OX2QT6pnUvnNgHUiW4HvS/88Gi/lH2nd3Kx0zbJe5glxkhp1T54Dq LatnmtA4Kck7cthBM5/7DD4Wkt1WMh8aT+h2Pp8L99emSUT6yFc= =kjVX -END PGP SIGNATURE End Message ---
Processed: reassign 1024318 to ghostscript, severity of 1023330 is grave, forcibly merging 1023330 1024318
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 #1024318 to the same values previously set Bug #1024318 [ghostscript] gv: x11 output driver not found Marked as found in versions ghostscript/10.0.0~dfsg-6. > severity 1023330 grave Bug #1023330 [ghostscript] ghostscript 10.0.0~dfsg-6: x11 support missing, thus 'gv 1:3.7.4-2+b1' is failing Severity set to 'grave' from 'important' > forcemerge 1023330 1024318 Bug #1023330 [ghostscript] ghostscript 10.0.0~dfsg-6: x11 support missing, thus 'gv 1:3.7.4-2+b1' is failing Bug #1023330 [ghostscript] ghostscript 10.0.0~dfsg-6: x11 support missing, thus 'gv 1:3.7.4-2+b1' is failing Added tag(s) sid and bookworm. Bug #1024318 [ghostscript] gv: x11 output driver not found Merged 1023330 1024318 > thanks Stopping processing here. Please contact me if you need assistance. -- 1023330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023330 1024318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1024327, tagging 1024318
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. Please contact me if you need assistance. -- 1024318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024318 1024327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024327 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025296: closing 1025296
close 1025296 thanks clementine was part of the protobuf transition. A binNMU fixed this issue. Cheers
Processed: closing 1025296
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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025296 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1024987 to java-wrappers, forcibly merging 1024453 1024987, affects 1024453
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 versions of bug #1024987 to the same values previously set Bug #1024987 [java-wrappers] sweethome3d: Fail to start Marked as found in versions java-wrappers/0.3. > forcemerge 1024453 1024987 Bug #1024453 [java-wrappers] mediathek: fails to start with openjdk 17 Bug #1024987 [java-wrappers] sweethome3d: Fail to start Added indication that 1024987 affects mediathekview Added tag(s) bookworm and sid. Merged 1024453 1024987 > affects 1024453 sweethome3d Bug #1024453 [java-wrappers] mediathek: fails to start with openjdk 17 Bug #1024987 [java-wrappers] sweethome3d: Fail to start Added indication that 1024453 affects sweethome3d Added indication that 1024987 affects sweethome3d > thanks Stopping processing here. Please contact me if you need assistance. -- 1024453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024453 1024987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024987 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1024453
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: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024453 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 1011567 with 1012103
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: 1012103 > thanks Stopping processing here. Please contact me if you need assistance. -- 1011567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011567 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1025308: gsequencer: FTBFS with fftw3 (3.3.10-1)
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 attached. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 diff -Nru gsequencer-4.4.1/debian/changelog gsequencer-4.4.1/debian/changelog --- gsequencer-4.4.1/debian/changelog 2022-09-16 05:57:45.0 +0200 +++ gsequencer-4.4.1/debian/changelog 2022-12-02 12:21:38.0 +0100 @@ -1,3 +1,11 @@ +gsequencer (4.4.1-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Build depend on libfftw3-dev, fftw3-dev no longer provided. + * Set LIBGL_ALWAYS_SOFTWARE=1 for xvfb-run to work around #1025312. + + -- Bas Couwenberg Fri, 02 Dec 2022 12:21:38 +0100 + gsequencer (4.4.1-1) unstable; urgency=medium * New upstream version 4.4.1 diff -Nru gsequencer-4.4.1/debian/control gsequencer-4.4.1/debian/control --- gsequencer-4.4.1/debian/control 2022-09-16 05:57:45.0 +0200 +++ gsequencer-4.4.1/debian/control 2022-12-02 12:21:38.0 +0100 @@ -10,7 +10,7 @@ docbook-xml, docbook-xsl, dssi-dev, - fftw3-dev, + libfftw3-dev, fop, gettext, gstreamer1.0-plugins-bad, diff -Nru gsequencer-4.4.1/debian/rules gsequencer-4.4.1/debian/rules --- gsequencer-4.4.1/debian/rules 2022-09-16 05:57:45.0 +0200 +++ gsequencer-4.4.1/debian/rules 2022-12-02 12:21:38.0 +0100 @@ -43,7 +43,7 @@ $(MAKE) DESTDIR=$$(pwd)/debian/tmp pdf override_dh_auto_test: - xvfb-run --server-args="-screen 0 1920x1080x24" -a dh_auto_test + LIBGL_ALWAYS_SOFTWARE=1 xvfb-run --server-args="-screen 0 1920x1080x24" -a dh_auto_test override_dh_auto_install: dh_auto_install --no-parallel
Bug#1025315: marked as done (pyxplot: FTBFS with fftw3 (3.3.10-1))
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 with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1025315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025315 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pyxplot Version: 0.9.2-12 Severity: serious Tags: ftbfs patch Dear Maintainer, Your package FTBFS with fftw3 (3.3.10-1) because it not longer provides fftw3-dev. The attached patch resolves the issue by changing the dependency to libfftw3-dev. Kind Regards, Bas diff -Nru pyxplot-0.9.2/debian/changelog pyxplot-0.9.2/debian/changelog --- pyxplot-0.9.2/debian/changelog 2020-12-28 08:42:15.0 +0100 +++ pyxplot-0.9.2/debian/changelog 2022-12-02 13:29:47.0 +0100 @@ -1,3 +1,10 @@ +pyxplot (0.9.2-12.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Build depend on libfftw3-dev, fftw3-dev no longer provided. + + -- Bas Couwenberg Fri, 02 Dec 2022 13:29:47 +0100 + pyxplot (0.9.2-12) unstable; urgency=medium * Update Standards-Version to 4.5.1 (no changes required). diff -Nru pyxplot-0.9.2/debian/control pyxplot-0.9.2/debian/control --- pyxplot-0.9.2/debian/control2020-12-28 08:42:15.0 +0100 +++ pyxplot-0.9.2/debian/control2022-12-02 13:29:45.0 +0100 @@ -4,7 +4,7 @@ Section: math Build-Depends: debhelper-compat (= 13), - fftw3-dev, + libfftw3-dev, ghostscript, imagemagick, libcfitsio-dev, --- End Message --- --- Begin Message --- Source: pyxplot Source-Version: 0.9.2-13 Done: Stuart Prescott We believe that the bug you reported is fixed in the latest version of pyxplot, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stuart Prescott (supplier of updated pyxplot package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 04 Dec 2022 22:00:26 +1100 Source: pyxplot Architecture: source Version: 0.9.2-13 Distribution: unstable Urgency: medium Maintainer: Stuart Prescott Changed-By: Stuart Prescott Closes: 1025315 Changes: pyxplot (0.9.2-13) unstable; urgency=medium . [ Bas Couwenberg ] * Build depend on libfftw3-dev, fftw3-dev no longer provided, with thanks to Bas Couwenberg for the patch (Closes: #1025315). . [ Debian Janitor ] * Remove constraints unnecessary since buster . [ Stuart Prescott ] * Update Standards-Version to 4.6.1 (no changes required). * Add lots of lintian overrides to improve the signal:noise. Checksums-Sha1: c7075845e5ac8b3e3bfcf63e555c960e02c43a9b 2297 pyxplot_0.9.2-13.dsc aac0c961c8a7acb75cde3cf10a7a728968042281 96332 pyxplot_0.9.2-13.debian.tar.xz 83fce1825abb3b853273c078250ed78e84aecd12 11166 pyxplot_0.9.2-13_amd64.buildinfo Checksums-Sha256: 1b0bef0a4acbfa2b67d9625c5dff7b8a5986c8b1ef92eafd717cc39c528a9504 2297 pyxplot_0.9.2-13.dsc bb17a5d89512b28d5296b9587a1e05c7141833249ac2fb46e46b1d76c7ebc909 96332 pyxplot_0.9.2-13.debian.tar.xz cf281ab68949b0623bbadc40d7d0949e2875103464d803030e666be500c9546e 11166 pyxplot_0.9.2-13_amd64.buildinfo Files: 05239f70223d16d2f269b9d83ebc0ae5 2297 math optional pyxplot_0.9.2-13.dsc 719017376607dcea4b8eed401fbc5e26 96332 math optional pyxplot_0.9.2-13.debian.tar.xz 9f02f2edc3692b0714ef5a7db49e88a3 11166 math optional pyxplot_0.9.2-13_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkOLSwa0Uaht+u4kdu8F+uxOW8vcFAmOMgt4ACgkQu8F+uxOW 8vdnMw/6A3wQ4ogog/4wuS4rD6ulsDh5kGgvvrTVjLqzhDdjpU0W7tWRkuGg217I NY/FAJjwSTjYTmzcR9vuiaHB1mluEP9cD8TnyqbJ7X4JvyensMe8EitprRq5d5ij GZ0jEF+8E4pLUftUIz3SEbLUJqS9oKZ9+iIZq//+qjLt86lBiYzmT71TjAPlamWf gDr3LxT+Kg3zBcpnlMd7S+qRv3whEH0K1A7MMvdKZnwAPOD6+/fkZJiXKFlwDaOm IGuLe+thXSq4hE7wasQRlEYsem2JN6/48gSRoZeHthSp4+pcmn4xNVJjbdAqYfsz xkSSZlkVyoQ3LX9jodbrDkutll/O5medWMUuBdzpog4UUmn/6PX+r+aUX4UlEnsQ r56FdNK2Rjr5JdQuF5iqSbDZaDEmPvXpaCL8U6AQ9nAvhnq8iiVyGb4gvQnY1cRk /xKmhg8KRz8zIClnKzWB/KVyrkE5rUCz179Wr5HCIljbGGqgO9nCTO6L7sOAKOXP
Bug#938322: fixed in qtwebengine-opensource-src 5.15.11+dfsg-1
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 Arch Linux but using versioned > > python3. > > - Add chromium-python3.patch, copied from Arch Linux. > > This is now literally the last package that has build depends on python2 in > bookworm. > Is there a chance to move the experimental package to sid soon? Done! It requires binNMU of two reverse deps, that is tracked in #1025055. -- Dmitry Shachnev signature.asc Description: PGP signature
Processed: Re: Bug#1023156: haskell-gi-gtk FTBFS on armel
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 problems
Bug#1023156: haskell-gi-gtk FTBFS on armel
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 the removal of haskell-gi-gtk and reverse dependencies > > on armel. > > I think that's probably a good plan. I believe I may have reported this bug > (or one similar to it) to ghc, but it didn't sound like it was something > that was going to fixed quickly/easily. I requested the removal of haskell-gi-gtk on armel. https://bugs.debian.org/1025412 -- Ilias
Bug#1025366: Note that the bug is also present in 7.0.2
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
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 RuntimeError: Could not find fapi config at ['/etc/tpm2-tss/fapi-config.json', '/usr/local/etc/tpm2-tss/fapi-config.json'], set env var TSS2_FAPICONF G. OpenPGP_signature Description: OpenPGP digital signature
Bug#1025408: python-certbot-dns-standalone: FTBFS (Depending on old python3-acme-abi-1)
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: extracting python-certbot-dns-standalone in python-certbot-dns-standalone-1.0.3 dpkg-source: info: unpacking python-certbot-dns-standalone_1.0.3.orig.tar.gz dpkg-source: info: unpacking python-certbot-dns-standalone_1.0.3-2.debian.tar.xz I: Not using root during the build. I: Installing the build-deps -> Attempting to parse the build-deps -> Considering build-depdebhelper-compat (= 13) -> Trying to add debhelper-compat=13 -> Considering build-dep dh-python -> Trying to add dh-python -> Considering build-dep python3 -> Trying to add python3 -> Considering build-dep python3-setuptools -> Trying to add python3-setuptools -> Considering build-dep python3-acme-abi-1 -> Trying to add python3-acme-abi-1 -> Loop detected, last APT error was: == Reading package lists... Building dependency tree... Reading state information... Package python3-acme-abi-1 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'python3-acme-abi-1' has no installation candidate -> = -> (not adding to python3-acme-abi-1) -> Cannot install python3-acme-abi-1; apt errors follow: Reading package lists... Building dependency tree... Reading state information... Package python3-acme-abi-1 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'python3-acme-abi-1' has no installation candidate OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: tpm2-pytss: FTBFS in sid
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
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 tpm2-pytss-1.2.0/debian/changelog
--- tpm2-pytss-1.2.0/debian/changelog 2022-10-21 11:37:20.0 +
+++ tpm2-pytss-1.2.0/debian/changelog 2022-12-04 08:37:49.0 +
@@ -1,3 +1,10 @@
+tpm2-pytss (1.2.0-2.1) unstable; urgency=medium
+
+ * Depend on libpython3-all-dev to make it build with non-default
+Python3 versions (Closes: #1025406)
+
+ -- Gianfranco Costamagna Sun, 04 Dec 2022
09:37:49 +0100
+
tpm2-pytss (1.2.0-2) unstable; urgency=high
* Team upload
diff -Nru tpm2-pytss-1.2.0/debian/control tpm2-pytss-1.2.0/debian/control
--- tpm2-pytss-1.2.0/debian/control 2022-10-21 10:30:41.0 +
+++ tpm2-pytss-1.2.0/debian/control 2022-12-04 08:37:48.0 +
@@ -12,7 +12,7 @@
python3-asn1crypto,
python3-cffi (>= 1.0.0),
python3-cryptography (>= 3.0),
- python3-dev,
+ python3-all-dev,
python3-doc,
python3-myst-parser,
python3-pkgconfig,
G.
On Sun, 4 Dec 2022 09:09:54 +0100 Gianfranco Costamagna
wrote:
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 2022
I: pbuilder-time-stamp: 1670141169
I: Building the build Environment
I: extracting base tarball [/home/locutus/pbuilder/sid-base.tgz]
I: copying local configuration
W: No local /etc/mailname to copy, relying on /tmp/build/209176/etc/mailname to
be correct
W: --override-config is not set; not updating apt.conf Read the manpage for
details.
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [tpm2-pytss_1.2.0-2.dsc]
I: copying [./tpm2-pytss_1.2.0.orig.tar.gz]
I: copying [./tpm2-pytss_1.2.0-2.debian.tar.xz]
I: Extracting source
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/tmp/dpkg-gpg-verify.AFKkmrLk/trustedkeys.kbx':
General error
gpgv: Signature made Fri Oct 21 11:38:32 2022 UTC
gpgv:using RSA key 406220C8B8552802378CCE411F5C7A8B45564314
gpgv:issuer "b...@debian.org"
gpgv: Can't check signature: No public key
dpkg-source: warning: cannot verify inline signature for
./tpm2-pytss_1.2.0-2.dsc: no acceptable signature found
dpkg-source: info: extracting tpm2-pytss in tpm2-pytss-1.2.0
dpkg-source: info: unpacking tpm2-pytss_1.2.0.orig.tar.gz
dpkg-source: info: unpacking tpm2-pytss_1.2.0-2.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying
debian-hacks/docs-Use-internal-ressources-for-intersphinx.patch
I: Not using root during the build.
I: Installing the build-deps
-> Attempting to parse the build-deps
-> Considering build-depdebhelper-compat (= 13)
-> Trying to add debhelper-compat=13
-> Considering build-dep dh-sequence-python3
-> Trying to add dh-sequence-python3
-> Considering build-dep libtss2-dev
-> Trying to add libtss2-dev
-> Considering build-dep pybuild-plugin-pyproject
-> Trying to add pybuild-plugin-pyproject
-> Considering build-dep python3-all:any
-> Trying to add python3-all:any
-> Considering build-dep python3-asn1crypto
-> Trying to add python3-asn1crypto
-> Considering build-dep python3-cffi (>= 1.0.0)
-> Trying to add python3-cffi
-> Considering build-dep python3-cryptography (>= 3.0)
OpenPGP_signature
Description: OpenPGP digital signature
Bug#1024154: marked as done (llvm-toolchain-14: FTBFS: testsuite hangs on i386, x32)
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 the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1024154: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1024154 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: llvm-toolchain-14 Version: 1:14.0.6-8 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, llvm-toolchain-14 recently started to fail to build on i386 and x32: the build gets killed after 150 minutes of inactivity while running the testsuite. This does not seem to be a flaky test, but happenes every time. https://buildd.debian.org/status/logs.php?pkg=llvm-toolchain-14=i386 What's interesting is that the buildds report nearly twice as much disk usage (8.69 GB) for the failed builds than for previous succeeding builds (4.44 GB). Andreas --- End Message --- --- Begin Message --- Source: llvm-toolchain-14 Source-Version: 1:14.0.6-9 Done: Gianfranco Costamagna We believe that the bug you reported is fixed in the latest version of llvm-toolchain-14, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1024...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Gianfranco Costamagna (supplier of updated llvm-toolchain-14 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 04 Dec 2022 09:03:06 +0100 Source: llvm-toolchain-14 Built-For-Profiles: noudeb Architecture: source Version: 1:14.0.6-9 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Gianfranco Costamagna Closes: 1024154 1025394 Changes: llvm-toolchain-14 (1:14.0.6-9) unstable; urgency=medium . * Cherry-pick upstream commit c081bf4098c729afacf20303cc9df62bf13c3362 to fix chromium failure in basic_string (Closes: #1025394) * Disable the MLIR testsuite run because of a freeze (Closes: #1024154) See https://github.com/llvm/llvm-project/issues/58357 * Disable wasm on riscv64 Checksums-Sha1: 52cbab955d3cb870193e46ace769e10872260ea7 7208 llvm-toolchain-14_14.0.6-9.dsc 18d14faf33aa3814fbe53c833d4bbc3edb50e14f 156272 llvm-toolchain-14_14.0.6-9.debian.tar.xz 094601d998a7215d5385b40df41aa62acd0df429 11938 llvm-toolchain-14_14.0.6-9_source.buildinfo Checksums-Sha256: 7c7721da865ba934374015108856e919e893ce3bc8e5090541c091f2b015b27d 7208 llvm-toolchain-14_14.0.6-9.dsc 878dfd1ab373a2f5da7a89e27e3b92de69a808cfac4aae27f7c13532b179f17e 156272 llvm-toolchain-14_14.0.6-9.debian.tar.xz a623befeb33e864de940920671dd4a9dea913f4719fe5b63216814f133bf754f 11938 llvm-toolchain-14_14.0.6-9_source.buildinfo Files: 8f0bf16c11a90cf4027a807278e4856e 7208 devel optional llvm-toolchain-14_14.0.6-9.dsc 60d915f5178b7570a22dff62e7ccb6b3 156272 devel optional llvm-toolchain-14_14.0.6-9.debian.tar.xz d7df3ab01b199820e16469b0f5a5968f 11938 devel optional llvm-toolchain-14_14.0.6-9_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmOMVgYACgkQ808JdE6f XdmVFg/9FcYdpsg0JO2hdZwqsTnEbIDLev6dYby6JlmzqXwkmXjQX1zvLVA5axR5 VLLHq5Kbf4UoH220nTxfKcWesl++5+N9cQpvYTq3cqClSitlr/gD3OVEMGEEAWHS fVRLN+EhpjAjC/C1e0VkklJ7m1e5M7RF97KX8f4QZNbc0jZvPjVsMum2i2XruBSR mWzb9KvxicaJI6Tqh+aEikHB4CUUMg9/X58RF9CWKKCYRxEMHAcsY3Wu0mRbnxh6 ocfvoHDnK8EBKGRzgn68VOQyS8ikIWFJTYvZHXsvmtvZ7+ON4GeW/o5yzYZmBvlP 8FQIMnRLM2wCDX5wVqUxaV29OYJ53KR3JvpQFZRI/v3UQkZ4qR3NrvL8snle6nHh KvC0e1jgDdwhX9CKtA5xAIGVIklmdzl+K4HC7Rm/5d0Fhta8W0H/PC61K+N6hbqH n3nN4Mepv47hUGzz7OqpgtfmJSCI0iPpYQBerNbB1lRgF3uDNlxeRjKelUWc/1uh 1KRihp4Z90dtT95Hs0LBvEtbvq8AtKMNc4A44x1+pzvHB5z8czE7VLPFlz0IQBV4 eoqzpv/nbvGhKTfDOLRruVQCHEpWLV8AeelNhKACMuNlU9+kcx3XjiZCUtekjhVd N7dAPXwxhnDr6vGKATnDF0M5ZEw4n05qMdtVOioUgu7HGEGOtTM= =ZG7N -END PGP SIGNATURE End Message ---
Bug#1025406: tpm2-pytss: FTBFS in sid
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 2022
I: pbuilder-time-stamp: 1670141169
I: Building the build Environment
I: extracting base tarball [/home/locutus/pbuilder/sid-base.tgz]
I: copying local configuration
W: No local /etc/mailname to copy, relying on /tmp/build/209176/etc/mailname to
be correct
W: --override-config is not set; not updating apt.conf Read the manpage for
details.
I: mounting /proc filesystem
I: mounting /sys filesystem
I: creating /{dev,run}/shm
I: mounting /dev/pts filesystem
I: redirecting /dev/ptmx to /dev/pts/ptmx
I: policy-rc.d already exists
I: Obtaining the cached apt archive contents
I: Copying source file
I: copying [tpm2-pytss_1.2.0-2.dsc]
I: copying [./tpm2-pytss_1.2.0.orig.tar.gz]
I: copying [./tpm2-pytss_1.2.0-2.debian.tar.xz]
I: Extracting source
gpgv: unknown type of key resource 'trustedkeys.kbx'
gpgv: keyblock resource '/tmp/dpkg-gpg-verify.AFKkmrLk/trustedkeys.kbx':
General error
gpgv: Signature made Fri Oct 21 11:38:32 2022 UTC
gpgv:using RSA key 406220C8B8552802378CCE411F5C7A8B45564314
gpgv:issuer "b...@debian.org"
gpgv: Can't check signature: No public key
dpkg-source: warning: cannot verify inline signature for
./tpm2-pytss_1.2.0-2.dsc: no acceptable signature found
dpkg-source: info: extracting tpm2-pytss in tpm2-pytss-1.2.0
dpkg-source: info: unpacking tpm2-pytss_1.2.0.orig.tar.gz
dpkg-source: info: unpacking tpm2-pytss_1.2.0-2.debian.tar.xz
dpkg-source: info: using patch list from debian/patches/series
dpkg-source: info: applying
debian-hacks/docs-Use-internal-ressources-for-intersphinx.patch
I: Not using root during the build.
I: Installing the build-deps
-> Attempting to parse the build-deps
-> Considering build-depdebhelper-compat (= 13)
-> Trying to add debhelper-compat=13
-> Considering build-dep dh-sequence-python3
-> Trying to add dh-sequence-python3
-> Considering build-dep libtss2-dev
-> Trying to add libtss2-dev
-> Considering build-dep pybuild-plugin-pyproject
-> Trying to add pybuild-plugin-pyproject
-> Considering build-dep python3-all:any
-> Trying to add python3-all:any
-> Considering build-dep python3-asn1crypto
-> Trying to add python3-asn1crypto
-> Considering build-dep python3-cffi (>= 1.0.0)
-> Trying to add python3-cffi
-> Considering build-dep python3-cryptography (>= 3.0)
-> Trying to add python3-cryptography
-> Considering build-dep python3-dev
-> Trying to add python3-dev
-> Considering build-dep python3-doc
-> Trying to add python3-doc
-> Considering build-dep python3-myst-parser
-> Trying to add python3-myst-parser
-> Considering build-dep python3-pkgconfig
-> Trying to add python3-pkgconfig
-> Considering build-dep python3-pytest
-> Trying to add python3-pytest
-> Considering build-dep python3-pytest-cov
-> Trying to add python3-pytest-cov
-> Considering build-dep python3-pytest-forked
-> Trying to add python3-pytest-forked
-> Considering build-dep python3-pytest-xdist
-> Trying to add python3-pytest-xdist
-> Considering build-dep python3-setuptools
-> Trying to add python3-setuptools
-> Considering build-dep python3-setuptools-scm
-> Trying to add python3-setuptools-scm
-> Considering build-dep python3-sphinx
-> Trying to add python3-sphinx
-> Considering build-dep python3-sphinx-rtd-theme
-> Trying to add python3-sphinx-rtd-theme
-> Considering build-dep swtpm
-> Trying to add swtpm
-> Installing debhelper-compat=13 dh-sequence-python3 libtss2-dev
pybuild-plugin-pyproject python3-all:any python3-asn1crypto python3-cffi
python3-cryptography python3-dev python3-doc python3-myst-parser python3-pkgconfig
python3-pytest python3-pytest-cov python3-pytest-forked python3-pytest-xdist
python3-setuptools python3-setuptools-scm python3-sphinx python3-sphinx-rtd-theme
swtpm
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
adduser autoconf automake autopoint autotools-dev bsdextrautils
ca-certificates dh-autoreconf dh-strip-nondeterminism docutils-common dwz
file fonts-font-awesome fonts-lato gettext gettext-base groff-base
intltool-debian libarchive-zip-perl libbrotli1 libcurl4 libcurl4-openssl-dev
libdebhelper-perl libelf1 libexpat1 libexpat1-dev
libfile-stripnondeterminism-perl libglib2.0-0 libicu72 libjs-jquery
libjs-jquery-hotkeys libjs-jquery-isonscreen libjs-jquery-metadata
libjs-jquery-tablesorter libjs-jquery-throttle-debounce libjs-sphinxdoc
libjs-underscore libjson-c-dev libjson-c5 libjson-perl libkmod2
libldap-2.5-0 libmagic-mgc libmagic1 libmpdec3 libncursesw6 libnghttp2-14
libpipeline1 libpkgconf3 libpsl5 libpython3-dev libpython3-stdlib
Bug#1023978: scikit-learn: FTBFS with Python 3.11 as a supported version
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 upstream has some commits adding 3.11 support, but none of them seem like they would fix the build failure. Looking at the changes to the file with the failing test I found the commit above and then confirmed that this hunk from it fixes the build. --- a/sklearn/datasets/tests/test_lfw.py +++ b/sklearn/datasets/tests/test_lfw.py @@ -84,8 +84,8 @@ def setup_module(): for i in range(5): first_name, second_name = random_state.sample(FAKE_NAMES, 2) -first_index = random_state.choice(np.arange(counts[first_name])) -second_index = random_state.choice(np.arange(counts[second_name])) +first_index = np_rng.choice(np.arange(counts[first_name])) +second_index = np_rng.choice(np.arange(counts[second_name])) f.write( ( "%s\t%d\t%s\t%d\n" -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed: Re: scikit-learn: FTBFS with Python 3.11 as a supported version
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 > https://github.com/scikit-learn/scikit-learn/commit/63f92d4adb61aed58d656544cc6caa9d68cb6065 Bug #1023978 [src:scikit-learn] scikit-learn: FTBFS with Python 3.11 as a supported version Set Bug forwarded-to-address to 'https://github.com/scikit-learn/scikit-learn/commit/63f92d4adb61aed58d656544cc6caa9d68cb6065'. -- 1023978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023978 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
