date:20160120

Package: z88dk
Severity: minor
Tags: patch
User: pkg-llvm-t...@lists.alioth.debian.org
Usertags: clang-ftbfs

Hello,

Using the rebuild infrastructure, your package fails to build with clang
(instead of gcc).

Detected this kind of error:
http://clang.debian.net/status.php?version=3.6.0=FUNCTION_RETURNS_VALUE

Full build log is available here:
http://clang.debian.net/logs/2015-03-25/z88dk_1.8.ds1-10_unstable_clang.log

I have attached a patch to fix this error.


Regards,
--Arthur Marble


-- System Information:
Debian Release: sid (unstable)
Architecture: amd64 (x86_64)
Kernel: Linux 4.2.0-1-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE="en_US.UTF-8"
Shell: /bin/sh linked to /bin/dash
Compiler: Debian clang version 3.6.2-3 (based on LLVM 3.6.2)
--- a/src/cpp/cpp2.c
+++ b/src/cpp/cpp2.c
@@ -336,14 +336,14 @@
 else {
 compiling = FALSE;
 }
-return;
+return 0;
 
 badif:  cerror("#if, #ifdef, or #ifndef without an argument", NULLST);
 #if !OLD_PREPROCESSOR
 skipnl();   /* Prevent an extra */
 unget();/* Error message*/
 #endif
-return;
+return 0;
 }
 
 FILE_LOCAL
@@ -402,10 +402,10 @@
 goto incerr;
 }
 else if (openinclude(def_filename, (delim == '"')))
-return;
+return 0;
 #else
 if (openinclude(work, (delim == '"')))
-return;
+return 0;
 #endif
 /*
  * No sense continuing if #include file isn't there.
@@ -413,7 +413,7 @@
 cfatal("Cannot open include file \"%s\"", work);
 
 incerr: cerror("#include syntax error", NULLST);
-return;
+return 0;
 }
 
 FILE_LOCAL int
--- a/src/cpp/cpp4.c
+++ b/src/cpp/cpp4.c
@@ -211,7 +211,7 @@
 	if (old != NULL)			/* We don't need the	*/
 		free(old);			/* old definition now.	*/
 	}	 
-	return;
+	return 0;
 
 bad_define:
 	cerror("#define syntax error", NULLST);
@@ -236,7 +236,7 @@
 	for (i = 0; i < nargs; i++) {		/* For each argument	*/
 	if (streq(parlist[i], token)) {	/* If it's known	*/
 		save(i + MAC_PARM);		/* Save a magic cookie	*/
-		return;/* And exit the search	*/
+		return 0;			/* And exit the search	*/
 	}
 	}
 	if (streq(dp->name, token))		/* Macro name in body?	*/
@@ -295,7 +295,7 @@
 
 	wp = workp;			/* Here's where it starts	*/
 	if (!scanstring(delim, save))
-	return;			/* Exit on scanstring error	*/
+	return 0;			/* Exit on scanstring error	*/
 	workp[-1] = EOS;		/* Erase trailing quote		*/
 	wp++;/* -> first string content byte	*/ 
 	for (i = 0; i < nargs; i++) {
@@ -304,7 +304,7 @@
 		*wp++ = (i + MAC_PARM);		/* Make a formal marker	*/
 		*wp = wp[-3];			/* Add on closing quote	*/
 		workp = wp + 1;			/* Reset string end	*/
-		return;
+		return 0;
 	}
 	}
 	workp[-1] = wp[-1];		/* Nope, reset end quote.	*/
@@ -402,7 +402,7 @@
 		} while (infile != NULL && infile->fp == NULL);
 		unget();
 		recursion = 0;
-		return;
+		return 0;
 	}
 	}
 	/*
@@ -451,7 +451,7 @@
 		unget();
 		cwarn("Macro \"%s\" needs arguments", tokenp->name);
 		fputs(tokenp->name, stdout);
-		return;
+		return 0;
 	}
 	else if (expcollect()) {		/* Collect arguments	*/
 		if (tokenp->nargs != nargs) {	/* Should be an error?	*/
--- a/src/cpp/cpp6.c
+++ b/src/cpp/cpp6.c
@@ -315,7 +315,7 @@
 	(*outfun)('.');			/* Always out the dot	*/
 	if (type[(c = get())] != DIG) {	/* If not a float numb,	*/
 		unget();			/* Rescan strange char	*/
-		return;/* All done for now	*/
+		return 0;			/* All done for now	*/
 	}
 	}	/* End of float test	*/
 	else if (c == '0') {			/* Octal or hex?	*/
@@ -851,7 +851,7 @@
 	register FILEINFO	*file;
 
 	if ((file = infile) == NULL)
-	return;			/* Unget after EOF		*/
+	return 0;			/* Unget after EOF		*/
 	if (--file->bptr < file->buffer)
 	cfatal("Too much pushback", NULLST);
 	if (*file->bptr == '\n')	/* Ungetting a newline?		*/
@@ -917,7 +917,7 @@
 	fprintf(stderr, format, (int) arg);
 	putc('\n', stderr);
 	if ((file = infile) == NULL)
-	return;/* At end of file	*/
+	return 0;/* At end of file	*/
 	if (file->fp != NULL) {
 	tp = file->buffer;			/* Print current file	*/
 	fprintf(stderr, "%s", tp);		/* name, making sure	*/

Bug#810924: chmod Patch

2016-01-20 Thread Mark Hindley

On Wed, Jan 20, 2016 at 06:51:13PM +0100, ch...@trash-mail.com wrote:
> 
> 

> Sorry inserting two times the chmod $tmpfile, oct(600); does not help.

Sorry, my mistake. I gave you the arguments the wrong way round.
Please try with

 chmod oct(600), $tmpfile;

Thanks.

Mark

Bug#812161: metview: FTBFS with GCC 6: reference to '...' is ambiguous

Package: metview
Version: 4.6.1-4
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-reference-ambiguous

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.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> [  7%] Building CXX object src/libUtil/CMakeFiles/Util.dir/MvFlextra.cc.o
> cd /<>/debian/build/src/libUtil && /usr/bin/c++   
> -DH_INCLUDES_CC -DLITTLE_END -DMETVIEW -DMETVIEW_QT5 -DQT_NO_DEBUG_OUTPUT 
> -DR64 -DUSE_NEW_IO -I/<>/debian/build/module 
> -I/<>/src/libMetview -I/<>/src/libUtil 
> -I/<>/src/libMarsClient -I/<>/src/libMars 
> -I/<>/debian/build/src/libMars -I/<>/src 
> -I/<>/src/libFTimeUtil -I/<>/src/libMvNetCDF 
> -I/usr/include/x86_64-linux-gnu/qt5 
> -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets 
> -I/usr/include/x86_64-linux-gnu/qt5/QtGui 
> -I/usr/include/x86_64-linux-gnu/qt5/QtCore 
> -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 
> -I/usr/include/x86_64-linux-gnu/qt5/QtXml 
> -I/usr/include/x86_64-linux-gnu/qt5/QtXmlPatterns 
> -I/usr/include/x86_64-linux-gnu/qt5/QtNetwork 
> -I/usr/include/x86_64-linux-gnu/qt5/QtPrintSupport -I/usr/lib/include 
> -I/usr/include/hdf5/serial  -g -O2 -fPIE -fstack-protector-strong -Wdate-time 
> -D_FORTIFY_SOURCE=
> 2  -pipe -fpermissive -Wno-write-strings -Wno-deprecated -O3 -DNDEBUG -fPIC   
> -o CMakeFiles/Util.dir/MvFlextra.cc.o -c 
> /<>/src/libUtil/MvFlextra.cc
> In file included from /<>/src/libMarsClient/mars.h:203:0,
>  from /<>/src/libMetview/MvDate.h:13,
>  from /<>/src/libUtil/MvFlextra.cc:12:
> /<>/debian/build/src/libMars/rpcmars.h:38:2: error: reference to 
> 'void_t' is ambiguous
>   void_t data;
>   ^~
> 
> /<>/debian/build/src/libMars/rpcmars.h:19:15: note: candidates 
> are: typedef void* void_t
>  typedef void *void_t;
>^~
> 
> In file included from /usr/include/c++/6/bits/move.h:57:0,
>  from /usr/include/c++/6/bits/nested_exception.h:40,
>  from /usr/include/c++/6/exception:171,
>  from /usr/include/c++/6/ios:39,
>  from /usr/include/c++/6/istream:38,
>  from /usr/include/c++/6/fstream:38,
>  from /<>/src/libUtil/MvFlextra.h:13,
>  from /<>/src/libUtil/MvFlextra.cc:10:
> /usr/include/c++/6/type_traits:2536:44: note: template ...> using void_t = void
>template using void_t = void;
> ^
> 
> /<>/src/libUtil/MvFlextra.cc: In member function 'void 
> MvFlextra::decode()':
> /<>/src/libUtil/MvFlextra.cc:685:59: error: no matching function 
> for call to 'make_pair(std::__cxx11::string&, bool&)'
>pair p=make_pair(comment,cstep);
>^
> 
> In file included from /usr/include/c++/6/bits/stl_algobase.h:64:0,
>  from /usr/include/c++/6/bits/char_traits.h:39,
>  from /usr/include/c++/6/ios:40,
>  from /usr/include/c++/6/istream:38,
>  from /usr/include/c++/6/fstream:38,
>  from /<>/src/libUtil/MvFlextra.h:13,
>  from /<>/src/libUtil/MvFlextra.cc:10:
> /usr/include/c++/6/bits/stl_pair.h:406:5: note: candidate: template _T1, class _T2> constexpr std::pair std::__decay_and_strip<_Tp>::__type, typename 
> std::__decay_and_strip<_T2>::__type> std::make_pair(_T1&&, _T2&&)
>  make_pair(_T1&& __x, _T2&& __y)
>  ^
> 
> /usr/include/c++/6/bits/stl_pair.h:406:5: note:   template argument 
> deduction/substitution failed:
> /<>/src/libUtil/MvFlextra.cc:685:59: note:   cannot convert 
> 'comment' (type 'std::__cxx11::string {aka 
> std::__cxx11::basic_string}') to type 
> 'std::__cxx11::basic_string&&'
>pair p=make_pair(comment,cstep);
>^
> 
> src/libUtil/CMakeFiles/Util.dir/build.make:305: recipe for target 
> 'src/libUtil/CMakeFiles/Util.dir/MvFlextra.cc.o' failed
> make[3]: *** [src/libUtil/CMakeFiles/Util.dir/MvFlextra.cc.o] Error 1
> make[3]: Leaving directory '/<>/debian/build'

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

Bug#812160: qtwebkit: FTBFS with GCC 6: symbol changes

Package: qtwebkit
Version: 2.3.4.dfsg-6
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.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
>dh_makeshlibs -O--parallel -O--fail-missing 
> -O--dbg-package=libqtwebkit4-dbg
> dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libqtwebkit4/DEBIAN/symbols doesn't match 
> completely debian/libqtwebkit4.symbols
> --- debian/libqtwebkit4.symbols (libqtwebkit4_2.3.4.dfsg-6_amd64)
> +++ dpkg-gensymbolsYBbUq1 2016-01-21 04:29:11.397038924 +
> @@ -939,4 +939,4 @@
>   (c++)"non-virtual thunk to QGraphicsWebView::~QGraphicsWebView()@Base" 
> 2.1.0~2011week13
>   (c++)"non-virtual thunk to QWebInspector::~QWebInspector()@Base" 
> 2.1.0~2011week13
>   (c++)"non-virtual thunk to QWebView::~QWebView()@Base" 2.1.0~2011week13
> - nullptr@Base 2.3.2
> +#MISSING: 2.3.4.dfsg-6# nullptr@Base 2.3.2
> dh_makeshlibs: failing due to earlier errors
> debian/rules:40: recipe for target 'binary' failed
> make: *** [binary] Error 2

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

Bug#812162: iceweasel: FTBFS with GCC 6: size of array

Package: iceweasel
Version: 43.0.4-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6

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.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> /<>/build-browser/_virtualenv/bin/python 
> /<>/config/expandlibs_exec.py --uselist --  g++ -Wdate-time 
> -D_FORTIFY_SOURCE=2 -Wall -Wempty-body -Woverloaded-virtual -Wsign-compare 
> -Wwrite-strings -Wno-invalid-offsetof -Wcast-align -fstack-protector-strong 
> -Wformat -Werror=format-security -fno-exceptions -fno-strict-aliasing 
> -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -fno-math-errno 
> -std=gnu++0x -pthread -pipe  -DNDEBUG -DTRIMMED -g -freorder-blocks -Os 
> -fomit-frame-pointer  -fPIC -shared -Wl,-z,defs -Wl,--gc-sections 
> -Wl,-h,libxul.so -o libxul.so  StaticXULComponentsStart.o   -lpthread  
> -Wl,--as-needed -Wl,--reduce-memory-overheads -Wl,--no-keep-memory 
> -Wl,--stats -Wl,-z,noexecstack -Wl,-z,text -Wl,--build-id 
> -Wl,-version-script,symverscript 
> /<>/toolkit/library/StaticXULComponents.ld
> -Wl,-rpath-link,/<>/build-browser/dist/bin 
> -Wl,-rpath-link,/usr/lib   ../../memory/volatile/libmemory_volatile.a 
> ../../media/
> kiss_fft/libmedia_kiss_fft.a 
> ../../media/libstagefright/libmedia_libstagefright.a 
> ../../security/sandbox/linux/common/libsecurity_sandbox_linux_common.a 
> ../../security/sandbox/linux/glue/libsecurity_sandbox_linux_glue.a 
> ../../security/certverifier/libsecurity_certverifier.a 
> ../../security/pkix/libmozillapkix.a ../../security/apps/libsecurity_apps.a 
> ../../xpcom/typelib/xpt/libxpt.a ../../xpcom/string/libxpcom_string.a 
> ../../xpcom/base/libxpcom_base.a ../../xpcom/ds/libxpcom_ds.a 
> ../../xpcom/io/libxpcom_io.a ../../xpcom/components/libxpcom_components.a 
> ../../xpcom/threads/libxpcom_threads.a 
> ../../xpcom/reflect/xptinfo/libxpcom_reflect_xptinfo.a 
> ../../xpcom/reflect/xptcall/libxpcom_reflect_xptcall.a 
> ../../xpcom/reflect/xptcall/md/unix/libxpcom_reflect_xptcall_md_unix.a 
> ../../chrome/libchrome.a ../../xpcom/build/libxpcom_build.a 
> ../../modules/libpref/libmodules_libpref.a 
> ../../intl/hyphenation/hyphen/libintl_hyphenation_hyphen.a 
> ../../intl/hyphenation/glue/libintl_hyphenation_glue.a 
> ../../intl/locale/libintl_locale.a 
> ../../intl/locale/unix/libintl_locale_unix.a ../../intl/lwbrk/libintl_lwbrk.a 
> ../../intl/strres/libintl_strres.a 
> ../../intl/unicharutil/libintl_unicharutil.a 
> ../../intl/unicharutil/util/internal/libintl_unicharutil_util_internal.a 
> ../../intl/uconv/libintl_uconv.a ../../intl/build/libintl_build.a 
> ../../netwerk/base/libnetwerk_base.a ../../netwerk/cookie/libnetwerk_cookie.a 
> ../../netwerk/dns/libnetwerk_dns.a 
> ../../netwerk/dns/mdns/libmdns/libnetwerk_dns_mdns_libmdns.a 
> ../../netwerk/socket/libnetwerk_socket.a ../../netwerk/mime/libnetwerk_mime.a 
> ../../netwerk/streamconv/libnetwerk_streamconv.a 
> ../../netwerk/streamconv/converters/libnetwerk_streamconv_converters.a 
> ../../netwerk/cache/libnetwerk_cache.a 
> ../../netwerk/cache2/libnetwerk_cache2.a 
> ../../netwerk/protocol/about/libnetwerk_protocol_about.a 
> ../../netwerk/protocol/app/libnetwerk_protocol_app.a 
> ../../netwerk/protocol/data/libnetwerk_protocol_data.a 
> ../../netwerk/protocol/device/libnetwerk_protocol_device.a 
> ../../netwerk/protocol/file/libnetwerk_protocol_file.a 
> ../../netwerk/protocol/ftp/libnetwerk_protocol_ftp.a 
> ../../netwerk/protocol/http/libnetwerk_protocol_http.a 
> ../../netwerk/protocol/res/libnetwerk_protocol_res.a 
> ../../netwerk/protocol/viewsource/libnetwerk_protocol_viewsource.a 
> ../../netwerk/protocol/websocket/libnetwerk_protocol_websocket.a 
> ../../netwerk/protocol/wyciwyg/libnetwerk_protocol_wyciwyg.a 
> ../../netwerk/system/linux/libnetwerk_system_linux.a 
> ../../netwerk/ipc/libnetwerk_ipc.a ../../netwerk/srtp/src/libnksrtp_s.a 
> ../../netwerk/sctp/src/libnksctp_s.a 
> ../../netwerk/sctp/datachannel/libnetwerk_sctp_datachannel.a 
> ../../netwerk/wifi/libnetwerk_wifi.a ../../netwerk/build/libnetwerk_build.a 
> ../../extensions/auth/libextensions_auth.a 
> ../../ipc/chromium/libipc_chromium.a ../../ipc/glue/libipc_glue.a 
> ../../ipc/ipdl/libipc_ipdl.a ../../ipc/testshell/libipc_testshell.a 
> ../../js/ipc/libjs_ipc.a ../../hal/libhal.a 
> ../../js/xpconnect/wrappers/libjs_xpconnect_wrappers.a 
> ../../js/xpconnect/loader/libjs_xpconnect_loader.a 
> ../../js/xpconnect/src/libjs_xpconnect_src.a 
> ../../intl/chardet/libintl_chardet.a 
> ../../media/libyuv/libyuv_libyuv/libyuv.a 
> ../../modules/libjar/libmodules_libjar.a 
>

Bug#812169: ratfor: FTBFS using clang instead of gcc

Package: ratfor
Severity: minor
Tags: patch
User: pkg-llvm-t...@lists.alioth.debian.org
Usertags: clang-ftbfs

Hello,

Using the rebuild infrastructure, your package fails to build with clang
(instead of gcc).

Detected this kind of error:
http://clang.debian.net/status.php?version=3.6.0=FUNCTION_RETURNS_VALUE

Full build log is available here:
http://clang.debian.net/logs/2015-03-25/ratfor_1.0-15_unstable_clang.log

I have attached a patch to fix this error.

Regards,
--Arthur Marble


-- System Information:
Debian Release: sid (unstable)
Architecture: amd64 (x86_64)
Kernel: Linux 4.2.0-1-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE="en_US.UTF-8"
Shell: /bin/sh linked to /bin/dash
Compiler: Debian clang version 3.6.2-3 (based on LLVM 3.6.2)
--- a/rat4.c
+++ b/rat4.c
@@ -364,7 +364,7 @@
 
 	if (gnbtok(token, MAXTOK) != LPAREN) {
 		synerr("missing left paren.");
-		return;
+		return 0;
 	}
 	outstr(token);
 	nlpar = 1;
@@ -1043,13 +1043,13 @@
 			xfer = YES;
 */
 			xfer = NO;
-			return;
+			return 0;
 		}
 	if (token == LEXBREAK)
 		synerr("illegal break.");
 	else
 		synerr("illegal next.");
-	return;
+	return 0;
 }
 
 /*
@@ -1112,7 +1112,7 @@
 	outcon(0);
 	if (gnbtok(token, MAXTOK) != LPAREN) {
 		synerr("missing left paren.");
-		return;
+		return 0;
 	}
 	if (gnbtok(token, MAXTOK) != SEMICOL) {   /* real init clause */
 		pbstr(token);
@@ -1139,7 +1139,7 @@
 nlpar--;
 			if (t == EOF) {
 pbstr(token);
-return;
+return 0;
 			}
 			if (t != NEWLINE && t != UNDERLINE)
 outstr(token);
