Bug#996305: marked as pending in ruby-json
Control: tag -1 pending Hello, Bug #996305 in ruby-json 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-json/-/commit/578dd65b8d2796435b047595560ddef24d29c53f d/ruby-tests.rake: Add required include dirs and option to run tests on Ruby 3.0. Closes: #996305 (this message was generated automatically) -- Greetings https://bugs.debian.org/996305
Processed: Bug#996305 marked as pending in ruby-json
Processing control commands:
> tag -1 pending
Bug #996305 {Done: Sergio Durigan Junior } [src:ruby-json]
ruby-json: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: NoMethodError:
undefined method `assert_separately'
Added tag(s) pending.
--
996305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#996305: marked as done (ruby-json: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: NoMethodError: undefined method `assert_separately')
Your message dated Sat, 30 Oct 2021 05:18:41 +
with message-id
and subject line Bug#996305: fixed in ruby-json 2.5.1+dfsg-2
has caused the Debian Bug report #996305,
regarding ruby-json: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:
NoMethodError: undefined method `assert_separately'
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.)
--
996305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-json
Version: 2.5.1+dfsg-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-json was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> Did you mean? assert_empty>, @method_name="test_generate">],
> @stop_tag=#, @failures=[],
> @errors=[# @test_name="test_generate(JSONInRactorTest)", @exception=# undefined method `assert_separately' for
> #
> Did you mean? assert_empty>, @method_name="test_generate">], @pendings=[],
> @omissions=[], @notifications=[],
> @channels={"Test::Unit::TestResult::FINISHED"=>{# @a_proc=# /usr/share/rubygems-integration/all/gems/test-unit-3.3.9/lib/test/unit/ui/testrunnermediator.rb:88>,
> @hash=94281040049560>=># /usr/share/rubygems-integration/all/gems/test-unit-3.3.9/lib/test/unit/ui/testrunnermediator.rb:88>},
>
> "Test::Unit::TestResult::CHANGED"=>{# @a_proc=# /usr/share/rubygems-integration/all/gems/test-unit-3.3.9/lib/test/unit/ui/testrunnermediator.rb:91>,
> @hash=94281040048400>=># /usr/share/rubygems-integration/all/gems/test-unit-3.3.9/lib/test/unit/ui/testrunnermediator.rb:91>},
>
> "Test::Unit::TestResult::PASS_ASSERTION"=>{# @a_proc=# /usr/share/rubygems-integration/all/gems/test-unit-3.3.9/lib/test/unit/ui/testrunnermediator.rb:94>,
> @hash=94281040047360>=># /usr/share/rubygems-integration/all/gems/test-unit-3.3.9/lib/test/unit/ui/testrunnermediator.rb:94>},
>
> "Test::Unit::TestResult::FAULT"=>{# @a_proc=# /usr/share/rubygems-integration/all/gems/test-unit-3.3.9/lib/test/unit/ui/testrunnermediator.rb:97>,
> @hash=94281040046320>=># /usr/share/rubygems-integration/all/gems/test-unit-3.3.9/lib/test/unit/ui/testrunnermediator.rb:97>}}>>
> Did you mean? assert_empty
> /<>/tests/ractor_test.rb:8:in `test_generate'
> 5:
> 6: class JSONInRactorTest < Test::Unit::TestCase
> 7: def test_generate
> => 8: assert_separately([], "#{<<~"begin;"}\n#{<<~'end;'}")
> 9: begin;
> 10: $VERBOSE = nil
> 11: require "json"
> ===
> : (0.042820)
> JSONParserTest:
> test_argument_encoding: .: (0.000209)
> test_backslash: .: (0.000121)
> test_construction: .: (0.78)
> test_error_message_encoding:.: (0.000158)
> test_freeze:.: (0.000218)
> test_generate_core_subclasses_with_default_to_json: .: (0.000145)
> test_generate_core_subclasses_with_new_to_json: .: (0.000242)
> test_generate_of_core_subclasses: .: (0.000123)
> test_nesting: .: (0.000632)
> test_parse_array_custom_array_derived_class:.: (0.000104)
> test_parse_array_custom_non_array_derived_class:.: (0.000105)
> test_parse_arrays: .: (0.000156)
> test_parse_big_integers:.: (0.000178)
> test_parse_bigdecimals: .: (0.000125)
> test_parse_comments:.: (0.000163)
> test_parse_complex_objects: .: (0.019595)
> test_parse_generic_object: .: (0.000173)
> test_parse_json_primitive_values: .: (0.000492)
> test_parse_more_complex_arrays: .: (0.012031)
> test_parse_numbers: .: (0.000589)
> test_parse_object: .: (0.000103)
> test_parse_object_custom_hash_derived_class:.: (0.000108)
> test_parse_object_custom_non_hash_derived_class:.: (0.000154)
> test_parse_simple_arrays: .:
Bug#997942: tomboy-ng: FTBFS with fpc 3.2.2
On Wed, 2021-10-27 at 14:11 +0200, Graham Inggs wrote: > Source: tomboy-ng > Version: 0.32-2 > Severity: serious > Tags: ftbfs bookworm sid Thanks Graham. I noticed the same problem myself a few days ago. Its a very simple fix but as I am very close to releasing a new version anyway, maybe we can wait until them ? I am waiting on an upstream fix to kcontrols that appears to have some issues depending on locale. Due to Debian dropping libappindicator3 and replacing it with libayatana (and the name change), the current version of tomboy-ng in debian is not a good solution anyway. And the new one is bigger and better ! ;-) Davo > > Hi Maintainer > > tomboy-ng fails to build from source since fpc 3.2.2 was uploaded to > unstable. I've copied what I hope is the relevant part of the log > below. > > Regards > Graham > > > make[1]: Entering directory '/build/1st/tomboy-ng-0.32' > == We have compiled [tomboy-ng] > == $BIN_DIR is [/usr/bin] > bash ./buildit.bash > /usr/bin/which: this version of `which' is deprecated; use `command > -v' in scripts instead. > /usr/bin/which: this version of `which' is deprecated; use `command > -v' in scripts instead. > Compiler reported [3.2.2] > Unclear about your compiler, maybe edit script to support new one, > exiting ... > make[1]: *** [Makefile:36: tomboy-ngx86_64] Error 1
Bug#997610: marked as done (suds: FTBFS: error in suds-community setup command: use_2to3 is invalid.)
Your message dated Sat, 30 Oct 2021 01:20:45 +
with message-id
and subject line Bug#997610: fixed in suds 1.0.0-1
has caused the Debian Bug report #997610,
regarding suds: FTBFS: error in suds-community setup command: use_2to3 is
invalid.
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.)
--
997610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: suds
Version: 0.8.5-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_clean
> I: pybuild base:232: python3.9 setup.py clean
> error in suds-community setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean --test-pytest -i python{version} -p 3.9
> returned exit code 13
> make[1]: *** [debian/rules:9: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/suds_0.8.5-1_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: suds
Source-Version: 1.0.0-1
Done: Scott Talbert
We believe that the bug you reported is fixed in the latest version of
suds, 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.
Scott Talbert (supplier of updated suds 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: Fri, 29 Oct 2021 20:49:26 -0400
Source: suds
Architecture: source
Version: 1.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Scott Talbert
Closes: 997610
Changes:
suds (1.0.0-1) unstable; urgency=medium
.
* d/watch: Mangle beta versions
* Update to new upstream version 1.0.0 (Closes: #997610)
Checksums-Sha1:
e5ea9e6c0b00ac14607860113d119e3f88abe4b3 2120 suds_1.0.0-1.dsc
8d4a794325651d8ded5eb5f94031c7fcbe6a4f33 312059 suds_1.0.0.orig.tar.gz
a3f9b56cacf77b21000cdfb6d75d785ce2daa808 4976 suds_1.0.0-1.debian.tar.xz
59d5599cb5e7c8a3b0846585b2a281ffdf708fe1 6902 suds_1.0.0-1_amd64.buildinfo
Checksums-Sha256:
75cdb20e2dba659d128cae308c1b9e96f51c2210f718e93bbe74897d42de8d77 2120
suds_1.0.0-1.dsc
22cd62a08424a320d3f1fe574d3e054b0197f52c260affb36a6ebcb417ba2a8c 312059
suds_1.0.0.orig.tar.gz
b0c89dbad0dd70fae40b660d5be5eba883d1b94c53133956a38430526425300a 4976
suds_1.0.0-1.debian.tar.xz
d7229d94f47b5d6de166776ba0ed2552408f5a2a8f6db9fa5eff2a297f3a278c 6902
suds_1.0.0-1_amd64.buildinfo
Files:
e85fce2254dc3ed95c52f7f3b88585de 2120 python optional suds_1.0.0-1.dsc
f0eee0835b487f5fa0f5659c6b94bfa8 312059 python optional suds_1.0.0.orig.tar.gz
d5f2cd338a5aaf9c8f78eaafa6673d82 4976 python optional
suds_1.0.0-1.debian.tar.xz
f90d64d62ded3c03b2f707acee375ab6 6902 python optional
suds_1.0.0-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJDBAEBCgAtFiEEbnQ09Yl9Q7F/zVe3U9W8ZLUjeKIFAmF8lz4PHHN3dEB0ZWNo
aWUubmV0AAoJEFPVvGS1I3iix80P/1P/E2wXasVez9qoQDRS/JroiVFI6yzoepMv
iUjrIgwWuTGjF92baUr2QuAlPb7YARSiBDhaMCiOvHLKJQxjqBsEPV45Ewbvucbb
Sq9YqF2Pt64ujwtQILYsOfceZwLxmZVeXigT0G+nSQwZUHKiPl3FX98M0d57b1n9
Z5ybkO9Yp7QloQH3wxmnVBNU95OK+/9nsMFS4AEiPxm7irFveZkTu5Kfwa3y+p9U
9P4ebRZA5dY6q/WVP2xK3ElRi36/OB0Q6Z73bMGrA09Zm+bg+S19UITwdD+dpzKm
lpdBa8UcOegkFbRsKUStefvgQr3QLotMxoAhoF+BUAJu3SfXhpuOUfuI5qKW0iAJ
4Ug4RtGLbM1suSRCWFaTK+8y5Cbn4D6I80BzC5ehuLlDAGVvlqrHTVldvo6wyi/Z
HP6/zz5TZwtkzUifXXvKVEGA8mWjZg4oSTs7zvJyg68gQps5VMTfzfvZqXUX72Sf
Bug#983770: marked as done (rnp: FTBFS on 32-bit platforms (test suite failures))
Your message dated Fri, 29 Oct 2021 18:42:38 -0400 with message-id <87ilxf5u75@fifthhorseman.net> and subject line Re: Bug#983770: Acknowledgement (rnp: FTBFS on 32-bit platforms (test suite failures)) has caused the Debian Bug report #983770, regarding rnp: FTBFS on 32-bit platforms (test suite failures) 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.) -- 983770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983770 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: rnp Version: 0.14.0-5 Severity: critical Control: forwarded -1 https://github.com/rnpgp/rnp/issues/1436 RNP's test suites are failing on all of the 32-bit platforms in debian. I've reported this upstream so that hopefully it can be resolved. It should not migrate into testing in this current state. --dkg signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 0.15.2-4 rnp upstream version 0.15 fixed the timestamp issues that were causing https://bugs.debian.org/983770 on 32-bit architectures. 0.15.2-4 is the latest version of rnp in debian; if the builds are successful, it should not be prohibited from migration to testing. --dkg signature.asc Description: PGP signature --- End Message ---
Bug#983770: Acknowledgement (rnp: FTBFS on 32-bit platforms (test suite failures))
Version: 0.15.2-4 rnp upstream version 0.15 fixed the timestamp issues that were causing https://bugs.debian.org/983770 on 32-bit architectures. 0.15.2-4 is the latest version of rnp in debian; if the builds are successful, it should not be prohibited from migration to testing. --dkg signature.asc Description: PGP signature
Bug#996724: ruby3.0: FTBFS on ppc64el: Segmentation fault
Hi, ruby 3.0 3.0.2-4: - builds fine in Debian stable - fails in unstable - builds fine in unstable snapshotted on 20210930T210616Z - fails in unstable snapshotted on 20211014T215029Z The differences in terms of packages between the two last builds are: 14c14 < ii bash 5.1-3+b1 ppc64el GNU Bourne Again SHell --- > ii bash 5.1-3+b2 ppc64el >GNU Bourne Again SHell 18c18 < ii bison2:3.8.1+dfsg-1 ppc64el YACC-compatible parser generator --- > ii bison2:3.8.2+dfsg-1 ppc64el >YACC-compatible parser generator 23c23 < ii ca-certificates 20210119 all Common CA certificates --- > ii ca-certificates 20211004 all >Common CA certificates 25c25 < ii cpp 4:10.2.1-1 ppc64el GNU C preprocessor (cpp) --- > ii cpp 4:11.2.0-2 ppc64el >GNU C preprocessor (cpp) 26a27 > ii cpp-11 11.2.0-9 ppc64el >GNU C preprocessor 43c44 < ii g++ 4:10.2.1-1 ppc64el GNU C++ compiler --- > ii g++ 4:11.2.0-2 ppc64el >GNU C++ compiler 45c46,47 < ii gcc 4:10.2.1-1 ppc64el GNU C compiler --- > ii g++-11 11.2.0-9 ppc64el >GNU C++ compiler > ii gcc 4:11.2.0-2 ppc64el >GNU C compiler 48c50,51 < ii gcc-11-base:ppc64el 11.2.0-8 ppc64el GCC, the GNU Compiler Collection (base package) --- > ii gcc-11 11.2.0-9 ppc64el >GNU C compiler > ii gcc-11-base:ppc64el 11.2.0-9 ppc64el >GCC, the GNU Compiler Collection (base package) 63,64c66,67 < ii libasan6:ppc64el 11.2.0-8 ppc64el AddressSanitizer -- a fast memory error detector < ii libatomic1:ppc64el 11.2.0-8 ppc64el support library providing __atomic built-in functions --- > ii libasan6:ppc64el 11.2.0-9 ppc64el >AddressSanitizer -- a fast memory error detector > ii libatomic1:ppc64el 11.2.0-9 ppc64el >support library providing __atomic built-in functions 66,67c69,70 < ii libaudit-common 1:3.0.5-1 all Dynamic library for security auditing - common files < ii libaudit1:ppc64el1:3.0.5-1 ppc64el Dynamic library for security auditing --- > ii libaudit-common 1:3.0.6-1 all >Dynamic library for security auditing - common files > ii libaudit1:ppc64el1:3.0.6-1 ppc64el >Dynamic library for security auditing 80c83 < ii libcc1-0:ppc64el 11.2.0-8 ppc64el GCC cc1 plugin for GDB --- > ii libcc1-0:ppc64el 11.2.0-9 ppc64el >GCC cc1 plugin for GDB 97c100 < ii libffi-dev:ppc64el 3.4.2-2ppc64el Foreign Function Interface library (development files) --- > ii libffi-dev:ppc64el 3.4.2-3ppc64el >Foreign Function Interface library (development files) 99c102 < ii libffi8:ppc64el 3.4.2-2ppc64el Foreign Function Interface library runtime --- > ii libffi8:ppc64el 3.4.2-3ppc64el >Foreign Function Interface library runtime 102c105,106 < ii libgcc-s1:ppc64el11.2.0-8 ppc64el GCC support library --- > ii libgcc-11-dev:ppc64el11.2.0-9 ppc64el >GCC support library (development files) > ii libgcc-s1:ppc64el11.2.0-9 ppc64el >GCC support library 112c116 < ii libgomp1:ppc64el 11.2.0-8 ppc64el GCC OpenMP (GOMP) support library --- > ii libgomp1:ppc64el 11.2.0-9 ppc64el >GCC OpenMP (GOMP) support library 119,120c123,124 < ii libisl23:ppc64el 0.23-1 ppc64el manipulating sets and relations of integer points bounded by linear constraints < ii libitm1:ppc64el 11.2.0-8 ppc64el GNU Transactional Memory Library --- > ii
Bug#997776: marked as done (pgsphere: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.)
Your message dated Sat, 30 Oct 2021 00:09:37 +0200
with message-id
and subject line Re: Bug#997776: pgsphere: FTBFS: Error: debian/control needs
updating from debian/control.in. Run 'pg_buildext updatecontrol'.
has caused the Debian Bug report #997776,
regarding pgsphere: FTBFS: Error: debian/control needs updating from
debian/control.in. Run 'pg_buildext updatecontrol'.
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.)
--
997776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997776
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pgsphere
Version: 1.1.1+2020-10-20-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering directory '/<>/doc/img'
> rm -f logo.eps sbox.eps scircle.eps sellipse.eps sline.eps spath.eps
> sphere.eps spoint.eps spoly.eps strans.eps
> make[3]: Leaving directory '/<>/doc/img'
> make[2]: Leaving directory '/<>/doc'
> make[1]: Leaving directory '/<>'
>dh_clean
>pg_buildext checkcontrol
> --- debian/control2021-06-21 13:26:51.0 +
> +++ debian/control.RJ7dbf 2021-10-23 07:35:30.187798035 +
> @@ -17,11 +17,11 @@
> Vcs-Browser: https://salsa.debian.org/postgresql/pgsphere
> Vcs-Git: https://salsa.debian.org/postgresql/pgsphere.git
>
> -Package: postgresql-13-pgsphere
> +Package: postgresql-14-pgsphere
> Architecture: any
> Depends: ${misc:Depends},
> ${shlibs:Depends},
> - postgresql-13,
> + postgresql-14,
> Provides: postgresql-pgsphere
> Description: Spherical data types for PostgreSQL
> PgSphere, an extension for PostgreSQL, aims at providing uniform
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
> make: *** [debian/rules:20: clean] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pgsphere_1.1.1+2020-10-20-2_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 ---
Version: 1.1.1+2020-10-20-4
Re: Lucas Nussbaum
> > - postgresql-13,
> > + postgresql-14,
> > Provides: postgresql-pgsphere
> > Description: Spherical data types for PostgreSQL
> > PgSphere, an extension for PostgreSQL, aims at providing uniform
> > Error: debian/control needs updating from debian/control.in. Run
> > 'pg_buildext updatecontrol'.
> > If you are seeing this message in a buildd log, a sourceful upload is
> > required.
I have just uploaded a version that is still using PG13 to get the
healpix-cxx3 transition unstuck.
Christoph--- End Message ---
Bug#996987: closed by Debian FTP Masters (reply to Drew Parsons ) (Bug#996987: fixed in fenics-dolfinx 1:0.3.0-6)
On 2021-10-29 23:03, Sebastian Ramacher wrote: On 2021-10-29 23:59:46 +0300, Adrian Bunk wrote: On Fri, Oct 29, 2021 at 10:54:21PM +0200, Sebastian Ramacher wrote: ... > > Thanks for the heads up. I've added removal hints for basix, ffcx, > dolfinx, fenics, and fenicsx-performance-tests. >... src:fenicsx-performance-tests has not been renamed, and built fine in the transition. src:fenics is not part of this transition, I do not know anything regarding how it is related to all this. They are reverse dependencies of dolfinx, so their removal is temporary until the new source packages migrate. Thanks for clarifying. I was getting worried. I don't want fenicsx-performance-tests to have to be redone in the NEW queue. Is dolfin+mshr clear to proceed with migration to testing? mshr is not supposed to be directly affected by this transition, but for some reason which I don't completely understand it needed to be rebuilt anyway (it's running fine in unstable now). Drew
Bug#996987: closed by Debian FTP Masters (reply to Drew Parsons ) (Bug#996987: fixed in fenics-dolfinx 1:0.3.0-6)
On 2021-10-29 23:59:46 +0300, Adrian Bunk wrote: > On Fri, Oct 29, 2021 at 10:54:21PM +0200, Sebastian Ramacher wrote: > > On 2021-10-29 22:47:33 +0300, Adrian Bunk wrote: > > > Control: reopen -1 > > > > > > On Sat, Oct 23, 2021 at 12:06:03AM +, Debian Bug Tracking System > > > wrote: > > > > This is an automatic notification regarding your Bug report > > > > which was filed against the src:dolfinx package: > > > > > > > > #996987: dolfinx: FTBFS: unsatisfiable Build-Depends > > > >... > > > > fenics-dolfinx (1:0.3.0-6) unstable; urgency=medium > > > > . > > > >* release dolfinx 0.3 to unstable. Closes: #996987. > > > >... > > > > > > src:dolfinx is still unfixed, and as I understand it it will never get > > > fixed since it was replaced with src:fenics-dolfinx. > > > > > > basix/ffcx/dolfinx might all need removal hints and hints to ignore > > > their test failures for this transition, since they've all been replaced > > > with fenics-* source packages. > > > > Thanks for the heads up. I've added removal hints for basix, ffcx, > > dolfinx, fenics, and fenicsx-performance-tests. > >... > > src:fenicsx-performance-tests has not been renamed, and built fine in > the transition. > > src:fenics is not part of this transition, I do not know anything > regarding how it is related to all this. They are reverse dependencies of dolfinx, so their removal is temporary until the new source packages migrate. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#996987: closed by Debian FTP Masters (reply to Drew Parsons ) (Bug#996987: fixed in fenics-dolfinx 1:0.3.0-6)
On Fri, Oct 29, 2021 at 10:54:21PM +0200, Sebastian Ramacher wrote: > On 2021-10-29 22:47:33 +0300, Adrian Bunk wrote: > > Control: reopen -1 > > > > On Sat, Oct 23, 2021 at 12:06:03AM +, Debian Bug Tracking System wrote: > > > This is an automatic notification regarding your Bug report > > > which was filed against the src:dolfinx package: > > > > > > #996987: dolfinx: FTBFS: unsatisfiable Build-Depends > > >... > > > fenics-dolfinx (1:0.3.0-6) unstable; urgency=medium > > > . > > >* release dolfinx 0.3 to unstable. Closes: #996987. > > >... > > > > src:dolfinx is still unfixed, and as I understand it it will never get > > fixed since it was replaced with src:fenics-dolfinx. > > > > basix/ffcx/dolfinx might all need removal hints and hints to ignore > > their test failures for this transition, since they've all been replaced > > with fenics-* source packages. > > Thanks for the heads up. I've added removal hints for basix, ffcx, > dolfinx, fenics, and fenicsx-performance-tests. >... src:fenicsx-performance-tests has not been renamed, and built fine in the transition. src:fenics is not part of this transition, I do not know anything regarding how it is related to all this. cu Adrian
Bug#996987: closed by Debian FTP Masters (reply to Drew Parsons ) (Bug#996987: fixed in fenics-dolfinx 1:0.3.0-6)
On 2021-10-29 22:47:33 +0300, Adrian Bunk wrote: > Control: reopen -1 > > On Sat, Oct 23, 2021 at 12:06:03AM +, Debian Bug Tracking System wrote: > > This is an automatic notification regarding your Bug report > > which was filed against the src:dolfinx package: > > > > #996987: dolfinx: FTBFS: unsatisfiable Build-Depends > >... > > fenics-dolfinx (1:0.3.0-6) unstable; urgency=medium > > . > >* release dolfinx 0.3 to unstable. Closes: #996987. > >... > > src:dolfinx is still unfixed, and as I understand it it will never get > fixed since it was replaced with src:fenics-dolfinx. > > basix/ffcx/dolfinx might all need removal hints and hints to ignore > their test failures for this transition, since they've all been replaced > with fenics-* source packages. Thanks for the heads up. I've added removal hints for basix, ffcx, dolfinx, fenics, and fenicsx-performance-tests. Drew, please file removal bugs to get those that got replaced from unstable as well. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#996496: marked as done (src:golang-gopkg-square-go-jose.v1: fails to migrate to testing for too long: uploader built arch:all binary)
Your message dated Fri, 29 Oct 2021 20:33:49 + with message-id and subject line Bug#996496: fixed in golang-gopkg-square-go-jose.v1 1.1.2-3.1 has caused the Debian Bug report #996496, regarding src:golang-gopkg-square-go-jose.v1: fails to migrate to testing for too long: uploader built arch:all binary 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.) -- 996496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996496 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-gopkg-square-go-jose.v1 Version: 1.1.2-2 Severity: serious Control: close -1 1.1.2-3 X-Debbugs-CC: jel...@debian.org Tags: sid bookworm pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:golang-gopkg-square-go-jose.v1 has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=golang-gopkg-square-go-jose.v1 OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: golang-gopkg-square-go-jose.v1 Source-Version: 1.1.2-3.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of golang-gopkg-square-go-jose.v1, 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 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated golang-gopkg-square-go-jose.v1 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: Thu, 14 Oct 2021 21:16:31 +0200 Source: golang-gopkg-square-go-jose.v1 Architecture: source Version: 1.1.2-3.1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Paul Gevers Closes: 996496 Changes: golang-gopkg-square-go-jose.v1 (1.1.2-3.1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #996496) Checksums-Sha1: ced0b93cc959153f5d91f8cc4f8cccb9ef3723ba 2063 golang-gopkg-square-go-jose.v1_1.1.2-3.1.dsc 7ffb370242c86a5251d9df69d936db6a326e0966 3600 golang-gopkg-square-go-jose.v1_1.1.2-3.1.debian.tar.xz Checksums-Sha256: d0709cce87eb81132267827f837d91a85ab72468b413ef796ba782efd57d6330 2063 golang-gopkg-square-go-jose.v1_1.1.2-3.1.dsc 1cebbb881263372b548d350c04db3624a77d81748f10476793eb0c792ecb9530 3600 golang-gopkg-square-go-jose.v1_1.1.2-3.1.debian.tar.xz Files: 0d34f9a2d23e767a14dcf57cff77475a 2063 devel optional golang-gopkg-square-go-jose.v1_1.1.2-3.1.dsc b9b96998f5282ba339d9ccae704c417c 3600 devel optional golang-gopkg-square-go-jose.v1_1.1.2-3.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmFogiwACgkQnFyZ6wW9
Bug#996493: marked as done (src:golang-github-getlantern-hidden: fails to migrate to testing for too long: uploader built arch:all binary)
Your message dated Fri, 29 Oct 2021 20:23:01 + with message-id and subject line Bug#996493: fixed in golang-github-getlantern-hidden 0.0~git20190325.f02dbb0-3.1 has caused the Debian Bug report #996493, regarding src:golang-github-getlantern-hidden: fails to migrate to testing for too long: uploader built arch:all binary 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.) -- 996493: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996493 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: golang-github-getlantern-hidden Version: 0.0~git20190325.f02dbb0-2 Severity: serious Control: close -1 0.0~git20190325.f02dbb0-3 X-Debbugs-CC: jel...@debian.org Tags: sid bookworm pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:golang-github-getlantern-hidden has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=golang-github-getlantern-hidden OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: golang-github-getlantern-hidden Source-Version: 0.0~git20190325.f02dbb0-3.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of golang-github-getlantern-hidden, 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 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated golang-github-getlantern-hidden 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: Thu, 14 Oct 2021 21:04:18 +0200 Source: golang-github-getlantern-hidden Architecture: source Version: 0.0~git20190325.f02dbb0-3.1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Paul Gevers Closes: 996493 Changes: golang-github-getlantern-hidden (0.0~git20190325.f02dbb0-3.1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #996493) Checksums-Sha1: a7ce0758edcbeea56d02abd07e617d599149854f 2282 golang-github-getlantern-hidden_0.0~git20190325.f02dbb0-3.1.dsc 6c73f654b61a7c82cb275537c373cb66f1238545 1764 golang-github-getlantern-hidden_0.0~git20190325.f02dbb0-3.1.debian.tar.xz Checksums-Sha256: 083e7ff9f6a4778020457d977331c3a1b9f6f55c1b0c89044f936686beafd407 2282 golang-github-getlantern-hidden_0.0~git20190325.f02dbb0-3.1.dsc 70eda315f9c670536a080c35b4e0d4f1ebf419b648cff47118e93b40dc01d335 1764 golang-github-getlantern-hidden_0.0~git20190325.f02dbb0-3.1.debian.tar.xz Files: 4426d89128f89a1dee2ccdb2a00af5b0 2282 devel optional golang-github-getlantern-hidden_0.0~git20190325.f02dbb0-3.1.dsc
Bug#997374: marked as done (pyswarms: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet')
Your message dated Fri, 29 Oct 2021 20:23:29 +
with message-id
and subject line Bug#997374: fixed in pyswarms 1.3.0-2
has caused the Debian Bug report #997374,
regarding pyswarms: FTBFS: AttributeError: 'Sphinx' object has no attribute
'add_stylesheet'
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.)
--
997374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyswarms
Version: 1.3.0-1
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[2]: Entering directory '/<>/docs'
> sphinx-build -b html -d _build/doctrees . _build/html
> Running Sphinx v4.2.0
> making output directory... done
>
> Exception occurred:
> File "/<>/docs/conf.py", line 167, in setup
> app.add_stylesheet("theme_overrides.css") # path relative to static
> AttributeError: 'Sphinx' object has no attribute 'add_stylesheet'
> The full traceback has been saved in /tmp/sphinx-err-48_kb6lf.log, if you
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error
> message can be provided next time.
> A bug report can be filed in the tracker at
> . Thanks!
> make[2]: *** [Makefile:53: html] Error 2
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pyswarms_1.3.0-1_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: pyswarms
Source-Version: 1.3.0-2
Done: Nilesh Patra
We believe that the bug you reported is fixed in the latest version of
pyswarms, 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.
Nilesh Patra (supplier of updated pyswarms 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: Fri, 29 Oct 2021 19:41:43 +
Source: pyswarms
Architecture: source
Version: 1.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team
Changed-By: Nilesh Patra
Closes: 997374
Changes:
pyswarms (1.3.0-2) unstable; urgency=medium
.
* Team Upload.
* d/p/Fix-FTBFS-with-new-sphinx.patch: Change api call
to fix doc building with sphinx 4.2.0 (Closes: #997374)
Checksums-Sha1:
e8951bc0bfbe1a425d18d3a17544e05f5ba0703d 2544 pyswarms_1.3.0-2.dsc
87ebeba7a1aca636e5f2766fd2145bd578dbdf3a 9712 pyswarms_1.3.0-2.debian.tar.xz
09d1b0b714487255bc0396bd8aa071aaa14b11ac 10061 pyswarms_1.3.0-2_amd64.buildinfo
Checksums-Sha256:
f121e58e3dfb3f0ad64473fc4305cb73aa33d76955cbae41c0c46bb709d199b9 2544
pyswarms_1.3.0-2.dsc
d973121a47253485066be00ce60ff594a6bbb7f270638ecc7c84ad1598a7ba80 9712
pyswarms_1.3.0-2.debian.tar.xz
e4d330df9144e8843a9103b4ce9a1fd43ebd1e8f7374626a94d7ccbe93d6d451 10061
pyswarms_1.3.0-2_amd64.buildinfo
Files:
80f24a358c5e5961b611c8d269994b3a 2544 python optional pyswarms_1.3.0-2.dsc
7fbea1d885c3db7c8ff553529691034c 9712 python optional
pyswarms_1.3.0-2.debian.tar.xz
7963099f9c1622150dbd207e08ada62d 10061 python optional
pyswarms_1.3.0-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmF8UbMSHG5pbGVzaEBk
ZWJpYW4ub3JnAAoJEAC650s0M2nxDmIQAKIM0XY4lfX5hOYpkOO+1LUadSqp9an/
7lPBBRvAOG1Pnm123pfwgJXKJweifTHybGzievBl46zFVg6PL09sxT40Y9YoWvNG
luvkP587ThvBynQspXZjehRUTfM9P1HrlFIqnWcL7avVgsCbJ45HoX2Zg+cZ8t+3
Nfr+rPF0jPROD79sLAZZEWtYOwablPGgzj6ZKD3WjUlh9TkQqvlC/Q6PVBgXJ4Hg
dt/toJLhzMOu+CkZN5BLdrF7VcB1FsR4kCQ3u6xnodXXilALK6AhD/nGdYGCZVyG
6QKqL3kqOrBq/aSzx9d7kQF7YQmGTxnU4/FO76VQWfkT1rCq4IWLpWFzwXa7I/Ub
Bug#984080: marked as done (lamarc: ftbfs with GCC-11)
Your message dated Fri, 29 Oct 2021 20:23:10 +
with message-id
and subject line Bug#984080: fixed in lamarc 2.1.10.1+dfsg-6
has caused the Debian Bug report #984080,
regarding lamarc: ftbfs with GCC-11
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.)
--
984080: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984080
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:lamarc
Version: 2.1.10.1+dfsg-5
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.
The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/lamarc_2.1.10.1+dfsg-5_unstable_gcc11.log
The last lines of the build log are at the end of this report.
To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html
GCC 11 defaults to the GNU++17 standard. If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.
[...]
| ^
/usr/include/wx-3.0/wx/hashmap.h:714:5: note: in expansion of macro
‘_WX_DECLARE_HASH_MAP’
714 | _WX_DECLARE_HASH_MAP( wxString, VALUE_T, wxStringHash,
wxStringEqual, \
| ^~~~
/usr/include/wx-3.0/wx/clntdata.h:24:1: note: in expansion of macro
‘WX_DECLARE_STRING_HASH_MAP_WITH_DECL’
24 | WX_DECLARE_STRING_HASH_MAP_WITH_DECL(
| ^~~~
/usr/include/wx-3.0/wx/hashmap.h:626:20: note: because ‘wxStringEqual’ has
user-provided ‘wxStringEqual& wxStringEqual::operator=(const wxStringEqual&)’
626 | wxStringEqual& operator=(const wxStringEqual&) { return *this; }
|^~~~
/usr/include/wx-3.0/wx/hashmap.h:255:11: warning: implicitly-declared
‘constexpr
wxShadowObjectFields_wxImplementation_KeyEx::wxShadowObjectFields_wxImplementation_KeyEx(const
wxShadowObjectFields_wxImplementation_KeyEx&)’ is deprecated
[-Wdeprecated-copy]
255 | m_getKey( ht.m_getKey ) \
| ^~~
/usr/include/wx-3.0/wx/hashmap.h:638:1: note: in expansion of macro
‘_WX_DECLARE_HASHTABLE’
638 | _WX_DECLARE_HASHTABLE( CLASSNAME##_wxImplementation_Pair, KEY_T,
HASH_T, \
| ^
/usr/include/wx-3.0/wx/hashmap.h:714:5: note: in expansion of macro
‘_WX_DECLARE_HASH_MAP’
714 | _WX_DECLARE_HASH_MAP( wxString, VALUE_T, wxStringHash,
wxStringEqual, \
| ^~~~
/usr/include/wx-3.0/wx/clntdata.h:24:1: note: in expansion of macro
‘WX_DECLARE_STRING_HASH_MAP_WITH_DECL’
24 | WX_DECLARE_STRING_HASH_MAP_WITH_DECL(
| ^~~~
/usr/include/wx-3.0/wx/hashmap.h:461:16: note: because
‘wxShadowObjectFields_wxImplementation_KeyEx’ has user-provided
‘wxShadowObjectFields_wxImplementation_KeyEx&
wxShadowObjectFields_wxImplementation_KeyEx::operator=(const
wxShadowObjectFields_wxImplementation_KeyEx&)’
461 | CLASSNAME& operator=(const CLASSNAME&) { return *this; } \
|^~~~
/usr/include/wx-3.0/wx/hashmap.h:637:1: note: in expansion of macro
‘_WX_DECLARE_HASH_MAP_KEY_EX’
637 | _WX_DECLARE_HASH_MAP_KEY_EX( KEY_T, CLASSNAME##_wxImplementation_Pair,
CLASSNAME##_wxImplementation_KeyEx, CLASSEXP ) \
| ^~~
/usr/include/wx-3.0/wx/hashmap.h:714:5: note: in expansion of macro
‘_WX_DECLARE_HASH_MAP’
714 | _WX_DECLARE_HASH_MAP( wxString, VALUE_T, wxStringHash,
wxStringEqual, \
| ^~~~
/usr/include/wx-3.0/wx/clntdata.h:24:1: note: in
Bug#996491: marked as done (src:gnome-authenticator: fails to migrate to testing for too long: uploader built arch:all)
Your message dated Fri, 29 Oct 2021 20:22:23 + with message-id and subject line Bug#996491: fixed in gnome-authenticator 3.32.2+dfsg1-3.1 has caused the Debian Bug report #996491, regarding src:gnome-authenticator: fails to migrate to testing for too long: uploader built arch:all 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.) -- 996491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gnome-authenticator Version: 3.32.2+dfsg1-2 Severity: serious Control: close -1 3.32.2+dfsg1-3 X-Debbugs-CC: jel...@debian.org Tags: sid bookworm pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:gnome-authenticator has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=gnome-authenticator OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: gnome-authenticator Source-Version: 3.32.2+dfsg1-3.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of gnome-authenticator, 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 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated gnome-authenticator 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: Thu, 14 Oct 2021 21:03:47 +0200 Source: gnome-authenticator Architecture: source Version: 3.32.2+dfsg1-3.1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Paul Gevers Closes: 996491 Changes: gnome-authenticator (3.32.2+dfsg1-3.1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #996491) Checksums-Sha1: a94c2caaea402171bfd7e54ccbe3ba50ada2d279 2376 gnome-authenticator_3.32.2+dfsg1-3.1.dsc a31e2957952adce17e6a915e2fccca315f2b6ce6 10536 gnome-authenticator_3.32.2+dfsg1-3.1.debian.tar.xz Checksums-Sha256: 24c9b9fb8e8d8be6443ea5ce372d514048c95b30665638c3d6feeca0bc0b3aaf 2376 gnome-authenticator_3.32.2+dfsg1-3.1.dsc 0025f340a1511dee4fb29a946e95dd729a60f5584b7eda801957ffa27fb2401e 10536 gnome-authenticator_3.32.2+dfsg1-3.1.debian.tar.xz Files: 389232cac6f3f1a2113719bb1b730797 2376 gnome optional gnome-authenticator_3.32.2+dfsg1-3.1.dsc ac3526b2ee753ab28b2d026341d8d62e 10536 gnome optional gnome-authenticator_3.32.2+dfsg1-3.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmFof0AACgkQnFyZ6wW9 dQrTGwf6AvFWyVMCZXsGvX09PYz9Mifu1IhJT1JVBzLmuqwCn1cdB0WRhe+ItgM1
Bug#993835: rnp FTBFS: rnp_tests.test_key_add_userid (Failed)
Version: 0.15.2-1 The RNP test suite no longer fails on test_key_add_userid as of version 0.15.2-1. There are new failures on armel and armhf with test_sym_encryption__rnp_aead, sigh, but i'll try to diagnose those in a separate bug report. --dkg On Tue 2021-09-07 05:52:14 +0300, Adrian Bunk wrote: > Source: rnp > Version: 0.14.0-6 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/package.php?p=rnp=sid > > ... > test 135 > Start 135: rnp_tests.test_key_add_userid > > 135: Test command: /<>/build/src/tests/rnp_tests > "--gtest_filter=rnp_tests.test_key_add_userid" > "--gtest_also_run_disabled_tests" > 135: Environment variables: > 135: RNP_TEST_DATA=/<>/src/tests/data > 135: Test timeout computed to be: 3000 > 135: Note: Google Test filter = rnp_tests.test_key_add_userid > 135: [==] Running 1 test from 1 test suite. > 135: [--] Global test environment set-up. > 135: [--] 1 test from rnp_tests > 135: [ RUN ] rnp_tests.test_key_add_userid > 135: unknown file: Failure > 135: C++ exception with description "rnp_exception" thrown in the test body. > 135: [ FAILED ] rnp_tests.test_key_add_userid (31 ms) > ... > > 99% tests passed, 1 tests failed out of 213 > > Total Test time (real) = 650.07 sec > > The following tests FAILED: > 135 - rnp_tests.test_key_add_userid (Failed) > Errors while running CTest > make[1]: *** [Makefile:129: test] Error 8 signature.asc Description: PGP signature
Bug#993835: marked as done (rnp FTBFS: rnp_tests.test_key_add_userid (Failed))
Your message dated Fri, 29 Oct 2021 15:43:42 -0400 with message-id <87o87762hd@fifthhorseman.net> and subject line Re: Bug#993835: rnp FTBFS: rnp_tests.test_key_add_userid (Failed) has caused the Debian Bug report #993835, regarding rnp FTBFS: rnp_tests.test_key_add_userid (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.) -- 993835: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rnp Version: 0.14.0-6 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=rnp=sid ... test 135 Start 135: rnp_tests.test_key_add_userid 135: Test command: /<>/build/src/tests/rnp_tests "--gtest_filter=rnp_tests.test_key_add_userid" "--gtest_also_run_disabled_tests" 135: Environment variables: 135: RNP_TEST_DATA=/<>/src/tests/data 135: Test timeout computed to be: 3000 135: Note: Google Test filter = rnp_tests.test_key_add_userid 135: [==] Running 1 test from 1 test suite. 135: [--] Global test environment set-up. 135: [--] 1 test from rnp_tests 135: [ RUN ] rnp_tests.test_key_add_userid 135: unknown file: Failure 135: C++ exception with description "rnp_exception" thrown in the test body. 135: [ FAILED ] rnp_tests.test_key_add_userid (31 ms) ... 99% tests passed, 1 tests failed out of 213 Total Test time (real) = 650.07 sec The following tests FAILED: 135 - rnp_tests.test_key_add_userid (Failed) Errors while running CTest make[1]: *** [Makefile:129: test] Error 8 --- End Message --- --- Begin Message --- Version: 0.15.2-1 The RNP test suite no longer fails on test_key_add_userid as of version 0.15.2-1. There are new failures on armel and armhf with test_sym_encryption__rnp_aead, sigh, but i'll try to diagnose those in a separate bug report. --dkg On Tue 2021-09-07 05:52:14 +0300, Adrian Bunk wrote: > Source: rnp > Version: 0.14.0-6 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/package.php?p=rnp=sid > > ... > test 135 > Start 135: rnp_tests.test_key_add_userid > > 135: Test command: /<>/build/src/tests/rnp_tests > "--gtest_filter=rnp_tests.test_key_add_userid" > "--gtest_also_run_disabled_tests" > 135: Environment variables: > 135: RNP_TEST_DATA=/<>/src/tests/data > 135: Test timeout computed to be: 3000 > 135: Note: Google Test filter = rnp_tests.test_key_add_userid > 135: [==] Running 1 test from 1 test suite. > 135: [--] Global test environment set-up. > 135: [--] 1 test from rnp_tests > 135: [ RUN ] rnp_tests.test_key_add_userid > 135: unknown file: Failure > 135: C++ exception with description "rnp_exception" thrown in the test body. > 135: [ FAILED ] rnp_tests.test_key_add_userid (31 ms) > ... > > 99% tests passed, 1 tests failed out of 213 > > Total Test time (real) = 650.07 sec > > The following tests FAILED: > 135 - rnp_tests.test_key_add_userid (Failed) > Errors while running CTest > make[1]: *** [Makefile:129: test] Error 8 signature.asc Description: PGP signature --- End Message ---
Bug#996987: closed by Debian FTP Masters (reply to Drew Parsons ) (Bug#996987: fixed in fenics-dolfinx 1:0.3.0-6)
Control: reopen -1 On Sat, Oct 23, 2021 at 12:06:03AM +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the src:dolfinx package: > > #996987: dolfinx: FTBFS: unsatisfiable Build-Depends >... > fenics-dolfinx (1:0.3.0-6) unstable; urgency=medium > . >* release dolfinx 0.3 to unstable. Closes: #996987. >... src:dolfinx is still unfixed, and as I understand it it will never get fixed since it was replaced with src:fenics-dolfinx. basix/ffcx/dolfinx might all need removal hints and hints to ignore their test failures for this transition, since they've all been replaced with fenics-* source packages. cu Adrian
Processed: Re: Bug#996987 closed by Debian FTP Masters (reply to Drew Parsons ) (Bug#996987: fixed in fenics-dolfinx 1:0.3.0-6)
Processing control commands:
> reopen -1
Bug #996987 {Done: Drew Parsons } [src:dolfinx] dolfinx:
FTBFS: unsatisfiable Build-Depends
'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 fenics-dolfinx/1:0.3.0-6.
--
996987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996987
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reopening 984157
Processing commands for cont...@bugs.debian.org:
> reopen 984157
Bug #984157 {Done: A. Maitland Bottoms } [src:uhd]
gnss-sdr: ftbfs with GCC-11
'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 uhd/3.15.0.0-5.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#984157: closed by Debian FTP Masters (reply to bott...@debian.org (A. Maitland Bottoms)) (Bug#984157: fixed in uhd 3.15.0.0-5)
On Fri, Oct 22, 2021 at 06:06:06AM +, Debian Bug Tracking System wrote: >... > /usr/include/uhd/property_tree.ipp:26:50: error: expected ‘)’ before ‘mode’ >26 | property_impl(property_tree::coerce_mode_t mode) : > _coerce_mode(mode) > | ~^ > | ) > /usr/include/uhd/property_tree.ipp:33:5: error: template-id not allowed for > destructor >33 | ~property_impl(void) > | ^ >... This part appears to still need fixing: https://buildd.debian.org/status/logs.php?pkg=gnss-sdr=0.0.15-1%2Bb1 cu Adrian
Bug#996569: OT: Roland Puntaier / "getmail6" drama
Sudip Mukherjee wrote: > > Marking this bug as serious and the binary packages should be removed > in the next 30 days. Thank you. Charles -- -- Charles Cazabon Software, consulting, and services available at http://pyropus.ca/ --
Processed: Re: [R-pkg-team] Bug#994443: marked as done (r-bioc-deseq2: autopkgtest regression)
Processing control commands: > fixed -1 1.32.0+dfsg-3 Bug #994443 [src:r-bioc-deseq2] r-bioc-deseq2: autopkgtest regression Marked as fixed in versions r-bioc-deseq2/1.32.0+dfsg-3. -- 994443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#994443: [R-pkg-team] Bug#994443: marked as done (r-bioc-deseq2: autopkgtest regression)
control: fixed -1 1.32.0+dfsg-3 Hi Graham, r-bioc-deseq2's autopkgtests started to again pass in testing on 2021-09-29, once r-bioc-tximportdata migrated. However, the autopkgtests in stable continue to fail [1]. I think you are doing something wrong if a change in a package in unstable affects a package in testing and stable. I think this has got nothing to do with our changes in unstable -- I'd be very surprised if so, since essentially atleast stable is disconnected, unless some other package has been on-purpose updated there. As I can see, tests in stable were always failing[1] This is due to missing dep, see Michael's mail below. So I'm marking this bug as fixed in the latest version to avoid autoremoval. Hope that is okay. [1]: https://ci.debian.net/packages/r/r-bioc-deseq2/stable/amd64/ Nilesh On Fri, 22 Oct 2021 14:05:45 +0200 "Michael R. Crusoe" wrote: On Thu, 21 Oct 2021 15:15:52 +0200 Graham Inggs wrote: > Control: reopen -1 > > r-bioc-deseq2's autopkgtests started to again pass in testing on > 2021-09-29, once r-bioc-tximportdata migrated. > However, the autopkgtests in stable continue to fail [1]. Correct, because the package r-bioc-tximportdata does not exist in stable. OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: Bug#996569: OT: Roland Puntaier / "getmail6" drama
Processing control commands: > severity -1 serious Bug #996569 [getmail6] getmail6 naming issues Severity set to 'serious' from 'normal' -- 996569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996569 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unmerging 984157
Processing commands for cont...@bugs.debian.org:
> unmerge 984157
Bug #984157 {Done: A. Maitland Bottoms } [src:uhd]
gnss-sdr: ftbfs with GCC-11
Bug #984375 {Done: A. Maitland Bottoms } [src:uhd] uhd:
ftbfs with GCC-11
Disconnected #984157 from all other report(s).
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984157
984375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984375
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#996642: FTBFS with glibc 2.32
Hi Alastair, On Tue, 26 Oct 2021 at 13:27, Alastair McKinstry < alastair.mckins...@sceal.ie> wrote: > Hi Nilesh > > > > Just uploaded a patched csh now. > > Apologies I was trying to port a later snapshot of csh but ran into > porting issues. > No worries, and thanks for the upload. But one odd thing that I noticed in this upload is (from debdiff): -Maintainer: Alastair McKinstry +Maintainer: Ubuntu Developers +XSBC-Original-Maintainer: Alastair McKinstry Is this really intended? Did you somehow make an (non-intended) ubuntu-specific change in the Debian package? Let me know. Thanks, Nilesh
Bug#997699: marked as done (r-cran-git2r: FTBFS: configure.ac: error: required file 'config.rpath' not found)
Your message dated Fri, 29 Oct 2021 18:35:05 + with message-id and subject line Bug#997699: fixed in r-cran-git2r 0.28.0-2 has caused the Debian Bug report #997699, regarding r-cran-git2r: FTBFS: configure.ac: error: required file 'config.rpath' not found 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.) -- 997699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-git2r Version: 0.28.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package r-cran-git2r > dpkg-buildpackage: info: source version 0.28.0-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Andreas Tille > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > debian/rules clean > dh clean --buildsystem R >dh_auto_clean -O--buildsystem=R >dh_autoreconf_clean -O--buildsystem=R >dh_clean -O--buildsystem=R > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building r-cran-git2r using existing > ./r-cran-git2r_0.28.0.orig.tar.gz > dpkg-source: info: building r-cran-git2r in > r-cran-git2r_0.28.0-1.debian.tar.xz > dpkg-source: info: building r-cran-git2r in r-cran-git2r_0.28.0-1.dsc > debian/rules binary > dh binary --buildsystem R >dh_update_autotools_config -O--buildsystem=R >dh_autoreconf -O--buildsystem=R > configure.ac: error: required file 'config.rpath' not found > dh_autoreconf: error: autoreconf -f -i returned exit code 1 > make: *** [debian/rules:4: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/10/23/r-cran-git2r_0.28.0-1_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: r-cran-git2r Source-Version: 0.28.0-2 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of r-cran-git2r, 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. Nilesh Patra (supplier of updated r-cran-git2r 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: Fri, 29 Oct 2021 18:19:30 + Source: r-cran-git2r Architecture: source Version: 0.28.0-2 Distribution: unstable Urgency: medium Maintainer: Debian R Packages Maintainers Changed-By: Nilesh Patra Closes: 997699 Changes: r-cran-git2r (0.28.0-2) unstable; urgency=medium . * Team Upload. * d/rules: create empty config.rpath to fix FTBFS with autoconf (Closes: #997699) * Bump Standards-Version to 4.6.0 (no changes needed) Checksums-Sha1: fd1173c07b9e69d02251ac0d3474547c7f6232e0 2091 r-cran-git2r_0.28.0-2.dsc 08ff27638c6409dbbfb08dcc4d44568d384972a3 4808 r-cran-git2r_0.28.0-2.debian.tar.xz a21999256a163d841f6d0a03603b8b0b5299f8fb 10573 r-cran-git2r_0.28.0-2_amd64.buildinfo Checksums-Sha256: 4b0137772dd3b9220c3cfd0a98d22b0f97b309a704d856eca7e1e0a0a54430e0 2091 r-cran-git2r_0.28.0-2.dsc 1aa297e83ad080216afa73847d79c7ed77eb0c9373db028aec717c34fc6b4562 4808 r-cran-git2r_0.28.0-2.debian.tar.xz 1cabf232cf8ccb1b57747116e78c2073ef6729e122c54d05baf0a3d194d7f89e 10573 r-cran-git2r_0.28.0-2_amd64.buildinfo Files: 38809d0eb3a06bede73d3beafe49a692 2091 gnu-r optional r-cran-git2r_0.28.0-2.dsc 1e9b06545f57c2f8105de42a4e4904a0 4808 gnu-r optional
Bug#997165: marked as done (multitail: FTBFS: mt.c:1746:17: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Fri, 29 Oct 2021 18:04:13 +
with message-id
and subject line Bug#997165: fixed in multitail 6.5.0-4
has caused the Debian Bug report #997165,
regarding multitail: FTBFS: mt.c:1746:17: error: format not a string literal
and no format arguments [-Werror=format-security]
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.)
--
997165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997165
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: multitail
Version: 6.5.0-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):
> cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -g -Wall -Wno-unused-parameter
> -funsigned-char -O3 -DLinux -DVERSION=\"6.5.0\" -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -g -DCONFIG_FILE=\"/etc/multitail.conf\" -MMD -MP
> -DUTF8_SUPPORT -c -o mt.o mt.c
> mt.c: In function ‘do_color_print’:
> mt.c:707:25: warning: implicit declaration of function ‘waddnwstr’; did you
> mean ‘waddnstr’? [-Wimplicit-function-declaration]
> 707 | waddnwstr(win -> win, , 1);
> | ^
> | waddnstr
> mt.c: In function ‘update_statusline’:
> mt.c:1467:126: warning: format ‘%lld’ expects argument of type ‘long long
> int’, but argument 5 has type ‘off64_t’ {aka ‘long int’} [-Wformat=]
> 1467 | mvwprintw(status ->
> win, 0, win_width - (strlen(timestamp) + cur_len), "%10lld - %s", fsize,
> timestamp);
> |
> ~^~
> |
>||
> |
>|off64_t {aka
> long int}
> |
>long long int
> |
> %10ld
> mt.c: In function ‘create_windows’:
> mt.c:1746:17: error: format not a string literal and no format arguments
> [-Werror=format-security]
> 1746 | wprintw(menu_win -> win, version_str);
> | ^~~
> cc1: some warnings being treated as errors
> make[1]: *** [: mt.o] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/multitail_6.5.0-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: multitail
Source-Version: 6.5.0-4
Done: Rene Engelhard
We believe that the bug you reported is fixed in the latest version of
multitail, 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.
Rene Engelhard (supplier of updated multitail 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: Fri, 29 Oct 2021 16:55:25 +
Source: multitail
Architecture: source
Version: 6.5.0-4
Distribution: unstable
Urgency: medium
Maintainer: Rene Engelhard
Changed-By: Rene Engelhard
Closes: 997165
Changes:
multitail (6.5.0-4) unstable; urgency=medium
.
* add some needed format strings (closes: #997165)
Checksums-Sha1:
Bug#995365: (no subject)
Dear maintainer, The fix you added solve the ImportError: cannot import name 'ENOENT'. However, it still prevent manpages build for trafficserver package. Using the latest release of sphinxcontrib.plantuml allows the build. Version 0.5 of the package is now 7 years old. Please consider packaging last release ? Thanks, Jean Baptiste OpenPGP_signature Description: OpenPGP digital signature
Bug#972084: marked as done (gweled: Display is glitching)
Your message dated Fri, 29 Oct 2021 16:18:44 + with message-id and subject line Bug#972084: fixed in gweled 0.9.1-8 has caused the Debian Bug report #972084, regarding gweled: Display is glitching 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.) -- 972084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gweled Version: 0.9.1-7 Severity: important Dear Maintainer, Gweled 0.9.1-7 The game launches well, menus work too but the game tiles are not readable (glitch images). I hadn't started the game for a while, so I can't say when the problem really happened. I found this bug report that seems to describe the same problem, maybe it can help: https://bugs.launchpad.net/gweled/+bug/1897498 Thanks for your work, Isabelle -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing'), (100, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-2-amd64 (SMP w/16 CPU threads) 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) LSM: AppArmor: enabled Versions of packages gweled depends on: ii libatk1.0-0 2.36.0-2 ii libc62.31-3 ii libcairo21.16.0-4 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.10.2+dfsg-3 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5 ii libglib2.0-0 2.66.0-2 ii libgtk2.0-0 2.24.32-4 ii libmikmod3 3.3.11.1-5 ii libpango-1.0-0 1.46.2-1 ii libpangocairo-1.0-0 1.46.2-1 ii libpangoft2-1.0-01.46.2-1 ii librsvg2-2 2.50.0+dfsg-1 gweled recommends no packages. gweled suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: gweled Source-Version: 0.9.1-8 Done: Stephen Kitt We believe that the bug you reported is fixed in the latest version of gweled, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen Kitt (supplier of updated gweled 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: Fri, 29 Oct 2021 17:57:28 +0200 Source: gweled Architecture: source Version: 0.9.1-8 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Stephen Kitt Closes: 972084 Changes: gweled (0.9.1-8) unstable; urgency=medium . * Apply upstream patch to fix SVGs and allow the game to work with current releases of librsvg. Closes: #972084. * Switch to debhelper compatibility level 13. * Upgrade debian/watch to version 4. * Standards-Version 4.6.0, no change required. Checksums-Sha1: 797cfe4fe2f05ae9448b33073bd9b831cb4eb9cd 1918 gweled_0.9.1-8.dsc 1e73075d39ea84345d90201cb4636a1864ac3c73 16908 gweled_0.9.1-8.debian.tar.xz ca9d1ad3a0f06c7db75776f256c337f194149c29 13463 gweled_0.9.1-8_source.buildinfo Checksums-Sha256: a73e520ac6b480eff8d1506f58c62b9882acb2acf8e9e46216a2117558ed81e9 1918 gweled_0.9.1-8.dsc 47e12345a53ded08a7e411d3870a85ac0b4b287ef66d9f9c718fbef7db5dac79 16908 gweled_0.9.1-8.debian.tar.xz 08bcc469e2983e58aa64bad0caf3c7423fa69c5ceeaeb74f29d4961512ce6e1c 13463 gweled_0.9.1-8_source.buildinfo Files: a9eebb5154872147e7fefb52c135a53b 1918 games optional gweled_0.9.1-8.dsc 941d523011c90f565136e39fa180e235 16908 games optional gweled_0.9.1-8.debian.tar.xz 456783766bc338aad8dde8e913720249 13463 games optional gweled_0.9.1-8_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmF8Gg0ACgkQgNMC9Yht g5ydOQ/+NGDgIjcyE+rsRofIMpnom28AZdhtFd0SANTLV+5wU8HDJhutQjytOzwK qzWJMhwZq8PjkScK2G/UPUmqnRMkswN3yFY6XRI26Pd0uB9HiNtUixrgsdB11cG3 i7TaKzzUN53nH873k/M+PNui/r6qa/XOwoeM411h8ca/LuvugMURhEb8CRnQsV4A hm+b5Pjr9RY1FaoBnhBtTKiPqasG8BqZybtn6DFjCGgRdRM0o1bG6fGjKcAyAf04 ttuU+Ai0shQbGKK0AWOBfGYkF3rUo9MwXISdlF+miLwCH2oBxbuZ800et/s8JBZE VlXXlREo4tVzVTA8MH54ytQs3oRX/c2p/cIx8c/lpzfgu2m9x2mxwplBGRcnIdAR F5iCaQQbm6ou5atliT9ujKkwHlte/rQOHHm/zDpbu3kcWzi52cmxyQj0wTW4xEo6
Processed: Bug#972084 marked as pending in gweled
Processing control commands: > tag -1 pending Bug #972084 [gweled] gweled: Display is glitching Added tag(s) pending. -- 972084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972084: marked as pending in gweled
Control: tag -1 pending Hello, Bug #972084 in gweled 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/games-team/gweled/-/commit/f0c1431f88d789885e82411ec156ab667ce7232d Apply upstream patch to fix SVGs Closes: #972084 (this message was generated automatically) -- Greetings https://bugs.debian.org/972084
Bug#997429: ycm-cmake-modules: FTBFS: Could not import extension cmake (exception: cannot import name 'htmlescape' from 'sphinx.util.pycompat' (/usr/lib/python3/dist-packages/sphinx/util/pycompat.py))
Hi Daniele, On Sat, 23 Oct 2021 22:33:30 +0200 Lucas Nussbaum wrote: Source: ycm-cmake-modules Version: 0.13.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs I did a fix for this and uploaded. The patch is here in salsa[1] -- if you think it is okay, could you please forward it upstream? [1]: https://salsa.debian.org/science-team/ycm-cmake-modules/-/blob/master/debian/patches/fix-sphinx-build.patch Thanks, Nilesh OpenPGP_signature Description: OpenPGP digital signature
Bug#997429: marked as done (ycm-cmake-modules: FTBFS: Could not import extension cmake (exception: cannot import name 'htmlescape' from 'sphinx.util.pycompat' (/usr/lib/python3/dist-packages/sphinx/ut
Your message dated Fri, 29 Oct 2021 15:49:32 + with message-id and subject line Bug#997429: fixed in ycm-cmake-modules 0.13.0-2 has caused the Debian Bug report #997429, regarding ycm-cmake-modules: FTBFS: Could not import extension cmake (exception: cannot import name 'htmlescape' from 'sphinx.util.pycompat' (/usr/lib/python3/dist-packages/sphinx/util/pycompat.py)) 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.) -- 997429: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997429 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ycm-cmake-modules Version: 0.13.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[4]: Entering directory '/<>/obj-x86_64-linux-gnu' > cd /<>/obj-x86_64-linux-gnu/build-modules && /usr/bin/cmake -E > echo_append > cd /<>/obj-x86_64-linux-gnu/build-modules && /usr/bin/cmake -E > echo_append > cd /<>/obj-x86_64-linux-gnu/style-modules && /usr/bin/cmake -E > echo_append > [ 92%] sphinx-build html: see > /<>/obj-x86_64-linux-gnu/docs/docs/build-html.log > cd /<>/obj-x86_64-linux-gnu/docs && /usr/bin/sphinx-build -c > /<>/obj-x86_64-linux-gnu/docs -d > /<>/obj-x86_64-linux-gnu/docs/doctrees -b html > /<>/help /<>/obj-x86_64-linux-gnu/docs/html > > build-html.log > cd /<>/obj-x86_64-linux-gnu/build-modules && /usr/bin/cmake -E > echo_append > cd /<>/obj-x86_64-linux-gnu/build-modules && /usr/bin/cmake -E > echo_append > cd /<>/obj-x86_64-linux-gnu/style-modules && /usr/bin/cmake -E > echo_append > cd /<>/obj-x86_64-linux-gnu/style-modules && /usr/bin/cmake -E > echo_append > cd /<>/obj-x86_64-linux-gnu/build-modules && /usr/bin/cmake -E > echo_append > cd /<>/obj-x86_64-linux-gnu/style-modules && /usr/bin/cmake -E > echo_append > cd /<>/obj-x86_64-linux-gnu/build-modules && /usr/bin/cmake -E > echo_append > cd /<>/style-modules && /usr/bin/cmake -P > /<>/obj-x86_64-linux-gnu/style-modules/CMakeFiles/style-modules.dir/ycm_localinstall__a4831d43_8_files.cmake > cd /<>/obj-x86_64-linux-gnu/style-modules && /usr/bin/cmake -E > touch > /<>/obj-x86_64-linux-gnu/style-modules/CMakeFiles/style-modules.dir/ycm_localinstall-complete > cd /<>/build-modules && /usr/bin/cmake -P > /<>/obj-x86_64-linux-gnu/build-modules/CMakeFiles/build-modules.dir/ycm_localinstall__ee93a30a_11_files.cmake > cd /<>/obj-x86_64-linux-gnu/build-modules && /usr/bin/cmake -E > touch > /<>/obj-x86_64-linux-gnu/build-modules/CMakeFiles/build-modules.dir/ycm_localinstall-complete > [ 94%] Files from style-modules installed in CMake build directory > cd /<>/style-modules && /usr/bin/cmake -E touch > /<>/obj-x86_64-linux-gnu/style-modules/CMakeFiles/style-modules.dir/ycm_target-complete > make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu' > [ 94%] Built target style-modules > [ 97%] Files from build-modules installed in CMake build directory > cd /<>/build-modules && /usr/bin/cmake -E touch > /<>/obj-x86_64-linux-gnu/build-modules/CMakeFiles/build-modules.dir/ycm_target-complete > make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu' > [ 97%] Built target build-modules > > Extension error: > Could not import extension cmake (exception: cannot import name 'htmlescape' > from 'sphinx.util.pycompat' > (/usr/lib/python3/dist-packages/sphinx/util/pycompat.py)) > make[4]: *** [docs/CMakeFiles/documentation.dir/build.make:77: > docs/doc_format_html] Error 2 The full build log is available from: http://qa-logs.debian.net/2021/10/23/ycm-cmake-modules_0.13.0-1_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: ycm-cmake-modules Source-Version: 0.13.0-2 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of ycm-cmake-modules, 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
Bug#997408: marked as done (libatomic-queue: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Fri, 29 Oct 2021 14:48:49 + with message-id and subject line Bug#997408: fixed in libatomic-queue 0.0+git20201108.d9d66b6-4 has caused the Debian Bug report #997408, regarding libatomic-queue: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below 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.) -- 997408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libatomic-queue Version: 0.0+git20201108.d9d66b6-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_strip || true > strip: debian/libatomic-queue-dev/usr/lib/x86_64-linux-gnu/libatomic_queue.a: > sorry: copying thin archives is not currently supported: invalid operation > dh_strip: error: strip --strip-debug --remove-section=.comment > --remove-section=.note --enable-deterministic-archives -R .gnu.lto_\* -R > .gnu.debuglto_\* -N __gnu_lto_slim -N __gnu_lto_v1 > debian/libatomic-queue-dev/usr/lib/x86_64-linux-gnu/libatomic_queue.a > returned exit code 1 > dh_strip: error: Aborting due to earlier error > make[1]: Leaving directory '/<>' >dh_makeshlibs -a > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libatomic-queue0/DEBIAN/symbols doesn't > match completely debian/libatomic-queue0.symbols > --- debian/libatomic-queue0.symbols > (libatomic-queue0_0.0+git20201108.d9d66b6-3_amd64) > +++ dpkg-gensymbolsxSCnKw 2021-10-23 06:30:08.270896359 + > @@ -137,8 +137,8 @@ > > _ZNSt8__detail4_NFAINSt7__cxx1112regex_traitsIcEEE17_M_insert_matcherESt8functionIFbcEE@Base > 0.0+git20201007.df79403 > > _ZNSt8__detail4_NFAINSt7__cxx1112regex_traitsIcEEE21_M_insert_subexpr_endEv@Base > 0.0+git20201007.df79403 > > _ZNSt8__detail4_NFAINSt7__cxx1112regex_traitsIcEEE23_M_insert_subexpr_beginEv@Base > 0.0+git20201007.df79403 > - (optional=yes)_ZNSt8__detail6_StateIcEC1EOS1_@Base 0.0+git20201007.df79403 > - (optional=yes)_ZNSt8__detail6_StateIcEC2EOS1_@Base 0.0+git20201007.df79403 > +#MISSING: 0.0+git20201108.d9d66b6-3# > (optional=yes)_ZNSt8__detail6_StateIcEC1EOS1_@Base 0.0+git20201007.df79403 > +#MISSING: 0.0+git20201108.d9d66b6-3# > (optional=yes)_ZNSt8__detail6_StateIcEC2EOS1_@Base 0.0+git20201007.df79403 > _ZNSt8__detail8_ScannerIcE12_M_eat_classEc@Base 0.0+git20201007.df79403 > _ZNSt8__detail8_ScannerIcE14_M_scan_normalEv@Base 0.0+git20201007.df79403 > _ZNSt8__detail8_ScannerIcE16_M_scan_in_braceEv@Base 0.0+git20201007.df79403 > @@ -235,8 +235,8 @@ > > _ZZNKSt8__detail9_ExecutorIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS5_9sub_matchISB_EEENS5_12regex_traitsIcEELb0EE10_M_is_wordEcE3__s@Base > 0.0+git20201007.df79403 > > _ZZNKSt8__detail9_ExecutorIN9__gnu_cxx17__normal_iteratorIPKcNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcESaINS5_9sub_matchISB_EEENS5_12regex_traitsIcEELb1EE10_M_is_wordEcE3__s@Base > 0.0+git20201007.df79403 > _ZZNSt19_Sp_make_shared_tag5_S_tiEvE5__tag@Base 0.0+git20201007.df79403 > - > _ZZNSt8__detail9_CompilerINSt7__cxx1112regex_traitsIcEEE18_M_expression_termILb0ELb0EEEbRSt4pairIbcERNS_15_BracketMatcherIS3_XT_EXT0_NKUlcE_clEc@Base > 0.0+git20201108.d9d66b6 > - > _ZZNSt8__detail9_CompilerINSt7__cxx1112regex_traitsIcEEE18_M_expression_termILb0ELb1EEEbRSt4pairIbcERNS_15_BracketMatcherIS3_XT_EXT0_NKUlcE_clEc@Base > 0.0+git20201108.d9d66b6 > +#MISSING: 0.0+git20201108.d9d66b6-3# > _ZZNSt8__detail9_CompilerINSt7__cxx1112regex_traitsIcEEE18_M_expression_termILb0ELb0EEEbRSt4pairIbcERNS_15_BracketMatcherIS3_XT_EXT0_NKUlcE_clEc@Base > 0.0+git20201108.d9d66b6 > +#MISSING: 0.0+git20201108.d9d66b6-3# > _ZZNSt8__detail9_CompilerINSt7__cxx1112regex_traitsIcEEE18_M_expression_termILb0ELb1EEEbRSt4pairIbcERNS_15_BracketMatcherIS3_XT_EXT0_NKUlcE_clEc@Base > 0.0+git20201108.d9d66b6 > > _ZZNSt8__detail9_CompilerINSt7__cxx1112regex_traitsIcEEE18_M_expression_termILb1ELb0EEEbRSt4pairIbcERNS_15_BracketMatcherIS3_XT_EXT0_NKUlcE_clEc@Base > 0.0+git20201007.df79403 > > _ZZNSt8__detail9_CompilerINSt7__cxx1112regex_traitsIcEEE18_M_expression_termILb1ELb1EEEbRSt4pairIbcERNS_15_BracketMatcherIS3_XT_EXT0_NKUlcE_clEc@Base > 0.0+git20201007.df79403 >
Bug#997525: marked as done (r-cran-pscbs: FTBFS: path[1]="/sbuild-nonexistent": No such file or directory)
Your message dated Fri, 29 Oct 2021 20:14:48 +0530
with message-id <11ca5177-4910-abdf-4c62-b338cc51f...@nileshpatra.info>
and subject line Re: r-cran-pscbs: FTBFS: path[1]="/sbuild-nonexistent": No
such file or directory
has caused the Debian Bug report #997525,
regarding r-cran-pscbs: FTBFS: path[1]="/sbuild-nonexistent": No such file or
directory
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.)
--
997525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-pscbs
Version: 0.65.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> dpkg-buildpackage
> -
>
> Command: dpkg-buildpackage -us -uc -sa -rfakeroot
> dpkg-buildpackage: info: source package r-cran-pscbs
> dpkg-buildpackage: info: source version 0.65.0-3
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Andreas Tille
> dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
> debian/rules clean
> dh clean --buildsystem R
>dh_auto_clean -O--buildsystem=R
>dh_autoreconf_clean -O--buildsystem=R
>dh_clean -O--buildsystem=R
> dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building r-cran-pscbs using existing
> ./r-cran-pscbs_0.65.0.orig.tar.gz
> dpkg-source: info: building r-cran-pscbs in
> r-cran-pscbs_0.65.0-3.debian.tar.xz
> dpkg-source: info: building r-cran-pscbs in r-cran-pscbs_0.65.0-3.dsc
> debian/rules binary
> dh binary --buildsystem R
>dh_update_autotools_config -O--buildsystem=R
>dh_autoreconf -O--buildsystem=R
>dh_auto_configure -O--buildsystem=R
>dh_auto_build -O--buildsystem=R
>dh_auto_test -O--buildsystem=R
>create-stamp debian/debhelper-build-stamp
>dh_testroot -O--buildsystem=R
>dh_prep -O--buildsystem=R
>dh_auto_install --destdir=debian/r-cran-pscbs/ -O--buildsystem=R
> I: R packages needed for DEP8: aroma.light, hmisc, foreign, nnet
> I: R Package: PSCBS Version: 0.65.0
> I: Building using R version 4.1.1-2
> I: R API version: r-api-4.0
> I: Using built-time from d/changelog: Mon, 18 May 2020 11:36:12 +0200
> mkdir -p /<>/debian/r-cran-pscbs/usr/lib/R/site-library
> R CMD INSTALL -l
> /<>/debian/r-cran-pscbs/usr/lib/R/site-library --clean .
> "--built-timestamp='Mon, 18 May 2020 11:36:12 +0200'"
> * installing *source* package ‘PSCBS’ ...
> ** using staged installation
> ** R
> ** inst
> ** byte-compile and prepare package for lazy loading
> Warning in normalizePath("~") :
> path[1]="/sbuild-nonexistent": No such file or directory
> Error: .onLoad failed in loadNamespace() for 'R.cache', details:
> call: mkdirs.default(parent, mustWork = mustWork, maxTries = maxTries,
> error: Failed to create directory (tried 5 times), most likely because of
> lack of file permissions (directory '' exists but nothing beyond):
> /sbuild-nonexistent
> Execution halted
> ERROR: lazy loading failed for package ‘PSCBS’
> * removing ‘/<>/debian/r-cran-pscbs/usr/lib/R/site-library/PSCBS’
> dh_auto_install: error: R CMD INSTALL -l
> /<>/debian/r-cran-pscbs/usr/lib/R/site-library --clean .
> "--built-timestamp='Mon, 18 May 2020 11:36:12 +0200'" returned exit code 1
> make: *** [debian/rules:4: binary] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/r-cran-pscbs_0.65.0-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 ---
On Sat, 23 Oct 2021 22:56:40 +0200 Lucas Nussbaum wrote:
Source: r-cran-pscbs
Version: 0.65.0-3
It is building in the latest, so closing this (non?)bug.
https://buildd.debian.org/status/fetch.php?pkg=r-cran-pscbs=all=0.66.0-1=1635361120=0
Thanks a lot for the archive-wide rebuilds though, they are very helpful
Nilesh
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
Bug#994833: OpenCL programs abort when intel-opencl-icd is installed
Control: block -1 with 998058 Control: fixed -1 intel-graphics-compiler/1.0.8744-2 On 29/10/2021 16.33, Jonas Smedegaard wrote: Reopening, since seemingly the detail about coordinated upload is still missing: Currently (in sid) intel-opencl-icd is flagged breaking its own dependencies and therefore impossible to install. There is a new FTBFS (also in the unmodified package currently in sid) due to some failing tests, otherwise I would have uploaded the second part of the fix today :-( Andreas
Processed: Re: Bug#994833: OpenCL programs abort when intel-opencl-icd is installed
Processing control commands: > block -1 with 998058 Bug #994833 [intel-opencl-icd] OpenCL programs abort when intel-opencl-icd is installed 994833 was not blocked by any bugs. 994833 was not blocking any bugs. Added blocking bug(s) of 994833: 998058 > fixed -1 intel-graphics-compiler/1.0.8744-2 Bug #994833 [intel-opencl-icd] OpenCL programs abort when intel-opencl-icd is installed Marked as fixed in versions intel-graphics-compiler/1.0.8744-2. -- 994833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#997408 marked as pending in libatomicqueue
Processing control commands: > tag -1 pending Bug #997408 [src:libatomic-queue] libatomic-queue: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below Added tag(s) pending. -- 997408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997408 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997408: marked as pending in libatomicqueue
Control: tag -1 pending Hello, Bug #997408 in libatomicqueue 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/med-team/libatomic-queue/-/commit/75017e1bacb34b763cbac6184c80f9f5916c914e Fix symbols (Closes: #997408) (this message was generated automatically) -- Greetings https://bugs.debian.org/997408
Bug#995838: [htcondor-debian] Bug#995838: Should condor be removed?
I plan to upload a new version this weekend. -- Tim Theisen (he, him, his) Release Manager HTCondor & Open Science Grid Center for High Throughput Computing Department of Computer Sciences University of Wisconsin - Madison 4261 Computer Sciences and Statistics 1210 W Dayton St Madison, WI 53706-1685 +1 608 265 5736 From: htcondor-debian on behalf of Moritz Muehlenhoff Sent: Wednesday, October 6, 2021 12:01 PM To: Debian Bug Tracking System Subject: [htcondor-debian] Bug#995838: Should condor be removed? Source: condor Severity: serious condor came up as a candidate for removal from Debian: - Last upload was in 2018 - Three RC bugs, including various toolchain issues (GCC, Python 2) - Open security issues If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz ___ htcondor-debian mailing list htcondor-deb...@cs.wisc.edu https://lists.cs.wisc.edu/mailman/listinfo/htcondor-debian
Bug#997521: freedict: FTBFS: Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No such file or directory
Hi Due to the way the FreeDict stylesheets are written, a lot of memory is used. Could you provide the amount of RAM that is used for the failed build? If it is below 16G, could it be increased, somehow? Thanks Sebastian signature.asc Description: PGP signature
Bug#997886: marked as done (prottest: autopkgtest regression: Stats file does not exist)
Your message dated Fri, 29 Oct 2021 13:34:07 + with message-id and subject line Bug#997886: fixed in prottest 3.4.2+dfsg-7 has caused the Debian Bug report #997886, regarding prottest: autopkgtest regression: Stats file does not exist 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.) -- 997886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997886 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: prottest Version: 3.4.2+dfsg-6 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of prottest the autopkgtest of prottest fails in testing when that autopkgtest is run with the binary packages of prottest from unstable. It passes when run with only packages from testing. In tabular form: passfail prottest from testing3.4.2+dfsg-6 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=prottest https://ci.debian.net/data/autopkgtest/testing/amd64/p/prottest/16225046/log.gz - Basic usage: - Sequential version: java -jar prottest-3.4.2.jar -i align_file [OPTIONS] ./prottest3 -i align_file [OPTIONS] - Parallel version: mpjrun.sh -wdir $PWD/ -np [NUM_PROCS] -jar prottest-3.4.2.jar -i align_file [OPTIONS] OPTIONS: -i alignment_filename Alignment input file (required) -t tree_filename Tree file (optional) [default: NJ tree] -o output_filename Output file (optional) [default: standard output] -log enabled/disabled Enables / Disables PhyML logging into log directory (see prottest.properties) -[matrix] Include matrix (Amino-acid) = JTT LG DCMut MtREV MtMam MtArt Dayhoff WAG RtREV CpREV Blosum62 VT HIVb HIVw FLU If you don't specify any matrix, all matrices displayed above will be included. -I Include models with a proportion of invariable sites -G Include models with rate variation among sites and number of categories -IG include models with both +I and +G properties -all-distributions Include models with rate variation among sites, number of categories and both -ncat number_of_categories Define number of categories for +G and +I+G models [default: 4] -F Include models with empirical frequency estimation -AIC Display models sorted by Akaike Information Criterion (AIC) -BIC Display models sorted by Bayesian Information Criterion (BIC) -AICC Display models sorted by Corrected Akaike Information Criterion (AICc) -DT Display models sorted by Decision Theory Criterion -all Displays a 7-framework comparison table -S optimization_strategy Optimization strategy mode: [default: 0] 0: Fixed BIONJ JTT 1: BIONJ Tree 2: Maximum Likelihood tree 3: User defined topology -s moves Tree search operation for ML search: NNI (fastest), SPR (slowest), BEST (best of NNI and SPR) [default: NNI] -t1 Display best-model's newick tree [default: false] -t2 Display best-model's ASCII tree [default: false] -tc consensus_threshold Display consensus tree with the specified threshold, between 0.5 and 1.0 [0.5 = majority rule consensus ; 1.0 = strict consensus] -threads number_or_threads Number of threads requested to compute (only if MPJ is not used) [default: 1] -verbose Verbose mode [default: false] - Example: - Sequential version: java -jar prottest-3.4.2.jar -i align_file -t tree_file -S 0 -all-distributions -F -AIC -BIC -tc 0.5 > output - Parallel version: mpjrun.sh -wdir $PWD/ -np 2
Bug#997886: marked as pending in prottest
Control: tag -1 pending Hello, Bug #997886 in prottest 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/med-team/prottest/-/commit/fa47ffe07086565dba469982f81d35d04a2b40e4 Add patch to fix autopkgtests (Closes: #997886) (this message was generated automatically) -- Greetings https://bugs.debian.org/997886
Processed: Bug#997886 marked as pending in prottest
Processing control commands: > tag -1 pending Bug #997886 [src:prottest] prottest: autopkgtest regression: Stats file does not exist Added tag(s) pending. -- 997886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997886 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997473: marked as done (swupdate: FTBFS: dpkg-checkbuilddeps: error: Unmet build dependencies: latexmk:native)
Your message dated Fri, 29 Oct 2021 13:04:26 + with message-id and subject line Bug#997473: fixed in swupdate 2021.04-1.1 has caused the Debian Bug report #997473, regarding swupdate: FTBFS: dpkg-checkbuilddeps: error: Unmet build dependencies: latexmk:native 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.) -- 997473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: swupdate Version: 2021.04-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > Command: dpkg-buildpackage -us -uc -sa -rfakeroot > dpkg-buildpackage: info: source package swupdate > dpkg-buildpackage: info: source version 2021.04-1 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by SZ Lin (林上智) > dpkg-source --before-build . > dpkg-buildpackage: info: host architecture amd64 > dpkg-checkbuilddeps: error: Unmet build dependencies: latexmk:native > dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting > dpkg-buildpackage: warning: (Use -d flag to override.) > > Build finished at 2021-10-23T06:31:56Z The full build log is available from: http://qa-logs.debian.net/2021/10/23/swupdate_2021.04-1_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: swupdate Source-Version: 2021.04-1.1 Done: Bastian Germann We believe that the bug you reported is fixed in the latest version of swupdate, 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. Bastian Germann (supplier of updated swupdate 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, 24 Oct 2021 13:34:27 +0200 Source: swupdate Architecture: source Version: 2021.04-1.1 Distribution: unstable Urgency: medium Maintainer: Stefano Babic Changed-By: Bastian Germann Closes: 997473 Changes: swupdate (2021.04-1.1) unstable; urgency=medium . * Non-maintainer upload * Remove deprecated Salsa CI config * latexmk without :native is alternative build dependency (Closes: #997473) * Add tex-gyre build dependency Checksums-Sha1: 231c9c77bd80d9f0716d1b281fcfd2e260f26b77 2845 swupdate_2021.04-1.1.dsc 12e7e17b8b1dbd6e779df1fe5ef4fe361d6d10d7 131632 swupdate_2021.04-1.1.debian.tar.xz 2c0b384331d49781fe76c338d949f43ec4367841 10995 swupdate_2021.04-1.1_source.buildinfo Checksums-Sha256: 2c630b6d3de80f06dfcebe00f3eee4b30fdebb36c4bab5aa3ba879b0ef703581 2845 swupdate_2021.04-1.1.dsc e3241badacd3ffc4de0ceabdf7a9e339be8015fea85d0082140d9d32026dbc4f 131632 swupdate_2021.04-1.1.debian.tar.xz fc1285f8ae497985893eb89aab9ca8ba4d2d1f5dfb0a7ef9e37f2abfbe1c3450 10995 swupdate_2021.04-1.1_source.buildinfo Files: 02936e3581fbd911769f4f72b715ce59 2845 embedded optional swupdate_2021.04-1.1.dsc efd9c64bacffecdfeaf3f8bbfeb0f76a 131632 embedded optional swupdate_2021.04-1.1.debian.tar.xz f79ba847b0f184cd3a0a2baadb426eb9 10995 embedded optional swupdate_2021.04-1.1_source.buildinfo -BEGIN PGP SIGNATURE- iQGzBAEBCgAdFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmF1TwoACgkQH1x6i0VW QxQGAgwA3GCQQmQvOy7+FgxqR5P75rfXa1PBjLWfSaBItbzqhahxJH/omGNtpYOR QlCPvEHrGF9eNcFHNS4RH0JR2DTPrNifR8jbkRPzTjYxAjg2w2cmUkUwFIvUgWMq EwC2GRQi3q2v20qGzwf73kFYO29aqSUTMYbRuP4FDHXYmKIKdl1dlEjq2MV6uDhJ WckZ11efxf2i586IIIqzwGpe4a44TiFn4MyvhfHr2bQRPHIl9AR/1xooI6N5wm+o
Bug#997175: marked as done (mgt: FTBFS: ascii.c:633:10: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Fri, 29 Oct 2021 07:41:09 -0500 with message-id <2323037.WGsR5YFZW9@riemann> and subject line Re: mgt: FTBFS: ascii.c:633:10: error: format not a string literal and no format arguments [-Werror=format-security] has caused the Debian Bug report #997175, regarding mgt: FTBFS: ascii.c:633:10: error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 997175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mgt Version: 2.31-7 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): > cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -DMGT_UNIX > -DMGT_LIB=\"/usr/lib/games/mgt/\" -c -o ascii.o ascii.c > ascii.c: In function ‘helpAscii’: > ascii.c:633:10: error: format not a string literal and no format arguments > [-Werror=format-security] > 633 | printw(edhelp[i]); > | ^~ > ascii.c: At top level: > ascii.c:1260:1: warning: return type defaults to ‘int’ [-Wimplicit-int] > 1260 | getInfoToChange() > | ^~~ > ascii.c: In function ‘getInfoToChange’: > ascii.c:1263:11: warning: type defaults to ‘int’ in declaration of ‘flag’ > [-Wimplicit-int] > 1263 |static flag = 0; > | ^~~~ > cc1: some warnings being treated as errors > make[1]: *** [Makefile:96: ascii.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/mgt_2.31-7_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 --- On Sat, 23 Oct 2021 21:07:07 +0200 Lucas Nussbaum wrote: > Source: mgt > Version: 2.31-7 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. build fixed signature.asc Description: This is a digitally signed message part. --- End Message ---
Processed: Re: Bug#994833: OpenCL programs abort when intel-opencl-icd is installed
Processing control commands:
> reopen -1
Bug #994833 {Done: Timo Aaltonen } [intel-opencl-icd]
OpenCL programs abort when intel-opencl-icd is installed
'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 intel-graphics-compiler/1.0.8744-2.
--
994833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#994833: OpenCL programs abort when intel-opencl-icd is installed
Control: reopen -1 Andreas Beckmann wrote: > Commits are pushed to both packages in git, they need a coordinated > upload due to the Depends/Breaks added. Reopening, since seemingly the detail about coordinated upload is still missing: Currently (in sid) intel-opencl-icd is flagged breaking its own dependencies and therefore impossible to install. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#996387: FTBFS - also with ruby 2.7.4
Hi.
I get the same "rpc/rpc.h" error while rebuilding against (at least
essentially) debian-testing and ruby 2.7.4.
gcc -fdebug-prefix-map=/<>=. -I.
-I/usr/include/x86_64-linux-gnu/ruby-2.7.0
-I/usr/include/ruby-2.7.0/ruby/backward -I/usr/include/ruby-2.7.0 -I.
-Wdate-time -D_FORTIFY_SOURCE=2 -I../../include -I../../src/os/linux
-U_FILE_OFFSET_BITS -DRB_HAS_RE_ERROR -DRB_RUBY_19 -fPIC -g -O2
-ffile-prefix-map=/build/ruby2.7-5goTBM/ruby2.7-2.7.4=.
-fstack-protector-strong -Wformat -Werror=format-security -fPIC -o
sigar_util.o -c sigar_util.c
sigar_util.c: In function ‘sigar_proc_list_procfs_get’:
sigar_util.c:167:5: warning: ‘readdir_r’ is deprecated
[-Wdeprecated-declarations]
167 | while (readdir_r(dirp, , ) == 0) {
| ^
In file included from sigar_util.c:31:
/usr/include/dirent.h:183:12: note: declared here
183 | extern int readdir_r (DIR *__restrict __dirp,
|^
sigar_util.c: In function ‘sigar_proc_fd_count’:
sigar_util.c:210:5: warning: ‘readdir_r’ is deprecated
[-Wdeprecated-declarations]
210 | while (readdir_r(dirp, , ) == 0) {
| ^
In file included from sigar_util.c:31:
/usr/include/dirent.h:183:12: note: declared here
183 | extern int readdir_r (DIR *__restrict __dirp,
|^
sigar_util.c: At top level:
sigar_util.c:742:10: fatal error: rpc/rpc.h: No such file or directory
742 | #include
| ^~~
compilation terminated.
make[1]: *** [Makefile:245: sigar_util.o] Error 1
+--+
| Build environment
|
+--+
Kernel: Linux 5.10.40-1-amd64 #1 SMP Debian 5.10.40-1 (2021-06-22) amd64
(x86_64)
Toolchain package versions: binutils_2.37-7 dpkg-dev_1.20.9
g++-10_10.3.0-11 gcc-10_10.3.0-11 libc6-dev_2.32-4
libstdc++-10-dev_10.3.0-11 libstdc++6_11.2.0-9 linux-libc-dev_5.10.46-5
Package versions: adduser_3.118 apt_2.3.11 autoconf_2.71-2
automake_1:1.16.4-2 autopoint_0.21-4 autotools-dev_20180224.1+nmu1
base-files_12 base-passwd_3.5.52 bash_5.1-3 binutils_2.37-7
binutils-common_2.37-7 binutils-x86-64-linux-gnu_2.37-7
bsdextrautils_2.37.2-3 bsdutils_1:2.37.2-3 build-essential_12.9
bzip2_1.0.8-4 ca-certificates_20210119 coreutils_8.32-4 cpp_4:10.2.1-1
cpp-10_10.3.0-11 dash_0.5.11+git20210120+802ebd4-1 debconf_1.5.77
debhelper_13.5.2 debian-archive-keyring_2021.1.1 debianutils_4.11.2
devscripts_2.21.4 dh-autoreconf_20 dh-strip-nondeterminism_1.12.0-2
diffutils_1:3.7-5 dirmngr_2.2.27-2 dpkg_1.20.9 dpkg-dev_1.20.9 dwz_0.14-1
e2fsprogs_1.46.4-1 eatmydata_130-2 fakeroot_1.25.3-1.1 file_1:5.39-3
findutils_4.8.0-1 g++_4:10.2.1-1 g++-10_10.3.0-11 gcc_4:10.2.1-1
gcc-10_10.3.0-11 gcc-10-base_10.3.0-11 gcc-11-base_11.2.0-9
gcc-8-base_8.4.0-7+build1 gcc-9-base_9.4.0-2 gem2deb_1.6
gem2deb-test-runner_1.6 gettext_0.21-4 gettext-base_0.21-4 gnupg_2.2.27-2
gnupg-l10n_2.2.27-2 gnupg-utils_2.2.27-2 goobuntu-base_29 gpg_2.2.27-2
gpg-agent_2.2.27-2 gpg-wks-client_2.2.27-2 gpg-wks-server_2.2.27-2
gpgconf_2.2.27-2 gpgsm_2.2.27-2 gpgv_2.2.27-2 grep_3.7-1
groff-base_1.22.4-7 gzip_1.10-4 hostname_3.23 init-system-helpers_1.60
intltool-debian_0.35.0+20060710.5 libacl1_2.3.1-1 libapt-pkg6.0_2.3.11
libarchive-zip-perl_1.68-1 libasan6_11.2.0-9 libassuan0_2.5.5-1
libatomic1_11.2.0-9 libattr1_1:2.5.1-1 libaudit-common_1:3.0.6-1
libaudit1_1:3.0.6-1 libb-hooks-op-check-perl_0.22-1 libbinutils_2.37-7
libblkid1_2.37.2-3 libboost-filesystem1.74.0_1.74.0-9
libboost-iostreams1.74.0_1.74.0-9 libboost-program-options1.74.0_1.74.0-9
libbsd0_0.11.3-1 libbz2-1.0_1.0.8-4 libc-bin_2.32-4 libc-dev-bin_2.32-4
libc6_2.32-4 libc6-dev_2.32-4 libcap-ng0_0.7.9-2.2 libcap2_1:2.44-1
libcc1-0_11.2.0-9 libclass-method-modifiers-perl_2.13-1
libcom-err2_1.46.4-1 libcrypt-dev_1:4.4.25-2 libcrypt1_1:4.4.25-2
libctf-nobfd0_2.37-7 libctf0_2.37-7 libdb5.3_5.3.28+dfsg1-0.8
libdebconfclient0_0.260 libdebhelper-perl_13.5.2
libdevel-callchecker-perl_0.008-1 libdpkg-perl_1.20.9
libdynaloader-functions-perl_0.003-1.1 libeatmydata1_130-2
libedit2_3.1-20210910-1 libelf1_0.185-2 libencode-locale-perl_1.05-1.1
libexpat1_2.4.1-2 libext2fs2_1.46.4-1 libfakeroot_1.25.3-1.1
libffi8_3.4.2-2 libfile-dirlist-perl_0.05-2 libfile-homedir-perl_1.006-1
libfile-listing-perl_6.14-1 libfile-stripnondeterminism-perl_1.12.0-2
libfile-touch-perl_0.12-1 libfile-which-perl_1.23-1 libgcc-10-dev_10.3.0-11
libgcc-s1_11.2.0-9 libgcrypt20_1.9.4-3 libgdbm-compat4_1.22-1
libgdbm6_1.22-1 libgmp-dev_2:6.2.1+dfsg-2 libgmp10_2:6.2.1+dfsg-2
libgmpxx4ldbl_2:6.2.1+dfsg-2 libgnutls30_3.7.2-2 libgomp1_11.2.0-9
libgpg-error0_1.42-3 libgssapi-krb5-2_1.18.3-7 libhogweed6_3.7.3-1
libhtml-parser-perl_3.76-1 libhtml-tagset-perl_3.20-4
libhtml-tree-perl_5.07-2 libhttp-cookies-perl_6.10-1
libhttp-date-perl_6.05-1 libhttp-message-perl_6.33-1
libhttp-negotiate-perl_6.01-1 libicu67_67.1-7 libidn2-0_2.3.2-2
libimport-into-perl_1.002005-1 libio-html-perl_1.004-2
Bug#998016: marked as done (liburdfdom-tools3.0: missing Breaks+Replaces: liburdfdom-tools (<< 3))
Your message dated Fri, 29 Oct 2021 11:34:41 + with message-id and subject line Bug#998016: fixed in urdfdom 3.0.0+ds-2 has caused the Debian Bug report #998016, regarding liburdfdom-tools3.0: missing Breaks+Replaces: liburdfdom-tools (<< 3) 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.) -- 998016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: liburdfdom-tools3.0 Version: 3.0.0+ds-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. This error may also be triggered by having a predecessor package from 'sid 'installed while installing the package from 'experimental'. 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 .../liburdfdom-tools3.0_3.0.0+ds-1_amd64.deb ... Unpacking liburdfdom-tools3.0 (3.0.0+ds-1) ... dpkg: error processing archive /var/cache/apt/archives/liburdfdom-tools3.0_3.0.0+ds-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/check_urdf', which is also in package liburdfdom-tools 1.0.4+ds-5 Errors were encountered while processing: /var/cache/apt/archives/liburdfdom-tools3.0_3.0.0+ds-1_amd64.deb cheers, Andreas liburdfdom-tools=1.0.4+ds-5_liburdfdom-tools3.0=3.0.0+ds-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: urdfdom Source-Version: 3.0.0+ds-2 Done: Jose Luis Rivero We believe that the bug you reported is fixed in the latest version of urdfdom, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jose Luis Rivero (supplier of updated urdfdom 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: Fri, 29 Oct 2021 11:08:44 + Source: urdfdom Architecture: source Version: 3.0.0+ds-2 Distribution: experimental Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Jose Luis Rivero Closes: 998016 Changes: urdfdom (3.0.0+ds-2) experimental; urgency=medium . [ Jochen Sprickerhof ] * Drop superfluous dependencies . [ Jose Luis Rivero ] * Add Replaces+Break for liburdfdom-tools (Closes: #998016) Checksums-Sha1: 17bc50c531d892f6599ededd8030b1dc1aace929 2169 urdfdom_3.0.0+ds-2.dsc dcd71cc0450bffc88d2968e19619c2805db5932c 4548 urdfdom_3.0.0+ds-2.debian.tar.xz 50da6d35d23ee6b00a2683610253a0cb595fbd78 6186 urdfdom_3.0.0+ds-2_source.buildinfo Checksums-Sha256: 42d943b3e824929dbdbdf1cf1c8480cb9624821434dce70480bc55e043e4c286 2169 urdfdom_3.0.0+ds-2.dsc 1eeeb2c2bf703790d2ba13711c258551e085a193e7bc9c384397e16d22d78abe 4548 urdfdom_3.0.0+ds-2.debian.tar.xz 62aee2948abfd3579407f8cf4e3d71c94e7f0aee5d8c33278d76401a0228561b 6186 urdfdom_3.0.0+ds-2_source.buildinfo Files: 3d7521e9202877a2f949f907e007c41d 2169 libs optional urdfdom_3.0.0+ds-2.dsc 24d6931b93207a0a983933711484480b 4548 libs optional urdfdom_3.0.0+ds-2.debian.tar.xz c63ae054e955dd6b33ffd2b75fdb78ca 6186 libs optional urdfdom_3.0.0+ds-2_source.buildinfo -BEGIN PGP SIGNATURE- iQFOBAEBCgA4FiEEoIFhu+wcwGOWFFkDXpRsCQr/BCcFAmF7174aHGpyaXZlcm9A b3NyZm91bmRhdGlvbi5vcmcACgkQXpRsCQr/BCc1kQgA01uyaeypyMxObCEQrWs4 4NjSxkE80YJrLJovFB3SQZhogEUbeXI4usw7ZFf6Z8rnsOQ8TghuWFV2rD0w0euy sE2bvY7ypVXtM2Yh0GxftjaPgT7B7sihProANZZcd1ZGkktW+UWScXcQaYdX44ff s+3WMJZilkT9XxtmS0oxkE+NLhA/yc1U6A7HfcKgSbXbNNnHPI1go290XIlSxH0U D1BWaRVfYm66B/AXQFWG2/sBED9zbz95+QXntHimUlOjclaIDZmNh/uE8NEQsNZL 77+cf6buZLRebEhZFQyeOae65B+QlRgusCO/N6UTrusILwusAVjD6TfOVb7hyVmz HQ== =nnPJ -END PGP SIGNATURE End Message ---
Bug#997210: marked as done (binutils-m68hc1x: FTBFS: configure.ac:34: error: Please use exactly Autoconf 2.69 instead of 2.71.)
Your message dated Fri, 29 Oct 2021 13:26:01 +0200 with message-id and subject line binutils-m68hc1x has caused the Debian Bug report #997210, regarding binutils-m68hc1x: FTBFS: configure.ac:34: error: Please use exactly Autoconf 2.69 instead of 2.71. 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.) -- 997210: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997210 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: binutils-m68hc1x Version: 1:2.35.1-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): > DC-Build-Header: binutils-m68hc1x 1:2.35.1-3 / 2021-10-23 06:30:28 + > DC-Task: type:rebuild-full source:binutils-m68hc1x version:1:2.35.1-3 > chroot:unstable esttime: logfile:/tmp/binutils-m68hc1x_2.35.1-3_unstable.log > modes: > DC-Sbuild-call: su user42 -c 'sbuild -n -A -s --force-orig-source > --apt-update -d unstable -v --no-run-lintian binutils-m68hc1x_1:2.35.1-3' > sbuild (Debian sbuild) 0.78.1 (09 February 2019) on > ip-172-31-2-128.eu-central-1.compute.internal > > +==+ > | binutils-m68hc1x 1:2.35.1-3 (amd64) Sat, 23 Oct 2021 06:30:28 > + | > +==+ > > Package: binutils-m68hc1x > Version: 1:2.35.1-3 > Source Version: 1:2.35.1-3 > Distribution: unstable > Machine Architecture: amd64 > Host Architecture: amd64 > Build Architecture: amd64 > Build Type: full > > I: NOTICE: Log filtering will replace > 'var/run/schroot/mount/sid-amd64-sbuild-ecc83b14-9ae3-4a75-ab21-c1f106e104ee' > with '<>' > I: NOTICE: Log filtering will replace > 'build/binutils-m68hc1x-T32Nbq/resolver-w3pBRi' with '<>' > > +--+ > | Update chroot > | > +--+ > > Get:1 http://127.0.0.1:12990/debian sid InRelease [165 kB] > Get:2 http://127.0.0.1:12990/debian sid/main Sources.diff/Index [63.6 kB] > Get:3 http://127.0.0.1:12990/debian sid/main amd64 Packages.diff/Index [63.6 > kB] > Get:4 http://127.0.0.1:12990/debian sid/main Sources > T-2021-10-23-0205.55-F-2021-10-22-2010.35.pdiff [26.7 kB] > Get:4 http://127.0.0.1:12990/debian sid/main Sources > T-2021-10-23-0205.55-F-2021-10-22-2010.35.pdiff [26.7 kB] > Get:5 http://127.0.0.1:12990/debian sid/main amd64 Packages > T-2021-10-23-0205.55-F-2021-10-22-2010.35.pdiff [34.5 kB] > Get:5 http://127.0.0.1:12990/debian sid/main amd64 Packages > T-2021-10-23-0205.55-F-2021-10-22-2010.35.pdiff [34.5 kB] > Fetched 353 kB in 2s (148 kB/s) > Reading package lists... > Reading package lists... > Building dependency tree... > Calculating upgrade... > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > +--+ > | Fetch source files > | > +--+ > > > Check APT > - > > Checking available source versions... > > Download source files with APT > -- > > Reading package lists... > NOTICE: 'binutils-m68hc1x' packaging is maintained in the 'Git' version > control system at: > https://salsa.debian.org/VSmeets/binutils-m68hc1x.git > Please use: > git clone https://salsa.debian.org/VSmeets/binutils-m68hc1x.git > to retrieve the latest (possibly unreleased) updates to the package. > Need to get 22.1 MB of source archives. > Get:1 http://127.0.0.1:12990/debian sid/main binutils-m68hc1x 1:2.35.1-3 > (dsc) [2267 B] > Get:2 http://127.0.0.1:12990/debian sid/main binutils-m68hc1x 1:2.35.1-3 > (tar) [22.0 MB] > Get:3 http://127.0.0.1:12990/debian sid/main binutils-m68hc1x 1:2.35.1-3 > (asc) [833 B] > Get:4 http://127.0.0.1:12990/debian sid/main binutils-m68hc1x 1:2.35.1-3 > (diff) [91.5 kB] > Fetched 22.1 MB in 1s (32.7 MB/s) > Download complete and in download only mode > I: NOTICE: Log filtering will replace > 'build/binutils-m68hc1x-T32Nbq/binutils-m68hc1x-2.35.1' with '<>' > I: NOTICE: Log filtering will replace 'build/binutils-m68hc1x-T32Nbq' with > '<>' > > +--+ > | Install package build dependencies
Bug#984134: fluxbox: ftbfs with GCC-11
Hi, * Matthias Klose [Wed Mar 03, 2021 at 04:12:26PM +]: > Package: src:fluxbox > Version: 1.3.5-2 > Severity: normal > Tags: sid bookworm > User: debian-...@lists.debian.org > Usertags: ftbfs-gcc-11 > > [This bug is not targeted to the upcoming bullseye release] [...] Is the fluxbox package actually still maintained by you, Dmitry and/or Paul? The latest upload to Debian seems to date back to 2015, targeting experimental, and we still have only v1.3.5 in oldoldoldstable up to unstable, while fluxbox is completely missing in Debian/testing (upcoming bookworm) due to #984134 nowadays. Looking at http://git.fluxbox.org/fluxbox.git/, upstream seems to be still around, so it might be worth forwarding this ftbfs bug towards https://sourceforge.net/p/fluxbox/bugs/ as a starting point? regards -mika- signature.asc Description: PGP signature
Processed: Reduce severity
Processing commands for cont...@bugs.debian.org: > severity #994057 important Bug #994057 [libegl-mesa0] libegl-mesa0: 21.2.1-2 with intel graphic card produces artifact on firefox-esr Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 994057: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997198: marked as done (gnomint: FTBFS: gthread.h:129:37: error: extra brace group at end of initializer)
Your message dated Fri, 29 Oct 2021 09:18:51 +
with message-id
and subject line Bug#997198: fixed in gnomint 1.3.0-4
has caused the Debian Bug report #997198,
regarding gnomint: FTBFS: gthread.h:129:37: error: extra brace group at end of
initializer
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.)
--
997198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnomint
Version: 1.3.0-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):
> gcc -DPACKAGE_NAME=\"gnoMint\" -DPACKAGE_TARNAME=\"gnomint\"
> -DPACKAGE_VERSION=\"1.3.0\" -DPACKAGE_STRING=\"gnoMint\ 1.3.0\"
> -DPACKAGE_BUGREPORT=\"\\" -DPACKAGE_URL=\"\"
> -DPACKAGE_COPYRIGHT=\"\(c\)\ 2006-2016\ David\ Marín\ Carreño\
> \\" -DPACKAGE_WEBSITE=\"http://gnomint.sourceforge.net\;
> -DPACKAGE_AUTHORS=\"David\ Marín\ Carreño\ \\\nAhmed\
> Baizid\ \\\nJaroslav\ Imrich\ \\\nStaněk\
> Luboš\ \\" -DPACKAGE=\"gnomint\"
> -DVERSION=\"1.3.0\" -DHAVE_STDIO_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
> -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_STRINGS_H=1 -DHAVE_SYS_STAT_H=1
> -DHAVE_SYS_TYPES_H=1 -DHAVE_UNISTD_H=1 -DHAVE_SYS_TIME_H=1 -DSTDC_HEADERS=1
> -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_LIBINTL_H=1 -DHAVE_LOCALE_H=1
> -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MALLOC=1 -DHAVE_ALARM=1
> -DHAVE_STRFTIME=1 -DHAVE_MEMSET=1 -DHAVE_STRCASECMP=1 -DHAVE_STRDUP=1
> -DGETTEXT_PACKAGE=\"gnomint\"
> -DBONOBO_EXPLICIT_TRANSLATION_DOMAIN=\"gnomint\" -DHAVE_LOCALE_H=1
> -DHAVE_LC_MESSAGES=1 -DHAVE_BIND_TEXTDOMAIN_CODESET=1 -DHAVE_GETTEXT=1
> -DHAVE_DCGETTEXT=1 -DENABLE_NLS=1 -DPACKAGE_LOCALE_DIR=\"/usr/share/locale\"
> -DADVANCED_GNUTLS=\"yes\" -I. -Wdate-time -D_FORTIFY_SOURCE=2 -I.. -I..
> -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0
> -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0
> -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0
> -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi
> -I/usr/include/harfbuzz -I/usr/include/atk-1.0 -I/usr/include/cairo
> -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2
> -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16
> -I/usr/include/x86_64-linux-gnu -I/usr/include/libmount -I/usr/include/blkid
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
> -I/usr/include/p11-kit-1-DPACKAGE_DATA_DIR=\""/usr/share"\"
> -DCOMPILATION_DATE=`date +%s` -DHAVE_CONFIG_H -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -c -o gnomint-tls.o `test -f 'tls.c' || echo
> './'`tls.c
> In file included from /usr/include/glib-2.0/glib/deprecated/gthread.h:124,
> from /usr/include/glib-2.0/glib.h:112,
> from ca_creation.h:23,
> from ca_creation.c:20:
> /usr/include/glib-2.0/glib/deprecated/gthread.h:129:37: error: extra brace
> group at end of initializer
> 129 | #define G_STATIC_MUTEX_INIT { NULL, PTHREAD_MUTEX_INITIALIZER }
> GLIB_DEPRECATED_MACRO_IN_2_32_FOR(g_mutex_init)
> | ^
> ca_creation.c:32:49: note: in expansion of macro ‘G_STATIC_MUTEX_INIT’
>32 | static GMutex ca_creation_thread_status_mutex = G_STATIC_MUTEX_INIT;
> | ^~~
> /usr/include/glib-2.0/glib/deprecated/gthread.h:129:37: note: (near
> initialization for ‘ca_creation_thread_status_mutex’)
> 129 | #define G_STATIC_MUTEX_INIT { NULL, PTHREAD_MUTEX_INITIALIZER }
> GLIB_DEPRECATED_MACRO_IN_2_32_FOR(g_mutex_init)
> | ^
> ca_creation.c:32:49: note: in expansion of macro ‘G_STATIC_MUTEX_INIT’
>32 | static GMutex ca_creation_thread_status_mutex = G_STATIC_MUTEX_INIT;
> | ^~~
> /usr/include/glib-2.0/glib/deprecated/gthread.h:129:37: error: extra brace
> group at end of initializer
> 129 | #define G_STATIC_MUTEX_INIT { NULL, PTHREAD_MUTEX_INITIALIZER }
> GLIB_DEPRECATED_MACRO_IN_2_32_FOR(g_mutex_init)
> | ^
> ca_creation.c:32:49: note: in expansion of macro ‘G_STATIC_MUTEX_INIT’
>32 | static GMutex
Bug#998058: intel-compute-runtime: FTBFS due to 2 failing tests
Source: intel-compute-runtime Version: 21.32.20609-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, while trying to rebuild the package with my llvm dependency updates (#994833), I noticed that it does FTBFS with some failing tests now: ./opencl/test/unit_test/kernel/kernel_arg_info_tests.cpp:157: Failure Expected equality of these values: 0 result Which is: -12 [ FAILED ][ RKL ][ 84512 ] KernelArgInfoTest.GivenParamWhenGettingKernelTypeNameThenCorrectValueIsReturned ./opencl/test/unit_test/kernel/kernel_tests.cpp:423: Failure Value of: pKernelInfo->getArgDescriptorAt(0).isReadOnly() Actual: false Expected: true [ FAILED ][ TGLLP ][ 84530 ] KernelFromBinaryTests.givenArgumentDeclaredAsConstantWhenKernelIsCreatedThenArgumentIsMarkedAsReadOnly The tests seem to fail several times in different scenarios, full build log (rebuilding the unmodified -1 from sid in sid) attached. Andreas intel-compute-runtime_21.32.20609-1.sid.build.xz Description: application/xz
Bug#996442: marked as done (src:aspell-hr: fails to migrate to testing for too long: uploader built arch:all)
Your message dated Fri, 29 Oct 2021 08:34:19 + with message-id and subject line Bug#996442: fixed in aspell-hr 0.51-6.1 has caused the Debian Bug report #996442, regarding src:aspell-hr: fails to migrate to testing for too long: uploader built arch:all 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.) -- 996442: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996442 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: aspell-hr Version: 0.51-5 Severity: serious Control: close -1 0.51-6 X-Debbugs-CC: jel...@debian.org Tags: sid bookworm pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:aspell-hr has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=aspell-hr OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: aspell-hr Source-Version: 0.51-6.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of aspell-hr, 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 996...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated aspell-hr 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: Thu, 14 Oct 2021 09:00:56 +0200 Source: aspell-hr Architecture: source Version: 0.51-6.1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Paul Gevers Closes: 996442 Changes: aspell-hr (0.51-6.1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #996442) Checksums-Sha1: c63144970aaf7aecc3d72836ae1f00ea8637c8c3 1676 aspell-hr_0.51-6.1.dsc 4d0c7b7214f47d024f4737731589422b29ddbeb6 4312 aspell-hr_0.51-6.1.debian.tar.xz Checksums-Sha256: a97ef426ad17bb3e5d2f594f20fd5b51bb79f8210d2d01b12491b6a0372c8f6a 1676 aspell-hr_0.51-6.1.dsc 88b6582a100dbaa7eec12e527b8fc753fdc9d235233707c6a844153348cffc19 4312 aspell-hr_0.51-6.1.debian.tar.xz Files: 7d474b50484e0930c862718f5f8c8e6f 1676 text optional aspell-hr_0.51-6.1.dsc 5a263188b95adc506ded1fb8ad6616ad 4312 text optional aspell-hr_0.51-6.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmFn1cwACgkQnFyZ6wW9 dQrswgf/Xy+8egZDecyfthB2KzjtNutN7bE7s0mzytbhO5pYQHjeEIm26cRNOCsp He+67t+VZNj8t0JSr4dn+gssZWF/PLFQ5wnr9qdwCumhiydxYUs5P+vrvCaLvk3R tEIZzknVqOK4nSmo+3Q+NKfbT9s58yzEIuEqJc8JiwbOkTcuAh2w0y5Xa49Nj8h/ 8fu71jcboiFIGR+X87fvd11DAGCteQEuF7q5gu3KcY0Wz6e5FuEuofuA3vRu6ULl wsHLG5Jcjw/hU/wQGjmTXB2eGtKMQK9REX+D34W+KgMtJtdxAmKiGuyFKboc+qoN +zGMX2swGVuiAbcl7cQzUjq7zhTFBQ== =HzZ7 -END PGP
Bug#984093: libcifpp_1.0.1-4_amd64.changes REJECTED
Am Fri, Oct 29, 2021 at 08:06:07AM +0200 schrieb Maarten L. Hekkelman: > See: https://www.wwpdb.org/about/usage-policies > > Now, if you look at the text of this license, it is huge. Should that really > go into the debian/copyright file? Yes, the length of the text does not matter. If you find it on some web page something like lynx -dump > copyright.tmp vi copyright.tmp remove some lines :s/^/ / :s/^[[:space:]]*$/ ./ comes very handy to bring the text into the required shape. Kind regards Andreas. -- http://fam-tille.de
Bug#984044: marked as done (dx: ftbfs with GCC-11)
Your message dated Fri, 29 Oct 2021 07:33:55 +
with message-id
and subject line Bug#984044: fixed in dx 1:4.4.4-14
has caused the Debian Bug report #984044,
regarding dx: ftbfs with GCC-11
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.)
--
984044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984044
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:dx
Version: 1:4.4.4-13
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11
[This bug is not targeted to the upcoming bullseye release]
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.
The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/dx_4.4.4-13_unstable_gcc11.log
The last lines of the build log are at the end of this report.
To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-11/porting_to.html
GCC 11 defaults to the GNU++17 standard. If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.
[...]
#define HAVE_FCNTL_H 1
#define HAVE_LIMITS_H 1
#define HAVE_MALLOC_H 1
#define HAVE_NETDB_H 1
#define HAVE_NETINET_IN_H 1
#define HAVE_PWD_H 1
#define HAVE_SIGNAL_H 1
#define HAVE_STRING_H 1
#define HAVE_STRINGS_H 1
#define HAVE_SYS_ERRNO_H 1
#define HAVE_SYS_FILE_H 1
#define HAVE_SYS_IOCTL_H 1
#define HAVE_SYS_PARAM_H 1
#define HAVE_SYS_SELECT_H 1
#define HAVE_SYS_SHM_H 1
#define HAVE_SYS_SIGNAL_H 1
#define HAVE_SYS_STAT_H 1
#define HAVE_SYS_TIMEB_H 1
#define HAVE_SYS_TIMES_H 1
#define HAVE_SYS_TIME_H 1
#define HAVE_SYS_TYPES_H 1
#define HAVE_SYS_UN_H 1
#define HAVE_SYS_UTSNAME_H 1
#define HAVE_TIME_H 1
#define HAVE_UNISTD_H 1
#define HAVE_VALUES_H 1
#define HAVE_WAIT_H 1
#define HAVE_X11_XMU_EDITRES_H 1
#define HAVE_NET_IF_H 1
#define STATFUNC stat
#define STATSTRUCT stat
#define HAVE_DIRENT_H 1
#define HAVE_IOSTREAM 1
#define HAVE_REGEX_H 1
#define HAVE_SSTREAM 1
#define HAVE_FSTREAM 1
#define HAVE_LIBNSL 1
#define REQUIRES_GETHOSTNAME_DECLARATION 0
#define REQUIRES_BZERO_DECLARATION 0
#define HAS_M_PI 1
#define HAS_M_SQRT2 1
#define HAS_S_ISDIR 1
#define RETSIGTYPE void
#define HAVE_FORK 1
#define HAVE_VFORK 1
#define HAVE_WORKING_VFORK 1
#define HAVE_WORKING_FORK 1
#define HAVE_VPRINTF 1
#define byte signed char
#define ubyte unsigned char
#define int8 char
#define uint8 unsigned char
#define int16 short
#define uint16 unsigned short
#define int32 int
#define uint32 unsigned int
#define int64 long
#define float64 double
#define uint64 unsigned long
#define __int64 long long
#define float32 float
#define SELECT_ARG_TYPE fd_set
#define SOCK_LENGTH_TYPE socklen_t
configure: exit 1
dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --prefix=/usr/share
--enable-smp-linux --with-rsh=/usr/bin/ssh --disable-dependency-tracking
--enable-shared returned exit code 1
make[1]: *** [debian/rules:21: override_dh_auto_configure] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:18: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: dx
Source-Version: 1:4.4.4-14
Done: Graham Inggs
We believe that the bug you reported is fixed in the latest version of
dx, which is due to be installed in the Debian FTP archive.
A summary of the changes between
Bug#998052: ltt-control build depends liblttng-ust-dev (< 2.13.0~) but 2.13.0-2 is to be installed
Source: ltt-control Version: 2.12.3-1 Severity: serious Tags: ftbfs bookworm sid The following packages have unmet dependencies: builddeps:ltt-control : Depends: liblttng-ust-dev (< 2.13.0~) but 2.13.0-2 is to be installed
