date:20180204

Bug#889521: libmsv FTBFS on mips64el: shared library not built

2018-02-04 Thread Aurelien Jarno

control: retitle -1 Bug#889521: libmsv: missing build-dependency on file
control: tag -1 + patch

On 2018-02-04 08:38, Adrian Bunk wrote:
> Source: libmsv
> Version: 1.1.1-1
> Severity: serious
> 
> https://buildd.debian.org/status/fetch.php?pkg=libmsv=mips64el=1.1.1-1=1517695216=0
> 
> ...
> checking whether to build shared libraries... no
> ...
> mv debian/libmsv1/usr/lib/*.a debian/libmsv-dev/usr/lib
> mv debian/libmsv1/usr/lib/*.so debian/libmsv-dev/usr/lib
> mv: cannot stat 'debian/libmsv1/usr/lib/*.so': No such file or directory
> debian/rules:45: recipe for target 'binary-arch' failed
> make: *** [binary-arch] Error 1

The problem comes from the following lines at the beginning of the build
log when running the configure script:

| checking how to truncate binary pipes... /bin/dd bs=4096 count=1
| ./configure: line 6508: /usr/bin/file: No such file or directory
| ./configure: line 6516: /usr/bin/file: No such file or directory
| ./configure: line 6524: /usr/bin/file: No such file or directory
| checking for mt... no

The new upstream version has an updated libtool, which requires
/usr/bin/file on mips64el.

Note that file is also missing on other architectures, though the build
succeed. For example on amd64:

| checking how to truncate binary pipes... /bin/dd bs=4096 count=1
| ./configure: line 6548: /usr/bin/file: No such file or directory
| checking for mt... no

The fix for that is to build-depends on file, like done in the attached
patch.

> For some reason it Works for me on eller.

The default chroots on porterboxes have file installed.

Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net
diff -Nru libmsv-1.1.1/debian/control libmsv-1.1.1/debian/control
--- libmsv-1.1.1/debian/control	2018-02-03 21:19:40.0 +0100
+++ libmsv-1.1.1/debian/control	2018-02-04 12:54:28.0 +0100
@@ -1,7 +1,7 @@
 Source: libmsv
 Priority: optional
 Maintainer: Clint Adams 
-Build-Depends: doxygen, libcurl4-nss-dev, libjansson-dev, dpkg (>= 1.19.0.3~)
+Build-Depends: doxygen, libcurl4-nss-dev, libjansson-dev, dpkg (>= 1.19.0.3~), file
 Standards-Version: 4.1.3
 Section: libs
 Homepage: http://floss.scru.org/libmsv/

signature.asc
Description: PGP signature

Bug#889547: dpkg: please add hurd-amd64

2018-02-04 Thread Samuel Thibault

Package: dpkg
Version: 1.19.0.5
Severity: important

Hello,

Talking with aurel32 at FOSDEM about future 64bit support in GNU/Hurd,
he advised me that the hurd-amd64 arch should probably be added in dpkg
already, so that it's available in the archive software etc. on time for
bootstrapping the packages set.

Could you have a look?

Thanks,
Samuel

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

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

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.6-8.1
ii  libc62.26-4
ii  liblzma5 5.2.2-1.3
ii  libselinux1  2.7-2
ii  tar  1.29b-2
ii  zlib1g   1:1.2.8.dfsg-5

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt1.6~alpha7
pn  debsig-verify  

-- no debconf information

-- 
Samuel
AUTHOR
 FvwmM4 is the result of a random  bit  mutation  on  a  hard
 disk,  presumably  a  result  of  a  cosmic-ray or some such
 thing.
(extrait de la page de man de FvwmM4)

Bug#889181: cacti changes for PHP7.2 and dep8 tests

2018-02-04 Thread Paul Gevers

Control: tags -1 confirmed upstream pending

Hi Nishanth,

Thanks for the report and the work with upstream to get this fixed.

On 03-02-18 07:25, Nishanth Aravamudan wrote:
> In Ubuntu, the attached patch was applied to achieve the following:
> 
>   * debian/patches/php72_count_bc_changes.patch: PHP7.2 has deprecated
> count() of non-Countable objects.
>   * debian/patches/update-cactisql.patch: Update cacti.sql for
> readstring to community change.

I'll most likely just wait for the next upstream release, which I expect
to come soon (they release about every other week).

> Note that even with this change, the DEP8 tests fail on Ubuntu 18.04,
> with:
> 
> Unexpected output in /var/log/cacti/cacti.log:
> 02/02/2018 16:40:07 - AUTOM8 ERROR: The Network ID: 1 is disabled. You must 
> use the 'force' option to force it's execution.
> 
> Which I think might be because we need to pass force to some URL or
> check a network enabled box in the script?

If I understood upstream correctly about this issue, we should just add
the line to the accepted output.

Paul



signature.asc
Description: OpenPGP digital signature

Bug#889550: affiche.app: Missing resources after upgrading

2018-02-04 Thread Yavor Doganov

Package: affiche.app
Version: 0.6.0-9+b1
Severity: important

Starting the application:

2018-02-04 14:23:55.658 Affiche[6261:6261] Bad application class '(null)' 
specified

There is no icon displayed and the note windows are missing the
buttons.  This is because after the upgrade
/usr/lib/GNUstep/Applications/Affiche.app/Resources is an empty
directory.

Note that dpkg will not replace a real directory with a symlink and
vice-versa.  You need to use dpkg-maintscript-helper for that.

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

Kernel: Linux 4.14.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=bg_BG.utf8, LC_CTYPE=bg_BG.utf8 (charmap=UTF-8), 
LANGUAGE=bg_BG.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages affiche.app depends on:
ii  gnustep-back0.26   0.26.2-2
ii  gnustep-base-runtime   1.25.1-1
ii  gnustep-common [gnustep-fslayout-fhs]  2.7.0-3
ii  gnustep-gui-runtime0.26.2-2
ii  libc6  2.26-6
ii  libgnustep-base1.251.25.1-1
ii  libgnustep-gui0.26 0.26.2-2
ii  libobjc4   7.3.0-1

affiche.app recommends no packages.

affiche.app suggests no packages.

-- no debconf information

Bug#889566: ITP: golang-go4 -- go4 collection of packages

2018-02-04 Thread Michael Stapelberg

Package: wnpp
Severity: wishlist
Owner: Michael Stapelberg 

* Package name: golang-go4
  Version : 0.0~git20180103.fba789b-1
  Upstream Author : go4 authors
* URL : https://github.com/camlistore/go4
* License : Apache-2.0
  Programming Lang: Go
  Description : go4 collection of packages
 go4 is a collection of packages for Go programmers, which started out in
 Camlistore but have nothing to do with it anymore.

This is a dependency of golang-github-opencontainers-image-spec and 
golang-github-appc-spec.

Bug#887586: node-chokidar: build hangs with mocha 4.0.1-3

2018-02-04 Thread Adrian Bunk

Control: reassign -1 mocha 4.0.1-3
Control: retitle -1 mocha 4.0.1-3 causes build hangs in various build-rdeps
Control: affects -1 src:node-chokidar src:node-errorhandler 
src:node-compression src:node-connect src:node-connect-timeout 
src:node-cookie-parser src:node-on-finished src:node-vhost src:node-webpack

On Thu, Jan 18, 2018 at 09:59:11AM +0200, Adrian Bunk wrote:
> Source: node-chokidar
> Version: 1.7.0-1
> Severity: serious
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-chokidar.html
> 
> ...
>debian/rules override_dh_auto_test
> make[1]: Entering directory '/build/1st/node-chokidar-1.7.0'
> mocha -R spec
>...
> Wed Jan  3 16:30:12 UTC 2018 - pbuilder was killed by timeout after 18h.
> Wed Jan  3 16:30:14 UTC 2018  I: 
> https://tests.reproducible-builds.org/debian/unstable/amd64/node-chokidar : 
> reproducible ➤ FTBFS
> Wed Jan  3 16:30:16 UTC 2018 - total duration: 18h 0m 31s.

This is actually an issue that seems to affect more build-rdeps of mocha
(build logs are in the reproducible builds of the affected packages).

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#889006: dh-autoreconf is run before patching

2018-02-04 Thread Gergely Nagy

Sorry for the brevity, I'm a tad short on time right now: yeah, I'm ok
with a 0-day NMU of dpatch, that tweaks the sequence, and includes the
patch for #868978 as well.

Thanks!

-- 
|8]

Bug#889538: extended description outdated, should mention GtkBuilder instead of libglade

2018-02-04 Thread Sébastien Villemot

Package: glade
Version: 3.20.2-1
Severity: minor

Dear Maintainers,

The extended description of glade is outdated. It says:

“You will probably want to use it with tools such as libglade, which can load
 the XML files and create the interfaces at runtime.”

Since libglade is now deprecated and superseded by GtkBuilder in GTK+ 3, the
extended description should be updated.

Best,

-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  http://sebastien.villemot.name
⠈⠳⣄  http://www.debian.org


signature.asc
Description: PGP signature

Bug#889043: openmsx uses deprecated Tcl 8.5

2018-02-04 Thread Dr. Bas Wijnen

Hi Sergei,

Thanks for the report!

On Thu, Feb 01, 2018 at 03:19:51PM +0300, Sergei Golovan wrote:
> Since Tcl 8.5 has reached its end-of-life it is to be removed from Debian. So
> please, switch the openmsx package to a modern Tcl version.

That seems like a simple change.  I take it Tcl does not have compatibility
problems between versions?  Or is there anything I need to test to see if
things work properly?

There is another change I want to upload anyway, so I'll include this with it.
Thanks for the patch though.

Thanks,
Bas

signature.asc
Description: PGP signature

Bug#889543: CMake Error: The following variables are used in this project, but they are set to NOTFOUND.

2018-02-04 Thread Ondřej Surý

Hi Jean-Christophe,

what is your build environment?

Is liblz4-dev installed?

Cheers,
--
Ondřej Surý
ond...@sury.org



> On 4 Feb 2018, at 11:45, jean-christophe manciot  
> wrote:
> 
> Package: mariadb-10.1
> Version: 1:10.1.29-6
> 
> Building with:
> debuild -i -I --no-sign --build=binary
> 
> leads to:
> ...
> -- Looking for event.h
> -- Looking for event.h - found
> CMake Deprecation Warning at cmake/for_clients.cmake:15 (CMAKE_POLICY):
>   The OLD behavior for policy CMP0007 will be removed from a future version
>   of CMake.
> 
>   The cmake-policies(7) manual explains that the OLD behaviors of all
>   policies are deprecated and that a policy should be set to OLD only under
>   specific short-term circumstances.  Projects should be ported to the NEW
>   behavior and not rely on setting a policy to OLD.
> Call Stack (most recent call first):
>   CMakeLists.txt:422 (INCLUDE)
> 
> 
> CMake Error: The following variables are used in this project, but they are 
> set to NOTFOUND.
> Please set them or make sure they are set and tested correctly in the CMake 
> files:
> LZ4_LIBS
> linked by target "libgroonga" in directory 
> /home/actionmystique/src/MariaDB/mariadb-10.1-10.1.29-6/storage/mroonga/vendor/groonga/lib
> 
> -- Configuring incomplete, errors occurred!
> See also 
> "/home/actionmystique/src/MariaDB/mariadb-10.1-10.1.29-6/builddir/CMakeFiles/CMakeOutput.log".
> See also 
> "/home/actionmystique/src/MariaDB/mariadb-10.1-10.1.29-6/builddir/CMakeFiles/CMakeError.log".
> 
> The following files are attached:
> - full build log
> - CMakeOutput.log
> - CMakeError.log
> 
> -- 
> Jean-Christophe Manciot
>

Bug#889542: wmbattery ate my 4GByte ram on T400 WITH docking station

2018-02-04 Thread Andreas Metzler

Control: forcemerge 816872 889542

On 2018-02-04 Michelle Konzack  wrote:
> Package: wmbattery
> Version: 2.50-1+b1
> Release: Stretch

> Hello Maintainers,

> I have a Lenovo ThinkPad T400 with 4 GByte of memory, installed Stretch
> and have 4 GByte of swap.
[...]
> However, I just discovered with htop, that it is wmbattery which
> used more then 3 GByte of memory and Linux started kicking other
> applications.

> Unfortunately I have currently no screenshot of the huge memory
> consumption but I will send you with this Bugreport the current htop
> screenshoot and tomorrow the second one (If my system does not
> unexpected reboot which happen since Stretch a couple of times)

Looks like a duplicate of 816872. Closing.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#889483: libegl1 disables amdgpu drm with Buster mesa

2018-02-04 Thread fin4478 fin4478

Reopen this bug, the log file shows that this bug is for Debian Buster
Mesa.

Bug#889554: RFP: gnome-shell-extension-backslide -- wallpaper slideshow extension for GNOME Shell

2018-02-04 Thread Ghislain Antony Vaillant

Package: wnpp
Severity: wishlist

* Package name: gnome-shell-extension-backslide
  Version : 1.4.4
  Upstream Author : Lukas Knuth
* URL : https://extensions.gnome.org/extension/543/backslide/
* License : GPL-3+
  Programming Lang: Javascript
  Description : wallpaper slideshow extension for GNOME Shell

Long-Description:
 A simple Gnome-Shell Extension for setting up an automatic
 background-image (wallpaper) slideshow.

Bug#889562: gcompris: missing L10n in gcompris-edit desktop file

2018-02-04 Thread Ronny Standtke

Package: gcompris
Version: 15.10-1+b1
Severity: minor
Tags: patch, l10n

The gcompris-edit desktop file is missing a German translation for the
GenericName entry. This is user visible e.g. in the KDE Plasma desktop start
menu. The attached patch fixes this issue.

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

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

Versions of packages gcompris depends on:
ii  gcompris-data   15.10-1
ii  gstreamer1.0-alsa [gstreamer1.0-audiosink]  1.10.4-1
ii  gstreamer1.0-plugins-bad [gstreamer1.0-audiosink]   1.10.4-1
ii  gstreamer1.0-plugins-base   1.10.4-1
ii  gstreamer1.0-plugins-good [gstreamer1.0-audiosink]  1.10.4-1
ii  gstreamer1.0-pulseaudio [gstreamer1.0-audiosink]    1.10.4-1
ii  libatk1.0-0 2.22.0-1
ii  libc6   2.24-11+deb9u1
ii  libcairo2   1.14.8-1
ii  libfontconfig1  2.11.0-6.7+b1
ii  libfreetype6    2.6.3-3.2
ii  libgdk-pixbuf2.0-0  2.36.5-2+deb9u2
ii  libglib2.0-0    2.50.3-2
ii  libgstreamer1.0-0   1.10.4-1
ii  libgtk2.0-0 2.24.31-2
ii  libpango-1.0-0  1.40.5-1
ii  libpangocairo-1.0-0 1.40.5-1
ii  libpangoft2-1.0-0   1.40.5-1
ii  libpython2.7    2.7.13-2+deb9u2
ii  librsvg2-2  2.40.16-1+b1
ii  librsvg2-common 2.40.16-1+b1
ii  libsqlite3-0    3.16.2-5+deb9u1
ii  libx11-6    2:1.6.4-3
ii  libxml2
2.9.4+dfsg1-2.2+deb9u2
ii  python-cairo    1.8.8-2.2
ii  python-gtk2 2.24.0-5.1
ii  python-pysqlite2    2.7.0-1

gcompris recommends no packages.

Versions of packages gcompris suggests:
ii  gnucap    1:0.36~20091207-2+b3
ii  tuxpaint  1:0.9.22-3

-- no debconf information

--- gcompris-edit.desktop.orig	2018-02-04 15:42:31.466945000 +0100
+++ gcompris-edit.desktop	2018-02-04 15:42:03.538945000 +0100
@@ -49,6 +49,7 @@
 Name[zu]=Abaphathi be-GCompris
 GenericName=Administration interface for educational game
 GenericName[cs]=SprÃ¡vcovskÃ© rozhranÃ pro vÃ½ukovou hru
+GenericName[de]=Verwaltungsschnittstelle fÃ¼r Lernspiel
 GenericName[es]=Interfaz de administraciÃ³n para juegos educativos
 GenericName[hu]=AdminisztrÃ¡ciÃ³s felÃ¼let az oktatÃ³jÃ¡tÃ©khoz
 GenericName[lt]=Administravimo sÄsaja mokomajam Å¾aidimui

Bug#888627: Acknowledgement (m instruction in score partition cause segfault)

2018-02-04 Thread Mickael Viey


Hello,


I tried to build csound 6.11. This version is built perfecly on my 
system. And fixes this bug.



Is there any reason the 6.11 is not available in officials repositories ?


Best,

Mik


Le 28/01/2018 à 02:09, Debian Bug Tracking System a écrit :

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 888627: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888627.

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

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

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


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

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

Bug#889564: xrandr lists modes that it then cannot find

2018-02-04 Thread 積丹尼 Dan Jacobson

Package: libxrandr2
Version: 2:1.5.1-1
X-Debbugs-Cc: Cyril Brulebois 

Maybe libxrandr2 is the right place for me to report
#882444 (xrandr lists modes that it then cannot find). I'm not sure.

Bug#888630: Acknowledgement (r instruction in score partition doesn't work as expected)

2018-02-04 Thread Mickael Viey


Hello,


I tried to build csound 6.11. This version is built perfecly on my 
system. And fixes this bug.



Is there any reason the 6.11 is not available in officials repositories ?


Best,

Mik


Le 28/01/2018 à 02:21, Debian Bug Tracking System a écrit :

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 888630: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888630.

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

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

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


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

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

Bug#889563: linphone: Wrong contact list sort order

2018-02-04 Thread Rob van der Putten

Package: linphone
Version: 3.6.1-3
Severity: normal

Dear Maintainer,


Linphone sorts contacts by username (EG: ) as
opposed to display_name (EG: "John Doe"). Below a small patch by a friend
which fixes this problem;


--- friendlist.c.bak2013-05-15 13:02:23.606072868 +0200
+++ friendlist.c2018-02-03 19:54:22.712164226 +0100
@@ -588,8 +588,15 @@
const LinphoneAddress *addr1,*addr2;
addr1=linphone_friend_get_address(lf1);
addr2=linphone_friend_get_address(lf2);
-   u1=linphone_address_get_username(addr1);
-   u2=linphone_address_get_username(addr2);
+   /*Fix by Simon IJskes*/
+   u1=linphone_address_get_display_name(addr1);
+   if (u1 == NULL) {
+   u1=linphone_address_get_username(addr1);
+   }
+   u2=linphone_address_get_display_name(addr2);
+   if (u2 == NULL) {
+   u2=linphone_address_get_username(addr2);
+   }
if (u1 && u2) return strcasecmp(u1,u2);
if (u1) return 1;
else return -1;
@@ -1077,4 +1084,4 @@
 void linphone_gtk_buddy_info_updated(LinphoneCore *lc, LinphoneFriend *lf){
/*refresh the entire list*/
linphone_gtk_show_friends();
-}
\ No newline at end of file
+}