@@ -1337,7 +1337,7 @@
 {
 	xfer = NO;
 	if (n <= 0 && outp == 0)
-		return;/* don't need unlabeled continues */
+		return 0;   /* don't need unlabeled continues */
 	if (n > 0)
 		outnum(n);
 	outtab();
@@ -1409,7 +1409,7 @@
 int n;
 {
 	if (xfer == YES)
-		return;
+		return 0;
 	outtab();
 	outstr(rgoto);
 	outnum(n);
@@ -1874,7 +1874,7 @@
 
 	if (swtop <= 0) {
 		synerr ("illegal case or default.");
-		return;
+		return 0;
 	}
 	outgo(lab + 1);		/* # terminate previous case */
 	xfer = YES;

Bug#811351: additional request...

* Rick Thomas  [2016-01-20 16:59]:
> > However, Debian probably needs to provide its own documentation
> > how to modify the .dtb (probably some example how to convert the
> > dtb to source with dtc, then how to do the modifications, and
> > compile the source back to dtb).
> 
> Andrew (I think it was) suggested that the instructions for doing
> that could go on Martin’s web page, which anyone who wants to use
> Debian on OpenRD will need to reference anyway.
> 
> Martin, are you willing to do that?

I doubt there's demand for it since there are so few OpenRD users
left, but if there's demadn I can document it.

-- 
Martin Michlmayr
http://www.cyrius.com/

Bug#812148: vftool: FTBFS with clang instead of gcc

Package: vftool
Severity: minor
Tags: patch
User: pkg-llvm-t...@lists.alioth.debian.org
Usertags: clang-ftbfs

Hello,

Using the rebuild infrastructure, your package fails to build with clang
(instead of gcc).

Detected this kind of error:
http://clang.debian.net/status.php?version=3.6.0=FUNCTION_RETURNS_VALUE

Full build log is available here:
http://clang.debian.net/logs/2015-03-25/vftool_2.0alpha-4.1_unstable_clang.log 


I have attached a patch to fix this error.

Regards,
--Arthur Marble


-- System Information:
Debian Release: sid (unstable)
Architecture: amd64 (x86_64)
Kernel: Linux 4.2.0-1-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE="en_US.UTF-8"
Shell: /bin/sh linked to /bin/dash
Compiler: Debian clang version 3.6.2-3 (based on LLVM 3.6.2)
--- a/mka2bkjvf.c
+++ b/mka2bkjvf.c
@@ -172,7 +172,7 @@
 byte b[sizeof(int)], db[sizeof(int)];
 
 if ((ct = getctype(jis, jfmfi)) == 0)
-	return;
+	return 0;
 pl = 3;	/* SET2 jis */
 for (; 0 < curfix->code && curfix->code < jis; curfix++)
 	;
@@ -194,7 +194,7 @@
 } else
 	gl = dgl = 0;
 if (gl == 0 && dgl == 0 && jfmfi->ch[ct].tfmw == jfmfi->ch[0].tfmw)
-	return;
+	return 0;
 if (gl != 0) {
 	n = inttob(b, gl, TRUE);
 	pl += 1+n;
--- a/mkbkv2hjvf.c
+++ b/mkbkv2hjvf.c
@@ -148,7 +148,7 @@
 	if (vc->cc == jis)
 	break;
 if (vc->cc == 0)
-	return;
+	return 0;
 rn = inttob(rb, rdisp-vc->y, TRUE);
 pl += 1+rn;
 dn = inttob(db, ddisp-vc->x, TRUE);
--- a/mkvsyvf.c
+++ b/mkvsyvf.c
@@ -158,7 +158,7 @@
 	sp_end = mirror_end;
 	sp_end_len = mirror_end_len;
 } else
-	return;
+	return 0;
 pl = 3;	/* SET2 cc */
 rn = inttob(rb, rd, TRUE);
 pl += 1+rn;
--- a/mkvsydvf.c
+++ b/mkvsydvf.c
@@ -106,7 +106,7 @@
 	rd = depthratio;
 	dd = -rdisp;
 } else
-	return;
+	return 0;
 pl = 5;	/* DIR 1 SET2 cc */
 rn = inttob(rb, rd, TRUE);
 pl += 1+rn;

Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)

2016-01-20 Thread adrian15


El 18/01/16 a las 12:57, Michal Suchanek escribió:


Unless
the user requests two bootloaders that are incompatible the medium can
be created.

Ignoring bootloaders is not a good idea. If the user requested
something that is not possible the build should report an error and
stop.


Yeah, that it's hard to implement from the perspective of a single
bootloader script. So I decided not to implement it.

You could add an additional script or function named:
check_compatible_bootable_pairs (as you propose) but then you need to
maintain that fictional database each time a new bootloader gets in.

That's why I decide to avoid it using it.

What it's straight-forward to implement is one of the only-secondary
bootloaders finding themselves as a primary bootloader and outputting a
warning message. But, I'm not sure what to put there as a warning. Any
suggestion?


Unsupported bootloader combination or whatever.

It should not be a warning however. The script should avoid making
unbootable medium.

Thanks

Michal


I have implemented: Check_Primary_Bootloader_Role, 
Check_Secondary_Bootloader_Role functions for avoiding non supported 
bootloader combinations on:


https://github.com/adrian15/live-build/tree/efi_support_based_on_debian_cd_rebased

So that part is solved.

(I'll send a proper rebased set of patches in the future).

adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software 
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/

Bug#811802: povray: FTBFS with GCC 6: multiple errors

2016-01-20 Thread Andreas Beckmann

On 2016-01-20 03:07, Martin Michlmayr wrote:
> Usertags: ftbfs-gcc-6 gcc-6-reference-ambiguous

> You may be able to find out more about this issue at
> https://gcc.gnu.org/gcc-6/changes.html

>> g++ -DHAVE_CONFIG_H -I. -I..  -I.. -I../source/backend -I../source/base 
>> -I../source/frontend -I../unix -I../vfe -I../vfe/unix -I/usr/include/SDL 
>> -D_GNU_SOURCE=1 -D_REENTRANT -pthread -I/usr/include/OpenEXR -Wdate-time 
>> -D_FORTIFY_SOURCE=2 -pthread -I/usr/include  -I/usr/include  -pipe 
>> -Wno-multichar -Wno-write-strings -fno-enforce-eh-specs -g -O2 
>> -fstack-protector-strong -Wformat -Werror=format-security -O3 -pthread -c -o 
>> backend/math/hcmplx.o backend/math/hcmplx.cpp
>> In file included from ./backend/control/messagefactory.h:39:0,
>>  from ./backend/frame.h:58,
>>  from backend/scene/atmosph.cpp:35:
>> ./backend/control/renderbackend.h:112:34: error: template argument 2 is 
>> invalid
>>map scenes;

Hi Martin,

I haven't looked into this, yet, but the most prominent change seems to
be the default switch to -std=c++14. Have you tried rebuilding the
failing packages with g++-6 -std=c++11/c++03/c++98/.../gnuXX (not sure
whether the old ones are correctly spelled) to see if that succeeds
somewhere? If additionally information is given like "But it builds
successfully with g++6 -std=c++11" or "And it also fails with g++-6
-std=c++AA/BB/CC/gnuXX/YY/ZZ" that should narrow the place where to
start looking for this problem.


Andreas

... and now I'm thinking how to write a pbuilder hook that switches
gcc/g++ to -6 on-the-fly without having experimental enabled for the
actual build

Bug#812082: Fwd: Bug#812082: rubber: always recompile

2016-01-20 Thread Sebastian Kapfer

Hi,

If you're curious, you can have a look at this branch:
https://github.com/skapfer/rubber/tree/preview

This should not recompile all the time, but has received little testing so far.
Bug reports welcome!

Cheers,
  Sebastian

On Thu, Jan 21, 2016 at 01:34:30AM +0100, Sebastian Kapfer wrote:
> 
> Hi,
> 
> Rubber currently is in overcautious mode since the widely distributed 1.1
> release missed rebuilds in a lot of cases and cause quite some user
> frustration.  Since then, I've been working on rewriting the dependency code, 
> a
> transition which is not quite complete.
> 
> As a result, one compilation is currently always forced.  We're close to 
> fixing
> everything up (BibTeX was a huge mess) - this limitation might well be gone 
> for
> the 1.5 release.
> 
> @Hilmar The linked patch does not fix this.  It just provides more detailed
> messages.  It's worth applying though, same as the other change since 1.4.
> Both are harmless fixes unlikely to break something.
> 
> Cheers
>   Sebastian
> 
> 
> 
> On Wed, Jan 20, 2016 at 10:19:05PM +0100, Preuße, Hilmar wrote:
> > Hallo Sebastian,
> > 
> > eine gesundes neues Jahr!
> > 
> > ich habe einen neuen Case rein bekommen. rubber macht einen Rebuild, obwohl 
> > sich
> > an den Source-File nicht geändert hat. Ja, in den release Notes steht, daß
> > rubber derzeit lieber einmal zuviel, als einmal zuwenig compiliert, aber im
> > aktuellen Fall scheint rubber gar keine Zeitstempel zu prüfen.
> > 
> > Das würde ich mal als nicht FAD qualifizieren. Hilft mir
> > https://git.launchpad.net/rubber/patch/?id=8871e6d40213b63668f34bcd148c30a36a79933a
> > weiter?
> > 
> > Hilmar
> > -- 
> > sigfault
> 
> > Date: Wed, 20 Jan 2016 12:22:52 +0100
> > From: "r.ductor" 
> > To: Debian Bug Tracking System 
> > Subject: Bug#812082: rubber: always recompile
> > X-Mailer: reportbug 6.6.5
> > 
> > Package: rubber
> > Version: 1.4-1
> > Severity: normal
> > 
> > Dear Maintainer,
> > 
> > It is important (for me) to check that the document stack is updated 
> > without unnecessaryly recompile.
> > 
> > In previous versions, when the modification time of the dependencies was in 
> > the correct order,
> > rubber output "nothing to do for ...".
> > 
> > This feature seems lost ("running ps2pdf") and rubber seems to recompile 
> > without necessity. See example below.
> > 
> > Thanks for your time.
> > r.
> > 
> > $ date && ls -lt --time-style=full-iso && rubber -pd -vvv bug 
> > Wed Jan 20 12:11:33 CET 2016
> > total 196
> > -rw-r--r-- 1 anonymous anonymous  21547 2016-01-20 12:10:49.190190490 +0100 
> > bug.pdf
> > -rw-r--r-- 1 anonymous anonymous 159509 2016-01-20 12:10:49.090187074 +0100 
> > bug.ps
> > -rw-r--r-- 1 anonymous anonymous279 2016-01-20 12:10:49.022184750 +0100 
> > bug.aux
> > -rw-r--r-- 1 anonymous anonymous   1096 2016-01-20 12:10:49.022184750 +0100 
> > bug.dvi
> > -rw-r--r-- 1 anonymous anonymous   2546 2016-01-20 12:10:49.022184750 +0100 
> > bug.log
> > -rw-r--r-- 1 anonymous anonymous463 2016-01-20 12:06:54.590175830 +0100 
> > bug.tex
> > This is Rubber version 1.4.
> > [latex] parsing /home/anonymous/CACCA/bug-rubber/bug.tex
> > [latex] script module article registered
> > [latex] end of /home/anonymous/CACCA/bug-rubber/bug.tex
> > [latex] dependencies: ['bug.aux', 
> > '/home/anonymous/CACCA/bug-rubber/bug.tex']
> > [latex] directive: module dvips
> > [latex] built-in module dvips registered
> > [latex] directive: module ps2pdf
> > [latex] built-in module ps2pdf registered
> > [depend] make bug.pdf -> ['bug.ps']
> > [depend] make bug.ps -> ['bug.dvi']
> > [depend] make bug.dvi -> ['bug.aux', 
> > '/home/anonymous/CACCA/bug-rubber/bug.tex']
> > [depend] while making bug.dvi: cyclic dependency on bug.aux (pruned)
> > [latex] building additional files...
> > compiling bug.tex...
> > executing: latex \nonstopmode \input{bug.tex}
> >   with environment: {'TEXINPUTS': '.:.:'}
> > process 3244 (latex) returned 0
> > [latex] running post-compilation scripts...
> > [depend] while making bug.dvi: cyclic dependency on bug.aux (pruned)
> > [depend] while making bug.dvi: contents of bug.aux unchanged, ignoring mtime
> > [depend] while making bug.ps: timestamp of dependency bug.dvi changed, 
> > rebuilding
> > executing: dvips bug.dvi
> > process 3246 (dvips) returned 0
> > [depend] make bug.dvi -> ['bug.aux', 
> > '/home/anonymous/CACCA/bug-rubber/bug.tex']
> > [depend] while making bug.dvi: cyclic dependency on bug.aux (pruned)
> > [depend] while making bug.dvi: contents of bug.aux unchanged, ignoring mtime
> > [depend] while making bug.pdf: timestamp of dependency bug.ps changed, 
> > rebuilding
> > running: ps2pdf bug.ps bug.pdf...
> > [depend] make bug.ps -> ['bug.dvi']
> > [depend] make bug.dvi -> ['bug.aux', 
> > '/home/anonymous/CACCA/bug-rubber/bug.tex']
> > [depend] while making bug.dvi: cyclic dependency on bug.aux (pruned)
> > [depend] while making bug.dvi: contents of bug.aux unchanged, ignoring mtime

Bug#812118: mailagent: Mailbox compression broken with Perl 5.22

2016-01-20 Thread Rafael Laboissiere


* Manoj Srivastava  [2016-01-20 21:12]:


On Wed, Jan 20 2016, Rafael Laboissiere wrote:


Package: mailagent
Version: 1:3.1-81-1
Severity: important


   It might (and then again, it might not) be reassuring to know I
have exactly the same version of perl nd mailagent; and mailagent did 
pass all tests, including the compression tests. I have not seen the 
mail lossage (the defined(@array) is fairly benign, despite the dire 
warning) .


The attached patch fixed the problem for me.  There may have other 
instances of defined(@array) in the code, but I did not check this 
carefully.


The problem with messages that are not dropped in ~/mbox.$user, in case 
of failure, is a separate bug from the one that is addressed by my patch.


Best,

Rafael
--- mailagent-3.1-81.orig/agent/pl/compress.pl
+++ mailagent-3.1-81/agent/pl/compress.pl
@@ -210,7 +210,7 @@
 sub restore {
 	return unless $cf'compress;		# Do nothing if no compress parameter
 	return unless -s $cf'compress;	# No compress list file, or empty
-	 unless defined @compress;	# Initialize array only once
+	 unless @compress;	# Initialize array only once
 	return unless defined $Ext{$cf'comptag};	# Invalid compression tag
 	local($folder) = @_;			# Folder candidate for uncompression
 	&'add_log("candidate folder is $folder") if $'loglvl > 18;

Bug#812072: module 'subprocess' has no attribute 'mswindows'

2016-01-20 Thread Andreas Beckmann

Control: tag -1 sid stretch
Control: block 810136 with -1

On Wed, 20 Jan 2016 16:46:24 +0800 Thomas Goirand  wrote:
> Package: python3-cmd2
> Version: 0.6.7-2

> AttributeError: module 'subprocess' has no attribute 'mswindows'
> 
> Obviously, I'm not running mswindows... :)

seems to be related to python 3.5:

$ python3.4 -m cmd2
$ python3.5 -m cmd2
Traceback (most recent call last):
  File "/usr/lib/python3.5/runpy.py", line 184, in _run_module_as_main
"__main__", mod_spec)
  File "/usr/lib/python3.5/runpy.py", line 85, in _run_code
exec(code, run_globals)
  File "/usr/lib/python3/dist-packages/cmd2.py", line 181, in 
if subprocess.mswindows:
AttributeError: module 'subprocess' has no attribute 'mswindows'


Andreas

Bug#812153: [Pkg-utopia-maintainers] Bug#812153: Bug#812153: policykit-1: allows ordinary users to mount filesystems

On Thu, 2016-01-21 at 04:13 +0100, Michael Biebl wrote:
> This behaviour has been since 2000 or so, since at least the
> introduction of hal and pmount.

Then one has still some 30 years before where it has been different...

> You don't gain anything security wise by not allowing removable media
> to
> be mounted. The only thing it will cause for sure is inconvenience.

As I told you before, this is not true,.. you may have easily have
secured terminals where people can log in, but where they cannot e.g.
physically access such devices.

> Please don't reopen anymore, or I'll ask bts listmaster to block your
> address.

Ah quite funny... "do as I want... or I use dictatorship methods"...

It's quite disturbing when a real issue is reported, that this is
simply done away by threatening people.

How sad to see, that certain cabals that pursue to convert Debian to a
desktop/tablet only OS succeed since they simply hold all the necessary
organisational positions and quite successfully push out any other DDs
that try to resist that agenda...

smime.p7s
Description: S/MIME cryptographic signature

Bug#812163: qutecom: FTBFS with GCC 6: no match for

Package: qutecom
Version: 2.2.1+dfsg1-5.2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-no-match

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.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> [ 53%] Building CXX object 
> qutecom/src/CMakeFiles/owphone.dir/model/profile/UserProfile.o
> cd /<>/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/qutecom/src && 
> /usr/bin/g++   -DDEBUG -I/<>/qutecom-2.2.1+dfsg1/libs/owutil 
> -I/<>/qutecom-2.2.1+dfsg1/libs/imwrapper/include 
> -I/<>/qutecom-2.2.1+dfsg1/libs/imwrapper/src/null 
> -I/<>/qutecom-2.2.1+dfsg1/libs/pixertool/include 
> -I/<>/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/libs/pixertool 
> -I/<>/qutecom-2.2.1+dfsg1/libs/sipwrapper/include 
> -I/<>/qutecom-2.2.1+dfsg1/libs/sound/include 
> -I/<>/qutecom-2.2.1+dfsg1/libs/imwrapper/src/purple 
> -I/<>/qutecom-2.2.1+dfsg1/wifo/phapi 
> -I/<>/qutecom-2.2.1+dfsg1/obj-x86_64-linux-gnu/wifo/phapi 
> -I/<>/qutecom-2.2.1+dfsg1/wifo/phapi-util/include 
> -I/<>/qutecom-2.2.1+dfsg1/wifo/wifo-plugins/sfp-plugin/include 
> -I/<>/qutecom-2.2.1+dfsg1/libs/sipwrapper/src/phapi 
> -I/<>/qutecom-2.2.1+dfsg1/libs/imwrapper/src/multiim/../multiim 
> -I/<>/qutecom-2.2.1+dfsg1
> /qutecom/src 
> -I/<>/qutecom-2.2.1+dfsg1/qutecom/src/model/coipmanager/include 
> -I/<>/qutecom-2.2.1+dfsg1/qutecom/src/model/coipmanager/filesessionmanager/include
>  -I/<>/qutecom-2.2.1+dfsg1/libs/webcam/include 
> -I/<>/qutecom-2.2.1+dfsg1/wifo/netlib/include 
> -I/<>/qutecom-2.2.1+dfsg1/wifo/owsl/include 
> -I/<>/qutecom-2.2.1+dfsg1/wifo/owbase/include 
> -I/<>/qutecom-2.2.1+dfsg1/qutecom/src/buildid 
> -I/<>/qutecom-2.2.1+dfsg1/libs/qtutil/include 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -I/usr/include/glib-2.0/glib -I/usr/include/glib-2.0/gobject 
> -I/usr/include/x86_64-linux-gnu -I/usr/include/libpurple -I/usr/include/qt4 
> -I/usr/include/qt4/Qt -I/usr/include/qt4/QtCore  -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -Wall -Wdate-time 
> -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG   -fPIC -Wall -Wstrict-aliasing 
> -Wno-unused-parameter -fmessage-length=0 -DBOOST_ALL_DYN_LINK -pthread 
> -DOWUTIL_DLL -D__STDC_CONSTANT_MACROS -DPHAPI_DLL -DPHAPIUTIL_DLL 
> -DSFP_PLUGIN_DLL -DWEBCAM_DLL -DOWBASE_DLL -DOWSL_DLL   -DQT_DLL 
> -DQT_NO_KEYWORDS -DOW_RESOURCEDIR='"/usr/share/qutecom"' -o 
> CMakeFiles/owphone.dir/model/profile/UserProfile.o -c 
> /<>/qutecom-2.2.1+dfsg1/qutecom/src/model/profile/UserProfile.cpp
> In file included from 
> /<>/qutecom-2.2.1+dfsg1/libs/owutil/util/Event.h:25:0,
>  from 
> /<>/qutecom-2.2.1+dfsg1/qutecom/src/model/profile/Profile.h:29,
>  from 
> /<>/qutecom-2.2.1+dfsg1/qutecom/src/model/profile/UserProfile.h:23,
>  from 
> /<>/qutecom-2.2.1+dfsg1/qutecom/src/model/profile/UserProfile.cpp:20:
> /usr/include/boost/signal.hpp:17:4: warning: #warning "Boost.Signals is no 
> longer being maintained and is now deprecated. Please switch to 
> Boost.Signals2. To disable this warning message, define 
> BOOST_SIGNALS_NO_DEPRECATION_WARNING." [-Wcpp]
>  #  warning  "Boost.Signals is no longer being maintained and 
> is now deprecated. Please switch to Boost.Signals2. To disable this warning 
> message, define BOOST_SIGNALS_NO_DEPRECATION_WARNING."
> ^~~
> 
> In file included from /usr/include/boost/bind.hpp:22:0,
>  from 
> /<>/qutecom-2.2.1+dfsg1/libs/owutil/util/Event.h:27,
>  from 
> /<>/qutecom-2.2.1+dfsg1/qutecom/src/model/profile/Profile.h:29,
>  from 
> /<>/qutecom-2.2.1+dfsg1/qutecom/src/model/profile/UserProfile.h:23,
>  from 
> /<>/qutecom-2.2.1+dfsg1/qutecom/src/model/profile/UserProfile.cpp:20:
> /usr/include/boost/bind/bind.hpp: In instantiation of 'void 
> boost::_bi::list3::operator()(boost::_bi::type, F&, A&, 
> int) [with F = boost::_mfi::mf2 EnumSipLoginState::SipLoginState>; A = boost::_bi::list2 const EnumSipLoginState::SipLoginState&>; A1 = 
> boost::_bi::value; A2 = boost::arg<1>; A3 = boost::arg<2>]':
> /usr/include/boost/bind/bind.hpp:917:50:   required from 
> 'boost::_bi::bind_t::result_type boost::_bi::bind_t L>::operator()(A1&&, A2&&) [with A1 = SipAccount; A2 = 
> EnumSipLoginState::SipLoginState; R = void; F = boost::_mfi::mf2 UserProfile, SipAccount&, EnumSipLoginState::SipLoginState>; L = 
> boost::_bi::list3, boost::arg<1>, 
> boost::arg<2> >; boost::_bi::bind_t

Bug#812165: pinot: FTBFS with GCC 6: cannot convert

Package: pinot
Version: 1.05-1.1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-cannot-convert

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.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> lib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -DHAVE_DBUS  -fPIC -g 
> -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall 
> -std=gnu++11 -DNDEBUG -c -o ModuleFactory.lo ModuleFactory.cpp
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
> -D_FORTIFY_SOURCE=2 -D_FILE_OFFSET_BITS=64 -I../Utils -I../Tokenize 
> -I../Tokenize/filters -I../Collect -I../IndexSearch/cjkv 
> -I../IndexSearch/Google -DUSE_CURL -DUSE_SSL -std=c++11 
> -I/usr/include/libxml++-2.6 -I/usr/lib/x86_64-linux-gnu/libxml++-2.6/include 
> -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 
> -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sigc++-2.0 
> -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -DUSE_GIO -pthread 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
> -std=c++11 -I/usr/include/glibmm-2.4 
> -I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/sigc++-2.0 
> -I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu
> /glib-2.0/include -DHAVE_DBUS -fPIC -g -O2 -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -std=gnu++11 -DNDEBUG -c ModuleFactory.cpp  
> -fPIC -DPIC -o .libs/ModuleFactory.o
> ModuleFactory.cpp: In static member function 'static IndexInterface* 
> ModuleFactory::getLibraryIndex(const string&, const string&)':
> ModuleFactory.cpp:135:10: error: cannot convert 'bool' to 'IndexInterface*' 
> in return
>return false;
>   ^
> 
> Makefile:648: recipe for target 'ModuleFactory.lo' failed
> make[3]: *** [ModuleFactory.lo] Error 1
> make[3]: Leaving directory '/<>/IndexSearch'

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

Bug#812164: gnome-chemistry-utils: FTBFS with GCC 6: cannot convert

Package: gnome-chemistry-utils
Version: 0.14.10-2
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-cannot-convert

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.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> 
> document.cc: In member function 'void gcr::Document::OnExportVRML(const 
> string&) const':
> document.cc:1524:24: error: cannot convert 'std::ostringstream {aka 
> std::__cxx11::basic_ostringstream}' to 'gpointer {aka void*}' for 
> argument '1' to 'void g_object_unref(gpointer)'
> g_object_unref (file);
> ^
> 
> Makefile:599: recipe for target 'document.lo' failed
> make[4]: *** [document.lo] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

