Bug#831258: refind: FTBFS: edk2/ComponentName.h:55:23: error: conflicting types for 'EFI_COMPONENT_NAME_GET_DRIVER_NAME'

[Tianon Gravi]

On 14 July 2016 at 03:28, Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.

The attached patch allows the package to build again, but I'd rather
make sure from Rod before officially applying it that just removing
these duplicate declarations is the right approach. :)

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4
diff --git a/filesystems/edk2/ComponentName.h b/filesystems/edk2/ComponentName.h
index a4c3749..7a01e29 100644
--- a/filesystems/edk2/ComponentName.h
+++ b/filesystems/edk2/ComponentName.h
@@ -50,6 +50,8 @@ typedef struct _EFI_COMPONENT_NAME_PROTOCOL  EFI_COMPONENT_NAME_PROTOCOL;
 language specified by Language.
 
 **/
+/*
+// /usr/include/efi/efiprot.h:878:10: note: previous declaration of 'EFI_COMPONENT_NAME_GET_DRIVER_NAME' was here
 typedef
 EFI_STATUS
 (EFI_FUNCTION EFIAPI *EFI_COMPONENT_NAME_GET_DRIVER_NAME)(
@@ -57,6 +59,7 @@ EFI_STATUS
   IN  CHAR8*Language,
   OUT CHAR16   **DriverName
   );
+*/
 
 
 /**
@@ -99,6 +102,8 @@ EFI_STATUS
 language specified by Language.
 
 **/
+/*
+// /usr/include/efi/efiprot.h:885:10: note: previous declaration of 'EFI_COMPONENT_NAME_GET_CONTROLLER_NAME' was here
 typedef
 EFI_STATUS
 (EFI_FUNCTION EFIAPI *EFI_COMPONENT_NAME_GET_CONTROLLER_NAME)(
@@ -108,6 +113,7 @@ EFI_STATUS
   IN  CHAR8   *Language,
   OUT CHAR16  **ControllerName
   );
+*/
 
 ///
 /// This protocol is used to retrieve user readable names of drivers 

Bug#833895: nvidia-legacy-340xx-driver: blank screen after upgrade

[Luis Mochan]

Package: nvidia-legacy-340xx-driver
Version: 340.96-9
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I upgraded my system today. I received a warning that the nvidia driver 
wouldn't work anymore with my old card 
and that I should install the legacy-340xx package. After installation I chose 
the legacy package with the 
updage-glx program. During installation I had some problems as I hadn't 
installed the appropriatte linux-headers
package installed, but after I did, reinstalled the driver and booted the 
system I finally got to see the green NVIDIA 
logo flash momentarily in my screen. But then, I get a blank screen and my 
laptop becomes unresponsive to its keyboard. 
The system is running though, and I looged into it with ssh to write this 
message. 

Best regards,
Luis

-- Package-specific info:
uname -a:
Linux fmunu 4.6.0-1-686-pae #1 SMP Debian 4.6.4-1 (2016-07-18) i686 GNU/Linux

/proc/version:
Linux version 4.6.0-1-686-pae (debian-ker...@lists.debian.org) (gcc version 
5.4.0 20160609 (Debian 5.4.0-6) ) #1 SMP Debian 4.6.4-1 (2016-07-18)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86 Kernel Module  340.96  Sun Nov  8 21:45:55 PST 
2015
GCC version:  gcc version 5.4.0 20160609 (Debian 5.4.0-6) 

lspci 'VGA compatible controller [0300]':
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G86M [Quadro NVS 
140M] [10de:0429] (rev a1) (prog-if 00 [VGA controller])
Subsystem: Lenovo ThinkPad T61 [17aa:20d8]
Physical Slot: 1-1
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nvidia

dmesg:
[0.00] Console: colour VGA+ 80x25
[0.266470] vgaarb: setting as boot device: PCI::01:00.0
[0.266470] vgaarb: device added: 
PCI::01:00.0,decodes=io+mem,owns=io+mem,locks=none
[0.268003] vgaarb: loaded
[0.268101] vgaarb: bridge control possible :01:00.0
[1.233916] Linux agpgart interface v0.103
[   12.795907] nvidia: module license 'NVIDIA' taints kernel.
[   12.821281] vgaarb: device changed decodes: 
PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[   12.823357] [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on 
minor 0
[   12.823493] NVRM: loading NVIDIA UNIX x86 Kernel Module  340.96  Sun Nov  8 
21:45:55 PST 2015

Device node permissions:
crw-rw 1 root video 226,   0 Aug  9 21:32 /dev/dri/card0
crw-rw-rw- 1 root root  195,   0 Aug  9 21:32 /dev/nvidia0
crw-rw-rw- 1 root root  195, 255 Aug  9 21:32 /dev/nvidiactl
video:x:44:mochan,david,luquesnel,elias,gatis,david,irina

OpenGL and NVIDIA library files installed:
lrwxrwxrwx 1 root root   15 Aug  9 20:57 /etc/alternatives/glx -> 
/usr/lib/nvidia
lrwxrwxrwx 1 root root   42 Aug  9 20:57 
/etc/alternatives/glx--libEGL.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libEGL.so.1
lrwxrwxrwx 1 root root   41 Aug  9 20:57 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   41 Aug  9 20:57 
/etc/alternatives/glx--libGL.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libGL.so.1
lrwxrwxrwx 1 root root   48 Aug  9 20:57 
/etc/alternatives/glx--libGLESv1_CM.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   48 Aug  9 20:57 
/etc/alternatives/glx--libGLESv1_CM.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libGLESv1_CM.so.1
lrwxrwxrwx 1 root root   45 Aug  9 20:57 
/etc/alternatives/glx--libGLESv2.so.2-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libGLESv2.so.2
lrwxrwxrwx 1 root root   45 Aug  9 20:57 
/etc/alternatives/glx--libGLESv2.so.2-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libGLESv2.so.2
lrwxrwxrwx 1 root root   49 Aug  9 20:57 
/etc/alternatives/glx--libnvidia-cfg.so.1-i386-linux-gnu -> 
/usr/lib/i386-linux-gnu/nvidia/libnvidia-cfg.so.1
lrwxrwxrwx 1 root root   25 Aug  9 20:57 
/etc/alternatives/glx--linux-libglx.so -> /usr/lib/nvidia/libglx.so
lrwxrwxrwx 1 root root   42 Aug  9 20:57 
/etc/alternatives/glx--nvidia-blacklists-nouveau.conf -> 
/etc/nvidia/nvidia-blacklists-nouveau.conf
lrwxrwxrwx 1 root root   36 Aug  9 20:57 
/etc/alternatives/glx--nvidia-bug-report.sh -> 
/usr/lib/nvidia/nvidia-bug-report.sh
lrwxrwxrwx 1 root root   39 Aug  9 20:57 
/etc/alternatives/glx--nvidia-drm-outputclass.conf -> 
/etc/nvidia/nvidia-drm-outputclass.conf
lrwxrwxrwx 1 root root   28 Aug  9 20:57 
/etc/alternatives/glx--nvidia-load.conf -> /etc/nvidia/nvidia-load.conf
lrwxrwxrwx 1 root root   32 Aug  9 20:57 
/etc/alternatives/glx--nvidia-modprobe.conf -> /etc/nvidia/nvidia-modprobe.conf
lrwxrwxrwx 1 root root   29 Aug  9 20:57 
/etc/alternatives/glx--nvidia_drv.so -> /usr/lib/nvidia/nvidia_drv.so
lrwxrwxrwx 1 root root   28 Aug  9 20:57 

Bug#833698: Icedove 1:45.2.0-2+b1 (Debian Testing) SegFault

[Viktor Jägersküpper]

Everybody who reads only this bug report, please consider my workaround
mentioned in bug 833532:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833532#50

Bug#832908: marked as done (mongodb: CVE-2016-6494: world-readable .dbshell history file)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2016 22:26:49 +
with message-id 
and subject line Bug#832908: fixed in mongodb 1:2.6.12-3
has caused the Debian Bug report #832908,
regarding mongodb: CVE-2016-6494: world-readable .dbshell history file
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.)


-- 
832908: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832908
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mongodb-clients
Version: 2.4.10-5
Severity: grave
Tags: security

During the report on redis-tools
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832460), lamby@
linked to a codesearch and the same bug was found in mongodb-clients.

mongodb-clients stores its history in ~/.dbshell, this file is created
with permissions 0644. Home folders are world readable as well in
debian, so any user can access other users mongodb history, even though
db.auth commands don't appear to be logged like redis did.

I filed a bug on upstream as well:
https://jira.mongodb.org/browse/SERVER-25335

Demo: `cat /home/*/.dbshell`
--- End Message ---
--- Begin Message ---
Source: mongodb
Source-Version: 1:2.6.12-3

We believe that the bug you reported is fixed in the latest version of
mongodb, 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 832...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated mongodb package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 08 Aug 2016 21:56:32 +
Source: mongodb
Binary: mongodb mongodb-server mongodb-clients
Architecture: source amd64
Version: 1:2.6.12-3
Distribution: unstable
Urgency: high
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Description:
 mongodb- object/document-oriented database (metapackage)
 mongodb-clients - object/document-oriented database (client apps)
 mongodb-server - object/document-oriented database (server package)
Closes: 832908
Changes:
 mongodb (1:2.6.12-3) unstable; urgency=high
 .
   * Fix CVE-2016-6494 , prevent group and other access to .dbshell
 (closes: #832908).
Checksums-Sha1:
 15971b52c299b7c6ee59d9944d22262388b0c999 2738 mongodb_2.6.12-3.dsc
 d19c2e03cf445e197e0bd2bc28f9b08be3309c47 53000 mongodb_2.6.12-3.debian.tar.xz
 2859ad4ca521169e02035c52386d0d7a9ab2ce9b 1255815488 
mongodb-clients-dbgsym_2.6.12-3_amd64.deb
 8fdfe5a132d4ac364a93943e8422a3a311fbea98 47043808 
mongodb-clients_2.6.12-3_amd64.deb
 3427389cd93143fa5d1ff812d60832c1746bfc84 178246036 
mongodb-server-dbgsym_2.6.12-3_amd64.deb
 1681cb59efc82a229a7359967023193a215d440f 7216400 
mongodb-server_2.6.12-3_amd64.deb
 514b73f0cffcb910e60f378a5750ba094dd72238 16994 mongodb_2.6.12-3_amd64.deb
Checksums-Sha256:
 fbb0c2ef8b3c151d6e6f67cc97b2ad0501499386b5b62aa08468373ff26566b5 2738 
mongodb_2.6.12-3.dsc
 b534195da23b96936c1d702f4fac9edc516ac83737b9ec9bdce7324ac3b08c0d 53000 
mongodb_2.6.12-3.debian.tar.xz
 7017bcdadda0f32af1ee6ce1b7fada5c81a6397d997631c0c6d9fdd3d6557023 1255815488 
mongodb-clients-dbgsym_2.6.12-3_amd64.deb
 c757867ad5b391e7088d0be5c018b7b4cbef20900c59fc835e92a27faa4be0ff 47043808 
mongodb-clients_2.6.12-3_amd64.deb
 5bbf4005b5ca3be8a321d185dde5de72d1d9ca7fa90819ba64e5d62702266c21 178246036 
mongodb-server-dbgsym_2.6.12-3_amd64.deb
 2ce9e01a4747e06f3b160c9a0c52464613faf6102bb88e88d6e7808ddd676233 7216400 
mongodb-server_2.6.12-3_amd64.deb
 df480f6ca6c22409bd1dc6c2120be02e9726793f94773a0fa2baf70df1aac241 16994 
mongodb_2.6.12-3_amd64.deb
Files:
 bf33b695c54c99b71c92345ff5181d1e 2738 database optional mongodb_2.6.12-3.dsc
 c1bf57240f0a679bf96c0696ae4b4841 53000 database optional 
mongodb_2.6.12-3.debian.tar.xz
 40d2974b66c2a9b1c7859f71a660716b 1255815488 debug extra 
mongodb-clients-dbgsym_2.6.12-3_amd64.deb
 36a9205c8fe7c9e75df8c7a82314118f 47043808 database optional 
mongodb-clients_2.6.12-3_amd64.deb
 1a50e5879ebbbd7fe6ecaae0d15e0217 178246036 debug extra 
mongodb-server-dbgsym_2.6.12-3_amd64.deb
 3206ea83f7b1e367d935740a64a5f6ec 7216400 database optional 
mongodb-server_2.6.12-3_amd64.deb
 

Processed: maradns: diff for NMU version 2.0.13-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 806075 + pending
Bug #806075 [src:maradns] maradns: FTBFS when built with dpkg-buildpackage -A 
(No such file or directory)
Added tag(s) pending.

-- 
806075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#833532: calendar-google-provider causes crash of icedove

[Vladimir K]

I do not have calendar-google-provider installed, but have 
calendar-exchange-provider installed. Same crash happens. 
Setting "javascript.options.baselinejit" to "false" helps.

Bug#818817: marked as done (woo: FTBFS with libc 2.23: 'isnan' was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Tue, 9 Aug 2016 21:46:32 +0200
with message-id 

and subject line Closing the bug #818817
has caused the Debian Bug report #818817,
regarding woo: FTBFS with libc 2.23: 'isnan' was not declared in this scope
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.)


-- 
818817: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818817
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: woo
Version: 1.0+dfsg1-1
Severity: important
User: debian-gl...@lists.debian.org
Usertags: 2.23

This package fails to build with libc6 2.23 (2.23-0experimental0 from
experimental).

> sbuild (Debian sbuild) 0.68.0 (15 Jan 2016) on dl580gen9-02.hlinux
...