It's not known if the tests u1 == NULL and u2 == NULL are really
necessary, but it can't hurt.


Rgards,
Rob

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

Kernel: Linux 4.9.0-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages linphone depends on:
ii  libasound21.1.3-5
ii  libatk1.0-0   2.22.0-1
ii  libavcodec57  7:3.2.10-1~deb9u1
ii  libavutil55   7:3.2.10-1~deb9u1
ii  libc6 2.24-11+deb9u1
ii  libcairo2 1.14.8-1
ii  libexosip2-11 4.1.0-2.1
ii  libfontconfig12.11.0-6.7+b1
ii  libfreetype6  2.6.3-3.2
ii  libgdk-pixbuf2.0-02.36.5-2+deb9u2
ii  libgl1-mesa-glx [libgl1]  13.0.6-1+b2
ii  libglew2.02.0.0-3+b1
ii  libglib2.0-0  2.50.3-2
ii  libglu1-mesa [libglu1]9.0.0-2.1
ii  libgtk2.0-0   2.24.31-2
ii  liblinphone5  3.6.1-3
ii  libmediastreamer-base33.6.1-3
ii  libnotify40.7.7-2
ii  libogg0   1.3.2-1
ii  libopus0  1.2~alpha2-1
ii  libortp9  3.6.1-3
ii  libosip2-11   4.1.0-2.1
ii  libpango-1.0-01.40.5-1
ii  libpangocairo-1.0-0   1.40.5-1
ii  libpangoft2-1.0-0 1.40.5-1
ii  libpulse0 10.0-1+deb9u1
ii  libsoup2.4-1  2.56.0-2+deb9u1
ii  libspandsp2   0.0.6+dfsg-0.1
ii  libspeex1 1.2~rc1.2-1+b2
ii  libspeexdsp1  1.2~rc1.2-1+b2
ii  libsqlite3-0  3.16.2-5+deb9u1
ii  libswscale4   7:3.2.10-1~deb9u1
ii  libtheora01.1.1+dfsg.1-14+b1
ii  libudev1  232-25+deb9u1
ii  libupnp6  1:1.6.19+git20160116-1.2
ii  libv4l-0  1.12.3-1
ii  libvpx4   1.6.1-3
ii  libx11-6  2:1.6.4-3
ii  libxv12:1.0.11-1
ii  linphone-nogtk3.6.1-3

linphone recommends no packages.

Versions of packages linphone suggests:
ii  yelp  3.22.0-1

-- no debconf information

Bug#889565: libical3: please make the build reproducible

2018-02-04 Thread Chris Lamb

forwarded 889565 https://github.com/libical/libical/pull/324
thanks

I've forwarded this upstream here:

  https://github.com/libical/libical/pull/324


Regards,

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

Bug#889006: dh-autoreconf is run before patching

2018-02-04 Thread Niels Thykier

Gergely Nagy:
> Sorry for the brevity, I'm a tad short on time right now: yeah, I'm ok
> with a 0-day NMU of dpatch, that tweaks the sequence, and includes the
> patch for #868978 as well.
> 
> Thanks!
> 

Thanks, I have uploaded dpatch/2.0.38+nmu1 with the attached changes. :)

Apologies for the noise from a "2.0.37+nmu1" upload; I was basing it off
git and did not notice that git was out of date for the upload.

Thanks,
~Niels
diff -Nru dpatch-2.0.38/debhelper/dpatch.pm 
dpatch-2.0.38+nmu1/debhelper/dpatch.pm
--- dpatch-2.0.38/debhelper/dpatch.pm   2015-11-30 11:34:18.0 +0100
+++ dpatch-2.0.38+nmu1/debhelper/dpatch.pm  2018-02-04 16:23:16.0 
+0100
@@ -3,7 +3,7 @@
 use strict;
 use Debian::Debhelper::Dh_Lib;
 
-insert_before("dh_auto_configure", "dh_dpatch_patch");
+insert_before("dh_update_autotools_config", "dh_dpatch_patch");
 insert_before("dh_clean", "dh_dpatch_unpatch");
 
 # Eval to avoid problem with debhelper < 7.3.12