Bug#785272: Fwd: This bug showed up again

2016-01-20 Thread Individual User

-- Forwarded message --
From: Individual User 
Date: Thu, 21 Jan 2016 09:14:19 +0700
Subject: This bug showed up again
To: 785...@bugs.debian.org

Hi,

This bug showed up again in recent updates in debian testing.

I checked - window-list.c changed a little from previous releases.
Please apply the new patch again. It is in the attachment.

Thanks

-- Version information --

$ aptitude versions gir1.2-mate-panel libmate-panel-applet-4-1
mate-panel mate-panel-common
Package gir1.2-mate-panel:
i A 1.12.1-1
   testing
500

Package libmate-panel-applet-4-1:
i A 1.12.1-1
   testing
500

Package libmate-panel-applet-dbg:
p   1.12.1-1
   testing
500

Package libmate-panel-applet-dev:
p   1.12.1-1
   testing
500

Package libmate-panel-applet-doc:
p   1.12.1-1
   testing
500

Package mate-panel:
i A 1.12.1-1
   testing
500

Package mate-panel-common:
i A 1.12.1-1
   testing
500

Package mate-panel-dbg:
p   1.12.1-1
   testing
500
--- applets/wncklet/window-list.c.orig
+++ applets/wncklet/window-list.c
@@ -127,6 +127,7 @@
 	wnck_tasklist_set_orientation (tasklist->tasklist, new_orient);
 #endif
 #endif
+wnck_tasklist_set_orientation (tasklist->tasklist, new_orient); //MIHAI
 	tasklist_update(tasklist);
 }
 
@@ -454,7 +455,7 @@
 	wnck_tasklist_set_middle_click_close (WNCK_TASKLIST (tasklist->tasklist), TRUE);
 #endif
 #endif
-
+wnck_tasklist_set_orientation (tasklist->tasklist, tasklist->orientation); //MIHAI
 	wnck_tasklist_set_icon_loader(WNCK_TASKLIST(tasklist->tasklist), icon_loader_func, tasklist, NULL);
 
 	g_signal_connect(G_OBJECT(tasklist->tasklist), "destroy", G_CALLBACK(destroy_tasklist), tasklist);

Bug#812170: qrouter: FTBFS using clang instead of gcc

Package: qrouter
Severity: minor
Tags: patch
User: pkg-llvm-t...@lists.alioth.debian.org
Usertags: clang-ftbfs

Hello,

Using the rebuild infrastructure, your package fails to build with clang
(instead of gcc).

Detected this kind of error:
http://clang.debian.net/status.php?version=3.6.0=FUNCTION_RETURNS_VALUE

Full build log is available here:
http://clang.debian.net/logs/2015-03-25/qrouter_1.3.3-1_unstable_clang.log

I have attached a patch to fix this error.

Regards,
--Arthur Marble


