Bug#950496: marked as done (msgpack-c: FTBFS on 32-bit: error: narrowing conversion of ‘4294967295’ from ‘long unsigned int’ to ‘__time_t’ {aka ‘long int’})
Your message dated Sat, 06 Jun 2020 04:04:04 +
with message-id
and subject line Bug#950496: fixed in msgpack-c 3.3.0-1
has caused the Debian Bug report #950496,
regarding msgpack-c: FTBFS on 32-bit: error: narrowing conversion of
‘4294967295’ from ‘long unsigned int’ to ‘__time_t’ {aka ‘long int’}
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.)
--
950496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: msgpack-c
Version: 3.2.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
msgpack-c/experimental on all 32-bit architectures:
https://buildd.debian.org/status/package.php?p=msgpack-c=experimental
[17/122] /usr/bin/c++ -I../build-gtest/install/include -I../include -Iinclude
-DMSGPACK_DEFAULT_API_VERSION=3 -std=c++11 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2-Wall -Wextra
-Wconversion -MD -MT test/CMakeFiles/msgpack_cpp11.dir/msgpack_cpp11.cpp.o -MF
test/CMakeFiles/msgpack_cpp11.dir/msgpack_cpp11.cpp.o.d -o
test/CMakeFiles/msgpack_cpp11.dir/msgpack_cpp11.cpp.o -c
../test/msgpack_cpp11.cpp
FAILED: test/CMakeFiles/msgpack_cpp11.dir/msgpack_cpp11.cpp.o
/usr/bin/c++ -I../build-gtest/install/include -I../include -Iinclude
-DMSGPACK_DEFAULT_API_VERSION=3 -std=c++11 -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2-Wall -Wextra
-Wconversion -MD -MT test/CMakeFiles/msgpack_cpp11.dir/msgpack_cpp11.cpp.o -MF
test/CMakeFiles/msgpack_cpp11.dir/msgpack_cpp11.cpp.o.d -o
test/CMakeFiles/msgpack_cpp11.dir/msgpack_cpp11.cpp.o -c
../test/msgpack_cpp11.cpp
../test/msgpack_cpp11.cpp: In member function ‘virtual void
MSGPACK_TIMESPEC_timespec_pack_convert_32bit_sec_Test::TestBody()’:
../test/msgpack_cpp11.cpp:1081:36: error: narrowing conversion of ‘4294967295’
from ‘long unsigned int’ to ‘__time_t’ {aka ‘long int’} [-Wnarrowing]
1081 | timespec val1{ 0xUL, 0 };
|^
../test/msgpack_cpp11.cpp: In member function ‘virtual void
MSGPACK_TIMESPEC_timespec_object_with_zone_32bit_sec_Test::TestBody()’:
../test/msgpack_cpp11.cpp:1097:36: error: narrowing conversion of ‘4294967295’
from ‘long unsigned int’ to ‘__time_t’ {aka ‘long int’} [-Wnarrowing]
1097 | timespec val1{ 0xUL, 0 };
|^
Andreas
--- End Message ---
--- Begin Message ---
Source: msgpack-c
Source-Version: 3.3.0-1
Done: James McCoy
We believe that the bug you reported is fixed in the latest version of
msgpack-c, 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 950...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
James McCoy (supplier of updated msgpack-c 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, 05 Jun 2020 23:40:36 -0400
Source: msgpack-c
Architecture: source
Version: 3.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: James McCoy
Changed-By: James McCoy
Closes: 919672 950496
Changes:
msgpack-c (3.3.0-1) unstable; urgency=medium
.
* New upstream release
+ Fix FTBFS on 32-bit architectures (Closes: #950496)
* copyright: Remove unused Files/License paragraphs
* Declare compliance with Policy 4.5.0, no changes needed
* tests/control:
+ Add libcjson-dev to Depends for new json example
.
msgpack-c (3.2.1-1) experimental; urgency=medium
.
* New upstream release (Closes: #919672)
* rules:
+ Remove obsolete handling of differing hardening=+all,-pie semantics
+ Run build-time tests for C++11 and C++17
* Switch to debhelper compat 12 via debhelper-compat
* control:
+ Add graphviz to Build-Depends-Indep to build graphs in API docs
+ Mark libmsgpack-doc Multi-Arch: foreign
+ Mark libmsgpack-dev Multi-Arch: same
* Use jdupes to reduce size of libmsgpack-doc
* Declare compliance with Policy 4.4.1, no changes needed
* autopkgtests:
+ Depend on
Bug#960378: marked as done (cegui-mk2: FTBFS with boost 1.71)
Your message dated Sat, 06 Jun 2020 01:03:52 + with message-id and subject line Bug#960378: fixed in cegui-mk2 0.8.7-7 has caused the Debian Bug report #960378, regarding cegui-mk2: FTBFS with boost 1.71 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.) -- 960378: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960378 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cegui-mk2 Version: 0.8.12-3 Severity: important User: team+bo...@tracker.debian.org Usertags: boost1.71 In a test rebuild for the boost 1.71 transition, cegui-mk2 failed to build with: | dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below | dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below | dpkg-gensymbols: warning: debian/libcegui-mk2-0.8.7/DEBIAN/symbols doesn't match completely debian/libcegui-mk2-0.8.7.symbols | --- debian/libcegui-mk2-0.8.7.symbols (libcegui-mk2-0.8.7_0.8.7-6_amd64) | +++ dpkg-gensymbolsZRDpst 2020-05-12 01:23:02.449347977 + | @@ -12528,6 +12528,11 @@ | _ZTVN5CEGUI23InvalidRequestExceptionE@Base 0.8.7 | libCEGUIOgreRenderer-0.so.2 libcegui-mk2-0.8.7 #MINVER# | * Build-Depends-Package: libcegui-mk2-dev | + _ZGVZN5boost6system15system_categoryEvE24system_category_instance@Base 0.8.7-6 | + _ZGVZN5boost6system16generic_categoryEvE25generic_category_instance@Base 0.8.7-6 | + _ZGVZN5boost6system6detail15to_std_categoryERKNS0_14error_categoryEE15system_instance@Base 0.8.7-6 | + _ZGVZN5boost6system6detail15to_std_categoryERKNS0_14error_categoryEE16generic_instance@Base 0.8.7-6 | + _ZGVZN5boost6system6detail15to_std_categoryERKNS0_14error_categoryEE4map_@Base 0.8.7-6 | _ZN4Ogre13FrameListener10frameEndedERKNS_10FrameEventE@Base 0.8.7 | _ZN4Ogre13FrameListener12frameStartedERKNS_10FrameEventE@Base 0.8.7 | _ZN4Ogre13SharedPtrInfoD0Ev@Base 0.8.7 | @@ -12733,9 +12738,12 @@ | (arch=!armel !armhf)_ZN5boost6system12system_errorD0Ev@Base 0.8.7 | (arch=!armel !armhf)_ZN5boost6system12system_errorD1Ev@Base 0.8.7 | (arch=!armel !armhf)_ZN5boost6system12system_errorD2Ev@Base 0.8.7 | - (arch=!armel !armhf)_ZN5boost6system14error_category12std_categoryD0Ev@Base 0.8.7 | - (arch=!armel !armhf)_ZN5boost6system14error_category12std_categoryD1Ev@Base 0.8.7 | - (arch=!armel !armhf)_ZN5boost6system14error_category12std_categoryD2Ev@Base 0.8.7 | +#MISSING: 0.8.7-6# (arch=!armel !armhf)_ZN5boost6system14error_category12std_categoryD0Ev@Base 0.8.7 | +#MISSING: 0.8.7-6# (arch=!armel !armhf)_ZN5boost6system14error_category12std_categoryD1Ev@Base 0.8.7 | +#MISSING: 0.8.7-6# (arch=!armel !armhf)_ZN5boost6system14error_category12std_categoryD2Ev@Base 0.8.7 | + _ZN5boost6system6detail12std_categoryD0Ev@Base 0.8.7-6 | + _ZN5boost6system6detail12std_categoryD1Ev@Base 0.8.7-6 | + _ZN5boost6system6detail12std_categoryD2Ev@Base 0.8.7-6 | _ZNK4Ogre7Texture8getWidthEv@Base 0.8.7 | _ZNK4Ogre7Texture9getHeightEv@Base 0.8.7 | _ZNK4Ogre8Resource9getHandleEv@Base 0.8.7 | @@ -12790,12 +12798,28 @@ | (arch=!armel !armhf)_ZNK5boost6system12system_error4whatEv@Base 0.8.7 | (arch=!armel !armhf)_ZNK5boost6system14error_category10equivalentERKNS0_10error_codeEi@Base 0.8.7 | (arch=!armel !armhf)_ZNK5boost6system14error_category10equivalentEiRKNS0_15error_conditionE@Base 0.8.7 | - (arch=!armel !armhf)_ZNK5boost6system14error_category12std_category10equivalentERKSt10error_codei@Base 0.8.7 | - (arch=!armel !armhf)_ZNK5boost6system14error_category12std_category10equivalentEiRKSt15error_condition@Base 0.8.7 | - (arch=!armel !armhf)_ZNK5boost6system14error_category12std_category23default_error_conditionEi@Base 0.8.7 | - (arch=!armel !armhf)_ZNK5boost6system14error_category12std_category4nameEv@Base 0.8.7 | - (arch=!armel !armhf)_ZNK5boost6system14error_category12std_category7messageB5cxx11Ei@Base 0.8.7 | +#MISSING: 0.8.7-6# (arch=!armel !armhf)_ZNK5boost6system14error_category12std_category10equivalentERKSt10error_codei@Base 0.8.7 | +#MISSING: 0.8.7-6# (arch=!armel !armhf)_ZNK5boost6system14error_category12std_category10equivalentEiRKSt15error_condition@Base 0.8.7 | +#MISSING: 0.8.7-6# (arch=!armel !armhf)_ZNK5boost6system14error_category12std_category23default_error_conditionEi@Base 0.8.7 | +#MISSING: 0.8.7-6# (arch=!armel !armhf)_ZNK5boost6system14error_category12std_category4nameEv@Base 0.8.7 | +#MISSING: 0.8.7-6# (arch=!armel !armhf)_ZNK5boost6system14error_category12std_category7messageB5cxx11Ei@Base 0.8.7 | (arch=!armel
Bug#961986: lix FTBFS: Error: undefined identifier `FracSec`, did you mean function `fracSec`?
tags 961986 +patch
thanks
Some googling of the error message led me via a few links to an upstream patch
at
https://github.com/Abscissa/SDLang-D/pull/70/commits/90e5bdad1d803a507b34d46c5ecf82cb1feb7cd4
I extracted the commit as a patch, tweaked the paths so it would apply to the
Debian lix package and I was able to get succesful builds in debian sid amd64
and raspbian bullseye-staging
My fix has been uploaded to raspbian, a debdiff is attached to this mail. No
intent to NMU in Debian.
(note: the pull request was squashed and merged and the other commit in the
pull request did not seem relevant, so I used the commit from the pull request
rather than the one from the main repo).
diff -Nru lix-0.9.29/debian/changelog lix-0.9.29/debian/changelog
--- lix-0.9.29/debian/changelog 2019-12-10 08:02:16.0 +
+++ lix-0.9.29/debian/changelog 2020-06-05 22:49:20.0 +
@@ -1,3 +1,10 @@
+lix (0.9.29-1+rpi1) bullseye-staging; urgency=medium
+
+ * Add patch from upstream pull request to fix build with new libphobos
+(Closes: 961986)
+
+ -- Peter Michael Green Fri, 05 Jun 2020 22:49:20
+
+
lix (0.9.29-1) unstable; urgency=medium
* New upstream version. (Closes: #941390)
diff -Nru lix-0.9.29/debian/patches/phobos-2.091.patch
lix-0.9.29/debian/patches/phobos-2.091.patch
--- lix-0.9.29/debian/patches/phobos-2.091.patch1970-01-01
00:00:00.0 +
+++ lix-0.9.29/debian/patches/phobos-2.091.patch2020-06-05
22:48:24.0 +
@@ -0,0 +1,39 @@
+Patch taken from
https://github.com/Abscissa/SDLang-D/pull/70/commits/90e5bdad1d803a507b34d46c5ecf82cb1feb7cd4
+with paths adjusted to apply to the Debian lix package.
+
+commit 90e5bdad1d803a507b34d46c5ecf82cb1feb7cd4
+Author: Steven Schveighoffer
+Date: Fri Mar 20 17:26:58 2020 -0400
+
+Remove FracSec usage if not available in Phobos (2.091+) Fixes #68.
+
+diff --git a/sdlang-d-0.10.4/sdlang-d/src/sdlang/token.d
b/sdlang-d-0.10.4/sdlang-d/src/sdlang/token.d
+index 593746c..074c705 100644
+--- a/sdlang-d-0.10.4/sdlang-d/src/sdlang/token.d
b/sdlang-d-0.10.4/sdlang-d/src/sdlang/token.d
+@@ -24,9 +24,11 @@ struct DateTimeFrac
+ {
+ DateTime dateTime;
+ Duration fracSecs;
+- deprecated("Use fracSecs instead.") {
++ static if(is(FracSec)) {
++ deprecated("Use fracSecs instead.") {
+ @property FracSec fracSec() const { return
FracSec.from!"hnsecs"(fracSecs.total!"hnsecs"); }
+ @property void fracSec(FracSec v) { fracSecs = v.hnsecs.hnsecs;
}
++ }
+ }
+ }
+
+@@ -44,9 +46,11 @@ struct DateTimeFracUnknownZone
+ {
+ DateTime dateTime;
+ Duration fracSecs;
+- deprecated("Use fracSecs instead.") {
++ static if(is(FracSec)) {
++ deprecated("Use fracSecs instead.") {
+ @property FracSec fracSec() const { return
FracSec.from!"hnsecs"(fracSecs.total!"hnsecs"); }
+ @property void fracSec(FracSec v) { fracSecs = v.hnsecs.hnsecs;
}
++ }
+ }
+ string timeZone;
+
diff -Nru lix-0.9.29/debian/patches/series lix-0.9.29/debian/patches/series
--- lix-0.9.29/debian/patches/series2018-12-04 09:55:25.0 +
+++ lix-0.9.29/debian/patches/series2020-06-05 22:45:25.0 +
@@ -1 +1,2 @@
dub-i-dub-i-dub-dub-dub
+phobos-2.091.patch
Processed: re: lix FTBFS: Error: undefined identifier `FracSec`, did you mean function `fracSec`?
Processing commands for cont...@bugs.debian.org: > tags 961986 +patch Bug #961986 [src:lix] lix FTBFS: Error: undefined identifier `FracSec`, did you mean function `fracSec`? Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 961986: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961986 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#934160: Bug#962254: NFS(v4) broken at 4.19.118-2
I've run into a problem which produces the same behavior as bug #934160, but attributed it elsewhere due to other observations. What are the version(s) of the Linux kernel being used on your server and clients? I've confirmed using a 4.9 kernel on a client instead of a 4.19 kernel also works around this issue. In fact one client using a kernel from 4.19.98+1+deb10u1 source doesn't display the issue, but one using 4.19.118+2 source does. This timeframe though doesn't match when you reported the issue. Could be there are several things working together to cause this. I haven't yet tried tried using NFS version 4.1, instead of 4.2. -- (\___(\___(\__ --=> 8-) EHM <=-- __/)___/)___/) \BS (| ehem+sig...@m5p.com PGP 87145445 |) / \_CS\ | _ -O #include O- _ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
Bug#950131: marked as pending in mixxx
Control: tag -1 pending Hello, Bug #950131 in mixxx 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/multimedia-team/mixxx/-/commit/b6fd161644fc6ff83db7d4f960f1f80592595375 debian/patches/: patchset updated against v2.2.4 - 0005-scons-3.patch dropped (applied upstream) - 0005-remove_inappropriate_i386_flags.patch added Closes: #950131 (this message was generated automatically) -- Greetings https://bugs.debian.org/950131
Processed: Bug#950131 marked as pending in mixxx
Processing control commands: > tag -1 pending Bug #950131 [src:mixxx] mixxx: Baseline violation on i386 Added tag(s) pending. -- 950131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960791: marked as done (firmware-b43-installer: when language is not English, install fails. Script attempts to parse localized output)
Your message dated Fri, 05 Jun 2020 22:21:16 + with message-id and subject line Bug#960791: fixed in b43-fwcutter 1:019-6 has caused the Debian Bug report #960791, regarding firmware-b43-installer: when language is not English, install fails. Script attempts to parse localized output 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.) -- 960791: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firmware-b43-installer Version: 1:019-5 Severity: normal Tags: l10n Dear Maintainer, when installing or removing firmware with a non-US locale, the following happens: dpkg -P b43-fwcutter firmware-b43legacy-installer firmware-b43-installer (Lese Datenbank ... 234244 Dateien und Verzeichnisse sind derzeit installiert.) Entfernen von firmware-b43legacy-installer (1:019-5) ... /var/lib/dpkg/info/firmware-b43legacy-installer.prerm: Deleting installed firmware... rm: das Entfernen von 'passt' ist nicht möglich: Datei oder Verzeichnis nicht gefunden rm: das Entfernen von 'passt' ist nicht möglich: Datei oder Verzeichnis nicht gefunden rm: das Entfernen von 'passt' ist nicht möglich: Datei oder Verzeichnis nicht gefunden rm: das Entfernen von 'passt' ist nicht möglich: Datei oder Verzeichnis nicht gefunden rm: das Entfernen von 'passt' ist nicht möglich: Datei oder Verzeichnis nicht gefunden rm: das Entfernen von 'passt' ist nicht möglich: Datei oder Verzeichnis nicht gefunden [] and the action fails (purge in this case). The word "passt" is a german word. It should not be parsed. Version info: pi b43-fwcutter 1:019-5 amd64utility for extracting Broadcom 43xx firmware pF firmware-b43-installer 1:019-5 all firmware installer for the b43 driver pF firmware-b43legacy-installer 1:019-5 all firmware installer for the b43legacy driver Solution: Switch locale, remove catalog file from /lib/firmware/b43 and re-do install/remove -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.6.13-towo.1-siduction-amd64 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8), LANGUAGE=de_AT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages firmware-b43-installer depends on: pn b43-fwcutter ii bzip21.0.8-2 ii ca-certificates 20190110 ii wget 1.20.3-1+b2 firmware-b43-installer recommends no packages. firmware-b43-installer suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: b43-fwcutter Source-Version: 1:019-6 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of b43-fwcutter, 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. Andreas Beckmann (supplier of updated b43-fwcutter package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Jun 2020 00:04:21 +0200 Source: b43-fwcutter Architecture: source Version: 1:019-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 956858 958566 960279 960791 962052 Changes: b43-fwcutter (1:019-6) unstable; urgency=medium . * QA upload. * Install classic (5.100.138) firmware for cards working badly with 6.x, thanks to Gert van de Kraats. (Closes: #958566, #960279) * Add dependency on pciutils for lspci. * Run firmware removal commands under LC_ALL=C. (Closes: #960791) * Do not fail while removing no longer existing files. (Closes: #956858) * Updated Spanish debconf translations thanks to Camaleón. (Closes: #962052) * Simplify install rules. * Set Rules-Requires-Root: no. * Switch to debhelper-compat (= 13). * Bump Standards-Version 4.5.0 (no changes). Checksums-Sha1: 9283d2f5c02f9d9068a4f3f95d57d77c73b616a8 2117 b43-fwcutter_019-6.dsc
Bug#958566: marked as done (b43-fwcutter: Wifi Broadcom at BCM4311 very slow after installing new firmware-b43-installer_019-5_all.deb)
Your message dated Fri, 05 Jun 2020 22:21:15 + with message-id and subject line Bug#958566: fixed in b43-fwcutter 1:019-6 has caused the Debian Bug report #958566, regarding b43-fwcutter: Wifi Broadcom at BCM4311 very slow after installing new firmware-b43-installer_019-5_all.deb 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.) -- 958566: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958566 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: b43-fwcutter Version: 1:019-5 Severity: grave Justification: renders package unusable Dear Maintainer, After the recent upgrade to package firmware-b43-installer_019-5_all wifi connection was extremely slow causing e.g. timeouts at Firefox. This package contains firmware version 6.30.163.46 To solve the problem I had to reinstall firmware-b43-installer_019-4_all with firmware version 5.100.138. Probably the new version is not compatible network controller BCM4311. 0c:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM4311 802.11a/b/g [14e4:4312] (rev 01) Subsystem: Dell Wireless 1490 Dual Band WLAN Mini-Card [1028:0007] Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at dfdfc000 (32-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 2 Capabilities: [58] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [d0] Express Legacy Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Virtual Channel Kernel driver in use: b43-pci-bridge Kernel modules: ssb -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 5.5.0-1-686-pae (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages b43-fwcutter depends on: ii debconf [debconf-2.0] 1.5.73 ii libc6 2.30-4 b43-fwcutter recommends no packages. b43-fwcutter suggests no packages. -- debconf information: b43-fwcutter/install-unconditional: true --- End Message --- --- Begin Message --- Source: b43-fwcutter Source-Version: 1:019-6 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of b43-fwcutter, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated b43-fwcutter package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 06 Jun 2020 00:04:21 +0200 Source: b43-fwcutter Architecture: source Version: 1:019-6 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Andreas Beckmann Closes: 956858 958566 960279 960791 962052 Changes: b43-fwcutter (1:019-6) unstable; urgency=medium . * QA upload. * Install classic (5.100.138) firmware for cards working badly with 6.x, thanks to Gert van de Kraats. (Closes: #958566, #960279) * Add dependency on pciutils for lspci. * Run firmware removal commands under LC_ALL=C. (Closes: #960791) * Do not fail while removing no longer existing files. (Closes: #956858) * Updated Spanish debconf translations thanks to Camaleón. (Closes: #962052) * Simplify install rules. * Set Rules-Requires-Root: no. * Switch to debhelper-compat (= 13). * Bump Standards-Version 4.5.0 (no changes). Checksums-Sha1: 9283d2f5c02f9d9068a4f3f95d57d77c73b616a8 2117 b43-fwcutter_019-6.dsc 2f0450aeda0b894d5848bb25d507c74e1f600365 19596 b43-fwcutter_019-6.debian.tar.xz b33771ba7da391a834a67bcc3f5a231e3b18c764 5158 b43-fwcutter_019-6_source.buildinfo Checksums-Sha256: 1d69a12a6b5f2c37ab9290d45a6d36c8d4d753da04b40f5c862aa9a5fc5c9bb1 2117 b43-fwcutter_019-6.dsc cf0919df427c9b7e4cbc9292877201bf8d578822984c5ae17b5d7e6319919940 19596 b43-fwcutter_019-6.debian.tar.xz a41f8675eaa805a518e4b91bdc4bd30f7f1d07e9890c130ab0febb1f056e3b92 5158
Bug#956710: marked as done (abiword: Please witch to enchant-2 instead of enchant(1))
Your message dated Fri, 05 Jun 2020 22:03:34 +
with message-id
and subject line Bug#956710: fixed in abiword 3.0.2-11
has caused the Debian Bug report #956710,
regarding abiword: Please witch to enchant-2 instead of enchant(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.)
--
956710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: abiword
Version: 3.0.2-10
Severity: important
Tags: patch
Control: block 947979 by -1
Hello,
Could you please switch from enchant(1) to the enchant-2 library?
We are trying to get rid of enchant(1) for the bullseye release.
The attached patch should fix this
Kind regards,
Laurent Bigonville
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1,
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.5.0-1-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8),
LANGUAGE=fr_BE:fr (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy
diff -Nru abiword-3.0.2/debian/control abiword-3.0.2/debian/control
--- abiword-3.0.2/debian/control2020-04-02 14:46:29.0 +0200
+++ abiword-3.0.2/debian/control2020-04-14 15:22:12.0 +0200
@@ -13,7 +13,7 @@
libchamplain-gtk-0.12-dev,
libebook1.2-dev (>= 3.8.5),
libical-dev (>= 3.0),
- libenchant-dev,
+ libenchant-2-dev,
libfribidi-dev,
libgcrypt20-dev,
libgirepository1.0-dev,
diff -Nru abiword-3.0.2/debian/patches/enchant2.patch
abiword-3.0.2/debian/patches/enchant2.patch
--- abiword-3.0.2/debian/patches/enchant2.patch 1970-01-01 01:00:00.0
+0100
+++ abiword-3.0.2/debian/patches/enchant2.patch 2020-04-14 15:24:39.0
+0200
@@ -0,0 +1,40 @@
+--- a/configure.ac
b/configure.ac
+@@ -94,7 +94,7 @@ xp_pkgs="
+ "
+
+ # optional deps
+-enchant_req='enchant >= 1.2.0'
++enchant_req='enchant-2 >= 1.2.0'
+ gio_req='gio-2.0'
+ goffice_req='libgoffice-0.10 >= 0.10.0'
+
+--- a/src/af/xap/xp/enchant_checker.cpp
b/src/af/xap/xp/enchant_checker.cpp
+@@ -127,7 +127,7 @@ EnchantChecker::_suggestWord (const UT_U
+ pvSugg->addItem (ucszSugg);
+ }
+
+- enchant_dict_free_suggestions (m_dict, suggestions);
++ enchant_dict_free_string_list (m_dict, suggestions);
+ }
+
+ return pvSugg;
+@@ -139,7 +139,7 @@ bool EnchantChecker::addToCustomDict (co
+
+ if (word && len) {
+ UT_UTF8String utf8 (word, len);
+- enchant_dict_add_to_personal (m_dict, utf8.utf8_str(),
utf8.byteLength());
++ enchant_dict_add (m_dict, utf8.utf8_str(), utf8.byteLength());
+ return true;
+ }
+ return false;
+@@ -150,7 +150,7 @@ bool EnchantChecker::isIgnored (const UT
+ UT_return_val_if_fail (m_dict, false);
+
+ UT_UTF8String ignore (toCorrect, toCorrectLen);
+- return enchant_dict_is_in_session (m_dict, ignore.utf8_str(),
ignore.byteLength()) != 0;
++ return enchant_dict_is_added (m_dict, ignore.utf8_str(),
ignore.byteLength()) != 0;
+ }
+
+ void EnchantChecker::ignoreWord (const UT_UCSChar *toCorrect, size_t
toCorrectLen)
diff -Nru abiword-3.0.2/debian/patches/series
abiword-3.0.2/debian/patches/series
--- abiword-3.0.2/debian/patches/series 2020-04-02 14:46:29.0 +0200
+++ abiword-3.0.2/debian/patches/series 2020-04-14 15:21:47.0 +0200
@@ -11,3 +11,4 @@
libical3.diff
build-Don-t-check-for-libecal.patch
git_build_fix.patch
+enchant2.patch
--- End Message ---
--- Begin Message ---
Source: abiword
Source-Version: 3.0.2-11
Done: Jonas Smedegaard
We believe that the bug you reported is fixed in the latest version of
abiword, 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 956...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jonas Smedegaard (supplier of updated abiword package)
(This message was generated automatically at their request; if you
believe that there is a
Bug#962179: marked as done (wfmath FTBFS on 32bit: symbol differences)
Your message dated Fri, 05 Jun 2020 21:21:32 + with message-id and subject line Bug#962179: fixed in wfmath 1.0.2+dfsg1-8 has caused the Debian Bug report #962179, regarding wfmath FTBFS on 32bit: symbol differences 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.) -- 962179: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962179 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wfmath Version: 1.0.2+dfsg1-7 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=wfmath=sid ... dh_makeshlibs -a -a dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libwfmath-1.0-1v5/DEBIAN/symbols doesn't match completely debian/libwfmath-1.0-1v5.symbols --- debian/libwfmath-1.0-1v5.symbols (libwfmath-1.0-1v5_1.0.2+dfsg1-7_i386) +++ dpkg-gensymbolsSnl7JC 2020-06-04 01:44:11.048846158 + @@ -49,6 +49,7 @@ _ZN6WFMath13_ScaleEpsilonEfff@Base 1.0.0 _ZN6WFMath14BoundingSphereILi2ESt6vectorEENS_4BallIXT_EEERKT0_INS_5PointIXT_EEESaIS6_EE@Base 0.3.11 _ZN6WFMath14BoundingSphereILi3ESt6vectorEENS_4BallIXT_EEERKT0_INS_5PointIXT_EEESaIS6_EE@Base 1.0.0 + _ZN6WFMath14SloppyDistanceILi3EEEfRKNS_5PointIXT_EEES4_@Base 1.0.2+dfsg1-7 _ZN6WFMath14_ReadCoordListERSiPfi@Base 0.3.11 _ZN6WFMath15SquaredDistanceILi2EEEfRKNS_5PointIXT_EEES4_@Base 0.3.11 _ZN6WFMath15SquaredDistanceILi3EEEfRKNS_5PointIXT_EEES4_@Base 0.3.11 @@ -607,10 +608,10 @@ (optional=inline)_ZN6WFMath9_miniball5BasisILi3EE4pushERKNS0_13Wrapped_arrayILi3EEE@Base 1.0.0 (optional=inline)_ZN6WFMath9_miniball8MiniballILi2EE13move_to_frontESt14_List_iteratorINS0_13Wrapped_arrayILi2@Base 0.3.11 _ZN6WFMath9_miniball8MiniballILi2EE6mtf_mbESt14_List_iteratorINS0_13Wrapped_arrayILi2@Base 0.3.11 - (optional=GCC10_added)_ZN6WFMath9_miniball8MiniballILi2EE8pivot_mbESt14_List_iteratorINS0_13Wrapped_arrayILi2@Base 1.0.2 +#MISSING: 1.0.2+dfsg1-7# (optional=GCC10_added)_ZN6WFMath9_miniball8MiniballILi2EE8pivot_mbESt14_List_iteratorINS0_13Wrapped_arrayILi2@Base 1.0.2 (optional=inline)_ZN6WFMath9_miniball8MiniballILi3EE13move_to_frontESt14_List_iteratorINS0_13Wrapped_arrayILi3@Base 1.0.0 _ZN6WFMath9_miniball8MiniballILi3EE6mtf_mbESt14_List_iteratorINS0_13Wrapped_arrayILi3@Base 1.0.0 - (optional=GCC10_added)_ZN6WFMath9_miniball8MiniballILi3EE8pivot_mbESt14_List_iteratorINS0_13Wrapped_arrayILi3@Base 1.0.2 +#MISSING: 1.0.2+dfsg1-7# (optional=GCC10_added)_ZN6WFMath9_miniball8MiniballILi3EE8pivot_mbESt14_List_iteratorINS0_13Wrapped_arrayILi3@Base 1.0.2 _ZN6WFMathdVILi2EEERNS_6VectorIXT_EEES3_f@Base 0.3.11 _ZN6WFMathdVILi3EEERNS_6VectorIXT_EEES3_f@Base 0.3.11 _ZN6WFMathdvILi2EEENS_6VectorIXT_EEERKS2_f@Base 0.3.11 @@ -1014,9 +1015,11 @@ (regex|optional=inline)_ZNSt6vectorIfSaIfEE17_M_default_appendE[mj]@Base 1.0.2 _ZNSt6vectorIfSaIfEE17_M_realloc_insertIJRKfEEEvN9__gnu_cxx17__normal_iteratorIPfS1_EEDpOT_@Base 1.0.2 (optional=inline)_ZNSt6vectorIfSaIfEE6insertEN9__gnu_cxx17__normal_iteratorIPKfS1_EERS4_@Base 1.0.2 - _ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIflfNS0_5__ops15_Iter_less_iterEEvT_T0_SA_T1_T2_@Base 1.0.2 + _ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIfifNS0_5__ops15_Iter_less_iterEEvT_T0_SA_T1_T2_@Base 1.0.2+dfsg1-7 +#MISSING: 1.0.2+dfsg1-7# _ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIflfNS0_5__ops15_Iter_less_iterEEvT_T0_SA_T1_T2_@Base 1.0.2 _ZSt16__insertion_sortIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIfNS0_5__ops15_Iter_less_iterEEvT_S9_T0_@Base 1.0.2 - _ZSt16__introsort_loopIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIflNS0_5__ops15_Iter_less_iterEEvT_S9_T0_T1_@Base 1.0.2 + _ZSt16__introsort_loopIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIfiNS0_5__ops15_Iter_less_iterEEvT_S9_T0_T1_@Base 1.0.2+dfsg1-7 +#MISSING: 1.0.2+dfsg1-7# _ZSt16__introsort_loopIN9__gnu_cxx17__normal_iteratorIPfSt6vectorIfSaIflNS0_5__ops15_Iter_less_iterEEvT_S9_T0_T1_@Base 1.0.2 _ZTIN6WFMath10ParseErrorE@Base 0.3.11 _ZTIN6WFMath15ColinearVectorsILi2EEE@Base 0.3.11 _ZTIN6WFMath15ColinearVectorsILi3EEE@Base 0.3.11 dh_makeshlibs: error: failing due to earlier errors make: *** [debian/rules:7: binary-arch] Error 25 --- End Message --- --- Begin Message --- Source: wfmath Source-Version: 1.0.2+dfsg1-8 Done: Olek Wojnar We believe that the bug you reported is
Bug#788319: marked as done ([yui3] Some sources are not included in your package)
Your message dated Fri, 05 Jun 2020 21:22:29 + with message-id and subject line Bug#962167: Removed package(s) from unstable has caused the Debian Bug report #788319, regarding [yui3] Some sources are not included in your package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 788319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:yui3 Version: 3.5.1-1 user: lintian-ma...@debian.org usertags: source-is-missing severity: serious X-Debbugs-CC: ftpmas...@debian.org Hi, your package includes some files that seem to lack sources in prefered forms of modification: build/io-xdr/io.swf build/uploader/assets/flashuploader.swf build/uploader-deprecated/assets/uploader.swf api/assets/vendor/prettify/prettify-min.js docs/assets/panel/vendor/prettify/prettify-min.js Please override false positive with comment build/text-data-wordbreak/text-data-wordbreak-debug.js (long line due to enumeration) build/datatype-date-format/lang/*.js (enumeration) build/calendar/lang/* (enumeration) build/calendar-base/lang/* (enumeration) According to Debian Free Software Guidelines [1] (DFSG) #2: "The program must include source code, and must allow distribution in source code as well as compiled form." In some cases this could also constitute a license violation for some copyleft licenses such as the GNU GPL. (While sometimes the licence allows not to ship the source, the DFSG always mandates source code.) In order to solve this problem, you could: 1. repack the origin tarball and add the missing source files to it. 2 add the source files to "debian/missing-sources" directory. Both way satisfy the requirement to ship all source code. The second option might be preferable due to the following reasons [2]: - Upstream can do it too and you could even supply a patch to them, thus full filling our social contract [3], see particularly §2. - If source and non-source are in different locations, ftpmasters may miss the source and (needlessly) reject the package. - The source isn't duplicated in every .diff.gz/.debian.tar.* (though this only really matters for larger sources). You could also ask debian...@lists.debian.org or #debian-qa for more guidance. [1] https://www.debian.org/social_contract.en.html#guidelines [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736873#8 [3] https://www.debian.org/social_contract signature.asc Description: This is a digitally signed message part. --- End Message --- --- Begin Message --- Version: 3.5.1-1.1+rm Dear submitter, as the package yui3 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/962167 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---
Bug#959480: marked as done (FTBFS with Boost 1.71)
Your message dated Fri, 05 Jun 2020 21:03:48 +
with message-id
and subject line Bug#959480: fixed in frogatto 1.3.1+dfsg-5
has caused the Debian Bug report #959480,
regarding FTBFS with Boost 1.71
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.)
--
959480: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959480
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: frogatto
Version: 1.3.1+dfsg-4
Severity: wishlist
Tags: patch
User: team+bo...@tracker.debian.org
Usertags: boost1.71
Dear Maintainer,
your package fails to build with boost1.71. You can find a build log
attached. If you want to attempt the build yourself, an updated version
of boost-defaults which brings in boost1.71 dependencies can be found
adding this line to your sources.list file:
deb https://people.debian.org/~gio/reprepro gio main
This bug has severity whishlist for the moment, but it will raised to RC
as soon as version 1.71 of Boost is promoted to default.
More specifically, your package fails building because it uses a retired
API from Boost.Asio. The attached patch should fix the bug.
Thanks and all the best, Giovanni.
--
Giovanni Mascellani
Postdoc researcher - Université Libre de Bruxelles
Index: frogatto-1.3.1+dfsg/src/http_server.cpp
===
--- frogatto-1.3.1+dfsg.orig/src/http_server.cpp
+++ frogatto-1.3.1+dfsg/src/http_server.cpp
@@ -31,7 +31,7 @@ web_server::web_server(boost::asio::io_s
void web_server::start_accept()
{
- socket_ptr socket(new tcp::socket(acceptor_.get_io_service()));
+ socket_ptr socket(new tcp::socket(acceptor_.get_executor()));
acceptor_.async_accept(*socket, boost::bind(_server::handle_accept, this, socket, boost::asio::placeholders::error));
}
frogatto.log.gz
Description: application/gzip
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: frogatto
Source-Version: 1.3.1+dfsg-5
Done: Martin Quinson
We believe that the bug you reported is fixed in the latest version of
frogatto, 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 959...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Martin Quinson (supplier of updated frogatto 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, 05 Jun 2020 22:23:41 +0200
Source: frogatto
Architecture: source
Version: 1.3.1+dfsg-5
Distribution: unstable
Urgency: low
Maintainer: Dmitry E. Oboukhov
Changed-By: Martin Quinson
Closes: 959480
Changes:
frogatto (1.3.1+dfsg-5) unstable; urgency=low
.
* New patch to fix a FTBFS with Boost 1.71 (Closes: #959480).
Thanks Giovanni Mascellani for the report and the patch.
* Trim trailing whitespace.
* Bump debhelper from deprecated 9 to 10.
* Change priority extra to priority optional.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
Checksums-Sha1:
364bbc3b61d7b16e7f875c86ce6dca9e091f0224 2309 frogatto_1.3.1+dfsg-5.dsc
646848fd8370f7c051b21ddec6b2d1b83d78d940 10504
frogatto_1.3.1+dfsg-5.debian.tar.xz
6e84c7df502b5c51701af85a20244c511cf5f2d4 11084
frogatto_1.3.1+dfsg-5_amd64.buildinfo
Checksums-Sha256:
2ec033f02b66c9a2578f42f8c06970a7228cac8d75ae766c150c4dd6f6751de4 2309
frogatto_1.3.1+dfsg-5.dsc
c7ad0797b4d0debdc57f5314ad00d5380577ba4dff63cfb05936d280ab3419c8 10504
frogatto_1.3.1+dfsg-5.debian.tar.xz
2af6bf16e21f42c099ec953f7cdb3b66987781211706a8ac7f209ff71a28ce6a 11084
frogatto_1.3.1+dfsg-5_amd64.buildinfo
Files:
0b981d57a29fcb60662111bae3c8277d 2309 contrib/games optional
frogatto_1.3.1+dfsg-5.dsc
0e4808dae055c7b09a8e00c6baf28132 10504 contrib/games optional
frogatto_1.3.1+dfsg-5.debian.tar.xz
0231c351e3e95b0ac17f69614df1f529 11084 contrib/games optional
frogatto_1.3.1+dfsg-5_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJIBAEBCgAyFiEET76cTupS7xPVQWYSmL2XJE9zvqcFAl7arngUHG1xdWluc29u
QGRlYmlhbi5vcmcACgkQmL2XJE9zvqeRyhAAhgi2AhNmGyjixmkBJPwJkOZot3ZU
EHX0DiZREw+kFnB4dS6OdhtgonlHPP5vNoGWXUIopcH+HXcTyA5IJ2fKmIF/WJB2
aumazKS1OfL1Vgycv9RqpwmK4DuRfGq0tEKmz/UdG8Ph3pSXQ0dSKw20FLJ/q4X4
Bug#962299: marked as done (frogatto-data: Depends on removed ttf-dejavu package)
Your message dated Fri, 05 Jun 2020 20:48:45 + with message-id and subject line Bug#962299: fixed in frogatto-data 1.3.1+dfsg-2 has caused the Debian Bug report #962299, regarding frogatto-data: Depends on removed ttf-dejavu package to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 962299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962299 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: frogatto-data Severity: grave Version: 1.3.1+dfsg-1 Tags: sid bullseye X-Debbugs-CC: mquin...@debian.org vch...@debian.org Dear Debian frogatoo-data maintainers, Your package depends on package ttf-dejavu, which has been a transitional package for 7 years and was just removed in favor of fonts-dejavu. Please properly update your package dependencies and remove any hardcoded references to ttf-dejavu in the source code. -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: frogatto-data Source-Version: 1.3.1+dfsg-2 Done: Martin Quinson We believe that the bug you reported is fixed in the latest version of frogatto-data, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Martin Quinson (supplier of updated frogatto-data 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, 05 Jun 2020 22:13:53 +0200 Source: frogatto-data Architecture: source Version: 1.3.1+dfsg-2 Distribution: unstable Urgency: low Maintainer: Dmitry E. Oboukhov Changed-By: Martin Quinson Closes: 794229 962299 Changes: frogatto-data (1.3.1+dfsg-2) unstable; urgency=low . [ Vincent Cheng ] * Install high resolution icon file. (Closes: #794229) * Migrate dependency from old transitional ttf-dejavu-core package to fonts-dejavu-core instead. (Closes: #962299) * Update email address. . [ Debian Janitor ] * Trim trailing whitespace. * Use secure URI in Homepage field. * Bump debhelper from old 9 to 10. * Change priority extra to priority optional. * Update Vcs-* headers to use salsa repository. . [ Martin Quinson ] * Review the changes of the Janitor, and upload to unstable. Checksums-Sha1: b748a8f6735dc565c2f29b6bab60221c51632fe9 2097 frogatto-data_1.3.1+dfsg-2.dsc d0f5d131eedb23e2d1d1df557953596e2854d524 2968 frogatto-data_1.3.1+dfsg-2.debian.tar.xz f4dd1b1c06ba9543f670a1dcae921d7e2ffee0d1 5415 frogatto-data_1.3.1+dfsg-2_amd64.buildinfo Checksums-Sha256: 9a4955ba17e16d64aadd954c473577fa6bc7f0e867726d7620e4c1ba521087f5 2097 frogatto-data_1.3.1+dfsg-2.dsc 0f2b34610feeeaa2618c06cce9bc7fe7f7f41baf4c9bbbdd06ea94dd5d3bf84f 2968 frogatto-data_1.3.1+dfsg-2.debian.tar.xz 5ab7c7fc3759a7bdeee6529fa9fe6ad0778634fc2bd457a2f93d8925e39be620 5415 frogatto-data_1.3.1+dfsg-2_amd64.buildinfo Files: 09659207081bfcb78eb163ef38dbd22d 2097 non-free/games optional frogatto-data_1.3.1+dfsg-2.dsc e959f1b51259ff67c876d534066d688a 2968 non-free/games optional frogatto-data_1.3.1+dfsg-2.debian.tar.xz 7353035c10a8dc465c3c7811f69eab19 5415 non-free/games optional frogatto-data_1.3.1+dfsg-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEET76cTupS7xPVQWYSmL2XJE9zvqcFAl7aqjUUHG1xdWluc29u QGRlYmlhbi5vcmcACgkQmL2XJE9zvqezdg/9ESCE55GOvZJYUPBwrt/8eCqHg2E5 swRTISkHYncMi3epWxCKapwTNreahJaABn1dus191plzNE79vggxhwoyMM61G+5Z dWHaMOMHbrJheFzUBur/jobduQtQ3DBB5wBDzpugm0sunvgwAH0JTE06Ph9NMgn9 4WqjZQD7Rtwh0CpyHQGPoVicssrecPslgQijRtnNs0Ic2HTe64b37rsToZKOtPzg GXoOB0OElcCa7ZgQy9NviscQMEXCqzGh05n1OsB1lscxrOQoX4kyE5IMzwhpByG4 saWO5Leh2UTKrOHnhVVd6/aNM0oY3D+Y1ChXO+yVL/R7c4QNQlMbUOusRMIoV4Nb EglYobtKIKrPpDpI9VjYew4ehCfdPb2G9KVD/vsLRyM0pfoit3vNRvB0JUeADIZK lpOZeDnZWaDI2ka2AUd2cTVGjsqqgUPjR540TX2G0aylPWpTLAs7+u0H+EJzFMbL pG0v+BGZC1sGGKJPhuerfeHZ8CRFdQV+YqIJm1ndmJkz2XZUuxy4qhzAonq6ohPa EeJYXOd1MAhzQvWJ6xgOtS4bVtjVtUlmoyqsuqgIVtHi3mwkZS4t+IPYaw4qVRwv qLLGPfAtW6qyNTJBhKjGoxyRyfpFlQ5TTc8x+3ZJcAX/vkQ3tTIBKDCFkYIpGure fIGCimddEuxRXZ0= =8jP0 -END PGP SIGNATURE End Message ---
Bug#962299: frogatto-data: Depends on removed ttf-dejavu package
Source: frogatto-data Severity: grave Version: 1.3.1+dfsg-1 Tags: sid bullseye X-Debbugs-CC: mquin...@debian.org vch...@debian.org Dear Debian frogatoo-data maintainers, Your package depends on package ttf-dejavu, which has been a transitional package for 7 years and was just removed in favor of fonts-dejavu. Please properly update your package dependencies and remove any hardcoded references to ttf-dejavu in the source code. -- Regards, Boyuan Yang signature.asc Description: This is a digitally signed message part
Bug#962300: dmraid: dmraid fails do install in a debootstrapped chroot
Source: dmraid Severity: grave Dear Maintainer, On an amd64 host I created armel chroot with qemu-debootstrap. I attempted to install dracut which pulled dmraid and other packages. After installing all packages but dmraid apt install shows following messages (with set -x added to dmraid.postinst) --8<---cut here---start->8--- # LANG=C apt install dracut Reading package lists... Done Building dependency tree Reading state information... Done dracut is already the newest version (048+80-2). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up dmraid (1.0.0.rc16-8) ... + command -v update-initramfs + udevadm trigger --subsystem-match=block --action=change Failed to scan devices: No such file or directory dpkg: error processing package dmraid (--configure): installed dmraid package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: dmraid E: Sub-process /usr/bin/dpkg returned an error code (1) --8<---cut here---end--->8--- I'd expect the package to install regardles of available devices. -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: armel Kind regards, -- Łukasz Stelmach Samsung R Institute Poland Samsung Electronics signature.asc Description: PGP signature
Bug#961560: marked as done (yade: Build-Depends-Indep on cruft package texlive-generic-extra)
Your message dated Fri, 05 Jun 2020 19:21:00 + with message-id and subject line Bug#961560: fixed in yade 2020.01a-8 has caused the Debian Bug report #961560, regarding yade: Build-Depends-Indep on cruft package texlive-generic-extra 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.) -- 961560: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961560 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yade Version: 2020.01a-7 Severity: serious As the subject says: src:yade has a Build-Depends-Indep on texlive-generic-extra | texlive-plain-generic where texlive-generic-extra is no longer built by the texlive-extra source package. That will cause issues trying to build using sbuild on a testing chroot, since sbuild forces the first alternative to be used. -- Daniel Schepler --- End Message --- --- Begin Message --- Source: yade Source-Version: 2020.01a-8 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of yade, 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 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated yade 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, 05 Jun 2020 21:11:47 +0200 Source: yade Architecture: source Version: 2020.01a-8 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Anton Gladky Closes: 961560 Changes: yade (2020.01a-8) unstable; urgency=medium . * [3091434] Remove texlive-generic-extra from build-depends. (Closes: #961560) * [114d383] Set compat level 13 * [30a1dcf] Install some files in usr/share/doc Checksums-Sha1: 45dc08d627769062d93955d8a5aa8994231fdba9 3204 yade_2020.01a-8.dsc 96707200df33535457228f3b8a0e2729adb97f01 23048 yade_2020.01a-8.debian.tar.xz 0c265ebdf1bda0793d108e5310c3a53ae0dc2be3 23442 yade_2020.01a-8_source.buildinfo Checksums-Sha256: 27b06dfc04c588475b0582da31c4f59008d2ec6937f42a38b34f430bc796 3204 yade_2020.01a-8.dsc f4d37fc662ec8f3a9ba07b5f5120c55a8cc109f11ab64e4468529d7cc9bc1e37 23048 yade_2020.01a-8.debian.tar.xz ed200dc4270b225c544b05372aa70a746554ccefd5a4d166fee5298653f73a2d 23442 yade_2020.01a-8_source.buildinfo Files: 7caa1d635dd1c8548a851302b993f78f 3204 science optional yade_2020.01a-8.dsc 31d253c34f1c93584967af010e38d367 23048 science optional yade_2020.01a-8.debian.tar.xz 8118c8c4eddc7f21d80a817ff848b831 23442 science optional yade_2020.01a-8_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAl7amRAACgkQ0+Fzg8+n /wbLSBAAi3ki57v9NGJRmwXBVX+7pogY6/zPwzYficf9Ei5FZVqf90hhqktMH68q KmhhGhOc1l5L8W5WhVj1VDos8JW7c/myFajQ7laR3jvWJAU/bnf9jxo63zCo7sa4 AcZ1dOUxde1n33+kxx22H3/IlBDK+R4BauwcT9yFQPmrqL+Ov8MaaJbyibL9NjNt I18VdELzNR7tHsvijoE2lZvJoMioRTvIcEFKAWRPQZiuN8kcDxmQzwJUccFljH2Z vem7wPEXblLKuIRTnlGcp2nwdlOJHLWWAuXiSCQtbiRw2NOnpSmRvxOUU2QJVGDp HSDmE+O61OKYY5o/O1PzidnG6WT1CEU+F/7gDWYBPCz9hi3UzTnp4hPZBaGFk8fY 9ytVqogwklGG778DRYKCn1PGd+IZE6EVhQmTCubdoUc82bJzoJxAhjA0Qgn7AhP8 05n40eHXE6UAttjOYA3M/lijzuqg4pKlp7AkTW+Fkz2y6EdngYUc8IydJqDau0OL GJFH1rY46ITjPaxETJNuAxz3n2gv1uEq5RZtbp0AcR2/FSQoELPYLuDjWaMdusBJ +rh5BrpVEux8J4q8l4baiV1kEEx58/wVj3Jhduvb3TCYj4B0NuFXJDDxuxOzbAng hXIznx7IyXXbf0aK/avs2XUGDhIMtss2YNtIqPpXuJ8TG0SPh54= =oQ4p -END PGP SIGNATURE End Message ---
Bug#962081: gnucobol: Failing autopkgtest scripts should report what went wrong
On 05 Jun 2020 19:02, Petter Reinholdtsen wrote: > > I discovered what the problem is. The test [ $res ] do not work the way > you want it to. It need to compare with 0, like this: Which is kind of strange, and makes autopkgtest very hard to use since this works fine when run locally like so: # cd # autopkgtest -- null Everything passes when run this way. Easy fix now that you've pointed it out, but passing strange. > diff --git a/debian/tests/test01 b/debian/tests/test01 > index 1c0d63f..73e1fac 100755 > --- a/debian/tests/test01 > +++ b/debian/tests/test01 > @@ -1,4 +1,5 @@ > #!/bin/sh > + > cd debian/tests > > echo "info: compiling" > @@ -7,7 +8,7 @@ echo "info: compiling" > echo "info: running" > cmp -s test01.exp $AUTOPKGTEST_TMP/test01.act > res=$? > -if [ $res ] ; then > +if [ 0 = $res ] ; then > echo "success: test01 produced proper results" > else > echo "error: test01 did not produce proper results" > diff --git a/debian/tests/test02 b/debian/tests/test02 > index fb85d2e..cb4359d 100755 > --- a/debian/tests/test02 > +++ b/debian/tests/test02 > @@ -7,7 +7,7 @@ echo "info: compiling" > echo "info: running" > cmp -s test02.exp $AUTOPKGTEST_TMP/test02.act > res=$? > -if [ $res ] ; then > +if [ 0 == $res ] ; then > echo "success: test02 produced proper results" > else > echo "error: test02 did not produce proper results" > diff --git a/debian/tests/test03 b/debian/tests/test03 > index c028d8b..07d679c 100755 > --- a/debian/tests/test03 > +++ b/debian/tests/test03 > @@ -7,7 +7,7 @@ echo "info: compiling" > echo "info: running" > cmp -s test03.exp $AUTOPKGTEST_TMP/test03.act > res=$? > -if [ $res ] ; then > +if [ 0 == $res ] ; then > echo "success: test03 produced proper results" > else > echo "error: test03 did not produce proper results" > diff --git a/debian/tests/test04 b/debian/tests/test04 > index fd2a6ad..ee31d4a 100755 > --- a/debian/tests/test04 > +++ b/debian/tests/test04 > @@ -7,7 +7,7 @@ echo "info: compiling" > echo "info: running" > cmp -s test04.exp t$AUTOPKGTEST_TMP/est04.act > res=$? > -if [ $res ] ; then > +if [ 0 == $res ] ; then > echo "success: test04 produced proper results" > else > echo "error: test04 did not produce proper results" > > -- > Happy hacking > Petter Reinholdtsen > -- Ciao, al -- Al Stone Debian Developer E-mail: a...@ahs3.nethttp://www.debian.org a...@debian.org --
Bug#961509: marked as done (libxine2-bin: missing Breaks+Replaces: libxine2-doc (<< 1.2.10))
Your message dated Fri, 05 Jun 2020 18:50:15 + with message-id and subject line Bug#961509: fixed in xine-lib-1.2 1.2.10-3 has caused the Debian Bug report #961509, regarding libxine2-bin: missing Breaks+Replaces: libxine2-doc (<< 1.2.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.) -- 961509: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961509 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libxine2-bin Version: 1.2.10-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other packages files without declaring a Breaks+Replaces relation. See policy 7.6 at https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces >From the attached log (scroll to the bottom...): Preparing to unpack .../libxine2-bin_1.2.10-2_amd64.deb ... Unpacking libxine2-bin (1.2.10-2) ... dpkg: error processing archive /var/cache/apt/archives/libxine2-bin_1.2.10-2_amd64.deb (--unpack): trying to overwrite '/usr/share/man/man5/xine.5.gz', which is also in package libxine2-doc 1.2.9-1 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libxine2-bin_1.2.10-2_amd64.deb cheers, Andreas libxine2-doc=1.2.9-1_libxine2-bin=1.2.10-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: xine-lib-1.2 Source-Version: 1.2.10-3 Done: =?utf-8?q?H=C3=A5vard_Flaget_Aasen?= We believe that the bug you reported is fixed in the latest version of xine-lib-1.2, 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 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Håvard Flaget Aasen (supplier of updated xine-lib-1.2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 03 Jun 2020 11:47:36 +0200 Source: xine-lib-1.2 Architecture: source Version: 1.2.10-3 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Håvard Flaget Aasen Closes: 961509 Changes: xine-lib-1.2 (1.2.10-3) unstable; urgency=medium . * QA upload. * Add Breaks and Replaces closes: #961509 * Exclude more files from hurd-i386 Checksums-Sha1: 9db46ae1e033b68b860a24ab5ef0a1115bc81f21 3402 xine-lib-1.2_1.2.10-3.dsc c5a535b5546b8f914d8369f016329e5ad9f588fb 37736 xine-lib-1.2_1.2.10-3.debian.tar.xz Checksums-Sha256: 9a34b25aa4c4f1f4e44b41133fa7aff42fc1bb3550153cef01cc7b869e26dd32 3402 xine-lib-1.2_1.2.10-3.dsc ffd8649c2acd1306863b43c2e733710ed2fd040db697c30973e698f425a04419 37736 xine-lib-1.2_1.2.10-3.debian.tar.xz Files: f91cda8532e6bb1046907491d936cbff 3402 libs optional xine-lib-1.2_1.2.10-3.dsc 9a85f309820817eb5cfa42e04a95b4c0 37736 libs optional xine-lib-1.2_1.2.10-3.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZaEt9P4xrWusTXauM1X01jtYIcwFAl7akgcACgkQM1X01jtY IcyhXhAAkbGrSKM+DiPdnVGj6/r88cyhnVAvD0BHwcvAprQCRUfmHeIVIAotZS0+ lEOzAD1iFrLfIDSMl5kaFIuSW3ajUn89rp8Ytpgx1sxLs5tZMSX8TszJYV/6cJeE O8csPBZXlQM2AAxiaoF/Fk0pMTqQStzZP4uHsMAu8xmRGxjHILbdUnntulvCH77S EiAQf90I7vSKxUCStuMg6CDme7FL72pnOGvG4oHb7e9pcVacRWwZiCJ6r+V8YB1v fX/QiWmRU+nYy69mcHJGqVCrglJZHrZg1gbv5NeyRVtoOhArwIoi/28UssyNSKWx nh3ZLnYQS53piwr3U2M9d8Bvj0N0lWfm1o3XbzUpVOh2S4Sob3fQSh6DhAGYIcwT suEG/XooIx6lrVLrFRbk3rppSE4EYUR/mxHq1nmFu6+HWcA9WTBe/G8ruuOSqAKO 1K0EsxdOKuYZ3D4B+HANVj30I6kyEbjIujb2znfThJdKZC2fAbX65/wS5LrvyO8j 8OEfN71HeCG7ICQ4ryL4TQFxfzzhfWyi9KTmuTonDYBDT/bX+u81pDiipxBYyj9+ //Xn1ZjiZ6lw9ZbnlnfciG1MdH1RQBOxIAvuzr53wLGg39HB5wqLekWmwWE18ST6 niQY0ikkNM31mz8ZIVH/DKBkfQ5XoMfZnpvtgcRHJZ3XIYOGiHI= =To57 -END PGP SIGNATURE End Message ---
Bug#962263: marked as done (nvidia-cuda-toolkit: missing libjpeg62-dev dependency)
Your message dated Fri, 05 Jun 2020 18:23:27 + with message-id and subject line Bug#962263: fixed in nvidia-cuda-toolkit 10.1.243-6 has caused the Debian Bug report #962263, regarding nvidia-cuda-toolkit: missing libjpeg62-dev dependency 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.) -- 962263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962263 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-cuda-toolkit Version: 10.1.243-5 Severity: serious tags: patch Hello, looks like that control file is missing an explicit libjpeg62-dev dependency, and this fails when a different jpeg implementation is default in the system. dpkg-shlibdeps: error: cannot find library libjpeg.so.62 needed by debian/nvidia-openjdk-8-jre/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/libsplashscreen.so (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64') --- nvidia-cuda-toolkit-10.1.243/debian/changelog 2020-06-03 09:54:22.0 +0200 +++ nvidia-cuda-toolkit-10.1.243/debian/changelog 2020-06-05 08:09:24.0 +0200 @@ -1,3 +1,9 @@ +nvidia-cuda-toolkit (10.1.243-5.1) unstable; urgency=medium + + * Add missing libjpeg62 dependency to fix build failure (Closes: #-1) + + -- Gianfranco Costamagna Fri, 05 Jun 2020 08:09:24 +0200 + nvidia-cuda-toolkit (10.1.243-5) unstable; urgency=medium * Merge changes from 10.1.168-11. diff -Nru nvidia-cuda-toolkit-10.1.243/debian/control nvidia-cuda-toolkit-10.1.243/debian/control --- nvidia-cuda-toolkit-10.1.243/debian/control 2020-06-03 09:54:22.0 +0200 +++ nvidia-cuda-toolkit-10.1.243/debian/control 2020-06-05 08:09:24.0 +0200 @@ -42,6 +42,7 @@ liblcms2-dev, libpcsclite-dev, libpng-dev, + libjpeg62, (please don't use libjpeg62-dev package, because it conflicts with the turbo one, and makes the package bd-uninstallable) Cheers Gianfranco --- End Message --- --- Begin Message --- Source: nvidia-cuda-toolkit Source-Version: 10.1.243-6 Done: Andreas Beckmann We believe that the bug you reported is fixed in the latest version of nvidia-cuda-toolkit, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Beckmann (supplier of updated nvidia-cuda-toolkit 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: Fri, 05 Jun 2020 19:15:23 +0200 Source: nvidia-cuda-toolkit Architecture: source Version: 10.1.243-6 Distribution: unstable Urgency: medium Maintainer: Debian NVIDIA Maintainers Changed-By: Andreas Beckmann Closes: 962263 Changes: nvidia-cuda-toolkit (10.1.243-6) unstable; urgency=medium . * nsight-systems: Do not ship libstdc++.so.6, libhyphen.so.0. * Use vendor specific jre dependency substitutions. * Adjust B-D to use libjpeg62-dev on Ubuntu. (Closes: #962263) * Do not build nvidia-openjdk-8-jre on Ubuntu. * Use versioned openjdk-8-jre component tarballs. * nvidia-openjdk-8-jre: Use a snapshot of openjdk-8-jre (8u252-b09-1~deb9u1) from Debian stretch which is backportable to buster. Checksums-Sha1: 33b8f75264ae1b53cf2d923d1cd3dc30a9a89f93 7882 nvidia-cuda-toolkit_10.1.243-6.dsc 3677b8d5fdf2b56ca5a36999cce53ec16f035332 1422206208 nvidia-cuda-toolkit_10.1.243.orig-amd64.tar.xz 6d6297443641be20c955f4115b1060cc581bb9d1 27471664 nvidia-cuda-toolkit_10.1.243.orig-openjdk-8-jre-amd64-8u252-b09-1-d9u1.tar.xz 4f2f7309a8d1e4fa36041a6d52b23e2f1f20d3bb 26562820 nvidia-cuda-toolkit_10.1.243.orig-openjdk-8-jre-ppc64el-8u252-b09-1-d9u1.tar.xz 06f732cee1b4492cd3e93c5f81d990f2743d746f 71935984 nvidia-cuda-toolkit_10.1.243.orig-openjdk-8-source-8u252-b09-1-d9u1.tar.xz f0b94a831e553ce5b89f934b7578cb220b2d736c 1209727584 nvidia-cuda-toolkit_10.1.243.orig-ppc64el.tar.xz 7c0831e83122beb3814b07ccd8875af4f100de81 196 nvidia-cuda-toolkit_10.1.243.orig.tar.xz c02aa3324fe94b15bf378aaf82103ddce06e446c 66264 nvidia-cuda-toolkit_10.1.243-6.debian.tar.xz ba9922479dc4059f6aa1156c126c2bde3e654c28 5921 nvidia-cuda-toolkit_10.1.243-6_source.buildinfo Checksums-Sha256:
Processed: found 962158 in 2.77.0
Processing commands for cont...@bugs.debian.org: > found 962158 2.77.0 Bug #962158 [lintian] lintian: Swapped exit statuses and --fail-on default value require downstream adjustments Marked as found in versions lintian/2.77.0. > thanks Stopping processing here. Please contact me if you need assistance. -- 962158: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#950564: marked as done (olive-editor FTBFS on 32bit: error: narrowing conversion)
Your message dated Fri, 05 Jun 2020 17:50:00 +
with message-id
and subject line Bug#950564: fixed in olive-editor 20200528-1
has caused the Debian Bug report #950564,
regarding olive-editor FTBFS on 32bit: error: narrowing conversion
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.)
--
950564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950564
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: olive-editor
Version: 20200121-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=olive-editor=sid
...
cd /<>/obj-i686-linux-gnu/app && /usr/bin/c++
-DAPPVERSION=\"0.2.0\" -DGITHASH=\"\" -DQT_CORE_LIB -DQT_DEPRECATED_WARNINGS
-DQT_GUI_LIB -DQT_MULTIMEDIA_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB
-DQT_SVG_LIB -DQT_WIDGETS_LIB -I/<>/obj-i686-linux-gnu/app
-I/<>/app
-I/<>/obj-i686-linux-gnu/app/olive-editor_autogen/include -isystem
/usr/include/i386-linux-gnu/qt5 -isystem /usr/include/i386-linux-gnu/qt5/QtCore
-isystem /usr/lib/i386-linux-gnu/qt5/mkspecs/linux-g++ -isystem
/usr/include/i386-linux-gnu/qt5/QtGui -isystem
/usr/include/i386-linux-gnu/qt5/QtWidgets -isystem
/usr/include/i386-linux-gnu/qt5/QtMultimedia -isystem
/usr/include/i386-linux-gnu/qt5/QtNetwork -isystem
/usr/include/i386-linux-gnu/qt5/QtOpenGL -isystem
/usr/include/i386-linux-gnu/qt5/QtSvg -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -Werror
-Wuninitialized -pedantic-errors -Wall -Wextra -Wconversion -Wsign-conversion
-fPIC -std=c++11 -o CMakeFiles/olive-editor.dir/node/inputarray.cpp.o -c
/<>/app/node/inputarray.cpp
/<>/app/node/input.cpp: In member function ‘virtual void
NodeInput::Load(QXmlStreamReader*, QHash&,
QList&, QList&)’:
/<>/app/node/input.cpp:166:71: error: narrowing conversion of
‘QXmlStreamReader::text() const().QStringRef::toULongLong(0, 10)’ from
‘qulonglong’ {aka ‘long long unsigned int’} to ‘quintptr’ {aka ‘unsigned int’}
[-Wnarrowing]
166 | input_connections.append({this,
reader->text().toULongLong()});
| ~~^~
/<>/app/node/input.cpp:166:71: error: conversion from ‘qulonglong’
{aka ‘long long unsigned int’} to ‘quintptr’ {aka ‘unsigned int’} may change
value [-Werror=conversion]
/<>/app/node/input.cpp: In member function ‘QVariant
NodeInput::StringToValue(const QString&, QList&)’:
/<>/app/node/input.cpp:275:57: error: narrowing conversion of ‘(&
string)->QString::toULongLong(0, 10)’ from ‘qulonglong’ {aka ‘long long
unsigned int’} to ‘quintptr’ {aka ‘unsigned int’} [-Wnarrowing]
275 | footage_connections.append({this, string.toULongLong()});
| ~~^~
/<>/app/node/input.cpp:275:57: error: conversion from ‘qulonglong’
{aka ‘long long unsigned int’} to ‘quintptr’ {aka ‘unsigned int’} may change
value [-Werror=conversion]
cc1plus: all warnings being treated as errors
make[3]: *** [app/CMakeFiles/olive-editor.dir/build.make:1452:
app/CMakeFiles/olive-editor.dir/node/input.cpp.o] Error 1
--- End Message ---
--- Begin Message ---
Source: olive-editor
Source-Version: 20200528-1
Done: =?utf-8?q?G=C3=BCrkan_Myczko?=
We believe that the bug you reported is fixed in the latest version of
olive-editor, 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 950...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Gürkan Myczko (supplier of updated olive-editor package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 02 Jun 2020 08:32:58 +0200
Source: olive-editor
Architecture: source
Version: 20200528-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers
Changed-By: Gürkan Myczko
Closes: 950564
Changes:
olive-editor (20200528-1) unstable; urgency=medium
.
* New upstream version.
* d/control:
- don't build on 32-bit architectures. (Closes: #950564)
- add libopenexr-dev to Build-Depends.
Checksums-Sha1:
347c890b3de815b84703d0d903cf485c3dac1cc3 2379 olive-editor_20200528-1.dsc
Bug#962262: Acknowledgement (opendmarc fails many emails without apparent reason)
Dear Maintainer I think I got it. Maybe updating the manpage would be very helpfull for other people who stumble over the same problem. DMARC needs to do an SPF check. Well I have milter-greylist already performing SPF check, so I configured what I tought would make opendmarc ignore the SPF check and assuming an email that went that far already passed SPF check (which is true in my case). Now I understand, opendmarc need to do SPF check itself. Only this way the result ever returns 'pass'. SPFSelfValidate true Problem solved. I wonder if I could make milter-greylist to create a header which would satisfy opendmarc but I could not find any documentation of the Authentication-Result: header. -Benoît-
Bug#962265: patch for sword ICU 67.1 detection
Control: tags -1 +patch Hi, It seems your upstream is inactive. It was me who patched sword for ICU 63.1 and here is the patch for the ICU 67.1 version. Please apply this soon. Thanks, Laszlo/GCS Description: fix ICU checking Let still search for icu-config but use pkg-config method after that. Forwarded: no Author: Laszlo Boszormenyi (GCS) Last-Update: 2020-06-05 --- --- sword-1.8.1+dfsg.orig/configure.ac +++ sword-1.8.1+dfsg/configure.ac @@ -238,9 +238,19 @@ if test x$with_icu = xyes; then AM_CXXFLAGS="$AM_CXXFLAGS -D_ICU_" AM_CFLAGS="$AM_CFLAGS -D_ICU_" else - echo "*** The icu-config script installed by icu could not be found" - echo "*** compiling without ICU support" - with_icu=no + PKG_CHECK_MODULES([ICU], [icu-i18n >= 63.1], [found_icu=yes]) + if test "$found_icu" = "yes"; then + PKG_CHECK_MODULES([ICU_IO], [icu-io >= 63.1]) + ICU_IOLIBS="$ICU_IO_LIBS" + with_icu=yes + LIBS="$LIBS $ICU_LIBS $ICU_IOLIBS" + AM_CXXFLAGS="$AM_CXXFLAGS -D_ICU_" + AM_CFLAGS="$AM_CFLAGS -D_ICU_" + else + echo "*** The icu-config script installed by icu could not be found" + echo "*** compiling without ICU support" + with_icu=no + fi fi fi
Processed: patch for sword ICU 67.1 detection
Processing control commands: > tags -1 +patch Bug #962265 [src:sword] sword silently loses ICU support when built with ICU without icu-config Added tag(s) patch. -- 962265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962288: marked as done (ros-actionlib build depends on libboost-signals-dev that is removed in boost1.71)
Your message dated Fri, 05 Jun 2020 17:19:05 + with message-id and subject line Bug#962288: fixed in ros-actionlib 1.12.0-5 has caused the Debian Bug report #962288, regarding ros-actionlib build depends on libboost-signals-dev that is removed in boost1.71 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.) -- 962288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962288 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ros-actionlib Version: 1.12.0-4 Severity: serious Tags: ftbfs Control: block 961995 by -1 https://buildd.debian.org/status/package.php?p=ros-actionlib libboost-signals-dev is removed in boost1.71. --- End Message --- --- Begin Message --- Source: ros-actionlib Source-Version: 1.12.0-5 Done: Jochen Sprickerhof We believe that the bug you reported is fixed in the latest version of ros-actionlib, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated ros-actionlib 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, 05 Jun 2020 18:57:34 +0200 Source: ros-actionlib Architecture: source Version: 1.12.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Jochen Sprickerhof Closes: 962288 Changes: ros-actionlib (1.12.0-5) unstable; urgency=medium . * Drop unused build dependency (Closes: #962288) * bump policy version Checksums-Sha1: 9c45782927eda5efc94492185328539fe2837b5a 2832 ros-actionlib_1.12.0-5.dsc 81054de54760fa7ee41e1553904c8dca1483ca7e 5392 ros-actionlib_1.12.0-5.debian.tar.xz 23395772dc6003bba708378a19eb66eee54f5fb8 14127 ros-actionlib_1.12.0-5_source.buildinfo Checksums-Sha256: 2f5080dc73f895b31833de72b2c5155fa97c8ea244e3ceccbddac0df7b46a7e3 2832 ros-actionlib_1.12.0-5.dsc 3cb4544afc1a4debd15f5b20d4c603c54b9bcfaf05a45a4c69c61580a6e10397 5392 ros-actionlib_1.12.0-5.debian.tar.xz 0ce383aac3aeed859d4ba3dfba7e036df189fcf4ed20e6e0f786cc46dcf9c23a 14127 ros-actionlib_1.12.0-5_source.buildinfo Files: 66054848f6f9d03e84300c8540eaf3b3 2832 libs optional ros-actionlib_1.12.0-5.dsc 0c45a4fa49e8ead787c0950e7ff3dc78 5392 libs optional ros-actionlib_1.12.0-5.debian.tar.xz b0be1777b1c0407bac1b764a3c0ce921 14127 libs optional ros-actionlib_1.12.0-5_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAl7aebwACgkQW//cwljm lDM+fQ//eCxnArbE+N4OSt6BHDyDCvyd3TJc7QEe5doPz0MgHIDPc5/mQfUBb5nS y/vvJ1gmBwI62/v+iGDwxwASkDZluzXvpqmiIoJG37wD2jvSW75y8xgmm6czvaiI 4J1KrmuLrpRKt4t0uEYoB3MsvKp2z9uIBoPSM5Uj1qyVhFP9+od+nCy0V/dQYwPg iC11ApLL7TaAzbYVwtgny9ngWaBlQmnXJj9scTKWNRYFQ1xYjhsw2oAfGOhN7VnQ w6en0xd3pBaF6Vvj8VXjz0D62ZT9qXD4fMDTrTcM4npkMSJ5pZcz2qy+bUXuKS7+ /yBzjyfZLagvu3iwRmcdGr87mfbfzO0zCHg5Dq3cn6S+YB3u/1QUGuFzmHslx/l3 uWZT9tZSIDwID89LOz3yrnd87Iw3qQ+LR+U2vZQJzxSEMtafvFoqYyXVsCmvKTD4 xemoL22MPUJkzvYsrQ0CQAPBneMt3ihjmi2nGHt1h0ME+F8iuRlSlVyIce/EK/Xm aDKYdrHQ3B4yx1E1AITWWWP4k+OafV/9hmRpBMWsU2g8HsZWlqvwXh0aPt7A1v6q 5HxuFaZXT3abhNTG5w/75KDie2suQxFwlYbMTxUayhUyclPIvX+PTLg35Nq+9jVC Gg9AF/iko9TWmv4yt5GSjNDRlCsZNiWmTcN5fJVeTnaV6GvfOlQ= =rRU1 -END PGP SIGNATURE End Message ---
Bug#962287: marked as done (ros-image-common FTBFS with boost 1.71)
Your message dated Fri, 05 Jun 2020 17:05:13 + with message-id and subject line Bug#962287: fixed in ros-image-common 1.11.13-8 has caused the Debian Bug report #962287, regarding ros-image-common FTBFS with boost 1.71 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.) -- 962287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ros-image-common Version: 1.11.13-7 Severity: serious Tags: ftbfs Control: block 961995 by -1 https://buildd.debian.org/status/package.php?p=ros-image-common ... -- Found Python: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found version "3.8") found components: Development CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake:117 (find_package): Could not find a package configuration file provided by "boost_python3.8" (requested version 1.71.0) with any of the following names: boost_python3.8Config.cmake boost_python3.8-config.cmake Add the installation prefix of "boost_python3.8" to CMAKE_PREFIX_PATH or set "boost_python3.8_DIR" to a directory containing one of the above files. If "boost_python3.8" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake:182 (boost_find_component) /usr/share/cmake-3.16/Modules/FindBoost.cmake:443 (find_package) camera_calibration_parsers/CMakeLists.txt:7 (find_package) -- Configuring incomplete, errors occurred! The Ubuntu diff (linked from tracker.debian.org) seems to contain a fix (untested). --- End Message --- --- Begin Message --- Source: ros-image-common Source-Version: 1.11.13-8 Done: Jochen Sprickerhof We believe that the bug you reported is fixed in the latest version of ros-image-common, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated ros-image-common 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, 05 Jun 2020 18:48:45 +0200 Source: ros-image-common Architecture: source Version: 1.11.13-8 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Jochen Sprickerhof Closes: 962287 Changes: ros-image-common (1.11.13-8) unstable; urgency=medium . * Fix boost python version string (Closes: #962287) Checksums-Sha1: cf285eb83729e7716c604be2560b0dcfe9fba456 3496 ros-image-common_1.11.13-8.dsc 713f969be9c81f6ea804d1d0e94798222a9ede06 6676 ros-image-common_1.11.13-8.debian.tar.xz d35a4ef32aca768bd95972eeed4c78be5926d8a8 10480 ros-image-common_1.11.13-8_source.buildinfo Checksums-Sha256: 0cd3545a68595c8fbef9c37a07dc4331903e674547dae0b5f3aeed0d748915ac 3496 ros-image-common_1.11.13-8.dsc e020e342cd590282f5f44c2b646f78525a42f33d94cc9bc0c81db0f870c667db 6676 ros-image-common_1.11.13-8.debian.tar.xz 920b4e50199ff41442bd5960847ad66f619443a676aac439f7a2e3e66900e239 10480 ros-image-common_1.11.13-8_source.buildinfo Files: d1b9c5ea4c029f50e051635728442918 3496 libs optional ros-image-common_1.11.13-8.dsc 803d24bb2c8a5fb163e82fc4988c817e 6676 libs optional ros-image-common_1.11.13-8.debian.tar.xz c0738223ead1c63385844704f67ed9da 10480 libs optional ros-image-common_1.11.13-8_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAl7ad4EACgkQW//cwljm lDP1aQ//Vz2b5mZNYF+wQu67ECDY+1SyhBX62jvYQMBrUAfCQE7iJ0zCv43Bm/7A DqQQyXLOP8XPNCRO4nTSHI9cwSOgm90klCbzrEt1ruZEKR7L7Mc7arFVVKFMbqhA vjO/BZwI3IByyLRNVW2pM5TC00OvI7YdVvWHvKj1pwPw5Db8lNfjaKL0BRNbEsck WeULBqzPPvtwLi5RfqoMsn6q0x2TDgxXCY8i813oFhpArj4qpvneUAdXLQe2Z7h+ YTGo8UiFLKKWoaypNHSjo2GFK5NHOZ4J66/U4IK3XlNV1X+AMkSXg0UxBmdvHnIE FGyY3ZmOFcDzieDUplK14pnRkTAhlaeEhyQ/GrKb/Xi2bPRoOKzcDz7g+xWBPvV+ yT5tWpjuu9FTzS+xxc+k5yKndarGT2ojduI9s1NOEDbEIVppqmhftaBPTzhOesig PWBCnzIK7WclHi9N/GSlQWIclivtla2Z0R80hFnQ4QpuWGd7/aEyBpOppX5/gMJ3 zTQV2rDQ85T7H2sl6vtZtIfVUCx33IUTnq8UjeN8wcxmAYHH0s8sReF59+i4cGpB H8wq3XgmGKgMZ/VFAgcShJYx59r3X2VShJtI5zm8YAsINJdwJkmNVvTvXhtYhord
Bug#961907: marked as done (ca-certificates: Remove expired mozilla/AddTrust_External_Root.crt)
Your message dated Fri, 05 Jun 2020 17:02:08 + with message-id and subject line Bug#961907: fixed in ca-certificates 20200601~deb10u1 has caused the Debian Bug report #961907, regarding ca-certificates: Remove expired mozilla/AddTrust_External_Root.crt 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.) -- 961907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961907 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: ca-certificates Version: 20190110 Severity: important Dear Maintainer, The AddTrust_External_Root.crt certificate has expired, and its continued inclusion in the ca-certificates set is causing GnuTLS-based client applications (and OpenSSL 1.0.x) to barf on a lot of sites. It could probably be argued that this is a bug in GnuTLS rather than ca-certificates, but I don't see the point in keeping an expired certificate here. The problem is confirmed to affect Epiphany and VLC. See also: https://gitlab.com/gnutls/gnutls/-/issues/1008 https://www.agwa.name/blog/post/fixing_the_addtrust_root_expiration Best regards, -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64 Kernel: Linux 5.6.0-2-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fi_FI.UTF-8), LANGUAGE=fr:en_GB:fi (charmap=UTF-8) (ignored: LC_ALL set to fi_FI.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ca-certificates depends on: ii debconf [debconf-2.0] 1.5.74 ii openssl1.1.1g-1 ca-certificates recommends no packages. ca-certificates suggests no packages. -- debconf information excluded --- End Message --- --- Begin Message --- Source: ca-certificates Source-Version: 20200601~deb10u1 Done: Michael Shuler We believe that the bug you reported is fixed in the latest version of ca-certificates, 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 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Shuler (supplier of updated ca-certificates package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 03 Jun 2020 13:09:34 -0500 Source: ca-certificates Architecture: source Version: 20200601~deb10u1 Distribution: buster Urgency: medium Maintainer: Michael Shuler Changed-By: Michael Shuler Closes: 911289 955038 956411 961907 Changes: ca-certificates (20200601~deb10u1) buster; urgency=medium . * Rebuild for buster. * Merge changes from 20200601 - d/control; set d/gbp.conf branch to debian-buster * This release updates the Mozilla CA bundle to 2.40, blacklists distrusted Symantec roots, and blacklists expired "AddTrust External Root". Closes: #956411, #955038, #911289, #961907 Checksums-Sha1: f020fb7815a9611704021209916abf624692125c 1837 ca-certificates_20200601~deb10u1.dsc 5f56d6d72598aaf0b5818fa629336dd56972314f 245828 ca-certificates_20200601~deb10u1.tar.xz Checksums-Sha256: 41120aa922b9520b73b88ef3fef18b807c7e5b6dd98c9dec51a3841dabe7fcb8 1837 ca-certificates_20200601~deb10u1.dsc 5911c0471fd83141285c56c414be7f6e7176f28dc8d14a3c55f06303b79a92aa 245828 ca-certificates_20200601~deb10u1.tar.xz Files: 446b9d09b73e92b641319ac58a28503d 1837 misc optional ca-certificates_20200601~deb10u1.dsc d31e6fb6f4f22c7ea7300b5022b71123 245828 misc optional ca-certificates_20200601~deb10u1.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAl7aAJ0ACgkQiNJCh6LY mLG9zw//XDxRww0+aEwPrUbFOw9AhlPrs0kWRp3L4Zq3uc6+TtavRvf/8XE6JYTq 7woNmWI9Jl/GtukF2NZwXOW/CseAHhYU67epf9pX23tsLLYwjQqmGRtXxvPO90D7 Um3Hqu7HqNs4yJkX+iRZ7ENKiUqYBFrIt+vilIRthnEYmAxJ4QN5qQqnTsnb6MSO kdb096u1oxEg7+iP6fmFpe1RFd00leB/nKX4aR7oyXatgGm1NxoCWmPt/4wfiCd6 jj9abKAF6+bN7RuyoqkNnyhSHZN91R48eruoUXLlMGuC+sQUOwF6ppTfoBBordXJ bvkYf3fnCG6hI5gvpWmO+zw1g7+K/U1S+ldBDf831zmmjhCu7MFX3j7yYmkBr0sK
Bug#962081: gnucobol: Failing autopkgtest scripts should report what went wrong
I discovered what the problem is. The test [ $res ] do not work the way you want it to. It need to compare with 0, like this: diff --git a/debian/tests/test01 b/debian/tests/test01 index 1c0d63f..73e1fac 100755 --- a/debian/tests/test01 +++ b/debian/tests/test01 @@ -1,4 +1,5 @@ #!/bin/sh + cd debian/tests echo "info: compiling" @@ -7,7 +8,7 @@ echo "info: compiling" echo "info: running" cmp -s test01.exp $AUTOPKGTEST_TMP/test01.act res=$? -if [ $res ] ; then +if [ 0 = $res ] ; then echo "success: test01 produced proper results" else echo "error: test01 did not produce proper results" diff --git a/debian/tests/test02 b/debian/tests/test02 index fb85d2e..cb4359d 100755 --- a/debian/tests/test02 +++ b/debian/tests/test02 @@ -7,7 +7,7 @@ echo "info: compiling" echo "info: running" cmp -s test02.exp $AUTOPKGTEST_TMP/test02.act res=$? -if [ $res ] ; then +if [ 0 == $res ] ; then echo "success: test02 produced proper results" else echo "error: test02 did not produce proper results" diff --git a/debian/tests/test03 b/debian/tests/test03 index c028d8b..07d679c 100755 --- a/debian/tests/test03 +++ b/debian/tests/test03 @@ -7,7 +7,7 @@ echo "info: compiling" echo "info: running" cmp -s test03.exp $AUTOPKGTEST_TMP/test03.act res=$? -if [ $res ] ; then +if [ 0 == $res ] ; then echo "success: test03 produced proper results" else echo "error: test03 did not produce proper results" diff --git a/debian/tests/test04 b/debian/tests/test04 index fd2a6ad..ee31d4a 100755 --- a/debian/tests/test04 +++ b/debian/tests/test04 @@ -7,7 +7,7 @@ echo "info: compiling" echo "info: running" cmp -s test04.exp t$AUTOPKGTEST_TMP/est04.act res=$? -if [ $res ] ; then +if [ 0 == $res ] ; then echo "success: test04 produced proper results" else echo "error: test04 did not produce proper results" -- Happy hacking Petter Reinholdtsen
Bug#962286: marked as done (ros-dynamic-reconfigure build depends on libboost-signals-dev that is removed in boost1.71)
Your message dated Fri, 05 Jun 2020 16:48:40 + with message-id and subject line Bug#962286: fixed in ros-dynamic-reconfigure 1.6.0-4 has caused the Debian Bug report #962286, regarding ros-dynamic-reconfigure build depends on libboost-signals-dev that is removed in boost1.71 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.) -- 962286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ros-dynamic-reconfigure Version: 1.6.0-3 Severity: serious Tags: ftbfs Control: block 961995 by -1 https://buildd.debian.org/status/package.php?p=ros-dynamic-reconfigure libboost-signals-dev is removed in boost1.71. --- End Message --- --- Begin Message --- Source: ros-dynamic-reconfigure Source-Version: 1.6.0-4 Done: Jochen Sprickerhof We believe that the bug you reported is fixed in the latest version of ros-dynamic-reconfigure, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jochen Sprickerhof (supplier of updated ros-dynamic-reconfigure 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, 05 Jun 2020 18:25:58 +0200 Source: ros-dynamic-reconfigure Architecture: source Version: 1.6.0-4 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Jochen Sprickerhof Closes: 962286 Changes: ros-dynamic-reconfigure (1.6.0-4) unstable; urgency=medium . * Drop unused build dependency (Closes: #962286) * bump policy Checksums-Sha1: a9587ff683b61e00721a09de9e1545c68718b22a 2876 ros-dynamic-reconfigure_1.6.0-4.dsc 83c55d2fea599292be2fe40ecb5840f674d40e45 4332 ros-dynamic-reconfigure_1.6.0-4.debian.tar.xz 8ee3b9f331ac7e2dd5a1c084f963dc438f917f1e 10288 ros-dynamic-reconfigure_1.6.0-4_source.buildinfo Checksums-Sha256: ffb6d448f55190fe10083169ca7c24c1dc2cfff0c4f9c1b1029d4aae95c869ee 2876 ros-dynamic-reconfigure_1.6.0-4.dsc b8379364e3c7ec5c5545ab1b97d6af7048a2ef38c7da1102edbe377a4273cef0 4332 ros-dynamic-reconfigure_1.6.0-4.debian.tar.xz d83819b771731fac6f37dc96dbb470f62f85fa13fb552c82cc681da6b1f8b2e1 10288 ros-dynamic-reconfigure_1.6.0-4_source.buildinfo Files: c55953dcdb65e5d22da50cf43d3dc84e 2876 libs optional ros-dynamic-reconfigure_1.6.0-4.dsc c35405bf64f95887d5212b7cc7838e32 4332 libs optional ros-dynamic-reconfigure_1.6.0-4.debian.tar.xz 525927710fbc1d7a81ecf754fe9ace03 10288 libs optional ros-dynamic-reconfigure_1.6.0-4_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAl7ack8ACgkQW//cwljm lDNIKA//RbfHo6s0bP69Cb3kyMFmfEb6IiHSSjzoFBoM5U4XTeRSB7rjTc9vubn8 0oGvRTUTODCqlpUg1ZgT2HG5FhbcK257yFg9sIuX3nNpA2AJNK/0fSCm3+xqvc9T 6KZxan0WrXzw6OOKrkXB3vOdUDd+qJDCJ0TPyiCMIvFyrZhYlOl70tV+bvsM2d0l B3SW4mCUlg3036zuRKOb5FlWGFy0ZBPoHGKwW6XPgZOmOKPDyQhPVXgsLC+MqYDd SUjr5EgwKAgyz2lb65h6VTiz0FUjpqpVpJKJDnDMWEJ5+aTaCIMIjaSHIifJFl1u LeR5GPicXxwkaCdMG10M5A3gWMZfGVCIwPdDjzuqgbIsoeC5PcJr3kF1rcX8a17S yFAW8z5tkVTlGR+hiA1qTe2xZHIKLnrqlMW30MSboXWifPwjoSAMlgwjJamVqbSV J+6gcGhRAKUfV6Ovm4BfZGm3nedrcXL/JNqXdfVF6ibFkYLSZSVRHQO+6xVjRtut 1zNcMFAfVQGzU+dEU/RM6Vl6ZYcNmdg4q0C1Yqbk8tjoCc7sxZoqCP74SWZgzX93 /ZiiifqyhLReCtWS6IjLEHoZ4LYEUut4nSrBKZU+Hdjne2Ls4FfmF/+gz9jYw807 YjrL6kiYKvB/LUV81fXfnkCFXJoBt7Hf3aRQXL425cBve1osIAo= =AsUv -END PGP SIGNATURE End Message ---
Bug#962262: Acknowledgement (opendmarc fails many emails without apparent reason)
On Friday, June 5, 2020 9:44:03 AM EDT you wrote: > Dear Maintainer > > I think I got it. Maybe updating the manpage would be very helpfull for > other people who stumble over the same problem. > > DMARC needs to do an SPF check. > > Well I have milter-greylist already performing SPF check, so I > configured what I tought would make opendmarc ignore the SPF check and > assuming an email that went that far already passed SPF check (which is > true in my case). > > Now I understand, opendmarc need to do SPF check itself. Only this way > the result ever returns 'pass'. > > SPFSelfValidate true > > Problem solved. > > I wonder if I could make milter-greylist to create a header which would > satisfy opendmarc but I could not find any documentation of the > Authentication-Result: header. OpenDMARC has a new upstream maintainer. I would suggest submitting the documentation issue upstream on GitHub directly. Assuming I'm looking at the right milter-greylist homepage: http://hcpnet.free.fr/milter-greylist It's SPF implementation is very old. It predates the existence of the authentication results header field. Scott K signature.asc Description: This is a digitally signed message part.
Bug#962289: gnutls28: CVE-2020-13777: session resumption works without master key allowing MITM
Source: gnutls28 Version: 3.6.13-4 Severity: grave Tags: security upstream Forwarded: https://gitlab.com/gnutls/gnutls/-/issues/1011 Control: found -1 3.6.4-1 Control: found -1 3.6.7-4+deb10u3 Hi Andreas, The following vulnerability was published for gnutsl28, filling it as RC given the resulting in authentication bypass possibility, but if you do not agree please downgrade. CVE-2020-13777[0]: | GnuTLS 3.6.x before 3.6.14 uses incorrect cryptography for encrypting | a session ticket (a loss of confidentiality in TLS 1.2, and an | authentication bypass in TLS 1.3). The earliest affected version is | 3.6.4 (2018-09-24) because of an error in a 2018-09-18 commit. Until | the first key rotation, the TLS server always uses wrong data in place | of an encryption key derived from an application. If you want I can try to help preparing as well a corresponding buster-security update. The issue was introduced in 3.6.4 upstream, so stretch is not affected. 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-13777 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-13777 [1] https://gnutls.org/security-new.html#GNUTLS-SA-2020-06-03 [2] https://gitlab.com/gnutls/gnutls/-/issues/1011 Regards, Salvatore
Processed: gnutls28: CVE-2020-13777: session resumption works without master key allowing MITM
Processing control commands: > found -1 3.6.4-1 Bug #962289 [src:gnutls28] gnutls28: CVE-2020-13777: session resumption works without master key allowing MITM Marked as found in versions gnutls28/3.6.4-1. > found -1 3.6.7-4+deb10u3 Bug #962289 [src:gnutls28] gnutls28: CVE-2020-13777: session resumption works without master key allowing MITM Marked as found in versions gnutls28/3.6.7-4+deb10u3. -- 962289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962289 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962269: marked as done (haskell-hakyll: build-depends on missing: libghc-file-embed-dev:amd64 (< 0.0.12))
Your message dated Fri, 5 Jun 2020 18:10:46 +0200 with message-id <841efb0f-7da0-d94b-fb57-48b7afcb0...@debian.org> and subject line Re: haskell-hakyll: build-depends on missing: libghc-file-embed-dev:amd64 (< 0.0.12) has caused the Debian Bug report #962269, regarding haskell-hakyll: build-depends on missing: libghc-file-embed-dev:amd64 (< 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.) -- 962269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962269 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: haskell-hakyll Version: 4.13.3.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) haskell-hakyll is stuck in BD-Uninstallable: | haskell-hakyll build-depends on missing: | - libghc-file-embed-dev:amd64 (< 0.0.12) haskell-file-embed is at version 0.0.12.0-1 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- On Fri, 5 Jun 2020 12:10:55 +0200 Sebastian Ramacher wrote: > Source: haskell-hakyll > Version: 4.13.3.0-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > > haskell-hakyll is stuck in BD-Uninstallable: > | haskell-hakyll build-depends on missing: > | - libghc-file-embed-dev:amd64 (< 0.0.12) > > haskell-file-embed is at version 0.0.12.0-1 > please wait for the transition to continue, it will build eventually. G. > Cheers > -- > Sebastian Ramacher--- End Message ---
Processed: bug 962218 is forwarded to https://gitlab.com/gnutls/gnutls/-/issues/1007
Processing commands for cont...@bugs.debian.org: > forwarded 962218 https://gitlab.com/gnutls/gnutls/-/issues/1007 Bug #962218 [src:gnutls28] gnutls28: build fails on IPv6-only buildds Set Bug forwarded-to-address to 'https://gitlab.com/gnutls/gnutls/-/issues/1007'. > thanks Stopping processing here. Please contact me if you need assistance. -- 962218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962218 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962288: ros-actionlib build depends on libboost-signals-dev that is removed in boost1.71
Source: ros-actionlib Version: 1.12.0-4 Severity: serious Tags: ftbfs Control: block 961995 by -1 https://buildd.debian.org/status/package.php?p=ros-actionlib libboost-signals-dev is removed in boost1.71.
Processed: ros-actionlib build depends on libboost-signals-dev that is removed in boost1.71
Processing control commands: > block 961995 by -1 Bug #961995 [release.debian.org] transition: boost-defaults 961995 was blocked by: 959437 960426 962252 948127 962286 959479 960422 962229 954351 962287 960427 960378 959439 958156 962253 948122 960413 962070 955581 960412 960331 959463 959573 948281 960418 960385 960421 960416 962251 960381 953873 959417 960424 954711 954649 954648 962086 960383 949837 953871 960500 948407 960414 955579 962173 959480 961995 was not blocking any bugs. Added blocking bug(s) of 961995: 962288 -- 961995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961995 962288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962288 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962287: ros-image-common FTBFS with boost 1.71
Source: ros-image-common Version: 1.11.13-7 Severity: serious Tags: ftbfs Control: block 961995 by -1 https://buildd.debian.org/status/package.php?p=ros-image-common ... -- Found Python: /usr/lib/x86_64-linux-gnu/libpython3.8.so (found version "3.8") found components: Development CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake:117 (find_package): Could not find a package configuration file provided by "boost_python3.8" (requested version 1.71.0) with any of the following names: boost_python3.8Config.cmake boost_python3.8-config.cmake Add the installation prefix of "boost_python3.8" to CMAKE_PREFIX_PATH or set "boost_python3.8_DIR" to a directory containing one of the above files. If "boost_python3.8" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake:182 (boost_find_component) /usr/share/cmake-3.16/Modules/FindBoost.cmake:443 (find_package) camera_calibration_parsers/CMakeLists.txt:7 (find_package) -- Configuring incomplete, errors occurred! The Ubuntu diff (linked from tracker.debian.org) seems to contain a fix (untested).
Processed: ros-image-common FTBFS with boost 1.71
Processing control commands: > block 961995 by -1 Bug #961995 [release.debian.org] transition: boost-defaults 961995 was blocked by: 960412 960416 954711 948127 954648 953871 960426 960422 960418 960378 959573 948122 962252 959439 962229 960427 954351 960424 962070 959463 954649 959417 955581 962253 960414 960413 960383 959437 948281 960331 962086 958156 960385 959479 962173 953873 960500 962286 955579 960381 949837 962251 960421 959480 948407 961995 was not blocking any bugs. Added blocking bug(s) of 961995: 962287 -- 961995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961995 962287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962287 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962286: ros-dynamic-reconfigure build depends on libboost-signals-dev that is removed in boost1.71
Source: ros-dynamic-reconfigure Version: 1.6.0-3 Severity: serious Tags: ftbfs Control: block 961995 by -1 https://buildd.debian.org/status/package.php?p=ros-dynamic-reconfigure libboost-signals-dev is removed in boost1.71.
Processed: ros-dynamic-reconfigure build depends on libboost-signals-dev that is removed in boost1.71
Processing control commands: > block 961995 by -1 Bug #961995 [release.debian.org] transition: boost-defaults 961995 was blocked by: 954711 953873 959573 958156 960385 960424 949837 960378 960331 960383 960413 960412 960421 953871 959439 960500 960414 959463 959479 948127 960422 959480 962086 960418 960381 948281 948122 960426 960427 962173 962252 962253 955581 948407 959417 954649 959437 960416 955579 962251 962070 962229 954351 954648 961995 was not blocking any bugs. Added blocking bug(s) of 961995: 962286 -- 961995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961995 962286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962286 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#960321: burp: flaky arm64 autopkgtest: .../src/test/clientscript failed
I advised the upstream maintainer[1] and temporary placed the flag "flaky" for the "burp-builtin-test" test[2]. Thank you so much. References: [1]: https://github.com/grke/burp/issues/866 [2]: https://salsa.debian.org/debian/burp/-/commit/513e4c37a59f5cea98bc7723188c2ed0cb70f776 signature.asc Description: OpenPGP digital signature
Bug#962271: libncurses5-dev: Dependency issue
Control: severity -1 normal Control: tags -1 moreinfo wontfix On 2020-06-05 14:35 +0300, Mohammed Alnajdi wrote: > Package: libncurses5-dev > Version: 6.1+20181013-2+deb10u2 > Severity: serious > Justification: Installing libncurses5-dev installs libncurses6 from > libncurses-dev and not > > Hello, I noticed that if i install libncurses5-dev i get libncurses6 which > breaks software which still relay on libncurse5. I fail to see how it does that, could you please elaborate? > I believe installing > libncurses5-dev should bring everything that is libncurses5 not > libncurses6. Sorry, not going to happen. In general Debian only provides -dev packages for the latest ABI of libraries, and ncurses is no exception, especially as its API has not changed. If for some reason you need to compile software against the old ABI, use a chroot for that, e.g. with Debian 9 in it. Or build ncurses yourself. Cheers, Sven
Processed: Re: Bug#962271: libncurses5-dev: Dependency issue
Processing control commands: > severity -1 normal Bug #962271 [libncurses5-dev] libncurses5-dev: Dependency issue Severity set to 'normal' from 'serious' > tags -1 moreinfo wontfix Bug #962271 [libncurses5-dev] libncurses5-dev: Dependency issue Added tag(s) moreinfo and wontfix. -- 962271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962271 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962262: Acknowledgement (opendmarc fails many emails without apparent reason)
Additional Infos: History file entry of such an failing email: job 055AOEWZ026900 reporter magma.woody.ch received 1591352655 ipaddr 2a00:1450:4864:20::52c from gmail.com mfrom gmail.com spf -1 pdomain gmail.com policy 18 rua mailto:mailauth-repo...@google.com pct 100 adkim 114 aspf 114 p 110 sp 113 align_dkim 5 align_spf 5 action 2
Bug#945745: marked as done (wiki2beamer: Python2 removal in sid/bullseye)
Your message dated Fri, 05 Jun 2020 14:39:44 + with message-id and subject line Bug#945745: fixed in wiki2beamer 0.10.0-1 has caused the Debian Bug report #945745, regarding wiki2beamer: Python2 removal in sid/bullseye 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.) -- 945745: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945745 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wiki2beamer Version: 0.9.5-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests (the specific reason can be found searching this source package in https://people.debian.org/~morph/mass-bug-py2removal_take3.txt ). Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: wiki2beamer Source-Version: 0.10.0-1 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of wiki2beamer, 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 945...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated wiki2beamer 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, 05 Jun 2020 09:40:23 -0400 Source: wiki2beamer Architecture: source Version: 0.10.0-1 Distribution: unstable Urgency: medium Maintainer: Boyuan Yang Changed-By: Boyuan Yang Closes: 945745 Changes: wiki2beamer (0.10.0-1) unstable; urgency=medium . * New upstream release 0.10.0. * Migrate from python2 to python3. (Closes: #945745) * debian/control: + Bump Standards-Version to 4.5.0. + Bump debhelper compat to v13. + Update homepage to the current one. * debian/source/options: Drop custom compression option. Checksums-Sha1: e2867208c19c4210373ae09975ab2ecf733b86d5 1888 wiki2beamer_0.10.0-1.dsc 02e3923575b0fe88ba5d9f2c2bb84eb75a7a28d2 164911 wiki2beamer_0.10.0.orig.tar.gz 85182d4ffe03e9e6e6e1a2b899a7807ab9afb0f4 2560 wiki2beamer_0.10.0-1.debian.tar.xz 35f0b2b321be1548b4a6b38b985353c1d04b7a01 6244 wiki2beamer_0.10.0-1_amd64.buildinfo Checksums-Sha256: d112b9f17e367cd0a3a579f1322b1e824d7419a91434dc239a267d5389ff41fb 1888 wiki2beamer_0.10.0-1.dsc e9662674cbf6b859bc1847e0dfa9cc89b1c2e1d1e0f727285de9a374875cb6a7 164911 wiki2beamer_0.10.0.orig.tar.gz
Bug#948122: marked as done ([aegisub] FTBFS with boost1.71)
Your message dated Fri, 05 Jun 2020 14:37:51 +
with message-id
and subject line Bug#948122: fixed in aegisub 3.2.2+dfsg-6
has caused the Debian Bug report #948122,
regarding [aegisub] FTBFS with boost1.71
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.)
--
948122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: aegisub
Version: 3.2.2+dfsg-5
Severity: wishlist
Tags: patch
User: team+bo...@tracker.debian.org
Usertags: boost1.71
Dear Maintainer,
your package fails to build with boost1.71. You can find a build log
attached. If you want to attempt the build yourself, an updated version
of boost-defaults which brings in boost1.71 dependencies can be found
adding this line to your sources.list file:
deb https://people.debian.org/~gio/reprepro gio main
This bug has severity whishlist for the moment, but it will raised to RC
as soon as version 1.71 of Boost is promoted to default.
More specifically, your package fails building because it uses the
deprecated header boost/gil/gil_all.hpp.
Please consider applying the attached patch as soon as possible, which
should fix the problem.
Thanks and all the best, Giovanni.
--
Giovanni Mascellani
Postdoc researcher - Université Libre de Bruxelles
From 3d940069289ccc3adcf5e7544c0af61543ad5b9e Mon Sep 17 00:00:00 2001
From: Giovanni Mascellani
Date: Sat, 4 Jan 2020 10:39:02 +0100
Subject: [PATCH] Fix compilation with Boost 1.71.
---
...0018-Fix-compilation-with-Boost-1.71.patch | 65 +++
debian/patches/series | 1 +
2 files changed, 66 insertions(+)
create mode 100644 debian/patches/0018-Fix-compilation-with-Boost-1.71.patch
diff --git a/debian/patches/0018-Fix-compilation-with-Boost-1.71.patch b/debian/patches/0018-Fix-compilation-with-Boost-1.71.patch
new file mode 100644
index 000..ee7c564
--- /dev/null
+++ b/debian/patches/0018-Fix-compilation-with-Boost-1.71.patch
@@ -0,0 +1,65 @@
+From: Giovanni Mascellani
+Date: Sat, 4 Jan 2020 10:36:17 +0100
+Subject: Fix compilation with Boost 1.71.
+
+Header gil_all.hpp does not exist anymore. This patch uses gil.hpp
+instead.
+---
+ src/colour_button.cpp | 2 +-
+ src/subtitles_provider_libass.cpp | 2 +-
+ src/video_frame.cpp | 2 +-
+ src/video_provider_dummy.cpp | 2 +-
+ 4 files changed, 4 insertions(+), 4 deletions(-)
+
+diff --git a/src/colour_button.cpp b/src/colour_button.cpp
+index f985e62..d176aaa 100644
+--- a/src/colour_button.cpp
b/src/colour_button.cpp
+@@ -18,7 +18,7 @@
+
+ #include "dialogs.h"
+
+-#include
++#include
+
+ wxDEFINE_EVENT(EVT_COLOR, wxThreadEvent);
+
+diff --git a/src/subtitles_provider_libass.cpp b/src/subtitles_provider_libass.cpp
+index 3dc047e..1afd441 100644
+--- a/src/subtitles_provider_libass.cpp
b/src/subtitles_provider_libass.cpp
+@@ -50,7 +50,7 @@
+ #include
+
+ #include
+-#include
++#include
+ #include
+ #include
+
+diff --git a/src/video_frame.cpp b/src/video_frame.cpp
+index 6100058..c51f929 100644
+--- a/src/video_frame.cpp
b/src/video_frame.cpp
+@@ -16,7 +16,7 @@
+
+ #include "video_frame.h"
+
+-#include
++#include
+ #include
+
+ namespace {
+diff --git a/src/video_provider_dummy.cpp b/src/video_provider_dummy.cpp
+index 39eb69e..71a4424 100644
+--- a/src/video_provider_dummy.cpp
b/src/video_provider_dummy.cpp
+@@ -46,7 +46,7 @@
+ #include
+ #include
+ #include
+-#include
++#include
+
+ DummyVideoProvider::DummyVideoProvider(double fps, int frames, int width, int height, agi::Color colour, bool pattern)
+ : framecount(frames)
diff --git a/debian/patches/series b/debian/patches/series
index fd132da..2355a92 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -15,3 +15,4 @@ add-icu-prefix.patch
simplify-version.patch
add-keywords-desktop.patch
fix-crash-spell-language.patch
+0018-Fix-compilation-with-Boost-1.71.patch
--
2.25.0.rc1
aegisub.log.gz
Description: application/gzip
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: aegisub
Source-Version: 3.2.2+dfsg-6
Done: Aniol Marti
We believe that the bug you reported is fixed in the latest version of
aegisub, 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 948...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian
Bug#962218: gnutls28: build fails on IPv6-only buildds
On 2020-06-05 Julien Cristau wrote: > On Thu, Jun 04, 2020 at 11:19:31PM +0200, Julien Cristau wrote: > > The arch:all failure is at grnet and that buildd has both v4 and v6 > > addresses, so presumably unrelated. > > > A further give-back seems to have worked, so 3.6.13-4 managed to build > on all arches and move to testing now. Thank you!
Bug#962173: marked as done (wsjtx: hard-codes boost 1.67)
Your message dated Fri, 5 Jun 2020 15:33:08 +0200 with message-id <20200605133308.ga2645...@msg.df7cb.de> and subject line Re: Bug#962173: wsjtx: hard-codes boost 1.67 has caused the Debian Bug report #962173, regarding wsjtx: hard-codes boost 1.67 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.) -- 962173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wsjtx Version: 2.2.0+repack-1 Severity: serious User: team+bo...@tracker.debian.org Usertags: boost1.71 Control: block 961995 by -1 wsjtx hard-codes he boost version Build-Depends. Since the transition to boost 1.71 is currently ongoing, please switch to the the unversioned packages (libboost-dev) or at least replace it with liboost1.71-dev. Cheers -- Sebastian Ramacher signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Version: 2.2.0+repack-2 Re: Sebastian Ramacher > Source: wsjtx > Version: 2.2.0+repack-1 > Severity: serious > User: team+bo...@tracker.debian.org > Usertags: boost1.71 > Control: block 961995 by -1 > > wsjtx hard-codes he boost version Build-Depends. Since the transition to > boost 1.71 is currently ongoing, please switch to the the unversioned > packages (libboost-dev) or at least replace it with liboost1.71-dev. Fixed in the last upload, but I forgot to mention the bug number in the changelog. Thanks for spotting! Christoph--- End Message ---
Bug#961841: fontforge FTBFS on 64bit big endian: test failures
It appears that upstream commit was already cherry-picked in https://salsa.debian.org/fonts-team/fontforge/-/commit/ad2b5f648241de5920a6f7f738dea091290a0af0, so all it needs is a release (and ideally a mention to this bug in the changelog next to the "add patches cherry-picked upstream to fix a range of issues" line). >
Bug#960326: json-c: CVE-2020-12762
Hi, A fix has landed in json-c-0.12 (which is the upstream used for json-c in Debian Buster): https://github.com/json-c/json-c/commit/f2b7d0b5cbd0eccf4fb3c1851ec0864952be1057 I do not know how to get this fix in Debian's json-c repository https://salsa.debian.org/debian/json-c as there is a branch named debian/buster which contains changes made specifically for Debian and I am unaware of the review/release process of this package. What should be the next steps? Best regards, Armand Grillet
Bug#962276: zfs-linux: FTBFS with current sphinx
Source: zfs-linux Version: 0.8.4-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, zfs-linux recently started to FTBFS with this error: debian/rules override_dh_installdocs make[1]: Entering directory '/build/zfs-linux-0.8.4' dh_installdocs http_proxy='127.0.0.1:9' /usr/share/sphinx/scripts/python3/sphinx-build /usr/bin/sphinx-build -N -bhtml "/build/zfs-linux-0.8.4/contrib/pyzfs/docs/source/" debian/pyzfs-doc/usr/share/doc/pyzfs-doc/html/ usage: sphinx-build [OPTIONS] SOURCEDIR OUTPUTDIR [FILENAMES...] sphinx-build: error: cannot find files ['debian/pyzfs-doc/usr/share/doc/pyzfs-doc/html/'] make[1]: *** [debian/rules:185: override_dh_installdocs] Error 2 This still worked with sphinx 2.4.3-2 a few weeks ago, it does now fail with sphinx 2.4.3-4. Andreas zfs-linux_0.8.4-1.log.gz Description: application/gzip
Bug#962275: snort: Failed to start LSB
Package: snort Version: 2.9.15.1-2 Severity: grave Dear Maintainer, installation of 'snort' fails with a subprocess error (fresh install, /etc/snort doesn't exist before installation. Accepting the propose d network settings: 192.168.0.0/16). Aptitude output: ** Performing actions... Retrieving bug reports... Done Parsing Found/Fixed information... Done Preconfiguring packages ... Snort configuration: interface default not set, using 'eth0' Selecting previously unselected package snort-common-libraries. (Reading database ... 649619 files and directories currently installe d.) Preparing to unpack .../0-snort-common-libraries_2.9.15.1-2_amd64.deb ... Unpacking snort-common-libraries (2.9.15.1-2) ... Preparing to unpack .../1-snort-rules-default_2.9.15.1-2_all.deb ... Unpacking snort-rules-default (2.9.15.1-2) ... Preparing to unpack .../2-snort-common_2.9.15.1-2_all.deb ... Unpacking snort-common (2.9.15.1-2) ... Selecting previously unselected package libdaq2. Preparing to unpack .../3-libdaq2_2.0.7-2_amd64.deb ... Unpacking libdaq2 (2.0.7-2) ... Selecting previously unselected package snort. Preparing to unpack .../4-snort_2.9.15.1-2_amd64.deb ... Unpacking snort (2.9.15.1-2) ... Preparing to unpack .../5-oinkmaster_2.0-4_all.deb ... Unpacking oinkmaster (2.0-4) ... Setting up oinkmaster (2.0-4) ... Setting up snort-common (2.9.15.1-2) ... Setting up libdaq2 (2.0.7-2) ... Setting up snort-rules-default (2.9.15.1-2) ... Setting up snort-common-libraries (2.9.15.1-2) ... Setting up snort (2.9.15.1-2) ... Snort configuration: interface default not set, using 'eth0' WARNING: tempfile is deprecated; consider using mktemp instead. Job for snort.service failed because the control process exited with error code. See "systemctl status snort.service" and "journalctl -xe" for details . invoke-rc.d: initscript snort, action "start" failed. ● snort.service - LSB: Lightweight network intrusion detection system Loaded: loaded (/etc/init.d/snort; generated) Active: failed (Result: exit-code) since Fri 2020-06-05 13:41:4 3 CEST; 5ms ago Docs: man:systemd-sysv-generator(8) Process: 259261 ExecStart=/etc/init.d/snort start (code=exited, status=1/FAILURE) Jun 05 13:41:43 holly systemd[1]: Starting LSB: Lightweight network i ntrusion detection system... Jun 05 13:41:43 holly snort[259261]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface configuration, using /etc/snort/snort.conf Jun 05 13:41:43 holly snort[259273]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface configuration, using /etc/sno Jun 05 13:41:43 holly snort[259261]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface con Jun 05 13:41:43 holly snort[259275]: Starting Jun 05 13:41:43 holly systemd[1]: snort.service: Control process exit ed, code=exited, status=1/FAILURE Jun 05 13:41:43 holly systemd[1]: snort.service: Failed with result ' exit-code'. Jun 05 13:41:43 holly systemd[1]: Failed to start LSB: Lightweight ne twork intrusion detection system. dpkg: error processing package snort (--configure): installed snort package post-installation script subprocess returne d error exit status 1 Processing triggers for systemd (245.5-3) ... Processing triggers for man-db (2.9.2-1) ... Processing triggers for libc-bin (2.30-8) ... Errors were encountered while processing: snort [ Rootkit Hunter version 1.4.6 ] File updated: searched for 181 files, found 152 needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) Setting up snort (2.9.15.1-2) ... Snort configuration: interface default set, using eth0 WARNING: tempfile is deprecated; consider using mktemp instead. Job for snort.service failed because the control process exited with error code. See "systemctl status snort.service" and "journalctl -xe" for details . invoke-rc.d: initscript snort, action "start" failed. ● snort.service - LSB: Lightweight network intrusion detection system Loaded: loaded (/etc/init.d/snort; generated) Active: failed (Result: exit-code) since Fri 2020-06-05 13:41:5 4 CEST; 4ms ago Docs: man:systemd-sysv-generator(8) Process: 269896 ExecStart=/etc/init.d/snort start (code=exited, status=1/FAILURE) Jun 05 13:41:54 holly systemd[1]: Starting LSB: Lightweight network i ntrusion detection system... Jun 05 13:41:54 holly snort[269896]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface configuration, using /etc/snort/snort.conf Jun 05 13:41:54 holly snort[269907]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface configuration, using /etc/sno Jun 05 13:41:54 holly snort[269896]: Starting Network Intrusion Detec tion System : snort (eth0 no specific interface con Jun 05 13:41:54 holly snort[269909]: Starting Jun 05 13:41:54 holly
Bug#962262: opendmarc fails many emails without apparent reason
Package: opendmarc Version: 1.3.2-6+deb10u1 Severity: grave Justification: renders package unusable Dear Maintainer, I started using DMARC and DKIM using both opendkim for signing and verification of DKIM Signatures and opendmarc to check policies regarding domain alignment, report failurs, reject failed emails. As I added myself in the CC I started wondering about the many failures. So I removed reject go get the emails and check myself why they failed. Example: Return-Path: Received: from smtp-8fb4.mail.infomaniak.ch (smtp-8fb4.mail.infomaniak.ch [IPv6:2001:1600:4:17:0:0:0:8fb4]) by magma.woody.ch (8.15.2/8.15.2/Debian-14~deb10u1) with ESMTPS id 0558TFJS016651 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT) for ; Fri, 5 Jun 2020 10:29:16 +0200 Authentication-Results: magma.woody.ch; dkim=pass (1024-bit key; secure) header.d=infomaniak.com header.i=@infomaniak.com header.b="CbZg5UxD"; dkim-atps=neutral Authentication-Results: OpenDMARC; dmarc=fail (p=reject dis=none) header.from=infomaniak.com Received: from h2dmu11.infomaniak.ch (unknown [128.65.195.40]) by smtp-3-1000.mail.infomaniak.ch (Postfix) with ESMTP id 49dbQr0WTqzlhZQ3; Fri, 5 Jun 2020 10:29:08 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=infomaniak.com; s=s1024; t=1591345748; bh=HHIYggwIYZM6Vv4Bqgw/PkqYPHF6PS4+bI/YdDSwMTI=; h=Date:Subject:From:To:References:In-Reply-To:From; b=CbZg5UxD8cVHlHVrsN2hDsaQrLFuflU8C9FQUQtyiBENgVwOjBvkvs7kIlUdFeJLK FZxplJjqTuBHGEny4W6zaaQJOcABz7dmPJbESItpdaHMPjFX+vfm/g5aKxEr1FJJLT F9lSw+3D/0+l+IhQ84TiwbXVXfSm5MktamR/Q3gk= Received: from tickets.infomaniak.ch (localhost [127.0.0.1]) by h2dmu11.infomaniak.ch (8.14.5/8.14.5) with ESMTP id 0558T7lD002901; Fri, 5 Jun 2020 10:29:08 +0200 Message-ID: Date: Fri, 05 Jun 2020 10:29:07 +0200 Subject: Re: [support #INK-ZIB-19449-823] Abuse report about 128.65.195.112 From: Support Infomaniak Network To: nicolask...@hotmail.com, nob...@woody.ch MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 X-Mailer: Cerb 9.3.8 (Build 2019112401) References: In-Reply-To: [...] X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.5.11 (magma.woody.ch [IPv6:2001:4060:dead:beef:0:0:0:1]); Fri, 05 Jun 2020 10:29:16 +0200 (CEST) [...] X-SNCH-Report: Start der SNCH-SpamAssassin Auswertung 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% [score: 0.5000] -0.0 SPF_PASS SPF: sender matches SPF record 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature -0.1 DKIM_VALID_EF Message has a valid DKIM or DK signature from envelope-from domain 0.1 DKIM_SIGNEDMessage has a DKIM or DK signature, not necessarily valid Ende der SNCH-SpamAssassin Auswertung As you see, opendkim verified the signature and this passed. Milter-Greylist passed SPF Test SpamAssassin passed SPF and DKIM Tests opendmarc would have rejected this email because of a policy failure (yes, another one of that source got rejected) So let's check that: Envelope Sender: supp...@infomaniak.com From Header: supp...@infomaniak.com Allignment strict! infomaniak.com descriptive text "v=spf1 include:spf.infomaniak.ch include:_spf.mailrelay.rrpproxy.net -all" relay.mail.infomaniak.ch descriptive text "v=spf1 ip4:45.157.188.8/29 ip4:185.125.25.8/29 ip4:83.166.143.168/29 ip4:84.16.66.168/29 ip6:2001:1600:3:17::/64 ip6:2001:1600:4:17::/64 -all" Sender IP ist part of the SPF entry. I come to no other conclusion, that email should have passed SFP / DKIM and the whole DMARC Test. So I have to assume, opendmarc has a serious bug which causes those tests to fail in many cases. Unfortunately i have not found any debug options which would lead to an outpout showing WHY exactly opendmarc is failing on such emails. Please advise. -Benoît- -- System Information: Debian Release: 10.4 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-9-amd64 (SMP w/4 CPU cores) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE=de_CH:de (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages opendmarc depends on: ii adduser3.118 ii dbconfig-mysql 2.0.11+deb10u1 ii debconf [debconf-2.0] 1.5.71 ii libbsd00.9.1-2 ii libc6 2.28-10 ii libmilter1.0.1
Processed: block 962273 with 956955
Processing commands for cont...@bugs.debian.org: > block 962273 with 956955 Bug #962273 [src:vault] vault: FTBFS due to failing tests 962273 was not blocked by any bugs. 962273 was not blocking any bugs. Added blocking bug(s) of 962273: 956955 > thanks Stopping processing here. Please contact me if you need assistance. -- 962273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962273 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962217: marked as done (libgdf: autopkgtest needs update for new version of boost-defaults: deprecation warning on stderr)
Your message dated Fri, 05 Jun 2020 12:48:42 +
with message-id
and subject line Bug#962217: fixed in libgdf 0.1.3-4
has caused the Debian Bug report #962217,
regarding libgdf: autopkgtest needs update for new version of boost-defaults:
deprecation warning on stderr
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.)
--
962217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962217
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgdf
Version: 0.1.3-3
Severity: serious
Tags: sid bullseye
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:boost-defaults
[X-Debbugs-CC: debian...@lists.debian.org,
boost-defau...@packages.debian.org]
Dear maintainer(s),
With a recent upload of boost-defaults the autopkgtest of libgdf fails
in testing when that autopkgtest is run with the binary packages of
boost-defaults from unstable. It passes when run with only packages from
testing. In tabular form:
passfail
boost-defaults from testing1.71.0.3
libgdf from testing0.1.3-3
all others from testingfrom testing
I copied some of the output at the bottom of this report. If possible,
disable deprecation warnings as autopkgtest is not the place to test for
those or, if that's not possible, add the allow-stderr restriction such
that these warnings will be ignored.
Currently this regression is blocking the migration of boost-defaults to
testing [1]. Of course, boost-defaults shouldn't just break your
autopkgtest (or even worse, your package), but it seems to me that the
change in boost-defaults was intended and your package needs to update
to the new situation.
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=boost-defaults
https://ci.debian.net/data/autopkgtest/testing/amd64/libg/libgdf/5757118/log.gz
Copying data OK
Copying events
reading non-equidistant samples (NEQS) ... OK
writing non-equidistant samples .
OK
Comparing files OK
Removing test.gdf.tmp
autopkgtest [23:08:06]: test compile-and-run-tests: ---]
autopkgtest [23:08:07]: test compile-and-run-tests: - - - - - - - - - -
results - - - - - - - - - -
compile-and-run-tests FAIL stderr: In file included from
/usr/include/boost/detail/endian.hpp:9,
autopkgtest [23:08:07]: test compile-and-run-tests: - - - - - - - - - -
stderr - - - - - - - - - -
In file included from /usr/include/boost/detail/endian.hpp:9,
from /usr/include/GDF/Types.h:24,
from /usr/include/GDF/HeaderItem.h:22,
from /usr/include/GDF/SignalHeader.h:22,
from /usr/include/GDF/Channel.h:22,
from /usr/include/GDF/RecordBuffer.h:22,
from /usr/include/GDF/Writer.h:22,
from testCreateGDF.cpp:19:
/usr/include/boost/predef/detail/endian_compat.h:11:161: note: #pragma
message: The use of BOOST_*_ENDIAN and BOOST_BYTE_ORDER is deprecated.
Please include and use BOOST_ENDIAN_*_BYTE
instead
11 | #pragma message("The use of BOOST_*_ENDIAN and BOOST_BYTE_ORDER
is deprecated. Please include and use
BOOST_ENDIAN_*_BYTE instead")
|
^
In file included from /usr/include/boost/detail/endian.hpp:9,
from /usr/include/GDF/Types.h:24,
from /usr/include/GDF/HeaderItem.h:22,
from /usr/include/GDF/SignalHeader.h:22,
from /usr/include/GDF/Channel.h:22,
from /usr/include/GDF/Record.h:22,
from /usr/include/GDF/Reader.h:22,
from testDataTypes.cpp:21:
/usr/include/boost/predef/detail/endian_compat.h:11:161: note: #pragma
message: The use of BOOST_*_ENDIAN and BOOST_BYTE_ORDER is deprecated.
Please include and use BOOST_ENDIAN_*_BYTE
instead
11 | #pragma message("The use of BOOST_*_ENDIAN and BOOST_BYTE_ORDER
is deprecated. Please include and use
BOOST_ENDIAN_*_BYTE instead")
|
^
In file included from /usr/include/boost/detail/endian.hpp:9,
from /usr/include/GDF/Types.h:24,
from /usr/include/GDF/HeaderItem.h:22,
from /usr/include/GDF/SignalHeader.h:22,
from /usr/include/GDF/Channel.h:22,
from /usr/include/GDF/RecordBuffer.h:22,
from /usr/include/GDF/Writer.h:22,
Bug#962263: marked as done (nvidia-cuda-toolkit: missing libjpeg62-dev dependency)
Your message dated Fri, 5 Jun 2020 14:36:39 +0200 with message-id <4ca4f201-6e4b-56f4-867a-6371962a1...@debian.org> and subject line Re: Bug#962263: nvidia-cuda-toolkit: missing libjpeg62-dev dependency has caused the Debian Bug report #962263, regarding nvidia-cuda-toolkit: missing libjpeg62-dev dependency 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.) -- 962263: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962263 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nvidia-cuda-toolkit Version: 10.1.243-5 Severity: serious tags: patch Hello, looks like that control file is missing an explicit libjpeg62-dev dependency, and this fails when a different jpeg implementation is default in the system. dpkg-shlibdeps: error: cannot find library libjpeg.so.62 needed by debian/nvidia-openjdk-8-jre/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/libsplashscreen.so (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64') --- nvidia-cuda-toolkit-10.1.243/debian/changelog 2020-06-03 09:54:22.0 +0200 +++ nvidia-cuda-toolkit-10.1.243/debian/changelog 2020-06-05 08:09:24.0 +0200 @@ -1,3 +1,9 @@ +nvidia-cuda-toolkit (10.1.243-5.1) unstable; urgency=medium + + * Add missing libjpeg62 dependency to fix build failure (Closes: #-1) + + -- Gianfranco Costamagna Fri, 05 Jun 2020 08:09:24 +0200 + nvidia-cuda-toolkit (10.1.243-5) unstable; urgency=medium * Merge changes from 10.1.168-11. diff -Nru nvidia-cuda-toolkit-10.1.243/debian/control nvidia-cuda-toolkit-10.1.243/debian/control --- nvidia-cuda-toolkit-10.1.243/debian/control 2020-06-03 09:54:22.0 +0200 +++ nvidia-cuda-toolkit-10.1.243/debian/control 2020-06-05 08:09:24.0 +0200 @@ -42,6 +42,7 @@ liblcms2-dev, libpcsclite-dev, libpng-dev, + libjpeg62, (please don't use libjpeg62-dev package, because it conflicts with the turbo one, and makes the package bd-uninstallable) Cheers Gianfranco --- End Message --- --- Begin Message --- Hello On Fri, 5 Jun 2020 13:47:53 +0200 Andreas Beckmann wrote: > On 05/06/2020 11.17, Gianfranco Costamagna wrote: > > Hello, looks like that control file is missing an explicit libjpeg62-dev > > dependency, and this fails when > > a different jpeg implementation is default in the system. > > > > dpkg-shlibdeps: error: cannot find library libjpeg.so.62 needed by > > debian/nvidia-openjdk-8-jre/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/libsplashscreen.so > > (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: > > '/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64') > > That is on Ubuntu? > yes, closing this bug, since Graham is already taking care of it! G. > Andreas > > --- End Message ---
Bug#962273: vault: FTBFS due to failing tests
Source: vault Version: 1.0.2+dfsg2-5 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, vault recently started to FTBFS due to some failing tests, see the attached buildlog for details. I don't see anywhere in the log *what* failed, only *that* some test failed. In my logs I have a successful build from March (when the package was uploaded) and a failure from May 18, reproducible today. Andreas vault_1.0.2+dfsg2-5.log.gz Description: application/gzip
Bug#962263: nvidia-cuda-toolkit: missing libjpeg62-dev dependency
On 05/06/2020 11.17, Gianfranco Costamagna wrote: > Hello, looks like that control file is missing an explicit libjpeg62-dev > dependency, and this fails when > a different jpeg implementation is default in the system. > > dpkg-shlibdeps: error: cannot find library libjpeg.so.62 needed by > debian/nvidia-openjdk-8-jre/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/libsplashscreen.so > (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: > '/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64') That is on Ubuntu? Andreas
Bug#962090: Same Issue with a Python3 Project for Buster
> "pyversions" is part of package "python2-minimal". Why python2-minimal if I > build a Python3 project? "p3versions" is part of package "python3-minimal". But "/usr/share/perl5/Debian/Debhelper/Buildsystem/python_distutils.pm" calls the external script explicitly (`pyversions`) in line 124. "python_distutils.pm" should be updated for Python3 builds using "py3versions" - right? Notwithstanding, if I add "python2-minimal" package to my build dependencies the Python3 project will be built.
Bug#962271: libncurses5-dev: Dependency issue
Package: libncurses5-dev Version: 6.1+20181013-2+deb10u2 Severity: serious Justification: Installing libncurses5-dev installs libncurses6 from libncurses-dev and not Hello, I noticed that if i install libncurses5-dev i get libncurses6 which breaks software which still relay on libncurse5. I believe installing libncurses5-dev should bring everything that is libncurses5 not libncurses6. Thanks. --- malnajdi@debian:~$ apt-cache depends libncurses5-dev libncurses5-dev Depends: libtinfo6 Depends: libncurses-dev --- malnajdi@debian:~$ apt-cache depends libncurses-dev libncurses-dev Depends: libtinfo6 Depends: libncurses6 Depends: libncursesw6 |Depends: libc6-dev Depends: libc6-dev Depends: ncurses-bin Conflicts: Breaks: libncurses5-dev Breaks: libncursesw5-dev Breaks: libtinfo-dev Suggests: ncurses-doc Replaces: libncurses5-dev Replaces: libncursesw5-dev Replaces: libtinfo-dev Replaces: ncurses-bin Replaces: libncurses-dev ---
Bug#958848: marked as done (pytest (build-)depends on pypy-funcsigs which the maintainer would like to get rid of.)
Your message dated Fri, 05 Jun 2020 11:18:59 + with message-id and subject line Bug#958848: fixed in pytest 4.6.10-1 has caused the Debian Bug report #958848, regarding pytest (build-)depends on pypy-funcsigs which the maintainer would like to get rid of. 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.) -- 958848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pytest Version: 4.6.9-3 x-debbugs-cc: vangua...@packages.debian.org As discussed in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937769 the maintainer of the python-funcsigs source package (which builds the python-funcsigs, python3-funcsigs and pypy-funcsigs binary packages) would like to get rid of the python-funcsigs source package completely rather than simply removing cpython 2 support from it. pypy-pytest depends on and the pytest source package build-depends on the pypy-funcsigs package. I am assuming that removing the dependency on this package would mean dropping the pypy-pytest binary package. checking reverse dependencies with dak reveals. # Broken Build-Depends: python-atomicwrites: pypy-pytest python-pluggy: pypy-pytest python-py: pypy-pytest setuptools-scm: pypy-pytest vanguards: pypy-pytest wcwidth: pypy-pytest most of these seem to be python module packages that are maintained by the python modules team and build pypy modules to directly or indirectly support pypy-pytest. vanguards on the other hand is an application which I assume relies on pytest for it's testsuite. So I guess the question is whether it is worth keeping this pile of pypy modules around to support the testsuite of one application? --- End Message --- --- Begin Message --- Source: pytest Source-Version: 4.6.10-1 Done: =?utf-8?b?T25kxZllaiBOb3bDvQ==?= We believe that the bug you reported is fixed in the latest version of pytest, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ondřej Nový (supplier of updated pytest 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, 05 Jun 2020 13:03:24 +0200 Source: pytest Architecture: source Version: 4.6.10-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Ondřej Nový Closes: 958848 959974 Changes: pytest (4.6.10-1) unstable; urgency=medium . * New upstream release. * Drop PyPy support (Closes: #958848) * Set Rules-Requires-Root: no. * Bump Standards-Version to 4.5.0. * Bump debhelper compat level to 13. * d/tests/smoketest-3: Use supported not installed Python versions. * Fix doc-base and add symlinks for docs (Closes: #959974). Checksums-Sha1: b984fcd63f28e2887eaf850eab80f9cfb7f21812 2461 pytest_4.6.10-1.dsc 93384000ec4e04500b97cba18a2fdb193b07f7eb 951516 pytest_4.6.10.orig.tar.gz 51164499bbcd8a4dc22e145be38c0d82da0e41f5 11204 pytest_4.6.10-1.debian.tar.xz 711a5f4548188a2fbe77a05d2d79b384aa0c9544 8225 pytest_4.6.10-1_amd64.buildinfo Checksums-Sha256: 4e3bfcdfd9273431ddd5a9cd44ea31e46cf18b16c478dc508d2c69758ee59695 2461 pytest_4.6.10-1.dsc 0031b5021e1204f12e5a044500fbf31e3f64c6f2d69ded910af003abd0d91ae4 951516 pytest_4.6.10.orig.tar.gz ccafe1bfa03904a8266cbf25999f96e46550d5953fc040776c5cb1f2f1f60ca2 11204 pytest_4.6.10-1.debian.tar.xz 0beaa3298d857d3c089b19d54ec80a6632e435c8e7e08586868779f9d70a06a5 8225 pytest_4.6.10-1_amd64.buildinfo Files: 26c9c3a1181b7f656d7917b46b4bcad9 2461 python optional pytest_4.6.10-1.dsc 476f58ed4df73be92dfa16a8d10e1072 951516 python optional pytest_4.6.10.orig.tar.gz 47d96c99fabf2eaf8919801ab2d19266 11204 python optional pytest_4.6.10-1.debian.tar.xz c2db24a15642e3bbdbcc771ca7a2c381 8225 python optional pytest_4.6.10-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAl7aJ80ACgkQNXMSVZ0e BkvCog/+LBa6sSdWmFPHcrxmizL2JYlTzo1410fElcYQ3u+DNkTAHqp7GuO61tOF oGXnok2QkBoxV/n8Rc5OfAGhIOUu/imzaQ/3tumDjjZY3TauX6O2R8SHtzCwQU7u sngtCjxFVyOjuyFZAD7XRewYbIf2fXgMj63WBl+0ZIuXdawUJWDUCfg1Al7LQ5gM
Bug#952331: iso-flags-svg: FTBFS: rsvg-convert -o build/png-country-4x2-fancy/res-320x240/mv.png -w 320 -h 240 build/svg-country-4x2-fancy/mv.svg # [31mfail[0m:
Il 23/02/2020 14:43, Lucas Nussbaum ha scritto: > Source: iso-flags-svg > Version: 1.0.2-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200222 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > ... > The full build log is available from: >http://qa-logs.debian.net/2020/02/22/iso-flags-svg_1.0.2-1_unstable.log > > A list of current common problems and possible solutions is available at > http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! > > About the archive rebuild: The rebuild was done on EC2 VM instances from > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every > failed build was retried once to eliminate random failures. > As spotted by Norbert Preining seems rsvg-convert bug that has been fixed in newer releases and we are unable to reproduce it. It is still reproducible by someone?
Bug#955157: marked as done (upx-ucl: autopkgtest regression: basic-check Segmentation fault)
Your message dated Fri, 05 Jun 2020 10:34:08 +
with message-id
and subject line Bug#955157: fixed in upx-ucl 3.96-2
has caused the Debian Bug report #955157,
regarding upx-ucl: autopkgtest regression: basic-check Segmentation fault
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.)
--
955157: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=955157
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: upx-ucl
Version: 3.96-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of upx-ucl the autopkgtest of upx-ucl fails in
testing when that autopkgtest is run with the binary packages of upx-ucl
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
upx-uclfrom testing3.96-1
versioned deps [0] from testingfrom unstable
all others from testingfrom testing
I copied some of the output at the bottom of this report.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[1] https://qa.debian.org/excuses.php?package=upx-ucl
https://ci.debian.net/data/autopkgtest/testing/amd64/u/upx-ucl/4693222/log.gz
autopkgtest [18:38:05]: test basic-check: [---
+ cp /bin/ls /tmp/tmp.Wq2JAZbAI0
+ upx-ucl ./ls
Ultimate Packer for eXecutables
Copyright (C) 1996 - 2020
UPX 3.96Markus Oberhumer, Laszlo Molnar & John Reiser Jan 23rd
2020
File size Ratio Format Name
-- --- ---
138848 -> 67100 48.33% linux/arm64 ls
Packed 1 file.
+ ./ls -al
Segmentation fault
autopkgtest [18:38:05]: test basic-check: ---]
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: upx-ucl
Source-Version: 3.96-2
Done: Robert Luberda
We believe that the bug you reported is fixed in the latest version of
upx-ucl, 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 955...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Robert Luberda (supplier of updated upx-ucl 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: Fri, 05 Jun 2020 12:14:39 +0200
Source: upx-ucl
Architecture: source
Version: 3.96-2
Distribution: unstable
Urgency: medium
Maintainer: Robert Luberda
Changed-By: Robert Luberda
Closes: 955157
Changes:
upx-ucl (3.96-2) unstable; urgency=medium
.
* Add 02-arm64-crashes.patch that reverts one of upstream commits, what
should
fix crashes visible on arm64 (closes: 955157).
* Bump debhelper's compat version to 13.
Checksums-Sha1:
ff51269e694c87bf775b1f8066f30ef498ced5bd 1867 upx-ucl_3.96-2.dsc
eef1306a2c120a9cc8b5ea6ce07ae2ee43eb9ab0 58104 upx-ucl_3.96-2.debian.tar.xz
3695563cd3d57e3857737c458673487be1185fc0 5883 upx-ucl_3.96-2_amd64.buildinfo
Checksums-Sha256:
5d8697d02ca2321d8fe6d9ca9f33294edf3e8728159b7affb6ccbe3ec4221385 1867
upx-ucl_3.96-2.dsc
1c6625ed86e318a6413647fb561279c0dbd9871bd673c9163c93c789882522a2 58104
upx-ucl_3.96-2.debian.tar.xz
f78ed2bc0b08107159c94b9245244df561a16875a1fc627fac21382d498ffe0c 5883
upx-ucl_3.96-2_amd64.buildinfo
Files:
521f5a6ff1001e0b3a2322fd8601f5f1 1867 utils optional upx-ucl_3.96-2.dsc
a6ae5bbf5ddd7db5862c96daf5f68863 58104 utils optional
upx-ucl_3.96-2.debian.tar.xz
4d03fd23ae1194bbc075a84e94997712 5883 utils optional
upx-ucl_3.96-2_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEENeh2+rTTcy6TtNI3Yx3nVTvor9QFAl7aHEAACgkQYx3nVTvo
r9SESBAAjFtLQUhSUTiZbfWCJh7tdW2mLBnO6BLeoJB92pnjue4NnwdM5tXwkXdu
QT4Qq8BcXFktLu+gTlKBmlktOdBCMDk/0M4RhYCCkjaUs+6+X6Gim8W6jWbShYYG
X18wlz4Hflz17vXw09jMEpfl3NAQXUtQG5U0+ZsU+M4yaxkqqrZh8Y3pG4AZ
7mEuhFNS0vWHOYjW3d1ZxdbLxg/YC13NNKnlQYuWW1Q8gUr3Pu5C/ErRlTiSLa3E
Processed: found 962173 in 2.2.0~rc1+repack-1
Processing commands for cont...@bugs.debian.org: > found 962173 2.2.0~rc1+repack-1 Bug #962173 [src:wsjtx] wsjtx: hard-codes boost 1.67 Marked as found in versions wsjtx/2.2.0~rc1+repack-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 962173: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962218: gnutls28: build fails on IPv6-only buildds
On Thu, Jun 04, 2020 at 11:19:31PM +0200, Julien Cristau wrote: > The arch:all failure is at grnet and that buildd has both v4 and v6 > addresses, so presumably unrelated. > A further give-back seems to have worked, so 3.6.13-4 managed to build on all arches and move to testing now. Cheers, Julien
Bug#962217: marked as pending in libgdf
Control: tag -1 pending Hello, Bug #962217 in libgdf 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/neurodebian-team/libgdf/-/commit/51a737871ecc665c70c8be6733b2867d621aa805 Allow stderr in unit tests This allows autopkgtest to pass with libboost 1.71, since messages regarding the deprecation of BOOST_*_ENDIAN BOOST_BYTE_ORDER are issued at compilation time. This is a quick fix while waiting for the problem to be fixed upstream. Gbp-Dch: Full Closes: #962217 (this message was generated automatically) -- Greetings https://bugs.debian.org/962217
Processed: Bug#962217 marked as pending in libgdf
Processing control commands: > tag -1 pending Bug #962217 [src:libgdf] libgdf: autopkgtest needs update for new version of boost-defaults: deprecation warning on stderr Added tag(s) pending. -- 962217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962269: haskell-hakyll: build-depends on missing: libghc-file-embed-dev:amd64 (< 0.0.12)
Source: haskell-hakyll Version: 4.13.3.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) haskell-hakyll is stuck in BD-Uninstallable: | haskell-hakyll build-depends on missing: | - libghc-file-embed-dev:amd64 (< 0.0.12) haskell-file-embed is at version 0.0.12.0-1 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: tagging 962265
Processing commands for cont...@bugs.debian.org: > tags 962265 - bullseye sid Bug #962265 [src:sword] sword silently loses ICU support when built with ICU without icu-config Removed tag(s) bullseye and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 962265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#958848 marked as pending in pytest
Processing control commands: > tag -1 pending Bug #958848 [src:pytest] pytest (build-)depends on pypy-funcsigs which the maintainer would like to get rid of. Added tag(s) pending. -- 958848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#958848: marked as pending in pytest
Control: tag -1 pending Hello, Bug #958848 in pytest 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/pytest/-/commit/2f18c525fd7ead65324ebba3c012652275edfb31 Drop PyPy support (Closes: #958848) (this message was generated automatically) -- Greetings https://bugs.debian.org/958848
Bug#962252: marked as done (orthanc-mysql FTBFS with boost1.71)
Your message dated Fri, 05 Jun 2020 09:32:19 + with message-id and subject line Bug#962252: fixed in orthanc-mysql 2.0-3 has caused the Debian Bug report #962252, regarding orthanc-mysql FTBFS with boost1.71 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.) -- 962252: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: orthanc-mysql Version: 2.0-2 Severity: serious Tags: ftbfs bullseye sid Control: block 961995 by -1 https://buildd.debian.org/status/package.php?p=orthanc-mysql ... -- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake (found version "1.71.0") CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake:182 (boost_find_component): boost_find_component Macro invoked with incorrect arguments for macro named: boost_find_component Call Stack (most recent call first): /usr/share/cmake-3.16/Modules/FindBoost.cmake:443 (find_package) /<>/Build/Orthanc-1.5.2/Resources/CMake/BoostConfiguration.cmake:15 (find_package) /<>/Build/Orthanc-1.5.2/Resources/CMake/OrthancFrameworkConfiguration.cmake:417 (include) /<>/Resources/CMake/DatabasesFrameworkConfiguration.cmake:62 (include) /<>/Resources/CMake/DatabasesPluginConfiguration.cmake:21 (include) CMakeLists.txt:18 (include) orthanc-mysql builds an own copy of src:orthanc, and this copy does not have #953884 fixed. --- End Message --- --- Begin Message --- Source: orthanc-mysql Source-Version: 2.0-3 Done: Sebastien Jodogne We believe that the bug you reported is fixed in the latest version of orthanc-mysql, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Jodogne (supplier of updated orthanc-mysql 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, 05 Jun 2020 10:33:02 +0200 Source: orthanc-mysql Architecture: source Version: 2.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Sebastien Jodogne Closes: 962252 Changes: orthanc-mysql (2.0-3) unstable; urgency=medium . * Updated Orthanc framework to 1.7.0. Closes: #962252 Checksums-Sha1: 54e54d34af371f9e2e4d6d50eef863d831ccf113 2165 orthanc-mysql_2.0-3.dsc 3fee3445d204401f15ee9ec52a9f7b7a0472e433 423536 orthanc-mysql_2.0-3.debian.tar.xz 6f43a4ef1b7ae8542db3851e9f56fa1a9bf835c7 13486 orthanc-mysql_2.0-3_source.buildinfo Checksums-Sha256: 97c77965ea8e7b8b3ca321b6a36510d14d82db78d1d46c6005fde22ce41bd033 2165 orthanc-mysql_2.0-3.dsc ff67957b733d897a18da1da67ec471086136716c98e7c7a6b4fc500f767db5d8 423536 orthanc-mysql_2.0-3.debian.tar.xz ff60a040c5559c1fa92dd7932203d3134039b3d09842e829150aa86ef477cb8c 13486 orthanc-mysql_2.0-3_source.buildinfo Files: 97d0a771f531c5a80e5fd981e50d923d 2165 science optional orthanc-mysql_2.0-3.dsc b6eae540dcb407174b38f153eb9bb8c8 423536 science optional orthanc-mysql_2.0-3.debian.tar.xz a18e31e1e80e0d9635f06cd916bac443 13486 science optional orthanc-mysql_2.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEk76fGX7V0MMOWT2Lp3ZYKzEqw10FAl7aCtIUHHMuam9kb2du ZUBnbWFpbC5jb20ACgkQp3ZYKzEqw10P7w//f3f2gT18dqgFWbw7ts0dDQ0DqZ02 L3YJyLWcb43ewlbeS7nz09l47H7fIefVn/0OV/f0gKinjci4LvLsYNrAfOamE5SP D4yBdtTUqqb19k9O6fbsAPtbg/DQ3bN/uadZaYgD6od8XgMP82SAtCFhbtPG/hZX YqCvHY8kS4Xyxb+f/H6/JU90ikulkYd1uBI56Kr8+F/d79Ox8RncZBgBmNRoovx3 cSLLmwVztdd4hE2sKFzO33arQBRUcOdnee7RjnUkHbJS0Def6qp0b2m3srOFWSGR Onsgw3mfjt5/V9DB4QWMyqtXu0xfVxanPoL1XHXXeVJjdE9a+G7DAshWbXKAFpLv 1TCaj0JBqYtDJpn76sjnXTzzdrox3tWuiC2jI5Og4XtkBLY1aJbxh3IQ8OZHNGQ7 WBmOE6n7F50iHg8h4zMulSPflM4mSqu2ml+hPce/RjwUQLbWg7c5vBkcDVvHoZKe vLB0eZji2FjaNsd60jZE0HMZX2M3IbEhbp8gffWyJ/65zP/6WNhMlNFDD77z8JuO me5gTX5Zx1Kpecq1tnkMnwTRfhbptG2Klj6q5QgANs0t9D966CS4qPC9oy/QZeLX 462RNnws4qOeJljNr1lFCeMdY+uLL/p7VinIeeVheHAWEdK8uTyuT8LuFsC7zTMX T3KtjVlSZUrmUBU= =i/1B -END PGP SIGNATURE End Message ---
Processed: Re: Bug#962194: lintian-brush: autopkgtest failure on s390x
Processing control commands: > severity -1 serious Bug #962194 [src:lintian-brush] lintian-brush: autopkgtest failure on s390x Severity set to 'serious' from 'normal' -- 962194: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962194 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: sword silently loses ICU support when built with ICU without icu-config
Processing control commands: > block 960193 by -1 Bug #960193 [release.debian.org] transition: icu 960193 was blocked by: 962069 960239 959756 960241 960236 960263 960374 955114 960243 960237 960623 962095 960193 was not blocking any bugs. Added blocking bug(s) of 960193: 962265 -- 960193: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960193 962265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962265 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962265: sword silently loses ICU support when built with ICU without icu-config
Source: sword Version: 1.8.1+dfsg-8 Severity: serious Tags: bullseye sid Control: block 960193 by -1 https://buildd.debian.org/status/package.php?p=sword ... checking for icu-config... no *** The icu-config script installed by icu could not be found *** compiling without ICU support ... Dependencies for standard use: REGEX:yes ZLIB: yes LIBICU: no LIBCURL: yes CLUCENE-CORE: yes 2.x ... This is due to icu (63.1-6) unstable; urgency=medium * Build without icu-config (closes: #898820). ... -- Laszlo Boszormenyi (GCS) Wed, 23 Jan 2019 16:51:20 +
Processed: tagging 962253
Processing commands for cont...@bugs.debian.org: > tags 962253 + ftbfs Bug #962253 [esys-particle] esys-particle: Broken section number in manpage Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 962253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962253 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 937049
Processing commands for cont...@bugs.debian.org: > tags 937049 + ftbfs Bug #937049 [src:mini-buildd] mini-buildd: Python2 removal in sid/bullseye Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 937049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937049 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962263: nvidia-cuda-toolkit: missing libjpeg62-dev dependency
Source: nvidia-cuda-toolkit Version: 10.1.243-5 Severity: serious tags: patch Hello, looks like that control file is missing an explicit libjpeg62-dev dependency, and this fails when a different jpeg implementation is default in the system. dpkg-shlibdeps: error: cannot find library libjpeg.so.62 needed by debian/nvidia-openjdk-8-jre/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64/libsplashscreen.so (ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: '/usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64') --- nvidia-cuda-toolkit-10.1.243/debian/changelog 2020-06-03 09:54:22.0 +0200 +++ nvidia-cuda-toolkit-10.1.243/debian/changelog 2020-06-05 08:09:24.0 +0200 @@ -1,3 +1,9 @@ +nvidia-cuda-toolkit (10.1.243-5.1) unstable; urgency=medium + + * Add missing libjpeg62 dependency to fix build failure (Closes: #-1) + + -- Gianfranco Costamagna Fri, 05 Jun 2020 08:09:24 +0200 + nvidia-cuda-toolkit (10.1.243-5) unstable; urgency=medium * Merge changes from 10.1.168-11. diff -Nru nvidia-cuda-toolkit-10.1.243/debian/control nvidia-cuda-toolkit-10.1.243/debian/control --- nvidia-cuda-toolkit-10.1.243/debian/control 2020-06-03 09:54:22.0 +0200 +++ nvidia-cuda-toolkit-10.1.243/debian/control 2020-06-05 08:09:24.0 +0200 @@ -42,6 +42,7 @@ liblcms2-dev, libpcsclite-dev, libpng-dev, + libjpeg62, (please don't use libjpeg62-dev package, because it conflicts with the turbo one, and makes the package bd-uninstallable) Cheers Gianfranco
Bug#962253: debhelper: dh_installman error instead of warning on invalid section
Control: reassign -1 esys-particle Control: retitle -1 esys-particle: Broken section number in manpage Adrian Bunk: > On Fri, Jun 05, 2020 at 07:55:33AM +0200, Niels Thykier wrote: >> Adrian Bunk: >>> Source: debhelper >>> Version: 13.1 >>> Severity: serious >>> Control: affects -1 src:esys-particle >>> Control: block 961995 by -1 >>> >>> https://buildd.debian.org/status/package.php?p=esys-particle >>> >>> ... >>>dh_installman -a >>> dh_installman: warning: Section for ./debian/esysparticle.1 is computed as >>> "2012-12-30", which is not a valid section >>> dh_installman: error: Could not determine section for >>> ./debian/esysparticle.1 >>> dh_installman: error: Aborting due to earlier error >>> make: *** [debian/rules:15: binary-arch] Error 25 >>> >>> >>> debhelper (13.1) unstable; urgency=low >>> ... >>> * dh_installman: Improve error messages and handling of broken >>> section numbers. Notably ignore (with a warning) sections from >>> manpages that look suspiciously like a version number. Thanks >>> to Paul Gevers for reporting the bug. (Closes: #958343) >>> ... >>> >> >> Hi Adrian, > > [...]>> Prior to that error, dh_installman silently installed it in >> /usr/share/man/man2, which would clearly have been wrong: >> >> """ >> $ apt-file show esys-particle | grep share/man/ >> esys-particle: /usr/share/man/man2/esysparticle.2012-12-30.gz >> """ >> >> Based on this, can we agree that this and future instances you find of >> this case should in general be filed against packages containing the >> manpage rather then debhelper? > > My reading of the debhelper changelog was that "ignore (with a warning)" > means that this was not intended to cause an error. > > I might have misunderstood that. > > > cu > Adrian > I see how this could have caused the confusion. I will update the changelog to better reflect the reality. The "ignore" here refers to the auto-detected section number and not the manpage itself. Without a well-defined section number, dh_installman would then stop with an error (which it has always done - it is just more picky in its auto-detection mechanism). Related, I have reassigned this bug to esys-particle. ~Niels
Processed: Re: Bug#962253: debhelper: dh_installman error instead of warning on invalid section
Processing control commands: > reassign -1 esys-particle Bug #962253 [src:debhelper] debhelper: dh_installman error instead of warning on invalid section Bug reassigned from package 'src:debhelper' to 'esys-particle'. No longer marked as found in versions debhelper/13.1. Ignoring request to alter fixed versions of bug #962253 to the same values previously set > retitle -1 esys-particle: Broken section number in manpage Bug #962253 [esys-particle] debhelper: dh_installman error instead of warning on invalid section Changed Bug title to 'esys-particle: Broken section number in manpage' from 'debhelper: dh_installman error instead of warning on invalid section'. -- 962253: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962253 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org: > reassign 962257 src:sword 1.8.1+dfsg-8 Bug #962257 [sword] sword: FTBFS on mips64el Bug reassigned from package 'sword' to 'src:sword'. No longer marked as found in versions 1.8.1+dfsg-8. Ignoring request to alter fixed versions of bug #962257 to the same values previously set Bug #962257 [src:sword] sword: FTBFS on mips64el Marked as found in versions sword/1.8.1+dfsg-8. > reassign 962230 src:sword 1.8.1+dfsg-8 Bug #962230 [src:xiphos] xiphos: FTBFS on mips64el Bug reassigned from package 'src:xiphos' to 'src:sword'. No longer marked as found in versions xiphos/4.1.0.1+dfsg1-1+b1. Ignoring request to alter fixed versions of bug #962230 to the same values previously set Bug #962230 [src:sword] xiphos: FTBFS on mips64el Marked as found in versions sword/1.8.1+dfsg-8. > forcemerge 962257 962230 Bug #962257 [src:sword] sword: FTBFS on mips64el Bug #962230 [src:sword] xiphos: FTBFS on mips64el Added indication that 962230 affects src:xiphos Merged 962230 962257 > thanks Stopping processing here. Please contact me if you need assistance. -- 962230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962230 962257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: setg version
Processing commands for cont...@bugs.debian.org: > found 961851 cross-toolchain-base/45 Bug #961851 [cross-toolchain-base] make-dfsg breaks cross-toolchain-base autopkgtest: debian/kernelarch.make:5: *** empty variable name Marked as found in versions cross-toolchain-base/45. > thanks Stopping processing here. Please contact me if you need assistance. -- 961851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962229: marked as done (orthanc-postgresql FTBFS with boost1.71)
Your message dated Fri, 05 Jun 2020 08:34:49 + with message-id and subject line Bug#962229: fixed in orthanc-postgresql 3.2-2 has caused the Debian Bug report #962229, regarding orthanc-postgresql FTBFS with boost1.71 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.) -- 962229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: orthanc-postgresql Version: 3.2-1 Severity: serious Tags: ftbfs bullseye sid Control: block 961995 by -1 https://buildd.debian.org/status/package.php?p=orthanc-postgresql=sid ... -- Found Boost: /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake (found version "1.71.0") CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Boost-1.71.0/BoostConfig.cmake:182 (boost_find_component): boost_find_component Macro invoked with incorrect arguments for macro named: boost_find_component Call Stack (most recent call first): /usr/share/cmake-3.16/Modules/FindBoost.cmake:443 (find_package) /<>/Build/Orthanc-1.5.4/Resources/CMake/BoostConfiguration.cmake:15 (find_package) /<>/Build/Orthanc-1.5.4/Resources/CMake/OrthancFrameworkConfiguration.cmake:417 (include) /<>/Resources/CMake/DatabasesFrameworkConfiguration.cmake:62 (include) /<>/Resources/CMake/DatabasesPluginConfiguration.cmake:21 (include) CMakeLists.txt:22 (include) ... orthanc-postgresql builds an own copy of src:orthanc, and this copy does not have #953884 fixed. --- End Message --- --- Begin Message --- Source: orthanc-postgresql Source-Version: 3.2-2 Done: Sebastien Jodogne We believe that the bug you reported is fixed in the latest version of orthanc-postgresql, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Jodogne (supplier of updated orthanc-postgresql 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, 05 Jun 2020 08:59:16 +0200 Source: orthanc-postgresql Architecture: source Version: 3.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Sebastien Jodogne Closes: 962229 Changes: orthanc-postgresql (3.2-2) unstable; urgency=medium . * Updated Orthanc framework to 1.7.0. Closes: #962229 Checksums-Sha1: 2f05d67e13764e87154f87a78970cefe245d77bc 2210 orthanc-postgresql_3.2-2.dsc ecc83d9cd74dc3a2c421b515f1757c4202a2615a 425088 orthanc-postgresql_3.2-2.debian.tar.xz 0990e51db8fadb36ba43caf9106ae9a2f99f21eb 13618 orthanc-postgresql_3.2-2_source.buildinfo Checksums-Sha256: 6187af76238d5fe286699ab70ef1b9727ec1b82bc40354a28c85064575584488 2210 orthanc-postgresql_3.2-2.dsc afadbc5f487dff11eb223d19742dec5dbf85d8879edca4d9f4ab702fdf8a971a 425088 orthanc-postgresql_3.2-2.debian.tar.xz 0dd4ac3eef3f3b54ef001d3031e5d876b7aef78a39ea7fd5751433661af354b7 13618 orthanc-postgresql_3.2-2_source.buildinfo Files: 69c31b4d2711aacbf9833f2d3c15e0cd 2210 science optional orthanc-postgresql_3.2-2.dsc 4578eee6f349b4ce6f232e3691a4b1fb 425088 science optional orthanc-postgresql_3.2-2.debian.tar.xz 86025ac90d508dffa636952e7565e998 13618 science optional orthanc-postgresql_3.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEk76fGX7V0MMOWT2Lp3ZYKzEqw10FAl7Z+jAUHHMuam9kb2du ZUBnbWFpbC5jb20ACgkQp3ZYKzEqw11GzQ/6AqX+Mp9CV1aYCcuwr23lCu2HrLWX 45PRbMZ5uwTsookoIfZ54BA0T9h7Dtyigp8KdEuofkeNhg43ID5ASEKNHzOa8lmy B3nzP8+S4CF1T5FaiO6uuAAYgy2lvIzIFRsp+h275twjTq/wg65uGPaL/FicCLzW UL2L1qZpqxNF1ry2BPQNAFmwgX4kA4ZfMpO2GjOYT8jSQVdpmEBC6N/hDs1BE4YB fWySMEJ2EpWhuBb3aOWKiGgRjIuJipFDpfy3spYg4Zhi5bwdT6TL9U9jozRyRahv nrxhBXKvtx+skayG9Ye/P87VWrEety35ieeyMcTrinUFbmpUbNC8jFMapDZ2rsmA ioOs0htN8Jxr39T3u+f+mISN0GbEs/emiofUZAXjXebyNjhqm5qPDKU/25h2AH0Z jShK3v9lIAiFi4a44U9Y30uEoeIzTWqFACRsxLsQ6dy2N8vnG8JtiqNkybCeorF+ /1thoquZZY/q8DFZOzgZZNWQ8SmQF09VWllESvxy8PWrmr4CHfLgHLBWsdwImZ7N UbGcZ36fTB/txD2iam1TeUV5dKr9utAshxICM3Fq/e+IbuANsGCapnQLqgEz9ID6 dVQLXXf4WdVXglK2oRdb0NJZPN+m08DQc8qk8awn233q+J5UrNk1yb2/5yN+pdVN s3Ijkkim27PF/k8= =l9Bw -END PGP SIGNATURE End Message ---
Processed: affects 962257
Processing commands for cont...@bugs.debian.org: > affects 962257 src:xiphos Bug #962257 [sword] sword: FTBFS on mips64el Added indication that 962257 affects src:xiphos > thanks Stopping processing here. Please contact me if you need assistance. -- 962257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962257 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962257: sword: FTBFS on mips64el
Package: sword Version: 1.8.1+dfsg-8 Severity: serious Tags: ftbfs sid bullseye sword failed to build on mips64el: | libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../include -I../include -I/usr/include -DUSE_AUTOTOOLS -DUNIX -Dunix -D__unix__ -D_FTPLIB_NO_COMPAT -Wdate-time -D_FORTIFY_SOURCE=2 -Ofast -fPIC -DEXCLUDEBZIP2 -DEXCLUDEXZ -DCURLAVAILABLE -DCURLSFTPAVAILABLE -I/usr/lib/mips64el-linux-gnuabi64 -DUSELUCENE -DCLUCENE2 -I/usr/lib/mips64el-linux-gnuabi64 -Wno-address -Wno-nonnull-compare -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -ftemplate-depth=100 -c ../src/keys/listkey.cpp -o listkey.o >/dev/null 2>&1 | In file included from /usr/include/mips64el-linux-gnuabi64/asm/types.h:23, | from /usr/include/linux/types.h:5, | from /usr/include/linux/stat.h:5, | from /usr/include/mips64el-linux-gnuabi64/bits/statx.h:31, | from /usr/include/mips64el-linux-gnuabi64/sys/stat.h:446, | from ../include/filemgr.h:26, | from ../src/keys/treekeyidx.cpp:31: | /usr/include/asm-generic/int-l64.h:29:25: error: conflicting declaration ‘typedef long int __s64’ |29 | typedef __signed__ long __s64; | | ^ | In file included from ../include/swkey.h:31, | from ../include/treekey.h:27, | from ../include/treekeyidx.h:27, | from ../src/keys/treekeyidx.cpp:24: | ../include/sysdata.h:49:44: note: previous declaration as ‘typedef long long int __s64’ |49 | __extension__ typedef __signed__ long long __s64; | |^ | In file included from /usr/include/mips64el-linux-gnuabi64/asm/types.h:23, | from /usr/include/linux/types.h:5, | from /usr/include/linux/stat.h:5, | from /usr/include/mips64el-linux-gnuabi64/bits/statx.h:31, | from /usr/include/mips64el-linux-gnuabi64/sys/stat.h:446, | from ../include/filemgr.h:26, | from ../src/keys/treekeyidx.cpp:31: | /usr/include/asm-generic/int-l64.h:30:23: error: conflicting declaration ‘typedef long unsigned int __u64’ |30 | typedef unsigned long __u64; | | ^ | In file included from ../include/swkey.h:31, | from ../include/treekey.h:27, | from ../include/treekeyidx.h:27, | from ../src/keys/treekeyidx.cpp:24: | ../include/sysdata.h:50:42: note: previous declaration as ‘typedef long long unsigned int __u64’ |50 | __extension__ typedef unsigned long long __u64; | | ^ | make[3]: *** [Makefile:1328: treekeyidx.lo] Error 1 See https://buildd.debian.org/status/fetch.php?pkg=sword=mips64el=1.8.1%2Bdfsg-8%2Bb2=1591156115=0 Cheers -- Sebastian Ramacher signature.asc Description: PGP signature
Processed: reassign to the cross-toolchain-base package
Processing commands for cont...@bugs.debian.org: > reassign 961851 cross-toolchain-base 45 Bug #961851 [src:make-dfsg, src:cross-toolchain-base] make-dfsg breaks cross-toolchain-base autopkgtest: debian/kernelarch.make:5: *** empty variable name Bug reassigned from package 'src:make-dfsg, src:cross-toolchain-base' to 'cross-toolchain-base'. No longer marked as found in versions cross-toolchain-base/45. Ignoring request to alter fixed versions of bug #961851 to the same values previously set Bug #961851 [cross-toolchain-base] make-dfsg breaks cross-toolchain-base autopkgtest: debian/kernelarch.make:5: *** empty variable name There is no source info for the package 'cross-toolchain-base' at version '45' with architecture '' Unable to make a source version for version '45' Marked as found in versions 45. > thanks Stopping processing here. Please contact me if you need assistance. -- 961851: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961851 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#962145: marked as done (nodejs: CVE-2020-11080 CVE-2020-8172 CVE-2020-8174 (June 2020 security release))
Your message dated Fri, 05 Jun 2020 07:18:47 + with message-id and subject line Bug#962145: fixed in nodejs 10.21.0~dfsg-1 has caused the Debian Bug report #962145, regarding nodejs: CVE-2020-11080 CVE-2020-8172 CVE-2020-8174 (June 2020 security release) 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.) -- 962145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nodejs Version: 10.20.1~dfsg-1 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 10.19.0~dfsg1-1 Hi, The following vulnerabilities were published for nodejs. CVE-2020-11080[0]: HTTP/2 Large Settings Frame DoS CVE-2020-8172[1]: TLS session reuse can lead to host certificate verification bypass CVE-2020-8174[2]: napi_get_value_string_*() allows various kinds of memory corruption If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-11080 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11080 [1] https://security-tracker.debian.org/tracker/CVE-2020-8172 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8172 [2] https://security-tracker.debian.org/tracker/CVE-2020-8174 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8174 [3] https://nodejs.org/en/blog/vulnerability/june-2020-security-releases Regards, Salvatore --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 10.21.0~dfsg-1 Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= We believe that the bug you reported is fixed in the latest version of nodejs, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs 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, 05 Jun 2020 08:55:38 +0200 Source: nodejs Architecture: source Version: 10.21.0~dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Closes: 962145 Changes: nodejs (10.21.0~dfsg-1) unstable; urgency=medium . * New upstream version 10.21.0~dfsg. Closes: #962145. * Security fixes: + CVE-2020-11080 + CVE-2020-8172 + CVE-2020-8174 * Build-Depend nghttp2 >= 1.41.0 Checksums-Sha1: 22312895497bcd5bc02956bc89d332a724d20251 3126 nodejs_10.21.0~dfsg-1.dsc c95948f590918a4f36de05b61dcc785c8887e7a0 16231704 nodejs_10.21.0~dfsg.orig.tar.xz 5f26e1919a96555420cb58732a0ad36ca1190d0b 96856 nodejs_10.21.0~dfsg-1.debian.tar.xz 98d37a2334a78634d04c4067834c20ac40ed691c 13776 nodejs_10.21.0~dfsg-1_source.buildinfo Checksums-Sha256: 39a2a639e181f73b9cc4ab76af60112295e1b350939265c86cf857ee31cb8000 3126 nodejs_10.21.0~dfsg-1.dsc 111d0a59a5d0ed8c2f64d46e344e14ea152b0b23f4e892d166a37e5b15c8cb99 16231704 nodejs_10.21.0~dfsg.orig.tar.xz 2387a6b9c7a88aeed5ad437d0958e8b49d9b712d1e5423a7e0f71f32b7b55842 96856 nodejs_10.21.0~dfsg-1.debian.tar.xz eccb23d4599b25b062a632d33d80a6390af28fcba8449de6c2e29cb78e586455 13776 nodejs_10.21.0~dfsg-1_source.buildinfo Files: d47dfffd85e98423b82793c26637eb13 3126 javascript optional nodejs_10.21.0~dfsg-1.dsc 3a6dff10c0d58ed9cc7a929aef80da19 16231704 javascript optional nodejs_10.21.0~dfsg.orig.tar.xz 373bbdd9916d977e831c0f7a5a35039b 96856 javascript optional nodejs_10.21.0~dfsg-1.debian.tar.xz 6053d46effbab42c7b0b65acb826ed87 13776 javascript optional nodejs_10.21.0~dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAl7Z7NYSHGthcG91ZXJA bWVsaXgub3JnAAoJEGYRwF7dOfN0b8gP/jLNGOIM0SVg9v9CyRzqw4BHhauzeR4+ 862FlXS+jnWkQ7ASliFVc9oY5gVR9UqtklflCFMSq5XlvwPxNfUnJ/Kkt1X7vwMQ UpR6imLVegGSVq4pflocByuuyAotyMHtp7FZNvcQKYrP//CKCvWJqRQDPV4Zb+KG 3s4X/dTkvaiDefJAW8E/8bvWATEXI2Z3r03cB5LVJR0DWOhKCygu7jIbsHX6usoZ 5VNEfWF+1LkP4qE2b8sd8PF8Jf9WdPkxmZDWbeYWkYbhOdFZ9BYkkT5eljwC1wCY r/Po0ImCQzO3myJKbXKM41WDeqhyaDbf5AO8x7rf3YH/ivxv0h8NL1doNApfqxWz
Bug#962145: marked as done (nodejs: CVE-2020-11080 CVE-2020-8172 CVE-2020-8174 (June 2020 security release))
Your message dated Fri, 05 Jun 2020 07:18:56 + with message-id and subject line Bug#962145: fixed in nodejs 12.18.0~dfsg-1 has caused the Debian Bug report #962145, regarding nodejs: CVE-2020-11080 CVE-2020-8172 CVE-2020-8174 (June 2020 security release) 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.) -- 962145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nodejs Version: 10.20.1~dfsg-1 Severity: grave Tags: security upstream Justification: user security hole Control: found -1 10.19.0~dfsg1-1 Hi, The following vulnerabilities were published for nodejs. CVE-2020-11080[0]: HTTP/2 Large Settings Frame DoS CVE-2020-8172[1]: TLS session reuse can lead to host certificate verification bypass CVE-2020-8174[2]: napi_get_value_string_*() allows various kinds of memory corruption If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-11080 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11080 [1] https://security-tracker.debian.org/tracker/CVE-2020-8172 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8172 [2] https://security-tracker.debian.org/tracker/CVE-2020-8174 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8174 [3] https://nodejs.org/en/blog/vulnerability/june-2020-security-releases Regards, Salvatore --- End Message --- --- Begin Message --- Source: nodejs Source-Version: 12.18.0~dfsg-1 Done: =?utf-8?b?SsOpcsOpbXkgTGFs?= We believe that the bug you reported is fixed in the latest version of nodejs, 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 962...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jérémy Lal (supplier of updated nodejs 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, 05 Jun 2020 09:07:20 +0200 Source: nodejs Architecture: source Version: 12.18.0~dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Closes: 962145 Changes: nodejs (12.18.0~dfsg-1) experimental; urgency=medium . * New upstream version 12.18.0~dfsg. Closes: #962145. * Security fixes: + CVE-2020-11080 + CVE-2020-8172 + CVE-2020-8174 * Build-Depends nghttp2 >= 1.41.0 Checksums-Sha1: 94e5afdffc6c42c29fc2a32f2a1a6f92bca9b890 3103 nodejs_12.18.0~dfsg-1.dsc e39d5e955e45f7c8d688758e5e839441bf961a1f 18122988 nodejs_12.18.0~dfsg.orig.tar.xz f43d2c52b4bd00c658a7db492f537904c10b27fc 131604 nodejs_12.18.0~dfsg-1.debian.tar.xz a0925f768a126107979d6f2415d2198ef21c37bd 13757 nodejs_12.18.0~dfsg-1_source.buildinfo Checksums-Sha256: 20b2230180531e4bc656d156d80930c33fe5f74de099bc44609a0514d918bb5d 3103 nodejs_12.18.0~dfsg-1.dsc b8e5e94888fb2a88b0bfca620b7401243104620d01adfe376fac91775787bae9 18122988 nodejs_12.18.0~dfsg.orig.tar.xz ae8949671a0a8a41f05c76aa61f8e4999fc33241ef031ddacd66575f18780e30 131604 nodejs_12.18.0~dfsg-1.debian.tar.xz 990628f801e514b2a7ecba5b2e24e6da8f52cd5ef995836d536f18ed3131ee78 13757 nodejs_12.18.0~dfsg-1_source.buildinfo Files: 30de2976c99050046fd4bac5932573c5 3103 javascript optional nodejs_12.18.0~dfsg-1.dsc 1902c93988d8d2ef3151736941b40d3e 18122988 javascript optional nodejs_12.18.0~dfsg.orig.tar.xz 3b18e84d6ea13bd34843798242043dae 131604 javascript optional nodejs_12.18.0~dfsg-1.debian.tar.xz 74b1185fa5f27fd398d859834111e484 13757 javascript optional nodejs_12.18.0~dfsg-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAl7Z70MSHGthcG91ZXJA bWVsaXgub3JnAAoJEGYRwF7dOfN0woUP/0/mJSb1WuuWrzLruXL3hEiq/wVP7l97 MEDKR5QFtsqjY0DPdz1qywqivI59bNSb7FQWmgwtPLkz5/yzCSFcWk7rvrfkv5eh /m1GX3FlyZ4BqYiPW5yfJ8N7FqedbKN2FG/3t7j6W+AQ+8FVhOgtPbuM+oelahgy Z3tYw5ZzWBM58dtZPZSxa6w/6JiO+Gdt6QHNsTdIkN9qOwNfBnyZg5NDXo6cxAve M7kM4maR6t9Zk4y6TdsSBMOjwPFMslvAZv95DSr56GBQpa5KO+fbD9ygeKCtkLDP VqjJ8DcAqVe08ucg3a3RHICAW2v8vehqjdJwJuPneA7TH3rRHaxL3rVMoHy7IIu9
Bug#962253: debhelper: dh_installman error instead of warning on invalid section
On Fri, Jun 05, 2020 at 07:55:33AM +0200, Niels Thykier wrote: > Adrian Bunk: > > Source: debhelper > > Version: 13.1 > > Severity: serious > > Control: affects -1 src:esys-particle > > Control: block 961995 by -1 > > > > https://buildd.debian.org/status/package.php?p=esys-particle > > > > ... > >dh_installman -a > > dh_installman: warning: Section for ./debian/esysparticle.1 is computed as > > "2012-12-30", which is not a valid section > > dh_installman: error: Could not determine section for > > ./debian/esysparticle.1 > > dh_installman: error: Aborting due to earlier error > > make: *** [debian/rules:15: binary-arch] Error 25 > > > > > > debhelper (13.1) unstable; urgency=low > > ... > > * dh_installman: Improve error messages and handling of broken > > section numbers. Notably ignore (with a warning) sections from > > manpages that look suspiciously like a version number. Thanks > > to Paul Gevers for reporting the bug. (Closes: #958343) > > ... > > > > Hi Adrian, Hi Niels, > I do not understand how you came to the conclusion that because > esys-particle has a completely broken manpage then debhelper should have > an RC bug. it is a FTBFS, so there has to be an RC bug somewhere. > Prior to that error, dh_installman silently installed it in > /usr/share/man/man2, which would clearly have been wrong: > > """ > $ apt-file show esys-particle | grep share/man/ > esys-particle: /usr/share/man/man2/esysparticle.2012-12-30.gz > """ > > Based on this, can we agree that this and future instances you find of > this case should in general be filed against packages containing the > manpage rather then debhelper? My reading of the debhelper changelog was that "ignore (with a warning)" means that this was not intended to cause an error. I might have misunderstood that. > ~Niels cu Adrian
Bug#961778: marked as done (flex: binary-all FTBFS)
Your message dated Fri, 05 Jun 2020 06:03:28 + with message-id and subject line Bug#961778: fixed in flex 2.6.4-8 has caused the Debian Bug report #961778, regarding flex: binary-all FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 961778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flex Version: 2.6.4-7 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=flex=all=2.6.4-7=1590040409=0 ... debian/rules override_dh_installexamples make[1]: Entering directory '/<>' I: flex_2.6.4 dh_installexamples # Clean up embedded build paths in order to ensure reproducible builds. sed -i -e "s,-fdebug-prefix-map=/<>=\.,,g" \ -e "s,-ffile-prefix-map=/<>=\.,,g" \ -e "s,abs_.*/<>.*,,g" \ -e "s,/<>.*missing --run,,g" \ -e "s,/<>,./,g" \ /<>/debian/flex/usr/share/doc/flex/examples/fastwc/Makefile \ /<>/debian/flex/usr/share/doc/flex/examples/manual/Makefile sed: can't read /<>/debian/flex/usr/share/doc/flex/examples/fastwc/Makefile: No such file or directory sed: can't read /<>/debian/flex/usr/share/doc/flex/examples/manual/Makefile: No such file or directory make[1]: *** [debian/rules:98: override_dh_installexamples] Error 2 --- End Message --- --- Begin Message --- Source: flex Source-Version: 2.6.4-8 Done: Manoj Srivastava We believe that the bug you reported is fixed in the latest version of flex, 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 961...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Manoj Srivastava (supplier of updated flex 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: Thu, 04 Jun 2020 22:32:05 -0700 Source: flex Architecture: source Version: 2.6.4-8 Distribution: unstable Urgency: medium Maintainer: Manoj Srivastava Changed-By: Manoj Srivastava Closes: 961778 Changes: flex (2.6.4-8) unstable; urgency=medium . * The source does not ship with example Makefiles, so no need to massage them. * Bug fix: "binary-all FTBFS", thanks to Adrian Bunk (Closes: #961778). * Movement on Bug#603787 https://github.com/westes/flex/pull/357 Checksums-Sha1: c4ebd95ffd916c36fd7fc22c9e05cbe53f6cf61c 2002 flex_2.6.4-8.dsc 8fde85d2ef4feb6a7f528aa289f000338c7c4325 59683 flex_2.6.4-8.diff.gz Checksums-Sha256: 9a1ca21e42fb6d1c42dfe01d4b435230f520bfd8a0f367aadd863cd1b66c56b3 2002 flex_2.6.4-8.dsc fce60da0d3ff9e9d452316089447467a0bb5be4c2d383e5e39697b5b1b4a6149 59683 flex_2.6.4-8.diff.gz Files: 2d852978e44716fc56c1888d78a6e458 2002 devel optional flex_2.6.4-8.dsc 2722a5b2681e1244998b263187a749f0 59683 devel optional flex_2.6.4-8.diff.gz -BEGIN PGP SIGNATURE- iQGZBAEBCgCDFiEEq6cQJaG1qIpOX2jCNr1yD29XZHIFAl7Z3EFQFIAAGwAs c3JpdmFzdGFAZ29sZGVuLWdyeXBob24uY29tQUJBNzEwMjVBMUI1QTg4QTRFNUY2 OEMyMzZCRDcyMEY2RjU3NjQ3Ml8zMDkUHHNyaXZhc3RhQGRlYmlhbi5vcmcACgkQ Nr1yD29XZHLO9QgAjC/Q5qLxthCvPn7dz5HY+C1/8TrM50wfX61ml1pK+DQX6zw0 51KFiXlLkuridjq9jQOQSxWrUUx4sWFS/PMwlmWdyiYvPBF5PLIqvnKiojhn4AbG EbRVtvyttT5HEluh3I6Ef7MH1jf6COAm9JwDQiS8BUCUGJ6SLHocJPjJ/EbqJmR7 YLLEx7g8waLF4PJqZqTwdegQEFoCW3Els/UIYXGtzf8Q5dcntnUoLt0SEma2CnYh +OpEKnqqhJr+UYnEWEqYA4XFEQYGJGECNd0vL9z52QvYUs865SQu+SHVKTiSrYtf FwJpmtL7YXgVV4DF/GtyVaZfoVkZ4bmzBIw4HQ== =aI6O -END PGP SIGNATURE End Message ---
Bug#962253: debhelper: dh_installman error instead of warning on invalid section
Adrian Bunk: > Source: debhelper > Version: 13.1 > Severity: serious > Control: affects -1 src:esys-particle > Control: block 961995 by -1 > > https://buildd.debian.org/status/package.php?p=esys-particle > > ... >dh_installman -a > dh_installman: warning: Section for ./debian/esysparticle.1 is computed as > "2012-12-30", which is not a valid section > dh_installman: error: Could not determine section for ./debian/esysparticle.1 > dh_installman: error: Aborting due to earlier error > make: *** [debian/rules:15: binary-arch] Error 25 > > > debhelper (13.1) unstable; urgency=low > ... > * dh_installman: Improve error messages and handling of broken > section numbers. Notably ignore (with a warning) sections from > manpages that look suspiciously like a version number. Thanks > to Paul Gevers for reporting the bug. (Closes: #958343) > ... > Hi Adrian, I do not understand how you came to the conclusion that because esys-particle has a completely broken manpage then debhelper should have an RC bug. Prior to that error, dh_installman silently installed it in /usr/share/man/man2, which would clearly have been wrong: """ $ apt-file show esys-particle | grep share/man/ esys-particle: /usr/share/man/man2/esysparticle.2012-12-30.gz """ Based on this, can we agree that this and future instances you find of this case should in general be filed against packages containing the manpage rather then debhelper? ~Niels
