Processed: src:gprconfig-kb: fails to migrate to testing for too long: autopkgtest regression
Processing control commands: > close -1 23.0.0-4 Bug #1056633 [src:gprconfig-kb] src:gprconfig-kb: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions gprconfig-kb/23.0.0-4. Bug #1056633 [src:gprconfig-kb] src:gprconfig-kb: fails to migrate to testing for too long: autopkgtest regression Marked Bug as done -- 1056633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056633: src:gprconfig-kb: fails to migrate to testing for too long: autopkgtest regression
Source: gprconfig-kb Version: 23.0.0-3 Severity: serious Control: close -1 23.0.0-4 Tags: sid trixie 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 30 days as having a Release Critical bug in testing [1]. Your package src:gprconfig-kb has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable doesn't pass its own autopkgtest on multiple architectures as some test dependencies aren't available there. 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 trixie, 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/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=gprconfig-kb OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1052949: closing 1052949
close 1052949 thanks
Processed: closing 1052949
Processing commands for cont...@bugs.debian.org: > close 1052949 Bug #1052949 [src:gap-polymaking] gap-polymaking: FTBFS: polymake: ERROR: "/usr/share/polymake/perllib/Polymake/Core/CPlusPlus.pm", line 1785: Can't load shared module /usr/lib/polymake/lib/ideal.so: libsingular-Singular-4.3.1.so: cannot open shared object file: No such file or directory Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1052949: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052949 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052949: closing 1052949
close 1052949 jzo...@heute-morgen.de thanks
Bug#1055862: marked as done (node-http-proxy-agent: missing Breaks+Replaces: node-https-proxy-agent (<< 7))
Your message dated Fri, 24 Nov 2023 03:04:18 + with message-id and subject line Bug#1055862: fixed in node-proxy-agents 0~2023071921-3 has caused the Debian Bug report #1055862, regarding node-http-proxy-agent: missing Breaks+Replaces: node-https-proxy-agent (<< 7) 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.) -- 1055862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-http-proxy-agent Version: 7.0.0~0~2023071921-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'sid' to 'experimental'. It installed fine in 'sid', then the upgrade to 'experimental' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. This error may also be triggered by having a predecessor package from 'sid' installed while installing the package from 'experimental'. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../node-http-proxy-agent_7.0.0~0~2023071921-1_all.deb ... Unpacking node-http-proxy-agent (7.0.0~0~2023071921-1) ... dpkg: error processing archive /var/cache/apt/archives/node-http-proxy-agent_7.0.0~0~2023071921-1_all.deb (--unpack): trying to overwrite '/usr/share/nodejs/http-proxy-agent/dist/index.d.ts', which is also in package node-https-proxy-agent 5.0.1+~cs8.0.0-3 Errors were encountered while processing: /var/cache/apt/archives/node-http-proxy-agent_7.0.0~0~2023071921-1_all.deb The following files have moved to a new package: usr/share/nodejs/http-proxy-agent/dist/index.d.ts usr/share/nodejs/http-proxy-agent/dist/index.js usr/share/nodejs/http-proxy-agent/dist/index.js.map usr/share/nodejs/http-proxy-agent/package.json cheers, Andreas node-https-proxy-agent=5.0.1+~cs8.0.0-3_node-http-proxy-agent=7.0.0~0~2023071921-1.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: node-proxy-agents Source-Version: 0~2023071921-3 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-proxy-agents, 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 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-proxy-agents package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 24 Nov 2023 06:22:44 +0400 Source: node-proxy-agents Built-For-Profiles: nocheck Architecture: source Version: 0~2023071921-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1055862 1056599 Changes: node-proxy-agents (0~2023071921-3) unstable; urgency=medium . * Team upload * Add missing Breaks+Replaces node-https-proxy-agent < 7 in node-http-proxy-agent (Closes: #1055862) * Drop tests that needs Internet (Closes: #1056599) Checksums-Sha1: bf86d686d90e0ab48ed73ebfa4622458172427f8 4275 node-proxy-agents_0~2023071921-3.dsc eaa441efec0944dabca50e00967795954735c6bb 43712 node-proxy-agents_0~2023071921-3.debian.tar.xz Checksums-Sha256: 94112a247c3a51c55f86a88c6783db9c2fbc164e198e082f8c67d4a9f652be09 4275 node-proxy-agents_0~2023071921-3.dsc 144c0cd12b51848a50d7bda91936dcd91b14f53f67e77752c0730b4e1b179ab4 43712 node-proxy-agents_0~2023071921-3.debian.tar.xz Files: a786c2cf56e9cae4d94f7f1b442898c8 4275 javascript optional node-proxy-agents_0~2023071921-3.dsc b6df728d1daf7bb43b0bf598aad6e8cf 43712 javascript optional node-proxy-agents_0~2023071921-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmVgCXMACgkQ9tdMp8mZ 7um/ng//UOstRKbm5RgiIVpoiftk0YfnyU4Dh48iH5sKPJiTrAAva5HRXVl+yzYk DJn+nYyr5F2sQP2dnuwsx8e8suIUV97i1JIqW0XMXmGEu3b7VA9+9zmtl/ygydAZ kpYCBrvTKhD3X4dSgqACnGmhty4uO2cH1v9Q18xxHGRq87c+AbEsGFozwi+vha5J 6jbn2YYL48fR6v9SXQQ+WOJ6cKdY8TH/uDJWPaMW4r4XMla81HJqnmuUk4NheRpm O+nc6waNGdWSJtKm+KoZR5u7k8vlLolEFwLRN5PDs+/ktGfuzCbProuueDzA2K59
Bug#1056599: marked as done (node-proxy-agents: FTBFS with internet disabled)
Your message dated Fri, 24 Nov 2023 03:04:18 +
with message-id
and subject line Bug#1056599: fixed in node-proxy-agents 0~2023071921-3
has caused the Debian Bug report #1056599,
regarding node-proxy-agents: FTBFS with internet disabled
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.)
--
1056599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056599
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-proxy-agents
Version: 0~2023071921-1
Severity: serious
Hello, looks like the package tries to do calls to internet during build.
+ jest --testTimeout 5 --env node --moduleDirectories node_modules
--testRegex test/dnsDomainIs.test.ts test/dnsDomainLevels.test.ts
test/dnsResolve.test.ts test/isInNet.test.ts test/isPlainHostName.test.ts
test/isResolvable.test.ts test/localHostOrDomainIs.test.ts
test/shExpMatch.test.ts test/timeRange.test.ts
PASS test/shExpMatch.test.ts
PASS test/timeRange.test.ts
PASS test/localHostOrDomainIs.test.ts
(node:8627) [DEP0118] DeprecationWarning: The provided hostname "null" is not a
valid hostname, and is supported in the dns module solely for compatibility.
(Use `node --trace-deprecation ...` to show where the warning was created)
PASS test/isInNet.test.ts
FAIL test/dnsResolve.test.ts
● dnsResolve(host) › should return `true` for "www.netscape.com"
assert(received)
Expected value to be equal to:
true
Received:
false
12 | const res = await dnsResolve(input);
13 | if (expected) {
> 14 | assert(typeof res === 'string');
|^
15 | expect(isIP(res)).toEqual(4);
16 | } else {
17 | expect(res).toBeNull();
at test/dnsResolve.test.ts:14:11
PASS test/dnsDomainIs.test.ts
FAIL test/isResolvable.test.ts
● isResolvable(host) › should return `true` for "www.netscape.com"
expect(received).toEqual(expected) // deep equality
Expected: true
Received: false
9 | async ({ input, expected }) => {
10 | const res = await isResolvable(input);
> 11 | expect(res).toEqual(expected);
| ^
12 | }
13 | );
14 | });
at test/isResolvable.test.ts:11:16
PASS test/isPlainHostName.test.ts
PASS test/dnsDomainLevels.test.ts
Test Suites: 2 failed, 7 passed, 9 total
Tests: 2 failed, 37 passed, 39 total
Snapshots: 0 total
Time:4.549 s
Ran all test suites.
dh_auto_test: error: cd ./packages/pac-resolver && sh -ex
../../debian/nodejs/packages/pac-resolver/test returned exit code 1
make: *** [debian/rules:10: binary] Error 25
Gianfranco
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-proxy-agents
Source-Version: 0~2023071921-3
Done: Yadd
We believe that the bug you reported is fixed in the latest version of
node-proxy-agents, 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 1056...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yadd (supplier of updated node-proxy-agents package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 24 Nov 2023 06:22:44 +0400
Source: node-proxy-agents
Built-For-Profiles: nocheck
Architecture: source
Version: 0~2023071921-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Yadd
Closes: 1055862 1056599
Changes:
node-proxy-agents (0~2023071921-3) unstable; urgency=medium
.
* Team upload
* Add missing Breaks+Replaces node-https-proxy-agent < 7 in
node-http-proxy-agent (Closes: #1055862)
* Drop tests that needs Internet (Closes: #1056599)
Checksums-Sha1:
bf86d686d90e0ab48ed73ebfa4622458172427f8 4275
node-proxy-agents_0~2023071921-3.dsc
eaa441efec0944dabca50e00967795954735c6bb 43712
node-proxy-agents_0~2023071921-3.debian.tar.xz
Checksums-Sha256:
Processed: Bug#1056599 marked as pending in node-proxy-agents
Processing control commands: > tag -1 pending Bug #1056599 [src:node-proxy-agents] node-proxy-agents: FTBFS with internet disabled Added tag(s) pending. -- 1056599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056599: marked as pending in node-proxy-agents
Control: tag -1 pending Hello, Bug #1056599 in node-proxy-agents 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-proxy-agents/-/commit/0c04315db7e332a47986831e17b35b4fd4cda8dc Drop tests that needs Internet Closes: #1056599 (this message was generated automatically) -- Greetings https://bugs.debian.org/1056599
Processed: Bug#1055862 marked as pending in node-proxy-agents
Processing control commands: > tag -1 pending Bug #1055862 [node-http-proxy-agent] node-http-proxy-agent: missing Breaks+Replaces: node-https-proxy-agent (<< 7) Added tag(s) pending. -- 1055862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055862: marked as pending in node-proxy-agents
Control: tag -1 pending Hello, Bug #1055862 in node-proxy-agents 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-proxy-agents/-/commit/4c7081cebe776c994e6a97e5b604faa5b01ff973 Add missing Breaks+Replaces node-https-proxy-agent < 7 in node-http-proxy-agent Closes: #1055862 (this message was generated automatically) -- Greetings https://bugs.debian.org/1055862
Processed: cython3 has an undeclared file conflict
Processing control commands: > affects -1 + cython3-dbg Bug #1056627 [cython3] cython3 has an undeclared file conflict Added indication that 1056627 affects cython3-dbg -- 1056627: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056627 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056627: cython3 has an undeclared file conflict
Package: cython3 Version: 0.29.36-2 Severity: serious User: debian...@lists.debian.org Usertags: fileconflict Control: affects -1 + cython3-dbg cython3 has an undeclared file conflict. This may result in an unpack error from dpkg. The files * /usr/lib/python3/dist-packages/Cython/Compiler/FlowControl.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Compiler/FusedNode.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Compiler/Scanning.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Compiler/Visitor.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Plex/Actions.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Plex/Scanners.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Runtime/refnanny.cpython-311d-x86_64-linux-gnu.so * /usr/lib/python3/dist-packages/Cython/Tempita/_tempita.cpython-311d-x86_64-linux-gnu.so are contained in the packages * cython3/0.29.36-2 as present in unstable * cython3-dbg * 0.29.32-2+b1 as present in bookworm * 0.29.36-1 as present in trixie These packages can be unpacked concurrently, because there is no relevant Replaces or Conflicts relation. Attempting to unpack these packages concurrently results in an unpack error from dpkg, because none of the packages installs a diversion for the affected files. Kind regards The Debian Usr Merge Analysis Tool This bug report has been automatically filed with no human intervention. The source code is available at https://salsa.debian.org/helmutg/dumat. If the filing is unclear or in error, don't hesitate to contact hel...@subdivi.de for assistance.
Bug#1054718: marked as done (ruby-uc.micro-rb: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: require 'pry-byebug')
Your message dated Thu, 23 Nov 2023 23:06:51 + with message-id and subject line Bug#1054718: fixed in ruby-uc.micro-rb 1.0.6-1 has caused the Debian Bug report #1054718, regarding ruby-uc.micro-rb: FTBFS: ERROR: Test "ruby3.1" failed: Failure/Error: require 'pry-byebug' 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.) -- 1054718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-uc.micro-rb Version: 1.0.5-2 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20231027 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Failure/Error: require 'pry-byebug' > > Gem::MissingSpecError: > Could not find 'pry' (~> 0.13.0) among 103 total gem(s) > Checked in > 'GEM_PATH=/<>/debian/ruby-uc.micro-rb/usr/share/rubygems-integration/all:/<>/debian/.debhelper/generated/_source/home/.local/share/gem/ruby/3.1.0:/var/lib/gems/3.1.0:/usr/local/lib/ruby/gems/3.1.0:/usr/lib/ruby/gems/3.1.0:/usr/lib/x86_64-linux-gnu/ruby/gems/3.1.0:/usr/share/rubygems-integration/3.1.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/3.1.0' > at: > /usr/share/rubygems-integration/all/specifications/pry-byebug-3.9.0.gemspec, > execute `gem env` for more information > # ./spec/spec_helper.rb:1:in `' > # ./spec/uc.micro-rb/test_spec.rb:1:in `' > # -- > # --- Caused by: --- > # LoadError: > # cannot load such file -- pry-byebug > # ./spec/spec_helper.rb:1:in `' > No examples found. > > Finished in 0.5 seconds (files took 0.18527 seconds to load) > 0 examples, 0 failures, 1 error occurred outside of examples > > /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 --format documentation failed > ERROR: Test "ruby3.1" failed: The full build log is available from: http://qa-logs.debian.net/2023/10/27/ruby-uc.micro-rb_1.0.5-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20231027;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20231027=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: ruby-uc.micro-rb Source-Version: 1.0.6-1 Done: Cédric Boutillier We believe that the bug you reported is fixed in the latest version of ruby-uc.micro-rb, 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 1054...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cédric Boutillier (supplier of updated ruby-uc.micro-rb 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: Thu, 23 Nov 2023 22:38:59 +0100 Source: ruby-uc.micro-rb Architecture: source Version: 1.0.6-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Cédric Boutillier Closes: 1054718 Changes: ruby-uc.micro-rb (1.0.6-1) unstable; urgency=medium . * Team upload * Remove pry-byebug from tests (Closes: #1054718) + Do not build-depend on ruby-pry-byebug anymore * Remove X?-Ruby-Versions fields from d/control * Bump Standards-Version to 4.6.2 (no changes needed) * New upstream version 1.0.6 * standard .gitattributes Checksums-Sha1: 2c22edfa98def37dd84b50e46e40b221be16122d 1463 ruby-uc.micro-rb_1.0.6-1.dsc 35443d754c7f3c783db36014faff748c61fbf976 3173 ruby-uc.micro-rb_1.0.6.orig.tar.gz
Bug#1056621: reportbug: http://www.crbug.com
Package: reportbug Version: 12.0.0 Severity: serious Justification: Please do not redirect bugs to third party sites Dear Maintainer, pkg chromium is redirecting bugs through reportbug to http://www.crbug.com $ apt policy chromium chromium: Installed: 119.0.6045.159-1~deb12u1 I do not appreciate this. thanks, bw -- Package-specific info: ** Environment settings: INTERFACE="text" ** /home/user/.reportbugrc: reportbug_version "7.1.7" mode standard ui text email "bwtn...@yahoo.com" no-cc smtphost reportbug.debian.org -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-0.deb12.1-amd64 (SMP w/8 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 reportbug depends on: ii apt2.6.1 ii python33.11.2-1+b1 ii python3-reportbug 12.0.0 ii sensible-utils 0.0.17+nmu1 reportbug recommends no packages. Versions of packages reportbug suggests: pn claws-mail ii debconf1.5.82 pn debsums pn dlocate pn emacs-bin-common ii exim4-daemon-light [mail-transport-agent] 4.96-15+deb12u2 ii file 1:5.44-3 ii gnupg 2.2.40-1.1 pn python3-urwid pn reportbug-gtk ii xdg-utils 1.1.3-4.1 Versions of packages python3-reportbug depends on: ii apt2.6.1 ii file 1:5.44-3 ii python33.11.2-1+b1 ii python3-apt2.6.0 ii python3-debian 0.1.49 ii python3-debianbts 4.0.1 ii python3-requests 2.28.1+dfsg-1 ii sensible-utils 0.0.17+nmu1 python3-reportbug suggests no packages. -- no debconf information
Processed: lowering priority
Processing control commands: > severity -1 important Bug #1056580 [src:llvm-toolchain-17] LLVM-17's autopkg tests fail (command1) Severity set to 'important' from 'serious' -- 1056580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056580: lowering priority
Control: severity -1 important lowering priority, technically it's not a regression (new package).
Bug#1053686: pandoc: cannot fulfill the build dependencies
Quoting Ilias Tsitsimpis (2023-11-23 21:10:36) > On Fri, Nov 17, 2023 at 09:28AM, Ilias Tsitsimpis wrote: > > On Thu, Nov 16, 2023 at 10:16PM, Jonas Smedegaard wrote: > > > Quoting John MacFarlane (2023-11-16 19:25:17) > > > > Removing lua support would be most unfortunate! If you need help from > > > > upstream in getting things to work, let me know. > > > > > > I agree: Pandoc with its core scripting language disabled is a severely > > > crippled Pandoc. > > > > Understood, but I am not really sure how to move forward, since Pandoc > > doesn't fully support the latest Stackage LTS. I can help with > > packaging/upgrade libraries if you can provide the right set of > > libraries we need. > > I uploaded the following packages: > > * haskell-hslua-cli_v1.3.0-1, > * haskell-hslua-module-doclayout_v1.1.0-1 > * haskell-hslua-module-zip_v1.1.0-1 > > I believe the next step is to update pandoc to 3.0.1, so we can then > package pandoc-lua-engine, pandoc-server and eventually pandoc-cli. > > Jonas, how can I help move this forward? Pandoc is the last blocker to > finish the Haskell transition. I think this will be the best way forward: Haskell team introduces new source package haskell-pandoc. When available, I can build package pandoc depending on it. I really don't like breaking upstream project pandoc into two Debian source packages like that, but I don't have the energy at the moment to try fix dh-haskell (which I suspect will be similar work as I am doing to dh-cargo currently). - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ * Sponsorship: https://ko-fi.com/drjones [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1056608: timeshift: Timeshift cant restore RSYNC snapshots if your system installed on BTRFS with wrong subvolume
Package: timeshift Version: 22.11.2-1 Severity: grave Justification: causes non-serious data loss X-Debbugs-Cc: truescore149...@gmail.com Dear Maintainer, User cant make BTRFS snapshots without "@" subvolume (debian uses "@rootfs"), but user can make RSYNC snapshot. The problem is that when you try to restore that snapshot, you have alert about wrong BTRFS subvolumes, but RSYNC doesnt need BTRFS subvolumes. Steps to reproduce : * Install Debian on BTRFS * Create a RSYNC (not BTRFS) snapshot * Try to restore that snapshot Upstream doesnt have that problem, but I decided to report it because it can greatly damage the system due to the illusion of security. The user creates a snapshot thinking that this will save him from serious system errors and ultimately will not be able to recover. Thank you for your attention, -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-13-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 timeshift depends on: ii cron [cron-daemon] 3.0pl1-162 ii libc62.36-9+deb12u3 ii libcairo21.16.0-7 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-1+b1 ii libgee-0.8-2 0.20.6-1 ii libglib2.0-0 2.74.6-2 ii libgtk-3-0 3.24.38-2~deb12u1 ii libjson-glib-1.0-0 1.6.6-1 ii libvte-2.91-00.70.6-2~deb12u1 ii libxapp1 2.4.2-3 ii psmisc 23.6-1 ii rsync3.2.7-1 timeshift recommends no packages. timeshift suggests no packages. -- no debconf information
Bug#1053686: pandoc: cannot fulfill the build dependencies
On Fri, Nov 17, 2023 at 09:28AM, Ilias Tsitsimpis wrote: > On Thu, Nov 16, 2023 at 10:16PM, Jonas Smedegaard wrote: > > Quoting John MacFarlane (2023-11-16 19:25:17) > > > Removing lua support would be most unfortunate! If you need help from > > > upstream in getting things to work, let me know. > > > > I agree: Pandoc with its core scripting language disabled is a severely > > crippled Pandoc. > > Understood, but I am not really sure how to move forward, since Pandoc > doesn't fully support the latest Stackage LTS. I can help with > packaging/upgrade libraries if you can provide the right set of > libraries we need. I uploaded the following packages: * haskell-hslua-cli_v1.3.0-1, * haskell-hslua-module-doclayout_v1.1.0-1 * haskell-hslua-module-zip_v1.1.0-1 I believe the next step is to update pandoc to 3.0.1, so we can then package pandoc-lua-engine, pandoc-server and eventually pandoc-cli. Jonas, how can I help move this forward? Pandoc is the last blocker to finish the Haskell transition. -- Ilias
Bug#1052975: marked as done (assess-el: FTBFS: make: *** [debian/rules:4: binary] Error 25)
Your message dated Thu, 23 Nov 2023 19:03:55 +
with message-id
and subject line Bug#1052975: fixed in assess-el 0.6+git20231120.2399936-1
has caused the Debian Bug report #1052975,
regarding assess-el: FTBFS: make: *** [debian/rules:4: binary] Error 25
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.)
--
1052975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: assess-el
Version: 0.6-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> skipping upstream build
> make[1]: Leaving directory '/<>'
>dh_elpa_test
> emacs -batch -Q -l package --eval "(add-to-list 'package-directory-list
> \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list
> 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f
> package-initialize -L . -L test -l test/assess-robot-test.el -l
> test/assess-call-test.el -l test/assess-discover-test.el -l
> test/assess-test.el --eval \(ert-run-tests-batch-and-exit\)
> Running 46 tests (2023-09-26 06:54:47+, selector ‘t’)
>passed 1/46 assess--test-indent-in-mode (0.000344 sec)
>passed 2/46 assess--test-indentation= (0.011001 sec)
>passed 3/46 assess-call-return-value (0.000122 sec)
>passed 4/46 assess-call-test-capture-fail (0.000128 sec)
>passed 5/46 assess-call-test-hook-fail (0.57 sec)
>passed 6/46 assess-call-test-hook-test (0.000101 sec)
>passed 7/46 assess-discover-test (0.34 sec)
>passed 8/46 assess-discover-test-has-this-been-defined (0.28 sec)
>failed 9/46 assess-fail-for-sure (0.70 sec)
> Test assess-robot-test-execute-kmacro backtrace:
> signal(wrong-type-argument (integer-or-marker-p [104 101 108 108 111
> apply(signal (wrong-type-argument (integer-or-marker-p [104 101 108
> (setq value-23 (apply fn-21 args-22))
> (unwind-protect (setq value-23 (apply fn-21 args-22)) (setq form-des
> (if (unwind-protect (setq value-23 (apply fn-21 args-22)) (setq form
> (let (form-description-25) (if (unwind-protect (setq value-23 (apply
> (let ((value-23 'ert-form-evaluation-aborted-24)) (let (form-descrip
> (let* ((fn-21 #'assess=) (args-22 (condition-case err (let ((signal-
> (closure (t) nil (let* ((fn-21 #'assess=) (args-22 (condition-case e
> ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
> ert-run-test(#s(ert-test :name assess-robot-test-execute-kmacro :doc
> ert-run-or-rerun-test(#s(ert--stats :selector t :tests ... :test-map
> ert-run-tests(t #f(compiled-function (event-type event-args) #
> ert-run-tests-batch(nil)
> ert-run-tests-batch-and-exit()
> command-line-1(("-l" "package" "--eval" "(add-to-list 'package-direc
> command-line()
> normal-top-level()
> Test assess-robot-test-execute-kmacro condition:
> (wrong-type-argument integer-or-marker-p
>[104 101 108 108 111])
>FAILED 10/46 assess-robot-test-execute-kmacro (0.003662 sec) at
> test/assess-robot-test.el:65
>passed 11/46 assess-robot-test-with-switched-buffer (0.000137 sec)
>passed 12/46 assess-robot-test-with-switched-buffer-string (0.80 sec)
>passed 13/46 assess-robot-test-with-temp-switched-buffer (0.72 sec)
>passed 14/46 assess-test-create-multiple-directories-and-files (0.000675
> sec)
>passed 15/46 assess-test-create-multiple-files (0.000552 sec)
>passed 16/46 assess-test-create-nested-directories (0.000478 sec)
>passed 17/46 assess-test-create-non-empty-file (0.000463 sec)
>passed 18/46 assess-test-create-non-empty-nested-file (0.000530 sec)
>passed 19/46 assess-test-face-at-multiple-faces (0.002377 sec)
>passed 20/46 assess-test-face-at-multiple-positions (0.000815 sec)
>passed 21/46 assess-test-face-at-simple (0.000532 sec)
>passed 22/46 assess-test-face-at-with-m-buffer (0.000492 sec)
>passed 23/46 assess-test-face-at-with-strings (0.000877 sec)
>passed 24/46 assess-test-file-face-at (0.004856 sec)
>passed 25/46 assess-test-file-roundtrip-indentation-explain= (0.007721
> sec)
>passed 26/46 assess-test-file-roundtrip-indentation= (0.010114 sec)
>passed 27/46 assess-test-nest-files-recursively (0.001947 sec)
>passed 28/46 assess-test-related-file (0.000527 sec)
>passed 29/46
Bug#1056599: node-proxy-agents: FTBFS with internet disabled
Source: node-proxy-agents
Version: 0~2023071921-1
Severity: serious
Hello, looks like the package tries to do calls to internet during build.
+ jest --testTimeout 5 --env node --moduleDirectories node_modules
--testRegex test/dnsDomainIs.test.ts test/dnsDomainLevels.test.ts
test/dnsResolve.test.ts test/isInNet.test.ts test/isPlainHostName.test.ts
test/isResolvable.test.ts test/localHostOrDomainIs.test.ts
test/shExpMatch.test.ts test/timeRange.test.ts
PASS test/shExpMatch.test.ts
PASS test/timeRange.test.ts
PASS test/localHostOrDomainIs.test.ts
(node:8627) [DEP0118] DeprecationWarning: The provided hostname "null" is not a
valid hostname, and is supported in the dns module solely for compatibility.
(Use `node --trace-deprecation ...` to show where the warning was created)
PASS test/isInNet.test.ts
FAIL test/dnsResolve.test.ts
● dnsResolve(host) › should return `true` for "www.netscape.com"
assert(received)
Expected value to be equal to:
true
Received:
false
12 | const res = await dnsResolve(input);
13 | if (expected) {
> 14 | assert(typeof res === 'string');
|^
15 | expect(isIP(res)).toEqual(4);
16 | } else {
17 | expect(res).toBeNull();
at test/dnsResolve.test.ts:14:11
PASS test/dnsDomainIs.test.ts
FAIL test/isResolvable.test.ts
● isResolvable(host) › should return `true` for "www.netscape.com"
expect(received).toEqual(expected) // deep equality
Expected: true
Received: false
9 | async ({ input, expected }) => {
10 | const res = await isResolvable(input);
> 11 | expect(res).toEqual(expected);
| ^
12 | }
13 | );
14 | });
at test/isResolvable.test.ts:11:16
PASS test/isPlainHostName.test.ts
PASS test/dnsDomainLevels.test.ts
Test Suites: 2 failed, 7 passed, 9 total
Tests: 2 failed, 37 passed, 39 total
Snapshots: 0 total
Time:4.549 s
Ran all test suites.
dh_auto_test: error: cd ./packages/pac-resolver && sh -ex
../../debian/nodejs/packages/pac-resolver/test returned exit code 1
make: *** [debian/rules:10: binary] Error 25
Gianfranco
OpenPGP_signature.asc
Description: OpenPGP digital signature
Bug#1056348: FTBFS: tests fail in clean environment
Le 2023-11-23 à 11 h 20, Steve McIntyre a écrit : AFAICS in a non-interactive environment, USER isn't required to be set but LOGNAME is; see https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html Alternatively, the tets should probably be calling get(e)uid and getpwent() rather than relying on the environment here. Indeed, I also had the same conclusion using other documentation. But then, if LOGNAME is mandatory, I suppose it would be better to use $LOGNAME alone instead of the condition. (I'm not refusing your patch, I just try to see if there's a better and cleaner way to fix it) I'll open a bug upstream to get their feedback on this /Nicolas
Processed: [bts-link] source package src:assess-el
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:assess-el > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1052975 (http://bugs.debian.org/1052975) > # Bug title: assess-el: FTBFS: make: *** [debian/rules:4: binary] Error 25 > # * https://github.com/phillord/assess/issues/19 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1052975 + fixed-upstream Bug #1052975 [src:assess-el] assess-el: FTBFS: make: *** [debian/rules:4: binary] Error 25 Added tag(s) fixed-upstream. > usertags 1052975 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1052975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052975 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: [bts-link] source package dracut
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package dracut > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1056059 (http://bugs.debian.org/1056059) > # Bug title: dracut: systemd 255: dracut fails to boot due to lack of > systemd-executor > # * https://github.com/dracutdevs/dracut/pull/2535 > # * remote status changed: (?) -> closed > # * closed upstream > tags 1056059 + fixed-upstream Bug #1056059 [dracut] dracut: systemd 255: dracut fails to boot due to lack of systemd-executor Added tag(s) fixed-upstream. > usertags 1056059 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056059 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1052949: closing 1052949
close 1052949 jzo...@heute-morgen.de Should be fixed in polymake 4.11-1
Bug#1056594: mat2: test failure
Source: mat2 Version: 0.13.4-2 Severity: serious Tags: upstream patch ftbfs Justification: fails to build from source (but built successfully in the past) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Currently mat2's test suite fails, maybe due to newer libimage-exiftool-perl releases. This can be seen on ci.debian.net, but the same failures occur during the build tests, so the package FTBFS. I've locally added upstream commit https://0xacab.org/jvoisin/mat2/-/commit/bbd5b2817c9d64013e2f5ed670aca8d4738bb484 as a quilt patch, and the tests pass both during build and autopkgtest. Cheers, gregor -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmVfhfFfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgbGDw/+IvB5zN2PAQj7XFfbyVvqdjr3JIp7krnucMzO+qBemoFW2BdVptGFawgD XrEn2nj5XtKmG3EKLnqKjevLLeAcgFILEviUa0U1tM+/2pJkHiFC7J3eK5x8ug+9 JRjLVEh3WpG3vdBbvsOQ52B7xurqahfU9ReqR8Awnd/dQUXYycWgei/CUC320KRS bfuRPcbsR+ibwspLD+3iw8oezikr/WCzXyYjffASJYQDyp7D+LOpHGVfHfFYAVt0 xJby75cKpq0AcMC2Rgg8JYYK0GJ/RJ4a8jptXohl8hcEA8w6htYxUiedA0eaikS3 9t9o2/7yZObpd3TYmpuoGRz00cpQ3bEYATZlYALs1umoCp9WsOjJ8by8tnHKZxUa 7jOfdRhTRF0rkwZ07LoneMFg966HaDTAQeN0TMHKLYvShY7hyVFNf+1AD02qqP8x +guJ2YQw7U5mu4aEJtNvUXv1Pqh8Hl9hbiQNn23yL8IoCvfDzZUAqaEzRmLYjVt2 Ujoj6LHZgOZsBprIEBMch86MgyL65CeCzJr6JZ8wZmb/b//rPcVAv/VElTs+GfzS Ka8qQygGzvulrIsA2t0loJG7QtwRcZk6ckaCq/2IVvgDpFf4UCIOGnAt2qtt0+Ak Xy9Wb0YgnrY0v7BeTMZ+XU5LzWHqWLmj1d3PDvmy+sp9elbUgRU= =mYNd -END PGP SIGNATURE-
Bug#1056348: FTBFS: tests fail in clean environment
On Thu, Nov 23, 2023 at 10:46:34AM -0500, Nicolas Mora wrote: >Le 2023-11-23 à 09 h 46, Steve McIntyre a écrit : >> >> Ah, apologies - that version is bogus, it's just the version on the >> bullseye machine I ran reportbug from. >> >> The tests are failing on current unstable source. >> > >OK, makes more sense then. > >Nevertheless I'm wondering about the seriousness of the bug, I can't >reproduce on my environment and all the buildd environments where libssh2 is >built don't have the problem. AFAICS in a non-interactive environment, USER isn't required to be set but LOGNAME is; see https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html Alternatively, the tets should probably be calling get(e)uid and getpwent() rather than relying on the environment here. >Could your issue be fixed by running something like this? >USER=$LOGNAME dpkg-buiildpackage > >I'm just wondering if the patch is worth applying it to fix a less probable >case. The tests failed in a CI system we use at work, so I needed to fix it there. The patch just adds fallback here, and makes things more robust. -- Steve McIntyre, Cambridge, UK.st...@einval.com You raise the blade, you make the change... You re-arrange me 'til I'm sane...
Bug#1056348: FTBFS: tests fail in clean environment
Le 2023-11-23 à 09 h 46, Steve McIntyre a écrit : Ah, apologies - that version is bogus, it's just the version on the bullseye machine I ran reportbug from. The tests are failing on current unstable source. OK, makes more sense then. Nevertheless I'm wondering about the seriousness of the bug, I can't reproduce on my environment and all the buildd environments where libssh2 is built don't have the problem. Could your issue be fixed by running something like this? USER=$LOGNAME dpkg-buiildpackage I'm just wondering if the patch is worth applying it to fix a less probable case. /Nicolas
Bug#1056396: marked as done (orthanc-webviewer: autopkgtest failure on !x86)
Your message dated Thu, 23 Nov 2023 15:08:38 + with message-id and subject line Bug#1056396: fixed in orthanc-webviewer 2.8-4 has caused the Debian Bug report #1056396, regarding orthanc-webviewer: autopkgtest failure on !x86 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.) -- 1056396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056396 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: orthanc-webviewer Version: 2.8-3 Severity: serious https://tracker.debian.org/pkg/orthanc-webviewer Issues preventing migration: ∙ ∙ autopkgtest for orthanc-webviewer/2.8-3: amd64: Pass, arm64: Regression ♻ , armel: Regression ♻ , armhf: Regression ♻ , i386: Pass, ppc64el: Regression ♻ , s390x: Regression ♻ ... 75s autopkgtest [19:13:51]: test run-unit-test: [--- 75s cc1plus: error: ‘-fcf-protection=full’ is not supported for this target 75s autopkgtest [19:13:51]: test run-unit-test: ---] 76s autopkgtest [19:13:52]: test run-unit-test: - - - - - - - - - - results - - - - - - - - - - 76s run-unit-testFAIL non-zero exit status 1 -fcf-protection=full shouldn't be necessary in debian/tests/run-unit-test --- End Message --- --- Begin Message --- Source: orthanc-webviewer Source-Version: 2.8-4 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of orthanc-webviewer, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated orthanc-webviewer package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 23 Nov 2023 20:09:02 +0530 Source: orthanc-webviewer Architecture: source Version: 2.8-4 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Nilesh Patra Closes: 1056396 Changes: orthanc-webviewer (2.8-4) unstable; urgency=medium . * Team Upload. * Remove fcf-protection flag from autopkgtests (Closes: #1056396) Checksums-Sha1: c1412f2cec421353e9bdd332edcf429f00214d28 1849 orthanc-webviewer_2.8-4.dsc 205eab58731e5742e913669f4fb2f4cbee9b7435 255748 orthanc-webviewer_2.8-4.debian.tar.xz 499fa867e9ce4fa0e6ee1509ea4c2fd07ccf88e9 15976 orthanc-webviewer_2.8-4_source.buildinfo Checksums-Sha256: 2825e386d87e9d5a9c0fa4d41471f0eb1cc3c451add0dde8a3b2993f80d184c1 1849 orthanc-webviewer_2.8-4.dsc 7a2d0b42b80bf6c1a844588f733f8c04a8e9fb1f4d0a4ae9573aa7ecee3c03c7 255748 orthanc-webviewer_2.8-4.debian.tar.xz b91f0824108da1cda68990515613545ec90b171a8960a0088b665728644ea30c 15976 orthanc-webviewer_2.8-4_source.buildinfo Files: 81144121a286ba7aced389ae7f45c469 1849 science optional orthanc-webviewer_2.8-4.dsc aa49e68189f36fc1d755a46fba8e17eb 255748 science optional orthanc-webviewer_2.8-4.debian.tar.xz 02593e3cca147a4e058ac5c1c08647cd 15976 science optional orthanc-webviewer_2.8-4_source.buildinfo -BEGIN PGP SIGNATURE- iHUEARYIAB0WIQSglbZu4JAkvuai8HIqJ5BL1yQ+2gUCZV9lPwAKCRAqJ5BL1yQ+ 2rK2AP46fMkb62JeUusHUqdFVxsYRFYkCU48N2MYwypTdsr3LgEAyv9rqrK1a41q RK/dx/+6qUBJchWf/wGeuguMj8y1+w0= =TisL -END PGP SIGNATURE End Message ---
Bug#1056062: coq: FTBFS in sid (dune update?)
Hi, Le mercredi 22 novembre 2023 à 18:48 +0100, Gianfranco Costamagna a écrit : > control: tags -1 patch > > Hello, not sure why and how, but this upstream commit > fbe9e28b667e795a5ceb41bd7784bd2ea7ab10bf > > https://launchpadlibrarian.net/699029680/coq_8.17.0+dfsg-1build4_8.17.0+dfsg-1ubuntu1.diff.gz > > Subject: [PATCH] make-library-index: use mktemp, general cleanup > > This fixes the "sed: can't read tmp" error on my machine, not that I > understand why it happened. > > Looks fixing the issue > Good: that means the problem will be fixed when I'll be able to upload 8.18.0+dfsg-1 to unstable. control: fixed -1 8.18.0+dfsg-1 Thanks! J.Puydt
Bug#1056348: FTBFS: tests fail in clean environment
On Thu, Nov 23, 2023 at 09:20:37AM -0500, Nicolas Mora wrote: >Hello, > >On Tue, 21 Nov 2023 13:30:31 + Steve McIntyre wrote: >> Source: libssh2 >> Version: 1.9.0-2 >> Severity: serious >> Tags: ftbfs patch >> >> Hi! >> >> Building libssh2 using debuild in a clean local chroot, I get test >> failures and even a core dump! >> >Thanks for reporting the bug, although I have concerns on its scope. > >The package you have found the issue is the bullseye one, and the package >updates for oldstable are allowed mostly for security patches. > >Your bug is related to the test suite, and the patch won't change the binary >files in the package, so I assume the patch isn't going to be allowed for >proposed-updates. > >I've added the release team to ask for their opinion. > >Friends from the release team, do you have a feedback on this? Ah, apologies - that version is bogus, it's just the version on the bullseye machine I ran reportbug from. The tests are failing on current unstable source. -- Steve McIntyre, Cambridge, UK.st...@einval.com You lock the door And throw away the key There's someone in my head but it's not me
Bug#1056396: marked as pending in orthanc-webviewer
Control: tag -1 pending Hello, Bug #1056396 in orthanc-webviewer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/orthanc-webviewer/-/commit/3f4f676ecd7feae5da0e2d4e86f2acb15d8d6687 Remove fcf-protection flag from autopkgtests (Closes: #1056396) (this message was generated automatically) -- Greetings https://bugs.debian.org/1056396
Processed: Bug#1056396 marked as pending in orthanc-webviewer
Processing control commands: > tag -1 pending Bug #1056396 [src:orthanc-webviewer] orthanc-webviewer: autopkgtest failure on !x86 Added tag(s) pending. -- 1056396: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056396 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forwarded LLVM issues
Processing commands for cont...@bugs.debian.org: > forwarded 1056580 https://github.com/llvm/llvm-project/issues/73244 Bug #1056580 [src:llvm-toolchain-17] LLVM-17's autopkg tests fail (command1) Set Bug forwarded-to-address to 'https://github.com/llvm/llvm-project/issues/73244'. > forwarded 1056126 https://github.com/llvm/llvm-project/issues/73245 Bug #1056126 [libclang1-17] libclang1-17: libclang-17.so.1 uses wrong SONAME Set Bug forwarded-to-address to 'https://github.com/llvm/llvm-project/issues/73245'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1056126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056126 1056580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Tests disabled
Processing control commands: > severity 1039001 wishlist Bug #1039001 [src:hera] hera: Updating to version 2.0.0 Severity set to 'wishlist' from 'serious' -- 1039001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039001 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1039001: Tests disabled
Source: hera Version: 1.0.0+dfsg-2 Followup-For: Bug #1039001 Control: severity 1039001 wishlist Uploading catch2 v3 also made hera FTBFS (#1054686), and it is not clear whether the catch2 package will provide backwards-compatible headers (#1055237). Since updating hera is not entirely trivial, the fix for #1054686 was to temporarily disable tests. With tests disabled, I'm lowering the severity of this bug. signature.asc Description: PGP signature
Bug#1056348: FTBFS: tests fail in clean environment
Hello, On Tue, 21 Nov 2023 13:30:31 + Steve McIntyre wrote: Source: libssh2 Version: 1.9.0-2 Severity: serious Tags: ftbfs patch Hi! Building libssh2 using debuild in a clean local chroot, I get test failures and even a core dump! Thanks for reporting the bug, although I have concerns on its scope. The package you have found the issue is the bullseye one, and the package updates for oldstable are allowed mostly for security patches. Your bug is related to the test suite, and the patch won't change the binary files in the package, so I assume the patch isn't going to be allowed for proposed-updates. I've added the release team to ask for their opinion. Friends from the release team, do you have a feedback on this? /Nicolas
Bug#1054698: pixmap: FTBFS: ././Pixmap.c:1145:(.text+0xe631): undefined reference to `xpmReadRgbNames'
On Fri 27 Oct 2023, Lucas Nussbaum wrote: > Source: pixmap > Version: 2.6.6-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20231027 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > > /usr/bin/ld: Pixmap.o: in function `Initialize': > > ././Pixmap.c:1145:(.text+0xe631): undefined reference to `xpmReadRgbNames' > > collect2: error: ld returned 1 exit status I've traced this to commit 7f60f3428aa21d5d643eb75bfd9417cfabf48970 on libxpm: Explicitly mark non-static symbols as export or hidden Hides private API from external linkage Signed-off-by: Alan Coopersmith That commit marks those functions as hidden for some reason. I'm contacting the libxpm maintainers. Paul
Bug#1055778: libamtk-5-dev: Depends: gir1.2-amtk-5 (= 5.6.1-2) but 5.8.0-4 is to be installed
On 2023-11-23 08:43:16 -0500, Jeremy Bícha wrote: > On Sat, Nov 11, 2023 at 5:09 AM Sebastian Ramacher > wrote: > > Package: libamtk-5-dev > > Version: libamtk-5-dev > > Severity: serious > > Tags: sid trixie > > X-Debbugs-Cc: sramac...@debian.org > > > … > > The following packages have unmet dependencies: > > libamtk-5-dev : Depends: gir1.2-amtk-5 (= 5.6.1-2) but 5.8.0-4 is to be > > installed > > E: Unable to correct problems, you have held broken packages. > > > > > > gir1.2-amtk-5 has been taken over by libgedit-amtk. > > Sebastian, could you help hint this transition through? Affected > packages that need to get to Testing are gedit, gedit-plugins, > libgedit-amtk, and tepl. I imagine you may need to remove amtk from > Testing. Is amtk still useful? If not, please file a RM request for unstable against ftp.debian.org. Cheers -- Sebastian Ramacher
Bug#1056583: kaidan: FTBFS with disabled network
Source: kaidan Version: 0.9.1-2 Severity: serious Hello, the package FTBFS trying to call search.jabber.network, something forbidden by policy. 6: QWARN : GroupChatTest::test_GroupChatSearchManager_GroupChatModel() public-group-chat.search: Search request error: Host search.jabber.network not found 6: FAIL! : GroupChatTest::test_GroupChatSearchManager_GroupChatModel() 'spyError.isEmpty()' returned FALSE. () Full log available e.g. here: https://launchpadlibrarian.net/698369989/buildlog_ubuntu-noble-amd64.kaidan_0.9.1-2_BUILDING.txt.gz I think disabling that test function should work as workaround. G. OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1055778: libamtk-5-dev: Depends: gir1.2-amtk-5 (= 5.6.1-2) but 5.8.0-4 is to be installed
On Sat, Nov 11, 2023 at 5:09 AM Sebastian Ramacher wrote: > Package: libamtk-5-dev > Version: libamtk-5-dev > Severity: serious > Tags: sid trixie > X-Debbugs-Cc: sramac...@debian.org > … > The following packages have unmet dependencies: > libamtk-5-dev : Depends: gir1.2-amtk-5 (= 5.6.1-2) but 5.8.0-4 is to be > installed > E: Unable to correct problems, you have held broken packages. > > > gir1.2-amtk-5 has been taken over by libgedit-amtk. Sebastian, could you help hint this transition through? Affected packages that need to get to Testing are gedit, gedit-plugins, libgedit-amtk, and tepl. I imagine you may need to remove amtk from Testing. Thank you, Jeremy Bícha
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> unarchive 1053956
Bug #1053956 {Done: Paul Gevers } [src:alsa-lib]
src:alsa-lib: fails to migrate to testing for too long: unresolved RC bugs
Unarchived Bug 1053956
> block 1053956 by 1054896
Bug #1053956 {Done: Paul Gevers } [src:alsa-lib]
src:alsa-lib: fails to migrate to testing for too long: unresolved RC bugs
1053956 was blocked by: 1052720 1051901
1053956 was not blocking any bugs.
Added blocking bug(s) of 1053956: 1054896
> archive 1053956
Bug #1053956 {Done: Paul Gevers } [src:alsa-lib]
src:alsa-lib: fails to migrate to testing for too long: unresolved RC bugs
archived 1053956 to archive/56 (from 1053956)
> merge 1054896 1051901
Bug #1054896 [libasound2] libasound2: alsa 1.2.10-1 segfaults on i386
Bug #1051901 [libasound2] libasound2: 1.2.10 breaks ability to play audio using
i386 binaries on amd64 host
Merged 1051901 1054896
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1051901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051901
1053956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053956
1054896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054896
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1056312: marked as done (zlib1g makes tex-common fail to install due to fmtutil failing)
Your message dated Thu, 23 Nov 2023 13:21:26 + with message-id and subject line Bug#1056312: fixed in zlib 1:1.3.dfsg-3 has caused the Debian Bug report #1056312, regarding zlib1g makes tex-common fail to install due to fmtutil failing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1056312: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056312 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zlib1g Version: 1:1.3.dfsg-2 Severity: serious Hi, I didn't investigate this further yet but filing this as RC as it is easy to reproduce and it's easy to find out that only zlib1g changed using debbisect. Downgrading to zlib1g 1:1.2.13.dfsg-3 makes the problem go away. Steps to reproduce: $ mmdebstrap --include=tex-common,texlive-base unstable /dev/null Processing triggers for tex-common (6.18) ... Running updmap-sys. This may take some time... done. Running mktexlsr /var/lib/texmf ... done. Building format(s) --all. This may take some time... fmtutil failed. Output has been stored in /tmp/fmtutil.tcAsaQVq Please include this file if you report a bug. dpkg: error processing package tex-common (--configure): installed tex-common package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: tex-common E: Sub-process env returned an error code (1) --- End Message --- --- Begin Message --- Source: zlib Source-Version: 1:1.3.dfsg-3 Done: Mark Brown We believe that the bug you reported is fixed in the latest version of zlib, 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 1056...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mark Brown (supplier of updated zlib 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: Thu, 23 Nov 2023 13:02:20 + Source: zlib Architecture: source Version: 1:1.3.dfsg-3 Distribution: unstable Urgency: low Maintainer: Mark Brown Changed-By: Mark Brown Closes: 1056312 Changes: zlib (1:1.3.dfsg-3) unstable; urgency=low . * Update the version of texlive-binaries we break since they still had broken version checks (closes: #1056312). Checksums-Sha1: 625231c3542253e2ebb192682cdbb8ddfda8f6ca 2547 zlib_1.3.dfsg-3.dsc d143c3cf5028810be600a74e0216c98128255c47 17308 zlib_1.3.dfsg-3.debian.tar.xz 0005039cd21aa53df22756a1ba453054c3ebee84 9104 zlib_1.3.dfsg-3_amd64.buildinfo Checksums-Sha256: ff17bb7134b314999d3a205a056cb39235f18636253b4e39703c0d9bbbaa377b 2547 zlib_1.3.dfsg-3.dsc 3fab93040e86f3f980f90b03687a60c6aad097122e19d055aa8a3df58511e4eb 17308 zlib_1.3.dfsg-3.debian.tar.xz 38893f7e67e123246750d1d42abf015a257e23dfb2aa249503a86610f64e3b29 9104 zlib_1.3.dfsg-3_amd64.buildinfo Files: 3b823f6aa4aaeaae61d17d6f9bfdcd14 2547 libs optional zlib_1.3.dfsg-3.dsc a9652b2780769de92b1007b837ecaca6 17308 libs optional zlib_1.3.dfsg-3.debian.tar.xz 25660385d2dc503abe8c02eee3dd4b6f 9104 libs optional zlib_1.3.dfsg-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQFHBAEBCgAxFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmVfTf0THGJyb29uaWVA ZGViaWFuLm9yZwAKCRAk1otyXVSH0BkAB/9ap8jUUvND9TfLUqXiY+seIIg3G9wn 9za+2P/4npAL6FXi0lom278cVfOAmHyvxWS0wceS+4I8exUjAQOYgUYaQnujz1kD Uc5QxAXYkIRnYXuUjBCVFY8eSzJaf2kJ49itCL/Laed4JlWwrBw+A1m2DOttVql3 NkmYgZUJvX8O88diA/1deDQ9JCwAHh0B8o7B8wgCBM7NokcKcGNVUrJ0wofyyWw8 S+lhI3aTg01JohXJcOCXdtX2yYv+KZ84jh5SQuxCmnrm7xxtBj4WqY+J7xTCbvNz /3LCe/Fz6Q/YZ/il9tzUEMgiRWcWkNuJ+XYRQkruDd/cSJYZrk/6+a+F =9Ipt -END PGP SIGNATURE End Message ---
Processed (with 2 errors): your mail
Processing commands for cont...@bugs.debian.org: > block 1053956 by 1054896 Failed to set blocking bugs of 1053956: Not altering archived bugs; see unarchive. > merge 1054896 1051901 Bug #1054896 [libasound2] libasound2: alsa 1.2.10-1 segfaults on i386 Unable to merge bugs because: blocks of #1051901 is '1053956' not '' Failed to merge 1054896: Did not alter merged bugs. > End of message, stopping processing here. Please contact me if you need assistance. -- 1051901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051901 1054896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): your mail
Processing commands for cont...@bugs.debian.org: > block 1054896 by 1053956 Bug #1054896 [libasound2] libasound2: alsa 1.2.10-1 segfaults on i386 No valid blocking bug(s) given; not doing anything Failed to set blocking bugs of 1054896: Unknown/archived blocking bug(s):1053956. > merge 1054896 1051901 Bug #1054896 [libasound2] libasound2: alsa 1.2.10-1 segfaults on i386 Unable to merge bugs because: blocks of #1051901 is '1053956' not '' Failed to merge 1054896: Did not alter merged bugs. > End of message, stopping processing here. Please contact me if you need assistance. -- 1051901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051901 1054896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): your mail
Processing commands for cont...@bugs.debian.org: > severity 1054896 serious Bug #1054896 [libasound2] libasound2: alsa 1.2.10-1 segfaults on i386 Severity set to 'serious' from 'grave' > block 1054896 1053956 Unknown command or malformed arguments to command. > merge 1054896 1051901 Bug #1054896 [libasound2] libasound2: alsa 1.2.10-1 segfaults on i386 Unable to merge bugs because: blocks of #1051901 is '1053956' not '' Failed to merge 1054896: Did not alter merged bugs. > End of message, stopping processing here. Please contact me if you need assistance. -- 1051901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051901 1054896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 2 errors): your mail
Processing commands for cont...@bugs.debian.org: > severity serious 1054896 Unknown command or malformed arguments to command. > tags 1054896 fixed-upstream upstream Bug #1054896 [libasound2] libasound2: alsa 1.2.10-1 segfaults on i386 Added tag(s) fixed-upstream and upstream. > forwarded 1054896 https://github.com/alsa-project/alsa-lib/issues/352 Bug #1054896 [libasound2] libasound2: alsa 1.2.10-1 segfaults on i386 Set Bug forwarded-to-address to 'https://github.com/alsa-project/alsa-lib/issues/352'. > merge 1054896 1051901 Bug #1054896 [libasound2] libasound2: alsa 1.2.10-1 segfaults on i386 Unable to merge bugs because: severity of #1051901 is 'serious' not 'grave' blocks of #1051901 is '1053956' not '' Failed to merge 1054896: Did not alter merged bugs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1051901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051901 1054896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056580: LLVM-17's autopkg tests fail (command1)
Package: src:llvm-toolchain-17 Version: 1:17.0.5-1 Severity: serious Tags: sid trixie [...] 231s clang++-$VERSION -std=c++14 -stdlib=libc++ foo.cpp -lc++experimental -o o 233s /usr/bin/ld: cannot find -lc++experimental: No such file or directory 233s clang++-17: error: linker command failed with exit code 1 (use -v to see invocation) 16 used to pass one more -L flag, 17 is missing that: @@ -17,7 +17,6 @@ -L/lib/../lib64 -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib64 --L/usr/lib/llvm-16/bin/../lib -L/lib -L/usr/lib foo.o
Bug#1056238: gcc-13: FTBFS on mips64el: E: Build killed with signal TERM after 150 minutes of inactivity
On 2023-11-23 12:22:05 +0100, Matthias Klose wrote: > Control: tags -1 + moreinfo > > I'm not looking into that, CCing the ports maintainers. Sure, we can > disable running the tests on mips64el. It used to be no problem while the faster mips64el buildds were available. But currently we only have the slow ones, where the tests timeout. Best Sebastian > > On 19.11.23 11:18, Sebastian Ramacher wrote: > > Source: gcc-13 > > Version: 13.2.0-6 > > 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=gcc-13=mips64el=13.2.0-6=1700351970=0 > > > > === libstdc++ Summary for unix === > > > > # of expected passes3886 > > # of expected failures 43 > > # of unsupported tests 139 > > Running target unix/-fstack-protector > > Using /usr/share/dejagnu/baseboards/unix.exp as board description file for > > target. > > Using /usr/share/dejagnu/config/unix.exp as generic interface file for > > target. > > Using /<>/src/libstdc++-v3/testsuite/config/default.exp as > > tool-and-target-specific interface file. > > Running /<>/src/libstdc++-v3/testsuite/libstdc++-abi/abi.exp > > ... > > Running > > /<>/src/libstdc++-v3/testsuite/libstdc++-prettyprinters/prettyprinters.exp > > ... > > FAIL: libstdc++-abi/abi_check > > Running > > /<>/src/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ... > > Running > > /<>/src/libstdc++-v3/testsuite/libstdc++-xmethods/xmethods.exp > > ... > > > > === libstdc++ Summary for unix === > > > > # of expected passes158 > > # of unexpected failures1 > > # of unresolved testcases 1 > > Running target unix/-fstack-protector > > Using /usr/share/dejagnu/baseboards/unix.exp as board description file for > > target. > > Using /usr/share/dejagnu/config/unix.exp as generic interface file for > > target. > > Using /<>/src/libstdc++-v3/testsuite/config/default.exp as > > tool-and-target-specific interface file. > > Running /<>/src/libstdc++-v3/testsuite/libstdc++-abi/abi.exp > > ... > > Running > > /<>/src/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ... > > Running > > /<>/src/libstdc++-v3/testsuite/libstdc++-prettyprinters/prettyprinters.exp > > ... > > Running > > /<>/src/libstdc++-v3/testsuite/libstdc++-xmethods/xmethods.exp > > ... > > > > === libstdc++ Summary for unix === > > > > # of expected passes3689 > > # of unexpected failures1 > > # of expected failures 37 > > # of unsupported tests 186 > > Running target unix/-fstack-protector > > Using /usr/share/dejagnu/baseboards/unix.exp as board description file for > > target. > > Using /usr/share/dejagnu/config/unix.exp as generic interface file for > > target. > > Using /<>/src/libstdc++-v3/testsuite/config/default.exp as > > tool-and-target-specific interface file. > > Running /<>/src/libstdc++-v3/testsuite/libstdc++-abi/abi.exp > > ... > > Running > > /<>/src/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ... > > > > testsuite still running ... > > > > E: Build killed with signal TERM after 150 minutes of inactivity > > > > > > Cheers > -- Sebastian Ramacher
Bug#1055669: marked as done (bcftools: test_vcf_merge failures on armhf: Bus error)
Your message dated Thu, 23 Nov 2023 11:49:03 + with message-id and subject line Bug#1055669: fixed in bcftools 1.18-2 has caused the Debian Bug report #1055669, regarding bcftools: test_vcf_merge failures on armhf: Bus error 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.) -- 1055669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055669 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bcftools Version: 1.18-1 Severity: serious Tags: ftbfs Justification: ftbfs Control: forwarded -1 https://github.com/samtools/bcftools/issues/2036 Dear Maintainer, bcftools currently ftbfs on armhf due to multiple test_vcf_merge failures with Bus error[1]. I already informed upstream[2]. This bug is mostly to keep track of the issue on Debian side and eventually comment on possible Debian specific workarounds. For the context, there are 44 failure looking typically like: test_vcf_merge: /<>/bcftools merge --no-version -Ob --force-samples -0 /tmp/YVqRgiAYOP/merge.a.vcf.gz /tmp/YVqRgiAYOP/merge.b.vcf.gz /tmp/YVqRgiAYOP/merge.c.vcf.gz | /<>/bcftools view --no-version | grep -v ^##bcftools_ Non-zero status 1 Failed to read from standard input: unknown file type .. failed ... [1]: https://buildd.debian.org/status/fetch.php?pkg=bcftools=armhf=1.18-1=1699434189=1 [2]: https://github.com/samtools/bcftools/issues/2036 For information, -- .''`. Étienne Mollier : :' : gpg: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/2, please excuse my verbosity `-on air: Silent Voices - Humancradlegrave signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: bcftools Source-Version: 1.18-2 Done: Étienne Mollier We believe that the bug you reported is fixed in the latest version of bcftools, 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 1055...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Étienne Mollier (supplier of updated bcftools 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: Thu, 23 Nov 2023 12:01:34 +0100 Source: bcftools Architecture: source Version: 1.18-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Étienne Mollier Closes: 1055669 Changes: bcftools (1.18-2) unstable; urgency=medium . * skip_new_test_failing_on_32bit.patch: refresh. * tests-pluginpath.patch: refresh. * fix-bus-error-armhf.patch: new: fix Bus errors. Thanks to Rob Davies (Closes: #1055669) Checksums-Sha1: 3c16a6e336b49e7664b3bb2cdafa7609eb938dc7 2270 bcftools_1.18-2.dsc 0b9ed4789b2084ebb7605702f8923b0cd0b5c860 11828 bcftools_1.18-2.debian.tar.xz Checksums-Sha256: 997d592c4148c573a57dbb81ebac64d73b1a444d2eb4ea126abf00292fb0cbab 2270 bcftools_1.18-2.dsc 400f5f1fb6597fa5f30763df21aca026b026284f3610308c0fe53ae328d9e187 11828 bcftools_1.18-2.debian.tar.xz Files: f66b80c253c2f150a5b426869365fb36 2270 science optional bcftools_1.18-2.dsc bd8588e544280dde67a99335ec9e9c54 11828 science optional bcftools_1.18-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmVfN4kUHGVtb2xsaWVy QGRlYmlhbi5vcmcACgkQeTz2fo8NEdqi8RAAgiuGgES2JKfEVeTz4WDN13sBcS/a ZlGVD59akFubxJ9hdXSLMF7mOfkg0A1jde0N+g5Yx8nDJU8S6b6OEOrC05Q3AyuV b6N3+KJMinJv6+N4FXU569u6tNmVbdURXkbU8HOmETDrEOQ7rM/hyhbmSW//uODg 43mZBR0bzIJmUCoZfpfgbtJnYqWomlFwga3q17Ttx6mPxluKNngQYYehXyUEOCje COGPC0XPmwb8rEgnBw0CLJtnnfzMb0j/lZXtAkg/6EAiAUx8SlCHoco5jefyTxVX gf5gwqXaqjJseBk8TpOCHn3p42Bam1Bl28IHb1iZvpLUgQZy2Jqo08F1CDFxf0vd 05Id5LiAwRUd4948l6ZQQkBpwqHUJqsq7mC8Ux630jmaV1Blc6728DOivRntC9VV qMLQFHlXucdX4VZWLHKj51XROVHe4VNJyqz5Qhq89N7aiI5d1tAIs2q7rg2eUu6d S6beUdJWIp/sJlm6e/bfRGBKEOQod6vT6/hxJhiJBnPO+21SAW4L6s10Uw3AzWup M0v+7mNcwxX+Y7V83/GK2Pof1atGTr6AbQ0KvWhoTXCWCibybgtITQBIZHX5cO4e rgZXJI7ok+eJtyhLx7DML+nZuq+0BbnRDwWIfhHy3CY0wT+1UJgFWOfBK/lzdnHt 0gEBI80xt09JUpw= =yQV3 -END PGP SIGNATURE End Message ---
Bug#1041838: marked as done (libclang-rt-17-dev: undeclared file conflict with libclang-rt-17-dev-wasm{32,64} on /usr/lib/llvm-17/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm*.a)
Your message dated Thu, 23 Nov 2023 12:37:43 +0100
with message-id
and subject line fixed for LLVM 17
has caused the Debian Bug report #1041838,
regarding libclang-rt-17-dev: undeclared file conflict with
libclang-rt-17-dev-wasm{32,64} on
/usr/lib/llvm-17/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm*.a
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.)
--
1041838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libclang-rt-16-dev
Version: 1:16.0.6-5
Severity: serious
libclang-rt-16-dev installs
/usr/lib/llvm-16/lib/clang/16/lib/wasi/libclang_rt.builtins-wasm{32,64}.a,
which are also installed by libclang-rt-16-dev-wasm{32,64} respectively.
Trying to coinstall these packages in unstable results in an unpack
error. I guess that these files should only be contained in the
respective wasm packages. Don't forget to include the necessary
Breaks+Replaces when fixing this.
Helmut
--- End Message ---
--- Begin Message ---
this is fixed:
$ dpkg -L libclang-rt-17-dev|grep -c wasi
0--- End Message ---
Bug#1041838: fixed for LLVM 17
this is fixed: $ dpkg -L libclang-rt-17-dev|grep -c wasi 0
Processed: Re: Bug#1056238: gcc-13: FTBFS on mips64el: E: Build killed with signal TERM after 150 minutes of inactivity
Processing control commands: > tags -1 + moreinfo Bug #1056238 [src:gcc-13] gcc-13: FTBFS on mips64el: E: Build killed with signal TERM after 150 minutes of inactivity Added tag(s) moreinfo. -- 1056238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056238 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1056238: gcc-13: FTBFS on mips64el: E: Build killed with signal TERM after 150 minutes of inactivity
Control: tags -1 + moreinfo I'm not looking into that, CCing the ports maintainers. Sure, we can disable running the tests on mips64el. On 19.11.23 11:18, Sebastian Ramacher wrote: Source: gcc-13 Version: 13.2.0-6 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=gcc-13=mips64el=13.2.0-6=1700351970=0 === libstdc++ Summary for unix === # of expected passes3886 # of expected failures 43 # of unsupported tests 139 Running target unix/-fstack-protector Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /<>/src/libstdc++-v3/testsuite/config/default.exp as tool-and-target-specific interface file. Running /<>/src/libstdc++-v3/testsuite/libstdc++-abi/abi.exp ... Running /<>/src/libstdc++-v3/testsuite/libstdc++-prettyprinters/prettyprinters.exp ... FAIL: libstdc++-abi/abi_check Running /<>/src/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ... Running /<>/src/libstdc++-v3/testsuite/libstdc++-xmethods/xmethods.exp ... === libstdc++ Summary for unix === # of expected passes158 # of unexpected failures1 # of unresolved testcases 1 Running target unix/-fstack-protector Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /<>/src/libstdc++-v3/testsuite/config/default.exp as tool-and-target-specific interface file. Running /<>/src/libstdc++-v3/testsuite/libstdc++-abi/abi.exp ... Running /<>/src/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ... Running /<>/src/libstdc++-v3/testsuite/libstdc++-prettyprinters/prettyprinters.exp ... Running /<>/src/libstdc++-v3/testsuite/libstdc++-xmethods/xmethods.exp ... === libstdc++ Summary for unix === # of expected passes3689 # of unexpected failures1 # of expected failures 37 # of unsupported tests 186 Running target unix/-fstack-protector Using /usr/share/dejagnu/baseboards/unix.exp as board description file for target. Using /usr/share/dejagnu/config/unix.exp as generic interface file for target. Using /<>/src/libstdc++-v3/testsuite/config/default.exp as tool-and-target-specific interface file. Running /<>/src/libstdc++-v3/testsuite/libstdc++-abi/abi.exp ... Running /<>/src/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ... testsuite still running ... E: Build killed with signal TERM after 150 minutes of inactivity Cheers
Processed: Bug#1055669 marked as pending in bcftools
Processing control commands: > tag -1 pending Bug #1055669 [src:bcftools] bcftools: test_vcf_merge failures on armhf: Bus error Added tag(s) pending. -- 1055669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055669 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1055669: marked as pending in bcftools
Control: tag -1 pending Hello, Bug #1055669 in bcftools reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/bcftools/-/commit/cc9b561acb4c6f577954b5534857f42674e7e361 fix-bus-error-armhf.patch: new: fix Bus errors. Thanks: Rob Davies Closes: #1055669 (this message was generated automatically) -- Greetings https://bugs.debian.org/1055669
Bug#1056569: marked as done (libbrotli-dev: libbrotlidec.a corrupted due to c-p error in 0001-build-static-libraries-by-default.patch)
Your message dated Thu, 23 Nov 2023 10:49:01 +
with message-id
and subject line Bug#1056569: fixed in brotli 1.1.0-2
has caused the Debian Bug report #1056569,
regarding libbrotli-dev: libbrotlidec.a corrupted due to c-p error in
0001-build-static-libraries-by-default.patch
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.)
--
1056569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056569
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbrotli-dev
Version: 1.1.0-1
Severity: normal
Dear Maintainer,
libbrotlidec.a is unusable in brotli 1.1.0-1 since it is identical to
libbrotlicommon.a
This happened because patch 0001-build-static-libraries-by-default.patch seems
to contain
a copy paste error:
+add_library(brotlicommon-static STATIC ${BROTLI_COMMON_SOURCES})
+add_library(brotlidec-static STATIC ${BROTLI_COMMON_SOURCES})
+add_library(brotlienc-static STATIC ${BROTLI_ENC_SOURCES})
I rebuild the package with the line of brotlidec-static changed to
BROTLI_DEC_SOURCES
and the library is usable again.
I caught the problem because I tried to link libfreetype statically
which required libbrotlidec.a
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-4-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 libbrotli-dev depends on:
ii libbrotli1 1.1.0-1
libbrotli-dev recommends no packages.
libbrotli-dev suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: brotli
Source-Version: 1.1.0-2
Done: Gianfranco Costamagna
We believe that the bug you reported is fixed in the latest version of
brotli, 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 1056...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Gianfranco Costamagna (supplier of updated brotli
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Thu, 23 Nov 2023 11:41:29 +0100
Source: brotli
Built-For-Profiles: noudeb
Architecture: source
Version: 1.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Tomasz Buchert
Changed-By: Gianfranco Costamagna
Closes: 1056569
Changes:
brotli (1.1.0-2) unstable; urgency=medium
.
* Team upload
* Fixup patch to build static libraries, this should
fix freetype autopkgtests errors (Closes: #1056569).
Thanks Philipp Wolski for the patch
Checksums-Sha1:
945cc97a14ad1f3355fe0dda327c0b0db0cb3047 2261 brotli_1.1.0-2.dsc
4cad3b75c791652657abb6ea166f1f8817afbb1a 5480 brotli_1.1.0-2.debian.tar.xz
a0c6bad39b5b33258934ffa3e3a3eec1c5ebe8f9 9835 brotli_1.1.0-2_source.buildinfo
Checksums-Sha256:
39b06802a852629132d549a7f7449dee7f435e801706714a4bc2ea2f15b28f36 2261
brotli_1.1.0-2.dsc
3d913a3740bcad9a294007575a6beb1846beadbd62b44fb2bf9fdaeddea3236f 5480
brotli_1.1.0-2.debian.tar.xz
f091b404edc3873d6829980326759092e598e26aef8115d6cc5bfb2473929486 9835
brotli_1.1.0-2_source.buildinfo
Files:
6a7dcebce6d0dbcffca27fe4a1fbb2e7 2261 python optional brotli_1.1.0-2.dsc
9eb311aaa7e3b17f900913645b43806d 5480 python optional
brotli_1.1.0-2.debian.tar.xz
1ce6d7bb1163cd17c39e471a7acbec1e 9835 python optional
brotli_1.1.0-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmVfLIYACgkQ808JdE6f
XdlwTw//e/vO5tfbZSg4FmJrKJpOaG4iBdzcUeS0UmUG1+B85i99tQbOIozozF62
mfjRJdsEB0FMJ+1AQHoFeFVwr9UQ9crxx6carlAZPRoqHwm5tMzzBeDwJD5BSKhU
PyQk/jZcrXX8qm/eF3bGxzWWCI/HAnzILZtBhLW1GaSa/b5MNM4HnR3cGhmnu4cZ
jueyiqeVN8OjVoLc0aY5OI+MXv+rIQRiyaNnK8AX9FQ+QoJNjWUvOan/ntXjW0BS
elplqMgwxWLpPMhzwfvuVGF/MAW6+IvWqTwi/uaI7QLpdNbwYMNUJEdwNOx0pTrh
nXrRToyM1APpUaqxA0EjEvOIOTqwmw7eLFbBqSLyjLHh3Uh0zEgU0AiQmyQ5e26Y
drp73RDrvaPMDKnxMhKH92sQ8zkHua428Cu2M1DPWZ7S3Y4C4Ult01qvOom4Atz8
waoxkV8akjAuR8NZy/aGoxjrdRUcsnO0CeUIjl7scKER0jp7xCnEVuPQ+7dHO2EO
1zEjCCQ9TRZ+TsruuicHF2rwwW0q99vXAqy8kKKF5qLAWadmMyAklDA5zATelpZP
Processed: Re: libbrotli-dev: libbrotlidec.a corrupted due to c-p error in 0001-build-static-libraries-by-default.patch
Processing control commands: > severity -1 serious Bug #1056569 [libbrotli-dev] libbrotli-dev: libbrotlidec.a corrupted due to c-p error in 0001-build-static-libraries-by-default.patch Severity set to 'serious' from 'normal' > tags -1 patch pending Bug #1056569 [libbrotli-dev] libbrotli-dev: libbrotlidec.a corrupted due to c-p error in 0001-build-static-libraries-by-default.patch Added tag(s) pending and patch. -- 1056569: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056569 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1050236: FTBFS: 30 - testlpe fails
Hi. Two notes: 1) This doesn't just fail on rscv64 but also on amd64 and i386 with the same error as in the linked build log from the original report: [...] [ RUN ] LPETest.MeasureSegments_multi_px_1_0_2 add_actions_edit_document: no app! add_actions_pages: no app! add_actions_undo: no app! ./testfiles/lpespaths-test.h:96: Failure The difference between pointc[Geom::X] and pointd[Geom::X] is 1.40444821, which exceeds precission, where pointc[Geom::X] evaluates to 297.9448959997, pointd[Geom::X] evaluates to 299.3493439997, and precission evaluates to 1.3999. ./testfiles/lpespaths-test.h:97: Failure The difference between pointc[Geom::Y] and pointd[Geom::Y] is 1.53307541, which exceeds precission, where pointc[Geom::Y] evaluates to 295.8470760002, pointd[Geom::Y] evaluates to 297.3801520001, and precission evaluates to 1.3999. ./testfiles/lpespaths-test.h:96: Failure [...] [ FAILED ] LPETest.MeasureSegments_multi_px_1_0_2 [ FAILED ] LPETest.MeasureSegments_multi_mm_1_0_2 2) If I'm not mistaken, that means that the "forwarded" tag is wrong here (or at least the linked issue is: This is not segfaulting (like the "forwarded" bug) but erroring out on imprecise measurements. If I recall correctly, there is a separate issue on github about this, somehow related to font rendering(?). However, I can't seem to find it anymore. Kind regards, Sven
Bug#1050066: marked as done (adequate: autopkgtest fails on !amd64)
Your message dated Thu, 23 Nov 2023 09:33:57 + with message-id and subject line Bug#1050066: fixed in adequate 0.15.9 has caused the Debian Bug report #1050066, regarding adequate: autopkgtest fails on !amd64 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.) -- 1050066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1050066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: adequate Version: 0.15.7 Severity: serious User: debian...@lists.debian.org Usertags: fails-always Dear maintainer(s), Your package has an autopkgtest, great. However, it fails on all architectures but amd64. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this report. The release team has announced [1] that failing autopkgtest on amd64 and arm64 are considered RC in testing. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://lists.debian.org/debian-devel-announce/2019/07/msg2.html https://ci.debian.net/data/autopkgtest/testing/arm64/a/adequate/36619533/log.gz 65s check adequate-testpkg-symbol-size-mismatch ... FAIL 65s -adequate-testpkg-symbol-size-mismatch: symbol-size-mismatch /usr/bin/adequate-test-symsize => this_symbol_size_varies OpenPGP_signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: adequate Source-Version: 0.15.9 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of adequate, 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 1050...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated adequate package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 23 Nov 2023 10:06:17 +0100 Source: adequate Architecture: source Version: 0.15.9 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 1050066 Changes: adequate (0.15.9) unstable; urgency=medium . * QA upload. * Skip symbol-size-mismatch test on architectures where array symbols don't include a specific length. (Closes: #1050066) Checksums-Sha1: b0dc95749c38a76ed9195bc0f52c457817ef176c 1734 adequate_0.15.9.dsc ae1d2f64403f90cd291e389aa580262782fa8020 27812 adequate_0.15.9.tar.xz 23b2fffefe468057f4980b15998608743be56925 6095 adequate_0.15.9_source.buildinfo Checksums-Sha256: 01ade04986f788e7980964ff0f34c0219f5ef33a3a467b54800d13cf26beb4da 1734 adequate_0.15.9.dsc 906e94b55e8a9cb30b8e899f2e534c48e9f59582f01836b47c11e1e9ca058456 27812 adequate_0.15.9.tar.xz d688a74c74e935eed61ce13f7c90176d2465d7a212b6f36c38f8f209f4ffe57b 6095 adequate_0.15.9_source.buildinfo Files: 712f772a131ccfb06211af0fff103ea2 1734 utils optional adequate_0.15.9.dsc 28f61d1e3d20b5a2965cda8318664c16 27812 utils optional adequate_0.15.9.tar.xz f300608ffee656980973fa2981b66877 6095 utils optional adequate_0.15.9_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmVfFqkQHGFuYmVAZGVi aWFuLm9yZwAKCRBfsz+TWentCFcEEACAXcCVYBXsN83nsiSqAc+bhC4nVedyM+Ps 35HwDPTQP/LuJtMdSjJgPaUCek7WKNut8vSjE06ePjdG6r4kpo9AogAa4US1k7rL Wr5t81MlbynQpae62y7PIFa0ToKFgkaoOie/pNVr3aJ7258k42J2Nc9nmTPJiEZR scp0eQuNmbybAcDUNrAGwIex6BroJM0Zs6nAuPyFLlhz9ARM5c4TPE7pdJNiRm0h qxMHWfUxA+d+8RfRn7R18LKl2JcN9X9OC01sQ8vHFt4NDeGXUJLbLnsheUi5fw0W 4DTt+DJC8Vds2yFmu8TYMsm5WPZk9aQqHF4BCOTwDu+nUAGz91qZ43vTHfnoAEaJ /+fJYf1xeiGP7AltzTJ237E4KqNcEFDj3iYxT7GUtzPqIOhDITy0ZjfVria/L0Hg 9mtblKnu5P8FoktggfKuw0sTMbqg/+Eq+s6gl+I5Un3BLvzzWJ1LaKBNlhxk/QER jJUyWuqxSpd2d5bRYFCLmCNMGTjB0MFMpApjCpPDwbE3HxtPpytB6h6OwDdBv5IH PiKZOZZlKtSWT9fhY7PGuI2NjfRk6bhs/Miw5ZD7VMOKOY1Oo2AmhhUCE1H/X3ku n3M4J6hjsMBkz6Ysv+lWI6+4qYpvVIjzLE/TQjGZ8aE0y41jeOkUIcW9kuuqT7fL RRnLlwuH2g== =s9f5 -END PGP SIGNATURE End Message ---
Bug#1042298: marked as done (node-wikibase-cli: FTBFS: TypeError: Cannot read properties of undefined (reading 'Q11'))
Your message dated Thu, 23 Nov 2023 09:19:05 + with message-id and subject line Bug#1042298: fixed in node-wikibase-cli 15.15.4-5 has caused the Debian Bug report #1042298, regarding node-wikibase-cli: FTBFS: TypeError: Cannot read properties of undefined (reading 'Q11') 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.) -- 1042298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042298 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-wikibase-cli Version: 15.15.4-4 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie 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 >dh_auto_test --buildsystem=nodejs > mkdir -p node_modules > ln -s ../. node_modules/wikibase-cli > /bin/sh -ex debian/tests/pkg-js/test > + http_proxy=127.0.0.1 https_proxy=127.0.0.1 mocha --exit test/general.js > test/wb-aliases.js test/wb-claims.js test/wb-config.js test/wb-convert.js > test/wb-create-entity.js test/wb-data.js test/wb-description.js > test/wb-generate-template.js test/wb-hub.js test/wb-id.js test/wb-label.js > test/wb-lang.js test/wb-lemma.js test/wb-open.js test/wb-query.js > test/wb-revisions.js test/wb-search.js test/wb-sparql.js test/wb-summary.js > > > general > 1) should allow to customize the instance > undefined should accept options before arguments (1025ms) > dry mode > undefined should not require credentials (516ms) > > wb aliases > undefined should display help (486ms) > undefined (763ms) > undefined should be tolerant on input (751ms) > > wb claims > undefined should display help when requested without argument (423ms) > undefined should display all entity claims when passed an entity id > (2164ms) > undefined shoud display property claims when passed and entity id and a > property id (788ms) > undefined should filters properties from text (1255ms) > undefined should find the GUID of a claim when provided a value (789ms) > > wb config > undefined should display config (425ms) > undefined should display help (442ms) > > wb convert > undefined should convert external ids (669ms) > undefined should convert external ids passed on stdin (657ms) > undefined should convert Wikidata ids (671ms) > undefined should convert external ids that look like Wikidata ids (614ms) > > wb edit-entity > undefined should show the command help menu when called without argument > (526ms) > undefined should show the help menu for the requested template (1580ms) > > wb data > undefined (1285ms) > undefined should accept several ids (1499ms) > undefined should output entities as ndjson (1336ms) > undefined should simplify entity when requested (1210ms) > undefined should simplify entities when requested (1228ms) > undefined should return only the desired props when requested (1190ms) > - should support lexemes > undefined should accept ids on stdin (1200ms) > undefined should return ttl when requested (882ms) > undefined should fetch a specific revision (1027ms) > undefined should simplify a specific revision (837ms) > undefined should return entities schema text (940ms) > property claims data > undefined should get property claims data provided a property claims id > (983ms) > claim data > undefined should get a claim data provided a claim guid (1061ms) > undefined should accept prefixed claim GUIDs (1044ms) > undefined should accept claim GUIDs with an - in place of a $ (1070ms) > undefined should get a simplified claim (1097ms) > undefined should keep the requested simplified claim data (967ms) > undefined should use specified time-converter (1042ms) > > wb description > undefined should display help (445ms) > undefined (655ms) > undefined should be tolerant on input (655ms) > > wb generate-template > undefined should generate a template from an item id (1194ms) > > wb hub > undefined should display help (436ms) > > wb id > undefined display help (425ms) > undefined should accept a Wikipedia article title (1077ms) > undefined should accept a sitelink URL (941ms) >
Bug#1054729: errbot: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13
Dear Maintainer, After moving conftest.py from package root to tests/ (as upstream did), your package builds fine in a sid chroot environment and all tests pass as well. Kind Regards