-- System Information:
Debian Release: sid (unstable)
Architecture: amd64 (x86_64)
Kernel: Linux 4.2.0-1-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE="en_US.UTF-8"
Shell: /bin/sh linked to /bin/dash
Compiler: Debian clang version 3.6.2-3 (based on LLVM 3.6.2)
--- a/qrouter.c
+++ b/qrouter.c
@@ -68,7 +68,7 @@
 {
int i;
 
-   if (NumChannelsX[0] != 0) return;	/* Already been called */
+   if (NumChannelsX[0] != 0) return 1;	/* Already been called */
 
for (i = 0; i < Num_layers; i++) {
   if (PitchX[i] == 0.0 || PitchY[i] == 0.0) {
@@ -108,7 +108,7 @@
 {
int i;
 
-   if (Obs[0] != NULL) return;	/* Already been called */
+   if (Obs[0] != NULL) return 1;	/* Already been called */
 
for (i = 0; i < Num_layers; i++) {
   Obs[i] = (u_int *)calloc(NumChannelsX[i] * NumChannelsY[i],
--- a/graphics.c
+++ b/graphics.c
@@ -488,7 +488,7 @@
tktop = Tk_MainWindow(interp);
if (tktop == NULL) {
   tcl_printf(stderr, "No Top-level Tk window available. . .\n");
-  return;
+  return 3;
}
 
qrouterdrawwin = (char *)Tcl_GetVar(interp, "drawwindow", TCL_GLOBAL_ONLY);

Bug#812157: sundials: FTBFS with clang instead of gcc

Package: sundials
Severity: minor
Tags: patch
User: pkg-llvm-t...@lists.alioth.debian.org
Usertags: clang-ftbfs

Hello,

Using the rebuild infrastructure, your package fails to build with clang
(instead of gcc).

Detected this kind of error:
http://clang.debian.net/status.php?version=3.6.0=FUNCTION_RETURNS_VALUE

Full build log is available here:
http://clang.debian.net/logs/2015-03-25/sundials_2.5.0-3_unstable_clang.log

I have attached a patch to fix this error.


Regards,
--Arthur Marble


-- System Information:
Debian Release: sid (unstable)
Architecture: amd64 (x86_64)
Kernel: Linux 4.2.0-1-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE="en_US.UTF-8"
Shell: /bin/sh linked to /bin/dash
Compiler: Debian clang version 3.6.2-3 (based on LLVM 3.6.2)
--- a/sundialsTB/kinsol/kim/src/kim.c
+++ b/sundialsTB/kinsol/kim/src/kim.c
@@ -679,7 +679,7 @@
   int status;
 
 
-  if (kimData == NULL) return;
+  if (kimData == NULL) return 0;
 
   status = KINGetNumNonlinSolvIters(kin_mem, );
   if (status != KIN_SUCCESS) goto error_return;
@@ -807,5 +807,5 @@
 
   KINFree(_mem);
 
-  return;
+  return 0;
 }

Bug#812158: spacearyarya: FTBFS with clang instead of gcc

Package: spacearyarya
Severity: minor
Tags: patch
User: pkg-llvm-t...@lists.alioth.debian.org
Usertags: clang-ftbfs

Hello,

Using the rebuild infrastructure, your package fails to build with clang
(instead of gcc).

Detected this kind of error:
http://clang.debian.net/status.php?version=3.6.0=FUNCTION_RETURNS_VALUE

Full build log is available here:
http://clang.debian.net/logs/2015-03-25/spacearyarya_1.0.2-7_unstable_clang.log

I have attached a patch to fix this error.


Regards,
--Arthur Marble


-- System Information:
Debian Release: sid (unstable)
Architecture: amd64 (x86_64)
Kernel: Linux 4.2.0-1-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE="en_US.UTF-8"
Shell: /bin/sh linked to /bin/dash
Compiler: Debian clang version 3.6.2-3 (based on LLVM 3.6.2)
--- a/src/ranking.c
+++ b/src/ranking.c
@@ -15,7 +15,7 @@
 if (Ranking[i]->Score < Root->Score)
   break;
   if (i == 5)
-return;
+return 0;
   if (i != 4) {
 for (j = 4; j > i; j --)
   memcpy(Ranking[j], Ranking[j - 1], sizeof(RankingData));

Bug#812159: please enable new featured libaria2

2016-01-20 Thread PICCORO McKAY Lenz

Package: aria2
Version: 1.19.0-1
Severity: wishlist

please enable libarai2 as feature lib

since version 1.18 aria provides a new aria library for api access.

-- 
Lenz McKAY Gerardo (PICCORO)
http://qgqlochekone.blogspot.com

Bug#812154: texlive-extra-utils: /usr/bin/texdef shows errors "Unescaped left brace..."

2016-01-20 Thread Norbert Preining

Hi Igor,

On Thu, 21 Jan 2016, Igor Liferenko wrote:
> $ texdef leavevmode
> Unescaped left brace in regex is deprecated, passed through in regex; marked 
> by <-- HERE in m/^\\\@protected\@testopt { <-- HERE ?\\.*? }? *(.*?) / at 
> /usr/bin/texdef line 391.

Nothing to do with the update of texlive, but only with the
update pof perl to 5.22

perl has gotten *very* noisy, the patch is probably trivial
by escaping the { and } in lines 391 and 394.

Norbert


PREINING, Norbert   http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13   fp: F7D8 A928 26E3 16A1 9FA0  ACF0 6CAC A448 860C DC13

Bug#812166: xen: FTBFS with GCC 6: statement is indented as if...

Package: xen
Version: 4.6.0-1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-misleading-indentation

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.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> gcc -O2 -fomit-frame-pointer -m64 -fno-strict-aliasing -std=gnu99 -Wall 
> -Wstrict-prototypes -Wdeclaration-after-statement 
> -Wno-unused-but-set-variable -Wno-unused-local-typedefs   -DNDEBUG 
> -I/<>/debian/build/build-hypervisor_amd64_amd64/xen/include  
> -I/<>/debian/build/build-hypervisor_amd64_amd64/xen/include/asm-x86/mach-generic
>  
> -I/<>/debian/build/build-hypervisor_amd64_amd64/xen/include/asm-x86/mach-default
>  -msoft-float -fno-stack-protector -fno-exceptions -Wnested-externs 
> -DHAVE_GAS_VMX -DHAVE_GAS_EPT -DHAVE_GAS_FSGSBASE -mno-red-zone -mno-sse 
> -fpic -fno-asynchronous-unwind-tables -DGCC_HAS_VISIBILITY_ATTRIBUTE 
> -fno-builtin -fno-common -Werror -Wredundant-decls -Wno-pointer-arith -pipe 
> -g -D__XEN__ -include 
> /<>/debian/build/build-hypervisor_amd64_amd64/xen/include/xen/config.h
>  -nostdinc -DCONFIG_SHADOW_PAGING -DHAS_ACPI -DHAS_GDBSX -DHAS_PASSTHROUGH 
> -DHAS_MEM_ACCESS -DHAS_MEM_PAGING -DHAS_MEM_SHARING -DHAS_PCI -DHAS_IOPORT
> S -DHAS_PDX -MMD -MF .non-fatal.o.d -c non-fatal.c -o non-fatal.o
> non-fatal.c: In function 'init_nonfatal_mce_checker':
> non-fatal.c:103:2: error: statement is indented as if it were guarded by... 
> [-Werror=misleading-indentation]
>   switch (c->x86_vendor) {
>   ^~
> 
> non-fatal.c:97:5: note: ...this 'if' clause, but it is not
>  if ( __get_cpu_var(poll_bankmask) == NULL )
>  ^~
> 
> cc1: all warnings being treated as errors

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

Bug#812167: glob2: FTBFS with GCC 6: no match for

Package: glob2
Version: 0.9.4.4-2.4
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-no-match

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.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> g++ -o src/EditorMainMenu.o -c -g -DHAVE_CONFIG_H -D_GNU_SOURCE=1 
> -D_REENTRANT -Ilibgag/include -I. -I/usr/include/SDL src/EditorMainMenu.cpp
> src/EditorMainMenu.cpp: In member function 'virtual void 
> EditorMainMenu::onAction(GAGGUI::Widget*, GAGGUI::Action, int, int)':
> src/EditorMainMenu.cpp:93:80: error: no matching function for call to 
> 'ChooseMapScreen::ChooseMapScreen(const char [5], const char [4], bool, const 
> char [6], const char [5], bool)'
> ChooseMapScreen chooseMapScreen("maps", "map", false, "games", "game", 
> false);
>   
>   ^
> 
> In file included from src/EditorMainMenu.cpp:24:0:
> src/ChooseMapScreen.h:46:2: note: candidate: 
> ChooseMapScreen::ChooseMapScreen(const char*, const char*, bool, const char*, 
> const char*, const char*)
>   ChooseMapScreen(const char *directory, const char *extension, bool recurse, 
> const char* alternateDirectory=NULL, const char* alternateExtension=NULL, 
> const char* alternateRecurse=NULL);
>   ^~~
> 
> src/ChooseMapScreen.h:46:2: note:   no known conversion for argument 6 from 
> 'bool' to 'const char*'
> src/ChooseMapScreen.h:40:7: note: candidate: 
> ChooseMapScreen::ChooseMapScreen(const ChooseMapScreen&)
>  class ChooseMapScreen : public Glob2Screen
>^~~
> 
> src/ChooseMapScreen.h:40:7: note:   candidate expects 1 argument, 6 provided
> scons: *** [src/EditorMainMenu.o] Error 1
> scons: building terminated because of errors.
> debian/rules:31: recipe for target 'build-stamp' failed
> make: *** [build-stamp] Error 2

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

Bug#800835: The firrmare is in firmware-misc-nonfree

2016-01-20 Thread Mihai Maties

The specific firmware is part of the firmware-misc-nonfree package (just
install it and the error will go away).


Best regards,
Mihai

Bug#812171: pmacct: FTBFS using clang instead of gcc

Package: pmacct
Severity: minor
Tags: patch
User: pkg-llvm-t...@lists.alioth.debian.org
Usertags: clang-ftbfs

Hello,

Using the rebuild infrastructure, your package fails to build with clang
(instead of gcc).

Detected this kind of error:
http://clang.debian.net/status.php?version=3.6.0=FUNCTION_RETURNS_VALUE

Full build log is available here:
http://clang.debian.net/logs/2015-03-25/pmacct_1.5.0-4_unstable_clang.log

I have attached a patch to fix this error.

Regards,
--Arthur Marble


-- System Information:
Debian Release: sid (unstable)
Architecture: amd64 (x86_64)
Kernel: Linux 4.2.0-1-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE="en_US.UTF-8"
Shell: /bin/sh linked to /bin/dash
Compiler: Debian clang version 3.6.2-3 (based on LLVM 3.6.2)
--- a/src/plugin_hooks.c
+++ b/src/plugin_hooks.c
@@ -868,7 +868,7 @@
   char *rk = NULL, sep[] = "-";
   int len = 0;
 
-  if (!name || !type) return;
+  if (!name || !type) return NULL;
 
   len = strlen(name) + strlen(type) + 2;
 
@@ -918,7 +918,7 @@
   struct plugin_pipe_amqp_sleeper *pas;
   int size = sizeof(struct plugin_pipe_amqp_sleeper);
 
-  if (!amqp_host || !flag) return;
+  if (!amqp_host || !flag) return NULL;
 
   pas = malloc(size);

Bug#812150: rfkill: rkfill doesn't fully turn on bluetooth on ThinkPad X230.

2016-01-20 Thread Fabián Inostroza

Package: rfkill
Version: 0.5-1
Severity: important

Dear Maintainer,

I use tlp to control power settings of my laptop and I have disabled bluetooth
on startup, when I want to use it I have to run 'rfkill unblock bluetooth'.
Before running 'rfkill unblock bluetooth', 'rfkill list' shows:
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: yes
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

and after running 'rfkill unblock bluetooth', 'rfkill list' shows

0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no

unblocking bluetooth a second time makes the bluetooth adapter available to use.

I would expect just once 'rfkill unblock bluetooth' to enable bluetooth.

I found this bug while using tlp but it is not related to tlp.
Please see: https://github.com/linrunner/TLP/issues/180


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

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

Versions of packages rfkill depends on:
ii  libc6  2.21-6

rfkill recommends no packages.

rfkill suggests no packages.

-- no debconf information

Bug#812151: linux-image-4.3.0-1-amd64: USB freeze issue on AMD SBx00 chipsets is not fully resolved

2016-01-20 Thread oldtechaa

Package: src:linux
Version: 4.3.3-5
Severity: important
Tags: upstream

Dear Maintainer,

We have tried several different kernels on this Dell Optiplex 320. The USB
chipset is an AMD SB600, which was previously known by developers to have
freeze issues when multiple devices were plugged in. We are using a KWorld
UB435-Q TV tuner, a Ralink wireless adapter, and a Creative wireless keyboard
mouse combo. Logs on the matter have been limited, not displaying anything
regarding this problem.

The patch that was applied to help in multiple device situations does not seem
to have fully resolved the issue, as when using the TV Tuner, it fails to
acquire all of the video data. When the Ralink adapter is unplugged, the video
signal from the tuner gets better, but still has green artifacts throughout.
Unfortunately, we cannot unplug the keyboard mouse combination as the
motherboard has no PS/2 ports to use with a non-USB keyboard. Testing with the
keyboard/mouse removed results in no green spots in the video data, but still
freezes occasionally during recording. This could be due to the USB 1.1
controllers which appear as connected USB devices. The problem also affects the
usage of the keyboard and mouse, causing loss of some characters and jumps on
the mouse.

The reason this is marked as important is because it makes Linux unusable for
our purposes on this computer. Fortunately, we have other computers to use
instead. This computer will likely be taken down soon and replaced with one of
those, so testing and logging time may be limited.



-- Package-specific info:
** Version:
Linux version 4.3.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.3.1
20160101 (Debian 5.3.1-5) ) #1 SMP Debian 4.3.3-5 (2016-01-04)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.3.0-1-amd64 root=UUID=7cb582fa-
c97f-4253-be61-77df3ac21ed0 ro quiet

** Not tainted

** Kernel log:
[262123.381400] wlan1: authenticated
[262123.384045] wlan1: associate with 94:10:3e:f9:ed:e4 (try 1/3)
[262123.389870] wlan1: RX AssocResp from 94:10:3e:f9:ed:e4 (capab=0x1 status=0
aid=5)
[262123.397740] wlan1: associated
[264007.777513] device-mapper: uevent: version 1.0.3
[264007.778241] device-mapper: ioctl: 4.33.0-ioctl (2015-8-18) initialised: dm-
de...@redhat.com
[264010.057403] SGI XFS with ACLs, security attributes, realtime, no debug
enabled
[264010.132522] JFS: nTxBlock = 8192, nTxLock = 65536
[264010.236093] ntfs: driver 2.1.32 [Flags: R/W MODULE].
[264010.345043] QNX4 filesystem 0.2.3 registered.
[264010.428023] raid6: sse2x1   gen()  2852 MB/s
[264010.496016] raid6: sse2x1   xor()  3052 MB/s
[264010.564023] raid6: sse2x2   gen()  3313 MB/s
[264010.632025] raid6: sse2x2   xor()  3650 MB/s
[264010.700022] raid6: sse2x4   gen()  5232 MB/s
[264010.768017] raid6: sse2x4   xor()  3533 MB/s
[264010.768024] raid6: using algorithm sse2x4 gen() 5232 MB/s
[264010.768026] raid6:  xor() 3533 MB/s, rmw enabled
[264010.768029] raid6: using ssse3x2 recovery algorithm
[264010.779449] xor: measuring software checksum speed
[264010.816018]prefetch64-sse:  4935.000 MB/sec
[264010.856053]generic_sse:  4328.000 MB/sec
[264010.856065] xor: using function: prefetch64-sse (4935.000 MB/sec)
[264010.900504] Btrfs loaded
[264011.145027] EXT4-fs (sda2): unable to read superblock
[264011.147739] EXT4-fs (sda2): unable to read superblock
[264011.150343] EXT4-fs (sda2): unable to read superblock
[264011.159683] XFS (sda2): Invalid superblock magic number
[264011.165931] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT
filesystems, filesystem will be case sensitive!
[264011.166094] FAT-fs (sda2): bogus number of reserved sectors
[264011.166101] FAT-fs (sda2): Can't find a valid FAT filesystem
[264011.169486] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT
filesystems, filesystem will be case sensitive!
[264011.169770] FAT-fs (sda2): bogus number of reserved sectors
[264011.169776] FAT-fs (sda2): Can't find a valid FAT filesystem
[264011.182339] MINIX-fs: unable to read superblock
[264011.214274] attempt to access beyond end of device
[264011.214285] sda2: rw=16, want=3, limit=2
[264011.214288] hfsplus: unable to find HFS+ superblock
[264011.219111] qnx4: no qnx4 filesystem (no root dir).
[264011.221955] ufs: You didn't specify the type of your ufs filesystem

mount -t ufs -o
ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ...

>>>WARNING<<< Wrong ufstype may corrupt your filesystem,
default is ufstype=old
[264011.228365] hfs: can't find a HFS filesystem on dev sda2
[264027.718105] EXT4-fs (sda2): unable to read superblock
[264027.720902] EXT4-fs (sda2): unable to read superblock
[264027.723865] EXT4-fs (sda2): unable to read superblock
[264027.732369] XFS (sda2): Invalid superblock magic number
[264027.737781] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT
filesystems, filesystem will be case sensitive!
[264027.737948] FAT-fs (sda2): bogus number of reserved sectors

Bug#812153: [Pkg-utopia-maintainers] Bug#812153: Bug#812153: Bug#812153: policykit-1: allows ordinary users to mount filesystems

On Thu, 2016-01-21 at 04:32 +0100, Michael Biebl wrote:
> Right, since we had removable media 30 years ago.
No but mounting filesystems.


> In such a very specialised situation you can easily lock down the
> configuration. For such a setup you will most likely need custom
> configuration anyway to be secure.
> A default configuration needs to usable by the majority of users.
The problem with that is:
AFAIU, when I override polkit rules, that it's really just the specific
rule that are overriden... and no the whole config file e.g.
org.freedesktop.udisks2.policy

While this makes at first since of course, it also means that one have
no real chance to go back to sane permissions unless one would track
any single change of /usr/share/polkit-
1/actions/org.freedesktop.udisks2.policy.
Of course one can override all rules that are there right now, but new
properties get added or existing ones removed, and then one's back to
insecure-per-default settings.


> There is no "real issue".
Maybe not for you, others may have tighter security constraints,
though. E.g. I wouldn't want to have everyone-may-access-everything
just it may seem convenient for some people and they set up their
systems like this.


>  Point.
> You are making a big fuss for nothing and wasting everyones time,
> mine
> included. I'm not willing to tolerate that.
Uhm I had understood that before.
Not-an-issue-for-you plus threatening people for whom it is - bug
solving by oppression (guess I should try that at the institute as well
=) ),...
So no need to point out and praise your position of power again.

Anyway,.. the bug is closed as you enforced it,.. perhaps it should be
marked wontfix?

Cheers,
Chris.

smime.p7s
Description: S/MIME cryptographic signature

Bug#812116: newly built initrd complains about missing init

2016-01-20 Thread Harald Dunkel

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Yup.

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJWoGOcAAoJEAqeKp5m04HLqk8H/RLH14ZPiDgZr1yHFCyiGEPY
46snYvavBNa2JBjYZXdwynHTRS9oWApYPTgSAdNYhYJ2Kjbr838hiH9V/5Wv030q
yVofhD1bNm7sA1ynflMXdgvvDI8RemNRpmKflG7rRBeZfOHkDxgOXYiT0wNLaoDg
TmGv8PNzqIw83ioTXg/Q2M71aB0QrHes/HKjnfQI/Axak6P7AWOj/9tLqx7ApxAn
KKozOFtg1m8WeUzHaIHZ+Q/NaUmmDaM5CYQIXEgVdni2UoAUgrqdNcf9DYf/KwFw
P1OUD2BRT6lVRr3Q62gcPWKOavmcpXKzmm3hLuMRl98PrdCvJMwkXLeehUCks78=
=8I09
-END PGP SIGNATURE-

Bug#812153: policykit-1: allows ordinary users to mount filesystems

Package: policykit-1
Version: 0.105-14.1
Severity: grave
Tags: security


Hi.

Apparently polkit (or at least I guess it's ultimately the offender here,
if not please reassign accordingly) allows ordinary users to mount any
filesystem per default.
E.g. such connected via USB, or set up via losetup.
At least that works so e.g. via nautilus,.. wich disturbingly seem to do
that even automatically though nothing from that attached device/fs was
accessed... o.O

Since such filesystems may have totally different user/group owners
or even none and be world wrtiable (e.g. with *FAT filesystems) and since
they may contain any sensitve data frm keys to secret source code, etc.,
this is a grave security breach.


May not matter that much on a notebook or tablet, but one should hope that
even nowadays Debian isn't just made for those people,.. and there are
perhaps still some other systems out there were devices with such filesystems
are connected and where uses have direct and/or remote accesses, but where
they should not be able to mount any fs.

Since it has been the long standing behaviour of UNIX/Linux ever, that normal
users cannot mountfilesystems unless explicitly allowed, please revert to
that behaviour.

Cheers,
Chris.

Bug#811275: ITP: uclibc-ng -- uClibc-ng is an implementation of the standard C library that is much smaller than glibc, which makes it useful for embedded systems.

2016-01-20 Thread Waldemar Brodkorb

Hi Thorsten,
Thorsten Glaser wrote,

> On Mon, 18 Jan 2016, Waldemar Brodkorb wrote:
> 
> > From a good friend I would expect some more positive feedback
> > for my hobby project ;)
> 
> I said, it has its niche, but I doubt it has a place
> as a generic Debian package… libraries are generally
> only packaged when something uses them, and C libra‐
> ries are hard.

May be you didn't know the reason for the package.
I'll try to use it for rebootstrap to build a complete
Debian system based on uClibc-ng. So then "something" 
or even "everything" will use it ;)

You can help doing some review of the package:
http://downloads.uclibc-ng.org/debian/

best regards
 Waldemar

Bug#796956: Explanation

2016-01-20 Thread Lisandro Damián Nicanor Pérez Meyer

On Tuesday 19 January 2016 11:12:06 you wrote:
> Hi Bálint!
> 
> On Monday 18 January 2016 10:38:05 Bálint Réczey wrote:
> > Hi Lisandro,
> 
> [snip]
> 
> > 5.6.x is beta in experimental and I can't tell when it enters
> > unstable. If it does not
> > get uploaded to unstable in a few days with a good chance of migrating
> > to testing
> > soon please upload a fix to 5.5.x.
> 
> I'm working for pushing it in 5.5.2, hopefully real soon.

Pushed it today. Hope it helps.

-- 
6: Cual es el boton del mouse que permite acceder a las acciones mas
comunes del manejo de archivos
* Depende el tipo de accion mas comun
Damian Nadales
http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


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

Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)

2016-01-20 Thread adrian15

El 18/01/16 a las 13:38, Thomas Schmitt escribió:

Hi,

adrian15 wrote:

* What is it a secondary bootloader?
It's what happens when you request mkisofs that your bootloader to be
boot in second place or as a second partition. I don't know how it
actually works.

An ISO may contain several lures for boot firmware.

If it is booted from CD/DVD/BD, then the lures are in the El Torito
boot catalog. In case of debian-cd it contains two entries which
point to boot images. One entry is marked as suitable for BIOS and
one marked as suitable for EFI. The boot firmware then picks what
it deems right and starts it, or offers it to the user for starting.

Interesting.

If the ISO is presented on USB stick or alike, then BIOS looks
for the magic number of an MBR and if so, mindlessly executes
the x86 machine code that starts at byte 0 of the ISO.
This code then hops onto the same boot code that is advertised
by El Torito (because xorriso or isohybrid patched its block
address into the MBR code).

Aha.

EFI looks on USB stick for an MBR partition of type 0xef or
for a single partition of type 0xee. In the latter case it assumes
the presence of GPT and looks for a GPT partition with type GUID
28732ac11ff8d211ba4b00a0c93ec93b.
Inside the found partition it expects a FAT filesystem and
particular binaries for each supported processor archictecture.
E.g. \EFI\BOOT\BOOTX64.EFI

The El Torito EFI boot image has the same content specification
as the EFI System Partition. Therefore both boot paths can share
the same data.

My cheat sheet is at

http://bazaar.launchpad.net/~libburnia-team/libisofs/scdbackup/view/head:/doc/boot_sectors.txt

Great! I want to document the different ways of how BIOS boot, UEFI boot
and Secure Boot work and that might be helpful.

So, I guess the -eltorito-alt-boot does the magic but I'm not sure.
Maybe someone else can explain it better than me.

-eltorito-alt-boot is simply a separator between the options of
El Torito boot images.
I assume your first boot image is announced by -b and gets
the usual options
-no-emul-boot -boot-load-size 4 -boot-info-table

Before the announcement of the EFI boot image begins, option
-eltorito-alt-boot is needed to protect your -b and its helpers
from being overwritten.

That it's quite interesting. Do you mean if you have:

xorriso bunch-of-options-1 -eltorito-alt-boot bunch-of-options-2

you could just re-arrange them as:

xorriso bunch-of-options-2 -eltorito-alt-boot bunch-of-options-1

and it would be fine?

So that it's not strictly necessary for syslinux or grub-pc to be a
primary bootloader (or first lure in your definition) ?

That would also simplify my contributed code to live-build by not
needing to handle if a bootloader is primary/secondary or not.

So in grub-efi we just add to the xorriso options:
-eltorito-alt-boot \
-e boot/grub/efi.img \
-no-emul-boot \
-isohybrid-gpt-basdat \
-isohybrid-apm-hfsplus

Here a second boot image gets announced by -e and the next three
options apply to it.

Ok.

And in syslinux-efi (currently) we add:
-eltorito-alt-boot \
--efi-boot boot/efi.img \

Option --efi-boot is a shortcut for
-eltorito-alt-boot -e ... -no-emul-boot -eltorito-alt-boot
normally used by grub-mkrescue. The SYSLINUX community prefers -e.
Knowing that I will probably expand that so that the syslinux-efi and
grub-efi options are more similar and we can compare them in a more easy
manner.

-append_partition 2 0x01 \
binary/boot/efi.img

I wonder what EFI firmware would hop on an MBR partition of type 0x01.
An EFI System Partition in MBR should have type 0xef to be recognized.

That needs to be asked to Hertzog. I just tried to use his original work.

It looks like this variant will not get GPT. That's fully compliant
to UEFI 2.4. Just the MBR partition type should be 0xef.

(Does "syslinux-efi" mean that you can boot from ISO via EFI
and SYSLINUX stuff to an operating system ? That would be new.)
I don't know what you mean by 'SYLINUX stuff to an operating system. I
understand that Hertzog work let's you boot into the cd booting by the
means of EFI. The EFI image needs to include the configuration file (as
opossed to the grub-efi implementation which only stores its
configuration file in the CD/DVD/BD media).

---

Above options do not produce HFS+ with blessing.
Option -isohybrid-apm-hfsplus causes an Apple Partition Map entry
which points to the data content of boot/grub/efi.img.

If I'm not mistaken Hertzog removed that option because you suggested to
remove it on:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731709#66

Are you requesting to put this option back ?

There are two ways known to me how to get a boot path via HFS+:
Fedora Live CD as of Matthew Garrett
or grub-mkrescue as of Vladimir Serbinenko.

The debian-cd method is one of them? Or is it not?

Bug#812155: release.debian.org: Patch to make heidi output optional

2016-01-20 Thread Robert Bruce Park

Package: release.debian.org
Severity: wishlist
Tags: patch
User: release.debian@packages.debian.org
Usertags: britney

Hi, I'm doing some work on britney as used by ubuntu and I've made Heidi output 
optional as we were not using it in all cases, in the hopes of saving some 
time/disk space.

Please consider the attached patch, thanks.



-- System Information:
Debian Release: stretch/sid
  APT prefers xenial-updates
  APT policy: (500, 'xenial-updates'), (500, 'xenial-security'), (500, 
'xenial'), (100, 'xenial-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-5-generic (SMP w/8 CPU cores)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
=== modified file 'britney.py'
--- britney.py	2016-01-19 20:05:32 +
+++ britney.py	2016-01-20 02:17:12 +
@@ -453,7 +453,7 @@
  not getattr(self.options, k.lower()):
 setattr(self.options, k.lower(), v)
 
-if not hasattr(self.options, "heidi_delta_output"):
+if self.options.heidi_output and not hasattr(self.options, "heidi_delta_output"):
 self.options.heidi_delta_output = self.options.heidi_output + "Delta"
 
 self.options.nobreakall_arches = self.options.nobreakall_arches.split()
@@ -3023,14 +3023,15 @@
 except AttributeError:
 self.write_dates(self.options.testing, self.dates)
 
-# write HeidiResult
-self.__log("Writing Heidi results to %s" % self.options.heidi_output)
-write_heidi(self.options.heidi_output, self.sources["testing"],
-self.binaries["testing"])
+if self.options.heidi_output:
+# write HeidiResult
+self.__log("Writing Heidi results to %s" % self.options.heidi_output)
+write_heidi(self.options.heidi_output, self.sources["testing"],
+self.binaries["testing"])
 
-self.__log("Writing delta to %s" % self.options.heidi_delta_output)
-write_heidi_delta(self.options.heidi_delta_output,
-  self.all_selected)
+self.__log("Writing delta to %s" % self.options.heidi_delta_output)
+write_heidi_delta(self.options.heidi_delta_output,
+  self.all_selected)
 
 
 self.printuninstchange()

Bug#812153: [Pkg-utopia-maintainers] Bug#812153: policykit-1: allows ordinary users to mount filesystems

Control: reopen -1
Control: reassign -1 udisks2

On Thu, 2016-01-21 at 03:39 +0100, Michael Biebl wrote:
> Policykit is the wrong package. What you look for is udisks, most
> likely.
I went through /usr/share/polkit-
1/actions/org.freedesktop.udisks2.policy but all settings there seem to
be auth_admin and none seems to be specifically for removable devices.

>  And what you say is not true, only removable drives  are
> automounted, and that is deliberate and not going to change.
It's still breaking long standing behaviour. You cannot just add such
security regressions and call it "deliberate" thus "not going to
change".

Especially since any device can be removable... people connect normal
hard disks via USB/SATA gateways, which are detected as such as well.

If Debian introduces behaviour that likely allows access to data where
normal users shouldn't have access, than this should be an opt-in.

Thus reopening.

smime.p7s
Description: S/MIME cryptographic signature

Bug#812118: mailagent: Mailbox compression broken with Perl 5.22

2016-01-20 Thread Manoj Srivastava

On Wed, Jan 20 2016, Rafael Laboissiere wrote:

> Package: mailagent
> Version: 1:3.1-81-1
> Severity: important

Hi,

It might (and then again, it might not) be reassuring to know I
 have exactly the same version of perl nd mailagent; and mailagent did
 pass all tests, including the compression tests. I have not seen the
 mail lossage (the defined(@array) is fairly benign, despite the dire
 warning) .

manoj

-- 
Beware of low-flying butterflies.
Manoj Srivastava    
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20  05B6 CF48 9438 C577 9A1C

signature.asc
Description: PGP signature

Bug#812118: mailagent: Mailbox compression broken with Perl 5.22

2016-01-20 Thread Manoj Srivastava

On Wed, Jan 20 2016, Rafael Laboissiere wrote:
> Package: mailagent
> Version: 1:3.1-81-1
> Severity: important

> I upgraded the perl package in my testing system to version 5.22.1-4 
> today and mailagent ceased to work.  I had error messages like the
> following one in the mailagent log file:

>16/01/20 19:17:43 mailagent[178656]: ERROR Can't use
> 'defined(@array)' (Maybe you should just omit the defined()?) at (eval
> 1219) line 5,  chunk 618., while parsing code of
> compress'restore.

This should be reasonably easy to fix. I am afraid is this is
 not the only bug that would be introduced; mailagent has not really
 been updated beyond perl4 much, I am afraid.

> It is even worse than that: even though there were messages like these
> ones in the log file:
>
>16/01/20 19:17:43 mailagent[178656]: NOTICE not saved, leaving in mailbox
>16/01/20 19:17:43 mailagent[178656]: WARNING using
> /home/rafael/mbox.rafael for mailbox
>
> the non-filtered email messages were not saved anywhere.  The file
> /home/rafael/mbox.rafael was not created, contrary to what is
> indicated above.  I had severe email loss this afternoon!
>
> BTW, I considered raising the severity level of this bug report to
> "serious".  However, I could find a workaround for the problem, by
> commenting the definitions for the configuration variables "compress",
> "compspecs", and "comptag" in my ~/.mailagent file.

> I apologize for not proposing a patch.  Hacking the Perl code in
> /usr/bin/mailagent is far beyond my current aptitudes.

I’ll take a crack at it.

manoj
-- 
To err is human, to repent, divine, to persist, devilish. Benjamin
Franklin
Manoj Srivastava    
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20  05B6 CF48 9438 C577 9A1C


signature.asc
Description: PGP signature

Bug#730049: linux-image-3.12-1-amd64: kernel does not boot

2016-01-20 Thread Ben Hutchings

On Thu, 2015-12-10 at 04:03 +, Ben Hutchings wrote:
> Control: retitle -1 RAID boot failure with Linux 3.10
> Control: tag -1 moreinfo
> 
> I'm treating this bug (#730049) as covering the boot failure described
> in message #14  and bug #717698 as
> covering the original boot failure described in messages #5, #24, etc.
> Please keep these issues separate.
> 
> Do you still see a failure to set up the RAID ("mdadm: No devices
> listed in conf file were found") on some machines?  Can you send the
> /etc/mdadm.conf file from one of those?

Please answer these questions, or we will eventually just close the bug.

Ben.

-- 
Ben Hutchings
Horngren's Observation:
   Among economists, the real world is often a special case.

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

Bug#812149: retext: program crash

2016-01-20 Thread Erik

Package: retext
Version: 5.3.0-1
Severity: grave
Justification: renders package unusable

Ran: retext docs/api.md and received the below output:

Traceback (most recent call last):
  File "/usr/share/retext/ReText/highlighter.py", line 129, in highlightBlock
if not self.dictionary.check(match.group(0)):
  File "/usr/lib/python3/dist-packages/enchant/__init__.py", line 634, in check
self._check_this()
  File "/usr/lib/python3/dist-packages/enchant/__init__.py", line 606, in 
_check_this
_EnchantObject._check_this(self,msg)
  File "/usr/lib/python3/dist-packages/enchant/__init__.py", line 176, in 
_check_this
raise Error(msg)
enchant.errors.Error: Dict unusable: the underlying C-library object has been 
freed.

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

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

Versions of packages retext depends on:
ii  python3-docutils0.12+dfsg-1
ii  python3-enchant 1.6.6-2
ii  python3-markdown2.6.5-1
ii  python3-markups 1.0.1-1
ii  python3-pygments2.0.1+dfsg-2
ii  python3-pyqt5   5.5.1+dfsg-3+b1
ii  python3-pyqt5.qtwebkit  5.5.1+dfsg-3+b1
pn  python3:any 

Versions of packages retext recommends:
ii  docutils-common   0.12+dfsg-1
ii  shared-mime-info  1.5-2

retext suggests no packages.

-- no debconf information

Bug#674059: initramfs generation fails at fs/udf/udf.ko

2016-01-20 Thread Ben Hutchings

On Fri, 2015-12-11 at 02:10 +, Ben Hutchings wrote:
> Nikolay, I'm sorry we didn't respond to your last message.  Did you
> ever find a solution to this problem?

Please tell us whether this is fixed, otherwise we'll eventually just
close it.

Ben.

> On Thu, 7 Jun 2012 23:39:32 +0300 Nikolay Zaynelov
>  wrote:
> [...]
> > I started the last command but it does not ended for a long period of time
> > so I stopped it with ctrl+c. The result is empty /tmp/foo file and this
> > content in /tmp/log file:
> [...]
> > + manual_add_modules xfs
> > + local kmod firmware
> > + modprobe --set-version=2.6.32-5-amd64 --ignore-install --quiet+
> > -show-depends xfs
> > awk /^insmod/ { print $2 }
> [...]
> 
> So it looks like the problem was actually related to adding the xfs
> module, not udf.
> 
> Ben.
> 
-- 
Ben Hutchings
Horngren's Observation:
   Among economists, the real world is often a special case.

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

Bug#811921: ffmpeg: FTBFS with GCC 6: misc errors

2016-01-20 Thread Andreas Cadhalpun

Control: reassign -1 gcc-6 6-20160117-1
Control: affects -1 ffmpeg

Hi Martin,

On 20.01.2016 04:44, Martin Michlmayr wrote:
> 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.
> 
> You may be able to find out more about this issue at
> https://gcc.gnu.org/gcc-6/changes.html
> 
>> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
> ...
>> cc -I. -I/<>/ -Wdate-time -D_FORTIFY_SOURCE=2 -U_FORTIFY_SOURCE 
>> -D_FORTIFY_SOURCE=2 -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 
>> -D_LARGEFILE_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DPIC 
>> -DZLIB_CONST -g -O2 -fstack-protector-strong -Wformat 
>> -Werror=format-security -fno-strict-overflow -fstack-protector-all   
>> -std=c99 -fomit-frame-pointer -fPIC -pthread -I/usr/include/p11-kit-1 
>> -I/usr/include/harfbuzz -I/usr/include/freetype2 -I/usr/include/fribidi 
>> -I/usr/include/freetype2  -I/usr/include/bs2b  -I/usr/include/freetype2 
>> -I/usr/include/freetype2 -I/usr/include/fribidi  -I/usr/include/opencv 
>> -I/usr/include/opus -D_REENTRANT -I/usr/include/p11-kit-1 
>> -I/usr/include/schroedinger-1.0 -I/usr/include/orc-0.4 
>> -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL  -g 
>> -Wdeclaration-after-statement -Wall -Wdisabled-optimization -Wpointer-arith 
>> -Wredundant-decls -Wwrite-strings -Wtype-limits -Wundef -Wmissing-prototypes 
>> -Wno-pointer-to-int-cast -Wstrict-prototypes
>>  -Wempty-body -Wno-parentheses -Wno-switch -Wno-format-zero-length 
>> -Wno-pointer-sign -O3 -fno-math-errno -fno-signed-zeros -fno-tree-vectorize 
>> -Werror=format-security -Werror=implicit-function-declaration 
>> -Werror=missing-prototypes -Werror=return-type -Werror=vla -Wformat 
>> -fdiagnostics-color=auto -Wno-maybe-uninitialized-c -o ffmpeg_opt.o 
>> /<>/ffmpeg_opt.c
>> /<>/ffplay.c:3217:46: error: missing binary operator before 
>> token "("
>>  #if defined(__APPLE__) && SDL_VERSION_ATLEAST(1, 2, 14)
>>   ^
>> cc -I. -I/<>/ -Wdate-time -D_FORTIFY_SOURCE=2 -U_FORTIFY_SOURCE 
>> -D_FORTIFY_SOURCE=2 -D_ISOC99_SOURCE -D_FILE_OFFSET_BITS=64 
>> -D_LARGEFILE_SOURCE -D_POSIX_C_SOURCE=200112 -D_XOPEN_SOURCE=600 -DPIC 
>> -DZLIB_CONST -DHAVE_AV_CONFIG_H -MM 
>> /<>/libavfilter/avf_showvolume.c | sed -e "/^#.*/d" -e 
>> "s,^[[:space:]]*avf_showvolume\\.o,libavfilter/avf_showvolume.o," > 
>> libavfilter/avf_showvolume.d
>> /<>/libavfilter/avf_showcqt.c:38:10: error: #include expects 
>> "FILENAME" or 
>>  #include FT_FREETYPE_H
>>   ^
> ...
>> -Wstrict-prototypes -Wempty-body -Wno-parentheses -Wno-switch 
>> -Wno-format-zero-length -Wno-pointer-sign -O3 -fno-math-errno 
>> -fno-signed-zeros -fno-tree-vectorize -Werror=format-security 
>> -Werror=implicit-function-declaration -Werror=missing-prototypes 
>> -Werror=return-type -Werror=vla -Wformat -fdiagnostics-color=auto 
>> -Wno-maybe-uninitialized   -c -o libavfilter/vf_drawbox.o 
>> /<>/libavfilter/vf_drawbox.c
>> /<>/libavfilter/vf_drawtext.c:69:10: error: #include expects 
>> "FILENAME" or 
>>  #include FT_FREETYPE_H
>>   ^
>>
>> /<>/libavfilter/vf_drawtext.c:70:10: error: #include expects 
>> "FILENAME" or 
>>  #include FT_GLYPH_H
>>   ^~
>>
>> /<>/libavfilter/vf_drawtext.c:71:10: error: #include expects 
>> "FILENAME" or 
>>  #include FT_STROKER_H
>>   ^~~~
>>
>> /<>/libavfilter/vf_drawtext.c:275:10: error: #include expects 
>> "FILENAME" or 
>>  #include FT_ERRORS_H
>>   ^~~

These "errors" are a red herring: they happen during dependency
generation and are thus harmless. They can also be seen when building
in unstable. (They now get suppressed upstream.)

The real problems are test failures:
[...]
Test vsynth1-svq1 failed. Look at tests/data/fate/vsynth1-svq1.err for details.
[...]
Test vsynth3-svq1 failed. Look at tests/data/fate/vsynth3-svq1.err for details.
[...]
Test vsynth2-svq1 failed. Look at tests/data/fate/vsynth2-svq1.err for details.

These worked fine when I tested building with gcc-6 6-20151211-1.
So this seems to be a regression introduced during the last month.

Interestingly these tests pass upstream [1] when building with
"gcc 6.0.0 (GCC) 20160119 (experimental)".
So this either got fixed between 17. and 19. January, or it is a
Debian specific problem.

The problem is in svq1_encode_plane in libavcodec/svq1enc.c.
For P-frames, the decoded_plane buffer gets overwritten with wrong
values:
$ cd debian/standard
$ export 
LD_LIBRARY_PATH="libavcodec:libavdevice:libavfilter:libavformat:libavresample:libavutil:libpostproc:libswresample:libswscale"
$ gdb --args ./ffmpeg -nostdin -nostats -cpuflags all -f rawvideo -s 352x288 
-pix_fmt yuv420p -threads 1

Bug#812143: Wide character in print at /usr/bin/ts line 126, <> line 1.

2016-01-20 Thread Nicolas Schier

Dear Evgeny,

> After I upgraded Perl to version 5.22, ts started printing a warning 
> before every line, like this:
> 
> Wide character in print at /usr/bin/ts line 126, <> line 1.

could you please supply your locale settings (the output of 'locale') 
and an example of a 'ts' output line?

Thanks and kind regards,
Nicolas


signature.asc
Description: PGP signature

Bug#811458: RFS: nanopolish

2016-01-20 Thread Afif Elghraoui

Hello,
Since fast5 was accepted (Thanks for uploading it, Andreas), nanopolish
is now ready to go in. Could someone please upload this one?

git+ssh://git.debian.org/git/debian-med/nanopolish.git
http://anonscm.debian.org/debian-med/nanopolish.git

Many thanks and regards
Afif

-- 
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#808430: perl-modules-5.22: after the upgrade to perl 5.22, the Module::Build module is no longer present

2016-01-20 Thread Dominic Hargreaves

On Sun, Jan 17, 2016 at 11:40:34PM +0100, gregor herrmann wrote:
> I was curious if I can reproduce this issue [0]:
> 
> - jessie chroot (from cowbuilder)
> - rm /etc/apt/apt.conf.d/15pbuilder
>   (APT::Install-Recommends "false";)
> - aptitude install libmodule-build-perl+M
> - make sure libmodule-build-perl is really marked auto
> - sed -i -e 's/jessie/stretch/g' /etc/apt/sources.list
> - aptitude update
> - aptitude dist-upgrade
> - allow aptitude to remove perl-modules
> - let the upgrade run
> 
> Result:
> libmodule-build-perl is still installed at this point. Good.
> Opening aptitudes TUI then suggests to remove a bunch of perl
> packages, among them libmodule-build-perl. Bad.
> 
> Without aptitude:
> - jessie chroot (from cowbuilder)
> - rm /etc/apt/apt.conf.d/15pbuilder
>   (APT::Install-Recommends "false";)
> - apt-get install libmodule-build-perl
> - apt-mark auto libmodule-build-perl
> - sed -i -e 's/jessie/stretch/g' /etc/apt/sources.list
> - apt-get update
> - apt-get dist-uprade
> 
> Result:
> This throws away some automatically installed packages but not
> libmodule-build-perl. Good.
> apt-get autoremove then removes it. Bad.

Or to put it another way: system working as designed. This isn't
a problem with the tools, it's that at the end of the day there
is no real way to express that a package is being split out from
another one.

If someone has the energy to propose a Recommends-like field which is
'sticky' during upgrades, that would be an interesting discussion to have.

The problem is that it would be a field which would introduce some
weird unreproducibility - because a system seeded with a fixed set of
manually requested packages at different times would result in a
different set of installed packages; which seems contrary to the
spirit of the thing.

> The interesting point is that in both cases, libmodule-build-perl is
> _not_ removed during the dist-upgrade. But it's "marked" as a removal
> candidate and would need manual intervention to keep it.
> 
> 
> For the future we might try to remember that having a Recommends in a
> package which gets removed leaves the recommended package in an
> "orphaned" state from the POV of apt{itude,-get}.
> (In this case, IIRC, the decision to replace perl-modules by a
> versioned package came only after the jessie release ...)

I don't think we can really do more than we already do - although
in this particular case, having dh-make-perl depend on 
libmodule-build-perl as you suggested latest wouldn't be a bad idea.

Cheers,
Dominic.

Bug#808610: libxapian22: xapian database corruption causes recollindex loop

2016-01-20 Thread Olly Betts

Control: tag -1 + jessie

On Wed, Jan 20, 2016 at 02:45:15PM +1300, Olly Betts wrote:
> On Mon, Dec 28, 2015 at 02:45:43AM +, Olly Betts wrote:
> > On Mon, Dec 21, 2015 at 01:14:40PM +, John Kozak wrote:
> > > I run recollindex from a crontab every night against a corpus of pdf
> > > files. After upgrading to jessie, every few days this update would go
> > > into a cpu busy loop, requiring the process to be killed and the
> > > database to be deleted and remade.  Rebuilding `xapian-core` using the
> > > 1.2.21_git68 version of xapian-core from the xapian project has fixed 
> > > this.
> 
> That means whatever the fix is, it's in 1.2.22, so packaging the latest
> upstream version will address this for unstable and testing.

Now uploaded, so we just need to determine the targetted fix for jessie
(and potentially older releases if they are also affected).

Cheers,
Olly

Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)

2016-01-20 Thread adrian15


El 18/01/16 a las 14:00, Thomas Schmitt escribió:

So any bootloader is made primary by leaving out -eltorito-alt-boot.


There is no "primary" or "secondary" on the level of boot images
and loaders. (Of course you may call them this way in your project.)

There are first, second, third ... El Torito boot images or MBR, GPT,
APM partition entries.
The sequence is just needed because not all can be first in the list.

The boot firmware inspects the medium for its known lures,
picks a tasty one, and follows it to the boot loader or kernel.


So, yes, I'm the one who invented the term primary for live-build. 
Actually, it was not meant for alt El Torito boot entries (or non first 
entries as you clarify).


The first idea was to add both syslinux and grub-pc in the same image. 
Grub-pc would be the one installed to be boot but syslinux files would 
be there for Multi-USB tools to know how to understand the iso and put 
it into an USB.


The Grub-pc bits were thought in first place for Super Grub2 Disk (which 
it is Grub2 cfg files mainly).


(Now that I think of the current 'check primary bootloader role' 
functions unable me to perform that Super Grub2 Disk Debian Live that 
included the Syslinux bits too. Anyways I'll find a workaround for that 
in the future. Not a priority right now.)


Now primary means: "First lure" and secondary means "Second lure" by 
your definition.


Currently there's no way to stop you from requesting:

--bootloaders="syslinux,grub-efi,syslinux-efi"

Given the way that both grub-efi and syslinux-efi use:

/efi/boot/bootia32.efi
and
/efi/boot/bootx64.efi

the last one to be run would overwrite the first one efi files.



You can probably use only one legacy bootloader but syslinux-efi and
grub-efi use different files so it should be possible to install both.
I am not sure how selecting one or the other would work, though.


You can offer several EL Torito boot images for BIOS, indeed.
It will depend on your BIOS what it does in this case.

Interesting.


There can be only one MBR, though. So you would have to hop
by MBR x86 code to a standalone program which chooses among
the BIOS suitable El Torito boot images.

With EFI it makes few sense to offer more than one El Torito
boot image or EFI System Partition. UEFI 2.4 rather prescribes to
handle all alternatives inside the FAT filesystem. The firmware
will start the \EFI\BOOT\BOOT*.EFI binary which it deems suitable
for its processor type.
This binary is quite free in its further proceedings.

So... How would you go about for a:

--bootloaders="syslinux,grub-efi,syslinux-efi"

to make sense if, as I have stated earlier (although I might have missed 
something there) they would overwrite their /efi/boot/boot*efi files ?




adrian15
--
Support free software. Donate to Super Grub Disk. Apoya el software 
libre. Dona a Super Grub Disk. http://www.supergrubdisk.org/donate/

Bug#812154: texlive-extra-utils: /usr/bin/texdef shows errors "Unescaped left brace..."

2016-01-20 Thread Igor Liferenko

Package: texlive-extra-utils
Version: 2015.20151225-2
Severity: normal

Dear Maintainer,

In texlive-extra-utils 2015.20151016-1 texdef worked like this:

$ texdef leavevmode

\leavevmode:
macro:->\unhbox \voidb@x 

In current texlive-extra-utils it works like this:

$ texdef leavevmode
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/^\\\@protected\@testopt { <-- HERE ?\\.*? }? *(.*?) / at 
/usr/bin/texdef line 391.
Unescaped left brace in regex is deprecated, passed through in regex; marked by 
<-- HERE in m/^\\\@testopt { <-- HERE ?(\\.*?) }?/ at /usr/bin/texdef line 394.

\leavevmode:
macro:->\unhbox \voidb@x 

Best regards,
Igor

-- Package-specific info:
IMPORTANT INFORMATION: We will only consider bug reports concerning
the packaging of TeX Live as relevant. If you have problems with
combination of packages in a LaTeX document, please consult your
local TeX User Group, the comp.text.tex user group, the author of
the original .sty file, or any other help resource. 

In particular, bugs that are related to up-upstream, i.e., neither
Debian nor TeX Live (upstream), but the original package authors,
will be closed immediately.

   *** The Debian TeX Team is *not* a LaTeX Help Desk ***

If you report an error when running one of the TeX-related binaries 
(latex, pdftex, metafont,...), or if the bug is related to bad or wrong
output, please include a MINIMAL example input file that produces the
error in your report.

Please run your example with
(pdf)latex -recorder ...
(or any other program that supports -recorder) and send us the generated
file with the extension .fls, it lists all the files loaded during
the run and can easily explain problems induced by outdated files in
your home directory.

Don't forget to also include minimal examples of other files that are 
needed, e.g. bibtex databases. Often it also helps
to include the logfile. Please, never send included pictures!

If your example file isn't short or produces more than one page of
output (except when multiple pages are needed to show the problem),
you can probably minimize it further. Instructions on how to do that
can be found at

http://www.minimalbeispiel.de/mini-en.html (english)

or 

http://www.minimalbeispiel.de/mini.html (german)

##
minimal input file


##
other files

##
 List of ls-R files

-rw-r--r-- 1 user staff 2434 Jan 21 09:39 /usr/local/share/texmf/ls-R
-rw-r--r-- 1 root root 1418 Jan 21 09:39 /var/lib/texmf/ls-R
-rw-r--r-- 1 user staff 2434 Jan 21 09:39 /usr/local/share/texmf/ls-R
lrwxrwxrwx 1 root root 29 Oct 14 10:48 /usr/share/texmf/ls-R -> 
/var/lib/texmf/ls-R-TEXMFMAIN
lrwxrwxrwx 1 root root 31 Dec 26 09:48 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
lrwxrwxrwx 1 root root 31 Dec 26 09:48 /usr/share/texlive/texmf-dist/ls-R -> 
/var/lib/texmf/ls-R-TEXLIVEDIST
##
 Config files
-rw-r--r-- 1 user staff 107 Jan 20 17:33 /usr/local/share/texmf/web2c/texmf.cnf
lrwxrwxrwx 1 root root 33 Dec 26 09:48 /usr/share/texmf/web2c/fmtutil.cnf -> 
/var/lib/texmf/fmtutil.cnf-DEBIAN
lrwxrwxrwx 1 root root 32 Dec 26 09:48 /usr/share/texmf/web2c/updmap.cfg -> 
/var/lib/texmf/updmap.cfg-DEBIAN
-rw-r--r-- 1 root root 3095 Jan 20 17:32 
/var/lib/texmf/tex/generic/config/language.dat
##
 Files in /etc/texmf/web2c/
total 8
-rw-r--r-- 1 root root 283 Oct 14 10:48 mktex.cnf
-rw-r--r-- 1 root root 475 Jan 20 17:29 texmf.cnf
##
 md5sums of texmf.d
ca40c66f144b4bafc3e59a2dd32ecb9c  /etc/texmf/texmf.d/00debian.cnf

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

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

Versions of packages texlive-extra-utils depends on:
ii  python2.7   2.7.11-2
ii  python3 3.4.3-7
ii  tex-common  6.04
ii  texlive-base2015.20151225-1
ii  texlive-binaries2015.20150524.37493-7+b1
ii  texlive-latex-base  2015.20151225-1

Versions of packages texlive-extra-utils recommends:
ii  ghostscript 9.16~dfsg-2
ii  libfile-homedir-perl1.00-1
ii  libyaml-tiny-perl   1.69-1
ii  ruby1:2.2.4
ii  ruby2.2 [ruby-interpreter]  2.2.3-2
ii  texlive-latex-recommended   2015.20151225-1

Versions of packages texlive-extra-utils suggests:
pn  chktex  
pn  dvidvi  
pn  dvipng  
pn  fragmaster  
pn  lacheck 
pn  latexdiff   
pn  latexmk 
pn  purifyeps   
pn  xindy   

Versions of packages tex-common depends on:
ii  dpkg  1.18.4
ii  ucf   3.0031

Versions of packages tex-common suggests:
ii  debhelper  9.20151225

Versions of

Bug#812153: [Pkg-utopia-maintainers] Bug#812153: Bug#812153: Bug#812153: policykit-1: allows ordinary users to mount filesystems

Am 21.01.2016 um 04:18 schrieb Christoph Anton Mitterer:
> On Thu, 2016-01-21 at 04:13 +0100, Michael Biebl wrote:
>> This behaviour has been since 2000 or so, since at least the
>> introduction of hal and pmount.
> 
> Then one has still some 30 years before where it has been different...

Right, since we had removable media 30 years ago.

> 
>> You don't gain anything security wise by not allowing removable media
>> to
>> be mounted. The only thing it will cause for sure is inconvenience.
> 
> As I told you before, this is not true,.. you may have easily have
> secured terminals where people can log in, but where they cannot e.g.
> physically access such devices.

In such a very specialised situation you can easily lock down the
configuration. For such a setup you will most likely need custom
configuration anyway to be secure.
A default configuration needs to usable by the majority of users.

>> Please don't reopen anymore, or I'll ask bts listmaster to block your
>> address.
> 
> Ah quite funny... "do as I want... or I use dictatorship methods"...
> 
> It's quite disturbing when a real issue is reported, that this is
> simply done away by threatening people.

There is no "real issue". Point.
You are making a big fuss for nothing and wasting everyones time, mine
included. I'm not willing to tolerate that.


Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Bug#812168: skyeye: FTBFS using clang instead of gcc

Package: skyeye
Severity: minor
Tags: patch
User: pkg-llvm-t...@lists.alioth.debian.org
Usertags: clang-ftbfs

Hello,

Using the rebuild infrastructure, your package fails to build with clang
(instead of gcc).

Detected this kind of error:
http://clang.debian.net/status.php?version=3.6.0=FUNCTION_RETURNS_VALUE

Full build log is available here:
http://clang.debian.net/logs/2015-03-25/skyeye_1.2.5-4_unstable_clang.log

I have attached a patch to fix this error.

Regards,
--Arthur Marble


-- System Information:
Debian Release: sid (unstable)
Architecture: amd64 (x86_64)
Kernel: Linux 4.2.0-1-amd64
Locale: LANG=en_US.UTF-8, LC_CTYPE="en_US.UTF-8"
Shell: /bin/sh linked to /bin/dash
Compiler: Debian clang version 3.6.2-3 (based on LLVM 3.6.2)

--- a/arch/arm/common/armsupp.c
+++ b/arch/arm/common/armsupp.c
@@ -693,7 +693,7 @@
 		//chy 2004-07-19 should fix in the future
 		//printf("SKYEYE ARMul_MRC,NOT ALLOWed UndefInstr  CPnum is %x, instr %x\n",CPNum, instr);
 		ARMul_UndefInstr (state, instr);
-		return;
+		return 0;
 	}
 
 	cpab = (state->MRC[CPNum]) (state, ARMul_FIRST, instr, );
--- a/arch/bfin/mach/bf533_io.c
+++ b/arch/bfin/mach/bf533_io.c
@@ -864,7 +864,7 @@
 	default:
 		IO_ERR;
 	}
