date:20160626

Bug#828682: pesign: broken command line parsing for most commands

2016-06-26 Thread Julien Cristau

Source: pesign
Version: 0.112-1
Severity: important
Tags: upstream patch fixed-upstream

Hi,

most commands shipped with pesign got their command line parsing broken
in February.  Fixed upstream with
https://github.com/rhinstaller/pesign/commit/5be0515dee24308fd7e270bf2e0fb5e5a7a78f32

Cheers,
Julien

Bug#828639: Pending fixes for bugs in the libmarpa-r2-perl package

2016-06-26 Thread pkg-perl-maintainers

tag 828639 + pending
thanks

Some bugs in the libmarpa-r2-perl package are closed in revision
18c52361a3d4a1da639626b8a0eec48fb4131311 in branch 'master' by
intrigeri

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libmarpa-r2-perl.git/commit/?id=18c5236

Commit message:

Honour SOURCE_DATE_EPOCH for embedded timestamp, if it is set, for build 
reproducibility. Thanks to Reiner Herrmann  for the patch! 
(Closes: #828639)

Bug#827746: mirror submission for mirrors.xjtu.edu.cn

2016-06-26 Thread Donald Norwood

control: tag -1 +moreinfo

Hello,

Thank you for your support and for mirroring Debian.

Your submission looks good, please change your update frequency to 4
times per 24 hours, rather than 2.

Please respond to this email when this change has been made and we will
add you to the official listing.

Best regards,

Donald Norwood
-Debian Mirrors Team


On Mon, 20 Jun 2016 12:47:28 + "Tiaozhan Operation Team"
 wrote:
> Package: mirrors
> Severity: wishlist
> User: mirr...@packages.debian.org
> Usertags: mirror-submission
> 
> Submission-Type: new
> Site: mirrors.xjtu.edu.cn
> Aliases: mirrors.tiaozhan.com
> Type: leaf
> Archive-architecture: amd64 i386 
> Archive-http: /debian/
> CDImage-http: /debian-cd/
> IPv6: no
> Archive-upstream: mirrors.tuna.tsinghua.edu.cn
> CDImage-upstream: mirrors.tuna.tsinghua.edu.cn
> Updates: twice
> Maintainer: Tiaozhan Operation Team 
> Country: CN China
> Location: Xi'an Jiaotong University
> Sponsor: Xingchi Zhu https://www.tiaozhan.com/
> 
> 



signature.asc
Description: OpenPGP digital signature

Bug#828681: keyutils: please make the build reproducible

2016-06-26 Thread Reiner Herrmann

Source: keyutils
Version: 1.5.9-9
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi!

While working on the "reproducible builds" effort [1], we have noticed
that keyutils could not be built reproducibly.
In the last upload support for SOURCE_DATE_EPOCH was added, but it is
still evaluated timezone-dependent.

The attached patch fixes this reading SOURCE_DATE_EPOCH in UTC.

Regards,
 Reiner

[1]: https://wiki.debian.org/ReproducibleBuilds
diff --git a/debian/rules b/debian/rules
index 272feb5..27bba4a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,7 +1,7 @@
 #!/usr/bin/make -f
 
 # $SOURCE_DATE_EPOCH is exported by debhelper
-CHANGEDATE = $(shell date -d @$(SOURCE_DATE_EPOCH) +%F)
+CHANGEDATE = $(shell date -u -d @$(SOURCE_DATE_EPOCH) +%F)
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+all

Bug#828046: ess: taking a huge time to load in emacs

2016-06-26 Thread Julian Gilbey

On Sun, Jun 26, 2016 at 07:56:51AM -0500, Dirk Eddelbuettel wrote:
> I can't really help you. I don't program elisp. I can forward this for you
> (you know how it goes) but I honestly think we should close this here and you
> refile at
> 
>https://github.com/emacs-ess/ESS/issues
> 
> I lurk there as they gave me write access just for the debian/ directory.
> I honestly cannot see any other solution than patient triaging,
> (un)installing one package at a time.  Maybe starting in an empty Debian
> testing Docker container?

That's so weird.  I tried in an empty sid Docker container, and I just
can't reproduce this behaviour.

So there must be some weird package interaction somewhere.

I don't have the time to track it down completely, so let's close this
bug.

Thanks for your help, and sorry for the time spent.

Best wishes,

   Julian

Bug#778911: vlc: Please make N Curses interface configurable

2016-06-26 Thread Sebastian Ramacher

Control: tags -1 upstream

Hi Axel

On 2015-02-21 18:40:03, Axel Stammler wrote:
> Package: vlc
> Version: 2.0.3-5+deb7u2+b1
> Severity: wishlist
> 
> Dear Maintainer,
> 
> VLC works well with this interface (sometimes I think it works better than 
> using a
> graphical interface), so I would suggest making this interface more versatile 
> and
> configurable:
> 
> - colours
> - which information is shown by default in each part of the screen
> - window title

Feature requests should be taken upstream: https://trac.videolan.org/vlc

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#824901: Updates on gpg2 segfault? -- gone in 2.1.13

2016-06-26 Thread Christoph Egger

Hi!
Christoph Egger  writes:
> Hi!
>
> FWIW I've just upgraded to .13 and gpg does not seem to segfault any
> more

Actually not really.

I can now do most things but

| $ gpg --check-trustdb
| 
| gpg: signal Segmentation fault caught ... exiting
| zsh: segmentation fault  gpg --check-trustdb

  Christoph

Bug#828680: debiandoc-sgml-doc-pt-br: please make the build reproducible

2016-06-26 Thread Dhole

Source: debiandoc-sgml-doc-pt-br 
Version: 1.1.12+nm 
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: locale
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi,

While working on the "reproducible builds" effort [1], we have noticed that
debiandoc-sgml-doc-pt-br could not be built reproducibly.

When generating the documentation files, a timestamp of the current month and
year is embedded.

The attached patch fixes this by setting the timestamp to a reproducible value.
Once applied, debiandoc-sgml-doc-pt-br can be built reproducibly in our current
experimental framework.

 [1]: https://wiki.debian.org/ReproducibleBuilds

Regards,

-- 
Dhole
diff -Nru debiandoc-sgml-doc-pt-br-1.1.12/debian/changelog 
debiandoc-sgml-doc-pt-br-1.1.12+nmu1/debian/changelog
--- debiandoc-sgml-doc-pt-br-1.1.12/debian/changelog2016-02-03 
12:48:25.0 +0100
+++ debiandoc-sgml-doc-pt-br-1.1.12+nmu1/debian/changelog   2016-06-25 
20:47:02.0 +0200
@@ -1,3 +1,10 @@
+debiandoc-sgml-doc-pt-br (1.1.12+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Replace debiandoc timestamp by SOURCE_DATE_EPOCH.
+
+ -- Eduard Sanou   Sat, 25 Jun 2016 20:46:48 +0200
+
 debiandoc-sgml-doc-pt-br (1.1.12) unstable; urgency=medium
 
   * Use onsgml for the migration from sp to opensp. Closes: #812188
diff -Nru debiandoc-sgml-doc-pt-br-1.1.12/debian/rules 
debiandoc-sgml-doc-pt-br-1.1.12+nmu1/debian/rules
--- debiandoc-sgml-doc-pt-br-1.1.12/debian/rules2016-02-02 
10:21:32.0 +0100
+++ debiandoc-sgml-doc-pt-br-1.1.12+nmu1/debian/rules   2016-06-26 
00:15:08.0 +0200
@@ -7,6 +7,10 @@
 ## uncomment this to turn on verbose mode
 #export DH_VERBOSE=1
 
+ifdef SOURCE_DATE_EPOCH
+   export DEBIANDOC_DATE ?= $(shell LC_ALL=pt_BR date -u -d 
"@$(SOURCE_DATE_EPOCH)" +"%d %B %Y")
+endif
+
 ## --
 ## Targets
 


signature.asc
Description: PGP signature

Bug#824901: Updates on gpg2 segfault? -- gone in 2.1.13

2016-06-26 Thread Christoph Egger

Hi!

Christoph Egger  writes:
> Actually not really.
>
> I can now do most things but
>
> | $ gpg --check-trustdb
> | 
> | gpg: signal Segmentation fault caught ... exiting
> | zsh: segmentation fault  gpg --check-trustdb

Ignore me, didn't update *all* systems from .12 to .13

  Christoph

Bug#828679: llgal: Typo in man llgalrc

2016-06-26 Thread Baptiste Jammet

Package: llgal
Version: 0.13.17-2
Severity: minor
Tags: patch

Dear Maintainer,

There is a small typo in man llgalrc that bugged me before I understand it:
The "make_caption_from_image_comment" is written twice, 
the second one instead of "make_caption_from image_timestamp".

Patch attached for clarity !

Thanks for maintaining llgal.
Baptiste

-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages llgal depends on:
ii  imagemagick 8:6.8.9.9-5+deb8u3
ii  libimage-size-perl  3.232-1
ii  liblocale-gettext-perl  1.05-8+b1
ii  liburi-perl 1.64-1
ii  perl5.20.2-3+deb8u5

Versions of packages llgal recommends:
ii  libimage-exiftool-perl  9.74-1

llgal suggests no packages.

-- no debconf information
--- llgalrc.5.orig	2011-08-02 12:42:20.0 +0200
+++ llgal-0.13.17/llgalrc.5	2016-06-26 12:58:39.583244178 +0200
@@ -435,15 +435,15 @@
 .I make_caption_from_image_comment = ",-separated strings of +-separated strings"
 .RS
 Generate captions from image comment tag
 .RB [ --cc ].
 Default is \fB""\fR
 .RB ( disabled ).
 .RE
-.I make_caption_from_image_comment = <0/1>
+.I make_caption_from_image_timestamp = <0/1>
 .RS
 Add image timestamp to generated captions
 .RB [ --ct ].
 Default is
 .BR 0 " (" disabled ).
 .RE
 .I show_dimensions = <0/1>

Bug#827686: pink-pony: port to glfw3

2016-06-26 Thread James Cowgill

Control: tags -1 pending

On Sun, 2016-06-19 at 17:33 +0100, James Cowgill wrote:
> Source: pink-pony
> Version: 1.4.1-1
> Severity: wishlist
> Tags: sid stretch patch
> 
> Hi,
> 
> At some point I would like to remove the old version of glfw which is
> no longer maintained upstream. The last release was in 2013.
> 
> To do this I've ported pink-pony to glfw3. Most of the porting was
> straightforward although I had to make some large changes to pass the
> new GLFWwindow pointer to the various classes and ensure the keycodes
> from the old config file work with GLFW3.

I'm going to upload this now. I found a small regression in my patch
where the game used the incorrect video mode on the first run. If any
more are found I'll happily take a look at them.

The revised glfw3.patch which will be uploaded is attached.

Thanks,
JamesDescription: Port to GLFW 3
 The most significant changes here are:
 - Having to pass a GLFWwindow* around to various classes.
 - The key_to_glfw3 function which is needed to allow key ids from old config
   files to work with GLFW 3.
Author: James Cowgill 
---
This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
--- a/external/flextGL/flextGL.c
+++ b/external/flextGL/flextGL.c
@@ -2,7 +2,7 @@
 /* Do not edit. */
 
 #include "flextGL.h"
-#include "GL/glfw.h"
+#include "GLFW/glfw3.h"
 
 #include 
 
@@ -14,11 +14,11 @@ extern "C" {
 
 void flextLoadOpenGLFunctions(void);
 
-int flextInit(void)
+int flextInit(GLFWwindow* window)
 {
   
-int major = glfwGetWindowParam(GLFW_OPENGL_VERSION_MAJOR);
-int minor = glfwGetWindowParam(GLFW_OPENGL_VERSION_MINOR);
+int major = glfwGetWindowAttrib(window, GLFW_CONTEXT_VERSION_MAJOR);
+int minor = glfwGetWindowAttrib(window, GLFW_CONTEXT_VERSION_MINOR);
 
 flextLoadOpenGLFunctions();
 
--- a/external/flextGL/flextGL.h
+++ b/external/flextGL/flextGL.h
@@ -6677,7 +6677,10 @@ extern int FLEXT_ARB_geometry_shader4;
 extern int FLEXT_EXT_transform_feedback;
 extern int FLEXT_EXT_texture_filter_anisotropic;
 
-int flextInit(void);
+struct GLFWwindow;
+typedef struct GLFWwindow GLFWwindow;
+
+int flextInit(GLFWwindow* window);
 
 #define FLEXT_MAJOR_VERSION 2
 #define FLEXT_MINOR_VERSION 0
--- a/src/Config.cc
+++ b/src/Config.cc
@@ -4,7 +4,7 @@
 Config::Config()
 : width(800),
   height(600),
-  window_mode(GLFW_FULLSCREEN),
+  window_fullscreen(true),
   fsaa_samples(4),
   swap_interval(1),
   polygon_mode(GL_FILL),
@@ -108,7 +108,7 @@ void Config::set_value(string name, stri
 
 int ival = 0;
 float fval = 0.0f;
-int winmodeval = GLFW_WINDOW;
+bool winmodeval = false;
 GLenum polymodeval = GL_FILL;
 string sval = "";
 V2f vec2val;
@@ -153,9 +153,9 @@ void Config::set_value(string name, stri
 
 if (value.find("window") != string::npos &&
 value.find("window") < value.find(';')) {
-winmodeval = GLFW_WINDOW;
+winmodeval = false;
 } else {
-winmodeval = GLFW_FULLSCREEN;
+winmodeval = true;
 }
 
 if (value.find("fill") != string::npos &&
@@ -177,7 +177,7 @@ void Config::set_value(string name, stri
 
 if (name == "width") width = ival;
 else if (name == "height") height = ival;
-else if (name == "window_mode") window_mode = winmodeval;
+else if (name == "window_mode") window_fullscreen = winmodeval;
 else if (name == "fsaa_samples") fsaa_samples = ival;
 else if (name == "swap_interval") swap_interval = ival;
 else if (name == "polygon_mode") polygon_mode = polymodeval;
@@ -321,7 +321,7 @@ bool Config::write_file(string filename)
 os << "height = " << height << ";" << endl;
 os << "swap_interval = " << swap_interval <<  ";" << endl;
 os << "window_mode = ";
-if (window_mode == GLFW_WINDOW)
+if (!window_fullscreen)
 os << "window;" << endl;
 else
 os << "fullscreen;" << endl;
--- a/src/Config.hh
+++ b/src/Config.hh
@@ -10,7 +10,7 @@ class Config
 
 // Window properties:
 int width, height;
-int window_mode;
+bool window_fullscreen;
 int fsaa_samples;
 int swap_interval;
 GLenum polygon_mode;
--- a/src/Menu.cc
+++ b/src/Menu.cc
@@ -7,21 +7,21 @@
 
 Menu* Menu::callback_menu = NULL;
 
-void GLFWCALL menu_mouse_callback(int button, int action)
+void menu_mouse_callback(GLFWwindow* window, int button, int action, int mods)
 {
 if (Menu::callback_menu != NULL)
 Menu::callback_menu->mouse_callback(button, action);
 }
 
-void GLFWCALL menu_resize_callback(int width, int height)
+void menu_resize_callback(GLFWwindow* window, int width, int height)
 {
 if (Menu::callback_menu != NULL)
 Menu::callback_menu->resize_callback(width, height);
 }
 
-void GLFWCALL menu_key_callback(int key, int state)
+void menu_key_callback(GLFWwindow* window, int key, int scancode, int action, int mods)
 {
-if (state != GLFW_PRESS || Menu::callback_menu == NULL ) 
+if (action !=

Bug#811682: FTBFS with GCC 6: could not convert a from x to y

2016-06-26 Thread Gert Wollny

Are you sure?
> It fails to build from source in unstable.
> 
> View.cc: In member function 'SmartPtr View::getCharAt(const
> scaled&, const scaled&, CharIndex&, Point*, BoundingBox*) const':
> View.cc:294:10: error: 'nullptr' was not declared in this scope
>    return nullptr;

Arrg, "nullptr" is a c++11 construct, and since g++-5  defaults to
c++03, it doesn't compile like this.

Instead 

   return SmartPtr(); 

should work in both cases (if this SmartPtr template defines a sensible
default constructor). Otherwise "return NULL" should be the (ugly)
solution.

Best, 
Gert

Bug#828518:

2016-06-26 Thread Tristan Seligmann

Control: tag -1 + pending upstream

Upstream have OpenSSL 1.1.0 support nearly ready to go, basically just
waiting on the final 1.1.0 release to be out. See:

https://github.com/pyca/cryptography/milestones/1.1.0%20Support

Bug#828281: [Debian-med-packaging] Bug#828281: dcmtk: FTBFS with openssl 1.1.0

2016-06-26 Thread Gert Wollny

Control: tags -1 pending 

Thanks for reporting. An updated version fix this will be uploaded once
the current upstream release has passed the NEW pipeline. 

Best, 
Gert

Bug#826166: [Pkg-phototools-devel] Bug#826166: Bug#826166: libgphoto2-dev: location of gphoto2-config is not in PATH

2016-06-26 Thread Herbert Fortes

Hi,


Em Dom, 2016-06-26 às 10:23 -0500, Steve M. Robbins escreveu:
> Hi,
> 
> I'm the debian maintainer of digikam and just ran into the same problem.
> 
> On Thu, 2 Jun 2016 20:43:58 -0300 "Herbert Fortes (hpfn)"  
> wrote:
> 
> > > I recon these files should be in /usr/bin unless I am missing something?
> > > 
> > 
> > It is about lintian tag[0] 'old-style-config-script'.
> > 
> > [0] - https://lintian.debian.org/tags/old-style-config-script.html
> 
> That link makes the following 3 suggestions.I think you're referring to 
> #3.  Please note that #3 begins with "after fixing every reverse depends 
> "; 
> as a reverse-depends maintainer, I'd have appreciated at least a note of this 
> compatibility break.  :-)
> 
> Has any work been done with respect to a pkg-config replacement (#1, #2)?
> 
> Thanks,
> -Steve
> 
> 1. You should consider to move to pkg-config file and warn your user to not 
> use 
> this script, and open a bug upstream.
> 
> 2. You should also consider to implement this file as a compatibility wrapper 
> over pkg-config.
> 
> 3. After fixing every reverse depends of your package and use pkg-config 
> reverse 
> depends makefile, you should consider to put this script, as a temporary 
> convenience of your users, under /usr/lib/$DEB_HOST_MULTIARCH/$PACKAGE/bin 
> where $DEB_HOST_MULTIARCH is the multi-arch triplet and $PACKAGE is the 
> package name. You should also consider to add a NEWS.Debian entry.
> 

I tried to stop packaging these scripts months 
ago. But maybe KDE team only was aware about
that. I am sorry. Digikam uses pkg-config and 
libgphoto2 has a .pc file for long time.

If you need the old-style-config-script and has to
use the old path, I can manage it for you. But please,
move to pkg-config.

I am waiting your response.



regards,
-- Herbert Parentes Fortes Neto (hpfn)

signature.asc
Description: This is a digitally signed message part

Bug#811682: FTBFS with GCC 6: could not convert a from x to y

2016-06-26 Thread Sylvestre Ledru

Le 26/06/2016 à 14:27, Gert Wollny a écrit :
> Control: tags -1 patch 
>
> Hello, 
>
> the attached patch fixes the reported compile error and also fixes the
> "narrowing conversion" errors that came up with g++-6.
>
> The package now builds with g++-6 (but it is not lintian-clean). 
>
> Best, 
> Gert 
Hello,

Are you sure?
It fails to build from source in unstable.

View.cc: In member function 'SmartPtr View::getCharAt(const
scaled&, const scaled&, CharIndex&, Point*, BoundingBox*) const':
View.cc:294:10: error: 'nullptr' was not declared in this scope
   return nullptr;

Thanks

S

Bug#828633: mount in testing/unstable should conflict with old bash-completion

2016-06-26 Thread Sven Joachim

On 2016-06-26 18:42 +0200, Andreas Henriksson wrote:

> Control: tags -1 + pending
> Control: severity -1 serious
>
> Hello!
>
> Thanks for your bug report. I apparently forgot to bump the version
> of the already existing Breaks/Replaces statements in previous upload.
> Fixed in git, will be part of next upload.

The fix in git is wrong (at least not sufficient), though.  You bumped
the Breaks/Replaces combination in util-linux, but really it needs to be
changed in mount, removing the spurious tilde:

--8<---cut here---start->8---
diff --git a/debian/control b/debian/control
index cef4980..61f66ba 100644
--- a/debian/control
+++ b/debian/control
@@ -78,8 +78,8 @@ Section: admin
 Pre-Depends: ${misc:Pre-Depends}, ${shlibs:Depends}
 Depends: ${misc:Depends}
 Suggests: nfs-common (>=1:1.1.0-13)
-Breaks: bash-completion (<< 1:2.1-4.3~)
-Replaces: bash-completion (<< 1:2.1-4.3~)
+Breaks: bash-completion (<< 1:2.1-4.3)
+Replaces: bash-completion (<< 1:2.1-4.3)
 Multi-Arch: foreign
 Description: tools for mounting and manipulating filesystems
  This package provides the mount(8), umount(8), swapon(8),
--8<---cut here---end--->8---

Cheers,
   Sven

Bug#828457: nodejs: FTBFS with openssl 1.1.0

2016-06-26 Thread Jérémy Lal

2016-06-26 12:23 GMT+02:00 Kurt Roeckx :

> Source: nodejs
> Version: 4.4.3~dfsg-1
> Severity: important
> Control: block 827061 by -1
>
> Hi,
>
> OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
> OpenSSL this package fail to build.  A log of that build can be found at:
>
> https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/nodejs_4.4.3~dfsg-1_amd64-20160529-1457
>
> On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various
> of the
> reasons why it might fail.  There are also updated man pages at
> https://www.openssl.org/docs/manmaster/ that should contain useful
> information.
>
> There is a libssl-dev package available in experimental that contains a
> recent
> snapshot, I suggest you try building against that to see if everything
> works.
>
> If you have problems making things work, feel free to contact us.
>


I'm on it, and after a couple things i could solve, i need a "gentle push"
to continue solving these:

```
  g++ '-DNODE_ARCH="x64"' '-DNODE_PLATFORM="linux"'
'-DNODE_WANT_INTERNALS=1' '-DV8_DEPRECATION_WARNINGS=1'
'-DNODE_HAVE_I18N_SUPPORT=1' '-DHAVE_OPENSSL=1' '-D__POSIX__'
'-DHTTP_PARSER_STRICT=0' -I/usr/include/x86_64-linux-gnu -I../src
-I../tools/msvs/genfiles -I../deps/uv/src/ares
-I/home/dev/Software/debian/nodejs/collab-maint/out/Release/obj/gen
-I../deps/v8 -I../deps/cares/include -I../deps/v8/include
-I../deps/http_parser  -pthread -Wall -Wextra -Wno-unused-parameter -m64
-O3 -ffunction-sections -fdata-sections -fno-omit-frame-pointer -fno-rtti
-fno-exceptions -std=gnu++0x -MMD -MF
/home/dev/Software/debian/nodejs/collab-maint/out/Release/.deps//home/dev/Software/debian/nodejs/collab-maint/out/Release/obj.target/node/src/node.o.d.raw
-g -O2 -fstack-protector-strong -Wformat -Werror=format-security
-Wdate-time -D_FORTIFY_SOURCE=2  -c -o
/home/dev/Software/debian/nodejs/collab-maint/out/Release/obj.target/node/src/node.o
../src/node.cc
In file included from ../src/node.cc:16:0:
../src/node_crypto.h:94:54: error: invalid application of ‘sizeof’ to
incomplete type ‘SSL_CTX {aka ssl_ctx_st}’
   static const int64_t kExternalSize = sizeof(SSL_CTX);
  ^
../src/node_crypto.h:225:17: error: invalid application of ‘sizeof’ to
incomplete type ‘SSL {aka ssl_st}’
   sizeof(SSL) + sizeof(SSL3_STATE) + 42 * 1024;
 ^
../src/node_crypto.h:225:28: error: ‘SSL3_STATE’ was not declared in this
scope
   sizeof(SSL) + sizeof(SSL3_STATE) + 42 * 1024;
^
../src/node_crypto.h:469:18: error: field ‘ctx_’ has incomplete type
‘EVP_CIPHER_CTX {aka evp_cipher_ctx_st}’
   EVP_CIPHER_CTX ctx_; /* coverity[member_decl] */
  ^
In file included from /usr/include/openssl/crypto.h:31:0,
 from /usr/include/openssl/comp.h:16,
 from /usr/include/openssl/ssl.h:47,
 from ../src/node_crypto.h:20,
 from ../src/node.cc:16:
/usr/include/openssl/ossl_typ.h:89:16: note: forward declaration of
‘EVP_CIPHER_CTX {aka struct evp_cipher_ctx_st}’
 typedef struct evp_cipher_ctx_st EVP_CIPHER_CTX;
^
In file included from ../src/node.cc:16:0:
../src/node_crypto.h:505:12: error: field ‘ctx_’ has incomplete type
‘HMAC_CTX {aka hmac_ctx_st}’
   HMAC_CTX ctx_; /* coverity[member_decl] */
^
In file included from /usr/include/openssl/crypto.h:31:0,
 from /usr/include/openssl/comp.h:16,
 from /usr/include/openssl/ssl.h:47,
 from ../src/node_crypto.h:20,
 from ../src/node.cc:16:
/usr/include/openssl/ossl_typ.h:101:16: note: forward declaration of
‘HMAC_CTX {aka struct hmac_ctx_st}’
 typedef struct hmac_ctx_st HMAC_CTX;
^
In file included from ../src/node.cc:16:0:
../src/node_crypto.h:536:14: error: field ‘mdctx_’ has incomplete type
‘EVP_MD_CTX {aka evp_md_ctx_st}’
   EVP_MD_CTX mdctx_; /* coverity[member_decl] */
  ^
In file included from /usr/include/openssl/crypto.h:31:0,
 from /usr/include/openssl/comp.h:16,
 from /usr/include/openssl/ssl.h:47,
 from ../src/node_crypto.h:20,
 from ../src/node.cc:16:
/usr/include/openssl/ossl_typ.h:91:16: note: forward declaration of
‘EVP_MD_CTX {aka struct evp_md_ctx_st}’
 typedef struct evp_md_ctx_st EVP_MD_CTX;
^
In file included from ../src/node.cc:16:0:
../src/node_crypto.h:568:14: error: field ‘mdctx_’ has incomplete type
‘EVP_MD_CTX {aka evp_md_ctx_st}’
   EVP_MD_CTX mdctx_; /* coverity[member_decl] */
  ^
In file included from /usr/include/openssl/crypto.h:31:0,
 from /usr/include/openssl/comp.h:16,
 from /usr/include/openssl/ssl.h:47,
 from ../src/node_crypto.h:20,
 from ../src/node.cc:16:
/usr/include/openssl/ossl_typ.h:91:16: note: forward declaration of
‘EVP_MD_CTX {aka struct

Bug#828678: dibbler-client: overwrites /etc/resolv.conf link (aka. no resolvconf support)

2016-06-26 Thread Peter Poeschl

Package: dibbler-client
Version: 1.0.1-1
Severity: normal
Tags: ipv6 patch

Dear Maintainer,

   * What led up to the situation?
Installed dibbler-client

   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Start the dibbler-client daemon

   * What was the outcome of this action?
The /etc/resolv.conf symlink was overwritten with a resolv.conf file

   * What outcome did you expect instead?
dibbler-client should call resolvconf to let it update the file linked to by
/etc/resolv.conf.


Installing and compiling the dibbler source package, I found in
dibbler-config.h

   /* Support for /sbin/resolvconf enabled? */
   /* #undef MOD_RESOLVCONF */

i.e. the package is compiled without resolvconf support.


Adding the attached patch solved the problem.


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

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

Versions of packages dibbler-client depends on:
ii  debconf [debconf-2.0]  1.5.59
ii  libc6  2.22-11
ii  libgcc11:6.1.1-7
ii  libstdc++6 6.1.1-7
ii  ucf3.0036

Versions of packages dibbler-client recommends:
ii  dibbler-doc  1.0.1-1
ii  resolvconf   1.79

dibbler-client suggests no packages.

-- Configuration Files:
/etc/init.d/dibbler-client changed:
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/dibbler-client
NAME=dibbler-client
DESC="DHCPv6 client"
DAEMON_OPTS=run
test -x $DAEMON || exit 0
if [ -f /etc/default/dibbler ] ; then
. /etc/default/dibbler
fi
set -e
case "$1" in
  start)
echo -n "Starting $DESC: "
$DAEMON start 2>&1 > /dev/null
echo "$NAME."
;;
  stop)
echo -n "Stopping $DESC: "
($DAEMON stop 2>&1 > /dev/null || true)
echo "$NAME."
;;
  status)
echo "Status $DESC: $NAME"
$DAEMON status
;;
  #reload)
#
#   If the daemon can reload its config files on the fly
#   for example by sending it SIGHUP, do it here.
#
#   If the daemon responds to changes in its config file
#   directly anyway, make this a do-nothing entry.
#
# echo "Reloading $DESC configuration files."
# start-stop-daemon --stop --signal 1 --quiet --pidfile \
#   /var/run/$NAME.pid --exec $DAEMON
  #;;
  restart|force-reload)
#
#   If the "reload" option is implemented, move the "force-reload"
#   option to the "reload" entry above. If not, "force-reload" is
#   just the same as "restart".
#
echo -n "Restarting $DESC: "
($DAEMON stop 2>&1 > /dev/null || true)
sleep 1
$DAEMON start 2>&1 > /dev/null
echo "$NAME."
;;
  *)
N=/etc/init.d/$NAME
# echo "Usage: $N {start|stop|restart|reload|force-reload}" >&2
echo "Usage: $N {start|stop|restart|force-reload}" >&2
exit 1
;;
esac
exit 0


-- debconf information:
* dibbler-client/options: dns, domain
* dibbler-client/interfaces: eth0
  dibbler-client/title:
* dibbler-client/start: true
diff --git a/debian/rules b/debian/rules
index 700412f..9039143 100755
--- a/debian/rules
+++ b/debian/rules
@@ -12,6 +12,10 @@ override_dh_strip:
dh_strip -pdibbler-client --dbg-package=dibbler-client-dbg
dh_strip -pdibbler-relay  --dbg-package=dibbler-relay-dbg
 
+.PHONY: override_dh_auto_configure
+override_dh_auto_configure:
+   dh_auto_configure -- --enable-resolvconf
+
 %:
dh $@ --with autotools_dev

Bug#820822: vlc consumes all RAM within seconds and system swaps and freezes

2016-06-26 Thread Sebastian Ramacher

Control: reassign -1 libvdpau-va-gl1 0.3.6-1
Control: tags -1 - moreinfo

On 2016-04-14 13:03:30, Γιώργος Πάλλας wrote:
> On 12/04/16 22:59, Sebastian Ramacher wrote:
> > Control: tags -1 + moreinfo
> > 
> > On 2016-04-12 22:36:30, Giorgos Pallas wrote:
> > > Package: src:vlc
> > > Version: 2.2.2-5+b2
> > > Severity: important
> > > 
> > > Dear Maintainer,
> > > 
> > > Whatever video I will try to play, vlc consumes within seconds all 4GB of 
> > > RAM and makes the system swap
> > > and eventually freeze, requiring a reboot. This started after upgrading 
> > > to debian testing
> > > (vlc 2.2.2-5), and continues even after I upgraded vlc to unstable (vlc 
> > > 2.2.2-5+b2).
> > > 
> > > Below is vlc -vvv log:
> > > 
> > >   $ vlc -vvv dvgrab-078.dv
> > Does it happen only with this file or any file?
> 
> As I wrote above, it happens with all video files of various types and
> codecs.
> 
> > 
> > > [7feca0001268] vdpau_display vout display debug: using back-end 
> > > OpenGL/VAAPI/libswscale backend for VDPAU
> > > [7feca0001268] vdpau_display vout display debug: using RGBA format 2
> > > [7feca0001268] vdpau_display vout display debug: using X11 window 
> > > 0x0481
> > ...
> > > [7feca4000958] core video output warning: picture is too late to be 
> > > displayed (missing 79 ms)
> > > [7feca4000958] core video output warning: picture is too late to be 
> > > displayed (missing 39 ms)
> > > [7feca4000958] core video output warning: picture is too late to be 
> > > displayed (missing 95 ms)
> > > [7feca4000958] core video output warning: picture is too late to be 
> > > displayed (missing 56 ms)
> > This reminds me of libvdpau-va-gl1 bugs. Is it any better if you remove
> > libvdpau-va-gl1?
> > 
> > Regards
> 
> You got it! After removing that package, vlc would not freeze anymore.

Thanks for the update. Re-assigning to libvdpau-va-gl1. As 0.4.0 fixed some
libvpdau-va-gl issues related to vlc, this issue might be fixed as well.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#828636: [Reproducible-builds] Bug#828636: Bug#828636: libembperl-perl: please make the build reproducible

2016-06-26 Thread Axel Beckert

Hi!

gregor herrmann wrote:
> On Sun, 26 Jun 2016 17:16:52 +0200, Reiner Herrmann wrote:
> > > Sorry, but that's wrong:
> > > 
> > > → dpkg -L libembperl-perl | egrep man/de/man./
> > > /usr/share/man/de/man3/Embperl::Features.3pm.gz
> > > → man /usr/share/man/de/man3/Embperl::Features.3pm.gz
> > > 
> > > That's clearly my mother tongue. :-)
> > 
> > Sorry, I assumed Embperl::Features was also misdetected (because the
> > original file ends with D) and haven't looked into it.
> 
> Oops, sorry, I missed that too when applying Reiner's patch.

Oh, you were quick. (Well, as usual. ;-)

> Looking at the manpage:
> 
> Das standart Layout einer Website can einmal definiert werden
> 
> I have a hard time defining this as German though :/

There are umlauts in it!!!1!elf! ;-)

> So yes, I guess we can remove this document.
> 
> Implemented in git; I'm holding off with a second hasty upload, sorry
> for the first one.

Oh, meh.

Reiner Herrmann wrote:
> On Sun, Jun 26, 2016 at 05:07:54PM +0200, Axel Beckert wrote:
> > I currently fail to see why this can catch Embperl::Syntax::POD in one
> > build, but not in another. IMHO this should happen with every build.
> > Will investigate.
> 
> It's actually related to the shell...
>
> $ touch aD bD cD dD eD AD BD
> $ dash -c "ls *[a-z]D"
> aD  bDcD  dD  eD
> $ bash -c "ls *[a-z]D"
> aD  ADbD  BD  cD  dD  eD
> 
> With bash POD.3pm also matches *[a-z]D.3pm.

Yay, thanks for that. I actually also suspected capitalization during
matching as culprit, but suspected different locales as reason for
that.

Will do an upload which re-includes the man page, but with proper
matching.

Thanks again for that bug-report.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#828369: krb5: FTBFS with openssl 1.1.0

2016-06-26 Thread Benjamin Kaduk

I believe that https://github.com/krb5/krb5/pull/447 has upstream's
efforts at OpenSSL 1.0 compatibility.

-Ben

Bug#828633: mount in testing/unstable should conflict with old bash-completion

2016-06-26 Thread Andreas Henriksson

Control: tags -1 + pending
Control: severity -1 serious

Hello!

Thanks for your bug report. I apparently forgot to bump the version
of the already existing Breaks/Replaces statements in previous upload.
Fixed in git, will be part of next upload.

Regards,
Andreas Henriksson

Bug#828677: tech-ctte: user/root password occasionally appear in clear text when rebooting from CLI

2016-06-26 Thread Bruce Gilbert

Package: tech-ctte
Severity: important

Dear Maintainer,
   Before version 8 jessie, I frequently rebooted/shutdown from the
CLI... When I tried doing so since installing version 8 ( I
think I was up to 8.3?) I would get varying results: mostly the machine would
"Hang" for a minute or so & then power down; but occassionally it would reboot.
After the minute of hanging - a flashing little white line in the top Left Hand
Side of a black screen - I would get unformatted messages across the screen
followed occasionally by my password in clear text before the (tty?) login...On
one occasion, it was my root password! I experimented with several suggestions
from various forums: ; ; ...but got
confused. So I went to the Devuan site & downloaded it because in my gut, I
believed that the problems were caused by systemd? I think systemd "has its
finger in too many pies"! i.e.: it is involved in too many processes beyond the
initialisation of the computer. This seems to me to go against the general
grain of the basic Unix/Linux philosophy: (my paraphrase): Do ONE thing- Keep
it SIMPLE - do it RIGHT.



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

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Bug#775555: vlc: VLC segfaults when converting a DVD with a title number greater than zero

2016-06-26 Thread Sebastian Ramacher

Hi Derek

almost a year past, my bad :(

On 2015-07-20 15:54:48, Derek wrote:
> It still happens
> 
> I've included attachments:
> vlc-vvv.txt: contains the output when calling vlc from the command line
> vlc_gdb_bt.txt: the output of "bt" when running vlc within gdb
> vlc_bt_full.txt: the output of "bt full" from gdb
> 
> 
> A few notes.
> From reportbug-ng:
> 
> "Use "rm ~/.cache/vlc/plugins-*.dat" to remove your plugins cache."
>~/.cache/vlc/ doesn't exist
> 
> "Check that modules are correctly loaded: "vlc -vvv --color --list"
>If you have yellow warning lines at the top, that could well be the
>problem"
> 
>   There are no yellow warning lines produced by that command
> 
> If you have installed libraries from other repositories (e.g. to use
>allegedly patent-encumbred encoders), revert to the official Debian
>libraries before reporting a bug.
> 
>   The only thing I've installed from outside of the Debian repo
>   is libdvdcss2 from the vlc repo to get DVD playback working

If this is still an issue with 2.2.4, could you please report this issue
upstream at [1]? Thanks! Please let us know the bug number.

Cheers

[1] https://trac.videolan.org/vlc/
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#828630: jessie-pu: package libbusiness-creditcard-perl/0.33-1+deb8u1

2016-06-26 Thread gregor herrmann

On Sun, 26 Jun 2016 17:00:36 +0100, Adam D. Barratt wrote:

> On Sun, 2016-06-26 at 15:10 +0200, gregor herrmann wrote:
> > I've prepared an update for libbusiness-creditcard-perl in
> > jessie{,-updates} which fixes #814479 for stable users. The issue at
> > hand is that the credit card ranges of several providers need to be
> > updated.
> That bug report says "[t]he most important change in this release is
> recognition of new MasterCard ranges which will be issued starting in
> October 2016". Given that (I'd really hope that) the next point release
> will be well before October, are any of the other changes sufficiently
> urgent to need a -updates release?

I'm also only aware of the October deadline.
Maybe Ivan knows more?
(Cc'd. Too bad X-Debbugs-CC does't get carried over from original bug
report.)
 
> > In practice there are several options to do this update in stable:
> > - What I've prepared (attached as a debdiff) for now is to backport
> >   the functional and some documentation changes from 0.34 and 0.35 to
> >   0.33 in 3 logically separate quilt patches, in order to make
> >   reviewing easy. In practice this leaves out only some minor changes
> >   in metadata and unrelated documentation changes from 0.35.
> > - Ivan (upstream and Debian contributor) originally asked to take
> >   the 0.35 release and upload it to stable (presumably as
> >   0.35-0+deb8u1). This had the advantage of shipping a fully tested
> >   release but is probably not the release team's typically preferred
> >   way. -- Complete diff:
> >   
> > https://metacpan.org/diff/file?target=IVAN%2FBusiness-CreditCard-0.35%2F=IVAN%2FBusiness-CreditCard-0.33%2F
> 
> I'd be okay with either of those options, having looked at the upstream
> diff.

Thanks, then I think we can proceed with the second option, i.e.
updating to the "full" 0.35 release.

I'm attaching a new debdiff for the proposed upload.


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   
diff -Nru libbusiness-creditcard-perl-0.33/Changes libbusiness-creditcard-perl-0.35/Changes
--- libbusiness-creditcard-perl-0.33/Changes	2014-09-14 01:13:26.0 +0200
+++ libbusiness-creditcard-perl-0.35/Changes	2016-02-09 23:43:57.0 +0100
@@ -1,5 +1,21 @@
 Revision history for Perl extension Business::CreditCard.
 
+0.35  Tue Feb  9 14:43:38 PST 2016
+- Fix bug identifying 49* Visa cards introduced in 0.34, patch from
+  Ed J, thanks!
+- doc: Clarify processing agreements don't apply to Canada
+
+0.34  Fri Feb  5 07:24:00 PST 2016
+- 19 digit Visa and Discover cards
+- MasterCard 222100–272099 range
+- Canada does not process JCB 3529-3589 as Discover, but Puerto Rico,
+  US Virgin Islans, Northern Mariana Islands, Palau and Guam do
+- China Union Pay only processed as Discover in the US, Mexico and
+  the Caribbean, not elsewhere outside China
+- 14 digit Discover remain only in 36*
+- receipt_cardtype subroutine supporting Discover's new receipt
+  requirements
+
 0.33  Sat Sep 13 16:13:15 PDT 2014
 - With $Country explicity to CA, fix identification of JCB 3529-3589
   as Discover
diff -Nru libbusiness-creditcard-perl-0.33/CreditCard.pm libbusiness-creditcard-perl-0.35/CreditCard.pm
--- libbusiness-creditcard-perl-0.33/CreditCard.pm	2014-09-14 01:12:48.0 +0200
+++ libbusiness-creditcard-perl-0.35/CreditCard.pm	2016-02-09 23:43:32.0 +0100
@@ -5,7 +5,7 @@
 
 @ISA = qw( Exporter );
 
-$VERSION = "0.33";
+$VERSION = "0.35";
 
 $Country = 'US';
 
@@ -83,7 +83,7 @@
 other networks, in which one type of card is processed as another card type.
 
 By default, Business::CreditCard returns the type the card should be treated as
-in the US and Canada.  You can change this to return the type the card should
+in the US.  You can change this to return the type the card should
 be treated as in a different country by setting
 C<$Business::CreditCard::Country> to your two-letter country code.  This
 is probably what you want to determine if you accept the card, or which
@@ -99,28 +99,30 @@
 
 =item Most Diner's club is now identified as Discover.  (This supercedes the earlier identification of some Diner's club cards as MasterCard inside the US and Canada.)
 
-=item JCB cards in the 3528-3589 range are identified as Discover inside the US and Canada.
+=item JCB cards in the 3528-3589 range are identified as Discover inside the US and territories.
 
-=item China Union Pay cards are identified as Discover cards outside China.
+=item China Union Pay cards are identified as Discover cards in the US, Mexico and most Caribbean countries.
 
 =back
 
-=head1 NOTE ON INTENDED PURPOSE
+=head1 RECEIPT REQUIREMENTS
 
-This module is for verifying I B.  It

Bug#828674: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: python-django-treebeard
Version: 4.0.1+dfsg-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that python-django-treebeard FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


python-django-treebeard_4.0.1+dfsg-1.log.txt.gz
Description: Binary data

Bug#828675: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: python-jingo
Version: 0.8-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that python-jingo FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


python-jingo_0.8-1.log.txt.gz
Description: Binary data

Bug#828673: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: python-django-tagging
Version: 1:0.4.1-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that python-django-tagging FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


python-django-tagging_1:0.4.1-1.log.txt.gz
Description: Binary data

Bug#828672: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: python-django-registration
Version: 2.0.4-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that python-django-registration FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


python-django-registration_2.0.4-1.log.txt.gz
Description: Binary data

Bug#828676: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: python-restless
Version: 2.0.1-5
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that python-restless FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


python-restless_2.0.1-5.log.txt.gz
Description: Binary data

Bug#828663: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: python-django-contact-form
Version: 1.2~git23.8413069-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that python-django-contact-form FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


python-django-contact-form_1.2~git23.8413069-1.log.txt.gz
Description: Binary data

Bug#828664: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: python-django-debug-toolbar
Version: 1:1.4-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that python-django-debug-toolbar FTBFS with 
1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


python-django-debug-toolbar_1:1.4-1.log.txt.gz
Description: Binary data

Bug#828669: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: python-django-mptt
Version: 0.8.3-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that python-django-mptt FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


python-django-mptt_0.8.3-1.log.txt.gz
Description: Binary data

Bug#828666: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: python-django-feincms
Version: 1.11.4-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that python-django-feincms FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


python-django-feincms_1.11.4-1.log.txt.gz
Description: Binary data

Bug#828671: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: python-django-pyscss
Version: 2.0.2-4
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that python-django-pyscss FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


python-django-pyscss_2.0.2-4.log.txt.gz
Description: Binary data

Bug#828665: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: python-django-extensions
Version: 1.6.7-2
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that python-django-extensions FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


python-django-extensions_1.6.7-2.log.txt.gz
Description: Binary data

Bug#828661: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: python-django-bootstrap-form
Version: 3.1.0-6
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that python-django-bootstrap-form FTBFS with 
1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


python-django-bootstrap-form_3.1.0-6.log.txt.gz
Description: Binary data

Bug#828668: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: python-django-jsonfield
Version: 1.0.0-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that python-django-jsonfield FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


python-django-jsonfield_1.0.0-1.log.txt.gz
Description: Binary data

Bug#828662: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: python-django-compressor
Version: 2.0-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that python-django-compressor FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


python-django-compressor_2.0-1.log.txt.gz
Description: Binary data

Bug#828667: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: python-django-formtools
Version: 1.0-2
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that python-django-formtools FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


python-django-formtools_1.0-2.log.txt.gz
Description: Binary data

Bug#828670: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: python-django-openstack-auth
Version: 2.2.1-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that python-django-openstack-auth FTBFS with 
1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


python-django-openstack-auth_2.2.1-1.log.txt.gz
Description: Binary data

Bug#828209: [Debian-med-packaging] Bug#828209: libssw: FTBFS on non-SSE architectures

2016-06-26 Thread Aaron M. Ucko

Sascha Steinbiss  writes:

> I can’t see why code containing SSE instructions would run on i386?

My expectation ws that depending on the processor's capabilities, this
code would either succeed (on reasonably modern processors) or fail with
SIGILL (Illegal instruction).  In general, i386 binaries should be able
to use modern processor features on suitable hardware; GCC just makes a
point of conservatively targeting the lowest common denominator unless
specifically directed otherwise.

However, I was able to reproduce the segfault on a system of my own that
definitely supports these instructions, so I'm not sure what's up --
particularly given that the x32 build ran into no such trouble, and that
-Wall yielded no warnings whatsoever.  As such, perhaps you should just
give up on any-i386 after all.

Thanks for the quick reply, and sorry my suggestion didn't work out.

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Bug#828660: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: mini-buildd
Version: 1.0.12
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that mini-buildd FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


mini-buildd_1.0.12.log.txt.gz
Description: Binary data

Bug#828650: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: django-markupfield
Version: 1.4.0-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-markupfield FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


django-markupfield_1.4.0-1.log.txt.gz
Description: Binary data

Bug#828647: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: django-floppyforms
Version: 1.6.2+dfsg-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-floppyforms FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


django-floppyforms_1.6.2+dfsg-1.log.txt.gz
Description: Binary data

Bug#828657: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: django-sitetree
Version: 1.5.1-2
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-sitetree FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


django-sitetree_1.5.1-2.log.txt.gz
Description: Binary data

Bug#828646: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: django-countries
Version: 3.4.1-2
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-countries FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


django-countries_3.4.1-2.log.txt.gz
Description: Binary data

Bug#828652: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: django-nose
Version: 1.4.3-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-nose FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


django-nose_1.4.3-1.log.txt.gz
Description: Binary data

Bug#828651: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: django-model-utils
Version: 2.4-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-model-utils FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


django-model-utils_2.4-1.log.txt.gz
Description: Binary data

Bug#828654: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: django-polymorphic
Version: 0.9.2-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-polymorphic FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


django-polymorphic_0.9.2-1.log.txt.gz
Description: Binary data

Bug#828658: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: django-stronghold
Version: 0.2.7+debian-2
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-stronghold FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


django-stronghold_0.2.7+debian-2.log.txt.gz
Description: Binary data

Bug#828659: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: django-taggit
Version: 0.20.0-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-taggit FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


django-taggit_0.20.0-1.log.txt.gz
Description: Binary data

Bug#828649: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: django-localflavor
Version: 1.2-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-localflavor FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


django-localflavor_1.2-1.log.txt.gz
Description: Binary data

Bug#828648: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: django-hijack
Version: 2.0.7-2
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-hijack FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


django-hijack_2.0.7-2.log.txt.gz
Description: Binary data

Bug#828653: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: django-pipeline
Version: 1.6.8-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-pipeline FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


django-pipeline_1.6.8-1.log.txt.gz
Description: Binary data

Bug#828656: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: django-sekizai
Version: 0.9.0-3
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-sekizai FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


django-sekizai_0.9.0-3.log.txt.gz
Description: Binary data

Bug#828655: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: django-recurrence
Version: 1.3.0-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-recurrence FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


django-recurrence_1.3.0-1.log.txt.gz
Description: Binary data

Bug#828641: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: celery-haystack
Version: 0.10-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that celery-haystack FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


celery-haystack_0.10-1.log.txt.gz
Description: Binary data

Bug#828645: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: django-compat
Version: 1.0.12-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-compat FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


django-compat_1.0.12-1.log.txt.gz
Description: Binary data

Bug#828643: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: django-celery-transactions
Version: 0.3.6-1
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-celery-transactions FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


django-celery-transactions_0.3.6-1.log.txt.gz
Description: Binary data

Bug#828644: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: django-classy-tags
Version: 0.7.2-2
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-classy-tags FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


django-classy-tags_0.7.2-2.log.txt.gz
Description: Binary data

Bug#828642: FTBFS under Django 1.10

2016-06-26 Thread Chris Lamb

Source: django-celery
Version: 3.1.17-3
Severity: important
User: python-dja...@packages.debian.org
Usertags: django110 django110-ftbfs

Hi,

Whilst rebuilding all reverse build-dependencies of python-django
with the latest beta, I noticed that django-celery FTBFS with 1.10.

Please update your package to work with Django 1.10 (in experimental)
as I will uploading it to unstable once it is released (and at the same
time raising the severity of this bug to RC).

Upstream's release notes may be helpful in diagnosing the issue:

  https://docs.djangoproject.com/en/dev/releases/1.10/

The full build log is attached.


Regards,

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


django-celery_3.1.17-3.log.txt.gz
Description: Binary data

Bug#828639: [Reproducible-builds] Bug#828639: libmarpa-r2-perl: please make the build reproducible

2016-06-26 Thread Reiner Herrmann

On Sun, Jun 26, 2016 at 05:58:37PM +0200, Reiner Herrmann wrote:
> The attached patch makes it honour SOURCE_DATE_EPOCH, if it is
> available, to get a deterministic timestamp.

Sorry, the patch contained one line too much.
Updated patch attached.
diff --git a/debian/patches/reproducible_build.patch b/debian/patches/reproducible_build.patch
new file mode 100644
index 000..24cf4ff
--- /dev/null
+++ b/debian/patches/reproducible_build.patch
@@ -0,0 +1,23 @@
+Author: Reiner Herrmann 
+Description: Honour SOURCE_DATE_EPOCH for embedded timestamp, if it is set
+
+--- a/inc/Marpa/R2/Build_Me.pm
 b/inc/Marpa/R2/Build_Me.pm
+@@ -83,7 +83,7 @@
+ 
+ ##no critic(ValuesAndExpressions::RequireInterpolationOfMetachars)
+ $text .= q{use vars qw($TIMESTAMP)} . qq{;\n};
+-$text .= q{$TIMESTAMP='} . localtime()->datetime . qq{';\n};
++$text .= q{$TIMESTAMP='} . (gmtime($ENV{SOURCE_DATE_EPOCH}) || localtime())->datetime . qq{';\n};
+ ##use critic
+ 
+ for my $package (@use_packages) {
+@@ -104,7 +104,7 @@
+ 
+ ##no critic(ValuesAndExpressions::RequireInterpolationOfMetachars)
+ $text .= q{use vars qw($TIMESTAMP)} . qq{;\n};
+-$text .= q{$TIMESTAMP='} . localtime()->datetime . qq{';\n};
++$text .= q{$TIMESTAMP='} . (gmtime($ENV{SOURCE_DATE_EPOCH}) || localtime())->datetime . qq{';\n};
+ ##use critic
+ 
+ for my $package (@use_packages) {
diff --git a/debian/patches/series b/debian/patches/series
index f8d2256..b4a3780 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 1001_xs_boot_workaround.patch
 2001_libmarpa_external_linkage.patch
+reproducible_build.patch


signature.asc
Description: Digital signature

Bug#828636: [Reproducible-builds] Bug#828636: libembperl-perl: please make the build reproducible

2016-06-26 Thread gregor herrmann

On Sun, 26 Jun 2016 17:16:52 +0200, Reiner Herrmann wrote:

> > Sorry, but that's wrong:
> > 
> > → dpkg -L libembperl-perl | egrep man/de/man./
> > /usr/share/man/de/man3/Embperl::Features.3pm.gz
> > → man /usr/share/man/de/man3/Embperl::Features.3pm.gz
> > 
> > That's clearly my mother tongue. :-)
> 
> Sorry, I assumed Embperl::Features was also misdetected (because the
> original file ends with D) and haven't looked into it.

Oops, sorry, I missed that too when applying Reiner's patch.

Looking at the manpage:

Das standart Layout einer Website can einmal definiert werden

I have a hard time defining this as German though :/
 

So yes, I guess we can remove this document.

Implemented in git; I'm holding off with a second hasty upload, sorry
for the first one.

Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#828344: Processed: httrack: FTBFS with openssl 1.1.0

2016-06-26 Thread Xavier Roche


Hi!

This should be fixed by 3.48.23-1 (uploaded few minutes ago, the culprit 
was a libtool issue)


Thanks for the report,
Xavier

Bug#828509: postgis: FTBFS with openssl 1.1.0

2016-06-26 Thread Sebastiaan Couwenberg

Control: tags -1 unreproducible moreinfo

Hi Kurt,

Thanks for your work on OpenSSL.

On 06/26/2016 12:23 PM, Kurt Roeckx wrote:
> OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
> OpenSSL this package fail to build.  A log of that build can be found at:
> https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/postgis_2.2.2+dfsg-2_amd64-20160529-1510

postgis has no direct dependency on libssl nor libcrypto. There is no
clear openssl related failure in the buildlog, but it does show that it
only installs the custom openssl dependencies and relies on unstable for
the rest of the packages. So none of postgis build dependencies have
been rebuilt with the new openssl packages. I suspect this issue is
caused by postgres still linking to the old openssl whereas the new
openssl is installed in the build environment.

> There is a libssl-dev package available in experimental that contains a recent
> snapshot, I suggest you try building against that to see if everything works.
> 
> If you have problems making things work, feel free to contact us.

postgis is not among the reverse dependencies for openssl in the
auto-openssl transition tracker [0], so I guess postgis was only rebuilt
for your tests because it build depends on libssl-dev.

I cannot reproduce the issue with the libssl-dev from experimental, so
I'm starting to suspect this issue is a false positive.

Can you confirm that the openssl update to 1.1.0 only affects packaging
linking its libssl and/or libcrypto?

[0] https://release.debian.org/transitions/html/auto-openssl.html

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1

Bug#828640: conky: Segmentation fault at start (conky 10.10.2)

2016-06-26 Thread markus

Package: conky
Version: 1.10.2-1
Severity: important

Dear Maintainer,

when I start conky, I imediately get a segmentation fault error.
- standard configuration, nothing changed

___

$conky --version
conky 1.10.2 compiled Wed May  4 00:32:04 UTC 2016 for Linux 3.16.0-4-powerpc64
ppc

Compiled in features:

System config file: /etc/conky/conky.conf
Package library path: /usr/lib/conky


 General:
  * math
  * hddtemp
  * portmon
  * IPv6
  * support for IBM/Lenovo notebooks
  * builtin default configuration
  * old configuration syntax
  * apcupsd
  * iostats
  * ncurses
  * Internationalization support

 Music detection:
  * MPD
  * MOC

 Default values:
  * Netdevice: eth0
  * Local configfile: $HOME/.conkyrc
  * Localedir: /usr/share/locale
  * Maximum netdevices: 64
  * Maximum text size: 16384
  * Size text buffer: 256



-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: powerpc (ppc)

Kernel: Linux 4.5.0-2-powerpc
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages conky depends on:
ii  conky-cli  1.10.2-1

conky recommends no packages.

conky suggests no packages.

-- no debconf information

Bug#828639: libmarpa-r2-perl: please make the build reproducible

2016-06-26 Thread Reiner Herrmann

Source: libmarpa-r2-perl
Version: 2.086000~dfsg-5
Severity: wishlist
Tags: patch upstream
User: reproducible-bui...@lists.alioth.debian.org
Usertags: timestamps
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi!

While working on the "reproducible builds" effort [1], we have noticed
that libmarpa-r2-perl could not be built reproducibly.
It embeds the current build date into Version.pm.

The attached patch makes it honour SOURCE_DATE_EPOCH, if it is
available, to get a deterministic timestamp.

Regards,
 Reiner

[1]: https://wiki.debian.org/ReproducibleBuilds
diff --git a/debian/patches/reproducible_build.patch b/debian/patches/reproducible_build.patch
new file mode 100644
index 000..7d80ba7
--- /dev/null
+++ b/debian/patches/reproducible_build.patch
@@ -0,0 +1,22 @@
+Author: Reiner Herrmann 
+Description: Honour SOURCE_DATE_EPOCH for embedded timestamp, if it is set
+
+--- a/inc/Marpa/R2/Build_Me.pm
 b/inc/Marpa/R2/Build_Me.pm
+@@ -83,7 +83,7 @@
+ 
+ ##no critic(ValuesAndExpressions::RequireInterpolationOfMetachars)
+ $text .= q{use vars qw($TIMESTAMP)} . qq{;\n};
+-$text .= q{$TIMESTAMP='} . localtime()->datetime . qq{';\n};
++$text .= q{$TIMESTAMP='} . (gmtime($ENV{SOURCE_DATE_EPOCH}) || localtime())->datetime . qq{';\n};
+ ##use critic
+ 
+ for my $package (@use_packages) {
+@@ -105,6 +105,7 @@
+ ##no critic(ValuesAndExpressions::RequireInterpolationOfMetachars)
+ $text .= q{use vars qw($TIMESTAMP)} . qq{;\n};
+ $text .= q{$TIMESTAMP='} . localtime()->datetime . qq{';\n};
++$text .= q{$TIMESTAMP='} . (gmtime($ENV{SOURCE_DATE_EPOCH}) || localtime())->datetime . qq{';\n};
+ ##use critic
+ 
+ for my $package (@use_packages) {
diff --git a/debian/patches/series b/debian/patches/series
index f8d2256..b4a3780 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
 1001_xs_boot_workaround.patch
 2001_libmarpa_external_linkage.patch
+reproducible_build.patch

Bug#828227: jessie-pu: package libdatetime-timezone-perl/1:1.75-2+2016e

2016-06-26 Thread gregor herrmann

On Sun, 26 Jun 2016 16:46:15 +0100, Adam D. Barratt wrote:

> On Sun, 2016-06-26 at 12:19 +0200, gregor herrmann wrote:
> > I've prepared an update for libdatetime-timezone-perl in
> > jessie{,-updates} to include the new data from the Olson db 2016e.
> > This includes contemporary change for Egypt becoming effective on 7
> > July.
> 
> Please go ahead.

Thank you! Uploaded.


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#828630: jessie-pu: package libbusiness-creditcard-perl/0.33-1+deb8u1

2016-06-26 Thread Adam D. Barratt

Control: tags -1 + confirmed

On Sun, 2016-06-26 at 15:10 +0200, gregor herrmann wrote:
> I've prepared an update for libbusiness-creditcard-perl in
> jessie{,-updates} which fixes #814479 for stable users. The issue at
> hand is that the credit card ranges of several providers need to be
> updated.

That bug report says "[t]he most important change in this release is
recognition of new MasterCard ranges which will be issued starting in
October 2016". Given that (I'd really hope that) the next point release
will be well before October, are any of the other changes sufficiently
urgent to need a -updates release?

> In practice there are several options to do this update in stable:
> - What I've prepared (attached as a debdiff) for now is to backport
>   the functional and some documentation changes from 0.34 and 0.35 to
>   0.33 in 3 logically separate quilt patches, in order to make
>   reviewing easy. In practice this leaves out only some minor changes
>   in metadata and unrelated documentation changes from 0.35.
> - Ivan (upstream and Debian contributor) originally asked to take
>   the 0.35 release and upload it to stable (presumably as
>   0.35-0+deb8u1). This had the advantage of shipping a fully tested
>   release but is probably not the release team's typically preferred
>   way. -- Complete diff:
>   
> https://metacpan.org/diff/file?target=IVAN%2FBusiness-CreditCard-0.35%2F=IVAN%2FBusiness-CreditCard-0.33%2F

I'd be okay with either of those options, having looked at the upstream
diff.

Regards,

Adam

Bug#828585: unworkable: FTBFS with openssl 1.1.0

2016-06-26 Thread Michael Stapelberg

I’ve submitted a fix upstream at https://github.com/niallo/Unworkable/pull/2.
In case upstream merges it in a timely manner and releases a new version,
I’d prefer packaging the new version. Otherwise, we can apply the patch in
Debian directly.

On Sun, Jun 26, 2016 at 12:24 PM, Kurt Roeckx  wrote:

> Source: unworkable
> Version: 0.53-3
> Severity: important
> Control: block 827061 by -1
>
> Hi,
>
> OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
> OpenSSL this package fail to build.  A log of that build can be found at:
>
> https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/unworkable_0.53-3_amd64-20160529-1547
>
> On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various
> of the
> reasons why it might fail.  There are also updated man pages at
> https://www.openssl.org/docs/manmaster/ that should contain useful
> information.
>
> There is a libssl-dev package available in experimental that contains a
> recent
> snapshot, I suggest you try building against that to see if everything
> works.
>
> If you have problems making things work, feel free to contact us.
>
>
> Kurt
>



-- 
Best regards,
Michael

Bug#828629: nvidia-driver 355.11-2 (experimental, amd64) not installable

2016-06-26 Thread Luca Boccassi

On Sun, 2016-06-26 at 17:40 +0200, Roman Horník wrote:
> apt:
> 
> # apt install nvidia-driver=355.11-2

You are using the wrong command. You need to pass -t experimental

apt-get install -t experimental nvidia-driver=355.11-2

But you should be aware that if you are on stretch or sid, that version
is not compatible with the Xorg ABI in stretch/sid, so you should really
not install it.

Kind regards,
Luca Boccassi

signature.asc
Description: This is a digitally signed message part

Bug#828227: jessie-pu: package libdatetime-timezone-perl/1:1.75-2+2016e

2016-06-26 Thread Adam D. Barratt

Control: tags -1 + confirmed

On Sun, 2016-06-26 at 12:19 +0200, gregor herrmann wrote:
> I've prepared an update for libdatetime-timezone-perl in
> jessie{,-updates} to include the new data from the Olson db 2016e.
> This includes contemporary change for Egypt becoming effective on 7
> July.

Please go ahead.

Regards,

Adam

Bug#823864: libpam-cgfs: installing libpam-cgfs from backport on stable prevent session from opening

2016-06-26 Thread Evgeni Golov

Hi Xavier,

On Thu, Jun 16, 2016 at 09:00:47PM +0200, Evgeni Golov wrote:
> > To reproduce the problem, both boxes need :
> > (1) sysinit (no systemd) as system startup
> > (2) cgroupfs-mount installed
> 
> One thing was missing from that list: libpam-systemd.
> I was able to reproduce this by taking a plain jessie vm and installing the 
> following:
> - libpam-cgfs
> - cgroupfs-mount
> - sysvinit-core
> - libpam-systemd
> - linux-image-4.5.0-0.bpo.2-amd64
> 
> Not using kernel 4.5.x does not trigger the issue.

So I can reproduce that on a Jessie system with
 linux-image-4.5.0-0.bpo.2-amd64 4.5.4-1~bpo8+1
But cannot on the same system when I boot
 linux-image-4.6.0-0.bpo.1-amd64 4.6.1-1~bpo8+1

Xavier, can you confirm that?

> I guess this is an issue somewhere between the new cgroups in 4.5 and 
> systemd-shim.
> I'll try to pinpoint that futher when I have some time.

Still think this is the case, but did not investigate further.
If it works for you in 4.6, I'd just close this bug as a glitch in the matrix 
and carry on, ok?

Greets
Evgeni

Bug#828192: /lib/systemd/system/pesign.service is a directory

2016-06-26 Thread Julien Cristau

Control: tag -1 patch

On Sun, Jun 26, 2016 at 00:51:50 +0200, Michael Biebl wrote:

> Package: pesign
> Version: 0.112-1
> Severity: important
> 
> Hi,
> 
> the service shipped in this package is not installed correctly:
> 
> /lib/systemd/system/pesign.service/pesign.service
> 
> That should be
> /lib/systemd/system/pesign.service
> 
I just ran into that.  This should fix it:

diff --git a/debian/pesign.install b/debian/pesign.install
index 3d76ce9..6895c2f 100755
--- a/debian/pesign.install
+++ b/debian/pesign.install
@@ -27,7 +27,7 @@ echo /etc/pki/pesign
 #echo %ghost %attr(0660, -, -) ${localstatedir}/run/%{name}/socket
 #echo %ghost %attr(0660, -, -) ${localstatedir}/run/%{name}/pesign.pid
 echo ${prefix}/lib/tmpfiles.d/pesign.conf
-echo usr/${unitdir}/pesign.service ${unitdir}/pesign.service
+echo usr/${unitdir}/pesign.service ${unitdir}
 echo ${datadir}/pesign/pesign-authorize-users
 echo ${datadir}/pesign/pesign-authorize-groups
 echo ${sysconfdir}/pesign/users

Cheers,
Julien

Bug#828411: libre: FTBFS with openssl 1.1.0

2016-06-26 Thread Vasudev Kamath


Control: tag -1 +pending

Hi Kurt,

Kurt Roeckx  writes:
>
> OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
> OpenSSL this package fail to build.  A log of that build can be found at:
> https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/libre_0.4.14-4_amd64-20160529-1444
>
> On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of 
> the
> reasons why it might fail.  There are also updated man pages at
> https://www.openssl.org/docs/manmaster/ that should contain useful 
> information.
>
> There is a libssl-dev package available in experimental that contains a recent
> snapshot, I suggest you try building against that to see if everything works.
>
> If you have problems making things work, feel free to contact us.

Thanks for the report. I already informed upstream about the transition
and they have provided a patch which is updated in our git¹. I will
upload it once the openssl enters unstable (Hoping my key will be
migrated into Developer keyring.)

¹ 
http://anonscm.debian.org/cgit/pkg-voip/libre.git/commit/?id=7cc4b10cbaba158380910ad3885bf7e6b6895fca

Bug#826166: [Pkg-phototools-devel] Bug#826166: libgphoto2-dev: location of gphoto2-config is not in PATH

2016-06-26 Thread Steve M. Robbins

Hi,

I'm the debian maintainer of digikam and just ran into the same problem.

On Thu, 2 Jun 2016 20:43:58 -0300 "Herbert Fortes (hpfn)"  
wrote:

> > I recon these files should be in /usr/bin unless I am missing something?
> >
> 
> It is about lintian tag[0] 'old-style-config-script'.
> 
> [0] - https://lintian.debian.org/tags/old-style-config-script.html

That link makes the following 3 suggestions.I think you're referring to 
#3.  Please note that #3 begins with "after fixing every reverse depends "; 
as a reverse-depends maintainer, I'd have appreciated at least a note of this 
compatibility break.  :-)

Has any work been done with respect to a pkg-config replacement (#1, #2)?

Thanks,
-Steve

1. You should consider to move to pkg-config file and warn your user to not use 
this script, and open a bug upstream.

2. You should also consider to implement this file as a compatibility wrapper 
over pkg-config.

3. After fixing every reverse depends of your package and use pkg-config 
reverse 
depends makefile, you should consider to put this script, as a temporary 
convenience of your users, under /usr/lib/$DEB_HOST_MULTIARCH/$PACKAGE/bin 
where $DEB_HOST_MULTIARCH is the multi-arch triplet and $PACKAGE is the 
package name. You should also consider to add a NEWS.Debian entry.

signature.asc
Description: This is a digitally signed message part.

Bug#828636: [Reproducible-builds] Bug#828636: libembperl-perl: please make the build reproducible

2016-06-26 Thread Reiner Herrmann

On Sun, Jun 26, 2016 at 05:07:54PM +0200, Axel Beckert wrote:
> I currently fail to see why this can catch Embperl::Syntax::POD in one
> build, but not in another. IMHO this should happen with every build.
> Will investigate.

It's actually related to the shell...

$ touch aD bD cD dD eD AD BD
$ dash -c "ls *[a-z]D"
aD  bD  cD  dD  eD
$ bash -c "ls *[a-z]D"
aD  AD  bD  BD  cD  dD  eD

With bash POD.3pm also matches *[a-z]D.3pm.


signature.asc
Description: Digital signature

Bug#816059: lua5.2 spews garbage to the terminal when it exits on mips64el

2016-06-26 Thread Aurelien Jarno

control: tag -1 + patch

On 2016-02-26 21:08, James McCoy wrote:
> Package: lua5.2
> Version: 5.2.4-1
> Severity: important
> File: /usr/bin/lua5.2
> 
> Taking the first few lines of lua output (piped through "cat -A" to show
> the non-printables) from the Vim build on mips64el[0]:
> 
> checking Lua version... 5.2$
> 5.2$
> $
> ^H^B$
> ^H^W$
> ^H,$
> ^A$
> ^HA$
> ^A^K^A^SY^Q^A^T^\k$
> ^Hk$
> @^B^L@^P$
> ^B^A^C$H#^R^B^C$$
> ^C$
> ^C$
> ^C$
> ^B^H$
> @^B$
> $$
> ^C$
> 
> memorybtblcrcsclcecdCCcmdohoviCMvendllupvsdcdldshdasmbmdtidmmhimmkmpmrsousecaeedeiseuevbfffsi1isi3ificipkbkakCktkDkLkdkMkEkSk0k1k;k2k3k4k5k6k7k8k9khkIkAklkHkNkPkrkFkRkTkukeksl0l1lal2l3l4l5l6l7l8l9mommnwpcDCDLDOICSFALLERISRUPpkplpxpspfporpr1r2r3rfrccvscsfsrsastwitatsuchuiPK1K3K2K4K5pOrPacpnkBSXRXSARAXNXFeALOLF@1@2@3@4@5@6@7@8@9@0%1%2%3%4%5%6%7%8%9%0&1&2&3&4&5&6&7&8&9&0*1*2*3*4*5*6*7*8*9*0#1#2#3#4%a%b%c%d%e%f%g%h%i%j!1!2!3RFF1F2F3F4F5F6F7F8F9FAFBFCFDFEFFFGFHFIFJFKFLFMFNFOFPFQFRFSFTFUFVFWFXFYFZFaFbFcFdFeFfFgFhFiFjFkFlFmFnFoFpFqFrcbMCMLMRLfSCDKRCCWWGHUDIQDTOPUfhPAWAu0u1u2u3u4u5u6u7u8u9opocIcIpspSfSbZAZBZCZDZEZFZGZHZIZJZKZLZMZNZOZPZQZRZSZTZUZVZWZXZYZZZaZbZcZdZeZfZgZhZiZjZkZlZmZnZoZpZqZrZsZtZuZvZwZxZyKmMiRQGmAFABxldvcis0s1s2s3MTXyZzYvYwYxYyYzYZS1S2S3S4S5S6S7S8XhXlXoXrXtXvsAYIi2nlbckomaG2G3G1G4GRGLGUGDGHGVGCmlmubxcoitlilmsgpbvtwsNllhlwMWCopaNCYaYbYcYdYeYfYgYhYiYjYkYlYmYnBTYoYpugdCdNdBdTknbwamxbxsxneognhckmhsindadbmimsosesxthzulxonx5iHCNRNPNDccuthlYAYBYCYDYEYFYGnsncNLptxr^F^K^O^U^Z^^$)-38 
> Something similar can also be seen by running lua5.2's REPL in the
> mips64el chroot on etler.debian.org.  Just start it up and then exit.

The problem is that the lua5.2 package in debian adds symbol versioning
to the lua5.2 binary. By doing so it fails to correctly export the 
_IO_stdin_used symbol added by the GNU libc.

The patch below fixes the problem.

Aurelien


diff -Nru lua5.2-5.2.4/debian/version-script lua5.2-5.2.4/debian/version-script
--- lua5.2-5.2.4/debian/version-script
+++ lua5.2-5.2.4/debian/version-script
@@ -152,6 +152,16 @@
luaopen_package;
luaopen_string;
luaopen_table;
+
+   /* The _IO_stdin_used symbol is used by the GNU libc determine
+  which version of the I/O function should be used.  Not
+  exporting it means that the "old" version is used, causing
+  crashes or other issues on some architectures.  It should be
+  exported as an anonymous tag, but ld does not support mixing
+  anonymous version tags with other version tags.  Fortunately
+  the GNU libc is able to cope with the symbol having the wrong
+  version tag.  */
+   _IO_stdin_used;
local :
*;
 };

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net

Bug#828636: Pending fixes for bugs in the libembperl-perl package

2016-06-26 Thread pkg-perl-maintainers

tag 828636 + pending
thanks

Some bugs in the libembperl-perl package are closed in revision
1be07d0920e81edc12efcb9aed0e50b4c7f1710f in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libembperl-perl.git/commit/?id=1be07d0

Commit message:

debian/rules: drop special handling of German manpages.

They are gone, and the machinery causes problems for reproducible builds.

Thanks: Reiner Herrmann for the bug report and patch.
Closes: #828636

Bug#828636: [Reproducible-builds] Bug#828636: libembperl-perl: please make the build reproducible

2016-06-26 Thread Reiner Herrmann

On Sun, Jun 26, 2016 at 05:07:54PM +0200, Axel Beckert wrote:
> > In one build the manpage Embperl::Syntax::POD.3pm is incorrectly sorted
> > to the German manpages (Embperl::FeaturesD too), because their names end
> > with D.
> 
> Why only in one build? Due to different locale settings? Anyway, if
> there's a way that Embperl::Syntax::POD is installed as
> /usr/share/man/de/man3/Embperl::Syntax::PO.3pm.gz, that's clearly a
> bug and deserves a higher severity than just wishlist.

Why this happens only in one build is also not yet clear to me.

> > As the package provides no German manpages anyway,
> 
> Sorry, but that's wrong:
> 
> → dpkg -L libembperl-perl | egrep man/de/man./
> /usr/share/man/de/man3/Embperl::Features.3pm.gz
> → man /usr/share/man/de/man3/Embperl::Features.3pm.gz
> 
> That's clearly my mother tongue. :-)

Sorry, I assumed Embperl::Features was also misdetected (because the
original file ends with D) and haven't looked into it.

> > -   # move German manpages to usr/share/man/de/man{1,2,3}
> > -   @set -e;\
> > -   for f in $(TMP)/usr/share/man/man3/*[a-z]D.3pm; do \
> > -   f_de=`echo $$f | sed 
> > 's,man\(.\)/\([^/]*\)D\.\([^/]*\)$$,de/man\1/\2.\3,'` ;\
> > -   echo "mv $$f $$f_de" ;\
> > -   mv $$f $$f_de ;\
> > -   done
> 
> I currently fail to see why this can catch Embperl::Syntax::POD in one
> build, but not in another. IMHO this should happen with every build.
> Will investigate.

I'm also not sure, but I can imagine it's related to the locale and
*[a-z] works somewhat differently.


signature.asc
Description: Digital signature

Bug#828638: emacs24: Bug in bytecompilation of ob-core.el

2016-06-26 Thread Remi Vanicat

Package: emacs24
Version: 24.4+1-5
Severity: normal

Dear Maintainer,

When trying to evaluate an org SRC block on a file edited remotely
through tramp, it failed with the error

org-babel-local-file-name: Invalid function: with-parsed-tramp-file-name

The problem seem to be that ob-core.el use the
with-parsed-tramp-file-name macro as if it was a function.

Adding

(eval-when-compile
(require 'tramp))

at beginning of the file should fix this.

Note that org-mode from the org-mode unstable package don't have this
bug, but Emacs from sid has it.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 8.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable'), (150, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages emacs24 depends on:
ii  emacs24-bin-common 24.4+1-5
ii  gconf-service  3.2.6-3
ii  libacl12.2.52-2
ii  libasound2 1.0.28-1
ii  libatk1.0-02.14.0-1
ii  libc6  2.19-18+deb8u4
ii  libcairo-gobject2  1.14.0-2.1+deb8u1
ii  libcairo2  1.14.0-2.1+deb8u1
ii  libdbus-1-31.8.20-0+deb8u1
ii  libfontconfig1 2.11.0-6.3
ii  libfreetype6   2.5.2-3+deb8u1
ii  libgconf-2-4   3.2.6-3
ii  libgdk-pixbuf2.0-0 2.31.1-2+deb8u5
ii  libgif44.1.6-11+deb8u1
ii  libglib2.0-0   2.42.1-1+b1
ii  libgnutls-deb0-28  3.3.8-6+deb8u3
ii  libgomp1   4.9.2-10
ii  libgpm21.20.4-6.1+b2
ii  libgtk-3-0 3.14.5-1+deb8u1
ii  libice62:1.0.9-1+b1
ii  libjpeg62-turbo1:1.3.1-12
ii  libm17n-0  1.6.4-3
ii  libmagickcore-6.q16-2  8:6.8.9.9-5+deb8u3
ii  libmagickwand-6.q16-2  8:6.8.9.9-5+deb8u3
ii  libotf00.9.13-2
ii  libpango-1.0-0 1.36.8-3
ii  libpangocairo-1.0-01.36.8-3
ii  libpng12-0 1.2.50-2+deb8u2
ii  librsvg2-2 2.40.5-1+deb8u2
ii  libselinux12.3-2
ii  libsm6 2:1.2.2-1+b1
ii  libtiff5   4.0.3-12.3+deb8u1
ii  libtinfo5  6.0+20160319-2+b1
ii  libx11-6   2:1.6.2-3
ii  libxft22.3.2-1
ii  libxinerama1   2:1.1.3-1+b1
ii  libxml22.9.1+dfsg1-5+deb8u2
ii  libxpm41:3.5.11-1+b1
ii  libxrandr2 2:1.4.2-1+b1
ii  libxrender11:0.9.8-1+b1
ii  zlib1g 1:1.2.8.dfsg-2+b1

emacs24 recommends no packages.

Versions of packages emacs24 suggests:
ii  emacs24-common-non-dfsg  24.4+1-2

-- no debconf information

-- 
Rémi Vanicat

Bug#828635: Pending fixes for bugs in the libnet-tclink-perl package

2016-06-26 Thread pkg-perl-maintainers

tag 828635 + pending
thanks

Some bugs in the libnet-tclink-perl package are closed in revision
8f2b28a46fafc3d3556ee7137e4b632d04fc90c4 in branch 'master' by gregor
herrmann

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/libnet-tclink-perl.git/commit/?id=8f2b28a

Commit message:

Add patch from Reiner Herrmann to make build reproducible.

Closes: #828635

Bug#828636: [Reproducible-builds] Bug#828636: libembperl-perl: please make the build reproducible

2016-06-26 Thread Axel Beckert

Control: tag -1 - patch
Control: severity -1 normal

Hi Reiner,

Reiner Herrmann wrote:
> While working on the "reproducible builds" effort [1], we have noticed
> that libembperl-perl could not be built reproducibly.

Thanks for the examination and the bug report.

> In one build the manpage Embperl::Syntax::POD.3pm is incorrectly sorted
> to the German manpages (Embperl::FeaturesD too), because their names end
> with D.

Why only in one build? Due to different locale settings? Anyway, if
there's a way that Embperl::Syntax::POD is installed as
/usr/share/man/de/man3/Embperl::Syntax::PO.3pm.gz, that's clearly a
bug and deserves a higher severity than just wishlist.

> As the package provides no German manpages anyway,

Sorry, but that's wrong:

→ dpkg -L libembperl-perl | egrep man/de/man./
/usr/share/man/de/man3/Embperl::Features.3pm.gz
→ man /usr/share/man/de/man3/Embperl::Features.3pm.gz

That's clearly my mother tongue. :-)

> I think the part in debian/rules, which moves the manpages can be
> safely removed.

I disagree at least with the reasoning here.

I nevertheless think, that if Embperl::Features.3pm is the only German
man page in the source package, we can remove it from the binary
package without much impact since that's the kind of documentation you
usually read _before_ installing the package, e.g. online on the
upstream website.

> - # move German manpages to usr/share/man/de/man{1,2,3}
> - @set -e;\
> - for f in $(TMP)/usr/share/man/man3/*[a-z]D.3pm; do \
> - f_de=`echo $$f | sed 
> 's,man\(.\)/\([^/]*\)D\.\([^/]*\)$$,de/man\1/\2.\3,'` ;\
> - echo "mv $$f $$f_de" ;\
> - mv $$f $$f_de ;\
> - done

I currently fail to see why this can catch Embperl::Syntax::POD in one
build, but not in another. IMHO this should happen with every build.
Will investigate.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#827721: apt-cacher-ng stalls on upgrade

2016-06-26 Thread Eduard Bloch

Control: forcemerge 825154 827721
Control: tags 827721 +pending

Hallo,
* Joerg Dorchain [Mon, Jun 20 2016, 10:17:20AM]:

> Here, Acquire::http::Proxy setting points to the apt-cacher-ng
> itself running on the local machine. This stalls, as at this time
> of the upgrade cycle, the old apt-cacher-ng version has been
> stopped by apt-get, but the new version has not yet been started.

This will be solved by not stopping acng during upgrades.

Regards,
Eduard.

Bug#790969: Same here...

2016-06-26 Thread Andreas Heinlein

I came acrosss this bug since it describes exactly my problem - except
that I can rule out any hardware fault.

My setup is working fine under Ubuntu 12.04 with Kernel 3.13 and LIRC
0.9.0. I installed Debian 8.5 on the same machine on another partition,
using the same lircd.conf and getting exactly the problems that are
describe above. I am using kernel 4.6 from jessie-backports.

I too have a One4All remote, namely URC-6440.

I would be glad to help solve this problem, as it is a real show-stopper.

Bug#828072: Pending fixes for bugs in the golang-gopkg-ini.v1 package

2016-06-26 Thread pkg-go-maintainers

tag 828072 + pending
thanks

Some bugs in the golang-gopkg-ini.v1 package are closed in revision
ec7195ca60531b8d491bc996fedd97f5f73487d0 in branch 'master' by
Martín Ferrari

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/golang-gopkg-ini.v1.git/commit/?id=ec7195c

Commit message:

Use new features of dh-golang, and only install relevant files. Clean up 
properly after tests. Thanks to Chris Lamb for the patch.  Closes: #828072.

Bug#825382: java.io.IOException: Transport scheme NOT recognized: [stomp]

2016-06-26 Thread Florian Ernst

Hello,

On Sun, Jun 26, 2016 at 03:39:51PM +0200, Markus Koschany wrote:
> the stomp module is not activated in Debian's Stretch version and in
> Jessie it didn't exist as a separate module. I have just enabled it and
> will upload a new package soon. We had to disable more modules due to
> missing dependencies in Debian. See also README.Debian. [...]

True, true, I should have noticed that this is actually documented in
libactivemq-java/README.Debian. However, I didn't even check for such a
README as the package description clearly states:

| This message broker supports :
|  * [...]
|  * OpenWire (cross language wire protocol) and
|Stomp (Streaming Text Orientated Messaging Protocol) protocols

In the light of this I'd suggest to keep the package description in sync
with the actual capabilities provided by the package(s) lest other
people experience similar misunderstanding.

> Thank you for testing ActiveMQ.

Thank you for your reply and the pending fix.

Regards,
Flo

signature.asc
Description: PGP signature

Bug#828637: [zhcon] --utf8 functionality broken

2016-06-26 Thread Lumin

Package: zhcon
Version: 1:0.2.6-10
Severity: normal

Hi,

zhcon for jessie cannot even correctly parse the `--utf8` option, and the
usage of `--utf8` will trigger an abort.

-- 
Best,
Lumin

Bug#814426: sympa: New upstream version available (6.2.12)

2016-06-26 Thread Jonas Smedegaard

Quoting Jérôme Lebleu (2016-06-26 16:02:22)
> Hi Jonas,
> 
> On Sat, 25 Jun 2016 13:45:22 +0200 Jonas Smedegaard  wrote:
> > Quoting Jérôme Lebleu (2016-06-25 11:22:11)
> >> I've just never contributed yet and I'm not a Debian developer too 
> >> - but after reading https://www.debian.org/devel/join/ it seems 
> >> that it's not required and even a good gateway, or I'm wrong?
[...]
> > At a minimum you can propose patches by email.
[...]
> > Here are some pointers to get you started: 
> > https://alioth.debian.org/projects/pkg-sympa/ 
> > https://wiki.debian.org/Alioth/FAQ 
> > https://wiki.debian.org/Alioth/SSH#Logging_in_for_the_first_time 
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sympa-devel 
> > https://tracker.debian.org/pkg/sympa 
> > http://anonscm.debian.org/gitweb/?p=collab-maint/sympa.git
> > 
> > (hmm, which reveals: We really could use a nice wiki intro page for our 
> > team at the Debian wiki...)
[...]
> Thank you for all of this information, links and others! :-)
> 
> I've subscribed to the pkg-sympa-devel mailing list and created an 
> account at Alioth (I think I understood what you mean by "don't try 
> make sens of Alioth web interface"...!).

Great!


> I'll wait until Emmanuel has time to push his 6.2 branch in order to 
> see if I can help - and how, and proposing you a first patch by email 
> before requesting membership to your Alioth group.
>
> Anyway, I'm already delighted with our few exchanges and impatient to 
> start contributing!

Well, one thing you need not wait for - on the contrary, in fact: 
(Create a wiki account, and) add a page for our team at the Debian wiki, 
and then link it to https://wiki.debian.org/Teams (where you can get 
inspiration from the numerous other teams on what is sensible to write 
on such page. :-)


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#826089: [check-all-the-things] 02/02: Only act on arguments once when parsing text for the -c/-f options

2016-06-26 Thread Paul Wise

On Sun, 2016-06-26 at 16:40 +0200, Jakub Wilk wrote:

> After this commit, the command
> 
> check-all-the-things -f=-network
> 
> no longer disables network access. :-(

There are more bugs introduced by it too, working on fixing that now.

> I don't think there's a sane way to fix #826089 without bringing back 
> distinction between topical groups and flags indicating potentially 
> unwanted behavior. (I don't like the name "flags"; I'd call them 
> "inhibitors" or something.)

Bug #826089 happens with the code that had both -g and -f so I don't
think bringing back groups will help at all.

-- 

bye,
pabs

https://wiki.debian.org/PaulWise


signature.asc
Description: This is a digitally signed message part

Bug#828636: libembperl-perl: please make the build reproducible

2016-06-26 Thread Reiner Herrmann

Source: libembperl-perl
Version: 2.5.0-6
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Hi!

While working on the "reproducible builds" effort [1], we have noticed
that libembperl-perl could not be built reproducibly.
In one build the manpage Embperl::Syntax::POD.3pm is incorrectly sorted
to the German manpages (Embperl::FeaturesD too), because their names end
with D.
As the package provides no German manpages anyway, I think the part in
debian/rules, which moves the manpages can be safely removed.

Regards,
 Reiner

[1]: https://wiki.debian.org/ReproducibleBuilds
diff --git a/debian/rules b/debian/rules
index f643b0b..ab91682 100755
--- a/debian/rules
+++ b/debian/rules
@@ -27,14 +27,6 @@ override_dh_auto_install: $(POD2TEXT)
 	# install by default
 	install -m 755 *cgi.pl debian/libembperl-perl/usr/lib/cgi-bin/
 
-	# move German manpages to usr/share/man/de/man{1,2,3}
-	@set -e;\
-	for f in $(TMP)/usr/share/man/man3/*[a-z]D.3pm; do \
-	f_de=`echo $$f | sed 's,man\(.\)/\([^/]*\)D\.\([^/]*\)$$,de/man\1/\2.\3,'` ;\
-	echo "mv $$f $$f_de" ;\
-	mv $$f $$f_de ;\
-	done
-
 	# ship Apache config in mods-available
 	sed -e 's,@ARCHLIB@,$(ARCHLIB),g' debian/zembperl.load.in > debian/zembperl.load
 	install -m 644 debian/zembperl.conf debian/zembperl.load \

Bug#826089: [check-all-the-things] 02/02: Only act on arguments once when parsing text for the -c/-f options

2016-06-26 Thread Jakub Wilk


* Paul Wise , 2016-06-26, 09:45:

commit 8f70b2e913bf82c7bd2eea5a006e95dbef843063
Author: Paul Wise 
Date:   Sun Jun 26 11:41:56 2016 +0200

   Only act on arguments once when parsing text for the -c/-f options


After this commit, the command

check-all-the-things -f=-network

no longer disables network access. :-(


I don't think there's a sane way to fix #826089 without bringing back 
distinction between topical groups and flags indicating potentially 
unwanted behavior. (I don't like the name "flags"; I'd call them 
"inhibitors" or something.)


--
Jakub Wilk

Bug#828398: libmongoc: FTBFS with openssl 1.1.0

2016-06-26 Thread A. Jesse Jiryu Davis

Thanks; we're tracking this in the upstream bug tracker here:

https://jira.mongodb.org/browse/CDRIVER-1066

On Sun, Jun 26, 2016 at 6:22 AM, Kurt Roeckx  wrote:
> Source: libmongoc
> Version: 1.3.5-1
> Severity: important
> Control: block 827061 by -1
>
> Hi,
>
> OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
> OpenSSL this package fail to build.  A log of that build can be found at:
> https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/libmongoc_1.3.5-1_amd64-20160529-1442
>
> On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of 
> the
> reasons why it might fail.  There are also updated man pages at
> https://www.openssl.org/docs/manmaster/ that should contain useful 
> information.
>
> There is a libssl-dev package available in experimental that contains a recent
> snapshot, I suggest you try building against that to see if everything works.
>
> If you have problems making things work, feel free to contact us.
>
>
> Kurt

Bug#811970: blackbox: FTBFS with GCC 6: symbol changes

2016-06-26 Thread Herbert Fortes

Hi,

On Tue, 19 Jan 2016 20:09:51 -0800 Martin Michlmayr  wrote:
> Package: blackbox
> Version: 0.70.1-30
> Severity: important
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-6 gcc-6-symbols
> 
> This package fails to build with GCC 6.  GCC 6 has not been released
> yet, but it's expected that GCC 6 will become the default compiler for
> stretch.
> 
> Note that only the first error is reported; there might be more.  You
> can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
> you can set CC=gcc-6 CXX=g++-6 explicitly.

I am trying to fix this bug.



regards,
-- 

signature.asc
Description: This is a digitally signed message part

Bug#828625: nethack-console: wizard mode permanently identify does not works on armhf port

2016-06-26 Thread James Cowgill

Control: forwarded -1 devt...@nethack.org
Control: tags -1 pending

Hi,

On Sun, 2016-06-26 at 20:02 +0800, Mo Jun wrote:
> Package: nethack-console
> Version: 3.6.0-3
> Severity: normal
> Tags: patch
> 
> Dear Maintainer,
> 
> 1. This bug is only found on armhf port; it is not found on amd64 port.
>   It can be reproduced on a chroot Debian system on a ARMv7 smart phone
>   and on a full Debian system in a QEMU virtual machine.
[...]
>   When ^I is pressed in the Debug Identify menu, the identifier will be
>   returned by display_pickinv(). And wiz_identify() will check whether the
>   return value of display_pickinv() equals -1(src/cmd.c:595):
>    if (display_inventory((char *) 0, TRUE) == -1)
>   then determine to fully identify all items or do nothing.
> 
>   However the type char is unsigned by default on arm port. "any.a_char = -1;"
>   will set any.a_char to 255 actually on arm port(this can be verified
> by using gdb), so
>   that above if statement will never success, and the permanent wizard 
> identify
>   will never be performed.

Your reasoning seems perfectly sound to me, and I can reproduce the bug
on one of Debian's armhf porterboxes. I've sent an email to the Nethack
devteam about this bug, and I'll upload your patch in a few moments.

Thanks a lot!
James

signature.asc
Description: This is a digitally signed message part

Bug#828618: zeroinstall-injector: FTBFS with openssl 1.1.0

2016-06-26 Thread Kurt Roeckx

block 828618 by 828462
thanks

On Sun, Jun 26, 2016 at 03:15:30PM +0100, Thomas Leonard wrote:
> 
> I don't mind. I guess blocks might be better, to remind me to test it
> when the ocaml-ssl bug is fixed.

So I've set that.

Bug#828618: zeroinstall-injector: FTBFS with openssl 1.1.0

2016-06-26 Thread Thomas Leonard

On 26 June 2016 at 13:15, Kurt Roeckx  wrote:
> On Sun, Jun 26, 2016 at 12:20:33PM +0100, Thomas Leonard wrote:
>> On 26 June 2016 at 11:24, Kurt Roeckx  wrote:
>> > Hi,
>> >
>> > OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
>> > OpenSSL this package fail to build.  A log of that build can be found at:
>> > https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/zeroinstall-injector_2.10-2_amd64-20160530-2117
>> >
>> > On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various 
>> > of the
>> > reasons why it might fail.  There are also updated man pages at
>> > https://www.openssl.org/docs/manmaster/ that should contain useful 
>> > information.
>> >
>> > There is a libssl-dev package available in experimental that contains a 
>> > recent
>> > snapshot, I suggest you try building against that to see if everything 
>> > works.
>> >
>> > If you have problems making things work, feel free to contact us.
>>
>> The problem appears to be in ocaml-ssl. See:
>>
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828462
>
> So should it just be merged, or do you want to have 1 block the
> other?

I don't mind. I guess blocks might be better, to remind me to test it
when the ocaml-ssl bug is fixed.

Thanks,


-- 
talex5 (GitHub/Twitter)http://roscidus.com/blog/
GPG: DA98 25AE CAD0 8975 7CDA  BD8E 0713 3F96 CA74 D8BA

Bug#828088: licensecheck invokes find with -follow

2016-06-26 Thread Dominique Dumont

On Friday 24 June 2016 22:51:56 Sandro Mani wrote:
>   I think [-follow] should be removed, for
> three reasons.  Reason 1: self loops like the one in giac make find, and
> therefore licensecheck, fail.  Reason 2: symlinks can point anywhere.  Do
> you really want to let licensecheck run over arbitrary parts of the
> filesystem?  Reason 3: every file in a package *should* be reachable
> without traversing symlinks at all.  (If fedora-review doesn't have a check
> for that, it probably should.)

I agree with point 2 above. 

A symlinks either points:
- inside the scanned package and the file will be found by find with another 
 path (furthermote, using -follow may lead to duplicate results)
- a symlink points in another package and it license should be covered by 
 the license description of the other package.

The commit [1] that added -follow with the scan directory feature does not 
mention any specific reason to use -follow option.

All in all, I think -follow option should be removed.

Thoughts ?

All the best

[1] 
https://anonscm.debian.org/cgit/collab-maint/devscripts.git/commit/?id=ffd90771b2a4ebd22bc3e27d2415112fbc506571
-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

< 1 2 3 4 5 6 7 >

101 - 200 of 671 matches

Mail list logo