diff -Nru dpatch-2.0.38/debian/changelog dpatch-2.0.38+nmu1/debian/changelog
--- dpatch-2.0.38/debian/changelog  2015-11-30 12:19:57.0 +0100
+++ dpatch-2.0.38+nmu1/debian/changelog 2018-02-04 16:23:16.0 +0100
@@ -1,3 +1,15 @@
+dpatch (2.0.38+nmu1) unstable; urgency=medium
+
+  * Non-maintainer upload.  Uploaded without delay with
+maintainer's permission  (#889006 comment 44).
+  * Apply patch from Sven Joachim to FTBFS if awk is provided
+by original-awk rather than mawk.  (Closes: #868978)
+  * Run dh_dpatch_patch before dh_update_autotools_config rather
+than before dh_auto_configure to ensure patching happens
+before autotools "retooling".  (Closes: #889006)
+
+ -- Niels Thykier   Sun, 04 Feb 2018 15:23:16 +
+
 dpatch (2.0.38) unstable; urgency=medium
 
   * Don't just install bash completion to a new place, remove the old files
diff -Nru dpatch-2.0.38/tools/shpp.awk dpatch-2.0.38+nmu1/tools/shpp.awk
--- dpatch-2.0.38/tools/shpp.awk2015-11-30 11:34:18.0 +0100
+++ dpatch-2.0.38+nmu1/tools/shpp.awk   2018-02-04 16:23:16.0 +0100
@@ -1,4 +1,4 @@
-#!/usr/bin/nawk -f
+#!/usr/bin/awk -f
 # shpp.awk -- Simple preprocessor for shell scripts
 #
 #  Copyright (C) 2003  Miles Bader 


signature.asc
Description: OpenPGP digital signature

Bug#889528: mpv: Reading bluray using mpv fails

2018-02-04 Thread James Cowgill

Hi,

On 04/02/18 09:38, mahashakti89 wrote:
> Package: mpv
> Version: 0.27.0-3
> Severity: important
> 
> Dear Maintainer,
> 
> I am using smplayer to read blurays - choosen multimedia engine is mpv - but 
> it
> fails with following message :
> 
> Playing: br:media/toto/cdrom0
> No protocol handler found to open URL br:media/toto/cdrom0
> The protocol is either unsupported, or was disabled at compile-time.

mpv uses a slightly different "bd" protocol instead of "br". Try this:
 mpv br:// --bluray-device=/media/toto/cdrom0

See the mpv manual page.

Unfortunately I do not have a bluray reader do I can't test this.

James



signature.asc
Description: OpenPGP digital signature

Bug#889528: mpv: Reading bluray using mpv fails

2018-02-04 Thread James Cowgill

On 04/02/18 16:46, James Cowgill wrote:
> Hi,
> 
> On 04/02/18 09:38, mahashakti89 wrote:
>> Package: mpv
>> Version: 0.27.0-3
>> Severity: important
>>
>> Dear Maintainer,
>>
>> I am using smplayer to read blurays - choosen multimedia engine is mpv - but 
>> it
>> fails with following message :
>>
>> Playing: br:media/toto/cdrom0
>> No protocol handler found to open URL br:media/toto/cdrom0
>> The protocol is either unsupported, or was disabled at compile-time.
> 
> mpv uses a slightly different "bd" protocol instead of "br". Try this:
>  mpv br:// --bluray-device=/media/toto/cdrom0

Err this of course should be:
 mpv bd:// --bluray-device=/media/toto/cdrom0

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#878757: Ping! autoremovals need help

2018-02-04 Thread debian

This bug needs a modification so autoremovals/testing migrations can
work. Thanks, nthykier!

Thanks, BTS.

Chris.

Bug#858930: Ping! Trying to help openvswitch

2018-02-04 Thread debian

openvswitch, the only rdep of this package, has been fixed to not depend
on it. This bug needs pinging to help it migrating (thanks, nthykier!).

Hopefully this bug will eventually be fixed by RM.

Cheers,
Chris.

Bug#872773: ITP: firefox-passff -- pass manager extension for Firefox

2018-02-04 Thread Michael Meskes

On Mon, Aug 21, 2017 at 09:46:33PM +0800, Yao Wei wrote:
> I later found out that the package is not ready for Chromium yet, but
> anyways I started the thread in debian-devel and pkg-mozext-maintainers
> now.
> 
> Also found out that the package ublock-origin has been maintained by
> pkg-mozext team for both xul-ext and chromium addons.

Where do we stand with this effort. I'd love to see passff in Debian. As an
alternative browserpass seems to work with both, Firefox and Chrome.

Michael

-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL


signature.asc
Description: PGP signature

Bug#889535: lintian: Can't use an undefined value as an ARRAY reference at /srv/lintian.debian.org/lintian/lib/Lintian/Path.pm line 326.

2018-02-04 Thread Chris Lamb

tags 889535 + pending
thanks

Thanks! Fixed in Git, pending upload:

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


Regards,

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

Bug#889527: puppet: Puppet master/agent on testing/buster fails with SSL errors

2018-02-04 Thread Clayton

Attached is the debug output that goes along with those SSL errors.
[0;36mDebug: Applying settings catalog for sections main, agent, ssl[0m
[0;36mDebug: Caching environment 'production' (ttl = 0 sec)[0m
[0;36mDebug: Evicting cache entry for environment 'production'[0m
[0;36mDebug: Caching environment 'production' (ttl = 0 sec)[0m
[0;36mDebug: Evicting cache entry for environment 'production'[0m
[0;36mDebug: Caching environment 'production' (ttl = 0 sec)[0m
[0;36mDebug: Evicting cache entry for environment 'production'[0m
[0;36mDebug: Caching environment 'production' (ttl = 0 sec)[0m
[0;36mDebug: Using settings: adding file resource 'confdir': 
'File[/etc/puppet]{:path=>"/etc/puppet", :ensure=>:directory, 
:loglevel=>:debug, :links=>:follow, :backup=>false}'[0m
[0;36mDebug: Using settings: adding file resource 'codedir': 
'File[/etc/puppet/code]{:path=>"/etc/puppet/code", :ensure=>:directory, 
:loglevel=>:debug, :links=>:follow, :backup=>false}'[0m
[0;36mDebug: Evicting cache entry for environment 'production'[0m
[0;36mDebug: Caching environment 'production' (ttl = 0 sec)[0m
[0;36mDebug: Failed to load library 'cfpropertylist' for feature 
'cfpropertylist'[0m
[0;36mDebug: Evicting cache entry for environment 'production'[0m
[0;36mDebug: Caching environment 'production' (ttl = 0 sec)[0m
[0;36mDebug: Evicting cache entry for environment 'production'[0m
[0;36mDebug: Caching environment 'production' (ttl = 0 sec)[0m
[0;36mDebug: Puppet::Type::User::ProviderDirectoryservice: file 
/usr/bin/uuidgen does not exist[0m
[0;36mDebug: Failed to load library 'ldap' for feature 'ldap'[0m
[0;36mDebug: Puppet::Type::User::ProviderLdap: feature ldap is missing[0m
[0;36mDebug: Puppet::Type::User::ProviderPw: file pw does not exist[0m
[0;36mDebug: Puppet::Type::User::ProviderUser_role_add: file roleadd does not 
exist[0m
[0;36mDebug: /User[puppet]: Provider useradd does not support features 
libuser; not managing attribute forcelocal[0m
[0;36mDebug: Failed to load library 'cfpropertylist' for feature 
'cfpropertylist'[0m
[0;36mDebug: Puppet::Type::Group::ProviderDirectoryservice: file /usr/bin/dscl 
does not exist[0m
[0;36mDebug: Failed to load library 'ldap' for feature 'ldap'[0m
[0;36mDebug: Puppet::Type::Group::ProviderLdap: feature ldap is missing[0m
[0;36mDebug: Puppet::Type::Group::ProviderPw: file pw does not exist[0m
[0;36mDebug: /Group[puppet]: Provider groupadd does not support features 
libuser; not managing attribute forcelocal[0m
[0;36mDebug: Using settings: adding file resource 'vardir': 
'File[/var/cache/puppet]{:path=>"/var/cache/puppet", :owner=>"puppet", 
:group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, 
:backup=>false}'[0m
[0;36mDebug: Using settings: adding file resource 'logdir': 
'File[/var/log/puppet]{:path=>"/var/log/puppet", :mode=>"750", 
:owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'[0m
[0;36mDebug: Using settings: adding file resource 'statedir': 
'File[/var/cache/puppet/state]{:path=>"/var/cache/puppet/state", :mode=>"1755", 
:ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'[0m
[0;36mDebug: Using settings: adding file resource 'rundir': 
'File[/run/puppet]{:path=>"/run/puppet", :mode=>"755", :owner=>"puppet", 
:group=>"puppet", :ensure=>:directory, :loglevel=>:debug, :links=>:follow, 
:backup=>false}'[0m
[0;36mDebug: Using settings: adding file resource 'libdir': 
'File[/var/cache/puppet/lib]{:path=>"/var/cache/puppet/lib", 
:ensure=>:directory, :loglevel=>:debug, :links=>:follow, :backup=>false}'[0m
[0;36mDebug: Using settings: adding file resource 'hiera_config': 
'File[/etc/puppet/hiera.yaml]{:path=>"/etc/puppet/hiera.yaml", :ensure=>:file, 
:loglevel=>:debug, :links=>:follow, :backup=>false}'[0m
[0;36mDebug: Using settings: adding file resource 'preview_outputdir': 
'File[/var/cache/puppet/preview]{:path=>"/var/cache/puppet/preview", 
:mode=>"750", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, 
:loglevel=>:debug, :links=>:follow, :backup=>false}'[0m
[0;36mDebug: Using settings: adding file resource 'certdir': 
'File[/var/lib/puppet/ssl/certs]{:path=>"/var/lib/puppet/ssl/certs", 
:mode=>"755", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, 
:loglevel=>:debug, :links=>:follow, :backup=>false}'[0m
[0;36mDebug: Using settings: adding file resource 'ssldir': 
'File[/var/lib/puppet/ssl]{:path=>"/var/lib/puppet/ssl", :mode=>"771", 
:owner=>"puppet", :group=>"puppet", :ensure=>:directory, :loglevel=>:debug, 
:links=>:follow, :backup=>false}'[0m
[0;36mDebug: Using settings: adding file resource 'publickeydir': 
'File[/var/lib/puppet/ssl/public_keys]{:path=>"/var/lib/puppet/ssl/public_keys",
 :mode=>"755", :owner=>"puppet", :group=>"puppet", :ensure=>:directory, 
:loglevel=>:debug, :links=>:follow, :backup=>false}'[0m
[0;36mDebug: Using settings: adding file resource 'requestdir':

Bug#889552: needrestart: add support for ignoring young processes under a configurable age

2018-02-04 Thread Paul Wise

Package: needrestart
Version: 2.11-4
Severity: wishlist

The Debian sysadmins recently added to dsa-check-libs (a needrestart
equivalent) support for ignoring young processes under a configurable
age. This was added to make the system ignore all processes within
piuparts chroots, which are constantly being upgraded and thus usually
have processes that have had files upgraded. It occurred to me this
could be a useful feature for needrestart since there are probably
similar situations where young processes are soon likely to be
restarted or terminate anyway.

https://salsa.debian.org/dsa-team/mirror/dsa-nagios/commit/eacadbfdc7c120280a8a0192aa2e44ef3e649305
https://salsa.debian.org/dsa-team/mirror/dsa-nagios/commit/8fc6ab7d7dd452c12e8d1d7e153c4eba3d9975ae

-- 
bye,
pabs

https://wiki.debian.org/PaulWise


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

Bug#889561: Mention what to do when xrandr lists modes that it then cannot find

2018-02-04 Thread 積丹尼 Dan Jacobson

Package: xserver-xorg
Version: 1:7.7+19
Severity: wishlist
File: /usr/share/doc/xorg/howto/use-xrandr.txt.gz
X-Debbugs-Cc: Cyril Brulebois 

/usr/share/doc/xorg/howto/use-xrandr.txt.gz should discuss the proper
thing to do when #882444 (xrandr lists modes that it then cannot find) happens.

Bug#889565: libical3: please make the build reproducible

2018-02-04 Thread Chris Lamb

Source: libical3
Version: 3.0.1-5
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness fileordering
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort [0], we noticed
that libical3 could not be built reproducibly.

Patch attached.

 [0] https://reproducible-builds.org/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- a/debian/patches/0002-reproducible-build.patch  1970-01-01 
01:00:00.0 +0100
--- b/debian/patches/0002-reproducible-build.patch  2018-02-04 
14:23:38.286140899 +
@@ -0,0 +1,63 @@
+Description: Make the build reproducible
+Author: Chris Lamb 
+Last-Update: 2018-02-04
+
+--- libical3-3.0.1.orig/src/libical-glib/tools/generator.c
 libical3-3.0.1/src/libical-glib/tools/generator.c
+@@ -1096,6 +1096,7 @@ void generate_forward_declarations_heade
+ gchar *typeName;
+ gchar *typeKind;
+ GList *link;
++GList *typeNamesList = NULL;
+ GHashTable *typeNames;
+ GHashTableIter iter_table;
+ gpointer key;
+@@ -1156,13 +1157,18 @@ void generate_forward_declarations_heade
+ if (g_strcmp0(buffer, "forward_declarations") == 0) {
+ g_hash_table_iter_init(_table, typeNames);
+ while (g_hash_table_iter_next(_table, , )) {
+-typeName = (gchar *)key;
++typeNamesList = g_list_prepend(typeNamesList, 
g_strdup(key));
++}
++typeNamesList = g_list_sort(typeNamesList, 
(GCompareFunc)g_strcmp0);
++for (link = g_list_first(typeNamesList); link != NULL; link = 
g_list_next(link)) {
++typeName = link->data;
+ write_str(out, "typedef struct _");
+ write_str(out, typeName);
+ write_str(out, " ");
+ write_str(out, typeName);
+ write_str(out, ";\n");
+ }
++g_list_free_full(typeNamesList, g_free);
+ } else if (g_strcmp0(buffer, "upperSnake") == 0) {
+ write_str(out, "I_CAL_FORWARD_DECLARATIONS");
+ } else {
+@@ -2156,6 +2162,8 @@ static gint generate_library(const gchar
+ gchar *buffer;
+ GList *structures;
+ GList *iter_list;
++GList *filenames;
++GList *iter_filenames;
+ GDir *dir;
+ GError *local_error = NULL;
+ gint res = 0;
+@@ -2186,6 +2194,11 @@ static gint generate_library(const gchar
+ 
+ /* Parse the all the XML files into the Structure */
+ while (filename = g_dir_read_name(dir), filename) {
++filenames = g_list_prepend(filenames, g_strdup(filename));
++}
++filenames = g_list_sort(filenames, (GCompareFunc)g_strcmp0);
++for (iter_filenames = g_list_first(filenames); iter_filenames != NULL; 
iter_filenames = g_list_next(iter_filenames)) {
++filename = iter_filenames->data;
+ gint len = (gint)strlen(filename);
+ 
+ if (len <= 4 || g_ascii_strncasecmp(filename + len - 4, ".xml", 4) != 
0)
+@@ -2280,6 +2293,7 @@ static gint generate_library(const gchar
+ g_hash_table_destroy(type2structure);
+ g_hash_table_destroy(defaultValues);
+ g_list_free_full(structures, (GDestroyNotify)structure_free);
++g_list_free_full(filenames, g_free);
+ g_free(buffer);
+ 
+ return res;
--- a/debian/patches/series 2018-02-04 13:36:45.872268239 +
--- b/debian/patches/series 2018-02-04 13:57:47.788970001 +
@@ -1 +1,2 @@
 0001-reproducible-build.patch
+0002-reproducible-build.patch

Bug#889489: lintian: improve description of maintainer-script-should-not-use-recursive-chown-or-chmod

2018-02-04 Thread Chris Lamb

tags 889489 + pending
thanks

Applied in Git with a few changes. Many many thanks :)

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


Regards,

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

Bug#889539: pandas FTBFS: test failures

2018-02-04 Thread Adrian Bunk

Source: pandas
Version: 0.20.3-11
Severity: serious

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

...
=== FAILURES ===
 TestDataFramePlots.test_boxplot_legacy 

self = 

@slow
def test_boxplot_legacy(self):
df = DataFrame(randn(6, 4),
   index=list(string.ascii_letters[:6]),
   columns=['one', 'two', 'three', 'four'])
df['indic'] = ['foo', 'bar'] * 3
df['indic2'] = ['foo', 'bar', 'foo'] * 2

_check_plot_works(df.boxplot, return_type='dict')
_check_plot_works(df.boxplot, column=[
  'one', 'two'], return_type='dict')
# _check_plot_works adds an ax so catch warning. see GH #13188
with tm.assert_produces_warning(UserWarning):
_check_plot_works(df.boxplot, column=['one', 'two'],
  by='indic')
_check_plot_works(df.boxplot, column='one', by=['indic', 'indic2'])
with tm.assert_produces_warning(UserWarning):
_check_plot_works(df.boxplot, by='indic')
with tm.assert_produces_warning(UserWarning):
>   _check_plot_works(df.boxplot, by=['indic', 'indic2'])

../debian/tmp/usr/lib/python2.7/dist-packages/pandas/tests/plotting/test_boxplot_method.py:57:
 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python2.7/contextlib.py:24: in __exit__
self.gen.next()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

expected_warning = , filter_level = 'always'
clear = None, check_stacklevel = True

@contextmanager
def assert_produces_warning(expected_warning=Warning, filter_level="always",
clear=None, check_stacklevel=True):
"""
Context manager for running code that expects to raise (or not raise)
warnings.  Checks that code raises the expected warning and only the
expected warning. Pass ``False`` or ``None`` to check that it does *not*
raise a warning. Defaults to ``exception.Warning``, baseclass of all
Warnings. (basically a wrapper around ``warnings.catch_warnings``).

>>> import warnings
>>> with assert_produces_warning():
... warnings.warn(UserWarning())
...
>>> with assert_produces_warning(False):
... warnings.warn(RuntimeWarning())
...
Traceback (most recent call last):
...
AssertionError: Caused unexpected warning(s): ['RuntimeWarning'].
>>> with assert_produces_warning(UserWarning):
... warnings.warn(RuntimeWarning())
Traceback (most recent call last):
...
AssertionError: Did not see expected warning of class 'UserWarning'.

..warn:: This is *not* thread-safe.
"""
with warnings.catch_warnings(record=True) as w:

if clear is not None:
# make sure that we are clearning these warnings
# if they have happened before
# to guarantee that we will catch them
if not is_list_like(clear):
clear = [clear]
for m in clear:
try:
m.__warningregistry__.clear()
except:
pass

saw_warning = False
warnings.simplefilter(filter_level)
yield w
extra_warnings = []

for actual_warning in w:
if (expected_warning and issubclass(actual_warning.category,
expected_warning)):
saw_warning = True

if check_stacklevel and issubclass(actual_warning.category,
   (FutureWarning,
DeprecationWarning)):
from inspect import getframeinfo, stack
caller = getframeinfo(stack()[2][0])
msg = ("Warning not set with correct stacklevel. "
   "File where warning is raised: {0} != {1}. "
   "Warning message: {2}".format(
   actual_warning.filename, caller.filename,
   actual_warning.message))
assert actual_warning.filename == caller.filename, msg
else:
extra_warnings.append(actual_warning.category.__name__)
if expected_warning:
assert saw_warning, ("Did not see expected warning of class %r."
 % expected_warning.__name__)
assert not extra_warnings, ("Caused unexpected warning(s): %r."
>

Bug#889540: upgrade-reports: Buster testing update fail

2018-02-04 Thread John Lindholm

Package: upgrade-reports
Severity: important

Dear Maintainer,

Update of system Buster Testing. Reboot.
[OK]Started Update UTMP about System Runlevel Changes...
[OK]Started Update UTMP about System Runlevel Changes.
It hangs.

Solution:
Reboot and login as root
apt --fix-broken install




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

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

Bug#100808: hello 2h

2018-02-04 Thread sanfordgregory

Good day, I have a business proposal for you .For more details get back
via:sanfordgregory2...@hotmail.com

Bug#843837: libxft-dev: Xft/Xft.h header incorrectly includes ft2build.h

2018-02-04 Thread Hugh McMaster

Hi Graham,

Sorry for the delayed reply.

On Wednesday, 31 January 2018 5:23 PM, Graham Inggs wrote:
> I saw this message in bug #887595 [1] and thought it would be relevant here:
>
> On Tue, Jan 23, 2018 at 11:56:38AM +, Hugh McMaster wrote:
>> Also note that the Freetype2 developers no longer recommend using
>> #include 
>> in source files (which was the intent of my patch). The following should be
>> used instead:
>> #include 
>> #include FT_FREETYPE_H
>>
>> Developers would then use either freetype-config or pkg-config to
>> obtain the cflags etc.
>
> Hugh, do you have a reference for the above?

The freetype-2.8 API reference shows this #include usage.  Look at the 
documentation
provided with libfreetype6-dev in 
/usr/share/doc/libfreetype6/documentation.html,
particulary Tutorial #1 and Example #1.

Freetype-2.9 (the most recent upstream version) also has this information.
See [1] for information on freetype2's header inclusion scheme and [2] for the 
tutorial.

[1] https://www.freetype.org/freetype2/docs/reference/ft2-header_inclusion.html
[2] https://www.freetype.org/freetype2/docs/tutorial/step1.html
[3] 
https://anonscm.debian.org/cgit/collab-maint/motif.git/tree/debian/patches/fix_ac_find_xft.patch

Bug#889549: ITP: qpack -- Python3 implementation of the QPack protocol

2018-02-04 Thread Paul Gevers

Package: wnpp
Severity: wishlist
Owner: Paul Gevers 

* Package name: qpack
  Version : 0.0.17
  Upstream Author : Jeroen van der Heijden

* URL : https://github.com/transceptor-technology/qpack
* License : Expat
  Programming Lang: Python
  Description : Python3 implementation of the QPack protocol

 QPack is a fast and efficient serialization format like MessagePack.
 One key difference is flexible map and array support. This enables code
 to write directly to a qpack buffer without knowledge of the size of
 the map or array beforehand.

This package is a dependency of siridb-connector, another ITP of me.

The package will be maintained in the SiriDB team.



signature.asc
Description: OpenPGP digital signature

Bug#889548: ITP: siridb-connector -- Python3 interface for the SiriDB time series database server

2018-02-04 Thread Paul Gevers

Package: wnpp
Severity: wishlist
Owner: Paul Gevers 

* Package name: siridb-connector
  Version : 2.0.5
  Upstream Author : Jeroen van der Heijden

* URL :
   https://github.com/transceptor-technology/siridb-connector
* License : Expat
  Programming Lang: Python
  Description : Python3 interface for the SiriDB time series
database server

 SiriDB is a scalable, robust and fast time series database. Build from
 the ground up SiriDB uses a mechanism to operate without a global index
 and allows server resources to be added on the fly. SiriDB's query
 language includes dynamic grouping of time series for easy analysis
 over large amounts of time series.
 .
 This package provides the Python3 interface.

The package will be maintained in the SiriDB team.



signature.asc
Description: OpenPGP digital signature

Bug#887674: upload in NEW

2018-02-04 Thread Matthew Vernon


Control: tags 887674 + pending

Hi,

I've made an upload that adds the udeb; it's a new package, so is 
currently in NEW. Thanks for Cyril for the patch.


Regards,

Matthew

Bug#889321: python-grib: Segmentation fault reading NCEP grib file

2018-02-04 Thread alastair


Dear Hugh

Thanks for this report. I confirm that on my system, I also get an 
failure, although a

different one:

corrupted double-linked list (not small)
Aborted


Will investigate further,

Best regards
Alastair McKinstry


On 2018-02-03 15:04, Hugh Pumphrey wrote:

Subject: python-grib: Segmentation fault reading NCEP grib file
Package: python-grib
Version: 2.0.2-1
Severity: normal

Dear Maintainer,

I have a python script that reads in some data from a GRIB file
obtained from NCEP. Last time I used it (about a year ago), it worked;
that was on Debian 8 (and, I think, i386). This year, having upgraded
to Debian 9.3 (and gone all amd64), it crashes. A minimal segment of
the script that causes the crash is as follows:

Bug#889551: spectre-meltdown-checker should be in /usr/sbin/respect-meltdown-checker

2018-02-04 Thread shirish शिरीष

Package: spectre-meltdown-checker
Version: 0.32-1
Severity: normal

Dear Maintainer,

I was trying to run spectre-meltdown-checker as a normal user first -

/home/shirish> spectre-meltdown-checker
Spectre and Meltdown mitigation detection tool v0.32

Note that you should launch this script with root privileges to get
accurate information.
We'll proceed but you might see permission denied errors.
To run it as root, you can try the following command: sudo
/usr/bin/spectre-meltdown-checker

if it needs roots privileges, shouldn't it be in
/usr/sbin/spectre-meltdown-checker ?

It kinda feels twisted especially when you see that it's the kernel
which is being looked into,
not the userspace.

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

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=UTF-8)
(ignored: LC_ALL set to en_IN.UTF-8), LANGUAGE=en_IN.UTF-8
(charmap=UTF-8) (ignored: LC_ALL set to en_IN.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

-- no debconf information

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#888950: brotli: Use dh_missing --fail-missing

2018-02-04 Thread Jeremy Bicha

On Sat, Feb 3, 2018 at 2:19 AM, Tomasz Buchert  wrote:
> I first bumped the compat level and update the changelog, but then
> thought that maybe you actually really on the version 10.3 of
> debhelper, so I reverted my change ... without reverting the
> changelog.

You can bump the compat level if you want (especially since you
already mentioned it in your changelog).

The only reason I hesitated is because I'll need to lower the compat
to 10 for when I backport brotli to Ubuntu 17.10. (But I'll have to
lower the compat to 9 for 16.04 LTS anyway so not a big deal.)

berto has been doing "sloppy backports" of webkit2gtk to oldstable so
he would need to adjust the debhelper dependency and compat level for
that too.

The brotli backports will be needed by webkit2gtk 2.20 +.

Thanks,
Jeremy Bicha

Bug#889555: linux-image-4.14.0-3-amd64: general protection fault, SMP PTI, while running hwinfo

2018-02-04 Thread J Mo

Package: src:linux
Version: 4.14.13-1
Severity: normal

linux-image-4.14.0-3-amd64: general protection fault, SMP PTI, while running 
hwinfo

I upgraded one of my desktop systems two days ago and noticed immediately that 
it was freezing up every day at the same time. Total system lock. The trigger 
seems to be a cron job that collects and saves info about the system using 
tools like 'lshw' 'dmidecode' 'hwinfo' 'apt-show-versions', etc-etc-etc.

Previous kernel was 4.12.0-1-amd64 and that was very stable -- uptime was about 
110 days when I rebooted it for this upgrade.

Hardware is a Gigabyte GA-H170N-WIFI with a skylake i5-6500. I have four other 
older systems but only this one has shown any problem thus far. Interesting 
system features include: running bcache, lots of KVM VMs run locally, heavy 
desktop-type usage.

I ran my sysinfo collector script manually a few times after a fresh boot. The 
first two ran fine, but the third coughed up this GPF, the system started to 
fail, and I had to force a reboot:



Feb 04 01:38:11.433173 myhost kernel: general protection fault:  [#1] SMP 
PTI
Feb 04 01:38:11.433236 myhost kernel: Modules linked in: lp parport_pc 
xt_physdev br_netfilter nf_log_ipv4 nf_log_common xt_LOG xt_tcpudp xt_mac 
vhost_net vhost tap tun sctp_diag sc
Feb 04 01:38:11.433281 myhost kernel:  iTCO_wdt intel_cstate snd_timer 
intel_uncore snd intel_rapl_perf pcspkr iTCO_vendor_support cfg80211 sg joydev 
drbg mei_me soundcore evdev cdc
Feb 04 01:38:11.433307 myhost kernel: CPU: 2 PID: 1 Comm: systemd Tainted: P
   O4.14.0-3-amd64 #1 Debian 4.14.13-1
Feb 04 01:38:11.433326 myhost kernel: Hardware name: Gigabyte Technology Co., 
Ltd. H170N-WIFI/H170N-WIFI-CF, BIOS F21 03/07/2017
Feb 04 01:38:11.433344 myhost kernel: task: 96141af32040 task.stack: 
a7d88318
Feb 04 01:38:11.433363 myhost kernel: RIP: 0010:__task_pid_nr_ns+0x4a/0x90
Feb 04 01:38:11.433381 myhost kernel: RSP: 0018:a7d883183e60 EFLAGS: 
00010202
Feb 04 01:38:11.433399 myhost kernel: RAX:  RBX: 
96131f20f180 RCX: 3fdf9690a09eb2d6
Feb 04 01:38:11.433418 myhost kernel: RDX: b3844c60 RSI: 
 RDI: 961282e239a0
Feb 04 01:38:11.433438 myhost kernel: RBP: a7d883183f20 R08: 
1000 R09: 000b
Feb 04 01:38:11.433456 myhost kernel: R10: 55c1f77e7010 R11: 
96123e0be00a R12: 96125147af00
Feb 04 01:38:11.433474 myhost kernel: R13:  R14: 
961282e23410 R15: 96131f20f180
Feb 04 01:38:11.433492 myhost kernel: FS:  7fbd7e19fe00() 
GS:96143ed0() knlGS:
Feb 04 01:38:11.433510 myhost kernel: CS:  0010 DS:  ES:  CR0: 
80050033
Feb 04 01:38:11.433528 myhost kernel: CR2: 5626d0ac3988 CR3: 
000819ffe001 CR4: 003626e0
Feb 04 01:38:11.433546 myhost kernel: Call Trace:
Feb 04 01:38:11.433564 myhost kernel:  cgroup_procs_show+0x15/0x30
Feb 04 01:38:11.433584 myhost kernel:  seq_read+0x331/0x440
Feb 04 01:38:11.433603 myhost kernel:  vfs_read+0x89/0x130
Feb 04 01:38:11.433621 myhost kernel:  SyS_read+0x52/0xc0
Feb 04 01:38:11.433640 myhost kernel:  system_call_fast_compare_end+0xc/0x6f
Feb 04 01:38:11.433658 myhost kernel: RIP: 0033:0x7fbd7dada908
Feb 04 01:38:11.433676 myhost kernel: RSP: 002b:7ffee6997f10 EFLAGS: 
0246
Feb 04 01:38:11.433694 myhost kernel: Code: 04 74 0e 89 f6 48 8d 04 76 48 8d 04 
c5 90 05 00 00 48 8b bf 58 05 00 00 48 01 c7 31 c0 48 8b 0f 48 85 c9 74 18 8b 
b2 30 08 00 00 <3b> 71
Feb 04 01:38:11.433712 myhost kernel: RIP: __task_pid_nr_ns+0x4a/0x90 RSP: 
a7d883183e60
Feb 04 01:38:11.433731 myhost kernel: ---[ end trace b4a3bf3b2fb7682a ]---
Feb 04 01:38:11.433750 myhost kernel: [ cut here ]
Feb 04 01:38:11.433769 myhost kernel: WARNING: CPU: 2 PID: 1 at 
/build/linux-LHmLg5/linux-4.14.13/kernel/fork.c:419 __put_task_struct+0xeb/0x150
Feb 04 01:38:11.433788 myhost kernel: Modules linked in: lp parport_pc 
xt_physdev br_netfilter nf_log_ipv4 nf_log_common xt_LOG xt_tcpudp xt_mac 
vhost_net vhost tap tun sctp_diag sc
Feb 04 01:38:11.433810 myhost kernel:  iTCO_wdt intel_cstate snd_timer 
intel_uncore snd intel_rapl_perf pcspkr iTCO_vendor_support cfg80211 sg joydev 
drbg mei_me soundcore evdev cdc
Feb 04 01:38:11.433832 myhost kernel: CPU: 2 PID: 1 Comm: systemd Tainted: P
  DO4.14.0-3-amd64 #1 Debian 4.14.13-1
Feb 04 01:38:11.433850 myhost kernel: Hardware name: Gigabyte Technology Co., 
Ltd. H170N-WIFI/H170N-WIFI-CF, BIOS F21 03/07/2017
Feb 04 01:38:11.433868 myhost kernel: task: 96141af32040 task.stack: 
a7d88318
Feb 04 01:38:11.433886 myhost kernel: RIP: 0010:__put_task_struct+0xeb/0x150
Feb 04 01:38:11.433905 myhost kernel: RSP: 0018:a7d883183e18 EFLAGS: 
00010246
Feb 04 01:38:11.433923 myhost kernel: RAX:  RBX: 
961282e23410 RCX: dead0200
Feb 04 01:38:11.433941 myhost kernel: RDX: 0001 RSI: 
9612d0903be0 RDI: 961282e23410

Bug#886833: [gweled] Not compatable with recent gtk

2018-02-04 Thread Juhani Numminen

Followup-For: Bug #886833
Package: gweled
Version: 0.9.1-4

I'm getting a segfault at startup as well. I obtained a backtrace
using the instructions from wiki:
https://wiki.debian.org/HowToGetABacktrace


juhani@computer:~$ LANG=C gdb gweled
GNU gdb (Debian 7.12-6+b1) 7.12.0.20161007-git
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gweled...Reading symbols from 
/usr/lib/debug/.build-id/e4/b0823b7d96de627877b9462eeccbf06106f160.debug...done.
done.
(gdb) set pagination 0
(gdb) run
Starting program: /usr/games/gweled 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Gtk-Message: Failed to load module "atk-bridge"
Error loading config file: No such file or directory
[New Thread 0x7fd56aaf3700 (LWP 2992)]
[New Thread 0x7fd56a2f2700 (LWP 2993)]

(gweled:2987): GLib-WARNING **: GError set over the top of a previous GError or 
uninitialized memory.
This indicates a bug in someone's code. You must ensure an error is NULL before 
it's set.
The overwriting error message was: Operation not supported

Thread 1 "gweled" received signal SIGSEGV, Segmentation fault.
__GI___libc_free (mem=0x180) at malloc.c:3097
3097malloc.c: No such file or directory.
(gdb) bt
#0  0x7fd578b463d1 in __GI___libc_free (mem=0x180) at malloc.c:3097
#1  0x562f8f00e179 in sge_load_svg_to_pixbuf 
(filename=filename@entry=0x562f9002dc00 "gweled/gem01.svg", width=48, 
height=48) at sge_utils.c:42
#2  0x562f8f00c676 in gweled_load_pixmaps () at graphic_engine.c:81
#3  0x562f8f00866d in main (argc=1, argv=0x7ffde66328a8) at main.c:429
(gdb) quit
A debugging session is active.

Inferior 1 [process 2987] will be killed.

Quit anyway? (y or n) y
juhani@computer:~$ 


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

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

Versions of packages gweled depends on:
ii  libatk1.0-0  2.26.1-3
ii  libc62.26-4
ii  libcairo21.15.8-3
ii  libfontconfig1   2.12.6-0.1
ii  libfreetype6 2.8.1-1
ii  libgdk-pixbuf2.0-0   2.36.11-1
ii  libglib2.0-0 2.54.3-2
ii  libgtk2.0-0  2.24.32-1
ii  libmikmod3   3.3.11.1-3
ii  libpango-1.0-0   1.40.14-1
ii  libpangocairo-1.0-0  1.40.14-1
ii  libpangoft2-1.0-01.40.14-1
ii  librsvg2-2   2.40.20-2

gweled recommends no packages.

gweled suggests no packages.

-- no debconf information

Bug#889483: libegl1 disables amdgpu drm with Buster mesa

2018-02-04 Thread Timo Aaltonen

On 04.02.2018 15:50, fin4478 fin4478 wrote:
> Reopen this bug, the log file shows that this bug is for Debian Buster
> Mesa.

No, you've messed up your system and it doesn't have a matching libgbm1
etc installed anymore. You need to fix it yourself.

Bug#848102: [octave] crashed with some random typing in octave editor

2018-02-04 Thread Lumin

On Thu, 1 Feb 2018 at 11:17 Mike Miller  wrote:

> On Wed, Dec 14, 2016 at 06:44:53 +, lumin wrote:
> > Randomly typing something in octave editor will cause
> > a crash with SIGSEGV.
> >
> > For example, I launched Octave and typed merely "asdfasdf"
> > and then octave crashed.
>
> Can you please try with the version of octave currently in testing?


I’m on unstable. I tried octave 4.2.1-5 (unstable) and the issue refers
By this bug no longer exists. Since the octave version in testing
Is the same, I think that should be ok too.


> Since this was reported, Octave now uses Qt 5 and it's possible that
> this bug only affects an older set of Qt and/or QScintilla libs.
>
> I used to be able to trigger a similar bug by installing qt-at-spi and
> setting the QT_ACCESSIBILITY environment variable. But as I understand
> it the Qt 5 a11y support has been redesigned.
>
> If octave still crashes for you, please provide your locale, keyboard
> layout, and any input method settings.


Thank you, this problem is resolved. I cannot crash octave editor by
The same way.


> --
> mike
>
-- 
Best,

Bug#888642: Your mail

2018-02-04 Thread Michael Biebl

On Sat, 3 Feb 2018 22:17:27 +0100 Christopher Schramm
 wrote:
> I think I found the initial problem: /usr/bin/dbus-launch does not
> terminate abnormally, it doesn't even start as it's not present. blueman
> is missing a dependency on dbus-x11.

Please don't add a direct dependency on dbus-x11. This is completely
unnecessary if say you are using dbus-user-session and makes our Debian
D-Bus maintainer unhappy.
Please use Depends: default-dbus-session-bus | dbus-session-bus
instead.

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

signature.asc
Description: OpenPGP digital signature

Bug#889012: Daemon flags aren't supported in systemd service

2018-02-04 Thread Vincent Blut


Control: tags -1 pending

Hi,

On Thu, Feb 01, 2018 at 09:44:04AM +0100, Christian Ehrhardt wrote:

Package: chrony
Version: 3.2-2

Description:
We still ship /etc/default/chrony which contians DAEMON_OPTS.
But the systemd service does not include that configuration, so we
lack a way to control options and upgraders might even regress and not
immediately see why.

The scheme to make those vars available in systemd services is pretty
common now and the suggested fix implements it this way.


Well, I did that on purpose to discourage systemd users from using this 
file (not to annoy them, after all I’m part of them) as that service 
manager provides capabilities to pass custom options to daemons (e.g.  
using drop-in files). So I wanted to invite them to use those 
capabilities rather than using the “/etc/default/chrony” file which is, 
to me, a lousy convention.


However, I do agree that it might confused some users so I’m willing to 
accept your patch.



Ubuntu-Bug: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1746081
Fix-in-Review: 
https://git.launchpad.net/~paelzer/ubuntu/+source/chrony/commit/?id=e36bec99099dfaf6be6fb1b885a09f11d6025844


[1]: 
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/336844

--
Christian Ehrhardt
Software Engineer, Ubuntu Server
Canonical Ltd


Cheers,
Vincent


signature.asc
Description: PGP signature

Bug#889543: CMake Error: The following variables are used in this project, but they are set to NOTFOUND.

2018-02-04 Thread jean-christophe manciot

Thanks for your swift reply.
The build env is a sid chroot and:
liblz4-dev:
  Installed: 0.0~r131-2+b1


On Sun, Feb 4, 2018 at 11:54 AM, Ondřej Surý  wrote:

> Hi Jean-Christophe,
>
> what is your build environment?
>
> Is liblz4-dev installed?
>
> Cheers,
> --
> Ondřej Surý
> ond...@sury.org
>
>
>
> > On 4 Feb 2018, at 11:45, jean-christophe manciot <
> actionmysti...@gmail.com> wrote:
> >
> > Package: mariadb-10.1
> > Version: 1:10.1.29-6
> >
> > Building with:
> > debuild -i -I --no-sign --build=binary
> >
> > leads to:
> > ...
> > -- Looking for event.h
> > -- Looking for event.h - found
> > CMake Deprecation Warning at cmake/for_clients.cmake:15 (CMAKE_POLICY):
> >   The OLD behavior for policy CMP0007 will be removed from a future
> version
> >   of CMake.
> >
> >   The cmake-policies(7) manual explains that the OLD behaviors of all
> >   policies are deprecated and that a policy should be set to OLD only
> under
> >   specific short-term circumstances.  Projects should be ported to the
> NEW
> >   behavior and not rely on setting a policy to OLD.
> > Call Stack (most recent call first):
> >   CMakeLists.txt:422 (INCLUDE)
> >
> >
> > CMake Error: The following variables are used in this project, but they
> are set to NOTFOUND.
> > Please set them or make sure they are set and tested correctly in the
> CMake files:
> > LZ4_LIBS
> > linked by target "libgroonga" in directory /home/actionmystique/src/
> MariaDB/mariadb-10.1-10.1.29-6/storage/mroonga/vendor/groonga/lib
> >
> > -- Configuring incomplete, errors occurred!
> > See also "/home/actionmystique/src/MariaDB/mariadb-10.1-10.1.29-
> 6/builddir/CMakeFiles/CMakeOutput.log".
> > See also "/home/actionmystique/src/MariaDB/mariadb-10.1-10.1.29-
> 6/builddir/CMakeFiles/CMakeError.log".
> >
> > The following files are attached:
> > - full build log
> > - CMakeOutput.log
> > - CMakeError.log
> >
> > --
> > Jean-Christophe Manciot
> > 
>
>


-- 
Jean-Christophe

Bug#888887: passwordsafe FTBFS on big endian: test failures

2018-02-04 Thread Adrian Bunk

On Sat, Feb 03, 2018 at 07:17:19PM -0500, Bill Blough wrote:
> 
> I have uploaded passwordsafe-1.04+dfsg-2 which fixes the failures on all
> big endian archs

Thanks!

> except for alpha and sparc64.
>...

Alpha is little endian, so that's unrelated.

sparc64 is big endian, but that's likely unrelated here.
Usually "Bus error" is the sparc way of saying "I do not like unaligned access"
(sparc is more picky on that than any other current Debian architecture).

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#889544: laptop-mode-tools causes `sda` disk to start and stop again and again when on battery

2018-02-04 Thread Slawomir Gonet

Package: laptop-mode-tools
Version: 1.72-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

just to note, my hardware is Dell e7450, disk drive is:
ata2.00: ATA-9: SAMSUNG SSD PM851 mSATA 256GB, EXT4AD0Q, max UDMA/133

* What led up to the situation?

 `apt full-upgrade -V` done on Feb 3, causing `laptop-mode-tools`
 update to version `1.72-1`

* What was the outcome of this action?

 After disconnecting laptop from power source (docking station)
 system become irresponsive - seemed like disk failure.


I have quickly done full disk backup (using Clonezilla, on AC, without
any errors) and started looking for cause.

Dell Onboard Diagnostics software found no problems with my hard drive
(running long DST)

Trying to reproduce this issue on some random gparted usb stick I had on
my desk failed - so this definitely meant software problem in my Debian.

Finally, looking into what updated recently I have found that
laptop-mode-tools has been updated yesterday. I've purged the package,
rebooted and system become stable without AC again.

Further tests narrowed case to (at least one of) two modules:

* intel-hda-powersave.conf
* intel-sata-powermgmt.conf

Setting:

CONTROL_INTEL_HDA_POWER=0
CONTROL_INTEL_SATA_POWER=

made laptop-mode-tools usable again. (see attached modified config
files)


* Logs

With laptop-mode-tools in standard configuration, when disconnected from
AC I was getting in `dmesg` similiard messages every few seconds:

[  +3.568871] sd 1:0:0:0: [sda] Synchronizing SCSI cache
[  +0.005399] sd 1:0:0:0: [sda] Stopping disk
[  +1.222534] sd 1:0:0:0: [sda] Starting disk
[  +0.347509] EXT4-fs (dm-3): re-mounted. Opts: data=ordered,commit=600
[  +0.261822] EXT4-fs (dm-1): re-mounted. Opts: data=ordered,commit=600

causing `sda` to be completely unusbable, causing `dm_crypt` errors in
the end:

Feb 04 00:27:52 odyssey kernel: INFO: task dmcrypt_write:247 blocked for more 
than 120 seconds.
Feb 04 00:27:52 odyssey kernel:   Not tainted 4.14.0-3-amd64 #1 Debian 
4.14.13-1
Feb 04 00:27:52 odyssey kernel: "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 04 00:27:52 odyssey kernel: dmcrypt_write   D0   247  2 0x8000


Thanks,
Slawek


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

Kernel: Linux 4.14.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)
LSM: AppArmor: enabled

Versions of packages laptop-mode-tools depends on:
ii  lsb-base9.20170808
ii  psmisc  23.1-1
ii  util-linux  2.30.2-0.3

Versions of packages laptop-mode-tools recommends:
ii  ethtool 1:4.11-1
ii  hdparm  9.53+ds-1
ii  net-tools   1.60+git20161116.90da8a0-1
ii  python3-pyqt5   5.9.2+dfsg-1
ii  rfkill  0.5-3
ii  sdparm  1.08-1+b1
ii  udev237-1
ii  wireless-tools  30~pre9-12+b1

Versions of packages laptop-mode-tools suggests:
ii  acpid  1:2.0.28-1+b1

-- Configuration Files:
/etc/laptop-mode/conf.d/intel-hda-powersave.conf changed:
DEBUG=0
CONTROL_INTEL_HDA_POWER=0
BATT_INTEL_HDA_POWERSAVE=1
LM_AC_INTEL_HDA_POWERSAVE=0
NOLM_AC_INTEL_HDA_POWERSAVE=0
INTEL_HDA_DEVICE_TIMEOUT=2
INTEL_HDA_DEVICE_CONTROLLER=1

/etc/laptop-mode/conf.d/intel-sata-powermgmt.conf changed:
DEBUG=0
CONTROL_INTEL_SATA_POWER=0
CONTROL_AHCI_RUNTIME_PM=1
BATT_SATA_POLICY=min_power
LM_AC_SATA_POLICY=max_performance
NOLM_AC_SATA_POLICY=max_performance

/etc/laptop-mode/laptop-mode.conf changed:
ENABLE_LAPTOP_MODE_TOOLS=1
VERBOSE_OUTPUT=1
LOG_TO_SYSLOG=1
DEBUG=0
ENABLE_LAPTOP_MODE_ON_BATTERY=0
ENABLE_LAPTOP_MODE_ON_AC=0
ENABLE_LAPTOP_MODE_WHEN_LID_CLOSED=0
ENABLE_AUTO_MODULES=1
MINIMUM_BATTERY_CHARGE_PERCENT=3
DISABLE_LAPTOP_MODE_ON_CRITICAL_BATTERY_LEVEL=1
DISABLE_BATTERY_ALARM_CHECK=0
HD="/dev/[hs]d[abcdefgh]"
PARTITIONS="auto /dev/mapper/* /dev/dm-*"
ASSUME_SCSI_IS_SATA=1
LM_BATT_MAX_LOST_WORK_SECONDS=600
LM_AC_MAX_LOST_WORK_SECONDS=360
CONTROL_READAHEAD=1
LM_READAHEAD=3072
NOLM_READAHEAD=128
CONTROL_NOATIME=0
USE_RELATIME=1
CONTROL_HD_IDLE_TIMEOUT=1
LM_AC_HD_IDLE_TIMEOUT_SECONDS=20
LM_BATT_HD_IDLE_TIMEOUT_SECONDS=20
NOLM_HD_IDLE_TIMEOUT_SECONDS=7200
CONTROL_HD_POWERMGMT=1
BATT_HD_POWERMGMT=1
LM_AC_HD_POWERMGMT=254
NOLM_AC_HD_POWERMGMT=254
CONTROL_HD_WRITECACHE=0
NOLM_AC_HD_WRITECACHE=1
NOLM_BATT_HD_WRITECACHE=0
LM_HD_WRITECACHE=0
CONTROL_MOUNT_OPTIONS=1
LM_DIRTY_RATIO=60
NOLM_DIRTY_RATIO=40
LM_DIRTY_BACKGROUND_RATIO=1
NOLM_DIRTY_BACKGROUND_RATIO=10
DEF_UPDATE=5
DEF_XFS_AGE_BUFFER=15
DEF_XFS_SYNC_INTERVAL=30
DEF_XFS_BUFD_INTERVAL=1
DEF_MAX_AGE=30
XFS_HZ=100
LM_SECONDS_BEFORE_SYNC=2


-- no debconf information

Bug#889543: CMake Error: The following variables are used in this project, but they are set to NOTFOUND.

2018-02-04 Thread Ondřej Surý

Control: forcemerge 887655 -1
Control: severity 887655 important

Please remove liblz4-dev and try again and I’ll declare proper Build-Conflict 
in git repository to be released in next MariaDB update. This is already 
tracked as #887655.

Ondrej
--
Ondřej Surý
ond...@sury.org



> On 4 Feb 2018, at 11:55, jean-christophe manciot  
> wrote:
> 
> Thanks for your swift reply.
> The build env is a sid chroot and:
> liblz4-dev:
>   Installed: 0.0~r131-2+b1
> 
> 
> On Sun, Feb 4, 2018 at 11:54 AM, Ondřej Surý  wrote:
> Hi Jean-Christophe,
> 
> what is your build environment?
> 
> Is liblz4-dev installed?
> 
> Cheers,
> --
> Ondřej Surý
> ond...@sury.org
> 
> 
> 
> > On 4 Feb 2018, at 11:45, jean-christophe manciot  
> > wrote:
> >
> > Package: mariadb-10.1
> > Version: 1:10.1.29-6
> >
> > Building with:
> > debuild -i -I --no-sign --build=binary
> >
> > leads to:
> > ...
> > -- Looking for event.h
> > -- Looking for event.h - found
> > CMake Deprecation Warning at cmake/for_clients.cmake:15 (CMAKE_POLICY):
> >   The OLD behavior for policy CMP0007 will be removed from a future version
> >   of CMake.
> >
> >   The cmake-policies(7) manual explains that the OLD behaviors of all
> >   policies are deprecated and that a policy should be set to OLD only under
> >   specific short-term circumstances.  Projects should be ported to the NEW
> >   behavior and not rely on setting a policy to OLD.
> > Call Stack (most recent call first):
> >   CMakeLists.txt:422 (INCLUDE)
> >
> >
> > CMake Error: The following variables are used in this project, but they are 
> > set to NOTFOUND.
> > Please set them or make sure they are set and tested correctly in the CMake 
> > files:
> > LZ4_LIBS
> > linked by target "libgroonga" in directory 
> > /home/actionmystique/src/MariaDB/mariadb-10.1-10.1.29-6/storage/mroonga/vendor/groonga/lib
> >
> > -- Configuring incomplete, errors occurred!
> > See also 
> > "/home/actionmystique/src/MariaDB/mariadb-10.1-10.1.29-6/builddir/CMakeFiles/CMakeOutput.log".
> > See also 
> > "/home/actionmystique/src/MariaDB/mariadb-10.1-10.1.29-6/builddir/CMakeFiles/CMakeError.log".
> >
> > The following files are attached:
> > - full build log
> > - CMakeOutput.log
> > - CMakeError.log
> >
> > --
> > Jean-Christophe Manciot
> > 
> 
> 
> 
> 
> -- 
> Jean-Christophe

Bug#889435: Updating the build-helper-maven-plugin Uploaders list

2018-02-04 Thread Matthias Schmitz

Hello everyone,

On Sat, 3 Feb 2018 17:26:19 +0100 Tobias Frost  wrote:
> Source: build-helper-maven-plugin
> Version: 1.8-1 3.0.0-1
> Severity: minor
> User: m...@qa.debian.org
> Usertags: mia-teammaint
> 
> Damien Raude-Morvan  has not been working on
> the build-helper-maven-plugin package for quite some time.
 
> We are tracking their status in the MIA team and would like to ask you
> to remove them from the Uploaders list of the package so we can close
> that part of the file.
please remove me as well from the uploaders.

best wishes,
Matthias Schmitz 



pgp33T5XULEWK.pgp
Description: Digitale Signatur von OpenPGP

Bug#889546: r-cran-reshape2: [INTL:de] Initial German translation

2018-02-04 Thread Chris Leick


Package: r-cran-reshape2
Version: R 2.15.1
Severity: wishlist
Tags: l10n patch



Hi,

please find attached the German translation.

Kind regards,
Chris

Bug#889557: ovito: (Build-)Depends on obsolete libbotan1.10-dev

2018-02-04 Thread Christian Hofstaedtler

Package: ovito
Version: 2.9.0+dfsg1-5
Severity: serious

Dear Maintainer,

your package ovito (build-)depends on botan1.10, which itself is
obsolete. Upstream will end security support at the end of 2018, so it
must not be part of buster.

Please drop the libbotan1.10-dev build dependency.

Thanks,
Chris

Bug#889558: qtcreator: (Build-)Depends on obsolete libbotan1.10-dev

2018-02-04 Thread Christian Hofstaedtler

Package: qtcreator
Version: 4.5.0-2
Severity: serious

Dear Maintainer,

your package qtcreator (build-)depends on botan1.10, which itself is
obsolete. Upstream will end security support at the end of 2018, so it
must not be part of buster.

Please drop the libbotan1.10-dev build dependency.

Thanks,
Chris

Bug#889556: monotone: (Build-)Depends on obsolete libbotan1.10-dev

2018-02-04 Thread Christian Hofstaedtler

Package: monotone
Version: 1.1-9
Severity: serious

Dear Maintainer,

your package monotone (build-)depends on botan1.10, which itself is
obsolete. Upstream will end security support at the end of 2018, so it
must not be part of buster.

Please drop the libbotan1.10-dev build dependency.

Thanks,
Chris

Bug#623945: Bug #623945: dpkg-dev: Please add option to tell dpkg-source 3.0 (quilt) to skip diffing source tree

2018-02-04 Thread Michael Banck

Hi,

On Sun, Apr 24, 2011 at 07:01:02PM +0200, Michael Banck wrote:
> I have a 90 mb source tarball, which is 528 mb unpacked.  Running
> dpkg-buildpackage -S on it takes ages (657 seconds, to be exact) on my
> notebook, as it checks whether there are changes in the original source
> to put into debian/patches/debian-changes-foo, even though I made sure
> there are no such changes.
> 
> Indeed, in most subversion-based work-flows, there are only supposed to
> be changes under debian/ and changes from diffing the source are usually
> bugs, not features.
> 
> So an option which tells dpkg-source to skip diffing the original source
> against the current soure tree would reduce time to build the source
> package tremendously and avoid unwanted errors due to
> debian/patches/debian-changes*.
> 
> Would you accept patches for this or even want to implement this
> yourself?

This just bugged me again, so I had a look at how invasive it would be.

It turns out all it takes would be to let do_build() in
Source/Package/V2.pm not call _generate_patch(), but include the
'Identify original tarballs' logic at the beginning of
_generate_patch().

The attached patch crudely does this, but breaks all the other
use-cases, of course.

I think the 'Identify original tarballs' part should be factored out
into a different function (_generate_patch() is at least also called
from do_commit()).


Michael
--- /usr/share/perl5/Dpkg/Source/Package/V2.pm.orig	2018-02-04 14:37:17.568686018 +0100
+++ /usr/share/perl5/Dpkg/Source/Package/V2.pm	2018-02-04 14:40:54.324192770 +0100
@@ -563,35 +563,58 @@
 $self->register_error();
 }
 };
+
+# Identify original tarballs
+my ($tarfile, %addonfile);
+my $comp_ext_regex = compression_get_file_extension_regex();
+my @origtarballs;
 
-# Create a patch
-my $autopatch = File::Spec->catfile($dir, 'debian', 'patches',
-$self->get_autopatch_name());
-my $tmpdiff = $self->_generate_patch($dir, order_from => $autopatch,
-header_from => $autopatch,
-handle_binary => $handle_binary,
-skip_auto => $self->{options}{auto_commit},
-usage => 'build');
-unless (-z $tmpdiff or $self->{options}{auto_commit}) {
-info(g_('you can integrate the local changes with %s'),
- 'dpkg-source --commit');
-error(g_('aborting due to unexpected upstream changes, see %s'),
-  $tmpdiff);
+foreach my $file (sort $self->find_original_tarballs()) {
+if ($file =~ /\.orig\.tar\.$comp_ext_regex$/) {
+if (defined($tarfile)) {
+error(g_('several orig.tar files found (%s and %s) but only ' .
+ 'one is allowed'), $tarfile, $file);
+}
+$tarfile = $file;
+push @origtarballs, $file;
+$self->add_file($file);
+$self->add_file("$file.asc") if -e "$file.asc";
+} elsif ($file =~ /\.orig-([[:alnum:]-]+)\.tar\.$comp_ext_regex$/) {
+$addonfile{$1} = $file;
+push @origtarballs, $file;
+$self->add_file($file);
+$self->add_file("$file.asc") if -e "$file.asc";
+}
 }
-push_exit_handler(sub { unlink($tmpdiff) });
+
+# Create a patch
+#my $autopatch = File::Spec->catfile($dir, 'debian', 'patches',
+#$self->get_autopatch_name());
+#my $tmpdiff = $self->_generate_patch($dir, order_from => $autopatch,
+#header_from => $autopatch,
+#handle_binary => $handle_binary,
+#skip_auto => $self->{options}{auto_commit},
+#usage => 'build');
+#unless (-z $tmpdiff or $self->{options}{auto_commit}) {
+#info(g_('you can integrate the local changes with %s'),
+# 'dpkg-source --commit');
+#error(g_('aborting due to unexpected upstream changes, see %s'),
+#  $tmpdiff);
+#}
+#push_exit_handler(sub { unlink($tmpdiff) });
 $binaryfiles->update_debian_source_include_binaries() if $include_binaries;
 
-# Install the diff as the new autopatch
-if ($self->{options}{auto_commit}) {
-make_path(File::Spec->catdir($dir, 'debian', 'patches'));
-$autopatch = $self->register_patch($dir, $tmpdiff,
-   $self->get_autopatch_name());
-info(g_('local changes have been recorded in a new patch: %s'),
- $autopatch) if -e $autopatch;
-rmdir(File::Spec->catdir($dir, 'debian', 'patches')); # No check on purpose
-}
-unlink($tmpdiff) or syserr(g_('cannot remove %s'), $tmpdiff);
-pop_exit_handler();
+## Install the diff as the new autopatch
+#if

Bug#889545: libopenmpt0: possible out-of-bounds memory read with malformed STP files

2018-02-04 Thread James Cowgill

Control: retitle -1 libopenmpt0: CVE-2018-6611

On 04/02/18 12:26, James Cowgill wrote:
> Package: libopenmpt0
> Version: 0.3.1-1
> Severity: grave
> Tags: security
> 
> This security update was published for libopenmpt:
> https://lib.openmpt.org/libopenmpt/2018/02/03/security-update-0.3.6/
> 
>> The OpenMPT/libopenmpt project released the latest stable libopenmpt version:
>>
>> libopenmpt 0.3.6 (2018-02-03)
>> [Sec] Possible out-of-bounds memory read with malformed STP files. (r9576)
> 
> The bug only affects 0.3.x so it will not require any updates to stable.
> 
> I have requested a CVE for this bug.

... and it was allocated CVE-2018-6611.

James



signature.asc
Description: OpenPGP digital signature

Bug#889144: stricter PIDfile handling breaks several daemons

2018-02-04 Thread Simon Kelley

With my dnsmasq maintainer hat on, the current arrangement looks like this.

1) /run/dnsmasq is a directory owned by dnsmasq:nogroup
2) /run/dnsmasq/dnsmasq.pid gets written by dnsmasq before it drops
root, so is root:root
3) The reason /run/dnsmasq is owned by dnsmasq is so that dnsmasq can
unlink the pidfile at shutdown, after it has dropped root and is running
as 'dnsmasq'


There's a potential security hole here, since an attacker who can become
user dnsmasq, can create a symlink at /run/dnsmasq/dnsmasq.pid to
anywhere, and have the target of the symlink overwritten (as root) at
startup. The dnsmasq PID-file creation code detects and blocks this
case: see src/dnsmasq.c around line 507.

I think that this can be fixed in dnsmasq by chown()ing the pid file to
the same user dnsmasq is about to drop privs too, but I'm not sure is
that's enough to keep the new systemd checks happy.

Cheers,

Simon.

Bug#889570: RFS: libt3window/0.3.0-1

2018-02-04 Thread Gertjan Halkes

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "libt3window"

* Package name: libt3window
  Version : 0.3.0-1
  Upstream Author : Gertjan Halkes 
* URL : https://os.ghalkes.nl/t3/libt3window.html
* License : GPLv3
  Section : libs

It builds those binary packages:

  libt3window-dev - Development files for libt3window
  libt3window0 - Library for creating window-based terminal programs

To access further information about this package, please visit the
following URL:

https://mentors.debian.net/package/libt3window

Alternatively, one can download the package with dget using this
command:

  dget -x
  
https://mentors.debian.net/debian/pool/main/libt/libt3key/libt3window_0.3.0-1.dsc

Changes since the last upload:

  * New upstream release.

The new upstream release improves line drawing, updates internal tables
to Unicode 10.0 and fixes some small bugs.

Regards,
 Gertjan Halkes

Bug#889569: RFS: libt3key/0.2.8-1

2018-02-04 Thread Gertjan Halkes

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "libt3key"

* Package name: libt3key
  Version : 0.2.8-1
  Upstream Author : Gertjan Halkes 
* URL : https://os.ghalkes.nl/t3/libt3key.html
* License : GPLv3
  Section : libs

It builds those binary packages:

  libt3key-bin - Utilities for working with libt3key terminal
descriptions libt3key-dev - Development files for libt3key
  libt3key1  - Terminal key sequence database library

To access further information about this package, please visit the
following URL:

https://mentors.debian.net/package/libt3key

Alternatively, one can download the package with dget using this
command:

  dget -x
  https://mentors.debian.net/debian/pool/main/libt/libt3key/libt3key_0.2.8-1.dsc

Changes since the last upload:

  * New upstream release.

The new upstream release improves key-sequence coverage for the linux
console and adds more fallbacks from the terminfo database.

Regards,
 Gertjan Halkes

Bug#889568: ibm-3270: Incomplete debian/copyright?

2018-02-04 Thread Chris Lamb

Source: ibm-3270
Version: 3.6ga4-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Philipp Kern 

Hi,

I just ACCEPTed ibm-3270 from NEW but noticed it was missing 
attribution in debian/copyright for some attributions in
x3270/select.c.

(This is not exhaustive so please check over the entire package 
carefully and address these on your next upload.)

Congrats on this hitting main!


Regards,

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

Bug#712394: lintian: Warn if override_dh_auto_test target doesn't check for DEB_BUILD_OPTIONS=nocheck

2018-02-04 Thread Chris Lamb

Chris Lamb wrote:

> We might just end up reverting the whole thing, naturally, but let's see
> how we go for now...

Some results coming in:

  
https://lintian.debian.org/tags/override_dh_auto_test-does-not-check-DEB_BUILD_PROFILES.html

Thoughts?


Regards,

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

Bug#883599: moarvm-dev: missing dependencies on -dev packages

2018-02-04 Thread Dominique Dumont

Hello

Sorry for the delay.

On Tue, 5 Dec 2017 15:03:33 + James Cowgill  wrote:
> Including /usr/include/moar/moar.h requires these packages to be
> installed (in addition to the existing dependencies):
>  libatomic-ops-dev
>  libtommath-dev
>  libuv1-dev

Indeed. This will be fixed in new release.

Thanks for the report


-- 
 https://github.com/dod38fr/   -o- http://search.cpan.org/~ddumont/
http://ddumont.wordpress.com/  -o-   irc: dod at irc.debian.org

Bug#883856: Acknowledgement (dpkg: Fails to build any package in path with '@' in it)

2018-02-04 Thread Guillem Jover

Control: forcemerge 881051 -1

On Sat, 2018-02-03 at 13:48:37 +0100, Tobias Frost wrote:
> On Fri, 08 Dec 2017 13:08:04 +0100 Dennis Kaarsemaker wrote:
> > Please note that the version number is incorrect, this happened on a
> > different box than where I filed the bug. That box has dpkg
> > 1.19.0.4ubuntu1, and I've verified that the bug also exists in the git
> > master branch (hence filing a bug with Debian instead of Ubuntu)

> I had this too (but with a "Ł" in the path*), but after updating dpkg
> this went away. Can you retest if you still have the issue?
> 
> * Disclaimer: Did not check if this character was really the culprit,
> I only updated dpkg and had it resolved)
> 
> Version: dpkg (1.19.0.5) updated from (1.19.0.4) ...

Yeah, this was fixed in 1.19.0.5 as reported by Mattia Rizzolo and
then on #881051. Merging now into the closed bug.

Thanks,
Guillem

Bug#889553: icedtea-netx-common: missing L10n in itweb-settings desktop file

2018-02-04 Thread Ronny Standtke

Package: icedtea-netx-common
Version: 1.6.2-3.1
Severity: minor
Tags: patch, l10n

The itweb-settings desktop file is missing translations of the Comment
field.
This field is user visible e.g. in the KDE Plasma start menu. The attached
patch adds a German translation.

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

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

-- no debconf information

--- itweb-settings.desktop.orig	2018-02-04 14:30:13.010879000 +0100
+++ itweb-settings.desktop	2018-02-04 14:23:31.950879000 +0100
@@ -1,6 +1,7 @@
 [Desktop Entry]
 Name=IcedTea Web Control Panel
 Comment=Configure IcedTea Web (javaws and plugin)
+Comment[de]=IcedTea Web (javaws und Plug-in) konfigurieren
 Exec=/usr/bin/itweb-settings
 Icon=javaws
 Terminal=false

Bug#888459: flint-arb's tests fail on 32bit archs using mpfr 4.0.0

2018-02-04 Thread Vincent Lefevre

On 2018-01-26 15:13:53 +0100, Vincent Lefevre wrote:
> It may be a bug in MPFR 4.

This was due to a bug in mpfr_div_ui, fixed in MPFR 4.0.1-rc2.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#737587: Commander Genius 2.0 inclusion

2018-02-04 Thread Gerhard Stein


Dear Debian team,

after struggling with some features and fixing old bugs there is a 
stable release worth a try for your game collection.


Mageia already has it in its central repositories, Arch provides an 
support through AUR and even Retropie has it. There even is a PPA.


It would be cool to also see it here. This is a nice free platformer 
which can enhance the experience of the Debian ecosystem. :-D


Kind Regards,

 - Gerhard Stein

Bug#889560: trilinos: cmake files seem to be missing

2018-02-04 Thread Adrian Bunk

Source: trilinos
Version: 12.12.1-3
Severity: serious
Control: affects -1 src:deal.ii

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/deal.ii.html

...
-- Include /build/1st/deal.ii-8.4.2/cmake/configure/configure_2_trilinos.cmake
CMake Error at /usr/lib/x86_64-linux-gnu/cmake/ROL/ROLConfig.cmake:174 
(INCLUDE):
  INCLUDE could not find load file:

/usr/lib/x86_64-linux-gnu/cmake/ROL/../MiniTensor/MiniTensorConfig.cmake
Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/Piro/PiroConfig.cmake:143 (INCLUDE)
  /usr/lib/x86_64-linux-gnu/cmake/Trilinos/TrilinosConfig.cmake:146 (INCLUDE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/modules/FindTRILINOS.cmake:40 (FIND_PACKAGE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/configure/configure_2_trilinos.cmake:22 (FIND_PACKAGE)
  obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/macro_configure_feature.tmp:1 
(FEATURE_TRILINOS_FIND_EXTERNAL)
  cmake/macros/macro_configure_feature.cmake:76 (INCLUDE)
  cmake/macros/macro_configure_feature.cmake:240 (RUN_COMMAND)
  cmake/configure/configure_2_trilinos.cmake:220 (CONFIGURE_FEATURE)
  cmake/macros/macro_verbose_include.cmake:19 (INCLUDE)
  CMakeLists.txt:119 (VERBOSE_INCLUDE)


CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Piro/PiroConfig.cmake:145 
(INCLUDE):
  INCLUDE could not find load file:

/usr/lib/x86_64-linux-gnu/cmake/Piro/../Tempus/TempusConfig.cmake
Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/Trilinos/TrilinosConfig.cmake:146 (INCLUDE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/modules/FindTRILINOS.cmake:40 (FIND_PACKAGE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/configure/configure_2_trilinos.cmake:22 (FIND_PACKAGE)
  obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/macro_configure_feature.tmp:1 
(FEATURE_TRILINOS_FIND_EXTERNAL)
  cmake/macros/macro_configure_feature.cmake:76 (INCLUDE)
  cmake/macros/macro_configure_feature.cmake:240 (RUN_COMMAND)
  cmake/configure/configure_2_trilinos.cmake:220 (CONFIGURE_FEATURE)
  cmake/macros/macro_verbose_include.cmake:19 (INCLUDE)
  CMakeLists.txt:119 (VERBOSE_INCLUDE)


CMake Error at /usr/lib/x86_64-linux-gnu/cmake/Piro/PiroConfig.cmake:181 
(INCLUDE):
  INCLUDE could not find load file:

/usr/lib/x86_64-linux-gnu/cmake/Piro/../MiniTensor/MiniTensorConfig.cmake
Call Stack (most recent call first):
  /usr/lib/x86_64-linux-gnu/cmake/Trilinos/TrilinosConfig.cmake:146 (INCLUDE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/modules/FindTRILINOS.cmake:40 (FIND_PACKAGE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/configure/configure_2_trilinos.cmake:22 (FIND_PACKAGE)
  obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/macro_configure_feature.tmp:1 
(FEATURE_TRILINOS_FIND_EXTERNAL)
  cmake/macros/macro_configure_feature.cmake:76 (INCLUDE)
  cmake/macros/macro_configure_feature.cmake:240 (RUN_COMMAND)
  cmake/configure/configure_2_trilinos.cmake:220 (CONFIGURE_FEATURE)
  cmake/macros/macro_verbose_include.cmake:19 (INCLUDE)
  CMakeLists.txt:119 (VERBOSE_INCLUDE)


CMake Warning at 
/usr/lib/x86_64-linux-gnu/cmake/Trilinos/TrilinosConfig.cmake:156 (MESSAGE):
  Component "Tempus" NOT found.
Call Stack (most recent call first):
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/modules/FindTRILINOS.cmake:40 (FIND_PACKAGE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/configure/configure_2_trilinos.cmake:22 (FIND_PACKAGE)
  obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/macro_configure_feature.tmp:1 
(FEATURE_TRILINOS_FIND_EXTERNAL)
  cmake/macros/macro_configure_feature.cmake:76 (INCLUDE)
  cmake/macros/macro_configure_feature.cmake:240 (RUN_COMMAND)
  cmake/configure/configure_2_trilinos.cmake:220 (CONFIGURE_FEATURE)
  cmake/macros/macro_verbose_include.cmake:19 (INCLUDE)
  CMakeLists.txt:119 (VERBOSE_INCLUDE)


CMake Warning at 
/usr/lib/x86_64-linux-gnu/cmake/Trilinos/TrilinosConfig.cmake:156 (MESSAGE):
  Component "Domi" NOT found.
Call Stack (most recent call first):
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/modules/FindTRILINOS.cmake:40 (FIND_PACKAGE)
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/configure/configure_2_trilinos.cmake:22 (FIND_PACKAGE)
  obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/macro_configure_feature.tmp:1 
(FEATURE_TRILINOS_FIND_EXTERNAL)
  cmake/macros/macro_configure_feature.cmake:76 (INCLUDE)
  cmake/macros/macro_configure_feature.cmake:240 (RUN_COMMAND)
  cmake/configure/configure_2_trilinos.cmake:220 (CONFIGURE_FEATURE)
  cmake/macros/macro_verbose_include.cmake:19 (INCLUDE)
  CMakeLists.txt:119 (VERBOSE_INCLUDE)


CMake Warning at 
/usr/lib/x86_64-linux-gnu/cmake/Trilinos/TrilinosConfig.cmake:156 (MESSAGE):
  Component "MiniTensor" NOT found.
Call Stack (most recent call first):
  cmake/macros/macro_find_package.cmake:27 (_FIND_PACKAGE)
  cmake/modules/FindTRILINOS.cmake:40

Bug#888829: wpad-extract broken on stretch

2018-02-04 Thread Mike Gabriel


On  Mi 31 Jan 2018 13:33:34 CET, Wolfgang Schweer wrote:


After trying different kioslaverc settings to no avail, the only
chance to get it working again seems to be using pactester, i.e. the
Buster wpad-extract script version

Wolfgang


Thanks Wolfgang for evaluating the possibilities. I will take care of  
a stretch-pu of debian-edu-config. I am sure, that we will get this in  
alright.


Do you see any other issues that we should fix with such a  
proposed-update? Only changes / fixes that are not too invasive.


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



pgpEIt9yPn5xX.pgp
Description: Digitale PGP-Signatur

Bug#888829: wpad-extract broken on stretch

2018-02-04 Thread Wolfgang Schweer

Hi Mike,

On Sun, Feb 04, 2018 at 04:39:43PM +, Mike Gabriel wrote:
> Do you see any other issues that we should fix with such a proposed-update?
> Only changes / fixes that are not too invasive.
 
Fixing smb.conf would require to add only one line. Fixed in Buster, see

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864663#5

Wolfgang


signature.asc
Description: PGP signature

Bug#889572: transmission-daemon: web ui fails to connect to server

2018-02-04 Thread Adam Borowski

Package: transmission-daemon
Version: 2.92-3
Severity: normal

Hi!
In the new version, transmission's web ui (aka
http://HOST:9091/transmission/web/) says it failed to connect to the
server.  This is very puzzling as the web server (on port 9091) comes from
the same process as actual torrents.

Same happens if I build 2.92-2+deb9u1 (stretch-security) on current
unstable.  Only reverting to 2.92-2 makes it work again.

I'm on a second-class arch (x32), I did not test on a release one as I'd
have to recall how to install and configure transmission for remote work.
If you'd require me to test on a first-class arch, please says so.


Meow!
-- System Information:
Debian Release: buster/sid
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: x32 (x86_64)

Kernel: Linux 4.14.0-0.bpo.2-amd64 (SMP w/4 CPU cores)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages transmission-daemon depends on:
ii  adduser  3.117
ii  init-system-helpers  1.51
ii  libc62.26-6
ii  libcurl3-gnutls  7.58.0-2
ii  libevent-2.1-6   2.1.8-stable-4
ii  libminiupnpc10   1.9.20140610-4
ii  libnatpmp1   20110808-4
ii  libssl1.11.1.0g-2
ii  libsystemd0  237-1
ii  lsb-base 9.20170808
ii  transmission-common  2.92-3
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages transmission-daemon recommends:
ii  transmission-cli  2.92-3

transmission-daemon suggests no packages.

-- Configuration Files:
/etc/transmission-daemon/settings.json [Errno 13] Permission denied: 
'/etc/transmission-daemon/settings.json'

-- no debconf information

Bug#889589: geany has a missing-pkg-dependency according to adequate

2018-02-04 Thread shirish शिरीष

Package: geany
Version: 1.32-2
Severity: normal

Usertags: missing-pkgconfig-dependency adequate
User: debian...@lists.debian.org

Dear Maintainer,

I was installing geany when adequate reported that there is a missing
pkgconfig-dependency.

>From adequate's manpage -

  missing-pkgconfig-dependency
   Dependency of a pkg-config (.pc) file shipped by this
package couldn't be satisfied.

   References: Debian Policy §8.4.

/home/shirish> adequate geany
geany: missing-pkgconfig-dependency geany => gtk+-3.0

At the same time it should also change the suggests from libvte9 to
libvte-2.91-0 which is now in Debian buster/testing .

Please fix the same.

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

Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_IN.UTF-8, LC_CTYPE=en_IN.UTF-8 (charmap=UTF-8)
(ignored: LC_ALL set to en_IN.UTF-8), LANGUAGE=en_IN.UTF-8
(charmap=UTF-8) (ignored: LC_ALL set to en_IN.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages geany depends on:
ii  geany-common 1.32-2
ii  libatk1.0-0  2.26.1-3
ii  libc62.26-4
ii  libcairo-gobject21.15.10-1
ii  libcairo21.15.10-1
ii  libgcc1  1:7.2.0-19
ii  libgdk-pixbuf2.0-0   2.36.11-1
ii  libglib2.0-0 2.54.3-2
ii  libgtk-3-0   3.22.26-2
ii  libpango-1.0-0   1.40.14-1
ii  libpangocairo-1.0-0  1.40.14-1
ii  libstdc++6   7.2.0-19

geany recommends no packages.

Versions of packages geany suggests:
pn  doc-base  
pn  libvte9   

-- no debconf information


-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#889144: stricter PIDfile handling breaks several daemons

2018-02-04 Thread Michael Biebl

Am 03.02.2018 um 14:35 schrieb Sven Hartge:
> Um 14:00 Uhr am 03.02.18 schrieb Michael Biebl:

>> The alternative afaics would be, that the daemon writes the pid file as
>> munin:munin then (or ulog:ulog for the above case).
> 
> No, this would open a potential DoS vector.
> 
> Image an attacker gaining access to the munin user. He would then be able
> to write any PID to the PIDfile and the init system would kill the other
> process when the munin-node service is stopped/restarted.
> 

I don't think this applies to systemd though. If the process id listed
in the pid file is not found in the service cgroup, systemd should not
kill the process listed in the pid file. I suspect that MainPID will not
be properly set and systemd will complain about it.

Michael


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



signature.asc
Description: OpenPGP digital signature

Bug#887126: RFS: ddupdate/0.2.0-1 #886546

2018-02-04 Thread Michael Kolmodin

Hi Juhani!

Thanks for your reply, and sorry that I missed it! It was probably lost
in the noise, was not really prepared for a reply from the bug  so to
speak. Listening to high-volume lists is not always easy :(

For better or worse, both upstream and the packaging has evolved since
your review.

On Tue, 16 Jan 2018 15:22:37 +0200 Juhani Numminen
 wrote:
> Alec Leamas kirjoitti 14.01.2018 klo 11:07:
> > I am looking for a sponsor for my package "ddupdate"
>
> Here's a review, but please note that I cannot sponsor you.

It's a pity, but thanks anyway! Perhaps someone else could be motivated
once we are finished with this...

> I don't have network admin knowledge, so I didn't test the
functionality of ddupdate.

It's actually rather straight-forward these days, especially using the
ddupdate-config configuration script (which wasn't there when you
reviewed). That said, focusing on the packaging seems perfectly fine for me.

> Please use up-to-date lintian. It'll give you an error tag and several
> informational and pedantic tags, some of which are easily dealt with.

I'm using sid, updated as of current?!

> This review is based on the package you have uploaded to mentors, but
I also
> had a look at your git repo, where you wrote in a commit message:
> > debian: Fix Standards-Version: to current sid 4.0.0
> Your sources for that information are outdated, you should check [1]
instead.

This one beats me... should I read it that current standard is 4.1.3?

Fixing using the ideas Standards-Version == 4.1.3 and compat level ==
11. Still unsure, though.

> At the mentors site, you write:
> > I cannot understand what's wrong with the copyright file. I guess
it's a silly oversight.
> >
> > uscan works just fine for me, the watch file error seems weird.
>
> If you're referring to "P: ddupdate source: no-dep5-copyright", it's
because your
> debian/copyright doesn't follow the specification[2]: it doesn't have
a header paragraph
> and the license text for MIT isn't specified.

Fixed

> Uscan works for me as well, mentors.debian.net has a broken check indeed.

Good to hear :)

> debian/control: Please add Vcs-Git. To specify the branch, see
Policy[1] §5.6.26.

Fixed

> Typo in Description: ubiquotious->ubiquitous.

Fixed (actually not a typo, silly me couldn't  spell it).

> debian/ddupdate-docs.docs: There is no "ddupdate-docs" binary package
so this file
> doesn't do anything[3], please remove.

Fixed

> debian/README.debian: Typo: updatet->updated.

Fixed

> I think Debian should be capitalized as a proper noun in user
documentation.

Right, fixed

> debian/rules:
> Debhelper has picked Makefile instead of setup.py, so you should add
> "--buildsystem=pybuild" after the --with arguments. Then you can
remove override_dh_build,
> override_dh_auto_install and override_dh_python3 rules, and delete the
file debian/install.

However, this is on purpose. I control upstream, and the Makefile
actually does the right things. Is there anything wrong with this approach?

That said, rules is in a much better shape since the review, cleaned up
and with a dh_override_missing added.

> However, this causes that every file that setup.py installs goes into
the package.
> To control what gets installed, you can add something like this to
debian/rules:
> override_dh_install:
> dh_install
> rm debian/ddupdate/usr/share/doc/ddupdate/CONTRIBUTE.md \
> debian/ddupdate/usr/share/doc/ddupdate/LICENSE.txt

This is fixed upstream (which used to install these files, one of my
really bad ideas).

> The installed package is missing some Depends: "ModuleNotFoundError:
No module named 'straight'".

Recent dependencies  for the .deb package looks ok to me. Note that the
straight.plugin and sudo deps have been dropped by upstream.

Cheers!
--alec

Bug#889570: RFS: libt3window/0.3.0-1

2018-02-04 Thread Adam Borowski

On Sun, Feb 04, 2018 at 04:57:49PM +0100, Gertjan Halkes wrote:
> * Package name: libt3window
>   Version : 0.3.0-1

>   
> https://mentors.debian.net/debian/pool/main/libt/libt3key/libt3window_0.3.0-1.dsc

Obviously /libt3window/.

> Changes since the last upload:
> 
>   * New upstream release.
> 
> The new upstream release improves line drawing, updates internal tables
> to Unicode 10.0 and fixes some small bugs.

Alas, the changelog looks mangled:

diff -Nru libt3window-0.2.6/debian/changelog libt3window-0.3.0/debian/changelog
--- libt3window-0.2.6/debian/changelog  2017-12-30 09:35:12.0 +0100
+++ libt3window-0.3.0/debian/changelog  2018-02-04 13:25:17.0 +0100
@@ -1,11 +1,11 @@
-libt3window (0.2.6-1) unstable; urgency=low
+libt3window (0.3.0-1) unstable; urgency=low
 
   * New upstream release.
 
- -- Gertjan Halkes   Sat, 30 Dec 2017 09:35:12 +0100
+ -- Gertjan Halkes   Sun, 04 Feb 2018 13:25:17 +0100
 
-libt3window (0.2.5-1) unstable; urgency=low
+libt3window (0.2.6-1) unstable; urgency=low
 
   * Initial release. (Closes: #885597)
 
- -- Gertjan Halkes   Thu, 28 Dec 2017 17:43:24 +0100
+ -- Gertjan Halkes   Sat, 30 Dec 2017 09:35:12 +0100


I see nothing wrong in the actual contents of the package, though.


Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ The bill with 3 years prison for mentioning Polish concentration
⣾⠁⢰⠒⠀⣿⡁ camps is back.  What about KL Warschau (operating until 1956)?
⢿⡄⠘⠷⠚⠋⠀ Zgoda?  Łambinowice?  Most ex-German KLs?  If those were "soviet
⠈⠳⣄ puppets", Bereza Kartuska?  Sikorski's camps in UK (thanks Brits!)?

Bug#884987: reworked patch from Redhat's bugzilla

2018-02-04 Thread Sanjoy Mahajan

> But the patch there doesn't apply to the Debian
> /etc/etckeeper/pre-commit.d/20warn-problem-files

But the following reworked version of the patch does apply.  It has
fixed the problem for me.

--- etc/etckeeper/pre-commit.d/20warn-problem-files	2016-07-18 01:01:39.0 +0200
+++ etc/etckeeper/pre-commit.d/20warn-problem-files	2017-08-12 10:36:13.360410731 +0200
@@ -1,19 +1,20 @@
 #!/bin/sh
 set -e
 
-exclude_internal () {
-	egrep -v '(^|/)(\.git|\.hg|\.bzr|_darcs)/'
-}
+# (Note that when using this, the find expression must end with 
+# -print or -exec, else the excluded directories will actually be
+# printed!)
+NOVCS='. -path ./.git -prune -o -path ./.bzr -prune -o -path ./.hg -prune -o -path ./_darcs -prune -o'
 
 if [ "$VCS" = bzr ] || [ "$VCS" = darcs ]; then
-	special=$(find . ! -type d ! -type f ! -type l | exclude_internal) || true
-	hardlinks=$(find . -type f ! -links 1 | exclude_internal ) || true
+	special=$(find $NOVCS ! -type d ! -type f ! -type l -print) || true
+	hardlinks=$(find $NOVCS -type f ! -links 1 -print) || true
 elif [ "$VCS" = hg ]; then
-	special=$(find . ! -type d ! -type f ! -type l | exclude_internal) || true
-	hardlinks=$(find . -type f ! -links 1 -exec hg status {} \; | exclude_internal ) || true
+	special=$(find $NOVCS ! -type d ! -type f ! -type l -print) || true
+	hardlinks=$(find $NOVCS -type f ! -links 1 -exec hg status {} \; -print) || true
 elif [ "$VCS" = git ]; then
-	special=$(find . ! -type d ! -type f ! -type l -exec git ls-files --exclude-standard --cached --others {} + | exclude_internal) || true
-	hardlinks=$(find . -type f ! -links 1 -exec git ls-files --exclude-standard --cached --others {} + | exclude_internal) || true
+	special=$(find $NOVCS ! -type d ! -type f ! -type l -exec git ls-files --exclude-standard --cached --others {} + -print) || true
+	hardlinks=$(find $NOVCS -type f ! -links 1 -exec git ls-files --exclude-standard --cached --others {} + -print) || true
 else
 	special=""
 fi

Bug#844125: dgit: Built-in support for pbuilder [and 1 more messages]

2018-02-04 Thread Sean Whitton

Hello,

On Mon, Jan 29 2018, Ian Jackson wrote:

> Mattia Rizzolo writes ("Bug#844125: dgit: Built-in support for
>pbuilder [and 1 more messages]"):
>> [lots of explanation]
>
> Thanks, that is very helpful information.

Indeed.  Many thanks.

>> Anyway, isn't this discussion kind of moot?  I understood that for
>> reasons you're thinking of specifying `--debbuiltopts -b`, so you'd
>> get a binary only build and that one would discard the .orig as well
>> (as with -b the source don't appear on the .changes at all).
>
> Yes, well, technically it is moot for supporting pbuilder as a dgit
> build option.  But I think gbp users will probably want
> --build--products-dir more often than eg sbuild users, so proper
> pbuilder support means fixing #863582 (that --b-p-d does not always
> work properly) and #857316 (that it is not configurable).

Not fixing #863582 will make `dgit pbuilder` very confusing; on the
other hand, not fixing #857316 just makes it inconvenient.  So I think
this bug is blocked by only the former (as indeed the BTS metadata says
ATM).

> It might be necessary for dgit to override some of the user's pbuilder
> config.  (And, as I said in my other mail, it might also be desirable
> for dgit to interrogate the pbuilder config so that it can honour it.)

Like Mattia, I'm very queasy about this, because pbuilder's config is
not declarative.  Indeed, everything seems to be shell scripts.

I haven't yet read your older mail where you came to the conclusion that
it would be necessary for dgit to parse pbuilder's config, but we should
be really sure it's necessary before going for that.

On Mon, Jan 29 2018, Mattia Rizzolo wrote:

> Then, there are other gotchas, that make the whole "ask pbuilder what
> its configuration is" kind of pointless: pbuilderrc is a shell script
> and therefore interpreted at runtime.  If a user wants to (I do for
> some things) it can compute values according to what I've been asked
> to do, so for example somebody may have options with different values
> according to what subcommand is being run.  But I believe this is very
> similar for sbuild as well, isn't it?

sbuild uses shell scripts to add things like tmpfs usage to the build,
but its configuration is a mixture of perl and ini, not shell.  So the
situation is slightly better.

-- 
Sean Whitton

signature.asc
Description: PGP signature

Bug#886278: Unable to open Audio Disc

2018-02-04 Thread Jack Underwood

Okay, I have just done some more online research and I have found this bug 
relating to libcdio:
https://www.mail-archive.com/ubuntustudio-bugs@lists.launchpad.net/msg06384.html

I don't know enough to make a guess as to whether this exists as the same 
double-free bug,
but if so, then the problem lies with libcdio, and the fixed version was 
uploaded to experimental
just a few days ago.


Best,
Jack

Bug#889528: mpv: Reading bluray using mpv fails

2018-02-04 Thread James Cowgill

Control: tags -1 confirmed

Hi,

On 04/02/18 19:32, mahashakti89 wrote:
> On Sun, Feb 04, 2018 at 04:53:24PM +0100, James Cowgill wrote:
>> On 04/02/18 16:46, James Cowgill wrote:
>>> Hi,
>>>
>>> On 04/02/18 09:38, mahashakti89 wrote:
 Package: mpv
 Version: 0.27.0-3
 Severity: important

 Dear Maintainer,

 I am using smplayer to read blurays - choosen multimedia engine is
 mpv - but it
 fails with following message :

 Playing: br:media/toto/cdrom0
 No protocol handler found to open URL br:media/toto/cdrom0
 The protocol is either unsupported, or was disabled at compile-time.
>>>
>>> mpv uses a slightly different "bd" protocol instead of "br". Try this:
>>>  mpv br:// --bluray-device=/media/toto/cdrom0
>>
>> Err this of course should be:
>> mpv bd:// --bluray-device=/media/toto/cdrom0
> 
> Hi,
> mpv bd:// --bluray-device=/media/cdrom0
> Error parsing option bluray-device (option not found)
> Setting commandline option --bluray-device=/media/cdrom0 failedi.
> 
> Extract of the mount command
> 
> gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse
> (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
> fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
> /dev/sdg1 on /media/toto/PATRIOT2 type fuseblk
> (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096,uhelper=udisks2)
> 
> /dev/sr0 on /media/cdrom0 type udf
> (ro,nosuid,nodev,noexec,relatime,utf8,user)
> 
> Till then mpv worked fairly well with playing blurays.

After looking a bit more closely, mpv isn't pulling in libbluray at all.
The build log contains:> Checking for Bluray support
  : no ('libbluray >= 0.3.0' not found)

I'll try and see why it's not detecting the library.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#889585: smartmontools: Warn on high load cycle count (193) by default, especially on WD Green drives

2018-02-04 Thread Felix Lechner

Package: smartmontools
Version: 6.5+svn4324-1
Severity: wishlist

Hi,

Some time ago I received a replacement WD Green drive via RMA and forgot to set
the power settings. By default, those drives park heads after 8 seconds[1], but
that can easily be changed with a tools like 'idle3-tools'[2]. When I realized
my error a year later, the drive had more than 421,000 cycles. It is rated for
500,000 or so.

It would be nice if smartd's default configuration could send a brief warning
when attribute 193 (load cycle count) advances too quickly. I don't remember
the initial count on the refurbished drive and unfortunately cannot make a good
suggestion, but it should probably be something like 50,000 or lower in less
than a year. Thank you!

Best regards,
Felix

[1] hdparm(8), see description of '-J'
[2] http://idle3-tools.sourceforge.net/



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

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

Versions of packages smartmontools depends on:
ii  debianutils  4.8.4
ii  init-system-helpers  1.51
ii  libc62.26-4
ii  libcap-ng0   0.7.7-3.1+b1
ii  libgcc1  1:7.2.0-19
ii  libselinux1  2.7-2+b1
ii  libstdc++6   7.2.0-19
ii  lsb-base 9.20170808

Versions of packages smartmontools recommends:
ii  mailutils [mailx]  1:3.4-1

Versions of packages smartmontools suggests:
ii  gsmartcontrol   1.1.3-1
ii  smart-notifier  0.28-5

-- no debconf information

Bug#889511: libpodofo: CVE-2018-5295

2018-02-04 Thread Mattia Rizzolo

Control: forwarded -1 https://sourceforge.net/p/podofo/mailman/message/36215539/

On Sun, Feb 04, 2018 at 01:24:53AM +0100, Matthias Brinke wrote:
> CVE-2018-5295 from the security-tracker.debian.org:
> In PoDoFo 0.9.5, there is an integer overflow in
> the PdfXRefStreamParserObject::ParseStream function
> (base/PdfXRefStreamParserObject.cpp). Remote attackers
> could leverage this vulnerability to cause a denial-of-service
> via a crafted pdf file.

Right.
For cross-reference, this is being dealt upstream by this thread that
started the 6th of Jan:
https://sourceforge.net/p/podofo/mailman/message/36180168/

> I've implemented a patch to fix this vulnerability, it is attached
> and tested

Thank you!
I've forwarded it upstream, see the first url above.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#889590: tesseract-ocr-aze has circular Depends on tesseract-ocr-aze-cyrl

2018-02-04 Thread Bill Allombert

Package: tesseract-ocr-aze
Version: 4.00~git15-45ed289-5
Severity: important

Hello Jeff,

There is a circular dependency between tesseract-ocr-aze and 
tesseract-ocr-aze-cyrl:

tesseract-ocr-aze   :Depends: tesseract-ocr-aze-cyrl (>= 3.99)
tesseract-ocr-aze-cyrl  :Depends: tesseract-ocr-aze (>= 3.99)

Circular dependencies are known to cause problems during upgrade between
stable releases, 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#889592: lintian: false positive for override_dh_auto_test-does-not-check-DEB_BUILD_PROFILES

2018-02-04 Thread Mattia Rizzolo

Package: lintian
Version: 2.5.73

On Sun, Feb 04, 2018 at 03:36:45PM +0530, Chris Lamb wrote:
> Some results coming in:
> 
>   
> https://lintian.debian.org/tags/override_dh_auto_test-does-not-check-DEB_BUILD_PROFILES.html
> 
> Thoughts?

Randomly checked few packages and they were mostly all fpos:

https://tracker.debian.org/media/packages/a/aff4/rules-0.24.post1-3
Ok, this is crazy, he deserves what he got for being too clever with
make :D

https://tracker.debian.org/media/packages/a/autoconf-dickey/rules-2.52%2B20170501-2
https://tracker.debian.org/media/packages/a/avro-c/rules-1.8.2-1
Not sure why this is matched, I thought it wouldn't have been:
|override_dh_auto_test:
|   dh_auto_test --no-parallel

https://tracker.debian.org/media/packages/libx/libxcb/rules-1.12-1
Similar to the previous:
|override_dh_auto_test:
|   dh_auto_test -- VERBOSE=1

https://tracker.debian.org/media/packages/o/osm2pgsql/rules-0.94.0%2Bds-1
Also similar:
|override_dh_auto_test:
|   dh_auto_test || echo "Ignoring test failures"

https://tracker.debian.org/media/packages/a/akonadi-calendar-tools/rules-417.08.3-2
https://tracker.debian.org/media/packages/b/biosig4c%2B%2B/rules-1.4.1-1.1
This seems to be a recurring pattern:
|override_dh_auto_test:
|   # Disable dh_auto_test at build time
|   :

https://tracker.debian.org/media/packages/b/bibletime/rules-2.11.1-1
I believe this is going the be another recurring pattern:
|override_dh_auto_test:
|   echo "Skip dh_auto_test because the tests rely on a display which is 
not there"


Whilst true that the last two technically should deal with
DEB_BUILD_OPTIONS=nocheck, I believe running a single `:` or a single
`echo` should be considered fine.


In my random pick, I saw this real positive:
https://tracker.debian.org/media/packages/l/lua-lgi/rules-0.9.2-1
|override_dh_auto_test:
|   make -C tests all
|   GI_TYPELIB_PATH=tests LD_LIBRARY_PATH=tests xvfb-run dh_auto_test
I recommend to add a similar thing to the testsuite, as this one is
*also* calling dh_auto_test, but it should still handle
DEB_BUILD_OPTIONS=nocheck by hand.

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature

Bug#889567: cloning 889006, reassign 889006 to dpatch ...

2018-02-04 Thread Adrian Bunk

On Sun, Feb 04, 2018 at 03:17:33PM +, Niels Thykier wrote:
> clone 889006 -1
> reassign 889006 dpatch 
> retitle -1 debhelper,dh-autoreconf: Handle backports for quilt.pm users
> thanks

Is there a reason against doing
  reassign 889567 dh-autoreconf 16
  retitle 889567 dh-autoreconf needs Breaks: quilt (<< 0.63-8.2~)
?

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#889546: r-cran-reshape2: [INTL:de] Initial German translation

2018-02-04 Thread Andreas Tille

Hi,

On Sun, Feb 04, 2018 at 12:37:23PM +0100, Chris Leick wrote:
> Package: r-cran-reshape2
> Version: R 2.15.1
> Severity: wishlist
> Tags: l10n patch
> 
> please find attached the German translation.

There is no translation attached and in general I wonder what
exactly do you intend to translate in this package.

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#888829: wpad-extract broken on stretch

2018-02-04 Thread Wolfgang Schweer

> On Sun, Feb 04, 2018 at 04:39:43PM +, Mike Gabriel wrote:
> > Do you see any other issues that we should fix with such a proposed-update?
> > Only changes / fixes that are not too invasive.
>  
> Fixing smb.conf would require to add only one line. Fixed in Buster, see
 
d-e-c commit 3fdd5748ca6a0ea09e4d3c78ab04284d22b76ea2

Wolfgang


signature.asc
Description: PGP signature

Bug#888282:

2018-02-04 Thread ziegler


Today things are back to normal.

I updated quite a few testing-packets 
since yesterday. I do not know, which of them was 
responsible for the change, sorry.


thanks,
Martin

Bug#889486: Please check for packages named "dh-*" in binary-package-depends-on-toolchain-package

2018-02-04 Thread Josh Triplett

On Sun, Feb 04, 2018 at 02:28:35PM +0530, Chris Lamb wrote:
> Thanks. :)  Fixed in Git, pending upload:
> 
>   
> https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=f8d52f6db1309feb076c938923518e7e323e46d8

Thanks!

- Josh Triplett

Bug#889144: stricter PIDfile handling breaks several daemons

2018-02-04 Thread Sven Hartge

On 04.02.2018 17:25, Michael Biebl wrote:
> Am 03.02.2018 um 14:35 schrieb Sven Hartge:
>> Um 14:00 Uhr am 03.02.18 schrieb Michael Biebl:

>>> The alternative afaics would be, that the daemon writes the pid file as
>>> munin:munin then (or ulog:ulog for the above case).
>>
>> No, this would open a potential DoS vector.
>>
>> Image an attacker gaining access to the munin user. He would then be able
>> to write any PID to the PIDfile and the init system would kill the other
>> process when the munin-node service is stopped/restarted.
>>
> 
> I don't think this applies to systemd though. If the process id listed
> in the pid file is not found in the service cgroup, systemd should not
> kill the process listed in the pid file. I suspect that MainPID will not
> be properly set and systemd will complain about it.

But it applies to SysV-Init. If the init-script does not use
start-stop-daemon correctly to check if the PID in the PIDfile belongs
to the executable to be killed or if the init-script uses some other
method of killing the daemon, it might easily kill a different program.

I know, this is not systemds concern whether other init implementations
behave correctly, but if you change the behaviour of a program because
of a behaviour change in systemd and then break other init systems or
increase the insecurity when used with other init systems because of
this, it will fall back negatively on systemd.

Grüße,
Sven.

signature.asc
Description: OpenPGP digital signature

Bug#889181: cacti changes for PHP7.2 and dep8 tests

2018-02-04 Thread Nish Aravamudan

Hi Paul,

On Feb 4, 2018 04:38, "Paul Gevers"  wrote:

Hi Nishanth,

Thanks for the report and the work with upstream to get this fixed.

On 03-02-18 07:25, Nishanth Aravamudan wrote:
> In Ubuntu, the attached patch was applied to achieve the following:
>
>   * debian/patches/php72_count_bc_changes.patch: PHP7.2 has deprecated
> count() of non-Countable objects.
>   * debian/patches/update-cactisql.patch: Update cacti.sql for
> readstring to community change.

I'll most likely just wait for the next upstream release, which I expect
to come soon (they release about every other week).

Sure, I was not aware of cacti's release schedule and we are moving to 7.2
for 18.04, so just wanted you to be aware. I will sync the update once I
see it from Debian.

> Note that even with this change, the DEP8 tests fail on Ubuntu 18.04,
> with:
>
> Unexpected output in /var/log/cacti/cacti.log:
> 02/02/2018 16:40:07 - AUTOM8 ERROR: The Network ID: 1 is disabled. You
must use the 'force' option to force it's execution.
>
> Which I think might be because we need to pass force to some URL or
> check a network enabled box in the script?

If I understood upstream correctly about this issue, we should just add
the line to the accepted output.

Yeah, that is what I will do in our delta, and then it should be part of
the sync if you make the same change.

-Nish

Paul

Bug#889563: linphone: Wrong contact list sort order

2018-02-04 Thread Geert Stappers

On Sun, Feb 04, 2018 at 03:52:02PM +0100, Rob van der Putten wrote:
> 
> Linphone sorts contacts by username (EG: ) as
> opposed to display_name (EG: "John Doe").

SIP usernames are global unique, display_names not.

SIP username is always present, display_name is optional.

> Below a small patch by a friend which fixes this problem;

Patch has been seen (at least by me)

But I don't understand the "problem".  Please elaborate.

Groeten
Geert Stappers
-- 
Leven en laten leven

Bug#889493: tech-ctte: Please review if systemd is reliable enough to be the default

2018-02-04 Thread Kingsley G. Morse Jr.

Hi Phil,

I find I often benefit from other people's point
of view.

If you happen to have the time, and are so
inclined, and it would be comfortable, feel free
to elaborate on your comment in bug report #889493.

I'm particularly curious why you wrote it had no
merit.

So,
Kingsley

-- 
Time is the fire in which we all burn.

Bug#888917: ocrmypdf fails to run it's testsuite

2018-02-04 Thread Sean Whitton

Hello,

On Fri, Feb 02 2018, James R Barlow wrote:

> Do you think you could take a few minutes to identify which test is
> taking this long and report it? This may be an upstream bug, if some
> input triggers an infinite loop.
>
> I have my suspicions. [...]

Thanks for the hints.  I will attempt to reproduce the hang at some
point in the next few weeks, and report back, with an upstream bug
report if I can pinpoint the issue.

-- 
Sean Whitton

signature.asc
Description: PGP signature

Bug#855942: Beta version of Anki has been available since July 2017

2018-02-04 Thread Julian Gilbey

Update on this bug: the beta version of anki is currently in unstable,
but upstream has explicitly requested that it not be packaged for
distributions until a new stable version has been released.  So I will
leave this bug report open until then.

   Julian

Bug#889576: sslh: Please package new upstream release

2018-02-04 Thread Axel Beckert

Package: sslh
Version: 1.18-1

Hi,

there have been two new upstream versioned released in the past
weeks. please package the new upstream version (1.19b as of this
writing) which introduces quite some new features like support for SNI,
etc. and a "truckload of bug fixes and documentation improvements".

TIA!

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (980, 'unstable-debug'), (600, 'testing'), 
(111, 'buildd-unstable'), (111, 'buildd-experimental'), (110, 'experimental'), 
(105, 'experimental-debug')
Architecture: amd64 (x86_64)

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

Bug#889559: wavpack: heap buffer overflow while running wavpack

2018-02-04 Thread Sebastian Ramacher

Hi

On 2018-02-04 23:35:47, Joonun Jang wrote:
> Package: wavpack
> Version: 5.1.0-2
> Severity: important
> Tags: security
> 
> heap buffer overflow running wavpack with "-y poc.wav" option

Thanks for filing this. It's probably easier to file those directly upstream at
https://github.com/dbry/WavPack. I have forwarded the other two bug reports
there.

Cheers

> 
> Running 'wavpack -y poc.wav' with the attached file raises heap buffer 
> overflow
> which may allow a remote attacker to cause unspecified impact including 
> denial-of-service attack
> I expected the program to terminate without segfault, but the program crashes 
> as follow
> 
> june@june:~/temp/report/wavpack/9776$ 
> ../../binary/wavpack-5.1.0/cli/.libs/wavpack -y poc.wav
> 
>  WAVPACK  Hybrid Lossless Audio Compressor  Linux Version 5.1.0
>  Copyright (c) 1998 - 2017 David Bryant.  All Rights Reserved.
> 
> creating 
> poc.wv,=
> ==3834==ERROR: AddressSanitizer: heap-buffer-overflow on address 
> 0x6020ef91 at pc 0x76e8105b bp 0x7fffb2e0 sp 0x7fffaa90
> READ of size 2 at 0x6020ef91 thread T0
> #0 0x76e8105a  (/usr/lib/x86_64-linux-gnu/libasan.so.3+0x4305a)
> #1 0x5557ad85 in ParseDsdiffHeaderConfig 
> /home/june/temp/report/binary/wavpack-5.1.0/cli/dsdiff.c:171
> #2 0x55567c3a in pack_file 
> /home/june/temp/report/binary/wavpack-5.1.0/cli/wavpack.c:1774
> #3 0x55565e5e in main 
> /home/june/temp/report/binary/wavpack-5.1.0/cli/wavpack.c:1270
> #4 0x765902b0 in __libc_start_main 
> (/lib/x86_64-linux-gnu/libc.so.6+0x202b0)
> #5 0x555609a9 in _start 
> (/home/june/temp/report/binary/wavpack-5.1.0/cli/.libs/wavpack+0xc9a9)
> 
> 0x6020ef91 is located 0 bytes to the right of 1-byte region 
> [0x6020ef90,0x6020ef91)
> allocated by thread T0 here:
> #0 0x76effd28 in malloc 
> (/usr/lib/x86_64-linux-gnu/libasan.so.3+0xc1d28)
> #1 0x5557ac4a in ParseDsdiffHeaderConfig 
> /home/june/temp/report/binary/wavpack-5.1.0/cli/dsdiff.c:156
> #2 0x55567c3a in pack_file 
> /home/june/temp/report/binary/wavpack-5.1.0/cli/wavpack.c:1774
> #3 0x55565e5e in main 
> /home/june/temp/report/binary/wavpack-5.1.0/cli/wavpack.c:1270
> #4 0x765902b0 in __libc_start_main 
> (/lib/x86_64-linux-gnu/libc.so.6+0x202b0)
> 
> SUMMARY: AddressSanitizer: heap-buffer-overflow 
> (/usr/lib/x86_64-linux-gnu/libasan.so.3+0x4305a)
> Shadow bytes around the buggy address:
>   0x0c047fff9da0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
>   0x0c047fff9db0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
>   0x0c047fff9dc0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
>   0x0c047fff9dd0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
>   0x0c047fff9de0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
> =>0x0c047fff9df0: fa fa[01]fa fa fa fd fd fa fa 03 fa fa fa 00 fa
>   0x0c047fff9e00: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
>   0x0c047fff9e10: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
>   0x0c047fff9e20: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
>   0x0c047fff9e30: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
>   0x0c047fff9e40: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
> Shadow byte legend (one shadow byte represents 8 application bytes):
>   Addressable:   00
>   Partially addressable: 01 02 03 04 05 06 07
>   Heap left redzone:   fa
>   Heap right redzone:  fb
>   Freed heap region:   fd
>   Stack left redzone:  f1
>   Stack mid redzone:   f2
>   Stack right redzone: f3
>   Stack partial redzone:   f4
>   Stack after return:  f5
>   Stack use after scope:   f8
>   Global redzone:  f9
>   Global init order:   f6
>   Poisoned by user:f7
>   Container overflow:  fc
>   Array cookie:ac
>   Intra object redzone:bb
>   ASan internal:   fe
>   Left alloca redzone: ca
>   Right alloca redzone:cb
> ==3834==ABORTING
> 
> This bug was found with a fuzzer developed by 'SoftSec' group at KAIST
> 
> -- System Information:
> Debian Release: 9.3
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), 
> (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 4.9.0-3-amd64 (SMP w/1 CPU core)
> 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)
> 
> Versions of packages wavpack depends on:
> ii  libc62.24-11+deb9u1
> ii  libwavpack1  5.1.0-2
> 
> wavpack recommends no packages.
> 
> wavpack suggests no packages.
> 
> -- no debconf information


> ___
> pkg-multimedia-maintainers mailing list
> pkg-multimedia-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers


-- 
Sebastian

Bug#887828: needrestart: Possible false positive on postifx and wazuh-agent running in LXC container

2018-02-04 Thread Chris

Hi,
On 03.02.2018 23:26, Thomas Liske wrote:
> Hi,

thanks for your reply.

> you are running needrestart outside of the container?

The posted outputs are from running needrestart within the container.
Sorry that i havn't clarified this from the beginning of my post.

> And the postfix service name looks suspicious. Could you
> please provide the content of /proc/$PID/cgroup of the postfix's master
> service?

This is the output of the various content of each detected PID cgroup
within the container:

[main] #338 uses non-existing /var/ossec/bin/ossec-agentd
[main] #338 is not a child
[main] #25460 uses non-existing /usr/lib/postfix/sbin/pickup
[main] #25460 is a child of #430
[main] #338 exe => /var/ossec/bin/ossec-agentd
[main] #338 is wazuh-agent.service
[main] #430 exe => /usr/lib/postfix/sbin/master
[main] #430 is postfix@-.service


cat /proc/338/cgroup
-

12:cpuset:/
11:hugetlb:/
10:perf_event:/
9:blkio:/
8:net_cls,net_prio:/
7:memory:/
6:rdma:/
5:cpu,cpuacct:/
4:freezer:/
3:pids:/system.slice/wazuh-agent.service
2:devices:/system.slice/wazuh-agent.service
1:name=systemd:/system.slice/wazuh-agent.service


cat /proc/25460/cgroup
--

12:cpuset:/
11:hugetlb:/
10:perf_event:/
9:blkio:/
8:net_cls,net_prio:/
7:memory:/
6:rdma:/
5:cpu,cpuacct:/
4:freezer:/
3:pids:/system.slice/system-postfix.slice/postfix@-.service
2:devices:/system.slice/system-postfix.slice
1:name=systemd:/system.slice/system-postfix.slice/postfix@-.service

cat /proc/430/cgroup


12:cpuset:/
11:hugetlb:/
10:perf_event:/
9:blkio:/
8:net_cls,net_prio:/
7:memory:/
6:rdma:/
5:cpu,cpuacct:/
4:freezer:/
3:pids:/system.slice/system-postfix.slice/postfix@-.service
2:devices:/system.slice/system-postfix.slice
1:name=systemd:/system.slice/system-postfix.slice/postfix@-.service


As you have mentioned cgroups i'm also getting the following output from
the postfix services within the containers:

Jan 28 15:51:51 example systemd[1]: postfix.service: Failed to reset
devices.list: Operation not permitted
Jan 28 15:51:51 example systemd[1]: postfix.service: Failed to set
invocation ID on control group /system.slice/postfix.service, ignoring:
Operation not permitted

Not sure if this is related here.

> Thanks,
> Thomas
> 
> 
> Chris  writes:
> 
>> Package: needrestart
>> Version: 2.11-3
>> Severity: normal
>>
>> Dear Maintainer,
>>
>> having Postfix and the wazuh-agent package from [1] on a current Debian
>> Stretch 9.3 running within an LXC container shows the following services
>> as required for a restart even if the services, the container or the
>> host was freshly restarted:
>>
>> postfix@-.service
>> wazuh-agent.service
>>
>> Running needrestart with the -v parameter shows this output:
>>
>> [main] eval /etc/needrestart/needrestart.conf
>> [main] needrestart v2.11
>> [main] running in root mode
>> [Core] Using UI 'NeedRestart::UI::stdio'...
>> [main] detected systemd
>> [main] #372 uses non-existing /var/ossec/bin/ossec-agentd
>> [main] #372 is not a child
>> [main] #1047 uses non-existing /usr/lib/postfix/sbin/pickup
>> [main] #1047 is a child of #438
>> [main] #372 exe => /var/ossec/bin/ossec-agentd
>> [main] #372 is wazuh-agent.service
>> [main] #438 exe => /usr/lib/postfix/sbin/master
>> [main] #438 is postfix@-.service
>> [Kernel] Linux: kernel release 4.13.13-5-pve, kernel version #1 SMP PVE 
>> 4.13.13-36 (Mon, 15 Jan 2018 12:36:49 +0100)
>> [Kernel/Linux] Did not find any linux images.
>> Failed to retrieve available kernel versions.
>> Restarting services...
>> Services to be restarted:
>> Restart «postfix@-.service»? [Ynas?] n
>> Restart «wazuh-agent.service»? [Ynas?] n
>> Services being skipped:
>>  systemctl restart postfix@-.service
>>  systemctl restart wazuh-agent.service
>> No containers need to be restarted.
>> No user sessions are running outdated binaries.
>>
>> The two mentioned binaries which doesn't exist according to needrestart
>> output are there and accessible:
>>
>> ls -la /var/ossec/bin/ossec-agentd
>>
>> -rwxr-x--- 1 root root 528136 Dez 22 18:59 /var/ossec/bin/ossec-agentd
>>
>> ls -la /usr/lib/postfix/sbin/pickup
>>
>> -rwxr-xr-x 1 root root 14408 Sep 27 06:56 /usr/lib/postfix/sbin/pickup
>>
>> ls -la 
>>
>> Not sure what causes this behavior. If there are any additional info i
>> could / need to provide please let me know.
>>
>> Thanks,
>>
>> [1] 
>> https://documentation.wazuh.com/current/installation-guide/installing-wazuh-agent/wazuh_agent_deb.html
>

Bug#889551: spectre-meltdown-checker should be in /usr/sbin/respect-meltdown-checker

2018-02-04 Thread Sylvestre Ledru

Hello,

Le 04/02/2018 à 13:56, shirish शिरीष a écrit :
> Package: spectre-meltdown-checker
> Version: 0.32-1
> Severity: normal
>
> Dear Maintainer,
>
> I was trying to run spectre-meltdown-checker as a normal user first -
>
> /home/shirish> spectre-meltdown-checker
> Spectre and Meltdown mitigation detection tool v0.32
>
> Note that you should launch this script with root privileges to get
> accurate information.
> We'll proceed but you might see permission denied errors.

I had the feeling that a bunch of non-root information are still
interesting and relevant.

This is why I put it in /usr/bin/

S

Bug#888348: lives: FTBFS with FFmpeg 3.5

2018-02-04 Thread salsaman

I believe all the issues noted should be fixed now. You will need to
replace the follwoing files:
configure.ac
libweed/weed-compat.h
libweed/weed-compat.pc
plugins/decoders/*

(the weed-compat changes are unrelated, but you will need to update them to
compile the current decoder plugins).

1 2 3 >

1 - 100 of 242 matches

Mail list logo