-	return;
+	return 0;
 
 }
 static bu32
@@ -883,7 +883,7 @@
 	default:
 		IO_ERR;
 	}
-	return;
+	return 0;
 
 }
 static void
--- a/arch/bfin/mach/bf537_io.c
+++ b/arch/bfin/mach/bf537_io.c
@@ -870,7 +870,7 @@
 	default:
 		IO_ERR;
 	}
-	return;
+	return 0;
 
 }
 static bu32
@@ -889,7 +889,7 @@
 	default:
 		IO_ERR;
 	}
-	return;
+	return 0;
 
 }
 static void
--- a/arch/coldfire/common/cf_arch_interface.c
+++ b/arch/coldfire/common/cf_arch_interface.c
@@ -41,7 +41,7 @@
 #include "skyeye_config.h"
 char Run_Exit = 0;
 
-SKYEYE_DBGR_DEFAULT_CHANNEL(run);
+/* SKYEYE_DBGR_DEFAULT_CHANNEL(run); // Unused macro? */
 
 static int stop_now = 0;
 
--- a/arch/coldfire/common/exception.c
+++ b/arch/coldfire/common/exception.c
@@ -10,7 +10,7 @@
 
 #include "coldfire.h"
 
-SKYEYE_DBGR_DEFAULT_CHANNEL(exception);
+/* SKYEYE_DBGR_DEFAULT_CHANNEL(exception);  // Unused macro? */
 
 static short exception_pending = 0;
 static unsigned int (*iack_func[8])(unsigned int interrupt_level)
--- a/arch/coldfire/common/i.c
+++ b/arch/coldfire/common/i.c
@@ -10,7 +10,7 @@
 #include "coldfire.h"
 
 
-SKYEYE_DBGR_DEFAULT_CHANNEL(i);
+/* SKYEYE_DBGR_DEFAULT_CHANNEL(i);  // Unused Macro? */
 
 #define MALLOC_STEP 16
 struct _Instruction *Instruction = NULL;
--- a/arch/coldfire/common/handlers.c
+++ b/arch/coldfire/common/handlers.c
@@ -11,7 +11,7 @@
 
 #include "coldfire.h"
 
-SKYEYE_DBGR_DEFAULT_CHANNEL(handlers);
+/* SKYEYE_DBGR_DEFAULT_CHANNEL(handlers);  // Unused macro? */
 
 
 void SR_Set(short Instr, int Source, int Destination, int Result)
--- a/arch/coldfire/common/ram.c
+++ b/arch/coldfire/common/ram.c
@@ -15,7 +15,7 @@
 /*#define SKYEYE_DBGR_OFF*/
 #include "coldfire.h"
 
-SKYEYE_DBGR_DEFAULT_CHANNEL(ram);
+/* SKYEYE_DBGR_DEFAULT_CHANNEL(ram);  // Unused macro? */
 
 void ram_init(void);
 static void ram_setup(struct _memory_segment *s);
--- a/arch/coldfire/common/memory.c
+++ b/arch/coldfire/common/memory.c
@@ -31,7 +31,7 @@
 /* memory core copy with values used when reset */
 static struct _memory_core memory_core_reset_values;
 
-TRACER_DEFAULT_CHANNEL(memory);
+TRACER_DEFAULT_CHANNEL(char memory);
 
 
 static struct _memory_module *memory_module = NULL;
--- a/arch/coldfire/instruction/i_div.c
+++ b/arch/coldfire/instruction/i_div.c
@@ -63,7 +63,7 @@
 
 int DIVSTime[8]={18, 20, 20, 20, 20, -1, -1, -1};
 
-SKYEYE_DBGR_DEFAULT_CHANNEL(i_div);
+/* SKYEYE_DBGR_DEFAULT_CHANNEL(i_div);  // Unused macro? */
 
 
 #define DIV_W_REGISTER(word) 	(((word)&0x0e00) >> 9)
--- a/arch/mips/common/dcache.c
+++ b/arch/mips/common/dcache.c
@@ -242,7 +242,8 @@
 int i;
 
 // A direct memory access.
