Bug#992854: digikam: symbol lookup error: undefined symbol: FT_Palette_Select
On 26/08/2021 00:35, Steven Robbins wrote: ldd /usr/bin/digikam |grep -i freetype Hello, I had a old libfreetype.so.6 sitting in /usr/local. I did make searches for libfreetype but hadn't the reflexe of ldd digikam. Sorry for the error and thanks for your help. Best regards Alain
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 992932 https://github.com/project-gemmi/gemmi/issues/136 Bug #992932 [src:gemmi] gemmi FTBFS on i386: pptest (Failed) Set Bug forwarded-to-address to 'https://github.com/project-gemmi/gemmi/issues/136'. > tags 992932 + confirmed upstream fixed-upstream Bug #992932 [src:gemmi] gemmi FTBFS on i386: pptest (Failed) Added tag(s) confirmed, fixed-upstream, and upstream. > tags 992926 + confirmed upstream Bug #992926 [src:cod-tools] cod-tools: autopkgtest regression on 32bit Added tag(s) confirmed and upstream. > owner 992926 ! Bug #992926 [src:cod-tools] cod-tools: autopkgtest regression on 32bit Owner recorded as Andrius Merkys . > thanks Stopping processing here. Please contact me if you need assistance. -- 992926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992926 992932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#978695: notepadqq: Input windows hangs so input is not possible
Processing control commands: > severity -1 important Bug #978695 [notepadqq] notepadqq: Input windows hangs so input is not possible Severity set to 'important' from 'grave' > tags -1 moreinfo unreproducible Bug #978695 [notepadqq] notepadqq: Input windows hangs so input is not possible Added tag(s) unreproducible and moreinfo. -- 978695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978695 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978695: notepadqq: Input windows hangs so input is not possible
Control: severity -1 important Control: tags -1 moreinfo unreproducible On Wed, 30 Dec 2020 12:42:15 +0100 Michael Rasmussen wrote: > Package: notepadqq > Version: 2.0.0~beta1-1+b1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > When notepadqq is started you expect to see an empty tab > or tabs with reason files, but neither happens. Try to open a tab > resolves in a frozen application and if started from command line > the following is seen: > > js: Uncaught ReferenceError: $ is not defined > js: Uncaught ReferenceError: $ is not defined > Now close application and this is shown: > js: Uncaught TypeError: Cannot read property 'isClean' of undefined > > From here only way to actually quit the application is ^C Hi Michael, Thank you for your bug report. However, when testing on Debian unstable shortly after the Debian 11 (bullseye) release, I am unable to reproduce any of the errors that you encountered in December 2020. Could you please try again and see if you could still see any of such errors? Cheers, Anthony
Bug#990053: Same error on Debian 11
I have the same error on Debian 11:
[...]
yowsup-cli v2.0.15
yowsup v2.5.7
[...]
INFO:yowsup.common.http.warequest:b'{"login":"XXX","param":"authkey","reason":"missing_param","status":"fail"}\n'
status: b'fail'
reason: b'missing_param'
param: b'authkey'
login: b'XXX'
Bug#992854: digikam: symbol lookup error: undefined symbol: FT_Palette_Select
On Tuesday, August 24, 2021 4:32:33 A.M. CDT Alain Bertrand wrote: > > Launching digikam > digikam: symbol lookup error: > /lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5: undefined symbol: > FT_Palette_Select and digikam exits I have not encountered this myself. A quick google suggested possibly an issue with freetype library -- see https://bbs.archlinux.org/viewtopic.php?id=259420 What is output of ldd /usr/bin/digikam |grep -i freetype ? What freetype package/version is installed? Best, -Steve signature.asc Description: This is a digitally signed message part.
Bug#978856: marked as done (libmatheval: ftbfs with autoconf 2.70)
Your message dated Wed, 25 Aug 2021 22:19:28 + with message-id and subject line Bug#978856: fixed in libmatheval 1.1.11+dfsg-5 has caused the Debian Bug report #978856, regarding libmatheval: ftbfs with autoconf 2.70 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.) -- 978856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978856 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libmatheval Version: 1.1.11+dfsg-4 Severity: normal Tags: sid bookworm User: d...@debian.org Usertags: ftbfs-ac270 [This bug report is not targeted to the upcoming bullseye release] The package fails to build in a test rebuild on at least amd64 with autoconf 2.70, but succeeds to build with autoconf 2.69. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://qa-logs.debian.net/2020/09/26.ac270/libmatheval_1.1.11+dfsg-4_unstable_ac270.log The last lines of the build log are at the end of this report. To build with autoconf 2.70, please install the autoconf package from experimental: apt-get -t=experimental install autoconf [...] checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating tests/matheval.sh config.status: creating tests/Makefile config.status: creating Makefile config.status: creating doc/Makefile config.status: creating lib/Makefile config.status: creating libmatheval.pc config.status: creating config.h config.status: executing tests/atconfig commands config.status: executing depfiles commands config.status: executing libtool commands dh_auto_build -O--as-needed make -j4 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in lib make[3]: Entering directory '/<>/lib' /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pthread -I/usr/include/guile/3.0 -c -o parser.lo parser.c /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pthread -I/usr/include/guile/3.0 -c -o scanner.lo scanner.c /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pthread -I/usr/include/guile/3.0 -c -o error.lo error.c /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pthread -I/usr/include/guile/3.0 -c -o matheval.lo matheval.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pthread -I/usr/include/guile/3.0 -c parser.c -fPIC -DPIC -o .libs/parser.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pthread -I/usr/include/guile/3.0 -c error.c -fPIC -DPIC -o .libs/error.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pthread -I/usr/include/guile/3.0 -c scanner.c -fPIC -DPIC -o .libs/scanner.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pthread -I/usr/include/guile/3.0 -c matheval.c -fPIC -DPIC -o .libs/matheval.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pthread -I/usr/include/guile/3.0 -c error.c -o error.o >/dev/null 2>&1 /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pthread -I/usr/include/guile/3.0 -c -o g77_interface.lo g77_interface.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I..
Bug#992924: freefem++: autopkgtest failure on arm64/ppc64el
Hello Adrian, thanks for making the failures visible with this bug. I'm waiting for my access to porter boxes [1] in order to debug and fix the issue(s). In the meantime, do not hesitate to provide patch or any kind of help. Best Regards, François [1]: https://nm.debian.org/process/920/approval/
Bug#992968: marked as done (xarchiver FTBFS: configure: error: cannot find required auxiliary files: compile)
Your message dated Wed, 25 Aug 2021 20:37:38 +
with message-id
and subject line Bug#992968: fixed in xarchiver 1:0.5.4.17-3
has caused the Debian Bug report #992968,
regarding xarchiver FTBFS: configure: error: cannot find required auxiliary
files: compile
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.)
--
992968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992968
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xarchiver
Version: 1:0.5.4.17-2
Severity: serious
Tags: ftbfs
xarchiver fails to build from source in unstable, because configure
misses a compile file. The build ends with:
| dh_auto_configure -- --libexecdir=/usr/lib
| ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --libexecdir=/usr/lib
| configure: error: cannot find required auxiliary files: compile
| tail -v -n \+0 config.log
| ==> config.log <==
| ...
| configure: exit 1
| dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --libexecdir=/usr/lib
returned exit code 1
| make[1]: *** [debian/rules:9: override_dh_auto_configure] Error 25
| make[1]: Leaving directory '/build/1st/xarchiver-0.5.4.17'
| make: *** [debian/rules:5: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Also reproduced by reproducible builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/xarchiver_0.5.4.17-2.rbuild.log.gz
Helmut
--- End Message ---
--- Begin Message ---
Source: xarchiver
Source-Version: 1:0.5.4.17-3
Done: Markus Koschany
We believe that the bug you reported is fixed in the latest version of
xarchiver, 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 992...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Markus Koschany (supplier of updated xarchiver package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Wed, 25 Aug 2021 21:29:43 +0200
Source: xarchiver
Architecture: source
Version: 1:0.5.4.17-3
Distribution: unstable
Urgency: medium
Maintainer: Markus Koschany
Changed-By: Markus Koschany
Closes: 992968
Changes:
xarchiver (1:0.5.4.17-3) unstable; urgency=medium
.
* Do not run autogen.sh script because it does not work with autoconf 2.70.
Run dh_autoreconf instead. (Closes: #992968)
* Declare compliance with Debian Policy 4.6.0.
Checksums-Sha1:
e1c2351986fdff5f0eadaef5ea423928d7dafc0e 2038 xarchiver_0.5.4.17-3.dsc
af38bfb87a4016d71a529cfb442409027d6ff77c 9300
xarchiver_0.5.4.17-3.debian.tar.xz
a68599e2cfc61657e3c39c91bf681f613448201e 14462
xarchiver_0.5.4.17-3_amd64.buildinfo
Checksums-Sha256:
b0f5830703ff0a88cb70a9524a66cfbe29c03ec1ac549d1b4ad9e13cf31e4197 2038
xarchiver_0.5.4.17-3.dsc
2617497ee5ca33d59a134036eb00bacd95606bd731a233525da86c6185054b8c 9300
xarchiver_0.5.4.17-3.debian.tar.xz
438b4479fb46763bbbdf11b4f5b088f992bb586ca1d56d6232f35a9d715bfc82 14462
xarchiver_0.5.4.17-3_amd64.buildinfo
Files:
64649164f8c291e4ec8f65bc8efe9a3f 2038 x11 optional xarchiver_0.5.4.17-3.dsc
8820ece793be59bb524a76ae88995c16 9300 x11 optional
xarchiver_0.5.4.17-3.debian.tar.xz
ed1f8682be94904c45cb670246b1164c 14462 x11 optional
xarchiver_0.5.4.17-3_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAmEmoANfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkxSQQAJCt0Qobv4g+YIA4Pxv8QjdhnuK+AIZU5iKd
poDiC0SyHqBxfWDkGJDDZiqybnVeZWUxQhf/e8krwtR7BnZ5fXuKVMIkeYNaY/hW
n
Bug#983758: marked as done (python-xarray: autopkgtest regression on several architectures)
Your message dated Wed, 25 Aug 2021 20:36:44 + with message-id and subject line Bug#983758: fixed in python-xarray 0.19.0-3 has caused the Debian Bug report #983758, regarding python-xarray: autopkgtest regression on several architectures 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.) -- 983758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983758 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-xarray Version: 0.17.0-1 Severity: serious https://ci.debian.net/data/autopkgtest/testing/arm64/p/python-xarray/10765498/log.gz https://ci.debian.net/data/autopkgtest/testing/arm64/p/python-xarray/10765498/log.gz ... === FAILURES === ___ TestDataArray.test_pad_constant self = def test_pad_constant(self): ar = DataArray(np.arange(3 * 4 * 5).reshape(3, 4, 5)) actual = ar.pad(dim_0=(1, 3)) expected = DataArray( np.pad( np.arange(3 * 4 * 5).reshape(3, 4, 5).astype(np.float32), mode="constant", pad_width=((1, 3), (0, 0), (0, 0)), constant_values=np.nan, ) ) assert actual.shape == (7, 4, 5) assert_identical(actual, expected) ar = xr.DataArray([9], dims="x") actual = ar.pad(x=1) expected = xr.DataArray([np.NaN, 9, np.NaN], dims="x") assert_identical(actual, expected) actual = ar.pad(x=1, constant_values=1.23456) expected = xr.DataArray([1, 9, 1], dims="x") assert_identical(actual, expected) if LooseVersion(np.__version__) >= "1.20": with pytest.raises(ValueError, match="cannot convert float NaN to integer"): ar.pad(x=1, constant_values=np.NaN) else: actual = ar.pad(x=1, constant_values=np.NaN) expected = xr.DataArray( [-9223372036854775808, 9, -9223372036854775808], dims="x" ) > assert_identical(actual, expected) E AssertionError: Left and right DataArray objects are not identical E E Differing values: E L E array([0, 9, 0]) E R E array([-9223372036854775808,9, -9223372036854775808], E dtype=int64) /usr/lib/python3/dist-packages/xarray/tests/test_dataarray.py:4523: AssertionError === warnings summary === ... https://ci.debian.net/data/autopkgtest/testing/i386/p/python-xarray/10765494/log.gz ... === FAILURES === ___ TestDataArray.test_pad_constant self = def test_pad_constant(self): ar = DataArray(np.arange(3 * 4 * 5).reshape(3, 4, 5)) actual = ar.pad(dim_0=(1, 3)) expected = DataArray( np.pad( np.arange(3 * 4 * 5).reshape(3, 4, 5).astype(np.float32), mode="constant", pad_width=((1, 3), (0, 0), (0, 0)), constant_values=np.nan, ) ) assert actual.shape == (7, 4, 5) assert_identical(actual, expected) ar = xr.DataArray([9], dims="x") actual = ar.pad(x=1) expected = xr.DataArray([np.NaN, 9, np.NaN], dims="x") assert_identical(actual, expected) actual = ar.pad(x=1, constant_values=1.23456) expected = xr.DataArray([1, 9, 1], dims="x") assert_identical(actual, expected) if LooseVersion(np.__version__) >= "1.20": with pytest.raises(ValueError, match="cannot convert float NaN to integer"): ar.pad(x=1, constant_values=np.NaN) else: actual = ar.pad(x=1, constant_values=np.NaN) expected = xr.DataArray( [-9223372036854775808, 9, -9223372036854775808], dims="x" ) > assert_identical(actual, expected) E AssertionError: Left and right DataArray objects are not identical E E Differing values: E L E array([-2147483648, 9, -2147483648]) E R E array([-9223372036854775808,9, -9223372036854775808], E dtype=int64) /usr/lib/python3/dist-packages/xarray/tests/test_dataarray.py:4523: AssertionError === warnings summary
Bug#992786: passenger uses many vendored libraries
On Mon, Aug 23, 2021 at 08:18:42AM -0400, Michael Lazin wrote: > I am new to this list and would like to get involved, but I am a relative > beginner in programming. I understand from looking at this CVE that it is > triggered by a particular type of API call, which is probably unlikely in > the wild, unless prior recon has been done and there is already a threat > actor inside. The threat is less than six. I work in security and I have > seen many environments where threats this low are not patched. >... Debian has already issued a security advisory for this specific vulnerabily for the libuv1 package (and sent to the wrong list): https://www.debian.org/security/2021/dsa-4936 My bug report was about passenger having copies of libraries that might also be vulnerable to CVEs like for example this one. > If I would > have time and would want to volunteer help, can someone instruct me how to > get started? Thank you in advance. I apologize if I am making noise on the > list, I just signed up. I thought QA would be an easy way to get started > in the Debian community. Thanks. That's appreciated. General information: https://www.debian.org/intro/help The debian-mentors mailing list would be a good starting point for helping other contributors with problems packaging and maintaining software in Debian. > Michael Lazin >... cu Adrian
Bug#992975: Acknowledgement (Does not work on bullseye)
Severity: normal Hello, update/correction: the plugin still works with the usual vim-addon-manager Enrico -- GPG key: 4096R/634F4BD1E7AD5568 2009-05-08 Enrico Zini
Bug#978766: aprx: ftbfs with autoconf 2.70
Hi there, Do you have any recommendations on where to start with this bug? I've tried running autoupdate & autoreconf to no success - hibby@fennec ~/D/D/a/aprx (master)> autoreconf autoreconf: warning: autoconf input should be named 'configure.ac', not 'configure.in' aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in' configure.in:221: warning: The macro `AC_TRY_LINK' is obsolete. configure.in:221: You should run autoupdate. ./lib/autoconf/general.m4:2920: AC_TRY_LINK is expanded from... lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from... lib/m4sugar/m4sh.m4:699: AS_IF is expanded from... ./lib/autoconf/general.m4:2894: _AC_LINK_IFELSE is expanded from... ./lib/autoconf/general.m4:2911: AC_LINK_IFELSE is expanded from... lib/m4sugar/m4sh.m4:692: _AS_IF_ELSE is expanded from... lib/m4sugar/m4sh.m4:699: AS_IF is expanded from... ./lib/autoconf/libs.m4:100: AC_CHECK_LIB is expanded from... configure.in:221: the top level autoheader: warning: autoconf input should be named 'configure.ac', not 'configure.in' While I get changes I can capture in a patch, I still can't get this to build. Is there any documentation/resource I can read for assistance? Cheers DH -- Hibby MM0RFN On Thu, 31 Dec 2020, at 2:26 PM, Matthias Klose wrote: > Package: src:aprx > Version: 2.9.0+dfsg-2 > Severity: normal > Tags: sid bookworm > User: d...@debian.org > Usertags: ftbfs-ac270 > > [This bug report is not targeted to the upcoming bullseye release] > > The package fails to build in a test rebuild on at least amd64 with > autoconf 2.70, but succeeds to build with autoconf 2.69. The > severity of this report will be raised before the bookworm release, > so nothing has to be done for the bullseye release. > > The full build log can be found at: > http://qa-logs.debian.net/2020/09/26.ac270/aprx_2.9.0+dfsg-2_unstable_ac270.log > The last lines of the build log are at the end of this report. > > To build with autoconf 2.70, please install the autoconf package from > experimental: apt-get -t=experimental install autoconf > > [...] > LD='gcc' > LDFLAGS='-Wl,-z,relro -Wl,-z,now -Wl,--as-needed' > LIBCRYPTO='' > LIBGETADDRINFO='' > LIBM='' > LIBOBJS='' > LIBPTHREAD='' > LIBRESOLV='' > LIBRT='' > LIBS='' > LIBSOCKET='' > LIBSSL='' > LTLIBOBJS='' > OBJEXT='o' > PACKAGE_BUGREPORT='' > PACKAGE_NAME='' > PACKAGE_STRING='' > PACKAGE_TARNAME='' > PACKAGE_URL='' > PACKAGE_VERSION='' > PAT
Bug#992921: marked as done (timeshift: util-linux 2.37.2-1 breaks timeshift)
Your message dated Wed, 25 Aug 2021 19:35:25 + with message-id and subject line Bug#992921: fixed in timeshift 20.11.1-1.1 has caused the Debian Bug report #992921, regarding timeshift: util-linux 2.37.2-1 breaks timeshift 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.) -- 992921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992921 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: timeshift Version: 20.11.1-1 Severity: important X-Debbugs-Cc: rubenswa...@protonmail.com Dear Maintainer, Using the patch from kdmurthy in this thread https://github.com/teejee2008/timeshift/issues/753 fixed the problem for me. *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: 11.0 APT prefers testing APT policy: (990, 'testing'), (500, 'oldstable-updates'), (500, 'unstable'), (500, 'oldstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-8-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages timeshift depends on: ii libc62.31-13 ii libcairo21.16.0-5 ii libgdk-pixbuf-2.0-0 2.42.6+dfsg-2 ii libgee-0.8-2 0.20.4-1 ii libglib2.0-0 2.68.4-1 ii libgtk-3-0 3.24.30-1 ii libjson-glib-1.0-0 1.6.2-1 ii libvte-2.91-00.62.3-1 ii psmisc 23.4-2 ii rsync3.2.3-4 timeshift recommends no packages. timeshift suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: timeshift Source-Version: 20.11.1-1.1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of timeshift, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated timeshift package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 25 Aug 2021 14:21:02 -0400 Source: timeshift Architecture: source Version: 20.11.1-1.1 Distribution: unstable Urgency: high Maintainer: Yanhao Mo Changed-By: Boyuan Yang Closes: 992921 Changes: timeshift (20.11.1-1.1) unstable; urgency=high . * Non-maintainer upload. * Refresh packaging: + Bump Standards-Version to 4.6.0. + Bump debhelper-compat to v13. * debian/control: + Use github repo as homepage since original homepage is not working. + Add Breaks: util-linux (<< 2.37.2~) due to #992921. * debian/patches/d437..patch: Add upstream patch to fix compatibility with new util-linux. (Closes: #992921) * debian/rules: Remove broken upstream-provided man page before dh_installman (required by debhelper compat v13). Checksums-Sha1: f2c1382fc2c08aea73eac8f04893edbc67db2dae 1974 timeshift_20.11.1-1.1.dsc d35653aee927b963791f90edefcc835c2cd18d90 1401165 timeshift_20.11.1.orig.tar.gz 1785a6781d72a4e1deedd9dc773087b1f007a3fc 12592 timeshift_20.11.1-1.1.debian.tar.xz db5e0bcd850ce144c74963ec9f937b71e757ca0c 14439 timeshift_20.11.1-1.1_amd64.buildinfo Checksums-Sha256: 5bfd850fa292029b8b660cae47fd7c76ef6ad7938342d25100ab4cbebd9ac677 1974 timeshift_20.11.1-1.1.dsc c6dcca80b42f80a8c8d9d03e91eb17aa634be2f1031f667bba3f483410297abb 1401165 timeshift_20.11.1.orig.tar.gz e45759e190baf11b1b47ebaba3701a91b4d5d859988e4922c80b5b4ba94a9e9b 12592 timeshift_20.11.1-1.1.debian.tar.xz 6b9ffdeda953838e731f61a3006464b4b67f3710bc270ddf81a7e0c7a55462f4 14439 timeshift_20.11.1-1.1_amd64.buildinfo Files: e9f1cf2c9e749880056b561e574e1b49 1974 utils optional timeshift_20.11.1-1.1.dsc ca9e2c5261850d8fd51992188ea508dc 1401165 utils optional timeshift_2
Bug#992975: Does not work on bullseye
Package: vim-syntastic Version: 3.10.0-2 Severity: serious Hello, the upgrade instructions for bullseye say: * Before upgrading, run "vam remove " for any addon in this package that has been installed with "vam install ". Adjust the command as necessary for system-wide installed addon. * After upgrading, add "packadd! " to your vimrc for any addon that you want to use. The addon name can be found in the package description or the list of directories under /usr/share/vim-scripts. However, when I add `packadd! syntastic` in .vimrc, I get this error: E919: Directory not found in 'packpath': "pack/*/opt/syntastic" Using packadd! on, say, nerd-commenter (distributed by vim-scripts) works fine. It looks like vim-syntastic missed the update that vim-scripts had. /usr/share/doc/vim-syntastic/README.Debian doesn't mention anything relevant (and there's a typo where it says "pathogen" instead of "syntastic"). Unfortunately I don't know anything about vim plugin packaging and I can't be much of use, besides reporting the issue :( Enrico -- System Information: Debian Release: 11.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.0-0.bpo.7-amd64 (SMP w/4 CPU threads) Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vim-syntastic depends on: ii vim2:8.2.2434-3 ii vim-addon-manager 0.5.10 vim-syntastic recommends no packages. Versions of packages vim-syntastic suggests: pn checkstyle pn chktex pn closure-linter ii cppcheck 2.3-1 pn foodcritic pn hlint pn lacheck pn libperl-critic-perl ii libxml2-utils2.9.10+dfsg-6.7 pn pep8 pn puppet-lint pn pyflakes ii pylint 2.7.2-3 pn python-flake8 pn shellcheck pn sparse pn splint ii tidy 2:5.6.0-11 -- no debconf information
Bug#992973: plib: CVE-2021-38714
Source: plib Version: 1.8.5-8 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://sourceforge.net/p/plib/bugs/55/ X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for plib. CVE-2021-38714[0]: | In Plib through 1.85, there is an integer overflow vulnerability that | could result in arbitrary code execution. The vulnerability is found | in ssgLoadTGA() function in src/ssg/ssgLoadTGA.cxx file. The severity of the this bug is set op purpose higher as it is probably warranted. There is the following reason for that: plib is orphaned in Debian for a while, it is obsoleted and unmaintained upstream as well. Ideally it get's removed from Debian from the next release, but thee would be some revers dependencies issues to be solved, making it imposssible for now to remove the package: | Checking reverse dependencies... | # Broken Depends: | crrcsim: crrcsim [amd64 arm64 armhf i386 mips64el mipsel ppc64el s390x] | flightgear: flightgear | openuniverse: openuniverse | stormbaancoureur: stormbaancoureur | torcs: torcs | | # Broken Build-Depends: | crrcsim: libplib-dev | flightgear: libplib-dev | torcs: libplib-dev | | Dependency problem found. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-38714 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-38714 [1] https://sourceforge.net/p/plib/bugs/55/ Regards, Salvatore
Processed: Re: timeshift: util-linux 2.37.2-1 breaks timeshift
Processing control commands: > severity -1 grave Bug #992921 [timeshift] timeshift: util-linux 2.37.2-1 breaks timeshift Severity set to 'grave' from 'important' > tags -1 +bookworm +sid Bug #992921 [timeshift] timeshift: util-linux 2.37.2-1 breaks timeshift Added tag(s) bookworm. Bug #992921 [timeshift] timeshift: util-linux 2.37.2-1 breaks timeshift Added tag(s) sid. -- 992921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992921 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992968: xarchiver FTBFS: configure: error: cannot find required auxiliary files: compile
Source: xarchiver
Version: 1:0.5.4.17-2
Severity: serious
Tags: ftbfs
xarchiver fails to build from source in unstable, because configure
misses a compile file. The build ends with:
| dh_auto_configure -- --libexecdir=/usr/lib
| ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --libexecdir=/usr/lib
| configure: error: cannot find required auxiliary files: compile
| tail -v -n \+0 config.log
| ==> config.log <==
| ...
| configure: exit 1
| dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --libexecdir=/usr/lib
returned exit code 1
| make[1]: *** [debian/rules:9: override_dh_auto_configure] Error 25
| make[1]: Leaving directory '/build/1st/xarchiver-0.5.4.17'
| make: *** [debian/rules:5: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
Also reproduced by reproducible builds:
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/xarchiver_0.5.4.17-2.rbuild.log.gz
Helmut
Processed: tagging 992960
Processing commands for cont...@bugs.debian.org: > tags 992960 + pending Bug #992960 [src:nfstrace] nfstrace: FTBFS due to RPC removal from glibc Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 992960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978923: marked as done (wide-dhcpv6: ftbfs with autoconf 2.70)
Your message dated Thu, 26 Aug 2021 02:25:43 +0900 with message-id and subject line Re: Bug#978923: wide-dhcpv6: ftbfs with autoconf 2.70 has caused the Debian Bug report #978923, regarding wide-dhcpv6: ftbfs with autoconf 2.70 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.) -- 978923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:wide-dhcpv6 Version: 20080615-23 Severity: normal Tags: sid bookworm User: d...@debian.org Usertags: ftbfs-ac270 [This bug report is not targeted to the upcoming bullseye release] The package fails to build in a test rebuild on at least amd64 with autoconf 2.70, but succeeds to build with autoconf 2.69. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://qa-logs.debian.net/2020/09/26.ac270/wide-dhcpv6_20080615-23_unstable_ac270.log The last lines of the build log are at the end of this report. To build with autoconf 2.70, please install the autoconf package from experimental: apt-get -t=experimental install autoconf [...] 137 | %type IFNAME HOSTNAME AUTHNAME KEYNAME DUID_ID STRING QSTRING I... | ^~ cfparse.y:137.61-67: warning: POSIX yacc reserves %type to nonterminals [-Wyacc] 137 | %type IFNAME HOSTNAME AUTHNAME KEYNAME DUID_ID STRING QSTRING I... | ^~~ cfparse.y:137.69-72: warning: POSIX yacc reserves %type to nonterminals [-Wyacc] 137 | %type IFNAME HOSTNAME AUTHNAME KEYNAME DUID_ID STRING QSTRING I... | ^ cfparse.y:138.13-20: warning: POSIX yacc reserves %type to nonterminals [-Wyacc] 138 | %type POOLNAME PROFILENAME | ^~~~ cfparse.y:138.22-32: warning: POSIX yacc reserves %type to nonterminals [-Wyacc] 138 | %type POOLNAME PROFILENAME | ^~~ cfparse.y:139.13-18: warning: POSIX yacc reserves %type to nonterminals [-Wyacc] 139 | %type NUMBER duration authproto authalg authrdm | ^~ mv y.tab.c cfparse.c yacc cfparse.y cfparse.y:137.13-18: warning: POSIX yacc reserves %type to nonterminals [-Wyacc] 137 | %type IFNAME HOSTNAME AUTHNAME KEYNAME DUID_ID STRING QSTRING I... | ^~ cfparse.y:137.20-27: warning: POSIX yacc reserves %type to nonterminals [-Wyacc] 137 | %type IFNAME HOSTNAME AUTHNAME KEYNAME DUID_ID STRING QSTRING I... |^~~~ cfparse.y:137.29-36: warning: POSIX yacc reserves %type to nonterminals [-Wyacc] 137 | %type IFNAME HOSTNAME AUTHNAME KEYNAME DUID_ID STRING QSTRING I... | ^~~~ cfparse.y:137.38-44: warning: POSIX yacc reserves %type to nonterminals [-Wyacc] 137 | %type IFNAME HOSTNAME AUTHNAME KEYNAME DUID_ID STRING QSTRING I... | ^~~ cfparse.y:137.46-52: warning: POSIX yacc reserves %type to nonterminals [-Wyacc] 137 | %type IFNAME HOSTNAME AUTHNAME KEYNAME DUID_ID STRING QSTRING I... | ^~~ cfparse.y:137.54-59: warning: POSIX yacc reserves %type to nonterminals [-Wyacc] 137 | %type IFNAME HOSTNAME AUTHNAME KEYNAME DUID_ID STRING QSTRING I... | ^~ cfparse.y:137.61-67: warning: POSIX yacc reserves %type to nonterminals [-Wyacc] 137 | %type IFNAME HOSTNAME AUTHNAME KEYNAME DUID_ID STRING QSTRING I... | ^~~ cfparse.y:137.69-72: warning: POSIX yacc reserves %type to nonterminals [-Wyacc] 137 | %type IFNAME HOSTNAME AUTHNAME KEYNAME DUID_ID STRING QSTRING I... | ^ cfparse.y:138.13-20: warning: POSIX yacc reserves %type to nonterminals [-Wyacc] 138 | %type POOLNAME PROFILENAME | ^~~~ cfparse.y:138.22-32: warning: POSIX yacc reserves %type to nonterminals [-Wyacc] 138 | %type POOLNAME PROFILENAME | ^~~ cfparse.y:139.13-18: warning: POSIX yacc reserves %type to nonterminals [-Wyacc] 139 | %type NUMBER duration authproto authalg authrdm | ^~ mv -f y.tab.c cfparse.c gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -I. -Wd
Bug#978818: closing 978818
close 978818 thanks i'm closing this as unreproducible. E.g. in https://salsa.debian.org/multimedia-team/pd/gem/-/pipelines/280549 all jobs succeed. The builds use autoconf_2.71-2 (and 'malloc' is properly detected).
Processed: closing 978818
Processing commands for cont...@bugs.debian.org: > close 978818 Bug #978818 [src:gem] gem: ftbfs with autoconf 2.70 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 978818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978818 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992902: marked as done (lizzie build-depends on removed package)
Your message dated Wed, 25 Aug 2021 16:34:17 + with message-id and subject line Bug#992902: fixed in lizzie 0.7.4+dfsg1-3 has caused the Debian Bug report #992902, regarding lizzie build-depends on removed package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 992902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: lizzie version: 0.7.4+dfsg1-2 severity: serious lizzie build-depends on libjuniversalchardet-java-doc which is no longer built by the libjuniversalchardet-java source package. It is still present in unstable as a cruft package but is completely gone from testing. --- End Message --- --- Begin Message --- Source: lizzie Source-Version: 0.7.4+dfsg1-3 Done: tony mancill We believe that the bug you reported is fixed in the latest version of lizzie, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill (supplier of updated lizzie package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 25 Aug 2021 08:55:22 -0700 Source: lizzie Architecture: source Version: 0.7.4+dfsg1-3 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: tony mancill Closes: 992902 Changes: lizzie (0.7.4+dfsg1-3) unstable; urgency=medium . * Team upload. * Drop build-dep on libjuniversalchardet-java-doc (Closes: #992902) * Use debhelper-compat 13 * Bump Standards-Version to 4.6.0 * Mark liblizzie-java-doc as Multi-Arch: foreign * Set Rules-Requires-Root: no in debian/control Checksums-Sha1: 60c4adce7ffac0fd3208077bf0df349fc3376bad 2409 lizzie_0.7.4+dfsg1-3.dsc 51b537ea67ecb5f9c8d9f985b88b35101cc6bfa7 22900 lizzie_0.7.4+dfsg1-3.debian.tar.xz 4ab9340a2c19ba089fa9f3166ea997f3238dd2d2 14374 lizzie_0.7.4+dfsg1-3_amd64.buildinfo Checksums-Sha256: 5af8aed874e83253534ab7be981c7d237d939e8b488dcfc25edadeec5a175b18 2409 lizzie_0.7.4+dfsg1-3.dsc 2c568a129b385e65c496e0b80568c51a08c69784a03a69aef68e57593a03ccf0 22900 lizzie_0.7.4+dfsg1-3.debian.tar.xz 0711beb24cce66e34e1914fbff34acfda5b20b7a83b41103e773a422f8f03047 14374 lizzie_0.7.4+dfsg1-3_amd64.buildinfo Files: 9e744d3cfa8865b309534ad1f2a09cbe 2409 games optional lizzie_0.7.4+dfsg1-3.dsc 5a8bbc7ef5158e40623270b12d41cfd0 22900 games optional lizzie_0.7.4+dfsg1-3.debian.tar.xz f8c2dce6d2a50f2130d1cdbf7d4afee5 14374 games optional lizzie_0.7.4+dfsg1-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmEma7wUHHRtYW5jaWxs QGRlYmlhbi5vcmcACgkQIdIFiZdLPpYm0g//bks9ugWloVgH96PEibV0iGOq7RP6 2s5ae1+fFNiD5kFWvrx8xFZtBPI97GzX6mqedHbcU8r3xD+Hwfi2w3JvPG0K4xPm fG4B7a8ih4ozfxiD7RZt4NHOlMqmGwnoxC2tQvtKIMiPQXc7XezKx2w6q0IdGhU6 74uRpx2dR7sUSKBVqB//2mt/XDuU80oPyKf4ydooGFTOS2trJPCNBFavRkwx+ax2 FGw5VrcJPARGY2eCRooh91jX1quM84VekcxRajnk2r/CZQsBWjS7Hq32VzVBYZs+ 7uhGsZtusX34L3KHaJpEMA7cF2R0JdgNAViEkzngeVdGM0Wvs+BLq3PGUHaoRR6B gZqrKrokD2p9evllK91EfEyY382pBYsddJmAuvbwfXYqBOi3KlOcoBYbzHy81UYL VUaToCHFCeJekIdI3bo2GUOXAlw9LJ42ZVz3mvL+jtBIH/RmWOdCWHAUwFI7IHt6 Wr1f0PXcaxuuucc/8OCrM6/kIOOHFgbktXljZd/zVBr4vs2pjNd/FR/g7xv45u3M RcAFsMr3tGIRIlLFGW7HMVtxuw3ON0kol4GTzX2KixpbCFwSbvzuAOi0hC6tEA8c 8CouECuhypIIYYzwmq1Dp1E2CA4Knjlhwo0WN3gUrQLqxMX6sxz+MZfGYEhR8y8v m/46uB1wyHPABSg= =zTDP -END PGP SIGNATURE End Message ---
Bug#992964: gadap: FTBFS due to RPC removal from glibc
Source: gadap
Version: 2.0-12
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
The glibc SunRPC implementation has been marked obsolete for some time.
It has been removed upstream from glibc 2.32, and it got disabled in the
recent glibc uploads. The TI RPC implementation should be used instead.
For this reason gadap now fails to build from source. You will find
attached a patch to switch to the TI RPC implementation, fixing the
FTBFS.
Regards,
Aurelien
--- gadap-2.0/debian/control
+++ gadap-2.0/debian/control
@@ -4,7 +4,8 @@
Maintainer: Alastair McKinstry
Build-Depends: debhelper-compat (= 13),
libdap-dev (>= 3.14.0-4),
- libcurl4-gnutls-dev | libcurl-dev, libxml2-dev
+ libcurl4-gnutls-dev | libcurl-dev, libxml2-dev,
+ pkg-config, libtirpc-dev
Standards-Version: 4.5.1
Homepage: http://cola.gmu.edu/grads/grads.php
Vcs-Browser: https://salsa.debian.org:/science-team/gadap.git
--- gadap-2.0/debian/patches/libtirpc.patch
+++ gadap-2.0/debian/patches/libtirpc.patch
@@ -0,0 +1,29 @@
+Description: Switch to the TI RPC implementation
+Author: Aurelien Jarno
+Last-Updated: 2021-08-25
+Forwarded: no
+
+--- gadap-2.0.orig/configure.ac
gadap-2.0/configure.ac
+@@ -27,6 +27,13 @@ AC_FUNC_STRTOD
+ AC_CHECK_FUNCS([memset])
+
+ dnl Checks for specific libraries
++PKG_CHECK_MODULES([TIRPC], [libtirpc],
++ [
++ LIBS="$LIBS $TIRPC_LIBS"
++ CPPFLAGS="$CPPFLAGS $TIRPC_CFLAGS"
++ ],
++ [ AC_MSG_ERROR([Cannot find libtirpc])
++])
+ AC_CHECK_LIBDAP([3.7.3],
+ [
+ LIBS="$LIBS $DAP_LIBS $DAP_LIBS"
+--- gadap-2.0.orig/gadap.pc.in
gadap-2.0/gadap.pc.in
+@@ -10,4 +10,4 @@ Description:
+ Version: @PACKAGE_VERSION@
+ Libs: -L${libdir} -lgadap
+ Libs.private: -lpthread
+-Requires: libdapclient libdapserver
++Requires: libdapclient libdapserver libtirpc
--- gadap-2.0/debian/patches/series
+++ gadap-2.0/debian/patches/series
@@ -2,3 +2,4 @@
libdap-namespace.patch
test-errors.patch
pkg-config.patch
+libtirpc.patch
Bug#992963: netkit-rwall: FTBFS due to RPC removal from glibc
Source: netkit-rwall
Version: 0.17-8
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
The glibc SunRPC implementation has been marked obsolete for some time.
It has been removed upstream from glibc 2.32, and it got disabled in the
recent glibc uploads. The TI RPC implementation should be used instead.
For this reason netkit-rwall now fails to build from source. You will
find attached a patch to switch to the TI RPC implementation, fixing the
FTBFS.
Regards,
Aurelien
--- netkit-rwall-0.17/debian/control
+++ netkit-rwall-0.17/debian/control
@@ -3,7 +3,7 @@
Priority: optional
Maintainer: Alberto Gonzalez Iniesta
Standards-Version: 4.2.1
-Build-Depends: debhelper (>= 10~), cmake
+Build-Depends: debhelper (>= 10~), cmake, pkg-config, libtirpc-dev
Package: rwalld
Architecture: any
--- netkit-rwall-0.17/debian/patches/series
+++ netkit-rwall-0.17/debian/patches/series
@@ -1,3 +1,4 @@
define-salen.patch
fix-typo.patch
use-cmake-as-buildsystem.patch
+use-cmake-as-buildsystem-tirpc.patch
--- netkit-rwall-0.17/debian/patches/use-cmake-as-buildsystem-tirpc.patch
+++ netkit-rwall-0.17/debian/patches/use-cmake-as-buildsystem-tirpc.patch
@@ -0,0 +1,38 @@
+Description: Use TI RPC instead of GNU libc RPC
+Author: Aurelien Jarno
+Forwarded: no
+Last-Update: 2021-08-25
+
+--- netkit-rwall-0.17.orig/CMakeLists.txt
netkit-rwall-0.17/CMakeLists.txt
+@@ -5,5 +5,8 @@ set(BIN_DIR "${CMAKE_INSTALL_PREFIX}/bin
+ set(SBIN_DIR "${CMAKE_INSTALL_PREFIX}/sbin")
+ set(MAN_DIR "${CMAKE_INSTALL_PREFIX}/share/man")
+
++find_package(PkgConfig REQUIRED)
++pkg_check_modules(TIRPC REQUIRED libtirpc)
++
+ add_subdirectory(rpc.rwalld)
+ add_subdirectory(rwall)
+--- netkit-rwall-0.17.orig/rpc.rwalld/CMakeLists.txt
netkit-rwall-0.17/rpc.rwalld/CMakeLists.txt
+@@ -15,6 +15,8 @@ add_executable(
+ rwalld.c
+ rwall.h
+ )
++target_include_directories(rpc.rwalld PUBLIC ${TIRPC_INCLUDE_DIRS})
++target_link_libraries(rpc.rwalld ${TIRPC_LIBRARIES})
+ install(
+ TARGETS rpc.rwalld
+ DESTINATION ${SBIN_DIR}
+--- netkit-rwall-0.17.orig/rwall/CMakeLists.txt
netkit-rwall-0.17/rwall/CMakeLists.txt
+@@ -14,6 +14,8 @@ add_executable(
+ rwall.c
+ rwall.h
+ )
++target_include_directories(rwall PUBLIC ${TIRPC_INCLUDE_DIRS})
++target_link_libraries(rwall ${TIRPC_LIBRARIES})
+ install(
+ TARGETS rwall
+ DESTINATION ${BIN_DIR}
Bug#992962: netkit-rusers: FTBFS due to RPC removal from glibc
Source: netkit-rusers
Version: 0.17-10
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
The glibc SunRPC implementation has been marked obsolete for some time.
It has been removed upstream from glibc 2.32, and it got disabled in the
recent glibc uploads. The TI RPC implementation should be used instead.
For this reason netkit-rusers now fails to build from source. You will
find attached a patch to switch to the TI RPC implementation, fixing the
FTBFS.
Regards,
Aurelien
--- netkit-rusers-0.17/debian/control
+++ netkit-rusers-0.17/debian/control
@@ -3,7 +3,7 @@
Priority: optional
Maintainer: Alberto Gonzalez Iniesta
Standards-Version: 4.2.1
-Build-Depends: debhelper (>= 11), cmake
+Build-Depends: debhelper (>= 11), cmake, pkg-config, libtirpc-dev
Package: rusersd
Architecture: any
--- netkit-rusers-0.17/debian/patches/series
+++ netkit-rusers-0.17/debian/patches/series
@@ -2,3 +2,4 @@
system-headers-location.patch
use-cmake-as-buildsystem.patch
use-cmake-as-buildsystem-debian-extras.patch
+use-cmake-as-buildsystem-tirpc.patch
--- netkit-rusers-0.17/debian/patches/use-cmake-as-buildsystem-tirpc.patch
+++ netkit-rusers-0.17/debian/patches/use-cmake-as-buildsystem-tirpc.patch
@@ -0,0 +1,50 @@
+Description: Use TI RPC instead of GNU libc RPC
+Author: Aurelien Jarno
+Forwarded: no
+Last-Update: 2021-08-25
+
+--- netkit-rusers-0.17.orig/CMakeLists.txt
netkit-rusers-0.17/CMakeLists.txt
+@@ -7,6 +7,9 @@ set(MAN_DIR "${CMAKE_INSTALL_PREFIX}/sha
+
+ set(USE_GLIBC 1)
+
++find_package(PkgConfig REQUIRED)
++pkg_check_modules(TIRPC REQUIRED libtirpc)
++
+ add_subdirectory(rpc.rusersd)
+ add_subdirectory(rup)
+ add_subdirectory(rusers)
+--- netkit-rusers-0.17.orig/rpc.rusersd/CMakeLists.txt
netkit-rusers-0.17/rpc.rusersd/CMakeLists.txt
+@@ -21,6 +21,8 @@ add_executable(
+ daemon.c
+ rusers.h
+ )
++target_include_directories(rpc.rusersd PUBLIC ${TIRPC_INCLUDE_DIRS})
++target_link_libraries(rpc.rusersd ${TIRPC_LIBRARIES})
+ install(
+ TARGETS rpc.rusersd
+ DESTINATION ${SBIN_DIR}
+--- netkit-rusers-0.17.orig/rup/CMakeLists.txt
netkit-rusers-0.17/rup/CMakeLists.txt
+@@ -16,6 +16,8 @@ add_executable(
+ rstat_xdr.c
+ rstat.h
+ )
++target_include_directories(rup PUBLIC ${TIRPC_INCLUDE_DIRS})
++target_link_libraries(rup ${TIRPC_LIBRARIES})
+ install(
+ TARGETS rup
+ DESTINATION ${BIN_DIR}
+--- netkit-rusers-0.17.orig/rusers/CMakeLists.txt
netkit-rusers-0.17/rusers/CMakeLists.txt
+@@ -23,6 +23,8 @@ add_executable(
+ rusers_xdr.c
+ rusers.h
+ )
++target_include_directories(rusers PUBLIC ${TIRPC_INCLUDE_DIRS})
++target_link_libraries(rusers ${TIRPC_LIBRARIES})
+ install(
+ TARGETS rusers
+ DESTINATION ${BIN_DIR}
Bug#992961: netkit-bootparamd: FTBFS due to RPC removal from glibc
Source: netkit-bootparamd
Version: 0.17-10
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
The glibc SunRPC implementation has been marked obsolete for some time.
It has been removed upstream from glibc 2.32, and it got disabled in the
recent glibc uploads. The TI RPC implementation should be used instead.
For this reason netkit-bootparamd now fails to build from source. You
will find attached a patch to switch to the TI RPC implementation,
fixing the FTBFS.
Regards,
Aurelien
--- netkit-bootparamd-0.17/debian/control
+++ netkit-bootparamd-0.17/debian/control
@@ -3,7 +3,7 @@
Priority: optional
Maintainer: Alberto Gonzalez Iniesta
Standards-Version: 4.3.0
-Build-Depends: debhelper (>= 10~), cmake
+Build-Depends: debhelper (>= 10~), cmake, pkg-config, libtirpc-dev
Package: bootparamd
Architecture: any
--- netkit-bootparamd-0.17/debian/patches/series
+++ netkit-bootparamd-0.17/debian/patches/series
@@ -1,3 +1,5 @@
fix-getopt-return-type.patch
use-cmake-as-buildsystem.patch
use-cmake-as-buildsystem-debian-extras.patch
+use-cmake-as-buildsystem-tirpc.patch
+tirpc-drop-glibc-fix.patch
--- netkit-bootparamd-0.17/debian/patches/tirpc-drop-glibc-fix.patch
+++ netkit-bootparamd-0.17/debian/patches/tirpc-drop-glibc-fix.patch
@@ -0,0 +1,19 @@
+Description: Drop a GNU libc fix now that TI RPC is used instead
+Author: Aurelien Jarno
+Forwarded: no
+Last-Update: 2021-08-25
+
+--- netkit-bootparamd-0.17.orig/rpc.bootparamd/main.c
netkit-bootparamd-0.17/rpc.bootparamd/main.c
+@@ -16,11 +16,6 @@
+ #include "bootparam_prot.h"
+
+
+-#ifdef __GLIBC__
+- /* quick fix */
+- void get_myaddress(struct sockaddr_in *);
+-#endif
+-
+ int debug = 0;
+ int dolog = 0;
+ struct in_addr route_addr;
--- netkit-bootparamd-0.17/debian/patches/use-cmake-as-buildsystem-tirpc.patch
+++ netkit-bootparamd-0.17/debian/patches/use-cmake-as-buildsystem-tirpc.patch
@@ -0,0 +1,35 @@
+Description: Use TI RPC instead of GNU libc RPC
+Author: Aurelien Jarno
+Forwarded: no
+Last-Update: 2021-08-25
+
+--- netkit-bootparamd-0.17.orig/CMakeLists.txt
netkit-bootparamd-0.17/CMakeLists.txt
+@@ -5,4 +5,7 @@ set(BIN_DIR "${CMAKE_INSTALL_PREFIX}/bin
+ set(SBIN_DIR "${CMAKE_INSTALL_PREFIX}/sbin")
+ set(MAN_DIR "${CMAKE_INSTALL_PREFIX}/share/man")
+
++find_package(PkgConfig REQUIRED)
++pkg_check_modules(TIRPC REQUIRED libtirpc)
++
+ add_subdirectory(rpc.bootparamd)
+--- netkit-bootparamd-0.17.orig/rpc.bootparamd/CMakeLists.txt
netkit-bootparamd-0.17/rpc.bootparamd/CMakeLists.txt
+@@ -13,6 +13,8 @@ add_executable(
+
+ bootparam_prot.h
+ )
++target_include_directories(rpc.bootparamd PUBLIC ${TIRPC_INCLUDE_DIRS})
++target_link_libraries(rpc.bootparamd ${TIRPC_LIBRARIES})
+ add_executable(
+ callbootd
+
+@@ -22,6 +24,8 @@ add_executable(
+
+ bootparam_prot.h
+ )
++target_include_directories(callbootd PUBLIC ${TIRPC_INCLUDE_DIRS})
++target_link_libraries(callbootd ${TIRPC_LIBRARIES})
+
+ install(
+ TARGETS rpc.bootparamd
--- netkit-bootparamd-0.17/debian/control
+++ netkit-bootparamd-0.17/debian/control
@@ -3,7 +3,7 @@
Priority: optional
Maintainer: Alberto Gonzalez Iniesta
Standards-Version: 4.3.0
-Build-Depends: debhelper (>= 10~), cmake
+Build-Depends: debhelper (>= 10~), cmake, pkg-config, libtirpc-dev
Package: bootparamd
Architecture: any
--- netkit-bootparamd-0.17/debian/patches/series
+++ netkit-bootparamd-0.17/debian/patches/series
@@ -1,3 +1,5 @@
fix-getopt-return-type.patch
use-cmake-as-buildsystem.patch
use-cmake-as-buildsystem-debian-extras.patch
+use-cmake-as-buildsystem-tirpc.patch
+tirpc-drop-glibc-fix.patch
--- netkit-bootparamd-0.17/debian/patches/tirpc-drop-glibc-fix.patch
+++ netkit-bootparamd-0.17/debian/patches/tirpc-drop-glibc-fix.patch
@@ -0,0 +1,19 @@
+Description: Drop a GNU libc fix now that TI RPC is used instead
+Author: Aurelien Jarno
+Forwarded: no
+Last-Update: 2021-08-25
+
+--- netkit-bootparamd-0.17.orig/rpc.bootparamd/main.c
netkit-bootparamd-0.17/rpc.bootparamd/main.c
+@@ -16,11 +16,6 @@
+ #include "bootparam_prot.h"
+
+
+-#ifdef __GLIBC__
+- /* quick fix */
+- void get_myaddress(struct sockaddr_in *);
+-#endif
+-
+ int debug = 0;
+ int dolog = 0;
+ struct in_addr route_addr;
--- netkit-bootparamd-0.17/debian/patches/use-cmake-as-buildsystem-tirpc.patch
+++ netkit-bootparamd-0.17/debian/patches/use-cmake-as-buildsystem-tirpc.patch
@@ -0,0 +1,35 @@
+Description: Use TI RPC instead of GNU libc RPC
+Author: Aurelien Jarno
+Forwarded: no
+Last-Update: 2021-08-25
+
+--- netkit-bootparamd-0.17.orig/CMakeLists.txt
netkit-bootparamd-0.17/CMakeLists.txt
+@@ -5,4 +5,7 @@ set(BIN_DIR "${CMAKE_INSTALL_PREFIX}/bin
+ set(SBIN_DIR "${CMAKE_INSTALL_PREFIX}/sbin")
+ set(MAN_DIR "${CMAKE_INSTALL_PREFIX}/share/man")
+
++find_package(PkgConfig REQUIRED)
++pkg_check_modules(TIRPC REQUIRED libtirpc)
++
+ add_subdirectory(rpc.bootparamd)
+--- netkit-bootparamd-0.17.orig/rpc.b
Bug#992960: nfstrace: FTBFS due to RPC removal from glibc
Source: nfstrace
Version: 0.4.3.2+git20200805+b220d04-1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)
Dear maintainer,
The glibc SunRPC implementation has been marked obsolete for some time.
It has been removed upstream from glibc 2.32, and it got disabled in the
recent glibc uploads. The TI RPC implementation should be used instead.
For this reason nfstrace now fails to build from source. You will find
attached a patch to switch to the TI RPC implementation, fixing the
FTBFS.
Regards,
Aurelien
--- nfstrace-0.4.3.2+git20200805+b220d04/debian/control
+++ nfstrace-0.4.3.2+git20200805+b220d04/debian/control
@@ -10,7 +10,9 @@
libgtest-dev,
google-mock,
libncurses5-dev,
-libjson-c-dev
+libjson-c-dev,
+libtirpc-dev,
+pkg-config
Build-Depends-Indep:
doxygen,
graphviz,
--- nfstrace-0.4.3.2+git20200805+b220d04/debian/patches/series
+++ nfstrace-0.4.3.2+git20200805+b220d04/debian/patches/series
@@ -0,0 +1 @@
+tirpc.patch
--- nfstrace-0.4.3.2+git20200805+b220d04/debian/patches/tirpc.patch
+++ nfstrace-0.4.3.2+git20200805+b220d04/debian/patches/tirpc.patch
@@ -0,0 +1,30 @@
+Build with TI RPC instead of GNU libc RPC
+
+--- nfstrace-0.4.3.2+git20200805+b220d04.orig/CMakeLists.txt
nfstrace-0.4.3.2+git20200805+b220d04/CMakeLists.txt
+@@ -29,6 +29,9 @@ if ("${PCAP_LIBRARY}" STREQUAL "PCAP_LIB
+ message (FATAL_ERROR "Could NOT find PCAP")
+ endif ()
+
++find_package(PkgConfig REQUIRED)
++pkg_check_modules(TIRPC REQUIRED libtirpc)
++
+ # build application
+ set (CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++14 -pedantic -Wall -Werror
-Wextra -Wno-invalid-offsetof -Wno-error=address-of-packed-member -fPIC
-fvisibility=hidden")
+ set (CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} -Wl,--export-dynamic")
+@@ -56,13 +59,14 @@ else ()
+ string (TIMESTAMP COMPILATION_DATE "%Y-%m-%d")
+ endif ()
+
+-include_directories (src)
++include_directories (src ${TIRPC_INCLUDE_DIRS})
+
+ # nfstrace executable
==
+ file (GLOB_RECURSE SRCS "src/*.cpp")
+ set (LIBS ${CMAKE_DL_LIBS} # libdl with dlopen()
+ ${CMAKE_THREAD_LIBS_INIT} # libpthread
+ ${PCAP_LIBRARY} # libpcap
++ ${TIRPC_LIBRARIES}# libtirpc
+ )
+
+ configure_file (docs/nfstrace.8.in
${PROJECT_SOURCE_DIR}/docs/nfstrace.8)
Bug#992959: nx-libs: FTBFS due to RPC removal from glibc
Source: nx-libs Version: 2:3.5.99.26-2 Severity: serious Tags: patch ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, The glibc SunRPC implementation has been marked obsolete for some time. It has been removed upstream from glibc 2.32, and it got disabled in the recent glibc uploads. The TI RPC implementation should be used instead. Fortunately nx-libs already supports building libtirpc using the -DUseTIRPC=1 option, so the fix is really simple. Please find attached a patch fixing the FTBFS. Regards, Aurelien --- nx-libs-3.5.99.26/debian/control +++ nx-libs-3.5.99.26/debian/control @@ -15,6 +15,7 @@ libjpeg-dev, libpixman-1-dev (>= 0.13.2), libpng-dev, + libtirpc-dev, libtool, libxcomposite-dev, libxdamage-dev, --- nx-libs-3.5.99.26/debian/rules +++ nx-libs-3.5.99.26/debian/rules @@ -58,7 +58,7 @@ override_dh_auto_build: - PREFIX='/usr' dh_auto_build --no-parallel -- CDEBUGFLAGS="$(CPPFLAGS) $(CFLAGS)" LOCAL_LDFLAGS="$(LDFLAGS)" SHLIBGLOBALSFLAGS='$(filter-out -pie,$(LDFLAGS))' + PREFIX='/usr' dh_auto_build --no-parallel -- CDEBUGFLAGS="$(CPPFLAGS) $(CFLAGS)" LOCAL_LDFLAGS="$(LDFLAGS)" SHLIBGLOBALSFLAGS='$(filter-out -pie,$(LDFLAGS))' IMAKE_DEFINES="-DUseTIRPC=1" override_dh_makeshlibs: dh_makeshlibs -n
Bug#992928: marked as done (libtasn1-6 arch-only FTBFS: Can't exec "gtkdocize": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 293.)
Your message dated Wed, 25 Aug 2021 16:18:44 + with message-id and subject line Bug#992928: fixed in libtasn1-6 4.17.0-2 has caused the Debian Bug report #992928, regarding libtasn1-6 arch-only FTBFS: Can't exec "gtkdocize": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 293. 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.) -- 992928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992928 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libtasn1-6 Version: 4.16.0-2 Severity: serious Tags: ftbfs libtasn1-6 fails to perform an arch-only build (but succeeds a full build). A build ends with: | dh binary-arch |dh_update_autotools_config -a |dh_autoreconf -a | libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'. | libtoolize: copying file 'build-aux/ltmain.sh' | libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. | libtoolize: copying file 'm4/libtool.m4' | libtoolize: copying file 'm4/ltoptions.m4' | libtoolize: copying file 'm4/ltsugar.m4' | libtoolize: copying file 'm4/ltversion.m4' | libtoolize: copying file 'm4/lt~obsolete.m4' | Can't exec "gtkdocize": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 293. | autoreconf: error: gtkdocize failed with exit status: 2 | dh_autoreconf: error: autoreconf -f -i returned exit code 2 | make: *** [debian/rules:48: binary-arch] Error 25 | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 Likely, moving gtk-doc-tools to Build-Depends would fix the issue, but Andreas Metzler found a way to avoid this for gnutls28. Helmut --- End Message --- --- Begin Message --- Source: libtasn1-6 Source-Version: 4.17.0-2 Done: Andreas Metzler We believe that the bug you reported is fixed in the latest version of libtasn1-6, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Metzler (supplier of updated libtasn1-6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 25 Aug 2021 18:02:27 +0200 Source: libtasn1-6 Architecture: source Version: 4.17.0-2 Distribution: unstable Urgency: low Maintainer: Debian GnuTLS Maintainers Changed-By: Andreas Metzler Closes: 992928 Changes: libtasn1-6 (4.17.0-2) unstable; urgency=low . * Invoke dh_autoreconf with GTKDOCIZE=echo for arch-only builds, fixing FTBFS. Closes: #992928 * Upload to unstable. Checksums-Sha1: 525ec7a530ee96fc9e800386772bbb07b8ad7914 2586 libtasn1-6_4.17.0-2.dsc 8428b00841140bda5fcd1f4e597a33b6a37990e3 20168 libtasn1-6_4.17.0-2.debian.tar.xz Checksums-Sha256: 3094abb781ad3146d60c068fc5181d317001a0ab47dd4ff7edb0bf7f531c8f14 2586 libtasn1-6_4.17.0-2.dsc 29419f61d6f15bdea299e6ad12f9d408337e865828d362ca475f52e2fc5651df 20168 libtasn1-6_4.17.0-2.debian.tar.xz Files: 6c25a407ecc926b5f156707e981a100e 2586 libs optional libtasn1-6_4.17.0-2.dsc 3ce8d4edb9784148549c099bc7ba0857 20168 libs optional libtasn1-6_4.17.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmEmaugACgkQpU8BhUOC FIR4pQ/+KgicwKSfCGE6/bhcDZSCEiWQg3gJ6mgYZ7eARgEGIAHggjyUZgsi/phk x537nkyY0QsNDGnPtCV2oIIjp1yM6rTZrPDZJbAFslhGwxUPnHhPF+dH+uu6hLrl BOP67rOTWd+Aj5J23Ci9lKuUHyhSHzsdq5UZPqmWuki1w3ylHgK/bPfc3udsqT8t UU4ASTd3OmpgSgUKlx42smhj3xOgPHnkLQ3u6zJSpemoO9GiaDbflgKHpQ9+IwhY qU8ynCcmu8aSIR1kA6aqay0qTnOlo5gS7Gj4qSGyS6J/TVmKuwprBPxyNbz1YsTS RquA7HfT/WUROQBypuNjMBkYBxl45ncJjNT7AwZYEjwV033yao+l+CdEs8qpYph0 y5G0o2leZM5whqBb4MyOjUSUsXa6ZU/8db8Tacz0Fkw9ujsO/rCR2zdamqxhZy3X J+4Sm3/TEm3nspdU7NjgZHCTcee6UhvqBgGlkzj54RkK5dAHG1oh1+l6cpVhNIVa 8OOAtEiXD/UDwRG7JgeSXXWHC8T64mwpEzqI2Sai+37hzfeom5Or8kT4YsSuv1WM J4NeUcX+AXveudWivkPUMwBTD0TvfuUwrZPkIe+yzccWonp1OE2eGNy6qedx8Nwy 3jYBe1eBpLtHtt8b/5v4uQ/Va2LvC4/lCvmbVnjXw+UlhWkCQUc= =HUj/ -END PGP SIGNATURE End Message ---
Processed: owner 992902
Processing commands for cont...@bugs.debian.org: > owner 992902 tmanc...@debian.org Bug #992902 [lizzie] lizzie build-depends on removed package Owner recorded as tmanc...@debian.org. > thanks Stopping processing here. Please contact me if you need assistance. -- 992902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992902: lizzie build-depends on removed package
On Tue, Aug 24, 2021 at 08:25:29PM +0100, peter green wrote: > package: lizzie > version: 0.7.4+dfsg1-2 > severity: serious > > lizzie build-depends on libjuniversalchardet-java-doc which is no longer > built by the > libjuniversalchardet-java source package. It is still present in unstable as > a cruft > package but is completely gone from testing. Thank you for the bug report. Dropping this build-dep has no impact on the resulting binary packages, so I am preparing an upload now. Cheers, tony
Bug#992844: marked as done (mercurial: FTBFS on s390x (ERROR: test-upgrade-repo.t output changed))
Your message dated Wed, 25 Aug 2021 15:49:02 + with message-id and subject line Bug#992844: fixed in mercurial 5.9-2 has caused the Debian Bug report #992844, regarding mercurial: FTBFS on s390x (ERROR: test-upgrade-repo.t output changed) 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.) -- 992844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992844 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mercurial Version: 5.9-1 Severity: serious Tags: ftbfs >From the log https://buildd.debian.org/status/fetch.php?pkg=mercurial&arch=s390x&ver=5.9-1&stamp=1629766216&raw=0 > --- /<>/tests/test-upgrade-repo.t > +++ /<>/tests/test-upgrade-repo.t.err > @@ -1531,9 +1531,8 @@ >sparserevlog >store >$ hg debugsidedata -c 0 > - 2 sidedata entries > - entry-0001 size 4 > - entry-0002 size 32 > + abort: cannot read from revlog 00changelog-5e69c5d1.sda; expected > 1942585158 bytes from offset 0, data size is 90 > + [50] > > downgrade > > @@ -1552,6 +1551,8 @@ > - changelog > - manifest > > + abort: cannot read from revlog data/foo-1335303a.sda; expected 1942585158 > bytes from offset 0, data size is 0 > + [50] >$ hg debugformat -v >format-variant repo config default >fncache:yesyes yes > @@ -1563,7 +1564,7 @@ >persistent-nodemap: no no no (no-rust !) >persistent-nodemap: yesyes no (rust !) >copies-sdc: no no no > - revlog-v2: no no no > + revlog-v2: yes no no >changelog-v2:no no no >plain-cl-delta: yesyes yes >compression:zlib zlibzlib (no-zstd !) > @@ -1571,14 +1572,16 @@ >compression-level: default default default >$ cat .hg/requires >dotencode > - fncache > + exp-revlogv2.2 > + fncache > + persistent-nodemap (rust !) >generaldelta > - persistent-nodemap (rust !) > - revlog-compression-zstd (zstd !) > - revlogv1 > + revlog-compression-zstd >sparserevlog >store >$ hg debugsidedata -c 0 > + abort: cannot read from revlog 00changelog-5e69c5d1.sda; expected > 1942585158 bytes from offset 0, data size is 90 > + [50] > > upgrade from hgrc > > @@ -1587,20 +1590,8 @@ >> revlogv2=enable-unstable-format-and-corrupt-my-data >> EOF >$ hg debugupgraderepo --run --no-backup --quiet > - upgrade will perform the following actions: > - > - requirements > preserved: dotencode, fncache, generaldelta, sparserevlog, store > (no-zstd !) > - preserved: dotencode, fncache, generaldelta, revlog-compression-zstd, > sparserevlog, store (zstd no-rust !) > preserved: dotencode, fncache, generaldelta, persistent-nodemap, > revlog-compression-zstd, sparserevlog, store (rust !) > - removed: revlogv1 > - added: exp-revlogv2.2 > - > - processed revlogs: > -- all-filelogs > -- changelog > -- manifest > - >$ hg debugformat -v >format-variant repo config default >fncache:yesyes yes > @@ -1628,6 +1619,8 @@ >sparserevlog >store >$ hg debugsidedata -c 0 > + abort: cannot read from revlog 00changelog-5e69c5d1.sda; expected > 1942585158 bytes from offset 0, data size is 90 > + [50] > > Demonstrate that nothing to perform upgrade will still run all the way > through > > > ERROR: test-upgrade-repo.t output changed > !# Ret was: 0 (test-upgrade-repo.t) --- End Message --- --- Begin Message --- Source: mercurial Source-Version: 5.9-2 Done: Julien Cristau We believe that the bug you reported is fixed in the latest version of mercurial, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Cristau (supplier of updated mercurial package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 25 Aug 2021 17:22:58 +0200 Source: mercurial Architecture: source Version: 5.9-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Julien Cristau Closes: 992844 Changes: mercurial (5.9-2) unsta
Bug#978883: pnscan: ftbfs with autoconf 2.70
Control: tags 978883 unreproducible moreinfo Control: severity 978883 important Hi Matthias, I can't reproduce it in a fresh jail with autoconf 2.70/2.71 and GCC-10/11. I tested this package and 32 other packages with the same bug. I wasn't able to reproduce this issue in 18 packages. Maybe it is a failure in a robot. This issue is causing AUTORM in forensics-all and forensics-extra. Can you recheck? As an additional information, the package builds twice. Regards, Eriberto
Processed: Re: pnscan: ftbfs with autoconf 2.70
Processing control commands: > tags 978883 unreproducible moreinfo Bug #978883 [src:pnscan] pnscan: ftbfs with autoconf 2.70 Added tag(s) unreproducible and moreinfo. > severity 978883 important Bug #978883 [src:pnscan] pnscan: ftbfs with autoconf 2.70 Severity set to 'important' from 'serious' -- 978883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: tcpxtract: ftbfs with autoconf 2.70
Processing control commands: > tags 978906 unreproducible moreinfo Bug #978906 [src:tcpxtract] tcpxtract: ftbfs with autoconf 2.70 Added tag(s) unreproducible and moreinfo. > severity 978906 important Bug #978906 [src:tcpxtract] tcpxtract: ftbfs with autoconf 2.70 Severity set to 'important' from 'serious' -- 978906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978906 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978906: tcpxtract: ftbfs with autoconf 2.70
Control: tags 978906 unreproducible moreinfo Control: severity 978906 important Hi Matthias, I can't reproduce it in a fresh jail with autoconf 2.70/2.71 and GCC-10/11. I tested this package and 32 other packages with the same bug. I wasn't able to reproduce this issue in 18 packages. Maybe it is a failure in a robot. This issue is causing AUTORM in forensics-all and forensics-extra. Can you recheck? Regards, Eriberto
Bug#978905: tcpreplay: ftbfs with autoconf 2.70
Em qua., 25 de ago. de 2021 às 06:30, Christoph Biedl escreveu: > > Control: tags 978905 unreproducible moreinfo > > Matthias Klose wrote... > > > The package fails to build in a test rebuild on at least amd64 with > > autoconf 2.70, but succeeds to build with autoconf 2.69. The > > severity of this report will be raised before the bookworm release, > > so nothing has to be done for the bullseye release. > > Now looking into this, I cannot reproduce the issue in a pure Debian > build chroot, both usrmerged and non-usrmerged (in case that ever > matters). Indeed. The same case for pnscan and tcpxtract, both causing AUTORM for forensics-all and forensics-extra. Yesterday I tested 33 packages. I wasn't able to reproduce the issue in 18 packages. Regards, Eriberto
Bug#978793: dnssec-trigger: ftbfs with autoconf 2.70
Hey Matthias, > checking for library containing inet_pton... none required > checking for library containing socket... none required > checking for GNU libc compatible malloc... yes > configure: error: cannot run /bin/sh ./config.sub Can you double-check this/run a rebuild and see if it was a spurious issue? I'm not the maintainer, just a wandering passerby, but it seems dnssec-trigger's configure script builds and works just fine with Autoconf 2.71. I can't explain the error from your log with being unable to run config.sub, but it doesn't occur on my system and dnssec-trigger builds successfully. signature.asc Description: This is a digitally signed message part
Bug#991448: ui-utilcpp: diff for NMU version 1.10.0-1.1
Control: tags 991448 + patch Control: tags 991448 + pending I've prepared an NMU for ui-utilcpp (versioned as 1.10.0-1.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should delay it longer. MR at https://salsa.debian.org/debian/ui-utilcpp/-/merge_requests/1 if you want to integrate this that way. /Simon diff --git a/debian/changelog b/debian/changelog index e38ae11..4996f08 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,10 @@ +ui-utilcpp (1.10.0-1.1) unstable; urgency=medium + + * Non-maintainer upload + * Add FTBFS patch from Steve Langasek. Closes: #991448. + + -- Simon Josefsson Wed, 25 Aug 2021 10:23:30 +0200 + ui-utilcpp (1.10.0-1) unstable; urgency=medium [ Ondřej Nový ] diff --git a/debian/control b/debian/control index 48b4461..3964b68 100644 --- a/debian/control +++ b/debian/control @@ -12,6 +12,7 @@ Build-Depends: debhelper-compat (= 12), libidn11-dev, libcap-dev, libboost-all-dev (>= 1.35), + libtirpc-dev, xfslibs-dev, doxygen (>= 1.5.6), graphviz (>= 2.20.2) diff --git a/debian/patches/series b/debian/patches/series new file mode 100644 index 000..6a0390d --- /dev/null +++ b/debian/patches/series @@ -0,0 +1 @@ +tirpc.patch diff --git a/debian/patches/tirpc.patch b/debian/patches/tirpc.patch new file mode 100644 index 000..9c8a1d6 --- /dev/null +++ b/debian/patches/tirpc.patch @@ -0,0 +1,35 @@ +Description: Port from deprecated glibc rpcsvc to libtirpc-dev +Author: Steve Langasek +Forwarded: no +Last-Update: 2021-07-23 + +Index: ui-utilcpp-1.10.0/configure.ac +=== +--- ui-utilcpp-1.10.0.orig/configure.ac ui-utilcpp-1.10.0/configure.ac +@@ -83,8 +83,8 @@ + AC_CHECK_FUNCS(cap_clear_flag) + + # Push generic flags +-AC_SUBST(AM_CPPFLAGS, ["-I\$(top_srcdir)/src"]) +-AC_SUBST(AM_CXXFLAGS, ["-pthread -lrpcsvc $(ucommon-config --cflags)"]) ++AC_SUBST(AM_CPPFLAGS, ["-I\$(top_srcdir)/src -I/usr/include/tirpc"]) ++AC_SUBST(AM_CXXFLAGS, ["-pthread -ltirpc $(ucommon-config --cflags)"]) + AC_SUBST(AM_LDFLAGS, ["-pthread"]) + AC_SUBST(AM_LIBADD, $(ucommon-config --libs)) + AC_SUBST(AM_LDADD, $(ucommon-config --libs)) +Index: ui-utilcpp-1.10.0/src/ui-utilcpp/Makefile.am +=== +--- ui-utilcpp-1.10.0.orig/src/ui-utilcpp/Makefile.am ui-utilcpp-1.10.0/src/ui-utilcpp/Makefile.am +@@ -45,3 +45,10 @@ + libui_utilcpp_la_CXXFLAGS = @AM_CXXFLAGS@ -fvisibility=default + libui_utilcpp_la_LDFLAGS = @AM_LDFLAGS@ -version-info @SO_VERSION@ + libui_utilcpp_la_LIBADD = http/libui-utilcpp-http.la ++ ++nodist_libui_utilcpp_la_SOURCES = xdr_rquota.c ++CLEANFILES = xdr_rquota.c ++ ++xdr_rquota.c: ++ rpcgen -c /usr/include/rpcsvc/rquota.x > $@ ++ signature.asc Description: PGP signature
Bug#978786: marked as done (coinor-cbc: ftbfs with autoconf 2.70)
Your message dated Wed, 25 Aug 2021 14:28:32 +0200
with message-id
and subject line FTBFS failure with ac270 but not with ac271
has caused the Debian Bug report #978786,
regarding coinor-cbc: ftbfs with autoconf 2.70
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.)
--
978786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978786
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:coinor-cbc
Version: 2.10.5+ds1-2
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270
[This bug report is not targeted to the upcoming bullseye release]
The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.
The full build log can be found at:
http://qa-logs.debian.net/2020/09/26.ac270/coinor-cbc_2.10.5+ds1-2_unstable_ac270.log
The last lines of the build log are at the end of this report.
To build with autoconf 2.70, please install the autoconf package from
experimental: apt-get -t=experimental install autoconf
[...]
am__tar=''
am__untar=''
bindir='${exec_prefix}/bin'
build='x86_64-pc-linux-gnu'
build_alias='x86_64-linux-gnu'
build_cpu='x86_64'
build_os='linux-gnu'
build_vendor='pc'
coin_doxy_excludes=''
coin_doxy_logname=''
coin_doxy_tagfiles=''
coin_doxy_tagname=''
coin_doxy_usedot=''
coin_have_doxygen=''
coin_have_latex=''
datadir='${datarootdir}'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dos2unix=''
dvidir='${docdir}'
exec_prefix='NONE'
have_autoconf=''
have_automake=''
have_svn=''
host=''
host_alias=''
host_cpu=''
host_os=''
host_vendor=''
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${prefix}/share/info'
install_sh=''
libdir='${prefix}/lib/x86_64-linux-gnu'
libexecdir='${exec_prefix}/libexec'
localedir='${datarootdir}/locale'
localstatedir='/var'
mandir='${prefix}/share/man'
mkdir_p=''
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
runstatedir='/run'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sol_cc_compiler=''
subdirs=''
sysconfdir='/etc'
target_alias=''
## --- ##
## confdefs.h. ##
## --- ##
/* confdefs.h */
#define PACKAGE_NAME "Cbc"
#define PACKAGE_TARNAME "cbc"
#define PACKAGE_VERSION "2.10.5"
#define PACKAGE_STRING "Cbc 2.10.5"
#define PACKAGE_BUGREPORT "c...@lists.coin-or.org"
#define PACKAGE_URL ""
configure: exit 1
dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --enable-static
--enable-cbc-parallel --enable-dot --enable-dependency-linking returned exit
code 1
make[1]: *** [debian/rules:20: override_dh_auto_configure] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Hi,
we have autoconf 2.69 in stable and testing, which gave no failure.
Now autoconf 2.71 is in unstable and I checked: no failure.
So I guess there was a problem specific to autoconf 2.70 and I can
close that bug already.
Cheers,
J.Puydt--- End Message ---
Bug#979458: Reassigning, merging and rising severity level of Bugs #979458 and #979459
* Wookey [2021-08-25 12:30]: On 24/08/2021 07:45, Rafael Laboissière wrote: I am hereby reassigning the Bugs #979458 and #979459, which were assigned to the binary jed and jed-common packages, to the jed source package. I am also merging this two bug reports and rising their severity level to serious. The trivial patch that fixes the problem is attached to this message. Thanks Rafael. I'm away on expedition with negligible internet until 12th Sept, so if anyone wishes to NMU this, that's fine by me. Otherwise it'll get done sometime after I get back. Ok, I will NMU the new version. Would you mind if I add my changes to the Git repository at salsa.d.o? I will also add the changes for version 1:0.99.19-8, which are absent from the repository, if you agree. Best, Rafael Laboissière
Bug#982791: marked as done (mit-scheme FTBFS on i386: out of memory)
Your message dated Wed, 25 Aug 2021 11:33:32 + with message-id and subject line Bug#982791: fixed in mit-scheme 11.2-2 has caused the Debian Bug report #982791, regarding mit-scheme FTBFS on i386: out of memory 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.) -- 982791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mit-scheme Version: 11.1-1 Severity: serious https://buildd.debian.org/status/fetch.php?pkg=mit-scheme&arch=i386&ver=11.1-4&stamp=1612971495&raw=0 ... echo '(compile-directory "compiler/machine")' | 'mit-scheme-i386' --batch-mode --band tools/compiler.com --no-init-file --eval '(begin (set! sf/cross-compiling? true) (set! package/cross-compiling? true) (set! target-bytes-per-object (lambda () 4)) (set! compiler:cross-compiling? true) )' ;Compiling file: "compiler/machine/assmd.nib" => "compiler/machine/assmd.moc"... done ;Compiling file: "compiler/machine/coerce.nib" => "compiler/machine/coerce.moc"... done ;Compiling file: "compiler/machine/dassm1.nib" => "compiler/machine/dassm1.moc"... done ;Compiling file: "compiler/machine/dassm2.nib" => "compiler/machine/dassm2.moc"... done ;Compiling file: "compiler/machine/dassm3.nib" => "compiler/machine/dassm3.moc"... done ;Compiling file: "compiler/machine/decls.nib" => "compiler/machine/decls.moc"... done ;Compiling file: "compiler/machine/insmac.nib" => "compiler/machine/insmac.moc"... done ;Compiling file: "compiler/machine/instr1.nib" => "compiler/machine/instr1.moc"... aborted ;Aborting!: out of memory make[2]: *** [Makefile:322: compile-compiler-machine] Error 20 This means 4 GB address space were not enough. Starting with 11.1 upstream no longer seems to provide i386 binaries, which feels related. Perhaps it's time to drop i386 from Architecture? OTOH upstream does support arm64 now, so that could be added to Architecture. --- End Message --- --- Begin Message --- Source: mit-scheme Source-Version: 11.2-2 Done: Barak A. Pearlmutter We believe that the bug you reported is fixed in the latest version of mit-scheme, 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 982...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barak A. Pearlmutter (supplier of updated mit-scheme package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 25 Aug 2021 11:40:16 +0100 Source: mit-scheme Architecture: source Version: 11.2-2 Distribution: unstable Urgency: medium Maintainer: Barak A. Pearlmutter Changed-By: Barak A. Pearlmutter Closes: 982791 987373 Changes: mit-scheme (11.2-2) unstable; urgency=medium . * remove i386 from architecture list (closes: #982791) * add postrm script (closes: #987373) Checksums-Sha1: 8c2906d18260861a1affe390ecbb3e80b179c26f 2204 mit-scheme_11.2-2.dsc 12bf3c3840bc84402323339c695376014e38d8f0 38056 mit-scheme_11.2-2.debian.tar.xz 8a9a6fdfba6ed18e27be2afdf024b7389698b737 9864 mit-scheme_11.2-2_source.buildinfo Checksums-Sha256: 534dc1559fb4a7a16ed888e0bf4da7a2c6bf9c93216f76390e2077e3fc5f45c6 2204 mit-scheme_11.2-2.dsc 2908dfaf382a1d51453be8aed66bdcd232a626f3fa4678b84799c7e2b226abf4 38056 mit-scheme_11.2-2.debian.tar.xz 60ffb97cd6f6eadcf254ddd648f5349a9b0360facf662f8bfdbd0d39f4a6f3c7 9864 mit-scheme_11.2-2_source.buildinfo Files: 451f255a2f343b7968af9acd51038ac0 2204 lisp optional mit-scheme_11.2-2.dsc 3d37f5a0aaa51d4b7d46fe9962ea67fd 38056 lisp optional mit-scheme_11.2-2.debian.tar.xz 6944b5a6cdaeab229961cd81529bdda0 9864 lisp optional mit-scheme_11.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJDBAEBCgAtFiEE+nZaz+JE7Dn2AefCmesepNIze4gFAmEmJlIPHGJhcEBkZWJp YW4ub3JnAAoJEJnrHqTSM3uIncYP/05DjjpYo63ThfKl8L4HfSuC8/iz7QSpbIVX 8O9tDdp1iCRzi/MaHgoqG+Q6xySNds3yNNA8fULjEyLlzFrlHh7kNd6tZdcTaYgI f2peNmlIfwr1RYrmLZ2yJlcqTbAZ0+7flhFyRqMsyfiXFTKH7y1ksYXto4wuBVNa wTjsyCfwrBayy2zm+V8k3NY59ymWbrudnf1mtMeXphyjTLmwUGnSHcXSDqX7XF+e Lj3PP0d5Q3HOGA7SG6bGe9bx+vnuDhxPGLlRwsb29l7lEWs0Wqq7zkvdk+QPNjqb BZ/ncsyoa/nOf1j99szbkvVc0ox75aznmIB9RtErCMJPTVH5LrmaS3MaAilAevza FsKeb19LVhS7MsU1M+sgcI6mkmqFhhm+6SjgWaV07KLfZYMFLo6TVbr0LkXPyczp DOiyc
Bug#979458: Reassigning, merging and rising severity level of Bugs #979458 and #979459
On 24/08/2021 07:45, Rafael Laboissière wrote: I am hereby reassigning the Bugs #979458 and #979459, which were assigned to the binary jed and jed-common packages, to the jed source package. I am also merging this two bug reports and rising their severity level to serious. The trivial patch that fixes the problem is attached to this message. Thanks Rafael. I'm away on expedition with negligible internet until 12th Sept, so if anyone wishes to NMU this, that's fine by me. Otherwise it'll get done sometime after I get back. -- Wookey
Bug#992158: marked as done (Race in ifup maybe related to brctl failure in pre-up of network interface)
Your message dated Wed, 25 Aug 2021 12:24:07 +0200 with message-id and subject line Re: Bug#992158: Race in ifup maybe related to brctl failure in pre-up of network interface has caused the Debian Bug report #992158, regarding Race in ifup maybe related to brctl failure in pre-up of network interface 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.) -- 992158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: bridge-utils Version: 1.7-1 Severity: serious When running "brctl addbr" and "ip link set [if] address" immediately afterwards, the second command will fail to apply the address change. This is somehow annoying as the MAC would be used in security related filtering and monitoring of the network traffic, which then fails. The configuration from "/etc/network/interfaces" reliably triggering the bug is: auto virtbr0 iface virtbr0 inet static address 192.168.1.1 netmask 255.255.255.0 pre-up brctl addbr virtbr0 pre-up ip link set virtbr0 address 86:aa:aa:aa:aa:aa pre-up ip link set virtbr0 up post-down ip link set virtbr0 down post-down brctl delbr virtbr0 Running "ifdown virtbr0; ifup virtbr0; ip link show" will report link/ether 86:8a:6a:ee:5e:a2 brd ff:ff:ff:ff:ff:ff so the setting to "86:aa:aa:aa:aa:aa" does not take effect. The reason I expect the race to be in brctl itself or related a race in the kernel just exposed by brctl is, that following changes will produce correct results: * "strace -o dump ifup virtbr0" eliminates the behavior. * Using " pre-up brctl addbr virtbr0 && sleep 1" will make "ifup" wait for one second, correct MAC is set. Instead when changing the initial interfaces configuration to include pre-up ip link set virtbr0 address 86:aa:aa:aa:aa:aa || touch /root/fail "ifup" will still expose the bug but /root/fail is not created. So if "ip link" fails to react correctly on any intermediate state when the bridge is coming up, then at least it does not detect it correctly and report it via an error code. As attaching a debugger eliminates the bug I have no idea how to quickly rule out such an effect. Weirdly this bug does not occur on a multicore real-hardware machine (I have no single core hardware or tried to run Linux single core via boot options) but till now only in single core qemu machines (I did not test multi-core qemu yet). But the core count, kernel behaviour might be just a red herring. Any ideas how that could happen? Maybe would "brctl add" need to wait for a confirmation from kernel, that the bridge setup is completed before exiting? --- End Message --- --- Begin Message --- > Thank you for your assistance. With hint for the relevant man > page "bridge-utils-interfaces" I found the bridge setup working > using the configuration > > auto br0 > iface br0 inet static > address 192.168.1.1 > network 192.168.1.0 > netmask 255.255.255.0 > bridge_ports none > bridge_hw 86:aa:aa:aa:aa:aa > > With that there is no race observed, I deem this bug report as > invalid. Yes, that looks ok for a setup where you don't want to add any ports to a bridge. > I tested without the legacy stuff, worked, making this bug report > irrelevant. Testing how far the change can be backported is > done on demand later, not relevant here (Bullseye). I don't remember any reason why current bullseye package can't be used at buster or prior versions. Regards. -- Manty/BestiaTester -> http://manty.net--- End Message ---
Bug#992158: Race in ifup maybe related to brctl failure in pre-up of network interface
> Thank you for your assistance. With hint for the relevant man > page "bridge-utils-interfaces" I found the bridge setup working > using the configuration > > auto br0 > iface br0 inet static > address 192.168.1.1 > network 192.168.1.0 > netmask 255.255.255.0 > bridge_ports none > bridge_hw 86:aa:aa:aa:aa:aa > > With that there is no race observed, I deem this bug report as > invalid. Yes, that looks ok for a setup where you don't want to add any ports to a bridge. > I tested without the legacy stuff, worked, making this bug report > irrelevant. Testing how far the change can be backported is > done on demand later, not relevant here (Bullseye). I don't remember any reason why current bullseye package can't be used at buster or prior versions. Regards. -- Manty/BestiaTester -> http://manty.net
Bug#978905: marked as done (tcpreplay: ftbfs with autoconf 2.70)
Your message dated Wed, 25 Aug 2021 11:49:52 +0200
with message-id
and subject line Re: Bug#978905: tcpreplay: ftbfs with autoconf 2.70
has caused the Debian Bug report #978905,
regarding tcpreplay: ftbfs with autoconf 2.70
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.)
--
978905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978905
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:tcpreplay
Version: 4.3.3-2
Severity: normal
Tags: sid bookworm
User: d...@debian.org
Usertags: ftbfs-ac270
[This bug report is not targeted to the upcoming bullseye release]
The package fails to build in a test rebuild on at least amd64 with
autoconf 2.70, but succeeds to build with autoconf 2.69. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.
The full build log can be found at:
http://qa-logs.debian.net/2020/09/26.ac270/tcpreplay_4.3.3-2_unstable_ac270.log
The last lines of the build log are at the end of this report.
To build with autoconf 2.70, please install the autoconf package from
experimental: apt-get -t=experimental install autoconf
[...]
#define HAVE_SNPRINTF 1
#define HAVE_VSNPRINTF 1
#define HAVE_STRSIGNAL 1
#define HAVE_STRPBRK 1
#define HAVE_STRRCHR 1
#define HAVE_STRSPN 1
#define HAVE_STRSTR 1
#define HAVE_STRTOUL 1
#define HAVE_IOPERM 1
#define DEBUG 1
#define ENABLE_64BITS 1
#define ENABLE_DYNAMIC_LINK 1
#define HAVE_INET_ATON 1
#define HAVE_INET_PTON 1
#define HAVE_INET_NTOP 1
#define HAVE_INET_ADDR 1
#define HAVE_TUNTAP 1
#define HAVE_PCAP_SETNONBLOCK 1
#define HAVE_DLT_VAL_TO_DESC 1
#define HAVE_PCAP_GET_SELECTABLE_FD 1
#define HAVE_PCAP_DUMP_FOPEN 1
#define HAVE_PCAP_INJECT 1
#define HAVE_PCAP_SENDPACKET 1
#define HAVE_PCAP_VERSION 1
#define HAVE_PCAP_SNAPSHOT 1
#define ENABLE_TCPBRIDGE 1
#define ENABLE_TCPLIVEPLAY 1
#define HAVE_PF_PACKET 1
#define LIBDNET_VERSION ""
#define HAVE_DLT_LINUX_SLL 1
#define HAVE_DLT_C_HDLC 1
#define HAVE_TCPDUMP 1
#define TCPDUMP_BINARY "/usr/sbin/tcpdump"
#define ENABLE_VERBOSE 1
#define HAVE_LINUX 1
#define ENABLE_PCAP_FINDALLDEVS 1
#define HAVE_DIRENT_H 1
#define HAVE_SYS_MMAN_H 1
#define HAVE_SYS_PARAM_H 1
#define HAVE_SYS_POLL_H 1
#define HAVE_SYS_SELECT_H 1
#define HAVE_SYS_SOCKET_H 1
#define HAVE_SYS_TIME_H 1
#define HAVE_SYS_UN_H 1
#define HAVE_SYS_WAIT_H 1
#define HAVE_DLFCN_H 1
#define HAVE_ERRNO_H 1
#define HAVE_FCNTL_H 1
#define HAVE_LIBGEN_H 1
#define HAVE_LIBINTL_H 1
#define HAVE_MEMORY_H 1
#define HAVE_NETINET_IN_H 1
#define HAVE_SETJMP_H 1
#define HAVE_STDBOOL_H 1
#define HAVE_SYSEXITS_H 1
#define HAVE_UNISTD_H 1
#define HAVE_UTIME_H 1
#define HAVE_STDARG_H 1
#define HAVE_STRING_H 1
#define HAVE_LIMITS_H 1
#define HAVE_INTTYPES_H 1
#define HAVE_WCHAR_H 1
#define ENABLE_NLS 1
configure: exit 1
dh_auto_configure: error: ./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-option-checking --disable-silent-rules
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run
--disable-maintainer-mode --disable-dependency-tracking --host=x86_64-linux-gnu
--build=x86_64-linux-gnu --prefix=/usr --enable-debug --enable-dynamic-link
--mandir=\${prefix}/share/man --infodir=\${prefix}/share/info returned exit
code 1
make[1]: *** [debian/rules:9: override_dh_auto_configure] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
On 8/25/21 11:20 AM, Christoph Biedl wrote:
> Control: tags 978905 unreproducible moreinfo
>
> Matthias Klose wrote...
>
>> The package fails to build in a test rebuild on at least amd64 with
>> autoconf 2.70, but succeeds to build with autoconf 2.69. The
>> severity of this report will be raised before the bookworm release,
>> so nothing has to be done for the bullseye release.
>
> Now looking into this, I cannot reproduce the issue in a pure Debian
> build chroot, both usrmerged and non-usrmerged (in case that ever
> matters).
>
> Likewise, the just-uploaded 4.3.4-1 built on amd64 and many more
> architectures: https://buildd.debian.org/status/package.php?p=tcpreplay
>
> Also, the error message you'd encountered
>
> | configure: error: you must have stdlib.h on your system
>
> looks really strange to me and I doubt it's related to autoconf. Please
> re-check.
>
> Christoph
>
just closing.--- End Message ---
Processed: Re: Bug#978905: tcpreplay: ftbfs with autoconf 2.70
Processing control commands: > tags 978905 unreproducible moreinfo Bug #978905 [src:tcpreplay] tcpreplay: ftbfs with autoconf 2.70 Added tag(s) unreproducible and moreinfo. -- 978905: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978905 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#978905: tcpreplay: ftbfs with autoconf 2.70
Control: tags 978905 unreproducible moreinfo Matthias Klose wrote... > The package fails to build in a test rebuild on at least amd64 with > autoconf 2.70, but succeeds to build with autoconf 2.69. The > severity of this report will be raised before the bookworm release, > so nothing has to be done for the bullseye release. Now looking into this, I cannot reproduce the issue in a pure Debian build chroot, both usrmerged and non-usrmerged (in case that ever matters). Likewise, the just-uploaded 4.3.4-1 built on amd64 and many more architectures: https://buildd.debian.org/status/package.php?p=tcpreplay Also, the error message you'd encountered | configure: error: you must have stdlib.h on your system looks really strange to me and I doubt it's related to autoconf. Please re-check. Christoph signature.asc Description: PGP signature
Processed: ui-utilcpp: diff for NMU version 1.10.0-1.1
Processing control commands: > tags 991448 + patch Bug #991448 [ui-utilcpp] ui-utilcpp: migration to libtirpc-dev Ignoring request to alter tags of bug #991448 to the same tags previously set > tags 991448 + pending Bug #991448 [ui-utilcpp] ui-utilcpp: migration to libtirpc-dev Added tag(s) pending. -- 991448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991448 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 992912
Processing commands for cont...@bugs.debian.org: > tags 992912 + upstream fixed-upstream Bug #992912 [src:mat2] mat2: autopkgtests fail with ffmpeg 4.4 Added tag(s) upstream and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 992912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992912 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org:
> reassign 966899 src:xneur
Bug #966899 [src:gxneur] gxneur: FTBFS: ld:
gxneur-trayicon.o:/usr/include/xneur/xneur.h:35: multiple definition of
`main_window'; gxneur-misc.o:/usr/include/xneur/xneur.h:35: first defined here
Bug reassigned from package 'src:gxneur' to 'src:xneur'.
No longer marked as found in versions gxneur/0.20.0-2.1.
Ignoring request to alter fixed versions of bug #966899 to the same values
previously set
> unarchive 957991
Bug #957991 {Done: Alexander GQ Gerasiov } [src:xneur] xneur:
ftbfs with GCC-10
Unarchived Bug 957991
> forcemerge 957991 966899
Bug #957991 {Done: Alexander GQ Gerasiov } [src:xneur] xneur:
ftbfs with GCC-10
Bug #957991 {Done: Alexander GQ Gerasiov } [src:xneur] xneur:
ftbfs with GCC-10
Added tag(s) ftbfs and bookworm.
Bug #966899 [src:xneur] gxneur: FTBFS: ld:
gxneur-trayicon.o:/usr/include/xneur/xneur.h:35: multiple definition of
`main_window'; gxneur-misc.o:/usr/include/xneur/xneur.h:35: first defined here
Marked Bug as done
Marked as fixed in versions xneur/0.20.0-3.
Marked as found in versions xneur/0.20.0-2.
Added tag(s) patch.
Merged 957991 966899
> affects 957991 src:gxneur
Bug #957991 {Done: Alexander GQ Gerasiov } [src:xneur] xneur:
ftbfs with GCC-10
Bug #966899 {Done: Alexander GQ Gerasiov } [src:xneur] gxneur:
FTBFS: ld: gxneur-trayicon.o:/usr/include/xneur/xneur.h:35: multiple definition
of `main_window'; gxneur-misc.o:/usr/include/xneur/xneur.h:35: first defined
here
Added indication that 957991 affects src:gxneur
Added indication that 966899 affects src:gxneur
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
957991: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957991
966899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966899
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#992376: marked as done (systemd-standalone-{sysusers,tmpfiles}: missing Breaks+Replaces: systemd (<< 249.3-2))
Your message dated Wed, 25 Aug 2021 08:41:40 +
with message-id
and subject line Bug#992376: fixed in systemd 249.3-4
has caused the Debian Bug report #992376,
regarding systemd-standalone-{sysusers,tmpfiles}: missing Breaks+Replaces:
systemd (<< 249.3-2)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
992376: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992376
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd-standalone-sysusers,systemd-standalone-tmpfiles
Version: 249.3-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
>From the attached log (scroll to the bottom...):
Preparing to unpack .../systemd-standalone-sysusers_249.3-3_amd64.deb ...
Unpacking systemd-standalone-sysusers (249.3-3) ...
dpkg: error processing archive
/var/cache/apt/archives/systemd-standalone-sysusers_249.3-3_amd64.deb
(--unpack):
trying to overwrite '/bin/systemd-sysusers', which is also in package
systemd 247.9-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/systemd-standalone-sysusers_249.3-3_amd64.deb
Preparing to unpack .../systemd-standalone-tmpfiles_249.3-3_amd64.deb ...
Unpacking systemd-standalone-tmpfiles (249.3-3) ...
dpkg: error processing archive
/var/cache/apt/archives/systemd-standalone-tmpfiles_249.3-3_amd64.deb
(--unpack):
trying to overwrite '/bin/systemd-tmpfiles', which is also in package
systemd 247.9-1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/systemd-standalone-tmpfiles_249.3-3_amd64.deb
249.3-2 seems to be the version that split out the two packages,
please adjust the version for the B+R if needed.
cheers,
Andreas
# Partial distribution upgrade
# * install sid: systemd (247.9-1)
# * pick experimental: systemd-standalone-sysusers (249.3-3)
0m0.0s INFO:
--
0m0.0s INFO: To quickly glance what went wrong, scroll down to the bottom of
this logfile.
0m0.0s INFO: FAQ available at https://wiki.debian.org/piuparts/FAQ
0m0.0s INFO: The FAQ also explains how to contact us in case you think piuparts
is wrong.
0m0.0s INFO:
--
0m0.0s INFO: piuparts version 1.0.1~202108170201~0.95-51460-g807134c85 starting
up.
0m0.0s INFO: Command line arguments: /srv/piuparts/sbin/piuparts
--no-upgrade-test --warn-on-leftovers-after-purge --skip-logrotatefiles-test
--scriptsdir /etc/piuparts/scripts/ --tmpdir /tmp/piupartss/dose --mirror
http://ftp.de.debian.org/debian --basetgz
/srv/piuparts/slave/basetgz/sid_amd64.tar.gz -d sid -i /etc/nsswitch.conf
--log-file /tmp/tmp.f13PkTTlRJ --scriptsdir /tmp/tmp.ALTjEHowzD --apt hello
0m0.0s INFO: Running on: Linux zam378 5.10.40 #1 SMP Mon May 31 11:35:20 CEST
2021 x86_64
0m0.0s DEBUG: Created temporary directory /tmp/piupartss/dose/tmpTXXz9I/chroot
0m0.0s DEBUG: Unpacking /srv/piuparts/slave/basetgz/sid_amd64.tar.gz into
/tmp/piupartss/dose/tmpTXXz9I/chroot
0m0.0s DEBUG: Starting command: ['eatmydata', 'tar', '-C',
'/tmp/piupartss/dose/tmpTXXz9I/chroot', '-zxf',
'/srv/piuparts/slave/basetgz/sid_amd64.tar.gz']
0m1.1s DEBUG: Command ok: ['eatmydata', 'tar', '-C',
'/tmp/piupartss/dose/tmpTXXz9I/chroot', '-zxf',
'/srv/piuparts/slave/basetgz/sid_amd64.tar.gz']
0m1.1s DEBUG: Starting command: ['mount', '-t', 'proc', 'proc',
'/tmp/piupartss/dose/tmpTXXz9I/chroot/proc']
0m1.1s DEBUG: Command ok: ['mount', '-t', 'proc', 'proc',
'/tmp/piupartss/dose/tmpTXXz9I/chroot/proc']
0m1.1s DEBUG: Starting command: ['mount', '-t', 'devpts', '-o',
'newinstance,noexec,nosuid,gid=5,mode=0620,ptmxmode=0666', 'devpts',
'/tmp/piupartss/dose/tmpTXXz9I/chroot/dev/pts']
0m1.1s DEBUG: Command ok: ['mount', '-t', 'devpts', '-o',
'newinstance,noexec,nosuid,gid=5,mode=0620,ptmxmode=0666', 'devpts',
'/tmp/piupartss/dose/tmpTXXz9I/chroot/dev/pts']
0m1.1s DEBUG: Starting command: ['mount', '-o', 'bind',
'/tmp/piupartss/dose/tmpTXXz9I/chroot/dev/pts/ptmx',
'/tmp/piupartss/dos
Bug#983758: python-xarray: autopkgtest regression on several architectures
Source: python-xarray Version: 0.19.0-2 Followup-For: Bug #983758 The problem is exacerbated in 0.19.0-2 by this error during test collection /usr/lib/python3/dist-packages/xarray/tests/test_tutorial.py:9: in class TestLoadDataset: /usr/lib/python3/dist-packages/xarray/tests/test_tutorial.py:21: in TestLoadDataset ??? E NameError: name 'pyest' is not defined Looks like a simple typo, pyest instead of pytest.
Bug#992929: ukui-media FTBFS: ../ukmedia_device_switch_widget.cpp:5553:40: error: invalid use of incomplete type ‘MateMixerStreamControlPrivate’ {aka ‘struct _MateMixerStreamControlPrivate’}
Source: ukui-media
Version: 3.0.3-1
Severity: serious
Tags: ftbfs
ukui-media fails to build from source. A parallel=1 build ends with:
| g++ -c -pipe -std=c++11 -g -O2 -ffile-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -std=gnu++11 -pthread -pthread -pthread -Wall -Wextra
-D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -DQT_SVG_LIB -DQT_WIDGETS_LIB
-DQT_GUI_LIB -DQT_CORE_LIB -DQT_MULTIMEDIA_LIB -DQT_NETWORK_LIB -D_REENTRANT
-DQT_NO_KEYWORDS -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_DBUS_LIB -DQT_XML_LIB
-DQT_NETWORK_LIB -DQT_CORE_LIB -I../../ukui-volume-control-applet-qt -I.
-I../../ukui-volume-control-applet-qt -I../QtSingleApplication
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
-I/usr/include/mate-mixer -I/usr/include/x86_64-linux-gnu/qt5/QGSettings
-I/usr/include/x86_64-linux-gnu/qt5/QtSvg -I/usr/include/x86_64-linux-gnu/qt5
-I/usr/include/x86_64-linux-gnu/qt5/QtWidgets
-I/usr/include/x86_64-linux-gnu/qt5/QtGui
-I/usr/include/x86_64-linux-gnu/qt5/QtCore -I/usr/include/libmount
-I/usr/include/blkid -I/usr/include/x86_64-linux-gnu/qt5/QtMultimedia
-I/usr/include/x86_64-linux-gnu/qt5/QtNetwork -I/usr/include/dconf
-I/usr/include/KF5/KWindowSystem -I/usr/include/x86_64-linux-gnu/qt5/QtDBus
-I/usr/include/x86_64-linux-gnu/qt5/QtXml -I.
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o
ukmedia_device_switch_widget.o ../ukmedia_device_switch_widget.cpp
| ../ukmedia_device_switch_widget.cpp: In member function ‘virtual bool
UkmediaTrayIcon::event(QEvent*)’:
| ../ukmedia_device_switch_widget.cpp:98:22: warning: ‘int QWheelEvent::delta()
const’ is deprecated: Use angleDelta() [-Wdeprecated-declarations]
|98 | if (e->delta() > 0) {
| | ^
| In file included from /usr/include/x86_64-linux-gnu/qt5/QtGui/QMouseEvent:1,
| from ../ukmedia_device_volume_widget.h:25,
| from ../ukmedia_device_switch_widget.h:23,
| from ../ukmedia_device_switch_widget.cpp:18:
| /usr/include/x86_64-linux-gnu/qt5/QtGui/qevent.h:219:16: note: declared here
| 219 | inline int delta() const { return qt4D; }
| |^
| ../ukmedia_device_switch_widget.cpp:101:27: warning: ‘int
QWheelEvent::delta() const’ is deprecated: Use angleDelta()
[-Wdeprecated-declarations]
| 101 | else if (e->delta() < 0) {
| | ^
| In file included from /usr/include/x86_64-linux-gnu/qt5/QtGui/QMouseEvent:1,
| from ../ukmedia_device_volume_widget.h:25,
| from ../ukmedia_device_switch_widget.h:23,
| from ../ukmedia_device_switch_widget.cpp:18:
| /usr/include/x86_64-linux-gnu/qt5/QtGui/qevent.h:219:16: note: declared here
| 219 | inline int delta() const { return qt4D; }
| |^
| ../ukmedia_device_switch_widget.cpp: In member function ‘virtual void
DeviceSwitchWidget::paintEvent(QPaintEvent*)’:
| ../ukmedia_device_switch_widget.cpp:115:50: warning: unused parameter ‘event’
[-Wunused-parameter]
| 115 | void DeviceSwitchWidget::paintEvent(QPaintEvent *event)
| | ~^
| ../ukmedia_device_switch_widget.cpp: In lambda function:
| ../ukmedia_device_switch_widget.cpp:467:18: warning: variable ‘retval’ set
but not used [-Wunused-but-set-variable]
| 467 | gint retval;
| | ^~
| ../ukmedia_device_switch_widget.cpp: In member function ‘void
DeviceSwitchWidget::initSystemVolume()’:
| ../ukmedia_device_switch_widget.cpp:635:18: warning: unused variable
‘neddInit’ [-Wunused-variable]
| 635 | bool neddInit =
m_pInitSystemVolumeSetting->get(MIC_VOLUME).toBool();
| | ^~~~
| ../ukmedia_device_switch_widget.cpp: In member function ‘void
DeviceSwitchWidget::initHuaweiAudio(DeviceSwitchWidget*)’:
| ../ukmedia_device_switch_widget.cpp:642:62: warning: unused parameter ‘w’
[-Wunused-parameter]
| 642 | void DeviceSwitchWidget::initHuaweiAudio(DeviceSwitchWidget *w)
| | ^
| ../ukmedia_device_switch_widget.cpp: In member function ‘void
DeviceSwitchWidget::jumpControlPanelSlot()’:
| ../ukmedia_device_switch_widget.cpp:1072:46: warning: ‘void
QProcess::start(const QString&, QIODevice::OpenMode)’ is deprecated: Use
QProcess::start(const QString &program, const QStringList &arguments,OpenMode
mode = ReadWrite) instead [-Wdeprecated-declarations]
| 1072 | m_process->start("ukui-control-center -s");
| | ^
| In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/QProcess:1,
| from ../ukmedia_device_switch_widget.h:41,
| from ../ukmedia_device_switch_widget.cpp:18:
| /usr/include/x86_64-linux-gnu/qt5/QtCore/qprocess.h:168:10: note: declared
here
| 168 |
Bug#992928: libtasn1-6 arch-only FTBFS: Can't exec "gtkdocize": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 293.
Source: libtasn1-6 Version: 4.16.0-2 Severity: serious Tags: ftbfs libtasn1-6 fails to perform an arch-only build (but succeeds a full build). A build ends with: | dh binary-arch |dh_update_autotools_config -a |dh_autoreconf -a | libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'. | libtoolize: copying file 'build-aux/ltmain.sh' | libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'. | libtoolize: copying file 'm4/libtool.m4' | libtoolize: copying file 'm4/ltoptions.m4' | libtoolize: copying file 'm4/ltsugar.m4' | libtoolize: copying file 'm4/ltversion.m4' | libtoolize: copying file 'm4/lt~obsolete.m4' | Can't exec "gtkdocize": No such file or directory at /usr/share/autoconf/Autom4te/FileUtils.pm line 293. | autoreconf: error: gtkdocize failed with exit status: 2 | dh_autoreconf: error: autoreconf -f -i returned exit code 2 | make: *** [debian/rules:48: binary-arch] Error 25 | dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 Likely, moving gtk-doc-tools to Build-Depends would fix the issue, but Andreas Metzler found a way to avoid this for gnutls28. Helmut
Bug#992927: mutt: Mutt 2.1.2 is available, fixing a potential data-loss IMAP bug
Package: mutt Version: 2.0.5-4.1 Severity: grave Justification: causes non-serious data loss Mutt 2.1.2 is available. From the announce: "This is an important bug-fix release, fixing a potential data-loss IMAP bug. IMAP users are strongly advised to upgrade." For stable and oldstable: "Packagers, please consider backporting commit 647efbd1 if at all possible." See http://lists.mutt.org/pipermail/mutt-announce/Week-of-Mon-20210823/40.html for additional information. Note also that there is a minor "mutt -v" output issue with the current Mutt and, in particular, GNU Autoconf 2.71, which is now in unstable. I fixed this issue in Mutt's repository yesterday and I'm going to report a second bug for that. -- Package-specific info: Mutt 2.1.1+55 (898eb3ca) vl-138565 (2021-08-24) Copyright (C) 1996-2021 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 5.10.0-8-amd64 (x86_64) ncurses: ncurses 6.2.20201114 (compiled with 6.2) libidn: 1.38 (compiled with 1.38) Compiler: Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/10/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:amdgcn-amdhsa:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Debian 10.2.1-6' --with-bugurl=file:///usr/share/doc/gcc-10/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,m2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-10 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-bootstrap --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --enable-libphobos-checking=release --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-10-Km9U7s/gcc-10-10.2.1/debian/tmp-nvptx/usr,amdgcn-amdhsa=/build/gcc-10-Km9U7s/gcc-10-10.2.1/debian/tmp-gcn/usr,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu --with-build-config=bootstrap-lto-lean --enable-link-mutex Thread model: posix Supported LTO compression algorithms: zlib zstd gcc version 10.2.1 20210110 (Debian 10.2.1-6) Configure options: '--prefix=/home/vinc17 --enable-debug --enable-pop --enable-imap --with-ssl --enable-compressed --with-exec-shell=/home/vinc17/bin/sh.screen --enable-gpgme --with-system-dotlock=/usr/bin/mutt_dotlock CC=gcc '\''CFLAGS=-g -O3 -march=native -fsanitize=undefined -fno-sanitize-recover'\''' Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O3 -march=native -fsanitize=undefined -fno-sanitize-recover Compile options: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK +USE_POP +USE_IMAP -USE_SMTP +USE_SSL_OPENSSL -USE_SSL_GNUTLS -USE_SASL -USE_GSS +HAVE_GETADDRINFO +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_FUTIMENS +CRYPT_BACKEND_CLASSIC_PGP +CRYPT_BACKEND_CLASSIC_SMIME +CRYPT_BACKEND_GPGME -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_LIBIDN -HAVE_LIBIDN2 +HAVE_GETSID -USE_HCACHE -USE_SIDEBAR +USE_COMPRESSED +USE_INOTIFY ISPELL="/usr/bin/ispell" SENDMAIL="/usr/sbin/sendmail" MAILPATH="/var/mail" PKGDATADIR="/home/vinc17/share/mutt" SYSCONFDIR="/home/vinc17/etc" EXECSHELL="/home/vinc17/bin/sh.screen" -MIXMASTER To contact the developers, please mail to . To report a bug, please contact the Mutt maintainers via gitlab: https://gitlab.com/muttmua/mutt/issues patch-20200424.vl.pretty_size.1 patch-20200505.vl.simplesearchkw.1 patch-20200424.pdmef.progress.vl.1 patch-20201129.vl.address_all_patt.1 patch-20201130.tamovl.sysdotlock.1 -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=POSIX, LC_CTYPE=C.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 packa
Bug#979458: Reassigning, merging and rising severity level of Bugs #979458 and #979459
* Rafael Laboissière [2021-08-24 08:45]: […] The trivial patch that fixes the problem is attached to this message. Please, consider rather the patch that is attached to the present message. The jed-common.prerm script must honor the failed-upgrade argument, since the script in version 1:0.99.19-8 will fail on upgrade. In order to remove the jed package from their systems, users will have to upgrade it to 1:0.99.19-9 previously. Best, Rafael Laboissière diff -Nru jed-0.99.19/debian/jed-common.postinst jed-0.99.19/debian/jed-common.postinst --- jed-0.99.19/debian/jed-common.postinst 2014-06-09 22:54:57.0 -0300 +++ jed-0.99.19/debian/jed-common.postinst 2021-08-25 04:34:25.0 -0300 @@ -7,7 +7,7 @@ case "$1" in configure) - TEMP=$(tempfile) + TEMP=$(mktemp) printf "Running /usr/share/jed/compile/jed-common..." if ! /usr/share/jed/compile/jed-common install >$TEMP 2>&1; then diff -Nru jed-0.99.19/debian/jed-common.prerm jed-0.99.19/debian/jed-common.prerm --- jed-0.99.19/debian/jed-common.prerm 2014-06-09 22:54:57.0 -0300 +++ jed-0.99.19/debian/jed-common.prerm 2021-08-25 04:35:10.0 -0300 @@ -3,9 +3,9 @@ set -e case "$1" in -remove|upgrade|deconfigure) +remove|upgrade|deconfigure|failed-upgrade) -TEMP=$(tempfile) +TEMP=$(mktemp) printf "Running /usr/share/jed/compile/jed-common..." RET=0 /usr/share/jed/compile/jed-common remove >$TEMP 2>&1 || RET=$? @@ -18,9 +18,6 @@ ;; -failed-upgrade) -;; - *) echo "prerm called with unknown argument \`$1'" >&2 exit 1 diff -Nru jed-0.99.19/debian/jed.postinst jed-0.99.19/debian/jed.postinst --- jed-0.99.19/debian/jed.postinst 2014-06-09 22:54:57.0 -0300 +++ jed-0.99.19/debian/jed.postinst 2021-08-25 04:34:25.0 -0300 @@ -12,7 +12,7 @@ --install /usr/bin/jed-script jed-script /usr/bin/jed 50 \ --slave /usr/share/man/man1/jed-script.1.gz jed-script.1.gz /usr/share/man/man1/jed.1.gz; -TEMP=$(tempfile) +TEMP=$(mktemp) RET=0 printf "Updating precompiled files..." run-parts --exit-on-error --arg=install /usr/share/jed/compile/ \ diff -Nru jed-0.99.19/debian/xjed.postinst jed-0.99.19/debian/xjed.postinst --- jed-0.99.19/debian/xjed.postinst 2014-06-09 22:54:57.0 -0300 +++ jed-0.99.19/debian/xjed.postinst 2021-08-25 04:34:25.0 -0300 @@ -12,7 +12,7 @@ --install /usr/bin/jed-script jed-script /usr/bin/xjed 40 \ --slave /usr/share/man/man1/jed-script.1.gz jed-script.1.gz /usr/share/man/man1/xjed.1.gz; -TEMP=$(tempfile) +TEMP=$(mktemp) RET=0 printf "Updating precompiled files..." run-parts --exit-on-error --arg=install /usr/share/jed/compile/ \
Processed: tagging 978824
Processing commands for cont...@bugs.debian.org: > tags 978824 + ftbfs Bug #978824 [src:granule] granule: ftbfs with autoconf 2.70 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 978824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978824 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#992926: cod-tools: autopkgtest regression on 32bit
Source: cod-tools Version: 3.2.0+dfsg-1 Severity: serious https://ci.debian.net/data/autopkgtest/testing/i386/c/cod-tools/14823189/log.gz https://ci.debian.net/data/autopkgtest/testing/armhf/c/cod-tools/14823170/log.gz ... /tmp/autopkgtest-lxc.jeerr0gs/downtmp/autopkgtest_tmp/tests/cases/cif_filter_157.inp: FAILED: ... > perl: malloc.c:2379: sysmalloc: Assertion `(old_top == initial_top (av) && > old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse > (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed. > Aborted ... upstream FAIL non-zero exit status 1 ...
Bug#992924: freefem++: autopkgtest failure on arm64/ppc64el
Source: freefem++ Version: 4.9+dfsg1-2 Severity: serious https://ci.debian.net/data/autopkgtest/testing/arm64/f/freefem++/14730686/log.gz https://ci.debian.net/data/autopkgtest/testing/ppc64el/f/freefem++/14702337/log.gz ... g++ -c -fPIC '-I/usr/include/freefem++' -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -DNDEBUG -O3 -std=c++14 -DBAMG_LONG_LONG -DNCHECKPTR -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/suitesparse -I/usr/include/hdf5/serial -I/usr/include '/tmp/autopkgtest-lxc.pbpt2s9x/downtmp/build.g9L/src/plugin/seq/myfunction.cpp' g++ -shared -fPIC -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -DNDEBUG -O3 -std=c++14 -DBAMG_LONG_LONG -DNCHECKPTR -fPIC -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/suitesparse -I/usr/include/hdf5/serial -I/usr/include 'myfunction.o' -o myfunction.so build: OK running myfunction with load.edp... -- FreeFem++ v4.9 ( - git no git) Load: lg_fem lg_mesh lg_mesh3 eigenvalue 1 : // Example of dynamic function load 2 : // 3 : // $Id$ 4 : 5 : load "myfunction" 6 : // dumptable(cout); 7 : mesh Th=square(5,5); 8 : fespace Vh(Th,P1); 9 : Vh uh= myfunction(); // warning do not forget () 10 : cout << uh[].min << " " << uh[].max << endl; 11 : cout << " test io ( " << endl; 12 : testio(); 13 : cout << " ) end test io .. " << endl; sizestack + 1024 =1416 ( 392 ) -- Square mesh : nb vertices =36 , nb triangles = 50 , nb boundary edges 20 0 0.841471 test io ( test cout 3.14159 test cout 512 test cerr 3.14159 test cerr 512 ) end test io .. times: compile 0.005264s, execution 0.000154s, mpirank:0 CodeAlloc : nb ptr 3586, size :484696 mpirank: 0 Ok: Normal End Segmentation fault autopkgtest [22:45:03]: test build-and-run-lib: ---] build-and-run-libFAIL non-zero exit status 139 ...
Bug#992923: manaplus: binary-any FTBFS
Source: manaplus Version: 2.1.3.17-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=manaplus&ver=2.1.3.17-1 ... debian/rules override_dh_install make[1]: Entering directory '/<>' dh_install chmod -x /<>/debian/manaplus-data/usr/share/icons/hicolor/scalable/apps/manaplus.svg chmod: cannot access '/<>/debian/manaplus-data/usr/share/icons/hicolor/scalable/apps/manaplus.svg': No such file or directory make[1]: *** [debian/rules:17: override_dh_install] Error 1
Bug#992908: awesome: autopkgtest regression between 20 and 23 August 2021: Could not resolve keysym
Hi,
I can reproduce the autopkgtest failure on my system after only
upgrading xkb-data from 2.29-2 to 2.33-1.
I noticed that the xkb-data build has been changed to meson [1], and
it is no longer instructed to install xfree86 symlinks.
And also according to a debdiff, xfree86-related symlinks are now
dropped:
> Files in first .deb but not in second
> -
> lrwxrwxrwx root/root /usr/share/X11/xkb/rules/xfree86 -> base
> lrwxrwxrwx root/root /usr/share/X11/xkb/rules/xfree86.lst -> base.lst
> lrwxrwxrwx root/root /usr/share/X11/xkb/rules/xfree86.xml -> base.xml
But even with manually restoring the symlinks, the errors still appear
("Could not resolve keysym XF86RightUp" etc).
@Timo, do you have an idea why XF86* keysyms are no longer available
with the new xkb-data?
The actual output on stderr seems to come from xkbcomp.
Kind regards,
Reiner
[1]
https://salsa.debian.org/xorg-team/data/xkeyboard-config/-/commit/89b2833a2271d5cac9ede6dfe506ae811db299fe
signature.asc
Description: PGP signature
Bug#992922: gpgme1.0 FTBFS on 32bit: segfault during tests
Source: gpgme1.0
Version: 1.16.0-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/logs.php?pkg=gpgme1.0&ver=1.16.0-1
...
[-- Response --]
pub:-:1024:17:FE180B1DA9E3B0B2:920888034:0::-:::sca
fpr:D695676BDCEDCC2CDD6152BCFE180B1DA9E3B0B2:
sub:-:1024:16:5381EA4EE29BA37F:920888071:0:e
fpr:FA23A4BE04E938CF921EDE7E5381EA4EE29BA37F:
uid:-Bob (demo key):::S10 S3 H3 H2 Z2 Z1,no-ks-modify:1,p::
uid:-Bravo Test (demo key) :::S10 S3 H3 H2 Z2
Z1,no-ks-modify:2,::
pub:-:1024:17:FE180B1DA9E3B0B2:920888034:0::-:::sca
fpr:D695676BDCEDCC2CDD6152BCFE180B1DA9E3B0B2:
sub:-:1024:16:5381EA4EE29BA37F:920888071:0:e
fpr:FA23A4BE04E938CF921EDE7E5381EA4EE29BA37F:
uid:-Bob (demo key):::S10 S3 H3 H2 Z2 Z1,no-ks-modify:1,ps::
uid:-Bravo Test (demo key) :::S10 S3 H3 H2 Z2
Z1,no-ks-modify:2,::
pub:-:1024:17:FE180B1DA9E3B0B2:920888034:0::-:::sca
fpr:D695676BDCEDCC2CDD6152BCFE180B1DA9E3B0B2:
sub:-:1024:16:5381EA4EE29BA37F:920888071:0:e
fpr:FA23A4BE04E938CF921EDE7E5381EA4EE29BA37F:
uid:-Bob (demo key):::S10 S3 H3 H2 Z2 Z1,no-ks-modify:1,psm::
uid:-Bravo Test (demo key) :::S10 S3 H3 H2 Z2
Z1,no-ks-/bin/bash: line 6: 591523 Segmentation fault
GNUPGHOME=/<>/build/tests/gpg LC_ALL=C GPG_AGENT_INFO=
top_srcdir=../../.. ${dir}$tst
FAIL: t-edit-sign
...
===
1 of 27 tests failed
Please report to https://bugs.gnupg.org
===
make[6]: *** [Makefile:894: check-TESTS] Error 1
Bug#978768: marked as done (gold linker crashing with -Wl,--threads)
Your message dated Wed, 25 Aug 2021 09:16:53 +0200 with message-id <6c30fa3b-de06-bba0-1e8d-b2af7b25b...@debian.org> and subject line Re: gold linker crashing with -Wl,--threads has caused the Debian Bug report #978768, regarding gold linker crashing with -Wl,--threads 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.) -- 978768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:apt-cacher-ng Version: 3.5-1 Severity: normal Tags: sid bookworm User: d...@debian.org Usertags: ftbfs-ac270 [This bug report is not targeted to the upcoming bullseye release] The package fails to build in a test rebuild on at least amd64 with autoconf 2.70, but succeeds to build with autoconf 2.69. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://qa-logs.debian.net/2020/09/26.ac270/apt-cacher-ng_3.5-1_unstable_ac270.log The last lines of the build log are at the end of this report. To build with autoconf 2.70, please install the autoconf package from experimental: apt-get -t=experimental install autoconf [...] cd /<>/obj-x86_64-linux-gnu/source && /usr/bin/c++ -DACNG_CORE_IN_SO -Dsupacng_EXPORTS -I/<>/obj-x86_64-linux-gnu -I/<> -I/<>/include -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -D_FILE_OFFSET_BITS=64 -Wall -Wextra -Wno-unused-parameter -fvisibility=hidden -fdata-sections -ffunction-sections -pthread -fvisibility-inlines-hidden -std=gnu++14 -o CMakeFiles/supacng.dir/dnsiter.cc.o -c /<>/source/dnsiter.cc [ 84%] Linking CXX shared library ../libsupacng.so cd /<>/obj-x86_64-linux-gnu/source && /usr/bin/cmake -E cmake_link_script CMakeFiles/supacng.dir/link.txt --verbose=1 /usr/bin/c++ -fPIC -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -Wl,--gc-sections -shared -Wl,-soname,libsupacng.so -o ../libsupacng.so CMakeFiles/supacng.dir/sockio.cc.o CMakeFiles/supacng.dir/acbuf.cc.o CMakeFiles/supacng.dir/acfg.cc.o CMakeFiles/supacng.dir/acfg_defaults.cc.o CMakeFiles/supacng.dir/aclogger.cc.o CMakeFiles/supacng.dir/caddrinfo.cc.o CMakeFiles/supacng.dir/dirwalk.cc.o CMakeFiles/supacng.dir/dlcon.cc.o CMakeFiles/supacng.dir/fileio.cc.o CMakeFiles/supacng.dir/fileitem.cc.o CMakeFiles/supacng.dir/filelocks.cc.o CMakeFiles/supacng.dir/filereader.cc.o CMakeFiles/supacng.dir/header.cc.o CMakeFiles/supacng.dir/meta.cc.o CMakeFiles/supacng.dir/tcpconnect.cc.o CMakeFiles/supacng.dir/cleaner.cc.o CMakeFiles/supacng.dir/job.cc.o CMakeFiles/supacng.dir/bgtask.cc.o CMakeFiles/supacng.dir/cacheman.cc.o CMakeFiles/supacng.dir/conn.cc. o CMakeFiles/supacng.dir/conserver.cc.o CMakeFiles/supacng.dir/expiration.cc.o CMakeFiles/supacng.dir/lockable.cc.o CMakeFiles/supacng.dir/maintenance.cc.o CMakeFiles/supacng.dir/mirror.cc.o CMakeFiles/supacng.dir/pkgimport.cc.o CMakeFiles/supacng.dir/showinfo.cc.o CMakeFiles/supacng.dir/evabase.cc.o CMakeFiles/supacng.dir/evasocket.cc.o CMakeFiles/supacng.dir/dnsiter.cc.o -latomic -levent -levent_pthreads -levent -lwrap -lz -lbz2 -llzma -lssl -lcrypto -lsystemd -lpthread -levent_pthreads -lwrap -lz -lbz2 -llzma -lssl -lcrypto -lsystemd -lpthread make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' [ 84%] Built target supacng make -f fs/CMakeFiles/acngfs.dir/build.make fs/CMakeFiles/acngfs.dir/depend make -f source/CMakeFiles/acngtool.dir/build.make source/CMakeFiles/acngtool.dir/depend make -f source/CMakeFiles/apt-cacher-ng.dir/build.make source/CMakeFiles/apt-cacher-ng.dir/depend make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/source /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/source /<>/obj-x86_64-linux-gnu/source/CMakeFiles/acngtool.dir/DependInfo.cmake --color= make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/fs /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/fs /<>/obj-x86_64-linux-gnu/fs/CMakeFiles/acngfs.dir/DependInfo.cmake --color= make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/source /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-
Bug#978768: gold linker crashing with -Wl,--threads
Version: 2.37-4 builds fine at least on amd64.
