Processed: python-matplotlib-doc: not installable in Sid
Processing commands for cont...@bugs.debian.org: > reassign #1027601 python-matplotlib-doc Bug #1027601 [graph-tool] fix graph-tool, python-matplotlib-doc is no longer generated by src:matplotlib Bug reassigned from package 'graph-tool' to 'python-matplotlib-doc'. Ignoring request to alter found versions of bug #1027601 to the same values previously set Ignoring request to alter fixed versions of bug #1027601 to the same values previously set > retitle #1027601 python-matplotlib-doc: not installable in Sid Bug #1027601 [python-matplotlib-doc] fix graph-tool, python-matplotlib-doc is no longer generated by src:matplotlib Changed Bug title to 'python-matplotlib-doc: not installable in Sid' from 'fix graph-tool, python-matplotlib-doc is no longer generated by src:matplotlib'. > affects #1027601 graph-tool Bug #1027601 [python-matplotlib-doc] python-matplotlib-doc: not installable in Sid Added indication that 1027601 affects graph-tool > thanks Stopping processing here. Please contact me if you need assistance. -- 1027601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027072: marked as done (ruby-fission: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: Fission::Action::VM::Stopper.new(self).stop(options))
Your message dated Mon, 02 Jan 2023 07:04:17 +
with message-id
and subject line Bug#1027072: fixed in ruby-fission 0.5.0-3
has caused the Debian Bug report #1027072,
regarding ruby-fission: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1"
failed: Failure/Error: Fission::Action::VM::Stopper.new(self).stop(options)
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.)
--
1027072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027072
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-fission
Version: 0.5.0-2.1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12
Hi,
I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-fission failed to build.
Relevant part of the build log (hopefully):
> Failure/Error: Fission::Action::VM::Stopper.new(self).stop(options)
>
># received :stop with unexpected arguments
> expected: ({:hard=>true}) (keyword arguments)
> got: ({:hard=>true}) (options hash)
> # ./lib/fission/vm.rb:135:in `stop'
> # ./spec/fission/vm_spec.rb:93:in `block (3 levels) in '
>
> Deprecation Warnings:
>
> Using `should_receive` from rspec-mocks' old `:should` syntax without
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or
> explicitly enable `:should` instead. Called from
> /<>/spec/fission/action/execute_shell_command_spec.rb:12:in
> `block (3 levels) in '.
>
> Using `should` from rspec-expectations' old `:should` syntax without
> explicitly enabling the syntax is deprecated. Use the new `:expect` syntax or
> explicitly enable `:should` with `config.expect_with(:rspec) { |c| c.syntax =
> :should }` instead. Called from
> /<>/spec/fission/action/execute_shell_command_spec.rb:18:in
> `block (3 levels) in '.
>
>
> If you need more of the backtrace for any of these deprecations to
> identify where to make the necessary changes, you can configure
> `config.raise_errors_for_deprecations!`, and it will turn the
> deprecation warnings into errors, giving you the full backtrace.
>
> 2 deprecation warnings total
>
> Finished in 0.8034 seconds (files took 0.32206 seconds to load)
> 350 examples, 2 failures
>
> Failed examples:
>
> rspec ./spec/fission/vm_spec.rb:51 # Fission::VM start should return a
> successful response when starting headless
> rspec ./spec/fission/vm_spec.rb:88 # Fission::VM stop should return a
> successful response when stopping hard
>
> /usr/bin/ruby3.1
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb failed
> ERROR: Test "ruby3.1" failed:
The full build log is attached.
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
ruby-fission.log.gz
Description: application/gzip
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-fission
Source-Version: 0.5.0-3
Done: HIGUCHI Daisuke (VDR dai)
We believe that the bug you reported is fixed in the latest version of
ruby-fission, 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 1027...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
HIGUCHI Daisuke (VDR dai) (supplier of updated ruby-fission
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: Mon, 02 Jan 2023 15:30:25 +0900
Source: ruby-fission
Architecture: source
Version: 0.5.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: HIGUCHI Daisuke (VDR dai)
Closes: 1027072
Changes:
ruby-fission (0.5.0-3) unstable; urgency=medium
.
* Team upload.
.
[ Cédric Boutillier ]
* Use https:// in Vcs-* fields
* Bump Standards-Version to 3.9.7 (no changes needed)
* Use new default gem2deb Rakefile to run the tests
.
[ Utkarsh Gupta ]
* Add salsa-ci.yml
.
[ Debian Janitor ]
* Use secure
Bug#1027696: src:cqrlib: fails to migrate to testing for too long: FTBFS on i386
Source: cqrlib Version: 1.1.4-1 Severity: serious Control: close -1 1.1.4-2 Tags: sid bookworm ftbfs 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:cqrlib has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your packaged failed to build on i386, while it built successfully there in the past. 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. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=cqrlib OpenPGP_signature Description: OpenPGP digital signature
Processed: src:cqrlib: fails to migrate to testing for too long: FTBFS on i386
Processing control commands: > close -1 1.1.4-2 Bug #1027696 [src:cqrlib] src:cqrlib: fails to migrate to testing for too long: FTBFS on i386 Marked as fixed in versions cqrlib/1.1.4-2. Bug #1027696 [src:cqrlib] src:cqrlib: fails to migrate to testing for too long: FTBFS on i386 Marked Bug as done -- 1027696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027696 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1026719: vmg: FTBFS: /usr/bin/ld.bfd: cannot find -latk-1.0: No such file or directory
Hi Abou, On 01-01-2023 23:51, Abou Al Montacir wrote: Yes, sure. But for bookworm we'll apparently stay with gtk2, so let's make that that works, at least. Maybe this makes sens, but I can't revert a decision made by the team on my own, because a user decided something else. I'll wait for feedback from others. After this discussion (thanks for having it), I think it's best to reopen bug 967348, have fp-units-gtk2-x.y.z depend on libgtk2.0-dev again and *stop shipping* fp-units-gtk2-x.y.z once libgtk2.0-dev needs to be removed. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1027071: marked as done (ruby-eim-xml: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: EimXML::Formatter.write(element, opt.merge(:preservers=>PRESERVE_SPACES)))
Your message dated Mon, 2 Jan 2023 14:58:12 +0900
with message-id
and subject line close #1027071
has caused the Debian Bug report #1027071,
regarding ruby-eim-xml: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1"
failed: Failure/Error: EimXML::Formatter.write(element,
opt.merge(:preservers=>PRESERVE_SPACES))
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.)
--
1027071: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027071
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-eim-xml
Version: 0.0.4-4.1
Severity: important
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby-rspec-3.12
Hi,
I'm about to upload ruby-rspec 3.12. During a test rebuild with that version,
ruby-eim-xml failed to build.
Relevant part of the build log (hopefully):
> Failure/Error: EimXML::Formatter.write(element,
> opt.merge(:preservers=>PRESERVE_SPACES))
>
># received :write with unexpected arguments
> expected: (, {:opt=>:dummy,
> :preservers=>[EimXML::XHTML::PreserveSpace_]}) (keyword arguments)
> got: (, {:opt=>:dummy,
> :preservers=>[EimXML::XHTML::PreserveSpace_]}) (options hash)
> # ./lib/eim_xml/xhtml.rb:150:in `write'
> # ./spec/xhtml_spec.rb:432:in `block (3 levels) in '
>
> Finished in 0.06762 seconds (files took 0.1275 seconds to load)
> 111 examples, 2 failures
>
> Failed examples:
>
> rspec ./spec/formatter_spec.rb:240 # EimXML::Formatter::ElementWrapper#each
> will give options from formatter
> rspec ./spec/xhtml_spec.rb:429 # EimXML::XHTML::Formatter#write should set
> :preservers=>PRESERVE_SPACES to default option
>
> /usr/bin/ruby3.1
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.12.0/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.12.0/exe/rspec
> --pattern spec/\*\*\{,/\*/\*\*\}/\*_spec.rb failed
> ERROR: Test "ruby3.1" failed:
The full build log is attached.
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
ruby-eim-xml.log.gz
Description: application/gzip
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Package: ruby-eim-xml
Version: 0.0.4-5
I got the wrong bug number in changelog, sorry.
--
Regards,
dai
GPG Fingerprint = 0B29 D88E 42E6 B765 B8D8 EA50 7839 619D D439 668E
signature.asc
Description: PGP signature
--- End Message ---
Bug#1027072: marked as pending in ruby-fission
Control: tag -1 pending Hello, Bug #1027072 in ruby-fission 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-fission/-/commit/e18e39d6799dc28fdd56152fbfb27e4937aa08db fix FTBFS with ruby-rspec 3.12 (Closes: #1027072) (this message was generated automatically) -- Greetings https://bugs.debian.org/1027072
Processed: Bug#1027072 marked as pending in ruby-fission
Processing control commands: > tag -1 pending Bug #1027072 [src:ruby-fission] ruby-fission: FTBFS with ruby-rspec 3.12: ERROR: Test "ruby3.1" failed: Failure/Error: Fission::Action::VM::Stopper.new(self).stop(options) Added tag(s) pending. -- 1027072: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027072 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027690: lmms: Segfault on startup with kwidgetsaddons 5.101.0
Package: lmms Version: 1.2.2+dfsg1-4+b3 Severity: grave Tags: patch upstream Justification: renders package unusable Forwarded: https://github.com/LMMS/lmms/issues/6587 Dear Maintainer, LMMS experiences a segmentation fault on startup. According to an upstream bug report [1], this appears to be due to a specific workaround for an old bug in KXMLGUI [2], which breaks with kwidgetsaddons 5.101.0. As the comments on the upstream bug report suggest, a workaround is to downgrade kwidgetsaddons to 5.100.0. I can confirm that downgrading the libkf5widgetsaddons5 and libkf5widgetsaddons-data packages works on my system. The fix for this segmentation fault is to remove the workaround [3], as the KXMLGUI bug has been fixed for some time (since version 5.55.0). Philip Chung [1] https://github.com/LMMS/lmms/issues/6587 [2] https://bugs.kde.org/show_bug.cgi?id=337491 [3] See this fix in another distribution: https://github.com/void-linux/void-packages/pull/41313 -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.0.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lmms depends on: ii libasound21.2.8-1 ii libc6 2.36-7 ii libfftw3-single3 3.3.10-1 ii libfltk1.31.3.8-5 ii libfluidsynth32.3.0-1+b1 ii libgcc-s1 12.2.0-11 ii libgig10 4.3.0~ds1-2+b1 ii libmp3lame0 3.100-6 ii libogg0 1.3.5-3 ii libportaudio2 19.6.0-1.2 ii libpulse0 16.1+dfsg1-2+b1 ii libqt5core5a 5.15.7+dfsg-2 ii libqt5gui55.15.7+dfsg-2 ii libqt5widgets55.15.7+dfsg-2 ii libqt5xml55.15.7+dfsg-2 ii libsamplerate00.2.2-3 ii libsdl1.2debian 1.2.15+dfsg2-8 ii libsndfile1 1.1.0-3+b1 ii libsndio7.0 1.9.0-0.3+b1 ii libsoundio2 2.0.0-2 ii libstdc++612.2.0-11 ii libstk-4.6.2 4.6.2+dfsg-2 ii libvorbis0a 1.3.7-1 ii libvorbisenc2 1.3.7-1 ii libvorbisfile31.3.7-1 ii lmms-common 1.2.2+dfsg1-4 ii stk 4.6.2+dfsg-2 ii zlib1g1:1.2.13.dfsg-1 Versions of packages lmms recommends: ii caps 0.9.26-1 pn lmms-vst-server ii tap-plugins 1.0.0-1 Versions of packages lmms suggests: ii caps [ladspa-plugin] 0.9.26-1 pn fil-plugins pn fluid-soundfont-gm pn freepats pn mcp-plugins pn omins ii tap-plugins [ladspa-plugin] 1.0.0-1 -- no debconf information
Bug#1026692: marked as done (underscore: FTBFS: make[1]: *** [debian/rules:21: override_dh_auto_build] Error 1)
Your message dated Mon, 02 Jan 2023 04:34:26 + with message-id and subject line Bug#1026692: fixed in underscore 1.13.4~dfsg+~1.11.4-3 has caused the Debian Bug report #1026692, regarding underscore: FTBFS: make[1]: *** [debian/rules:21: override_dh_auto_build] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: underscore Version: 1.13.4~dfsg+~1.11.4-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 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 '/<>' > uglifyjs --compress --mangle \ > --source-map \ > --output underscore.min.js \ > underscore.js > pigz --force --keep -11 -- underscore.min.js underscore.min.js.map > brotli --force --keep --best -- underscore.min.js underscore.min.js.map > rollup -f commonjs -o underscore-esm.cjs underscore-esm.js > [36m > [1munderscore-esm.js[22m → [1munderscore-esm.cjs[22m...[39m > [1m[33m(!) Mixing named and default exports[39m[22m > [90mhttps://rollupjs.org/guide/en/#outputexports[39m > [1mThe following entry modules are using named and default exports > together:[22m > underscore-esm.js > > Consumers of your bundle will have to use chunk.default to access their > default export, which may not be what you want. Use `output.exports: "named"` > to disable this warning. > [32mcreated [1munderscore-esm.cjs[22m in [1m382ms[22m[39m > rollup -c > [36m > [1mmodules/index-all.js[22m → [1munderscore-esm.js[22m...[39m > [32mcreated [1munderscore-esm.js[22m in [1m578ms[22m[39m > [36m > [1mmodules/index-default.js[22m → [1munderscore-umd.js[22m...[39m > [32mcreated [1munderscore-umd.js[22m in [1m439ms[22m[39m > [36m > [1mmodules/index-default.js, modules/index-all.js[22m → [1m.[22m...[39m > [32mcreated [1m.[22m in [1m440ms[22m[39m > [36m > [1mmodules/_baseCreate.js, modules/_baseIteratee.js, modules/_cb.js, > modules/_chainResult.js, modules/_collectNonEnumProps.js, > modules/_createAssigner.js, modules/_createEscaper.js, > modules/_createIndexFinder.js, modules/_createPredicateIndexFinder.js, > modules/_createReduce.js, modules/_createSizePropertyCheck.js, > modules/_deepGet.js, modules/_escapeMap.js, modules/_executeBound.js, > modules/_flatten.js, modules/_getByteLength.js, modules/_getLength.js, > modules/_group.js, modules/_has.js, modules/_hasObjectTag.js, > modules/_isArrayLike.js, modules/_isBufferLike.js, modules/_keyInObj.js, > modules/_methodFingerprint.js, modules/_optimizeCb.js, modules/_setup.js, > modules/_shallowProperty.js, modules/_stringTagBug.js, modules/_tagTester.js, > modules/_toBufferView.js, modules/_toPath.js, modules/_unescapeMap.js, > modules/after.js, modules/allKeys.js, modules/before.js, modules/bind.js, > modules/bindAll.js, modules/chain.js, modules/chunk.js, modules/clone.js, > modules/compact.js, modules/compose.js, modules/constant.js, > modules/contains.js, modules/countBy.js, modules/create.js, > modules/debounce.js, modules/defaults.js, modules/defer.js, modules/delay.js, > modules/difference.js, modules/each.js, modules/escape.js, modules/every.js, > modules/extend.js, modules/extendOwn.js, modules/filter.js, modules/find.js, > modules/findIndex.js, modules/findKey.js, modules/findLastIndex.js, > modules/findWhere.js, modules/first.js, modules/flatten.js, > modules/functions.js, modules/get.js, modules/groupBy.js, modules/has.js, > modules/identity.js, modules/index-default.js, modules/index.js, > modules/indexBy.js, modules/indexOf.js, modules/initial.js, > modules/intersection.js, modules/invert.js, modules/invoke.js, > modules/isArguments.js, modules/isArray.js, modules/isArrayBuffer.js, > modules/isBoolean.js, modules/isDataView.js, modules/isDate.js, > modules/isElement.js, modules/isEmpty.js, modules/isEqual.js, > modules/isError.js, modules/isFinite.js, modules/isFunction.js, > modules/isMap.js, modules/isMatch.js, modules/isNaN.js, modules/isNull.js, > modules/isNumber.js, modules/isObject.js, modules/isRegExp.js, > modules/isSet.js, modules/isString.js, modules/isSymbol.js, > modules/isTypedArray.js, modules/isUndefined.js, modules/isWeakMap.js, > modules/isWeakSet.js, modules/iteratee.js, modules/keys.js, modules/last.js, > modules/lastIndexOf.js, modules/map.js, modules/mapObject.js, >
Bug#1026706: marked as done (node-grunt-contrib-requirejs: FTBFS: make: *** [debian/rules:8: binary] Error 1)
Your message dated Mon, 02 Jan 2023 04:34:16 + with message-id and subject line Bug#1026706: fixed in node-grunt-contrib-requirejs 1.0.0-8 has caused the Debian Bug report #1026706, regarding node-grunt-contrib-requirejs: FTBFS: make: *** [debian/rules:8: binary] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-grunt-contrib-requirejs Version: 1.0.0-7 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs >dh_auto_build --buildsystem=nodejs > No build command found, searching known files > cd ./. && grunt > Running "clean:test" (clean) task > >> 0 paths cleaned. > > Running "requirejs:compile" (requirejs) task > > Running "requirejs:template" (requirejs) task > > Running "requirejs:onOptimize" (requirejs) task > > Running "nodeunit:tests" (nodeunit) task > Testing requirejs_test.js...OK > >> 3 assertions passed (4ms) > > Running "contrib-ci" task > Warning: Unable to read > "/usr/share/nodejs/grunt-contrib-internal/.github/workflows/test.yml" file > (Error code: ENOENT). Use --force to continue. > > Aborted due to warnings. > dh_auto_build: warning: ### Command "grunt" failed in . > > dh_auto_build: warning: > > 1 failures, unable to build automatically. > Install a debian/nodejs/./build or add a "override_dh_auto_build:" target > in debian/rules > > > dh_auto_build: warning: Aborting auto_build > > make: *** [debian/rules:8: binary] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/12/20/node-grunt-contrib-requirejs_1.0.0-7_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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: node-grunt-contrib-requirejs Source-Version: 1.0.0-8 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-grunt-contrib-requirejs, 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 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-grunt-contrib-requirejs 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: Mon, 02 Jan 2023 07:41:05 +0400 Source: node-grunt-contrib-requirejs Architecture: source Version: 1.0.0-8 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1026706 Changes: node-grunt-contrib-requirejs (1.0.0-8) unstable; urgency=medium . * Team upload * Update standards version to 4.6.2, no changes needed. * Disable auto-build (Closes: #1026706) Checksums-Sha1: 91b878469bfc240df01a88afa9cf964661cc4d6a 2376 node-grunt-contrib-requirejs_1.0.0-8.dsc c822dfa36ee5f74be109782700eddab1f836f64f 3664 node-grunt-contrib-requirejs_1.0.0-8.debian.tar.xz Checksums-Sha256: 2b32e7401785c98fbd537b29d03cb093f9bed2a0c3f3f676b324fed8943a2cd0 2376 node-grunt-contrib-requirejs_1.0.0-8.dsc
Bug#1026654: marked as done (node-grunt-contrib-concat: FTBFS: make: *** [debian/rules:8: binary] Error 1)
Your message dated Mon, 02 Jan 2023 04:34:09 + with message-id and subject line Bug#1026654: fixed in node-grunt-contrib-concat 2.1.0-2 has caused the Debian Bug report #1026654, regarding node-grunt-contrib-concat: FTBFS: make: *** [debian/rules:8: binary] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1026654: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026654 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-grunt-contrib-concat Version: 2.1.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20221220 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs >dh_auto_build --buildsystem=nodejs > No build command found, searching known files > cd ./. && grunt > Running "clean:tests" (clean) task > >> 0 paths cleaned. > > Running "concat:default_options" (concat) task > > Running "concat:custom_options" (concat) task > > Running "concat:handling_invalid_files" (concat) task > >> Source file "invalid_file/should_warn/but_not_fail" not found. > > Running "concat:process_function" (concat) task > > Running "concat:dir" (concat) task > > Running "concat:overwrite_one" (concat) task > > Running "concat:overwrite_two" (concat) task > > Running "concat:sourcemap_options" (concat) task > (node:1308941) [DEP0005] DeprecationWarning: Buffer() is deprecated due to > security and usability issues. Please use the Buffer.alloc(), > Buffer.allocUnsafe(), or Buffer.from() methods instead. > (Use `node --trace-deprecation ...` to show where the warning was created) > > Running "concat:sourcemap2_options" (concat) task > > Running "concat:sourcemap3_options" (concat) task > > Running "concat:sourcemap_js" (concat) task > > Running "concat:sourcemap_css" (concat) task > > Running "nodeunit:tests" (nodeunit) task > Testing concat_test.jsOK > >> 21 assertions passed (10ms) > > Running "contrib-ci" task > Warning: Unable to read > "/usr/share/nodejs/grunt-contrib-internal/.github/workflows/test.yml" file > (Error code: ENOENT). Use --force to continue. > > Aborted due to warnings. > dh_auto_build: warning: ### Command "grunt" failed in . > > dh_auto_build: warning: > > 1 failures, unable to build automatically. > Install a debian/nodejs/./build or add a "override_dh_auto_build:" target > in debian/rules > > > dh_auto_build: warning: Aborting auto_build > > make: *** [debian/rules:8: binary] Error 1 The full build log is available from: http://qa-logs.debian.net/2022/12/20/node-grunt-contrib-concat_2.1.0-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20221220;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20221220=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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: node-grunt-contrib-concat Source-Version: 2.1.0-2 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-grunt-contrib-concat, 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 1026...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-grunt-contrib-concat 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: Mon, 02 Jan 2023
Bug#1026692: marked as pending in underscore
Control: tag -1 pending Hello, Bug #1026692 in underscore 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/js-team/underscore/-/commit/077ff6ae7fe5e62181e31051e3cebe9751a92521 Update rollup-3 patch Closes: #1026692 (this message was generated automatically) -- Greetings https://bugs.debian.org/1026692
Bug#1026706: marked as pending in node-grunt-contrib-requirejs
Control: tag -1 pending Hello, Bug #1026706 in node-grunt-contrib-requirejs 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/js-team/node-grunt-contrib-requirejs/-/commit/3aeeb91c4108a86fd2bb813e67d4643eb6d28ed6 Disable auto-build Closes: #1026706 (this message was generated automatically) -- Greetings https://bugs.debian.org/1026706
Processed: Bug#1026706 marked as pending in node-grunt-contrib-requirejs
Processing control commands: > tag -1 pending Bug #1026706 [src:node-grunt-contrib-requirejs] node-grunt-contrib-requirejs: FTBFS: make: *** [debian/rules:8: binary] Error 1 Added tag(s) pending. -- 1026706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1026692 marked as pending in underscore
Processing control commands: > tag -1 pending Bug #1026692 [src:underscore] underscore: FTBFS: make[1]: *** [debian/rules:21: override_dh_auto_build] Error 1 Added tag(s) pending. -- 1026692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026692 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027615: marked as done (dateparser: FTBFS: build-dependency not installable: python3-regex (< 0.1.20220315))
Your message dated Mon, 02 Jan 2023 03:49:10 + with message-id and subject line Bug#1027615: fixed in dateparser 1.1.5-1 has caused the Debian Bug report #1027615, regarding dateparser: FTBFS: build-dependency not installable: python3-regex (< 0.1.20220315) 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.) -- 1027615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dateparser Version: 1.1.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), dh-python, locales-all, > python3-all, python3-convertdate, python3-coverage, python3-dateutil, > python3-fasttext, python3-langdetect, python3-mock, python3-parameterized, > python3-parsel, python3-pytest, python3-requests, python3-ruamel.yaml, > python3-regex (<< 0.1.20220315), python3-setuptools, python3-six, python3-tz, > python3-tzlocal, build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), dh-python, locales-all, > python3-all, python3-convertdate, python3-coverage, python3-dateutil, > python3-fasttext, python3-langdetect, python3-mock, python3-parameterized, > python3-parsel, python3-pytest, python3-requests, python3-ruamel.yaml, > python3-regex (<< 0.1.20220315), python3-setuptools, python3-six, python3-tz, > python3-tzlocal, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [513 B] > Get:5 copy:/<>/apt_archive ./ Packages [585 B] > Fetched 2055 B in 0s (155 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-main-dummy : Depends: python3-regex (< 0.1.20220315) > but it is not going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/01/01/dateparser_1.1.2-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230101=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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: dateparser Source-Version: 1.1.5-1 Done: Antoine Beaupré We believe that the bug you reported is fixed in the latest version of dateparser, 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 1027...@bugs.de
Bug#1027495: marked as done (feed2exec: FTBFS: build-dependency not installable: python3-regex (< 0.1.20220315))
Your message dated Sun, 01 Jan 2023 22:30:34 -0500 with message-id <878rilobol@angela.anarc.at> and subject line Re: Bug#1027495: feed2exec: FTBFS: build-dependency not installable: python3-regex (< 0.1.20220315) has caused the Debian Bug report #1027495, regarding feed2exec: FTBFS: build-dependency not installable: python3-regex (< 0.1.20220315) 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.) -- 1027495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027495 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: feed2exec Version: 0.18.0 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 12), dh-python, python3, > python3-betamax (>= 0.8.0), python3-click, python3-dateparser, python3-doc, > python3-feedparser, python3-html2text, python3-html5lib, python3-lxml, > python3-pytest-cov, python3-pytest-runner, python3-requests, > python3-requests-file, python3-setuptools, python3-setuptools-scm, > python3-sphinx, python3-sphinx-rtd-theme, python3-unidecode, python3-xdg, > build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 12), dh-python, python3, > python3-betamax (>= 0.8.0), python3-click, python3-dateparser, python3-doc, > python3-feedparser, python3-html2text, python3-html5lib, python3-lxml, > python3-pytest-cov, python3-pytest-runner, python3-requests, > python3-requests-file, python3-setuptools, python3-setuptools-scm, > python3-sphinx, python3-sphinx-rtd-theme, python3-unidecode, python3-xdg, > build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [960 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [501 B] > Get:5 copy:/<>/apt_archive ./ Packages [585 B] > Fetched 2046 B in 0s (159 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > python3-dateparser : Depends: python3-regex (< 0.1.20220315) but it is not > going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/01/01/feed2exec_0.18.0_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230101=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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 --- This is actually an issue in dateparser, not feed2exec. See #1027615, fixed in latest dateparser 1.1.5-1 upload I just did. A. -- By now the computer has moved out of the den and into the rest of your life. It will consume all of your spare time, and even
Bug#1026548: marked as done (python-pgpy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)
Your message dated Sun, 01 Jan 2023 19:40:00 -0700
with message-id <874jt9accf@melete.silentflame.com>
and subject line Fix uploaded
has caused the Debian Bug report #1026548,
regarding python-pgpy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.11 3.10" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1026548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pgpy
Version: 0.5.4-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 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 '/<>'
> LC_ALL=C.UTF-8 PYBUILD_VERSIONS=3.6 dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11_pgpy/build;
> python3.11 -m pytest tests
> == PGPy Test Suite ==
> Working Directory: /<>/.pybuild/cpython3_3.11_pgpy/build
> Using OpenSSL 3.0.7
> Using GnuPG 2.2.40
>
> [1m= test session starts
> ==[0m
> platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack --
> /usr/bin/python3.11
> cachedir: .pytest_cache
> rootdir: /<>, configfile: tox.ini
> plugins: cov-4.0.0
> [1mcollecting ... [0mcollected 21 items / 8 errors
>
> ERRORS
>
> [31m[1m_ ERROR collecting
> .pybuild/cpython3_3.11_pgpy/build/tests/test_01_packetfields.py _[0m
> [1m[31mtests/test_01_packetfields.py[0m:7: in
> [94mfrom[39;49;00m
> [04m[96mpgpy[39;49;00m[04m[96m.[39;49;00m[04m[96mconstants[39;49;00m
> [94mimport[39;49;00m HashAlgorithm
> [1m[31mpgpy/__init__.py[0m:4: in
> [94mfrom[39;49;00m [04m[96m.[39;49;00m[04m[96mpgp[39;49;00m
> [94mimport[39;49;00m PGPKey
> [1m[31mpgpy/pgp.py[0m:27: in
> [94mfrom[39;49;00m [04m[96m.[39;49;00m[04m[96mconstants[39;49;00m
> [94mimport[39;49;00m CompressionAlgorithm
> [1m[31mpgpy/constants.py[0m:23: in
> [94mfrom[39;49;00m [04m[96m.[39;49;00m[04m[96m_curves[39;49;00m
> [94mimport[39;49;00m BrainpoolP256R1, BrainpoolP384R1, BrainpoolP512R1,
> X25519, Ed25519
> [1m[31mpgpy/_curves.py[0m:37: in
> [37m@utils[39;49;00m.register_interface(ec.EllipticCurve)
> [1m[31mE AttributeError: module 'cryptography.utils' has no attribute
> 'register_interface'[0m
> [31m[1m_ ERROR collecting
> .pybuild/cpython3_3.11_pgpy/build/tests/test_02_packets.py __[0m
> [1m[31mtests/test_02_packets.py[0m:8: in
> [94mfrom[39;49;00m
> [04m[96mpgpy[39;49;00m[04m[96m.[39;49;00m[04m[96mpacket[39;49;00m
> [94mimport[39;49;00m Packet
> [1m[31mpgpy/__init__.py[0m:4: in
> [94mfrom[39;49;00m [04m[96m.[39;49;00m[04m[96mpgp[39;49;00m
> [94mimport[39;49;00m PGPKey
> [1m[31mpgpy/pgp.py[0m:27: in
> [94mfrom[39;49;00m [04m[96m.[39;49;00m[04m[96mconstants[39;49;00m
> [94mimport[39;49;00m CompressionAlgorithm
> [1m[31mpgpy/constants.py[0m:23: in
> [94mfrom[39;49;00m [04m[96m.[39;49;00m[04m[96m_curves[39;49;00m
> [94mimport[39;49;00m BrainpoolP256R1, BrainpoolP384R1, BrainpoolP512R1,
> X25519, Ed25519
> [1m[31mpgpy/_curves.py[0m:37: in
> [37m@utils[39;49;00m.register_interface(ec.EllipticCurve)
> [1m[31mE AttributeError: module 'cryptography.utils' has no attribute
> 'register_interface'[0m
> [31m[1m__ ERROR collecting
> .pybuild/cpython3_3.11_pgpy/build/tests/test_03_armor.py ___[0m
> [1m[31mtests/test_03_armor.py[0m:9: in
> [94mfrom[39;49;00m
> [04m[96mpgpy[39;49;00m[04m[96m.[39;49;00m[04m[96mconstants[39;49;00m
> [94mimport[39;49;00m HashAlgorithm
> [1m[31mpgpy/__init__.py[0m:4: in
> [94mfrom[39;49;00m [04m[96m.[39;49;00m[04m[96mpgp[39;49;00m
> [94mimport[39;49;00m PGPKey
> [1m[31mpgpy/pgp.py[0m:27: in
> [94mfrom[39;49;00m [04m[96m.[39;49;00m[04m[96mconstants[39;49;00m
> [94mimport[39;49;00m CompressionAlgorithm
> [1m[31mpgpy/constants.py[0m:23: in
> [94mfrom[39;49;00m [04m[96m.[39;49;00m[04m[96m_curves[39;49;00m
> [94mimport[39;49;00m BrainpoolP256R1, BrainpoolP384R1, BrainpoolP512R1,
> X25519, Ed25519
> [1m[31mpgpy/_curves.py[0m:37: in
> [37m@utils[39;49;00m.register_interface(ec.EllipticCurve)
> [1m[31mE AttributeError: module 'cryptography.utils' has no attribute
>
Bug#1027418: autopkgtest failure - iconv issue?
2023년 1월 2일 (월) 오전 5:31, Rene Engelhard 님이 작성: > > Hi, > > Am 01.01.23 um 21:25 schrieb Changwoo Ryu: > > I can't reproduce it myself. > I am not sure either what happens... > > In your test, every word failed to be checked with the same error and > > the error message came from hunspell, when iconv() conversion on text > > fails. Probably your chroot environment lacked some libs necessary for > > iconv(). > > Yes, but that then needs to be reflected in the test depends strictly > speaking... If there's a missing dependency which breaks hunspell like this, then it needs to be added to hunspell dependencies, not to this test's. It is enough having 'hunspell' in Depends to run hunspell. But I believe dependency is not an issue. I think you made your chroot dir without fully installing libc6. Note that glibc's iconv() function loads dynamic encoding conversion libs under /usr/lib/x86_64-linux-gnu/gconv/ on runtime. I ran the test like this (and it succeeded): $ sudo autopkgtest-build-docker $ sudo autopkgtest . -- docker autopkgtest/debian:unstable
Bug#1027535: marked as done (dpmb: FTBFS: unsatisfiable build-dependencies (purely virtual?): qt6-base-abi (= 6.3.1), qt6-base-abi (= 6.3.1))
Your message dated Mon, 2 Jan 2023 02:24:11 +0100 with message-id <20230102012410.qbhovoq4w72ks...@sym.noone.org> and subject line Re: Bug#1027535: dpmb: FTBFS: unsatisfiable build-dependencies (purely virtual?): qt6-base-abi (= 6.3.1), qt6-base-abi (= 6.3.1) has caused the Debian Bug report #1027535, regarding dpmb: FTBFS: unsatisfiable build-dependencies (purely virtual?): qt6-base-abi (= 6.3.1), qt6-base-abi (= 6.3.1) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dpmb Version: 0~2021.03.01 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), build-essential, fakeroot, > asciidoc, asciidoc-dblatex (>= 8.6.9-5) | asciidoc (<= 8.6.9-3.1), calibre, > dblatex, texlive-lang-german, xmlto > Filtered Build-Depends: debhelper-compat (= 13), build-essential, fakeroot, > asciidoc, asciidoc-dblatex (>= 8.6.9-5), calibre, dblatex, > texlive-lang-german, xmlto > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [443 B] > Get:5 copy:/<>/apt_archive ./ Packages [503 B] > Fetched 1903 B in 0s (155 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > calibre-bin : Depends: qt6-base-abi (= 6.3.1) > python3-pyqt6 : Depends: qt6-base-abi (= 6.3.1) > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/01/01/dpmb_0~2021.03.01_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230101=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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 --- Control: notfound -1 0~2021.03.01 Hi Lucas, Axel Beckert wrote: > > > The following information may help to resolve the situation: > > > > > > The following packages have unmet dependencies: > > > calibre-bin : Depends: qt6-base-abi (= 6.3.1) > > > python3-pyqt6 : Depends: qt6-base-abi (= 6.3.1) > > Since the package has neither a Build-Depends on either package, I > suspect this is a follow-up issue of he current (recent?) Qt6 6.3.x to > 6.4.x library transition and should go away from itself. > > Probably the build-dependency on calibre is the main cause: > https://buildd.debian.org/status/package.php?p=calibre says that the > BinNMU builds of calibre were just 6 to 9 hours ago. Which is about >
Processed: Bug#1027566 marked as pending in neovim
Processing control commands: > tag -1 pending Bug #1027566 [src:neovim] neovim: FTBFS: [ RUN ] nvim_ui_attach() invalid option returns error: 7.12 ms OK Added tag(s) pending. -- 1027566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027566: marked as pending in neovim
Control: tag -1 pending Hello, Bug #1027566 in neovim 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/vim-team/neovim/-/commit/dd9165a249022eb7d3c0b88cc040895a11d48ed3 Bump minimum lua-nvim to 0.2.4-1 0.2.4-1 changed how process exit is communicated, so the tests had to be adapted accordingly. The upstream fixes are in the previous commit, but we need to ensure we're using a new enough lua-nvim when running with these changes. Closes: #1027566 Signed-off-by: James McCoy (this message was generated automatically) -- Greetings https://bugs.debian.org/1027566
Processed: Re: Bug#1027535: dpmb: FTBFS: unsatisfiable build-dependencies (purely virtual?): qt6-base-abi (= 6.3.1), qt6-base-abi (= 6.3.1)
Processing control commands: > tag -1 + moreinfo Bug #1027535 [src:dpmb] dpmb: FTBFS: unsatisfiable build-dependencies (purely virtual?): qt6-base-abi (= 6.3.1), qt6-base-abi (= 6.3.1) Added tag(s) moreinfo. -- 1027535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027535: dpmb: FTBFS: unsatisfiable build-dependencies (purely virtual?): qt6-base-abi (= 6.3.1), qt6-base-abi (= 6.3.1)
Control: tag -1 + moreinfo Hi Lucas, Lucas Nussbaum wrote: > Source: dpmb > Version: 0~2021.03.01 […] > During a rebuild of all packages in sid, your package failed to build > on amd64. […] > > The following information may help to resolve the situation: > > > > The following packages have unmet dependencies: > > calibre-bin : Depends: qt6-base-abi (= 6.3.1) > > python3-pyqt6 : Depends: qt6-base-abi (= 6.3.1) Since the package has neither a Build-Depends on either package, I suspect this is a follow-up issue of he current (recent?) Qt6 6.3.x to 6.4.x library transition and should go away from itself. Probably the build-dependency on calibre is the main cause: https://buildd.debian.org/status/package.php?p=calibre says that the BinNMU builds of calibre were just 6 to 9 hours ago. Which is about the time you've reported the bug report. As of now, at least it installed all build-dependencies successfully in an up to date chroot. I'll close the bug report if the build succeeds. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#1027474: marked as done (qbs: FTBFS: symbol errors)
Your message dated Mon, 02 Jan 2023 00:23:33 +
with message-id
and subject line Bug#1027474: fixed in qbs 1.24.0+dfsg-4
has caused the Debian Bug report #1027474,
regarding qbs: FTBFS: symbol errors
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.)
--
1027474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qbs
Version: 1.24.0+dfsg-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org
https://buildd.debian.org/status/fetch.php?pkg=qbs=amd64=1.24.0%2Bdfsg-2%2Bb1=1672570009=0
dpkg-gensymbols: warning: debian/libqbscore1.24/DEBIAN/symbols doesn't match
completely debian/libqbscore1.24.symbols
--- debian/libqbscore1.24.symbols (libqbscore1.24_1.24.0+dfsg-2+b1_amd64)
+++ dpkg-gensymbols1HiWRK 2023-01-01 10:46:37.336628656 +
@@ -20,6 +20,7 @@
(optional=templinst)_Z41qRegisterNormalizedMetaTypeImplementationIN3qbs9ErrorInfoEEiRK10QByteArray@Base
1.23.1
(optional=templinst)_Z41qRegisterNormalizedMetaTypeImplementationIPN3qbs11AbstractJobEEiRK10QByteArray@Base
1.23.1
(optional=templinst)_Z41qRegisterNormalizedMetaTypeImplementationIPN3qbs8Internal11InternalJobEEiRK10QByteArray@Base
1.23.1
+ _Z5qHashI7QStringEmRK5QListIT_Em@Base 1.24.0+dfsg-2+b1
_Z5qHashRK19QProcessEnvironment@Base 1.22.0
_Z5qHashRK5QListI7QStringE@Base 1.23.1
_ZGVZN3qbs8Internal15StringConstants10falseValueEvE3var@Base 1.22.0
@@ -178,6 +179,7 @@
(optional=templinst)_ZN10QMultiHashI7QStringN3qbs8Internal12ModuleLoader17ProductModuleInfoEE14emplace_helperIJRKS4_EEENS5_8iteratorEOS0_DpOT_@Base
1.23.1
(optional=templinst)_ZN10QMultiHashI7QStringN3qbs8Internal12ModuleLoader17ProductModuleInfoEE7emplaceIJRKS4_EEENS5_8iteratorEOS0_DpOT_@Base
1.23.1
(optional=templinst)_ZN11QMetaTypeIdIN3qbs9ErrorInfoEE14qt_metatype_idEv@Base
1.22.0
+ _ZN12QHashPrivate12GrowthPolicy18bucketsForCapacityEm@Base 1.24.0+dfsg-2+b1
(optional=templinst|subst)_ZN12QHashPrivate4DataINS_4NodeI11QStringView7QStringEEE6rehashE{size_t}@Base
1.23.1
(optional=templinst)_ZN12QHashPrivate4DataINS_4NodeI11QStringView7QStringEEEC1ERKS5_@Base
1.23.1
(optional=templinst)_ZN12QHashPrivate4DataINS_4NodeI11QStringView7QStringEEEC2ERKS5_@Base
1.23.1
@@ -228,6 +230,7 @@
(optional=templinst|arch=amd64 armel
mipsel)_ZN12QHashPrivate4DataINS_4NodeI7QString5QHashIS2_N3qbs8Internal27InputArtifactScannerContext27ResolvedDependencyCacheItemED1Ev@Base
1.23.1
(optional=templinst|arch=amd64 armel
mipsel)_ZN12QHashPrivate4DataINS_4NodeI7QString5QHashIS2_N3qbs8Internal27InputArtifactScannerContext27ResolvedDependencyCacheItemED2Ev@Base
1.23.1
(optional=templinst)_ZN12QHashPrivate4DataINS_4NodeI7QString5QListIS2_12findOrInsertERKS2_@Base
1.23.1
+
_ZN12QHashPrivate4DataINS_4NodeI7QString5QListIS2_5eraseENS6_6BucketE@Base
1.24.0+dfsg-2+b1
(optional=templinst|subst)_ZN12QHashPrivate4DataINS_4NodeI7QString5QListIS2_6rehashE{size_t}@Base
1.23.1
(optional=templinst)_ZN12QHashPrivate4DataINS_4NodeI7QString5QListIS2_8detachedEPS6_@Base
1.23.1
(optional=templinst)_ZN12QHashPrivate4DataINS_4NodeI7QString5QListIS2_C1ERKS6_@Base
1.23.1
@@ -235,6 +238,7 @@
(optional=templinst)_ZN12QHashPrivate4DataINS_4NodeI7QString5QListIS2_D1Ev@Base
1.23.1
(optional=templinst)_ZN12QHashPrivate4DataINS_4NodeI7QString5QListIS2_D2Ev@Base
1.23.1
(optional=templinst)_ZN12QHashPrivate4DataINS_4NodeI7QStringN3qbs8Internal21RescuableArtifactData12findOrInsertERKS2_@Base
1.23.1
+
_ZN12QHashPrivate4DataINS_4NodeI7QStringN3qbs8Internal21RescuableArtifactData5eraseENS7_6BucketE@Base
1.24.0+dfsg-2+b1
(optional=templinst|subst)_ZN12QHashPrivate4DataINS_4NodeI7QStringN3qbs8Internal21RescuableArtifactData6rehashE{size_t}@Base
1.23.1
(optional=templinst)_ZN12QHashPrivate4DataINS_4NodeI7QStringN3qbs8Internal21RescuableArtifactDataC1ERKS7_@Base
1.23.1
(optional=templinst)_ZN12QHashPrivate4DataINS_4NodeI7QStringN3qbs8Internal21RescuableArtifactDataC2ERKS7_@Base
1.23.1
@@ -323,7 +327,7 @@
(optional=templinst|subst)_ZN12QHashPrivate4DataINS_4NodeIN3qbs8Internal11QualifiedIdEPNS3_4Item6rehashE{size_t}@Base
1.23.1
(optional=templinst)_ZN12QHashPrivate4DataINS_4NodeIN3qbs8Internal11QualifiedIdEPNS3_4ItemC1ERKS8_@Base
1.23.1
(optional=templinst)_ZN12QHashPrivate4DataINS_4NodeIN3qbs8Internal11QualifiedIdEPNS3_4ItemC2ERKS8_@Base
1.23.1
-
Bug#1026709: marked as done (python-pykka: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)
Your message dated Mon, 2 Jan 2023 00:57:00 +0100
with message-id
and subject line Re: Bug#1026709: python-pykka: FTBFS: dh_auto_test: error:
pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit
code 13
has caused the Debian Bug report #1026709,
regarding python-pykka: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.11 3.10" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1026709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pykka
Version: 2.0.3-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh build --with python3,sphinxdoc --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508:
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use
> license_files instead.
> warnings.warn(msg, warning_class)
> running config
> I: pybuild base:240: python3.10 setup.py config
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508:
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use
> license_files instead.
> warnings.warn(msg, warning_class)
> running config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3.11 setup.py build
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508:
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use
> license_files instead.
> warnings.warn(msg, warning_class)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_pykka/build/pykka
> copying pykka/__init__.py ->
> /<>/.pybuild/cpython3_3.11_pykka/build/pykka
> copying pykka/_registry.py ->
> /<>/.pybuild/cpython3_3.11_pykka/build/pykka
> copying pykka/_future.py ->
> /<>/.pybuild/cpython3_3.11_pykka/build/pykka
> copying pykka/debug.py ->
> /<>/.pybuild/cpython3_3.11_pykka/build/pykka
> copying pykka/_actor.py ->
> /<>/.pybuild/cpython3_3.11_pykka/build/pykka
> copying pykka/_threading.py ->
> /<>/.pybuild/cpython3_3.11_pykka/build/pykka
> copying pykka/messages.py ->
> /<>/.pybuild/cpython3_3.11_pykka/build/pykka
> copying pykka/_ref.py ->
> /<>/.pybuild/cpython3_3.11_pykka/build/pykka
> copying pykka/_envelope.py ->
> /<>/.pybuild/cpython3_3.11_pykka/build/pykka
> copying pykka/_proxy.py ->
> /<>/.pybuild/cpython3_3.11_pykka/build/pykka
> copying pykka/gevent.py ->
> /<>/.pybuild/cpython3_3.11_pykka/build/pykka
> copying pykka/eventlet.py ->
> /<>/.pybuild/cpython3_3.11_pykka/build/pykka
> copying pykka/_exceptions.py ->
> /<>/.pybuild/cpython3_3.11_pykka/build/pykka
> creating /<>/.pybuild/cpython3_3.11_pykka/build/pykka/_compat
> copying pykka/_compat/__init__.py ->
> /<>/.pybuild/cpython3_3.11_pykka/build/pykka/_compat
> copying pykka/_compat/await_py3.py ->
> /<>/.pybuild/cpython3_3.11_pykka/build/pykka/_compat
> I: pybuild base:240: /usr/bin/python3 setup.py build
> /usr/lib/python3/dist-packages/setuptools/config/setupcfg.py:508:
> SetuptoolsDeprecationWarning: The license_file parameter is deprecated, use
> license_files instead.
> warnings.warn(msg, warning_class)
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.10_pykka/build/pykka
> copying pykka/__init__.py ->
> /<>/.pybuild/cpython3_3.10_pykka/build/pykka
> copying pykka/_registry.py ->
> /<>/.pybuild/cpython3_3.10_pykka/build/pykka
> copying pykka/_future.py ->
> /<>/.pybuild/cpython3_3.10_pykka/build/pykka
> copying pykka/debug.py ->
> /<>/.pybuild/cpython3_3.10_pykka/build/pykka
> copying pykka/_actor.py ->
> /<>/.pybuild/cpython3_3.10_pykka/build/pykka
> copying pykka/_threading.py ->
> /<>/.pybuild/cpython3_3.10_pykka/build/pykka
> copying pykka/messages.py ->
> /<>/.pybuild/cpython3_3.10_pykka/build/pykka
> copying pykka/_ref.py ->
> /<>/.pybuild/cpython3_3.10_pykka/build/pykka
> copying pykka/_envelope.py ->
> /<>/.pybuild/cpython3_3.10_pykka/build/pykka
> copying pykka/_proxy.py ->
> /<>/.pybuild/cpython3_3.10_pykka/build/pykka
> copying pykka/gevent.py ->
> /<>/.pybuild/cpython3_3.10_pykka/build/pykka
> copying pykka/eventlet.py ->
>
Bug#1026719: [Pkg-pascal-devel] Bug#1026719: vmg: FTBFS: /usr/bin/ld.bfd: cannot find -latk-1.0: No such file or directory
Abou Al Montacir, le dim. 01 janv. 2023 23:51:45 +0100, a ecrit: > > Things were just working perfectly previously. Why breaking the build > > of packages using fp-units-gtk2-3.2.0 by dropping the pull? Is there an > > *actual* reason for not making fp-units-gtk2-3.2.0 pull it, > > Yes, the reason is to close the bug [1]https://bugs.debian.org/cgi-bin/ > bugreport.cgi?bug=967348 Oh, so it actually is possible to build fp-units-gtk2-3.0.0 without build-depending on libgtk2.0-dev? That was surprising but then yet I understand that position and that it allows you to "close" 967348. But all users of fp-units-gtk2 will still have to wait for a fp-units-gtk3 to become available anyway. Samuel
Bug#1026469: marked as done (metakernel: FTBFS: FAILED metakernel/magics/tests/test_parallel_magic.py::test_parallel_magic)
Your message dated Sun, 01 Jan 2023 23:02:38 +
with message-id
and subject line Bug#1026469: fixed in metakernel 0.29.4-1
has caused the Debian Bug report #1026469,
regarding metakernel: FTBFS: FAILED
metakernel/magics/tests/test_parallel_magic.py::test_parallel_magic
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.)
--
1026469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: metakernel
Version: 0.27.5-4
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 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 '/<>'
> PYTHONPATH=./metakernel_python/ python3 generate_help.py
> /usr/lib/python3/dist-packages/IPython/paths.py:70: UserWarning: IPython
> parent '/sbuild-nonexistent' is not a writable location, using a temp
> directory.
> warn("IPython parent '{0}' is not a writable location,"
> Generating README.md...
> done!
> PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml docs/ build/html
> Running Sphinx v5.3.0
> making output directory... done
> WARNING: html_static_path entry 'source/static' does not exist
> WARNING: The config value `today' has type `datetime', defaults to `str'.
> loading intersphinx inventory from
> /usr/share/doc/python3-doc/html/objects.inv...
> [autosummary] generating autosummary for: index.rst, source/README.md,
> source/api.rst, source/info.rst, source/installation.rst
> building [mo]: targets for 0 po files that are out of date
> building [html]: targets for 5 source files that are out of date
> updating environment: [new config] 5 added, 0 changed, 0 removed
> reading sources... [ 20%] index
> reading sources... [ 40%] source/README
> reading sources... [ 60%] source/api
> reading sources... [ 80%] source/info
> reading sources... [100%] source/installation
>
> /<>/docs/source/README.md:82: WARNING: Title underline too short.
>
> Options:
> ---
> /<>/docs/source/README.md:173: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:173: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:192: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:192: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:211: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:211: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:244: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:244: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:278: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:278: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:324: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:324: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:343: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:343: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:375: ERROR: Unexpected indentation.
> /<>/docs/source/README.md:390: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:390: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:411: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:411: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:479: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:479: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:533: ERROR: Unexpected indentation.
> /<>/docs/source/README.md:536: ERROR: Unexpected indentation.
> /<>/docs/source/README.md:539: WARNING: Block quote ends without
> a blank line; unexpected unindent.
> /<>/docs/source/README.md:540: WARNING: Block quote ends without
> a blank line; unexpected unindent.
> /<>/docs/source/README.md:598: WARNING: Title underline too
> short.
>
> Options:
> ---
> /<>/docs/source/README.md:598: WARNING: Title underline too
> short.
>
> Options:
>
Bug#1026719: [Pkg-pascal-devel] Bug#1026719: vmg: FTBFS: /usr/bin/ld.bfd: cannot find -latk-1.0: No such file or directory
On Sun, 2023-01-01 at 21:45 +0100, Samuel Thibault wrote: > > • Technically, Lazarus doe snot need libgtk2.0-dev for running, and thus > > should not pull it. > > Lazarus itself, no indeed. But the fp-units-gtk2-3.2.0 package does not > make any sense without libgtk2.0-dev, since there is no way to use the > former without the latter. That was the reason why fp-units-gtk2-x.y.z made dependent on the libgtk2.0-dev. However, with deprecation of gtk2, we decided to relax that constraint. Of course, one can argue, as you do, that the bindings packages does not make sens without depending on the libraries package. That makes sense, but we discussed this and relaxing the dependency was the easiest way for us, given that FPC does not seem to be ready to provide bindings for gtk3. > > • Technically, FPC does not need any GTK related lib, it only provide > > binding > > units. > > Yes, and *all* languages that provide bindings do provide the required > pulls so that users of the bindings don't have to care about what > should be pulled. The information is recorded in only the bindings > package, and not sprinkled over all packages that happen to use it > (which would require changes in all of them for no good reason whenever > the underlying C library happens to change its C API, for instance). I tend to agree here. > > Things were just working perfectly previously. Why breaking the build > of packages using fp-units-gtk2-3.2.0 by dropping the pull? Is there an > *actual* reason for not making fp-units-gtk2-3.2.0 pull it, Yes, the reason is to close the bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967348 > how does it > hurt in any way? Is that because fpc-3.2.0 happens to depend on it? > Then why does it do so, since from what you say it does not actually > need it? fpc-x.y.z is a meta-package that is there to pull all packages created by the fpc source package. > > Really, I don't understand: fp-units-gtk2-3.2.0 does need libgtk2.0-dev > to work at all, while you are saying that fpc-3.2.0 does not need > fp-units-gtk2-3.2.0 to work. The current "Depends" that are set on those > package are exactly the inverse of that... You are confused between fpc as a meta-package and fpc as an executable. The package depends on all fp-units-* created by fpc source package. While the executable (compiler) does not. > > > • For building, Lazarus build depends on libgtk2.0-dev, until it will > > migrate > > to gtk3. And so shall do all programs that use it. > > Yes, sure. But for bookworm we'll apparently stay with gtk2, so let's > make that that works, at least. Maybe this makes sens, but I can't revert a decision made by the team on my own, because a user decided something else. I'll wait for feedback from others. > > > I hope this makes it clear, why neither Lazarus, nor FPC or any of their > > packages should pull libgtk2.0-dev package. > > No, not at all. > > > You should handle this bug in VMG, and probably the best way to do it is to > > build depend on libgtk-2.0-dev > > From point point of view it's not the best way since it means that'll be > yet something more to change when switching to gtk3, then to gtk4, etc. > while everything could be just handled in the bindings package. Yes, ideally it should be that way. In practice, I'm not sure it will be possible. > > > until you fix [2]https://bugs.debian.org/cgi-bin /bugreport.cgi?bug=967799 > > That only boils down to making lazarus support gtk3, since vmg just > uses LCL. If Lazarus was providing a gtk bindings package which does > not encode the 2 vs 3 notion, the vmg package would be more than > happy to just use it and not have to care at all about the underlying > incompatibilities. -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part
Bug#1027380: safeclib: FTBFS in bullseye (missing build-depends on tzdata)
[ Thanks for fixing the bug in unstable so fast ] I'm all for fixing bugs in stable that: * are obviously bugs (rather than a point of debate) You are the only one debating this, but it should really not be a point of debate. Packages with missing build-depends are buggy and always have been. This is both in Debian Policy which we have already quoted and also in Release Policy for bullseye, which is the one that counts here: Packages must list any packages they require to build beyond those that are "build-essential" in the appropriate Build-Depends: fields. Ref: 4.2 https://release.debian.org/bullseye/rc_policy.txt Release Policy exists as a subset of Policy so that we don't have to discuss each time about which bugs we want a stable release to *never* have. If you think required packages are automatically build-essential, feel free to ask debian-policy for clarification. [ In fact, I wonder why you bothered to add the missing B-D if you really believe it is not a bug. There has not been any change in Debian Policy or Release Policy regarding this between bullseye and bookworm. Therefore, this is a bug in bullseye (or not) the same way it is a bug in bookworm (or not). ]. BTW: I'm not taking the build-essential package to determine which packages are build-essential or not, because there is already a definition in Policy, namely, those packages required to build a "hello world" program in C or C++ (Policy 4.2). I have still 87 FTBFS bugs to fix in stable. You are of course free to not help me fixing yours. Per the Developers Reference, a mass bug filing of many bugs on the same topic is required to be discussed before filing. Hmm, I have made a mistake in the wording which has led to a misunderstanding. I didn't say those 87 FTBFS bugs were of the same type. The ones about missing build-depends are already filed, and most of them are also unfixed in bookworm, so I believe they are correctly filed. The other bugs in bullseye are of very different types. Quite a number of them were already reported by Lucas Nussbaum and fixed in unstable but not in bullseye, where they also happen. An example: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997580 In cases like that I have to "resurrect" the bug and usually I propose a debdiff to the maintainer for the bullseye upload, when I can. This is not fixing a bug retroactively, this is ensuring that packages in stable build in stable, something that we promised at release time and are not honoring yet (but we are very close). There are also quote a number of FTBFS bugs which happen because they contained a "time bomb": https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025096 Again, this is not fixing a package retroactively, it's that the package had a silly unit test which was destined to fail in the future. I think it is important to honor the promises we made to the users. We promised a stable release without FTBFS bugs, and we are almost delivering it, but not completely. In the end, it boils down to where do we draw the line. You think having a reduced number of packages which FTBFS according to Policy is ok. I think the only acceptable number of FTBFS bugs to have in a stable release is zero, and I am working towards such goal. So the only thing I ask is that you do not insist that this is not a bug when I reopen it for bullseye. Since I will be the one doing the work, I think I should be allowed to use the BTS to track those bugs. Thanks.
Bug#1026709: python-pykka: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13
tag 1026709 pending thanks Hi, I've just uploaded the latest upstream version, 3.1.1, which no longer uses the previously deprecated and now removed `asyncio.coroutine` decorator. This was previously blocked by pyproject/Poetry not being well supported by Debian packaging, but it seems that is no longer the situation, and getting in sync with upstream was now trivial. I forgot to add a `Closes` tag to the changelog, so I'll close this issue manually once the new version hits the archive. -jodal signature.asc Description: PGP signature
Bug#1025389: libgl1-mesa-dri: AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
Am Sun, Jan 01, 2023 at 11:02:08PM +0100 schrieb Eduard Bloch: > reopen 1025389 > severity 1025389 serious > thanks > > Am Sun, Jan 01, 2023 at 02:29:01PM +0100 schrieb Fabio Pedretti: > > Version: 22.3.0-3 > > > > 22.3.0-3 reenabled two intel drivers missing in previou release. > > Why the heck are you closing this when the very specific issue in the > subject is not resolved? And the fun goes on. After some websearch, I found: https://www.phoronix.com/review/ivy-bridge-crocus So was THAT supposed to replace i965 support in mesa-22? Well, then it simply DOES NOT WORK. Yes, I found that crocus lib. But: MESA_LOADER_DRIVER_OVERRIDE=crocus strace -f -o wtf.log vlc ... $ grep crocus wtf.log 21999 openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/dri/tls/crocus_dri.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) 21999 openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/dri/crocus_dri.so", O_RDONLY|O_CLOEXEC) = 23 21999 write(2, "failed to load driver: crocus\n", 30) = 30 22019 openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/dri/tls/crocus_dri.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) 22019 openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/dri/crocus_dri.so", O_RDONLY|O_CLOEXEC) = 28 22019 openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/dri/tls/crocus_dri.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) 22011 openat(AT_FDCWD, "/usr/lib/x86_64-linux-gnu/dri/tls/crocus_dri.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (Datei oder Verzeichnis nicht gefunden) 22011 write(2, "failed to load driver: crocus\n", 30) = 30 So, and now? Is that internal implementation change something which was supposed to be communicated to users? If yes, where are the docs? If not, why is this not at least sufficiently transparent to developers, and made easy to debug? In any case, it seems to be broken as of now.
Bug#1026695: undertow: FTBFS: make: *** [debian/rules:4: build] Error 25
This is some kind of incompatibility with jboss-classfilewriter 1.3.0. I will look into it after the release of Debian 12. Undertow should not be part of a stable release as long as there is no real demand for another Java web server anyway. signature.asc Description: This is a digitally signed message part
Processed: Re: libgl1-mesa-dri: AIGLX error: dlopen of /usr/lib/x86_64-linux-gnu/dri/i965_dri.so
Processing commands for cont...@bugs.debian.org:
> reopen 1025389
Bug #1025389 {Done: Fabio Pedretti }
[libgl1-mesa-dri] libgl1-mesa-dri: AIGLX error: dlopen of
/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
'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 22.3.0-3.
> severity 1025389 serious
Bug #1025389 [libgl1-mesa-dri] libgl1-mesa-dri: AIGLX error: dlopen of
/usr/lib/x86_64-linux-gnu/dri/i965_dri.so
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1025389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1017892, #1017906: vendored stuff in librsvg
Processing control commands: > severity 1017892 wishlist Bug #1017892 [src:librsvg] librsvg: Has vendored copies of Rust libraries that are in Debian Ignoring request to change severity of Bug 1017892 to the same value. > severity 1017906 serious Bug #1017906 [src:librsvg] librsvg: Contains generated files whose source is not necessarily the same version that's in main Ignoring request to change severity of Bug 1017906 to the same value. -- 1017892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017892 1017906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017906 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#1017892, #1017906: vendored stuff in librsvg
Processing control commands: > severity 1017892 wishlist Bug #1017892 [src:librsvg] librsvg: Has vendored copies of Rust libraries that are in Debian Severity set to 'wishlist' from 'serious' > severity 1017906 serious Bug #1017906 [src:librsvg] librsvg: Contains generated files whose source is not necessarily the same version that's in main Severity set to 'serious' from 'wishlist' -- 1017892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017892 1017906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017906 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017892: , #1017906: vendored stuff in librsvg
Control: severity 1017892 wishlist Control: severity 1017906 serious On Sun, 01 Jan 2023 at 17:15:19 +0100, Paul Gevers wrote: > On Mon, 22 Aug 2022 14:29:56 -0700 Sean Whitton > wrote: > > #1017892 is wishlist or not a bug. [...] > > > #1017906 *might* be a problem. [...] > > It seems like you mixed up the bugs in your control message? I'm not Sean, but I agree the one that is *maybe* RC is #1017906 (depending on how the ftp team choose to interpret the source code requirement, corresponding source, and similar things), while #1017892 (use of vendored Rust at versions chosen by upstream) is not. If the ftp team consider #1017906 to be RC, then the solution to it is to bundle another copy of GLib source code with librsvg, corresponding to the version of GLib's GObject-Introspection data in vendor/glib-sys, similar to what I did for src:gobject-introspection (I used 3.0 (quilt) multiple original tarballs, which seemed slightly nicer than dropping it into debian/ and having it duplicated in every Debian revision). Using the GIR XML generated by Debian's GLib is not a solution, because that would result in glib-sys changing its API whenever it was rebuilt with a newer (or older!) GLib, and rebuilt libraries changing their APIs is generally bad news. I personally think GIR XML is a reasonable form for modification and a plausible way to exercise freedom-to-modify, despite not being the "least-derived" source, but it is true that it was mechanically generated from GLib's C code and is not the form you would modify to make an upstream contribution (the upstream of vendor/glib-sys is unlikely to accept any contribution to the GIR XML not of the form "update to GLib x.y.z", but the DFSG does not require that changes made downstream could be accepted upstream, and if it did then we would immediately lose sqlite and some GNU projects). As a result, I personally think this is not a particularly productive use of Debian maintainers' time; but if it's a requirement then I'll try to make time for it at some point, at the cost of an equivalent amount of other Debian work not getting done. smcv
Bug#1027380: marked as done (safeclib: FTBFS in bullseye (missing build-depends on tzdata))
Your message dated Sun, 01 Jan 2023 21:18:13 + with message-id and subject line Bug#1027380: fixed in safeclib 3.7.1-2 has caused the Debian Bug report #1027380, regarding safeclib: FTBFS in bullseye (missing build-depends on tzdata) 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.) -- 1027380: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027380 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:safeclib Version: 3.5-3 Severity: serious Tags: ftbfs patch Dear maintainer: During a rebuild of all packages in bullseye, your package failed to build: [...] debian/rules build-arch dh build-arch dh_update_autotools_config -a dh_autoreconf -a [...] FAIL: t_gmtime_s FAIL: t_localtime_s PASS: t_getenv_s PASS: t_bsearch_s PASS: t_qsort_s = Safe C Library 04062019.0-ga99a05: tests/test-suite.log = # TOTAL: 124 # PASS: 122 # SKIP: 0 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: t_gmtime_s FAIL t_gmtime_s (exit status: 1) FAIL: t_localtime_s === FAIL t_localtime_s (exit status: 1) [...] make[3]: *** [Makefile:4324: check-am] Error 2 make[3]: Leaving directory '/<>/tests' make[2]: *** [Makefile:1188: check-recursive] Error 1 make[2]: Leaving directory '/<>' make[1]: *** [Makefile:1492: check] Error 2 make[1]: Leaving directory '/<>' dh_auto_test: error: make -j2 check VERBOSE=1 returned exit code 2 make: *** [debian/rules:9: build-arch] Error 25 dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit status 2 (The above is just how the build ends and not necessarily the most relevant part) Note: I'm using the "patch" tag because there is an obvious fix (indicated in the subject). About the archive rebuild: The build was made using virtual machines from Hetzner, with enough memory, enough disk, and either one or two CPUs, using a reduced chroot with only build-essential packages (plus debhelper). If you could not reproduce the bug please contact me privately, as I am willing to provide ssh access to a virtual machine where the bug is fully reproducible. If this is really a bug in one of the build-depends, please use reassign and affects, so that this is still visible in the BTS web page for this package. Thanks. --- End Message --- --- Begin Message --- Source: safeclib Source-Version: 3.7.1-2 Done: Adam Borowski We believe that the bug you reported is fixed in the latest version of safeclib, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adam Borowski (supplier of updated safeclib 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, 01 Jan 2023 19:17:45 +0100 Source: safeclib Architecture: source Version: 3.7.1-2 Distribution: unstable Urgency: medium Maintainer: Adam Borowski Changed-By: Adam Borowski Closes: 1027380 Changes: safeclib (3.7.1-2) unstable; urgency=medium . * Add tzdata to B-Depends. Closes: #1027380. Checksums-Sha1: 6ae406824a41b187ff1c119c9044ad86462b9a6d 1919 safeclib_3.7.1-2.dsc 023eac9800dba64b66a5c3b5afeafed274e76906 3992 safeclib_3.7.1-2.debian.tar.xz 0569852d2b22713e11025eb43b359d7975ef28e3 5702 safeclib_3.7.1-2_source.buildinfo Checksums-Sha256: 973fc2ffe5697bb14efd8392a143ca4807ca15eac1e86558cd3997679f912d64 1919 safeclib_3.7.1-2.dsc 435beb30e7f6aca777b65e5b434bb9020a923dfbfce97b1c5fe7fba24ed01597 3992 safeclib_3.7.1-2.debian.tar.xz 62167ebe22587e3691fdd711ce960a8fe925c7af090034f02bbfeb8c1cb67c43 5702 safeclib_3.7.1-2_source.buildinfo Files: 7edac73cde8812288927192fbb254ab2 1919 libs optional safeclib_3.7.1-2.dsc 339395b9e9fb5b8ee42aa2c6c6fb5fee 3992 libs optional safeclib_3.7.1-2.debian.tar.xz bb207d1eb1cab0650fe6acd852e20c92 5702 libs optional safeclib_3.7.1-2_source.buildinfo -BEGIN PGP
Bug#1025530: marked as done (llvm-toolchain-15: FTBFS with grpc 1.51+)
Your message dated Sun, 01 Jan 2023 21:15:26 + with message-id and subject line Bug#1025530: fixed in llvm-toolchain-15 1:15.0.6-4 has caused the Debian Bug report #1025530, regarding llvm-toolchain-15: FTBFS with grpc 1.51+ 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.) -- 1025530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025530 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: llvm-toolchain-15 Version: 1:15.0.6-2 Severity: important Usertags: grpc1_51 Tags: ftbfs bookworm sid Hi, I'm going to start the gRPC transition real soon. Your package FTBFS with it. Main reason is that during stage 2 build bin/clangd-index-server-monitor needs to link with -lgpr and -labsl_synchronization as well. Due to time constraints I can't (yet) provide you a drop-in patch - but the solution is provided above. Please look into it and be prepared to take core of it when time comes. Thanks, Laszlo/GCS --- End Message --- --- Begin Message --- Source: llvm-toolchain-15 Source-Version: 1:15.0.6-4 Done: Sylvestre Ledru We believe that the bug you reported is fixed in the latest version of llvm-toolchain-15, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1025...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sylvestre Ledru (supplier of updated llvm-toolchain-15 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 01 Jan 2023 15:46:39 +0100 Source: llvm-toolchain-15 Architecture: source Version: 1:15.0.6-4 Distribution: unstable Urgency: medium Maintainer: LLVM Packaging Team Changed-By: Sylvestre Ledru Closes: 1025530 Changes: llvm-toolchain-15 (1:15.0.6-4) unstable; urgency=medium . * link-grpc.diff: add the detection of other libs necessary for grpc (Closes: #1025530) Checksums-Sha1: afc3f8b26850eb779f6a06862c2fa1c9152a90dd 7419 llvm-toolchain-15_15.0.6-4.dsc d51f5c8c306f01b50efa8138341924afcd662359 163088 llvm-toolchain-15_15.0.6-4.debian.tar.xz c0cbc4beda1564f7d94e5c6a86cc193afedd6947 32028 llvm-toolchain-15_15.0.6-4_amd64.buildinfo Checksums-Sha256: c357851e89ddb0e0e81c60614690f439bc974452747cd129c9f125ddccdf250c 7419 llvm-toolchain-15_15.0.6-4.dsc 78f1e31b1d615755175b1d2d4e8427cecf2fd55a78b42b2fa7f98b538cfed7b5 163088 llvm-toolchain-15_15.0.6-4.debian.tar.xz d4720e1b6477d16bbbea58a523e31a8dfd490fab640295a8e27736aa0d44d746 32028 llvm-toolchain-15_15.0.6-4_amd64.buildinfo Files: 6e7e2cbbcdf953de1aee6ead04789532 7419 devel optional llvm-toolchain-15_15.0.6-4.dsc cffb4c379b864c264ba6a375df3a3a1c 163088 devel optional llvm-toolchain-15_15.0.6-4.debian.tar.xz da4f83ce3e307e949f69f85038c05239 32028 devel optional llvm-toolchain-15_15.0.6-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmOx5/EACgkQfmUo2nUv G+G88hAAmnWxHUNXlro22UUEG4J8HdqmWvkAwb3FI2s82UdPt/3pCHo9pU17UNjm lPtyfdu/sI3jyReqaHltXtHH6LtVWD94oL2iy62w5kUrHXe9rZFpR7uz7CuACgwU IwV5NJ555Do7/LzdWI9gW1YWNfUgevNUuTs0lrClej/Mn4/6p4Jn+lcj3nuCBH4D fd/WP7NG7mngTswOVEZjXFdup2cjix56d5SBRR244Rzc8COKZxTLLMfgH+VMmeu0 JNHtZ0//eA65CNI6mjdIn8/+tl+uVyobUeXL71a5le7eyIrehJ6KBqwUKVJwp1z5 Ng66F4s/+8iawPLzx+qAiX3XihY7E6bDz3Sm6oEkJwFqOZ9mvEsjsaauPyUNAKxg Tev6nt/jwFQpMGF4QpnejMOvxvl6JHmauJjXhXgPb1z/TDwL3jL/2m2d6f6lF5Aa hniTIvUCxV9zRUXTdUtIJlOF8yFcKTF+/84TlR9uEFkTmP7joX2rvGzqZ1X+9wy2 S7WI4Rq+PbJyn64xsbBRBM3FNUL6dtsENIEd4vw31DtnTN36hbGq49aLJBlPqd/A vd0Fy2z5SovMlLeWGv5hJUZZFfYP8jHQc4AlepE8uKZW0O8qpuVd/ehDTR5o7hB1 RDsk0xWc4IukC5uOYXs2Nag8vefh3l58IKP52gACwIT06OKAUfk= =2mC0 -END PGP SIGNATURE End Message ---
Bug#1027380: safeclib: FTBFS in bullseye (missing build-depends on tzdata)
On Sun, Jan 01, 2023 at 01:53:31PM +0100, Santiago Vila wrote: > Adam Borowski escribió: > > nor any of people running archive rebuilds so far. > > FWIW: I am one of those people running archive rebuilds. > I rebuilt the entire bullseye distribution, and I'm trying > to make it FTBFS bug free, as mandated by both Debian Policy > and Release Policy. Bullseye has been a non-moving target for two years, thus changing requirements packages there are expected to meet is grossly belated. There are cases where adding such a requirement is worth the effort (eg. new hardware, or a hitherto unknown type of bugs), but I don't see how something with no practical benefit qualifies. This doesn't mean I intend to stop your efforts for releases currently in development -- I've already fixed this very bug in unstable (even though I disagree with the premise). But doing this for stable... come on... On Sun, Jan 01, 2023 at 01:46:06PM +0100, Santiago Vila wrote: > El 1/1/23 a las 12:58, Adam Borowski escribió: > > Control: tags -1 +unreproducible moreinfo > > I don't think the unreproducible tag applies here. > > To reproduce, just try to build it in a chroot which does > not include tzdata. If debootstrap does not do that by default, > then it follows that you should not simply accept debootstrap's defaults. No tool in Bullseye produces such build chroots, and this is what matters here. There's no practical benefit of retroactively changing packages: neither security rebuilds nor packages built by the users themselves will lack tzdata (the former because of build tools, the latter because of how Policy 2.5 defines "required"). Thus: I argue this is not a bug, and that even if it actually is a bug, there are no practical benefits of fixing it in _stable_. We are free to redefine requirements for future releases, of course. > This is Policy 4.2: > > > If build-time dependencies are specified, it must be possible to build the > > package and produce working binaries on a system with only essential and > > build-essential packages installed and also those required to satisfy the > > build-time relationships > (including any implied relationships). > > So yes, this is undoubtedly a bug, because tzdata is not build-essential. It is. It is merely not included in the _informational_ list shipped by a metapackage by that name; it explicitly says: # This package is NOT the definition of what packages are # build-essential; the real definition is in the Debian Policy Manual. # This package contains merely an informational list, which is all # most people need. However, if this package and the manual disagree, # the manual is correct. And Policy 4.2 which you just quoted says: # (including any implied relationships) I'd say that the Policy declaring systems that lack Priority:required packages to be broken fulfills this clause. > I could agree that everything would be easier if debootstrap was fixed once > and forever: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837060 > > If you can push for that bug to be fixed for bookworm, that would certainly > help. It seems that multiple debootstrap maintainers disagree -- and so do I. But, as I said before, I have no real objections to changing this for Bookworm. Making an upload to add the B-Dependency was less effort than arguing, and I've already one so, thus complying with whatever rule wins. > > I have nothing against adding such a B-Dependency in unstable: this is where > > new development is supposed to be done, preparing a new upload costs but a > > few mins of my time. On the other hand, updating stable requires extensive > > process and wastes the time of me, the Release Team, of people preparing the > > new point release announcement, of users testing and deploying the update. > > Of course fixing bugs takes a little bit of time, but it may also be argued > that > not fixing this kind of bugs produces weird effects which makes some people > to lose > some of their time (for example, me building the whole archive trying to keep > stable free > from any kind of FTBFS bugs). These bugs are caused only by your intentional change to build chroots you use. You can save that time by not doing that _active_ step for past releases. > If, despite having a trivial fix for the bug, you decide > not to fix it in stable and leave the fix for others, I will have less time > for other things > which I also want to fix. I know that some people will not agree, but I > believe fixing > FTBFS bugs in stable should be primarily a responsibility of the affected > maintainers. > Offloading the work to those particularly interested in stable does not scale > well. I'm all for fixing bugs in stable that: * are obviously bugs (rather than a point of debate) * have a practical effect (because our process for stable update is a lot of work) > I have still 87 FTBFS bugs to fix in stable. You are of course free to > not help me fixing yours. Per the
Bug#1019707: snapd-glib: flaky autopkgtest, particularly on s390x: Test timed out after 300 seconds
Hi, On Tue, 13 Sep 2022 21:10:59 +0200 Paul Gevers wrote: I looked at the results of the autopkgtest of your package. I noticed that it regularly fails s390x and seems to fail everywhere once in a while. I had a further look today to try and spot a pattern, but really, all the logs I check failed at a different test. And it looks like it behaves "weird" before the time out. I.e. it's reporting a lot of lines like: Executing: snapd-glib/test-glib.test which from my reading of [1] is printed when the test is idle. I had the idea that maybe this was due to race conditions between different tests, but from [2] I gathered that the default is no parallelism, and I couldn't spot it being changed. Therefore I conclude that without the root cause found (I suspect in gnome-desktop-testing-runner), it's better to either disable the autopkgtest, or mark it as flaky. An alternative could be to disable the test-glib and test-qt tests, as they seem to always be involved. I'm not sure if the rest is worth it and/or more than superficial. Paul [1] https://gitlab.gnome.org/GNOME/gnome-desktop-testing/-/blob/master/src/gnome-desktop-testing-runner.c#L766 [2] https://manpages.debian.org/testing/gnome-desktop-testing/gnome-desktop-testing-runner.1.en.html For info, my log: https://ci.debian.net/data/autopkgtest/testing/s390x/s/snapd-glib/29785580/log.gz FAIL: snapd-glib-2/test-qt.test (Child process killed by signal 8) snapd-glib-2/test-glib.test after /get-system-information/refresh_schedule https://ci.debian.net/data/autopkgtest/testing/s390x/s/snapd-glib/29782315/log.gz snapd-glib-2/test-glib.test after /install/async-failure snapd-glib-2/test-qt.test after /list/sync https://ci.debian.net/data/autopkgtest/testing/s390x/s/snapd-glib/29760350/log.gz ok 98 /get-interfaces2/only-connected Executing: snapd-glib-2/test-qt.test https://ci.debian.net/data/autopkgtest/testing/s390x/s/snapd-glib/29747711/log.gz ok 36 /get-changes/filter-ready-snap Executing: snapd-glib-2/test-qt.test ok 80 /get-assertions/sync Executing: snapd-glib-2/test-glib.test https://ci.debian.net/data/autopkgtest/testing/s390x/s/snapd-glib/29706490/log.gz ok 143 /install/progress Executing: snapd-glib-2/test-glib.test ok 113 /find/bad-query Executing: snapd-glib-2/test-qt.test https://ci.debian.net/data/autopkgtest/testing/s390x/s/snapd-glib/29541611/log.gz ok 207 /check-buy/not-logged-in Executing: snapd-glib-2/test-glib.test https://ci.debian.net/data/autopkgtest/testing/s390x/s/snapd-glib/29352834/log.gz ok 27 /login/otp-invalid Executing: snapd-glib-2/test-qt.test https://ci.debian.net/data/autopkgtest/testing/s390x/s/snapd-glib/29352833/log.gz ok 58 /get-snap/classic-confinement Executing: snapd-glib-2/test-glib.test https://ci.debian.net/data/autopkgtest/testing/s390x/s/snapd-glib/29290447/log.gz ok 12 /maintenance/none Executing: snapd-glib/test-glib.test ok 41 /list/sync Executing: snapd-glib/test-qt.test OpenPGP_signature Description: OpenPGP digital signature
Bug#1027628: snapper: FTBFS: regex_compiler.tcc:179:19: error: expected unqualified-id before ‘=’ token
control: tags -1 +confirmed
control: tags -1 +forwarded https://github.com/openSUSE/snapper/issues/762
control: tags -1 +upstream
It was introduced with a change in libbtrfs-dev_6.1-1,
/usr/include/btrfs/kerncompat.h.
https://github.com/kdave/btrfs-progs/commit/788a71c16a917f8357784571106537a1d42012e8
> typedef struct wait_queue_head_s {
> } wait_queue_head_t;
>
> #define __init
> #define __cold
>
> #endif
Just commented out "#define __init", it can be compiled.
--
Regards,
Hideki Yamane henrich @ debian.org/iijmio-mail.jp
Processed (with 1 error): Re: snapper: FTBFS: regex_compiler.tcc:179:19: error: expected unqualified-id before ‘=’ token
Processing control commands: > tags -1 +confirmed Bug #1027628 [src:snapper] snapper: FTBFS: regex_compiler.tcc:179:19: error: expected unqualified-id before ‘=’ token Added tag(s) confirmed. > tags -1 +forwarded https://github.com/openSUSE/snapper/issues/762 Unknown tag/s: forwarded, https://github.com/openSUSE/snapper/issues/762. Recognized are: patch wontfix moreinfo unreproducible help security upstream pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye bullseye-ignore bookworm bookworm-ignore trixie trixie-ignore. Bug #1027628 [src:snapper] snapper: FTBFS: regex_compiler.tcc:179:19: error: expected unqualified-id before ‘=’ token Requested to add no tags; doing nothing. > tags -1 +upstream Bug #1027628 [src:snapper] snapper: FTBFS: regex_compiler.tcc:179:19: error: expected unqualified-id before ‘=’ token Added tag(s) upstream. -- 1027628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027628 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027623: marked as done (hatch-vcs: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)
Your message dated Sun, 01 Jan 2023 20:59:40 +
with message-id
and subject line Bug#1027623: fixed in hatch-vcs 0.3.0-2
has caused the Debian Bug report #1027623,
regarding hatch-vcs: FTBFS: dh_auto_test: error: pybuild --test --test-pytest
-i python{version} -p "3.11 3.10" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1027623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hatch-vcs
Version: 0.3.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild plugin_pyproject:107: Building wheel for python3.11 with "build"
> module
> I: pybuild base:240: python3.11 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.11_hatch-vcs
> * Building wheel...
> Successfully built hatch_vcs-0.3.0-py3-none-any.whl
> I: pybuild plugin_pyproject:119: Unpacking wheel built for python3.11 with
> "installer" module
> I: pybuild plugin_pyproject:107: Building wheel for python3.10 with "build"
> module
> I: pybuild base:240: python3.10 -m build --skip-dependency-check
> --no-isolation --wheel --outdir
> /<>/.pybuild/cpython3_3.10_hatch-vcs
> * Building wheel...
> Successfully built hatch_vcs-0.3.0-py3-none-any.whl
> I: pybuild plugin_pyproject:119: Unpacking wheel built for python3.10 with
> "installer" module
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd
> /<>/.pybuild/cpython3_3.11_hatch-vcs/build; python3.11 -m pytest
> tests
> = test session starts
> ==
> platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack
> rootdir: /<>/.pybuild/cpython3_3.11_hatch-vcs/build
> collected 22 items
>
> tests/test_build.py .F...[
> 22%]
> tests/test_build_config.py ..[
> 50%]
> tests/test_metadata_config.py [
> 68%]
> tests/test_version_config.py ...
> [100%]
>
> === FAILURES
> ===
> __ test_write
> __
>
> new_project_write = '/tmp/tmpffnpiawl/my-app'
>
> def test_write(new_project_write):
> build_project('-t', 'wheel')
>
> build_dir = os.path.join(new_project_write, 'dist')
> assert os.path.isdir(build_dir)
>
> artifacts = os.listdir(build_dir)
> assert len(artifacts) == 1
> wheel_file = artifacts[0]
>
> assert wheel_file == 'my_app-1.2.3-py2.py3-none-any.whl'
>
> extraction_directory =
> os.path.join(os.path.dirname(new_project_write), '_archive')
> os.mkdir(extraction_directory)
>
> with zipfile.ZipFile(os.path.join(build_dir, wheel_file), 'r') as
> zip_archive:
> zip_archive.extractall(extraction_directory)
>
> metadata_directory = os.path.join(extraction_directory,
> 'my_app-1.2.3.dist-info')
> assert os.path.isdir(metadata_directory)
>
> package_directory = os.path.join(extraction_directory, 'my_app')
> assert os.path.isdir(package_directory)
> assert len(os.listdir(package_directory)) == 5
>
> assert os.path.isfile(os.path.join(package_directory, '__init__.py'))
> assert os.path.isfile(os.path.join(package_directory, 'foo.py'))
> assert os.path.isfile(os.path.join(package_directory, 'bar.py'))
> assert os.path.isfile(os.path.join(package_directory, 'baz.py'))
>
> version_file = os.path.join(package_directory, '_version.py')
> assert os.path.isfile(version_file)
>
Bug#1027666: marked as done (binutils-mingw-w64: FTBFS: patches fail to apply Error 1)
Your message dated Sun, 01 Jan 2023 20:49:51 + with message-id and subject line Bug#1027666: fixed in binutils-mingw-w64 10 has caused the Debian Bug report #1027666, regarding binutils-mingw-w64: FTBFS: patches fail to apply Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027666 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: binutils-mingw-w64 Version: 9 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 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 '/<>' > tar xf /usr/src/binutils/binutils-2.39.50.tar.* > rm -rf /<>/upstream > mv binutils-* /<>/upstream > patch -d /<>/upstream -R -p1 < > /usr/src/binutils/patches/001_ld_makefile_patch.patch > patching file ld/Makefile.am > patching file ld/Makefile.in > Hunk #1 succeeded at 575 (offset 2 lines). > QUILT_SERIES=debian/patches/series QUILT_PATCHES=debian/patches quilt push -a > Applying patch debian/patches/testsuite-timeout.patch > patching file upstream/gas/testsuite/lib/gas-defs.exp > > Applying patch debian/patches/specify-timestamp.patch > patching file upstream/bfd/peXXigen.c > Hunk #1 succeeded at 74 with fuzz 2 (offset -3 lines). > Hunk #2 succeeded at 850 (offset -8 lines). > patching file upstream/ld/pe-dll.c > Hunk #2 succeeded at 1230 (offset 9 lines). > patching file upstream/ld/emultempl/pe.em > Hunk #1 succeeded at 338 (offset 20 lines). > patching file upstream/ld/emultempl/pep.em > Hunk #1 succeeded at 381 with fuzz 1 (offset 44 lines). > > Applying patch debian/patches/dont-run-objcopy.patch > patching file upstream/binutils/testsuite/binutils-all/objcopy.exp > Hunk #1 succeeded at 703 (offset 47 lines). > > Applying patch debian/patches/disable-flags.patch > patching file upstream/ld/emultempl/pe.em > Hunk #1 FAILED at 262. > Hunk #2 succeeded at 377 (offset 20 lines). > 1 out of 2 hunks FAILED -- rejects in file upstream/ld/emultempl/pe.em > patching file upstream/ld/emultempl/pep.em > Hunk #1 succeeded at 390 (offset 47 lines). > Patch debian/patches/disable-flags.patch does not apply (enforce with -f) > make[1]: *** [debian/rules:71: unpack] Error 1 The full build log is available from: http://qa-logs.debian.net/2023/01/01/binutils-mingw-w64_9_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230101=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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: binutils-mingw-w64 Source-Version: 10 Done: Stephen Kitt We believe that the bug you reported is fixed in the latest version of binutils-mingw-w64, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen Kitt (supplier of updated binutils-mingw-w64 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, 01 Jan 2023 20:35:22 +0100 Source: binutils-mingw-w64 Architecture: source Version: 10 Distribution: unstable Urgency: medium Maintainer: Stephen Kitt Changed-By: Stephen Kitt Closes: 1027666 Changes: binutils-mingw-w64 (10) unstable; urgency=medium . * Adjust for binutils 2.40. Closes: #1027666. * Standards-Version 4.6.2, no change required. * Update Lintian overrides
Bug#1026719: vmg: FTBFS: /usr/bin/ld.bfd: cannot find -latk-1.0: No such file or directory
Abou Al Montacir, le dim. 01 janv. 2023 20:02:51 +0100, a ecrit: > Lucas Nussbaum, le mar. 20 déc. 2022 18:31:46 +0100, a ecrit: > > Linking ./vmg > /usr/bin/ld.bfd: cannot find -lgdk-x11-2.0: No such file or > directory > /usr/bin/ld.bfd: cannot find -lgtk-x11-2.0: No such file or > directory > > ... > > /usr/bin/ld.bfd: cannot find -latk-1.0: No such file or directory > > > Yes, we had discussed it a bit in #967798, it is an issue in Lazarus: > fp-units-gtk2-3.2.0 used to have the libgtk2.0-dev dependency, but > fp-units-gtk2-3.2.2 doesn't any more, but it should, it shouldn't be up > to users of the gtk2 unit to know which C dependency it should take. > > > Sorry, but, as FPC maintaining team member, I don't share this __ should __ > statement for the following reasons. > > • GTK2 is declared as deprecated in Debian since long time ago. Yes, sure. > • Technically, Lazarus doe snot need libgtk2.0-dev for running, and thus > should not pull it. Lazarus itself, no indeed. But the fp-units-gtk2-3.2.0 package does not make any sense without libgtk2.0-dev, since there is no way to use the former without the latter. > • Technically, FPC does not need any GTK related lib, it only provide > binding > units. Yes, and *all* languages that provide bindings do provide the required pulls so that users of the bindings don't have to care about what should be pulled. The information is recorded in only the bindings package, and not sprinkled over all packages that happen to use it (which would require changes in all of them for no good reason whenever the underlying C library happens to change its C API, for instance). Things were just working perfectly previously. Why breaking the build of packages using fp-units-gtk2-3.2.0 by dropping the pull? Is there an *actual* reason for not making fp-units-gtk2-3.2.0 pull it, how does it hurt in any way? Is that because fpc-3.2.0 happens to depend on it? Then why does it do so, since from what you say it does not actually need it? Really, I don't understand: fp-units-gtk2-3.2.0 does need libgtk2.0-dev to work at all, while you are saying that fpc-3.2.0 does not need fp-units-gtk2-3.2.0 to work. The current "Depends" that are set on those package are exactly the inverse of that... > • For building, Lazarus build depends on libgtk2.0-dev, until it will > migrate > to gtk3. And so shall do all programs that use it. Yes, sure. But for bookworm we'll apparently stay with gtk2, so let's make that that works, at least. > I hope this makes it clear, why neither Lazarus, nor FPC or any of their > packages should pull libgtk2.0-dev package. No, not at all. > You should handle this bug in VMG, and probably the best way to do it is to > build depend on libgtk-2.0-dev >From point point of view it's not the best way since it means that'll be yet something more to change when switching to gtk3, then to gtk4, etc. while everything could be just handled in the bindings package. > until you fix [2]https://bugs.debian.org/cgi-bin /bugreport.cgi?bug=967799 That only boils down to making lazarus support gtk3, since vmg just uses LCL. If Lazarus was providing a gtk bindings package which does not encode the 2 vs 3 notion, the vmg package would be more than happy to just use it and not have to care at all about the underlying incompatibilities. Samuel
Processed: Bug#1027623 marked as pending in hatch-vcs
Processing control commands:
> tag -1 pending
Bug #1027623 [src:hatch-vcs] hatch-vcs: FTBFS: dh_auto_test: error: pybuild
--test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13
Added tag(s) pending.
--
1027623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: update bts meta info
Processing commands for cont...@bugs.debian.org:
> reassign 1027461 src:beets 1.6.0-3
Bug #1027461 {Done: Stefano Rivera }
[src:python-mediafile, src:beets] python-mediafile breaks beets autopkgtest:
object of type 'NoneType' has no len()
Bug reassigned from package 'src:python-mediafile, src:beets' to 'src:beets'.
No longer marked as found in versions python-mediafile/0.11.0-1 and
beets/1.6.0-3.
No longer marked as fixed in versions beets/1.6.0-4.
Bug #1027461 {Done: Stefano Rivera } [src:beets]
python-mediafile breaks beets autopkgtest: object of type 'NoneType' has no
len()
Marked as found in versions beets/1.6.0-3.
> fixed 1027461 1.6.0-4
Bug #1027461 {Done: Stefano Rivera } [src:beets]
python-mediafile breaks beets autopkgtest: object of type 'NoneType' has no
len()
Marked as fixed in versions beets/1.6.0-4.
> affects 1027461 src:python-mediafile
Bug #1027461 {Done: Stefano Rivera } [src:beets]
python-mediafile breaks beets autopkgtest: object of type 'NoneType' has no
len()
Added indication that 1027461 affects src:python-mediafile
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1027461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1027623: marked as pending in hatch-vcs
Control: tag -1 pending Hello, Bug #1027623 in hatch-vcs reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/hatch-vcs/-/commit/02cd4417ba053dd18c322e6e021f9c88f3e8cc35 Patch: Support setuptools_scm 7.1 in tests. (Closes: #1027623) (this message was generated automatically) -- Greetings https://bugs.debian.org/1027623
Bug#1027418: autopkgtest failure - iconv issue?
Hi, Am 01.01.23 um 21:25 schrieb Changwoo Ryu: I can't reproduce it myself. I am not sure either what happens... In your test, every word failed to be checked with the same error and the error message came from hunspell, when iconv() conversion on text fails. Probably your chroot environment lacked some libs necessary for iconv(). Yes, but that then needs to be reflected in the test depends strictly speaking... There is a successful autopkgtest log with hunspell 1.7.2+really1.7.1-2: https://ci.debian.net/data/autopkgtest/testing/amd64/h/hunspell-dict-ko/29801950/log.gz Yeah, noticed that too... Regards, Rene
Processed: affects 1027615
Processing commands for cont...@bugs.debian.org: > affects 1027615 src:mini-buildd Bug #1027615 [src:dateparser] dateparser: FTBFS: build-dependency not installable: python3-regex (< 0.1.20220315) Added indication that 1027615 affects src:mini-buildd > thanks Stopping processing here. Please contact me if you need assistance. -- 1027615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027418: autopkgtest failure - iconv issue?
Hello, 2022년 12월 31일 (토) 오후 5:36, Rene Engelhard 님이 작성: > It even fails here locally with 1.7.2+really1.7.1-2 which I needed to do > due to > https://ci.debian.net/data/autopkgtest/testing/amd64/r/r-cran-hunspell/29793480/log.gz. > > In a clean chroot + test deps + python3 (see #1027417), I get: > > rene@frodo:~/hunspell-dict-ko-0.7.92$ make hosttest > HOST_DICT_PATH=/usr/share/hunspell/ko > make -C tests test DICT=/usr/share/hunspell/ko > make[1]: Entering directory '/home/rene/hunspell-dict-ko-0.7.92/tests' > echo | hunspell -d /usr/share/hunspell/ko | head -1 > Hunspell 1.7.1 - hunspell-dict-ko 0.7.92 (requires Hunspell 1.3.1) > https://spellcheck-ko.github.io/ > python3 checkhunspellversion.py > Testing 001-pos-dependent-inflection.test... > error - iconv: ANSI_X3.4-1968 -> UTF-8 > error - iconv: ANSI_X3.4-1968 -> UTF-8 > . > make[1]: *** [Makefile:9: test] Error 1 > make[1]: Leaving directory '/home/rene/hunspell-dict-ko-0.7.92/tests' > make: *** [Makefile:53: hosttest] Error 2 > > This is with LANG=C but C.UTF-8 or even ko_KR.UTF-8 have the same problem. > > Somehow I don't believe it's hunspell at fault here (especially as 1.7.1 > now also fails and it obviously passed once), but... I can't reproduce it myself. In your test, every word failed to be checked with the same error and the error message came from hunspell, when iconv() conversion on text fails. Probably your chroot environment lacked some libs necessary for iconv(). There is a successful autopkgtest log with hunspell 1.7.2+really1.7.1-2: https://ci.debian.net/data/autopkgtest/testing/amd64/h/hunspell-dict-ko/29801950/log.gz
Processed: closing 1027525
Processing commands for cont...@bugs.debian.org: > close 1027525 Bug #1027525 [src:exadrums] exadrums: FTBFS: build-dependency not installable: libexadrums-dev (>= 0.7.0) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1027525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027525 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027550: marked as done (nitime: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.11 3.10" returned exit code 13)
Your message dated Sun, 01 Jan 2023 19:23:03 +
with message-id
and subject line Bug#1027550: fixed in nitime 0.9-4
has caused the Debian Bug report #1027550,
regarding nitime: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p "3.11 3.10" returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1027550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nitime
Version: 0.9-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules binary
> dh binary --with python3 --buildsystem pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:240: python3.11 setup.py config
> I: pybuild base:240: python3.10 setup.py config
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:240: /usr/bin/python3.11 setup.py build
> I: pybuild base:240: /usr/bin/python3 setup.py build
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build;
> python3.11 -m pytest
> = test session starts
> ==
> platform linux -- Python 3.11.1, pytest-7.2.0, pluggy-1.0.0+repack
> rootdir: /<>
> collected 123 items
>
> nitime/algorithms/tests/test_autoregressive.py . [
> 4%]
> nitime/algorithms/tests/test_coherence.py ..s[
> 16%]
> nitime/algorithms/tests/test_correlation.py .[
> 17%]
> nitime/algorithms/tests/test_entropy.py .[
> 21%]
> nitime/algorithms/tests/test_event_related.py . [
> 21%]
> nitime/algorithms/tests/test_spectral.py [
> 34%]
> nitime/analysis/tests/test_base.py . [
> 35%]
> nitime/analysis/tests/test_coherence.py .. [
> 40%]
> nitime/analysis/tests/test_correlation.py . [
> 41%]
> nitime/analysis/tests/test_granger.py .. [
> 43%]
> nitime/analysis/tests/test_snr.py . [
> 43%]
> nitime/fmri/tests/test_io.py . [
> 44%]
> nitime/tests/test_algorithms.py ..F. [
> 51%]
> nitime/tests/test_analysis.py ...[
> 56%]
> nitime/tests/test_descriptors.py . [
> 57%]
> nitime/tests/test_lazy.py .. [
> 59%]
> nitime/tests/test_timeseries.py [
> 88%]
> nitime/tests/test_utils.py ... [
> 97%]
> nitime/tests/test_viz.py ...
> [100%]
>
> === FAILURES
> ===
> ___ test_psd_matlab
>
>
> def test_psd_matlab():
>
> """ Test the results of mlab csd/psd against saved results from
> Matlab"""
>
> from matplotlib import mlab
>
> test_dir_path = os.path.join(nitime.__path__[0], 'tests')
>
> ts = np.loadtxt(os.path.join(test_dir_path, 'tseries12.txt'))
>
> #Complex signal!
> ts0 = ts[1] + ts[0] * np.complex(0, 1)
>
> NFFT = 256
> Fs = 1.0
> noverlap = NFFT / 2
>
> > fxx, f = mlab.psd(ts0, NFFT=NFFT, Fs=Fs, noverlap=noverlap,
> scale_by_freq=True)
>
> nitime/tests/test_algorithms.py:154:
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> _
> /usr/lib/python3/dist-packages/matplotlib/mlab.py:584: in psd
> Pxx, freqs = csd(x=x, y=None, NFFT=NFFT, Fs=Fs, detrend=detrend,
> /usr/lib/python3/dist-packages/matplotlib/mlab.
Bug#1027554: marked as done (libpappsomspp: FTBFS: timsframe.cpp:84:22: error: incomplete type ‘QObject’ used in nested name specifier)
Your message dated Sun, 01 Jan 2023 19:22:54 +
with message-id
and subject line Bug#1027554: fixed in libpappsomspp 0.9.3-1
has caused the Debian Bug report #1027554,
regarding libpappsomspp: FTBFS: timsframe.cpp:84:22: error: incomplete type
‘QObject’ used in nested name specifier
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.)
--
1027554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpappsomspp
Version: 0.9.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++
> -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK -DBOOST_CHRONO_DYN_LINK
> -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK
> -DBOOST_THREAD_DYN_LINK -DPMSPP_LIBRARY -DQT_CONCURRENT_LIB
> -DQT_CORE5COMPAT_LIB -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG
> -DQT_NO_DEBUG_OUTPUT -DQT_SQL_LIB -DQT_SVG_LIB -DQT_XML_LIB -DWITHOUT_MZ5
> -I/<>/obj-x86_64-linux-gnu/src/pappsomspp-static_autogen/include
> -I/<>/obj-x86_64-linux-gnu -I/usr/include/liblzf -isystem
> /usr/include/pwizlite -isystem /usr/include/x86_64-linux-gnu/qt6/QtCore
> -isystem /usr/include/x86_64-linux-gnu/qt6 -isystem
> /usr/lib/x86_64-linux-gnu/qt6/mkspecs/linux-g++ -isystem
> /usr/include/x86_64-linux-gnu/qt6/QtXml -isystem
> /usr/include/x86_64-linux-gnu/qt6/QtSvg -isystem
> /usr/include/x86_64-linux-gnu/qt6/QtGui -isystem
> /usr/include/x86_64-linux-gnu/qt6/QtSql -isystem
> /usr/include/x86_64-linux-gnu/qt6/QtConcurrent -isystem
> /usr/include/x86_64-linux-gnu/qt6/QtCore5Compat -isystem
> /usr/include/libalglib -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -O3 -DNDEBUG -Wno-unknown-pragmas -Wall -Wextra -fPIC
> -fPIC -std=gnu++17 -MD -MT
> src/CMakeFiles/pappsomspp-static.dir/pappsomspp/fasta/fastafileindexer.cpp.o
> -MF
> CMakeFiles/pappsomspp-static.dir/pappsomspp/fasta/fastafileindexer.cpp.o.d -o
> CMakeFiles/pappsomspp-static.dir/pappsomspp/fasta/fastafileindexer.cpp.o -c
> /<>/src/pappsomspp/fasta/fastafileindexer.cpp
> /<>/src/pappsomspp/vendors/tims/timsframe.cpp: In constructor
> ‘pappso::TimsFrame::TimsFrame(std::size_t, quint32, char*, std::size_t)’:
> /<>/src/pappsomspp/vendors/tims/timsframe.cpp:84:22: error:
> incomplete type ‘QObject’ used in nested name specifier
>84 | QObject::tr("TimsFrame::TimsFrame(%1,%2,nullptr,%3)
> FAILED")
> | ^~
> /<>/src/pappsomspp/vendors/tims/timsframe.cpp: In member
> function ‘void pappso::TimsFrame::unshufflePacket(const char*)’:
> /<>/src/pappsomspp/vendors/tims/timsframe.cpp:109:18: error:
> incomplete type ‘QObject’ used in nested name specifier
> 109 | QObject::tr("TimsFrame::unshufflePacket error: len%4 != 0"));
> | ^~
> make[4]: *** [src/CMakeFiles/pappsomspp-shared.dir/build.make:1964:
> src/CMakeFiles/pappsomspp-shared.dir/pappsomspp/vendors/tims/timsframe.cpp.o]
> Error 1
The full build log is available from:
http://qa-logs.debian.net/2023/01/01/libpappsomspp_0.9.2-1_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230101=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please mark 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: libpappsomspp
Source-Version: 0.9.3-1
Done: Filippo Rusconi
We believe that the bug you reported is fixed in the latest version of
libpappsomspp, 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 f
Processed: reassign 1027601 to graph-tool ...
Processing commands for cont...@bugs.debian.org: > reassign 1027601 graph-tool Bug #1027601 [python-matplotlib-doc] python-matplotlib-doc: not installable in Sid Bug reassigned from package 'python-matplotlib-doc' to 'graph-tool'. Ignoring request to alter found versions of bug #1027601 to the same values previously set Ignoring request to alter fixed versions of bug #1027601 to the same values previously set > retitle 1027601 fix graph-tool, python-matplotlib-doc is no longer generated > by src:matplotlib Bug #1027601 [graph-tool] python-matplotlib-doc: not installable in Sid Changed Bug title to 'fix graph-tool, python-matplotlib-doc is no longer generated by src:matplotlib' from 'python-matplotlib-doc: not installable in Sid'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027629: python-biopython: FTBFS: Test DSSP generation from MMCIF with non-standard residues.
Hi Maarten,
This seems to stem from your latest upload of dssp. Could you consider taking
a look at this one?
Thanks,
Nilesh
On Sun, 1 Jan 2023 15:20:12 +0100 Lucas Nussbaum wrote:
> Source: python-biopython
> Version: 1.80+dfsg-4
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20230101 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 '/<>'
> > mkdir -p Tests_avoid
> > for avoid in PAML_tools EmbossPhylipNew MSAProbs_tool NACCESS_tool
> > PopGen_GenePop PopGen_GenePop_EasyController XXmotif_tool PDB_ResidueDepth
> > mmtf mmtf_online BioSQL_MySQLdb BioSQL_psycopg2 \
> > ; do \
> > mv Tests/test_${avoid}.py Tests_avoid ; \
> > done
> > mv: cannot stat 'Tests/test_NACCESS_tool.py': No such file or directory
> > # For the doc package we need a clean testsuite without all the remaining
> > files. So keep a clean copy here
> > mkdir -p debian/tmp_tests
> > cp -a Tests debian/tmp_tests
> > # remove duplicated file
> > rm -f debian/tmp_tests/Tests/Quality/example.fastq.gz
> > # We also keep the tests we need to avoid for later inspection
> > cp -a Tests_avoid debian/tmp_tests
> > # in the Debian package dialign it is not needed to set DIALIGN2_DIR but
> > the test is verifying this dir
> > # to run the EMBOSS test test_Emboss also requires to have the environment
> > variable EMBOSS_ROOT set
> > LC_ALL=C.UTF-8 dh_auto_test -- --test --system=custom \
> > --test-args='set -e; \
> > mkdir -p {build_dir}/home; \
> > mkdir -p {build_dir}/Doc/examples; \
> > cp -a Doc/Tutorial.tex {build_dir}/Doc; \
> > cp -a Doc/Tutorial {build_dir}/Doc; \
> > cp -a Doc/examples {build_dir}/Doc; \
> > cp -a Tests {build_dir}; \
> > cd {build_dir}/Tests; \
> > env DIALIGN2_DIR=/usr/share/dialign
> > EMBOSS_ROOT=/usr/lib/emboss HOME={build_dir}/home {interpreter}
> > run_tests.py --offline'
> > pybuild --test -i python{version} -p "3.11 3.10" --test --system=custom
> > "--test-args=set -e; \\\
> > mkdir -p {build_dir}/home; \\\
> > mkdir -p {build_dir}/Doc/examples; \\\
> > cp -a Doc/Tutorial.tex {build_dir}/Doc; \\\
> > cp -a Doc/Tutorial {build_dir}/Doc; \\\
> > cp -a Doc/examples {build_dir}/Doc; \\\
> > cp -a Tests {build_dir}; \\\
> > cd {build_dir}/Tests; \\\
> > env DIALIGN2_DIR=/usr/share/dialign
> > EMBOSS_ROOT=/usr/lib/emboss HOME={build_dir}/home {interpreter}
> > run_tests.py --offline"
> > I: pybuild base:240: set -e; \
> > mkdir -p
> > /<>/.pybuild/cpython3_3.11/build/home; \
> > mkdir -p
> > /<>/.pybuild/cpython3_3.11/build/Doc/examples; \
> > cp -a Doc/Tutorial.tex
> > /<>/.pybuild/cpython3_3.11/build/Doc; \
> > cp -a Doc/Tutorial
> > /<>/.pybuild/cpython3_3.11/build/Doc; \
> > cp -a Doc/examples
> > /<>/.pybuild/cpython3_3.11/build/Doc; \
> > cp -a Tests
> > /<>/.pybuild/cpython3_3.11/build; \
> > cd
> > /<>/.pybuild/cpython3_3.11/build/Tests; \
> > env DIALIGN2_DIR=/usr/share/dialign
> > EMBOSS_ROOT=/usr/lib/emboss
> > HOME=/<>/.pybuild/cpython3_3.11/build/home python3.11
> > run_tests.py --offline
> > test_Ace ... ok
--
Best,
Nilesh
signature.asc
Description: PGP signature
Bug#1027519: marked as done (beets: FTBFS: InputError: [Errno 2] No such file or directory: '../CONTRIBUTING.rst'.)
Your message dated Sun, 01 Jan 2023 19:19:40 + with message-id and subject line Bug#1027519: fixed in beets 1.6.0-4 has caused the Debian Bug report #1027519, regarding beets: FTBFS: InputError: [Errno 2] No such file or directory: '../CONTRIBUTING.rst'. 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.) -- 1027519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027519 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: beets Version: 1.6.0-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 ftbfs-bookworm 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 v5.3.0 > making output directory... done > WARNING: extlinks: Sphinx-6.0 will require a caption string to contain > exactly one '%s' and all other '%' need to be escaped as '%%'. > WARNING: extlinks: Sphinx-6.0 will require a caption string to contain > exactly one '%s' and all other '%' need to be escaped as '%%'. > WARNING: extlinks: Sphinx-6.0 will require a caption string to contain > exactly one '%s' and all other '%' need to be escaped as '%%'. > WARNING: extlinks: Sphinx-6.0 will require a caption string to contain > exactly one '%s' and all other '%' need to be escaped as '%%'. > building [mo]: targets for 0 po files that are out of date > building [html]: targets for 87 source files that are out of date > updating environment: [new config] 87 added, 0 changed, 0 removed > reading sources... [ 1%] changelog > reading sources... [ 2%] contributing > reading sources... [ 3%] dev/cli > reading sources... [ 4%] dev/importer > reading sources... [ 5%] dev/index > reading sources... [ 6%] dev/library > reading sources... [ 8%] dev/plugins > reading sources... [ 9%] faq > reading sources... [ 10%] guides/advanced > reading sources... [ 11%] guides/index > reading sources... [ 12%] guides/main > reading sources... [ 13%] guides/tagger > reading sources... [ 14%] index > reading sources... [ 16%] plugins/absubmit > reading sources... [ 17%] plugins/acousticbrainz > reading sources... [ 18%] plugins/albumtypes > reading sources... [ 19%] plugins/aura > reading sources... [ 20%] plugins/badfiles > reading sources... [ 21%] plugins/bareasc > reading sources... [ 22%] plugins/beatport > reading sources... [ 24%] plugins/bpd > reading sources... [ 25%] plugins/bpm > reading sources... [ 26%] plugins/bpsync > reading sources... [ 27%] plugins/bucket > reading sources... [ 28%] plugins/chroma > reading sources... [ 29%] plugins/convert > reading sources... [ 31%] plugins/deezer > reading sources... [ 32%] plugins/discogs > reading sources... [ 33%] plugins/duplicates > reading sources... [ 34%] plugins/edit > reading sources... [ 35%] plugins/embedart > reading sources... [ 36%] plugins/embyupdate > reading sources... [ 37%] plugins/export > reading sources... [ 39%] plugins/fetchart > reading sources... [ 40%] plugins/filefilter > reading sources... [ 41%] plugins/fish > reading sources... [ 42%] plugins/freedesktop > reading sources... [ 43%] plugins/fromfilename > reading sources... [ 44%] plugins/ftintitle > reading sources... [ 45%] plugins/fuzzy > reading sources... [ 47%] plugins/gmusic > reading sources... [ 48%] plugins/hook > reading sources... [ 49%] plugins/ihate > reading sources... [ 50%] plugins/importadded > reading sources... [ 51%] plugins/importfeeds > reading sources... [ 52%] plugins/index > reading sources... [ 54%] plugins/info > reading sources... [ 55%] plugins/inline > reading sources... [ 56%] plugins/ipfs > reading sources... [ 57%] plugins/keyfinder > reading sources... [ 58%] plugins/kodiupdate > reading sources... [ 59%] plugins/lastgenre > reading sources... [ 60%] plugins/lastimport > reading sources... [ 62%] plugins/loadext > reading sources... [ 63%] plugins/lyrics > reading sources... [ 64%] plugins/mbcollection > reading sources... [ 65%] plugins/mbsubmit > reading sources... [ 66%] plugins/mbsync > reading sources... [ 67%] plugins/metasync > reading sources... [ 68%] plugins/missing > reading sources... [ 70%] plugins/mpdstats > reading sources... [ 71%] plugins/mpdupdate > reading sources... [ 72%] pl
Bug#1027461: marked as done (python-mediafile breaks beets autopkgtest: object of type 'NoneType' has no len())
Your message dated Sun, 01 Jan 2023 19:19:40 +
with message-id
and subject line Bug#1027461: fixed in beets 1.6.0-4
has caused the Debian Bug report #1027461,
regarding python-mediafile breaks beets autopkgtest: object of type 'NoneType'
has no len()
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.)
--
1027461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-mediafile, beets
Control: found -1 python-mediafile/0.11.0-1
Control: found -1 beets/1.6.0-3
Severity: serious
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: breaks needs-update
Dear maintainer(s),
With a recent upload of python-mediafile the autopkgtest of beets fails
in testing when that autopkgtest is run with the binary packages of
python-mediafile from unstable. It passes when run with only packages
from testing. In tabular form:
passfail
python-mediafile from testing0.11.0-1
beets from testing1.6.0-3
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration of python-mediafile
to testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package?
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=python-mediafile
https://ci.debian.net/data/autopkgtest/testing/amd64/b/beets/29792888/log.gz
=== FAILURES
===
EmbedartCliTest.test_clear_art_with_yes_input
_
self = testMethod=test_clear_art_with_yes_input>
def test_clear_art_with_yes_input(self):
self._setup_data()
album = self.add_album_fixture()
item = album.items()[0]
self.io.addinput('y')
self.run_command('embedart', '-f', self.small_artpath)
self.io.addinput('y')
self.run_command('clearart')
mediafile = MediaFile(syspath(item.path))
self.assertEqual(len(mediafile.images), 0)
E TypeError: object of type 'NoneType' has no len()
test/test_embedart.py:205: TypeError
- Captured stderr call
-
Sending event: database_change
Sending event: database_change
Sending event: item_copied
Sending event: database_change
Sending event: database_change
Sending event: database_change
Sending event: database_change
Sending event: database_change
no user configuration found at /tmp/tmppz0v9_v1/config.yaml
data directory: /tmp/tmppz0v9_v1
plugin paths: Sending event: pluginload
embedart: embedding
/tmp/autopkgtest-lxc.36cnu39s/downtmp/autopkgtest_tmp/test/rsrc/image-2x3.jpg
Sending event: write
Sending event: after_write
Sending event: cli_exit
no user configuration found at /tmp/tmppz0v9_v1/config.yaml
data directory: /tmp/tmppz0v9_v1
plugin paths: Sending event: pluginload
embedart: Clearing album art from 1 items
embedart: Clearing art for the artist - älbum - tïtle 0
Sending event: write
Sending event: after_write
Sending event: cli_exit
-- Captured log call
---
DEBUGbeets:plugins.py:485 Sending event: database_change
DEBUGbeets:plugins.py:485 Sending event: database_change
DEBUGbeets:plugins.py:485 Sending event: item_copied
DEBUGbeets:plugins.py:485 Sending event: database_change
DEBUGbeets:plugins.py:485 Sending event: database_change
DEBUGbeets:plugins.py:485 Sending event: database_change
DEBUGbeets:plugins.py:485 Sending event: database_change
DEBUGbeets:plugins.py:485 Sending event: database_change
DEBUGbeets:__init__.py:1202 no user configuration found at
/tmp/tmppz0v9_v1/config.yaml
DEBUGbeets:__init__.py:1205 data directory: /tmp/tmppz0v9_v1
DEBUGbeets:__init__.py: plugin paths: DEBUG
beets:plugins.py:485 Sending event: pluginload
DEBUGbeets.embedart:art.py:69 embedart: embedding
/tmp/autopkgtest-lxc.36cnu39s/downtmp/autopkgtest_tmp/test/rsrc/image-2x3.jpg
DEBUGbeets:plugins.py:485 Sending event: write
DEBUGbeets:plugins.py:485 Sending event: after_write
DEBUGbeets:plugins.py:485 Sending event: cli_exit
DEBUGbeets:__init__.py:1202 no user configuration found at
Bug#1026719: vmg: FTBFS: /usr/bin/ld.bfd: cannot find -latk-1.0: No such file or directory
Hi Samuel, > On Tue, 20 Dec 2022 19:27:23 +0100 Samuel Thibault > wrote: > Control: reassign -1 lazarus > Control: affects -1 + vmg > > Hello, > > Lucas Nussbaum, le mar. 20 déc. 2022 18:31:46 +0100, a ecrit: > > > Linking ./vmg > > > /usr/bin/ld.bfd: cannot find -lgdk-x11-2.0: No such file or directory > > > /usr/bin/ld.bfd: cannot find -lgtk-x11-2.0: No such file or directory ... > > > /usr/bin/ld.bfd: cannot find -latk-1.0: No such file or directory > > Yes, we had discussed it a bit in #967798, it is an issue in Lazarus: > fp-units-gtk2-3.2.0 used to have the libgtk2.0-dev dependency, but > fp-units-gtk2-3.2.2 doesn't any more, but it should, it shouldn't be up > to users of the gtk2 unit to know which C dependency it should take. Sorry, but, as FPC maintaining team member, I don't share this __ should __ statement for the following reasons. * GTK2 is declared as deprecated in Debian since long time ago. * Technically, Lazarus doe snot need libgtk2.0-dev for running, and thus should not pull it. * Technically, FPC does not need any GTK related lib, it only provide binding units. So it should not pull it either. * For building, Lazarus build depends on libgtk2.0-dev, until it will migrate to gtk3. And so shall do all programs that use it. I hope this makes it clear, why neither Lazarus, nor FPC or any of their packages should pull libgtk2.0-dev package. You should handle this bug in VMG, and probably the best way to do it is to build depend on libgtk-2.0-dev until you fix https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967798 -- Cheers, Abou Al Montacir signature.asc Description: This is a digitally signed message part
Bug#984153: marked as done (gle-graphics: ftbfs with GCC-11)
Your message dated Sun, 01 Jan 2023 19:05:23 + with message-id and subject line Bug#984153: fixed in gle-graphics 4.3.3-1 has caused the Debian Bug report #984153, regarding gle-graphics: 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.) -- 984153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gle-graphics Version: 4.2.5-9 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/gle-graphics_4.2.5-9_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. [...] 223 | void g_marker2(int i, double sz, double dval) throw (ParserError); | ^ ../core.h:240:62: error: ISO C++17 does not allow dynamic exception specifications 240 | void g_bitmap(string& fname, double wx, double wy, int type) throw(ParserError); | ^ ../core.h:241:65: error: ISO C++17 does not allow dynamic exception specifications 241 | void g_bitmap_info(string& fname, int xvar, int yvar, int type) throw(ParserError); | ^ ../core.h:252:68: error: ISO C++17 does not allow dynamic exception specifications 252 | void g_arrowline(double x2, double y2, int flag, int can_fillpath) throw(ParserError); |^ ../core.h:276:54: error: ISO C++17 does not allow dynamic exception specifications 276 | void g_arrow(double dx, double dy, int can_fillpath) throw(ParserError); | ^ ../core.h:298:47: error: ISO C++17 does not allow dynamic exception specifications 298 | int g_set_compatibility(const string& compat) throw (ParserError); | ^ ../core.h:299:49: error: ISO C++17 does not allow dynamic exception specifications 299 | int g_parse_compatibility(const string& compat) throw (ParserError); | ^ ../core.h:326:43: error: ISO C++17 does not allow dynamic exception specifications 326 | void g_set_arrow_style(const char* shape) throw (ParserError); | ^ ../core.h:327:39: error: ISO C++17 does not allow dynamic exception specifications 327 | void g_set_arrow_tip(const char* tip) throw (ParserError); | ^ ../core.h:329:59: error: ISO C++17 does not allow dynamic exception specifications 329 | void g_bitmap(GLEBitmap*, double wx, double wy, int type) throw(ParserError); | ^ ../core.h:421:47: error: ISO C++17 does not allow dynamic exception specifications 421 | void g_postscript(char *ss,double w,double h) throw (ParserError); | ^ In file included from gsurface.cpp:48: ../texinterface.h:222:42: error: ISO C++17 does not allow dynamic exception specifications
Processed: python-matplotlib-doc: not installable in Sid
Processing commands for cont...@bugs.debian.org: > reassign #1027601 python-matplotlib-doc Bug #1027601 [src:graph-tool] graph-tool: FTBFS: build-dependency not installable: python-matplotlib-doc Bug reassigned from package 'src:graph-tool' to 'python-matplotlib-doc'. No longer marked as found in versions graph-tool/2.45+ds-8. Ignoring request to alter fixed versions of bug #1027601 to the same values previously set > retitle #1027601 python-matplotlib-doc: not installable in Sid Bug #1027601 [python-matplotlib-doc] graph-tool: FTBFS: build-dependency not installable: python-matplotlib-doc Changed Bug title to 'python-matplotlib-doc: not installable in Sid' from 'graph-tool: FTBFS: build-dependency not installable: python-matplotlib-doc'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1023251: marked as done (pdf-redact-tools: Unusable since imagemagick disabled PDF support by default, unmaintained upstream)
Your message dated Sun, 01 Jan 2023 19:03:39 + with message-id and subject line Bug#1027464: Removed package(s) from unstable has caused the Debian Bug report #1023251, regarding pdf-redact-tools: Unusable since imagemagick disabled PDF support by default, unmaintained upstream 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.) -- 1023251: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023251 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pdf-redact-tools Version: 0.1.2-4 Severity: serious Hi, At least on Bullseye and sid, any pdf-redact-tools operation fails with an error like: convert-im6.q16: attempt to perform an operation not allowed by the security policy `PDF' @ error/constitute.c/IsCoderAuthorized/421. Touss, a fellow Tails contributor, reports this is caused by PDF support having been disabled in imagemagick: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964090 This change is effective on Buster and newer and a security team member indicated they'd rather not revert it. A workaround, to be able to use pdf-redact-tools, is to edit /etc/ImageMagick-6/policy.xml and comment out that line: … which re-introduces the attack surface that the security team wants to disable. Additionally, since May 2020 this project is not maintained upstream anymore: https://github.com/firstlookmedia/pdf-redact-tools/commit/e407942fa19027718b706033d460a1dec2097094 So I think this package should not be included in Bookworm, hence the RC severity. Cheers! -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (990, 'unstable'), (2, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-2-amd64 (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_USER Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pdf-redact-tools depends on: ii file 1:5.41-4 ii imagemagick 8:6.9.11.60+dfsg-1.3+b4 ii imagemagick-6.q16 [imagemagick] 8:6.9.11.60+dfsg-1.3+b4 ii libimage-exiftool-perl 12.49+dfsg-1 ii python3 3.10.6-1 pdf-redact-tools recommends no packages. pdf-redact-tools suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Version: 0.1.2-4+rm Dear submitter, as the package pdf-redact-tools has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1027464 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#1027678: marked as done (hunspell: blocking bug to avoid migration of 1.7.2+really1.7.1-2)
Your message dated Sun, 1 Jan 2023 20:01:19 +0100 with message-id <00ceb1f3-d622-655b-5850-50b877ee8...@debian.org> and subject line has caused the Debian Bug report #1027678, regarding hunspell: blocking bug to avoid migration of 1.7.2+really1.7.1-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: hunspell Version: 1.7.2+really1.7.1-2 Severity: serious 1.7.2+really1.7.1-2 is - as the name says - a reupload of 1.7.1 because 1.7.2 broke autopkgtests and this needs to be investigated. Since there is no change here and there probably (in case it happened we can lift the block) is no change needed anyway I think this should be blocked to have the "more sanely" versioned 1.7.1-1 in testing and bookworm instead of 1.7.2+really1.7.1-2. Regards, Rene --- End Message --- --- Begin Message --- Version: 1.7.2+really1.7.2-3--- End Message ---
Processed: retitle 1027474 to qbs: FTBFS: symbol errors
Processing commands for cont...@bugs.debian.org: > retitle 1027474 qbs: FTBFS: symbol errors Bug #1027474 [src:qbs] qbs: FTBFS: symol errors Bug #1027651 [src:qbs] qbs: FTBFS: 3: collect2: error: ld returned 1 exit status Changed Bug title to 'qbs: FTBFS: symbol errors' from 'qbs: FTBFS: symol errors'. Changed Bug title to 'qbs: FTBFS: symbol errors' from 'qbs: FTBFS: 3: collect2: error: ld returned 1 exit status'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027474 1027651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027678: hunspell: blocking bug to avoid migration of 1.7.2+really1.7.1-2
Source: hunspell Version: 1.7.2+really1.7.1-2 Severity: serious 1.7.2+really1.7.1-2 is - as the name says - a reupload of 1.7.1 because 1.7.2 broke autopkgtests and this needs to be investigated. Since there is no change here and there probably (in case it happened we can lift the block) is no change needed anyway I think this should be blocked to have the "more sanely" versioned 1.7.1-1 in testing and bookworm instead of 1.7.2+really1.7.1-2. Regards, Rene
Processed: Bug#1027461 marked as pending in beets
Processing control commands: > tag -1 pending Bug #1027461 [src:python-mediafile, src:beets] python-mediafile breaks beets autopkgtest: object of type 'NoneType' has no len() Added tag(s) pending. -- 1027461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027461 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027461: marked as pending in beets
Control: tag -1 pending Hello, Bug #1027461 in beets reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/beets/-/commit/3061f007222b4f780b740ee212c65a855926be37 Patch: Support mediafile 0.11. (Closes: #1027461, 1027519) (this message was generated automatically) -- Greetings https://bugs.debian.org/1027461
Bug#1027573: marked as done (kdump-tools: FTBFS: make[1]: *** [debian/rules:64: override_dh_auto_test] Error 1)
Your message dated Sun, 01 Jan 2023 18:20:20 + with message-id and subject line Bug#1027573: fixed in kdump-tools 1:1.8.1 has caused the Debian Bug report #1027573, regarding kdump-tools: FTBFS: make[1]: *** [debian/rules:64: override_dh_auto_test] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1027573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027573 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kdump-tools Version: 1:1.8 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 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 '/<>' > shellcheck -e SC1090,SC1091,SC3043 debian/kdump-config.in > debian/kernel-postrm-delete-initrd debian/kdump-tools.postinst > debian/kdump-tools.preinst debian/kdump-tools.postrm > debian/kdump-tools.config debian/kernel-postinst-generate-initrd > debian/initramfs.local-bottom debian/kdump-tools.init debian/initramfs.hook > > In debian/kdump-config.in line 62: > [ -d $KDUMP_COREDIR ] || mkdir -p $KDUMP_COREDIR ; > ^^ SC2086 (info): Double quote to prevent globbing and word > splitting. > ^^ SC2086 (info): Double quote > to prevent globbing and word splitting. > > Did you mean: > [ -d "$KDUMP_COREDIR" ] || mkdir -p "$KDUMP_COREDIR" ; > > > In debian/kdump-config.in line 178: > if [ -e $kexec_cmd_file ] ; then > ^-^ SC2086 (info): Double quote to prevent > globbing and word splitting. > > Did you mean: > if [ -e "$kexec_cmd_file" ] ; then > > > In debian/kdump-config.in line 179: > cat $kexec_cmd_file ; > ^-^ SC2086 (info): Double quote to prevent > globbing and word splitting. > > Did you mean: > cat "$kexec_cmd_file" ; > > > In debian/kdump-config.in line 266: > create_symlink $symlink "$KVER" >^--^ SC2086 > (info): Double quote to prevent globbing and word splitting. > > Did you mean: > create_symlink "$symlink" "$KVER" > > > In debian/kdump-config.in line 457: > logger -t $NAME "fadump registering failed" > ^---^ SC2086 (info): Double quote to prevent > globbing and word splitting. > > Did you mean: > logger -t "$NAME" "fadump registering failed" > > > In debian/kdump-config.in line 462: > logger -t $NAME "fadump registered successfully" > ^---^ SC2086 (info): Double quote to prevent globbing and > word splitting. > > Did you mean: > logger -t "$NAME" "fadump registered successfully" > > > In debian/kdump-config.in line 478: > logger -t $NAME "fadump un-registering failed" > ^---^ SC2086 (info): Double quote to prevent > globbing and word splitting. > > Did you mean: > logger -t "$NAME" "fadump un-registering failed" > > > In debian/kdump-config.in line 483: > logger -t $NAME "fadump un-registered successfully" > ^---^ SC2086 (info): Double quote to prevent globbing and > word splitting. > > Did you mean: > logger -t "$NAME" "fadump un-registered successfully" > > > In debian/kdump-config.in line 594: > logger -t $NAME "unloaded kdump kernel" > ^---^ SC2086 (info): Double quote to prevent > globbing and word splitting. > > Did you mean: > logger -t "$NAME" "unloaded kdump kernel" > > > In debian/kdump-config.in line 597: > logger -t $NAME "failed to unload kdump kernel" > ^---^ SC2086 (info): Double quote to prevent > globbing and word splitting. > > Did you mean: > logger -t "$NAME" "failed to unload kdu
Processed: fixed 1027509 in 2.1-3
Processing commands for cont...@bugs.debian.org: > fixed 1027509 2.1-3 Bug #1027509 [src:commons-vfs] commons-vfs: FTBFS: build-dependency not installable: libcommons-net-java-doc Marked as fixed in versions commons-vfs/2.1-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 1027509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027632: libwww-curl-perl: FTBFS: curlopt-constants.c:19:51: error: ‘CURL_DEPRECATED’ undeclared (first use in this function)
Control: tag -1 + confirmed On Sun, 01 Jan 2023 15:31:06 +0100, Lucas Nussbaum wrote: > Source: libwww-curl-perl > Version: 4.17-8 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20230101 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > > In file included from Curl.xs:578: > > curlopt-constants.c: In function ‘constant’: > > curlopt-constants.c:19:51: error: ‘CURL_DEPRECATED’ undeclared (first use > > in this function) > >19 | if (strEQ(name, "DEPRECATED")) return CURL_DEPRECATED; > > | ^~~ I think this is related to the following change in curl 7.87.0: https://github.com/curl/curl/pull/9667 https://github.com/curl/curl/commit/6967571bf20624bc4cfa68fb8f90cbc53a87c6f2 If I remove the new *DEPRECAT* macros from the generated curlopt-constants.c after `perl Makefile.PL' and before `make', we get a bit further until we hit this error: In file included from /usr/include/x86_64-linux-gnu/curl/curl.h:3195: Curl.xs:692:25: error: void value not ignored as it ought to be 692 | curl_easy_setopt(clone->curl, 1 + i, clone->strings[i]); Looks like this needs someone who actually speaks C and XS :) Cheers, gregor -- .''`. https://info.comodo.priv.at -- Debian Developer https://www.debian.org : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 AA06 `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe `- signature.asc Description: Digital Signature
Processed: Re: Bug#1027632: libwww-curl-perl: FTBFS: curlopt-constants.c:19:51: error: ‘CURL_DEPRECATED’ undeclared (first use in this function)
Processing control commands: > tag -1 + confirmed Bug #1027632 [src:libwww-curl-perl] libwww-curl-perl: FTBFS: curlopt-constants.c:19:51: error: ‘CURL_DEPRECATED’ undeclared (first use in this function) Added tag(s) confirmed. -- 1027632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: merging 984229 1027622
Processing commands for cont...@bugs.debian.org: > merge 984229 1027622 Bug #984229 [src:mccs] mccs: ftbfs with GCC-11 Bug #1027622 [src:mccs] mccs: FTBFS: stl_tree.h:770:15: error: static assertion failed: comparison object must be invocable as const Merged 984229 1027622 > thanks Stopping processing here. Please contact me if you need assistance. -- 1027622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027622 984229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Processing commands for cont...@bugs.debian.org:
> severity 1027489 normal
Bug #1027489 {Done: Sebastiaan Couwenberg }
[src:gr-fosphor] gr-fosphor: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Ignoring request to change severity of Bug 1027489 to the same value.
> severity 1027500 normal
Bug #1027500 {Done: Sebastiaan Couwenberg }
[src:gr-osmosdr] gr-osmosdr: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Ignoring request to change severity of Bug 1027500 to the same value.
> severity 1027514 normal
Bug #1027514 {Done: Sebastiaan Couwenberg }
[src:pyimagetool] pyimagetool: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Ignoring request to change severity of Bug 1027514 to the same value.
> severity 1027516 normal
Bug #1027516 {Done: Sebastiaan Couwenberg }
[src:python-pyqtgraph] python-pyqtgraph: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Ignoring request to change severity of Bug 1027516 to the same value.
> severity 1027520 normal
Bug #1027520 {Done: Sebastiaan Couwenberg } [src:gr-gsm]
gr-gsm: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1)
(versioned dep on a virtual pkg?)
Ignoring request to change severity of Bug 1027520 to the same value.
> severity 1027530 normal
Bug #1027530 {Done: Sebastiaan Couwenberg }
[src:python-qtpy] python-qtpy: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Ignoring request to change severity of Bug 1027530 to the same value.
> severity 1027531 normal
Bug #1027531 {Done: Sebastiaan Couwenberg } [src:gr-rds]
gr-rds: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1)
(versioned dep on a virtual pkg?)
Ignoring request to change severity of Bug 1027531 to the same value.
> severity 1027539 normal
Bug #1027539 [src:gqrx-sdr] gqrx-sdr: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> severity 1027541 normal
Bug #1027541 {Done: Sebastiaan Couwenberg }
[src:sphinx-qt-documentation] sphinx-qt-documentation: FTBFS: unsatisfiable
build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> severity 1027553 normal
Bug #1027553 {Done: Sebastiaan Couwenberg } [src:eric]
eric: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned
dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> severity 1027555 normal
Bug #1027555 [src:geophar] geophar: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> severity 1027559 normal
Bug #1027559 [src:gr-iqbal] gr-iqbal: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> severity 1027570 normal
Bug #1027570 {Done: Sebastiaan Couwenberg } [src:gr-radar]
gr-radar: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1)
(versioned dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> severity 1027578 normal
Bug #1027578 {Done: Sebastiaan Couwenberg } [src:dioptas]
dioptas: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1)
(versioned dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> severity 1027595 normal
Bug #1027595 {Done: Sebastiaan Couwenberg }
[src:gr-satellites] gr-satellites: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Ignoring request to change severity of Bug 1027595 to the same value.
> severity 1027597 normal
Bug #1027597 {Done: Sebastiaan Couwenberg }
[src:gr-air-modes] gr-air-modes: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Ignoring request to change severity of Bug 1027597 to the same value.
> severity 1027599 normal
Bug #1027599 {Done: Sebastiaan Couwenberg } [src:autokey]
autokey: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1)
(versioned dep on a virtual pkg?)
Ignoring request to change severity of Bug 1027599 to the same value.
> severity 1027616 normal
Bug #1027616 {Done: Sebastiaan Couwenberg }
[src:oggvideotools] oggvideotools: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Ignoring request to change severity of Bug 1027616 to the same value.
> severity 1027626 normal
Bug #1027626 {Done: Sebastiaan Couwenberg } [src:retext]
retext: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1)
(versioned dep on a virtual pkg?)
Ignoring request to change severity of Bug 1027626 to the same value.
> severity 1027641 normal
Bug #1027641 {Done: Sebastiaan Couwenberg }
[src:python-pymeasure] python-pymeasure: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep
Bug#1027504: marked as done (okular-dev: missing qtbase5-private-dev dependency for Qt5::CorePrivate target in cmake config files)
Your message dated Sun, 01 Jan 2023 17:21:14 +
with message-id
and subject line Bug#1027504: fixed in okular 4:22.12.0-2
has caused the Debian Bug report #1027504,
regarding okular-dev: missing qtbase5-private-dev dependency for
Qt5::CorePrivate target in cmake config files
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.)
--
1027504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: calligra
Version: 1:3.2.1+dfsg-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230101 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> /usr/bin/c++ -DICONV_SECOND_ARGUMENT_IS_CONST -D_GNU_SOURCE
> -D_LARGEFILE64_SOURCE -g -O2 -ffile-prefix-map=/<>=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wno-deprecated
> -Wno-deprecated-declarations -Wdate-time -D_FORTIFY_SOURCE=2
> -fno-operator-names -Wall -Wextra -Wcast-align -Wchar-subscripts
> -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor
> -Woverloaded-virtual -Werror=return-type -Werror=init-self -Wvla -Wdate-time
> -Wsuggest-override -Wlogical-op -fexceptions -std=c++17 -o
> CMakeFiles/cmTC_2b120.dir/src.cxx.o -c
> /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-MwSqRe/src.cxx
> /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-MwSqRe/src.cxx:
> In function ‘int main()’:
> /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-MwSqRe/src.cxx:9:17:
> error: invalid conversion from ‘const char**’ to ‘char**’ [-fpermissive]
> 9 | iconv(conv, , , , );
> | ^~~
> | |
> | const char**
> In file included from
> /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-MwSqRe/src.cxx:2:
> /usr/include/iconv.h:49:54: note: initializing argument 2 of ‘size_t
> iconv(iconv_t, char**, size_t*, char**, size_t*)’
>49 | extern size_t iconv (iconv_t __cd, char **__restrict __inbuf,
> |~~^~~
> gmake[3]: *** [CMakeFiles/cmTC_2b120.dir/build.make:78:
> CMakeFiles/cmTC_2b120.dir/src.cxx.o] Error 1
> gmake[3]: Leaving directory
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-MwSqRe'
> gmake[2]: *** [Makefile:127: cmTC_2b120/fast] Error 2
> gmake[2]: Leaving directory
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-MwSqRe'
>
>
> Source file was:
>
> #include
> int main(){
> iconv_t conv = 0;
> const char* in = 0;
> size_t ilen = 0;
> char* out = 0;
> size_t olen = 0;
> iconv(conv, , , , );
> return 0;
> }
>
>
> Determining if the include file sys/iconv.h exists failed with the following
> output:
> Change Dir:
> /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-QXKclh
>
> Run Build Command(s):/usr/bin/gmake -f Makefile cmTC_c251f/fast && gmake[2]:
> Entering directory
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-QXKclh'
> /usr/bin/gmake -f CMakeFiles/cmTC_c251f.dir/build.make
> CMakeFiles/cmTC_c251f.dir/build
> gmake[3]: Entering directory
> '/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-QXKclh'
> Building C object CMakeFiles/cmTC_c251f.dir/CheckIncludeFile.c.o
> /usr/bin/cc -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -g -O2
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fno-common -Wall
> -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long
> -Wpointer-arith -Wundef -Wmissing-format-attribute -Wwrite-strings
> -Werror=implicit-function-declaration -std=gnu90 -o
> CMakeFiles/cmTC_c251f.dir/CheckIncludeFile.c.o -c
> /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-QXKclh/CheckIncludeFile.c
> /<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeScratch/TryCompile-QXKclh/CheckIncludeFile.c:1:10:
> fatal error: sys/iconv.h: No such file or directory
> 1 | #include
> | ^
> compilation terminated.
> gmake[3]: *** [CMakeFiles/cmTC_c251f.dir/build.make:78:
> CMakeFiles/cmTC_c251f.dir/CheckIncludeFile.c.o]
Bug#1027570: marked as done (gr-radar: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?))
Your message dated Sun, 1 Jan 2023 18:18:58 +0100 with message-id <6b59ccec-99a2-adf5-370f-ee3f1b89f...@xs4all.nl> and subject line FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) has caused the Debian Bug report #1027570, regarding gr-radar: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) 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.) -- 1027570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027570 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gr-radar Version: 0.0.0.20220920-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: cmake, debhelper-compat (= 13), dh-python, > doxygen-latex, gir1.2-gtk-3.0, gnuradio-dev (>= 3.9), gobject-introspection, > libboost-system-dev, liborc-0.4-dev, libspdlog-dev, libqwt-qt5-dev, > libuhd-dev, pkg-config, python3-dev, python3-gi, python3-matplotlib, > python3-numpy, python3-tk, qtbase5-dev, qtchooser, build-essential, fakeroot, > doxygen > Filtered Build-Depends: cmake, debhelper-compat (= 13), dh-python, > doxygen-latex, gir1.2-gtk-3.0, gnuradio-dev (>= 3.9), gobject-introspection, > libboost-system-dev, liborc-0.4-dev, libspdlog-dev, libqwt-qt5-dev, > libuhd-dev, pkg-config, python3-dev, python3-gi, python3-matplotlib, > python3-numpy, python3-tk, qtbase5-dev, qtchooser, build-essential, fakeroot, > doxygen > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [529 B] > Get:5 copy:/<>/apt_archive ./ Packages [606 B] > Fetched 2092 B in 0s (164 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > python3-pyqt6 : Depends: qt6-base-abi (= 6.3.1) > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/01/01/gr-radar_0.0.0.20220920-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230101=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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 --- severity 1027539 normal severity 1027541 normal severity 1027553 normal severity 1027555 normal severity 1027559 normal severity 1027570 normal severity 1027578 normal thanks This issue is caused by pyqt6 not being rebuilt as part of the ongoing qt6baseabi-6.4.2 transition.--- End Message ---
Bug#1027553: marked as done (eric: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?))
Your message dated Sun, 1 Jan 2023 18:18:58 +0100 with message-id <6b59ccec-99a2-adf5-370f-ee3f1b89f...@xs4all.nl> and subject line FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) has caused the Debian Bug report #1027553, regarding eric: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) 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.) -- 1027553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027553 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: eric Version: 21.1+ds1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), dh-sequence-python3, > build-essential, fakeroot, pyqt5-dev, python3-all, python3-pyqt5, > python3-pyqt5.qsci, python3-sip-dev, qttools5-dev-tools > Filtered Build-Depends: debhelper-compat (= 13), dh-sequence-python3, > build-essential, fakeroot, pyqt5-dev, python3-all, python3-pyqt5, > python3-pyqt5.qsci, python3-sip-dev, qttools5-dev-tools > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [428 B] > Get:5 copy:/<>/apt_archive ./ Packages [502 B] > Fetched 1887 B in 0s (72.2 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > python3-pyqt6 : Depends: qt6-base-abi (= 6.3.1) > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/01/01/eric_21.1+ds1-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230101=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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 --- severity 1027539 normal severity 1027541 normal severity 1027553 normal severity 1027555 normal severity 1027559 normal severity 1027570 normal severity 1027578 normal thanks This issue is caused by pyqt6 not being rebuilt as part of the ongoing qt6baseabi-6.4.2 transition.--- End Message ---
Bug#1027541: marked as done (sphinx-qt-documentation: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?))
Your message dated Sun, 1 Jan 2023 18:18:58 +0100 with message-id <6b59ccec-99a2-adf5-370f-ee3f1b89f...@xs4all.nl> and subject line FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) has caused the Debian Bug report #1027541, regarding sphinx-qt-documentation: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) 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.) -- 1027541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sphinx-qt-documentation Version: 0.4.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), dh-python, pyqt5-dev-tools, > pyqt6-dev-tools, python3-all, python3-sphinx, python3-setuptools, > build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), dh-python, pyqt5-dev-tools, > pyqt6-dev-tools, python3-all, python3-sphinx, python3-setuptools, > build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [409 B] > Get:5 copy:/<>/apt_archive ./ Packages [493 B] > Fetched 1859 B in 0s (95.7 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > python3-pyqt6 : Depends: qt6-base-abi (= 6.3.1) > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/01/01/sphinx-qt-documentation_0.4.1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230101=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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 --- severity 1027539 normal severity 1027541 normal severity 1027553 normal severity 1027555 normal severity 1027559 normal severity 1027570 normal severity 1027578 normal thanks This issue is caused by pyqt6 not being rebuilt as part of the ongoing qt6baseabi-6.4.2 transition.--- End Message ---
Processed: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Processing commands for cont...@bugs.debian.org: > severity 1027644 normal Bug #1027644 [src:gr-limesdr] gr-limesdr: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) Severity set to 'normal' from 'serious' > severity 1027655 normal Bug #1027655 [src:gr-hpsdr] gr-hpsdr: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) Severity set to 'normal' from 'serious' > severity 1027665 normal Bug #1027665 [src:gr-funcube] gr-funcube: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1027644: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027644 1027655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027655 1027665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027665 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Processing commands for cont...@bugs.debian.org:
> severity 1027595 normal
Bug #1027595 {Done: Sebastiaan Couwenberg }
[src:gr-satellites] gr-satellites: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> severity 1027597 normal
Bug #1027597 [src:gr-air-modes] gr-air-modes: FTBFS: unsatisfiable
build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> severity 1027599 normal
Bug #1027599 {Done: Sebastiaan Couwenberg } [src:autokey]
autokey: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1)
(versioned dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> severity 1027616 normal
Bug #1027616 {Done: Sebastiaan Couwenberg }
[src:oggvideotools] oggvideotools: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> severity 1027626 normal
Bug #1027626 [src:retext] retext: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> severity 1027641 normal
Bug #1027641 {Done: Sebastiaan Couwenberg }
[src:python-pymeasure] python-pymeasure: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> severity 1027642 normal
Bug #1027642 [src:gnss-sdr] gnss-sdr: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1027595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027595
1027597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027597
1027599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027599
1027616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027616
1027626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027626
1027641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027641
1027642: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027642
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Processing commands for cont...@bugs.debian.org:
> severity 1027489 normal
Bug #1027489 {Done: Sebastiaan Couwenberg }
[src:gr-fosphor] gr-fosphor: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> severity 1027500 normal
Bug #1027500 [src:gr-osmosdr] gr-osmosdr: FTBFS: unsatisfiable
build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> severity 1027514 normal
Bug #1027514 [src:pyimagetool] pyimagetool: FTBFS: unsatisfiable
build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> severity 1027516 normal
Bug #1027516 {Done: Sebastiaan Couwenberg }
[src:python-pyqtgraph] python-pyqtgraph: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> severity 1027520 normal
Bug #1027520 [src:gr-gsm] gr-gsm: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> severity 1027530 normal
Bug #1027530 [src:python-qtpy] python-qtpy: FTBFS: unsatisfiable
build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> severity 1027531 normal
Bug #1027531 [src:gr-rds] gr-rds: FTBFS: unsatisfiable build-dependency:
qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1027489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027489
1027500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027500
1027514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027514
1027516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027516
1027520: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027520
1027530: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027530
1027531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1027641: marked as done (python-pymeasure: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?))
Your message dated Sun, 1 Jan 2023 18:04:50 +0100 with message-id and subject line FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) has caused the Debian Bug report #1027641, regarding python-pymeasure: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) 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.) -- 1027641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027641 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pymeasure Version: 0.9.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), dh-python, python3-all, > python3-numpy, python3-pandas, python3-pyqtgraph (>= 0.13.1), python3-pytest, > python3-pyvisa, python3-serial (>= 2.7), python3-setuptools, python3-sphinx, > python3-sphinx-rtd-theme, sphinx-common, build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), dh-python, python3-all, > python3-numpy, python3-pandas, python3-pyqtgraph (>= 0.13.1), python3-pytest, > python3-pyvisa, python3-serial (>= 2.7), python3-setuptools, python3-sphinx, > python3-sphinx-rtd-theme, sphinx-common, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [476 B] > Get:5 copy:/<>/apt_archive ./ Packages [541 B] > Fetched 1974 B in 0s (166 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > python3-pyqt6 : Depends: qt6-base-abi (= 6.3.1) > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/01/01/python-pymeasure_0.9.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230101=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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 --- severity 1027489 normal severity 1027500 normal severity 1027514 normal severity 1027516 normal severity 1027520 normal severity 1027530 normal severity 1027531 normal severity 1027539 normal severity 1027541 normal severity 1027553 normal severity 1027555 normal severity 1027559 normal severity 1027570 normal severity 1027578 normal severity 1027595 normal severity 1027597 normal severity 1027599 normal severity 1027616 normal severity 1027626 normal severity 1027641 normal severity 1027642 normal severity 1027644 normal severity 1027655 normal severity 1027665 normal thanks This issue is caused by pyqt6 not being rebuilt as part of the ongoing qt6baseabi-6.4.2 transition.--- End Message ---
Bug#1027616: marked as done (oggvideotools: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?))
Your message dated Sun, 1 Jan 2023 18:04:50 +0100 with message-id and subject line FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) has caused the Debian Bug report #1027616, regarding oggvideotools: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) 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.) -- 1027616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027616 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: oggvideotools Version: 0.9.1-6 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), cmake, libogg-dev, > libtheora-dev, libvorbis-dev, libsdl-dev, libgd-dev, libboost-dev, debconf, > python3-mecavideo, build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), cmake, libogg-dev, > libtheora-dev, libvorbis-dev, libsdl-dev, libgd-dev, libboost-dev, debconf, > python3-mecavideo, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [422 B] > Get:5 copy:/<>/apt_archive ./ Packages [508 B] > Fetched 1887 B in 0s (66.1 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > python3-pyqt6 : Depends: qt6-base-abi (= 6.3.1) > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/01/01/oggvideotools_0.9.1-6_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230101=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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 --- severity 1027489 normal severity 1027500 normal severity 1027514 normal severity 1027516 normal severity 1027520 normal severity 1027530 normal severity 1027531 normal severity 1027539 normal severity 1027541 normal severity 1027553 normal severity 1027555 normal severity 1027559 normal severity 1027570 normal severity 1027578 normal severity 1027595 normal severity 1027597 normal severity 1027599 normal severity 1027616 normal severity 1027626 normal severity 1027641 normal severity 1027642 normal severity 1027644 normal severity 1027655 normal severity 1027665 normal thanks This issue is caused by pyqt6 not being rebuilt as part of the ongoing qt6baseabi-6.4.2 transition.--- End Message ---
Bug#1027599: marked as done (autokey: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?))
Your message dated Sun, 1 Jan 2023 18:04:50 +0100 with message-id and subject line FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) has caused the Debian Bug report #1027599, regarding autokey: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) 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.) -- 1027599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: autokey Version: 0.95.10-2.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), dh-python, gir1.2-gtk-3.0, > pyqt5-dev-tools, python3, python3-dbus, python3-gi, python3-pyqt5.qsci, > python3-pyqt5.qtsvg, python3-setuptools, python3-xlib, build-essential, > fakeroot > Filtered Build-Depends: debhelper-compat (= 13), dh-python, gir1.2-gtk-3.0, > pyqt5-dev-tools, python3, python3-dbus, python3-gi, python3-pyqt5.qsci, > python3-pyqt5.qtsvg, python3-setuptools, python3-xlib, build-essential, > fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [438 B] > Get:5 copy:/<>/apt_archive ./ Packages [519 B] > Fetched 1914 B in 0s (158 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > python3-pyqt6 : Depends: qt6-base-abi (= 6.3.1) > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/01/01/autokey_0.95.10-2.1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230101=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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 --- severity 1027489 normal severity 1027500 normal severity 1027514 normal severity 1027516 normal severity 1027520 normal severity 1027530 normal severity 1027531 normal severity 1027539 normal severity 1027541 normal severity 1027553 normal severity 1027555 normal severity 1027559 normal severity 1027570 normal severity 1027578 normal severity 1027595 normal severity 1027597 normal severity 1027599 normal severity 1027616 normal severity 1027626 normal severity 1027641 normal severity 1027642 normal severity 1027644 normal severity 1027655 normal severity 1027665 normal thanks This issue is caused by pyqt6 not being rebuilt as part of the ongoing qt6baseabi-6.4.2 transition.--- End Message ---
Bug#1027595: marked as done (gr-satellites: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?))
Your message dated Sun, 1 Jan 2023 18:04:50 +0100 with message-id and subject line FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) has caused the Debian Bug report #1027595, regarding gr-satellites: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) 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.) -- 1027595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gr-satellites Version: 4.4.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: cmake, debhelper-compat (= 13), dh-python, doxygen, > gnuradio-dev, pkg-config, python3, python3-construct, python3-mako, > python3-numpy, python3-requests, python3-six, swig, build-essential, fakeroot > Filtered Build-Depends: cmake, debhelper-compat (= 13), dh-python, doxygen, > gnuradio-dev, pkg-config, python3, python3-construct, python3-mako, > python3-numpy, python3-requests, python3-six, swig, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [440 B] > Get:5 copy:/<>/apt_archive ./ Packages [523 B] > Fetched 1920 B in 0s (152 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > python3-pyqt6 : Depends: qt6-base-abi (= 6.3.1) > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/01/01/gr-satellites_4.4.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230101=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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 --- severity 1027489 normal severity 1027500 normal severity 1027514 normal severity 1027516 normal severity 1027520 normal severity 1027530 normal severity 1027531 normal severity 1027539 normal severity 1027541 normal severity 1027553 normal severity 1027555 normal severity 1027559 normal severity 1027570 normal severity 1027578 normal severity 1027595 normal severity 1027597 normal severity 1027599 normal severity 1027616 normal severity 1027626 normal severity 1027641 normal severity 1027642 normal severity 1027644 normal severity 1027655 normal severity 1027665 normal thanks This issue is caused by pyqt6 not being rebuilt as part of the ongoing qt6baseabi-6.4.2 transition.--- End Message ---
Bug#1027489: marked as done (gr-fosphor: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?))
Your message dated Sun, 1 Jan 2023 18:04:50 +0100 with message-id and subject line FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) has caused the Debian Bug report #1027489, regarding gr-fosphor: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) 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.) -- 1027489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gr-fosphor Version: 3.9~0.974ab2f-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: cmake, debhelper (>= 13), dh-python, doxygen, > gnuradio-dev (>= 3.9), graphviz, libboost-regex-dev, libboost-system-dev, > libboost-thread-dev, libfreetype6-dev, libgl1-mesa-dev, libglfw3-dev, > libgmp-dev, liblog4cpp5-dev, libqt5opengl5-dev, ocl-icd-opencl-dev | > amd-opencl-dev | nvidia-opencl-dev, opencl-headers, pkg-config, python3-dev, > python3-numpy, python3-six, qt5-qmake, qtbase5-dev, qttools5-dev, > build-essential, fakeroot > Filtered Build-Depends: cmake, debhelper (>= 13), dh-python, doxygen, > gnuradio-dev (>= 3.9), graphviz, libboost-regex-dev, libboost-system-dev, > libboost-thread-dev, libfreetype6-dev, libgl1-mesa-dev, libglfw3-dev, > libgmp-dev, liblog4cpp5-dev, libqt5opengl5-dev, ocl-icd-opencl-dev, > opencl-headers, pkg-config, python3-dev, python3-numpy, python3-six, > qt5-qmake, qtbase5-dev, qttools5-dev, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [542 B] > Get:5 copy:/<>/apt_archive ./ Packages [609 B] > Fetched 2108 B in 0s (152 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > python3-pyqt6 : Depends: qt6-base-abi (= 6.3.1) > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/01/01/gr-fosphor_3.9~0.974ab2f-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230101=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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 --- severity 1027489 normal severity 1027500 normal severity 1027514 normal severity 1027516 normal severity 1027520 normal severity 1027530 normal severity 1027531 normal severity 1027539 normal severity 1027541 normal severity 1027553 normal severity 1027555 normal severity 1027559 normal severity 1027570 normal severity 1027578 normal severity 1
Bug#1027578: marked as done (dioptas: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?))
Your message dated Sun, 1 Jan 2023 18:04:50 +0100 with message-id and subject line FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) has caused the Debian Bug report #1027578, regarding dioptas: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) 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.) -- 1027578: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027578 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dioptas Version: 0.5.2-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: dh-python, python3-setuptools, python3-all-dev, > debhelper (>= 13), python3-numpy, cython3, python3-qtpy, python3-pyqtgraph, > python3-pyfai, python3-scipy, python3-future, python3-fabio, python3-skimage, > python3-pycifrw, python3-sphinx, dbus, python3-lmfit, python3-pyepics, > python3-h5py, python3-extra-data, build-essential, fakeroot > Filtered Build-Depends: dh-python, python3-setuptools, python3-all-dev, > debhelper (>= 13), python3-numpy, cython3, python3-qtpy, python3-pyqtgraph, > python3-pyfai, python3-scipy, python3-future, python3-fabio, python3-skimage, > python3-pycifrw, python3-sphinx, dbus, python3-lmfit, python3-pyepics, > python3-h5py, python3-extra-data, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [473 B] > Get:5 copy:/<>/apt_archive ./ Packages [560 B] > Fetched 1990 B in 0s (84.4 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > python3-pyqt6 : Depends: qt6-base-abi (= 6.3.1) > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/01/01/dioptas_0.5.2-4_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230101=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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 --- severity 1027489 normal severity 1027500 normal severity 1027514 normal severity 1027516 normal severity 1027520 normal severity 1027530 normal severity 1027531 normal severity 1027539 normal severity 1027541 normal severity 1027553 normal severity 1027555 normal severity 1027559 normal severity 1027570 normal severity 1027578 normal severity 1027595 normal severity 1027597 normal severity 1027599 normal severity 1027616 normal severity 1027626 normal severity 1027641 normal severity 1027642 normal severity 1027644 normal severity 1027655 normal severity 1027665 normal thanks This issue is caused by pyqt6 not being rebuilt as part of the ongoing qt6baseabi-6.4.2 transition.--- End Message ---
Bug#1027516: marked as done (python-pyqtgraph: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?))
Your message dated Sun, 1 Jan 2023 18:04:50 +0100 with message-id and subject line FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) has caused the Debian Bug report #1027516, regarding python-pyqtgraph: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) 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.) -- 1027516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027516 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-pyqtgraph Version: 0.13.1-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230101 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), dh-python, libpyside2-py3, > python3-all, python3-numpy, python3-opengl, python3-pyqt5.qtopengl, > python3-setuptools, python3-sphinx, python3-sphinx-qt-documentation, > python3-sphinx-rtd-theme, pyqt5-dev-tools, pyqt6-dev-tools, > qtbase5-dev-tools, qt6-base-dev-tools, build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), dh-python, libpyside2-py3, > python3-all, python3-numpy, python3-opengl, python3-pyqt5.qtopengl, > python3-setuptools, python3-sphinx, python3-sphinx-qt-documentation, > python3-sphinx-rtd-theme, pyqt5-dev-tools, pyqt6-dev-tools, > qtbase5-dev-tools, qt6-base-dev-tools, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [473 B] > Get:5 copy:/<>/apt_archive ./ Packages [557 B] > Fetched 1987 B in 0s (117 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > python3-pyqt6 : Depends: qt6-base-abi (= 6.3.1) > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2023/01/01/python-pyqtgraph_0.13.1-3_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230101;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230101=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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 --- severity 1027489 normal severity 1027500 normal severity 1027514 normal severity 1027516 normal severity 1027520 normal severity 1027530 normal severity 1027531 normal severity 1027539 normal severity 1027541 normal severity 1027553 normal severity 1027555 normal severity 1027559 normal severity 1027570 normal severity 1027578 normal severity 1027595 normal severity 1027597 normal severity 1027599 normal severity 1027616 normal severity 1027626 normal severity 1027641 normal severity 1027642 normal severity 1027644 normal severity 1027655 normal severity 1027665 normal thanks This issue is caused by pyqt6 not being rebuilt as part of the ongoing qt6baseabi-6.4.2 transition.--- End Message ---
Bug#1027114: marked as done (docker.io: FTBFS: daemon/graphdriver/btrfs/btrfs.go:437:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no field or method max_referenced)
Your message dated Sun, 01 Jan 2023 17:06:23 + with message-id and subject line Bug#1027114: fixed in docker.io 20.10.22+dfsg1-1 has caused the Debian Bug report #1027114, regarding docker.io: FTBFS: daemon/graphdriver/btrfs/btrfs.go:437:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no field or method max_referenced) 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.) -- 1027114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: docker.io Version: 20.10.21+dfsg1-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=docker.io=amd64=20.10.21%2Bdfsg1-1%2Bb1=1672110377=0 ---> Making bundle: dynbinary (in bundles/dynbinary) Building: bundles/dynbinary-daemon/dockerd-20.10.21+dfsg1 GOOS="" GOARCH="" GOARM="" # github.com/docker/docker/daemon/graphdriver/btrfs daemon/graphdriver/btrfs/btrfs.go:437:11: args.lim.max_referenced undefined (type _Ctype_struct_btrfs_qgroup_limit has no field or method max_referenced) make[1]: *** [debian/rules:114: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>' Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: docker.io Source-Version: 20.10.22+dfsg1-1 Done: Shengjing Zhu We believe that the bug you reported is fixed in the latest version of docker.io, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Shengjing Zhu (supplier of updated docker.io 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: Mon, 02 Jan 2023 00:36:21 +0800 Source: docker.io Architecture: source Version: 20.10.22+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Shengjing Zhu Closes: 1027114 Changes: docker.io (20.10.22+dfsg1-1) unstable; urgency=medium . * Team upload. * New upstream release [20.10.22] + Temperory vendor etcd 3.3 library. * Add patch for btrfs-progs 6.1 (Closes: #1027114) Checksums-Sha1: 08294c9f6db91f8021de16e2af25fe500d21a570 6976 docker.io_20.10.22+dfsg1-1.dsc 25eec1683231e64e1ce4d0c85e25360a27e53615 1841884 docker.io_20.10.22+dfsg1.orig-cli.tar.xz 360dad858608be190a3b02817e3ff3984e505bfb 654248 docker.io_20.10.22+dfsg1.orig-libnetwork.tar.xz eaa9d01633fc0324e6a8e3760a8328cc8a8e6877 775612 docker.io_20.10.22+dfsg1.orig-swarmkit.tar.xz 1637d8ce469a54ecd1f99f115ba1cb456429a629 2346508 docker.io_20.10.22+dfsg1.orig.tar.xz ec12333e695c09dbee68eb80a8ec10d40adb7772 46588 docker.io_20.10.22+dfsg1-1.debian.tar.xz fb55d511a54f886bcfcaf9ddcaac249d3529d3dc 24863 docker.io_20.10.22+dfsg1-1_amd64.buildinfo Checksums-Sha256: d3f653038d3a9796efd7e55715c880bf0e5a15a8ec4b748128e521ea680a4153 6976 docker.io_20.10.22+dfsg1-1.dsc 1bf52c76ffe2b00c9e1be1de1bb47ebd56c571547137bc8108e1a4bfe3dd83c1 1841884 docker.io_20.10.22+dfsg1.orig-cli.tar.xz 082ddd4a8e3919793450f5390c3914df837755de39462e21a60b400e35b3bf8b 654248 docker.io_20.10.22+dfsg1.orig-libnetwork.tar.xz 60d0a75217e4c74fe7ce819df4c5b4e34952eb4fac87ecef07f1d85b50cc511b 775612 docker.io_20.10.22+dfsg1.orig-swarmkit.tar.xz 91da1f7a84293752de2e3d943c7e03b99dc26672310f03f46b59c674f393632a 2346508 docker.io_20.10.22+dfsg1.orig.tar.xz 1bd307273cabebc3b45fea88b6b47d6cdf5ecdd0059db7c3dcbbea55a7c76b2f 46588 docker.io_20.10.22+dfsg1-1.debian.tar.xz b5e3be1481ea3ce1e26465484c499564632bd14a561793b9d0aa880ce9baadaf 24863 docker.io_20.10.22+dfsg1-1_amd64.buildinfo Files: 86a337ec491a0886520b0c56ac0b91d9 6976 admin optional docker.io_20.10.22+dfsg1-1.dsc 0e195ccbd2e20d700e2a7b571e592d12 1841884 admin optional docker.io_20.10.22+dfsg1.orig-cli.tar.xz 056d9b9afb1be6b2d062c6e1d770b63a 654248 admin optional docker.io_20.10.22+dfsg1.orig-libnetwork.tar.xz 513d42f8c21a37a17c37dee5e98622ba 775612 admin optional docker.io_20.10.22+dfsg1.orig-swarmkit.tar.xz 0b0cd4bcb74db01d883c50793481ede7 2346508 admin optional
Processed: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?)
Processing commands for cont...@bugs.debian.org: > severity 1027569 normal Bug #1027569 [src:dewalls] dewalls: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) Severity set to 'normal' from 'serious' > severity 1027620 normal Bug #1027620 [src:qmath3d] qmath3d: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) Severity set to 'normal' from 'serious' > severity 1027625 normal Bug #1027625 [src:plotsauce] plotsauce: FTBFS: unsatisfiable build-dependency: qt6-base-abi (= 6.3.1) (versioned dep on a virtual pkg?) Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 1027569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027569 1027620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027620 1027625: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027625 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forcemerge 1027474 1027651 Bug #1027474 [src:qbs] qbs: FTBFS: symol errors Bug #1027474 [src:qbs] qbs: FTBFS: symol errors Added tag(s) bookworm and sid. Bug #1027651 [src:qbs] qbs: FTBFS: 3: collect2: error: ld returned 1 exit status Merged 1027474 1027651 > End of message, stopping processing here. Please contact me if you need assistance. -- 1027474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027474 1027651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027651 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> reopen 1027474
Bug #1027474 {Done: Patrick Franz } [src:qbs] qbs: FTBFS:
symol errors
'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 qbs/1.24.0+dfsg-3.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1027474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: merge
Processing commands for cont...@bugs.debian.org: > merge 1018083 1019707 Bug #1018083 [src:snapd-glib] : flaky autopkgtest on s390x: test-glib.test timed out after 300 seconds Bug #1018083 [src:snapd-glib] : flaky autopkgtest on s390x: test-glib.test timed out after 300 seconds Marked as found in versions snapd-glib/1.58-4. Bug #1019707 [src:snapd-glib] snapd-glib: flaky autopkgtest, particularly on s390x: Test timed out after 300 seconds Marked as found in versions snapd-glib/1.60-1. Merged 1018083 1019707 > thanks Stopping processing here. Please contact me if you need assistance. -- 1018083: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018083 1019707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019707 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1027484: marked as done (commons-vfs build-depends on dropped package.)
Your message dated Sun, 01 Jan 2023 16:20:26 + with message-id and subject line Bug#1027484: fixed in commons-vfs 2.1-3 has caused the Debian Bug report #1027484, regarding commons-vfs build-depends on dropped package. 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.) -- 1027484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027484 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: commons-vfs Version: 2.1-2 Tags: bookworm, sid Severity: serious Justification: rc policy - "packages must be buildable within the same release" User: debian...@lists.debian.org Usertags: edos-uninstallable commons-vfs build-depends on libcommons-net-java-doc which is no longer built by the libcommons-net-java source package and has been removed from both testing and unstable. --- End Message --- --- Begin Message --- Source: commons-vfs Source-Version: 2.1-3 Done: tony mancill We believe that the bug you reported is fixed in the latest version of commons-vfs, 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 1027...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill (supplier of updated commons-vfs 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, 01 Jan 2023 07:29:33 -0800 Source: commons-vfs Architecture: source Version: 2.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: tony mancill Closes: 1027484 Changes: commons-vfs (2.1-3) unstable; urgency=medium . * Team upload. * Drop libcommons-vfs-java-doc (Closes: #1027484) * Freshen years in debian/copyright * Update Homepage URL * Update Vcs URLs to point to Salsa * Remove get-orig-source target from debian/rules * Use debhelper-compat (=13) * Bump Standards-Version to 4.6.2 Checksums-Sha1: fd543479df6fcd14583bd550a9544c0b61b1d960 2301 commons-vfs_2.1-3.dsc 81b00ffb708b1c662af357f4228f5f6e197c133e 5544 commons-vfs_2.1-3.debian.tar.xz 9ea9eb34ef2fc463423582f8523348cda294fff2 14851 commons-vfs_2.1-3_amd64.buildinfo Checksums-Sha256: 1d56d6f332e00f9058442f0aaeb9dbf3a695c25ed9314b4bbb4bf04b28ddf58f 2301 commons-vfs_2.1-3.dsc 9d874d43cc972a7c0746fe7a6d0ce3b46ac98e1bb00eef0a2f4cff2544c095f3 5544 commons-vfs_2.1-3.debian.tar.xz 1d1eb39806e84b2ea9d7eb5d64f8b84fee77420d5c90d03c8c804c6d0f4cde50 14851 commons-vfs_2.1-3_amd64.buildinfo Files: 8f6c5fd3b1cec0b2fbf50fc3097dfcba 2301 java optional commons-vfs_2.1-3.dsc 268b58abbc9a77e33df8ad0a4aa099fd 5544 java optional commons-vfs_2.1-3.debian.tar.xz f8a3b02b28e49a1f8296104f3cb74fc8 14851 java optional commons-vfs_2.1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmOxqHMUHHRtYW5jaWxs QGRlYmlhbi5vcmcACgkQIdIFiZdLPpZSGg//aYyi6Itm7KlQns7/NUZzaiJtGpyo RcdFa3GiKPWswbYW5YIpkPsUa6kLwPOg6Q2HEeJmxD/JSB79Jotp1bKmoBQ3yL7L rR6PURqgb02wxj7TktbLa2obKEIiYPw+zx4P9ATrLdw3DuDdnFP20dO2eWSh0TId Gkg/TisS9xaL8Sseb70MqDNRabRd8I5gKcHNCHzIOF+wSkUqogB7eWKhDVR5ykLf rsMwttx4mliubPN6ebfHWFAGPKQ6a0twrQ4lAetigtj0qz3WFMpARNXoUXYwYDQI oL6VHqzMd7ZnPedzqmy16m/c8RzUjH8I1zZDO+ihW/oAJLSOzQkxGuLs0o2SGv93 b22ZkOOii7OWpr3JaufjHEV4lMntN8G0/HV9gwhj6YGv/FJvz55a6Eqg4E56zA/Z AwrHAS4tPNoA2TCv/2l2DjIN1bJYipd4G1/Gl7Yz2fI+HvJdfVtq4U9PSKSy2rFC IV95mqCU26ZJIHWO52pnGJmzQ51JOxq+Ww/Kbfq9t4Wrga1LZqC3KARysWLP/MWS 2HfWLQ3ueTlyKq5zzTSa1sVQr4RK21cmvEeem+nymXtrypTg7SJAyGNDUjT6Tywu kgod0gD8AZ4rBheyUZJCqx+rGl0yvOC4QRMG2mqjkK7T+jcVpSUPGCxE76Axfekz QI4MIVA2v9WrBGk= =JtVp -END PGP SIGNATURE End Message ---
Processed: tagging 1027477, tagging 1027504
Processing commands for cont...@bugs.debian.org:
> tags 1027477 = ftbfs
Bug #1027477 {Done: Pino Toscano } [qt6-quicktimeline-dev]
qt6-quicktimeline-dev: missing qml6 dependency for cmake config files
Added tag(s) ftbfs; removed tag(s) pending.
> tags 1027504 = pending
Bug #1027504 [okular-dev] okular-dev: missing qtbase5-private-dev dependency
for Qt5::CorePrivate target in cmake config files
Added tag(s) pending; removed tag(s) ftbfs, bookworm, and sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1027477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027477
1027504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: affects 1027504
Processing commands for cont...@bugs.debian.org: > affects 1027504 + src:calligra Bug #1027504 [okular-dev] okular-dev: missing qtbase5-private-dev dependency for Qt5::CorePrivate target in cmake config files Added indication that 1027504 affects src:calligra > thanks Stopping processing here. Please contact me if you need assistance. -- 1027504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027504 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1017892: Ships copies of libraries that are in Debian and autogenerated files that can't be renegerated with the code in Debian main
Hi Sean, On Mon, 22 Aug 2022 14:29:56 -0700 Sean Whitton wrote: control: severity 1017906 wishlist > Is there ftp team consensus that either or both of these issues are RC? #1017892 is wishlist or not a bug. [...] #1017906 *might* be a problem. [...] It seems like you mixed up the bugs in your control message? I'm currently staring at #1017892 (vendored copies) because it's RC, but I agree with you it looks much less severe. Given that, do you think #1017906 (no source) should be raised again until somebody has figured out if there's *no* RC problem? Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: reassign 1027504 to okular-dev ..., tagging 1027477
Processing commands for cont...@bugs.debian.org:
> reassign 1027504 okular-dev okular/4:22.12.0-1
Bug #1027504 [src:calligra] calligra: FTBFS: src.cxx:9:17: error: invalid
conversion from ‘const char**’ to ‘char**’ [-fpermissive]
Bug reassigned from package 'src:calligra' to 'okular-dev'.
No longer marked as found in versions calligra/1:3.2.1+dfsg-6.
Ignoring request to alter fixed versions of bug #1027504 to the same values
previously set
Bug #1027504 [okular-dev] calligra: FTBFS: src.cxx:9:17: error: invalid
conversion from ‘const char**’ to ‘char**’ [-fpermissive]
Marked as found in versions okular/4:22.12.0-1.
> retitle 1027504 okular-dev: missing qtbase5-private-dev dependency for
> Qt5::CorePrivate target in cmake config files
Bug #1027504 [okular-dev] calligra: FTBFS: src.cxx:9:17: error: invalid
conversion from ‘const char**’ to ‘char**’ [-fpermissive]
Changed Bug title to 'okular-dev: missing qtbase5-private-dev dependency for
Qt5::CorePrivate target in cmake config files' from 'calligra: FTBFS:
src.cxx:9:17: error: invalid conversion from ‘const char**’ to ‘char**’
[-fpermissive]'.
> tags 1027477 = pending
Bug #1027477 {Done: Pino Toscano } [qt6-quicktimeline-dev]
qt6-quicktimeline-dev: missing qml6 dependency for cmake config files
Added tag(s) pending; removed tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1027477: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027477
1027504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 1027637 to qt6-quick3d-dev, forcibly merging 1027475 1027637
Processing commands for cont...@bugs.debian.org:
> reassign 1027637 qt6-quick3d-dev
Bug #1027637 {Done: Pino Toscano } [qt6-quick3d-dev]
qtcreator: FTBFS: make[1]: *** [debian/rules:36: override_dh_auto_configure]
Error 2
Bug #1027475 {Done: Pino Toscano } [qt6-quick3d-dev]
qt6-quick3d-dev: missing qml6 dependencies for cmake config files
Ignoring request to reassign bug #1027637 to the same package
Ignoring request to reassign bug #1027475 to the same package
> forcemerge 1027475 1027637
Bug #1027475 {Done: Pino Toscano } [qt6-quick3d-dev]
qt6-quick3d-dev: missing qml6 dependencies for cmake config files
Bug #1027637 {Done: Pino Toscano } [qt6-quick3d-dev]
qtcreator: FTBFS: make[1]: *** [debian/rules:36: override_dh_auto_configure]
Error 2
Bug #1027637 {Done: Pino Toscano } [qt6-quick3d-dev]
qtcreator: FTBFS: make[1]: *** [debian/rules:36: override_dh_auto_configure]
Error 2
Merged 1027475 1027637
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1027475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027475
1027637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
