Bug#1010554: marked as done (orthanc: FTBFS with dcmtk >= 3.6.7)
Your message dated Thu, 05 May 2022 05:49:17 +
with message-id
and subject line Bug#1010554: fixed in orthanc 1.10.1+dfsg-2
has caused the Debian Bug report #1010554,
regarding orthanc: FTBFS with dcmtk >= 3.6.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.)
--
1010554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010554
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: orthanc
Version: 1.10.1+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: jo...@debian.org, ma...@debian.org
Hi,
orthanc FTBFS with dcmtk 3.6.7 from unstable:
/<>/OrthancFramework/Sources/DicomNetworking/Internals/DicomTls.cpp:110:118:
error: ‘TCS_ok’ was
not declared in this scope
110 | if
(tls->addTrustedCertificateFile(trustedCertificatesPath.c_str(),
DCF_Filetype_PEM /*opt_keyFi
leFormat*/) != TCS_ok)
|
^~
/<>/OrthancFramework/Sources/DicomNetworking/Internals/DicomTls.cpp:116:104:
error: ‘TCS_ok’ was
not declared in this scope
116 | if (tls->setPrivateKeyFile(ownPrivateKeyPath.c_str(),
DCF_Filetype_PEM /*opt_keyFileFormat*/) !=
TCS_ok)
|
^~
/<>/OrthancFramework/Sources/DicomNetworking/Internals/DicomTls.cpp:122:106:
error: ‘TCS_ok’ was
not declared in this scope
122 | if (tls->setCertificateFile(ownCertificatePath.c_str(),
DCF_Filetype_PEM /*opt_keyFileFormat*/)
!= TCS_ok)
|
^~
/<>/OrthancFramework/Sources/DicomNetworking/Internals/DicomTls.cpp:135:72:
error: ‘TCS_ok’ was n
ot declared in this scope
135 | if (tls->setTLSProfile(TSP_Profile_BCP195 /*opt_tlsProfile*/) !=
TCS_ok)
|
^~
/<>/OrthancFramework/Sources/DicomNetworking/Internals/DicomTls.cpp:140:36:
error: could not convert ‘DcmTLSTransportLayer::activateCipherSuites()()’ from
‘OFCondition’ to ‘bool’
140 | if (tls->activateCipherSuites())
| ~^~
||
|OFCondition
make[4]: *** [CMakeFiles/OrthancFramework.dir/build.make:1941:
CMakeFiles/OrthancFramework.dir/<>/OrthancFramework/Sources/DicomNetworking/Internals/DicomTls.cpp.o]
Error 1
The attached debdiff fixes above problem but the testsuite still fails with:
[100%] Linking CXX executable UnitTests
/usr/bin/ld:
/usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libdcmdata.so:
undefined reference to symbol 'inflateEnd'
/usr/bin/ld: /lib/x86_64-linux-gnu/libz.so.1: error adding symbols: DSO missing
from command line
collect2: error: ld returned 1 exit status
Maybe this has to be fixed in dcmtk but I'm not sure. Because my patch
is not complete I'm not tagging this bug with patch.
Thanks!
cheers, josch
diff -Nru orthanc-1.10.1+dfsg/debian/changelog
orthanc-1.10.1+dfsg/debian/changelog
--- orthanc-1.10.1+dfsg/debian/changelog2022-03-23 21:05:58.0
+0100
+++ orthanc-1.10.1+dfsg/debian/changelog2022-05-04 10:13:08.0
+0200
@@ -1,3 +1,10 @@
+orthanc (1.10.1+dfsg-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * add patch to build with dcmtk >= 3.6.7 (closes: #XXX)
+
+ -- Johannes Schauer Marin Rodrigues Wed, 04 May 2022
10:13:08 +0200
+
orthanc (1.10.1+dfsg-1) unstable; urgency=medium
* New upstream version
diff -Nru orthanc-1.10.1+dfsg/debian/patches/dcmtk-3.6.7
orthanc-1.10.1+dfsg/debian/patches/dcmtk-3.6.7
--- orthanc-1.10.1+dfsg/debian/patches/dcmtk-3.6.7 1970-01-01
01:00:00.0 +0100
+++ orthanc-1.10.1+dfsg/debian/patches/dcmtk-3.6.7 2022-05-04
10:13:08.0 +0200
@@ -0,0 +1,40 @@
+--- a/OrthancFramework/Sources/DicomNetworking/Internals/DicomTls.cpp
b/OrthancFramework/Sources/DicomNetworking/Internals/DicomTls.cpp
+@@ -107,19 +107,19 @@ namespace Orthanc
+ new DcmTLSTransportLayer(tmpRole /*opt_networkRole*/, NULL
/*opt_readSeedFile*/,
+ OFFalse /*initializeOpenSSL, done by
Orthanc::Toolbox::InitializeOpenSsl()*/));
+
+- if (tls->addTrustedCertificateFile(trustedCertificatesPath.c_str(),
DCF_Filetype_PEM /*opt_keyFileFormat*/) != TCS_ok)
++ if (tls->addTrustedCertificateFile(trustedCertificatesPath.c_str(),
DCF_Filetype_PEM /*opt_keyFileFormat*/).bad())
+ {
+ throw OrthancException(ErrorCode_BadFileFormat, "Cannot parse PEM
file with trusted certificates for DICOM TLS: " +
+trustedCertificatesPath);
+
Bug#1010589: cgreen: links to libraries from binutils which are not considered stable
Source: cgreen Version: 1.5.1-1 Severity: serious X-Debbugs-Cc: gin...@debian.org, d...@debian.org Dear maintainer, Quoting from bug #949570: Your package should not use the private binutils shared libraries. If it cannot be dropped, then please link those statically and document it with the Built-Using tag in the binary package. libbfd and libopcodes seem to be considered as a private interface because their API/ABI is too unstable. This is stated in the description: Description: GNU binary utilities (BFD development files) This package includes header files and static libraries necessary to build programs which use the GNU BFD library, which is part of binutils. Note that building Debian packages which depend on the shared libbfd is Not Allowed. Paul
Processed: src:webcamoid: fails to migrate to testing for too long: autopkgtest regression
Processing control commands:
> close -1 9.0.0-3
Bug #1010588 [src:webcamoid] src:webcamoid: fails to migrate to testing for too
long: autopkgtest regression
Marked as fixed in versions webcamoid/9.0.0-3.
Bug #1010588 [src:webcamoid] src:webcamoid: fails to migrate to testing for too
long: autopkgtest regression
Marked Bug as done
> block -1 by 1007738
Bug #1010588 {Done: Paul Gevers } [src:webcamoid]
src:webcamoid: fails to migrate to testing for too long: autopkgtest regression
1010588 was not blocked by any bugs.
1010588 was not blocking any bugs.
Added blocking bug(s) of 1010588: 1007738
--
1010588: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010588
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1010588: src:webcamoid: fails to migrate to testing for too long: autopkgtest regression
Source: webcamoid Version: 8.8.0+dfsg-1 Severity: serious Control: close -1 9.0.0-3 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1007738 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:webcamoid has been trying to migrate for 61 days [2]. Hence, I am filing this bug. The blocking issue has already been reported in bug #1007738: your autopkgtest regressed. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=webcamoid OpenPGP_signature Description: OpenPGP digital signature
Bug#1008354: fossil: FTBFS: ./conftest__.c:3: undefined reference to `sqlite3_open'
Dear Maintainer, This is a bug in the fossil configure tool, and fixed in upstream: commit: https://fossil-scm.org/home/info/8af827342f4c4a77 forum: https://fossil-scm.org/forum/info/549da79dd9 cf. https://www.sqlite.org/src/info/4cbb3e3efeb40cc4 Regards, Nobuhiro Ban
Processed: Move where it was fixed
Processing commands for cont...@bugs.debian.org:
> reassign 1010573 node-tap-parser 11.0.1+~cs2.1.2-3
Bug #1010573 {Done: Jérémy Lal } [node-yaml] node-yaml:
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './types' is not defined
by "exports" in /usr/share/node_modules/yaml/package.json
Bug reassigned from package 'node-yaml' to 'node-tap-parser'.
No longer marked as found in versions node-yaml/2.0.1-1.
No longer marked as fixed in versions 11.0.1+~cs2.1.2-4 and
node-tap-parser/11.0.1+~cs2.1.2-4.
Bug #1010573 {Done: Jérémy Lal } [node-tap-parser]
node-yaml: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './types' is
not defined by "exports" in /usr/share/node_modules/yaml/package.json
Marked as found in versions node-tap-parser/11.0.1+~cs2.1.2-3.
> fixed 1010573 11.0.1+~cs2.1.2-4
Bug #1010573 {Done: Jérémy Lal } [node-tap-parser]
node-yaml: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './types' is
not defined by "exports" in /usr/share/node_modules/yaml/package.json
Marked as fixed in versions node-tap-parser/11.0.1+~cs2.1.2-4.
> close 1010573
Bug #1010573 {Done: Jérémy Lal } [node-tap-parser]
node-yaml: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './types' is
not defined by "exports" in /usr/share/node_modules/yaml/package.json
Bug 1010573 is already marked as done; not doing anything.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1010573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 3 errors): Move where it was fixed
Processing commands for cont...@bugs.debian.org:
> reasign 1010573 node-tap-parser 11.0.1+~cs2.1.2-3
Unknown command or malformed arguments to command.
> fixed 1010573 11.0.1+~cs2.1.2-4
Bug #1010573 {Done: Jérémy Lal } [node-yaml] node-yaml:
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './types' is not defined
by "exports" in /usr/share/node_modules/yaml/package.json
There is no source info for the package 'node-yaml' at version
'11.0.1+~cs2.1.2-4' with architecture ''
Unable to make a source version for version '11.0.1+~cs2.1.2-4'
Marked as fixed in versions 11.0.1+~cs2.1.2-4.
> close 1010573
Bug #1010573 {Done: Jérémy Lal } [node-yaml] node-yaml:
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './types' is not defined
by "exports" in /usr/share/node_modules/yaml/package.json
Bug 1010573 is already marked as done; not doing anything.
> cu
Unknown command or malformed arguments to command.
> Adrian
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
1010573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1010573: marked as done (node-yaml: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './types' is not defined by "exports" in /usr/share/node_modules/yaml/package.json)
Your message dated Wed, 04 May 2022 22:06:30 +
with message-id
and subject line Bug#1010573: fixed in node-tap-parser 11.0.1+~cs2.1.2-4
has caused the Debian Bug report #1010573,
regarding node-yaml: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath
'./types' is not defined by "exports" in
/usr/share/node_modules/yaml/package.json
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.)
--
1010573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010573
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-modern-syslog
Version: 1.2.0-3
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=node-modern-syslog=mipsel=1.2.0-3%2Bb1=1651678779=0
gyp info ok
make[1]: Leaving directory '/<>'
dh_auto_test --buildsystem=nodejs -a
mkdir -p node_modules
ln -s ../. node_modules/modern-syslog
/bin/sh -ex debian/tests/pkg-js/test
+ tap --no-cov test/test-compat.js test/test-core.js test/test-openlog.js
test/test-setmask.js test/test-stream.js test/test-syslog.js
node:internal/modules/cjs/loader:488
throw e;
^
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './types' is not defined
by "exports" in /usr/share/node_modules/yaml/package.json
at new NodeError (node:internal/errors:371:5)
at throwExportsNotFound (node:internal/modules/esm/resolve:453:9)
at packageExportsResolve (node:internal/modules/esm/resolve:731:3)
at resolveExports (node:internal/modules/cjs/loader:482:36)
at Function.Module._findPath (node:internal/modules/cjs/loader:522:31)
at Function.Module._resolveFilename
(node:internal/modules/cjs/loader:919:27)
at Function.Module._load (node:internal/modules/cjs/loader:778:27)
at Module.require (node:internal/modules/cjs/loader:1005:19)
at require (node:internal/modules/cjs/helpers:102:18)
at Object. (/usr/share/nodejs/tap-yaml/lib/types/index.js:1:15) {
code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}
dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
make: *** [debian/rules:13: binary-arch] Error 25
Cheers
--
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: node-tap-parser
Source-Version: 11.0.1+~cs2.1.2-4
Done: Jérémy Lal
We believe that the bug you reported is fixed in the latest version of
node-tap-parser, 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 1010...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jérémy Lal (supplier of updated node-tap-parser 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: Wed, 04 May 2022 23:05:20 +0200
Source: node-tap-parser
Architecture: source
Version: 11.0.1+~cs2.1.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Jérémy Lal
Closes: 980293 1010573
Changes:
node-tap-parser (11.0.1+~cs2.1.2-4) unstable; urgency=medium
.
* Team upload
* Patch: switch tap-yaml to using yaml 2 api. Closes:#1010573
* Depends node-yaml >= 2.0.1
.
node-tap-parser (11.0.1+~cs2.1.2-3) unstable; urgency=medium
.
* Team upload
* Fix manpage. Closes:#980293.
Checksums-Sha1:
5136e21baf122deef6640c479f5ab2fb1dc3dd66 2912
node-tap-parser_11.0.1+~cs2.1.2-4.dsc
1eb59f075ce51ad50a321e4c342ef58adf5c389d 5044
node-tap-parser_11.0.1+~cs2.1.2-4.debian.tar.xz
d8f7f5c7f6f5c04b2c66f7c871b30d91d4d14762 8998
node-tap-parser_11.0.1+~cs2.1.2-4_source.buildinfo
Checksums-Sha256:
cab901221b31d4e834c1eae9ad9d87d43dd50f5b7d253ca5498e27283f6d1113 2912
node-tap-parser_11.0.1+~cs2.1.2-4.dsc
3f764839598a9572360b4d7bedff971cc3d2db42feb345d49bc40945faf9d81c 5044
node-tap-parser_11.0.1+~cs2.1.2-4.debian.tar.xz
135adcd06bc2b5eedc002dabc3f0686d4b595b3b264871c2940957f48aff34cd 8998
node-tap-parser_11.0.1+~cs2.1.2-4_source.buildinfo
Files:
7316b3b02918e2b5db3c202f515d943a 2912 javascript optional
node-tap-parser_11.0.1+~cs2.1.2-4.dsc
bb04b0a1f1be186047ac4cf8a248457a 5044 javascript optional
node-tap-parser_11.0.1+~cs2.1.2-4.debian.tar.xz
Processed: retitle 1010230 to nvidia-graphics-drivers-legacy-390xx: spurious module build failure in autopkgtest on armhf
Processing commands for cont...@bugs.debian.org: > retitle 1010230 nvidia-graphics-drivers-legacy-390xx: spurious module build > failure in autopkgtest on armhf Bug #1010230 [src:nvidia-graphics-drivers-legacy-390xx] nvidia-graphics-drivers-legacy-390xx: autopkgtest needs update for new version of dkms: includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch Changed Bug title to 'nvidia-graphics-drivers-legacy-390xx: spurious module build failure in autopkgtest on armhf' from 'nvidia-graphics-drivers-legacy-390xx: autopkgtest needs update for new version of dkms: includes a BUILD_EXCLUSIVE directive which does not match this kernel/arch'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1010230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1009839 to gdm3, reassign 1003755 to src:mailutils, fixed 1003755 in 1:3.15-1 ...
Processing commands for cont...@bugs.debian.org:
> reassign 1009839 gdm3 41.0-1
Bug #1009839 [gdm] issue when hard drive full
Warning: Unknown package 'gdm'
Bug reassigned from package 'gdm' to 'gdm3'.
No longer marked as found in versions 41.0.
Ignoring request to alter fixed versions of bug #1009839 to the same values
previously set
Bug #1009839 [gdm3] issue when hard drive full
Marked as found in versions gdm3/41.0-1.
> reassign 1003755 src:mailutils 1:3.14-1
Bug #1003755 {Done: Mattia Rizzolo }
[libmailutils8,libmailutils9] libmailutils8: 1:3.14-1 breaks ABI vs 1:3.13-1,
doesn't bump abiver
Warning: Unknown package 'libmailutils8'
Bug reassigned from package 'libmailutils8,libmailutils9' to 'src:mailutils'.
No longer marked as found in versions libmailutils8/1:3.14-1.
No longer marked as fixed in versions libmailutils9/1:3.15-1.
Bug #1003755 {Done: Mattia Rizzolo } [src:mailutils]
libmailutils8: 1:3.14-1 breaks ABI vs 1:3.13-1, doesn't bump abiver
Marked as found in versions mailutils/1:3.14-1.
> fixed 1003755 1:3.15-1
Bug #1003755 {Done: Mattia Rizzolo } [src:mailutils]
libmailutils8: 1:3.14-1 breaks ABI vs 1:3.13-1, doesn't bump abiver
Marked as fixed in versions mailutils/1:3.15-1.
> tags 1010454 - bookworm sid
Bug #1010454 [src:docker.io] docker.io: FTBFS on s390x: === FAIL: daemon/logger
TestCopierWithSized (0.00s)
Removed tag(s) bookworm and sid.
> tags 1010549 + sid bookworm
Bug #1010549 [src:itksnap] itksnap: FTBFS because b-d on libvtk6-dev
Added tag(s) bookworm and sid.
> tags 1001652 + sid bookworm
Bug #1001652 [rapid-photo-downloader] Package new version of Rapid Photo
Downloader (0.9.27)
Added tag(s) bookworm and sid.
> tags 1009029 + sid bookworm
Bug #1009029 [julia] julia: FTBFS with libgit2 1.3.0
Added tag(s) bookworm and sid.
> tags 1010421 + sid bookworm
Bug #1010421 [src:gir-to-d] gir-to-d: FTBFS with ldc 1.29
Added tag(s) bookworm and sid.
> notfixed 1009043 1.21.0
Bug #1009043 {Done: Guillem Jover } [dpkg]
dpkg-fsys-usrunmess abuses "Protected: yes" status
No longer marked as fixed in versions 1.21.0.
> reassign 1007830 src:dune-common
Bug #1007830 {Done: Drew Parsons } [src:opm-grid]
opm-grid: METIS_PartGraphVKway is available in metis v3 but opm-grid tests link
to metis v5
Bug reassigned from package 'src:opm-grid' to 'src:dune-common'.
No longer marked as found in versions opm-grid/2021.10-2.
No longer marked as fixed in versions dune-common/2.8.0-4.
> fixed 1007830 2.8.0-4
Bug #1007830 {Done: Drew Parsons } [src:dune-common]
opm-grid: METIS_PartGraphVKway is available in metis v3 but opm-grid tests link
to metis v5
Marked as fixed in versions dune-common/2.8.0-4.
> affects 1007830 + src:opm-grid
Bug #1007830 {Done: Drew Parsons } [src:dune-common]
opm-grid: METIS_PartGraphVKway is available in metis v3 but opm-grid tests link
to metis v5
Added indication that 1007830 affects src:opm-grid
> fixed 930697 2.29-1
Bug #930697 {Done: Aurelien Jarno } [src:glibc] glibc:
merge latest upstream 2.28 changes
Marked as fixed in versions glibc/2.29-1.
> reassign 1004292 s390-dasd 0.0.51
Bug #1004292 {Done: Cyril Brulebois } [src:debian-installer]
debian-installer:s390x: installer fails to format dasd disc on s390x systems
Bug reassigned from package 'src:debian-installer' to 's390-dasd'.
No longer marked as found in versions debian-installer/20210731+deb11u2.
No longer marked as fixed in versions s390-dasd/0.0.74.
Bug #1004292 {Done: Cyril Brulebois } [s390-dasd]
debian-installer:s390x: installer fails to format dasd disc on s390x systems
Marked as found in versions s390-dasd/0.0.51.
> fixed 1004292 0.0.74
Bug #1004292 {Done: Cyril Brulebois } [s390-dasd]
debian-installer:s390x: installer fails to format dasd disc on s390x systems
Marked as fixed in versions s390-dasd/0.0.74.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1001652: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001652
1003755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1003755
1004292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004292
1007830: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007830
1009029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009029
1009043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009043
1009839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009839
1010421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010421
1010454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010454
1010549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010549
930697: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#999225: cl-getopt: diff for NMU version 1.2.0-3.2
Control: tags 999225 + patch
Control: tags 999225 + pending
Dear maintainer,
I've prepared an NMU for cl-getopt (versioned as 1.2.0-3.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.
Regards.
diff -u cl-getopt-1.2.0/debian/changelog cl-getopt-1.2.0/debian/changelog
--- cl-getopt-1.2.0/debian/changelog
+++ cl-getopt-1.2.0/debian/changelog
@@ -1,3 +1,10 @@
+cl-getopt (1.2.0-3.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/rules: Add build-{arch,indep} (Closes: #999225).
+
+ -- Marcos Talau Thu, 28 Apr 2022 13:00:53 -0300
+
cl-getopt (1.2.0-3.1) unstable; urgency=medium
* Non-maintainer upload.
diff -u cl-getopt-1.2.0/debian/rules cl-getopt-1.2.0/debian/rules
--- cl-getopt-1.2.0/debian/rules
+++ cl-getopt-1.2.0/debian/rules
@@ -43,5 +43,7 @@
binary: binary-indep
+build-arch: build
+build-indep: build
-.PHONY: build clean binary-indep binary-arch binary install
+.PHONY: build build-arch build-indep clean binary-indep binary-arch binary install
Processed: cl-getopt: diff for NMU version 1.2.0-3.2
Processing control commands: > tags 999225 + patch Bug #999225 [src:cl-getopt] cl-getopt: missing required debian/rules targets build-arch and/or build-indep Added tag(s) patch. > tags 999225 + pending Bug #999225 [src:cl-getopt] cl-getopt: missing required debian/rules targets build-arch and/or build-indep Added tag(s) pending. -- 999225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999225 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#918984: fuse3 still not co-installable with fuse
Hi, Just for the record in this bug, the versioned Provides was implemented before the release of bullseye, so that didn't solve the problem Sebastian mentioned. Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: Bug#1010573: node-modern-syslog: FTBFS on mipsel
Processing control commands: > reassign -1 node-yaml 2.0.1-1 Bug #1010573 [src:node-modern-syslog] node-modern-syslog: FTBFS on mipsel Bug reassigned from package 'src:node-modern-syslog' to 'node-yaml'. No longer marked as found in versions node-modern-syslog/1.2.0-3. Ignoring request to alter fixed versions of bug #1010573 to the same values previously set Bug #1010573 [node-yaml] node-modern-syslog: FTBFS on mipsel Marked as found in versions node-yaml/2.0.1-1. > retitle -1 node-yaml: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath > './types' is not defined by "exports" in > /usr/share/node_modules/yaml/package.json Bug #1010573 [node-yaml] node-modern-syslog: FTBFS on mipsel Changed Bug title to 'node-yaml: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './types' is not defined by "exports" in /usr/share/node_modules/yaml/package.json' from 'node-modern-syslog: FTBFS on mipsel'. > affects -1 src:node-modern-syslog src:node-tap-parser Bug #1010573 [node-yaml] node-yaml: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './types' is not defined by "exports" in /usr/share/node_modules/yaml/package.json Added indication that 1010573 affects src:node-modern-syslog and src:node-tap-parser -- 1010573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010573 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010573: node-modern-syslog: FTBFS on mipsel
Control: reassign -1 node-yaml 2.0.1-1
Control: retitle -1 node-yaml: Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package
subpath './types' is not defined by "exports" in
/usr/share/node_modules/yaml/package.json
Control: affects -1 src:node-modern-syslog src:node-tap-parser
On Wed, May 04, 2022 at 07:13:29PM +0200, Sebastian Ramacher wrote:
>...
> https://buildd.debian.org/status/fetch.php?pkg=node-modern-syslog=mipsel=1.2.0-3%2Bb1=1651678779=0
>
> gyp info ok
> make[1]: Leaving directory '/<>'
>dh_auto_test --buildsystem=nodejs -a
> mkdir -p node_modules
> ln -s ../. node_modules/modern-syslog
> /bin/sh -ex debian/tests/pkg-js/test
> + tap --no-cov test/test-compat.js test/test-core.js test/test-openlog.js
> test/test-setmask.js test/test-stream.js test/test-syslog.js
> node:internal/modules/cjs/loader:488
> throw e;
> ^
>
> Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './types' is not
> defined by "exports" in /usr/share/node_modules/yaml/package.json
> at new NodeError (node:internal/errors:371:5)
> at throwExportsNotFound (node:internal/modules/esm/resolve:453:9)
> at packageExportsResolve (node:internal/modules/esm/resolve:731:3)
> at resolveExports (node:internal/modules/cjs/loader:482:36)
> at Function.Module._findPath (node:internal/modules/cjs/loader:522:31)
> at Function.Module._resolveFilename
> (node:internal/modules/cjs/loader:919:27)
> at Function.Module._load (node:internal/modules/cjs/loader:778:27)
> at Module.require (node:internal/modules/cjs/loader:1005:19)
> at require (node:internal/modules/cjs/helpers:102:18)
> at Object.
> (/usr/share/nodejs/tap-yaml/lib/types/index.js:1:15) {
> code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
> }
> dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
> make: *** [debian/rules:13: binary-arch] Error 25
This is not specific to mipsel or node-modern-syslog:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-modern-syslog.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-tap-parser.html
I cannot judge which package is technically at fault, but the breakage
is due to node-yaml 2.0.1-1.
> Cheers
cu
Adrian
Bug#901952: fixing pristine-tar w.r.t. changed tar escaping
Hi all, On Sun, 31 Mar 2019 03:13:28 +0200 "Bernhard R. Link" wrote: * Bernhard R. Link [190330 07:58]: > I'm looking into #901952 (pristine-tar failing to checkout out old files > with non-printable unicode characters) and think that might be solved > with the attached patches, by calling tar with --null and giving it > a copy of the manifest file that is unescaped and NUL-terminated. > > What I haven't looked into yet is whether it will break files > generated with 1.46, as that the format incompatibly without > changing the version of the delta (though perhaps that can be > mitigated by an additional variant at checkout time). > > What are your opinions on that? Is this worth trying to get into buster? Attached version with some small fixes, more tests convering those changes (and compatibility with previous versions), and an additional variant run on checkout time to also handle files commited with 1.46. Bernhard R. Link -- F8AC 04D5 0B9B 064B 3383 C3DA AFFC 96D1 151D FFDC I'm pretty sure that the fix for bug #933031 (in pristine-tar) works around the issue. Shall we close this bug as won't fix? Paul OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: firefox-esr: FTBFS and embeded copy of code
Processing control commands: > tag -1 - ftbfs Bug #993660 [src:firefox-esr] firefox-esr: FTBFS and embeded copy of code Removed tag(s) ftbfs. > tag 993659 - ftbfs Bug #993659 [src:firefox-esr] firefox-esr: FTBFS and embeded copy of code Removed tag(s) ftbfs. -- 993659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993659 993660: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993660 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993660: firefox-esr: FTBFS and embeded copy of code
Control: tag -1 - ftbfs Control: tag 993659 - ftbfs Hi Bastien, On Sat, 04 Sep 2021 11:46:35 + "=?utf-8?q?Bastien_Roucari=C3=A8s?=" wrote: Source: src:firefox-esr Version: FTBFS and embdeded copy Severity: serious Tags: upstream ftbfs Control: clone -1 -2 Control: affects -2 src:firefox Did you intent to have -2 (this bug 993660) reassigned to src:firefox instead? Now these two bugs are just clones against the firefox-esr source package. Also, ftbfs is used when the build fails, not when the build is not building all binary artifacts, we don't have a tag for that. Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#986590: Still reproducible
The bug is still reproducible. This time on armhf [1] and in CI [2]. [1] https://buildd.debian.org/status/fetch.php?pkg=dbus-test-runner=armhf=19.04.0-1%7Eexp1=1651644822=0 [2] https://salsa.debian.org/debian/dbus-test-runner/-/jobs/2731578 Regards Anton
Processed: tagging 1010573
Processing commands for cont...@bugs.debian.org: > tags 1010573 + sid bookworm Bug #1010573 [src:node-modern-syslog] node-modern-syslog: FTBFS on mipsel Added tag(s) sid and bookworm. > thanks Stopping processing here. Please contact me if you need assistance. -- 1010573: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010573 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1007890: marked as done (FTBFS: No module named 'ipython_genutils')
Your message dated Wed, 04 May 2022 19:11:23 +0200
with message-id <60d571bd67e68e5d4e5a626b23d2c2833d1c8c50.ca...@gmail.com>
and subject line Fixed since long, should be closed
has caused the Debian Bug report #1007890,
regarding FTBFS: No module named 'ipython_genutils'
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.)
--
1007890: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: theano
Version: 1.0.5+dfsg-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
cp
/var/lib/nspawn-runner/.build/js-team/nodejs/debian/output/theano-1.0.5+dfsg/doc/library/d3viz/index.ipynb
jupyter_tmp && jupyter-nbconvert --to notebook --execute
/var/lib/nspawn-runner/.build/js-team/nodejs/debian/output/theano-1.0.5+dfsg/jupyter_tmp/index.ipynb
--output
/var/lib/nspawn-runner/.build/js-team/nodejs/debian/output/theano-1.0.5+dfsg/jupyter_tmp/test.ipynb
Traceback (most recent call last):
File "/usr/bin/jupyter-nbconvert", line 33, in
sys.exit(load_entry_point('nbconvert==6.4.4', 'console_scripts',
'jupyter-nbconvert')())
File "/usr/bin/jupyter-nbconvert", line 25, in importlib_load_entry_point
return next(matches).load()
File "/usr/lib/python3.9/importlib/metadata.py", line 86, in load
module = import_module(match.group('module'))
File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 972, in _find_and_load_unlocked
File "", line 228, in _call_with_frames_removed
File "", line 1030, in _gcd_import
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 850, in exec_module
File "", line 228, in _call_with_frames_removed
File "/usr/lib/python3/dist-packages/nbconvert/__init__.py", line 4, in
from .exporters import *
File "/usr/lib/python3/dist-packages/nbconvert/exporters/__init__.py", line
4, in
from .slides import SlidesExporter
File "/usr/lib/python3/dist-packages/nbconvert/exporters/slides.py", line 12,
in
from ..preprocessors.base import Preprocessor
File "/usr/lib/python3/dist-packages/nbconvert/preprocessors/__init__.py",
line 10, in
from .execute import ExecutePreprocessor
File "/usr/lib/python3/dist-packages/nbconvert/preprocessors/execute.py",
line 8, in
from nbclient import NotebookClient, execute as _execute
File "/usr/lib/python3/dist-packages/nbclient/__init__.py", line 5, in
from .client import NotebookClient, execute # noqa: F401
File "/usr/lib/python3/dist-packages/nbclient/client.py", line 35, in
from .output_widget import OutputWidget
File "/usr/lib/python3/dist-packages/nbclient/output_widget.py", line 6, in
from .jsonutil import json_clean
File "/usr/lib/python3/dist-packages/nbclient/jsonutil.py", line 16, in
from ipython_genutils import py3compat
ModuleNotFoundError: No module named 'ipython_genutils'
make[1]: *** [debian/rules:46: override_dh_auto_build] Error 1
-- System Information:
Debian Release: bookworm/sid
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'unstable'), (101, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.16.0-5-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Hi,
I was wondering why a serious bug was still open - and with a patch -
after such a long time: it's been fixed since long, so I'm closing.
Cheers,
J.Puydt--- End Message ---
Bug#1010573: node-modern-syslog: FTBFS on mipsel
Source: node-modern-syslog
Version: 1.2.0-3
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=node-modern-syslog=mipsel=1.2.0-3%2Bb1=1651678779=0
gyp info ok
make[1]: Leaving directory '/<>'
dh_auto_test --buildsystem=nodejs -a
mkdir -p node_modules
ln -s ../. node_modules/modern-syslog
/bin/sh -ex debian/tests/pkg-js/test
+ tap --no-cov test/test-compat.js test/test-core.js test/test-openlog.js
test/test-setmask.js test/test-stream.js test/test-syslog.js
node:internal/modules/cjs/loader:488
throw e;
^
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './types' is not defined
by "exports" in /usr/share/node_modules/yaml/package.json
at new NodeError (node:internal/errors:371:5)
at throwExportsNotFound (node:internal/modules/esm/resolve:453:9)
at packageExportsResolve (node:internal/modules/esm/resolve:731:3)
at resolveExports (node:internal/modules/cjs/loader:482:36)
at Function.Module._findPath (node:internal/modules/cjs/loader:522:31)
at Function.Module._resolveFilename
(node:internal/modules/cjs/loader:919:27)
at Function.Module._load (node:internal/modules/cjs/loader:778:27)
at Module.require (node:internal/modules/cjs/loader:1005:19)
at require (node:internal/modules/cjs/helpers:102:18)
at Object. (/usr/share/nodejs/tap-yaml/lib/types/index.js:1:15) {
code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}
dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1
make: *** [debian/rules:13: binary-arch] Error 25
Cheers
--
Sebastian Ramacher
Bug#1010556: undefined symbol extract_begin
Thanks for reporting this bug. I confirm I can reproduce it on my system running unstable. Never caught it since I was running the poppler plugin. I'll have a closer look at this in the coming days. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄
Bug#1010558: marked as done (jetty9: FTBFS An API incompatibility was encountered while executing org.apache.maven.plugins:maven-assembly-plugin)
Your message dated Wed, 04 May 2022 16:54:31 + with message-id and subject line Bug#1010558: fixed in plexus-archiver 4.2.7-2 has caused the Debian Bug report #1010558, regarding jetty9: FTBFS An API incompatibility was encountered while executing org.apache.maven.plugins:maven-assembly-plugin 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.) -- 1010558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010558 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: jetty9 Version: 9.4.46-1 Severity: serious X-Debbugs-Cc: a...@debian.org Hi, I have just discovered that jetty9 fails to build from source. An API incompatibility was encountered while executing org.apache.maven.plugins:maven-assembly-plugin Probably some recently upgraded reverse-dependency is to blame here. Markus --- End Message --- --- Begin Message --- Source: plexus-archiver Source-Version: 4.2.7-2 Done: Emmanuel Bourg We believe that the bug you reported is fixed in the latest version of plexus-archiver, 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 1010...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg (supplier of updated plexus-archiver 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: Wed, 04 May 2022 18:18:14 +0200 Source: plexus-archiver Architecture: source Version: 4.2.7-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Emmanuel Bourg Closes: 1010558 Changes: plexus-archiver (4.2.7-2) unstable; urgency=medium . * Team upload. * Improved the backward compatibility (Closes: #1010558) - Default implementation of BaseFileSet.getFileMappers() - Default implementation of the new Archiver methods Checksums-Sha1: 9ff98392d1b08cdde0351d5194ea56111b0f5865 2330 plexus-archiver_4.2.7-2.dsc 060705f723ac23d9d66b983b54eabe002b37a979 5908 plexus-archiver_4.2.7-2.debian.tar.xz 1b89d8b7ec9e1738a76b9125f02805817f94d29c 15030 plexus-archiver_4.2.7-2_source.buildinfo Checksums-Sha256: 4dc5ebec4c10d87af64e8dfcfa939a69c3295aade8d7d871dd4f35b33dd6d0db 2330 plexus-archiver_4.2.7-2.dsc 5e550eecba9269f773987eadfa5fc435b0112c9ee42b636f439daae7c57a54b6 5908 plexus-archiver_4.2.7-2.debian.tar.xz 4a23bec8be01eb0357b0124c86552cc6f200d54aedba31ba878458194fa382a8 15030 plexus-archiver_4.2.7-2_source.buildinfo Files: 322fd8035b4fadfad1a8d9ebcf84dae4 2330 java optional plexus-archiver_4.2.7-2.dsc 4d418ea7d59b1dd00f0d8925c5560ee6 5908 java optional plexus-archiver_4.2.7-2.debian.tar.xz 643aa00973fea362f496b4ef349f0bce 15030 java optional plexus-archiver_4.2.7-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEuM5N4hCA3PkD4WxA9RPEGeS50KwFAmJyqXgSHGVib3VyZ0Bh cGFjaGUub3JnAAoJEPUTxBnkudCs14sP/3JDyjbDhymEAxA4XdqxeQs4ACnTca4Y zpR9RUHwqEQVIOVrUbCYqYdEQVq6aApVcxHdX63bCA4azgbZcbtIEXzSR8lTUQQr tx8qS7qpZGSX3jR2SiVvlde5tyAt5/uvTuxqYyWDgEMxWGzR7uuSscE/8hDJtcfP h7Jr7dH/34sAXLtkA7zassopVbeG4pjIaGFm7me2IJ8bVAP12ut7xgGQ0udYcTIs Ciq/932Qqgt3NxdXkMfkcYrcmCN4c/G94AR1Dq8pGqnyCRg37wB2vXvVSFkHSdZl 5K4wempO39s62cKiNuR5lB2B/92ECthLs4hHeSfNoxxVmlCQKW32AkKr860ec18C RGk3oa+kvuaOYdvRQdsph0DDrFZ7CVrLjezyrJdM6b27UGO8RZUQcyrBt+0NMC0Y djUYhyKRL2uSHmHqENl4deRAtFrC7T5cmQmdnbK8dqMnXpzU03GqBEqyMNzOjmIE efZWRTVBHv8IOJjgXnFFSNrtNZ3lIfz+nEntyoxgA/eNs5rF2cgI+G8yyLuuDFiz 0jwcqoyA7HkwgpmBAq9sd5AsGZ0uPdLys1my0QfwhC1ox9nB7QHIYRn8+QVQQhiY I6UEZ+QtnpwS/Bu0l8fEHs+VDME/iWVlJnL+YWueM1XePomgIqCvFXeYwfXrJP42 NNviQWQXfvOI =TqnC -END PGP SIGNATURE End Message ---
Bug#1010558: jetty9: FTBFS An API incompatibility was encountered while executing org.apache.maven.plugins:maven-assembly-plugin
Le 04/05/2022 à 13:10, Markus Koschany a écrit : I have just discovered that jetty9 fails to build from source. An API incompatibility was encountered while executing org.apache.maven.plugins:maven-assembly-plugin Probably some recently upgraded reverse-dependency is to blame here. Thank you for reporting the issue Markus, this is caused by an incompatibility in plexus-archiver/4.2.7-1. The fix will be uploaded soon. Emmanuel Bourg
Bug#1009464: marked as done (xdg-desktop-portal-wlr: FTBFS: string.h:283:21: error: implicit declaration of function ‘strtof_l’; did you mean ‘strtok_r’? [-Werror=implicit-function-declaration])
Your message dated Wed, 04 May 2022 16:36:11 + with message-id and subject line Bug#1009464: fixed in xdg-desktop-portal-wlr 0.5.0-4 has caused the Debian Bug report #1009464, regarding xdg-desktop-portal-wlr: FTBFS: string.h:283:21: error: implicit declaration of function ‘strtof_l’; did you mean ‘strtok_r’? [-Werror=implicit-function-declaration] 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.) -- 1009464: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009464 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xdg-desktop-portal-wlr Version: 0.5.0-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cc -Ixdg-desktop-portal-wlr.p -I. -I.. -I../include -Iprotocols > -I/usr/include/pipewire-0.3 -I/usr/include/spa-0.2 -fdiagnostics-color=always > -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O0 > -Wno-missing-braces -Wno-missing-field-initializers -Wno-unused-parameter > -D_POSIX_C_SOURCE=200809L '-DSYSCONFDIR="/etc"' -DHAVE_LIBSYSTEMD=1 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT -MD -MQ > xdg-desktop-portal-wlr.p/src_core_session.c.o -MF > xdg-desktop-portal-wlr.p/src_core_session.c.o.d -o > xdg-desktop-portal-wlr.p/src_core_session.c.o -c ../src/core/session.c > In file included from /usr/include/pipewire-0.3/pipewire/properties.h:35, > from /usr/include/pipewire-0.3/pipewire/core.h:87, > from /usr/include/pipewire-0.3/pipewire/context.h:67, > from /usr/include/pipewire-0.3/pipewire/protocol.h:46, > from /usr/include/pipewire-0.3/pipewire/proxy.h:108, > from /usr/include/pipewire-0.3/pipewire/client.h:35, > from /usr/include/pipewire-0.3/pipewire/pipewire.h:35, > from ../include/screencast_common.h:4, > from ../include/xdpw.h:13, > from ../src/core/session.c:6: > /usr/include/spa-0.2/spa/utils/string.h: In function ‘spa_strtof’: > /usr/include/spa-0.2/spa/utils/string.h:283:21: error: implicit declaration > of function ‘strtof_l’; did you mean ‘strtok_r’? > [-Werror=implicit-function-declaration] > 283 | v = strtof_l(str, endptr, locale); > | ^~~~ > | strtok_r > /usr/include/spa-0.2/spa/utils/string.h: In function ‘spa_strtod’: > /usr/include/spa-0.2/spa/utils/string.h:327:21: error: implicit declaration > of function ‘strtod_l’; did you mean ‘strtok_r’? > [-Werror=implicit-function-declaration] > 327 | v = strtod_l(str, endptr, locale); > | ^~~~ > | strtok_r > cc1: all warnings being treated as errors > [11/21] cc -Ixdg-desktop-portal-wlr.p -I. -I.. -I../include -Iprotocols > -I/usr/include/pipewire-0.3 -I/usr/include/spa-0.2 -fdiagnostics-color=always > -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O0 > -Wno-missing-braces -Wno-missing-field-initializers -Wno-unused-parameter > -D_POSIX_C_SOURCE=200809L '-DSYSCONFDIR="/etc"' -DHAVE_LIBSYSTEMD=1 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT -MD -MQ > xdg-desktop-portal-wlr.p/src_core_timer.c.o -MF > xdg-desktop-portal-wlr.p/src_core_timer.c.o.d -o > xdg-desktop-portal-wlr.p/src_core_timer.c.o -c ../src/core/timer.c > FAILED: xdg-desktop-portal-wlr.p/src_core_timer.c.o > cc -Ixdg-desktop-portal-wlr.p -I. -I.. -I../include -Iprotocols > -I/usr/include/pipewire-0.3 -I/usr/include/spa-0.2 -fdiagnostics-color=always > -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Werror -std=c11 -O0 > -Wno-missing-braces -Wno-missing-field-initializers -Wno-unused-parameter > -D_POSIX_C_SOURCE=200809L '-DSYSCONFDIR="/etc"' -DHAVE_LIBSYSTEMD=1 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT -MD -MQ > xdg-desktop-portal-wlr.p/src_core_timer.c.o -MF > xdg-desktop-portal-wlr.p/src_core_timer.c.o.d -o > xdg-desktop-portal-wlr.p/src_core_timer.c.o -c ../src/core/timer.c > In file included from /usr/include/pipewire-0.3/pipewire/properties.h:35, > from
Processed: reassign 1010558 to plexus-archiver
Processing commands for cont...@bugs.debian.org: > reassign 1010558 plexus-archiver Bug #1010558 [plexus-archiver] jetty9: FTBFS An API incompatibility was encountered while executing org.apache.maven.plugins:maven-assembly-plugin Ignoring request to reassign bug #1010558 to the same package > thanks Stopping processing here. Please contact me if you need assistance. -- 1010558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010558 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: reassign 1010558 to plexus-archiver
Processing commands for cont...@bugs.debian.org: > reassign 1010558 plexus-archiver Bug #1010558 [jetty9] jetty9: FTBFS An API incompatibility was encountered while executing org.apache.maven.plugins:maven-assembly-plugin Bug reassigned from package 'jetty9' to 'plexus-archiver'. No longer marked as found in versions jetty9/9.4.46-1. Ignoring request to alter fixed versions of bug #1010558 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1010558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010558 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995354: marked as done (ruby-async-http: autopkgtest needs update for new version of ruby-protocol-http: Could not find 'protocol-http' (~> 0.20.0))
Your message dated Wed, 04 May 2022 15:51:59 + with message-id and subject line Bug#995354: fixed in ruby-async-http 0.56.5-1 has caused the Debian Bug report #995354, regarding ruby-async-http: autopkgtest needs update for new version of ruby-protocol-http: Could not find 'protocol-http' (~> 0.20.0) 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.) -- 995354: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995354 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-async-http Version: 0.52.5-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, ruby-protocol-h...@packages.debian.org, ruby-protocol-h...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:ruby-protocol-http src:ruby-protocol-http1 Dear maintainer(s), With a recent upload of ruby-protocol-http the autopkgtest of ruby-async-http fails in testing when that autopkgtest is run with the binary packages of ruby-protocol-http from unstable. It passes when run with only packages from testing. In tabular form: passfail ruby-protocol-http from testing0.22.5-1 ruby-async-httpfrom testing0.52.5-1 versioned deps [0] from testingfrom unstable all others from testingfrom testing I copied some of the output at the bottom of this report. It looks to me that you have to make your package compatible with the next version of ruby-protocol-http Currently this regression is blocking the migration of ruby-protocol-http to testing [1]. Of course, ruby-protocol-http shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in ruby-protocol-http was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from ruby-protocol-http should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [0] You can see what packages were added from the second line of the log file quoted below. The migration software adds source package from unstable to the list if they are needed to install packages from ruby-protocol-http/0.22.5-1. I.e. due to versioned dependencies or breaks/conflicts. [1] https://qa.debian.org/excuses.php?package=ruby-protocol-http https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-async-http/15624245/log.gz autopkgtest [00:17:44]: test gem2deb-test-runner: [--- ┌──┐ │ Checking Rubygems dependency resolution on ruby2.7 │ └──┘ GEM_PATH= ruby2.7 -e gem\ \"async-http\" /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Could not find 'protocol-http' (~> 0.20.0) among 69 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/home/debci/.local/share/gem/ruby/2.7.0:/var/lib/gems/2.7.0:/usr/local/lib/ruby/gems/2.7.0:/usr/lib/ruby/gems/2.7.0:/usr/lib/x86_64-linux-gnu/ruby/gems/2.7.0:/usr/share/rubygems-integration/2.7.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.7.0' at: /usr/share/rubygems-integration/all/specifications/async-http-0.52.5.gemspec, execute `gem env` for more information from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1401:in `block in activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `each' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1390:in `activate_dependencies' from /usr/lib/ruby/vendor_ruby/rubygems/specification.rb:1372:in `activate' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `block in gem' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `synchronize' from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_gem.rb:68:in `gem' from -e:1:in `' /usr/lib/ruby/vendor_ruby/rubygems/dependency.rb:313:in `to_specs': Could not find 'protocol-http' (~> 0.20.0) - did find: [protocol-http-0.22.5]
Processed: Reassign autopkgtest bug
Processing commands for cont...@bugs.debian.org: > reassign 1010430 src:skimage 0.18.3-2 Bug #1010430 [src:tifffile, src:skimage] tifffile breaks skimage autopkgtest: asarray() got an unexpected keyword argument 'multifile' Bug reassigned from package 'src:tifffile, src:skimage' to 'src:skimage'. No longer marked as found in versions skimage/0.18.3-2. Ignoring request to alter fixed versions of bug #1010430 to the same values previously set Bug #1010430 [src:skimage] tifffile breaks skimage autopkgtest: asarray() got an unexpected keyword argument 'multifile' Marked as found in versions skimage/0.18.3-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1010430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): Reassign autopkgtest bug
Processing commands for cont...@bugs.debian.org: > notfound 1010430 tifffile/20220426-1 Bug #1010430 [src:tifffile, src:skimage] tifffile breaks skimage autopkgtest: asarray() got an unexpected keyword argument 'multifile' No longer marked as found in versions tifffile/20220426-1. > reassign 1010430 skimage/0.18.3-2 Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. -- 1010430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010430 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010536: libdcmimage.so.16: cannot open shared object file: No such file or directory
Hi Johannes, Am Wed, May 04, 2022 at 04:12:49PM +0200 schrieb Johannes Schauer Marin Rodrigues: > Quoting Andreas Tille (2022-05-04 16:07:27) > > I'm an3as in IRC but I do not lurk in IRC usually. > > Ah, nice word play in the nick. :) I invented it at DebConf Argentina and Spanish speaking people get it pretty easy. ;-) > > Well, I think I could do this in the source only upload. I just pushed that > > change to Git[1] to make sure we will not forget this. > > I think this should be a Breaks+Replaces with exactly version 3.6.7-1. There > is > no reason to make libdcmtk17 not be co-installable with other versions of > libdcmtk16, no? The file-conflict is only with libdcmtk16 (= 3.6.7-1). Fixed in Git. > > Roling back to dcmtk-3.6.7+really3.6.6 would remain an option anyway if this > > will be more convenient for you. > > Well, yes, it would be more convenient for me, but you are doing the work, so > I'm not going to make any demands. :D I think the stronger reason to go roll > back to dcmtk-3.6.7+really3.6.6 is, that Sebastian Ramacher as a release team > member pointed out that they would prefer that option. I think I'll go that route then (but probably tomorrow). BTW, I had (again) a look into ants and think the new upstream version can help to fix the open RC bugs. I once worked on this but at that point of time we did not yet had insighttoolkit5. Now the issue hopefully boiled down to some issue I've reported upstream[1]. As a general remark: The Debian Med team tries to take over and salvage all NeuroDebian packages - but its quite some work in addition to the many packages we just have. Kind regards Andreas. [1] https://github.com/ANTsX/ANTs/issues/1353 -- http://fam-tille.de
Processed: Re: ants: frequent test failures on amd64
Processing control commands: > block -1 by 909833 Bug #872741 [src:ants] ants: frequent test failures on amd64 872741 was not blocked by any bugs. 872741 was not blocking any bugs. Added blocking bug(s) of 872741: 909833 -- 872741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872741 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#872741: ants: frequent test failures on amd64
Control: block -1 by 909833 -- http://fam-tille.de
Bug#905417: ants: broken symlink: /usr/bin/jointfusion -> ../lib/ants/jointfusion
Control: block -1 by 909833 -- http://fam-tille.de
Processed: Re: ants FTBFS with gcc 8
Processing control commands: > tags -1 upstream Bug #909833 [src:ants] ants FTBFS with gcc 8 Added tag(s) upstream. > forwarded -1 https://github.com/ANTsX/ANTs/issues/1353 Bug #909833 [src:ants] ants FTBFS with gcc 8 Set Bug forwarded-to-address to 'https://github.com/ANTsX/ANTs/issues/1353'. -- 909833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: ants: broken symlink: /usr/bin/jointfusion -> ../lib/ants/jointfusion
Processing control commands: > block -1 by 909833 Bug #905417 [ants] ants: broken symlink: /usr/bin/jointfusion -> ../lib/ants/jointfusion 905417 was not blocked by any bugs. 905417 was not blocking any bugs. Added blocking bug(s) of 905417: 909833 -- 905417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#909833: ants FTBFS with gcc 8
Control: tags -1 upstream Control: forwarded -1 https://github.com/ANTsX/ANTs/issues/1353 Hi, I've started checking whether we can save ants inside Debian. The Debian Med team tries to take over packages from NeuroDebian and take over responsibility. The situation of ants became better since insighttoolkit5 became available but there is a remaining build issue which was reported upstream. Kind regards Andreas. -- http://fam-tille.de
Processed: Re: ants: FTBFS: URL using bad/illegal format or missing URL
Processing control commands: > block -1 by 909833 Bug #884710 [src:ants] ants: FTBFS: URL using bad/illegal format or missing URL 884710 was not blocked by any bugs. 884710 was not blocking any bugs. Added blocking bug(s) of 884710: 909833 -- 884710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884710 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#884710: ants: FTBFS: URL using bad/illegal format or missing URL
Control: block -1 by 909833 -- http://fam-tille.de
Bug#1005432: marked as done (yard: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error:)
Your message dated Wed, 04 May 2022 14:36:22 +
with message-id
and subject line Bug#1005432: fixed in yard 0.9.27-1
has caused the Debian Bug report #1005432,
regarding yard: FTBFS: ERROR: Test "ruby2.7" failed: Failure/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.)
--
1005432: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005432
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yard
Version: 0.9.26-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> Failure/Error:
>YARD::GemIndex.each.find do |spec|
> next unless spec.full_name == gemfile_without_ext
> yardoc = Registry.yardoc_file_for_gem(spec.name, "= #{spec.version}")
> if yardoc
>Registry.load_yardoc(yardoc)
>Registry.load_all
> else
>log.enter_level(Logger::ERROR) do
> olddir = Dir.pwd
> Gems.run(spec.name, spec.version.to_s)
>
># received :open with unexpected arguments
> expected: ("gem1.gem", "rb")
> got:
> ("/usr/share/rubygems-integration/all/specifications/asciidoctor-2.0.16.gemspec",
> "r:UTF-8:-")
> # ./lib/yard/cli/diff.rb:134:in `each'
> # ./lib/yard/cli/diff.rb:134:in `find'
> # ./lib/yard/cli/diff.rb:134:in `load_gem_data'
> # ./lib/yard/cli/diff.rb:33:in `block in run'
> # ./lib/yard/cli/diff.rb:29:in `map'
> # ./lib/yard/cli/diff.rb:29:in `run'
> # ./spec/cli/diff_spec.rb:229:in `block (3 levels) in '
> # ./spec/spec_helper.rb:121:in `block (2 levels) in '
>
> Top 5 slowest examples (1.04 seconds, 26.9% of total time):
> YARD::RegistryStore#save never saves as single object db if
> single_object_db is false
> 0.68972 seconds ./spec/registry_store_spec.rb:152
> YARD::Registry Thread local maintains two Registries in separate threads
> 0.10088 seconds ./spec/registry_spec.rb:396
> YARD::Registry Thread local allows setting of yardoc_file in separate
> threads
> 0.10035 seconds ./spec/registry_spec.rb:417
> YARD::Registry Thread local allows setting of po_dir in separate threads
> 0.10029 seconds ./spec/registry_spec.rb:442
> YARD::RegistryStore#save saves as single object db if single_object_db is
> true (and any amount of objects)
> 0.04807 seconds ./spec/registry_store_spec.rb:144
>
> Top 5 slowest example groups:
> YARD::Server::Commands::LibraryCommand
> 0.03814 seconds average (0.11442 seconds / 3 examples)
> ./spec/server/commands/library_command_spec.rb:4
> YARD::RegistryStore
> 0.02393 seconds average (0.78956 seconds / 33 examples)
> ./spec/registry_store_spec.rb:3
> YARD::Parser::C::CParser
> 0.02074 seconds average (0.37327 seconds / 18 examples)
> ./spec/parser/c_parser_spec.rb:3
>
> YARD::Templates::Engine::Template__build_yard_2uPQjK_yard_0_9_26_templates_default_module
> 0.01687 seconds average (0.11807 seconds / 7 examples)
> ./spec/templates/module_spec.rb:4
> YARD::CLI::Display
> 0.01554 seconds average (0.04661 seconds / 3 examples)
> ./spec/cli/display_spec.rb:3
>
> Finished in 3.86 seconds (files took 0.44782 seconds to load)
> 1920 examples, 1 failure
>
> Failed examples:
>
> rspec ./spec/cli/diff_spec.rb:217 # YARD::CLI::Diff File searching searches
> for .gem file
>
> /usr/bin/ruby2.7
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.10.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.10.1/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb --format documentation failed
> ERROR: Test "ruby2.7" failed:
The full build log is available from:
http://qa-logs.debian.net/2022/02/12/yard_0.9.26-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: yard
Source-Version: 0.9.27-1
Done: Cédric Boutillier
We believe that the bug you reported is fixed in the latest version of
yard, which is due
Bug#1010536: libdcmimage.so.16: cannot open shared object file: No such file or directory
Quoting Andreas Tille (2022-05-04 16:07:27) > I'm an3as in IRC but I do not lurk in IRC usually. Ah, nice word play in the nick. :) > > So it seems that the right way forward would be an upload of > > dcmtk-3.6.7+really3.6.6. > > > > And then not forgetting the Breaks+Replaces from libdcmtk17 on libdcmtk16 (= > > 3.6.7-1) > > Well, I think I could do this in the source only upload. I just pushed that > change to Git[1] to make sure we will not forget this. I think this should be a Breaks+Replaces with exactly version 3.6.7-1. There is no reason to make libdcmtk17 not be co-installable with other versions of libdcmtk16, no? The file-conflict is only with libdcmtk16 (= 3.6.7-1). > Roling back to dcmtk-3.6.7+really3.6.6 would remain an option anyway if this > will be more convenient for you. Well, yes, it would be more convenient for me, but you are doing the work, so I'm not going to make any demands. :D I think the stronger reason to go roll back to dcmtk-3.6.7+really3.6.6 is, that Sebastian Ramacher as a release team member pointed out that they would prefer that option. Thanks! cheers, josch signature.asc Description: signature
Bug#1010536: libdcmimage.so.16: cannot open shared object file: No such file or directory
Hi, Am Wed, May 04, 2022 at 03:34:43PM +0200 schrieb Johannes Schauer Marin Rodrigues: > > I asked in #debian-release and Sebastian Ramacher writes: > > 15:27 < Sebastinas> libdcmtk17 will also need Breaks+Replaces on the > libdcmtk16 version with the .so.17 files. > 15:29 < Sebastinas> At least odil is involved in one ongoing transition, so > the binNMU for icu may have broken that. > 15:29 < Sebastinas> I'd appreciate a revert. I'm an3as in IRC but I do not lurk in IRC usually. Its obvious that I did also this in a hurry. > So it seems that the right way forward would be an upload of > dcmtk-3.6.7+really3.6.6. > > And then not forgetting the Breaks+Replaces from libdcmtk17 on libdcmtk16 (= > 3.6.7-1) Well, I think I could do this in the source only upload. I just pushed that change to Git[1] to make sure we will not forget this. Roling back to dcmtk-3.6.7+really3.6.6 would remain an option anyway if this will be more convenient for you. Kind regards Andreas. [1] https://salsa.debian.org/med-team/dcmtk/-/commit/42df3f97b29e95646d2df5dc427cf03588664163 -- http://fam-tille.de
Bug#1010536: libdcmimage.so.16: cannot open shared object file: No such file or directory
Hi Andreas, Quoting Andreas Tille (2022-05-04 14:57:25) > > Will you take care of making sure that reverse dependencies are binNMU-ed? > > I admit I would use the chance to to real team uploads and check the > other dependencies manually. Your finding with ant makes me suspicious > about some of the other dependencies. However, what do you think about > asking ftpmaster for rejecting what is currently in new, re-upload 3.6.6 > to unstable and do a proper migration via experimental. Currently the > package is sitting in new and we have this chance. Or do you think it > is OK to force this "non-transition" somehow and leave things as they are > now? What does this mean from your blender perspective? I asked in #debian-release and Sebastian Ramacher writes: 15:27 < Sebastinas> libdcmtk17 will also need Breaks+Replaces on the libdcmtk16 version with the .so.17 files. 15:29 < Sebastinas> At least odil is involved in one ongoing transition, so the binNMU for icu may have broken that. 15:29 < Sebastinas> I'd appreciate a revert. So it seems that the right way forward would be an upload of dcmtk-3.6.7+really3.6.6. And then not forgetting the Breaks+Replaces from libdcmtk17 on libdcmtk16 (= 3.6.7-1) Thanks! cheers, josch signature.asc Description: signature
Bug#1010536: libdcmimage.so.16: cannot open shared object file: No such file or directory
Hi Johannes, Am Wed, May 04, 2022 at 12:22:50PM +0200 schrieb Johannes Schauer Marin Rodrigues: > Quoting Andreas Tille (2022-05-04 11:25:20) > > Aaargh, sorry for my sloppyness. I did not expect a SONAME bump connected > > with micro-Version bump. An updated package is in new. > > thanks a lot for this very quick fix! You are welcome and for sure I'm keen on fixing what I messed up before. > I think the problem is that package-name-doesnt-match-sonames is overridden > and > thus you didn't have Lintian tell you that there was a problem. That would've > probably have happened to me as well. Well, if I'm creating library packages I'm using d-shlibs which even breaks at build time in these cases. I would have even converted this package right now, but this does not work since no static library is build. I admit I simply underestimated the number of dependencies which I should habe checked. > Will you take care of making sure that reverse dependencies are binNMU-ed? I admit I would use the chance to to real team uploads and check the other dependencies manually. Your finding with ant makes me suspicious about some of the other dependencies. However, what do you think about asking ftpmaster for rejecting what is currently in new, re-upload 3.6.6 to unstable and do a proper migration via experimental. Currently the package is sitting in new and we have this chance. Or do you think it is OK to force this "non-transition" somehow and leave things as they are now? What does this mean from your blender perspective? Kind regards Andreas. -- http://fam-tille.de
Bug#1010340: git: Fails to clone and pull from existign repositories
Control: severity -1 important Hi Andrea, Andrea Palazzi wrote: > Turns out it'a Qemu issue: with -accel hax hardware acceleration I > have this error, if I use -accel tcg it works without issues. Interesting find, thanks for these details! > I think this bug report can ble closed then. Not sure, but it surely can be downgraded. Done so. The question is (and I can't answer that) if Debian generally supports running under these settings or if git has some (hopefully deactivatable) optimizations which fail under these settings. Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Processed: Re: Bug#1010340: git: Fails to clone and pull from existign repositories
Processing control commands: > severity -1 important Bug #1010340 [git] git: Fails to clone and pull from existign repositories Severity set to 'important' from 'grave' -- 1010340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1009998, tagging 923763
Processing commands for cont...@bugs.debian.org: > tags 1009998 - a11y Bug #1009998 [gvfs-backends] gvfs-backends: Unable to access smb://host/sharing on any file manager after upgrade Removed tag(s) a11y. > tags 923763 - a11y Bug #923763 [gvfs-backends] gvfs-backends: Cannot mount MTP mobile Device Removed tag(s) a11y. > thanks Stopping processing here. Please contact me if you need assistance. -- 1009998: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009998 923763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010558: jetty9: FTBFS An API incompatibility was encountered while executing org.apache.maven.plugins:maven-assembly-plugin
Package: jetty9 Version: 9.4.46-1 Severity: serious X-Debbugs-Cc: a...@debian.org Hi, I have just discovered that jetty9 fails to build from source. An API incompatibility was encountered while executing org.apache.maven.plugins:maven-assembly-plugin Probably some recently upgraded reverse-dependency is to blame here. Markus
Processed: src:zd1211-firmware: fails to migrate to testing for too long: non-free doesn't autobuild by default
Processing control commands: > close -1 1:1.5-8 Bug #1010557 [src:zd1211-firmware] src:zd1211-firmware: fails to migrate to testing for too long: non-free doesn't autobuild by default The source 'zd1211-firmware' and version '1:1.5-8' do not appear to match any binary packages Marked as fixed in versions zd1211-firmware/1:1.5-8. Bug #1010557 [src:zd1211-firmware] src:zd1211-firmware: fails to migrate to testing for too long: non-free doesn't autobuild by default Marked Bug as done -- 1010557: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010557 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010557: src:zd1211-firmware: fails to migrate to testing for too long: non-free doesn't autobuild by default
Source: zd1211-firmware Version: 1:1.5-7 Severity: serious Control: close -1 1:1.5-8 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:zd1211-firmware has been trying to migrate for 61 days [2]. Hence, I am filing this bug. Your package is in the non-free part of the archive where packages don't get automatically build. Although I appreciate we normally upload source only, that doesn't happen by default work for non-free, albeit in some cases that can be "fixed" [3]. If [3] doesn't work for you, please upload a self built binary (you don't need to upload source in that case). If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=zd1211-firmware [3] https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#marking-non-free-packages-as-auto-buildable OpenPGP_signature Description: OpenPGP digital signature
Processed: Re: undefined symbol extract_begin
Processing control commands: > severity -1 grave Bug #1010556 [qpdfview-pdf-mupdf-plugin] undefined symbol extract_begin Severity set to 'grave' from 'important' -- 1010556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#986709: rsnapshot is stable, not dead
Dear maintainer, could you please give some hints, why you actually think the package is unmaintainable or whre we can find information about this? This would be usefull for everyone considering to adopt it.
Bug#1010536: libdcmimage.so.16: cannot open shared object file: No such file or directory
Hi Andreas, Quoting Andreas Tille (2022-05-04 11:25:20) > Aaargh, sorry for my sloppyness. I did not expect a SONAME bump connected > with micro-Version bump. An updated package is in new. thanks a lot for this very quick fix! I think the problem is that package-name-doesnt-match-sonames is overridden and thus you didn't have Lintian tell you that there was a problem. That would've probably have happened to me as well. Will you take care of making sure that reverse dependencies are binNMU-ed? Thanks! cheers, josch signature.asc Description: signature
Bug#1010536: libdcmimage.so.16: cannot open shared object file: No such file or directory
Hi,
Am Wed, May 04, 2022 at 10:56:57AM +0200 schrieb Johannes Schauer Marin
Rodrigues:
> > I'm going to rebuild all reverse dependencies and see if anything breaks
> > and report back to you in case I find any FTBFS caused by the new dcmtk
> > version.
>
> the following source package build depend on libdcmtk-dev:
>
> aeskulap, amide, ants, biosig, cmtk, dicomscope, elastix, insighttoolkit4,
> insighttoolkit5, itksnap, mia, odil, odin, openimageio, orthanc, orthanc-wsi,
> plastimatch
>
> I cannot test insighttoolkit4 or insighttoolkit5 because my system lacks the
> resources to successfully build either source package (No space left on
> device).
This is really a hard one.
> ants FTBFS but is broken beyond repair and hasn't been in testing since 2017.
I'd vote for a removal of ants.
> itksnap FTBFS for for an unrelated reason (#1010549).
>
> plastimatch FTBFS because of a missing build dependency on
> libinsighttoolkit5-dev:
> https://buildd.debian.org/status/package.php?p=plastimatch
>
> It seems the new dcmtk version did not just bump ABI but also changed its API
> (the DcmTransportLayerStatus enum including TCS_ok was removed from dcmlayer.h
> and defining INCLUDE_{CSTRING,CSTDLIB,CSTDIO} now raises an error), so some
> patches were necessary:
>
> biosig: #1010545
> orthanc: #1010554
>
> Mathieu, since you filed #1010474 (upgrading dcmtk to 3.6.7) could you help
> clean this up?
I wished some warning would have been added. I'm not that involved into
those medical imaging tools and a deeply regret that I have messed up things
that heavily.
> For example maybe you find a solution to get orthanc to
> successfully compile again (I X-Debbugs-Cc-ed you on the last bug). Currently,
> the testsuite fails with:
>
> /usr/bin/ld:
> /usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libdcmdata.so:
> undefined reference to symbol 'inflateEnd'
> /usr/bin/ld: /lib/x86_64-linux-gnu/libz.so.1: error adding symbols: DSO
> missing from command line
> collect2: error: ld returned 1 exit status
>
> Which may be something that we have to fix in dcmtk?
Mathieu, could you say something about this? Wouldn't it be better
to upload dcmtk-3.6.7+really3.6.6 and go a more sensible route?
> Note, that I'm not a Debian Med team member. I'm just putting my time here,
> because the last dcmtk upload broke blender (because it depends on
> openimageio)
> which in turn hampers my work on the MNT Reform system image. So for me this
> is
> just one big yak shave...
I can absolutely understand your situation. Medical imaging is also
kind of yak shaving for me - well, may be re-shaving by updating
packages others prepared. But obviously I'm trapping fully into wide
open pitfalls.
Sorry again to pull several people into this
Andreas.
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging
--
http://fam-tille.de
Bug#1010536: libdcmimage.so.16: cannot open shared object file: No such file or directory
Control: tags -1 pending Aaargh, sorry for my sloppyness. I did not expect a SONAME bump connected with micro-Version bump. An updated package is in new. Kind regards Andreas. -- http://fam-tille.de
Processed: Re: Bug#1010536: libdcmimage.so.16: cannot open shared object file: No such file or directory
Processing control commands: > tags -1 pending Bug #1010536 [src:dcmtk] libdcmimage.so.16: cannot open shared object file: No such file or directory Added tag(s) pending. -- 1010536: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010536 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1010536: libdcmimage.so.16: cannot open shared object file: No such file or directory
Hi,
On Tue, 03 May 2022 22:17:24 +0200 Johannes Schauer Marin Rodrigues
wrote:
> thanks for your upload of the new upstream version of dcmtk. Unfortunately,
> I think this is missing a proper transition because the ABI and thus the
> SONAME changed. This can also be seen in the autopkgtests of biosig, odil and
> odin which all fail with a similar error right now:
>
> biosig & odil: ImportError: libdcmdata.so.16: cannot open shared object file:
> No such file or directory
>
> odin: gencoil: error while loading shared libraries: libdcmimgle.so.16:
> cannot open shared object file: No such file or directory
>
> This is because the new upstream version bumped the SONAME from 16 to
> 17. This means, that the binary package name should also change from
> libdcmtk16 to libdcmtk17. This probably would've been caught by
> lintian if package-name-doesnt-match-sonames wasn't overridden in
> debian/libdcmtk16.lintian-overrides... :/
>
> The package should've probably first been uploaded to experimental,
> would go through binary-NEW and create a auto-dcmtk transition. I'm
> unsure how to clean this up now that the package has already been
> uploaded to unstable.
>
> I'm going to rebuild all reverse dependencies and see if anything breaks
> and report back to you in case I find any FTBFS caused by the new dcmtk
> version.
the following source package build depend on libdcmtk-dev:
aeskulap, amide, ants, biosig, cmtk, dicomscope, elastix, insighttoolkit4,
insighttoolkit5, itksnap, mia, odil, odin, openimageio, orthanc, orthanc-wsi,
plastimatch
I cannot test insighttoolkit4 or insighttoolkit5 because my system lacks the
resources to successfully build either source package (No space left on
device).
ants FTBFS but is broken beyond repair and hasn't been in testing since 2017.
itksnap FTBFS for for an unrelated reason (#1010549).
plastimatch FTBFS because of a missing build dependency on
libinsighttoolkit5-dev:
https://buildd.debian.org/status/package.php?p=plastimatch
It seems the new dcmtk version did not just bump ABI but also changed its API
(the DcmTransportLayerStatus enum including TCS_ok was removed from dcmlayer.h
and defining INCLUDE_{CSTRING,CSTDLIB,CSTDIO} now raises an error), so some
patches were necessary:
biosig: #1010545
orthanc: #1010554
Mathieu, since you filed #1010474 (upgrading dcmtk to 3.6.7) could you help
clean this up? For example maybe you find a solution to get orthanc to
successfully compile again (I X-Debbugs-Cc-ed you on the last bug). Currently,
the testsuite fails with:
/usr/bin/ld:
/usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libdcmdata.so:
undefined reference to symbol 'inflateEnd'
/usr/bin/ld: /lib/x86_64-linux-gnu/libz.so.1: error adding symbols: DSO missing
from command line
collect2: error: ld returned 1 exit status
Which may be something that we have to fix in dcmtk?
Note, that I'm not a Debian Med team member. I'm just putting my time here,
because the last dcmtk upload broke blender (because it depends on openimageio)
which in turn hampers my work on the MNT Reform system image. So for me this is
just one big yak shave...
Thanks!
cheers, josch
signature.asc
Description: signature
Bug#1010554: orthanc: FTBFS with dcmtk >= 3.6.7
Source: orthanc
Version: 1.10.1+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: jo...@debian.org, ma...@debian.org
Hi,
orthanc FTBFS with dcmtk 3.6.7 from unstable:
/<>/OrthancFramework/Sources/DicomNetworking/Internals/DicomTls.cpp:110:118:
error: ‘TCS_ok’ was
not declared in this scope
110 | if
(tls->addTrustedCertificateFile(trustedCertificatesPath.c_str(),
DCF_Filetype_PEM /*opt_keyFi
leFormat*/) != TCS_ok)
|
^~
/<>/OrthancFramework/Sources/DicomNetworking/Internals/DicomTls.cpp:116:104:
error: ‘TCS_ok’ was
not declared in this scope
116 | if (tls->setPrivateKeyFile(ownPrivateKeyPath.c_str(),
DCF_Filetype_PEM /*opt_keyFileFormat*/) !=
TCS_ok)
|
^~
/<>/OrthancFramework/Sources/DicomNetworking/Internals/DicomTls.cpp:122:106:
error: ‘TCS_ok’ was
not declared in this scope
122 | if (tls->setCertificateFile(ownCertificatePath.c_str(),
DCF_Filetype_PEM /*opt_keyFileFormat*/)
!= TCS_ok)
|
^~
/<>/OrthancFramework/Sources/DicomNetworking/Internals/DicomTls.cpp:135:72:
error: ‘TCS_ok’ was n
ot declared in this scope
135 | if (tls->setTLSProfile(TSP_Profile_BCP195 /*opt_tlsProfile*/) !=
TCS_ok)
|
^~
/<>/OrthancFramework/Sources/DicomNetworking/Internals/DicomTls.cpp:140:36:
error: could not convert ‘DcmTLSTransportLayer::activateCipherSuites()()’ from
‘OFCondition’ to ‘bool’
140 | if (tls->activateCipherSuites())
| ~^~
||
|OFCondition
make[4]: *** [CMakeFiles/OrthancFramework.dir/build.make:1941:
CMakeFiles/OrthancFramework.dir/<>/OrthancFramework/Sources/DicomNetworking/Internals/DicomTls.cpp.o]
Error 1
The attached debdiff fixes above problem but the testsuite still fails with:
[100%] Linking CXX executable UnitTests
/usr/bin/ld:
/usr/lib/gcc/x86_64-linux-gnu/11/../../../x86_64-linux-gnu/libdcmdata.so:
undefined reference to symbol 'inflateEnd'
/usr/bin/ld: /lib/x86_64-linux-gnu/libz.so.1: error adding symbols: DSO missing
from command line
collect2: error: ld returned 1 exit status
Maybe this has to be fixed in dcmtk but I'm not sure. Because my patch
is not complete I'm not tagging this bug with patch.
Thanks!
cheers, josch
diff -Nru orthanc-1.10.1+dfsg/debian/changelog
orthanc-1.10.1+dfsg/debian/changelog
--- orthanc-1.10.1+dfsg/debian/changelog2022-03-23 21:05:58.0
+0100
+++ orthanc-1.10.1+dfsg/debian/changelog2022-05-04 10:13:08.0
+0200
@@ -1,3 +1,10 @@
+orthanc (1.10.1+dfsg-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * add patch to build with dcmtk >= 3.6.7 (closes: #XXX)
+
+ -- Johannes Schauer Marin Rodrigues Wed, 04 May 2022
10:13:08 +0200
+
orthanc (1.10.1+dfsg-1) unstable; urgency=medium
* New upstream version
diff -Nru orthanc-1.10.1+dfsg/debian/patches/dcmtk-3.6.7
orthanc-1.10.1+dfsg/debian/patches/dcmtk-3.6.7
--- orthanc-1.10.1+dfsg/debian/patches/dcmtk-3.6.7 1970-01-01
01:00:00.0 +0100
+++ orthanc-1.10.1+dfsg/debian/patches/dcmtk-3.6.7 2022-05-04
10:13:08.0 +0200
@@ -0,0 +1,40 @@
+--- a/OrthancFramework/Sources/DicomNetworking/Internals/DicomTls.cpp
b/OrthancFramework/Sources/DicomNetworking/Internals/DicomTls.cpp
+@@ -107,19 +107,19 @@ namespace Orthanc
+ new DcmTLSTransportLayer(tmpRole /*opt_networkRole*/, NULL
/*opt_readSeedFile*/,
+ OFFalse /*initializeOpenSSL, done by
Orthanc::Toolbox::InitializeOpenSsl()*/));
+
+- if (tls->addTrustedCertificateFile(trustedCertificatesPath.c_str(),
DCF_Filetype_PEM /*opt_keyFileFormat*/) != TCS_ok)
++ if (tls->addTrustedCertificateFile(trustedCertificatesPath.c_str(),
DCF_Filetype_PEM /*opt_keyFileFormat*/).bad())
+ {
+ throw OrthancException(ErrorCode_BadFileFormat, "Cannot parse PEM
file with trusted certificates for DICOM TLS: " +
+trustedCertificatesPath);
+ }
+
+- if (tls->setPrivateKeyFile(ownPrivateKeyPath.c_str(), DCF_Filetype_PEM
/*opt_keyFileFormat*/) != TCS_ok)
++ if (tls->setPrivateKeyFile(ownPrivateKeyPath.c_str(), DCF_Filetype_PEM
/*opt_keyFileFormat*/).bad())
+ {
+ throw OrthancException(ErrorCode_BadFileFormat, "Cannot parse PEM
file with private key for DICOM TLS: " +
+ownPrivateKeyPath);
+ }
+
+- if (tls->setCertificateFile(ownCertificatePath.c_str(),
DCF_Filetype_PEM /*opt_keyFileFormat*/) != TCS_ok)
++ if (tls->setCertificateFile(ownCertificatePath.c_str(),
DCF_Filetype_PEM /*opt_keyFileFormat*/).bad())
+ {
+ throw OrthancException(ErrorCode_BadFileFormat, "Cannot parse PEM
file with own certificate for DICOM TLS: " +
+
Processed: testing's version works fine with the libgit2 in testing.
Processing commands for cont...@bugs.debian.org:
> tags 1009034 +sid
Bug #1009034 {Done: Peter Michael Green }
[src:rust-libgit2-sys] rust-libgit2-sys: FTBFS with libgit2 1.3.0
Added tag(s) sid.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1009034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009034
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