> build-src-tree/woo/pkg/dem/Particle.hpp: In member function 'void 
> Shape::setBaseColor(Real)':
> build-src-tree/woo/pkg/dem/Particle.hpp:360:39: error: 'isnan' was not 
> declared in this scope
>   void setBaseColor(Real c){ if(isnan(c)) return; 
> color=trunc(color)+(color<0?-1:1)*CompUtils::clamped(c,0,1); }
>^
> build-src-tree/woo/pkg/dem/Particle.hpp:360:39: note: suggested alternatives:
> In file included from /usr/include/c++/5/random:38:0,
>  from /usr/include/c++/5/bits/stl_algo.h:66,
>  from /usr/include/c++/5/algorithm:62,
>  from /usr/include/boost/iterator/iterator_concepts.hpp:29,
>  from /usr/include/boost/range/concepts.hpp:20,
>  from /usr/include/boost/range/size_type.hpp:20,
>  from /usr/include/boost/range/size.hpp:21,
>  from /usr/include/boost/range/functions.hpp:20,
>  from /usr/include/boost/range/iterator_range_core.hpp:38,
>  from /usr/include/boost/lexical_cast.hpp:30,
>  from build-src-tree/woo/core/Dispatcher.hpp:11,
>  from build-src-tree/woo/pkg/dem/Collision.hpp:2,
>  from build-src-tree/woo/pkg/dem/InsertionSortCollider.hpp:4,
>  from build-src-tree/../pkg/dem/InsertionSortCollider.cpp:3,
>  from build-src-tree/src/chunk-65-InsertionSortCollider.cpp:1:
> /usr/include/c++/5/cmath:641:5: note:   'std::isnan'
>  isnan(_Tp __x)
>  ^
> In file included from /usr/include/boost/lexical_cast/detail/inf_nan.hpp:35:0,
>  from 
> /usr/include/boost/lexical_cast/detail/converter_lexical_streams.hpp:64,
>  from 
> /usr/include/boost/lexical_cast/detail/converter_lexical.hpp:53,
>  from 
> /usr/include/boost/lexical_cast/try_lexical_convert.hpp:34,
>  from /usr/include/boost/lexical_cast.hpp:32,
>  from build-src-tree/woo/core/Dispatcher.hpp:11,
>  from build-src-tree/woo/pkg/dem/Collision.hpp:2,
>  from build-src-tree/woo/pkg/dem/InsertionSortCollider.hpp:4,
>  from build-src-tree/../pkg/dem/InsertionSortCollider.cpp:3,
>  from build-src-tree/src/chunk-65-InsertionSortCollider.cpp:1:
> /usr/include/boost/math/special_functions/fpclassify.hpp:579:14: note:   
> 'boost::math::isnan'
>  inline bool (isnan)(T x)
>   ^
> In file included from /usr/include/eigen3/Eigen/Core:441:0,
>  from build-src-tree/woo/lib/base/Math.hpp:55,
>  from build-src-tree/woo/core/Master.hpp:16,
>  from build-src-tree/woo/core/Dispatcher.hpp:13,
>  from build-src-tree/woo/pkg/dem/Collision.hpp:2,
>  from build-src-tree/woo/pkg/dem/InsertionSortCollider.hpp:4,
>  from build-src-tree/../pkg/dem/InsertionSortCollider.cpp:3,
>  from build-src-tree/src/chunk-65-InsertionSortCollider.cpp:1:
> /usr/include/eigen3/Eigen/src/Core/GlobalFunctions.h:67:36: note:   
> 'Eigen::isnan'
>EIGEN_ARRAY_DECLARE_GLOBAL_UNARY(isnan,scalar_isnan_op)
> ^
> /usr/include/eigen3/Eigen/src/Core/GlobalFunctions.h:17:4: note: in 
> definition of macro 'EIGEN_ARRAY_DECLARE_GLOBAL_UNARY'
>(NAME)(const Eigen::ArrayBase& x) { \
> ^
> In file included from /usr/include/eigen3/Eigen/Core:302:0,
>  from build-src-tree/woo/lib/base/Math.hpp:55,
>  from build-src-tree/woo/core/Master.hpp:16,
>  from build-src-tree/woo/core/Dispatcher.hpp:13,
>  from build-src-tree/woo/pkg/dem/Collision.hpp:2,
>  from build-src-tree/woo/pkg/dem/InsertionSortCollider.hpp:4,
> 

Bug#806075: maradns: diff for NMU version 2.0.13-1.2

[zeha]

Control: tags 806075 + pending

Dear maintainer,

I've prepared an NMU for maradns (versioned as 2.0.13-1.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Cheers,
Chris.


diff -Nru maradns-2.0.13/debian/changelog maradns-2.0.13/debian/changelog
--- maradns-2.0.13/debian/changelog 2016-07-01 15:38:52.0 +
+++ maradns-2.0.13/debian/changelog 2016-08-09 19:39:43.0 +
@@ -1,3 +1,11 @@
+maradns (2.0.13-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS when built with dpkg-buildpackage -A.
+(Closes: #806075). Patch and report by Santiago Vila .
+
+ -- Christian Hofstaedtler   Tue, 09 Aug 2016 19:39:43 +
+
 maradns (2.0.13-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru maradns-2.0.13/debian/rules maradns-2.0.13/debian/rules
--- maradns-2.0.13/debian/rules 2015-10-03 07:37:13.0 +
+++ maradns-2.0.13/debian/rules 2016-08-09 19:39:40.0 +
@@ -38,7 +38,7 @@
make -f $(MAKEFILE) all COMPILED=\"${COMPILED}\" VERSION=\"${VERSION}\"
mv rng/rng-32bit-tables.h.bak rng/rng-32bit-tables.h
 
-override_dh_install:
+override_dh_install-arch:
dh_install
mv $(TMP)/usr/sbin/bind2csv2.py $(TMP)/usr/sbin/bind2csv2
 
@@ -48,7 +48,7 @@
 override_dh_installexamples:
dh_installexamples -XMakefile
 
-override_dh_installman:
+override_dh_installman-arch:
dh_installman
cd $(CURDIR)/debian/maradns-deadwood/usr/share/man/man1/ && mv 
Deadwood.1 deadwood.1 && cd -
 

Bug#800305: marked as done (nis: Please migrate a supported debhelper compat level)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2016 18:50:22 +
with message-id 
and subject line Bug#800305: fixed in nis 3.17-35
has caused the Debian Bug report #800305,
regarding nis: Please migrate a supported debhelper compat level
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.)


-- 
800305: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nis
Severity: important
Usertags: deprecated-debhelper-compat-leq-3

Hi,

The package nis is using a debhelper compat level of 3 or less
according to lintian.  These compat levels have been deprecated for
the past ~10 years and debhelper will remove support for them in the near
future (as declared in [1]).

 * Please migrate the package to a supported debhelper compat level.
   - Compat 9 is recommended
   - Compat 5 is the bare minimum (compat 4 will be removed soon as
 well)

 * If your package uses any of the following tools, please remove them
   from the rules files.  Neither of them does anything except warn
   about their deprecation.
   - dh_desktop
   - dh_scrollkeeper (deadline: January 1st 2016)
   - dh_suidregister
   - dh_undocumented

 * Please note that your package might have been flagged for using
   e.g. "DH_COMPAT=2 dh_foo ...".
   - This will still cause issues when the compat level is removed.

 * If the package has been relying on dh_install being lenient about
   missing files, please see "MIGRATING TO COMPAT 5 OR LATER" in [1].

 * Deadline: 
   - compat 1+2: November 1st 2015
   - compat 3: January 1st 2016

If you are using other deprecated debhelper features (such as omitting
the debian/compat file), please consider fixing those while you are at
it.

Thanks,
~Niels

[1] https://lists.debian.org/debian-devel/2015/09/msg00257.html
--- End Message ---
--- Begin Message ---
Source: nis
Source-Version: 3.17-35

We believe that the bug you reported is fixed in the latest version of
nis, 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 800...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mark Brown  (supplier of updated nis 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: SHA1

Format: 1.8
Date: Tue, 09 Aug 2016 19:04:10 +0100
Source: nis
Binary: nis
Architecture: source amd64
Version: 3.17-35
Distribution: unstable
Urgency: low
Maintainer: Mark Brown 
Changed-By: Mark Brown 
Description:
 nis- clients and daemons for the Network Information Service (NIS)
Closes: 800305 815362
Changes:
 nis (3.17-35) unstable; urgency=low
 .
   * Bump debhelper compat version, no changes other than creating a
 compat file since no relevant interfaces changed (closes: #800305).
   * Don't use libslp-dev since it got removed, unfortunately the removal
 has been coordinated by reassigning bugs and the BTS really doesn't
 notify that well (closes: #815362).
   * Remove network manager support, it never worked well and their APIs
 changed incompatibly.
Checksums-Sha1:
 efb752af0e8b350da7437fe9491ac7793909015a 1404 nis_3.17-35.dsc
 75f5ced6d2dba1be0a7b5a14c4237fd9aa32f6d7 44918 nis_3.17-35.diff.gz
 dd0e7488d5526d4402ec1ca1ee2fd74d47ddd990 164576 nis_3.17-35_amd64.deb
Checksums-Sha256:
 184253f6640ebd6e107d91702102a27932be43b8d4e876cb9079c3a8c2fdb5f7 1404 
nis_3.17-35.dsc
 3311d0c52c531590e8c97698560d92149e77ae278ed25bb9b1a53a21bb563dad 44918 
nis_3.17-35.diff.gz
 0d5be81d3bcaf7d50d99c9464da1266334e5442e7020e150c20a45eeccb68af7 164576 
nis_3.17-35_amd64.deb
Files:
 589ea94f6d742548fbb6f65a66714061 1404 net extra nis_3.17-35.dsc
 d654f4a1d095f1e4a57840c5ec105822 44918 net extra nis_3.17-35.diff.gz
 c23ab8e2eb87797a7e0115b64abd7ea7 164576 net extra nis_3.17-35_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJXqiOoAAoJECTWi3JdVIfQWHUH/0kolDxJXD/EIGtQDwcTuL3s
5E6cheKyiQNLgP3FxU6xHoEYbf1oiqxHQuGHSKTLMU0yXyghgsLNSjAxmrJekYu6
BgVlwHnX8AcxGhcr1XJgn79lymj0FPJimRPlKQJtTf4VdIUKPK2Q5Klg5dKPuGbl
C1GUrc7kJQRdrZPQpZaixGm+rW/g03wzVMs2auNuYL/ilQuoh9wzzM924IoVK8xU

Bug#831342: marked as done (nis: FTBFS due lacking debhelper compat file)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2016 18:50:22 +
with message-id 
and subject line Bug#800305: fixed in nis 3.17-35
has caused the Debian Bug report #800305,
regarding nis: FTBFS due lacking debhelper compat file
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.)


-- 
800305: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nis
Version: 3.17-34
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

Package no longer builds from source in up-to-date sid
environment. Build log attached.

-- System Information:
Debian Release: 8.5
  APT prefers stable
  APT policy: (900, 'stable'), (500, 'stable-updates'), (500, 
'buildd-unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-0.bpo.1-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
dpkg-buildpackage: info: source package nis
dpkg-buildpackage: info: source version 3.17-34
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Mark Brown 
dpkg-buildpackage: info: host architecture amd64
(cd yp-tools-2.9 && [ -f Makefile ] && make distclean)
debian/rules:67: recipe for target 'clean' failed
(cd ypbind-mt-1.20.1  && [ -f Makefile ] && make distclean)
debian/rules:67: recipe for target 'clean' failed
(cd ypserv-2.19  && [ -f Makefile ] && make distclean)
debian/rules:67: recipe for target 'clean' failed
rm -rf ypbind-mt-1.20.1/rpcsvc
rm -rf /home/user/stuff/nis-3.17/debian/tmp
rm -rf ypserv-2.19/autom4te.cache
rm -f build debian/{files,substvars,templates.gen}
find . -name '*.bak' -o -name '*~' | xargs -r rm --
rm -f */config.cache
dh_autoreconf_clean
rm -f debian/debhelper.log
dpkg-source: info: using source format '1.0'
dpkg-source: info: building nis using existing nis_3.17.orig.tar.gz
dpkg-source: info: building nis in nis_3.17-34.diff.gz
dpkg-source: info: use the '3.0 (quilt)' format to have separate and documented 
changes to upstream files, see dpkg-source(1)
dpkg-source: info: building nis in nis_3.17-34.dsc
dh_autoreconf
debian/rules:37: recipe for target 'build' failed
--- End Message ---
--- Begin Message ---
Source: nis
Source-Version: 3.17-35

We believe that the bug you reported is fixed in the latest version of
nis, 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 800...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mark Brown  (supplier of updated nis 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: SHA1

Format: 1.8
Date: Tue, 09 Aug 2016 19:04:10 +0100
Source: nis
Binary: nis
Architecture: source amd64
Version: 3.17-35
Distribution: unstable
Urgency: low
Maintainer: Mark Brown 
Changed-By: Mark Brown 
Description:
 nis- clients and daemons for the Network Information Service (NIS)
Closes: 800305 815362
Changes:
 nis (3.17-35) unstable; urgency=low
 .
   * Bump debhelper compat version, no changes other than creating a
 compat file since no relevant interfaces changed (closes: #800305).
   * Don't use libslp-dev since it got removed, unfortunately the removal
 has been coordinated by reassigning bugs and the BTS really doesn't
 notify that well (closes: #815362).
   * Remove network manager support, it never worked well and their APIs
 changed incompatibly.
Checksums-Sha1:
 efb752af0e8b350da7437fe9491ac7793909015a 1404 nis_3.17-35.dsc
 75f5ced6d2dba1be0a7b5a14c4237fd9aa32f6d7 44918 nis_3.17-35.diff.gz
 dd0e7488d5526d4402ec1ca1ee2fd74d47ddd990 164576 nis_3.17-35_amd64.deb
Checksums-Sha256:
 184253f6640ebd6e107d91702102a27932be43b8d4e876cb9079c3a8c2fdb5f7 1404 
nis_3.17-35.dsc
 3311d0c52c531590e8c97698560d92149e77ae278ed25bb9b1a53a21bb563dad 44918 
nis_3.17-35.diff.gz
 0d5be81d3bcaf7d50d99c9464da1266334e5442e7020e150c20a45eeccb68af7 164576 
nis_3.17-35_amd64.deb
Files:
 589ea94f6d742548fbb6f65a66714061 1404 net extra 

Bug#815362: marked as done (nis: build-depends on libslp-dev)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2016 18:50:22 +
with message-id 
and subject line Bug#815362: fixed in nis 3.17-35
has caused the Debian Bug report #815362,
regarding nis: build-depends on libslp-dev
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.)


-- 
815362: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815362
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openslp-dfsg
Severity: serious

The last maintainer upload of openslp happened in 2007
and it's orphaned for 5.5 years now. The 1.2 branch is
completely abandoned upstream.

At the minimum the package should be upgraded to 2.0,
but the comment at
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2015-5177
suggests it's completely abandoned upstream.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: nis
Source-Version: 3.17-35

We believe that the bug you reported is fixed in the latest version of
nis, 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 815...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mark Brown  (supplier of updated nis 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: SHA1

Format: 1.8
Date: Tue, 09 Aug 2016 19:04:10 +0100
Source: nis
Binary: nis
Architecture: source amd64
Version: 3.17-35
Distribution: unstable
Urgency: low
Maintainer: Mark Brown 
Changed-By: Mark Brown 
Description:
 nis- clients and daemons for the Network Information Service (NIS)
Closes: 800305 815362
Changes:
 nis (3.17-35) unstable; urgency=low
 .
   * Bump debhelper compat version, no changes other than creating a
 compat file since no relevant interfaces changed (closes: #800305).
   * Don't use libslp-dev since it got removed, unfortunately the removal
 has been coordinated by reassigning bugs and the BTS really doesn't
 notify that well (closes: #815362).
   * Remove network manager support, it never worked well and their APIs
 changed incompatibly.
Checksums-Sha1:
 efb752af0e8b350da7437fe9491ac7793909015a 1404 nis_3.17-35.dsc
 75f5ced6d2dba1be0a7b5a14c4237fd9aa32f6d7 44918 nis_3.17-35.diff.gz
 dd0e7488d5526d4402ec1ca1ee2fd74d47ddd990 164576 nis_3.17-35_amd64.deb
Checksums-Sha256:
 184253f6640ebd6e107d91702102a27932be43b8d4e876cb9079c3a8c2fdb5f7 1404 
nis_3.17-35.dsc
 3311d0c52c531590e8c97698560d92149e77ae278ed25bb9b1a53a21bb563dad 44918 
nis_3.17-35.diff.gz
 0d5be81d3bcaf7d50d99c9464da1266334e5442e7020e150c20a45eeccb68af7 164576 
nis_3.17-35_amd64.deb
Files:
 589ea94f6d742548fbb6f65a66714061 1404 net extra nis_3.17-35.dsc
 d654f4a1d095f1e4a57840c5ec105822 44918 net extra nis_3.17-35.diff.gz
 c23ab8e2eb87797a7e0115b64abd7ea7 164576 net extra nis_3.17-35_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJXqiOoAAoJECTWi3JdVIfQWHUH/0kolDxJXD/EIGtQDwcTuL3s
5E6cheKyiQNLgP3FxU6xHoEYbf1oiqxHQuGHSKTLMU0yXyghgsLNSjAxmrJekYu6
BgVlwHnX8AcxGhcr1XJgn79lymj0FPJimRPlKQJtTf4VdIUKPK2Q5Klg5dKPuGbl
C1GUrc7kJQRdrZPQpZaixGm+rW/g03wzVMs2auNuYL/ilQuoh9wzzM924IoVK8xU
FCX1rUvn+iiZKjgt7e7OODUGWoYGX7I4YD2C+WoGUa+zFwCmkgtDn4eiuW7Bgwsq
p1ZlulfqaOyjCdEM1taCZtmTA2aEYIXLgZfIhgvsm73SXKNjb96EFetaMsrpBuA=
=uQdZ
-END PGP SIGNATURE End Message ---

Bug#833881: caja-dropbox: FTBFS in sid: ./autogen.sh: 80: shift: can't shift that many

[Andreas Beckmann]

Source: caja-dropbox
Version: 1.14.0-1
Severity: serious
Justification: fails to build from source

Hi,

caja-dropbox recently started to FTBFS on sid, this is probably related
to some change in the toolchain, since the package built there
previously:

 debian/rules build
dh build --with python2 --parallel
   dh_testdir -O--parallel
   dh_update_autotools_config -O--parallel
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/build/caja-dropbox-1.14.0'
NOCONFIGURE=1 ./autogen.sh
/usr/bin/mate-autogen
checking for autoconf >= 2.53...
  testing autoconf2.50... not found.
  testing autoconf... found 2.69
checking for automake >= 1.9...
  testing automake-1.15... found 1.15
checking for libtool >= 1.4.3...
  testing libtoolize... ACLOCAL='aclocal-1.15'
AUTOCONF='autoconf'
AUTOHEADER='autoheader'
AUTOMAKE='automake-1.15'
CFLAGS='-g -O2 -fdebug-prefix-map=/build/caja-dropbox-1.14.0=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security'
CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2'
CXXFLAGS='-g -O2 -fdebug-prefix-map=/build/caja-dropbox-1.14.0=. -fPIE 
-fstack-protector-strong -Wformat -Werror=format-security'
DEBIAN_FRONTEND='noninteractive'
DEB_BUILD_ARCH='amd64'
[...]
want_libtool='true'
want_maintainer_mode='false'
want_pkg_config='true'
want_yelp_tools='false'
./autogen.sh: 80: shift: can't shift that many
debian/rules:13: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 2
make[1]: Leaving directory '/build/caja-dropbox-1.14.0'
debian/rules:10: recipe for target 'build' failed
make: *** [build] Error 2


Andreas


caja-dropbox_1.14.0-1.log.gz
Description: application/gzip

Bug#833402: marked as done (wpasupplicant: wpa_supplicant does not start because it could not read the interface p2p-dev-wlp1s0)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2016 18:34:15 +
with message-id 
and subject line Bug#833402: fixed in wpa 2.5-2+v2.4-2
has caused the Debian Bug report #833402,
regarding wpasupplicant: wpa_supplicant does not start because it could not 
read the interface p2p-dev-wlp1s0
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.)


-- 
833402: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833402
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wpasupplicant
Version: 2.5-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

After upgrading the system, wpasupplicant does not start because
it could not read the interface p2p-dev-wlp1s0.  When running,

 wpa_supplicant -B -i wlp1s0 -c /etc/wpa_supplicant/wpa_supplicant.conf

I get,

wpa_supplicant could not read the interface p2p-dev-wlp1s0.

Current solution involves downgrading to version 2.3-2.4 from the
testing branch.

Might be related to this other bug report, https://bugs.archlinux.org/task/44731

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages wpasupplicant depends on:
ii  adduser   3.115
ii  libc6 2.23-4
ii  libdbus-1-3   1.10.8-1
ii  libnl-3-200   3.2.27-1
ii  libnl-genl-3-200  3.2.27-1
ii  libpcsclite1  1.8.17-1
ii  libreadline6  6.3-8+b4
ii  libssl1.0.2   1.0.2h-1
ii  lsb-base  9.20160629

wpasupplicant recommends no packages.

Versions of packages wpasupplicant suggests:
pn  libengine-pkcs11-openssl  
pn  wpagui

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: wpa
Source-Version: 2.5-2+v2.4-2

We believe that the bug you reported is fixed in the latest version of
wpa, 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 833...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andrew Shadura  (supplier of updated wpa 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: SHA1

Format: 1.8
Date: Tue, 09 Aug 2016 20:11:27 +0200
Source: wpa
Binary: hostapd wpagui wpasupplicant wpasupplicant-udeb
Architecture: source
Version: 2.5-2+v2.4-2
Distribution: unstable
Urgency: medium
Maintainer: Debian wpasupplicant Maintainers 

Changed-By: Andrew Shadura 
Description:
 hostapd- IEEE 802.11 AP and IEEE 802.1X/WPA/WPA2/EAP Authenticator
 wpagui - graphical user interface for wpa_supplicant
 wpasupplicant - client support for WPA and WPA2 (IEEE 802.11i)
 wpasupplicant-udeb - Client support for WPA and WPA2 (IEEE 802.11i) (udeb)
Closes: 827253 833402
Changes:
 wpa (2.5-2+v2.4-2) unstable; urgency=medium
 .
   * Apply patches from upstream to unbreak dedicated P2P Device support
 (closes: #833402).
   * Reapply an accidentally lost patch to fix pkcs11 OpenSSL engine
 initialisation (Closes: #827253).
   * Retroactively redact the last changelog entry to represent the actual
 upload more accurately.
Checksums-Sha1:
 7c7a3e6e32a4a2a4181853701ccd6004e8e72953 2185 wpa_2.5-2+v2.4-2.dsc
 fb5d46a5992d2b7a02eeade572a6856aa82f7ac7 86532 wpa_2.5-2+v2.4-2.debian.tar.xz
Checksums-Sha256:
 801bf58ca9c9544dcf3c370378d788d15df3e15d5adebc77b6427708e7835d4e 2185 
wpa_2.5-2+v2.4-2.dsc
 3782e721cbd436cf36756d9809843ea7af8b9d588cc2bc392262873d520dd7b4 86532 
wpa_2.5-2+v2.4-2.debian.tar.xz
Files:
 32bc3107fbbd13e3c1ba9a0f070778ff 2185 net optional wpa_2.5-2+v2.4-2.dsc
 bdc4b81ae7a799204703560ac6fa6ee6 86532 net optional 
wpa_2.5-2+v2.4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJXqh21AAoJEJ1bI/kYT6UU5c0H/jS4DeFVFASWZKcYl4N5IU3X
tzDp9KmlCRdKZNWgYzO3SM1ojLEYjhmA+OHPHBcKMCaGwsTrz8U1Xk23eEjtYMoh
ydky7sTEZS839TENiK1yw1UFBMGCWaaRn3Wcjrl9PgHYf1swkYPSuD+8g0WWbRYO

Bug#833874: marked as done (yara-python: FTBFS: yara-python.c:18:20: fatal error: Python.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2016 18:19:28 +
with message-id 
and subject line Bug#833874: fixed in yara-python 3.5.0+dfsg-2
has caused the Debian Bug report #833874,
regarding yara-python: FTBFS: yara-python.c:18:20: fatal error: Python.h: No 
such file or directory
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
833874: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yara-python
Version: 3.5.0+dfsg-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

yara-python fails to build from source in unstable/amd64:

  [..]

  
  
**
  ** Starting build 
  **
  
**
  
   Package:  yara-python
   Version:  3.5.0+dfsg-1
   Build architecture:   amd64
   Date: Tue, 09 Aug 2016 18:49:19 +0100
   Hostname: 3bee5fd8e301
   Uname:Linux 3bee5fd8e301 4.6.0-1-amd64 #1 SMP Debian 4.6.4-1 
(2016-07-18) x86_64 GNU/Linux
   /etc/timezone:Europe/London
  
  
**
  ** Installing build dependencies  
  **
  
**
  
  dh_testdir
  dh_testroot
  dh_prep
  dh_testdir
  dh_testroot
  dh_install
  dh_installdocs
  dh_installchangelogs
  dh_compress
  dh_fixperms
  dh_installdeb
  dh_gencontrol
  dh_md5sums
  dh_builddeb
  dpkg-deb: building package 'yara-python-build-deps' in 
'../yara-python-build-deps_3.5.0+dfsg-1_all.deb'.
  
  The package has been created.
  Attention, the package has been created in the current directory,
  not in ".." as indicated by the message above!
  Selecting previously unselected package yara-python-build-deps.
  (Reading database ... 23218 files and directories currently installed.)
  Preparing to unpack yara-python-build-deps_3.5.0+dfsg-1_all.deb ...
  Unpacking yara-python-build-deps (3.5.0+dfsg-1) ...
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Correcting dependencies... Done
  The following additional packages will be installed:
libjansson4 libyara-dev libyara3 python-all python-setuptools python3-all
python3-pkg-resources python3-setuptools
  Suggested packages:
python-setuptools-doc
  The following NEW packages will be installed:
libjansson4 libyara-dev libyara3 python-all python-setuptools python3-all
python3-pkg-resources python3-setuptools
  0 upgraded, 8 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  Need to get 692 kB of archives.
  After this operation, 2439 kB of additional disk space will be used.
  Get:1 http://httpredir.debian.org/debian sid/main amd64 python-all amd64 
2.7.11-2 [938 B]
  Get:2 http://httpredir.debian.org/debian sid/main amd64 python-setuptools all 
20.10.1-1.1 [203 kB]
  Get:3 http://httpredir.debian.org/debian sid/main amd64 python3-all amd64 
3.5.1-4 [928 B]
  Get:4 http://httpredir.debian.org/debian sid/main amd64 python3-pkg-resources 
all 20.10.1-1.1 [112 kB]
  Get:5 http://httpredir.debian.org/debian sid/main amd64 python3-setuptools 
all 20.10.1-1.1 [122 kB]
  Get:6 http://httpredir.debian.org/debian sid/main amd64 libjansson4 amd64 
2.7-5 [27.8 kB]
  Get:7 http://httpredir.debian.org/debian sid/main amd64 libyara3 amd64 
3.5.0+dfsg-2 [101 kB]
  Get:8 http://httpredir.debian.org/debian sid/main amd64 libyara-dev amd64 
3.5.0+dfsg-2 [125 kB]
  Fetched 692 kB in 0s (37.0 MB/s)
  Selecting previously unselected package python-all.
  (Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading 

Processed (with 1 error): src: distinctions are not useful for single binary packages :(

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 800305 831342
Bug #800305 [src:nis] nis: Please migrate a supported debhelper compat level
Unable to merge bugs because:
package of #831342 is 'nis' not 'src:nis'
Failed to forcibly merge 800305: Did not alter merged bugs.

>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
800305: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800305
831342: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed (with 1 error): vdlkvgnjdfskjlvnsdf

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> merge 800305 831342
Bug #800305 [src:nis] nis: Please migrate a supported debhelper compat level
Unable to merge bugs because:
package of #831342 is 'nis' not 'src:nis'
Failed to merge 800305: Did not alter merged bugs.

>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
800305: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800305
831342: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#833875: apktool: FTBFS: YamlStringEscapeUtils.java:19: error: package org.apache.commons.lang3 does not exist

[Chris Lamb]

Source: apktool
Version: 2.1.1+dfsg-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

apktool fails to build from source in unstable/amd64:

  [..]

  :brut.j.util:processResources (Thread[Task worker Thread 5,5,main]) started.
  :brut.j.util:processResources
  :brut.j.dir:processResources (Thread[Task worker Thread 4,5,main]) started.
  :brut.j.dir:processResources
  :brut.apktool:apktool-lib:processResources (Thread[Task worker Thread 
6,5,main]) started.
  :brut.apktool:apktool-lib:processResources
  :brut.apktool:apktool-cli:processResources (Thread[Task worker Thread 
7,5,main]) started.
  :brut.apktool:apktool-cli:processResources
  file or directory 
'/home/lamby/temp/cdt.20160809184706.SGuIYBHTvk.apktool/apktool-2.1.1+dfsg/brut.j.util/src/main/resources',
 not found
  Skipping task ':brut.j.util:processResources' as it has no source files.
  :brut.j.util:processResources UP-TO-DATE
  :brut.j.util:processResources (Thread[Task worker Thread 5,5,main]) 
completed. Took 0.011 secs.
  file or directory 
'/home/lamby/temp/cdt.20160809184706.SGuIYBHTvk.apktool/apktool-2.1.1+dfsg/src/main/java',
 not found
  Skipping task ':compileJava' as it has no source files.
  :compileJava UP-TO-DATE
  file or directory 
'/home/lamby/temp/cdt.20160809184706.SGuIYBHTvk.apktool/apktool-2.1.1+dfsg/brut.apktool/src/main/java',
 not found
  Skipping task ':brut.apktool:compileJava' as it has no source files.
  :brut.apktool:compileJava UP-TO-DATE
  :brut.apktool:compileJava (Thread[Task worker Thread 2,5,main]) completed. 
Took 0.028 secs.
  :processResources (Thread[Task worker Thread 2,5,main]) started.
  :processResources
  file or directory 
'/home/lamby/temp/cdt.20160809184706.SGuIYBHTvk.apktool/apktool-2.1.1+dfsg/src/main/resources',
 not found
  Skipping task ':processResources' as it has no source files.
  :processResources UP-TO-DATE
  :processResources (Thread[Task worker Thread 2,5,main]) completed. Took 0.003 
secs.
  :classes (Thread[Task worker Thread 2,5,main]) started.
  :classes
  Skipping task ':classes' as it has no actions.
  :classes UP-TO-DATE
  :classes (Thread[Task worker Thread 2,5,main]) completed. Took 0.0 secs.
  :jar (Thread[Task worker Thread 2,5,main]) started.
  :jar
  :brut.apktool:processResources (Thread[Daemon worker,5,main]) started.
  :brut.apktool:processResources
  file or directory 
'/home/lamby/temp/cdt.20160809184706.SGuIYBHTvk.apktool/apktool-2.1.1+dfsg/brut.j.dir/src/main/resources',
 not found
  Skipping task ':brut.j.dir:processResources' as it has no source files.
  :brut.j.dir:processResources UP-TO-DATE
  :brut.j.dir:processResources (Thread[Task worker Thread 4,5,main]) completed. 
Took 0.019 secs.
  file or directory 
'/home/lamby/temp/cdt.20160809184706.SGuIYBHTvk.apktool/apktool-2.1.1+dfsg/brut.apktool/src/main/resources',
 not found
  Skipping task ':brut.apktool:processResources' as it has no source files.
  :brut.apktool:processResources UP-TO-DATE
  :brut.apktool:processResources (Thread[Daemon worker,5,main]) completed. Took 
0.001 secs.
  :brut.apktool:classes (Thread[Daemon worker,5,main]) started.
  :brut.apktool:classes
  Skipping task ':brut.apktool:classes' as it has no actions.
  :brut.apktool:classes UP-TO-DATE
  :brut.apktool:classes (Thread[Daemon worker,5,main]) completed. Took 0.0 secs.
  :brut.apktool:jar (Thread[Daemon worker,5,main]) started.
  :brut.apktool:jar
  file or directory 
'/home/lamby/temp/cdt.20160809184706.SGuIYBHTvk.apktool/apktool-2.1.1+dfsg/brut.apktool/apktool-cli/src/main/resources',
 not found
  Skipping task ':brut.apktool:apktool-cli:processResources' as it has no 
source files.
  :brut.apktool:apktool-cli:processResources UP-TO-DATE
  :brut.apktool:apktool-cli:processResources (Thread[Task worker Thread 
7,5,main]) completed. Took 0.018 secs.
  :compileJava (Thread[Task worker,5,main]) completed. Took 0.048 secs.
  Invalidating in-memory cache of 
/home/lamby/temp/cdt.20160809184706.SGuIYBHTvk.apktool/apktool-2.1.1+dfsg/.gradle/2.13/taskArtifacts/fileSnapshots.bin
  Invalidating in-memory cache of 
/home/lamby/temp/cdt.20160809184706.SGuIYBHTvk.apktool/apktool-2.1.1+dfsg/.gradle/2.13/taskArtifacts/fileHashes.bin
  Invalidating in-memory cache of 
/home/lamby/temp/cdt.20160809184706.SGuIYBHTvk.apktool/apktool-2.1.1+dfsg/.gradle/2.13/taskArtifacts/taskArtifacts.bin
  Executing task ':brut.apktool:jar' (up-to-date check took 0.052 secs) due to:
No history is available.
  Executing task ':brut.j.common:compileJava' (up-to-date check took 0.037 
secs) due to:
No history is available.
  Executing task ':brut.apktool:apktool-lib:processResources' (up-to-date check 
took 0.031 secs) due to:
No history is available.
  Executing task ':jar' (up-to-date check took 0.054 secs) due to:
No history is available.
  All input files are considered out-of-date for incremental 

Bug#833870: libprimesieve7-dev-common: fails to upgrade from 'testing' - trying to overwrite /usr/include/primesieve/Callback.hpp

[Jerome BENOIT]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi Andreas, thanks for your report.

On 09/08/16 17:50, Andreas Beckmann wrote:
> Package: libprimesieve7-dev-common
> Version: 5.7.0+ds-1
> 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#s-replaces
> 
>>From the attached log (scroll to the bottom...):
> 
>   Selecting previously unselected package libprimesieve7-dev-common.
>   Preparing to unpack .../libprimesieve7-dev-common_5.7.0+ds-1_all.deb ...
>   Unpacking libprimesieve7-dev-common (5.7.0+ds-1) ...
>   dpkg: error processing archive 
> /var/cache/apt/archives/libprimesieve7-dev-common_5.7.0+ds-1_all.deb 
> (--unpack):
>trying to overwrite '/usr/include/primesieve/Callback.hpp', which is also 
> in package libprimesieve6-dev-common 5.6.0+ds-2
>   Errors were encountered while processing:
>/var/cache/apt/archives/libprimesieve7-dev-common_5.7.0+ds-1_all.deb
> 
> 
> cheers,
> 
> Andreas
> 
> 
> 

- -- 
Jerome BENOIT, Ph.D. | jgmbenoit-at+rezozer*dot_net
http://www.rezozer.net/

- -- 
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B
-BEGIN PGP SIGNATURE-

iQQcBAEBCgAGBQJXqgxMAAoJED+SGaZ/NsaL/CIgAJ5IKRH4RvL5bdfLv/Ug4e2a
I3xNBjYZCdUskP9V/XaRw3Od/6hUKQQnzI8Urp+HhDTqbrFRsz/lsiECzorXIQi/
nLUPYrMzhka88YG1DOhsKdQ9OYIoZZ7BjB6nE6RmX4tdCUPN2kjKTFL297QrIrWK
m3AMkddaRzyWsXHAtXLAaawivoS74qzWnM4IVCMWriTy+GJhLQkLGvvBJ4VS/p3K
9nGVxsSmkHhiY5SNjDZ1Jjf0ffMI2s9xm3fr7XjFSM3TQS9Z2DS5nEl8Q3E/S9Qi
hXdL4zAiPZWNt9M/FnwqBfiTS9IqTlyxfMPQid5zFVaeSIckjfyiEBKEICh9QbYY
0/bG0m1D6aNpDwNAOfBdQ11+HDZZehixmdsyFDvyNLfkIfP9BnRIZpJ0qw/cwIvl
gHvukodKtKq6Z5wo9ZuszkFYAqfKu2cL0UIATdu/2YF0J/YHvVNqLNBrNSvUDvbj
QLVYUHk93pyEYkOkxYF39MwLsXpL3OTF0rGhdt2EbG4S1vvfCavEqReEMfHnndOW
NchAH7jFkoohxd/NT+PbXbfyxgWtv7tWJF6S1NzxzvNZW6lFmjmfUMWtycUwEvIX
J/Isg551XdQal6IYQ90gZ8ayVEcFYEhUJhjuu9K5VRoTNndipJfcZnT2OPRUi0Mf
ubEt5e2bhuDa6ppT0hnkUmb4k9bxnqcVftM8dCIhZ0YK9VP+ifeqWWA5pN1oC3u0
fulPUbBbKVGIuWpIHhOKf84bRkxlPGSBjGMNWUpAqDxGQiDGMoXOS0EopNRk4DmS
hv7p4YraG07gA/Fmk3sGFB4l7sTnhWuJDY9rjezqVT2LZrcnemFXUZOIyURdF5Iu
ZM9Nxcn0c1brZEuI/ISOTR+nwH14Q607XeE8EomPRb/wNgu7M3IM7fVLIwgaj/Oa
iRQFDZiBcFRDpvlmbXgi9zYHF77ekHA5xAO1Y9HRet1GkjM6TEjV8SGyc9CgHxHD
CsT80yn8YhiukpQcEvswCIbUQRXiSIb6wbsbJnvyYX92czOQHqSD6JGIZ/c6rEDK
ZfqJ5h5iZumKKriWgjy83M95DvBGghZOw2xREGTZ5AdNyyn3cYKPcc/EfbFaR8c+
g6lPY5LnwGUsQ/wGN+fCZWyEUzrOoBW2t/bLrO3BnA+R8BqrrO3cNdAtG5hh1dKD
7FZSjpjoDyjeweAJ7oaQPRcY1xm/L4HRzGV2gG1CUydePGshKjL8Miu4gT4TBsEX
Ssg1av8aEBf/DsgwxuMDRnbGce988ncj4xSKRTy5x15o1t6ZEbqLADBcntJSUmFl
00g/91c+Z0Cxfpo4tfKVRpOUwoJ0M3F4bsTIDuAFaAqbTq7R4BdC2fNpjxmUlr8=
=vUGz
-END PGP SIGNATURE-

Bug#833870: libprimesieve7-dev-common: fails to upgrade from 'testing' - trying to overwrite /usr/include/primesieve/Callback.hpp

[Andreas Beckmann]

Package: libprimesieve7-dev-common
Version: 5.7.0+ds-1
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#s-replaces

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package libprimesieve7-dev-common.
  Preparing to unpack .../libprimesieve7-dev-common_5.7.0+ds-1_all.deb ...
  Unpacking libprimesieve7-dev-common (5.7.0+ds-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libprimesieve7-dev-common_5.7.0+ds-1_all.deb (--unpack):
   trying to overwrite '/usr/include/primesieve/Callback.hpp', which is also in 
package libprimesieve6-dev-common 5.6.0+ds-2
  Errors were encountered while processing:
   /var/cache/apt/archives/libprimesieve7-dev-common_5.7.0+ds-1_all.deb


cheers,

Andreas


libprimesieve6-dev-common=5.6.0+ds-2_libprimesieve7-dev-common=5.7.0+ds-1.log.gz
Description: application/gzip

Bug#833335: namazu2-index-tools and namazu2: error when trying to install together

[Andreas Beckmann]

Followup-For: Bug #85
Control: found -1 2.0.21-16

Hi,

there is another file that was moved from namazu2-index-tools to
namazu2 without adding proper Breaks+Replaces:

  Selecting previously unselected package namazu2.
  Preparing to unpack .../namazu2_2.0.21-16_amd64.deb ...
  Unpacking namazu2 (2.0.21-16) ...
  dpkg: error processing archive 
/var/cache/apt/archives/namazu2_2.0.21-16_amd64.deb (--unpack):
   trying to overwrite '/usr/bin/nmzgrep', which is also in package 
namazu2-index-tools 2.0.21-12
  Processing triggers for libc-bin (2.23-4) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/namazu2_2.0.21-16_amd64.deb


Andreas

Processed: Re: namazu2-index-tools and namazu2: error when trying to install together

[Debian Bug Tracking System]

Processing control commands:

> found -1 2.0.21-16
Bug #85 {Done: NOKUBI Takatsugu } 
[namazu2,namazu2-index-tools] namazu2-index-tools and namazu2: error when 
trying to install together
Marked as found in versions namazu2/2.0.21-16; no longer marked as fixed in 
versions namazu2/2.0.21-16 and reopened.

-- 
85: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=85
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#821670: marked as done (yubikey-val: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2016 16:31:20 +
with message-id 
and subject line Bug#821670: fixed in yubikey-val 2.38-1
has caused the Debian Bug report #821670,
regarding yubikey-val: PHP 7.0 Transition
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.)


-- 
821670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: yubikey-val
Version: 2.33-1
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The yubikey-val package currently depends on php5 php5-cli php5-curl
php5-mysql php5-pgsql .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: yubikey-val -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

- -- System Information:
Debian Release: 8.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUrpXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsH+RQP/1Lacjr2RsXZiNxyq1ahDz5W
v+k5Du1xO4s+gCIxmjbgF1mNhqipK8ufrniyB05qd8YPMtquE9OUovo8xnjMvHYs
fktQggZ6h7yQD44kADYcyFePi/xfm1I/MVvjfXkqy4WfdQplEzwFlWlpur/ALtgT
h4hrLlM77utrk1w0vV0aDzsVKkflTR91mcdkqla6FxbnfMn7I+I06QrnNceK1dcN

Bug#831122: marked as done (yp-tools: FTBFS with GCC 6: do_ypcall.c:47:29: error: 'UDPTIMEOUT' defined but not used [-Werror=unused-const-variable=])

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2016 16:31:07 +
with message-id 
and subject line Bug#831122: fixed in yp-tools 3.3-4
has caused the Debian Bug report #831122,
regarding yp-tools: FTBFS with GCC 6: do_ypcall.c:47:29: error: 'UDPTIMEOUT' 
defined but not used [-Werror=unused-const-variable=]
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.)


-- 
831122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yp-tools
Version: 3.3-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  
> -I. -I/usr/include/tirpc -DLOCALEDIR=\"/usr/share/locale\" -Wdate-time 
> -D_FORTIFY_SOURCE=2 -W -Wall -Wbad-function-cast -Wcast-align -Winline 
> -Wnested-externs -Wshadow -Wmissing-declarations -Wmissing-prototypes 
> -Wstrict-prototypes -Wundef -Werror -D_REENTRANT=1 -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -c -o do_ypcall.lo 
> do_ypcall.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I. -I/usr/include/tirpc 
> -DLOCALEDIR=\"/usr/share/locale\" -Wdate-time -D_FORTIFY_SOURCE=2 -W -Wall 
> -Wbad-function-cast -Wcast-align -Winline -Wnested-externs -Wshadow 
> -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wundef 
> -Werror -D_REENTRANT=1 -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -c do_ypcall.c  -fPIC -DPIC -o .libs/do_ypcall.o
> do_ypcall.c:47:29: error: 'UDPTIMEOUT' defined but not used 
> [-Werror=unused-const-variable=]
>  static const struct timeval UDPTIMEOUT = {5, 0};
>  ^~
> cc1: all warnings being treated as errors
> make[3]: *** [do_ypcall.lo] Error 1

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/yp-tools_3.3-3_unstable_gcc6.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: yp-tools
Source-Version: 3.3-4

We believe that the bug you reported is fixed in the latest version of
yp-tools, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 831...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mark Brown  (supplier of updated yp-tools package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Format: 1.8
Date: Tue, 09 Aug 2016 14:53:16 +0100
Source: yp-tools
Binary: yp-tools libnis-dev libnis1
Architecture: source amd64
Version: 3.3-4
Distribution: unstable
Urgency: low
Maintainer: Mark Brown 
Changed-By: Mark Brown 
Description:
 libnis-dev - Library for NIS applications - development files
 libnis1- Library for Network Information Service (NIS) applications
 yp-tools   - Tools for working with Network Information System (NIS)
Closes: 831122
Changes:
 yp-tools (3.3-4) unstable; urgency=low
 .
   * Remove unused UDPTIMEOUT definition.  Why do people think -Werror is
 a good idea?  (closes: #831122).
Checksums-Sha1:
 e2ef33c4e6299cf25c8142609e2c5cfbc1c94cbd 1471 yp-tools_3.3-4.dsc
 5f72efbe2abac797ea3ae662fea6e57ef742581d 5192 yp-tools_3.3-4.debian.tar.xz
 b9601e1bc4f5fda342cd226f54f8163b4ce08366 14494 libnis-dev_3.3-4_amd64.deb
 d38c459a7896c32fb24d0c2b8b6b3ca49f478e9a 47622 libnis1-dbgsym_3.3-4_amd64.deb
 6e04a687461e08c53506772a717335496892169b 17234 

Bug#821669: marked as done (yubikey-ksm: PHP 7.0 Transition)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2016 16:31:14 +
with message-id 
and subject line Bug#821669: fixed in yubikey-ksm 1.15-5
has caused the Debian Bug report #821669,
regarding yubikey-ksm: PHP 7.0 Transition
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.)


-- 
821669: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821669
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: yubikey-ksm
Version: 1.15-4
Severity: important
User: pkg-php-ma...@lists.alioth.debian.org
Usertags: php7.0-transition

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer(s),

this bug is a part of ongoing php7.0 transition.  It is filled as
important, but the severity will be bumped to serious within quite short
(~month) timeframe as the transition was announced almost 3 months ago.

The yubikey-ksm package currently depends on php5 php5-mcrypt php5-mysql
php5-pgsql .

PHP 7.0 has landed in unstable with substantial changes to the packaging:

  1. Every package built from src:phpMAJOR.MINOR now include
 phpMAJOR.MINOR in the name, so f.e. php5-fpm is now php7.0-fpm.

  2. Accompanying src:php-defaults builds 1:1 mapping to a default
 MAJOR.MINOR version, e.g. php-fpm depends on php7.0-fpm.  When you
 specify a dependency, please use the generic name, unless you
 absolutely know that won't work for you.

  3. Every path in the system has been changed to a versioned, e.g.
 /etc/php5/cli is now /etc/php/7.0/cli

  4. dh_php5 is now dh_php

  5. php-pear is not built from independent source package.

  6. master-7.0 branches of several extensions (php-apcu, xdebug,
 php-apcu-bc) can be used as a template how to change the PHP
 extension packaging.  It's mostly cut since the d/rules tries
 to figure-out most of the variables from debian/ directory.

  7. pkg-php-tools package now supports PHP 7.0 packaging and if your
 package uses pkg-php-tools a simple binNMU is all it might need

  8. PHP 7.0 has changed extension API, so most-if-not-all extensions
 need work from upstream to be compatible with PHP 7.0.

  9. We expect to ship next Debian release (stretch) only with PHP
 7.0, that means that all packages needs to be made compatible with
 PHP 7.0.  Fortunately the PHP 7.0 is mostly compatible with properly
 maintained software.  However some extensions has been deprecated
 (f.e. mysql) and thus old unmaintained software will stop working
 and it will have to be either patched or removed from stable Debian.

So what you need to do:

Replace every occurence of php5 with just php, e.g. if you depend on
'php5' then you just need to depend on 'php'.  Also if you package a web
application and depend on specific SAPI, I would recommend depending just
on 'php' package and let the user decide whether he will install php-fpm,
libapache2-mod-php or php-cgi.

The script that was used to get the list of packages for MBF was not a
particular smart one (so it doesn't detect alternatives, etc.), so if
there's a false positive, please excuse me and just close the bug with
short explanation.

The other options that might be used with packages that don't and won't
support PHP 7.0 is to remove the software from Debian by changing the
title of this bugreport to:

RM: yubikey-ksm -- ROM; doesn't support PHP 7.0

reassigning it to ftp.debian.org pseudo-package and changing severity to
'normal'.

Also feel free to contact the maintainers at one of the lists:

pkg-php-p...@lists.alioth.debian.org -- for PEAR related packages
pkg-php-p...@lists.alioth.debian.org -- for PHP extensions
pkg-php-ma...@lists.alioth.debian.org -- main PHP packaging and catch-all

Cheers, Ondrej

- -- System Information:
Debian Release: 8.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 
'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.2.0-35-generic (SMP w/24 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQJ8BAEBCgBmBQJXFUrpXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQzMEI5MzNEODBGQ0UzRDk4MUEyRDM4RkIw
Qzk5QjcwRUY0RkNCQjA3AAoJEAyZtw70/LsHjcYP/jJXzG1Yq7BzdUl3y59jjzz7
tM6y3HvZugrTT8fGWkaUixYdboPlSFDoF89xLw8qY80ZivLmpG9x/lFQCKyeq6u3
SFErYENp1hyqE7z+/ub740DPT5uBJ7kfOz64d1DUijSPpUkaG+e/WDvZmwyktNH7
6V9ZEbit7MPHZbLqdW/6rrwLXVfcJC8y+verOrsJbt6HXTq6kS0TGYJm2lRJCWup

Bug#833846: marked as done (fflas-ffpack: don't generate optimised code based on the build machine)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2016 16:21:21 +
with message-id 
and subject line Bug#833846: fixed in fflas-ffpack 2.2.1-2
has caused the Debian Bug report #833846,
regarding fflas-ffpack: don't generate optimised code based on the build machine
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.)


-- 
833846: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fflas-ffpack
Version: 2.2.1-1
Severity: important

Dear Maintainer,

fflas-ffpack on amd64 was built with "-msse4.1 -mfma -mavx2" as can be seen
from the output of `pkg-config --cflags fflas-ffpack`. This unfortunately makes
it crash on amd64 machines that don't support these instructions, and we are
running into this issue whilst testing SageMath.

Please disable any build options that set optimisations based on autodetection
of the CPU features of the build machine.

It should be OK to hard-code "-mmmx -msse -msse2" for amd64 and "-msse -msse2"
for i386, according to wRAR on #debian-devel. This is somewhat based on
information from [1]. There might be other optimisations you can make, but I
haven't yet done the detailed research for that.

X

[1] https://lists.debian.org/debian-devel-announce/2016/05/msg1.html

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable'), (300, 'unstable'), (200, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages fflas-ffpack depends on:
ii  fflas-ffpack-common  2.2.1-1

fflas-ffpack recommends no packages.

Versions of packages fflas-ffpack suggests:
pn  fflas-ffpack-dev-doc   
pn  fflas-ffpack-user-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: fflas-ffpack
Source-Version: 2.2.1-2

We believe that the bug you reported is fixed in the latest version of
fflas-ffpack, 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 833...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Doug Torrance  (supplier of updated fflas-ffpack 
package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 09 Aug 2016 08:47:36 -0400
Source: fflas-ffpack
Binary: fflas-ffpack fflas-ffpack-common fflas-ffpack-user-doc 
fflas-ffpack-dev-doc
Architecture: source all amd64
Version: 2.2.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Doug Torrance 
Description:
 fflas-ffpack - Finite field linear algebra subroutines/package
 fflas-ffpack-common - Finite field linear algebra subroutines/package - common 
files
 fflas-ffpack-dev-doc - FFLAS-FFPACK Developer Documentation
 fflas-ffpack-user-doc - FFLAS-FFPACK User Documentation
Closes: 833846
Changes:
 fflas-ffpack (2.2.1-2) unstable; urgency=medium
 .
   * debian/rules
 - Disable processor extensions. May be present at build but not runtime
   (Closes: #833846).
Checksums-Sha1:
 d0311aa9971b14d72d7f10e9974a02df3e371099 2538 fflas-ffpack_2.2.1-2.dsc
 b0dfc02dd56a66ebedafa216bd7df837a831a36d 4940 
fflas-ffpack_2.2.1-2.debian.tar.xz
 c823789ccfa08dd3bffd4f21b40f527263f1cc9b 172076 
fflas-ffpack-common_2.2.1-2_all.deb
 5e58fc4437ef5cbe3c932e5f1da12d9498719ca4 417492 
fflas-ffpack-dev-doc_2.2.1-2_all.deb
 c17d17ed3e137af4579d93d882d66c6a6078f2af 115078 
fflas-ffpack-user-doc_2.2.1-2_all.deb
 3dbe9ebe282321144189f6272c588186b833d90b 10884 fflas-ffpack_2.2.1-2_amd64.deb
Checksums-Sha256:
 648ab47250d6395e2be0ee07f6472a22b127f5c1533ed04598573458e2f21f23 2538 
fflas-ffpack_2.2.1-2.dsc
 ed2d1bbbd4e4866606ba9b14589836bd18ebce07627ff58ac5fab46f717935d0 4940 
fflas-ffpack_2.2.1-2.debian.tar.xz
 b7333df8005ae3b2f38a84da8c7161d694d6202a018000ccef8eef71f151f65d 172076 
fflas-ffpack-common_2.2.1-2_all.deb
 

Bug#781180: Please add new youtube-dl in jessie-updates

[Antoine Beaupré]

On 2016-08-09 11:42:29, anarcat wrote:
> I will file a bug against release.debian.org to start that conversation.

See #833865 for now.

-- 
Conformity-the natural instinct to passively yield to that vague something
recognized as authority.
- Mark Twain

Bug#833868: boost1.60: do not release with Stretch

[Emilio Pozuelo Monfort]

Source: boost1.60
Severity: serious

We want to release Stretch just with boost 1.61. boost 1.60 should be
removed before the release.

Emilio

Processed: Re: Bug#781180: Please add new youtube-dl in jessie-updates

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #781180 [youtube-dl] [youtube-dl] Error fetch video from youtube
Severity set to 'grave' from 'normal'
> fixed -1 2016.02.22-1~bpo8+1
Bug #781180 [youtube-dl] [youtube-dl] Error fetch video from youtube
Marked as fixed in versions youtube-dl/2016.02.22-1~bpo8+1.

-- 
781180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=781180
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#822852: gedit-latex-plugin: Activation of the plugin makes gedit segfault on startup

[Fernando Ike]

On Thu, 28 Apr 2016 13:00:54 +0200 =?utf-8?q?Pawe=C5=82_T=2E_Jochym?=
 wrote:
  Hi,
 
> Package: gedit-latex-plugin
> Version: 3.8.0-3
> Severity: critical
> Justification: breaks unrelated software
> 
> After upgrade to gedit 3.20, gedit started to crash (segfaults) on
> startup. Deactivaion or uninstall of the plugin makes it work again.
> The plugin is completely unusable in present form.

  I tried to reproduce issue and didn't crash. Is this keep happened
for you? 


Best,
-- 
Fernando Ike
http://www.fernandoike.com

Bug#830824: Silently corrupted file in snapshots after send/receive

[Petter Reinholdtsen]

[ Antonio Russo 2016-07-11 ]
> Sorry, there is no 0.6.5.8 release. The fix does exist in the master branch,
> however.  (bc77ba7: OpenZFS 6513 - partially filled holes lose birth time)

As far as I can see from https://github.com/zfsonlinux/zfs/issues/4809 >,
the issue is still unsolved upstream.

Are you sure that commit is enough to solve the problem?  There are others
mentioned in issue #4809.

See also https://www.illumos.org/issues/6370 >,
https://www.illumos.org/issues/6513 > and
https://www.illumos.org/issues/6844 >.

-- 
Happy hacking
Petter Reinholdtsen

Processed: reassign 833698 to calendar-google-provider

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 833698 calendar-google-provider
Bug #833698 [icedove] icedove: SIGSEGV, Segmentation fault in 
js::jit::HandleExceptionIon
Bug reassigned from package 'icedove' to 'calendar-google-provider'.
No longer marked as found in versions icedove/1:45.2.0-2.
Ignoring request to alter fixed versions of bug #833698 to the same values 
previously set
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
833698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: forcibly merging 833698 833532

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 833698 833532
Bug #833698 [calendar-google-provider] icedove: SIGSEGV, Segmentation fault in 
js::jit::HandleExceptionIon
Bug #833635 [calendar-google-provider] calendar-google-provider causes crash of 
icedove
Severity set to 'grave' from 'serious'
Severity set to 'grave' from 'serious'
Severity set to 'grave' from 'serious'
Added tag(s) upstream.
Added tag(s) upstream.
Added tag(s) upstream.
Bug #833532 [calendar-google-provider] calendar-google-provider causes crash of 
icedove
Bug #833591 [calendar-google-provider] calendar-google-provider causes crash of 
icedove
Merged 833532 833591 833635 833698
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
833532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833532
833591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833591
833635: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833635
833698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: e17: diff for NMU version 0.17.6-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 806019 + pending
Bug #806019 [src:e17] e17: FTBFS when built with dpkg-buildpackage -A (No such 
file or directory)
Added tag(s) pending.

-- 
806019: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806019
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#806019: e17: diff for NMU version 0.17.6-1.1

[Mattia Rizzolo]

Control: tags 806019 + pending

Dear maintainer,

Ross Vandegrift has prepared an NMU for e17 (versioned as 0.17.6-1.1)
and I uploaded it to DELAYED/2.  See #833859.
Please feel free to tell me if I should delay it longer.

Regards.

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://mapreri.org : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
diffstat for e17-0.17.6 e17-0.17.6

 changelog |8 
 rules |2 +-
 2 files changed, 9 insertions(+), 1 deletion(-)

diff -Nru e17-0.17.6/debian/changelog e17-0.17.6/debian/changelog
--- e17-0.17.6/debian/changelog	2014-06-01 18:28:47.0 +
+++ e17-0.17.6/debian/changelog	2016-08-06 14:32:54.0 +
@@ -1,3 +1,11 @@
+e17 (0.17.6-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * debian/rules: override dh_fixperms only for arch-dependent packages.
+Thanks to Santiago Vila.  (Closes: #806019)
+
+ -- Ross Vandegrift   Sat, 06 Aug 2016 10:32:54 -0400
+
 e17 (0.17.6-1) unstable; urgency=medium
 
   * New upstream version
diff -Nru e17-0.17.6/debian/rules e17-0.17.6/debian/rules
--- e17-0.17.6/debian/rules	2014-06-01 18:28:47.0 +
+++ e17-0.17.6/debian/rules	2016-08-06 14:32:54.0 +
@@ -30,7 +30,7 @@
 	rm debian/tmp/usr/share/enlightenment/COPYING
 	dh_install
 
-override_dh_fixperms:
+override_dh_fixperms-arch:
 	dh_fixperms
 	chmod 4755 debian/e17/usr/lib/enlightenment/utils/enlightenment_sys
 	chmod 4755 debian/e17/usr/lib/enlightenment/modules/cpufreq/*/freqset


signature.asc
Description: PGP signature

Bug#833846: fflas-ffpack: don't generate optimised code based on the build machine

[Doug Torrance]

Control: tags -1 pending

On 08/09/2016 07:53 AM, Ximin Luo wrote:

Control: severity -1 serious

I was recommended by multiple people to bump the severity of this bug. Also to clarify that i386 
should have no optimisation flags, and not "-msse -msse2". My earlier comment was based 
on a misunderstanding of what "i386 doesn't have mmx" meant; sse and sse2 build on top of 
mmx.

X

Ximin Luo:

Package: fflas-ffpack
Version: 2.2.1-1
Severity: important

Dear Maintainer,

fflas-ffpack on amd64 was built with "-msse4.1 -mfma -mavx2" as can be seen
from the output of `pkg-config --cflags fflas-ffpack`. This unfortunately makes
it crash on amd64 machines that don't support these instructions, and we are
running into this issue whilst testing SageMath.

Please disable any build options that set optimisations based on autodetection
of the CPU features of the build machine.

It should be OK to hard-code "-mmmx -msse -msse2" for amd64 and "-msse -msse2"
for i386, according to wRAR on #debian-devel. This is somewhat based on
information from [1]. There might be other optimisations you can make, but I
haven't yet done the detailed research for that.

X

[1] https://lists.debian.org/debian-devel-announce/2016/05/msg1.html


Thanks for your report!  I had figured that there was an issue like 
this, as both the CI and reproducible build tasks have been failing.


I've disabled the use of these extensions and a new version is in git 
[1] awaiting sponsorship.


Doug

[1] 
https://anonscm.debian.org/cgit/debian-science/packages/fflas-ffpack.git/commit/?id=88c339f745dc54351d4c437eedd38a5b83dca993 

Processed: Re: Bug#833846: fflas-ffpack: don't generate optimised code based on the build machine

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #833846 [fflas-ffpack] fflas-ffpack: don't generate optimised code based on 
the build machine
Added tag(s) pending.

-- 
833846: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#833860: pexpect: accesses the internet during build

[Chris Lamb]

Source: pexpect
Version: 4.0.1-1
Severity: serious
Justification: Policy 4.9
User: la...@debian.org
Usertags: network-access

Dear Maintainer,

Whilst pexpect builds successfully on unstable/amd64, according to
Debian Policy 4.9 packages may not attempt network access during
a build.

  00:00:00.00 IP eac1635a20ce.60981 > 10.0.1.1.domain: 8906+ A? 
docs.python.org. (33)
  00:00:00.80 IP eac1635a20ce.60981 > 10.0.1.1.domain: 8118+ ? 
docs.python.org. (33)
  00:00:00.018270 IP 10.0.1.1.domain > eac1635a20ce.60981: 8906 3/0/0 CNAME 
python.map.fastly.net., CNAME prod.python.map.fastlylb.net., A 151.101.16.223 
(123)
  00:00:00.019536 IP 10.0.1.1.domain > eac1635a20ce.60981: 8118 3/0/0 CNAME 
python.map.fastly.net., CNAME prod.python.map.fastlylb.net.,  
2a04:4e42:4::223 (135)
  00:00:00.019959 IP eac1635a20ce.39208 > 151.101.16.223.http: Flags [S], seq 
3032797174, win 29200, options [mss 1460,sackOK,TS val 37297863 ecr 
0,nop,wscale 7], length 0
  00:00:00.028309 IP 151.101.16.223.http > eac1635a20ce.39208: Flags [S.], seq 
1707382839, ack 3032797175, win 28120, options [mss 1400,sackOK,TS val 
1890388879 ecr 37297863,nop,wscale 9], length 0
  00:00:00.028346 IP eac1635a20ce.39208 > 151.101.16.223.http: Flags [.], ack 
1, win 229, options [nop,nop,TS val 37297865 ecr 1890388879], length 0
  00:00:00.028424 IP eac1635a20ce.39208 > 151.101.16.223.http: Flags [P.], seq 
1:132, ack 1, win 229, options [nop,nop,TS val 37297865 ecr 1890388879], length 
131: HTTP: GET /3/objects.inv HTTP/1.1
  00:00:00.037583 IP 151.101.16.223.http > eac1635a20ce.39208: Flags [.], ack 
132, win 58, options [nop,nop,TS val 189031 ecr 37297865], length 0
  00:00:00.037840 IP 151.101.16.223.http > eac1635a20ce.39208: Flags [P.], seq 
1:295, ack 132, win 58, options [nop,nop,TS val 189031 ecr 37297865], 
length 294: HTTP: HTTP/1.1 301 Moved Permanently

  [..]

This appears to be caused by (at least) Sphinx's intersphinx mapping extension.
Please see #830186 for more information, including suggestions on how to fix it.

The full build log (including tcpdump output) is attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-


pexpect.4.0.1-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#806102: marked as done (qt-gstreamer: FTBFS when built with dpkg-buildpackage -A (No such file or directory))

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2016 13:04:30 +
with message-id 
and subject line Bug#806102: fixed in qt-gstreamer 1.2.0-4
has caused the Debian Bug report #806102,
regarding qt-gstreamer: FTBFS when built with dpkg-buildpackage -A (No such 
file or directory)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
806102: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806102
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:qt-gstreamer
Version: 1.2.0-3
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 fakeroot debian/rules binary-indep
dh binary-indep --parallel --with=pkgkde-symbolshelper
   dh_testroot -i -O--parallel
   dh_prep -i -O--parallel
   debian/rules override_dh_auto_install
make[1]: Entering directory '/<>'
dh_auto_install --parallel
make -j1 install DESTDIR=/<>/debian/tmp 
AM_UPDATE_INFO_DIR=no
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -H/<> -B/<>/obj-x86_64-linux-gnu 
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start 
/<>/obj-x86_64-linux-gnu/CMakeFiles 
/<>/obj-x86_64-linux-gnu/CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
make -f src/QGlib/CMakeFiles/QtGLib_automoc.dir/build.make 
src/QGlib/CMakeFiles/QtGLib_automoc.dir/depend
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/src/QGlib 
/<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/src/QGlib 
/<>/obj-x86_64-linux-gnu/src/QGlib/CMakeFiles/QtGLib_automoc.dir/DependInfo.cmake
 --color=
Scanning dependencies of target QtGLib_automoc
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make -f src/QGlib/CMakeFiles/QtGLib_automoc.dir/build.make 
src/QGlib/CMakeFiles/QtGLib_automoc.dir/build
make[4]: Entering directory '/<>/obj-x86_64-linux-gnu'
[  1%] Automatic moc for target QtGLib
cd /<>/obj-x86_64-linux-gnu/src/QGlib && /usr/bin/cmake -E 
cmake_autogen 
/<>/obj-x86_64-linux-gnu/src/QGlib/CMakeFiles/QtGLib_automoc.dir/ 
RelWithDebInfo

[... snipped ...]

-- Installing: 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QtGStreamer/libQtGStreamerQuick2.so
-- Removed runtime path from 
"/<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QtGStreamer/libQtGStreamerQuick2.so"
-- Installing: 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QtGStreamer/qmldir
-- Installing: 
/<>/debian/tmp/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstqt5videosink.so
make[2]: Leaving directory '/<>/x86_64-linux-gnu-qt5'
cp -r obj-x86_64-linux-gnu/doc debian/tmp/doc
cp: cannot stat 'obj-x86_64-linux-gnu/doc': No such file or directory
debian/rules:38: recipe for target 'override_dh_auto_install' failed
make[1]: *** [override_dh_auto_install] Error 1
make[1]: Leaving directory '/<>'
debian/rules:56: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one, but I can give some general hints:

* If all the arch-independent packages are dummy transitional packages
released with jessie, the easy fix is to drop them now.
 
* If not, debian/rules should be modified so that the binary-indep
target works in all cases, even when binary-arch is not used (this is
what the "Architecture: all" autobuilder does). For that:

* If you are using debhelper, you might want to use options -a and -i
for dh_* commands so that they do not act on packages they do not
have to act.

* Also, if you are using dh, the (independently) optional targets
override_dh_foo-arch and override_dh_foo-indep (for several values
of "foo") may be useful to write a debian/rules which behaves exactly
as desired.


After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B"
work properly, this package will be suitable to be uploaded in
source-only form if you wish (you might want to try it).

Thanks.
--- End Message ---
--- Begin Message ---
Source: qt-gstreamer
Source-Version: 1.2.0-4

We believe that the bug you reported is fixed in the latest version of
qt-gstreamer, which is due to be installed in 

Bug#833805: picon-domains: FTBFS when built with dpkg-buildpackage -A (binary build with no binary artifacts)

[Hakan Ardo]

Thanx for the repport and fix. I'll apply it shortely...

On Mon, Aug 8, 2016 at 11:21 PM, Santiago Vila  wrote:

> Hi.
>
> While we are at it: You might want to modernize debian/rules a little
> bit. In particular, targets build-arch and build-indep are now
> mandatory too (so it's likely that just swapping binary-arch and
> binary-indep might not be enough).
>
> But debhelper (or dh) takes care of this if you let it to care.
>
> For example, after creating debian/compat with "9" as the contents,
> the attached debian/rules would possibly work for picon-domains, and I
> guess that maybe for all the other packages as well without changing a
> single line.
>
> Thanks.




-- 
Håkan Ardö

Bug#833532: Rebuild against libicu57 causes icedove to crash

[Martin Lutz]

On Tue, 09 Aug 2016 09:14:00 + =?UTF-8?B?VmlrdG9yIErDpGdlcnNrw7xwcGVy?=
  wrote:

In case anyone is not able to use a version prior to 1:45.2.0-2+b1, and
since this version is in testing now, I tried a workaround and set
"javascript.options.baselinejit" to "false" in about:config. This worked
for me so far.




This workaround solves my problems as well. Iceowl-extension works fine. 
calendar-google-provider is not installed.

Bug#831106: marked as done (meep-mpich2: FTBFS with GCC 6: configure: error: could not find mpi library for --with-mpi)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2016 12:49:10 +
with message-id 
and subject line Bug#831106: fixed in meep-mpich2 1.3-4
has caused the Debian Bug report #831106,
regarding meep-mpich2: FTBFS with GCC 6: configure: error: could not find mpi 
library for --with-mpi
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.)


-- 
831106: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: meep-mpich2
Version: 1.3-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> checking for style of include used by make... GNU
> checking dependency style of x86_64-linux-gnu-g++... none
> checking for mpic++... mpic++
> checking for MPI_Init... yes
> checking for mpi.h... no
> configure: error: could not find mpi library for --with-mpi
>   "tail -v -n +0 config.log"

The full build log is available from:
   
http://people.debian.org/~lucas/logs/2016/07/13/meep-mpich2_1.3-3_unstable_gcc6.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: meep-mpich2
Source-Version: 1.3-4

We believe that the bug you reported is fixed in the latest version of
meep-mpich2, 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 831...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated meep-mpich2 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, 09 Aug 2016 14:10:00 +0200
Source: meep-mpich2
Binary: meep-mpich2 libmeep-mpich2-8 libmeep-mpich2-dev
Architecture: source amd64
Version: 1.3-4
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 libmeep-mpich2-8 - library for using parallel (OpenMPI) version of meep
 libmeep-mpich2-dev - development library for using parallel (OpenMPI) version 
of meep
 meep-mpich2 - software package for FDTD simulation, parallel (OpenMPI) version
Closes: 831106
Changes:
 meep-mpich2 (1.3-4) unstable; urgency=medium
 .
   * rebuild with gcc-6 (Closes: #831106)
   * debian/control: bump standard to 3.9.8, no changes
Checksums-Sha1:
 2671d26ed73b68775c8490a82d77f9dfb4811d78 2226 meep-mpich2_1.3-4.dsc
 68cf7b009d33f93de5684e9742f5bc1161f61310 740890 meep-mpich2_1.3.orig.tar.gz
 27e435374f73cb4b49418568fead7b1b96c22894 5668 meep-mpich2_1.3-4.debian.tar.xz
 f5451619adf537edb8252f12b6fae9da9ba2b723 1274408 
libmeep-mpich2-8-dbgsym_1.3-4_amd64.deb
 976659400189ef20bd5e4a616317004c92ba0262 256388 
libmeep-mpich2-8_1.3-4_amd64.deb
 224b23f1ac41b5645e0dae75b223f4d276fce6db 272442 
libmeep-mpich2-dev_1.3-4_amd64.deb
 02bc5cfd850879efde07376e6fd95ceed4afa38d 778610 
meep-mpich2-dbgsym_1.3-4_amd64.deb
 332bd3db187f38b1a706ab42814bf76cd4d57979 173412 meep-mpich2_1.3-4_amd64.deb
Checksums-Sha256:
 234c1a24026daf1a3c17b6c5d5765ecfa199a9fa755dbecacdd17eaf481e0591 2226 
meep-mpich2_1.3-4.dsc
 564c1ff1b413a3487cf81048a45deabfdac4243a1a37ce743f4fcf0c055fd438 740890 
meep-mpich2_1.3.orig.tar.gz
 ee796a49a5402dc8fe0ff666e3ecfa6eb7229f2a21f959aa55d50dc0d8716340 5668 
meep-mpich2_1.3-4.debian.tar.xz
 1a2cdb721641a06ea94dc86b8fc00a9416d98e36bb428b326a27a2d626c4e6d4 1274408 
libmeep-mpich2-8-dbgsym_1.3-4_amd64.deb
 63e61df1c74a4f7dd556a51c72d18f25bc2a60f38b4c143b309a225de66600bd 256388 

Bug#833636: Re%3A compile error with gcc-6

[Thorsten Alteholz]

On Mon, 8 Aug 2016, Steve M. Robbins wrote:


Help me reproduce the problem.  I can't find "alljoyn" sources:


Oh, sorry, the three packages are
  alljoyn-core-1504
  alljoyn-core-1509
  alljoyn-core-1604

In the last upload I deactivated the testsuite, so if you want to build it 
with gtest you need to uncomment all lines with "XXX deactivate tests for 
now:".


  Thorsten

Processed (with 1 error): forcibly merging 833698 833532

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 833698 833532
Bug #833698 [icedove] icedove: SIGSEGV, Segmentation fault in 
js::jit::HandleExceptionIon
Unable to merge bugs because:
package of #833532 is 'calendar-google-provider' not 'icedove'
package of #833635 is 'calendar-google-provider' not 'icedove'
package of #833591 is 'calendar-google-provider' not 'icedove'
Failed to forcibly merge 833698: Did not alter merged bugs.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
833532: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833532
833591: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833591
833635: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833635
833698: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#833698: Icedove 45.2.0-2+b1 (Debian Testing) SegFault

[Michael F. Herbst]

Hi everyone

I can also reproduce this bug when starting icedove with a fresh profile
and all plugins disabled.

If I open the config editor and click away the "be careful" warning, I
get a SIGSEGV with this backtrace:

--
Thread 1 "icedove" received signal SIGSEGV, Segmentation fault.
0x73e007a1 in js::jit::SnapshotIterator::numAllocations
(this=0x7fff8cc0) at ./mozilla/js/src/jit/JitFrames.cpp:2159
2159./mozilla/js/src/jit/JitFrames.cpp: Datei oder Verzeichnis nicht
gefunden.
(gdb) bt
#0  0x73e007a1 in js::jit::SnapshotIterator::numAllocations
(this=0x7fff8cc0) at ./mozilla/js/src/jit/JitFrames.cpp:2159
#1  js::jit::IonFrameStackDepthOp::IonFrameStackDepthOp (frame=...,
this=) at ./mozilla/js/src/jit/JitFrames.cpp:421
#2  js::jit::TryNoteIterIon::TryNoteIterIon (frame=...,
cx=0x7fffc3aed800, this=0x7fff8c80) at
./mozilla/js/src/jit/JitFrames.cpp:431
#3  js::jit::HandleExceptionIon (overrecursed=0x7fff8b6f,
rfe=0x7fff9120, frame=..., cx=0x7fffc3aed800)
at ./mozilla/js/src/jit/JitFrames.cpp:478
#4  js::jit::HandleException (rfe=0x7fff9120) at
./mozilla/js/src/jit/JitFrames.cpp:853
--

Best
Michael

Processed: severity of 833846 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 833846 serious
Bug #833846 [fflas-ffpack] fflas-ffpack: don't generate optimised code based on 
the build machine
Ignoring request to change severity of Bug 833846 to the same value.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
833846: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833846
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#831078: supercollider-sc3-plugins: FTBFS with GCC 6: DWG.hpp:1271:53: error: no matching function for call to 'min(float, double)'

[Petter Reinholdtsen]

Control: tags -1 + patch

[Lucas Nussbaum]
>> /"PKGBUILDDIR"/source/DWGUGens/dwglib/DWG.hpp: In member function 'void 
>> TUBE::set_area(float, float)':
>> /"PKGBUILDDIR"/source/DWGUGens/dwglib/DWG.hpp:1271:53: error: no matching 
>> function for call to 'min(float, double)'
>>  loss = 1.0 - std::min(lossF/sqrt(a1),1.0);
>>  ^

I had a look by compiling with -E and checked out the preprosessed sour code.
The problem is that a C++ version of sqrt() from  is used, which return
float and not double as a1 is float.  This causes the expression lossF/sqrt(a1)
to be float.  The end result is that the compiler try to locate min(float, 
double)
as 1.0 is double not float.  I'm not quite sure why the compiler do not promote
the float to a double, but a simple fix for this issue is to ask the compiler
to assume 1.0 is a float like this:

diff --git a/source/DWGUGens/dwglib/DWG.hpp b/source/DWGUGens/dwglib/DWG.hpp
index 85ed86c..b6df5b7 100644
--- a/source/DWGUGens/dwglib/DWG.hpp
+++ b/source/DWGUGens/dwglib/DWG.hpp
@@ -1268,7 +1268,7 @@ class TUBE{
 if(a1 < 1e-18)
 loss = 0.0;
 else
-loss = 1.0 - std::min(lossF/sqrt(a1),1.0);
+loss = 1.0 - std::min(lossF/sqrt(a1),1.0f);
 
 }
 void go(){

I'm not sure if the code used to operate on doubles or floats earlier, nor what
the author intended.  If it is important that the calculation is done using
doubles, I guess this approach is better:

diff --git a/source/DWGUGens/dwglib/DWG.hpp b/source/DWGUGens/dwglib/DWG.hpp
index 85ed86c..282b2da 100644
--- a/source/DWGUGens/dwglib/DWG.hpp
+++ b/source/DWGUGens/dwglib/DWG.hpp
@@ -1268,7 +1268,7 @@ class TUBE{
 if(a1 < 1e-18)
 loss = 0.0;
 else
-loss = 1.0 - std::min(lossF/sqrt(a1),1.0);
+loss = 1.0 - std::min(lossF/sqrt(static_cast(a1)),1.0);
 
 }
 void go(){

It make sure sqrt(a1) is operating on a double, and the compiler take care of 
the
converting the rest of the variables to double.  I suspect the 1.0f approach
is better, as the loss variable is a float, so any increased accuracy is lost
when the result is assigned anyway.  But I do not really know what the code
try to do, as I did not try to understand the context of the calculations.

-- 
Happy hacking
Petter Reinholdtsen

Processed: Re: supercollider-sc3-plugins: FTBFS with GCC 6: DWG.hpp:1271:53: error: no matching function for call to 'min(float, double)'

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #831078 [src:supercollider-sc3-plugins] supercollider-sc3-plugins: FTBFS 
with GCC 6: DWG.hpp:1271:53: error: no matching function for call to 
'min(float, double)'
Added tag(s) patch.

-- 
831078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831078
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#833698: Version: 1:45.2.0-2+b1 now in testing

[John Talbut]

Version: 1:45.2.0-2+b1 was uploaded to testing last night although it 
does not appear in the PTS.  It segfaults on start up, would this be due 
to this bug?


John

Bug#833829: libgcc-6-dev: Missing crtfastmath.o

[Matthias Klose]

Control: severity -1 important
Control: tags -1 + help

On 09.08.2016 09:12, Christian Marillat wrote:
> Package: libgcc-6-dev
> Version: 6.1.1-11
> Severity: grave
> 
> I'm unable to build a package because crtfastmath.o is missing from this
> package. Architecture is kfreebsd-i386. I don't see this bug on the
> kfreebsd-amd64
> 
> ,
> | cc -Wall -DPIC   -O2 -pipe -fno-tree-dominator-opts -fno-tree-pre 
> -ffast-math -DUSE_MMX -DUSE_SSE -DUSE_SSE2 -g -D_FILE_OFFSET_BITS=64 
> -D_LARGEFILE_SOURCE -fPIC -pthreadluma.c   -o luma
> | /usr/bin/ld: cannot find crtfastmath.o: No such file or directory
> `

https://buildd.debian.org/status/fetch.php?pkg=gcc-6=kfreebsd-i386=6.1.1-11=1470331624

looks like this is never built, and the install step succeeds despite it
complains about not finding this file.

Processed: Re: Bug#833829: libgcc-6-dev: Missing crtfastmath.o

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #833829 [libgcc-6-dev] libgcc-6-dev: Missing crtfastmath.o
Severity set to 'important' from 'grave'
> tags -1 + help
Bug #833829 [libgcc-6-dev] libgcc-6-dev: Missing crtfastmath.o
Added tag(s) help.

-- 
833829: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833829
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#831228: closed by Bart Martens <ba...@debian.org> (flashplugin-nonfree: update-flashplugin-nonfree references wrong version)

[Bart Martens]

On Tue, Aug 09, 2016 at 11:16:24AM +0200, Ingo wrote:
> An alternative solution is to apply the patch locally:
> 
> 1. get the patch from
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=831228;filename=flash.patch;msg=15
> 
> 2. Copy it into the directory /var/cache/flashplugin-nonfree/
> 
> 3. change to that directory and apply the patch by executing:
> "patch get-upstream-version.pl flash.patch"

I advise against that because removing get-upstream-version.pl from
/var/cache/flashplugin-nonfree/ is much easier for normal end users and ensures
that the latest get-upstream-version.pl will be used.

Regards,

Bart Martens

Bug#833532: Rebuild against libicu57 causes icedove to crash

[Viktor Jägersküpper]

In case anyone is not able to use a version prior to 1:45.2.0-2+b1, and
since this version is in testing now, I tried a workaround and set
"javascript.options.baselinejit" to "false" in about:config. This worked
for me so far.

Bug#831228: closed by Bart Martens <ba...@debian.org> (flashplugin-nonfree: update-flashplugin-nonfree references wrong version)

[Ingo]

An alternative solution is to apply the patch locally:

1. get the patch from
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=831228;filename=flash.patch;msg=15

2. Copy it into the directory /var/cache/flashplugin-nonfree/

3. change to that directory and apply the patch by executing:
"patch get-upstream-version.pl flash.patch"

Bug#833625: kmail crash at start

[Maximiliano Curia]

¡Hola Samuele!

El 2016-08-09 a las 09:25 +0200, Samuele Battarra escribió:
Package: kmail 
Version: 4:16.04.3-1 
Followup-For: Bug #833625


Have you closed your plasma session after upgrading kmail and akonadi? 

I have rebooted my pc, kmail still crashes.


please install the additional dbgsym packages ... 
Installed kmail-dbgsym, other packages? 
Where i can find logs? 
You can send me privately info how to get debug logs?


I was expecting kcrash to catch a kmail crash and show a window with the 
backtrace information, if that's not the case, then running kmail under gdb 
should give something similar:


$ gdb kmail
[ ... ]
(gdb) r
[ ... Wait for the crash ... ]
(gdb) thread apply all backtrace

This is better explained in: 
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports


Happy hacking,
--
Se necesitan voluntarios para dominar el mundo.
Saludos /\/\ /\ >< `/


signature.asc
Description: Digital signature

Bug#826366: marked as done (network-manager: does not remove resolv.conf symlink on package removal)

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2016 07:48:38 +
with message-id 
and subject line Bug#826366: fixed in network-manager 1.2.4-1
has caused the Debian Bug report #826366,
regarding network-manager: does not remove resolv.conf symlink on package 
removal
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.)


-- 
826366: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: network-manager
Version: 1.2.2-2
Severity: serious
Justification: makes alternative network managers fail

I have been having some problems with network-manager recently (as
reported in another bug report), so I thought I'd try out wicd
instead.  I purged NM and the related packages, but wicd would not
work.  I tracked down the reason: /etc/resolv.conf was still symlinked
to the now non-existent file /var/run/NetworkManager/resolv.conf

So when network-manager shuts down, it should revert /etc/resolv.conf
to a regular file.  This should also be checked when the package is
removed (and unarguably when the package is purged).

Best wishes,

   Julian
--- End Message ---
--- Begin Message ---
Source: network-manager
Source-Version: 1.2.4-1

We believe that the bug you reported is fixed in the latest version of
network-manager, 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 826...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated network-manager package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 09 Aug 2016 09:13:34 +0200
Source: network-manager
Binary: network-manager network-manager-dev libnm-glib4 libnm-glib-dev 
libnm-glib-vpn1 libnm-glib-vpn-dev libnm-util2 libnm-util-dev libnm0 libnm-dev 
gir1.2-networkmanager-1.0
Architecture: source
Version: 1.2.4-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Michael Biebl 
Description:
 gir1.2-networkmanager-1.0 - GObject introspection data for NetworkManager
 libnm-dev  - GObject-based client library for NetworkManager (development file
 libnm-glib-dev - network management framework (GLib interface)
 libnm-glib-vpn-dev - network management framework (GLib interface)
 libnm-glib-vpn1 - network management framework (GLib VPN shared library)
 libnm-glib4 - network management framework (GLib shared library)
 libnm-util-dev - network management framework (development files)
 libnm-util2 - network management framework (shared library)
 libnm0 - GObject-based client library for NetworkManager
 network-manager - network management framework (daemon and userspace tools)
 network-manager-dev - network management framework (development files)
Closes: 826366
Changes:
 network-manager (1.2.4-1) unstable; urgency=medium
 .
   * New upstream release.
   * Rebase patches.
   * Update symbols file for libnm0.
   * Replace /etc/resolv.conf symlink with an empty file on package removal
 to signal other packages that NetworkManager is no longer controlling the
 file. (Closes: #826366)
   * Clear WiFi requested_scan if wpa_supplicant exits or goes inactive.
 Patches cherry-picked from upstream Git.
Checksums-Sha1:
 d55e8b677def5e1bcd67a8cd41ef6713e377cac0 3594 network-manager_1.2.4-1.dsc
 b57ba5dd1485aeecfe5808999f65fb51ac7eced2 3728788 
network-manager_1.2.4.orig.tar.xz
 19a19588bc2d4e4342e1f07bbc27b2292fe95181 45372 
network-manager_1.2.4-1.debian.tar.xz
Checksums-Sha256:
 a56ac680a30fa121d1104261539090748578b60fa2a76c661b353cbdb8c5d050 3594 
network-manager_1.2.4-1.dsc
 19bfb7306dd472d010443a8027d91f9fd50fe6e0c5aa4ea8083845de0fa38faa 3728788 
network-manager_1.2.4.orig.tar.xz
 f3481e2d6b4ffb9273469248bce6f75fa39c278d66c86488da8be6747bf36bbe 45372 
network-manager_1.2.4-1.debian.tar.xz
Files:
 6f2b3cc18a87c4c08406574ff05edc15 3594 net optional network-manager_1.2.4-1.dsc
 66064dfe29c37502a0a9350e5caa46d3 3728788 net optional 
network-manager_1.2.4.orig.tar.xz
 11a56785caa0cfbd72fcb51006bccd47 45372 net optional 

Bug#833829: libgcc-6-dev: Missing crtfastmath.o

[Christian Marillat]

Package: libgcc-6-dev
Version: 6.1.1-11
Severity: grave

Dear Maintainer,

I'm unable to build a package because crtfastmath.o is missing from this
package. Architecture is kfreebsd-i386. I don't see this bug on the
kfreebsd-amd64

,
| cc -Wall -DPIC   -O2 -pipe -fno-tree-dominator-opts -fno-tree-pre -ffast-math 
-DUSE_MMX -DUSE_SSE -DUSE_SSE2 -g -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE 
-fPIC -pthreadluma.c   -o luma
| /usr/bin/ld: cannot find crtfastmath.o: No such file or directory
`

Christian

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: kfreebsd-i386 (i386)

Kernel: kFreeBSD 10.3-0-686
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libgcc-6-dev depends on:
ii  gcc-6-base6.1.1-11
ii  libatomic16.1.1-11
ii  libgcc1   1:6.1.1-11
ii  libgomp1  6.1.1-11
ii  libquadmath0  6.1.1-11

Versions of packages libgcc-6-dev recommends:
ii  libc0.1-dev  2.23-4

libgcc-6-dev suggests no packages.

-- no debconf information

Bug#831442: mpich: Broken /usr/lib/libmpich.so.12 symlink, depending on installation order

[Thibaut Paumard]

Control: severity -1 normal

Dear all,

I have been able to work around this bug in yorick by adding a file
debian/shlibs.local in the source tree with this single line:

libmpich 12 libmpich12

Le 08/08/2016 12:12, Thibaut Paumard a écrit :
> Hi have open a new bug against libc-bin (ldconfig) to follow that up on
> that side: 833728

The libc-bin maintainers think that the proper fix would be to also
convert openmpi to multiarch and move the alternative main link also to
the multiarch directory.

I'm downgrading the severity since a workaround exists to avoid FTBFS.

Kind regards, Thibaut.

Bug#833828: Migrations of stable's python3-django-markupfield (1.2.1) do not work with stable's django version (1.7.x).

[Thomas Viehmann]

Package: python3-django-markupfield
Severity: serious
Version: 1.2.1-2+deb8u1

Hello,

database migrations generated when using markupfields with 
python3-django-markupfield 1.2.1 do not work with stable's django 
version 1.7.x.

  https://github.com/jamesturk/django-markupfield/issues/20

This makes python3-django-markupfield fairly useless on stable.

What I did was port django-markupfield jessie's 1.4 to the backports 
django version (a mere recompile will do). Of course, that leaves the 
broken package in stable.


Best regards

Thomas

Processed: Re: Bug#831442: mpich: Broken /usr/lib/libmpich.so.12 symlink, depending on installation order

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #831442 [src:mpich] mpich: Broken /usr/lib/libmpich.so.12 symlink, 
depending on installation order
Severity set to 'normal' from 'serious'

-- 
831442: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831442
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#831406: marked as done (yorick: FTBFS: dpkg-shlibdeps: error: no dependency information found for /usr/lib/libmpich.so.12 (used by debian/yorick-mpy-mpich2/usr/lib/yorick/bin/mpy.mpich2))

[Debian Bug Tracking System]

Your message dated Tue, 09 Aug 2016 06:33:57 +
with message-id 
and subject line Bug#831406: fixed in yorick 2.2.04+dfsg1-6
has caused the Debian Bug report #831406,
regarding yorick: FTBFS: dpkg-shlibdeps: error: no dependency information found 
for /usr/lib/libmpich.so.12 (used by 
debian/yorick-mpy-mpich2/usr/lib/yorick/bin/mpy.mpich2)
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.)


-- 
831406: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831406
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yorick
Version: 2.2.04+dfsg1-5
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

yorick fails to build from source in unstable/amd64:

  [..]

  "manual/yorick_prt.html"
  mkdir -p ../../build/doc/images
  cp -p images/*.* ../../build/doc//images/
  mkdir -p ../../build/doc/
  cp skull.css style.css ../../build/doc/
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160715182504.pdcokDfkyE.yorick/yorick-2.2.04+dfsg1/doc/html'
  cp doc/html/packinfo.txt build/00yorick.packinfo
  cp doc/html/keywords.txt build/00yorick.keywords
  cp doc/html/aliases.txt build/00yorick.aliases
  find build/doc/manual -name "*.html" -not -name yorick_prt.html | xargs sed 
-e 's|^http://dhmunro.github.io/yorick-doc/;>Web HomeGetting StartedManualPackagesQuick 
Reference|' -e 's||&|' -i
  sed 's|yorick_1.html|index.html|' -i build/doc/*.html build/doc/*/*.html
  touch build-indep-stamp
   fakeroot debian/rules binary
  dh_testdir
  xvfb-run relocate/bin/yorick -batch testfull.i
   Begin Yorick parser test...
   Test 17x10x10 binary operators...
   Test unary operators...
   Test array manipulation functions...
   Test struct instancing and indexing...
   Test range functions...
   Test math functions...
   Test informational functions...
   Test func declarations...
   Test binary I/O functions...
   Test binary I/O to netCDF...
   Test ASCII I/O functions...
   Test string manipulation functions...
   Test list functions...
   Test catch function...
  End of Yorick parser test, 0 goofs
   begin string manipulation test...
  end string manipulation test, 0 goofs
   PASSED oxy test1
   PASSED oxy test2
   PASSED oxy test3
   PASSED closure called with no arguments
   PASSED all closure tests
   PASSED alternate closure tests
   PASSED oxy friend test
   PASSED oxy sibling test
   
   Zeroth test is pdtest files:
   Testing sun_primitives db1 write...
   Testing dec_primitives db1 write...
   Testing cray_primitives db1 write...
   Testing mac_primitives db1 write...
   Testing macl_primitives db1 write...
   Testing pc_primitives db1 write...
   Testing sun3_primitives db1 write...
   Testing vax_primitives db1 write...
   Testing vaxg_primitives db1 write...
   Testing xdr_primitives db1 write...
   Testing sun_primitives db1 write w/PDB-style pointers...
   Testing dec_primitives db1 write w/PDB-style pointers...
   Testing cray_primitives db1 write w/PDB-style pointers...
   Testing native db1 write...
   
 First test is to write flat files:
   Write using native formats
   Write using DEC primitive formats
   Write using Sun primitive formats
   Write using Cray primitive formats
   
Second test is to write files with pointers:
   Write using native formats
   Write using DEC primitive formats
   Write using Sun primitive formats
   Write using Cray primitive formats
   
Third test is to update pointered files with flat data:
   Update using native formats
   Update using DEC primitive formats
   Update using Sun primitive formats
   Update using Cray primitive formats
   
Fourth test is exhaustive check of other primitive formats:
   Testing Sun format
   Testing i86 format
   Testing alpha format
   Testing sgi64 format
   Testing DEC format
   Testing Cray format
   Testing XDR format
   Testing Mac format
   Testing Mac long-double format
   Testing IBM PC format
   Testing VAX format
   Testing VAX G-double format
   Testing Sun-3/Sun-2 format
   Testing native format
 Timing Category CPU sec  System secWall sec
  Time to write/test all formats   0.004   0.000   0.007
   
Fifth test is check of Contents Log machinery:
   Contents Log -- testing Sun format
   Contents Log -- testing DEC format
   Contents Log -- testing Cray format
   Contents Log -- testing VAX format
   Contents Log -- testing native format
   Non-PDB Contents Log -- testing Sun 

Bug#820583: flashplugin-nonfree: Signature status

[Bart Martens]

On Mon, Aug 08, 2016 at 04:54:32PM -0700, Elliott Mitchell wrote:
> Sorry to be the bearer of bad news, but:
> 
> $ wget 
> https://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp.22.0.0.209.sha512.amd64.pgp.asc
> --2016-08-08 16:48:41--  
> https://people.debian.org/~bartm/flashplugin-nonfree/D5C0FC14/fp.22.0.0.209.sha512.amd64.pgp.asc
> Resolving people.debian.org (people.debian.org)... 5.153.231.30, 
> 2001:41c8:1000:21::21:30
> Connecting to people.debian.org (people.debian.org)|5.153.231.30|:443... 
> connected.
> HTTP request sent, awaiting response... 404 Not Found
> 2016-08-08 16:48:41 ERROR 404: Not Found.

The newest version for Firefox is 11.2.202.632, not 22.0.0.209. So the behavior
you observed is normal.

If "update-flashplugin-nonfree --status" still selects 22.0.0.209, then you may
want to delete /var/cache/flashplugin-nonfree/get-upstream-version.pl and try
again. The package in unstable already deletes the old get-upstream-version.pl.
The package in stable not yet, and a new package is under review by the stable
release managers, so you may want to remove the old get-upstream-version.pl
manually for now, or install the package from unstable.

Regards,

Bart Martens