Bug#1011913: haskell-swish: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
On Sat, 28 May 2022, Jonas Smedegaard wrote: Control: reassign -1 haskell-devscripts Control: retitle -1 haskell-devscripts: DEB_ENABLE_TESTS ignored Control: affects -1 haskell-swish Quoting Lucas Nussbaum (2022-05-26 21:04:50) During a rebuild of all packages in sid, [haskell-swish] failed to build on amd64. [...] Running debian/hlibrary.setup test --builddir=dist-ghc --show-details=direct Non-zero exit code 1. hlibrary.setup: No test suites enabled. Did you remember to configure with '--enable-tests'? haskell-swish built successfully when released in January, and contains this in debian/rules: DEB_ENABLE_TESTS = yes Perhaps this really is bug#1010179 and the "fix" only papered over the underlying problem: @Scott, did you test packages _enabling_ tests or only the default of having tests disabled? Hi Jonas, Actually, it looks like DEB_ENABLE_TESTS=yes had been broken in haskell-devscripts for quite some time (even before Felix's changes). If you look at the January build log for haskell-swish, the tests were not run at that time. In the case of haskell-swish, DEB_ENABLE_TESTS needs to be defined *before* including hlibrary.mk. After fixing that, it seems there are some missing test dependencies. Scott
Bug#1002864: marked as done (FTBFS with webpack5: Cannot find uglifyjs-webpack-plugin)
Your message dated Sat, 28 May 2022 22:28:42 +
with message-id
and subject line Bug#1002864: fixed in node-source-map
0.7.0++dfsg2+really.0.6.1-10
has caused the Debian Bug report #1002864,
regarding FTBFS with webpack5: Cannot find uglifyjs-webpack-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.)
--
1002864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002864
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-source-map
Version: 0.7.0++dfsg2+really.0.6.1-9
Severity: important
Justification: ftbfs
Tags: ftbfs
User: pkg-javascript-de...@alioth-lists.debian.net
Usertags: webpack5
Hi,
We are starting to build against webpack5 in experimental and the
package needed for local build is webpack and node-webpack-source from
experimental.
During a test rebuild, node-source-map was found to fail to build in
that situation.
Relevant part (hopefully):
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
mkdir -p dist
webpack --mode development
[webpack-cli] Failed to load '/<>/webpack.config.js' config
[webpack-cli] Error: Cannot find module 'uglifyjs-webpack-plugin'
Require stack:
- /<>/webpack.config.js
- /usr/share/nodejs/webpack-cli/lib/webpack-cli.js
- /usr/share/nodejs/webpack-cli/lib/bootstrap.js
- /usr/share/nodejs/webpack-cli/bin/cli.js
- /usr/share/nodejs/webpack/bin/webpack.js
at Function.Module._resolveFilename
(internal/modules/cjs/loader.js:815:15)
at Function.Module._load (internal/modules/cjs/loader.js:667:27)
at Module.require (internal/modules/cjs/loader.js:887:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object. (/<>/webpack.config.js:5:22)
at Module._compile (internal/modules/cjs/loader.js:999:30)
at Object.Module._extensions..js
(internal/modules/cjs/loader.js:1027:10)
at Module.load (internal/modules/cjs/loader.js:863:32)
at Function.Module._load (internal/modules/cjs/loader.js:708:14)
at Module.require (internal/modules/cjs/loader.js:887:19) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'/<>/webpack.config.js',
'/usr/share/nodejs/webpack-cli/lib/webpack-cli.js',
'/usr/share/nodejs/webpack-cli/lib/bootstrap.js',
'/usr/share/nodejs/webpack-cli/bin/cli.js',
'/usr/share/nodejs/webpack/bin/webpack.js'
]
}
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:8: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit
status 2
The full log is attached to this mail
sbuild (Debian sbuild) 0.81.2 (31 January 2021) on Ayoyimika-PC.localdomain
+=+
| node-source-map 0.7.0++dfsg2+really.0.6.1-9 (amd64) Thu, 30 Dec 2021 10:05:21
+ |
+=+
Package: node-source-map
Version: 0.7.0++dfsg2+really.0.6.1-9
Source Version: 0.7.0++dfsg2+really.0.6.1-9
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary
I: NOTICE: Log filtering will replace
'var/run/schroot/mount/unstable-amd64-sbuild-720298ea-a666-4cb3-b3f7-3d35279ab4a4'
with '<>'
I: NOTICE: Log filtering will replace
'build/node-source-map-n5FNQG/resolver-XK85C7' with '<>'
+--+
| Update chroot|
+--+
Get:1 file:/build/node-source-map-n5FNQG/resolver-BYIqdH/apt_archive ./
InRelease
Ign:1 file:/build/node-source-map-n5FNQG/resolver-BYIqdH/apt_archive ./
InRelease
Get:2 file:/build/node-source-map-n5FNQG/resolver-BYIqdH/apt_archive ./ Release
[951 B]
Get:2 file:/build/node-source-map-n5FNQG/resolver-BYIqdH/apt_archive ./ Release
[951 B]
Get:3 file:/build/node-source-map-n5FNQG/resolver-BYIqdH/apt_archive ./
Release.gpg
Ign:3 file:/build/node-source-map-n5FNQG/resolver-BYIqdH/apt_archive ./
Release.gpg
Get:4 file:/build/node-source-map-n5FNQG/resolver-BYIqdH/apt_archive ./
Packages [798 B]
Err:4 file:/build/node-source-map-n5FNQG/resolver-BYIqdH/apt_archive ./ Packages
Could not open file
/build/node-source-map-n5FNQG/resolver-BYIqdH/apt_archive/./Packages - open
(13: Permission denied)
Get:4 file:/build/node-source-map-n5FNQG/resolver-BYIqdH/apt_archive ./
Packages [1381 B]
Get:5 http://deb.debian.org/debian unstable InRelease [165 kB]
Get:6
Bug#1005873: marked as done (gbp 0.9.26 will break dgit --gbp)
Your message dated Sat, 28 May 2022 22:22:54 + with message-id and subject line Bug#1005873: fixed in dgit 9.16 has caused the Debian Bug report #1005873, regarding gbp 0.9.26 will break dgit --gbp 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.) -- 1005873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: git-buildpackage Version: 0.9.25 Severity: normal I ran "gbp pq import" on my main branch, but had forgotten to commit some staged changes first. The command failed, as there was an issue with debian/patches/series. However, the changes in staging were all lost: the repository was effectively hard-reset back to HEAD. There was no warning about this. I would suggest that the command should abort without doing anything if there are uncommitted changes. Best wishes, Julian --- End Message --- --- Begin Message --- Source: dgit Source-Version: 9.16 Done: Ian Jackson We believe that the bug you reported is fixed in the latest version of dgit, 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 1005...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ian Jackson (supplier of updated dgit 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: Sat, 28 May 2022 22:49:53 +0100 Source: dgit Architecture: source Version: 9.16 Distribution: unstable Urgency: medium Maintainer: Ian Jackson Changed-By: Ian Jackson Closes: 1005873 Changes: dgit (9.16) unstable; urgency=medium . Compatibility with git-buildpackage gbp pq 0.9.26 (Closes:#1005873): * dgit: Move .pc aside while running gbp pq import * git-debrebase: convert-from-dgit-view: Disable ignore-new where needed . Other changes: * Fix typo in changelog for 9.14, noting that we closed #987304. * playtrees (for dgit and git-debrebase): Provide a gbp.conf. * tests: gdr: Provide a way to pass --diagnose. Checksums-Sha1: 1b932496b1fa6a22b83bcf102d51ee8eb32f7111 1846 dgit_9.16.dsc 10e422b0d9e84ce63f2760b05b385e6e34bf71b1 667789 dgit_9.16.tar.gz Checksums-Sha256: 6f1835bf791dbf17270d25fa71f3f015c42cff5040e47f68177b8fc6249482f4 1846 dgit_9.16.dsc 253e0d053a3ea9341e57f6c07ca9039bdd69461da4e779ae3fe131034d34fd76 667789 dgit_9.16.tar.gz Files: b90d3a397851f449a67fdb78012cfaa5 1846 devel optional dgit_9.16.dsc 853328a2aa06c113500e019b491daa80 667789 devel optional dgit_9.16.tar.gz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEVZrkbC1rbTJl58uh4+M5I0i1DTkFAmKSmTUACgkQ4+M5I0i1 DTmgwAgAnLEhnWdQA1Bvmdi2hr/5Ix+lvmQtVpWvxFkhQJ7Ba17siBnTad5tpv1A GDjZAnRvpcAZ0fdCeg9EG42ro5GpGspmI18UixiqjeaSE8SyD848cxsA7jzzPPs2 tkQ3KlgAzqM5NeObWLdY4D2726Sft/tyy19JMeQFd+AbkTPabXKNPtL0mCgs8rJi IiubLlFuaZeXGM6anDNb8ioYb+EPFMRtLDVJWvXb81xA+yIS1A5Yjnm0S+6IXUOK 0YJJohcwBrb9tx0Zq5/wIyEUaTmT74iGrU0RYPhcLVxHhtcvhpxDN55vVxR/WTTp XnAN9XWjMrHpzI3/paRP7+XM///W6A== =SvBr -END PGP SIGNATURE End Message ---
Bug#1012024: Please declare Breaks: dgit (<< 9.16~)
Package: git-buildpackage Version: 0.9.26 Severity: serious Hi. With recent gbp pq (as of 0.9.26), dgit needs to pass new options (well, actually, it does this via the config file so as to still work with older gbp). That's #1005873. dgit 9.16 which I have just uploaded does this (again, sorry for the delay). It passes my formal autopkgtest with my sid chroot so I expect it will be OK in ci.d.n. As I wrote in another mail, I would appreciate it if you would add to git-buildpackage: Breaks: dgit (<< 9.16~) This will arrange that users will necessarily install the updates in the correct order (and that partial updates will be correct). I am filing this bug as "serious" not because I think it is RC, but because if you agree with my suggestion, it would be good to prevent gbp 0.9.26 migrating to testing, since it is that version that presents the upgrade hazard, and instead migrate the updated version with the Breaks (presumably 0.9.27). That would avoid a window of opportunity for lossage. If you disagree with my choice of severity, do of course feel free to downgrade it. Regards, Ian. -- Ian JacksonThese opinions are my own. Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter. -- Ian JacksonThese opinions are my own. Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
Bug#1005873: [git-buildpackage/master] pq: Check if repo is clean before importing patches
Paul Gevers writes ("Bug#1005873: [git-buildpackage/master] pq: Check if repo
is clean before importing patches"):
> Control: severity -1 serious
...
> Seems like the autopkgtest of dgit is now blocking progression of
> git-buildpackage related to this change.
Thanks for escalating this. I had dropped the ball. I have uploaed a
fixed version of dgit which I hope will sort this out.
Thanks,
Ian.
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
Bug#1011041: marked as done (freeradius FTBFS with OpenSSL 3.0)
Your message dated Sat, 28 May 2022 21:19:33 +
with message-id
and subject line Bug#1011041: fixed in freeradius 3.2.0+dfsg-1
has caused the Debian Bug report #1011041,
regarding freeradius FTBFS with OpenSSL 3.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.)
--
1011041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011041
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: freeradius
Version: 3.0.25+dfsg-1.1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=freeradius=3.0.25%2Bdfsg-1.1%2Bb1
...
src/main/tls.c: In function ‘load_dh_params’:
src/main/tls.c:1701:13: warning: implicit declaration of function ‘FIPS_mode’
[-Wimplicit-function-declaration]
1701 | if (FIPS_mode() > 0) {
| ^
...
LINK build/bin/radwho
build/make/jlibtool --silent --mode=link gcc -o build/bin/radwho -rpath
/usr/lib/freeradius -Wl,-z,relro -Wl,-z,now build/objs/src/main/radwho.lo
build/lib/libfreeradius-server.la build/lib/libfreeradius-radius.la -lcrypto
-lssl -ltalloc -latomic -lpcre -lcap -lnsl -lresolv -ldl -lpthread -lreadline
/usr/bin/ld: build/objs/src/main/tls.o: in function `load_dh_params':
./src/main/tls.c:1701: undefined reference to `FIPS_mode'
collect2: error: ld returned 1 exit status
make[2]: *** [scripts/boiler.mk:639: build/bin/radiusd] Error 1
--- End Message ---
--- Begin Message ---
Source: freeradius
Source-Version: 3.2.0+dfsg-1
Done: Bernhard Schmidt
We believe that the bug you reported is fixed in the latest version of
freeradius, 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 1011...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bernhard Schmidt (supplier of updated freeradius package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 28 May 2022 22:24:26 +0200
Source: freeradius
Architecture: source
Version: 3.2.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian FreeRADIUS Packaging Team
Changed-By: Bernhard Schmidt
Closes: 1011041
Changes:
freeradius (3.2.0+dfsg-1) unstable; urgency=medium
.
* Acknowledge NMU, thanks Andreas Metzler
* New upstream version 3.2.0+dfsg (Closes: #1011041)
- Drop rlm_{cram,otp} (removed upstream), add rlm_json
* Refresh d/p/snakeoil-certs.diff
* Refresh d/p/python_config_script_update.diff
* Import test updates from Ubuntu, thanks Andreas Hasenack
- Add test for rlm_python3 (LP: #1969381):
- d/t/control: new rlm_python3 test
- d/t/rlm_python3-test: test the rlm_python3 module
- d/t/rlm_python3-data/*: test files
- d/t/freeradius: run python tests in verbose mode
- d/t/test-freeradius.py: test more authentication mechanisms
Checksums-Sha1:
8c57643808422862177bb60f3c07ccbfa84035e2 3608 freeradius_3.2.0+dfsg-1.dsc
d9726fe3188752f11ba928204d21d00ce460094c 1945280
freeradius_3.2.0+dfsg.orig.tar.xz
1ac15e55ba528756f0519e90ae3bb0ea24e6d10a 84968
freeradius_3.2.0+dfsg-1.debian.tar.xz
dbff28b0b7a899e229eed775fc22b7b3ea184e85 19323
freeradius_3.2.0+dfsg-1_amd64.buildinfo
Checksums-Sha256:
75586dc9e5792ad46bd662ccb63bf7316fbcb56a0aa976b423b07adfd944aef5 3608
freeradius_3.2.0+dfsg-1.dsc
4eb17f67f3a1c2db9284dde02890d81db505c13a0f466ca79cb1a991c3c15702 1945280
freeradius_3.2.0+dfsg.orig.tar.xz
fa35d30d320eb2948780aaa8f98ba63a1012fd8b01b5f461e50c64d1789cab5b 84968
freeradius_3.2.0+dfsg-1.debian.tar.xz
5507c7d5ba1a85bee714a266f566cfe4c6235b15e60b3e362c48c26d97f8a84a 19323
freeradius_3.2.0+dfsg-1_amd64.buildinfo
Files:
5c7b96088fb334c1bfbd459a954fa748 3608 net optional freeradius_3.2.0+dfsg-1.dsc
b69d3a81b10e2ef373bf8ce35591bbb3 1945280 net optional
freeradius_3.2.0+dfsg.orig.tar.xz
6d5375ea2ed75e887827e91bf7e9b6ad 84968 net optional
freeradius_3.2.0+dfsg-1.debian.tar.xz
29c4e48de0b7040a0a503cd7d91a63ba 19323 net optional
freeradius_3.2.0+dfsg-1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJFBAEBCgAvFiEE1uAexRal3873GVbTd1B55bhQvJMFAmKSjKURHGJlcm5pQGRl
Ymlhbi5vcmcACgkQd1B55bhQvJNAGg/9HAhIHfokbY9yFZQVENIAUmMOBULxfgQ7
UGnpdd2BWSDPf6vtrVOZqCVAVSqhOU8RyKZnsIxklHqkkEcqMi8JK0cgDD/DccEN
Bug#994736: marked as done (libmath-gsl-perl: FTBFS on several architectures: undefined symbol: gsl_matrix_char_norm1)
Your message dated Sat, 28 May 2022 21:04:00 + with message-id and subject line Bug#994736: fixed in libmath-gsl-perl 0.43-4 has caused the Debian Bug report #994736, regarding libmath-gsl-perl: FTBFS on several architectures: undefined symbol: gsl_matrix_char_norm1 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.) -- 994736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libmath-gsl-perl Version: 0.43-1 Severity: serious Tags: ftbfs This package failed to build on several architectures. >From >https://buildd.debian.org/status/fetch.php?pkg=libmath-gsl-perl=arm64=0.43-1=1632072156=0 # Failed test 'use Math::GSL::Matrix;' # at t/00-load.t line 14. # Tried to use 'Math::GSL::Matrix'. # Error: Can't load '/<>/blib/arch/auto/Math/GSL/Matrix/Matrix.so' for module Math::GSL::Matrix: /<>/blib/arch/auto/Math/GSL/Matrix/Matrix.so: undefined symbol: gsl_matrix_char_norm1 at /usr/lib/aarch64-linux-gnu/perl-base/DynaLoader.pm line 187. # at /<>/blib/lib/Math/GSL/Matrix.pm line 11. # Compilation failed in require at t/00-load.t line 14. # BEGIN failed--compilation aborted at t/00-load.t line 14. [...] Test Summary Report --- t/00-load.t (Wstat: 512 Tests: 56 Failed: 2) Failed tests: 7, 54 Non-zero exit status: 2 t/BLAS.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 109 tests but ran 0. t/Eigen.t(Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: Bad plan. You planned 59 tests but ran 0. t/GSL.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output t/Linalg.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output t/Matrix.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output t/Multifit.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output t/Multilarge.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output t/SparseMatrix.t (Wstat: 512 Tests: 0 Failed: 0) Non-zero exit status: 2 Parse errors: No plan found in TAP output Files=58, Tests=3449, 22 wallclock secs ( 1.15 usr 0.22 sys + 19.59 cusr 2.07 csys = 23.03 CPU) Result: FAIL -- Niko --- End Message --- --- Begin Message --- Source: libmath-gsl-perl Source-Version: 0.43-4 Done: Damyan Ivanov We believe that the bug you reported is fixed in the latest version of libmath-gsl-perl, 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 994...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Damyan Ivanov (supplier of updated libmath-gsl-perl 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: Sat, 28 May 2022 20:47:46 + Source: libmath-gsl-perl Architecture: source Version: 0.43-4 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: Damyan Ivanov Closes: 994736 Changes: libmath-gsl-perl (0.43-4) unstable; urgency=medium . * exclude all symbols that are missing on arm64 assuming the other failing architectures fail for the same reazon (Closes: #994736) Checksums-Sha1: d9fceb0955b9ce78773d4bda04537bc80796c561 2292 libmath-gsl-perl_0.43-4.dsc 1dfe72367d2a9949efa51e5fd1cbe2abc6adaf23 23612 libmath-gsl-perl_0.43-4.debian.tar.xz Checksums-Sha256: 4e71cb16e1b1963155d469c812e2ae06d215104fbb6667c94fbb7bf3c906b1ca 2292 libmath-gsl-perl_0.43-4.dsc 937d13b53bd24ebf006873e2b964323b72c0ab658cd086b43c8f6533ca9f70ac 23612 libmath-gsl-perl_0.43-4.debian.tar.xz Files: ab393eb8d46291584c1f4b11d5803bbd 2292 perl optional libmath-gsl-perl_0.43-4.dsc cc3c7bf7974d1a0f053e3e91a156bb9d 23612 perl optional libmath-gsl-perl_0.43-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEErqDETssFbpNjDZ0z276dTZnSoAQFAmKSjAgACgkQ276dTZnS oASRvQ//XO8zZyn/gmzO+bkeq1mcaExejXmq6DUrapbymlCY2icyD+2hj1FmNJlx
Bug#1011973: marked as done (node-webpack-sources: autopkgtest failure TypeError: addMapping is not a function )
Your message dated Sat, 28 May 2022 21:05:31 + with message-id and subject line Bug#1011973: fixed in node-webpack-sources 3.2.1-4 has caused the Debian Bug report #1011973, regarding node-webpack-sources: autopkgtest failure TypeError: addMapping is not a function 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.) -- 1011973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-webpack-sources Version: 3.2.1-3 Severity: serious Control: block -1 by 1004658 Control: tags -1 help Autopkgtest is failing as it needs node-source-map 0.7 and that is blocked by mismatch in embedded and built from source wasm file. This is blocking webpack 5 migration to testing. https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-webpack-sources/22182585/log.gz -- Sent from my Android device with K-9 Mail. Please excuse my brevity.--- End Message --- --- Begin Message --- Source: node-webpack-sources Source-Version: 3.2.1-4 Done: Pirate Praveen We believe that the bug you reported is fixed in the latest version of node-webpack-sources, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pirate Praveen (supplier of updated node-webpack-sources package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 29 May 2022 01:54:55 +0530 Source: node-webpack-sources Architecture: source Version: 3.2.1-4 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Pirate Praveen Closes: 1011973 Changes: node-webpack-sources (3.2.1-4) unstable; urgency=medium . * Add lib/helpers/__mocks__ to debian/tests/pkg-js/files * Install lib/helpers/__mocks__ (adding to debian/tests/pkg-js/files didn't work) (Closes: #1011973) Checksums-Sha1: 54c5bcfc6e461cdc409d57e8320aa1f7ce0d9527 2145 node-webpack-sources_3.2.1-4.dsc aec3a59afd867d62724cc18413bd8b39e59d74b1 5776 node-webpack-sources_3.2.1-4.debian.tar.xz 04ad0fbe69cafb265661fbd7e30bb13bdab32183 17405 node-webpack-sources_3.2.1-4_amd64.buildinfo Checksums-Sha256: 87e19ddd64d27314db701930e23024483a285a37948fb3258d93c92e41bc5730 2145 node-webpack-sources_3.2.1-4.dsc fd9abf0e778032f9a7ecdda7ff9cf2463cda6f1d49cb7082fa56dfa7f5757d82 5776 node-webpack-sources_3.2.1-4.debian.tar.xz 31a8a725872d50a53a7d1d0e550181d03cab62cba5705b06fc24da3aa7ecb3c9 17405 node-webpack-sources_3.2.1-4_amd64.buildinfo Files: 75760b2d893e8d18fd18f884bb8fc652 2145 javascript optional node-webpack-sources_3.2.1-4.dsc 9a9032da191dff1a942cf05c5f65b4d3 5776 javascript optional node-webpack-sources_3.2.1-4.debian.tar.xz 072e5a6b3ab047b591490843533f7e71 17405 javascript optional node-webpack-sources_3.2.1-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0whj4mAg5UP0cZqDj1PgGTspS3UFAmKSiEkACgkQj1PgGTsp S3V7ohAAoqu+EuvxymaOXEbwLfJLvNPFUDwViY420GgNol8BU7Fwu+dMcHuiNZpX sWPks3W527W5lEJkAGDCDGPbTKOtM5DhyNZ0TSp/lTumNxOv9Z3S+rSz+uikjhif CJNYECa1skOFstO9Jy5FMFGRvdf3MkuN4JFMjhCIp1eUcGLCTtzTaxvvTEY7tyG2 qzYSqP8aHkQTxmQueFfDUk8MYa+QLSlaVY3eCenEqRxjae0Usdfy80skg5frh86x VMLdxaUoAMhhJrL29XTShlCorV/OjaLIhuLK5rJlzXJwgnJ6GWjvCIAtPDpCMPja lG423zPWcEtPpInt8EfEwnc5WH6knkUHnJSPwSXR6FhiJ2WGM7bwnx2BKSLKHv9z vGnMyT+U5QnSmDYTgJa/yWZR5jl/8mMAhxtZZbUv+zjHHtExdIwRyJh4MwMnl0sE 4sMm1gvpdWj83YXSFxwY9AH0E6nYw9CFQl8djlMRYaENcWbkCJoD0hmNX0OihRQF pfDZ2W8qFNiHiVkwspuBB4Rxp6axAd3FJviYDUYBllCvDNLeSesK84IdkgZaypsu 7lREq4nbs5csTSeeWMG2ND0j7K+in3SLsm2YRrnHRxz3WLrCMoOIDNGU2ZzTL9A/ RG0ibyJAPs++kMO2U12nm49lLlxRxBdPM87ketmv9g2G5oVQi5A= =bg8/ -END PGP SIGNATURE End Message ---
Bug#994736: marked as pending in libmath-gsl-perl
Control: tag -1 pending Hello, Bug #994736 in libmath-gsl-perl 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/perl-team/modules/packages/libmath-gsl-perl/-/commit/a39ecf1dea34463c9a336a52239abea7248579bd exclude all symbols that are missing on arm64 assuming the other failing architectures fail for the same reazon Closes: #994736 (this message was generated automatically) -- Greetings https://bugs.debian.org/994736
Processed: Bug#994736 marked as pending in libmath-gsl-perl
Processing control commands: > tag -1 pending Bug #994736 [src:libmath-gsl-perl] libmath-gsl-perl: FTBFS on several architectures: undefined symbol: gsl_matrix_char_norm1 Added tag(s) pending. -- 994736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994736 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): clone and reassign bug to pkg-js-tools
Processing commands for cont...@bugs.debian.org: > clone 1011973 -1 Bug #1011973 [node-webpack-sources] node-webpack-sources: autopkgtest failure TypeError: addMapping is not a function Bug 1011973 cloned as bug 1012023 1012023 was blocked by: 1004658 1012023 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #1012023 to the same blocks previously set > reassign -1 pkg-js-tools Bug #1012023 [node-webpack-sources] node-webpack-sources: autopkgtest failure TypeError: addMapping is not a function Bug reassigned from package 'node-webpack-sources' to 'pkg-js-tools'. No longer marked as found in versions node-webpack-sources/3.2.1-3. Ignoring request to alter fixed versions of bug #1012023 to the same values previously set > retitle -1 debian/tests/pkg-js/files not working for Bug #1012023 [pkg-js-tools] node-webpack-sources: autopkgtest failure TypeError: addMapping is not a function Changed Bug title to 'debian/tests/pkg-js/files not working for' from 'node-webpack-sources: autopkgtest failure TypeError: addMapping is not a function '. > node-webpack-sources Unknown command or malformed arguments to command. > thanks Stopping processing here. Please contact me if you need assistance. -- 1011973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011973 1012023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012023 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012022: fenics-basix: FTBFS during separate binary-indep build
Source: fenics-basix Version: 0.4.0-1exp1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, fenics-basix/experimental FTBFS while performing a separate binary-indep build as would be done by the buildds. You can do that manually with dpkg-builpackage -A. [...] debian/rules execute_before_dh_install-indep make[1]: Entering directory '/build/fenics-basix-0.4.0' py3versions: no X-Python3-Version in control file, using supported versions LD_LIBRARY_PATH=/build/fenics-basix-0.4.0/debian/tmp/usr/lib/x86_64-linux-gnu PYTHONPATH=/build/fenics-basix-0.4.0/debian/python3-basix/usr/lib/python3.10/dist-packages: /usr/bin/make -C doc/python html make[2]: Entering directory '/build/fenics-basix-0.4.0/doc/python' Running Sphinx v4.5.0 Configuration error: There is a programmable error in your configuration file: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/sphinx/config.py", line 332, in eval_config_file exec(code, namespace) File "/build/fenics-basix-0.4.0/doc/python/source/conf.py", line 10, in import basix ModuleNotFoundError: No module named 'basix' make[2]: *** [Makefile:20: html] Error 2 make[2]: Leaving directory '/build/fenics-basix-0.4.0/doc/python' make[1]: *** [debian/rules:71: execute_before_dh_install-indep] Error 2 make[1]: Leaving directory '/build/fenics-basix-0.4.0' make: *** [debian/rules:42: binary-indep] Error 2 Andreas fenics-basix_0.4.0-1exp1_indep.log.gz Description: application/gzip
Bug#1010061: git-buildpackage: FTBFS on bookworm and sid: multiple issues
Guido Günther writes ("Re: Bug#1010061: git-buildpackage: FTBFS on bookworm and
sid: multiple issues"):
> Thanks. I did an upload a while back but now dgit's tests fail:
>
>https://tracker.debian.org/pkg/git-buildpackage
>https://ci.debian.net/data/autopkgtest/testing/amd64/d/dgit/22182444/log.gz
>
> Maybe you have an idea what has triggered this (not all of them look gbp
> related but looking at the tests many of them seem to pull in gbp):
Sorry about this. It's #1005873, which I had quite forgotten about.
Paul Gevers has reminded me (and raised that bug's severity,
appropriately). I have what I think is a fix and hope to upload very
soon.
Would you mind including a "Breaks:" in git-buildpackage for this ?
I think that ought to be
Breaks: dgit (<< 9.16~)
I think you can safely make that change immediately since I'm not
going to be releasing a 9.16 without fixing this issue.
I should really have fixed this some time ago and provided you with a
the version number to use, then. So, sorry for the inconvenience.
Regards,
Ian.
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
Processed: yarnpkg: segfault while building greenbone-security-assistant on !amd64
Processing control commands: > affects -1 + src:greenbone-security-assistant Bug #1012021 [yarnpkg] yarnpkg: segfault while building greenbone-security-assistant on !amd64 Added indication that 1012021 affects src:greenbone-security-assistant -- 1012021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012021: yarnpkg: segfault while building greenbone-security-assistant on !amd64
Package: yarnpkg Version: 1.22.19+~cs24.27.18-1 Severity: serious Tags: ftbfs Control: affects -1 + src:greenbone-security-assistant Hi, greenbone-security-assistant fails to built on most (all?) architectures except amd64. There seems to be a segmentation fault during a yarnpkg call: debian/rules build dh build dh_update_autotools_config dh_autoreconf debian/rules override_dh_auto_build make[1]: Entering directory '/build/greenbone-security-assistant-21.4.4' dh_auto_build yarnpkg yarn install v1.22.19 [1/5] Validating package.json... [2/5] Resolving packages... [3/5] Fetching packages... make[1]: *** [debian/rules:13: override_dh_auto_build] Segmentation fault make[1]: Leaving directory '/build/greenbone-security-assistant-21.4.4' make: *** [debian/rules:9: build] Error 2 Andreas greenbone-security-assistant_21.4.4-1.log.gz Description: application/gzip
Processed: Re: crystal: switch to llvm-toolchain-13
Processing control commands: > severity -1 serious Bug #1004882 [src:crystal] crystal: switch to llvm-toolchain-13 Severity set to 'serious' from 'important' -- 1004882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004882 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011146: hipercontracer is marked for autoremoval from testing
Hi, I get the autoremoval notification (see below) for my HiPerConTracer package. HiPerConTracer clearly has no dependency on anything related to NVIDIA drivers. It is a set of simple shell tools. There is probably something wrong with the autoremoval script. Den 26.05.2022 07:02, skrev Debian testing autoremoval watch: hipercontracer 1.6.5-1 is marked for autoremoval from testing on 2022-06-30 It (build-)depends on packages with these RC bugs: 1011146: nvidia-graphics-drivers-tesla-470: CVE-2022-28181, CVE-2022-28183, CVE-2022-28184, CVE-2022-28185, CVE-2022-28191, CVE-2022-28192 https://bugs.debian.org/1011146 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl -- Best regards / Mit freundlichen Grüßen / Med vennlig hilsen === Thomas Dreibholz SimulaMet -- Simula Metropolitan Centre for Digital Engineering Centre for Resilient Networks and Applications Pilestredet 52 0167 Oslo, Norway --- E-Mail: dre...@simula.no Homepage: http://simula.no/people/dreibh === OpenPGP_signature Description: OpenPGP digital signature
Bug#1011146: bibtexconv is marked for autoremoval from testing
Hi, I get the autoremoval notification (see below) for my BibTeXConv package. BibTeXConv clearly has no dependency on anything related to NVIDIA drivers. It is a set of simple shell tools. There is probably something wrong with the autoremoval script Den 26.05.2022 06:40, skrev Debian testing autoremoval watch: bibtexconv 1.3.2-1 is marked for autoremoval from testing on 2022-06-30 It (build-)depends on packages with these RC bugs: 1011146: nvidia-graphics-drivers-tesla-470: CVE-2022-28181, CVE-2022-28183, CVE-2022-28184, CVE-2022-28185, CVE-2022-28191, CVE-2022-28192 https://bugs.debian.org/1011146 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl -- Best regards / Mit freundlichen Grüßen / Med vennlig hilsen === Thomas Dreibholz SimulaMet -- Simula Metropolitan Centre for Digital Engineering Centre for Resilient Networks and Applications Pilestredet 52 0167 Oslo, Norway --- E-Mail: dre...@simula.no Homepage: http://simula.no/people/dreibh === OpenPGP_signature Description: OpenPGP digital signature
Bug#1011146: netperfmeter is marked for autoremoval from testing
Hi, I get the autoremoval notification (see below) for my NetPerfMeter package. NetPerfMeter clearly has no dependency on anything related to NVIDIA drivers. It is a set of simple shell tools. There is probably something wrong with the autoremoval script. Den 26.05.2022 07:27, skrev Debian testing autoremoval watch: netperfmeter 1.9.2-1 is marked for autoremoval from testing on 2022-06-30 It (build-)depends on packages with these RC bugs: 1011146: nvidia-graphics-drivers-tesla-470: CVE-2022-28181, CVE-2022-28183, CVE-2022-28184, CVE-2022-28185, CVE-2022-28191, CVE-2022-28192 https://bugs.debian.org/1011146 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl -- Best regards / Mit freundlichen Grüßen / Med vennlig hilsen === Thomas Dreibholz SimulaMet -- Simula Metropolitan Centre for Digital Engineering Centre for Resilient Networks and Applications Pilestredet 52 0167 Oslo, Norway --- E-Mail: dre...@simula.no Homepage: http://simula.no/people/dreibh === OpenPGP_signature Description: OpenPGP digital signature
Bug#1011146: rsplib is marked for autoremoval from testing
Hi, I get the autoremoval notification (see below) for my RSPLIB package. RSPLIB clearly has no dependency on anything related to NVIDIA drivers. There is probably something wrong with the autoremoval script. Den 26.05.2022 07:48, skrev Debian testing autoremoval watch: rsplib 3.4.1-1 is marked for autoremoval from testing on 2022-06-30 It (build-)depends on packages with these RC bugs: 1011146: nvidia-graphics-drivers-tesla-470: CVE-2022-28181, CVE-2022-28183, CVE-2022-28184, CVE-2022-28185, CVE-2022-28191, CVE-2022-28192 https://bugs.debian.org/1011146 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl -- Best regards / Mit freundlichen Grüßen / Med vennlig hilsen === Thomas Dreibholz SimulaMet -- Simula Metropolitan Centre for Digital Engineering Centre for Resilient Networks and Applications Pilestredet 52 0167 Oslo, Norway --- E-Mail: dre...@simula.no Homepage: http://simula.no/people/dreibh === OpenPGP_signature Description: OpenPGP digital signature
Bug#1011146: subnetcalc is marked for autoremoval from testing
Hi, I get the autoremoval notification (see below) for my SubNetCalc package. SubNetCalc clearly has no dependency on anything related to NVIDIA drivers. It is a simple shell tool. There is probably something wrong with the autoremoval script. Den 26.05.2022 07:57, skrev Debian testing autoremoval watch: subnetcalc 2.4.19-1 is marked for autoremoval from testing on 2022-06-30 It (build-)depends on packages with these RC bugs: 1011146: nvidia-graphics-drivers-tesla-470: CVE-2022-28181, CVE-2022-28183, CVE-2022-28184, CVE-2022-28185, CVE-2022-28191, CVE-2022-28192 https://bugs.debian.org/1011146 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl -- Best regards / Mit freundlichen Grüßen / Med vennlig hilsen === Thomas Dreibholz SimulaMet -- Simula Metropolitan Centre for Digital Engineering Centre for Resilient Networks and Applications Pilestredet 52 0167 Oslo, Norway --- E-Mail: dre...@simula.no Homepage: http://simula.no/people/dreibh === OpenPGP_signature Description: OpenPGP digital signature
Bug#1005718: marked as done (mosh: FTBFS with OpenSSL 3.0)
Your message dated Sat, 28 May 2022 19:49:03 + with message-id and subject line Bug#1005718: fixed in mosh 1.3.2-2.2 has caused the Debian Bug report #1005718, regarding mosh: FTBFS with OpenSSL 3.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.) -- 1005718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mosh Version: 1.3.2-2.1 Severity: important Tags: bookworm sid User: pkg-openssl-de...@lists.alioth.debian.org Usertags: ftbfs-3.0 Your package is failing to build using OpenSSL 3.0 with the following error: | c++ -DHAVE_CONFIG_H -I. -I../.. -I./../util -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Werror -Wextra -pedantic -Wno-long-long -Weffc++ -Wmissing-declarations -fno-strict-overflow -D_FORTIFY_SOURCE=2 -fstack-protector-all -Wstack-protector --param ssp-buffer-size=1 -fPIE -fno-default-inline -pipe -g -O2 -ffile-prefix-map=/<>=. -Wformat -Werror=format-security -c -o ocb.o ocb.cc | ocb.cc: In function ‘void AES_ecb_encrypt_blks(block*, unsigned int, AES_KEY*)’: | ocb.cc:360:80: error: ‘void AES_encrypt(const unsigned char*, unsigned char*, const AES_KEY*)’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] | 360 | AES_encrypt((unsigned char *)(blks+nblks), (unsigned char *)(blks+nblks), key); | | ^ | In file included from ocb.cc:354: | /usr/include/openssl/aes.h:57:6: note: declared here |57 | void AES_encrypt(const unsigned char *in, unsigned char *out, | | ^~~ | ocb.cc: In function ‘void AES_ecb_decrypt_blks(block*, unsigned int, AES_KEY*)’: | ocb.cc:367:80: error: ‘void AES_decrypt(const unsigned char*, unsigned char*, const AES_KEY*)’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] | 367 | AES_decrypt((unsigned char *)(blks+nblks), (unsigned char *)(blks+nblks), key); | | ^ | In file included from ocb.cc:354: | /usr/include/openssl/aes.h:60:6: note: declared here |60 | void AES_decrypt(const unsigned char *in, unsigned char *out, | | ^~~ | ocb.cc: In function ‘int ae_init(ae_ctx*, const void*, int, int, int)’: | ocb.cc:804:75: error: ‘int AES_set_encrypt_key(const unsigned char*, int, AES_KEY*)’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] | 804 | AES_set_encrypt_key((unsigned char *)key, key_len*8, >encrypt_key); | | ^ | In file included from ocb.cc:354: | /usr/include/openssl/aes.h:51:5: note: declared here |51 | int AES_set_encrypt_key(const unsigned char *userKey, const int bits, | | ^~~ | ocb.cc:808:82: error: ‘int AES_set_decrypt_key(const unsigned char*, int, AES_KEY*)’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] | 808 | AES_set_decrypt_key((unsigned char *)key, (int)(key_len*8), >decrypt_key); | | ^ | In file included from ocb.cc:354: | /usr/include/openssl/aes.h:54:5: note: declared here |54 | int AES_set_decrypt_key(const unsigned char *userKey, const int bits, | | ^~~ | ocb.cc:817:76: error: ‘void AES_encrypt(const unsigned char*, unsigned char*, const AES_KEY*)’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] | 817 | (unsigned char *)>Lstar, >encrypt_key); | | ^ | In file included from ocb.cc:354: | /usr/include/openssl/aes.h:57:6: note: declared here |57 | void AES_encrypt(const unsigned char *in, unsigned char *out, | | ^~~ | ocb.cc: In function ‘block gen_offset_from_nonce(ae_ctx*, const void*)’: | ocb.cc:854:72: error: ‘void AES_encrypt(const unsigned char*, unsigned char*, const AES_KEY*)’ is deprecated: Since OpenSSL 3.0 [-Werror=deprecated-declarations] | 854 | AES_encrypt(tmp.u8, (unsigned char *)>KtopStr, >encrypt_key); | | ^ | In file included from ocb.cc:354: | /usr/include/openssl/aes.h:57:6: note: declared here |57 | void AES_encrypt(const unsigned char *in, unsigned char *out, | | ^~~ | ocb.cc: In function ‘int
Bug#1011781: marked as done (libphp-swiftmailer: FTBFS: make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1)
Your message dated Sat, 28 May 2022 19:33:54 + with message-id and subject line Bug#1011781: fixed in libphp-swiftmailer 6.3.0-2 has caused the Debian Bug report #1011781, regarding libphp-swiftmailer: FTBFS: make[1]: *** [debian/rules:14: override_dh_auto_test] Error 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1011781: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011781 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libphp-swiftmailer Version: 6.3.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > mkdir -p vendor > cp debian/autoload.test.php vendor/autoload.php > phpunit -v --include-path lib > PHPUnit 9.5.16 by Sebastian Bergmann and contributors. > > Runtime: PHP 8.1.5 > Configuration: /<>/phpunit.xml.dist > > Testing > . 61 / 1275 ( > 4%) > . 122 / 1275 ( > 9%) > . 183 / 1275 ( > 14%) > . 244 / 1275 ( > 19%) > . 305 / 1275 ( > 23%) > . 366 / 1275 ( > 28%) > . 427 / 1275 ( > 33%) > . 488 / 1275 ( > 38%) > . 549 / 1275 ( > 43%) > . 610 / 1275 ( > 47%) > . 671 / 1275 ( > 52%) > . 732 / 1275 ( > 57%) > .SS.. 793 / 1275 ( > 62%) > ..F.. 854 / 1275 ( > 66%) > . 915 / 1275 ( > 71%) > . 976 / 1275 ( > 76%) > . 1037 / 1275 ( > 81%) > . 1098 / 1275 ( > 86%) > . 1159 / 1275 ( > 90%) > . 1220 / 1275 ( > 95%) > S.. 1275 / 1275 > (100%) > > Time: 00:01.242, Memory: 76.01 MB > > There was 1 failure: > > 1) Swift_Transport_Esmtp_Auth_NTLMAuthenticatorTest::testLMv1Generator > %s: The keys should be the same cause we use the same values to generate them. > Failed asserting that two strings are equal. > --- Expected > +++ Actual > @@ @@ > -'1879f60127f8a877022132ec221bcbf3ca016a9f76095606' > +'' > > /<>/tests/unit/Swift/Transport/Esmtp/Auth/NTLMAuthenticatorTest.php:39 > > -- > > There were 31 skipped tests: > > 1) Swift_Signers_OpenDKIMSignerTest::testBasicSigningHeaderManipulation > Need OpenDKIM extension run these tests. > > /<>/tests/unit/Swift/Signers/OpenDKIMSignerTest.php:12 > > 2) Swift_Signers_OpenDKIMSignerTest::testSigningDefaults > Need OpenDKIM extension run these tests. > > /<>/tests/unit/Swift/Signers/OpenDKIMSignerTest.php:12 > > 3) Swift_Signers_OpenDKIMSignerTest::testSigning256 > Need OpenDKIM extension run these tests. > > /<>/tests/unit/Swift/Signers/OpenDKIMSignerTest.php:12 > > 4) Swift_Signers_OpenDKIMSignerTest::testSigningRelaxedRelaxed256 > Need OpenDKIM extension run these tests. > > /<>/tests/unit/Swift/Signers/OpenDKIMSignerTest.php:12 > > 5) Swift_Signers_OpenDKIMSignerTest::testSigningRelaxedSimple256 > Need OpenDKIM extension run these tests. > > /<>/tests/unit/Swift/Signers/OpenDKIMSignerTest.php:12 > > 6) Swift_Signers_OpenDKIMSignerTest::testSigningSimpleRelaxed256 > Need OpenDKIM extension run these tests. > > /<>/tests/unit/Swift/Signers/OpenDKIMSignerTest.php:12 > > 7) Swift_Transport_StreamBuffer_BasicSocketAcceptanceTest::testReadLine > Cannot run test without an SMTP host to connect to (define SWIFT_SMTP_HOST in > tests/acceptance.conf.php if you wish to run this test) > >
Bug#1012016: libapache-poi-java breaks octave-io autopkgtest: assert (size (d) == [1001, 2]) failed
Source: libapache-poi-java, octave-io Control: found -1 libapache-poi-java/4.0.1-4 Control: found -1 octave-io/2.6.4-1 Severity: serious Tags: sid bookworm User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of libapache-poi-java the autopkgtest of octave-io fails in testing when that autopkgtest is run with the binary packages of libapache-poi-java from unstable. It passes when run with only packages from testing. In tabular form: passfail libapache-poi-java from testing4.0.1-4 octave-io from testing2.6.4-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of libapache-poi-java to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=libapache-poi-java https://ci.debian.net/data/autopkgtest/testing/amd64/o/octave-io/22169972/log.gz Testing default interface for XLSX... warning: xlsopen: no'.xlsx' spreadsheet I/O support with available interfaces. warning: xlsopen: no'.xlsx' spreadsheet I/O support with available interfaces. error: assert (size (d) == [1001, 2]) failed error: called from assert at line 107 column 11 testhelper at line 14 column 5 autopkgtest [15:22:44]: test xlsx-default OpenPGP_signature Description: OpenPGP digital signature
Processed: libapache-poi-java breaks octave-io autopkgtest: assert (size (d) == [1001, 2]) failed
Processing control commands: > found -1 libapache-poi-java/4.0.1-4 Bug #1012016 [src:libapache-poi-java, src:octave-io] libapache-poi-java breaks octave-io autopkgtest: assert (size (d) == [1001, 2]) failed Marked as found in versions libapache-poi-java/4.0.1-4. > found -1 octave-io/2.6.4-1 Bug #1012016 [src:libapache-poi-java, src:octave-io] libapache-poi-java breaks octave-io autopkgtest: assert (size (d) == [1001, 2]) failed Marked as found in versions octave-io/2.6.4-1. -- 1012016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012015: breezy: FTBFS: error: can't find Rust compiler
Source: breezy
Version: 3.3.0~bzr7571-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
breezy/experimental did FTBFS on all architectures:
https://buildd.debian.org/status/package.php?p=breezy=experimental
debian/rules clean
dh clean --with python3,sphinxdoc,bash_completion --buildsystem=pybuild
debian/rules override_dh_auto_clean
make[1]: Entering directory '/<>'
dh_auto_clean
I: pybuild base:239: python3.9 setup.py clean
/usr/lib/python3/dist-packages/setuptools/dist.py:493: UserWarning: Normalizing
'3.3.0.dev' to '3.3.0.dev0'
warnings.warn(tmpl.format(**locals()))
running clean
removing '/<>/.pybuild/cpython3_3.9_breezy/build' (and everything
under it)
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-3.9' does not exist -- can't clean it
running clean_rust
error: can't find Rust compiler
If you are using an outdated pip version, it is possible a prebuilt wheel is
available for this package but pip is not able to install from it. Installing
from the wheel would avoid the need for a Rust compiler.
To update pip, run:
pip install --upgrade pip
and then retry package installation.
If you did intend to build this package from source, try installing a Rust
compiler from your system package manager and ensure it is on the PATH during
installation. Alternatively, rustup (available at https://rustup.rs) is the
recommended way to download and update the Rust compiler toolchain.
E: pybuild pybuild:369: clean: plugin distutils failed with: exit code=1:
python3.9 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p "3.9 3.10" returned
exit code 13
make[1]: *** [debian/rules:36: override_dh_auto_clean] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:15: clean] Error 2
Andreas
Bug#1012014: r8125: fails to build module for Linux 5.17
Source: r8125 Version: 9.007.01-3 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, since autopkg tests now actually attempt to build kernel modules, we quickly see that this does not work for Linux 5.17: https://ci.debian.net/data/autopkgtest/testing/amd64/r/r8125/22177051/log.gz == /var/lib/dkms/r8125/9.007.01/build/make.log == DKMS make.log for r8125-9.007.01 for kernel 5.17.0-1-amd64 (x86_64) Fri May 27 21:15:08 UTC 2022 make: Entering directory '/usr/src/linux-headers-5.17.0-1-amd64' warning: the compiler differs from the one used to build the kernel The kernel was built by: gcc-11 (Debian 11.2.0-20) 11.2.0 You are using: gcc-11 (Debian 11.3.0-3) 11.3.0 CC [M] /var/lib/dkms/r8125/9.007.01/build/r8125_n.o CC [M] /var/lib/dkms/r8125/9.007.01/build/rtl_eeprom.o CC [M] /var/lib/dkms/r8125/9.007.01/build/rtltool.o /var/lib/dkms/r8125/9.007.01/build/r8125_n.c: In function ‘rtl8125_proc_open’: /var/lib/dkms/r8125/9.007.01/build/r8125_n.c:1749:50: error: implicit declaration of function ‘PDE_DATA’; did you mean ‘NODE_DATA’? [-Werror=implicit-function-declaration] 1749 | int (*show)(struct seq_file *, void *) = PDE_DATA(inode); | ^~~~ | NODE_DATA /var/lib/dkms/r8125/9.007.01/build/r8125_n.c:1749:50: warning: initialization of ‘int (*)(struct seq_file *, void *)’ from ‘int’ makes pointer from integer without a cast [-Wint-conversion] /var/lib/dkms/r8125/9.007.01/build/r8125_n.c: In function ‘rtl8125_get_mac_address’: /var/lib/dkms/r8125/9.007.01/build/r8125_n.c:10756:34: error: assignment of read-only location ‘*(dev->dev_addr + (sizetype)i)’ 10756 | dev->dev_addr[i] = RTL_R8(tp, MAC0 + i); | ^ ... Andreas PS: please also drop obsolete REMAKE_INITRD from debian/*.dkms
Bug#1012010: matrix-hydrogen: build-depends on no longer available node-commander (< 7)
Source: matrix-hydrogen Version: 0.1.30~dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, matrix-hydrogen can no longer be built since one of its Build-Depends has moved on: The following packages have unmet dependencies: builddeps:matrix-hydrogen : Depends: node-commander (< 7) but 9.2.0-1 is to be installed Andreas
Processed: tagging 1011992, found 1005873 in 0.9.26, tagging 1011989, found 1011647 in 0.0~svnr250-1.4 ...
Processing commands for cont...@bugs.debian.org:
> tags 1011992 + sid bookworm
Bug #1011992 [src:haskell-hslua-module-text] ftbfs: : commitBuffer:
invalid argument (invalid character)
Added tag(s) bookworm and sid.
> found 1005873 0.9.26
Bug #1005873 [src:dgit] gbp 0.9.26 will break dgit --gbp
The source 'dgit' and version '0.9.26' do not appear to match any binary
packages
Marked as found in versions dgit/0.9.26.
> tags 1011989 + sid bookworm
Bug #1011989 [src:haskell-tasty-lua] FTBFS: : commitBuffer: invalid
argument (invalid character)
Added tag(s) sid and bookworm.
> found 1011647 0.0~svnr250-1.4
Bug #1011647 [netsend] RM: netsend -- RoQA, RC-buggy, dead-upstream,
unmaintained, low popcon
Marked as found in versions netsend/0.0~svnr250-1.4.
> tags 1011647 + sid bookworm
Bug #1011647 [netsend] RM: netsend -- RoQA, RC-buggy, dead-upstream,
unmaintained, low popcon
Added tag(s) sid and bookworm.
> notfixed 949521 5.3.3
Bug #949521 {Done: Victor Seva }
[src:kamailio] kamailio: loses link (and a bunch of other files) against
libxml2 not shipping xml2-config
The source 'kamailio' and version '5.3.3' do not appear to match any binary
packages
No longer marked as fixed in versions kamailio/5.3.3.
> fixed 949521 5.3.3-1
Bug #949521 {Done: Victor Seva }
[src:kamailio] kamailio: loses link (and a bunch of other files) against
libxml2 not shipping xml2-config
Marked as fixed in versions kamailio/5.3.3-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1005873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005873
1011647: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011647
1011989: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011989
1011992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011992
949521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949521
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: ITP: node-dommatrix -- ES6+ shim for DOMMatrix
Processing control commands: > block 1001631 by -1 Bug #1001631 [src:pdf.js] pdf.js: FTBFS with webpack5: Error: Missing file or directory 1001631 was not blocked by any bugs. 1001631 was not blocking any bugs. Added blocking bug(s) of 1001631: 1012009 -- 1001631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001631 1012009: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012009 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1001016: marked as done (telegram-desktop: Version in stable (2.6.1) becoming unusable)
Your message dated Sat, 28 May 2022 18:32:31 + with message-id and subject line Bug#1001016: fixed in telegram-desktop 3.1.1+ds-1~deb11u2 has caused the Debian Bug report #1001016, regarding telegram-desktop: Version in stable (2.6.1) becoming unusable 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.) -- 1001016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001016 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: telegram-desktop Version: 2.6.1+ds-1+deb11u1 Severity: grave Justification: renders package unusable Hi, I got a message in the 'Telegram' channel on telegram: "Please update your app to the latest version. The version you are using is out of date and will stop working soon." There is a 3.1.1 in testing but I won't upgrade the whole system from stable to testing for that. How can I upgrade to a version that won't stop working soon? Shouldn't there be a policy in the telegram team to support old clients as long as they are in current stable versions of distributions? Is the version of telegram-desktop in debian stable supported at all, does it get security updates and backported security fixes? Ralf -- Package-specific info: -- System Information: Debian Release: 11.1 APT prefers proposed-updates APT policy: (800, 'proposed-updates'), (800, 'stable'), (799, 'oldstable'), (750, 'testing-proposed-updates'), (750, 'testing'), (300, 'unstable') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 5.10.0-9-amd64 (SMP w/2 CPU threads) Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages telegram-desktop depends on: ii libavcodec58 7:4.3.3-0+deb11u1 ii libavformat58 7:4.3.3-0+deb11u1 ii libavutil56 7:4.3.3-0+deb11u1 ii libc6 2.31-13+deb11u2 ii libdbusmenu-qt5-2 0.9.3+16.04.20160218-2+b1 ii libgcc-s1 10.2.1-6 ii libgdk-pixbuf-2.0-0 2.42.2+dfsg-1 ii libglib2.0-0 2.66.8-1 ii libgtk-3-03.24.24-4 ii libhunspell-1.7-0 1.7.0-3 ii libjpeg62-turbo 1:2.0.6-4 ii libkf5waylandclient5 4:5.78.0-2 ii liblz4-1 1.9.3-2 ii liblzma5 5.2.5-2 ii libminizip1 1.1-8+b1 ii libopenal11:1.19.1-2 ii libopus0 1.3.1-0.1 ii libqrcodegencpp1 1.6.0-1 ii libqt5core5a [qtbase-abi-5-15-2] 5.15.2+dfsg-9 ii libqt5dbus5 5.15.2+dfsg-9 ii libqt5gui55.15.2+dfsg-9 ii libqt5network55.15.2+dfsg-9 ii libqt5waylandclient5 [qtwayland-client-abi-5-15- 5.15.2-3 ii libqt5widgets55.15.2+dfsg-9 ii librlottie0-1 0.1+dfsg-2 ii libssl1.1 1.1.1k-1+deb11u1 ii libstdc++610.2.1-6 ii libswresample37:4.3.3-0+deb11u1 ii libswscale5 7:4.3.3-0+deb11u1 ii libx11-6 2:1.7.2-1 ii libxcb-keysyms1 0.4.0-1+b2 ii libxcb-record01.14-3 ii libxcb-screensaver0 1.14-3 ii libxcb1 1.14-3 ii libxxhash00.8.0-2 ii qt5-image-formats-plugins 5.15.2-2 ii zlib1g1:1.2.11.dfsg-2 Versions of packages telegram-desktop recommends: ii fonts-open-sans 1.11-1.1 telegram-desktop suggests no packages. -- no debconf information -- debsums errors found: dpkg-query: warning: parsing file '/var/lib/dpkg/status' near line 144653 package 'musepack-decoder': 'Version' field value 'sv7.15+1.95z67-1': version number does not start with digit dpkg-divert: warning: parsing
Processed: Merge failed, closing bug #1002382 manually
Processing commands for cont...@bugs.debian.org: > fixed 1002382 nbconvert/6.3.0-1 Bug #1002382 [src:nbconvert] nbsphinx: FTBFS: AttributeError: module 'mistune' has no attribute 'BlockGrammar' Marked as fixed in versions nbconvert/6.3.0-1. > close 1002382 Bug #1002382 [src:nbconvert] nbsphinx: FTBFS: AttributeError: module 'mistune' has no attribute 'BlockGrammar' Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1002382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002382 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1011823 marked as pending in purple-xmpp-http-upload
Processing control commands: > tag -1 pending Bug #1011823 [src:purple-xmpp-http-upload] purple-xmpp-http-upload: FTBFS: dpkg-shlibdeps: error: cannot find library libjabber.so.0 needed by debian/purple-xmpp-http-upload/usr/lib/x86_64-linux-gnu/purple-2/jabber_http_file_upload.so (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '') Added tag(s) pending. -- 1011823: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011823 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011823: marked as pending in purple-xmpp-http-upload
Control: tag -1 pending Hello, Bug #1011823 in purple-xmpp-http-upload 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/DebianOnMobile-team/purple-xmpp-http-upload/-/commit/f480bf62f1640548d02f5af4a0a0659344a53b05 Adjust shlibdeps override Closes: #1011823, thanks to Lucas Nussbaum (this message was generated automatically) -- Greetings https://bugs.debian.org/1011823
Processed (with 1 error): Re: Bug#1002382: nbsphinx: FTBFS: AttributeError: module 'mistune' has no attribute 'BlockGrammar'
Processing control commands:
> reassign -1 src:nbconvert 6.1.0-1
Bug #1002382 [src:nbsphinx] nbsphinx: FTBFS: AttributeError: module 'mistune'
has no attribute 'BlockGrammar'
Bug reassigned from package 'src:nbsphinx' to 'src:nbconvert'.
No longer marked as found in versions nbsphinx/0.8.7+ds-1.
Ignoring request to alter fixed versions of bug #1002382 to the same values
previously set
Bug #1002382 [src:nbconvert] nbsphinx: FTBFS: AttributeError: module 'mistune'
has no attribute 'BlockGrammar'
Marked as found in versions nbconvert/6.1.0-1.
> unarchive 1002372
Bug #1002372 {Done: Gordon Ball } [src:nbconvert]
nbconvert: FTBFS: AttributeError: module 'mistune' has no attribute
'BlockGrammar'
Bug #1002397 {Done: Gordon Ball } [src:nbconvert]
qiskit-terra: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p
"3.10 3.9" returned exit code 13
Unarchived Bug 1002372
Unarchived Bug 1002397
> forcemerge 1002372 -1
Bug #1002372 {Done: Gordon Ball } [src:nbconvert]
nbconvert: FTBFS: AttributeError: module 'mistune' has no attribute
'BlockGrammar'
Bug #1002397 {Done: Gordon Ball } [src:nbconvert]
qiskit-terra: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p
"3.10 3.9" returned exit code 13
Bug #1002382 [src:nbconvert] nbsphinx: FTBFS: AttributeError: module 'mistune'
has no attribute 'BlockGrammar'
Set Bug forwarded-to-address to
'https://github.com/jupyter/nbconvert/issues/1685'.
Failed to forcibly merge 1002372: Failure while trying to adjust bugs, please
report this as a bug: Not altering archived bugs; see unarchive..
at /usr/local/lib/site_perl/Debbugs/Control.pm line 2133.
> archive 1002372
Bug #1002372 {Done: Gordon Ball } [src:nbconvert]
nbconvert: FTBFS: AttributeError: module 'mistune' has no attribute
'BlockGrammar'
Bug #1002397 {Done: Gordon Ball } [src:nbconvert]
qiskit-terra: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p
"3.10 3.9" returned exit code 13
archived 1002372 to archive/72 (from 1002372)
archived 1002397 to archive/97 (from 1002372)
--
1002372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002372
1002382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002382
1002397: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002397
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1002382: nbsphinx: FTBFS: AttributeError: module 'mistune' has no attribute 'BlockGrammar'
Control: reassign -1 src:nbconvert 6.1.0-1 Control: unarchive 1002372 Control: forcemerge 1002372 -1 Control: archive 1002372 On Wed, Dec 22, 2021 at 09:05:08AM +0100, Lucas Nussbaum wrote: > Source: nbsphinx > Version: 0.8.7+ds-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20211220 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > Relevant part (hopefully): > > make[1]: Entering directory '/<>' > > PYTHONPATH=/<>/src python3 -m sphinx -b html doc > > /<>/debian/python-nbsphinx-doc/usr/share/doc/python-nbsphinx/html > > Running Sphinx v4.3.2 > > > > Exception occurred: > > File > > "/usr/lib/python3/dist-packages/nbconvert/filters/markdown_mistune.py", > > line 31, in > > class MathBlockGrammar(mistune.BlockGrammar): > > AttributeError: module 'mistune' has no attribute 'BlockGrammar' It is a bug in nbconvert, same as #1002372. And already fixed. -- Dmitry Shachnev signature.asc Description: PGP signature
Bug#1011973: node-webpack-sources: autopkgtest failure TypeError: addMapping is not a function
with node-source-map 0.7 built from salsa master branch, there is only 1 failure. 26 tests were failing earlier with node-source-map 0.6. This is a red herring. The autopkgtest fails aren't related to node-source-map at all. Specifically, the tests don't fail in gbp buildpackage, but only in autopkgtest, that too only in one particular stage. That's because the __mocks__ that jest relies on are in the lib/helpers/ directory and that's not available somehow to the autopkgtest run. For example, if you do autopkgtest with --shell-fail and after it fails copy __mocks__ to /usr/share/nodejs/webpack-sources/lib/helpers and rerun the test with /usr/share/pkg-js-autopkgtest/runner it passes You can replicate it by downloading upstream code and removing `__mocks__` folder and running yarnpkg test https://wiki.debian.org/ContinuousIntegration/AutopkgtestBestPractices#Recommendations > Use upstream test-suite if they have as-installed test The jest tests are not as-installed
Bug#1011645: marked as done (librust-once-cell-dev: broken dependencies.)
Your message dated Sat, 28 May 2022 17:41:53 +0100 with message-id <282e622e-39de-539c-6f1b-e8b57a6ce...@debian.org> and subject line re: librust-once-cell-dev: broken dependencies. has caused the Debian Bug report #1011645, regarding librust-once-cell-dev: broken dependencies. 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.) -- 1011645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011645 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: librust-once-cell-dev Version: 1.12.0-1 X-debbugs-cc: tsimo...@debian.org Simon Quingley just uploaded a new version of rust-once-cell. Unfortunately the binary package librust-once-cell-dev resulting from this upload is not installable. It has two dependencies that are not satisfiable. librust-atomic-polyfill-0.1+default-dev and librust-parking-lot-core-0.9-dev rust-atomic-polyfill is not currently in Debian, nor is it in the new queue it looks like Sylvestre started packaging it but never actually uploaded it. The previous version of once-cell was patched to remove the atomic-polyfill dependency but this patch was dropped without explanation in Simon's upload. rust-parking-lot-core is in Debian but is at version 0.8.5, I have not yet investigated what it would take to upgrade it or how feasible it would. be to make the new version of once-cell work with the older parking-lot-core. Simon does not appear to be a member of the rust team on salsa, nor do the commits for this or other uploads appear to have been pushed to his personal account there. Simon: what is your intent here? can you push your commits somewhere? do you intend to fix the broken librust-once-cell package or do you need help with it? do you wish to join the rust team? --- End Message --- --- Begin Message --- I make a 1.12.0-2 upload reinstating the patch to drop atomic-polyfill and adding a new patch to switch the version of rayon-core to the version that is in debian. once-cell is now installable again.--- End Message ---
Bug#1010061: git-buildpackage: FTBFS on bookworm and sid: multiple issues
Hi Ian, On Wed, May 11, 2022 at 12:40:35PM +0100, Ian Jackson wrote: > Guido: > > These all make sense. Pushed, thanks! > > Would you mind doing an upload ? My grep-excuses is warning me about > autoremovals. > > If you don't have time I would be willing to do it myself from the > relevant git branch, but I certainly wouldn't want to do that without > coordinating with you... Thanks. I did an upload a while back but now dgit's tests fail: https://tracker.debian.org/pkg/git-buildpackage https://ci.debian.net/data/autopkgtest/testing/amd64/d/dgit/22182444/log.gz Maybe you have an idea what has triggered this (not all of them look gbp related but looking at the tests many of them seem to pull in gbp): debpolicy-quilt-gbp FAIL non-zero exit status 16 TEST FAILED gbp-orig FAIL non-zero exit status 16 TEST FAILED overwrite-splitbrains FAIL non-zero exit status 16 TEST FAILED quilt-gbpFAIL non-zero exit status 16 + echo 'OPERATION FAILED' TEST FAILED quilt-gbp-build-modes FAIL non-zero exit status 16 TEST FAILED quilt-splitbrainsFAIL non-zero exit status 16 TEST FAILED rpush-quilt FAIL non-zero exit status 16 baredebian-multitar FAIL non-zero exit status 16 baredebian-plusgit FAIL non-zero exit status 16 baredebian-push FAIL non-zero exit status 16 baredebian-tarball FAIL non-zero exit status 16 gdr-import-dgit FAIL non-zero exit status 16 gdr-diverge-nmu FAIL non-zero exit status 16 gdr-diverge-nmu-dgit FAIL non-zero exit status 16 gdr-editsFAIL non-zero exit status 16 gdr-import-dgitview FAIL non-zero exit status 16 gdr-makepatches7 FAIL non-zero exit status 16 gdr-subcommands FAIL non-zero exit status 16 gdr-unprocessableFAIL non-zero exit status 16 gdr-unprocessable-hints FAIL non-zero exit status 16 tagupl-baredebianFAIL non-zero exit status 16 tagupl-gbp FAIL non-zero exit status 16 debpolicy-quilt-gbp FAIL non-zero exit status 16 gbp-orig FAIL non-zero exit status 16 overwrite-splitbrains FAIL non-zero exit status 16 quilt-gbpFAIL non-zero exit status 16 quilt-gbp-build-modes FAIL non-zero exit status 16 quilt-splitbrainsFAIL non-zero exit status 16 rpush-quilt FAIL non-zero exit status 16 Cheers, -- Guido > > Thanks, > Ian. > > -- > Ian JacksonThese opinions are my own. > > Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk, > that is a private address which bypasses my fierce spamfilter. >
Processed: Re: Processed: Re: Bug#1011078: chromium: arm64 package not available in bullseye-security
Processing commands for cont...@bugs.debian.org:
> close 1011078
Bug #1011078 [chromium] chromium: arm64 package not available in
bullseye-security
Marked Bug as done
> reopen 1011096
Bug #1011096 {Done: Andres Salomon } [chromium] chromium:
i386 and armhf packages FTBFS in bullseye
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions chromium/102.0.5005.61-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1011078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011078
1011096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011096
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1002869: marked as done (node-vue-resource: FTBFS with webpack5: Error: Invalid webpack options)
Your message dated Sat, 28 May 2022 15:19:22 + with message-id and subject line Bug#1002869: fixed in node-vue-resource 1.5.3+dfsg+~1.3.6-3 has caused the Debian Bug report #1002869, regarding node-vue-resource: FTBFS with webpack5: Error: Invalid webpack options to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1002869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-vue-resource Version: 1.5.3+dfsg+~1.3.6-2 Severity: important Justification: ftbfs Tags: ftbfs User: pkg-javascript-de...@alioth-lists.debian.net Usertags: webpack5 Hi, We are starting to build against webpack5 in experimental and the package needed for local build is webpack and node-webpack-source from experimental. During a test rebuild, node-vue-resource was found to fail to build in that situation. Relevant part (hopefully): debian/rules override_dh_auto_build make[1]: Entering directory '/<>' webpack --config debian/webpack.config.js --mode development \ --entry ./src/index.js --output dist/vue-resource.common.js \ --output-library-target commonjs \ --module-bind 'js=babel-loader' [webpack-cli] Error: Unknown option '--output' make[1]: *** [debian/rules:10: override_dh_auto_build] Error 1 make[1]: Leaving directory '/<>' make: *** [debian/rules:6: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 The full log is attached to this mail sbuild (Debian sbuild) 0.81.2 (31 January 2021) on Ayoyimika-PC.localdomain +===+ | node-vue-resource 1.5.3+dfsg+~1.3.6-2 (amd64) Thu, 30 Dec 2021 10:12:11 + | +===+ Package: node-vue-resource Version: 1.5.3+dfsg+~1.3.6-2 Source Version: 1.5.3+dfsg+~1.3.6-2 Distribution: unstable Machine Architecture: amd64 Host Architecture: amd64 Build Architecture: amd64 Build Type: binary I: NOTICE: Log filtering will replace 'var/run/schroot/mount/unstable-amd64-sbuild-c1dd29bf-113d-4ea4-8699-1ff571390dc3' with '<>' I: NOTICE: Log filtering will replace 'build/node-vue-resource-DJJm1n/resolver-vf5qvV' with '<>' +--+ | Update chroot| +--+ Get:1 file:/build/node-vue-resource-DJJm1n/resolver-D9O9zU/apt_archive ./ InRelease Ign:1 file:/build/node-vue-resource-DJJm1n/resolver-D9O9zU/apt_archive ./ InRelease Get:2 file:/build/node-vue-resource-DJJm1n/resolver-D9O9zU/apt_archive ./ Release [951 B] Get:2 file:/build/node-vue-resource-DJJm1n/resolver-D9O9zU/apt_archive ./ Release [951 B] Get:3 file:/build/node-vue-resource-DJJm1n/resolver-D9O9zU/apt_archive ./ Release.gpg Ign:3 file:/build/node-vue-resource-DJJm1n/resolver-D9O9zU/apt_archive ./ Release.gpg Get:4 file:/build/node-vue-resource-DJJm1n/resolver-D9O9zU/apt_archive ./ Packages [798 B] Err:4 file:/build/node-vue-resource-DJJm1n/resolver-D9O9zU/apt_archive ./ Packages Could not open file /build/node-vue-resource-DJJm1n/resolver-D9O9zU/apt_archive/./Packages - open (13: Permission denied) Get:4 file:/build/node-vue-resource-DJJm1n/resolver-D9O9zU/apt_archive ./ Packages [1381 B] Get:5 http://deb.debian.org/debian unstable InRelease [165 kB] Get:6 http://deb.debian.org/debian experimental InRelease [75.4 kB] Get:7 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB] Get:8 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index [63.6 kB] Get:9 http://deb.debian.org/debian unstable/main all Contents (deb).diff/Index [63.8 kB] Get:10 http://deb.debian.org/debian unstable/main amd64 Contents (deb).diff/Index [63.8 kB] Get:11 http://deb.debian.org/debian experimental/main Sources.diff/Index [63.3 kB] Get:12 http://deb.debian.org/debian experimental/main amd64 Packages.diff/Index [63.3 kB] Get:13 http://deb.debian.org/debian experimental/main amd64 Contents (deb).diff/Index [63.6 kB] Get:14 http://deb.debian.org/debian experimental/main all Contents (deb).diff/Index [63.6 kB] Get:15 http://deb.debian.org/debian unstable/main Sources T-2021-12-30-0801.19-F-2021-12-22-2012.55.pdiff [266 kB] Get:16 http://deb.debian.org/debian unstable/main amd64 Packages T-2021-12-30-0801.19-F-2021-12-22-2012.55.pdiff [277 kB] Get:15 http://deb.debian.org/debian unstable/main Sources
Bug#1011728: marked as done (pidgin-librvp: FTBFS: rm: cannot remove '/<>/debian/pidgin-librvp/usr/lib/purple-2/librvp.la': No such file or directory)
Your message dated Sat, 28 May 2022 15:03:56 +
with message-id
and subject line Bug#1011728: fixed in pidgin-librvp 0.9.7cvs-3
has caused the Debian Bug report #1011728,
regarding pidgin-librvp: FTBFS: rm: cannot remove
'/<>/debian/pidgin-librvp/usr/lib/purple-2/librvp.la': No such
file or directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1011728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011728
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pidgin-librvp
Version: 0.9.7cvs-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> if echo "-pthread -I/usr/include/pidgin -I/usr/include/gtk-2.0
> -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0
> -I/usr/include/atk-1.0 -I/usr/include/gdk-pixbuf-2.0
> -I/usr/include/x86_64-linux-gnu -I/usr/include/pango-1.0
> -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/libmount
> -I/usr/include/blkid -I/usr/include/fribidi -I/usr/include/cairo
> -I/usr/include/pixman-1 -I/usr/include/harfbuzz -I/usr/include/uuid
> -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/libpurple
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include" |
> /bin/grep -q GAIM_IS_GAIM;\
> then\
> mkdir -p
> "/<>/debian/pidgin-librvp/usr/share/pixmaps/pidgin/status/default";\
> /usr/bin/install -c -m 0644 rvp.png
> "/<>/debian/pidgin-librvp/usr/share/pixmaps/pidgin/status/default/rvp.png";\
> mkdir -p
> "/<>/debian/pidgin-librvp/usr/share/pixmaps/pidgin/smileys/rvp";\
> for p in smileys/*.png smileys/theme; do f=f=`echo $p | sed -e
> 's|^.*/||'`;\
> /usr/bin/install -c -m 0644 $p
> "/<>/debian/pidgin-librvp/usr/share/pixmaps/pidgin/smileys/rvp/$f";\
> done;\
> else\
> for p in 16 22 32 48;\
> do \
> mkdir -p
> "/<>/debian/pidgin-librvp/usr/share/pixmaps/pidgin/protocols/$p";\
> /usr/bin/convert rvp.png -resize ${p}x${p}
> "/<>/debian/pidgin-librvp/usr/share/pixmaps/pidgin/protocols/$p/rvp.png";\
> done; \
> /usr/bin/install -c -m 0644 rvp.png
> "/<>/debian/pidgin-librvp/usr/share/pixmaps/pidgin/emotes/default/rvp.png";\
> mkdir -p
> "/<>/debian/pidgin-librvp/usr/share/pixmaps/pidgin/emotes/rvp";\
> for p in smileys/*.png smileys/theme; do f=f=`echo $p | sed -e
> 's|^.*/||'`;\
> /usr/bin/install -c -m 0644 $p
> "/<>/debian/pidgin-librvp/usr/share/pixmaps/pidgin/emotes/rvp/$f";\
> done;\
> fi
> /usr/bin/install: cannot create regular file
> '/<>/debian/pidgin-librvp/usr/share/pixmaps/pidgin/emotes/default/rvp.png':
> No such file or directory
> make[3]: Leaving directory '/<>'
> make[2]: Leaving directory '/<>'
> make[1]: Leaving directory '/<>'
>debian/rules execute_after_dh_auto_install
> make[1]: Entering directory '/<>'
> rm -v /<>/debian/pidgin-librvp/usr/lib/purple-2/librvp.la
> rm: cannot remove
> '/<>/debian/pidgin-librvp/usr/lib/purple-2/librvp.la': No such
> file or directory
> make[1]: *** [debian/rules:21: execute_after_dh_auto_install] Error 1
The full build log is available from:
http://qa-logs.debian.net/2022/05/25/pidgin-librvp_0.9.7cvs-2_unstable.log
All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: pidgin-librvp
Source-Version: 0.9.7cvs-3
Done: Boyuan Yang
We believe that the bug you reported is fixed in the latest version of
pidgin-librvp, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to
Bug#1011992: ftbfs: : commitBuffer: invalid argument (invalid character)
Source: haskell-hslua-module-text Version: 0.2.1-2 Severity: serious Tags: ftbfs Justification: FTBFS -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 haskell-hslua-module-text fails to build from source: Running debian/hlibrary.setup register --builddir=dist-ghc --gen-pkg-config --verbose=verbose+nowrap Non-zero exit code 1. /usr/bin/ghc --abi-hash -fbuilding-cabal-package -O -outputdir dist-ghc/build -odir dist-ghc/build -hidir dist-ghc/build -stubdir dist-ghc/build -i -idist-ghc/build -isrc -idist-ghc/build/autogen -idist-ghc/build/global-autogen -Idist-ghc/build/autogen -Idist-ghc/build/global-autogen -Idist-ghc/build -optP-include -optPdist-ghc/build/autogen/cabal_macros.h -this-unit-id hslua-module-text-0.2.1-KVQIhWqJT8R8zGxab7jo31 -hide-all-packages -Wmissing-home-modules -no-user-package-db -XHaskell2010 Foreign.Lua.Module.Text -optl-Wl,-z,relro name: hslua-module-text version: 0.2.1 visibility: public id: hslua-module-text-0.2.1-KVQIhWqJT8R8zGxab7jo31 key: hslua-module-text-0.2.1-KVQIhWqJT8R8zGxab7jo31 license: MIT copyright:: commitBuffer: invalid argument (invalid character) make: *** [/usr/share/cdbs/1/class/hlibrary.mk:172: install/libghc-hslua-module-text-dev] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKSMbIACgkQLHwxRsGg ASFndw/+M6U4U1Khb4eTbWPYpgKX/zQi9JvMs0yEnLhHrZVQRj+yr7X0LzLTv8Sp rjfT484Xp14nZrjd1qg6FnYCV4EEBBOmT4RBZP8+k1QwZZlLeOU4cOHmbdn6lK+p vgw8sOukuy00V6Y6Xupqvauh9OsQah7ORwxGqUsGtlrChMxEf58D/u2553598Cib RDfEUD89CbdtVbdrhQCRDjbgnpFwQSUIc/DtTbsUmqW41+nBoWTBn4PeZaX4pRd9 ZNjmweRoGVEdAVBs/cGHLmxjckyNfs0t4j+g1wAiRen34cn9pMR77kQAu2LVlPHZ LYuxfqxw5ysAkllymoSmX3OthoLiZWXQwCfROQ0/NkY9+u0PfoCL063RuHlE0Fk6 wAJdZIHJeCtgM1dxB9D6Pt4URAnaXmtKk8Lg8bm+EOcCDcO6vl0BxL85hB+f949V 0CHeAcSmtdz1RhMtPWM64iY67d5/3F65XZ41hVs4QoTE7y2RcWGgruXzYq2jyB6z qnpR22hf7qWg/LiegqyXoze+MndoHyl9M1kZX0AFCTi6+q95qtEROHof+N7XLhAD oqFeBxIkdRXeaTkcdcsbkZUiyz2IqgbxUK/aTKLC5IItq5Z5TV+x8GtdqwjDXlVQ Cm7fb56x4dZ2ynzUeVAdHxAYpq1rtNzk36UGRLOVamEpxHK1UMA= =ytyU -END PGP SIGNATURE-
Processed: RM: libgnatcoll-python -- ROM; NPOASR; temporary package not needed anymore
Processing control commands: > unblock 936624 by 936869 Bug #936624 [src:gnat-gps] gnat-gps: Python2 removal in sid/bullseye 936624 was not blocked by any bugs. 936624 was blocking: 936869 937271 937448 937569 937849 938492 938528 938656 943104 Removed blocking bug(s) of 936624: 936869 -- 1011991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011991 936624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936624 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936869: RM: libgnatcoll-python -- ROM; NPOASR; temporary package not needed anymore
Package: ftp.debian.org
Severity: normal
Control: unblock 936624 by 936869
Hello.
Please remove these packages from unstable:
libgnatcoll-python:src
libgnatcoll-python19
libgnatcoll-python19-dev
I am the maintainer of libgnatcoll-bindings and libgnatcoll-python.
The normal situation is that
the libgnatcoll-bindings source package produces
libgnatcoll-${COMPONENT}{SOVERSION} and
libgnatcoll-${COMPONENT}{ALIVERSION}-dev
for various COMPONENTs including python.
A few years ago, the python component was ready for both python2&3,
but its only reverse dependency gnat-gps was requiring python2.
As a temporary measure, the separate libgnatcoll-python source package
was introduced. This allowed the other components to be updated in
testing, while the python(2) component and gnat-gps were RC-buggy in
unstable (#936869 and #936624 respectively).
Nowadays
* gnat-gps has been RC-buggy for a while.
It depends on libgnatcoll-python18 that no one is building anymore.
* If/when we manage to rebuild gnat-gps, latest upstream version is
ready for python3. Hence the unblock command above.
There is no need for a separate package anymore, so
libgnatcoll-bindings builds the python(3) component again.
libgnatcoll-python3.1
libgnatcoll-python3.1-dev
These fully replace the removed packages.
Thanks.
Processed: RM: libgnatcoll-python -- ROM; NPOASR; temporary package not needed anymore
Processing control commands: > unblock 936624 by 936869 Bug #936624 [src:gnat-gps] gnat-gps: Python2 removal in sid/bullseye 936624 was not blocked by any bugs. 936624 was blocking: 936869 937271 937448 937569 937849 938492 938528 938656 943104 Removed blocking bug(s) of 936624: 936869 -- 936624: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936624 936869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936869 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011990: pappl: autopkgtest regression: fails on output to stderr
Source: pappl
Version: 1.2.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of pappl the autopkgtest of pappl fails in testing
when that autopkgtest is run with the binary packages of pappl from
unstable. It passes when run with only packages from testing. In tabular
form:
passfail
pappl from testing1.2.0-1
all others from testingfrom testing
I copied some of the output at the bottom of this report. The test
itself seems to pass, but there's output to stderr. Output to stderr is
by default treated as failure by autopkgtest, unless the allow-stderr
restriction is set.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=pappl
https://ci.debian.net/data/autopkgtest/testing/amd64/p/pappl/22174962/log.gz
testsuiteFAIL stderr: Starting tests...
autopkgtest [18:13:16]: test testsuite: - - - - - - - - - - stderr - -
- - - - - - - -
Starting tests...
api: papplSystemFindLoc('de'): PASS
api: papplLocGetString('A printer with that name already exists.'): PASS
(got 'Ein Drucker mit diesem Namen existiert bereits.')
api: papplSystemFindLoc('en'): PASS
api: papplLocGetString('A printer with that name already exists.'): PASS
(got 'A printer with that name already exists.')
api: papplSystemFindLoc('es'): PASS
api: papplLocGetString('A printer with that name already exists.'): PASS
(got 'Una impresora con ese nombre ya existe.')
api: papplSystemFindLoc('fr'): PASS
api: papplLocGetString('A printer with that name already exists.'): PASS
(got 'Une imprimante avec ce nom existe déjà.')
api: papplSystemFindLoc('it'): PASS
api: papplLocGetString('A printer with that name already exists.'): PASS
(got 'Una stampante con quel nome esiste già.')
api: papplSystemFindLoc('ja'): PASS
api: papplLocGetString('A printer with that name already exists.'): PASS
(got '既に存在している名前のプリンター。')
api: papplSystemFindLoc('zz'): PASS (got NULL)
api: papplLocGetString('A printer with that name already exists.'): PASS
(got key string)
api: papplSystemGetAdminGroup: PASS
api: papplSystemGet/SetAdminGroup('admin-0'): PASS
api: papplSystemGet/SetAdminGroup('admin-1'): PASS
api: papplSystemGet/SetAdminGroup('admin-2'): PASS
api: papplSystemGet/SetAdminGroup('admin-3'): PASS
api: papplSystemGet/SetAdminGroup('admin-4'): PASS
api: papplSystemGet/SetAdminGroup('admin-5'): PASS
api: papplSystemGet/SetAdminGroup('admin-6'): PASS
api: papplSystemGet/SetAdminGroup('admin-7'): PASS
api: papplSystemGet/SetAdminGroup('admin-8'): PASS
api: papplSystemGet/SetAdminGroup('admin-9'): PASS
api: papplSystemGet/SetAdminGroup(NULL): PASS
api: papplSystemGetContact: PASS
api: papplSystemGet/SetContact('Admin 0'): PASS
api: papplSystemGet/SetContact('Admin 1'): PASS
api: papplSystemGet/SetContact('Admin 2'): PASS
api: papplSystemGet/SetContact('Admin 3'): PASS
api: papplSystemGet/SetContact('Admin 4'): PASS
api: papplSystemGet/SetContact('Admin 5'): PASS
api: papplSystemGet/SetContact('Admin 6'): PASS
api: papplSystemGet/SetContact('Admin 7'): PASS
api: papplSystemGet/SetContact('Admin 8'): PASS
api: papplSystemGet/SetContact('Admin 9'): PASS
api: papplSystemGetDefaultPrinterID: PASS (1)
api: papplSystemSetDefaultPrinterID(2): PASS
api: papplSystemSetDefaultPrinterID(1): PASS
api: papplSystemGetDefaultPrintGroup: PASS
api: papplSystemGet/SetDefaultPrintGroup('users-0'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-1'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-2'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-3'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-4'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-5'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-6'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-7'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-8'): PASS
api: papplSystemGet/SetDefaultPrintGroup('users-9'): PASS
api: papplSystemGet/SetDefaultPrintGroup(NULL): PASS
api: papplSystemGetDNSSDName: PASS
api: papplSystemGet/SetDNSSDName('System Test A'): PASS
api: papplSystemGet/SetDNSSDName('System Test B'): PASS
api: papplSystemGet/SetDNSSDName('System Test C'): PASS
api: papplSystemGet/SetDNSSDName('System Test D'): PASS
api: papplSystemGet/SetDNSSDName('System Test E'): PASS
api: papplSystemGet/SetDNSSDName('System Test F'): PASS
api: papplSystemGet/SetDNSSDName('System Test G'): PASS
api: papplSystemGet/SetDNSSDName('System Test H'): PASS
api: papplSystemGet/SetDNSSDName('System Test I'): PASS
api: papplSystemGet/SetDNSSDName('System Test J'): PASS
api: papplSystemGet/SetDNSSDName(NULL): PASS
api: papplSystemGetFooterHTML: PASS
api:
Processed: Re: Bug#1005873: [git-buildpackage/master] pq: Check if repo is clean before importing patches
Processing control commands: > severity -1 serious Bug #1005873 [src:dgit] gbp 0.9.26 will break dgit --gbp Severity set to 'serious' from 'normal' -- 1005873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 1011645 is serious
Processing commands for cont...@bugs.debian.org: > severity 1011645 serious Bug #1011645 [librust-once-cell-dev] librust-once-cell-dev: broken dependencies. Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1011645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011645 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011989: FTBFS: : commitBuffer: invalid argument (invalid character)
Source: haskell-tasty-lua Version: 0.2.2-2 Severity: serious Tags: ftbfs Justification: FTBFS -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 haskell-tasty-lua fails to build from source: Running debian/hlibrary.setup register --builddir=dist-ghc --gen-pkg-config --verbose=verbose+nowrap Non-zero exit code 1. /usr/bin/ghc --abi-hash -fbuilding-cabal-package -O -outputdir dist-ghc/build -odir dist-ghc/build -hidir dist-ghc/build -stubdir dist-ghc/build -i -idist-ghc/build -isrc -idist-ghc/build/autogen -idist-ghc/build/global-autogen -Idist-ghc/build/autogen -Idist-ghc/build/global-autogen -Idist-ghc/build -optP-include -optPdist-ghc/build/autogen/cabal_macros.h -this-unit-id tasty-lua-0.2.2-F8d0iSXAcfI2gsDTgxUog4 -hide-all-packages -Wmissing-home-modules -no-user-package-db -XHaskell2010 Test.Tasty.Lua Test.Tasty.Lua.Core Test.Tasty.Lua.Module Test.Tasty.Lua.Translate -Wall -optl-Wl,-z,relro name: tasty-lua version: 0.2.2 visibility: public id: tasty-lua-0.2.2-F8d0iSXAcfI2gsDTgxUog4 key: tasty-lua-0.2.2-F8d0iSXAcfI2gsDTgxUog4 license: MIT copyright:: commitBuffer: invalid argument (invalid character) make: *** [/usr/share/cdbs/1/class/hlibrary.mk:172: install/libghc-tasty-lua-dev] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 - Jonas -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmKSLcwACgkQLHwxRsGg ASGpIRAApbsNdoKG4wARtWZHUz9jylBYKjC/MvsMuWcH+WLevQNA1O4EWRnvPDBQ MLUOMRM2MjpyF11dTRNGLHHdm6Er4xxRN3FrSJ8ZUul3qtTAYczGVAk6GJ3kRYz+ GJ4Tr5VIJZYsVC8R7OZykxmaVJA1IIMQemGiAdSYRHSyfODUsKuRZXPLMFzqpOZU Z79V4rz9uhnBQvDqGpbTc67vhTyBKFVjupTx+nlpYmAsn7h2qvN/zeikoe8KXy9n ctxTX8Yfi7UGHXBF21tOHNfmLEKzq6RCw3ebV+ObYkt4YJb7HOLlzSOjCnA71e8H Su8+kdExGdTOv+OSDxEIdhgkE8oT5tlFgtVf6WvHG7PPsyn6AYw8y+bf4q/zbO8t RXGZLWJuVGmOINC3nRabVmIDlyBaNtQf81ZYc9ZfptXaCZw/clu0u4RgcSoZlTd4 uibOM2C3hL1UZTwm87dEVgZjvaDIS0Q0bvevYaQLB0rfbaxo+uEy/Pphd8kKWs/e saNQb1vui7UhYzzEwePf3pDoi4/Lo3n7/73i4HZPtPLejxSZv6peS6ylp6MUsPm4 pAyYT5fVzVCwgrRwBdOfYtkU8CxY9czvTMA7+s4ojJpz0am8ORhypgC1yhoKpp7p 6jOVSC6BenRIzhsxC663Iv7LpmGj/PTEVd/uOHrYM3+T32InhDE= =F/Hz -END PGP SIGNATURE-
Processed: Re: Bug#1011913: haskell-swish: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
Processing control commands: > reassign -1 haskell-devscripts Bug #1011913 [src:haskell-swish] haskell-swish: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25 Bug reassigned from package 'src:haskell-swish' to 'haskell-devscripts'. No longer marked as found in versions haskell-swish/0.10.1.0-1. Ignoring request to alter fixed versions of bug #1011913 to the same values previously set > retitle -1 haskell-devscripts: DEB_ENABLE_TESTS ignored Bug #1011913 [haskell-devscripts] haskell-swish: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25 Changed Bug title to 'haskell-devscripts: DEB_ENABLE_TESTS ignored' from 'haskell-swish: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25'. > affects -1 haskell-swish Bug #1011913 [haskell-devscripts] haskell-devscripts: DEB_ENABLE_TESTS ignored Added indication that 1011913 affects haskell-swish -- 1011913: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011913 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011913: haskell-swish: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:153: build-ghc-stamp] Error 25
Control: reassign -1 haskell-devscripts Control: retitle -1 haskell-devscripts: DEB_ENABLE_TESTS ignored Control: affects -1 haskell-swish Quoting Lucas Nussbaum (2022-05-26 21:04:50) > During a rebuild of all packages in sid, [haskell-swish] failed to build > on amd64. [...] > > Running debian/hlibrary.setup test --builddir=dist-ghc --show-details=direct > > Non-zero exit code 1. > > hlibrary.setup: No test suites enabled. Did you remember to configure with > > '--enable-tests'? haskell-swish built successfully when released in January, and contains this in debian/rules: > DEB_ENABLE_TESTS = yes Perhaps this really is bug#1010179 and the "fix" only papered over the underlying problem: @Scott, did you test packages _enabling_ tests or only the default of having tests disabled? - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Bug#1004699: marked as done (libdigest-bcrypt-perl breaks libdancer2-plugin-passphrase-perl autopkgtest: Bcrypt needs encoded text)
Your message dated Sat, 28 May 2022 12:19:08 + with message-id and subject line Bug#1004699: fixed in libdancer2-plugin-passphrase-perl 3.3.4-2 has caused the Debian Bug report #1004699, regarding libdigest-bcrypt-perl breaks libdancer2-plugin-passphrase-perl autopkgtest: Bcrypt needs encoded text 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.) -- 1004699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libdigest-bcrypt-perl, libdancer2-plugin-passphrase-perl Control: found -1 libdigest-bcrypt-perl/1.212-1 Control: found -1 libdancer2-plugin-passphrase-perl/3.3.4-1 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of libdigest-bcrypt-perl the autopkgtest of libdancer2-plugin-passphrase-perl fails in testing when that autopkgtest is run with the binary packages of libdigest-bcrypt-perl from unstable. It passes when run with only packages from testing. In tabular form: passfail libdigest-bcrypt-perl from testing1.212-1 libdancer2-plugin-passphrase-perl from testing3.3.4-1 all othersfrom testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of libdigest-bcrypt-perl to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=libdigest-bcrypt-perl https://ci.debian.net/data/autopkgtest/testing/amd64/libd/libdancer2-plugin-passphrase-perl/18819128/log.gz t/001_basics.t .. 1..1 ok 1 - use Dancer2::Plugin::Passphrase; ok t/003_default_settings.t 1..3 ok 1 - RFC compliant hash generated ok 2 - Match plaintext to hash ok 3 - Incorrect passwords should be rejected ok t/004_all_algorithm_matching.t .. 1..26 ok 1 - With Salt - Match plaintext to hash => MD5 ok 2 - With Salt - Incorrect passwords should be rejected => MD5 ok 3 - With Salt - Match plaintext to hash => SHA-1 ok 4 - With Salt - Incorrect passwords should be rejected => SHA-1 ok 5 - With Salt - Match plaintext to hash => SHA-224 ok 6 - With Salt - Incorrect passwords should be rejected => SHA-224 ok 7 - With Salt - Match plaintext to hash => SHA-256 ok 8 - With Salt - Incorrect passwords should be rejected => SHA-256 ok 9 - With Salt - Match plaintext to hash => SHA-384 ok 10 - With Salt - Incorrect passwords should be rejected => SHA-384 ok 11 - With Salt - Match plaintext to hash => SHA-512 ok 12 - With Salt - Incorrect passwords should be rejected => SHA-512 ok 13 - With Salt - Match plaintext to hash => Bcrypt ok 14 - With Salt - Incorrect passwords should be rejected => Bcrypt ok 15 - No Salt - Match plaintext to hash => MD5 ok 16 - No Salt - Incorrect passwords should be rejected => MD5 ok 17 - No Salt - Match plaintext to hash => SHA-1 ok 18 - No Salt - Incorrect passwords should be rejected => SHA-1 ok 19 - No Salt - Match plaintext to hash => SHA-224 ok 20 - No Salt - Incorrect passwords should be rejected => SHA-224 ok 21 - No Salt - Match plaintext to hash => SHA-256 ok 22 - No Salt - Incorrect passwords should be rejected => SHA-256 ok 23 - No Salt - Match plaintext to hash => SHA-384 ok 24 - No Salt - Incorrect passwords should be rejected => SHA-384 ok 25 - No Salt - Match plaintext to hash => SHA-512 ok 26 - No Salt - Incorrect passwords should be rejected => SHA-512 ok t/005_random_passphrase.t ... 1..3 ok 1 - Basic password generation ok 2 - Custom password length ok 3 - Custom chracter set ok t/006_return_object.t ... 1..20 ok 1 - An object of class 'Dancer2::Plugin::Passphrase::Hashed' isa 'Dancer2::Plugin::Passphrase::Hashed' ok 2 - Contains RFC 2307 representation ok 3 - Contains correct scheme ok 4 - Contains correct cost ok 5 - Contains raw salt ok 6 - Contains hex hash ok 7 - Contains base64 hash ok 8 - Contains raw salt ok 9 - Contains hex salt ok 10 - Contains base64 salt ok 11 - Contains correct plaintext ok 12 - Extracted raw salt is the same as the defined raw salt ok 13 - Extracted base64 salt is the same as the defined base64 salt ok 14 - Extracted
Bug#1011963: marked as done (open-invaders FTBFS on riscv64)
Your message dated Sat, 28 May 2022 11:20:49 + with message-id and subject line Bug#1011963: fixed in open-invaders 0.3-8 has caused the Debian Bug report #1011963, regarding open-invaders FTBFS on riscv64 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.) -- 1011963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011963 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: open-invaders Version: 0.3-7 Severity: serious Tags: ftbfs patch Justification: fails to build from source X-Debbugs-Cc: ab.bea...@gmail.com Dear Maintainer, open-invaders has a ftbfs issue on riscv64. Full buildd log here: https://buildd.debian.org/status/fetch.php?pkg=open-invaders=riscv64=0.3-7=1651106683=0 At compile time it tries to detect the architecture to determine datatype sizes, and it is missing the check for riscv64, so it defaults to an incorrect value. I am including a patch which fixes the problem. Please consider applying it in the next upload. Thank you. -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: riscv64 Kernel: Linux 5.18.0-starfive-5.18 (SMP w/2 CPU threads) 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) Versions of packages open-invaders depends on: ii libaldmb1 1:0.9.3-6 ii liballegro4.4 2:4.4.3.1-2 ii libc6 2.33-7 ii libdumb11:0.9.3-6 ii libgcc-s1 12.1.0-2 ii libstdc++6 12.1.0-2 ii open-invaders-data 0.3-7 open-invaders recommends no packages. open-invaders suggests no packages. -- no debconf information From: Alan Beadle Date: Fri 27 May 2022 09:36:54 PM EDT Subject: Fix ftbfs on riscv Fix failing compile-time detection of dataype size --- open-invaders-0.3.orig/headers/pmask.h +++ open-invaders-0.3/headers/pmask.h @@ -37,7 +37,7 @@ confusing. //don't worry about setting it incorrectly //you'll get a compile error if you do, not a run-time error #if defined(__alpha__) || defined(__ia64__) || (defined(__x86_64__) && defined(__LP64__)) || defined(__s390x__) || (defined(__sparc__) && defined(__arch64__)) \ - || defined(__powerpc64__) || defined(__aarch64__) || (defined(__mips64) && defined(__LP64__)) + || defined(__powerpc64__) || defined(__aarch64__) || (defined(__mips64) && defined(__LP64__)) || (defined(__riscv) && defined(__LP64__)) #define MASK_WORD_BITBITS 6 #else #define MASK_WORD_BITBITS 5 --- End Message --- --- Begin Message --- Source: open-invaders Source-Version: 0.3-8 Done: Adam Borowski We believe that the bug you reported is fixed in the latest version of open-invaders, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adam Borowski (supplier of updated open-invaders package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 28 May 2022 11:55:46 +0200 Source: open-invaders Architecture: source Version: 0.3-8 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Adam Borowski Closes: 989063 1011963 Changes: open-invaders (0.3-8) unstable; urgency=medium . * QA upload. * Drop 404-compliant git URLs to Salsa. * Fix FTBFS on new platforms in a future-proof way, closes: #1011963 * Mark -data as MA:foreign. * Fix an occassional crash during gameplay, closes: #989063 [John G] Checksums-Sha1: f3db3226a1047ed9366264dfaff587706cd52b56 1938 open-invaders_0.3-8.dsc 2b33e750caf896f6a5dff1888365760ea0d2f7d4 7360 open-invaders_0.3-8.debian.tar.xz 009932d8916e668cf470cb5672af8374fac7b450 6702 open-invaders_0.3-8_source.buildinfo Checksums-Sha256: 54354c6bd2cc0daab1cb1ad2d003fe4dd00cd4f6e6fc3403c323349895283ac3 1938 open-invaders_0.3-8.dsc 0b8d68b2edb14e5f9a9a11abf414ce0ec382ffac666c5736c0db1285cf5fe519 7360 open-invaders_0.3-8.debian.tar.xz dd29660e5ca5e5ab9009dafe9a7052f4150e190e1ae1a7eedb2deee9e6ec88bd 6702 open-invaders_0.3-8_source.buildinfo Files: 7ed78f6d10d4004354164a6ba81b5ac8
Processed: tagging 1006510
Processing commands for cont...@bugs.debian.org:
> tags 1006510 + fixed
Bug #1006510 {Done: Mattias Ellert }
[src:myproxy] myproxy: FTBFS with OpenSSL 3.0
Added tag(s) fixed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1006510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006510
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: kakoune FTBFS on big endian
Processing control commands:
> block 1010335 by -1
Bug #1010335 {Done: Paul Gevers } [src:kakoune] src:kakoune:
fails to migrate to testing for too long: FTBFS on s390x
1010335 was not blocked by any bugs.
1010335 was not blocking any bugs.
Added blocking bug(s) of 1010335: 1011978
--
1010335: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010335
1011978: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011978
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1011978: kakoune FTBFS on big endian
Source: kakoune Version: 2021.11.08-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: debian-s...@lists.debian.org Control: block 1010335 by -1 https://buildd.debian.org/status/logs.php?pkg=kakoune=2021.11.08-1 ... Fatal error: assert failed "hash_data(data, strlen(data)) == 0xf816f95b" at hash.cc:76 ... debian-s390 list is Cc'ed on this bug.
Bug#997488: marked as done (q2cli: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Sat, 28 May 2022 08:39:31 +
with message-id
and subject line Bug#997488: fixed in q2cli 2021.8.0-2
has caused the Debian Bug report #997488,
regarding q2cli: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.9 returned exit code 13
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: q2cli
Version: 2021.8.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> === short test summary info
>
> FAILED q2cli/tests/test_cli.py::CliTests::test_action_parameter_types -
> Asser...
> FAILED q2cli/tests/test_cli.py::CliTests::test_deprecated_help_text -
> Asserti...
> FAILED q2cli/tests/test_cli.py::CliTests::test_examples - AssertionError: 1
> != 0
> FAILED q2cli/tests/test_cli.py::CliTests::test_extract - AssertionError: 1 != > 0
> FAILED q2cli/tests/test_cli.py::CliTests::test_info - AssertionError: 1 != 0
> FAILED q2cli/tests/test_cli.py::CliTests::test_no_examples - AssertionError:
> ...
> FAILED q2cli/tests/test_cli.py::CliTests::test_qza_extension -
> AssertionError...
> FAILED q2cli/tests/test_cli.py::CliTests::test_qzv_extension -
> AssertionError...
> FAILED q2cli/tests/test_cli.py::CliTests::test_run_deprecated_gets_warning_msg
> FAILED q2cli/tests/test_cli.py::CliTests::test_show_importable_formats -
> Asse...
> FAILED q2cli/tests/test_cli.py::CliTests::test_show_importable_types -
> Assert...
> FAILED q2cli/tests/test_cli.py::CliTests::test_split_ints - AssertionError:
> 1...
> FAILED q2cli/tests/test_cli.py::CliTests::test_syntax_error_in_env -
> Assertio...
> FAILED q2cli/tests/test_cli.py::CliTests::test_validate_max -
> AssertionError:...
> FAILED q2cli/tests/test_cli.py::CliTests::test_validate_min -
> AssertionError:...
> FAILED q2cli/tests/test_cli.py::CliTests::test_variadic_inputs -
> AssertionErr...
> FAILED q2cli/tests/test_cli.py::CliTests::test_verbose_shows_stacktrace -
> Ass...
> FAILED q2cli/tests/test_cli.py::CliTests::test_with_parameters_only -
> Asserti...
> FAILED q2cli/tests/test_cli.py::CliTests::test_without_inputs_or_parameters
> FAILED
> q2cli/tests/test_cli.py::TestOptionalArtifactSupport::test_all_optional_artifacts_provided
> FAILED
> q2cli/tests/test_cli.py::TestOptionalArtifactSupport::test_no_optional_artifacts_provided
> FAILED
> q2cli/tests/test_cli.py::TestOptionalArtifactSupport::test_one_optional_artifact_provided
> FAILED
> q2cli/tests/test_cli.py::TestOptionalArtifactSupport::test_optional_artifact_type_mismatch
> FAILED
> q2cli/tests/test_cli.py::TestMetadataSupport::test_invalid_metadata_merge
> FAILED q2cli/tests/test_cli.py::TestMetadataSupport::test_multiple_metadata
> FAILED
> q2cli/tests/test_cli.py::TestMetadataSupport::test_optional_metadata_missing
> FAILED
> q2cli/tests/test_cli.py::TestMetadataSupport::test_required_metadata_missing
> FAILED q2cli/tests/test_cli.py::TestMetadataSupport::test_single_metadata -
> A...
> FAILED
> q2cli/tests/test_cli.py::TestMetadataSupport::test_single_metadata_alt_id_header
> FAILED
> q2cli/tests/test_cli.py::TestMetadataColumnSupport::test_categorical_metadata_column
> FAILED
> q2cli/tests/test_cli.py::TestMetadataColumnSupport::test_categorical_metadata_column_type_mismatch
> FAILED
> q2cli/tests/test_cli.py::TestMetadataColumnSupport::test_multiple_metadata
> FAILED
> q2cli/tests/test_cli.py::TestMetadataColumnSupport::test_multiple_metadata_column
> FAILED
> q2cli/tests/test_cli.py::TestMetadataColumnSupport::test_numeric_metadata_column
> FAILED
> q2cli/tests/test_cli.py::TestMetadataColumnSupport::test_numeric_metadata_column_type_mismatch
> FAILED
> q2cli/tests/test_cli.py::TestMetadataColumnSupport::test_optional_column_without_metadata
> FAILED
> q2cli/tests/test_cli.py::TestMetadataColumnSupport::test_optional_metadata_missing
> FAILED
> q2cli/tests/test_cli.py::TestMetadataColumnSupport::test_optional_metadata_without_column
> FAILED
> q2cli/tests/test_cli.py::TestMetadataColumnSupport::test_required_missing
> FAILED
> q2cli/tests/test_cli.py::TestMetadataColumnSupport::test_single_metadata
> FAILED q2cli/tests/test_core.py::TestOption::test_repeated_action_flag -
> Asse...
> FAILED
Bug#1005718: mosh: FTBFS with OpenSSL 3.0
To prevent mosh from being deleted from testing in a few days, I am proposing to change warnings level to distcheck. This option effectively adds `-Wno-error=unused-parameter -Wno-error=deprecated-declarations` compiler flags. This solution will buy us time to rewrite related code before the deprecated low-level functions get removed away. diffstat for mosh-1.3.2 mosh-1.3.2 changelog |8 rules |2 +- 2 files changed, 9 insertions(+), 1 deletion(-) diff -Nru mosh-1.3.2/debian/changelog mosh-1.3.2/debian/changelog --- mosh-1.3.2/debian/changelog 2018-08-08 20:45:44.0 +0300 +++ mosh-1.3.2/debian/changelog 2022-05-28 10:01:51.0 +0300 @@ -1,3 +1,11 @@ +mosh (1.3.2-2.2) unstable; urgency=medium + + * Non-maintainer upload. + * Lower warning level to distcheck to solve build against OpenSSL 3.0 with +permitted deprecated declarations. (Closes: #1005718) + + -- Nicholas Guriev Sat, 28 May 2022 10:01:51 +0300 + mosh (1.3.2-2.1) unstable; urgency=low * Non-maintainer upload. diff -Nru mosh-1.3.2/debian/rules mosh-1.3.2/debian/rules --- mosh-1.3.2/debian/rules 2017-08-25 01:04:25.0 +0300 +++ mosh-1.3.2/debian/rules 2022-05-28 10:01:46.0 +0300 @@ -22,7 +22,7 @@ --disable-silent-rules \ --enable-ufw \ --enable-completion \ - --enable-compile-warnings=error + --enable-compile-warnings=distcheck override_dh_perl: # mosh only uses Perl modules in perl-base. signature.asc Description: This is a digitally signed message part
Processed: RFS: mosh/1.3.2-2.2 [NMU] [RC] -- Mobile shell that supports roaming and intelligent local echo
Processing control commands: > block 1005718 by -1 Bug #1005718 [src:mosh] mosh: FTBFS with OpenSSL 3.0 1005718 was not blocked by any bugs. 1005718 was not blocking any bugs. Added blocking bug(s) of 1005718: 1011974 -- 1005718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005718 1011974: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011974 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: node-webpack-sources: autopkgtest failure TypeError: addMapping is not a function
Processing control commands: > block -1 by 1004658 Bug #1011973 [node-webpack-sources] node-webpack-sources: autopkgtest failure TypeError: addMapping is not a function 1011973 was not blocked by any bugs. 1011973 was not blocking any bugs. Added blocking bug(s) of 1011973: 1004658 > tags -1 help Bug #1011973 [node-webpack-sources] node-webpack-sources: autopkgtest failure TypeError: addMapping is not a function Added tag(s) help. -- 1011973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011966: marked as done (alt-ergo: autopkgtest regression: /usr/share/doc/alt-ergo/examples/valid/*.why: No such file or directory)
Your message dated Sat, 28 May 2022 07:03:48 +
with message-id
and subject line Bug#1011966: fixed in alt-ergo 2.4.1-2
has caused the Debian Bug report #1011966,
regarding alt-ergo: autopkgtest regression:
/usr/share/doc/alt-ergo/examples/valid/*.why: No such file or directory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1011966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011966
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: alt-ergo
Version: 2.4.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of alt-ergo the autopkgtest of alt-ergo fails in
testing when that autopkgtest is run with the binary packages of
alt-ergo from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
alt-ergo from testing2.4.1-1
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=alt-ergo
https://ci.debian.net/data/autopkgtest/testing/amd64/a/alt-ergo/22180660/log.gz
Fatal error: exception
Sys_error("/usr/share/doc/alt-ergo/examples/valid/*.why: No such file or
directory")
autopkgtest [23:11:40]: test valid
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: alt-ergo
Source-Version: 2.4.1-2
Done: Julien Puydt
We believe that the bug you reported is fixed in the latest version of
alt-ergo, 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 1011...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Julien Puydt (supplier of updated alt-ergo package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sat, 28 May 2022 08:36:08 +0200
Source: alt-ergo
Architecture: source
Version: 2.4.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian OCaml Maintainers
Changed-By: Julien Puydt
Closes: 1011966
Changes:
alt-ergo (2.4.1-2) unstable; urgency=medium
.
* Team upload.
* Ship the examples (Closes: #1011966).
Checksums-Sha1:
3ed04315627dc7753d314ca7e0ee7f0bc26d0ed8 2271 alt-ergo_2.4.1-2.dsc
0e5e3f8d4fd49c3a247eb1dd6eaee6d8b4c81cd1 7136 alt-ergo_2.4.1-2.debian.tar.xz
ea74c3966c33b5ab8a220de451517fd300b38fc0 15558
alt-ergo_2.4.1-2_source.buildinfo
Checksums-Sha256:
59b9997dde83b1206a93326b8b72d630dba6999bdf48b8ce6675877cd38720a7 2271
alt-ergo_2.4.1-2.dsc
d0665637409757526e8beda242ca5eec28875d48c2fce0896e3b1c400c893ccc 7136
alt-ergo_2.4.1-2.debian.tar.xz
0b19aedad10ae43b055c55940c17f62a64875b329a743967258920b2a75292b2 15558
alt-ergo_2.4.1-2_source.buildinfo
Files:
3a956a5768241d8b2bb8edb6b1c2b1d4 2271 math optional alt-ergo_2.4.1-2.dsc
df160fbd8bce7cca14466fedf992d346 7136 math optional
alt-ergo_2.4.1-2.debian.tar.xz
7a4756340566362b6ede7cd9ac49efa0 15558 math optional
alt-ergo_2.4.1-2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmKRwvkSHGpwdXlkdEBk
ZWJpYW4ub3JnAAoJEATFO9f+AwVRfyoP/jZkJ2FryVC/CTyApm6XLjbog4LcJyDl
drY79yTD7nVpiCoHbORL043LYG4WtXAgAGUWdOXCg7dv/3RD7kMXyYeQ0L+Iat7S
R442jNQdalzRUH5Vod1byxETVmE7xA+cOzFSN2Yk/YShAfycv0GTEYBmcFyqUeac
wZmYa0BVf2QjvsVF8dgLhAItuDwSQc3CfDBo8JnRU+IoKapEUngGJ0Bp5Dn9Gtw+
rif/jSHiWddwFXuc5Bx1zq2fluxovR12xKX3iVcJ6Yjhs+6M9Vf1l6Ux73caUYog
SS6+dTmL3KQZGHg7gcR/0/zmgya2PjbCSjk1KnbOHceHufY4xszuUwtPBtXSV2Ae
F2Ci7Z++B47CgBI5el0K94+uYiR1tLPHCCGpGFbqa5A0pC+l3gJYB1XE7l9ZDFq+
E+ZZCeFTpMEgFshtt1fmIIPgG75TGZ59OWdA8BKwS6IOhY8yxarmEhLKf3jVVV85
hUw5RgEMTR7CmLL8wv4/3svho6SPE+C/HQ0OeJF8WCtuKVZDJ/ajGwXalAL5t2QW
q1hVUUmBAyJfxzS/hcKpS7QRrN62xCSmsUo1aetZ7YTXwRUAILhiilYnYyn1h21X
Uwm1SwtJopLdRFvVKhma8EdxRNatw/YfEplWyRcFKxtvcoWS4mvuK2vFeUgtx1Z9
0cODbCNSr5+f
=vgnn
-END PGP SIGNATURE End Message ---
Bug#1011908: marked as done (node-css-what: FTBFS: node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations.)
Your message dated Sat, 28 May 2022 07:04:08 + with message-id and subject line Bug#1011908: fixed in node-css-what 5.1.0-3 has caused the Debian Bug report #1011908, regarding node-css-what: FTBFS: node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations. 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.) -- 1011908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-css-what Version: 5.1.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs > Link ./node_modules/pretty-format -> /usr/share/nodejs/pretty-format > Link ./node_modules/ts-jest -> /usr/share/nodejs/ts-jest > Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node > Copy /usr/share/nodejs/jest-diff -> ./node_modules/ > Copy /usr/share/nodejs/@types/jest -> ./node_modules/@types >debian/rules override_dh_auto_build > make[1]: Entering directory '/<>' > tsc --lib es6 > node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module > 'jest-matcher-utils' or its corresponding type declarations. > make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2022/05/25/node-css-what_5.1.0-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: node-css-what Source-Version: 5.1.0-3 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-css-what, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-css-what package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 28 May 2022 08:44:42 +0200 Source: node-css-what Built-For-Profiles: nocheck Architecture: source Version: 5.1.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1011908 Changes: node-css-what (5.1.0-3) unstable; urgency=medium . * Team upload * Fix filenamemangle * Declare compliance with policy 4.6.1 * Fix build links (Closes: #1011908) Checksums-Sha1: 2e661140c195eb18f3ecda18381054c565494257 2118 node-css-what_5.1.0-3.dsc cc8898baba2ead433ed71434c64a3074ed1dcb53 3572 node-css-what_5.1.0-3.debian.tar.xz Checksums-Sha256: c705b5bcd8fb25846c05e710ab0ecaa92789ac8cb187e70be56f3f86b09cda0b 2118 node-css-what_5.1.0-3.dsc f284336e0e8b87bf6ef1bf91c6dbb467815284f561ddb848c705a9a191b3d50d 3572 node-css-what_5.1.0-3.debian.tar.xz Files: 065eb44c8bb75c9100c808bf8139e578 2118 javascript optional node-css-what_5.1.0-3.dsc 9c9bf9ea24d3dd0503b79207ebc07269 3572 javascript optional node-css-what_5.1.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmKRxSMACgkQ9tdMp8mZ 7umI8g//cbn2LG1v6CyXgM8AoovHKLBzwsjnJT75dNPqrAtK/yzqafFbmfnJ8AeP p3gFt6bX7fn5RbjBsombg4Yu3bhaFQ6djtH3P6w6CdVS0LK1aH9ewyx0aAkwDlbO oiGvXbutZMkLpXWAepPjpFaatuL1by0nBgUgPN7k595fuOah6qhbURYO8rZZmA0P
Bug#1011848: marked as done (node-domhandler: FTBFS: node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations.)
Your message dated Sat, 28 May 2022 07:04:14 + with message-id and subject line Bug#1011848: fixed in node-domhandler 5.0.3-2 has caused the Debian Bug report #1011848, regarding node-domhandler: FTBFS: node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations. 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.) -- 1011848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-domhandler Version: 5.0.3-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs > Link ./node_modules/domelementtype -> /usr/share/nodejs/domelementtype > Link ./node_modules/htmlparser2 -> /usr/share/nodejs/htmlparser2 > Link ./node_modules/pretty-format -> /usr/share/nodejs/pretty-format > Link ./node_modules/source-map -> /usr/share/nodejs/source-map > Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node > Copy /usr/share/nodejs/jest-diff -> ./node_modules/ > Copy /usr/share/nodejs/ts-jest -> ./node_modules/ > Copy /usr/share/nodejs/@types/jest -> ./node_modules/@types > Copy /usr/share/nodejs/@types/source-map-support -> ./node_modules/@types >debian/rules override_dh_auto_build > make[1]: Entering directory '/<>' > tsc > node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module > 'jest-matcher-utils' or its corresponding type declarations. > make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2022/05/25/node-domhandler_5.0.3-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: node-domhandler Source-Version: 5.0.3-2 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-domhandler, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-domhandler package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 28 May 2022 07:39:35 +0200 Source: node-domhandler Built-For-Profiles: nocheck Architecture: source Version: 5.0.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1011848 Changes: node-domhandler (5.0.3-2) unstable; urgency=medium . * Team upload * Declare compliance with policy 4.6.1 * Fix build links (Closes: #1011848) * Workaround bad jest config Checksums-Sha1: bbdb2445d9d92abc007ad57d23aaa9387568b282 2264 node-domhandler_5.0.3-2.dsc 11f74acc5abd8bf55989e75d72833c8602f05a17 4948 node-domhandler_5.0.3-2.debian.tar.xz Checksums-Sha256: 15688a5ec48f26d9dd9b527a65acd3af26ba293c4b1fb824581055583a6d9152 2264 node-domhandler_5.0.3-2.dsc 189ff3a5ad9f9c5bc97c3acfdf967fadfe62be1c6f3ea24403cd7b077dc1fd0d 4948 node-domhandler_5.0.3-2.debian.tar.xz Files: 23787369dc1df7507de333f8652cf68c 2264 javascript optional node-domhandler_5.0.3-2.dsc 3c3e8856d0c63ed8de0c9100a33164a4 4948 javascript optional node-domhandler_5.0.3-2.debian.tar.xz -BEGIN PGP
Bug#1011839: marked as done (node-cheerio: FTBFS: ../node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations.)
Your message dated Sat, 28 May 2022 07:03:56 + with message-id and subject line Bug#1011839: fixed in node-cheerio 1.0.0~rc~10+repack-3 has caused the Debian Bug report #1011839, regarding node-cheerio: FTBFS: ../node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations. 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.) -- 1011839: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011839 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-cheerio Version: 1.0.0~rc~10+repack-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build --buildsystem=nodejs > Found debian/nodejs/cheerio-select/build > cd ./cheerio-select && sh -ex ../debian/nodejs/cheerio-select/build > + tsc > ../node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find > module 'jest-matcher-utils' or its corresponding type declarations. > dh_auto_build: error: cd ./cheerio-select && sh -ex > ../debian/nodejs/cheerio-select/build returned exit code 2 > make[1]: *** [debian/rules:11: override_dh_auto_build] Error 25 The full build log is available from: http://qa-logs.debian.net/2022/05/25/node-cheerio_1.0.0~rc~10+repack-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: node-cheerio Source-Version: 1.0.0~rc~10+repack-3 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-cheerio, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-cheerio package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 28 May 2022 08:29:35 +0200 Source: node-cheerio Built-For-Profiles: nocheck Architecture: source Version: 1.0.0~rc~10+repack-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1011839 Changes: node-cheerio (1.0.0~rc~10+repack-3) unstable; urgency=medium . * Declare compliance with policy 4.6.1 * Fix build links (Closes: #1011839) Checksums-Sha1: 490cb2479bdae821345bed711acc3008adffafb7 2885 node-cheerio_1.0.0~rc~10+repack-3.dsc 769078fc38e9c957e72a1457fbf4ad6d65515b2d 11028 node-cheerio_1.0.0~rc~10+repack-3.debian.tar.xz Checksums-Sha256: ffc6bba38f97ce92ba3efc11561063539cda7363a524bf91fdf7893661061857 2885 node-cheerio_1.0.0~rc~10+repack-3.dsc 15c528ada5ce5195d8d423d35f71cee35b15cdc98f084789da9ecdebc26d77b6 11028 node-cheerio_1.0.0~rc~10+repack-3.debian.tar.xz Files: 2df3e05ab5d1b42b96524e9344f41a37 2885 javascript optional node-cheerio_1.0.0~rc~10+repack-3.dsc b793925c9f47e78244b75b0ea40badf9 11028 javascript optional node-cheerio_1.0.0~rc~10+repack-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmKRwxEACgkQ9tdMp8mZ 7ukL/A//Vlpvt4MLYtPJ1Ja22uU+Jlx4RzXIx1cVyk+W7uBEzTlR//TfyTcxiwo7 1D9W94zkCKjOkD5wxYCPyuzuEFGDVUAChHHJZpjiVmjnEFIMIm2Tg5yhoeWTnl8w EJq8uKTk37Xnw4tYklWB9CBmPwWU2W7fd5Wsu0bCohjPn50mI3WxPzSkSHRS7peZ Yf1d4z3V5e/fAJUYzfzuD6EheVOwfD4+nFeDwE4w6horU1RoBjyroUIo5V/xCMgC TNRvPr0ooLWzo+6zf5GZJ9C5MJafbXRKmv+Qg3mZNjbyQ4gjMXVdumE6E7Vj3fHg
Bug#1011798: marked as done (node-css-select: FTBFS: node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations.)
Your message dated Sat, 28 May 2022 07:04:02 + with message-id and subject line Bug#1011798: fixed in node-css-select 4.2.1-3 has caused the Debian Bug report #1011798, regarding node-css-select: FTBFS: node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations. 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.) -- 1011798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-css-select Version: 4.2.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf >dh_auto_configure --buildsystem=nodejs > Link ./node_modules/@babel/parser -> /usr/share/nodejs/@babel/parser > Link ./node_modules/@babel/types -> /usr/share/nodejs/@babel/types > Link ./node_modules/css-what -> /usr/share/nodejs/css-what > Link ./node_modules/domelementtype -> /usr/share/nodejs/domelementtype > Link ./node_modules/htmlparser2 -> /usr/share/nodejs/htmlparser2 > Link ./node_modules/nth-check -> /usr/share/nodejs/nth-check > Link ./node_modules/pretty-format -> /usr/share/nodejs/pretty-format > Link ./node_modules/ts-jest -> /usr/share/nodejs/ts-jest > Link ./node_modules/@types/boolbase -> /usr/share/nodejs/@types/boolbase > Link ./node_modules/@types/istanbul-lib-coverage -> > /usr/share/nodejs/@types/istanbul-lib-coverage > Link ./node_modules/@types/node -> /usr/share/nodejs/@types/node > Copy /usr/share/nodejs/domhandler -> ./node_modules/ > Copy /usr/share/nodejs/domutils -> ./node_modules/ > Copy /usr/share/nodejs/dom-serializer -> ./node_modules/ > Copy /usr/share/nodejs/jest-diff -> ./node_modules/ > Copy /usr/share/nodejs/@types/istanbul-lib-report -> ./node_modules/@types > Copy /usr/share/nodejs/@types/jest -> ./node_modules/@types >debian/rules override_dh_auto_build > make[1]: Entering directory '/<>' > tsc > node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module > 'jest-matcher-utils' or its corresponding type declarations. > make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2 The full build log is available from: http://qa-logs.debian.net/2022/05/25/node-css-select_4.2.1-2_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: node-css-select Source-Version: 4.2.1-3 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-css-select, 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 1011...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-css-select package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 28 May 2022 08:40:35 +0200 Source: node-css-select Built-For-Profiles: nocheck Architecture: source Version: 4.2.1-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1011798 Changes: node-css-select (4.2.1-3) unstable; urgency=medium . * Team upload * Declare compliance with policy 4.6.1 * Fix build links (Closes: #1011798) Checksums-Sha1: db3eace67f0a351e2162423735a1fbc8dccf4d9e 2329 node-css-select_4.2.1-3.dsc
Processed: Bug#1011908 marked as pending in node-css-what
Processing control commands: > tag -1 pending Bug #1011908 [src:node-css-what] node-css-what: FTBFS: node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations. Added tag(s) pending. -- 1011908: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011908 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011908: marked as pending in node-css-what
Control: tag -1 pending Hello, Bug #1011908 in node-css-what 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-css-what/-/commit/cc994598e71fcfe7f74c38f14401aa62f791a934 Fix build links Closes: #1011908 (this message was generated automatically) -- Greetings https://bugs.debian.org/1011908
Processed: Bug#1011798 marked as pending in node-css-select
Processing control commands: > tag -1 pending Bug #1011798 [src:node-css-select] node-css-select: FTBFS: node_modules/@types/jest/index.d.ts(503,30): error TS2307: Cannot find module 'jest-matcher-utils' or its corresponding type declarations. Added tag(s) pending. -- 1011798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011798 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1011798: marked as pending in node-css-select
Control: tag -1 pending Hello, Bug #1011798 in node-css-select 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-css-select/-/commit/d85187e9632dcabb316f471a7cb0f145896845f8 Fix build links Closes: #1011798 (this message was generated automatically) -- Greetings https://bugs.debian.org/1011798
Bug#1011971: libmobi: CVE-2022-1533 CVE-2022-1534 CVE-2022-1907 CVE-2022-1908
Source: libmobi Version: 0.10+dfsg1-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerabilities were published for libmobi. CVE-2022-1533[0]: | Buffer Over-read in GitHub repository bfabiszewski/libmobi prior to | 0.11. This vulnerability is capable of arbitrary code execution. CVE-2022-1534[1]: | Buffer Over-read at parse_rawml.c:1416 in GitHub repository | bfabiszewski/libmobi prior to 0.11. The bug causes the program reads | data past the end of the intented buffer. Typically, this can allow | attackers to read sensitive information from other memory locations or | cause a crash. CVE-2022-1907[2]: | Buffer Over-read in GitHub repository bfabiszewski/libmobi prior to | 0.11. CVE-2022-1908[3]: | Buffer Over-read in GitHub repository bfabiszewski/libmobi prior to | 0.11. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. We can probably wait until upstream releases 0.11, but the RC severity makes sure we do not go unfixed in bookworm. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2022-1533 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1533 [1] https://security-tracker.debian.org/tracker/CVE-2022-1534 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1534 [2] https://security-tracker.debian.org/tracker/CVE-2022-1907 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1907 [3] https://security-tracker.debian.org/tracker/CVE-2022-1908 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-1908 Regards, Salvatore
