Processed (with 5 errors): Re: Bug#964471: libreoffice-l10n-ru: error when configuring: cp: cannot create regular file '/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory
Processing commands for cont...@bugs.debian.org:
> tag 964471 - moreinfo
Bug #964471 {Done: Rene Engelhard } [libreoffice-l10n-ru]
libreoffice-l10n-ru: error when configuring: cp: cannot create regular file
'/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory
Removed tag(s) moreinfo.
> tag 964471 - unreproducible
Bug #964471 {Done: Rene Engelhard } [libreoffice-l10n-ru]
libreoffice-l10n-ru: error when configuring: cp: cannot create regular file
'/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory
Removed tag(s) unreproducible.
> Hi,
Unknown command or malformed arguments to command.
> Am 07.07.20 um 23:05 schrieb Evgeny Kapun:
Unknown command or malformed arguments to command.
> > On 07.07.2020 22:40, Rene Engelhard wrote:
Unknown command or malformed arguments to command.
> >> Even that worked for me in said testing VM "upgraded" to unstable with
Unknown command or malformed arguments to command.
> >> your apt-get --with-new-pkgs upgrade.
Unknown command or malformed arguments to command.
Too many unknown commands, stopping here.
Please contact me if you need assistance.
--
964471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964471
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#964471: libreoffice-l10n-ru: error when configuring: cp: cannot create regular file '/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory
tag 964471 - moreinfo tag 964471 - unreproducible Hi, Am 07.07.20 um 23:05 schrieb Evgeny Kapun: > On 07.07.2020 22:40, Rene Engelhard wrote: >> Even that worked for me in said testing VM "upgraded" to unstable with >> your apt-get --with-new-pkgs upgrade. >> >> libreoffice-l10n-de, libreoffice-l10n-ru and other LO packages were kept >> back. > > After some testing, I found out that you also need to pass > `--no-install-recommends`, as otherwise `Recommends: libreoffice-core > (>> 1:7.0.0~rc1)` in libreoffice-l10n-ru prevents it from upgrading. > Ah, yes, indeed. Regards, Rene
Bug#963304: marked as done (cpio: FTBFS: i686-w64-mingw32-ld: ../gnu/libgnu.a(progname.o):progname.c:(.bss+0x0): multiple definition of `program_name'; global.o:global.c:(.bss+0xd8): first defined her
Your message dated Wed, 08 Jul 2020 04:48:52 + with message-id and subject line Bug#963304: fixed in cpio 2.13+dfsg-3 has caused the Debian Bug report #963304, regarding cpio: FTBFS: i686-w64-mingw32-ld: ../gnu/libgnu.a(progname.o):progname.c:(.bss+0x0): multiple definition of `program_name'; global.o:global.c:(.bss+0xd8): first defined here 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.) -- 963304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963304 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cpio Version: 2.13+dfsg-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj-win32/src' > CC copyin.o > CC copyout.o > ../../src/copyout.c: In function ‘process_copy_out’: > ../../src/copyout.c:794:15: warning: implicit declaration of function > ‘readlink’ [-Wimplicit-function-declaration] > 794 | link_size = readlink (orig_file_name, link_name, > | ^~~~ > CC copypass.o > ../../src/copypass.c: In function ‘process_copy_pass’: > ../../src/copypass.c:275:16: warning: implicit declaration of function > ‘readlink’ [-Wimplicit-function-declaration] > 275 |link_size = readlink (input_name.ds_string, link_name, > |^~~~ > CC defer.o > CC dstring.o > CC global.o > CC fatal.o > CC main.o > In file included from ../../lib/system.h:456, > from ../../src/main.c:24: > ../../src/main.c: In function ‘main’: > ../../gnu/gettext.h:88:25: warning: statement with no effect [-Wunused-value] >88 | ((void) (Domainname), (const char *) (Dirname)) > | ^~~ > ../../src/main.c:771:3: note: in expansion of macro ‘bindtextdomain’ > 771 | bindtextdomain (PACKAGE, LOCALEDIR); > | ^~ > ../../gnu/gettext.h:85:34: warning: statement with no effect [-Wunused-value] >85 | # define textdomain(Domainname) ((const char *) (Domainname)) > | ~^~~~ > ../../src/main.c:772:3: note: in expansion of macro ‘textdomain’ > 772 | textdomain (PACKAGE); > | ^~ > CC tar.o > ../../src/tar.c: In function ‘write_out_tar_header’: > ../../src/tar.c:213:7: warning: ‘strncpy’ output truncated before terminating > nul copying 2 bytes from a string of the same length [-Wstringop-truncation] > 213 | strncpy (tar_hdr->version, TVERSION, TVERSLEN); > | ^~ > CC util.o > In file included from > /usr/lib/gcc/i686-w64-mingw32/10-win32/include/stddef.h:1, > from ../gnu/sys/types.h:50, > from ../../lib/system.h:33, > from ../../src/util.c:20: > ../../src/util.c:48:12: warning: ‘_errno’ redeclared without dllimport > attribute: previous dllimport ignored [-Wattributes] >48 | extern int errno; > |^ > ../../src/util.c: In function ‘fchown_or_chown’: > ../../src/util.c:1205:12: warning: implicit declaration of function ‘fchown’; > did you mean ‘lchown’? [-Wimplicit-function-declaration] > 1205 | return fchown (fd, uid, gid); > |^~ > |lchown > ../../src/util.c: In function ‘fchmod_or_chmod’: > ../../src/util.c:1214:12: warning: implicit declaration of function ‘fchmod’; > did you mean ‘chmod’? [-Wimplicit-function-declaration] > 1214 | return fchmod (fd, mode); > |^~ > |chmod > CC filemode.o > CC idcache.o > CC makepath.o > CC userspec.o > CCLD cpio.exe > /usr/bin/i686-w64-mingw32-ld: > ../gnu/libgnu.a(progname.o):progname.c:(.bss+0x0): multiple definition of > `program_name'; global.o:global.c:(.bss+0xd8): first defined here > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/06/20/cpio_2.13+dfsg-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message
Processed: your mail
Processing commands for cont...@bugs.debian.org:
> notfound 963020 smbmap/1.8.2-1
Bug #963020 {Done: =?utf-8?q?Rapha=C3=ABl_Hertzog?=
} [src:impacket, src:smbmap] impacket breaks
smbmap autopkgtest: No module named 'pkg_resources'
No longer marked as found in versions smbmap/1.8.2-1.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
963020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963020
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: py2removal bugs severity updates - 2020-07-08 03:34:22.192895+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # and https://lists.debian.org/debian-python/2019/12/msg00076.html > # and https://lists.debian.org/debian-python/2020/03/msg00087.html > # mail threads for more details on this severity update > # viewmol is an application, has low popcon (376 <= 1000), and has 0 external > rdeps or not in testing > severity 938774 serious Bug #938774 [src:viewmol] viewmol: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 938774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#939739: marked as done (openipmi: fails to detect udev)
Your message dated Wed, 08 Jul 2020 03:19:02 + with message-id and subject line Bug#939739: fixed in openipmi 2.0.29-0.1 has caused the Debian Bug report #939739, regarding openipmi: fails to detect udev 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.) -- 939739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939739 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: openipmi Version: 2.0.25-2.1 Severity: serious User: debian-ad...@lists.debian.org Usertags: needed-by-DSA-Team X-Debbugs-Cc: debian-ad...@lists.debian.org /etc/init.d/openipmi tries to detect udev by looking for /sbin/udev or /sbin/udevd, however neither of those exist anymore, and it's spelled /lib/systemd/systemd-udevd instead. So the init script tries to handle device nodes itself in all kinds of horrible ways. Cheers, Julien --- End Message --- --- Begin Message --- Source: openipmi Source-Version: 2.0.29-0.1 Done: Sergio Durigan Junior We believe that the bug you reported is fixed in the latest version of openipmi, 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 939...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sergio Durigan Junior (supplier of updated openipmi 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: Tue, 07 Jul 2020 22:28:53 -0400 Source: openipmi Architecture: source Version: 2.0.29-0.1 Distribution: unstable Urgency: medium Maintainer: Noël Köthe Changed-By: Sergio Durigan Junior Closes: 920461 939739 946059 Changes: openipmi (2.0.29-0.1) unstable; urgency=medium . [ Sergio Durigan Junior ] * Non-maintainer upload. * d/watch: Update URL, since sf.net is giving a 404. * New upstream version 2.0.29. (Closes: #946059) * d/control: Add libreadline-dev to Build-Depends. The package doesn't use libedit anymore. Thanks to Christian Ehrhardt * d/control: Bump debhelper to 13; use debhelper-compat. * d/rules: Disable the Python support. The Python support is now on by default, and historically we don't ship it, so just disable it. Thanks to Christian Ehrhardt * d/rules: Adjust call to dh_install to use -a instead of -s. The "-s" option has been deprecated. * d/openipmi.init: Add check for systemd-udev. Even though udevadm and systemd-udev are distributed by the same package, it's a good idea to also check for the systemd-related udev binary, just in case. Thanks to Richard Laager (Closes: #939739) * d/control: Bump Standards-Version to 4.5. * d/control: Add Vcs-* fields. * d/openipmi.init: Remove erroneous "$" prefix when printing a string. (Closes: #920461) * d/watch: Use QA's sf.net redirector. . [ Christian Ehrhardt ] * d/openipmi.init: fix various issues identified upstream (LP: #188) Debians and upstreams init file diverged a long time ago, so it is hard to fully unify them. But we can follow upstreams changes and apply it to d/openipmi.init. Checksums-Sha1: dcc9dfe4c2d47ec43df9110037d34bd417263c5f 2063 openipmi_2.0.29-0.1.dsc a8dd1a9b877e94926af1da69421e8f2bd642c9c7 3119530 openipmi_2.0.29.orig.tar.gz cff1090c8670eab10160fde29fccd6114befc9f3 8828 openipmi_2.0.29-0.1.debian.tar.xz 962da71b04708f223b4d98e2afe7149a7974bd24 7305 openipmi_2.0.29-0.1_amd64.buildinfo Checksums-Sha256: a993d9acd2172b5de8924a1cdb3398b0f49a657a6925798f05d8c2134dd3d181 2063 openipmi_2.0.29-0.1.dsc 2244124579afb14e569f34393e9ac61e658a28b6ffa8e5c0d2c1c12a8ce695cd 3119530 openipmi_2.0.29.orig.tar.gz cc2bb8d8f4dec14878982eee17ad8adc7d497419e462bb6fdeb3878cca5b2cae 8828 openipmi_2.0.29-0.1.debian.tar.xz 196bd55b1fa4a1bd1d7d6dbff75a014ed2f78cb02caf26f4a4060d0b4c56a64f 7305 openipmi_2.0.29-0.1_amd64.buildinfo Files: 863e4d398a5a758d8b858712cbd0f9af 2063 admin optional openipmi_2.0.29-0.1.dsc 46b452e95d69c92e4172b3673ed88d52 3119530 admin optional openipmi_2.0.29.orig.tar.gz 3e447006d68064941a2bab37d9fa780a 8828 admin optional openipmi_2.0.29-0.1.debian.tar.xz d3e89feb6889d4049f13719be5836afe 7305 admin optional openipmi_2.0.29-0.1_amd64.buildinfo -BEGIN PGP SIGNATURE-
Bug#964362: chromium crash frequently, SEGV_MAPERR
Source: chromium Version: 83.0.4103.116-1~deb10u2 Followup-For: Bug #964362 Dear Maintainer, Frequent crash still occurred after upgrade from 83.0.4103.116-1~deb10u1 to ~deb10u2. Crash occurs after executing chromium for few minutes. Slow responsiveness found from 83..debu10u1 did not occur in this version. Command: /usr/bin/chromium --proxy-server="X.X.X.X:X" --proxy-bypass-list="X.X.*;X.X.*;*.X" --disk-cache-dir=/dev/null Error log: [9545:9545:0708/100337.163855:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [9506:9561:0708/100337.177992:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Code Cache/js [9506:9562:0708/100337.178131:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Code Cache/wasm [9506:9561:0708/100337.193285:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Code Cache/js [9506:9562:0708/100337.193285:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Code Cache/wasm [9506:9561:0708/100337.193321:ERROR:simple_backend_impl.cc(757)] Simple Cache Backend: wrong file structure on disk: 1 path: /dev/null/Profile 2/Code Cache/js [9506:9562:0708/100337.193331:ERROR:simple_backend_impl.cc(757)] Simple Cache Backend: wrong file structure on disk: 1 path: /dev/null/Profile 2/Code Cache/wasm [9506:9527:0708/100337.275442:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Code Cache/js [9506:9529:0708/100337.275452:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Code Cache/wasm [9506:9527:0708/100337.275485:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Code Cache/js [9506:9529:0708/100337.275493:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Code Cache/wasm [9506:9527:0708/100337.275494:ERROR:simple_backend_impl.cc(757)] Simple Cache Backend: wrong file structure on disk: 1 path: /dev/null/Profile 2/Code Cache/js [9506:9529:0708/100337.275507:ERROR:simple_backend_impl.cc(757)] Simple Cache Backend: wrong file structure on disk: 1 path: /dev/null/Profile 2/Code Cache/wasm [9550:9630:0708/100337.294177:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Cache [9550:9630:0708/100337.294308:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Cache [9550:9630:0708/100337.294328:ERROR:simple_backend_impl.cc(757)] Simple Cache Backend: wrong file structure on disk: 1 path: /dev/null/Profile 2/Cache [9550:9629:0708/100337.294541:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Cache [9550:9629:0708/100337.294580:ERROR:simple_backend_impl.cc(81)] Failed to create directory: /dev/null/Profile 2/Cache [9550:9629:0708/100337.294589:ERROR:simple_backend_impl.cc(757)] Simple Cache Backend: wrong file structure on disk: 1 path: /dev/null/Profile 2/Cache [9550:9616:0708/100337.303063:ERROR:disk_cache.cc(184)] Unable to create cache [9506:9506:0708/100337.305955:ERROR:disk_cache.cc(184)] Unable to create cache [9506:9506:0708/100337.305995:ERROR:disk_cache.cc(184)] Unable to create cache [9506:9528:0708/100346.855696:ERROR:connection_factory_impl.cc(420)] Failed to connect to MCS endpoint with error -111 [9506:9528:0708/100915.111885:ERROR:socket_stream.cc(218)] Closing stream with result -2 [9506:9528:0708/100915.118034:ERROR:connection_factory_impl.cc(420)] Failed to connect to MCS endpoint with error -111 Received signal 11 SEGV_MAPERR 7f01c431fad7 #0 0x564a040cc469 (/usr/lib/chromium/chromium+0x51f9468) #1 0x564a0402a193 (/usr/lib/chromium/chromium+0x5157192) #2 0x564a040cbff1 (/usr/lib/chromium/chromium+0x51f8ff0) #3 0x7ff2ed488730 (/lib/x86_64-linux-gnu/libpthread-2.28.so+0x1272f) #4 0x7ff2e7394d48 (/lib/x86_64-linux-gnu/libc-2.28.so+0x7fd47) #5 0x7ff2e7397a58 (/lib/x86_64-linux-gnu/libc-2.28.so+0x82a57) #6 0x7ff2e739956a __libc_malloc #7 0x564a040e3bee operator new() #8 0x7ff2e760e3cd std::__cxx11::basic_string<>::reserve() #9 0x7ff2e7602845 std::__cxx11::basic_stringbuf<>::overflow() #10 0x7ff2e760c9cb std::basic_streambuf<>::xsputn() #11 0x7ff2e75fdb34 std::__ostream_insert<>() #12 0x564a040cc7b9 (/usr/lib/chromium/chromium+0x51f97b8) #13 0x564a040cc844 (/usr/lib/chromium/chromium+0x51f9843) #14 0x564a0403c9d2 (/usr/lib/chromium/chromium+0x51699d1) #15 0x564a0403eb1e (/usr/lib/chromium/chromium+0x516bb1d) #16 0x564a027a762a (/usr/lib/chromium/chromium+0x38d4629) #17 0x564a027a767e (/usr/lib/chromium/chromium+0x38d467d) #18 0x564a01e4d98f (/usr/lib/chromium/chromium+0x2f7a98e) #19 0x564a02761559 (/usr/lib/chromium/chromium+0x388e558) #20 0x564a0276179e (/usr/lib/chromium/chromium+0x388e79d) #21 0x564a027aae67 (/usr/lib/chromium/chromium+0x38d7e66) #22 0x564a027d6ac2 (/usr/lib/chromium/chromium+0x3903ac1) #23 0x564a027d6d7e (/usr/lib/chromium/chromium+0x3903d7d) #24
Bug#964495: libmicrohttpd: New 0.97.1-1 version causes libkiwix to FTBFS
Package: libmicrohttpd
Version: 0.97.1-1
Severity: serious
Tags: ftbfs
The new 0.97.1 version is causing libkiwix to FTBFS.
[12/51] c++ -Isrc/25a6634@@kiwix@sha -Isrc -I../src -Iinclude -I../include
-I/usr/include/kainjow -Istatic -I/usr/include/x86_64-linux-gnu
-I/usr/include/p11-kit-1 -fdiagnostics-color=always -pipe
-D_FILE_OFFSET_BITS=64 -Werror -std=c++11 -g -O2
-fdebug-prefix-map=/build/libkiwix-9.3.0+dfsg=. -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread
-MD -MQ 'src/25a6634@@kiwix@sha/server.cpp.o' -MF
'src/25a6634@@kiwix@sha/server.cpp.o.d' -o
'src/25a6634@@kiwix@sha/server.cpp.o' -c ../src/server.cpp
FAILED: src/25a6634@@kiwix@sha/server.cpp.o
c++ -Isrc/25a6634@@kiwix@sha -Isrc -I../src -Iinclude -I../include
-I/usr/include/kainjow -Istatic -I/usr/include/x86_64-linux-gnu
-I/usr/include/p11-kit-1 -fdiagnostics-color=always -pipe
-D_FILE_OFFSET_BITS=64 -Werror -std=c++11 -g -O2
-fdebug-prefix-map=/build/libkiwix-9.3.0+dfsg=. -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread
-MD -MQ 'src/25a6634@@kiwix@sha/server.cpp.o' -MF
'src/25a6634@@kiwix@sha/server.cpp.o.d' -o
'src/25a6634@@kiwix@sha/server.cpp.o' -c ../src/server.cpp
../src/server.cpp: In member function ‘bool kiwix::InternalServer::start()’:
../src/server.cpp:248:29: error: invalid conversion from ‘int (*)(void*,
MHD_Connection*, const char*, const char*, const char*, const char*, size_t*,
void**)’ {aka ‘int (*)(void*, MHD_Connection*, const char*, const char*, const
char*, const char*, long unsigned int*, void**)’} to
‘MHD_AccessHandlerCallback’ {aka ‘MHD_Result (*)(void*, MHD_Connection*, const
char*, const char*, const char*, const char*, long unsigned int*, void**)’}
[-fpermissive]
248 | ,
| ^~
| |
| int (*)(void*, MHD_Connection*, const
char*, const char*, const char*, const char*, size_t*, void**) {aka int
(*)(void*, MHD_Connection*, const char*, const char*, const char*, const char*,
long unsigned int*, void**)}
In file included from ../src/server.cpp:39:
/usr/include/microhttpd.h:2428:45: note: initializing argument 5 of
‘MHD_Daemon* MHD_start_daemon(unsigned int, uint16_t, MHD_AcceptPolicyCallback,
void*, MHD_AccessHandlerCallback, void*, ...)’
2428 | MHD_AccessHandlerCallback dh, void *dh_cls,
| ~~^~
Upstream libkiwix ticket discussing the issue is
https://github.com/kiwix/kiwix-lib/issues/373, but I (and upstream) believe
this is an unexexpected breaking change in libmicrohttpd.
-- Kunal
Bug#964405: marked as done (lintian: autopkgtest regression: No tests were selected by your filter:)
Your message dated Tue, 07 Jul 2020 23:33:39 + with message-id and subject line Bug#964405: fixed in lintian 2.83.0 has caused the Debian Bug report #964405, regarding lintian: autopkgtest regression: No tests were selected by your filter: 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.) -- 964405: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964405 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: lintian Version: 2.82.0 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of lintian the autopkgtest of lintian fails in testing when that autopkgtest is run with the binary packages of lintian from unstable. It passes when run with only packages from testing. In tabular form: passfail lintianfrom testing2.82.0 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration to testing [1]. Can you please investigate the situation and fix it? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=lintian https://ci.debian.net/data/autopkgtest/testing/amd64/l/lintian/6153561/log.gz Running selected and required Perl test scripts. Files=0, Tests=0, 0 wallclock secs ( 0.26 usr + 0.07 sys = 0.33 CPU) Result: NOTESTS No tests were selected by your filter: suite:tags To select your tests, please use an appropriate argument with a selector like: 'suite:', 'test:', 'check:', 'tag:', or 'script:' You can also use 'minimal:', which runs only the tests that cannot be turned off, such as the internal tests for the harness. signature.asc Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: lintian Source-Version: 2.83.0 Done: Chris Lamb We believe that the bug you reported is fixed in the latest version of lintian, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb (supplier of updated lintian package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 07 Jul 2020 22:50:19 + Source: lintian Architecture: source Version: 2.83.0 Distribution: unstable Urgency: medium Maintainer: Debian Lintian Maintainers Changed-By: Chris Lamb Closes: 963765 964013 964073 964281 964282 964405 Changes: lintian (2.83.0) unstable; urgency=medium . [ Felix Lechner ] * Add a new standalone HTML output mode. * Warn about embedded javascript files provided by sphinx. (Closes: #964013) * Exempt links that stay inside /usr/lib from breakout-link. (Closes: #964073) * Rename second mention of tag manpage-in-wrong-directory. (Closes: #964282) * Extend spell check to all parts of debhelper rule targets. (Closes: #963765) * Only check the DEP-3 header for legacy encodings in debian/patches. (Closes: #964281) * Restrict top folder for breakout-link to architecture in /usr/lib and permit links freely within. (Closes: #964073) * Use the new path to test recipes in autopkgtest. (Closes: #964405) * Drop a test no longer building due to new restraints on version strings. (See: #953554) * Exempt Lintian's own test suite from scans in source files and remove programmatic conditionals in checks. * Replace references to 'manpages' with 'manual pages' in tag descriptions. . [ Chris Lamb ] * Correct a reference to "override_dh_" in the long description of the excessive-debhelper-overrides tag. . [ Lev Lamberov ] * Update Debian Emacsen team wiki page link. . [ Paul Wise ] * Add several spelling corrections. Checksums-Sha1: b0dcca981409c063d8de028f637041cfdb710c61 4359 lintian_2.83.0.dsc b39e4b9784355b48656984e289e9ab7399b13653 1968696 lintian_2.83.0.tar.xz 219f8b7c6641377c0b384c9cdcb5d7c88b8be548 18309
Bug#963424: marked as done (sensible-utils: FTBFS: po4a::po: Invalid value for option 'porefs' ('noline,wrap' is not one of 'full', 'counter', 'noline', 'file' or 'never'))
Your message dated Tue, 07 Jul 2020 23:33:51 +
with message-id
and subject line Bug#963424: fixed in sensible-utils 0.0.13
has caused the Debian Bug report #963424,
regarding sensible-utils: FTBFS: po4a::po: Invalid value for option 'porefs'
('noline,wrap' is not one of 'full', 'counter', 'noline', 'file' or 'never')
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.)
--
963424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sensible-utils
Version: 0.0.12+nmu1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200620 ftbfs-bullseye
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>/man'
> Makefile:541: warning: ignoring prerequisites on suffix rule definition
> Makefile:543: warning: ignoring prerequisites on suffix rule definition
> Makefile:545: warning: ignoring prerequisites on suffix rule definition
> sed -f ./utf8toman.sed -e 's/%PACKAGE%/sensible-utils/g' -e
> 's/%VERSION%/0.0.11/g' -e 's/%RELEASE_DATE%//g' -e 's:%CONFDIR%:/etc:g' -e
> 's:%LOGDIR%::g' -e 's:%ADMINDIR%::g' -e
> 's:%PKGDOCDIR%:/usr/share/doc/sensible-utils:g' -e 's:%PKGCONFDIR%::g' -e
> 's:%PKGLIBDIR%:/usr/lib/x86_64-linux-gnu/sensible-utils:g' -e
> 's:%PKGDATADIR%:/usr/share/sensible-utils:g' sensible-editor.man
> >sensible-editor.1
> sed -f ./utf8toman.sed -e 's/%PACKAGE%/sensible-utils/g' -e
> 's/%VERSION%/0.0.11/g' -e 's/%RELEASE_DATE%//g' -e 's:%CONFDIR%:/etc:g' -e
> 's:%LOGDIR%::g' -e 's:%ADMINDIR%::g' -e
> 's:%PKGDOCDIR%:/usr/share/doc/sensible-utils:g' -e 's:%PKGCONFDIR%::g' -e
> 's:%PKGLIBDIR%:/usr/lib/x86_64-linux-gnu/sensible-utils:g' -e
> 's:%PKGDATADIR%:/usr/share/sensible-utils:g' sensible-browser.man
> >sensible-browser.1
> sed -f ./utf8toman.sed -e 's/%PACKAGE%/sensible-utils/g' -e
> 's/%VERSION%/0.0.11/g' -e 's/%RELEASE_DATE%//g' -e 's:%CONFDIR%:/etc:g' -e
> 's:%LOGDIR%::g' -e 's:%ADMINDIR%::g' -e
> 's:%PKGDOCDIR%:/usr/share/doc/sensible-utils:g' -e 's:%PKGCONFDIR%::g' -e
> 's:%PKGLIBDIR%:/usr/lib/x86_64-linux-gnu/sensible-utils:g' -e
> 's:%PKGDATADIR%:/usr/share/sensible-utils:g' sensible-pager.man
> >sensible-pager.1
> sed -f ./utf8toman.sed -e 's/%PACKAGE%/sensible-utils/g' -e
> 's/%VERSION%/0.0.11/g' -e 's/%RELEASE_DATE%//g' -e 's:%CONFDIR%:/etc:g' -e
> 's:%LOGDIR%::g' -e 's:%ADMINDIR%::g' -e
> 's:%PKGDOCDIR%:/usr/share/doc/sensible-utils:g' -e 's:%PKGCONFDIR%::g' -e
> 's:%PKGLIBDIR%:/usr/lib/x86_64-linux-gnu/sensible-utils:g' -e
> 's:%PKGDATADIR%:/usr/share/sensible-utils:g' select-editor.man
> >select-editor.1
> po4a --previous --srcdir . --destdir . --no-backups --porefs noline,wrap
> --msgmerge-opt=--add-location=file --package-name sensible-utils
> ./po4a/po4a.cfg
> po4a::po: Invalid value for option 'porefs' ('noline,wrap' is not one of
> 'full', 'counter', 'noline', 'file' or 'never')
> make[2]: *** [Makefile:536: man.stamp] Error 2
The full build log is available from:
http://qa-logs.debian.net/2020/06/20/sensible-utils_0.0.12+nmu1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: sensible-utils
Source-Version: 0.0.13
Done: Anibal Monsalve Salazar
We believe that the bug you reported is fixed in the latest version of
sensible-utils, 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 963...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Anibal Monsalve Salazar (supplier of updated sensible-utils
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Tue, 07 Jul 2020 18:00:29 -0500
Source: sensible-utils
Binary: sensible-utils
Architecture: source all
Version: 0.0.13
Distribution: experimental
Urgency:
Bug#964445: marked as done (libbluray: binary-all FTBFS)
Your message dated Tue, 07 Jul 2020 22:48:33 + with message-id and subject line Bug#964445: fixed in libbluray 1:1.2.0-3 has caused the Debian Bug report #964445, regarding libbluray: binary-all FTBFS 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.) -- 964445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964445 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbluray Version: 1:1.2.0-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=libbluray=all=1%3A1.2.0-2=1594068597=0 ... fakeroot debian/rules binary-indep dh binary-indep --with javahelper dh_testroot -i dh_prep -i dh_install -i dh_install: warning: Cannot find (any matches for) "usr/share/java" (tried in ., debian/tmp) dh_install: warning: libbluray-bdj missing files: usr/share/java dh_install: error: missing files, aborting make: *** [debian/rules:23: binary-indep] Error 25 --- End Message --- --- Begin Message --- Source: libbluray Source-Version: 1:1.2.0-3 Done: Sebastian Ramacher We believe that the bug you reported is fixed in the latest version of libbluray, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastian Ramacher (supplier of updated libbluray 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, 08 Jul 2020 00:24:27 +0200 Source: libbluray Architecture: source Version: 1:1.2.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers Changed-By: Sebastian Ramacher Closes: 964445 Changes: libbluray (1:1.2.0-3) unstable; urgency=medium . * debian/: Fix Arch: all build (Closes: #964445) Checksums-Sha1: 19a5d17ac3f89b56ef4e26e4cda0b3b25ef60fe3 2420 libbluray_1.2.0-3.dsc f3b28c22e8b2e3a456038e8b6538501b251d3696 16948 libbluray_1.2.0-3.debian.tar.xz Checksums-Sha256: 947b62434169bd179f9110b57813efeb70376cb0dd33822655222efaaa8fb692 2420 libbluray_1.2.0-3.dsc 179cdf3ccb6041f8473c1200cec4bb16d345e1bce50a8d52072551c674affe95 16948 libbluray_1.2.0-3.debian.tar.xz Files: 3c767869fb547c49bfd002708cf1d926 2420 libs optional libbluray_1.2.0-3.dsc 75b5285527df2e7c69ec5e7fca7cce95 16948 libs optional libbluray_1.2.0-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl8E990ACgkQafL8UW6n GZMdxBAAsIZvtXC8WmNi8CzlcIFxLjtk171P+XReQ2vTg5FwCz/OTHY753QsMgH4 N3Wu2BYXmZTOiWTcKZhmT1GnbJB+M8g5G2wd81p530atJcjByJ2zc6IqMC88vtaY OBRq1+ykUDevtbqqD+XuQ0eTIu24Fcz88mUppuPOBvcH/jh1z3eAiPtYfG4dpTfH L8x+FgHbrRIlt5DpkuIeOB5lqNoYxBYRHp31cczvf2373NqQ+8dH9nfB+KQNctOE ZLVRBjXvlMwWncpXhMHLK1G3nomkVihN3eVetTgY37iZfCGDmkUSFxgbGg+NCJBr vBIgepnypvUZok9B7+WvrgC+psBRw3qwfLGEkfJSExUiDd4vJlKeS548/UGwU0X6 2NMy/qamL3bmqUXU5/dSxFgaxSaQLvjm0scEkoBiLnYK0zH4RC7EM8b5VMdWDeiN s2jRWMr+j88pqUlTpCfy9S08PsoU2SpNEZZXXhfJR+Vd0r4b+ejCbB0zQ3JbgNVB x67hMC/SkLVpLLPiuX7EG34X7ZnvcOJasc9W9ymhK1jWlq21XhWZEgOHedNA1qNk 4sgFPBcmJEvU2ONyzRAbVJK2HFWm0HWl3vr+qFVSPO6rnR6h9xNS7P+cvobsueEq VHAn8QqCLZFefSLDA6wUWwbeDUcSzD5BTZ+vI4VouVSIwCKwxMk= =IZPT -END PGP SIGNATURE End Message ---
Bug#963713: [Pkg-net-snmp-devel] Bug#963713: net-snmp: CVE-2019-20892
On Wed, 8 Jul 2020 at 01:48, Sylvain Beucler wrote: > On 07/07/2020 17:07, Sylvain Beucler wrote: > > In any case, all of this happens between 5.7.3 and 5.8.pre1. > > Restricting further (good..bad): > > $ git shortlog > > 1a0dbe19bf2787bb5bea913f210a9a5eb4c0c80c..e207b8113260fd7d84df0ebdb66925ab70da29b2 > Robert Story (2): > Add VMware copyright > tweak sndMsgMaxSize handling > > VMwareDev Randy (4): > getbulk enhancements: limit responses gathered > reduce session msg max sizes to transport max > getbulk enhancements: response size + fallback to forward encoding > move v3 engineID probe into initial packet build > Thanks for doing this bisect. So the issue happened after 5.7.3 (this change happened in 2015, 5.7.3 was released in 2014) which means we only need to worry about unstable and testing. - Craig
Bug#964399: Should ganglia be removed?
Hello Moritz I did some work time ago on ganglia [1] but i never get this work published due to unactive/unresponsive uploaders. I also done some work on ganglia-web and ganglia-linux-modules packages (also unpublished). I believe that it is still a good piece of software that deserve its place on Debian so i would like to step up as uploader (co-uploaders welcome!) if needed. I also would like to maintain it under pkg-security team umbrella. Please, let me know your thoughs. Greetings, Marcos [1] https://salsa.debian.org/mfouces-guest/ganglia El lun, 06-07-2020 a las 20:12 +0200, Moritz Muehlenhoff escribió: > Source: ganglia > Severity: serious > > Should ganglia be removed? It's dead upstream (last commits from over > three years ago, > last release from 2015), is now orphaned (last active maintainer is > no longer a DD, but > wasn't very actively maintained to begin with, the current packaged > version is from 2013), > most of the plugins depend on Python 2, there's unfixed security > issues dating back to > 2013 and doesn't even support ipv6 (730257). > > Unless anyone steps up for maintenance (and partly becomes upstream), > it should better > be removed. > > Cheers, > Moritz >
Bug#964471: libreoffice-l10n-ru: error when configuring: cp: cannot create regular file '/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory
On 07.07.2020 22:40, Rene Engelhard wrote: Even that worked for me in said testing VM "upgraded" to unstable with your apt-get --with-new-pkgs upgrade. libreoffice-l10n-de, libreoffice-l10n-ru and other LO packages were kept back. After some testing, I found out that you also need to pass `--no-install-recommends`, as otherwise `Recommends: libreoffice-core (>> 1:7.0.0~rc1)` in libreoffice-l10n-ru prevents it from upgrading. Anyway, upgrading any subset of packages, if permitted by dependencies, should not produce any errors. To test that this is indeed the case, I suggest running `apt-get --no-install-recommends install $pkg` in a test environment for every package to test the upgrade of that package in isolation (so that only the package and the packages that are strictly required to satisfy dependencies are upgraded).
Bug#959599: frama-c: FTBFS fixed upstream
On Sat, 06 Jun 2020 09:47:57 -0400 John Scott wrote: > Control: forwarded -1 https://lists.gforge.inria.fr/pipermail/frama-c-discuss/2020-June/005823.html > Control: tags -1 fixed-upstream > > I'm having trouble finding their VCS and what commit fixed this, but updating > Frama-C to the beta should be sufficient. Unstable and testing already have > Why3 >= 1.3. For information, the Frama-C public VCS (git) is available at: https://git.frama-c.com/pub/frama-c/-/tree/master There is no specific commit which updated compatibility from Why3 1.2 to Why3 1.3 (there is an entire branch with several commits related to it), but https://git.frama-c.com/pub/frama-c/-/commit/1c7acc37c44f914f60a27 would be close. In any case, thanks for looking into this, and please tell us if there's anything we can do to help fix the frama-c package on Debian testing. -- André Maroneze, for the Frama-C team
Processed: affects 964309, affects 964309
Processing commands for cont...@bugs.debian.org: > affects 964309 - src:javahelper Bug #964309 [bsdmainutils] bsdmainutils: FTBFS because of missing libncurses-dev dependency Removed indication that 964309 affects src:javahelper > affects 964309 + javahelper Bug #964309 [bsdmainutils] bsdmainutils: FTBFS because of missing libncurses-dev dependency Added indication that 964309 affects javahelper > thanks Stopping processing here. Please contact me if you need assistance. -- 964309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 964245 is forwarded to https://github.com/beetbox/beets/pull/3621
Processing commands for cont...@bugs.debian.org: > forwarded 964245 https://github.com/beetbox/beets/pull/3621 Bug #964245 [beets] beets: Crashes on launch after upgrading to python 3.8.4~rc1-1 Set Bug forwarded-to-address to 'https://github.com/beetbox/beets/pull/3621'. > thanks Stopping processing here. Please contact me if you need assistance. -- 964245: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964245 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964475: dpkg breaks apt autopkgtest: dpkg: error: unknown option --foreign-architecture
Control: tags -1 + pending Hi, On Tue, Jul 07, 2020 at 08:47:21PM +0200, Paul Gevers wrote: > Currently this regression is blocking the migration of dpkg to testing > [1]. Due to the nature of this issue, I filed this bug report against > both packages. Can you please investigate the situation and reassign the > bug to the right package? We (apt & dpkg maintainers) talked about this on IRC already and I pushed a workaround (of sorts) to apt.git [0] for this. The underlying problem is that the hookscript pkg-config installs does not support DPKG_ROOT while the newer version of dpkg does support it (more) now reporting architectures from the DPKG_ROOT rather than the host system it previously did (arguably incorrectly). Based on that pkg-config-dpkghook attempts to create (or remove) symlinks in /usr/bin for architectures added/removed in dpkgroot which it isn't allowed to (as it isn't run as root) and fails. APTs testcases detect these failures in "dpkg --add-architecture" and assumes it is working with a previous version of a dpkg Multi-Arch implementation used e.g. in older Ubuntus resulting in the tests eventually using commandline options unknown to the dpkg version it is really using here. The workaround detects these failures and ignores them now – as the hookscript is post-invoke the architecture is added, so we got what we were asking for – but ideally #824774 in pkg-config would be resolved. (Ignoring that dpkg should also probably not read /etc/dpkg.cfg.d files from the root system, but that might be an even longer endeavour) Best regards David Kalnischkies [0] https://salsa.debian.org/apt-team/apt/-/commit/3fe1419433f195d57b948b100b218cf14a2841d0 signature.asc Description: PGP signature
Processed: Re: Bug#964475: dpkg breaks apt autopkgtest: dpkg: error: unknown option --foreign-architecture
Processing control commands: > tags -1 + pending Bug #964475 [src:dpkg, src:apt] dpkg breaks apt autopkgtest: dpkg: error: unknown option --foreign-architecture Added tag(s) pending. -- 964475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964475 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963933: marked as done (glib2.0: autopkgtext: ld: cannot find -lcryptsetup)
Your message dated Tue, 07 Jul 2020 19:48:54 + with message-id and subject line Bug#963933: fixed in glib2.0 2.64.4-1 has caused the Debian Bug report #963933, regarding glib2.0: autopkgtext: ld: cannot find -lcryptsetup 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.) -- 963933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: glib2.0 Severity: serious Version: 2.64.3-1 Dear glib2.0 Maintainers, the autopkgtest suite offers quite interesting behaviour: With an installed libcryptsetup-dev, ld fails with "cannot find -lcryptsetup". Log: https://ci.debian.net/data/autopkgtest/testing/amd64/g/glib2.0/6071882/log.gz autopkgtest [00:19:30]: test build: preparing testbed .. Selecting previously unselected package libcryptsetup-dev:amd64. Preparing to unpack .../19-libcryptsetup-dev_2%3a2.3.3-1_amd64.deb ... Unpacking libcryptsetup-dev:amd64 (2:2.3.3-1) ... .. autopkgtest [00:19:45]: test build: ---] autopkgtest [00:19:45]: test build: - - - - - - - - - - results - - - - - - - - - - buildPASS (superficial) autopkgtest [00:19:45]: test build-static: preparing testbed .. + gcc -static -o gio-static gio.c -pthread -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -lgio-2.0 -ldl -pthread -lresolv -lgmodule-2.0 -pthread -ldl -lz -lmount -lblkid -lcryptsetup -lselinux -lsepol -lpcre2-8 -pthread -lgobject-2.0 -pthread -lffi -lglib-2.0 -pthread -lpcre -pthread /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/9/../../../x86_64-linux-gnu/libgmodule-2.0.a(gmodule.c.o): in function `g_module_open': (.text+0x703): warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking /usr/bin/ld: cannot find -lcryptsetup I imagine this might be caused by libcryptsetup-dev not shipping an .a library. This prevents libmount1/util-linux to transition. Please investigate and hopefully fix the problem at hand. Thanks, Chris --- End Message --- --- Begin Message --- Source: glib2.0 Source-Version: 2.64.4-1 Done: Simon McVittie We believe that the bug you reported is fixed in the latest version of glib2.0, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated glib2.0 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 07 Jul 2020 13:33:01 +0100 Source: glib2.0 Architecture: source Version: 2.64.4-1 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Simon McVittie Closes: 963933 Changes: glib2.0 (2.64.4-1) unstable; urgency=medium . * Team upload * New upstream release - Improve async-signal-safety * d/tests/build: Don't exercise static linking for GIO. libmount will no longer support being linked statically from 2.35.2-8 onwards. For now I'm continuing to test that the other libraries can still be statically linked, but please consider them to be "at risk". (Closes: #963933) * Re-enable libmount support. libmount no longer depends on libcryptsetup, avoiding the various crashes that we are working around. Future versions will dlopen it on-demand, which should also avoid those crashes. Bump the build-dependency to a suitable version. * d/p/tests-Use-g_assert_-in-cancellable-test-rather-than-g_ass.patch, d/p/gcancellable-Fix-minor-race-between-GCancellable-and-GCan.patch: Split combined d/p/git_gsource_segfault.patch into its two component upstream commits, and add metadata * d/p/glib-compile-resources-Fix-exporting-on-Visual-Studio.patch, d/p/gdesktopappinfo-Fix-unnecessarily-copied-and-leaked-URI-l.patch: Add post-release bugfixes from upstream Checksums-Sha1: fba1e1908ad38eed84e4a5a50034fdd57bec7203 3328 glib2.0_2.64.4-1.dsc 581ac4b4b4453eb2e696adb8a9417b65117f796f 4779456 glib2.0_2.64.4.orig.tar.xz 4a701b94c445ce264b019018ec000eb195bf77eb 93700
Bug#964471: libreoffice-l10n-ru: error when configuring: cp: cannot create regular file '/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory
On Tue, Jul 07, 2020 at 09:30:23PM +0200, Rene Engelhard wrote: > Am 07.07.20 um 21:21 schrieb Evgeny Kapun: > >> but how did you get into this situation? > > > > I've run `apt-get --with-new-pkgs upgrade`. This upgraded some > > libreoffice packages including libreoffice-l10n-ru, but not > > libreoffice-common because this would require it to remove > > libreoffice-style-tango. > > Aha. Will try. Even that worked for me in said testing VM "upgraded" to unstable with your apt-get --with-new-pkgs upgrade. libreoffice-l10n-de, libreoffice-l10n-ru and other LO packages were kept back. Regards, Rene
Bug#964471: marked as done (libreoffice-l10n-ru: error when configuring: cp: cannot create regular file '/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory)
Your message dated Tue, 07 Jul 2020 19:34:56 + with message-id and subject line Bug#964471: fixed in libreoffice 1:7.0.0~rc1-4 has caused the Debian Bug report #964471, regarding libreoffice-l10n-ru: error when configuring: cp: cannot create regular file '/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 964471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libreoffice-l10n-ru Version: 1:7.0.0~rc1-3 Severity: serious When upgrading Libreoffice, the following errors occur: Setting up libreoffice-l10n-ru (1:7.0.0~rc1-3) ... Creating config file /etc/libreoffice/registry/Langpack-ru.xcd with new version cp: cannot create regular file '/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory dpkg: error processing package libreoffice-l10n-ru (--configure): installed libreoffice-l10n-ru package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of libreoffice-help-ru: libreoffice-help-ru depends on libreoffice-l10n-ru; however: Package libreoffice-l10n-ru is not configured yet. dpkg: error processing package libreoffice-help-ru (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: libreoffice-l10n-ru libreoffice-help-ru This is apparently caused by /etc/libreoffice/registry not existing. --- End Message --- --- Begin Message --- Source: libreoffice Source-Version: 1:7.0.0~rc1-4 Done: Rene Engelhard We believe that the bug you reported is fixed in the latest version of libreoffice, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rene Engelhard (supplier of updated libreoffice 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: Tue, 07 Jul 2020 21:00:43 +0200 Source: libreoffice Architecture: source Version: 1:7.0.0~rc1-4 Distribution: unstable Urgency: medium Maintainer: Debian LibreOffice Maintainers Changed-By: Rene Engelhard Closes: 964471 Changes: libreoffice (1:7.0.0~rc1-4) unstable; urgency=medium . * debian/patches/disable-shortcuts_tab_navigation-uitest.diff: as name says, hangs in autopkgtest (or chroot), works in the build... . * debian/rules: - use --with-extra-buildid instead of --with-build-version * debian/control*.in: - make all packages having (moved) config files depend on libreoffice-common (>= 1:7.0.0~alpha~) (closes: #964471) Checksums-Sha1: 815d24c6a52b6556aeb4295bc90ccc51097b0520 30924 libreoffice_7.0.0~rc1-4.dsc c765212eba0bab6c873f691727590a8fab2dae8a 19409056 libreoffice_7.0.0~rc1-4.debian.tar.xz d101a4aead252e467236e81666c6735ce780a20e 36035 libreoffice_7.0.0~rc1-4_source.buildinfo Checksums-Sha256: 0a0dfbaafee553b342fb7246c7ee8165e2f8a8d9fbcf50a8f96923676aa78cdb 30924 libreoffice_7.0.0~rc1-4.dsc b645c904cbe6c4fb128e27cba5f1203023ae2bc577f8402d0ef3b66a0d5e915b 19409056 libreoffice_7.0.0~rc1-4.debian.tar.xz 4f0d4b9012699cd4c374cd3528c85eb991b37e90da1f99039694a88733abf888 36035 libreoffice_7.0.0~rc1-4_source.buildinfo Files: c06c3a3b7ebbca3eb8d61a7dc4c38d73 30924 editors optional libreoffice_7.0.0~rc1-4.dsc 1c4b87fcabb4eb4c207118c261dd2267 19409056 editors optional libreoffice_7.0.0~rc1-4.debian.tar.xz adddc226434b70d4f62ca36f0532c2fc 36035 editors optional libreoffice_7.0.0~rc1-4_source.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEE4S3qRnUGcM+pYIAdCqBFcdA+PnAFAl8EyH0QHHJlbmVAZGVi aWFuLm9yZwAKCRAKoEVx0D4+cMdREADiOIpLIqzsXRXobv0cL+1300kipF5rKO7h TC4dUG/VfzfZ8faSb6LuapFbS7wJfzG44hW8jWRKr8ypN6nifbiE5I59YEhzj4pY Efx103t5D5Vmu7USzyeOfY6KjZTME3GsdCUbRTnnZbOkpFU95GDCN5MvGQGncck2 DZevzLN9HEeWnXHySopTNeXynup97MHyY5BFushYTccIRFtOEuDqlybm14f68l5b jAemHnElr6M7c6ikZVNSV3+RmLmv9/qDf6iZL3XgvYPFOnloee2EbSbeWgbFk93Y tkVOj+DIqqxfm6f3TB+4KqYCNjYC9M527fwFA/HMOQ55ZPrRQuzTHaRXvZhxkWz4 i/8O8bk1adgUnjpAVo0I2hUsoXptIJsdUSZq7PPVx1fr/cswOE4Gl0Dxf+1k62ey
Bug#964471: libreoffice-l10n-ru: error when configuring: cp: cannot create regular file '/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory
Hi, Am 07.07.20 um 21:21 schrieb Evgeny Kapun: >> but how did you get into this situation? > > I've run `apt-get --with-new-pkgs upgrade`. This upgraded some > libreoffice packages including libreoffice-l10n-ru, but not > libreoffice-common because this would require it to remove > libreoffice-style-tango. Aha. Will try. And libreoffice-style-tango is required to be removed for a reason: It simply is gone upstream :-) > In the future, it seems wise to test plain `upgrade` and > `--with-new-pkgs upgrade` in addition to dist-upgrade. Maybe. But here you DO want dist-upgrade. You are not supposed to keep libreoffice-style-tango and the dependencies enforce that. Regards, Rene
Processed: Re: Bug#964471: libreoffice-l10n-ru: error when configuring: cp: cannot create regular file '/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory
Processing commands for cont...@bugs.debian.org: > tag 964471 + moreinfo Bug #964471 [libreoffice-l10n-ru] libreoffice-l10n-ru: error when configuring: cp: cannot create regular file '/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory Added tag(s) moreinfo. > tag 964471 + unreproducible Bug #964471 [libreoffice-l10n-ru] libreoffice-l10n-ru: error when configuring: cp: cannot create regular file '/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory Added tag(s) unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. -- 964471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964471: libreoffice-l10n-ru: error when configuring: cp: cannot create regular file '/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory
tag 964471 + moreinfo tag 964471 + unreproducible thanks Hi, On Tue, Jul 07, 2020 at 08:59:26PM +0200, Rene Engelhard wrote: > On Tue, Jul 07, 2020 at 08:40:54PM +0200, Rene Engelhard wrote: > > Any upgrade I tried (and yes, also with -l10n-de/-help-de installed) > > upgtaded libreoffice-common before the l10ns (and thus > > /etc/libreoffice/registry > > iwas there at .postinst time) > > And a clean testing VM dist-upgraded to unstable just now also worked. (with -help-ru installed.) > But anyways, as you should have already seen - added the same dependency in > git to > anything having anything in /etc/libreoffice/registry. > > Should fix it. Also for (which I think you did, why can't people just do proper upgrades, you "helpfully" didn't add your distro info added by reportbug in your report) "let's install the unstable package on testing" scenarios. Regards, Rene
Bug#964471: libreoffice-l10n-ru: error when configuring: cp: cannot create regular file '/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory
On Tue, Jul 07, 2020 at 08:40:54PM +0200, Rene Engelhard wrote: > Any upgrade I tried (and yes, also with -l10n-de/-help-de installed) > upgtaded libreoffice-common before the l10ns (and thus > /etc/libreoffice/registry > iwas there at .postinst time) And a clean testing VM dist-upgraded to unstable just now also worked. But anyways, as you should have already seen - added the same dependency in git to anything having anything in /etc/libreoffice/registry. Should fix it. Regards, Rene
Bug#964471: marked as pending in libreoffice
Control: tag -1 pending Hello, Bug #964471 in libreoffice reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/-/commit/7f92eacb5b48fab8f6a8f7a6e184d8850282eda2 make all packages having (moved) config files depend on libreoffice-common (>= 1:7.0.0~alpha~) (closes: #964471) (this message was generated automatically) -- Greetings https://bugs.debian.org/964471
Processed: Bug#964471 marked as pending in libreoffice
Processing control commands: > tag -1 pending Bug #964471 [libreoffice-l10n-ru] libreoffice-l10n-ru: error when configuring: cp: cannot create regular file '/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory Added tag(s) pending. -- 964471: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964471 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964366: [aristocratos/bashtop] [BUG] insecure use of /tmp (#161)
* Dylan Aïssi , 2020-07-06, 15:13:
pytmpdir=$(mktemp -d "${TMPDIR:-/tmp}"/)
pywrapper=$(mktemp "${pytmpdir}"/bashtop.psutil.)
Should fix the issue.
Does the proposed fix by upstream look good to you?
It's mostly OK, but:
- mktemp(1) can fail, and this failure should not be ignored;
- there's no need for two mktemp calls.
Something like this should work:
pytmpdir=$(mktemp -d "${TMPDIR:-/tmp}"/bashtop.XX) || exit 1
pywrapper=${pytmpdir}/psutil
--
Jakub Wilk
Bug#964471: libreoffice-l10n-ru: error when configuring: cp: cannot create regular file '/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory
Hi, On Tue, Jul 07, 2020 at 09:13:58PM +0300, Evgeny Kapun wrote: > When upgrading Libreoffice, the following errors occur: > > > Setting up libreoffice-l10n-ru (1:7.0.0~rc1-3) ... > > Creating config file /etc/libreoffice/registry/Langpack-ru.xcd with new > version > cp: cannot create regular file '/etc/libreoffice/registry/Langpack-ru.xcd': > No such file or directory > dpkg: error processing package libreoffice-l10n-ru (--configure): > installed libreoffice-l10n-ru package post-installation script subprocess > returned error exit status 1 > dpkg: dependency problems prevent configuration of libreoffice-help-ru: > libreoffice-help-ru depends on libreoffice-l10n-ru; however: > Package libreoffice-l10n-ru is not configured yet. > > dpkg: error processing package libreoffice-help-ru (--configure): > dependency problems - leaving unconfigured > Errors were encountered while processing: > libreoffice-l10n-ru > libreoffice-help-ru > > > This is apparently caused by /etc/libreoffice/registry not existing. Interesting. I had that error once for other packages: libreoffice (1:7.0.0~alpha1-2) experimental; urgency=medium libreoffice (1:7.0.0~alpha1-2) experimental; urgency=medium * debian/patches/libreoffice.jar-pom.diff: add pom for new libreoffice.jar * debian/patches/bigendian-ustrbuf-hxx.diff: add missing include on bigendian architectures * debian/patches/skia-SkOpts_crc32.diff: add missing SkOpts_crc32 to fix skia build on arm * debian/control*in: - make -librelogo, -sdbc-postgresql and -report-builder explicitly depend on libreoffice-common (>= 1:7.0.0~alpha~) as otherwise /etc/libreoffice/registry might not exist yet [...] but how did you get into this situation? Any upgrade I tried (and yes, also with -l10n-de/-help-de installed) upgtaded libreoffice-common before the l10ns (and thus /etc/libreoffice/registry iwas there at .postinst time) Regards, Rene
Processed: dpkg breaks apt autopkgtest: dpkg: error: unknown option --foreign-architecture
Processing control commands: > found -1 dpkg/1.20.4 Bug #964475 [src:dpkg, src:apt] dpkg breaks apt autopkgtest: dpkg: error: unknown option --foreign-architecture Marked as found in versions dpkg/1.20.4. > found -1 apt/2.1.6 Bug #964475 [src:dpkg, src:apt] dpkg breaks apt autopkgtest: dpkg: error: unknown option --foreign-architecture Marked as found in versions apt/2.1.6. -- 964475: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964475 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964475: dpkg breaks apt autopkgtest: dpkg: error: unknown option --foreign-architecture
Source: dpkg, apt Control: found -1 dpkg/1.20.4 Control: found -1 apt/2.1.6 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of dpkg the autopkgtest of apt fails in testing when that autopkgtest is run with the binary packages of dpkg from unstable. It passes when run with only packages from testing. In tabular form: passfail dpkg from testing1.20.4 aptfrom testing2.1.6 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of dpkg to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=dpkg https://ci.debian.net/data/autopkgtest/testing/amd64/a/apt/6176292/log.gz Test for successful execution of aptmark hold bar … dpkg: error: unknown option --foreign-architecture Type dpkg --help for help about installing and deinstalling packages [*]; Use 'apt' or 'aptitude' for user-friendly package management; Type dpkg -Dhelp for a list of dpkg debug flag values; Type dpkg --force-help for a list of forcing options; Type dpkg-deb --help for help about manipulating *.deb files; Options marked [*] produce a lot of output - pipe it through 'less' or 'more' ! E: Sub-process dpkg --set-selections returned an error code (2) E: Executing dpkg failed. Are you root? FAIL: exitcode 100 P Part of the test group: Test for successful execution of aptmark showholds bar … Test for correctness of file /tmp/tmp.nOcxNldGYL/rootdir/tmp/testsuccess.output … +bar === content of file we compared with (/tmp/tmp.nOcxNldGYL/rootdir/tmp/testsuccess.output) === FAIL T signature.asc Description: OpenPGP digital signature
Bug#959579: adapta-gtk-theme: FTBFS: make[2]: *** [Makefile:1040: all] Error 1
Dear Sidup, Thanks for the patch, it is of great value. The upstream of this package has archived the project and is currently not in development. However, after testing your patch, I think it is feasible to continue maintaining this package in Debian. Soon we will upload it with your patch. Thanks again. Em seg, 6 de jul de 2020 08:09, Sudip Mukherjee escreveu: > On Mon, Jul 6, 2020 at 11:19 AM Samuel Henrique > wrote: > > > > Hello Sudip, > > > > Just a quick update, I spoke to Franciscarlos (he will reply back here > > soon) and he intends to keep the package, so your patch will be > > accepted, he just wants to confirm that the package is working fine > > with the latest version of gnome. > > thats great. > > > > > Meanwhile, can you push your changes to the git repo? > > Sure, I have raised a merge request after changing the release to > "UNRELEASED", so that you can accept it after Franciscarlos has tested > it. > Kept it UNRELEASED as I assumed you might want to update the > Standards-Version and debhelper also (which I should not do as part of > NMU). > > > -- > Regards > Sudip >
Bug#964471: libreoffice-l10n-ru: error when configuring: cp: cannot create regular file '/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory
Package: libreoffice-l10n-ru Version: 1:7.0.0~rc1-3 Severity: serious When upgrading Libreoffice, the following errors occur: Setting up libreoffice-l10n-ru (1:7.0.0~rc1-3) ... Creating config file /etc/libreoffice/registry/Langpack-ru.xcd with new version cp: cannot create regular file '/etc/libreoffice/registry/Langpack-ru.xcd': No such file or directory dpkg: error processing package libreoffice-l10n-ru (--configure): installed libreoffice-l10n-ru package post-installation script subprocess returned error exit status 1 dpkg: dependency problems prevent configuration of libreoffice-help-ru: libreoffice-help-ru depends on libreoffice-l10n-ru; however: Package libreoffice-l10n-ru is not configured yet. dpkg: error processing package libreoffice-help-ru (--configure): dependency problems - leaving unconfigured Errors were encountered while processing: libreoffice-l10n-ru libreoffice-help-ru This is apparently caused by /etc/libreoffice/registry not existing.
Bug#951271: marked as done (java-gnome: Please migration from enchant(1) to enchant-2)
Your message dated Tue, 07 Jul 2020 17:06:14 + with message-id and subject line Bug#951271: fixed in java-gnome 4.1.3-8.1 has caused the Debian Bug report #951271, regarding java-gnome: Please migration from enchant(1) to enchant-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.) -- 951271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: java-gnome Version: 4.1.3-8 Severity: important X-Debbugs-CC: onkarshi...@ubuntu.com respawne...@gmail.com m...@codepencil.com Control: block 947979 by -1 Dear Debian Java maintainers, As libenchant upstream has bumped its version and released enchant 2.x, the old enchant 1.x is no longer maintained. Please consider switching from using the old package "enchant" to the new "enchant-2". If you need a patch, I believe the one currently in Arch Linux AUR can be used as a reference: https://aur.archlinux.org/packages/java-gnome/ -- Thanks, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: java-gnome Source-Version: 4.1.3-8.1 Done: Paul Wise We believe that the bug you reported is fixed in the latest version of java-gnome, 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 951...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Wise (supplier of updated java-gnome 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, 08 Jul 2020 00:01:41 +0800 Source: java-gnome Architecture: source Version: 4.1.3-8.1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: Paul Wise Closes: 951271 Changes: java-gnome (4.1.3-8.1) unstable; urgency=medium . * Non-maintainer upload. * Migrate from enchant 1 to enchant-2 (Closes: #951271) Checksums-Sha1: f84ec49a09181d3c383870911d5438015a0e8a7f 2411 java-gnome_4.1.3-8.1.dsc d6735390228812e3eab3b496fdaa223ca699e2c4 9812 java-gnome_4.1.3-8.1.debian.tar.xz d62ffcb6c8392500546cbdeebc0f0e3c4a7363a3 17824 java-gnome_4.1.3-8.1_amd64.buildinfo Checksums-Sha256: d6ced3c75f10d58792b7cd5b94123321fbe28bc9250597870628608381d16126 2411 java-gnome_4.1.3-8.1.dsc 5c658908d90ba8c5b82d30a04b36d636f588d9adfd0c31e84ca1c0f0f252294f 9812 java-gnome_4.1.3-8.1.debian.tar.xz b75866c053f04d9a15381650ea712fed81b07008884e7e2dbe8f620b13716f1e 17824 java-gnome_4.1.3-8.1_amd64.buildinfo Files: 16822a1ac81026d7cb5bf374d111887b 2411 java optional java-gnome_4.1.3-8.1.dsc 7ad1bd1418ce658feeeb49a008531c68 9812 java optional java-gnome_4.1.3-8.1.debian.tar.xz 54463539fe6551078af70128250964f8 17824 java optional java-gnome_4.1.3-8.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEYQsotVz8/kXqG1Y7MRa6Xp/6aaMFAl8EqacACgkQMRa6Xp/6 aaN1yBAAiaj+KQZ2bxKYTq0TsCqqiZl4SaAQqhKZyvWC0QaVKrMLHgOYFNx6hHcY 1hY84TFMOT3RbnVc8S4eWduPiUy1UfHZ62fdDwVgNS3/YYIEWhwu9IyG0xuNL/o6 BJ2NvOD5YfQNF764KqG+dhda8Le1Axm4/4qAtRA7OTuRoXJsQLjdQfPiG9v3/H/a 1NGmFL0hfpxGBlzK+aiWN+JxZvac03GPyoAIAl161BzMA/dwnxZ+1EayhITiUG7T ajp8GV++cczcK1tX1tHiPFX8k2LB3L0SYxEoKtzaV4SSLB8Uj4MFtcahrgWwLBkn Nnj/J1r5cyTOC+Rs33VZnf+J95Zps5x7uE6psUnYReitUpJrmJtgLPqbkYr+q3f8 DCp6szQ1PW8dAEz3jtgqJSUC7cvNLC2X4zG67u79scZXyF6UyqgJvTVmWyvctPb5 o7vx48Z0+reEak7vQoncN/zN+ZPl1HRD/w4DYTSwlVLLo9estCELKelfAvb1KCGl yiDbJxM0fSKLKv1PmTs2uqj4odpEzyiiADpx2jsD/mciUZBnh9/2YKzk+eehCoVG N/tAPd1lqtqVj+oLCSvcCmWTWutPzg+AzvvHVbn2pJB5UZxMS2ev8udhMqfdt0Pg n4Gq8KXx/fPPmRaQkzeI+K2ElwPlugfsG4sNYrAsvoJ1xO8uaDY= =WEi5 -END PGP SIGNATURE End Message ---
Bug#964334: segfault repeatedly
Package: chromium Version: 83.0.4103.116-2 Followup-For: Bug #964334 Dear Maintainer, seeing the same issue in chromium 83.0.4103.116-2, keeps crashing after a few minutes of use. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964362 is a dup of this one, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963548 *may* be, but that one also mentions tab crashes (as opposed to browser crashes) In 83.0.4103.116-1~deb10u2 I get both tab crashes (consistently when opening google chat) and browser crashes. In 83.0.4103.116-2 I only get browser crashes... [30759:30759:0707/165049.768521:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process. [30720:30840:0707/165050.050567:ERROR:object_proxy.cc(632)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files [30720:30840:0707/165050.054057:ERROR:object_proxy.cc(632)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files [30720:30840:0707/165050.054430:ERROR:object_proxy.cc(632)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files libpng warning: iCCP: known incorrect sRGB profile Received signal 11 SEGV_MAPERR 7f01bc2be677 #0 0x563a76110c69 (/usr/lib/chromium/chromium+0x52b3c68) #1 0x563a7606fef3 (/usr/lib/chromium/chromium+0x5212ef2) #2 0x563a761107f1 (/usr/lib/chromium/chromium+0x52b37f0) #3 0x7f62e4052110 (/lib/x86_64-linux-gnu/libpthread-2.30.so+0x1410f) #4 0x7f62df13dd3c (/lib/x86_64-linux-gnu/libc-2.30.so+0x85d3b) #5 0x7f62df13ff33 (/lib/x86_64-linux-gnu/libc-2.30.so+0x87f32) #6 0x7f62df141bf9 __libc_malloc #7 0x563a761289be operator new() #8 0x7f62df3c8a2c std::__cxx11::basic_string<>::reserve() #9 0x7f62df3be498 std::__cxx11::basic_stringbuf<>::overflow() #10 0x7f62df3c704a std::basic_streambuf<>::xsputn() #11 0x7f62df3b9714 std::__ostream_insert<>() #12 0x563a76110d39 (/usr/lib/chromium/chromium+0x52b3d38) #13 0x563a76111054 (/usr/lib/chromium/chromium+0x52b4053) #14 0x563a76082412 (/usr/lib/chromium/chromium+0x5225411) #15 0x563a76084548 (/usr/lib/chromium/chromium+0x5227547) #16 0x563a747ca12a (/usr/lib/chromium/chromium+0x396d129) #17 0x563a747ca17e (/usr/lib/chromium/chromium+0x396d17d) #18 0x563a73e1f387 (/usr/lib/chromium/chromium+0x2fc2386) #19 0x563a747833d9 (/usr/lib/chromium/chromium+0x39263d8) #20 0x563a7478361e (/usr/lib/chromium/chromium+0x392661d) #21 0x563a747cd967 (/usr/lib/chromium/chromium+0x3970966) #22 0x563a747f94c7 (/usr/lib/chromium/chromium+0x399c4c6) #23 0x563a747f977e (/usr/lib/chromium/chromium+0x399c77d) #24 0x563a747ca13f (/usr/lib/chromium/chromium+0x396d13e) #25 0x563a747ca17e (/usr/lib/chromium/chromium+0x396d17d) #26 0x563a73e1f387 (/usr/lib/chromium/chromium+0x2fc2386) #27 0x563a740e27a3 (/usr/lib/chromium/chromium+0x32857a2) #28 0x563a744510bc (/usr/lib/chromium/chromium+0x35f40bb) #29 0x563a7624245f (/usr/lib/chromium/chromium+0x53e545e) #30 0x563a76248a24 (/usr/lib/chromium/chromium+0x53eba23) #31 0x563a76246b62 (/usr/lib/chromium/chromium+0x53e9b61) #32 0x563a7624582d (/usr/lib/chromium/chromium+0x53e882c) #33 0x563a7623e213 (/usr/lib/chromium/chromium+0x53e1212) #34 0x563a76259abb (/usr/lib/chromium/chromium+0x53fcaba) #35 0x563a76259de0 (/usr/lib/chromium/chromium+0x53fcddf) #36 0x563a76259370 (/usr/lib/chromium/chromium+0x53fc36f) #37 0x563a740cbc46 (/usr/lib/chromium/chromium+0x326ec45) #38 0x563a740cb76c (/usr/lib/chromium/chromium+0x326e76b) #39 0x563a740c7eed (/usr/lib/chromium/chromium+0x326aeec) #40 0x563a740be74b (/usr/lib/chromium/chromium+0x326174a) #41 0x563a740b1044 (/usr/lib/chromium/chromium+0x3254043) #42 0x563a740b0d75 (/usr/lib/chromium/chromium+0x3253d74) #43 0x563a740cf426 (/usr/lib/chromium/chromium+0x3272425) #44 0x563a7612e0e0 (/usr/lib/chromium/chromium+0x52d10df) #45 0x7f62e2e07b0f (/usr/lib/x86_64-linux-gnu/libevent-2.1.so.7.0.0+0x23b0e) #46 0x7f62e2e0824f event_base_loop #47 0x563a7612e38e (/usr/lib/chromium/chromium+0x52d138d) #48 0x563a760ce5d5 (/usr/lib/chromium/chromium+0x52715d4) #49 0x563a760a6670 (/usr/lib/chromium/chromium+0x524966f) #50 0x563a743ec3b3 (/usr/lib/chromium/chromium+0x358f3b2) #51 0x563a760e42a9 (/usr/lib/chromium/chromium+0x52872a8) #52 0x563a76120c9e (/usr/lib/chromium/chromium+0x52c3c9d) #53 0x7f62e4046f27 start_thread #54 0x7f62df1b531f clone r8: 0077 r9: 0050 r10: 0004 r11: 007c r12: 7f62bc20 r13: 7f62bc30 r14: 7f62bc206850 r15: 0040 di: 0261 si: 0004 bp: 0260 bx: 7f01bc2be66f dx:
Bug#964465: python3-ironic-lib: missing Breaks+Replaces: ironic-common (<< 1:15)
Package: python3-ironic-lib Version: 4.2.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' 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 This test intentionally skipped 'testing' to find file overwrite problems before packages migrate from 'unstable' to 'testing'. >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-ironic-lib_4.2.1-1_all.deb ... Unpacking python3-ironic-lib (4.2.1-1) over (2.14.0-2) ... dpkg: error processing archive /var/cache/apt/archives/python3-ironic-lib_4.2.1-1_all.deb (--unpack): trying to overwrite '/etc/ironic/rootwrap.d/ironic-lib.filters', which is also in package ironic-common 1:11.1.0-6 Errors were encountered while processing: /var/cache/apt/archives/python3-ironic-lib_4.2.1-1_all.deb (Not sure which ironic-common version dropped the file, the sid version no longer has it.) cheers, Andreas ironic-common=1:11.1.0-6_python3-ironic-lib=4.2.1-1.log.gz Description: application/gzip
Bug#964464: libkimageannotator-common: missing Breaks+Replaces: libkimageannotator0 (<< 0.3.1-4)
Package: libkimageannotator-common Version: 0.3.1-4 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' 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 .../libkimageannotator-common_0.3.1-4_all.deb ... Unpacking libkimageannotator-common (0.3.1-4) ... dpkg: error processing archive /var/cache/apt/archives/libkimageannotator-common_0.3.1-4_all.deb (--unpack): trying to overwrite '/usr/share/kImageAnnotator/translations/kImageAnnotator_cs.qm', which is also in package libkimageannotator0:amd64 0.3.1-1 Errors were encountered while processing: /var/cache/apt/archives/libkimageannotator-common_0.3.1-4_all.deb cheers, Andreas libkimageannotator0=0.3.1-1_libkimageannotator-common=0.3.1-4.log.gz Description: application/gzip
Bug#963713: net-snmp: CVE-2019-20892
Hi, On 07/07/2020 17:07, Sylvain Beucler wrote: > On 06/07/2020 19:11, Sylvain Beucler wrote: >> Do we have definite info on what versions are affected? >> >> I cannot reproduce the issue in jessie/stretch/buster (5.7.x). >> >> Incidentally Salvatore's test now yields an error in bullseye >> (5.8dfsg-3), though I suspect the issue is at the client's level: >> # snmpbulkget -v3 -Cn1 -Cr1472 -l authPriv -u testuser -a SHA -A >> testpass -x AES -X testpass 127.0.0.1 1.3.6.1.2.1.1.5 1.3.6.1.2.1.1.7 >> Error in packet. >> Reason: (genError) A general failure occured > > Bisecting gives a range of ~20 commits where the server is buggy (either > goes 100% CPU, or rejects the request with "send response: Too long"). > > 1a0dbe19bf2787bb5bea913f210a9a5eb4c0c80c > "new snmp token sendMessageMaxSize" > works fine. > > 3eb4b473fed816108d1843dadee1ce877415b96b > "add debug_enable_token_logs debug_disable_token_logs to output_api.h" > triggers the double-free. > > Anything in-between is random, and includes 2 "getbulk enhancements". > The date varies greatly so this may be a series of cherry-picks. > > In any case, all of this happens between 5.7.3 and 5.8.pre1. Restricting further (good..bad): $ git shortlog 1a0dbe19bf2787bb5bea913f210a9a5eb4c0c80c..e207b8113260fd7d84df0ebdb66925ab70da29b2 Robert Story (2): Add VMware copyright tweak sndMsgMaxSize handling VMwareDev Randy (4): getbulk enhancements: limit responses gathered reduce session msg max sizes to transport max getbulk enhancements: response size + fallback to forward encoding move v3 engineID probe into initial packet build Cheers! Sylvain Beucler Debian LTS Team
Processed: tagging 951271 ...
Processing commands for cont...@bugs.debian.org: > tags 951271 + patch Bug #951271 [src:java-gnome] java-gnome: Please migration from enchant(1) to enchant-2 Added tag(s) patch. > forwarded 951271 > https://aur.archlinux.org/cgit/aur.git/plain/enchant_2.patch?h=java-gnome Bug #951271 [src:java-gnome] java-gnome: Please migration from enchant(1) to enchant-2 Set Bug forwarded-to-address to 'https://aur.archlinux.org/cgit/aur.git/plain/enchant_2.patch?h=java-gnome'. > thanks Stopping processing here. Please contact me if you need assistance. -- 951271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963836: marked as done (xscorch build depends on the removed libmikmod2-dev provides)
Your message dated Tue, 07 Jul 2020 15:18:44 + with message-id and subject line Bug#963836: fixed in xscorch 0.2.1-1+nmu3 has caused the Debian Bug report #963836, regarding xscorch build depends on the removed libmikmod2-dev provides 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.) -- 963836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xscorch Version: 0.2.1-1+nmu2 Severity: serious Tags: ftbfs bullseye sid The following packages have unmet dependencies: builddeps:xscorch : Depends: libmikmod2-dev but it is not installable Please upgrade the build dependency to libmikmod-dev. --- End Message --- --- Begin Message --- Source: xscorch Source-Version: 0.2.1-1+nmu3 Done: Luis Paulo Linares We believe that the bug you reported is fixed in the latest version of xscorch, 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 963...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luis Paulo Linares (supplier of updated xscorch package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 02 Jul 2020 09:57:17 -0300 Source: xscorch Architecture: source Version: 0.2.1-1+nmu3 Distribution: unstable Urgency: medium Maintainer: Jacob Luna Lundberg Changed-By: Luis Paulo Linares Closes: 963836 Changes: xscorch (0.2.1-1+nmu3) unstable; urgency=medium . * Non-maintainer upload. * debian/control: changed from 'libmikmod2-dev' to 'libmikmod-dev' in Build-Depends field to avoid a FTBFS. Thanks to Adrian Bunk . (Closes: #963836) Checksums-Sha1: 5f71dbb19dc4d158cad0bf4dd3ea1b63e658558e 1900 xscorch_0.2.1-1+nmu3.dsc 6689e930c780f1f3ba99179c212b2b1e42edfa3b 11444 xscorch_0.2.1-1+nmu3.debian.tar.xz 3cd96ea655f5d7330a82f37622f6f042375c37b2 11755 xscorch_0.2.1-1+nmu3_source.buildinfo Checksums-Sha256: 6f6cf4397a8e80c85c88f2fbdf2e2f4857df373ef8136e7f02e5a48001e97efb 1900 xscorch_0.2.1-1+nmu3.dsc 5f93fd281108956ba8f49c7c67de8000104967fc16cef791b1a576815daef33b 11444 xscorch_0.2.1-1+nmu3.debian.tar.xz f4ff2a2370df097a8142585f51bc82ab2ebb66e29277cdd71150510bb1bb79a2 11755 xscorch_0.2.1-1+nmu3_source.buildinfo Files: b33636fb3420f61979bd3f18be2eb839 1900 games optional xscorch_0.2.1-1+nmu3.dsc 1b33425d0d90cb2775b1228d63d42c73 11444 games optional xscorch_0.2.1-1+nmu3.debian.tar.xz e6668283a816c100d17380b1da87b5b4 11755 games optional xscorch_0.2.1-1+nmu3_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAl799SMUHHBsdWd3YXNo QGRlYmlhbi5vcmcACgkQDEjqKnqP/XtSew//YjGEHZ5KcnRgCf6VyXPp88We0AXu tir5ezcvMHtkrQ9jFoHhHai+9kvlwTdsiKfmYR0lDm0mp+4wh8hJ3FNV/fh9D9ex SLssEdIfMVV4t7L6ToWmSrhfpCqjm3aOqxDJOHpyyLLnoAtapxY6LPkqfLq14Ssw 8yqj43i4WLSZSADRGEKqeKakpWVnbFFDgeJd6EY2rOK0i1wZuXVKC0HnFD9lGkSC XcCrfNk5hRFO7A5rLx47iVs8x4KCcdIz4EEfsLmBdTxfEQOofvVtrxe4PZhD3f/E u7mDOABcC+S5aQzr2rbEcgZhgs55iBUXRoykCkLJrzFoPe3J3hM+Rk6Ho5XLVqOe 3wp0NKwsVpD4hogh08Y+7V3+Hf5BZIJVhWh1hT78/ApVCebuRT2JSEFgmgSQ9FkX VHz2ftVXl2RGEDC7QadZis51yYdKlDsVu6bFoTkKYRDjRWWjmC4/MUNWQB5SLzfn yJdWkm9bQkHm/F/4U6IiE6Ah0QIJgOAmtc9P7r9Z9uFvyZlzOxNNbPwa/XQiZITl 3fMGJ2/U3tc7N7vnIwqqYwmG2Q8glFAEMymLei3nTPkyXat9PF/WBpZZLynLAS21 OUpslfVklZ7m4qJq+I70aDxaTzf5gTNNr3bgK++42BB+urPmOYS3SdHWdU6rkYF0 Ys/ycvlmAUX5C6Q= =7VJ5 -END PGP SIGNATURE End Message ---
Processed: affects 964309
Processing commands for cont...@bugs.debian.org: > affects 964309 + src:javahelper Bug #964309 [bsdmainutils] bsdmainutils: FTBFS because of missing libncurses-dev dependency Added indication that 964309 affects src:javahelper > thanks Stopping processing here. Please contact me if you need assistance. -- 964309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963713: net-snmp: CVE-2019-20892
Hi, On 06/07/2020 19:11, Sylvain Beucler wrote: > Do we have definite info on what versions are affected? > > I cannot reproduce the issue in jessie/stretch/buster (5.7.x). > > Incidentally Salvatore's test now yields an error in bullseye > (5.8dfsg-3), though I suspect the issue is at the client's level: > # snmpbulkget -v3 -Cn1 -Cr1472 -l authPriv -u testuser -a SHA -A > testpass -x AES -X testpass 127.0.0.1 1.3.6.1.2.1.1.5 1.3.6.1.2.1.1.7 > Error in packet. > Reason: (genError) A general failure occured Bisecting gives a range of ~20 commits where the server is buggy (either goes 100% CPU, or rejects the request with "send response: Too long"). 1a0dbe19bf2787bb5bea913f210a9a5eb4c0c80c "new snmp token sendMessageMaxSize" works fine. 3eb4b473fed816108d1843dadee1ce877415b96b "add debug_enable_token_logs debug_disable_token_logs to output_api.h" triggers the double-free. Anything in-between is random, and includes 2 "getbulk enhancements". The date varies greatly so this may be a series of cherry-picks. In any case, all of this happens between 5.7.3 and 5.8.pre1. Cheers! Sylvain
Bug#962221: Fixes for CVE-2020-13696 (#962221)
Mattia, July 7, 2020 2:42:20 PM UTC, Vasyl Gello написав(-ла): >Got it! OK, let me do a quick fix for both issues and push additional commit. Commit is pushed, please try rebuilding the package! -- Vasyl Gello == Certified SolidWorks Expert Mob.:+380 (98) 465 66 77 E-Mail: vasek.ge...@gmail.com Skype: vasek.gello == 호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다 signature.asc Description: PGP signature
Bug#962221: Fixes for CVE-2020-13696 (#962221)
Hi Mattia! July 7, 2020 2:25:37 PM UTC, Mattia Rizzolo написав(-ла): >..however it fails to build :) > > dh_auto_install > install -d /build/xawtv-3.107/debian/tmp > make -j4 install DESTDIR=/build/xawtv-3.107/debian/tmp > AM_UPDATE_INFO_DIR=no >make[1]: Entering directory '/build/xawtv-3.107' >/usr/bin/install -c -d -m 755 /build/xawtv-3.107/debian/tmp/usr/bin >/usr/bin/install -c console/dump-mixers console/record console/showriff >console/showqt console/streamer console/webcam console/scantv console/ttv >console/radio console/fbtv console/v4l-info >/build/xawtv-3.107/debian/tmp/usr/bin >/usr/bin/install -c -m4755 -o root console/v4l-conf >/build/xawtv-3.107/debian/tmp/usr/bin >/usr/bin/install: cannot change ownership of >'/build/xawtv-3.107/debian/tmp/usr/bin/v4l-conf': Operation not permitted >make[1]: *** [console/Subdir.mk:100: install] Error 1 >make[1]: Leaving directory '/build/xawtv-3.107' >dh_auto_install: error: make -j4 install DESTDIR=/build/xawtv-3.107/debian/tmp >AM_UPDATE_INFO_DIR=no returned exit code 2 >make: *** [debian/rules:6: binary] Error 25 >dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 > > >this is related to the addition of Rules-Requires-Root. When run >without fakeroot it's not possible to run such `chmod` commands. In >fact, they are most likely always wrong to run them anyway… I of course built the package but my buildsetup always uses fakeroot exactly to get rid of chown() calls. I will update Rules-Requires-Root to yes then. >In d/copyright, that boilerplate-y thing you copied into the Comment >field, IMHO you should just get rid of it. Also, it's missing many of >the years in the copyright claims: a copyright claim without a year is >at most an legal headache and at worst invalid. Got it! OK, let me do a quick fix for both issues and push additional commit. -- Vasyl Gello == Certified SolidWorks Expert Mob.:+380 (98) 465 66 77 E-Mail: vasek.ge...@gmail.com Skype: vasek.gello == 호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다 signature.asc Description: PGP signature
Bug#964448: marked as done (oca-core: needs a source-only upload)
Your message dated Tue, 07 Jul 2020 14:39:11 + with message-id and subject line Bug#964448: fixed in oca-core 11.0.20191007-4 has caused the Debian Bug report #964448, regarding oca-core: needs a source-only upload 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.) -- 964448: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964448 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: oca-core Version: 11.0.20191007-3 Severity: serious The release team have decreed that non-buildd binaries can no longer migrate to testing. Please make a source-only upload so your package can migrate. --- End Message --- --- Begin Message --- Source: oca-core Source-Version: 11.0.20191007-4 Done: Sebastien Delafond We believe that the bug you reported is fixed in the latest version of oca-core, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Delafond (supplier of updated oca-core 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: Tue, 07 Jul 2020 15:38:01 +0200 Source: oca-core Architecture: source Version: 11.0.20191007-4 Distribution: unstable Urgency: medium Maintainer: OCA Packaging Team Changed-By: Sebastien Delafond Closes: 964448 Changes: oca-core (11.0.20191007-4) unstable; urgency=medium . [ Sébastien Delafond ] * Source-only upload (Closes: #964448) Checksums-Sha1: a23965a8d568ba3c41070a9debaffb3fbcba7945 1748 oca-core_11.0.20191007-4.dsc f9397a6af420c4ad0e590a01a1a67322b6e301f5 19672 oca-core_11.0.20191007-4.debian.tar.xz e84ba900ad09005e786ff6eeabe5d796695e3d6f 5890 oca-core_11.0.20191007-4_amd64.buildinfo Checksums-Sha256: 4161acf6b57fd759e30cad8390930769afcce5778ce6b215636684608022bd98 1748 oca-core_11.0.20191007-4.dsc 8728a722fb2e03704c94318e49dd30c340dcf2bf266f60459523d632a6dc0918 19672 oca-core_11.0.20191007-4.debian.tar.xz f30af1e52c9d661091dfb41cd1e202ad99e01b92804071161bbb5636db4216a5 5890 oca-core_11.0.20191007-4_amd64.buildinfo Files: d8ddf5a61dabf5de8949b6f4639d4086 1748 net optional oca-core_11.0.20191007-4.dsc 7040bb7f852b16146aa4e4590f8d5513 19672 net optional oca-core_11.0.20191007-4.debian.tar.xz 68691848d9f1a1190134bbf836b118a1 5890 net optional oca-core_11.0.20191007-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEAqSkbVtrXP4xJMh3EL6Jg/PVnWQFAl8EfHUACgkQEL6Jg/PV nWS0ZQf/XCtr/V4cA8w+ujnb5ZBGCJlMwJ8PrtKi+FOxhC6WSy9raRhsFTpF7HS9 9RX5ofb662r7lN+7ia+5dG/GLphFYIx86cuVdOhWnSkhulcLn9k2vS3N6jtLDkU2 NylkzePGaByM2WGGTwwPTxP2/sb2cELeUJEYf0kYnrqSbngdNBzCBiEjj9WQHtCq b0lxZAadxVFrJTXIzNyMb5WUI2cUX/ojWTBu/Lo1c4gCHaZgnSGH5TKrd9Hygzm3 O4VttC1AgdWRAuLGBfobz1t1ExyEi2h0X7psvj1Xkcs85AC0sQYV8w8QZT0P9Kiu GzZrCclm8DLgMQW61l0zCpacF7j1XA== =ny9N -END PGP SIGNATURE End Message ---
Bug#962221: Fixes for CVE-2020-13696 (#962221)
On Mon, Jul 06, 2020 at 09:07:31PM +, Vasyl Gello wrote: > I pushed the modernized package however ..however it fails to build :) dh_auto_install install -d /build/xawtv-3.107/debian/tmp make -j4 install DESTDIR=/build/xawtv-3.107/debian/tmp AM_UPDATE_INFO_DIR=no make[1]: Entering directory '/build/xawtv-3.107' /usr/bin/install -c -d -m 755 /build/xawtv-3.107/debian/tmp/usr/bin /usr/bin/install -c console/dump-mixers console/record console/showriff console/showqt console/streamer console/webcam console/scantv console/ttv console/radio console/fbtv console/v4l-info /build/xawtv-3.107/debian/tmp/usr/bin /usr/bin/install -c -m4755 -o root console/v4l-conf /build/xawtv-3.107/debian/tmp/usr/bin /usr/bin/install: cannot change ownership of '/build/xawtv-3.107/debian/tmp/usr/bin/v4l-conf': Operation not permitted make[1]: *** [console/Subdir.mk:100: install] Error 1 make[1]: Leaving directory '/build/xawtv-3.107' dh_auto_install: error: make -j4 install DESTDIR=/build/xawtv-3.107/debian/tmp AM_UPDATE_INFO_DIR=no returned exit code 2 make: *** [debian/rules:6: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 this is related to the addition of Rules-Requires-Root. When run without fakeroot it's not possible to run such `chmod` commands. In fact, they are most likely always wrong to run them anyway… > there are two errors claiming two libs are not compiled against libc and > several > others missing requured prerequisites. I have not figured yet how to fix > these, > maybe you know? I'll see them when I can fully build the package ;) In d/copyright, that boilerplate-y thing you copied into the Comment field, IMHO you should just get rid of it. Also, it's missing many of the years in the copyright claims: a copyright claim without a year is at most an legal headache and at worst invalid. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature
Processed: your mail
Processing commands for cont...@bugs.debian.org: > # bsdmainutils doesn't even build right now even with that fixed > # and if at all it would be affects javahelper. > # libreoffice doesn't use bsdmainutils itself. > affects 964309 - src:libreoffice Bug #964309 [bsdmainutils] bsdmainutils: FTBFS because of missing libncurses-dev dependency Removed indication that 964309 affects src:libreoffice > End of message, stopping processing here. Please contact me if you need assistance. -- 964309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > # bsdmainutils doesn't even build right now even with that fixed > # and if at all it would be affects javahelper. > # libreoffice doesn't use bsdmainutils itself. > affects 964309 - src: libreoffice Bug #964309 [bsdmainutils] bsdmainutils: FTBFS because of missing libncurses-dev dependency Removed indication that 964309 affects > End of message, stopping processing here. Please contact me if you need assistance. -- 964309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964449: autopkg test failures with binutils 2.35
Package: src:backward-cpp Version: 1.5-1 Severity: serious Tags: sid bullseye see https://ci.debian.net/data/autopkgtest/testing/amd64/b/backward-cpp/6173600/log.gz a work around would be to allow stderr in the test. autopkgtest [09:43:20]: test build: [--- Build: OK i=0 i=1 BFD: DWARF error: could not find variable specification at offset 1c07 BFD: DWARF error: could not find variable specification at offset 1c82 BFD: DWARF error: could not find variable specification at offset 1d09 BFD: DWARF error: could not find variable specification at offset b1cd BFD: DWARF error: could not find variable specification at offset b1d9 BFD: DWARF error: could not find variable specification at offset b3ab BFD: DWARF error: could not find variable specification at offset b3b7 BFD: DWARF error: could not find variable specification at offset b9c6 BFD: DWARF error: could not find variable specification at offset ba0d BFD: DWARF error: could not find variable specification at offset ba54 BFD: DWARF error: could not find variable specification at offset ba9b BFD: DWARF error: could not find variable specification at offset baca BFD: DWARF error: could not find variable specification at offset bb05 BFD: DWARF error: could not find variable specification at offset bb11 #0 at unsigned long backward::details::unwind::callback>(backward::StackTraceImpl::callback, unsigned long) #1 at backward::StackTraceImpl::load_here(unsigned long) #2 at TracedException::_get_trace[abi:cxx11]() #3 at TracedException::TracedException() #4 at f(int) #5 at f(int) #6 at f(int) #7 at main #8 at __libc_start_main #9 at _start #10 at Run: OK Test: OK
Processed: Adjust bug metadata for testing migration
Processing commands for cont...@bugs.debian.org:
> Reassign 963757 streamlink 1.4.1+dfsg-1
Bug #963757 {Done: Alexis Murzeau } [src:fonts-font-awesome,
src:streamlink] fonts-font-awesome breaks streamlink autopkgtest:
/usr/share/doc/python3-streamlink/html/_static/fonts/fontawesome-webfont.eot
MISSING
Bug reassigned from package 'src:fonts-font-awesome, src:streamlink' to
'streamlink'.
No longer marked as found in versions streamlink/1.4.1+dfsg-1 and
fonts-font-awesome/5.0.10+really4.7.0~dfsg-2.
No longer marked as fixed in versions streamlink/1.4.1+dfsg-2.
Bug #963757 {Done: Alexis Murzeau } [streamlink]
fonts-font-awesome breaks streamlink autopkgtest:
/usr/share/doc/python3-streamlink/html/_static/fonts/fontawesome-webfont.eot
MISSING
Marked as found in versions streamlink/1.4.1+dfsg-1.
> Fixed 963757 1.4.1+dfsg-2
Bug #963757 {Done: Alexis Murzeau } [streamlink]
fonts-font-awesome breaks streamlink autopkgtest:
/usr/share/doc/python3-streamlink/html/_static/fonts/fontawesome-webfont.eot
MISSING
Marked as fixed in versions streamlink/1.4.1+dfsg-2.
> Thanks
Stopping processing here.
Please contact me if you need assistance.
--
963757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#964448: oca-core: needs a source-only upload
Package: oca-core Version: 11.0.20191007-3 Severity: serious The release team have decreed that non-buildd binaries can no longer migrate to testing. Please make a source-only upload so your package can migrate.
Processed: re: oca-core: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd)
Processing commands for cont...@bugs.debian.org: > severity 962877 serious Bug #962877 [oca-core] oca-core: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd) Severity set to 'serious' from 'important' > close 962877 11.0.20191007-3 Bug #962877 [oca-core] oca-core: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd) Marked as fixed in versions oca-core/11.0.20191007-3. Bug #962877 [oca-core] oca-core: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 962877: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962877 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: re: zoneminder: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd)
Processing commands for cont...@bugs.debian.org: > severity 962886 serious Bug #962886 [src:zoneminder] zoneminder: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 962886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962886 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: re: python3-cylc: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd)
Processing commands for cont...@bugs.debian.org: > severity 962879 serious Bug #962879 [python3-cylc] python3-cylc: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 962879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962879 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: re: omnidb-common: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd)
Processing commands for cont...@bugs.debian.org: > severity 962878 serious Bug #962878 [omnidb-common] omnidb-common: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 962878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962878 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963425: marked as done (node-terser: FTBFS: ERROR: `m` is not a supported option)
Your message dated Tue, 07 Jul 2020 11:34:09 + with message-id and subject line Bug#963425: fixed in node-terser 4.1.2-7 has caused the Debian Bug report #963425, regarding node-terser: FTBFS: ERROR: `m` is not a supported option 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.) -- 963425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-terser Version: 4.1.2-6 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > NODE_PATH=lib TRAVIS=1 node test/run-tests.js \ > > *** Entering [compress] > --- arguments.js > Running test [replace_index] > Running test [replace_index_strict] > Running test [replace_index_keep_fargs] > Running test [replace_index_keep_fargs_strict] > Running test [modified] > Running test [modified_strict] > Running test [arguments_in_arrow_func_1] > Running test [arguments_in_arrow_func_2] > Running test [arguments_and_destructuring_1] > Running test [arguments_and_destructuring_2] > Running test [arguments_and_destructuring_3] > Running test [duplicate_parameter_with_arguments] > --- array-constructor.js > Running test [array_constructor] > Running test [array_constructor_unsafe] > --- arrays.js > Running test [holes_and_undefined] > Running test [constant_join] > Running test [constant_join_2] > Running test [spread_with_variable_as_last_element] > Running test [spread_with_variable_in_middle] > Running test [spread_with_variable_at_front] > Running test [spread_with_variable_at_front_after_elisions] > Running test [spread_with_array_at_end] > Running test [spread_with_logical_expression_at_end] > Running test [spread_with_logical_expression_at_middle] > Running test [constant_join_3] > Running test [for_loop] > Running test [index] > Running test [length] > Running test [index_length] > --- arrow.js > Running test [arrow_functions_without_body] > Running test [arrow_functions_with_body] > Running test [arrow_function_with_single_parameter_with_default] > Running test [arrow_binding_pattern] > Running test [arrow_binding_pattern_strict] > Running test [arrow_with_regexp] > Running test [arrow_unused] > Running test [arrow_unused_toplevel] > Running test [no_leading_parentheses] > Running test [async_identifiers] > Running test [async_function_expression] > Running test [issue_27] > Running test [issue_2105_1] > Running test [issue_2105_2] > Running test [issue_2136_2] > Running test [issue_2136_3] > Running test [call_args] > Running test [call_args_drop_param] > Running test [issue_485_crashing_1530] > Running test [issue_2084] > Running test [export_default_object_expression] > Running test [concise_methods_with_computed_property2] > Running test [async_object_literal] > Running test [issue_2271] > Running test [concise_method_with_super] > Running test [issue_3092a] > Running test [issue_3092b] > --- ascii.js > Running test [ascii_only_true] > Running test [ascii_only_false] > --- asm.js > Running test [asm_mixed] > Running test [asm_toplevel] > Running test [asm_function_expression] > Running test [asm_nested_functions] > --- assignment.js > Running test [op_equals_left_local_var] > Running test [op_equals_right_local_var] > Running test [op_equals_left_global_var] > Running test [op_equals_right_global_var] > --- async.js > Running test [await_precedence] > Running test [await_precedence_prop] > Running test [await_precedence_call] > Running test [async_function_declaration] > Running test [async_function_expression] > Running test [async_class] > Running test [async_object_literal] > Running test [async_export] > Running test [async_inline] > Running test [async_identifiers] > Running test [async_shorthand_property] > Running test [async_arrow] > Running test [async_arrow_wait] > Running test [async_arrow_iife] > Running test [async_arrow_iife_negate_iife] > Running test [issue_2344_1] > Running test [issue_2344_2] > Running test [issue_3079] > Running test [issue_3079_2] > Running test [for_await_of] > Running test [for_await_of_2] >
Processed: re: kytos-sphinx-theme-common: should depend on fonts-glyphicons-halflings (not fonts-glewlwyd)
Processing commands for cont...@bugs.debian.org: > severity 962876 serious Bug #962876 [kytos-sphinx-theme-common] kytos-sphinx-theme-common: should depend on fonts-glyphicons-halflings (not fonts-glewlwyd) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 962876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: python3-django-hyperkitty: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd)
Processing commands for cont...@bugs.debian.org: > severity 962880 serious Bug #962880 [python3-django-hyperkitty] python3-django-hyperkitty: should depend on fonts-font-awesome and/or fonts-glyphicons-halflings (not fonts-glewlwyd) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 962880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962880 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#963425 marked as pending in node-terser
Processing control commands: > tag -1 pending Bug #963425 [node-commander] node-terser: FTBFS: ERROR: `m` is not a supported option Ignoring request to alter tags of bug #963425 to the same tags previously set -- 963425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963425 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963425: marked as pending in node-terser
Control: tag -1 pending Hello, Bug #963425 in node-terser reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-terser/-/commit/f51cc5e36920dd79b1c1f01b58258d12644421f4 Add support for node-commander ≥ 4 Closes: #963425 (this message was generated automatically) -- Greetings https://bugs.debian.org/963425
Bug#953875: runit - default installation can force init switch
Package: runit Version: 2.1.2-36 Followup-For: Bug #953875 Control: tag -1 patch There is an open RFS bug (#960940) on mentors that fixes this bug. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960940 Lorenzo -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: runit (via /run/runit.stopit) Versions of packages runit depends on: ii libc6 2.30-8 ii sysuser-helper 1.3.3 Versions of packages runit recommends: ii runit-init 2.1.2-36 runit suggests no packages. -- Configuration Files: /etc/default/runit changed [not included] -- no debconf information
Processed: Re: runit - default installation can force init switch
Processing control commands: > tag -1 patch Bug #953875 [runit] runit - default installation can force init switch Added tag(s) patch. -- 953875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953875 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964445: libbluray: binary-all FTBFS
Source: libbluray Version: 1:1.2.0-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=libbluray=all=1%3A1.2.0-2=1594068597=0 ... fakeroot debian/rules binary-indep dh binary-indep --with javahelper dh_testroot -i dh_prep -i dh_install -i dh_install: warning: Cannot find (any matches for) "usr/share/java" (tried in ., debian/tmp) dh_install: warning: libbluray-bdj missing files: usr/share/java dh_install: error: missing files, aborting make: *** [debian/rules:23: binary-indep] Error 25
Processed: affects 964309
Processing commands for cont...@bugs.debian.org: > affects 964309 src:libreoffice Bug #964309 [bsdmainutils] bsdmainutils: FTBFS because of missing libncurses-dev dependency Added indication that 964309 affects src:libreoffice > thanks Stopping processing here. Please contact me if you need assistance. -- 964309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 964309
Processing commands for cont...@bugs.debian.org: > tags 964309 + ftbfs Bug #964309 [bsdmainutils] bsdmainutils: FTBFS because of missing libncurses-dev dependency Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 964309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964348: marked as done (bbhash: Missing test dependencies)
Your message dated Tue, 07 Jul 2020 10:18:46 + with message-id and subject line Bug#964348: fixed in bbhash 1.0.0-3 has caused the Debian Bug report #964348, regarding bbhash: Missing test dependencies to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 964348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964348 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bbhash Version: 1.0.0-2 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/b/bbhash/5910297/log.gz ... autopkgtest [21:08:27]: test run-unit-test: [--- g++ -o Bootest bootest.cpp -O3 -std=c++11 -lpthread make: g++: Command not found make: *** [makefile:29: Bootest] Error 127 --- End Message --- --- Begin Message --- Source: bbhash Source-Version: 1.0.0-3 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of bbhash, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille (supplier of updated bbhash package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 07 Jul 2020 12:01:38 +0200 Source: bbhash Architecture: source Version: 1.0.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 964348 Changes: bbhash (1.0.0-3) unstable; urgency=medium . * Add missing Test-Depends: build-essential Closes: #964348 Checksums-Sha1: 4ab72453a33999a8ecb319246b5bde1cee6e59c9 1982 bbhash_1.0.0-3.dsc f384c3ca9d90feaf0c261b3f3dbe9d81989aa232 3396 bbhash_1.0.0-3.debian.tar.xz e0e9cb5f114e129e18840447b26193b14b89ff5a 5469 bbhash_1.0.0-3_amd64.buildinfo Checksums-Sha256: d5a23fc965fa39d22c0b9c2bb63b34f3ff50079b1d307692d184bbb932416bc9 1982 bbhash_1.0.0-3.dsc 4f733636edcbb3167cb794ff1ea6f1724dae211da12cd810dfdbef76468827bd 3396 bbhash_1.0.0-3.debian.tar.xz a1e5dadf99dccc40c5eb6749a68769a4a54a88f5df1632840fe52a5462e09488 5469 bbhash_1.0.0-3_amd64.buildinfo Files: 89689d0150b5a7e4ccf3ac2520f2cb5f 1982 science optional bbhash_1.0.0-3.dsc 3b1121a738f4ea80bbac4172886df246 3396 science optional bbhash_1.0.0-3.debian.tar.xz 1afe17abc21baf9d023b542ea175378b 5469 science optional bbhash_1.0.0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl8ESJ8RHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtH0Uw/+ORCTi1/ToA7wCFE0QQ7RVHV9SWu6Ppmd o0yxVxBLmMFWGwUvkH+bj5eOpMzAI13MNRf5IWPwJh1VzAfMJUDDuxZy86Y7n47N tJOnpnwTbISbLYV8/RV6maQ9jWyFdco/LHKMKH60vbWRxf4FgSMsABoKdrNqHq5B TrfwwhhaxZwXMVYikyFloH5gt8CDoz6cZZfz8VCpHTAu9RgLBrzrOhSsohFR494e 5rwzJ3bXRvU0/msxNeOzLwL0Df9onmXn2WNbXGFuXNOE8GqJK56Utx5AourLG5zk puMb6a3jtSWsuxToUFL8DsOe54XlCpCo4OdPUFVslXmgtJ3z4+ISEGPbjYUYN7KC 8GnQRXzl9QRy7qg6z1yUkbg9uc+ysNODd0NsVV+6Y4O3j5vMUC+MmY4Ij49LhrfV FNutD1kGtXnuH+Kl1SB+tW2H8j8MG1MqYWiMIq985B0ckJryBJxF5DlQB0rYIome vtQ1Gac5xyOA9nulg2DYEGOWp2s29IWpKycyfJfoOqDlLMC5BZVgaRlfR6QR2uBF Iv7ycPQqDbTr9OUw+vH98bUWYXUqbmHRZv8Kkf7HJ8C6/wDxfhMRfNsNH9ioQQDN ww1YXB/V3eOOdMcqQmKWqWQEGXeyXn8aE7kaeRysOKJn9mZvEdEYi6QRArmyLUZv nIPI2OEWf9I= =iDGA -END PGP SIGNATURE End Message ---
Processed: tagging 964423
Processing commands for cont...@bugs.debian.org: > tags 964423 + bullseye sid Bug #964423 [src:dspdfviewer] FTBFS: QDesktopWidget::screenGeometry is deprecated Added tag(s) bullseye and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 964423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#925749: marked as done (liblemon: ftbfs with GCC-9)
Your message dated Tue, 07 Jul 2020 09:48:49 +
with message-id
and subject line Bug#925749: fixed in liblemon 1.3.1+dfsg-3
has caused the Debian Bug report #925749,
regarding liblemon: ftbfs with GCC-9
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.)
--
925749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=925749
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:liblemon
Version: 1.3.1+dfsg-2
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-9
Please keep this issue open in the bug tracker for the package it
was filed for. If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.
The package fails to build in a test rebuild on at least amd64 with
gcc-9/g++-9, but succeeds to build with gcc-8/g++-8. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc9-20190321/liblemon_1.3.1+dfsg-2_unstable_gcc9.log
The last lines of the build log are at the end of this report.
To build with GCC 9, either set CC=gcc-9 CXX=g++-9 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.
apt-get -t=experimental install g++
Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-9/porting_to.html
GCC 9 also passes the linker option --as-needed by default; typical
build issues are passing libraries before object files to the linker,
or underlinking of convenience libraries built from the same source.
[...]
1667 | min = _graph.oppositeArc(a);
In file included from
/<>/liblemon-1.3.1+dfsg/test/matching_test.cc:27:
/<>/liblemon-1.3.1+dfsg/lemon/concepts/graph.h:335:9: note: because
'lemon::concepts::Graph::Arc' has user-provided
'lemon::concepts::Graph::Arc::Arc(const lemon::concepts::Graph::Arc&)'
335 | Arc(const Arc&) { }
| ^~~
[ 71%] Linking CXX executable matching_test
cd /<>/liblemon-1.3.1+dfsg/obj-x86_64-linux-gnu/test &&
/usr/bin/cmake -E cmake_link_script CMakeFiles/matching_test.dir/link.txt
--verbose=1
/usr/bin/c++ -g -O2 -fdebug-prefix-map=/<>/liblemon-1.3.1+dfsg=.
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
-D_FORTIFY_SOURCE=2 -Wall -W -Wunused -Wformat=2 -Wctor-dtor-privacy
-Wnon-virtual-dtor -Wno-char-subscripts -Wwrite-strings -Wno-char-subscripts
-Wreturn-type -Wcast-qual -Wcast-align -Wsign-promo -Woverloaded-virtual
-fno-strict-aliasing -Wold-style-cast -Wno-unknown-pragmas -Wl,-z,relro
-Wl,-z,now -rdynamic CMakeFiles/matching_test.dir/matching_test.cc.o -o
matching_test -L/<>/liblemon-1.3.1+dfsg/obj-x86_64-linux-gnu/lemon
-Wl,-rpath,/<>/liblemon-1.3.1+dfsg/obj-x86_64-linux-gnu/lemon
../lemon/liblemon.so.1.3.1 -lglpk
make[5]: Leaving directory
'/<>/liblemon-1.3.1+dfsg/obj-x86_64-linux-gnu'
[ 71%] Built target matching_test
make -f test/CMakeFiles/lgf_test.dir/build.make
test/CMakeFiles/lgf_test.dir/depend
make[5]: Entering directory
'/<>/liblemon-1.3.1+dfsg/obj-x86_64-linux-gnu'
cd /<>/liblemon-1.3.1+dfsg/obj-x86_64-linux-gnu && /usr/bin/cmake -E
cmake_depends "Unix Makefiles" /<>/liblemon-1.3.1+dfsg
/<>/liblemon-1.3.1+dfsg/test
/<>/liblemon-1.3.1+dfsg/obj-x86_64-linux-gnu
/<>/liblemon-1.3.1+dfsg/obj-x86_64-linux-gnu/test
/<>/liblemon-1.3.1+dfsg/obj-x86_64-linux-gnu/test/CMakeFiles/lgf_test.dir/DependInfo.cmake
--color=
Scanning dependencies of target lgf_test
make[5]: Leaving directory
'/<>/liblemon-1.3.1+dfsg/obj-x86_64-linux-gnu'
make -f test/CMakeFiles/lgf_test.dir/build.make
test/CMakeFiles/lgf_test.dir/build
make[5]: Entering directory
'/<>/liblemon-1.3.1+dfsg/obj-x86_64-linux-gnu'
[ 71%] Building CXX object test/CMakeFiles/lgf_test.dir/lgf_test.cc.o
cd /<>/liblemon-1.3.1+dfsg/obj-x86_64-linux-gnu/test && /usr/bin/c++
-I/<>/liblemon-1.3.1+dfsg
-I/<>/liblemon-1.3.1+dfsg/obj-x86_64-linux-gnu -g -O2
-fdebug-prefix-map=/<>/liblemon-1.3.1+dfsg=. -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -W
-Wunused -Wformat=2 -Wctor-dtor-privacy -Wnon-virtual-dtor -Wno-char-subscripts
-Wwrite-strings -Wno-char-subscripts -Wreturn-type -Wcast-qual -Wcast-align
-Wsign-promo -Woverloaded-virtual
Processed: your mail
Processing commands for cont...@bugs.debian.org: > fixed 964366 0.9.20-1 Bug #964366 [bashtop] bashtop: insecure use of /tmp There is no source info for the package 'bashtop' at version '0.9.20-1' with architecture '' Unable to make a source version for version '0.9.20-1' Marked as fixed in versions 0.9.20-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 964366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964366 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964334: segfault repeatedly
I've seen this bug has been marked as "more info" (with no comment), but I'm not clear on which additional info are needed and how I can provide them. Advice on how I can help is welcome :-)
Bug#964234: marked as done (dpkg-source: Considers missing symlink targets directory traversals)
Your message dated Tue, 07 Jul 2020 06:33:49 + with message-id and subject line Bug#964234: fixed in dpkg 1.20.4 has caused the Debian Bug report #964234, regarding dpkg-source: Considers missing symlink targets directory traversals 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.) -- 964234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dpkg,firmware-nonfree Version: 20190717-2 Severity: serious Tags: ftbfs Justification: fails to build from source Control: found -1 20190717-2 Control: found -1 1.20.3 Hi, src:firmware-nonfree fails to unpack in sid with latest dpkg: dpkg-source: info: extracting firmware-nonfree in firmware-nonfree-20190717 dpkg-source: info: unpacking firmware-nonfree_20190717.orig.tar.xz dpkg-source: info: unpacking firmware-nonfree_20190717-2.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: applying gitignore.patch Use of uninitialized value $canon_pathname in pattern match (m//) at /usr/share/perl5/Dpkg/Source/Package.pm line 550. dpkg-source: error: pathname 'firmware-nonfree-20190717/debian/config/libertas/sd8688_helper.bin' points outside source root Since this could also be a dpkg error (see the perl warning before the failure) I'm assigning this bug to both packages, please reassign as appropriate. Andreas --- End Message --- --- Begin Message --- Source: dpkg Source-Version: 1.20.4 Done: Guillem Jover We believe that the bug you reported is fixed in the latest version of dpkg, 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 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Guillem Jover (supplier of updated dpkg 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: Tue, 07 Jul 2020 07:57:48 +0200 Source: dpkg Architecture: source Version: 1.20.4 Distribution: unstable Urgency: medium Maintainer: Dpkg Developers Changed-By: Guillem Jover Closes: 870383 964017 964111 964234 Changes: dpkg (1.20.4) unstable; urgency=medium . [ Guillem Jover ] * Improve PIE flags support: - Prefix the specs file spec string self_spec with + instead of *. This way we do not override any previous setting, otherwise when passing the -specs options twice (f.ex. to compile and link), only the last one will take effect, which can break the build. Closes: #870383 * Perl modules: - Dpkg::Source::Package: Explicitly initialize constructor options to their implicit values, otherwise other code end up assuming different defaults. Closes: #964017 - Dpkg::OpenPGP: Use a temporary directory for the GnuPG homedir in verify_signature(), to make sure we do not write to the user home directory, except for the trustkeys.db file if present. - Dpkg::Path: Refactor new check_directory_traversal() function out of Dpkg::Source::Package->extract(). - Dpkg::Path: Do not do partial matches for directory traversal checks, expect a trailing slash after the base directory name. - Dpkg::Path: Catch uncanonicanizable pathnames with a proper error. Closes: #964111 - Dpkg::Path: Do not consider missing symlink targets a directory traversal attempt. Closes: #964234 - Dpkg::Path: Allow /dev/null for directory traversals. Reported by Holger Levsen . * Build system: - Add Module::Signature as configure recommends for CPAN. * Test suite: - Use File::Path::make_path() instead of chained mkdir() in Dpkg_Path.t. - Add unit tests for Dpkg::Path::check_directory_traversal(). . [ Updated programs translations ] * German (Sven Joachim). Checksums-Sha1: 12983dabc712157582b2bcff0c1b0e6f1de9e65c 2109 dpkg_1.20.4.dsc 41a445efe3c51e07b38948defd51e601683a5448 4715020 dpkg_1.20.4.tar.xz 413c302f34195f09a53ef23943c9ebda3f811802 7501 dpkg_1.20.4_amd64.buildinfo Checksums-Sha256: 2762a810d5c151316d170bc0ab6e610283e6454c5df5c34edd2fd33d0c79a64a 2109 dpkg_1.20.4.dsc 3430d76d75b66eeccad8382dad7148e6f46fedce90587964608f0c5c733abe52 4715020
Processed: Bug#964234 in package dpkg marked as pending
Processing control commands: > tag 964234 pending Bug #964234 [dpkg-dev] dpkg-source: Considers missing symlink targets directory traversals Added tag(s) pending. -- 964234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964234 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964234: in package dpkg marked as pending
Control: tag 964234 pending Hi! Bug #964234 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=959c1dbdf --- commit 959c1dbdff41eba3fe108f148b70e4e95cf3113c Author: Guillem Jover Date: Fri Jul 3 07:11:25 2020 +0200 Dpkg::Path: Do not consider missing symlink targets a directory traversal Closes: #964234 diff --git a/debian/changelog b/debian/changelog index 7484c7106..a0394941c 100644 --- a/debian/changelog +++ b/debian/changelog @@ -14,6 +14,8 @@ dpkg (1.20.4) UNRELEASED; urgency=medium expect a trailing slash after the base directory name. - Dpkg::Path: Catch uncanonicanizable pathnames with a proper error. Closes: #964111 +- Dpkg::Path: Do not consider missing symlink targets a directory + traversal attempt. Closes: #964234 * Build system: - Add Module::Signature as configure recommends for CPAN. * Test suite:
