Bug#869934: cockpit: Incomplete debian/copyright?

2017-07-28 Thread Chris Lamb
Hi Martin,

> That's only for the bundled JavaScript modules.

I don't have the package in front of me right now but I think
the other issue was that d/copyright was mentioning .JS but in
the wrong location (node_modules/ vs. dist/ IIRC). Again this
is from memory so disregard if I'm wrong :)


Best wishes,

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



Bug#869962: [INTL:sv] Swedish strings for igtf-policy-bundle debconf

2017-07-28 Thread Martin Bagge
package: igtf-policy-bundle
severity: wishlist
tags: patch l10n

Please consider to add this file to translation of debconf.

-- 
brother
http://sis.bthstuden.se


sv.po
Description: Binary data


Bug#869934: cockpit: Incomplete debian/copyright?

2017-07-28 Thread Martin Pitt
Hey Chris,

Chris Lamb [2017-07-28  7:56 +0100]:
> > That's only for the bundled JavaScript modules.
> 
> I don't have the package in front of me right now but I think
> the other issue was that d/copyright was mentioning .JS but in
> the wrong location (node_modules/ vs. dist/ IIRC). Again this
> is from memory so disregard if I'm wrong :)

It's not wrong - node_modules/ has the original modules (i. e. preferred form
of modification).  The topmost comment in d/copyright tries to explain this:

  This does not directly cover the files in dist/*. These are "minified" and
  compressed JavaScript/HTML files built from pkg/* and node_modules/* with
  node, npm, and webpack. Their copyrights and licenses are described below.
  Rebuilding these requires internet access as that process needs to download
  additional npm modules from the Internet, thus upstream ships the pre-minified
  webpacks as part of the upstream release tarball so that the package can be
  built without internet access and lots of extra unpackaged build dependencies.

The upstream tarballs ship dist/ it to relieve downstreams from having to
build-depend on and call webpack during the package build (unless they want to
patch). So its similar to pre-generated PDF documentation or autotools
Makefiles. If that's unclear, I'm happy to improve the wording?

Thanks,

Pitti



Bug#869788: lintian: false positives in copyright-year-in-future

2017-07-28 Thread Chris Lamb
tags 869788 + pending
thanks

Fixed in Git:

  
https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=cefc1ccc531f61f944ed5a2b642b542e84371499


Regards,

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



Bug#869516: reproducible build for libcdio

2017-07-28 Thread Chris Lamb
Hi Rocky,

> If you create patch against the current libcdio sources
> https://savannah.gnu.org/git/?group=libcdio I will add that to the
> source.

Sure! However, I'm following that page and getting:

$ git clone https://git.savannah.gnu.org/libcdio.git
Cloning into 'libcdio'...
fatal: repository 'https://git.savannah.gnu.org/libcdio.git/' not found

:)


Regards,

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



Bug#869934: cockpit: Incomplete debian/copyright?

2017-07-28 Thread Chris Lamb
Hi Martin,

> The upstream tarballs ship dist/ it to relieve downstreams from having to
> build-depend on and call webpack during the package build (unless they want to
> patch). So its similar to pre-generated PDF documentation or autotools
> Makefiles. If that's unclear, I'm happy to improve the wording?

Please … or even repack, depending on how easy that is with your build
tools.


Regards,

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



Bug#851636: patch

2017-07-28 Thread Salvo Tomaselli
How did you create the patch?

Is it created against master in the git collab-maint? I can't seem to apply it.

-- 
Salvo Tomaselli

"Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di
senso, ragione ed intelletto intendesse che noi ne facessimo a meno."
-- Galileo Galilei

http://ltworf.github.io/ltworf/



Bug#869963: mutt: header_cache location is wrong

2017-07-28 Thread Paul Slootman
Package: mutt
Version: 1.8.3+neomutt20170609-2+b1
Severity: normal

3.96. header_cache

Type: path
Default: (empty)

This variable points to the header cache database. If pointing to a directory
Mutt will contain a header cache database file per folder, if pointing to a
file that file will be a single global header cache. By default it is unset so
no header caching will be used.

---

This is partly true; when specifying a directory, the value of $HOME/Mail
is appended to it, which frankly is quite insane.

With these settings:

set message_cachedir=~/Mail-a
set header_cache=~/Mail-b

and no other setting that contains "Mail", the header cache ends
up being written to
/home/paul/Mail-b/home/paul/Mail/imaps:p.sloot...@example.com@192.168.1.90/INBOX.hcache

The message cache is correctly written to
/home/paul/Mail-a/imaps:p.sloot...@example.com@192.168.1.90/INBOX/*


It seems that constructing the path for the header cache messes up
somewhere by always appending $HOME/Mail/ . This should be fixed.

I used Mail-a and Mail-b in the above settings instead of the original
Mail I had to determine whether message_cachedir was being appended to
the header_cache path, but apparently it's not.


thanks,
Paul

-- Package-specific info:
NeoMutt 20170609 (1.8.3)
Copyright (C) 1996-2016 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 4.11.3-wurtel-ws (x86_64)
libidn: 1.33 (compiled with 1.33)
hcache backends: tokyocabinet

Compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.4.0-1' 
--with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs 
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-6 --program-prefix=x86_64-linux-gnu- --enable-shared 
--enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext 
--enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ 
--enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie 
--with-system-zlib --disable-browser-plugin --enable-java-awt=gtk 
--enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre 
--enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-amd64 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64 
 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--with-target-system-zlib --enable-objc-gc=auto --enable-multiarch 
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 
--enable-multilib --with-tune=generic --enable-checking=release 
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 6.4.0 20170704 (Debian 6.4.0-1) 

Configure options: '--build=x86_64-linux-gnu' '--prefix=/usr' 
'--includedir=\${prefix}/include' '--mandir=\${prefix}/share/man' 
'--infodir=\${prefix}/share/info' '--sysconfdir=/etc' '--localstatedir=/var' 
'--disable-silent-rules' '--libdir=\${prefix}/lib/x86_64-linux-gnu' 
'--libexecdir=\${prefix}/lib/x86_64-linux-gnu' '--disable-maintainer-mode' 
'--disable-dependency-tracking' '--with-mailpath=/var/mail' 
'--enable-compressed' '--enable-debug' '--enable-fcntl' '--enable-hcache' 
'--enable-gpgme' '--enable-lua' '--enable-imap' '--enable-smtp' '--enable-pop' 
'--enable-sidebar' '--enable-nntp' '--enable-dotlock' '--enable-notmuch' 
'--disable-fmemopen' '--with-curses' '--with-gnutls' '--with-gss' '--with-idn' 
'--with-mixmaster' '--with-sasl' '--without-gdbm' '--without-bdb' 
'--without-qdbm' '--with-tokyocabinet' 'build_alias=x86_64-linux-gnu' 
'CFLAGS=-g -O2 
-fdebug-prefix-map=/build/mutt-PiaMLU/mutt-1.8.3+neomutt20170609=. 
 -fstack-protector-strong -Wformat -Werror=format-security' 
'LDFLAGS=-Wl,-z,relro -Wl,-z,now' 'CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2'

Compilation CFLAGS: -Wall -pedantic -Wno-long-long -g -O2 
-fdebug-prefix-map=/build/mutt-PiaMLU/mutt-1.8.3+neomutt20170609=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-fno-delete-null-pointer-checks

Compile options:
  +attach_headers_color +bkgdset +color +compose_to_sender +compress +cond_date 
  +curs_set +debug +dotlock +encrypt_to_self -exact_address +fcntl -flock 
  -fmemopen +forgotten_attachments +forwref +futimens +getaddrinfo +getsid 
  +gnutls +gpgme +gss +hcache -homespool -iconv_nontrans +ifdef +imap 
  +index_color +initials +keywords +libidn +limit_current_thread +lmdb 
  -locales_hack +lua +meta +mixmaster +multiple_fcc +nested_if +new_mail +nls 
  +nntp +notmuch -openssl +pgp +pop +progress +quasi_delete +regcomp 
  +reply_with_xorig +resizeterm +sasl +sensible_browser -setgi

Bug#849765: reportbug: produces invalid mails when there are long lines

2017-07-28 Thread Paul Slootman
I was bitten by the same problem while reporting a bug on mutt, there
the problem was the C compiler settings listed (I wonder why including
those is useful, those aren't specific to my environment?)

It really sucked that after taking 15 minutes to craft a good bug report
that due to this silly problem that time was completely wasted because of
the stupid exim handling of these too long lines. Perhaps an option to
always save a local copy before sending?

Paul



Bug#869964: postfix-add-policy: /usr/bin/python3: bad interpreter: No such file or directory

2017-07-28 Thread Louis van Belle
Package: postfix
Version: 3.1.4-7
Severity: minor

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation? 
trying to use : /usr/sbin/postfix-add-policy
   * What exactly did you do (or not do) that was effective (or
 ineffective)? run the command.
   * What was the outcome of this action?
postfix-add-policy: /usr/bin/python3: bad interpreter: No such file or 
directory
   * What outcome did you expect instead?
policy to be added in master.cf

The following happen and how to detect.
Basic stretch server installation. ( standard tools + ssh server ) 
Installed postfix.
when running the command : postfix-add-policy usename path_to_file
resulted in : /usr/bin/python3: bad interpreter: No such file or directory 
and nothing was added in master.cf

2 possible fixed, and correct solution is a depend problem fix.

fix1 : edit the file /usr/sbin/postfix-add-policy, change 
#!/usr/bin/python3 to #!/usr/bin/python

I installed reportbug. ( and all its dependecies, one of these fixed the 
problem also. 
i changed the #!/usr/bin/python back to #!/usr/bin/python3
did run the command again : postfix-add-policy usename path_to_file
Now it worked fine.

The following (python) packages where installed by reportbug, one of these 
fixed my problem.
dh-python
libpython3.5-minimal
libpython3.5-stdlib
libpython3-stdlib
python3
python3.5
python3.5-minimal
python3-apt
python3-chardet
python3-debian
python3-debianbts
python3-httplib2
python3-minimal
python3-pkg-resources
python3-pycurl
python3-pysimplesoap
python3-reportbug
python3-requests
python3-six
python3-urllib3
python-apt-common


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

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

Versions of packages postfix depends on:
ii  adduser3.115
ii  cpio   2.11+dfsg-6
ii  debconf [debconf-2.0]  1.5.61
ii  dpkg   1.18.24
ii  init-system-helpers1.48
ii  libc6  2.24-11+deb9u1
ii  libdb5.3   5.3.28-12+b1
ii  libicu57   57.1-6
ii  libsasl2-2 2.1.27~101-g0780600+dfsg-3
ii  libssl1.1  1.1.0f-3
ii  lsb-base   9.20161125
ii  netbase5.4
ii  postfix-sqlite 3.1.4-7
ii  ssl-cert   1.0.39

Versions of packages postfix recommends:
ii  python3  3.5.3-1

Versions of packages postfix suggests:
pn  dovecot-common
ii  libsasl2-modules  2.1.27~101-g0780600+dfsg-3
pn  postfix-cdb   
pn  postfix-doc   
ii  postfix-ldap  3.1.4-7
pn  postfix-lmdb  
ii  postfix-mysql 3.1.4-7
ii  postfix-pcre  3.1.4-7
pn  postfix-pgsql 
pn  procmail  
pn  resolvconf
ii  s-nail [mail-reader]  14.8.16-1
pn  sasl2-bin 
pn  ufw   

-- debconf information excluded



Bug#851636: patch

2017-07-28 Thread Chris Lamb
Hi Salvo,

> How did you create the patch?

6 months on I can't recall... ;)  Very likely against the version in
sid at the time, not a Git repo.


Best wishes,

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



Bug#869869: kalzium FTBFS with OCaml 4.05.0: Options -c and -o are incompatible when compiling C files

2017-07-28 Thread Stéphane Glondu

tags 869869 + patch
thanks

On 27/07/2017 11:40, Stéphane Glondu wrote:

kalzium FTBFS with OCaml 4.05.0. Relevant log:

[...]
[ 55%] Generating modwrap.o
cd /tmp/kalzium-16.08.3/obj-x86_64-linux-gnu/src && /usr/bin/ocamlopt -I 
/usr/lib/ocaml/facile -c /tmp/kalzium-16.08.3/src/solver/modwrap.c -o 
/tmp/kalzium-16.08.3/obj-x86_64-linux-gnu/src/modwrap.o
Options -c and -o are incompatible when compiling C files
src/CMakeFiles/kalzium.dir/build.make:107: recipe for target 'src/modwrap.o' 
failed
make[4]: *** [src/modwrap.o] Error 2
make[4]: Leaving directory '/tmp/kalzium-16.08.3/obj-x86_64-linux-gnu'
CMakeFiles/Makefile2:305: recipe for target 'src/CMakeFiles/kalzium.dir/all' 
failed
make[3]: *** [src/CMakeFiles/kalzium.dir/all] Error 2
[...]


Attached is a patch that forwards the -o option to the underlying C 
compiler. It should work with the ocaml currently in unstable as well.



Cheers,

--
Stéphane
Description: Fix compilation with OCaml 4.05.0

Bug-Debian: https://bugs.debian.org/869869
Forwarded: no
Last-Update: 2017-07-28

--- kalzium-16.08.3.orig/src/CMakeOCamlInstructions.cmake
+++ kalzium-16.08.3/src/CMakeOCamlInstructions.cmake
@@ -58,7 +58,7 @@ ocaml_ml_to_cmx(${CMAKE_CURRENT_BINARY_D
 # object files
 
 add_custom_command(OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/modwrap.o
-   COMMAND ${OCAML_OCAMLOPT_EXECUTABLE} -I ${LIBFACILE_INCLUDE_DIR} -c ${CMAKE_CURRENT_SOURCE_DIR}/solver/modwrap.c -o ${CMAKE_CURRENT_BINARY_DIR}/modwrap.o
+   COMMAND ${OCAML_OCAMLOPT_EXECUTABLE} -I ${LIBFACILE_INCLUDE_DIR} -c ${CMAKE_CURRENT_SOURCE_DIR}/solver/modwrap.c -ccopt -o -ccopt ${CMAKE_CURRENT_BINARY_DIR}/modwrap.o
DEPENDS ${CMAKE_CURRENT_SOURCE_DIR}/solver/modwrap.c ${CMAKE_CURRENT_BINARY_DIR}/solver.o
WORKING_DIRECTORY ${CMAKE_CURRENT_BINARY_DIR})
 set_directory_properties(PROPERTIES ADDITIONAL_MAKE_CLEAN_FILES ${CMAKE_CURRENT_BINARY_DIR}/modwrap.o)


Bug#869871: exim4-config: /etc/mailname is ignored

2017-07-28 Thread Marc Haber
On Thu, Jul 27, 2017 at 11:20:32AM +0200, root wrote:
> after a fresh install of exim4 on debian stretch, and moving our old
> configuration, I found out that mail to unqualified adresses is sent
> to user@`hostname -f` instead of user@`cat /etc/mailname`. Just as if
> MAIN_PRIMARY_HOSTNAME_AS_QUALIFY_DOMAIN was set.

How are you sending this mail? qualify_domain and qualify_recipient only
apply to locally generated messages and NOT to messages received from a
mail client via SMTP.

You might want to run exim with a debug option and look for the
qualification code in the debug output.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421



Bug#869956: transition: libevent 2.1.8-stable-2

2017-07-28 Thread Emilio Pozuelo Monfort
Control: tags -1 confirmed
Control: block -1 with 869900 869902 869951

On 28/07/17 02:23, Balint Reczey wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
> Block: -1 by 869900  869902 869951
> 
> Dear Release Team,
> 
> I would like to upload libevent 2.1.8-stable to unstable.
> 
> Test rebuild in Debian revealed 3 reverse build dependencies which
> FTBFS and I filed
> bugs against them linking to the build logs [1].
> 
> Test rebuild in Ubuntu showed similar results with a few unrelated
> build failures [2]

Go ahead.

Emilio



Bug#869965: vim: please add syntax highlighting for debian/copyright files

2017-07-28 Thread Chris Lamb
Source: vim
Version: 2:8.0.0197-5
Severity: normal
Tags: patch

Hi,

A patch is attached that adds simple syntax highlighting for
DEP-5 debian/copyright files.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb, Debian Project Leader
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/runtime/filetype.vim b/runtime/filetype.vim
index 9c9c808..b1f916d 100644
--- a/runtime/filetype.vim
+++ b/runtime/filetype.vim
@@ -592,6 +592,13 @@ au BufNewFile,BufRead control
\|   setf debcontrol
\| endif
 
+" Debian Copyright
+au BufNewFile,BufRead */debian/copyright   setf debcopyright
+au BufNewFile,BufRead copyright
+   \  if getline(1) =~ '^Format:'
+   \|   setf debcopyright
+   \| endif
+
 " Debian Sources.list
 au BufNewFile,BufRead */etc/apt/sources.list   setf debsources
 au BufNewFile,BufRead */etc/apt/sources.list.d/*.list  setf debsources
diff --git a/runtime/syntax/debcopyright.vim b/runtime/syntax/debcopyright.vim
new file mode 100644
index 000..dd34be4
--- /dev/null
+++ b/runtime/syntax/debcopyright.vim
@@ -0,0 +1,32 @@
+" Vim syntax file
+" Language:Debian copyright file
+" Maintainer:  Chris Lamb 
+" Last Change: 2017 Jul 28
+
+" Standard syntax initialization
+if exists("b:current_syntax")
+  finish
+endif
+
+let s:cpo_save = &cpo
+set cpo&vim
+
+syn case match
+
+syn match debcopyrightUrl   
"\vhttps?://[[:alnum:]][-[:alnum:]]*[[:alnum:]]?(\.[[:alnum:]][-[:alnum:]]*[[:alnum:]]?)*\.[[:alpha:]][-[:alnum:]]*[[:alpha:]]?(:\d+)?(/[^[:space:]]*)?$"
+syn match debcopyrightKey   
"^\%(Format\|Upstream-Name\|Upstream-Contact\|Disclaimer\|Source\|Comment\|Files\|Copyright\|License\):
 *"
+syn match debcopyrightEmail "[_=[:alnum:]\.+-]\+@[[:alnum:]\./\-]\+"
+syn match debcopyrightEmail "<.\{-}>"
+syn match debcopyrightComment   "^#.*$" contains=@Spell
+
+hi def link debcopyrightUrl Identifier
+hi def link debcopyrightKey Keyword
+hi def link debcopyrightEmail   Identifier
+hi def link debcopyrightComment Comment
+
+let b:current_syntax = "debcopyright"
+
+let &cpo = s:cpo_save
+unlet s:cpo_save
+
+" vim: ts=8 sw=2


Bug#868944: virtualbox: Fails to "up" vboxnet0 for host-only interface

2017-07-28 Thread Gianfranco Costamagna
control: fixed -1 5.1.26-dfsg-1
control: close -1

> 
> Since (one of) the last updates, virtualbox fails to set the host-only
> interfaces vboxnet0 and vboxnet1 to "up".

This was a regression in 5.1.24 fixed in 5.1.26, let me know if this is still a 
problem

G.



signature.asc
Description: OpenPGP digital signature


Bug#864847: CP15 Barrier emulation performance?

2017-07-28 Thread Riku Voipio
On Tue, Jul 11, 2017 at 09:45:49AM +0100, Ian Campbell wrote:
> On Tue, 2017-07-11 at 08:56 +0100, Edmund Grimley Evans wrote:
> > > Does this emulation take a considerable performance hit, as opposed
> > > to
> > > running on armhf hardware/kernel, where the instruction doesn't
> > > appear
> > > to be listed as deprecated?
> > 
> > I'd expect the kernel-emulated instruction to be much slower than any
> > non-emulated instruction, but the overall effect on performance will,
> > of course, depend on how often the instruction is used.
> > 
> > See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864847 (where I
> > think I claimed that the instruction is deprecated on armhf hardware
> > but I could easily be wrong)

> Deprecated for both ARMv7 and ARMv8 according to the Kconfig help:
> config CP15_BARRIER_EMULATION
> bool "Emulate CP15 Barrier instructions"
> help
>   The CP15 barrier instructions - CP15ISB, CP15DSB, and
>   CP15DMB - are deprecated in ARMv8 (and ARMv7). It is
>   strongly recommended to use the ISB, DSB, and DMB
>   instructions instead.
> 
>   Say Y here to enable software emulation of these
>   instructions for AArch32 userspace code. When this option is
>   enabled, CP15 barrier usage is traced which can help
>   identify software that needs updating.
> 
>   If unsure, say Y
> 
> However I there is a sysctl which allows selecting between "undef",
> "emulated" and "hw" (where the latter is dependent on the hw actually
> supporting the instructions in question). See:
> http://elixir.free-electrons.com/linux/latest/source/Documentation/arm64/legacy_instructions.txt

The ghc sources don't appeart to have direct CP15 instructions, so I suspect
ghc might be calling llvm with options that make it emit CP15 barriers instead
of DMB. Anyways look like a configuration error rather than a coding error.

Riku



Bug#860975:

2017-07-28 Thread Gianfranco Costamagna
control: fixed -1 5.1.26-dfsg-1
control: close -1


> This is a regression, as it has happened in the past quite a few times.
> Either the menu bar doesn't show up at all, or it shows up "under" the
> virtual machine's window/frame as pointed out previously.
I think this is fixed in 5.1.24-5.1.26, can you please confirm?

thanks

G.



signature.asc
Description: OpenPGP digital signature


Bug#869966: stretch-pu: package gosa-plugin-mailaddress/0.99.5-2+deb9u1

2017-07-28 Thread Mike Gabriel
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

Vincent Danjean spotted a flaw in gosa-plugin-mailaddress, recently, that 
relates to the
renaming of class constructor names as required with PHP 7.

The attached .debdiff fixes this issue for Debian stretch. Please accept the 
.debdiff as
a stretch-pu upload candidate.

Thanks,
Mike

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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru gosa-plugin-mailaddress-0.99.5/debian/changelog 
gosa-plugin-mailaddress-0.99.5/debian/changelog
--- gosa-plugin-mailaddress-0.99.5/debian/changelog 2017-01-09 
16:34:17.0 +0100
+++ gosa-plugin-mailaddress-0.99.5/debian/changelog 2017-07-28 
10:51:19.0 +0200
@@ -1,3 +1,15 @@
+gosa-plugin-mailaddress (0.99.5-2+deb9u1) stretch-proposed-updates; 
urgency=medium
+
+  * debian/patches:
++ Add 0001_php-7-compat-fix-parent-constructor-calls.patch. Fix parent
+  constructor calls. (Closes: #869214).
+  * debian/control:
++ Update versioned D (gosa-plugin-mailaddress): gosa
+  (>= 2.7.4+reloaded2-12~). Reason: since rev 12, gosa in Debian uses the
+  new constructor API required for PHP 7.
+
+ -- Mike Gabriel   Fri, 28 Jul 2017 10:51:19 +0200
+
 gosa-plugin-mailaddress (0.99.5-2) unstable; urgency=medium
 
   * debian/{control,copyright,watch}:
diff -Nru gosa-plugin-mailaddress-0.99.5/debian/control 
gosa-plugin-mailaddress-0.99.5/debian/control
--- gosa-plugin-mailaddress-0.99.5/debian/control   2017-01-09 
16:34:17.0 +0100
+++ gosa-plugin-mailaddress-0.99.5/debian/control   2017-07-28 
10:51:19.0 +0200
@@ -16,7 +16,7 @@
 Architecture: all
 Depends: 
  ${misc:Depends},
- gosa (>= 2.7),
+ gosa (>= 2.7.4+reloaded2-12~),
 Conflicts:
  gosa-plugin-mail,
 Description: Simple plugin to manage user mail addresses in GOsa²
diff -Nru 
gosa-plugin-mailaddress-0.99.5/debian/patches/0001_php-7-compat-fix-parent-constructor-calls.patch
 
gosa-plugin-mailaddress-0.99.5/debian/patches/0001_php-7-compat-fix-parent-constructor-calls.patch
--- 
gosa-plugin-mailaddress-0.99.5/debian/patches/0001_php-7-compat-fix-parent-constructor-calls.patch
  1970-01-01 01:00:00.0 +0100
+++ 
gosa-plugin-mailaddress-0.99.5/debian/patches/0001_php-7-compat-fix-parent-constructor-calls.patch
  2017-07-28 10:51:19.0 +0200
@@ -0,0 +1,39 @@
+From eb5651ef45b776b1c2d87e2ac6d13365bb353456 Mon Sep 17 00:00:00 2001
+From: Mike Gabriel 
+Date: Fri, 28 Jul 2017 10:30:48 +0200
+Subject: [PATCH] PHP 7 compatibility: Fix parent constructor calls.
+
+ Fixes gosa-project/gosa-plugin-mailaddress#1.
+
+ Thanks to Vincent Danjean for spotting this and notifying us.
+---
+ admin/groups/mailaddress/class_groupMail.inc | 2 +-
+ personal/mailaddress/class_mailAccount.inc   | 2 +-
+ 2 files changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/admin/groups/mailaddress/class_groupMail.inc 
b/admin/groups/mailaddress/class_groupMail.inc
+index c291de9..e477fc4 100644
+--- a/admin/groups/mailaddress/class_groupMail.inc
 b/admin/groups/mailaddress/class_groupMail.inc
+@@ -70,7 +70,7 @@ class mailgroup extends plugin {
+ var $cn="";
+ 
+ function __construct (&$config,$dn=NULL,$base_object=NULL) {
+-plugin::plugin ($config,$dn);
++plugin::__construct ($config,$dn);
+ 
+ /* Get attributes from parent object
+  */
+diff --git a/personal/mailaddress/class_mailAccount.inc 
b/personal/mailaddress/class_mailAccount.inc
+index 398b1de..0efaea1 100644
+--- a/personal/mailaddress/class_mailAccount.inc
 b/personal/mailaddress/class_mailAccount.inc
+@@ -62,7 +62,7 @@ class mailAccount extends plugin {
+ /*! \brief  Initialize the mailAccount
+  */
+ function __construct (&$config,$dn=NULL) {
+-plugin::plugin ($config,$dn);
++plugin::__construct ($config,$dn);
+ 
+ /* Get attributes from parent object
+  */
diff -Nru gosa-plugin-mailaddress-0.99.5/debian/patches/README 
gosa-plugin-mailaddress-0.99.5/debian/patches/README
--- gosa-plugin-mailaddress-0.99.5/debian/patches/README1970-01-01 
01:00:00.0 +0100
+++ gosa-plugin-mailaddress-0.99.5/debian/patches/README2017-07-28 
10:51:19.0 +0200
@@ -0,0 +1,3 @@
+0xxx: Grabbed from upstream development.
+1xxx: Possibly relevant for upstream adoption.
+2xxx: Only relevant for official Debian release.
diff -Nru gosa-plugin-mailaddress-0.99.5/debian/patches/series 
gosa-plugin-mailaddress-0.99.5/debian/patches/series
--- gosa-plugin-mailaddress-0.99.5/debian/patches/series1970-01-01 
01:00:00.0 +0100
+++ gosa-plugin-mailaddress-0.99.5/debian/patches/

Bug#869967: rebar: FTBFS on hppa

2017-07-28 Thread Philipp Huebner
Package: rebar
Version: 2.6.4-2
Severity: important

Hi,

rebar 2.6.4-2 FTBFS on hppa,
and the one that has already been built on hppa does not working,
breaking the whole chain of Erlang based packages that depend on it.

I know hppa is a port rather than a release architecture, but it would
still be nice to get this fixed.

Regards,
Philipp



Bug#857356: virtualbox: Should have a bug script for kernel related stuff

2017-07-28 Thread Gianfranco Costamagna
Hello Nelson,

> It would be good if we could have a bug script to automatically include
> information about the installed kernel images, headers, dmesg output and
> other important information that could be used to debug some specific
> problems with virtualbox (specially when using dkms).
> 
> For example, in #857354 we could automatically have included these kind
> of information (installed packages, error messages, etc).
> 

I'll be happy to apply a patch, can you please share one?

thanks!

G.



signature.asc
Description: OpenPGP digital signature


Bug#868849: src:orpie: FTBFS with ocaml 4.05.0

2017-07-28 Thread Stéphane Glondu

tags 868849 + patch
thanks

On 19/07/2017 10:35, Stéphane Glondu wrote:

orpie FTBFS with ocaml 4.05.0. Relevant log:


[...]
cd gsl && ocamlc.opt -ccopt "-I/usr/include  -g -O2 -DHAVE_INLINE -DHAVE_FENV -g 
-O2" -c mlgsl_error.c
In file included from mlgsl_error.c:9:0:
mlgsl_error.c: In function 'ml_gsl_raise_exn':
/usr/lib/ocaml/caml/memory.h:236:12: error: 'caml__frame' undeclared (first use 
in this function)
  (void) caml__frame, \
 ^
/usr/lib/ocaml/caml/memory.h:309:3: note: in expansion of macro 'CAMLxparam2'
CAMLxparam2 (x, y)
^~~
mlgsl_error.c:37:3: note: in expansion of macro 'CAMLlocal2'
CAMLlocal2(exn_msg, exn_arg);
^~
/usr/lib/ocaml/caml/memory.h:236:12: note: each undeclared identifier is 
reported only once for each function it appears in
  (void) caml__frame, \
 ^
/usr/lib/ocaml/caml/memory.h:309:3: note: in expansion of macro 'CAMLxparam2'
CAMLxparam2 (x, y)
^~~
mlgsl_error.c:37:3: note: in expansion of macro 'CAMLlocal2'
CAMLlocal2(exn_msg, exn_arg);
^~
Makefile:219: recipe for target 'gsl/mlgsl_error.o' failed
make[1]: *** [gsl/mlgsl_error.o] Error 2
make[1]: Leaving directory '/tmp/orpie-1.5.2'
debian/rules:21: recipe for target 'build-stamp' failed
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2


 From a cursory look, CAMLxparam2 should be CAMLparam2.


Actually, it was a CAMLparam0 that was missing. There is also another 
issue due to the new handling of externals.


Attached is a patch. It should also work with the ocaml currently in 
unstable.



Cheers,

--
Stéphane
Description: Fix FTBFS with OCaml 4.05.0
Author: Stephane Glondu 
Bug-Debian: https://bugs.debian.org/868849
Forwarded: no
Last-Update: 2017-07-28

--- orpie-1.5.2.orig/Makefile.in
+++ orpie-1.5.2/Makefile.in
@@ -81,7 +81,7 @@ CURSES_OOBJS = $(CURSES_CMX) $(CURSES_CO
 GSL_CMO = gsl/gsl_error.cmo gsl/gsl_blas.cmo gsl/gsl_complex.cmo gsl/gsl_matrix.cmo gsl/gsl_matrix_complex.cmo \
 		gsl/gsl_vector.cmo gsl/gsl_vector_complex.cmo gsl/gsl_vector_flat.cmo gsl/gsl_matrix_flat.cmo \
 		gsl/gsl_vector_complex_flat.cmo gsl/gsl_matrix_complex_flat.cmo gsl/gsl_vectmat.cmo \
-		gsl/gsl_permut.cmo gsl/gsl_linalg.cmo gsl/gsl_fun.cmo
+		gsl/gsl_permut.cmo gsl/gsl_linalg.cmo gsl/gsl_fun.cmo gsl/gsl_sf.cmo gsl/gsl_math.cmo
 GSL_CMX = $(GSL_CMO:.cmo=.cmx)
 GSL_COBJS = gsl/mlgsl_error.o gsl/mlgsl_blas.o gsl/mlgsl_blas_complex.o gsl/mlgsl_complex.o gsl/mlgsl_blas_float.o \
 		 gsl/mlgsl_blas_complex_float.o gsl/mlgsl_matrix_complex.o gsl/mlgsl_matrix_double.o gsl/mlgsl_matrix_float.o \
--- orpie-1.5.2.orig/gsl/gsl_sf.ml
+++ orpie-1.5.2/gsl/gsl_sf.ml
@@ -1142,6 +1142,7 @@ external legendre_Ql_e : int -> float ->
 
 
 
+(*
 (* Associated LEGENDRE functions *)
 external legendre_Plm : int -> int -> float -> float
 = "ml_gsl_sf_legendre_Plm"
@@ -1167,6 +1168,7 @@ external  legendre_sphPlm_array : int ->
 
 external  legendre_array_size : int -> int -> int 
 = "ml_gsl_sf_legendre_array_size"
+*)
 
 
 
--- orpie-1.5.2.orig/gsl/mlgsl_error.c
+++ orpie-1.5.2/gsl/mlgsl_error.c
@@ -34,6 +34,7 @@ static value   *ml_gsl_exn;
 
 static void ml_gsl_raise_exn(const char *msg, int gsl_errno)
 {
+  CAMLparam0();
   CAMLlocal2(exn_msg, exn_arg);
   exn_msg = copy_string(msg);
   exn_arg = alloc_small(2, 0);


Bug#869968: erlang-lager: FTBFS on alpha, hurd-i386, kfreebsd-amd64 and sparc64 due to failing eunit tests

2017-07-28 Thread Philipp Huebner
Package: erlang-lager
Version: 3.5.1-1
Severity: important
Tags: upstream

several different eunit tests fail on some of the ports,
namely alpha, hurd-i386, kfreebsd-amd64, and sparc64, due to failing eunit
tests, see
https://buildd.debian.org/status/package.php?p=erlang-lager&suite=sid



Bug#869969: ITP: gfapy -- flexible and extensible software library for handling sequence graphs

2017-07-28 Thread Sascha Steinbiss
Package: wnpp
Severity: wishlist
Owner: Sascha Steinbiss 

* Package name: gfapy
  Version : 1.0.0
  Upstream Author : Giorgio Gonnella
* URL : https://github.com/ggonnella/gfapy
* License : ISC
  Programming Lang: Python
  Description : flexible and extensible software library for handling 
sequence graphs

The Graphical Fragment Assembly (GFA) are formats for the representation of
sequence graphs, including assembly, variation and splicing graphs. Two
versions of GFA have been defined (GFA1 and GFA2) and several sequence
analysis programs have been adopting the formats as an interchange format,
which allow the user to easily combine different sequence analysis tools.

This library implements the GFA1 and GFA2 specification. It is possible to
create a Gfa object from a file in the GFA format or from scratch, to
enumerate the graph elements (segments, links, containments, paths and header
lines), to traverse the graph (by traversing all links outgoing from or
incoming to a segment), to search for elements (e.g. which links connect two
segments) and to manipulate the graph (e.g. to eliminate a link or a segment
or to duplicate a segment distributing the read counts evenly on the copies).

The GFA format can be easily extended by users by defining own custom tags
and record types. In Gfapy, it is easy to write extensions modules, which
allow one to define custom record types and datatypes for the parsing and
validation of custom fields. The custom lines can be connected, using
references, to each other and to lines of the standard record types.



Bug#869970: diamond: debugging output always on with --log-stdout

2017-07-28 Thread Filippo Giunchedi
Package: diamond
Version: 4.0.515-4
Severity: normal
Tags: upstream

Hi,
we've noticed that diamond invoked with --log-stdout results in DEBUG logging
level set regardless of configuration option and resulting in "syslog spam".
This seems to be fixed upstream with commit a8e474dc44 where --log-stdout now
honors the diamond.conf file for logging levels.

thanks!
Filippo

-- System Information:
Debian Release: 8.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable-proposed-updates'), 
(500, 'oldstable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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



Bug#860810: freerdp: please drop dbg packages in favour of dbgsym packages

2017-07-28 Thread Mike Gabriel

Control: close -1
Control: fixed -1 1.1.0~git20140921.1.440916e+dfsg1-14

Hi Paul,

On  Do 20 Apr 2017 15:23:55 CEST, Paul Wise wrote:


Source: freerdp
Version: 1.1.0~git20140921.1.440916e+dfsg1-13
Severity: wishlist
Usertags: debug

Please drop the dbg packages in favour of dbgsym packages:

https://wiki.debian.org/AutomaticDebugPackages


I missed closing this bug with the recent freerdp(v1) upload.

The dbg packages have been replaced by dbgsym packages now.

Greets,
Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgp1NNc9p81O9.pgp
Description: Digitale PGP-Signatur


Bug#869962: [INTL:sv] Swedish strings for igtf-policy-bundle debconf

2017-07-28 Thread Dennis van Dok
On 28-07-17 08:53, Martin Bagge wrote:
> package: igtf-policy-bundle
> severity: wishlist
> tags: patch l10n
> 
> Please consider to add this file to translation of debconf.

Will do, thanks!



Bug#854842: diamond takes a while to stop, errors out, slows down shutdown

2017-07-28 Thread Filippo Giunchedi
On Sun, Feb 12, 2017 at 01:04:41PM -0500, Sandro Tosi wrote:
> > As a user, what I can say is that slowing reboots down for a minute
> > (systemd showing the red error bar and says that's waiting for it), as
> > well as taking a minute to restart e.g. every time puppet pushes a new
> > config, is not an acceptable behavior for this kind of package. We have
> > diamond installed in ~1200 servers or so (currently v3.0) and this kind
> > of behavior would get annoying real quick.
> 
> Hopefully upstream will respond soon and i will still attempt to get a
> fix in stretch

I was able to reproduce this bug in stretch, see also the updates at
https://github.com/python-diamond/Diamond/issues/595. Though upstream's fix
committed in fd4146dc3 does the trick and results in a fast shutdown for 
diamond.

Any change the fix could be backported in unstable (ideally to stretch-updates
too) ? I'm happy to help too if needed!

thanks,
Filippo



Bug#869971: nose: Provide a package for PyPy

2017-07-28 Thread Ghislain Antony Vaillant
Source: nose
Severity: wishlist

Dear Maintainer,

The lack of a nose package for PyPy may block testing of future packaged
PyPy modules. Since nose should be compatible with PyPy according to the
upstream wiki [1], you might want to consider providing a corresponding
pypy-nose package.

[1] https://bitbucket.org/pypy/compatibility/wiki/nose

Cheers,
Ghis


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

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



Bug#869972: libbrlapi-dev: Missing model specific headers (brldefs-xx.h)

2017-07-28 Thread Mario Lang
Package: libbrlapi-dev
Version: 5.4-7+b1
Severity: normal

Hi.

BRLTTY exports model-specific headers to make key codes (and a few other
things) available as enums...  These are important
for BrlAPI clients that make use of "raw keycode" mode.

BRLTTY installs these into /usr/include/brltty/:

$ ls brldefs-*.h
brldefs-al.h  brldefs-cb.h  brldefs-hm.h  brldefs-mm.h  brldefs-sk.h
brldefs-at.h  brldefs-ce.h  brldefs-ht.h  brldefs-mt.h  brldefs-ts.h
brldefs-bg.h  brldefs-eu.h  brldefs-hw.h  brldefs-np.h  brldefs-vo.h
brldefs-bm.h  brldefs-fs.h  brldefs-ir.h  brldefs-pg.h  brldefs-vs.h
brldefs-bn.h  brldefs-hd.h  brldefs-md.h  brldefs-pm.h

But debian/brlapi-dev.install does not install them.

Please consider shipping these headers, they contain useful information.

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

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

Versions of packages libbrlapi-dev depends on:
ii  libbrlapi0.6  5.4-7+b1

libbrlapi-dev recommends no packages.

libbrlapi-dev suggests no packages.

-- no debconf information

-- 
CYa,
  ⡍⠁⠗⠊⠕ | Blog:   GitHub: 
  .''`. | Twitter: @blindbird23FaceBook: disyled
 : :' : | SoundCloud: 
 `. `'  | YouTube: 
   `-



Bug#869973: nrpe: please update to nrpe >= 3.2.1 (get rid of useless log message)

2017-07-28 Thread Bernd Zeimetz

Package: ngios-nrpe-server
Version: 3.2.0-4
Severity: normal

Hi,

nrpw 3.2.0 prints
ERROR: my_system() seteuid(0): Operation not permitted
for every plugin execution into the log, which is rather annoying.

Its fixed in 3.2.1:
https://github.com/NagiosEnterprises/nrpe/issues/148

Please update the package. I can take care of the backports if you'd 
like me to.


Thanks,

Bernd

--
Mit freundlichen Grüßen


Bernd Zeimetz
Systems Engineer
Debian Developer

conova communications GmbH
Web| http://www.conova.com/
E-Mail | b.zeim...@conova.com

Zentrale Salzburg
Karolingerstraße 36A
5020 Salzburg

Tel | +43 (0) 662 22 00 - 313
Fax | +43 (0) 662 22 00 - 209

Es gelten die Allgemeinen Geschäftsbedingungen der
conova communications GmbH, http://www.conova.com/de/agb/


smime.p7s
Description: S/MIME cryptographic signature


Bug#869201: RFS: etcd/3.1.8+dfsg-2+nmu1 [NMU]

2017-07-28 Thread Harish Sriram





> No, the correct suffix for non-native package NMUs is .1, not +nmu1.
> Please use dch --nmu and read
> https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#nmu

Uploaded a new version with proper name. Thanks!

> Besides, there are three RC bugs in the package while this NMU solves
only
> one. And you've even posted a patch to other one. While are you not
> including it here?

This NMU is olny for one RC bug. Is it mandatory to fix all RC bugs.

Regarding the other Bug, the patch fixes the integration related tests
only.
At the time of attaching to the Bug. That was the only issue observed while
running tests. Now, I observe that few other tests also fails which does
not
close the Bug. Hence, I have excluded that patch.

Thanks.
Harish


Bug#869201: RFS: etcd/3.1.8+dfsg-2+nmu1 [NMU]

2017-07-28 Thread Andrey Rahmatullin
On Fri, Jul 28, 2017 at 03:10:35PM +0530, Harish Sriram wrote:
> > No, the correct suffix for non-native package NMUs is .1, not +nmu1.
> > Please use dch --nmu and read
> > https://www.debian.org/doc/manuals/developers-reference/ch05.en.html#nmu
> 
> Uploaded a new version with proper name. Thanks!
Please include the new link and also retitle the bug accordingly.

> > Besides, there are three RC bugs in the package while this NMU solves
> only
> > one. And you've even posted a patch to other one. While are you not
> > including it here?
> 
> This NMU is olny for one RC bug. Is it mandatory to fix all RC bugs.
No, but what's the reason to upload a NMU to fix just one? Do you need
that fix on some unstable system?


-- 
WBR, wRAR


signature.asc
Description: PGP signature


Bug#869974: boinc: World Community Grid returns "Computation error" Job does not process

2017-07-28 Thread andy
Package: boinc
Version: 7.6.33+dfsg-12
Severity: normal

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Installed Boinc, no problems. Processes jobs from pogs (the Skynet) no 
problems. Jobs from World Community Grid won't process.
  


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

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

Versions of packages boinc depends on:
ii  boinc-client   7.6.33+dfsg-12
ii  boinc-manager  7.6.33+dfsg-12

boinc recommends no packages.

boinc suggests no packages.

-- no debconf information



Bug#869873: marked as done (Stretch regression: apt-key fails due to missing gnupg)

2017-07-28 Thread David Kalnischkies
On Thu, Jul 27, 2017 at 03:09:50PM +0200, Harald Dunkel wrote:
> If gpg and its derivatives are so fragile, I wonder if there
> is an alternative?

gpg isn't fragile. Fetching keys and stuff directly from the internet is
not much of a problem in its normal mode of operation as you still have
the web of trust – you don't magically trust a key just because it is in
the keyring. gpg will in fact complain about not trusting it if you or
trusted peers haven't signed it. That needs a user to actively maintain
it a bit by refreshing keys, assigning trust values and co through.

That is different from the situation apt is in: If a key is in the
keyring it has ultimate trust, so that keyring must be protected with
your life – but on the upside you don't need to manage it manually if
you don't want to as it will be managed for you.

Argueably the behaviour of gpg is better, but has one tiny problem: Have
you got a verify connection to the archive signing key via the web of
trust? The answer is very likely no, due to it being a rather technical
thing at the moment.

So what apt and basically any other software does is having some kind of
ultimate trust database. Your browser e.g. has a giant certificate
store. And they all hope that changes to that database are done with
great care.

In apt it was just decided that we aren't going to invent our own way of
public-key cryptography and implement it, but just reuse what already
exists in the form of gpg by bending it to our needs – with the upside
that one day we might 'easily' change to the web of trust if it becomes
feasible for our usecase.


Best regards

David Kalnischkies


signature.asc
Description: PGP signature


Bug#869975: [opencv] bug in debian/rules -> it isn't compiled with OPENGL=ON

2017-07-28 Thread Jean Jacques BRUCKER
Source: opencv
Version: 2.4.9.1+dfsg1-2

There should be missing an "else" in debian/rules which implies
WITH_OPENGL is always ON for ubuntu (overriding previous if-else
statement) and always undefined for other distributions.

Here is the fix: 

--- a/debian/rules
+++ b/debian/rules
@@ -33,6 +33,7 @@ CMAKE_ARCH_FLAGS += -DWITH_OPENGL=ON
 else
 CMAKE_ARCH_FLAGS += -DWITH_OPENGL=OFF
 endif
+else
 CMAKE_ARCH_FLAGS += -DWITH_OPENGL=ON
 endif


pgpdHmCkjIX91.pgp
Description: Signature digitale OpenPGP


Bug#869967: [Pkg-erlang-devel] Bug#869967: rebar: FTBFS on hppa

2017-07-28 Thread Sergei Golovan
Hi Philipp,

On Fri, Jul 28, 2017 at 12:00 PM, Philipp Huebner  wrote:
> Package: rebar
> Version: 2.6.4-2
> Severity: important
>
> Hi,
>
> rebar 2.6.4-2 FTBFS on hppa,
> and the one that has already been built on hppa does not working,
> breaking the whole chain of Erlang based packages that depend on it.

The reason looks awfully similar to this FTBFS of Yaws:
https://buildd.debian.org/status/fetch.php?pkg=yaws&arch=hppa&ver=2.0.4%2Bdfsg-2&stamp=1499690327&raw=0

Looks like a bug in Erlang re module (regexp engine) which shows only for hppa.

Cheers!
-- 
Sergei Golovan



Bug#869945: all kvm guests crash during startup

2017-07-28 Thread Michael Tokarev
Control: tag -1 + confirmed
Control: retitle -1 all qemu guests with nec-usb-xhci crash during startup 
(assertion falure)

28.07.2017 00:42, Ulrich Baum wrote:
> Package: qemu-system-x86
> Version: 1:2.8+dfsg-6+deb9u1
> 
> When I try to start any kvm guest via virsh start , the guest
> crashes during startup. See log extract below.
> Downgrading to qemu-system-x86=1:2.8+dfsg-6 solves the problem.
> 
> Extract from /var/log/libvirt/qemu/guest.log :

>  /usr/bin/qemu-system-x86_64 -name guest=a,debug-threads=on -S -object
...
> strict=on -device nec-usb-xhci,id
...
> warning: host doesn't support requested feature: CPUID.01H:EDX.ds [bit 21]
> warning: host doesn't support requested feature: CPUID.01H:EDX.acpi [bit 22]
> warning: host doesn't support requested feature: CPUID.01H:EDX.ht [bit 28]
> warning: host doesn't support requested feature: CPUID.01H:EDX.tm [bit 29]
> warning: host doesn't support requested feature: CPUID.01H:EDX.pbe [bit 31]
> warning: host doesn't support requested feature: CPUID.01H:ECX.dtes64 [bit 2]
> warning: host doesn't support requested feature: CPUID.01H:ECX.monitor [bit 3]
> warning: host doesn't support requested feature: CPUID.01H:ECX.ds-cpl [bit 4]
> warning: host doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]
> warning: host doesn't support requested feature: CPUID.01H:ECX.est [bit 7]
> warning: host doesn't support requested feature: CPUID.01H:ECX.tm2 [bit 8]
> warning: host doesn't support requested feature: CPUID.01H:ECX.xtpr [bit 14]
> warning: host doesn't support requested feature: CPUID.01H:ECX.pdcm [bit 15]
> warning: host doesn't support requested feature: CPUID.01H:ECX.osxsave [bit 
> 27]

I'm not sure what this means, it'd be interesting to know, but it is unrelated.

> qemu-system-x86_64:
> /build/qemu-0Yb2kr/qemu-2.8+dfsg/hw/usb/hcd-xhci.c:2169:
> xhci_kick_epctx: A
> ssertion `!epctx->kick_active' failed.

And here we go.

This is due to (apparently wrong) security fix in 1:2.8+dfsg-6+deb9u1,
"xhci: guard xhci_kick_epctx against recursive calls".

I'll investigate further.

Thanks!

/mjt



Bug#858733: RFS: clickhouse/1.1.54190-1 [ITP]

2017-07-28 Thread Andrey Rahmatullin
Control: tags -1 + moreinfo

Some preliminary remarks:

Why B-D specifically on gcc-6, g++-6?
Version in Depends: lsb-base (>= 3.2-14) can be dropped.
Current Standards-Version is 4.0.0.
Current debian/compat is 10.
Are you sure this Pre-Depends usage is correct? Have you discussed it as
required by the Policy? I suppose it's because clickhouse-client.postinst
uses the user created in clickhouse-common.postinst but I don't think it
is needed in this case.
Besides, I think you shouldn't use chown to change ownership, see
https://www.debian.org/doc/debian-policy/ch-files.html#s-permissions-owners
Besides, I don't think it's advisable to have a dir in /etc owned by a
service user (while the group will remain root? why?).
The current consensus is to not delete users on purge.
AUTHORS and README.md are included in several subpackages, this seems
wrong. And in debian/clickhouse-utils.docs they are listed twice.
There seems to be a typo in the PID file name in
debian/clickhouse-server.service
Some of the descriptions miss the trailing period.
Is debian/copy_clang_binaries.sh unused?
debian/libclickhouse1.symbols is empty.
debian/copyright is very wrong with a single copyright and license for the
entire project: it lacks licenses and copyrights for all bundled third-party
code, there are several MIT-licensed files in the main code and docs, and
that's without doing a full analysis.

Now to debian/rules.
Why --max-parallel=4?
override_dh_auto_clean runs dh_clean, not dh_auto_clean, and it also does
a bunch of rm's while dh_clean can do that with debian/clean.
I think removing embedded copies should be done in clean, not in build.
dh_auto_configure should run cmake, not override_dh_auto_build.
Manual make -j`grep -c ^processor /proc/cpuinfo` is wrong.
"will wait for the ability to use system libs instead of contrib ones"
comment is worrying, so did that already happen or not? 
copy_headers.sh seems wrong.
dh_install --sourcedir=debian/tmp is the default, isn't it? In any case it
shouldn't be run in override_dh_auto_install.
Creating dirs should be done by dh_installdirs.

And the build fails in sbuild:

./debian/tests_wrapper.sh
/<>
grep: ../../debian/clickhouse-server-config-tests-preprocessed.xml: No such 
file or directory
grep: /etc/clickhouse-server/config-preprocessed.xml: No such file or directory

Running stateless tests.

1_select_1:[ FAIL ] 
- return code 232
/usr/share/zoneinfo/Asia/Yekaterinburg: No such file or directory
Poco::Exception: Exception: Cannot load time zone Asia/Yekaterinburg
[...]
00039_inserts_through_http:[ FAIL ] 
- return code 7
curl: (7) Failed to connect to localhost port 8123: Connection refused
[...]
Having 58 errors!
./debian/tests_wrapper.sh: line 30: 31404 Aborted (core dumped) 
PATH=$PATH:./build/dbms/src/Server ./build/dbms/src/Server/clickhouse-server 
--config-file=./debian/clickhouse-server-config-tests.xml 2> /dev/null  (wd: 
/<>)
./debian/tests_wrapper.sh: line 18: kill: (31404) - No such process
debian/rules:31: recipe for target 'override_dh_auto_test' failed


-- 
WBR, wRAR


signature.asc
Description: PGP signature


Bug#869976: ITP: python-parameterized -- parameterized testing for Python

2017-07-28 Thread Ghislain Antony Vaillant
Package: wnpp
Severity: wishlist
Owner: Ghislain Antony Vaillant 

* Package name: python-parameterized
  Version : 0.6.1
  Upstream Author : David Wolever
* URL : https://github.com/wolever/parameterized
* License : BSD
  Programming Lang: Python
  Description : parameterized testing for Python

The parameterized module supersedes nose-parameterized (from the same
author) as it is no longer tied to nose specifically. Besides the name
change, the API is no longer compatible with the version of
nose-parameterized currently packaged in the archive (0.3.x). Both can
happily co-exist though, as they use different namespaces.

This package is required for the new version of Theano. It will be
co-maintained by the Debian Python Modules Team.



Bug#869977: ghostscript: CVE-2017-11714: Out of bounds read in igc_reloc_struct_ptr()

2017-07-28 Thread Salvatore Bonaccorso
Source: ghostscript
Version: 9.06~dfsg-2
Severity: grave
Tags: patch security upstream fixed-upstream
Forwarded: https://bugs.ghostscript.com/show_bug.cgi?id=698158

Hi,

the following vulnerability was published for ghostscript.

CVE-2017-11714[0]:
| psi/ztoken.c in Artifex Ghostscript 9.21 mishandles references to the
| scanner state structure, which allows remote attackers to cause a
| denial of service (application crash) or possibly have unspecified
| other impact via a crafted PostScript document, related to an
| out-of-bounds read in the igc_reloc_struct_ptr function in psi/igc.c.

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-2017-11714
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-11714
[1] https://bugs.ghostscript.com/show_bug.cgi?id=698158
[2] 
http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=671fd59eb657743aa86fbc1895cb15872a317caa

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore



Bug#869516: reproducible build for libcdio

2017-07-28 Thread Chris Lamb
Hi Rocky,

> If you create patch against the current libcdio sources
> https://savannah.gnu.org/git/?group=libcdio I will add that to the
> source.

Just looked at this. So:

a) The find […] -delete call is Debian-specific AFAICT, unless you
think otherwise?

b) The actual source/buldpath issue can be fixed better by simply
dropping the entire calculation of `pwd` altogether; it wasn't even
being used in the Doxygen config as FULL_PATH_NAMES is set to NO.

I've attached a patch that demonstrates what I mean, but please do
test it :)


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
From 08c1768aaeea86c522c0ef1705b9b6d434ebd3ae Mon Sep 17 00:00:00 2001
From: Chris Lamb 
Date: Fri, 28 Jul 2017 11:49:13 +0100
Subject: [PATCH] Drop LIBCDIO_SOURCE_PATH by dropping STRIP_FROM_PATH Doxygen
 setup; it's not used as FULL_PATH_NAMES = no

---
 configure.ac| 5 -
 doc/doxygen/Doxyfile.in | 2 +-
 2 files changed, 1 insertion(+), 6 deletions(-)

diff --git a/configure.ac b/configure.ac
index 30fa678e..ac1bdd50 100644
--- a/configure.ac
+++ b/configure.ac
@@ -552,11 +552,6 @@ AC_SUBST(HAVE_SOLARIS_CDROM)
 AC_SUBST(HAVE_WIN32_CDROM)
 AC_SUBST(HAVE_OS2_CDROM)
 
-LIBCDIO_SOURCE_PATH="`pwd`"
-AC_DEFINE_UNQUOTED(LIBCDIO_SOURCE_PATH, "$LIBCDIO_SOURCE_PATH",
-	[Full path to libcdio top_sourcedir.])
-AC_SUBST(LIBCDIO_SOURCE_PATH)
-
 AC_CHECK_FUNCS( [chdir drand48 fseeko fseeko64 ftruncate geteuid getgid \
 		 getuid getpwuid gettimeofday lseek64 lstat memcpy memset mkstemp rand \
 		 seteuid setegid snprintf setenv strndup unsetenv tzset sleep \
diff --git a/doc/doxygen/Doxyfile.in b/doc/doxygen/Doxyfile.in
index a16b99e0..53ff08da 100644
--- a/doc/doxygen/Doxyfile.in
+++ b/doc/doxygen/Doxyfile.in
@@ -138,7 +138,7 @@ FULL_PATH_NAMES= NO
 # If left blank the directory from which doxygen is run is used as the
 # path to strip.
 
-STRIP_FROM_PATH= @LIBCDIO_SOURCE_PATH@
+STRIP_FROM_PATH=
 
 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
 # the path mentioned in the documentation of a class, which tells
-- 
2.13.3



Bug#865803: libsoup2.4 FTBFS: Unacceptable TLS certificate

2017-07-28 Thread Simon McVittie
Control: retitle 865803 libsoup2.4 FTBFS: Unacceptable TLS certificate
Control: tags 865803 + upstream patch fixed-upstream
Control: forwarded 865803 https://bugzilla.gnome.org/show_bug.cgi?id=784949

On Sun, 25 Jun 2017 at 00:49:53 +0300, Adrian Bunk wrote:
> FAIL: misc-test 4 /misc/aliases

This is not very informative. The more interesting part of a recent
Autotools test log is further down, after the heading you quoted:

> ==
>libsoup 2.56.0: tests/test-suite.log
> ==
> 
> # TOTAL: 526
> # PASS:  461
> # SKIP:  50
> # XFAIL: 0
> # FAIL:  10
> # XPASS: 0
> # ERROR: 5

The bug here seems to be:

**
ERROR:misc-test.c:822:do_aliases_test_for_session: assertion failed 
(redirect_protocol == redirected_protocol): ("https" == NULL)
**
ERROR:misc-test.c:824:do_aliases_test_for_session: Unexpected status 6 
Unacceptable TLS certificate (expected 200 OK)
...
**
ERROR:server-test.c:397:do_multi_test: Unexpected status 6 Unacceptable TLS 
certificate (expected 200 OK)
**
ERROR:ssl-test.c:21:do_properties_test_for_session: assertion failed (flags == 
G_TLS_CERTIFICATE_UNKNOWN_CA): (3 == 1)
...
**
ERROR:ssl-test.c:122:do_strictness_test: 'soup_message_get_flags (msg) & 
SOUP_MESSAGE_CERTIFICATE_TRUSTED' should be TRUE

This seems to be https://bugzilla.gnome.org/show_bug.cgi?id=784949
for which there is a patch. The test certificate in tests/test-cert.pem
was not generated according to modern TLS practices: GNUTLS now wants to
see subjectAltName and SHA256.

S



Bug#869710: ITA: libunwind -- library to determine the call-chain of a program

2017-07-28 Thread Graham Inggs

Hi Adrian

The "Debian Julia Team", namely Peter Colberg and myself, were 
discussing  adopting libunwind [1].


Julia probably accounts for less than 10% of the installations of 
libunwind (by popcon), so I think it would be better if libunwind 
remained in collab-maint rather than moving to pkg-julia.


Would you be open to co-maintainers?  I'd be happy to be listed as an 
uploader.


Regards
Graham


[1] 
https://lists.alioth.debian.org/pipermail/pkg-julia-devel/Week-of-Mon-20170724/001658.html




Bug#869978: massif-visualizer FTBFS: datamodeltest (Failed)

2017-07-28 Thread Adrian Bunk
Source: massif-visualizer
Version: 0.6~git20161031-1
Severity: serious
Tags: buster sid

Some recent change in unstable makes massif-visualizer FTBFS:

https://tests.reproducible-builds.org/debian/history/massif-visualizer.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/massif-visualizer.html

...
xvfb-run -a dh_auto_test
make -j15 test ARGS\+=-j15
make[2]: Entering directory 
'/build/1st/massif-visualizer-0.6~git20161031/obj-x86_64-linux-gnu'
Running tests...
/usr/bin/ctest --force-new-ctest-process -j15
Test project /build/1st/massif-visualizer-0.6~git20161031/obj-x86_64-linux-gnu
Start 1: datamodeltest
1/1 Test #1: datamodeltest ***Failed0.11 sec
* Start testing of DataModelTest *
Config: Using QtTest library 5.7.1, Qt 5.7.1 (x86_64-little_endian-lp64 shared 
(dynamic) release build; by GCC 6.3.0 20170628)
PASS   : DataModelTest::initTestCase()
WARNING: DataModelTest::parseFile() testdata /data/massif.out.kate could not be 
located!
   Loc: [massif-visualizer_0.6~git20161031-1/test/datamodeltest.cpp(50)]
QWARN  : DataModelTest::parseFile() QFSFileEngine::open: No file name specified
FAIL!  : DataModelTest::parseFile() 'file.open(QIODevice::ReadOnly)' returned 
FALSE. ()
   Loc: [massif-visualizer_0.6~git20161031-1/test/datamodeltest.cpp(52)]
PASS   : DataModelTest::testUtils()
PASS   : DataModelTest::shortenTemplates(no-tpl)
PASS   : DataModelTest::shortenTemplates(tpl-func)
PASS   : DataModelTest::shortenTemplates(tpl-arg)
PASS   : DataModelTest::shortenTemplates(tpl-multi)
PASS   : DataModelTest::shortenTemplates(tpl-nested)
WARNING: DataModelTest::bigMem() testdata /data/massif.out.huge could not be 
located!
   Loc: [massif-visualizer_0.6~git20161031-1/test/datamodeltest.cpp(167)]
QWARN  : DataModelTest::bigMem() QFSFileEngine::open: No file name specified
FAIL!  : DataModelTest::bigMem() 'file.open(QIODevice::ReadOnly)' returned 
FALSE. ()
   Loc: [massif-visualizer_0.6~git20161031-1/test/datamodeltest.cpp(169)]
PASS   : DataModelTest::cleanupTestCase()
Totals: 8 passed, 2 failed, 0 skipped, 0 blacklisted, 15ms
* Finished testing of DataModelTest *


0% tests passed, 1 tests failed out of 1

Total Test time (real) =   0.11 sec

The following tests FAILED:
  1 - datamodeltest (Failed)
Errors while running CTest
Makefile:88: recipe for target 'test' failed
make[2]: *** [test] Error 8



Bug#869979: gcc-7-cross: please stop building libgnatvsn-dev-cross

2017-07-28 Thread Nicolas Boulenguez
Source: gcc-7-cross
Severity: wishlist

Hello.
As discussed on the debian-ada mailing list, building a cross
libgnatvsn is a waste of efforts.
Version 7.1.0-11 of gcc-7 will only produce a native libgnatvsn.
The attached diff starts the work of adapting gcc-7-cross.
--- a/debian/control
+++ b/debian/control
@@ -356,37 +356,6 @@
  .
  This package contains the runtime shared library.
 
-Package: libgnatvsn7-dev-ppc64el-cross
-Section: libdevel
-Architecture: all
-Priority: extra
-Depends: gcc-7-powerpc64le-linux-gnu-base (= ${gcc:Version}),
- libgnatvsn7-ppc64el-cross (= ${gcc:Version}), ${misc:Depends}
-Description: GNU Ada compiler selected components (development files)
- GNAT is a compiler for the Ada programming language. It produces optimized
- code on platforms supported by the GNU Compiler Collection (GCC).
- .
- The libgnatvsn library exports selected GNAT components for use in other
- packages, most notably ASIS tools. It is licensed under the GNAT-Modified
- GPL, allowing to link proprietary programs with it.
- .
- This package contains the development files and static library.
-
-Package: libgnatvsn7-ppc64el-cross
-Architecture: all
-Priority: extra
-Section: devel
-Depends: gcc-7-powerpc64le-linux-gnu-base (= ${gcc:Version}), libgnat-7-ppc64el-cross (= ${gcc:Version}), ${misc:Depends}
-Description: GNU Ada compiler selected components (shared library)
- GNAT is a compiler for the Ada programming language. It produces optimized
- code on platforms supported by the GNU Compiler Collection (GCC).
- .
- The libgnatvsn library exports selected GNAT components for use in other
- packages, most notably ASIS tools. It is licensed under the GNAT-Modified
- GPL, allowing to link proprietary programs with it.
- .
- This package contains the runtime shared library.
-
 Package: gcc-7-s390x-linux-gnu-base
 Architecture: amd64 i386 x32
 Section: devel
@@ -902,37 +871,6 @@
  GNAT is a compiler for the Ada programming language. It produces optimized
  code on platforms supported by the GNU Compiler Collection (GCC).
 
-Package: libgnatvsn7-dev-s390x-cross
-Section: libdevel
-Architecture: all
-Priority: extra
-Depends: gcc-7-s390x-linux-gnu-base (= ${gcc:Version}),
- libgnatvsn7-s390x-cross (= ${gcc:Version}), ${misc:Depends}
-Description: GNU Ada compiler selected components (development files)
- GNAT is a compiler for the Ada programming language. It produces optimized
- code on platforms supported by the GNU Compiler Collection (GCC).
- .
- The libgnatvsn library exports selected GNAT components for use in other
- packages, most notably ASIS tools. It is licensed under the GNAT-Modified
- GPL, allowing to link proprietary programs with it.
- .
- This package contains the development files and static library.
-
-Package: libgnatvsn7-s390x-cross
-Architecture: all
-Priority: extra
-Section: devel
-Depends: gcc-7-s390x-linux-gnu-base (= ${gcc:Version}), libgnat-7-s390x-cross (= ${gcc:Version}), ${misc:Depends}
-Description: GNU Ada compiler selected components (shared library)
- GNAT is a compiler for the Ada programming language. It produces optimized
- code on platforms supported by the GNU Compiler Collection (GCC).
- .
- The libgnatvsn library exports selected GNAT components for use in other
- packages, most notably ASIS tools. It is licensed under the GNAT-Modified
- GPL, allowing to link proprietary programs with it.
- .
- This package contains the runtime shared library.
-
 Package: gcc-7-aarch64-linux-gnu-base
 Architecture: amd64 i386 x32
 Section: devel
@@ -1257,38 +1195,6 @@
  .
  This package contains the runtime shared library.
 
-Package: libgnatvsn7-dev-arm64-cross
-Section: libdevel
-Architecture: all
-Priority: extra
-Depends: gcc-7-aarch64-linux-gnu-base (= ${gcc:Version}),
- libgnatvsn7-arm64-cross (= ${gcc:Version}), ${misc:Depends}
-Description: GNU Ada compiler selected components (development files)
- GNAT is a compiler for the Ada programming language. It produces optimized
- code on platforms supported by the GNU Compiler Collection (GCC).
- .
- The libgnatvsn library exports selected GNAT components for use in other
- packages, most notably ASIS tools. It is licensed under the GNAT-Modified
- GPL, allowing to link proprietary programs with it.
- .
- This package contains the development files and static library.
-
-Package: libgnatvsn7-arm64-cross
-Architecture: all
-Priority: extra
-Section: devel
-Depends: gcc-7-aarch64-linux-gnu-base (= ${gcc:Version}), libgnat-7-arm64-cross (= ${gcc:Version}), ${misc:Depends}
-Description: GNU Ada compiler selected components (shared library)
- GNAT is a compiler for the Ada programming language. It produces optimized
- code on platforms supported by the GNU Compiler Collection (GCC).
- .
- The libgnatvsn library exports selected GNAT components for use in other
- packages, most notably ASIS tools. It is licensed under the GNAT-Modified
- GPL, allowing to link proprietary programs with it.
- .
- This package contains the runtime shared library.
-

Bug#850891: Additional patch, to cover slurmdbd's duplicate code

2017-07-28 Thread Gennaro Oliva
tags 850891 + wontfix

Hi Rémi and Karl,
since the discussion about this possible feature is over I'm tagging 
this old bug with wontfix.
Thanks for your contribution
-- 
Gennaro Oliva



Bug#854115: RFS: python-verboselogs/1.5-1 [ITP]

2017-07-28 Thread Andrey Rahmatullin
Control: tags -1 + moreinfo

Please change the distribution to unstable.
Please update Standards-Version.
Please switch to the debhelper compat level 10.
Please drop the python2 subpackage unless some app in Debian needs it.
*:Recommends and *:Suggests substvars don't exist.
The license text in d/copyright contains the copyright line, it shouldn't
be there.

-- 
WBR, wRAR


signature.asc
Description: PGP signature


Bug#854249: News regarding the ITP for python-coloredlogs

2017-07-28 Thread Gaurav Juvekar
Hi,

> This issue is currently blocking my work on the spyder-terminal plugin,
> for which coloredlogs is a dependency. Could you guys keep me updated
> on the progress.
> 
> I'd be happy to take over if the motivation is gone.


It would be better if you take over the package. You can start from the last 
push to alioth.

-- 
Regards,
Gaurav Juvekar



Bug#869928: [Pkg-utopia-maintainers] Bug#869928: network-manager-pptp-gnome: Can't fill password

2017-07-28 Thread Александр Широбоков
I have nm-applet. When i click on edit connections -> add or edit pptp
connection,  i see pptp sitting: name, gateway, username, password,  i
can fill in all fields, exept password. Password field is unclickable.

So, how i can save password for this connection? In jessie i can save
password.

I use Mate Desktop Environment.

2017-07-27 20:17 GMT+03:00 Michael Biebl :

> Am 27.07.2017 um 19:10 schrieb ImmortalDragon:
> > Package: network-manager-pptp-gnome
> > Version: 1.2.4-2
> > Severity: important
> >
> > Dear Maintainer,
> >
> > I use mate
> >
> > I can't fill password in sittings. The field is not clickable. But show
> password checkbox is.
> > I can fill password after start connecting, but now checkbox to store
> password.
>
> I don't understand what you are trying to say, sorry.
> Can you try to explain your problem in more details please.
>
>
>


-- 
С уважением, Александр Широбоков.


Bug#869084: linux-image-4.12.0-trunk-amd64: rtl8723be fails to work with old firmware

2017-07-28 Thread Sven Joachim
Control: forwarded -1 https://marc.info/?l=linux-wireless&m=150124050420053&w=2

On 2017-07-20 13:54 +0200, Sven Joachim wrote:

> Package: src:linux
> Version: 4.12.2-1~exp1
> Severity: important
>
> As of commit f70e4df2b384d21e36a7c30a591639592692e0ec, the rtl8723be
> driver uses a new firmware file rtlwifi/rtl8723befw_36.bin which is not
> packaged for Debian yet.  There is fallback code to load the old
> firmware file rtlwifi/rtl8723befw.bin, but does not seem to work, for
> the wifi fails to come up on my laptop. :-(

AFAICS the problem is that request_firmware_nowait() does not wait for
the firmware to show up and returns 0 even if the file is not there, so
the code to load the fallback file will never be reached.

I have reported this upstream now.

Cheers,
   Sven



Bug#869874: [libreoffice]

2017-07-28 Thread Antonio Marcos López Alonso
Package: libreoffice
Version: 1:5.3.5~rc1-3

>"Just"? To 5.3.4-4? That one was obsoleted sincd 6 days by 5.3.5 rc1. Which 
>also
>is in testing since this morning. So how did you upgrade to 5.3.4-4 "just 
>(now)"?

OK, my bad: I forgot "apt update" and upgraded to whatever was in local cache 
(that was 
the reason behind "just (now)"). Just ;-) upgraded to 5.3.5~rc1-3 and the issue 
is still there.

>And what makes you think it's the same symptoms like the bug you reply to?
1) Yesterday I upgraded libreoffice and it immediately ceased to work.
2) Yesterday I opened Reportbug-NG and found a grave issue opened the very same 
day 
regarding libreoffice crashing.
3) I'm afraid I'm not that empirical... ;-)
Regards,
Antonio

--- System information. ---
Architecture: 
Kernel:   Linux 4.11.0-1-amd64

Debian Release: buster/sid
  500 testing ftp.es.debian.org 
  500 stable  dl.google.com 

--- Package information. ---
Depends(Version) | Installed
-+-
===
libreoffice-base | 1:5.3.5~rc1-3
libreoffice-calc | 1:5.3.5~rc1-3
libreoffice-core   (= 1:5.3.5~rc1-3) | 1:5.3.5~rc1-3
libreoffice-draw | 1:5.3.5~rc1-3
libreoffice-impress  | 1:5.3.5~rc1-3
libreoffice-math | 1:5.3.5~rc1-3
libreoffice-report-builder-bin   | 1:5.3.5~rc1-3
libreoffice-writer   | 1:5.3.5~rc1-3
libreoffice-avmedia-backend-gstreamer| 1:5.3.5~rc1-3
 OR libreoffice-avmedia-backend-vlc  | 
python3-uno (>= 4.4.0~beta2) | 1:5.3.5~rc1-3
fontconfig   | 2.12.3-0.2
fonts-opensymbol | 
2:102.10+LibO5.3.5~rc1-3
libreoffice-common  (>> 1:5.3.5~rc1) | 1:5.3.5~rc1-3
ure(>= 5.3.0~beta1~) | 5.3.5~rc1-3
libboost-date-time1.62.0 | 
1.62.0+dfsg-4+b1
libc6  (>= 2.16) | 
libcairo2(>= 1.14.0) | 
libclucene-contribs1v5 (>= 2.3.3.4+dfsg) | 
libclucene-core1v5 (>= 2.3.3.4+dfsg) | 
libcmis-0.5-5v5   (>= 0.5.1+git20160603) | 
libcups2  (>= 1.4.0) | 
libcurl3-gnutls  (>= 7.16.2) | 
libdbus-1-3  (>= 1.9.14) | 
libdbus-glib-1-2   (>= 0.78) | 
libdconf1(>= 0.14.0) | 
libeot0  | 
libepoxy0   (>= 1.0) | 
libexpat1 (>= 2.0.1) | 
libexttextcat-2.0-0   (>= 2.2-8) | 
libfontconfig1 (>= 2.12) | 
libfreetype6  (>= 2.3.5) | 
libgcc1   (>= 1:3.4) | 
libgl1-mesa-glx  | 
 OR libgl1   | 
libglib2.0-0 (>= 2.31.8) | 
libgltf-0.1-1| 
libgraphite2-3(>= 1.2.2) | 
libharfbuzz-icu0 (>= 0.9.42) | 
libharfbuzz0b(>= 0.9.42) | 
libhunspell-1.6-0| 
libhyphen0(>= 2.7.1) | 
libice6 (>= 1:1.0.0) | 
libicu57(>= 57.1-1~) | 
libjpeg62-turbo   (>= 1.3.1) | 
liblcms2-2  (>= 2.2+git20110628) | 
libldap-2.4-2 (>= 2.4.7) | 
libmythes-1.2-0  | 
libneon27-gnutls | 
libnspr4   (>= 2:4.9-2~) | 
libnss3  (>= 2:3.16) | 
libodfgen-0.1-1  | 
liborcus-0.12-0  | 
libpcre3 | 
libpng16

Bug#869710: ITA: libunwind -- library to determine the call-chain of a program

2017-07-28 Thread Adrian Bunk
On Fri, Jul 28, 2017 at 01:03:58PM +0200, Graham Inggs wrote:
> Hi Adrian

Hi Graham,

> The "Debian Julia Team", namely Peter Colberg and myself, were discussing
> adopting libunwind [1].
> 
> Julia probably accounts for less than 10% of the installations of libunwind
> (by popcon), so I think it would be better if libunwind remained in
> collab-maint rather than moving to pkg-julia.
> 
> Would you be open to co-maintainers?  I'd be happy to be listed as an
> uploader.

I am not a fan of comaintainance for small packages, and the previous 
unmaintained state of libunwind was also caused by the package
having two uploaders whose latest uploads were 2005 and never.

Updating to 1.2.1, going through the bugs, check that everything works:
That's a few hours of one-time work, with run-coredump-unwind-mdi in
"make check" sometimes failing when I tried upstream 1.2.1 likely being
the biggest issue.

Afterwards it seems more like a few hours per year of work on the package.

If you want to adopt the package instead of me that's fine for me.

But putting random people who are not currently working on the package 
and likely won't do in the future to Uploaders brings no benefits and 
delays orphaning when the maintainer goes MIA. Fixing issues when the 
maintainer does not respond is already covered by the normal NMU rules.

> Regards
> Graham
>...

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed



Bug#869874: libreoffice: broken. LibreOffice crashes at during startup.

2017-07-28 Thread ch...@musicchris.de
Am 27.07.2017 um 12:37 schrieb Rene Engelhard:
> 
> See http://bugs.debian.org/868507. Giving the information requested there
> would actually be nice.

Let me get back to this a little later, because:


> Try without the binary nvidia drivers if you used them?

Well, that wrecked my whole system! Unistalling of nvidia-driver shredded my 
initramfs, which in turn didn't allow me to open my luks root partition. I'm 
slowly recovering from that, so please don't be annoyed, if I'm not going to 
mess around with GTK3 on my MATE-desktop... :-/

Bottom line is, using Nouveau driver "repaired" LibreOffice! It works like a 
charm. Unfortunately I need the nvidia-driver...

Cheers
chris



-- 
https://musicchris.de

GnuPG Fingerprint: FCFF A94E E987 33C0 F9A0  3FB3 D5FC DF84 9FB3 AC75
GnuPG Info: https://musicchris.de/index.php?page=blog&index=13



signature.asc
Description: OpenPGP digital signature


Bug#869874: [libreoffice]

2017-07-28 Thread Antonio Marcos López Alonso
Package: libreoffice
Version: 1:5.3.5~rc1-3

Attaching "glxinfo" and backtrace, just in case. No NVIDIA involved.

Regards,
Antonio 


--- System information. ---
Architecture: 
Kernel:   Linux 4.11.0-1-amd64

Debian Release: buster/sid
  500 testing ftp.es.debian.org 
  500 stable  dl.google.com 

--- Package information. ---
Depends(Version) | Installed
-+-
===
libreoffice-base | 1:5.3.5~rc1-3
libreoffice-calc | 1:5.3.5~rc1-3
libreoffice-core   (= 1:5.3.5~rc1-3) | 1:5.3.5~rc1-3
libreoffice-draw | 1:5.3.5~rc1-3
libreoffice-impress  | 1:5.3.5~rc1-3
libreoffice-math | 1:5.3.5~rc1-3
libreoffice-report-builder-bin   | 1:5.3.5~rc1-3
libreoffice-writer   | 1:5.3.5~rc1-3
libreoffice-avmedia-backend-gstreamer| 1:5.3.5~rc1-3
 OR libreoffice-avmedia-backend-vlc  | 
python3-uno (>= 4.4.0~beta2) | 
1:5.3.5~rc1-3
fontconfig   | 2.12.3-0.2
fonts-opensymbol | 
2:102.10+LibO5.3.5~rc1-3
libreoffice-common  (>> 1:5.3.5~rc1) | 1:5.3.5~rc1-3
ure(>= 5.3.0~beta1~) | 5.3.5~rc1-3
libboost-date-time1.62.0 | 
1.62.0+dfsg-4+b1
libc6  (>= 2.16) | 
libcairo2(>= 1.14.0) | 
libclucene-contribs1v5 (>= 2.3.3.4+dfsg) | 
libclucene-core1v5 (>= 2.3.3.4+dfsg) | 
libcmis-0.5-5v5   (>= 0.5.1+git20160603) | 
libcups2  (>= 1.4.0) | 
libcurl3-gnutls  (>= 7.16.2) | 
libdbus-1-3  (>= 1.9.14) | 
libdbus-glib-1-2   (>= 0.78) | 
libdconf1(>= 0.14.0) | 
libeot0  | 
libepoxy0   (>= 1.0) | 
libexpat1 (>= 2.0.1) | 
libexttextcat-2.0-0   (>= 2.2-8) | 
libfontconfig1 (>= 2.12) | 
libfreetype6  (>= 2.3.5) | 
libgcc1   (>= 1:3.4) | 
libgl1-mesa-glx  | 
 OR libgl1   | 
libglib2.0-0 (>= 2.31.8) | 
libgltf-0.1-1| 
libgraphite2-3(>= 1.2.2) | 
libharfbuzz-icu0 (>= 0.9.42) | 
libharfbuzz0b(>= 0.9.42) | 
libhunspell-1.6-0| 
libhyphen0(>= 2.7.1) | 
libice6 (>= 1:1.0.0) | 
libicu57(>= 57.1-1~) | 
libjpeg62-turbo   (>= 1.3.1) | 
liblcms2-2  (>= 2.2+git20110628) | 
libldap-2.4-2 (>= 2.4.7) | 
libmythes-1.2-0  | 
libneon27-gnutls | 
libnspr4   (>= 2:4.9-2~) | 
libnss3  (>= 2:3.16) | 
libodfgen-0.1-1  | 
liborcus-0.12-0  | 
libpcre3 | 
libpng16-16 (>= 1.6.2-1) | 
librevenge-0.0-0 | 
libsm6   | 
libstdc++6  (>= 5.2) | 
libx11-6 | 
libxext6 | 
libxinerama1 | 
libxml2   (>= 2.7.4) | 
libxrandr2

Bug#869980: gyoto: test suite times out

2017-07-28 Thread Antonio Terceiro
Source: gyoto
Severity: normal
User: autopkgtest-de...@lists.alioth.debian.org
Usertags: autopkgtest

Hi,

the gyoto test suite times out on ci.debian.net after several hours. See
https://ci.debian.net/packages/g/gyoto/unstable/amd64/ for details

I am blacklisting it from CI, and will revisit this once this bug is
closed.


-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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


signature.asc
Description: PGP signature


Bug#864847: CP15 Barrier emulation performance?

2017-07-28 Thread Adrian Bunk
On Fri, Jul 28, 2017 at 08:30:30AM +, Riku Voipio wrote:
> On Tue, Jul 11, 2017 at 09:45:49AM +0100, Ian Campbell wrote:
> > On Tue, 2017-07-11 at 08:56 +0100, Edmund Grimley Evans wrote:
> > > > Does this emulation take a considerable performance hit, as opposed
> > > > to
> > > > running on armhf hardware/kernel, where the instruction doesn't
> > > > appear
> > > > to be listed as deprecated?
> > > 
> > > I'd expect the kernel-emulated instruction to be much slower than any
> > > non-emulated instruction, but the overall effect on performance will,
> > > of course, depend on how often the instruction is used.
> > > 
> > > See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864847 (where I
> > > think I claimed that the instruction is deprecated on armhf hardware
> > > but I could easily be wrong)
> 
> > Deprecated for both ARMv7 and ARMv8 according to the Kconfig help:
> > config CP15_BARRIER_EMULATION
> > bool "Emulate CP15 Barrier instructions"
> > help
> >   The CP15 barrier instructions - CP15ISB, CP15DSB, and
> >   CP15DMB - are deprecated in ARMv8 (and ARMv7). It is
> >   strongly recommended to use the ISB, DSB, and DMB
> >   instructions instead.
> > 
> >   Say Y here to enable software emulation of these
> >   instructions for AArch32 userspace code. When this option is
> >   enabled, CP15 barrier usage is traced which can help
> >   identify software that needs updating.
> > 
> >   If unsure, say Y
> > 
> > However I there is a sysctl which allows selecting between "undef",
> > "emulated" and "hw" (where the latter is dependent on the hw actually
> > supporting the instructions in question). See:
> > http://elixir.free-electrons.com/linux/latest/source/Documentation/arm64/legacy_instructions.txt
> 
> The ghc sources don't appeart to have direct CP15 instructions, so I suspect
> ghc might be calling llvm with options that make it emit CP15 barriers instead
> of DMB. Anyways look like a configuration error rather than a coding error.

https://sources.debian.net/src/ghc/8.0.2-5/compiler/llvmGen/LlvmCodeGen/Ppr.hs/#L55

ghc contains a hack to change that to arm-unknown-linux-gnueabi for armel.

Changing it to armv7-unknown-linux-gnueabihf will likely fix this issue
for armhf.

> Riku

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed



Bug#869874: [libreoffice]

2017-07-28 Thread Rene Engelhard
On Fri, Jul 28, 2017 at 12:51:40PM +0100, Antonio Marcos López Alonso wrote:
> Package: libreoffice
> Version: 1:5.3.5~rc1-3
> 
> Attaching "glxinfo" and backtrace, just in case. No NVIDIA involved.

Good, you didn't mention a X Error printed on the console. Anyways,
so it's NOT this bug since the originl reporter confirmed using nouveau
insted of nvidia fixes this bug.

(And thus this bug will be basically done nothing on, except mayne asking
upstream and/or reassigning and/or forcing OpenGL off.)

File a new bug for your bug, please.
{ reading the gdbtrace }
Ah, now, don't:

Thread 1 "soffice.bin" received signal SIGSEGV, Segmentation fault.
0xa931cf95 in _expand_stack_to(unsigned char*) () from 
/usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
#0  0xa931cf95 in _expand_stack_to(unsigned char*) () from 
/usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
#1  0xa931f7a4 in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) 
() from /usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
#2  0xa9329ce8 in os::create_main_thread(JavaThread*) () from 
/usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
#3  0xa946c69e in Threads::create_vm(JavaVMInitArgs*, bool*) () from 
/usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
#4  0xa9117f45 in JNI_CreateJavaVM () from 
/usr/lib/jvm/java-8-openjdk-i386/jre/lib/i386/server/libjvm.so
#5  0xb22c49a1 in ?? () from /usr/lib/libreoffice/program/libjvmfwklo.so
#6  0xb22d6bf4 in jfw_startVM(JavaInfo const*, JavaVMOption*, long, JavaVM_**, 
JNIEnv_**) () from /usr/lib/libreoffice/program/libjvmfwklo.so

This is the known Kernel stack class regression on i386. Wouldn't have happened 
on amd64.

FYI:
https://lwn.net/Articles/727206/


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865303


and "friends" merged to it. 


https://lwn.net/Articles/727703/ (ttbomk unforunately subscriber-only by now.)

> --- System information. ---
> Architecture: 
> Kernel:   Linux 4.11.0-1-amd64

Since reportbug-ng failed to report Architecture: I assumed amd64 given the 
kernel,
but obviously not.

This is  clear case of why "I report a me, too to a random bug which might
have appeared the same tim as mine but the symptoms are clearly different" is 
BAD.
Now it "clobbers" that bug log. :(

Regards,

Rene



Bug#869908: relax dependency on faraday in gemspec

2017-07-28 Thread Sebastien Badia
Control: tags -1 + pending moreinfo
Control: owner -1 !

Hi,

Thanks for the bug report, a new version with relaxed deps is ready in our git
repo¹, however, it's seems that you didn't upload ruby-faraday-middleware for 
the
moment (and ruby-faraday-middleware has strong deps on ruby-faraday).

  The following packages have unmet dependencies:
   ruby-faraday-middleware : Depends: ruby-faraday (< 0.10) but 0.11.0-1 is to 
be installed
  E: Unable to correct problems, you have held broken packages.
  root@fb598058d3e2:~# apt policy ruby-faraday-middleware
  ruby-faraday-middleware:
Installed: (none)
Candidate: 0.10.0-1

¹https://anonscm.debian.org/cgit/pkg-puppet/ruby-puppet-forge.git

Seb


signature.asc
Description: PGP signature


Bug#869874: libreoffice: broken. LibreOffice crashes at during startup.

2017-07-28 Thread Rene Engelhard
Hi,

On Fri, Jul 28, 2017 at 01:39:34PM +0200, ch...@musicchris.de wrote:
> Well, that wrecked my whole system!

It was wrecked before already ;)

> Bottom line is, using Nouveau driver "repaired" LibreOffice! It works like a 
> charm. Unfortunately I need the nvidia-driver...

No need to rush, I am not going to care much about this bug in any case if it 
works with nouveau - which you just confirmed. Asked upstream yesterday already,
they don't know off that crash but advise against enabling OpenGL anyways on 
Linux.

Regards,

Rene



Bug#869981: ITP: golang-github-gophercloud-gophercloud -- OpenStack SDK for Go

2017-07-28 Thread Shengjing Zhu
Package: wnpp
Severity: wishlist
Owner: Shengjing Zhu 

* Package name: golang-github-gophercloud-gophercloud
  Version : 0.0~git20170728.0.574cf4f
  Upstream Author : Gophercloud authors
* URL : https://github.com/gophercloud/gophercloud
* License : Apache-2.0
  Programming Lang: Go
  Description : OpenStack SDK for Go

 Gophercloud allows Go developers to connect their applications with
 OpenStack clouds. It is fully open source and supports many OpenStack
 services like Compute, Object Storage, Identity, Networking and
 Block Storage.

It's the new dependency for packer.

I will package this inside pkg-go team and need sponsor as well.

Additional info:

There's golang-github-rackspace-gophercloud in Debian archive, upstream is
https://github.com/rackspace/gophercloud/

gophercloud/gophercloud is considered as a successor of rackspace/gophercloud,
whoes feature was freezon.

In https://github.com/rackspace/gophercloud/issues/592, maintainer of
rackspace/gophercloud says the library will be migrated
gophercloud/gophercloud, and gophercloud/gophercloud are almost entirely
backwards-compatible. However the two libraries do have incompatible 
interface[1],
and they are both used in many projects[2][3].

So I think we can package this package as a new one. The golang import path for
them are different, and they can coexist together.

[1] https://github.com/gophercloud/gophercloud/blob/master/MIGRATING.md
[2] https://godoc.org/github.com/gophercloud/gophercloud?importers
[3] http://godoc.org/github.com/rackspace/gophercloud?importers

Regards,
Shengjing Zhu


signature.asc
Description: PGP signature


Bug#869874: libreoffice: broken. LibreOffice crashes at during startup.

2017-07-28 Thread ch...@musicchris.de
Am 28.07.2017 um 14:03 schrieb Rene Engelhard:
> Hi,
> 
> On Fri, Jul 28, 2017 at 01:39:34PM +0200, ch...@musicchris.de wrote:
>> Well, that wrecked my whole system!
> 
> It was wrecked before already ;)

Actually, it ran very smooth for a long time! That is, if you're not meaning to 
say that using nvidia-driver instead of nouveau is wrecking the system... :o)
I hope someday Nouveau will have all the features, that the nvidia-blob has.


>> Bottom line is, using Nouveau driver "repaired" LibreOffice! It
>> works like a charm. Unfortunately I need the nvidia-driver...
> 
> No need to rush, I am not going to care much about this bug in any case if it 
> works with nouveau - which you just confirmed. Asked upstream yesterday 
> already,
> they don't know off that crash but advise against enabling OpenGL anyways on 
> Linux.

How could I switch off OpenGL for LibreOffice?

BTW, still interested in the traces?




-- 
https://musicchris.de

GnuPG Fingerprint: FCFF A94E E987 33C0 F9A0  3FB3 D5FC DF84 9FB3 AC75
GnuPG Info: https://musicchris.de/index.php?page=blog&index=13



Bug#869954: ifupdown: FTBFS on hurd-i386 and kfreebsd-any

2017-07-28 Thread Guus Sliepen
On Fri, Jul 28, 2017 at 12:52:11AM +0200, Svante Signell wrote:

> ifupdown FTBFS due to a trivial omission to install  on both
> Hurd and kFreeBSD in files archhurd.c and archkfreebsd.c, respectively.

Thanks, I applied your patches.

> Additionally the function expand_matches() needs some fixes to cope
> with Hurd naming network interfaces e.g. /dev/eth0 instead of eth0.

Oh shit. And why is lo without /dev/? Gah! Maybe the best thing is to
find an alternative character for patterns on Hurd... backslash?

> I think we should continue the effort to remove global variables
> further, and provide test cases for the new functionality. Next would
> be a test for the rename option as well as ifquery. I'm pretty sure
> ifquery can be supported for Hurd too. For kFreeBSD I'm more unsure, I
> just checked that the build was OK with the proposed patch.

I can check it in a VM, although I'm not a user of kFreeBSD myself.

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: PGP signature


Bug#869874: libreoffice: broken. LibreOffice crashes at during startup.

2017-07-28 Thread Rene Engelhard
Hi,

On Fri, Jul 28, 2017 at 02:16:11PM +0200, ch...@musicchris.de wrote:
> > It was wrecked before already ;)
> 
> That is, if you're not meaning to say that using nvidia-driver instead of 
> nouveau is wrecking the system... :o)

I am meaning exactly that. :)

> >> Bottom line is, using Nouveau driver "repaired" LibreOffice! It
> >> works like a charm. Unfortunately I need the nvidia-driver...
> > 
> > No need to rush, I am not going to care much about this bug in any case if 
> > it 
> > works with nouveau - which you just confirmed. Asked upstream yesterday 
> > already,
> > they don't know off that crash but advise against enabling OpenGL anyways 
> > on Linux.
> 
> How could I switch off OpenGL for LibreOffice?
> 
> BTW, still interested in the traces?

Yes, anything which I can give upstream will help :), though admittedly I am 
not sure
whether gdb/strace are actually helpful in the case of a thrown X Error, would 
doub it :)

Regards,

Rene



Bug#869982: RM: icewm-themes -- ROM; lost upstream sources and copyright information, RC buggy since 2012

2017-07-28 Thread Eduard Bloch
Package: ftp.debian.org
Severity: normal

The icewm-themes package has been problematic for years. It is based on
original upstream source (where the license was mostly clear) but
contains additional data originating from Freshmeat (which has been dead
for years now) and the upstream version is not available more from the
original source anymore and the old upstream is effectively MIA so it's
hard to get any usable information.

Although there is alternative source to get most of the themes from
Internet (box-look.org), the license information handling there is
basically not existing, and I don't see myself capable of doing full
investigation on copyright issues in all those theme packages.

Therefore, I don't see any other solution but burying the icewm-themes
package in Debian. As said, it hasn't been in a Debian release for half
a decade anyway.

Best regards,
Eduard.



Bug#869983: [patch]: correct release date

2017-07-28 Thread Hideki Yamane
package: www.debian.org
severity: normal
tags: patch

Hi,

 There's a misedit in releases/stretch page, patch attached.

-- 
Regards,

 Hideki Yamane henrich @ debian.or.jp/org
 http://wiki.debian.org/HidekiYamane
--- english/releases/stretch/index.wml.orig	2017-07-28 21:29:31.610363242 +0900
+++ english/releases/stretch/index.wml	2017-07-28 21:32:50.925866263 +0900
@@ -8,7 +8,7 @@
 Debian  was
 released .
 "
-  "Debian 9.0 was initially released on <:=spokendate(''):>."
+  "Debian 9.0 was initially released on <:=spokendate('2017-06-17'):>."
 />
 The release included many major
 changes, described in 


Bug#869652: network-manager: Single work search domains are not written to resolv.conf

2017-07-28 Thread Tobias Ellinghaus
Hi,

according to the folks in #nm on Freenode this got fixed already and will be 
part of 1.8.4.
Maybe for the time being the patch [0] can be added to the Debian package?

Tobias

[0] https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?
id=5aa22ed8c9c1944f8843442912561dcec83a11b2

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


Bug#868977: Confirm that I'm able to verify the problem

2017-07-28 Thread Yaroslav Halchenko

On Thu, 27 Jul 2017, Andreas Tille wrote:

> > would need to dig in, may be later, meanwhile pushed my slight tune ups, 
> > feel
> > welcome to fix up.  You do know where to get the .orig.tar.gz ;)

> Sure I know and I used it for building.  What about simplifying things
> for your team mates and follow policy which does not require them
> downloading the source manually? :-P

> As I said, I would have added pristine-tar if this would not have messed
> up the repository for reasons I do not understand.  It would be really
> cool if you would consider this for next version.

apparently it is a problem in recent pandas, which isn't yet resolved or
worked around in statsmodels
https://github.com/statsmodels/statsmodels/issues/3841#issuecomment-318630239
so we might just need to wait a bit more

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik



Bug#869984: Symbols too large

2017-07-28 Thread Jörg Frings-Fürst
Package: xfce4-pulseaudio-plugin
Version: 0.2.5-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

some symbols at the mixer are displayed too large.

I attach a screenshot about this.


CU
Jörg



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

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

Versions of packages xfce4-pulseaudio-plugin depends on:
ii  libatk1.0-0  2.24.0-1
ii  libc62.24-12
ii  libcairo-gobject21.14.10-1
ii  libcairo21.14.10-1
ii  libdbus-1-3  1.10.20-1
ii  libdbus-glib-1-2 0.108-2
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.52.3-1
ii  libgtk-3-0   3.22.16-1
ii  libkeybinder-3.0-0   0.3.1-1
ii  libnotify4   0.7.7-2
ii  libpango-1.0-0   1.40.6-1
ii  libpangocairo-1.0-0  1.40.6-1
ii  libpulse-mainloop-glib0  10.0-2
ii  libpulse010.0-2
ii  libxfce4panel-2.0-4  4.12.1-2
ii  libxfce4ui-2-0   4.12.1-2
ii  libxfce4util74.12.1-3
ii  libxfconf-0-24.12.1-1

Versions of packages xfce4-pulseaudio-plugin recommends:
ii  pavucontrol  3.0-3.1
ii  pulseaudio   10.0-2

xfce4-pulseaudio-plugin suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY+AHX8jUOrs1qzDuCfifPIyh0l0FAll7Nj0ACgkQCfifPIyh
0l3AxhAA07Zt4RnctYzDgn+ERSVjwSOddw7XEL5zaWBXXHLSytKr3IhFOivR+ZzM
l7pdnDcMQvL0xc63cfBiJDAa6XpAuuzrfPHk4G9lo5kwchEfKVSj4O7srF4BgCG0
4bRMZuBokjs9BYiQIaL1Skqbexweu6xllS5i63cqMLZ6RWxxwVHLmEJVocgYiVn6
WZCZLe/I3RGNVMCDzm5fDkBSpR0y/n9sHqJP/oU7FT9OVL3GnqA/9zn+2bCG36Wt
o+GHbpbV6uSwa/Mj8eQvk1EtIMyEgz3BtrzgB7u67y1RXpzUWrxI3TQN0OzwnFpJ
q3/6lPZBO3mGrqiAtASoz92Kj6lhyD6VBUXFcw6tuc71HCMbLxivrXM1NFeOS4te
4zirNjTKbstnGxGnMdEV+GGkOgvE1L4MMIXBAaKk/+MvRhwYzr2EhdmsepJMpLi1
J21zFEiGuz4Qt9nMphcLmWRagSq6ewI7DNQGYR7xRhaZ5lfMbBvBhqZD4m2XtCRu
qwuJ9RCwQa4h+CzqoA3Hn6AaZxBCwynSf5N4AmNsHBKCc3o5DUHvumAO1E1So7WI
kYd9vE0fsvoSH2nHxciu7rr0xqsL/PgOWblCkicqT4drTITWcOGgrV0WYxT6LD3K
t3k5w7qlaFYWg/rLA7rQckTnlLCMxw3+04E7qevzCMHTtqqRZ5w=
=n32w
-END PGP SIGNATURE-


Bug#869985: ITP: maven-reporting-exec -- Apache Maven Reporting Executor

2017-07-28 Thread Emmanuel Bourg
Package: wnpp
Severity: wishlist
Owner: Emmanuel Bourg 

* Package name: maven-reporting-exec
  Version : 1.3
  Upstream Author : The Apache Software Foundation
* URL : http://maven.apache.org/shared/maven-reporting-exec/
* License : Apache-2.0
  Programming Lang: Java
  Description : Apache Maven Reporting Executor

This library provides classes to manage report plugin executions with Maven 3.
It is required to upgrade the maven-site-plugin and will be maintained by the
Java Team.



Bug#860572: ITA: delay -- a delayed pipe

2017-07-28 Thread Yu-Lun Shih
retitle 860572 ITA: delay -- a delayed pipe

owner 860572 !

thanks


Hi,

I'm willing to packaging this one.

Cheers,

YuLun Shih


Bug#868480: Please build-depend on ocamlbuild

2017-07-28 Thread Stéphane Glondu
retitle 868480 hhvm FTBFS with OCaml 4.05.0: missing ocamlbuild and 
other issues

tags 868480 + patch
thanks

On Sat, 15 Jul 2017 23:46:06 +0200 I wrote:

hhvm uses ocamlbuild. To ease a future transition to ocaml 4.05.0,
where ocamlbuild is a separate package, please add it to
Build-Depends. The dependency is fullfilled by ocaml 4.02.3-10 at the
moment.


There are other issues. Attached is a patch (to upstream) that fixes 
FTBFS with OCaml 4.05.0. It should be compatible with the OCaml 
currently in unstable. Don't forget to add ocamlbuild to Build-Depends.



Cheers,

--
Stéphane
--- hhvm-3.12.11+dfsg/hphp/hack/src/utils/sys_utils.ml	2016-12-17 03:16:10.0 +
+++ hhvm-3.12.11+dfsg.new/hphp/hack/src/utils/sys_utils.ml	2017-07-28 09:31:57.869572546 +
@@ -314,7 +314,7 @@
  on Windows since Vista, but until Seven (included), one should
  have administratrive rights in order to create symlink. *)
   let win32_symlink source dest = write_file ~file:dest source in
-  if Sys.win32 then win32_symlink else Unix.symlink
+  if Sys.win32 then win32_symlink else fun x y -> Unix.symlink x y
 
 (* Creates a symlink at / to
  * //-. *)
--- hhvm-3.12.11+dfsg/hphp/hack/src/_tags	2016-12-17 03:16:10.0 +
+++ hhvm-3.12.11+dfsg.new/hphp/hack/src/_tags	2017-07-28 11:03:23.877973621 +
@@ -1,4 +1,4 @@
-<**/*.ml*>: ocaml, warn_A, warn(-3-4-6-29-35-44-48-50), warn_error_A
+<**/*.ml*>: ocaml, warn_A, warn(-3-4-6-29-35-44-48-50-41-60-45-52), warn_error_A
 <*.ml*>: warn(-27)
 : warn(-27)
 : warn(-27)


Bug#869986: pacemaker FTBFS: missing symbols

2017-07-28 Thread Adrian Bunk
Source: pacemaker
Version: 1.1.17-1
Severity: serious

Some recent change in unstable makes pacemaker FTBFS:

https://tests.reproducible-builds.org/debian/history/pacemaker.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pacemaker.html

...
   dh_makeshlibs
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libcib4/DEBIAN/symbols doesn't match 
completely debian/libcib4.symbols
--- debian/libcib4.symbols (libcib4_1.1.17-1_amd64)
+++ dpkg-gensymbolsUUCK5o   2017-07-27 20:26:24.267558238 -1200
@@ -1,7 +1,7 @@
 libcib.so.4 libcib4 #MINVER#
 * Build-Depends-Package: libcib-dev
- (arch=!powerpc !powerpcspe !ppc64 !ppc64el)__start___verbose@Base 1.1.12
- (arch=!powerpc !powerpcspe !ppc64 !ppc64el)__stop___verbose@Base 1.1.12
+#MISSING: 1.1.17-1# (arch=!powerpc !powerpcspe !ppc64 
!ppc64el)__start___verbose@Base 1.1.12
+#MISSING: 1.1.17-1# (arch=!powerpc !powerpcspe !ppc64 
!ppc64el)__stop___verbose@Base 1.1.12
  anon_cred_c@Base 1.1.12
  cib_apply_patch_event@Base 1.1.12
  cib_client_add_notify_callback@Base 1.1.12
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libcrmcluster4/DEBIAN/symbols doesn't match 
completely debian/libcrmcluster4.symbols
--- debian/libcrmcluster4.symbols (libcrmcluster4_1.1.17-1_amd64)
+++ dpkg-gensymbolsDzcYkt   2017-07-27 20:26:24.731539968 -1200
@@ -1,7 +1,7 @@
 libcrmcluster.so.4 libcrmcluster4 #MINVER#
 * Build-Depends-Package: libcrmcluster-dev
- (arch=!powerpc !powerpcspe !ppc64 !ppc64el)__start___verbose@Base 1.1.10
- (arch=!powerpc !powerpcspe !ppc64 !ppc64el)__stop___verbose@Base 1.1.10
+#MISSING: 1.1.17-1# (arch=!powerpc !powerpcspe !ppc64 
!ppc64el)__start___verbose@Base 1.1.10
+#MISSING: 1.1.17-1# (arch=!powerpc !powerpcspe !ppc64 
!ppc64el)__stop___verbose@Base 1.1.10
  ais_membership_force@Base 1.1.10
  ais_membership_timer@Base 1.1.10
  check_message_sanity@Base 1.1.10
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libcrmcommon3/DEBIAN/symbols doesn't match 
completely debian/libcrmcommon3.symbols
--- debian/libcrmcommon3.symbols (libcrmcommon3_1.1.17-1_amd64)
+++ dpkg-gensymbolsz6i100   2017-07-27 20:26:25.359515239 -1200
@@ -1,7 +1,7 @@
 libcrmcommon.so.3 libcrmcommon3 #MINVER#
 * Build-Depends-Package: libcrmcommon-dev
- (arch=!powerpc !powerpcspe !ppc64 !ppc64el)__start___verbose@Base 1.1.9
- (arch=!powerpc !powerpcspe !ppc64 !ppc64el)__stop___verbose@Base 1.1.9
+#MISSING: 1.1.17-1# (arch=!powerpc !powerpcspe !ppc64 
!ppc64el)__start___verbose@Base 1.1.9
+#MISSING: 1.1.17-1# (arch=!powerpc !powerpcspe !ppc64 
!ppc64el)__stop___verbose@Base 1.1.9
  __xml_acl_to_text@Base 1.1.12
  add_list_element@Base 1.1.9
  add_message_xml@Base 1.1.9
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libcrmservice3/DEBIAN/symbols doesn't match 
completely debian/libcrmservice3.symbols
--- debian/libcrmservice3.symbols (libcrmservice3_1.1.17-1_amd64)
+++ dpkg-gensymbolsSd2Yry   2017-07-27 20:26:25.747499962 -1200
@@ -1,7 +1,7 @@
 libcrmservice.so.3 libcrmservice3 #MINVER#
 * Build-Depends-Package: libcrmservice-dev
- (arch=!powerpc !powerpcspe !ppc64 !ppc64el)__start___verbose@Base 1.1.13
- (arch=!powerpc !powerpcspe !ppc64 !ppc64el)__stop___verbose@Base 1.1.13
+#MISSING: 1.1.17-1# (arch=!powerpc !powerpcspe !ppc64 
!ppc64el)__start___verbose@Base 1.1.13
+#MISSING: 1.1.17-1# (arch=!powerpc !powerpcspe !ppc64 
!ppc64el)__stop___verbose@Base 1.1.13
  get_directory_list@Base 1.1.13
  pcmk_dbus_cb@Base 1.1.13
  resources_action_create@Base 1.1.13
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/liblrmd1/DEBIAN/symbols doesn't match 
completely debian/liblrmd1.symbols
--- debian/liblrmd1.symbols (liblrmd1_1.1.17-1_amd64)
+++ dpkg-gensymbols8MebvV   2017-07-27 20:26:26.279479014 -1200
@@ -1,7 +1,7 @@
 liblrmd.so.1 liblrmd1 #MINVER#
 * Build-Depends-Package: liblrmd-dev
- (arch=!powerpc !powerpcspe !ppc64 !ppc64el)__start___verbose@Base 1.1.9
- (arch=!powerpc !powerpcspe !ppc64 !ppc64el)__stop___verbose@Base 1.1.9
+#MISSING: 1.1.17-1# (arch=!powerpc !powerpcspe !ppc64 
!ppc64el)__start___verbose@Base 1.1.9
+#MISSING: 1.1.17-1# (arch=!powerpc !powerpcspe !ppc64 
!ppc64el)__stop___verbose@Base 1.1.9
  (arch=!powerpc !powerpcspe !ppc64 !ppc64el)lrmd@Base 1.1.9
  lrmd_api_delete@Base 1.1.9
  lrmd_api_new@Base 1.1.9
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libpe-rules2/DEBIAN/symbols doesn't match 
completely debian/libpe-rules2.symbols
--- debian/libpe-rules2.symbols (libpe-rules2_1.1.17-1_amd64)
+++ dpkg-gen

Bug#869987: document (and enable?) the automatic purge of downloaded packages (APT::Periodic::AutocleanInterval)

2017-07-28 Thread Antoine Beaupre
Package: unattended-upgrades
Version: 0.93.1+nmu1
Severity: normal
Tags: patch

Hi,

In the past week, my filesystem finally filled up due to 6GB of
archives in /var/cache/apt/archives. I identified unattended-upgrades
as the cause of this problem, as it didn't purge old packages (hello
texlive!) that it downloaded previously, even when there were
many versions of the same packages.

unattended-upgrades doesn't document how to work around this problem
at all, in itself. There is, however, sparse documentation here and
there that indicate there are ways of doing this with:

// Do "apt-get autoclean" every n-days (0=disable)
APT::Periodic::AutocleanInterval "7";

This is documented in:

https://wiki.debian.org/UnattendedUpgrades
https://debian-handbook.info/browse/stable/sect.regular-upgrades.html

It seem important that the default configuration also documents this
feature, if not just enable it by default.

I filed a pull request upstream for this:

https://github.com/mvo5/unattended-upgrades/pull/68

A.

-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable'), (1, 'experimental'), (1, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: armhf

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

Versions of packages unattended-upgrades depends on:
ii  apt1.4.7
ii  apt-utils  1.4.7
ii  debconf [debconf-2.0]  1.5.61
ii  init-system-helpers1.48
ii  lsb-base   9.20161125
ii  lsb-release9.20161125
ii  python33.5.3-1
ii  python3-apt1.4.0~beta3
ii  ucf3.0036
ii  xz-utils   5.2.2-1.2+b1

Versions of packages unattended-upgrades recommends:
ii  anacron 2.3-24
ii  cron [cron-daemon]  3.0pl1-128+b1

Versions of packages unattended-upgrades suggests:
ii  bsd-mailx 8.1.2-0.20160123cvs-4
ii  msmtp-mta [mail-transport-agent]  1.6.6-1
ii  needrestart   2.11-3

-- debconf information excluded



Bug#869988: highlight.js FTBFS: AssertionError: expected 'htmlbars' to be 'handlebars'

2017-07-28 Thread Adrian Bunk
Source: highlight.js
Version: 9.12.0+dfsg1-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=highlight.js&arch=all&ver=9.12.0%2Bdfsg1-1&stamp=1501157922&raw=0

...
  292 passing (17s)
  1 failing

  1) hljs.highlightAuto() should be detected as handlebars:

  AssertionError: expected 'htmlbars' to be 'handlebars'  
  actual expected
  
  "htmlbarshandlebars"
  
  at Assertion.fail (/usr/lib/nodejs/should/lib/assertion.js:92:17)
  at Assertion.Object.defineProperty.value 
(/usr/lib/nodejs/should/lib/assertion.js:164:19)
  at /<>/highlight.js-9.12.0+dfsg1/test/detect/index.js:27:23
  at Array.forEach (native)
  at Context. 
(/<>/highlight.js-9.12.0+dfsg1/test/detect/index.js:23:8)
  at callFn (/usr/lib/nodejs/mocha/lib/runnable.js:223:21)
  at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:216:7)
  at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10)
  at /usr/lib/nodejs/mocha/lib/runner.js:451:12
  at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14)
  at /usr/lib/nodejs/mocha/lib/runner.js:308:7
  at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23)
  at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:275:5)
  at processImmediate [as _immediateCallback] (timers.js:396:17)



debian/rules:18: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1



Bug#869989: golang-etcd-server-dev: circular dependency hell

2017-07-28 Thread Bill Allombert
Package: golang-etcd-server-dev
Version: 3.1.8+dfsg-2
Severity: important

Hello Debian Go maintainers,

There is a circular dependency between 
golang-etcd-server-dev, golang-github-spf13-cobra-dev, 
golang-github-spf13-viper-dev and 
golang-github-xordataexchange-crypt-dev:

golang-etcd-server-dev:  Depends: golang-github-spf13-cobra-dev
golang-github-spf13-cobra-dev:   Depends: golang-github-spf13-viper-dev (>= 
0.0~git20160605.0.c1ccc37)
golang-github-spf13-viper-dev:   Depends: 
golang-github-xordataexchange-crypt-dev
golang-github-xordataexchange-crypt-dev :Depends: golang-etcd-server-dev

Complex circular dependencies are known to cause problems during upgrade, so we
should try to avoid them.

Also there is little point in having four separated -dev packages, if
you have to install them all anyway.

See threads 
http://lists.debian.org/debian-devel/2005/06/msg02111.html
http://lists.debian.org/debian-devel/2005/11/msg01101.html

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 



Bug#869990: madness FTBFS with cmake 3.9.0

2017-07-28 Thread Adrian Bunk
Source: madness
Version: 0.10.1~gite4aa500e-10
Severity: serious
Tags: buster sid

https://buildd.debian.org/status/fetch.php?pkg=madness&arch=armel&ver=0.10.1~gite4aa500e-10&stamp=1501199307&raw=0
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/madness.html

...
-- Found PythonInterp: /usr/bin/python (found version "2.7.13") 
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE  
-- Found MPI_C: /usr/lib/arm-linux-gnueabi/libmpich.so  
-- Found MPI_CXX: 
/usr/lib/arm-linux-gnueabi/libmpichcxx.so;/usr/lib/arm-linux-gnueabi/libmpich.so
  
CMake Error at cmake/modules/FindMKL.cmake:43 (else):
  A duplicate ELSE command was found inside an IF block.
Call Stack (most recent call first):
  external/lapack.cmake:8 (find_package)
  CMakeLists.txt:495 (include)


-- Configuring incomplete, errors occurred!



Bug#869991: jessie-pu: package slurm-llnl/14.03.9-5

2017-07-28 Thread Gennaro Oliva
Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: pu


I'd like to update slurm-llnl in the next oldstable point release to
address a vulnerability in how the slurmd daemon informs users of
a Prolog failure on a compute node. That vulnerability could allow a
user to assume control of an arbitrary file on the system. Any
exploitation of this is dependent on the user being able to cause or
anticipate the failure (non-zero return code) of a Prolog script that
their job would run on (CVE-2016-10030).

debdiff is attached. The diffstat is:

 changelog  |7 +
 patches/CVE-2016-10030 |  198 +
 patches/series |1 
 3 files changed, 206 insertions(+)

Thanks
-- 
Gennaro Oliva
diff -Nru slurm-llnl-14.03.9/debian/changelog 
slurm-llnl-14.03.9/debian/changelog
--- slurm-llnl-14.03.9/debian/changelog 2014-11-12 12:07:35.0 +0100
+++ slurm-llnl-14.03.9/debian/changelog 2017-07-28 10:52:47.0 +0200
@@ -1,3 +1,10 @@
+slurm-llnl (14.03.9-5+deb8u1) jessie-security; urgency=high
+
+  * Fix security issue caused by insecure file path handling triggered by
+the failure of a Prolog script (CVE-2016-10030)
+
+ -- Gennaro Oliva   Fri, 28 Jul 2017 10:06:41 +0200
+
 slurm-llnl (14.03.9-5) unstable; urgency=medium
 
   [ Roland Fehrenbacher ]
diff -Nru slurm-llnl-14.03.9/debian/patches/CVE-2016-10030 
slurm-llnl-14.03.9/debian/patches/CVE-2016-10030
--- slurm-llnl-14.03.9/debian/patches/CVE-2016-100301970-01-01 
01:00:00.0 +0100
+++ slurm-llnl-14.03.9/debian/patches/CVE-2016-100302017-07-28 
10:03:53.0 +0200
@@ -0,0 +1,198 @@
+Description: FIX CVE-2016-10030
+ Fix security issue caused by insecure file path handling triggered by
+ the failure of a Prolog script. To exploit this a user needs to
+ anticipate or cause the Prolog to fail for their job.
+Author: Tim Wickberg 
+
+---
+Origin: 
https://github.com/SchedMD/slurm/commit/465c98ccff9f1e0018e6a0e6e86ee485ae480ae6
+Bug: 
+Bug-Debian: https://bugs.debian.org/850491
+Last-Update: 28-07-2017
+
+--- slurm-llnl-14.03.9.orig/src/slurmd/slurmd/req.c
 slurm-llnl-14.03.9/src/slurmd/slurmd/req.c
+@@ -155,6 +155,7 @@ static int  _kill_all_active_steps(uint3
+ static void _note_batch_job_finished(uint32_t job_id);
+ static int  _step_limits_match(void *x, void *key);
+ static int  _terminate_all_steps(uint32_t jobid, bool batch);
++static int  _receive_fd(int socket);
+ static void _rpc_launch_tasks(slurm_msg_t *);
+ static void _rpc_abort_job(slurm_msg_t *);
+ static void _rpc_batch_job(slurm_msg_t *msg, bool new_msg);
+@@ -214,6 +215,7 @@ static void _add_job_running_prolog(uint
+ static void _remove_job_running_prolog(uint32_t job_id);
+ static int  _compare_job_running_prolog(void *s0, void *s1);
+ static void _wait_for_job_running_prolog(uint32_t job_id);
++static int _open_as_other(char *path_name, batch_job_launch_msg_t *req);
+ 
+ /*
+  *  List of threads waiting for jobs to complete
+@@ -1275,9 +1277,8 @@ _prolog_error(batch_job_launch_msg_t *re
+   else
+   snprintf(path_name, MAXPATHLEN, "/%s", err_name_ptr);
+ 
+-  if ((fd = open(path_name, (O_CREAT|O_APPEND|O_WRONLY), 0644)) == -1) {
+-  error("Unable to open %s: %s", path_name,
+-slurm_strerror(errno));
++  if ((fd = _open_as_other(path_name, req)) == -1) {
++  error("Unable to open %s: Permission denied", path_name);
+   return;
+   }
+   snprintf(err_name, sizeof(err_name),
+@@ -5306,4 +5307,155 @@ done:
+   slurm_send_rc_msg(msg, rc);
+ }
+ 
++/* pass an open file descriptor back to the parent process */
++static void _send_back_fd(int socket, int fd)
++{
++  struct msghdr msg = { 0 };
++  struct cmsghdr *cmsg;
++  char buf[CMSG_SPACE(sizeof(fd))];
++  memset(buf, '\0', sizeof(buf));
++
++  msg.msg_iov = NULL;
++  msg.msg_iovlen = 0;
++  msg.msg_control = buf;
++  msg.msg_controllen = sizeof(buf);
++
++  cmsg = CMSG_FIRSTHDR(&msg);
++  cmsg->cmsg_level = SOL_SOCKET;
++  cmsg->cmsg_type = SCM_RIGHTS;
++  cmsg->cmsg_len = CMSG_LEN(sizeof(fd));
++
++  memmove(CMSG_DATA(cmsg), &fd, sizeof(fd));
++  msg.msg_controllen = cmsg->cmsg_len;
++
++  if (sendmsg(socket, &msg, 0) < 0)
++  error("%s: failed to send fd: %m", __func__);
++}
+ 
++/* receive an open file descriptor from fork()'d child over unix socket */
++static int _receive_fd(int socket)
++{
++  struct msghdr msg = {0};
++  struct cmsghdr *cmsg;
++  int fd;
++  msg.msg_iov = NULL;
++  msg.msg_iovlen = 0;
++  char c_buffer[256];
++  msg.msg_control = c_buffer;
++  msg.msg_controllen = sizeof(c_buffer);
++
++  if (recvmsg(socket, &msg, 0) < 0) {
++  error("%s: failed to receive fd: %m", __func__);
++  return -1;
++  }
++
++  cmsg = CMSG_FIRSTHDR(&msg);
++  memmove(

Bug#869992: libmaven-plugin-tools-java: circular with libsurefire-java

2017-07-28 Thread Bill Allombert
Package: libmaven-plugin-tools-java
Version: 3.5-3
Severity: important

Hello Debian Java Maintainers,

There is a circular dependency between libmaven-plugin-tools-java and
libsurefire-java:

libmaven-plugin-tools-java  :Depends: libsurefire-java
libsurefire-java:Depends: libmaven-plugin-tools-java

Complex circular dependencies are known to cause problems during
upgrade, so we should try to avoid them.

See threads 
http://lists.debian.org/debian-devel/2005/06/msg02111.html
http://lists.debian.org/debian-devel/2005/11/msg01101.html

Cheers,
-- 
Bill. 

Imagine a large red swirl here. 



Bug#869993: git-debrebase downstream autorebaser wishlist/spec

2017-07-28 Thread Ian Jackson
Package: dgit
Version: 3.12
Severity: wishlist

I had a converation with Matthew Vernon.  He investigated some of the
work done by Peter Green but is considering implementing some slightly
more gitish patch rebaser robot.

A piece of this is close to stuff that git-debrebase already does.
Here is an IRC conversation about what exactly Matthew might want from
git-debrebase.

Ian.

14:28  Emperor: I think you want a tool which strips the
   pseudomerge and maybe a changelog change ?
14:29  Emperor: Do you want it to reapply the pseudomerge ?
14:29  I think maybe not because the user may want to
   git-rebase -i ?
14:29  And that will not go right if there's a pseudomerge at
   the top of the branch.
14:30  Emperor: I think this tool may need two modes, one for
   your robot and one for humans ?
14:30  Emperor: You'll supply it with the base branch name,
   and invoke it with HEAD on the branch you want to edit
   ?
14:31  Are you going to generate debian/changelog entries with
   gbp dch ?  Does this tool want to do that for you ?
14:31  I was expecting to generate d/changelog entries with
   gbp dch, yes.
14:32  Do you in fact want to strip the changelog entries at
   all ?
14:32  I'm not sure why that would be needed if we can merge
   them.
14:32  Diziet: I think so, yes.
14:32  So you don't want a record in the current branch of the
   changelog entries for previous branches ?
14:33  I think that means that you're going to be using git
   tags to find what was done in previous version.
14:33  I was expecting to tag each successful build, yes.
14:34  Emperor: Tag just before publish.
14:35  I think when the distro moves from foo-X-Y to foo-X-Z
   we don't want the changelog from appling our patch(es)
   to foo-X-Y-local to appear in the changelog for
   foo-X-Z-local [assume I get the version numbering
   correct for a moment]
14:35  Emperor: So, the tool should basically take your HEAD
   and launder it by removing changelog updates and
   pseudomerges and leave you with something you can
   git-rebase
14:35  Emperor: Your patches won't have any changelog entries
   then
14:36  You probably want to make gbp dch put something in your
   generated changelogs saying "local history is not
   described here, pls see git"
14:36  Diziet: indeed, I was proposing that the patches would
   have suitable contents in their commit messages for the
   changelog entries to be automatically-produced by
   something like gbp dch
14:36  Emperor: Oh I see.
14:36  So you process the git log into a single new changelog
   entry.
14:36  That makes sense.
14:36  That was my thinking, yes
14:36  Dunno if gbp dch will do that nicely for you but it
   sounds not too hard.
14:37  And if you do that you will indeed generate a single
   commit containing only a changelog update, which a
   branch launderer can know to filter out.
14:37  I've not looked in detail, but a scan of the gbp docs
   suggest it will
14:37  Excellent.
14:38  I think the branch launderer does not need to record
   the current head for a future pseudomerge because
   that's just HEAD from before you start it ?
14:38  (Or maybe it's remotes/myserver/mybranch)
14:38  Emperor: And I think the branch launderer does not need
   to help you _make_ the psuedomerge because that's just
   git merge -s ours.
14:39  I think so
14:39  Looking at it this way means the branch launderer
   doesn't need to know anything about your ref namespace.
14:39  You can tell it explicitly the relevant inputs.
14:39  Well, I think my git-debrebase wip is very close to
   being the thing you want.
14:40  :)
14:40  It is even possible that I would have it in a state
   where it would be able to do that by the time I get
   back.
14:41  So I would recommend that you do not expend any effort
   on this part of your problem and instead hope that I
   will solve it by the time you need it.
14:41  If at any point you come up with an example branch I
   can use as a test case, do let me know.
14:41  OK
14:41  Ideally an example branch in a package that's not
   linux-kernel or libreoffice :-)


-- 
Ian JacksonThese opinions are my own.

If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.



Bug#869994: perl5.26 update: postgresql databases cannot be viewed using browser

2017-07-28 Thread Neil Redgate
Package: perl
Version: 5.26.0-4
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,

The perl 5.26 update on 26th July disabled the file /etc/perl/sitecustomize.pl
.
There were no problems with perl 5.24.

I can no longer access my postgressql database using any web browser for the
sql-ledger 3.2.4 package.
I just get the Internal Server Error - "The server encountered an internal
error or misconfiguration and was unable to complete your request"
Previous remedies included disabling the only line of command in the
sitecustomize.pl file

I have tried re-enabling the sitecustomize.pl file, followed by restarting the
apache2 and postgresql services (separate commands)  each time after making the
code in the file active or disabled. On all occasions the browser shows the
Internal Server Error message.

I can access postgres using the terminal (command line) and using pgAdmin3,
phpPgAdmin.
Apache2 works as I can access other packages through localhost.

When trying to open my postgres database using my web browser (epiphany-
browser) and see the Internal Server Error - I attach below the relevant part
of the apache2/error.log for this action -


[Fri Jul 28 13:45:40.995556 2017] [cgi:error] [pid 6345] [client ::1:40496] End
of script output before headers: admin.pl
[Fri Jul 28 13:46:12.133989 2017] [cgi:error] [pid 6231] [client ::1:40500]
AH01215: Can't locate bin/mozilla/login.pl in @INC (@INC contains: /etc/perl
/usr/local/lib/x86_64-linux-gnu/perl/5.26.0 /usr/local/share/perl/5.26.0
/usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-
gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl
/usr/lib/x86_64-linux-gnu/perl-base) at /usr/local/sql-ledger/login.pl line
119.: /usr/local/sql-ledger/login.pl
[Fri Jul 28 13:46:12.134085 2017] [cgi:error] [pid 6231] [client ::1:40500] End
of script output before headers: login.pl

Looking at the above error text, my system (testing with daily updates) does
not have /usr/local/share/perl nor /usr/local/lib/site_perl.
I created a soft link to /usr/share/perl in /usr/local/share - restarted
apache2 & postgresql services = problem not fixed.

There is no directory site_perl on my system, so I cannot create the
appropriate link.


I trust the above is helpful to identify the problem with the @INC feature
Please accept my apologies for any expected information normally submitted with
a bug report (my first time)
If you require any other information, please let me know

Neil




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

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

Versions of packages perl depends on:
ii  dpkg   1.18.24
ii  libperl5.265.26.0-4
ii  perl-base  5.26.0-4
ii  perl-modules-5.26  5.26.0-4

Versions of packages perl recommends:
ii  netbase  5.4
ii  rename   0.20-4

Versions of packages perl suggests:
ii  libterm-readline-gnu-perl   1.35-1+b2
ii  libterm-readline-perl-perl  1.0303-1
ii  make4.1-9.1
ii  perl-doc5.26.0-4

-- no debconf information



Bug#865006: [Help] Failed to upgrade bcftools to version 1.5

2017-07-28 Thread Andreas Tille
Hi Graham,

On Fri, Jul 28, 2017 at 03:23:40PM +0200, Graham Inggs wrote:
> On 25/07/2017 11:20, Andreas Tille wrote:
> > So how will we deal with #865006 and issues in python-pysam?
> 
> I made a few minor changes to python-pysam 0.11.2.2 (which builds against
> bcftools 1.4.1) as it stands in git, and managed to get it to build and pass
> its tests.  If there are no objections, I can push my changes and upload on
> Monday.

There are definitely no objections! :-)
If you push soon I can upload tomorrow - on Sunday I'll start traveling
and will not be able to upload before I'll reach DebConf venue
 
> The remaining bugs blocking the transition are augustus (bug #869126) and
> bcftools (bug #868958).  Sascha has already pushed the augustus changes to
> git, and it just needs an upload.  The two fixes for bcftools are in the bug
> report, someone should review them and upload.
> 
> The patches can be grabbed from the Ubuntu package:
> https://launchpad.net/ubuntu/+source/bcftools/1.4.1-2ubuntu2

Sascha, will you care for this?

Kind regards

  Andreas. 

-- 
http://fam-tille.de



Bug#869710: ITA: libunwind -- library to determine the call-chain of a program

2017-07-28 Thread Graham Inggs

On 28/07/2017 13:35, Adrian Bunk wrote:

I am not a fan of comaintainance for small packages, and the previous
unmaintained state of libunwind was also caused by the package
having two uploaders whose latest uploads were 2005 and never.


Agreed.


If you want to adopt the package instead of me that's fine for me.


No, please go ahead.  I'm happy that libunwind will be in good hands!



Bug#869789: Feedback

2017-07-28 Thread Shevek Mandragou
Thanks to everyone on this thread who helped us find a working solution
and to Carsten especially for explaining everything in detail and taking
the trouble to provide several solutions and rebuilding the package for
Jessie. That was of great help to us!

In the end we opted for using the Mozilla add-on since this seems to be
the solution less likely to break with future updates, if I understood
everything here correctly.

On Wed, 26 Jul 2017 at 19:05:17 +0200, Carsten Schoenert wrote:
> if seen you have open a similar bug report against enigmail. Please
> mention such similar bug reports also in the affecting package(s).

I'll keep that in mind in future, thanks for letting me know.

Cheers,
Shevek



Bug#869150: /usr/bin/uscan: doesn't find the correct version for directory based version detection

2017-07-28 Thread Osamu Aoki
Hi,


On Thu, Jul 20, 2017 at 07:30:35PM -0400, Paul Gevers wrote:
...
> With the attached (and uploaded) watch file for festlex-cmu, uscan
> reports that there is a version 4 available, while the version it
> found is 2.4. Also running "uscan -v" before the changelog was updated
> showed the wrong behavior.

Good catch! Thanks.

> I don't know enough perl to know how to do it, but I think that the
> expression for the version in the next line isn't greedy (I found this
> on line 3293 in the version in stretch):
> # uversionmanglesd version is '', make best effort to set it
> $newfile_base =~
> m/^.+[-_]?(\d[\-+\.:\~\da-zA-Z]*)(?:\.tar\.(gz|bz2|xz)|\.zip)$/i;
> $newversion = $1;
>^^^

Problem seems to be ".+" is greedy and eat "2."  So this must be
made non-greedy match.

> m/^(?:.+)[-_]?(\d[\-+\.:\~\da-zA-Z]*)(?:\.tar\.(gz|bz2|xz)|\.zip)$/i;
> $newversion = $2;

Question is is there similar code around...

Let's see the log:
> uscan info: Newest upstream tarball version from the filenamemangled
> filename: 4

It get version wrong

> uscan info: Download filename (filenamemangled):
> festvox-rablpc16k_2.4.tar.gz

But download OK...

Osamu
> version=4
> # Note that a "new" version doesn't seem to imply new content.
> opts="filenamemangle=s#.*/festival/@ANY_VERSION@/festlex_CMU#@PACKAGE@_$1#" \
>   http://festvox.org/packed/festival/@ANY_VERSION@/ festlex_CMU@ARCHIVE_EXT@



Bug#869973: nrpe: please update to nrpe >= 3.2.1 (get rid of useless log message)

2017-07-28 Thread Sebastiaan Couwenberg
This issue was already reported in the following bugreports:

 https://bugs.debian.org/868324
 https://bugs.debian.org/868326



Bug#869973: nrpe: please update to nrpe >= 3.2.1 (get rid of useless log message)

2017-07-28 Thread Sebastiaan Couwenberg
Control: tags -1 moreinfo

On Fri, 28 Jul 2017 11:31:34 +0200 Bernd Zeimetz wrote:
> Package: ngios-nrpe-server
> Version: 3.2.0-4

This revision of the package includes the commit for the upstream issue,
so it should only affect nagios-nrpe <= 3.2.0-3.

> Please update the package. I can take care of the backports if you'd 
> like me to.
Can you confirm that the issue does not affect 3.2.0-4?

I've not updated the backport to -4, but will backport 3.2.1 once that's
released and migrated to testing.

Kind Regards,

Bas

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



Bug#869996: RM: maven-embedder -- ROM; No longer used, moved to libmaven3-core-java

2017-07-28 Thread Emmanuel Bourg
Package: ftp.debian.org
Severity: normal

Hi,

Please remove the maven-embedder package, it is no longer used
and its content is now provided by libmaven3-core-java.

Thank you,

Emmanuel Bourg



Bug#869150: /usr/bin/uscan: doesn't find the correct version for directory based version detection

2017-07-28 Thread Osamu Aoki
Oops

I am not much of perl speaker ...

On Fri, Jul 28, 2017 at 11:14:01PM +0900, Osamu Aoki wrote:
> On Thu, Jul 20, 2017 at 07:30:35PM -0400, Paul Gevers wrote:
...
> > I don't know enough perl to know how to do it, but I think that the
> > expression for the version in the next line isn't greedy (I found this
> > on line 3293 in the version in stretch):
> > # uversionmanglesd version is '', make best effort to set it
> > $newfile_base =~
> > m/^.+[-_]?(\d[\-+\.:\~\da-zA-Z]*)(?:\.tar\.(gz|bz2|xz)|\.zip)$/i;
> > $newversion = $1;
> >^^^
> 
> Problem seems to be ".+" is greedy and eat "2."  So this must be
> made non-greedy match.
> 
> > m/^(?:.+)[-_]?(\d[\-+\.:\~\da-zA-Z]*)(?:\.tar\.(gz|bz2|xz)|\.zip)$/i;
> > $newversion = $2;

Should be non-greedy match ... not a non-capturing match .. Sigh

> > m/^.+?[-_]?(\d[\-+\.:\~\da-zA-Z]*)(?:\.tar\.(gz|bz2|xz)|\.zip)$/i;
> > $newversion = $1;

Osamu



Bug#869201: RFS: etcd/3.1.8+dfsg-2.1 [NMU]

2017-07-28 Thread Harish Sriram

Hi Andrey,

Please find the link to new upload.
https://mentors.debian.net/debian/pool/main/e/etcd/etcd_3.1.8+dfsg-2.1.dsc

Still we do not have patches for the other RC bugs. That is why is other
RC's are not addressed here.

Thanks,
Harish


Bug#444874: network-manager-openvpn-gnome: Celebrating ten years of this bug

2017-07-28 Thread Axel Stammler
Package: network-manager-openvpn-gnome
Version: 1.2.8-2
Followup-For: Bug #444874

Dear Maintainer,

the VPN gets incorrectly marked as the default. Configuring clients manually 
works.

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

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

Versions of packages network-manager-openvpn-gnome depends on:
ii  libatk1.0-0  2.22.0-1
ii  libc62.24-11+deb9u1
ii  libcairo-gobject21.14.8-1
ii  libcairo21.14.8-1
ii  libdbus-1-3  1.10.18-1
ii  libdbus-glib-1-2 0.108-2
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgtk-3-0   3.22.11-1
ii  libnm-glib-vpn1  1.6.2-3
ii  libnm-glib4  1.6.2-3
ii  libnm-gtk0   1.4.4-1
ii  libnm-util2  1.6.2-3
ii  libnm0   1.6.2-3
ii  libnma0  1.4.4-1
ii  libpango-1.0-0   1.40.5-1
ii  libpangocairo-1.0-0  1.40.5-1
ii  libsecret-1-00.18.5-3.1
ii  network-manager-openvpn  1.2.8-2

network-manager-openvpn-gnome recommends no packages.

network-manager-openvpn-gnome suggests no packages.

-- no debconf information



Bug#869994: perl5.26 update: postgresql databases cannot be viewed using browser

2017-07-28 Thread gregor herrmann
On Fri, 28 Jul 2017 14:45:11 +0100, Neil Redgate wrote:

Thanks for your detailed bug report!

> I can no longer access my postgressql database using any web browser for the
> sql-ledger 3.2.4 package.

> [Fri Jul 28 13:45:40.995556 2017] [cgi:error] [pid 6345] [client ::1:40496] 
> End
> of script output before headers: admin.pl
> [Fri Jul 28 13:46:12.133989 2017] [cgi:error] [pid 6231] [client ::1:40500]
> AH01215: Can't locate bin/mozilla/login.pl in @INC (@INC contains: /etc/perl
> /usr/local/lib/x86_64-linux-gnu/perl/5.26.0 /usr/local/share/perl/5.26.0
> /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-
> gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl
> /usr/lib/x86_64-linux-gnu/perl-base) at /usr/local/sql-ledger/login.pl line
> 119.: /usr/local/sql-ledger/login.pl
> [Fri Jul 28 13:46:12.134085 2017] [cgi:error] [pid 6231] [client ::1:40500] 
> End
> of script output before headers: login.pl

I'm afraid there's not much we can do here. /etc/perl/sitecustomize.pl
was a temporary workaround which is gone for good now.

It seems that you are using sql-ledger 3.2.4 which is not packaged in
Debian and installed in /usr/local/sql-ledger, and that this version
is not updated to work with Perl 5.26. (I had a brief look at 3.2.5
and it looks like it still does the same "do $file").

https://metacpan.org/pod/release/XSAWYERX/perl-5.26.0/pod/perldelta.pod#Removal-of-the-current-directory-%28%22.%22%29-from-@INC
has background information and a couple of suggestions to remedy the
situation which you can try yourself and/or suggest to the sql-ledger
upstream authors.

(Not closing the bug report yet in case the perl maintainers have
something to add.)


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at/ - Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature


Bug#869962: [INTL:sv] Swedish strings for igtf-policy-bundle debconf

2017-07-28 Thread Anders Jonsson

On Fri, 28 Jul 2017 11:15:58 +0200 Dennis van Dok wrote:
> On 28-07-17 08:53, Martin Bagge wrote:
> > package: igtf-policy-bundle
> > severity: wishlist
> > tags: patch l10n
> >
> > Please consider to add this file to translation of debconf.
>
> Will do, thanks!
>
>

Thanks for the translation, Martin. I saw a small typo in one string. 
("ages" should instead be "anges").


Fixed in the attached po file.


Regards,
Anders Jonsson
# Translation of igtf-policy-bundle debconf template to Swedish
# Copyright (C) 2014 Martin Bagge 
# This file is distributed under the same license as the igtf-policy-bundle package.
#
# Martin Bagge , 2014
msgid ""
msgstr ""
"Project-Id-Version: igtf-policy-bundle\n"
"Report-Msgid-Bugs-To: igtf-policy-bun...@packages.debian.org\n"
"POT-Creation-Date: 2017-07-24 17:44+0200\n"
"PO-Revision-Date: 2017-07-28 08:52+0200\n"
"Last-Translator: Martin Bagge / brother \n"
"Language-Team: Swedish \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Poedit 1.8.11\n"

#. Type: boolean
#. Description
#: ../templates.in:2001
msgid "Trust IGTF @PROFILE@ CAs by default?"
msgstr "Lita på certifikat utfärdade inom IGTF @PROFILE@ som standard?"

#. Type: boolean
#. Description
#: ../templates.in:2001
msgid ""
"Trusted IGTF Certification Authority certificates are installed in "
"${location}."
msgstr "Betrodda IGTF CA-certifikat installeras i ${location}."

#. Type: boolean
#. Description
#: ../templates.in:2001
msgid ""
"Accept this option to have certificates included by default unless they are "
"explicitly excluded. Reject it to choose the reverse policy, excluding them "
"unless explicitly included."
msgstr ""
"Välj detta alternativ för att låta certifikat bli inkluderade som standard "
"om de inte explicit har undantagits. För att ha den omvända funktionen ska "
"alternativet avböjas. Då exkluderas alla som inte explicit väljs för "
"inkludering."

#. Type: boolean
#. Description
#: ../templates.in:2001
msgid "You will then have the opportunity to define the list of exceptions."
msgstr "Då kommer du ha möjlighet att definiera en lista med undantag."

#. Type: multiselect
#. Description
#: ../templates.in:3001
msgid "Certificates to explicitly exclude:"
msgstr "Certifikat att explicit exkludera:"

#. Type: multiselect
#. Description
#: ../templates.in:3001
msgid ""
"Please select which certificates should not be installed in ${location}."
msgstr "Ange vilka certifikat som inte ska installeras i ${location}."

#. Type: multiselect
#. Description
#: ../templates.in:4001
msgid "Certificates to explicitly include:"
msgstr "Certifikat att explicit inkludera:"

#. Type: multiselect
#. Description
#: ../templates.in:4001
msgid "Please select which certificates should be installed in ${location}."
msgstr "Ange vilka certifikat som ska installeras i ${location}."

#. Type: string
#. Description
#: ../templates.in:5001
msgid "Installation directory of the certificates:"
msgstr "Installationskatalog för certifikaten:"

#. Type: string
#. Description
#: ../templates.in:5001
msgid ""
"The default location /etc/grid-security/certificates should work fine in "
"most cases."
msgstr ""
"Standardsökvägen /etc/grid-security/certificates bör fungera i de flesta "
"fall."

#. Type: string
#. Description
#: ../templates.in:5001
msgid "An alternative location can be given here if needed."
msgstr "En alternativ plats kan anges om det behövs."


Bug#869989: golang-etcd-server-dev: circular dependency hell

2017-07-28 Thread Shengjing Zhu
Hi Bill,

IMHO, golang-github-spf13-cobra-dev can be avoid depending
golang-github-spf13-viper-dev

In package github.com/spf13/cobra, it only has github.com/spf13/pflag imported.
github.com/spf13/cobra/cobra can be removed from golang-github-spf13-cobra-dev,
it's only used for building `cobra` binary. I don't think other
packages will import it.

Regards,
Shengjing Zhu


On Fri, Jul 28, 2017 at 9:34 PM, Bill Allombert  wrote:
> Package: golang-etcd-server-dev
> Version: 3.1.8+dfsg-2
> Severity: important
>
> Hello Debian Go maintainers,
>
> There is a circular dependency between
> golang-etcd-server-dev, golang-github-spf13-cobra-dev,
> golang-github-spf13-viper-dev and
> golang-github-xordataexchange-crypt-dev:
>
> golang-etcd-server-dev:  Depends: golang-github-spf13-cobra-dev
> golang-github-spf13-cobra-dev:   Depends: golang-github-spf13-viper-dev (>= 
> 0.0~git20160605.0.c1ccc37)
> golang-github-spf13-viper-dev:   Depends: 
> golang-github-xordataexchange-crypt-dev
> golang-github-xordataexchange-crypt-dev :Depends: golang-etcd-server-dev
>
> Complex circular dependencies are known to cause problems during upgrade, so 
> we
> should try to avoid them.
>
> Also there is little point in having four separated -dev packages, if
> you have to install them all anyway.
>
> See threads
> http://lists.debian.org/debian-devel/2005/06/msg02111.html
> http://lists.debian.org/debian-devel/2005/11/msg01101.html
>
> Cheers,
> --
> Bill. 
>
> Imagine a large red swirl here.
>
> ___
> Pkg-go-maintainers mailing list
> pkg-go-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers



Bug#869995: interface stays in "routable (configuring)", systemd-networkd-wait-online.service in failed state

2017-07-28 Thread Felipe Sateler
On Fri, Jul 28, 2017 at 10:00 AM, Marc Haber <
mh+debian-packa...@zugschlus.de> wrote:

> Package: systemd
> Version: 234-2
> Severity: normal
>
> Hi,
>
> this is on a KVM VM running Debian unstable with a custom kernel. I do
> see this on other machines as well and have not yet investigated
> completely. The phenomenon is the same as mentioned on
> https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1697730, but I
> don't have nplan (whatever that may be).
>
> The system learns its IPv4 configuration via DHCP, does SLAAC for IPv6
> and has an additional IPv6 address statically configured.
>


Does the problem go away if you remove all the static configuration? This
may be related (but not the same as) upstream issue #6359 .

https://github.com/systemd/systemd/issues/6359


-- 

Saludos,
Felipe Sateler


Bug#827414:

2017-07-28 Thread Rodrigo Aguilera
I think rygel is not a desktop application so that is not the appropriate way.
Does rygel comes with some kind of file that alllows you to manage it as a 
service with systemd?


Bug#869997: refcard: Portuguese translation update

2017-07-28 Thread Miguel Figueiredo

Package: refcard
version: n/a
Tags: l10m, patch
Severity: minor

Updated Portuguese translation. Feel free to use it.

BR

# Portugal Portuguese translation of the Debian reference card
# Copyright (C) 2008 Free Software Foundation, Inc.
# This file is distributed under the same license as the refcard package.
#
# Rute Solipa , 2005.
# Miguel Figueiredo , 2008, 2010, 2016, 2017.
msgid ""
msgstr ""
"Project-Id-Version: refcard 10.0\n"
"POT-Creation-Date: 2017-07-26 09:53+0200\n"
"PO-Revision-Date: 2017-07-28 15:50+0100\n"
"Last-Translator: Miguel Figueiredo \n"
"Language-Team: Portuguese \n"
"Language: pt\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Lokalize 1.0\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"

#. type: Attribute 'lang' of: 
#: entries.dbk:4
msgid "en-GB"
msgstr "pt"

#. type: Content of: 
#: entries.dbk:6
msgid "Debian Reference Card"
msgstr "Cartão de Referência Debian"

#. type: Content of: 
#: entries.dbk:9
msgid "The 101 most important things when using Debian"
msgstr "As 101 coisas mais importantes ao utilizar Debian"

#. type: Content of: 
#: entries.dbk:11
msgid ""
" 2004 2010 W. Martin Borgert   2016 2017 "
"Holger Wansing   2004 "
"2010 Your Name (\"Language\") "
msgstr ""
" 2004 2010 W. Martin Borgert   2016 2017 "
"Holger Wansing   2005 "
"Rute Solipa (Portuguese)   "
"2008 2010 2016 Miguel "
"Figueiredo (Portuguese) "

#. type: Content of: 
#: entries.dbk:27
msgid ""
"This document may be used under the terms of the GNU General Public License "
"version 3 or higher. The license text can be found at https://";
"www.gnu.org/copyleft/gpl.html\">https://www.gnu.org/copyleft/gpl.html and /usr/share/common-licenses/GPL-3."
msgstr ""
"Este documento pode ser utilizado sob os termos da licença GNU General "
"Public License versão 3 ou superior. O texto da licença pode ser encontrado "
"em https://www.gnu.org/copyleft/gpl.html\";>https://www.gnu.org/";
"copyleft/gpl.html e /usr/share/common-licenses/GPL-3."

#. type: Content of: 
#: entries.dbk:34 entries.dbk:368
msgid "APT"
msgstr "APT"

#. type: Content of: 
#: entries.dbk:35
msgid "Debian"
msgstr "Debian"

#. type: Content of: 
#: entries.dbk:36
msgid "dpkg"
msgstr "dpkg"

#. type: Content of: 
#: entries.dbk:37
msgid "reference card"
msgstr "cartão de referência"

#. type: Content of: 
#: entries.dbk:38
msgid "basic commands"
msgstr "comandos básicos"

#. type: Content of: 
#: entries.dbk:39
msgid "Version"
msgstr "Versão"

#. type: Content of: 
#: entries.dbk:40
msgid "Made by"
msgstr "Feito por"

#. type: Content of: 
#: entries.dbk:44
msgid "Getting Help"
msgstr "Obter Ajuda"

#. type: Content of: 
#: entries.dbk:47
msgid "man page or man bash"
msgstr "man página ou man bash"

#. type: Content of: 
#: entries.dbk:49
msgid "Read online help for every command and many configuration files."
msgstr ""
"Leia a ajuda online para todos os comandos e muitos ficheiros de "
"configuração."

#. type: Content of: 
#: entries.dbk:53
msgid ""
"command   --"
"help, -h"
msgstr ""
"comando   --"
"help, -h"

#. type: Content of: 
#: entries.dbk:56
msgid "Brief help for most commands."
msgstr "Breve resumo de ajuda para a maioria dos comandos."

#. type: Content of: 
#: entries.dbk:60
msgid ""
"/usr/share/doc/package-name/"
msgstr ""
"/usr/share/doc/  nome-do-pacote/"

#. type: Content of: 
#: entries.dbk:61
msgid ""
"Find all documentation here, optional file README.Debian contains specifics."
msgstr ""
"Aqui encontra toda a documentação, e opcionalmente o ficheiro "
"README.Debian que contém especificidades."

#. type: Content of: 
#: entries.dbk:66
msgid "https://www.debian.org/doc/\";>Web documentation"
msgstr "https://www.debian.org/doc/\";>Web documentation"

#. type: Content of: 
#: entries.dbk:68
msgid ""
"Reference, manuals, FAQs, HOWTOs, etc. at https://www.debian.org/";
"doc/"
msgstr ""
"Referências, manuais, FAQs, HOWTOs, etc. em https://www.debian.org/";
"doc/"

#. type: Content of: 
#: entries.dbk:72
msgid ""
"https://lists.debian.org/\";>Mailing lists at "
"https://lists.debian.org/"
msgstr ""
"https://lists.debian.org/\";>Mailing lists em "
"https://lists.debian.org/"

#. type: Content of: 
#: entries.dbk:75
msgid "The community is always helpful, search for users."
msgstr ""
"A comunidade é sempre uma boa ajuda, procure por users."

#. type: Content of: 
#: entries.dbk:79
msgid ""
"https://wiki.debian.org/\";>The Wiki at https://";
"wiki.debian.org/"
msgstr ""
"https://wiki.debian.org/\";>Wiki em https://";
"wiki.debian.org/"

#. type: Content of: 
#: entries.dbk:81
msgid "Contains all kind of useful information."
msgstr "Contém todo o tipo de informação útil."

#. type: Content of: 
#: entries.dbk:87
msgid "Installation"
msgstr "Instalação"

#. type: Content of: 
#: entries.dbk:90
msgid ""
"https://www.debian.org/devel/debian-installer/\";>Installer"
msgstr ""
"https://www.debian.org/devel/debian-installer/\";>Instalador"

#. type: C

Bug#869150: /usr/bin/uscan: doesn't find the correct version for directory based version detection

2017-07-28 Thread Osamu Aoki
On Fri, Jul 28, 2017 at 11:24:44PM +0900, Osamu Aoki wrote:
> Should be non-greedy match ... not a non-capturing match .. Sigh
> 
> > > m/^.+?[-_]?(\d[\-+\.:\~\da-zA-Z]*)(?:\.tar\.(gz|bz2|xz)|\.zip)$/i;
> > > $newversion = $1;

This worked:

uscan info: newest_dir => '2.4'
uscan info: Requesting URL:
   http://festvox.org/packed/festival/2.4/
uscan info: Matching pattern:
   
(?:(?:http://festvox.org)?\/packed\/festival\/2\.4\/)?festlex_CMU(?i)\.(?:tar\.xz|tar\.bz2|tar\.gz|zip)
uscan info: Found the following matching hrefs on the web page (newest first):
   festlex_CMU.tar.gz () index=-1 
uscan info: Matching target for downloadurlmangle: 
http://festvox.org/packed/festival/2.4/festlex_CMU.tar.gz
uscan info: Upstream URL (downloadurlmangled):
   http://festvox.org/packed/festival/2.4/festlex_CMU.tar.gz
uscan info: Matching target for filenamemangle: 
http://festvox.org/packed/festival/2.4/festlex_CMU.tar.gz
uscan info: Newest upstream tarball version from the filenamemangled filename: 
2.4
uscan info: Download filename (filenamemangled): festvox-rablpc16k_2.4.tar.gz
uscan: Newest version of festvox-rablpc16k on remote site is 2.4, local version 
is 0.0
uscan:=> Newer package available from
  http://festvox.org/packed/festival/2.4/festlex_CMU.tar.gz
uscan info: Downloading upstream package: festvox-rablpc16k_2.4.tar.gz
uscan info: Requesting URL:
   http://festvox.org/packed/festival/2.4/festlex_CMU.tar.gz
uscan info: Successfully downloaded package: festvox-rablpc16k_2.4.tar.gz
uscan info: Start checking for common possible upstream OpenPGP signature files
uscan info: End checking for common possible upstream OpenPGP signature files
uscan info: Missing OpenPGP signature.
uscan info: New orig.tar.* tarball version (oversionmangled): 2.4
uscan info: Executing internal command:
   mk-origtargz --package festvox-rablpc16k --version 2.4 --compression gzip 
--directory .. ../festvox-rablpc16k_2.4.tar.gz
uscan info: New orig.tar.* tarball version (after mk-origtargz): 2.4
uscan info: Successfully symlinked ../festvox-rablpc16k_2.4.tar.gz to 
../festvox-rablpc16k_2.4.orig.tar.gz.
uscan info: Scan finished



Bug#860296: lirc is spamming syslog with messages

2017-07-28 Thread Ayke van Laethem
Package: lirc
Version: 0.9.4c-9
Followup-For: Bug #860296

Dear Maintainer,

I believe this is a real bug. The problem is not that it logs the error
(which it should), the problem is that it *keeps* logging the error
without any form of throttling quickly filling the whole syslog:

$ ls -l /var/log/syslog
-rw-r- 1 root adm 4,2G jul 28 16:33 /var/log/syslog

Sample from syslog:
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Error: uirt2:
reading of byte 0 failed
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Invalid argument
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Error: uirt2:
reading of byte 0 failed
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Invalid argument
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Error: uirt2:
reading of byte 0 failed
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Invalid argument
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Error: uirt2:
reading of byte 0 failed
Jul 28 16:28:41 ayke-desktop lircd-0.9.4c[874]: Invalid argument

This became a problem during the upgrade from jessie to stretch. During
a large part of the upgrade my whole root disk was filled with useless
log messages (0 bytes free storage), so I'm actually surprised it
finished upgrading without issues. Upgrading is a critical operation so
I would consider this an important bug.

The configuration files attached here *should* be enough to reproduce
the issue. I am willing to provide the original configuration files that
I used.

In my opinion, lirc should be fixed to not retry this often or fail the
first time - there's no use in retrying with an invalid configuration.

A workaround is disabling lirc in stretch:

systemctl disable lirc


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

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

Versions of packages lirc depends on:
ii  init-system-helpers  1.48
ii  libasound2   1.1.3-5
ii  libc62.24-11+deb9u1
ii  libftdi1-2   1.3-2+b2
ii  libgcc1  1:6.3.0-18
ii  liblirc-client0  0.9.4c-9
ii  liblirc0 0.9.4c-9
ii  libportaudio219.6.0-1
ii  libstdc++6   6.3.0-18
ii  libsystemd0  232-25+deb9u1
ii  libudev1 232-25+deb9u1
ii  libusb-0.1-4 2:0.1.12-30
ii  libusb-1.0-0 2:1.0.21-1
ii  lsb-base 9.20161125
ii  python3  3.5.3-1

Versions of packages lirc recommends:
pn  gir1.2-vte
ii  python3-gi3.22.0-2
ii  python3-yaml  3.12-1

Versions of packages lirc suggests:
pn  ir-keytable  
pn  lirc-compat-remotes  
pn  lirc-doc 
pn  lirc-drv-irman   
pn  lirc-x   
pn  setserial

-- Configuration Files:
/etc/lirc/hardware.conf changed:
LIRCD_ARGS=""
LOAD_MODULES=false
DRIVER="uirt2"
DEVICE="/dev/ttyACM0"
MODULES=""
LIRCD_CONF=""
LIRCMD_CONF=""

/etc/lirc/lircd.conf changed:
begin remote
  name  philips
  bits   32
  eps30
  aeps  100
  one 0 0
  zero0 0
  post_data_bits  16
  post_data  0x0
  gap  114685
  toggle_bit_mask 0xF5108D99
  begin codes
  KEY_LEFT 0x97309DDB
  KEY_LEFT 0x6E3215BE
  KEY_RIGHT0x6FA99F00
  KEY_UP   0xA79C13E5
  KEY_DOWN 0xFB6351AD
  KEY_FORWARD  0x2200
  KEY_REWIND   0x1408
  KEY_PLAYPAUSE0x1500
  KEY_MENU 0xFEF2B8BF
  KEY_INFO 0x0F00
  KEY_INFO 0x0F08
  KEY_MUTE 0x0D08
  KEY_VOLUMEUP 0x1000
  KEY_VOLUMEDOWN   0x1108
  end codes
end remote


-- no debconf information



Bug#869994: perl5.26 update: postgresql databases cannot be viewed using browser

2017-07-28 Thread Dominic Hargreaves
Control: retitle -1 sql-ledger: Can't locate bin/mozilla/login.pl in @INC

On Fri, Jul 28, 2017 at 10:37:38AM -0400, gregor herrmann wrote:
> On Fri, 28 Jul 2017 14:45:11 +0100, Neil Redgate wrote:
> 
> Thanks for your detailed bug report!
> 
> > I can no longer access my postgressql database using any web browser for the
> > sql-ledger 3.2.4 package.
> 
> > [Fri Jul 28 13:45:40.995556 2017] [cgi:error] [pid 6345] [client ::1:40496] 
> > End
> > of script output before headers: admin.pl
> > [Fri Jul 28 13:46:12.133989 2017] [cgi:error] [pid 6231] [client ::1:40500]
> > AH01215: Can't locate bin/mozilla/login.pl in @INC (@INC contains: /etc/perl
> > /usr/local/lib/x86_64-linux-gnu/perl/5.26.0 /usr/local/share/perl/5.26.0
> > /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-
> > gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl
> > /usr/lib/x86_64-linux-gnu/perl-base) at /usr/local/sql-ledger/login.pl line
> > 119.: /usr/local/sql-ledger/login.pl
> > [Fri Jul 28 13:46:12.134085 2017] [cgi:error] [pid 6231] [client ::1:40500] 
> > End
> > of script output before headers: login.pl
> 
> I'm afraid there's not much we can do here. /etc/perl/sitecustomize.pl
> was a temporary workaround which is gone for good now.
> 
> It seems that you are using sql-ledger 3.2.4 which is not packaged in
> Debian and installed in /usr/local/sql-ledger, and that this version
> is not updated to work with Perl 5.26. (I had a brief look at 3.2.5
> and it looks like it still does the same "do $file").
> 
> https://metacpan.org/pod/release/XSAWYERX/perl-5.26.0/pod/perldelta.pod#Removal-of-the-current-directory-%28%22.%22%29-from-@INC
> has background information and a couple of suggestions to remedy the
> situation which you can try yourself and/or suggest to the sql-ledger
> upstream authors.
> 
> (Not closing the bug report yet in case the perl maintainers have
> something to add.)

Thanks gregoa for your investigation/response. I can confirm that I don't
think we can do anything here, unfortunately, as (after around a year)
we have indeed removed the workaround to enable potentially unsafe
operation.

I noticed that we do have an sql-ledger package in Debian, but that
hasn't been updated since before the @INC fix was made, so it's quite
likely to also be completely broken there.

The next steps for this bug report are to check whether the sql-ledger
package has the same problem, and if so reassign it. If the answer is
no, then that might at least point the way towards a resolution for the
reporter.

Cheers,
Dominic.



  1   2   3   >