-return mips_mem_read(pa, x, size);
+mips_mem_read(pa, x, size);
+	return;
 }
 /* Store data to the virtual address (va). The address translation has already
  * been performed and the physical address is (pa). The coherency algorithm to
@@ -336,5 +337,6 @@
 store(MIPS_State* mstate, UInt32 data, VA va, PA pa, int size)  {
 UInt32 addr=bits(pa, 31, 0);
 UInt32 x = data;
-return mips_mem_write(pa, , size);
+mips_mem_write(pa, , size);
+	return;
 }
--- a/utils/debugger/ppc_regdefs.c
+++ b/utils/debugger/ppc_regdefs.c
@@ -96,7 +96,7 @@
 			case 69:
 //XER = v;
 gCPU.xer = v;
-return;
+break;
 			case 70:
 //FPSCR = v;
 gCPU.fpscr = v;

Bug#811921: ffmpeg: FTBFS with GCC 6: misc errors

2016-01-20 Thread Timothy Gu

Hi,

On Thu, Jan 21, 2016 at 02:39:41AM +0100, Andreas Cadhalpun wrote:
> Interestingly these tests pass upstream [1] when building with
> "gcc 6.0.0 (GCC) 20160119 (experimental)".
> So this either got fixed between 17. and 19. January, or it is a
> Debian specific problem.

It’s definitely not a Debian-specific problem. See [1]: a build with GCC
6.0.0 20160116 failed as well [2].

[1]: http://fatebeta.ffmpeg.org/history/x86_64-archlinux-gcc-experimental
[2]: 
http://fatebeta.ffmpeg.org/report/x86_64-archlinux-gcc-experimental/20160116195307

Timothy

Bug#812093: libimager-perl: FTBFS: Failed 1/65 test programs. 0/4481 subtests failed.

2016-01-20 Thread Tony Cook

On Wed, Jan 20, 2016 at 10:38:27PM +0200, Niko Tyni wrote:
> On Wed, Jan 20, 2016 at 02:42:04PM +0100, Chris Lamb wrote:
> > Source: libimager-perl
> > Version: 1.004+dfsg-1
> > Severity: serious
> > Justification: fails to build from source
> > User: reproducible-bui...@lists.alioth.debian.org
> > Usertags: ftbfs
> > X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
> 
> > libimager-perl fails to build from source in unstable/amd64:
> 
> It broke with src:giflib 5.1.2-0.1 -> 5.1.1-0.2. Don't know
> why yet.
> 
> % perl -MImager -e 'Imager->new->read(type => "gif", file => 
> "GIF/testimg/expected.gif") or die'
> 
> dies with the new giflib but not the old one.
> 
> Cc'ing Matthias Klose as a heads-up, he uploaded 5.1.1-0.2.

The read failures are caused by a bug present in both 5.1.1 and 5.1.2,
partly fixed in giflib git at commit
ef0cb9b4be572262b49fbc26fb2348683f44a517.

A similar fix is required to DGifOpen() for Imager's GIF support to
work (reliably), reported upstream as
https://sourceforge.net/p/giflib/bugs/81/

Without the fix the Private member RunningBits isn't initialized,
leaving RunningBits as whatever happened to be in memory at that
point, so the check in DGifSetupDecompress() has a large chance of
failing with a D_GIF_ERR_READ_FAILED error.

Adding the initialization allows Imager to pass its tests.

That said, there is a bug in that test script, since its custom ok()
doesn't have a prototype, the tests on line 65 and 78 pass when they
should fail, leading to the crash on line 79 when it tries to compare
uninitialized images.

Adding a prototype fixes it, though I'll probably end up tossing the
custom code and using Test::More.

Tony

Bug#785272: This bug showed up again

2016-01-20 Thread Mike Gabriel

Hi,

On  Do 21 Jan 2016 03:15:51 CET, Individual User wrote:

-- Forwarded message --
From: Individual User 
Date: Thu, 21 Jan 2016 09:14:19 +0700
Subject: This bug showed up again
To: 785...@bugs.debian.org

Hi,

This bug showed up again in recent updates in debian testing.

I checked - window-list.c changed a little from previous releases.
Please apply the new patch again. It is in the attachment.

Thanks

I have unarchived #785275 and diverted your mail to the bug. It is now  
open again.

The patch must have been removed during one of the two major release bumps.

I will take a look with the next upload round.

Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/mailxchange/kronolith/fb.php?u=m.gabriel%40das-netzwerkteam.de

pgpkeJMmKNRYC.pgp
Description: Digitale PGP-Signatur

Bug#812017: yapet: FTBFS with GCC 6: return-statement with a value

2016-01-20 Thread Salvatore Bonaccorso

Control: tags -1 + confirmed

Hi Martin,

On Tue, Jan 19, 2016 at 08:32:53PM -0800, Martin Michlmayr wrote:
> Package: yapet
> Version: 1.0-5
> Severity: important
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-6
> 
> 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.

Thanks, confirmed.

Regards,
Salvatore

Bug#812172: gmrun: Incorrect $TERM value in gmrun's children

2016-01-20 Thread Vladimir Kudrya

Package: gmrun
Version: 0.9.2-2.1+b1
Severity: normal

Dear Maintainer, child processes of gmrun have incorrect value of TERM variable.
It is set to 'x-terminal-emulator'. This does not seem to be affected by
'Terminal' seting in gmrunrc, some other logic is the cause.

To reproduce: launch mssh or synaptic through gmrun. With mssh it will be
apparent right away, synaptic will have problems with terminal-dependent tools
like whiptail complaining about unknown terminal.


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

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

Versions of packages gmrun depends on:
ii  libatk1.0-0  2.18.0-1
ii  libc62.21-6
ii  libcairo21.14.4-1
ii  libfontconfig1   2.11.0-6.3
ii  libfreetype6 2.6.1-0.1
ii  libgcc1  1:5.3.1-5
ii  libgdk-pixbuf2.0-0   2.32.3-1
ii  libglib2.0-0 2.46.2-3
ii  libgtk2.0-0  2.24.29-1
ii  libpango-1.0-0   1.38.1-1
ii  libpangocairo-1.0-0  1.38.1-1
ii  libpangoft2-1.0-01.38.1-1
ii  libpopt0 1.16-10
ii  libstdc++6   5.3.1-5

gmrun recommends no packages.

gmrun suggests no packages.

-- no debconf information

Bug#812173: apt fails to distinguish between different Provides of different package versions

2016-01-20 Thread Johannes Schauer

Package: apt
Version: 1.2
Severity: serious
Justification: Policy 7.5
Control: affects -1 + src:libjpeg9

Hi,

steps to reproduce for apt-get build-dep:

$ sudo debootstrap --include=equivs sid debian-apt-bug  
http://snapshot.debian.org/archive/debian/20160119T151500Z
$ echo deb-src http://snapshot.debian.org/archive/debian/20160119T151500Z 
sid main | sudo tee -a debian-apt-bug/etc/apt/sources.list
$ sudo chroot debian-apt-bug apt-get update
$ sudo chroot debian-apt-bug apt-get build-dep libjpeg9
Reading package lists... Done
Building dependency tree... Done
The following NEW packages will be installed:
  autoconf automake autopoint build-essential cpp cpp-5 dh-autoreconf g++ 
g++-5 gcc gcc-5 libasan2 libatomic1
  libc-dev-bin libc6-dev libcc1-0 libcilkrts5 libgcc-5-dev libisl15 libitm1 
liblsan0 libmpc3 libmpfr4 libmpx0
  libquadmath0 libsigsegv2 libstdc++-5-dev libtool libtsan0 libubsan0 
linux-libc-dev m4
0 upgraded, 32 newly installed, 0 to remove and 0 not upgraded.
Need to get 102 MB of archives.
[...]
Get:7 http://snapshot.debian.org/archive/debian/20160119T151500Z sid/main 
amd64 automake all 1:1.15-3 [735 kB]
[...]
Selecting previously unselected package automake.
Preparing to unpack .../automake_1%3a1.15-3_all.deb ...
Unpacking automake (1:1.15-3) ...
[...]
$ sudo chroot debian-apt-bug apt-get source --build libjpeg9
dpkg-checkbuilddeps: error: Unmet build dependencies: automake-1.14
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; 
aborting
dpkg-buildpackage: warning: (Use -d flag to override.)
Build command 'cd libjpeg9-9a && dpkg-buildpackage -b -uc' failed.

As you can see from above, dpkg-checkbuilddeps and apt-get build-dep
disagree. This might be because unstable currently carries two automake
packages in different versions:

Package: automake
Source: automake-1.14
Version: 1:1.14.1-4
Architecture: all
Provides: automake-1.14, automaken
Depends: autoconf (>= 2.65), autotools-dev (>= 20020320.1)
Conflicts: automake (<< 1:1.4-p5-1), automake1.10-doc, automake1.5 (<< 
1.5-2), automake1.6 (<< 1.6.1-4)
Multi-Arch: foreign

Package: automake
Source: automake-1.15
Version: 1:1.15-3
Architecture: all
Provides: automake-1.15, automaken
Depends: autoconf (>= 2.65), autotools-dev (>= 20020320.1)
Suggests: autoconf-doc, gnu-standards
Conflicts: automake (<< 1:1.4-p5-1), automake1.10-doc, automake1.5 (<< 
1.5-2), automake1.6 (<< 1.6.1-4)
Multi-Arch: foreign

Steps to reproduce for apt-get install:

$ cat > control << END
> Package: dummy
> Depends: automake-1.14
> END
$ equivs-build control
$ apt-get install ./dummy_1.0_all.deb
The following packages have unmet dependencies:
 dummy : Depends: automake-1.14
E: Unable to correct problems, you have held broken packages.

It seems automake (= 1:1.14.1-4) provides automake-1.14 while automake
(= 1:1.15-3) provides automake-1.15. It might be that somehow apt sees
that "automake" provides automake-1.14 but does not store which version
of "automake" provides it and just either installs the newest one in the
"apt-get build-dep" case or only picks the newest one as a candidate and
then fails to satisfy the dependency because that version doesn't
provide automake-1.14.

Ideally, apt should see that there are different versions of the same
package with the same pin value but different provides and pick the one
that satisfies the dependency even if it's of a lower version. After
all, both packages are part of the same suite. Though with apt's
behaviour of selecting only the highest version as the candidate I can
see why this will not be happening and maybe instead automake should
change how they do their virtual packages. But then again, on what
grounds should automake change their provides? Only because of an apt
limitation? As far as I can see they are policy compliant and other
resolvers like dose3 or aspcud will happily find a solution.

The clear policy violation here is the "apt-get build-dep" problem
because apt installs a package that is not satisfying the build
dependency at hand. This has to be fixed. At least just fail in the same
way as during binary package installation.

What do you think?

cheers, josch

Bug#810814: libgnutls26: Encrypted LDAP connection doesn't work after libgnutls26 update

2016-01-20 Thread Frederic Van Espen

On Wed, Jan 20, 2016 at 11:10 AM, Frederic Van Espen
 wrote:
> I should add that running ldapsearch works fine though:

Also, we have this in our configuration file:
tls_cipher_suite = SECURE256

When I comment that it seems to work fine. Before the upgrade it
worked fine just like this though.

Best,

Frederic

Bug#812174: ITP: letsencrypt-sh -- ACME client implemented in Bash

2016-01-20 Thread Daniel Beyer

Package: wnpp
Severity: wishlist
Owner: Daniel Beyer 


* Package name: letsencrypt-sh
  Version : 0.0.0~2016.01.21~git23b0ef5
  Upstream Author : Lukas Schauer 
* URL : https://github.com/lukas2511/letsencrypt.sh
* License : Expat
  Programming Lang: Bash
  Description : ACME client implemented in Bash

The letsencrypt.sh ACME client allows signing certificates with an
ACME server, like the one provided by the Let’s Encrypt certificate
authority (letsencrypt.org). It is implemented as a relatively simple
Bash script, which uses curl to communicate with the ACME server and
OpenSSL to deal with keys, sign requests and certificates.
.
The ACME (Automated Certificate Management Environment) protocol makes
it possible to automatically obtain browser-trusted certificate.



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

Bug#809882: fix is in git, not uploaded

2016-01-20 Thread Tobias Frost

Control: reopen -1

closed by accident as not yet uploaded.

Bug#812145: sysvinit: 2.88dsf-59.3 generates bad initrd.img and boot on hppa

2016-01-20 Thread John David Anglin

Package: sysvinit
Version: 2.88dsf-59.3+b1
Severity: important

Dear Maintainer,

With initramfs-tools-core_0.121_all.deb, initramfs-tools_0.121_all.deb and
initscripts_2.88dsf-59.3+b1_hppa.deb, boot with a custom kernel fails with
the following errors:

[..deleted..]
SGI XFS with ACLs, security attributes, realtime, no debug enabled
Begin: Will now check root file system ... fsck from util-linux 2.27.1
[/sbin/fsck.xfs (1) -- /dev/sdc5] fsck.xfs -a /dev/sdc5 
/sbin/fsck.xfs: XFS file system.
done.
XFS (sdc5): Mounting V4 Filesystem
XFS (sdc5): Ending clean mount
done.
run-init: opening console: No such file or directory
Target filesystem doesn't have requested /sbin/init.
run-init: opening console: No such file or directory
run-init: opening console: No such file or directory
run-init: opening console: No such file or directory
run-init: opening console: No such file or directory
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
run-init: : No such file or directory
No init found. Try passing init= bootarg.
modprobe: module i8042 not found in modules.dep
modprobe: module ehci-orion not found in modules.dep
modprobe: module uhci-hcd not found in modules.dep
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver


BusyBox v1.22.1 (Debian 1:1.22.0-16) built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
(initramfs) ls
bin  dev  init proc run  scripts  tmp
conf etc  lib  root sbin sys  var

The kernel boots successfully if initramfs-tools-core is purged,
initscripts_2.88dsf-59.2_hppa.deb and initramfs-tools_0.120_all.deb
reinstalled, and initrd.img regenerated.

Regards,
Dave Anglin

-- System Information:
Debian Release: stretch/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: hppa (parisc64)

Kernel: Linux 3.18.25+ (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_CA.utf8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages sysvinit depends on:
ii  init 1.25
ii  libc62.21-6+b1
ii  libselinux1  2.4-3
ii  libsepol12.4-2

sysvinit recommends no packages.

sysvinit suggests no packages.

-- no debconf information

Bug#812146: FTBFS with libc6 2.22 from experimental

Package: afnix
Version: 2.5.1-1
Severity: important

afnix fails to build with libc6 2.22-0experimental1 from experimental.

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> g++ -g -O2 -fstack-protector-strong -Wformat -Werror=format-security   -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -std=c++11 -Wall 
> -Werror -fno-builtin -MMD -pthread -fPIC  -I. -I../acf -o csys.o -c 
> csys.cxx
> csys.cxx: In function 'char* afnix::c_username()':
> csys.cxx:193:49: error: null argument where non-null required (argument 5) 
> [-Werror=nonnull]
>  if (getpwuid_r (uid, , buf, 1024, NULL) != 0) {
>  ^
> cc1plus: all warnings being treated as errors
> ../../../../cnf/mak/afnix-rule.mak:103: recipe for target 'csys.o' failed
> make[6]: *** [csys.o] Error 1

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

Bug#731429: gdm3: Set up tap to click by default

2016-01-20 Thread Francois Gouget


This bug is still present in gdm3 3.18.

After many false leads I found how to enable tap-to-click in gdm3 in the 
GNOME bug below:

Bug 747811 - Mouse settings not getting propagated to GDM 
https://bugzilla.gnome.org/show_bug.cgi?id=747811

The instructions need slight adjustments so here they are for Debian:

$ xhost +SI:localuser:Debian-gdm
$ su

# DISPLAY=:0 sudo -u gdm gsettings set 
org.gnome.desktop.peripherals.touchpad tap-to-click true

I'm not sure why the access permissions of the logged in user are 
relevant to the gdm3 configuration but they proved essential. Of course 
you'd immediately cancel the effect of the xhost command, typically by 
logging out and back in. Plus you want to test that tap-to-click anyway, 
right?


I thought this could easily be turned into a way to enable 
tap-to-click by default, simply by putting the relevant dconf 
setting in /usr/share/gdm/dconf/50-tap-to-click as follows:

cat >/usr/share/gdm/dconf/50-tap-to-click <  http://fgouget.free.fr/
"Lotto: A tax on people who are bad at math." -- unknown
  "Windows: Microsoft's tax on computer illiterates." -- WE7U

Bug#811714: FTBFS in unstable

retitle 811714 FTBFS: unknown type name 'matrix'; did you mean 
'Feel::tag::matrix'
severity 811714 serious
user debian-...@lists.debian.org
usertag 811714 - ftbfs-gcc-6
thanks

Sorry, this issue isn't related to GCC 6 (obviously, since *cough* you're
using clang).

Seems it's just a generic build failure in unstable.

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

Bug#812147: O: simpletal -- Simple TAL, TALES and METAL implementation

2016-01-20 Thread Mattia Rizzolo

Package: wnpp

The package's maintainer is not reachable anymore at his address, and
nobody in the team is interested in it, so I'm orphaning the package
now.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#804277: Consul builds from source now

2016-01-20 Thread Potter, Tim (Converged Cloud)

Hi there.  I’ve checked in a few fixes in the d/patches directory to fix the 
various unit
test failures.

Mostly it was errors caused by test fixture locations, but I had to merge some 
changes
in from newer commits and disable one test that required syslog to be running.


Tim.


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#811351: additional request...

2016-01-20 Thread Rick Thomas

> On Jan 20, 2016, at 2:54 PM, Aaro Koskinen  wrote:
> 
> I can add more verbose comments to mainline kernel .dts on how to
> enable serial port, and how to select between rs232/485. Andrew, do
> you want me to resend the current patches, or can it be done with an
> incremental patch?
> 
> However, Debian probably needs to provide its own documentation how to
> modify the .dtb (probably some example how to convert the dtb to source
> with dtc, then how to do the modifications, and compile the source back
> to dtb).
> 
> A.

Andrew (I think it was) suggested that the instructions for doing that could go 
on Martin’s web page, which anyone who wants to use Debian on OpenRD will need 
to reference anyway.

Martin, are you willing to do that?

I can (and will gladly) test any changes and help with debuging (if such is 
necessary) .

Rick

Bug#811140: RFS: y-u-no-validate/2013052401-5 [ITA] -- browser extension to make security exceptions temporary by default

2016-01-20 Thread Jakub Wilk


* Sean Whitton , 2016-01-17, 17:56:

* Replace get-orig-source.sh script with xpi-repack invoked by uscan.
uscan doesn't call xpi-repack, unless you ask it for it explicitly, 
and you didn't. But uscan does seem to repack jar files to tar.gz 
automatically. Perhaps that's what you meant?
Are you sure?  This output suggested to me that it is doing everything 
your script was doing (especially the last line):


,
| uscan: Unpacking ../y_u_no_validate-2013052401-sm+fx.xpi
| Unpacking ./chrome/y-u-no-validate.jar
| Unpacked xpi file.
| Successfully repacked ../y_u_no_validate-2013052401-sm+fx.xpi as 
../y-u-no-validate_2013052401.orig.tar.gz.
`


Now that I looked closer at devscripts, I conclude we're both 
wrong. :-P


uscan (>= 2.15.10) calls mk-origtargz, which calls "xpi-unpack" (not 
"xpi-repack").


(The tarball uscan produces is quite different than the current 
.orig.tar, because the former lacks top-level directory. So if I were 
you, I'd postpone the get-orig-source removal until next upstream 
release. But then, it's not a big deal...)


--
Jakub Wilk

Bug#811409: owfs: Package compiled without USB support

2016-01-20 Thread Piotr Górski

I have only one USB to 1Wire converter that works right now in something
that is very important to me so right now I can't test older versions.

When I was testing owfs installed from Debian's apt repo I have found in
logs:

Jan 17 21:05:08 fire OWFS[1604]: DEFAULT: ow_arg.c:(552) USB support
(intentionally) not included in compilation. Check LIBUSB, then reconfigure
and recompile.

Package build-depends on libusb-1.0-0-dev so autobuilders must have that.




2016-01-18 20:25 GMT+01:00 Vincent Danjean :

> severity 811409 normal
> tag 811409 +moreinfo
> thanks
>
> Le 18/01/2016 18:37, Piotr Górski a écrit :
> > Severity: grave
> > Justification: renders package unusable
>
> Only for some use cases (as for most bugs). I corrected the severity.
>
>
> > Dear Maintainer,
> >
> > Package available in Debian's APT repository has no USB support.
>
> It is configurated with "--enable-usb". That said, the 3.1p0-2 version
> tried to avoid the uneeded dependency on the old usb library and
> it is possible that an error occurs.
>   I do not have a USB adapter so I cannot test myself. I will need
> your help.
>   Can you:
> - check which versions of owfs work (or not) with USB adapters
>   http://snapshot.debian.org/package/owfs/ can help you to check
>   older packages (take care to replace/install all owfs related
>   packages, ie owfs-fuse, owserver, ..., not just only the owfs
>   meta package)
> - show me a trace example when USB works and when it does not
>   (the owfs debug option will help you here)
>
> > Package needs to be created locally using debuild to enable USB
> > support.
>
> Did you change anything in the packaging before running debbuild?
>
> If no, this is probably a build-depends problem (ie something
> installed on your machine and not in the autobuilders).
>
>   Regards,
> Vincent
>
> > Most users use USB to 1-Wire adaptors so package isn't
> > working "out-of-the-box".
>
> >
> > -- System Information:
> > Debian Release: stretch/sid
> >   APT prefers testing
> >   APT policy: (500, 'testing')
> > Architecture: i386 (i686)
> >
> > Kernel: Linux 4.3.0-1-686-pae (SMP w/1 CPU core)
> > Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/dash
> > Init: systemd (via /run/systemd/system)
> >
> > Versions of packages owfs depends on:
> > ii  owfs-fuse  3.1p0-2
> > ii  owftpd 3.1p0-2
> > ii  owhttpd3.1p0-2
> > ii  owserver   3.1p0-2
> >
> > owfs recommends no packages.
> >
> > Versions of packages owfs suggests:
> > ii  owfs-doc  3.1p0-2
> >
> > -- no debconf information
> >
>
>
> --
> Vincent Danjean   GPG key ID 0xD17897FA vdanj...@debian.org
> GPG key fingerprint: 621E 3509 654D D77C 43F5  CA4A F6AE F2AF D178 97FA
> Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
> APT repo:  deb http://people.debian.org/~vdanjean/debian unstable main
>
>


-- 

*Piotr Górski*
*Specjalista ds. Multimediów **| Multimedia Specialist*




*Concept Music Art Sp. z o.o.*
ul. Przemysłowa 26 | 32-083 Balice
tel. +48.609.127.370

*www.cma.pl *



ESTRADA *|* STAGE *|* MULTIMEDIA *|* KONFERENCJE *|* CONFERENCES *|* EVENTY
*|* EVENTS *|* CATERING



Concept Music Art Sp. z o.o. z siedzibą: ul. Przemysłowa 26, 32-8083
Balice, wpisana do Rejestru Przedsiębiorców prowadzonego przez Sąd Rejonowy
dla Krakowa-Śródmieścia w Krakowie,

Wydział IX Gospodarczy Krajowego Rejestru Sądowego, numer KRS 287685,
Kapitał zakładowy: 1 500 000,00 zł,  NIP 945-19-68-783, REGON 356549517

Treść tej wiadomości jest poufna i prawnie chroniona. Odbiorcą może być
jedynie jej adresat z wyłączeniem dostępu osób trzecich. Jeżeli nie jesteś
adresatem niniejszej wiadomości, powinieneś ją niezwłocznie usunąć,

jej rozpowszechnianie, kopiowanie, rozprowadzanie lub inne działanie o
podobnym charakterze jest prawnie zabronione i może być karalne.

Bug#812101: xkb-data: fr(oss) and fr(bepo): keypad dot should be KP_Decimal

2016-01-20 Thread Daniel Dehennin

Package: xkb-data
Version: 2.16-1
Severity: normal

Dear Maintainer,

I have troubles using fr(oss) and fr(bepo) with libreoffice: the keypad
dot is not recognized as a decimal separator.

I made some tests with xev to see the keysym of the keypad dot:

- setxkbmap fr

KeyPress event, serial 41, synthetic NO, window 0xe1,
root 0x107, subw 0x0, time 19808533, (520,272), root:(521,292),
state 0x10, keycode 91 (keysym 0xffae, KP_Decimal), same_screen YES,
XKeysymToKeycode returns keycode: 129
XLookupString gives 1 bytes: (2e) "."
XmbLookupString gives 1 bytes: (2e) "."
XFilterEvent returns: False

KeyRelease event, serial 41, synthetic NO, window 0xe1,
root 0x107, subw 0x0, time 19808629, (520,272), root:(521,292),
state 0x10, keycode 91 (keysym 0xffae, KP_Decimal), same_screen YES,
XKeysymToKeycode returns keycode: 129
XLookupString gives 1 bytes: (2e) "."
XFilterEvent returns: False

- setxkbmap fr -variant oss

KeyPress event, serial 30, synthetic NO, window 0xe1,
root 0x107, subw 0x0, time 19936934, (869,455), root:(870,475),
state 0x10, keycode 91 (keysym 0x2e, period), same_screen YES,
XKeysymToKeycode returns keycode: 59
XLookupString gives 1 bytes: (2e) "."
XmbLookupString gives 1 bytes: (2e) "."
XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0xe1,
root 0x107, subw 0x0, time 19937038, (869,455), root:(870,475),
state 0x10, keycode 91 (keysym 0x2e, period), same_screen YES,
XKeysymToKeycode returns keycode: 59
XLookupString gives 1 bytes: (2e) "."
XFilterEvent returns: False

- setxkbmap fr -variant bepo

KeyPress event, serial 30, synthetic NO, window 0xe1,
root 0x107, subw 0x0, time 20338367, (792,630), root:(2473,650),
state 0x10, keycode 91 (keysym 0x2e, period), same_screen YES,
XKeysymToKeycode returns keycode: 55
XLookupString gives 1 bytes: (2e) "."
XmbLookupString gives 1 bytes: (2e) "."
XFilterEvent returns: False

KeyRelease event, serial 33, synthetic NO, window 0xe1,
root 0x107, subw 0x0, time 20338447, (792,630), root:(2473,650),
state 0x10, keycode 91 (keysym 0x2e, period), same_screen YES,
XKeysymToKeycode returns keycode: 55
XLookupString gives 1 bytes: (2e) "."
XFilterEvent returns: False


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

Kernel: Linux 4.3.0-1-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)

-- no debconf information

-- 
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6  2AAD CC1E 9E5B 7A6F E2DF

Bug#780530: [calendarserver]

2016-01-20 Thread Ximin Luo

Hey, I just tested 7.0+dfsg from git and it seems to work fine. Thanks for the 
work, and looking forward to the eventual upload! Just a few notes:

(a) You should say "python-pycalendar (>= 2.1~svn15020)" in Depends: otherwise 
you get an error at startup.

(b) You can (Closes: #770416) since the new upstream version no longer has 
calendarserver_bootstrap_database. Instead, the instructions in README.Debian 
seem to work fine for me (I tested peer authentication).

(c) You probably want to add a `debian/gbp.conf` to all your repos, like this:

 calendarserver/debian/gbp.conf 
[DEFAULT]
pristine-tar = true
debian-branch = debian/sid
upstream-tag = dfsg/%(version)s

[buildpackage]
dist = DEP14
 [other packages]/debian/gbp.conf 
[DEFAULT]
pristine-tar = true
debian-branch = debian/sid

[buildpackage]
dist = DEP14

Then one can simply use `gbp buildpackage`, with or without `--git-pbuilder 
--git-arch=amd64` as desired.

(d) The git history for the debian/wheezy branch of calendarserver is also 
messed up - you have version 3.2 committed on top of 5.2.2. It involves a bit 
of git magic to fix, which I can do, if you want to avoid the hassle yourself 
and you give me access.

I've also asked to be added to the calendarserver group on Alioth, so that I 
can make these changes myself.

X

On 28/11/15 04:53, Rahul Amaram wrote:
> Hi Ximin,
> 
> I can upload calendarsever myself. There are a few action items left (see 
> above), which needs to be completed before pushing calendarserver 7.0 debian 
> package. It would be great if you can help me with those tasks.
> 
> Thanks,
> Rahul.
> 

-- 
GPG: 4096R/1318EFAC5FBBDBCE
git://github.com/infinity0/pubkeys.git

Bug#812102: Acknowledgement (iproute2: Segmentation fault with 'ip link set')

2016-01-20 Thread Nicolas Dichtel


To reproduce it:

root@bretzel:~# ip -f inet6 tunnel add gre2 mode ip6gre local fd00:125::1:1 
remote fd00:125::1:2 dev eth0

root@bretzel:~# ip link set gre2 type ip6gre hoplimit 32
addattr_l ERROR: message exceeded bound of 1024
addattr_l ERROR: message exceeded bound of 1024
addattr_l ERROR: message exceeded bound of 1024
addattr_l ERROR: message exceeded bound of 1024
addattr_l ERROR: message exceeded bound of 1024
addattr_l ERROR: message exceeded bound of 1024
addattr_l ERROR: message exceeded bound of 1024
addattr_l ERROR: message exceeded bound of 1024
addattr_l ERROR: message exceeded bound of 1024
addattr_l ERROR: message exceeded bound of 1024
Segmentation fault


Le 20/01/2016 15:45, Debian Bug Tracking System a écrit :

Thank you for filing a new Bug report with Debian.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
  Debian iproute2 Maintainers 

If you wish to submit further information on this problem, please
send it to 812...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

Bug#810151: [Pkg-utopia-maintainers] Bug#810151: network-manager: Cannot use dhcpcd

Am 20.01.2016 um 15:11 schrieb Michael Biebl:
> Hi Tuomas,
> 
> Am 07.01.2016 um 01:46 schrieb Tuomas Suutari:
>> Luckily, it seems to be easy to fix this.  Just add dhcpcd5 as build dep
>> and pass the --with-dhcpcd option to configure.  I will include a patch
>> for this.
> 
> Can you elaborate, why the Build-Depends on dhcpcd5 is necessary if we
> are passing the full patch to ./configure via --with-dhcpcd=/sbin/dhcpcd?

Looking into this a bit more, specifically the configure check for
dhcpcd: If we pass the /sbin/dhcpcd path to --with-dhcpcd,
IPV6 support is not enabled, because the following check is not run:


elif $with_dhcpcd --version 2>&1 | grep -q "^dhcpcd [[6789]]\."; then
AC_DEFINE(DHCPCD_SUPPORTS_IPV6, 1, [Define if dhcpcd supports
IPv6 (6.x+)])
fi

Is that really intentional in your patch?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#810964: [BUG] EDAC infomation partially missing

2016-01-20 Thread Andreas Pflug

Initially reported to debian
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810964), redirected here:

With AMD Opteron 6xxx processors, half of the memory controllers are
missing from /sys/devices/system/edac/mc
Checked with single 6120 (dual memory controller) and twin 6344 (2x dual
MC), other dual-module CPUs might be affected too.

Booting plain Linux (3.2, 3.16, 4.1, 4.3), all memory controllers are
listed under /sys/devices/system/edac/mc as expected. Same happens, when
Xen 4.1 is used: all MCs present.

Starting with Xen 4.4 (Debian Jessie), only mc1 (on the single CPU
machine) or mc2/mc3 (dual CPU machine) are present, although the full
system memory is accessible. Checked versions were 4.1.4 (Debian
Wheezy), 4.4.1 (Jessie) and 4.6.0 (Sid)

Bug#783295: network-manager: CVE-2015-2924: IPv6 Hop limit lowering via RA messages

On Sat, 25 Apr 2015 15:08:19 +0200 Salvatore Bonaccorso
 wrote:
> Source: network-manager
> Version: 0.9.10.0-7
> Severity: normal
> Tags: security upstream
> 
> Hi,
> 
> the following vulnerability was published for network-manager.
> 
> CVE-2015-2924[0]:
> IPv6 Hop limit lowering via RA messages
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.
> 
> For further information see:
> 
> [0] https://security-tracker.debian.org/tracker/CVE-2015-2924
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1209902
> 
> Please adjust the affected versions in the BTS as needed.

The current versions in unstable/testing are not affected (fixed in
1.0.2, marked accordingly)

Do you consider this issue important enough for a stable-security upload?

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#811544: cpufrequtils: Disable init scripts by default (not needed anymore)

2016-01-20 Thread Mattia Dongili

severity 811544 normal
thanks

On Tue, Jan 19, 2016 at 06:36:17PM +0100, Christian Pernegger wrote:
...
> So the init scripts are just expensive noops. Maybe they're still
> needed in some cases but I think the default should be off (with a
> working low prio debconf question to enable).

Thanks for the report, I think there is material here to make this bug a
bit more relevant than a wishlist one.

The other issue with cpufrequtils as it stands, is that it's ancient and
should be replaced with the version included in the Linux kernel
distribution.

Work to fix this bug will be done while upgrading.

Regards,
-- 
mattia
:wq!

Bug#811522: proposed RM: jenkins -- RoQA; multiple security issues, FTBFS, unmaintained in Debian

2016-01-20 Thread Emmanuel Bourg

Hi Ansgar,

Le 19/01/2016 17:11, Ansgar Burchardt a écrit :

> I suggest to remove the package from Debian.  If there are no
> objections, I'll reassign the request to the ftp.debian.org pseudo-
> package later.

FYI the fate of the jenkins package is currently being discussed on the
debian-java list:

  https://lists.debian.org/debian-java/2016/01/msg00019.html


> I'm also wondering if "jenkins-memory-monitor" should also be removed
> at the same time or if it is also useful without jenkins?

jenkins-memory-monitor can indeed be removed with jenkins, as well as
the various plugins packaged and some libraries. Here is a quick list:

  access-modifier-checker
  bytecode-compatibility-transformer
  jellydoc
  jenkins-ant-plugin
  jenkins-antisamy-markup-formatter-plugin
  jenkins-commons-jelly
  jenkins-commons-jexl
  jenkins-constant-pool-scanner
  jenkins-crypto-util
  jenkins-dom4j
  jenkins-executable-war
  jenkins-htmlunit
  jenkins-htmlunit-core-js
  jenkins-instance-identity
  jenkins-json
  jenkins-mailer-plugin
  jenkins-matrix-auth-plugin
  jenkins-matrix-project-plugin
  jenkins-memory-monitor
  jenkins-remoting
  jenkins-ssh-cli-auth
  jenkins-task-reactor
  jenkins-test-annotations
  jenkins-trilead-ssh2
  jenkins-winstone
  jenkins-xstream
  maven-hpi-plugin
  maven-stapler-plugin
  sezpoz
  stapler
  stapler-adjunct-codemirror
  stapler-adjunct-timeline

Emmanuel Bourg

Bug#181735: wmaker: Disregards window placement rules when placing window in non-active workspace

2016-01-20 Thread Doug Torrance


Control: tags -1 fixed-upstream

On Thu, 20 Feb 2003 01:33:31 -0800 Andrew Gorcester  wrote:
> When placing a window in a non-active workspace (which usually happens
> if the user asks for a program to be started when wmaker is launched,
> and defines an initial workspace in the window's attributes dialog),
> Windowmaker doesn't follow specified rules on window placement.
>
> All windows of programs that don't manage their own window placement
> (Gaim manages placement itself, for instance) are placed in the far
> upper-left corner. Usually windows originate from 64, 64, because the
> clip occupies the upper-left corner by default.

The fix has appeared in the upstream git [1] and should appear in the 
next release.


[1] 
http://repo.or.cz/wmaker-crm.git/commitdiff/65802d3402dec0cfc995ec5cd1d50078fd35c183

Bug#797379: system upgrade by systemd

Hi Michael

On Sun, 30 Aug 2015 10:30:54 +0200 Michael Banck  wrote:
> Package: network-manager
> Severity: wishlist
> 
> On Sun, Aug 30, 2015 at 06:46:24AM +0200, Michael Meskes wrote:
> > > Itâs gnome-software in sid, or g-s-d in jessie, querying PackageKit for
> > > updates.
> > > The default policy is to not schedule any downloads when running on
> > > battery or on a modem connection.
> > 
> > Which is not enough IMO. (W)LAN connections cannot be expected to not
> > carry a penalty for download volume. Just think about the now standard
> > way of going on-line while traveling, making your cell play access
> > point. And at least in my area of the world no flat rate is really flat,
> > at least it will be slowed down to crazy low numbers if you reach a
> > certain threshold. Even worse, if you're roaming it'll cost a fortune.
>  
> In that case, the WLAN access point ("FooAP" or so) should be tagged as
> "modem", not sure if n-m can do that.  Am trying to file a wishlist
> bug for that by BCCing submit@.
> 
> But in general I think we want that our users get security updates ASAP,
> so the current default looks mostly sane to me.  Maybe somebody knows a
> shell on-liner along the line of systemd-inhibit or some d-bus call
> which deactivates automatic download for the time being for "power
> users" and/or tags a WLAN connection as "modem".

It's not quite clear to me, what you want from NM in this bug report.
How should NM know which WLAN connection to tag as metered?




-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#306808: additional keyboard shortcuts

2016-01-20 Thread Doug Torrance


Control: tags -1 fixed-upstream

On Tue, 19 Jan 2016 05:37:49 -0500 Doug Torrance 
 wrote:

> I'll submit a patch upstream for keeping a window on top.

This patch has been submitted [1] and the new shortcuts should appear in 
the next upstream release.


[1] 
http://repo.or.cz/wmaker-crm.git/commitdiff/563cda28d36fad44dc8fe299b0ab2aa2b9dc93bc

Bug#809756: Clarification

2016-01-20 Thread Willi Mann



Am 2016-01-20 um 09:13 schrieb Mobile Perpetuum:
> Hi, I confirm this bug in version 7.4.1+svn20151218rev302-1

Just for the record: what Mobile Perpetuum reports is not the same bug.
It is another problem with postfix that appears to require to execute a
specific printf call in order to occur.

WM

Bug#780530: [calendarserver]

2016-01-20 Thread Rahul Amaram




On Wednesday 20 January 2016 11:31 PM, Ximin Luo wrote:

On 20/01/16 18:48, Rahul Amaram wrote:

I had removed the calenarserver_upgrade instructions from README.Debian because 
it was not working and I was assuming that when I start calendarserver the 
upgrade will happen automatically. I will take care of all the points that you 
have mentioned and also mostly write a script for xml file upgrade while 
installing calendarserver 7.0. But this is odd. I feel, upstream should take 
care of all these upgrades automatically :).


Yes, they ought to have better documentation to help admins during upgrades. :( 
Even doc/Admin/DirectoryService-XML.rst describes the old format... I had to guess 
and also by looking at the output of http://$server:8008/addressbooks/ >:(


Thanks for all the help. I just can't tell you how awesome you have been. I do 
have one final request. I need the packages twextypy and pg8000 to be uploaded 
to Debian. I have reached out to my mentor but have not yet heard. He gets busy 
at times. In case I do not hear from him, would you be willing to upload these 
two packages? I have already raised ITP for them.


Sure, just let me know when you are ready. :) You can either send me a link to 
a git commit, or a link to a .dsc that you upload to mentors.debian.net.
Should I tag the commit so that you can easily build from it? If you 
would be reviewing it, it might be better to do it before I tag it. I 
will anyway, implement all your suggestions in the earlier mails. If you 
have anything apart from that, let me know.


X

Bug#812114: jsonpickle: FTBFS: SyntaxError: unexpected EOF while parsing

2016-01-20 Thread Chris Lamb

Source: jsonpickle
Version: 0.9.2-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

jsonpickle fails to build from source in unstable/amd64:

  [..]
  
  ==
  ERROR: test_ndarray_roundtrip (numpy_test.NumpyTestCase)
  --
  Traceback (most recent call last):
File 
"/home/lamby/temp/cdt.20160120190203.sPKSaEICvX/jsonpickle-0.9.2/tests/numpy_test.py",
 line 103, in test_ndarray_roundtrip
  decoded = self.roundtrip(array)
File 
"/home/lamby/temp/cdt.20160120190203.sPKSaEICvX/jsonpickle-0.9.2/tests/numpy_test.py",
 line 32, in roundtrip
  return jsonpickle.decode(jsonpickle.encode(obj))
File 
"/home/lamby/temp/cdt.20160120190203.sPKSaEICvX/jsonpickle-0.9.2/jsonpickle/__init__.py",
 line 148, in decode
  return unpickler.decode(string, backend=backend, keys=keys)
File 
"/home/lamby/temp/cdt.20160120190203.sPKSaEICvX/jsonpickle-0.9.2/jsonpickle/unpickler.py",
 line 26, in decode
  return context.restore(backend.decode(string), reset=reset)
File 
"/home/lamby/temp/cdt.20160120190203.sPKSaEICvX/jsonpickle-0.9.2/jsonpickle/unpickler.py",
 line 119, in restore
  value = self._restore(obj)
File 
"/home/lamby/temp/cdt.20160120190203.sPKSaEICvX/jsonpickle-0.9.2/jsonpickle/unpickler.py",
 line 159, in _restore
  return restore(obj)
File 
"/home/lamby/temp/cdt.20160120190203.sPKSaEICvX/jsonpickle-0.9.2/jsonpickle/unpickler.py",
 line 235, in _restore_object
  instance = handler(self).restore(obj)
File 
"/home/lamby/temp/cdt.20160120190203.sPKSaEICvX/jsonpickle-0.9.2/jsonpickle/ext/numpy.py",
 line 49, in restore
  dtype = self.restore_dtype(data)
File 
"/home/lamby/temp/cdt.20160120190203.sPKSaEICvX/jsonpickle-0.9.2/jsonpickle/ext/numpy.py",
 line 19, in restore_dtype
  return np.dtype(dtype)
File "/usr/lib/python2.7/dist-packages/numpy/core/_internal.py", line 191, 
in _commastring
  newitem = (dtype, eval(repeats))
File "", line 1
  (
  ^
  SyntaxError: unexpected EOF while parsing
  
  --
  Ran 230 tests in 0.166s
  
  FAILED (errors=1, skipped=9)
  E: pybuild pybuild:274: test: plugin custom failed with: exit code=1: 
tests/runtests.py
  dh_auto_test: pybuild --test -i python{version} -p 2.7 --dir . returned exit 
code 13
  debian/rules:10: recipe for target 'override_dh_auto_test' failed
  make[1]: *** [override_dh_auto_test] Error 25
  make[1]: Leaving directory 
'/home/lamby/temp/cdt.20160120190203.sPKSaEICvX/jsonpickle-0.9.2'
  debian/rules:7: recipe for target 'build' failed
  make: *** [build] Error 2

  [..]

The full build log is attached.


Regards,

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


jsonpickle.0.9.2-1.unstable.amd64.log.txt.gz
Description: Binary data

Bug#796931: [pkg-gnupg-maint] Bug#796931: Another data point

2016-01-20 Thread Daniel Kahn Gillmor

Hi Manoj--

On Wed 2016-01-20 04:04:43 -0500, Manoj Srivastava wrote:

> I sourced the file 70gnupg-agent.sh discussed earlier int he bug
> report.

If you're running X11, i'd assume that file would have been sourced
during your session startup.

> I am still having issues -- at least, with gpg, I can actually use
> gpg; gpg2 just fails.

can you show the version numbers you're using?

dpkg -l gnupg gnupg2 gnupg-agent


>> echo $GNUPGHOME
> /home/srivasta/lib/.sec
>>echo $GPG_AGENT_INFO
>
>> echo $GPG_AGENT
>
>> gpg-agent
> gpg-agent[1725]: gpg-agent running and available

the fact that GPG_AGENT_INFO isn't set is a little odd if you've sourced
70gpg-agent.sh, although the fact that you're not using a standard
GNUPGHOME also makes me wonder what's going on here.  do you have
"use-agent" set in /home/srivastava/lib/.sec/gpg.conf?  what about in
/home/srivastava/.gnupg/gpg.conf ?

>> gpg2 -vvv --clearsign ~/.login
> gpg: keyserver option 'include-disabled' is unknown
> gpg: keyserver option 'honor-http-proxy' is unknown
> gpg: using character set 'utf-8'
> gpg: Note: signature key 9D760D4D has been revoked
> gpg: Note: signature key 840A4306 expired Wed 11 May 2011 02:33:47 PM PDT
> gpg: using PGP trust model
> gpg: key C5779A1C: accepted as trusted key
> gpg: Note: signature key 9D760D4D has been revoked
> gpg: Note: signature key 840A4306 expired Wed 11 May 2011 02:33:47 PM PDT
> gpg: using subkey 6F576472 instead of primary key C5779A1C
> gpg: writing to '/home/srivasta/.login.asc'
> gpg: signing failed: No secret key
> gpg: /home/srivasta/.login: clearsign failed: No secret key
> [1]1767 exit 2 gpg2 -vvv --clearsign ~/.login

This response suggests that you might be using gpg2 2.1.x (it finds the
agent while GPG_AGENT_INFO is unset, without specifying
--use-standard-socket), but your secret keys have not been imported.
does /home/srivastava/lib/.sec/private-keys-v1.d/ contain the keygrip of
the secret key you need to use?

the keygrip for your signing-capable subkey 0x36BD720F6F576472 is
4AA76328759B16116F1C2F3380A3C313A1398F34 (you can find this with "gpg2
--with-keygrip --list-keys 0x36BD720F6F576472), so i'd expect there to
be a file at:

 
/home/srivastava/lib/.sec/private-keys-v1.d/4AA76328759B16116F1C2F3380A3C313A1398F34.key

If that doesn't exist, and you're using gpg 2.1.x, can you try importing
your gpgv1 secret keyring again and then retrying your command?

   gpg2 --import < /home/srivastava/lib/.sec/secring.gpg


If this solves things for you, i'd still like to understand why the
secret keyring didn't get imported automatically the first time you used
gpg 2.1.x.  Can you tell me any history of how and when (what versions?)
you first moved to 2.1.x ?

>> gpg -vvv --clearsign ~/.login
> gpg: using character set `utf-8'
> gpg: using PGP trust model
> gpg: key C5779A1C: accepted as trusted key
> gpg: can't handle public key algorithm 22
> gpg: can't handle public key algorithm 19
> gpg: error checking usability status of C7261095
> gpg: key C7261095: secret key without public key - skipped
> gpg: NOTE: signature key 840A4306 expired Wed 11 May 2011 02:33:47 PM PDT
> gpg: NOTE: signature key 840A4306 expired Wed 11 May 2011 02:33:47 PM PDT
> gpg: no secret subkey for public subkey 840A4306 - ignoring
> gpg: using subkey 6F576472 instead of primary key C5779A1C
>
> You need a passphrase to unlock the secret key for
> user: "Manoj Srivastava "
> gpg: NOTE: signature key 840A4306 expired Wed 11 May 2011 02:33:47 PM PDT
> gpg: using subkey 6F576472 instead of primary key C5779A1C
> 2048-bit RSA key, ID 6F576472, created 2009-07-23 (main key ID C5779A1C)
>
> gpg: gpg-agent is not available in this session
> You need a passphrase to unlock the secret key for
> user: "Manoj Srivastava "
> 2048-bit RSA key, ID 6F576472, created 2009-07-23 (main key ID C5779A1C)
>
> gpg: writing to `/home/srivasta/.login.asc'
> gpg: RSA/SHA512 signature from: "6F576472 Manoj Srivastava 
> "

This shows you not using the gpg-agent at all.

>  ps auwwx | egrep '[g]pg-agent'
> srivasta 24911  0.0  0.0 165000  2180 ?SNs  00:39   0:00 gpg-agent 
> --daemon --enable-ssh-support --allow-preset-passphrase 
> --no-allow-external-cache

OK, so the agent is running, but it's not clear what started it.  I
suspect it's likely that it was auto-launched by gpg 2.1.x.

Regards,

 --dkg

Bug#812080: gdc-6: array assignment fails to compile

2016-01-20 Thread Iain Buclaw

On 20 January 2016 at 10:48, Peter De Wachter  wrote:

> Package: gdc-6
> Version: 6-20160117-1
> Severity: normal
>
> Dear Maintainer,
>
> This program fails to compile in this gdc snapshot:
>
>   void main() {
> real[] a = [-1];
>   }
>
> It is accepted by both gdc-5 and the dmd reference compiler.
>
>
I'm sure I would have noticed if this was happening in upstream gdc.
However I don't want to be quick to point towards some local debian patch
causing the problem.  Are there debug builds to test?


Iain.

Bug#811825: ppl: FTBFS with GCC 6: no match for

* Roberto Bagnara  [2016-01-20 13:07]:
> roberto@jessie64:~$ sudo apt-get -t experimental install gcc-6
  ^^

It looks like you're on jessie.  experimental packages have to be
installed on top of unstable.

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise

Bug#811612: FTBFS with GCC 6: cannot convert x to y