Bug#865400: easytag: [Process Field] "Capitalize the first letter of each word" broken

[Federico]

Package: easytag
Version: 2.4.3-1
Severity: normal

Dear Maintainer,

In the new version of easytag shipped with Debian 9, the "Capitalize the first
letter of each word" is broken.
Every word of a field should be capitalised, which is not happening anymore.
Example, instead of Flight Of Icarus, you obtain Flight of Icarus.

You can easily compare the expected behaviour with a previous version of
easytag (ex 2.2.4).

Do you mind fixing the issue?

Best regards,

F.M.



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

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

Versions of packages easytag depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  libc62.24-11+deb9u1
ii  libflac8 1.3.2-1
ii  libgcc1  1:6.3.0-18
ii  libgdk-pixbuf2.0-0   2.36.5-2
ii  libglib2.0-0 2.50.3-2
ii  libgtk-3-0   3.22.11-1
ii  libid3-3.8.3v5   3.8.3-16.2+b1
ii  libid3tag0   0.15.1b-12
ii  libogg0  1.3.2-1
ii  libopus0 1.2~alpha2-1
ii  libopusfile0 0.8-1+b1
ii  libspeex11.2~rc1.2-1+b2
ii  libstdc++6   6.3.0-18
ii  libtag1v51.11.1+dfsg.1-0.1
ii  libvorbis0a  1.3.5-4
ii  libvorbisfile3   1.3.5-4
ii  libwavpack1  5.0.0-2

Versions of packages easytag recommends:
ii  gnome-icon-theme  3.12.0-2
ii  gvfs  1.30.4-1
ii  yelp  3.22.0-1

Versions of packages easytag suggests:
pn  easytag-nautilus  

-- no debconf information

Bug#865399: libghc-cabal-dev and ghc: error when trying to install together

[Ralf Treinen]

Package: ghc,libghc-cabal-dev
Version: ghc/8.0.2-1
Version: libghc-cabal-dev/1.24.2.0-1+b1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2017-06-21
Architecture: amd64
Distribution: sid

Hi,

automatic installation tests of packages that share a file and at the
same time do not conflict by their package dependency relationships has
detected the following problem:



Extracting templates from packages: 78%
Extracting templates from packages: 100%
Selecting previously unselected package gcc-6-base:amd64.
(Reading database ... 11004 files and directories currently installed.)
Preparing to unpack .../gcc-6-base_6.3.0-18_amd64.deb ...
Unpacking gcc-6-base:amd64 (6.3.0-18) ...
Selecting previously unselected package libgmp10:amd64.
Preparing to unpack .../libgmp10_2%3a6.1.2+dfsg-1_amd64.deb ...
Unpacking libgmp10:amd64 (2:6.1.2+dfsg-1) ...
Selecting previously unselected package libisl15:amd64.
Preparing to unpack .../libisl15_0.18-1_amd64.deb ...
Unpacking libisl15:amd64 (0.18-1) ...
Selecting previously unselected package libmpfr4:amd64.
Preparing to unpack .../libmpfr4_3.1.5-1_amd64.deb ...
Unpacking libmpfr4:amd64 (3.1.5-1) ...
Selecting previously unselected package libmpc3:amd64.
Preparing to unpack .../libmpc3_1.0.3-1+b2_amd64.deb ...
Unpacking libmpc3:amd64 (1.0.3-1+b2) ...
Selecting previously unselected package cpp-6.
Preparing to unpack .../cpp-6_6.3.0-18_amd64.deb ...
Unpacking cpp-6 (6.3.0-18) ...
Selecting previously unselected package cpp.
Preparing to unpack .../cpp_4%3a6.3.0-4_amd64.deb ...
Unpacking cpp (4:6.3.0-4) ...
Selecting previously unselected package gcc-7-base:amd64.
Preparing to unpack .../gcc-7-base_7.1.0-7_amd64.deb ...
Unpacking gcc-7-base:amd64 (7.1.0-7) ...
Processing triggers for libc-bin (2.24-12) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up gcc-7-base:amd64 (7.1.0-7) ...
(Reading database ... 11063 files and directories currently installed.)
Preparing to unpack .../libgcc1_1%3a7.1.0-7_amd64.deb ...
Unpacking libgcc1:amd64 (1:7.1.0-7) over (1:4.8.2-19) ...
Processing triggers for libc-bin (2.24-12) ...
Setting up libgcc1:amd64 (1:7.1.0-7) ...
Processing triggers for libc-bin (2.24-12) ...
(Reading database ... 11063 files and directories currently installed.)
Preparing to unpack .../libstdc++6_7.1.0-7_amd64.deb ...
Unpacking libstdc++6:amd64 (7.1.0-7) over (4.8.2-19) ...
Processing triggers for libc-bin (2.24-12) ...
Setting up libstdc++6:amd64 (7.1.0-7) ...
Processing triggers for libc-bin (2.24-12) ...
Selecting previously unselected package libcc1-0:amd64.
(Reading database ... 11077 files and directories currently installed.)
Preparing to unpack .../libcc1-0_7.1.0-7_amd64.deb ...
Unpacking libcc1-0:amd64 (7.1.0-7) ...
Selecting previously unselected package binutils.
Preparing to unpack .../binutils_2.28-6_amd64.deb ...
Unpacking binutils (2.28-6) ...
Selecting previously unselected package libgomp1:amd64.
Preparing to unpack .../libgomp1_7.1.0-7_amd64.deb ...
Unpacking libgomp1:amd64 (7.1.0-7) ...
Selecting previously unselected package libitm1:amd64.
Preparing to unpack .../libitm1_7.1.0-7_amd64.deb ...
Unpacking libitm1:amd64 (7.1.0-7) ...
Selecting previously unselected package libatomic1:amd64.
Preparing to unpack .../libatomic1_7.1.0-7_amd64.deb ...
Unpacking libatomic1:amd64 (7.1.0-7) ...
Selecting previously unselected package libasan3:amd64.
Preparing to unpack .../libasan3_6.3.0-18_amd64.deb ...
Unpacking libasan3:amd64 (6.3.0-18) ...
Selecting previously unselected package liblsan0:amd64.
Preparing to unpack .../liblsan0_7.1.0-7_amd64.deb ...
Unpacking liblsan0:amd64 (7.1.0-7) ...
Selecting previously unselected package libtsan0:amd64.
Preparing to unpack .../libtsan0_7.1.0-7_amd64.deb ...
Unpacking libtsan0:amd64 (7.1.0-7) ...
Selecting previously unselected package libubsan0:amd64.
Preparing to unpack .../libubsan0_7.1.0-7_amd64.deb ...
Unpacking libubsan0:amd64 (7.1.0-7) ...
Selecting previously unselected package libcilkrts5:amd64.
Preparing to unpack .../libcilkrts5_7.1.0-7_amd64.deb ...
Unpacking libcilkrts5:amd64 (7.1.0-7) ...
Selecting previously unselected package libmpx2:amd64.
Preparing to unpack .../libmpx2_7.1.0-7_amd64.deb ...
Unpacking libmpx2:amd64 (7.1.0-7) ...
Selecting previously unselected package libquadmath0:amd64.
Preparing to unpack .../libquadmath0_7.1.0-7_amd64.deb ...
Unpacking libquadmath0:amd64 (7.1.0-7) ...
Selecting previously unselected package libgcc-6-dev:amd64.
Preparing to unpack .../libgcc-6-dev_6.3.0-18_amd64.deb ...
Unpacking libgcc-6-dev:amd64 (6.3.0-18) ...
Selecting previously unselected package gcc-6.
Preparing to unpack .../gcc-6_6.3.0-18_amd64.deb ...
Unpacking gcc-6 (6.3.0-18) ...
Selecting previously unselected package gcc.
Preparing to unpack .../gcc_4%3a6.3.0-4_amd64.deb ...
Unpacking gcc (4:6.3.0-4) ...
Selecting previously unselected package libgmpxx4ldbl:amd64.
Preparing to unpack .../libgmpxx4ldbl_2%3a6.1.2+dfsg-1_amd64.deb ...
Unpacking libgmpxx4ldbl:amd64 

Bug#864995:

[Łukasz P . Michalik]

The relevant section is this:


DhtTrackerList::accessor itr = m_trackers.find(hash);

if (itr != m_trackers.end())
return itr.tracker();

[...]
std::pair res =
m_trackers.insert(std::make_pair(hash, new DhtTracker()));

if (!res.second)
throw internal_error("DhtRouter::get_tracker did not actually insert tracker.");


On first glance it would indicate that debian's stdlib is broken.
Code first checks if an element exists, it doesn't, it tries to
insert but is then told it was already there.

TR1 implementation of m_trackers uses a hashing function that
takes possibly unaligned subset of bytes and casts them directly
to size_t.  When hash is copied to prepare an insertion value, it
may get aligned differently then the original copy making the
hashing function return different hash.  I tried devising a
testcase that'd show it, but it's still fruitless.

I've forced USE_ALIGNED in config.h and now it runs fine for me
for over 12h whereas previously it was failing within minutes strongly
hinting that it's an alignment issue.
https://wiki.debian.org/ArchitectureSpecificsMemo#armel.2Farmhf.2Farm64
also recommends that unaligned access should be avoided on this
platform.

CCing Josef Drexler, author of DHT code.

Bug#865397: git merge -X renormalize fatal error in eol conversion

[Patrick]

Package: git
Version: 1:2.11.0-3
Severity: normal

Dear Maintainer,

I merge using -X renormalize option but git 2.11 has a fatal bug.
The merge abruptly fails with (no way to bypass):

  fatal: LF would be replaced by CRLF in "xxx.bat"

The git version from jessie - 2.1.4 does not have this issue, on the
exact same repo, and the merge succeeds with no problem.

The .gitattributes in both branches involved contains 

* text=auto
*.bat text eol=crlf

This could be related to the patches done on renormalize in git:

https://github.com/git/git/commit/7479ca4b44193acee43c480ae37e0bec98316f7a
https://github.com/git/git/search?q=renormalize=Commits=%E2%9C%93

I don't know if they fix this issue for certain but 
I don't think 2.11.0 in stretch has received all those.

>From what I was able to find, this probably got broken since 2.10:
https://github.com/git/git/blob/v2.10.0/Documentation/RelNotes/2.10.0.txt

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

Kernel: Linux 4.9.0-3-amd64 (SMP w/2 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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages git depends on:
ii  dpkg 1.18.24
ii  git-man  1:2.11.0-3
ii  libc62.24-11
ii  libcurl3-gnutls  7.52.1-5
ii  liberror-perl0.17024-1
ii  libexpat12.2.0-2
ii  libpcre3 2:8.39-3
ii  perl 5.24.1-3
ii  zlib1g   1:1.2.8.dfsg-5

Versions of packages git recommends:
ii  less 481-2.1
ii  openssh-client [ssh-client]  1:7.4p1-10
ii  patch2.7.5-1+b2
ii  rsync3.1.2-1

Versions of packages git suggests:
ii  gettext-base  0.19.8.1-2
pn  git-arch  
pn  git-cvs   
pn  git-daemon-run | git-daemon-sysvinit  
pn  git-doc   
pn  git-el
pn  git-email 
ii  git-gui   1:2.11.0-3
pn  git-mediawiki 
ii  git-svn   1:2.11.0-3
ii  gitk  1:2.11.0-3
pn  gitweb

-- no debconf information

Bug#865343: linux-image-4.9.0-3-amd64: On latest kernel java exits with SIGSEGV

[Rene Engelhard]

Hi,

On Wed, Jun 21, 2017 at 12:34:28AM +0100, Ben Hutchings wrote:
> > LibreOffice isn't and is also affected (#865303)
> 
> Does LibreOffice run Java code in its main thread?  I think that might
> be a common factor that makes a difference.  It *appears* that the
> 'java' command doesn't run Java code in the main thread, but JNI users
> may do.  And new threads are created through glibc aren't affected by
> this kernel change.

Assume so, yes. It doesn't run "java" either but directly jumps into the
JVM via its libs (ttbomk)

Regards,

Rene

Bug#865303: libreoffice: Libreoffice crashes silently upon startup after complaining about canberra module and murrine engine

[Rene Engelhard]

Hi,

On Wed, Jun 21, 2017 at 02:12:38AM +0100, Ben Hutchings wrote:
> On Tue, 2017-06-20 at 23:23 +0200, Rene Engelhard wrote:
> [...]
> > Indeed, LOs Java stuff crash :(. Checked with "just" creating a database.
> > (which uses hsqldb.)
> > 
> > Downgrading _the kernel_ (and of course rebooting) fixes it. 
> > 
> > No idea whether only LOs Java stuff is affected or more JDK usage (besides
> > #865311...), but...
> 
> I don't have a suitable VM to test this, so could you check whether it
> also crashes under linux 4.11.6-1 (from unstable)?  That has a later
> version of the stack clash fix.

_Seems_ so.

It also seems to me that stretch isn't affected. I can create a
database wiithout it immediately crashing. (Creating table has some problems,
though, no idea whether related or not.)

Need to do more tests when I have more time I guess.

Regards,

Rene

Bug#865319: [Pkg-shadow-devel] Bug#865319: passwd: Partial man French l10n: 1 untranslated sentence

[Christian PERRIER]

Quoting David Guyot (david.gu...@web-eci.com):
> Package: passwd
> Version: 1:4.4-4.1
> Severity: minor
> Tags: l10n
> 
> Dear Maintainer,
> 
> Reading the French passwd(1) man, I noticed that there was a remaining English
> sentence: "You can find advice on how to choose a strong password on
> http://en.wikipedia.org/wiki/Password_strength;. In French, that would
> translate to: "Vous trouverez des conseils concernant la robustesse d’un mot 
> de
> passe à l’adresse https://en.wikipedia.org/wiki/Password_strength (en)".
> 
> I did not pick the page from the French Wikipedia, as it is currently way too
> concise and useless, and I didn't know which other source I could use there.
> Regarding the translation, French being my first language, I'm rather 
> confident
> that it is good, but feel free to not take my word for it ;)


This is common practice in gettext-based translation work. Doing so
allows to keep the part that have been translated *and* avoid dropping
additional English parts.

I do not consider this a bug but a feature that helps in keeping alive
translation work even when nobody works on updating it.



Would I still be the package maintainer, I would consider closing the
bug report.




signature.asc
Description: PGP signature

Bug#839108: dh-golang: Please document behavior and variables used

[Guillem Jover]

Hi!

On Tue, 2017-06-20 at 09:49:26 +0200, Michael Stapelberg wrote:
> Guillem Jover  writes:
> > Please document at least the variables from the environment that
> > directly affect the behavior such as GOPATH, DH_GOPKG,
> > DH_GOLANG_INSTALL_ALL, DH_GOLANG_INSTALL_EXTRA, DH_GOLANG_BUILDPKG,
> > DH_GOLANG_GO_GENERATE. And the field control field Go-Import-Path.
> 
> What’s the correct place to document them? Stuffing this buildsystem
> related documentation into the dh_golang(1) manpage seems inappropriate,
> as that manpage should only document the dh_golang executable, right?

Yeah, that was my initial reaction as well. And I'm not sure where
the buildsystem and sequence behavior is supposed to be documented, or
whether debhelper maintainers would recommend doing so, so I've CCed
them in case they have any input.

OTOH, dh_golang(1p) already contains a brief note about the golang
buildsystem, so perhaps that man page is not such a bad idea after
all? Also because that's the entry point for the command, but yeah
as mentioned above I also see why it feels wrong.

Thanks,
Guillem

Bug#865289: ITP: ruby-tool -- general purpose Ruby library used by Sinatra 2.0 and Mustermann

[Gunnar Wolf]

Balasankar C dijo [Wed, Jun 21, 2017 at 08:18:11AM +0530]:
> >Umh, the name 'tool' is as generic as 'general purpose library'. Could
> >you provide a description that people would find useful to know
> >whether they could use this library (so that it's not _only_ used as a
> >dependency)?
> 
> To be honest, I did feel the same when I filed this ITP and I spent
> some time thinking of a better description. However, after reading
> the code, the description is probably the best one it can have. This
> gem basically bundles three or four different helper methods that
> are mainly to be used by Sinatra and Mustermann. I don't think I can
> find a better short description that conveys this fact. Maybe change
> "general purpose library" with "collection of helper methods".
> 
> What I can do is beef up the extended description to specify what
> all are the methods and clarify that they are mainly used by Sinatra
> and Mustermann for their specific code structure.

Ummm, I'd probably say "collection of helper methods for Sinatra and
Mustermann" then :) Making it clear from the short description what
this "tool" aims to.

(still, terrible naming for a piece of software!)

> As English isn't my best attribute, I'm open to any suggestion you
> may have. Else I will make the changes mentioned above.

I can tell you that it's quite clear that self.english.skills < 'native'
as well ;-)

Bug#865393: 865...@bugs.debian.org

[Francewhoa]

Sounds like this ticket #865393 I created is a duplicate of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853878

My bad. I'll try to use the backports mailing list to confirm or report
this bug

I'm not yet familiar with the workflow to report bug with backports
package. Thanks to Gianfranco for the information about using
debian-backports list for backports specific issues.

I did some research. I found that page at
https://backports.debian.org/Instructions/
Which reads "Please report bugs that you found in the packages to the
backports mailing list and NOT to the Debian BTS!"

Bug#865398: libguestfs0: unnessarly depends on systemd

[Ben Hildred]

Package: libguestfs0
Version: 1.34.6-2
Severity: serious
Justification: Policy 1.34.6-2

the dependency on systemd | sysvinit will not be satisfied by sysvinit-core.
This is a policy violation.



-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.9.0-1-rt-686-pae (SMP w/2 CPU cores; PREEMPT)
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: sysvinit (via /sbin/init)

Versions of packages libguestfs0 depends on:
ii  acl 2.2.52-3+b1
ii  attr1:2.4.47-2+b2
ii  binutils2.28-5
ii  bsdmainutils9.0.12+nmu1
ii  btrfs-progs 4.7.3-1
ii  btrfs-tools 4.7.3-1
ii  bzip2   1.0.6-8.1
ii  cpio2.11+dfsg-6
ii  cryptsetup  2:1.7.3-4
ii  curl7.52.1-5
ii  db-util 5.3.1
ii  diffutils   1:3.5-3
ii  dosfstools  4.1-1
ii  extlinux3:6.03+dfsg-14.1
ii  file1:5.30-1
ii  gawk1:4.1.4+dfsg-1
ii  gdisk   1.0.1-1
ii  genisoimage 9:1.1.11-3+b2
ii  grub2-common2.02~beta3-5
ii  icoutils0.31.2-1.1
ii  iproute24.9.0-1
ii  isc-dhcp-client 4.3.5-3
ii  kmod23-2
pn  ldmtool 
ii  less481-2.1
ii  libacl1 2.2.52-3+b1
pn  libaugeas0  
ii  libc6   2.24-11+deb9u1
ii  libcap2 1:2.25-1
ii  libfuse22.9.7-1
pn  libhivex0   
ii  libmagic1   1:5.30-1
ii  libpcre32:8.39-3
ii  libselinux1 2.6-3+b1
ii  libsystemd0 232-25
pn  libtsk13
ii  libvirt03.0.0-4
ii  libxml2 2.9.4+dfsg1-2.2
ii  libyajl22.1.0-2+b3
ii  lsscsi  0.27-3+b1
ii  lvm22.02.168-2
ii  lzop1.03-4+b1
pn  mdadm   
ii  mtools  4.0.18-2+b1
ii  netpbm  2:10.0-15.3+b2
ii  ntfs-3g 1:2016.2.22AR.1+dfsg-1
ii  openssh-client  1:7.4p1-10
pn  osinfo-db   
ii  parted  3.2-17
ii  procps  2:3.3.12-3
ii  psmisc  22.21-2.1+b2
ii  qemu-system-x86 1:2.8+dfsg-6
ii  qemu-utils  1:2.8+dfsg-6
pn  scrub   
ii  sgabios 0.0~svn8-3
pn  sleuthkit   
pn  supermin
ii  syslinux3:6.03+dfsg-14.1
pn  systemd | sysvinit  
ii  udev232-25
ii  xz-utils5.2.2-1.2+b1
pn  zerofree

Versions of packages libguestfs0 recommends:
pn  libguestfs-hfsplus   
pn  libguestfs-reiserfs  
pn  libguestfs-xfs   

Versions of packages libguestfs0 suggests:
pn  libguestfs-gfs2
pn  libguestfs-jfs 
pn  libguestfs-nilfs   
pn  libguestfs-rescue  

Bug#865306: [Pkg-fonts-devel] Bug#865306: Bug#865306: fonts-inconsolata: Please provide a TTF version

[Paul Wise]

On Tue, Jun 20, 2017 at 10:23 PM, Dmitry Shachnev wrote:

> Nice idea. I would like to patch the theme indeed, but that is a complicated
> task because to rebuild the CSS from SASS, I would need some 3rdparty
> dependencies packaged first (notably bourbon and wyrm).

That sounds like an RC bug; those build-dependencies should have been
packaged before packaging the font.

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Bug#865396: xelatex + unicode-math + \big = ↯

[Leon Meier]

Package: texlive-xetex
Version: 2016.20170123-5
Severity: minor

Details:
http://tex.stackexchange.com/questions/375355/xelatex-unicode-math-big

In short, the output of xelatex on

\documentclass{article}
\usepackage{unicode-math}
\begin{document}
\(\bigl[
,
  \mathchoice%
  {}%
  {}%
  {}%
  {\hbox{$\scriptscriptstyle a$}}
\bigr]\)
\end{document}

is buggy.

XeTeX Version 3.14159265-2.6-0.6 has the bug, and 
3.14159265-2.6-0.8 doesn't. Could you suggest the newer version into 
stable?

Bug#865395: witty-examples: error in building examples

[Tad Whiteside]

Package: witty-examples
Version: 3.3.6+dfsg-1.1
Severity: normal
Tags: patch

Dear Maintainer,

need to edit the default CMakeLists.txt file as described below to build 
hello.wt example


   * What led up to the situation? 
installed libhpdf-dev (which probably should be a prerequesite or a recommends 
with the package)

tried to compile the examples as described in the README 
(http://metadata.ftp-master.debian.org/changelogs/main/w/witty/witty_3.3.6+dfsg-1.1_README.Debian)
after typing:
cmake -DWT_SOURCE_DIR=/usr/lib/Wt -DEXAMPLES_CONNECTOR="wt;wthttp" 
-DCMAKE_BUILD_TYPE=Release /usr/lib/Wt/examples

make
the system failed:
[  0%] Linking CXX executable hello.wt
/usr/bin/ld: cannot find -llibhpdf
collect2: error: ld returned 1 exit status
hello/CMakeFiles/hello.wt.dir/build.make:94: recipe for target 'hello/hello.wt' 
failed

   * What exactly did you do (or not do) that was effective (or ineffective)?
edited /usr/lib/Wt/examples/CMakeLists.txt and changed line 43 from:
debug libhpdfd optimized libhpdf
to:
debug hpdfd optimized hpdf

   * What was the outcome of this action?
successful build:
[100%] Built target hello.wt


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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 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 /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages witty-examples depends on:
ii  libboost-filesystem1.62.0 1.62.0+dfsg-4
ii  libboost-program-options-dev  1.62.0.1
ii  libboost-system1.62.0 1.62.0+dfsg-4
ii  libboost-thread1.62.0 1.62.0+dfsg-4
ii  libc6 2.24-12
ii  libgcc1   1:7.1.0-7
ii  libhpdf-2.2.1 2.2.1-1.1+b1
ii  libqt4-dev4:4.8.7+dfsg-11
ii  libqtcore44:4.8.7+dfsg-11
ii  libstdc++67.1.0-7
ii  libwt40   3.3.6+dfsg-1.1
ii  libwtdbo403.3.6+dfsg-1.1
ii  libwtdbosqlite40  3.3.6+dfsg-1.1
ii  libwtext403.3.6+dfsg-1.1
ii  libwthttp40   3.3.6+dfsg-1.1

witty-examples recommends no packages.

Versions of packages witty-examples suggests:
ii  libwt-dev [witty-dev] 3.3.6+dfsg-1.1
ii  libwt-doc 3.3.6+dfsg-1.1
ii  libwtdbo-dev [witty-dev]  3.3.6+dfsg-1.1
ii  libwtdbo40 [witty-dev]3.3.6+dfsg-1.1
ii  libwtdbofirebird-dev [witty-dev]  3.3.6+dfsg-1.1
ii  libwtdbofirebird40 [witty-dev]3.3.6+dfsg-1.1
ii  libwtdbopostgres-dev [witty-dev]  3.3.6+dfsg-1.1
ii  libwtdbopostgres40 [witty-dev]3.3.6+dfsg-1.1
ii  libwtdbosqlite-dev [witty-dev]3.3.6+dfsg-1.1
ii  libwtdbosqlite40 [witty-dev]  3.3.6+dfsg-1.1
ii  libwtext-dev [witty-dev]  3.3.6+dfsg-1.1
ii  libwthttp-dev [witty-dev] 3.3.6+dfsg-1.1
ii  witty-dev 3.3.6+dfsg-1.1

-- no debconf information

Bug#865289: ITP: ruby-tool -- general purpose Ruby library used by Sinatra 2.0 and Mustermann

[Balasankar C]

Hi,

On 21 June 2017 4:05:35 AM IST, Gunnar Wolf  wrote:
>Balasankar C dijo [Tue, Jun 20, 2017 at 03:47:20PM +0530]:
>> Package: wnpp
>> Severity: wishlist
>> Owner: Balasankar C 
>> 
>> * Package name: ruby-tool
>>   Version : 0.2.3
>>   Upstream Author : Konstantin Haase
>> * URL : https://github.com/rkh/tool
>> * License : Expat
>>   Programming Lang: Ruby
>>   Description : general purpose Ruby library used by Sinatra 2.0
>and Mustermann
>> 
>> Required for GitLab 9.2.x
>
>Umh, the name 'tool' is as generic as 'general purpose library'. Could
>you provide a description that people would find useful to know
>whether they could use this library (so that it's not _only_ used as a
>dependency)?

To be honest, I did feel the same when I filed this ITP and I spent some time 
thinking of a better description. However, after reading the code, the 
description is probably the best one it can have. This gem basically bundles 
three or four different helper methods that are mainly to be used by Sinatra 
and Mustermann. I don't think I can find a better short description that 
conveys this fact. Maybe change "general purpose library" with "collection of 
helper methods".

What I can do is beef up the extended description to specify what all are the 
methods and clarify that they are mainly used by Sinatra and Mustermann for 
their specific code structure.

As English isn't my best attribute, I'm open to any suggestion you may have. 
Else I will make the changes mentioned above.
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#865394: check-mk-agent: Please provide systemd configuration

[Alessandro Polverini]

Package: check-mk-agent
Version: 1.2.8p16-1
Severity: wishlist

Dear Maintainer,

the check-mk-agent provides a xinetd configuration but a systemd
unit/socket configuration would be very welcome to avoid to use xinetd.

-- System Information:
Debian Release: 9.0
  APT prefers stable
  APT policy: (500, 'stable'), (200, 'testing'), (50, 'unstable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-3-amd64 (SMP w/10 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)

check-mk-agent depends on no packages.

Versions of packages check-mk-agent recommends:
pn  ethtool  

Versions of packages check-mk-agent suggests:
ii  python  2.7.13-2
pn  xinetd  

Bug#865393: [virtualbox] VirtualBox backport 5.1.8 not working with kernel 4.9.0

[Francewhoa]

Package: virtualbox
Version: 5.1.8-dfsg-6~bpo8+2
Severity: normal

--- Please enter the report below this line. ---

Hi Debian enthusiasts :)

Steps to reproduce errors:
1. If VirtualBox is already installed remove it and purge it

2. Reboot

3. Add Debian Backports sources

deb http://ftp.debian.org/debian jessie-backports main contrib

4. Using Terminal as user, refresh your source list

# sudo apt-get update


5. Using Terminal as user, install linux headers

# sudo apt-get install linux-headers-$(uname -r|sed 's,[^-]*-[^-]*-,,')


6. Using Terminal as user, install Virtualbox from jessie-backport

# sudo apt-get -t jessie-backports install virtualbox

Output start = = = = = = = = =
Reading package lists... Done
Building dependency tree  
Reading state information... Done
The following extra packages will be installed:
  virtualbox-dkms virtualbox-qt
Suggested packages:
  virtualbox-guest-additions-iso
The following NEW packages will be installed:
  virtualbox virtualbox-dkms virtualbox-qt
0 upgraded, 3 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/23.6 MB of archives.
After this operation, 104 MB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Selecting previously unselected package virtualbox-dkms.
(Reading database ... 218475 files and directories currently installed.)
Preparing to unpack .../virtualbox-dkms_5.1.8-dfsg-6~bpo8+2_all.deb ...
Unpacking virtualbox-dkms (5.1.8-dfsg-6~bpo8+2) ...
Selecting previously unselected package virtualbox.
Preparing to unpack .../virtualbox_5.1.8-dfsg-6~bpo8+2_amd64.deb ...
Unpacking virtualbox (5.1.8-dfsg-6~bpo8+2) ...
Selecting previously unselected package virtualbox-qt.
Preparing to unpack .../virtualbox-qt_5.1.8-dfsg-6~bpo8+2_amd64.deb ...
Unpacking virtualbox-qt (5.1.8-dfsg-6~bpo8+2) ...
Processing triggers for systemd (230-7~bpo8+2) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for menu (2.1.47) ...
Processing triggers for shared-mime-info (1.5-2~bpo8+1) ...
Unknown media type in type 'all/all'
Unknown media type in type 'all/allfiles'
Unknown media type in type 'uri/mms'
Unknown media type in type 'uri/mmst'
Unknown media type in type 'uri/mmsu'
Unknown media type in type 'uri/pnm'
Unknown media type in type 'uri/rtspt'
Unknown media type in type 'uri/rtspu'
Processing triggers for hicolor-icon-theme (0.13-1) ...
Processing triggers for desktop-file-utils (0.22-1) ...
Processing triggers for gnome-menus (3.13.3-6) ...
Processing triggers for mime-support (3.58) ...
Setting up virtualbox-dkms (5.1.8-dfsg-6~bpo8+2) ...
Loading new virtualbox-5.1.8 DKMS files...
Building for 4.9.0-0.bpo.3-amd64
Building initial module for 4.9.0-0.bpo.3-amd64
Error! Bad return status for module build on kernel: 4.9.0-0.bpo.3-amd64
(x86_64)
Consult /var/lib/dkms/virtualbox/5.1.8/build/make.log for more information.
Job for virtualbox.service failed because the control process exited
with error code.
See "systemctl status virtualbox.service" and "journalctl -xe" for details.
invoke-rc.d: initscript virtualbox, action "restart" failed.
Setting up virtualbox (5.1.8-dfsg-6~bpo8+2) ...
Setting up virtualbox-qt (5.1.8-dfsg-6~bpo8+2) ...
Processing triggers for menu (2.1.47) ...
Output end = = = = = = = = =


In the output above notice the error about: "Error! Bad return status
for module build on kernel: 4.9.0-0.bpo.3-amd64 (x86_64)".

Find attached to this ticket the "make.log" file

6. Open VirtualBox

7. Click on "New" button to build a new machine. Let's call it "Lorem".

8. Click on "Start" button. A first error message is display. Find
attached screenshot titled "Error_1---Francewhoa---2017-06-20.jpg".
Text copy below:

Error 1 start = = = = = = = = =
Failed to open a session for the virtual machine Lorem.

The virtual machine 'Lorem' has terminated unexpectedly during startup
with exit code 1 (0x1).


Result Code:
NS_ERROR_FAILURE (0x80004005)
Component:
MachineWrap
Interface:
IMachine {b2547866-a0a1-4391-8b86-}
Error 1 end = = = = = = = = =


A second error message is display. Find attached screenshot titled
"Error_2---Francewhoa---2017-06-20.jpg".
Text copy below:

Error 2 start = = = = = = = = =
Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or
there is a permission problem with /dev/vboxdrv. Please reinstall
virtualbox-dkms package and load the kernel module by executing

'modprobe vboxdrv'

as root.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The
support driver is not installed. On linux, open returned ENOENT.
Error 2 end = = = = = = = = =


Expected outcome:
• VirtualBox from jessie-backport should install without returning error
message. The DKMS module should be build using the kernel 4.9.0.


Notes:
• The kernel 4.9.0 is currently included by default with Debian 8.8
Jessie, 64-bit
• Installed using the instructions at
https://wiki.debian.org/VirtualBox#Debian_8_.22Jessie.22_Backports


What I tried that was not 

Bug#842614: Bug#842608: dgit pull should bail out in splitbrain mode

[Felipe Sateler]

gitOn Sun, 30 Oct 2016 20:09:24 + Ian Jackson <
ijack...@chiark.greenend.org.uk> wrote:
> Control: clone -1 -2
> Control: retitle -2 dgit pull should do "the right thing" in split brain
mode
> Control: severity -2 wishlist
>
> In split brain mode, dgit pull should merge the right bits.
>
> For example, with --gbp, it should merge debian/patches, and any
> upstream .gitignores, and leave the rest of the tree alone.

Indeed. While at it, the error message could be improved. This is
unparseable:

dgit: split brain (separate dgit view) may be needed (--quilt=gbp).
dgit: base trees orig=d510ca798480f37fc567 o+d/p=5c8951c97cef58952a93
dgit: quilt differences: src:  ## orig ## gitignores:  == orig ==
dgit: quilt differences:  HEAD ## o+d/p   HEAD == o+d/p
dgit: --quilt=gbp specified, implying patches-unapplied git tree
dgit:  but git tree differs from orig in upstream files.


Currently dgit is not really usable with gbp -managed repositories, as many
will have a .gitignore file ignoring the .pc dir.


Saludos

Bug#865303: libreoffice: Libreoffice crashes silently upon startup after complaining about canberra module and murrine engine

[Ben Hutchings]

On Tue, 2017-06-20 at 23:23 +0200, Rene Engelhard wrote:
[...]
> Indeed, LOs Java stuff crash :(. Checked with "just" creating a database.
> (which uses hsqldb.)
> 
> Downgrading _the kernel_ (and of course rebooting) fixes it. 
> 
> No idea whether only LOs Java stuff is affected or more JDK usage (besides
> #865311...), but...

I don't have a suitable VM to test this, so could you check whether it
also crashes under linux 4.11.6-1 (from unstable)?  That has a later
version of the stack clash fix.

Ben.

-- 
Ben Hutchings
The most exhausting thing in life is being insincere. - Anne Morrow
Lindberg



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

Bug#865311: jsvc: SIGSEV in child process when starting jsvc

[Ben Hutchings]

Control: tag -1 confirmed
Control: fixed -1 4.11.6-1

On Tue, 20 Jun 2017 15:12:25 +0200 Charles Leclerc  
wrote:
> Package: jsvc
> Version: 1.0.15-6+deb8u1
> Severity: important
> 
> When trying to start a very simple java daemon on jessie jsvc
> through systemd we obtain this error message:
> 
>  Service killed by signal 11
> 
> Then we need to SIGKILL the parent process.
[...]
> I've installed a fresh VM to try to reproduce this bug on a new machine :
> 
> - installed jessie with ssh and standard utilities
> - installed openjdk-8-jre from backports
> - installed jsvc
> - Created this java file:
[...]
> - compiled with:
>  $ javac -cp /usr/share/java/commons-daemon-1.0.15.jar Run.java
> - and tried to run with:
>  $ /usr/bin/jsvc -nodetach -outfile '&2' -errfile '&2' -pidfile /tmp/jsvc.pid 
> -cp /usr/share/java/commons-daemon-1.0.15.jar -java-home 
> /usr/lib/jvm/java-8-openjdk-amd64 Run
>  Service killed by signal 11
[...]

Thanks, this makes it pretty easy to reproduce.  I did have to add
':$PWD' to the end of the -cp argument though.

The kernel version in unstable has a later version of the fix and that
*doesn't* cause jsvc to crash.  So we should probably switch to that
version soon.

Ben.

-- 
Ben Hutchings
The most exhausting thing in life is being insincere. - Anne Morrow
Lindberg



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

Bug#865323: pdfsetmatrix error

[Norbert Preining]

Hi Joseph,

thanks for your prompt answer, and I am sure you'll find a good solution.
Considering that listings is quite common (in some areas I guess) a
fix is probably highly appreciated!

Thanks

Norbert

> I guess we'll have to go back to some non-public version of \space, but
> that redefinition is pretty risky (it's widely known that \space is an
> macro which expand to an explicit space).

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

Bug#865241: [Pkg-octave-devel] Bug#865241: Bug#865241: Please update dependencies from latex-xcolor to tl-latex-recommended

[Norbert Preining]

> You are right, I should have uploaded it to unstable, I just got confused.
> I will soon upload version 1.0.5-4 to unstable.

Thanks a lot to both of you!

Norbert

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

Bug#865392: RM: boost1.61 -- ROM; Obsoleted by newer Boost

[Steve M. Robbins]

Package: ftp.debian.org
Severity: normal

Hi,

This package was removed from testing during a transition to boost1.62
[1] but was mistakenly re-introduced into testing recently.  Please
remove the package from the archive -- both unstable and testing.

[1] https://packages.qa.debian.org/b/boost1.61/news/20170202T163914Z.html

Thanks,
-Steve

Bug#865343: linux-image-4.9.0-3-amd64: On latest kernel java exits with SIGSEGV

[Ben Hutchings]

On Tue, 20 Jun 2017 23:45:03 +0200 Rene Engelhard 
wrote:
> Hi,
> 
> On Tue, Jun 20, 2017 at 09:52:05PM +0100, Ben Hutchings wrote:
> > On Tue, 2017-06-20 at 21:47 +0100, Ben Hutchings wrote:
> > > Control: tag -1 - moreinfo
> > > Control: notfound -1 4.9.30-2
> > > Control: found -1 4.9.30-2+deb9u1
> > > Control: found -1 3.16.43-2+deb8u1
> > > 
> > > Thanks for the extra information.
> > 
> > One more question: are these applications started using jsvc?
> 
> LibreOffice isn't and is also affected (#865303)

Does LibreOffice run Java code in its main thread?  I think that might
be a common factor that makes a difference.  It *appears* that the
'java' command doesn't run Java code in the main thread, but JNI users
may do.  And new threads are created through glibc aren't affected by
this kernel change.

Ben.
 
-- 
Ben Hutchings
The most exhausting thing in life is being insincere. - Anne Morrow
Lindberg



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

Bug#865389: plasma-desktop: incorrect German translation of icon sizes

[Diederik de Haas]

Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=381467



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

Bug#865391: gnome-mines: sometimes impossible to know where to place a flag

[Byron]

Package: gnome-mines
Version: 1:3.22.2-1
Severity: normal

Dear Maintainer,

I have encountered this bug on both 8x8 and 16x16 grid sizes, but it occurs
much more frequently on 16x16 grids.

Some period in the game, usually at the beginning or end, it is impossible to
determine where a flag should be placed. I just did normal gameplay.

In the attached screenshot you can see on the left side that of, the two
squares next to the 5 and the two squares next to the 3, only one of them could
be a flag, but I can't figure out how to determine which one. Probed for a
"Hint" button, but found none.

Thank you for reading through all of this and helping to maintain this package
in gnome-games.



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

Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_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 gnome-mines depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.26.0-2+b1
ii  libc62.24-11+deb9u1
ii  libglib2.0-0 2.50.3-2
ii  libgnome-games-support-1-2   1.2.1-1
ii  libgtk-3-0   3.22.11-1

Versions of packages gnome-mines recommends:
ii  yelp  3.22.0-1

gnome-mines suggests no packages.

-- no debconf information

Bug#861581: ITP: rainloop -- Simple, modern & fast web-based email client

[Daniel Ring]

Hi Gunnar,

Sorry for the delay; I've done more work on the package, but I'm extremely busy
at the moment so updates/responses may take a while. The current version fixes
a lot of issues but isn't ready for inclusion in Debian yet.

> Ugh. The whole NodeJS ecosystem makes me shiver :-(

Agreed. I've been working on packaging dependencies individually when I can,
apparently 5 lines of code is enough to warrant an NPM package...

> That is also something that cannot be done; packaging software cannot
> depend on network connectivity (not even initiate network
> connections). The dependencies must be somehow build-depended upon; in
> the (ugliest, worst) case you could patch your sources to include the
> packages to fulfill this... But I doubt the ftp-masters will approve
> of it.

I've done this to make the package build successfully, but I'm working with the
pkg-javascript group on getting the non-library dependencies packaged
independently. Libraries missing from Debian should be OK
(using https://packages.debian.org/source/sid/netdata as an example) but build
system tools are a bit much.

I wrote a basic Makefile to replace upstream's Gulp build system, which helped
a lot, but webpack+babel is unavoidable so I'm working on that project at the
moment.

> We have to ship sources for every piece of software. You don't need to
> separate them as long as you provide all the sources and can *prove*
> they can be amalgamated to the identical "binary" you are
> shipping. That's not a trivial thing, sadly :(

Fortunately, the amalgamation is a step in upstream's build process; the bundled
libraries are included in source form.

The new DSC URL is:
https://mentors.debian.net/debian/pool/main/r/rainloop/rainloop_1.11.1-1.dsc

I think I've fixed all of the major issues with the package other than the
bundled build tools. I'll update the copyright file once that's done and I find
out what will still need to be bundled. Please let me know if there's anything
else I'm missing.

Sincerely,
Daniel Ring

Bug#758234: debian-policy: allow packages to depend on packages of lower priority

[Cyril Brulebois]

Hi,

Ansgar Burchardt  (2017-06-21):
> I discussed this a bit on IRC with the other ftp-masters and we came
> to this summary:
> 
> 0) We would like to drop the requirement for packages to not depend on
>packages of lower priority: it is better to declare only what we
>actually want included in the installation (that is at priority >=
>standard) rather than also the dependency closure.
> 
> 1) We agree that the 'extra' priority can be dropped.

Looks good to me.

> 2) We wonder if the 'standard' priority can also be dropped: as far as
>we know, it is used only by the "standard" task and it might make
>sense to treat it the same as other tasks.
>(Depending on what works better for the installer team.)
> 
> I've Cc'ed -boot@ as this policy change affects them (I don't think
> they have to read all of the way too long bug history though).

Comparing a Section field in the archive and a Depends list, I can
imagine we would have to arch-{qualify,filter} quite a number of
packages, which might be less convenient than just relying on the
archive contents.

On the other hand, I think it would be better to be able to track the
packages getting installed over time, instead of hoping for the best
when this or that package gets a (sometimes uncoordinated) priority
bump in the archive.

Initial impression is still that such a change might be welcome at
some point, but it needs to be carefully considered on the installer
side. This might also affect downstreams.

That being said, I'm very low on bandwidth right now, with 9.0.*
fixing and/or debugging, plus 9.1 preparations.


KiBi.


signature.asc
Description: Digital signature

Bug#851600: Please update to more recent upstream snapshot

[Vladimir K]

Also there is a fix for clipboard:
https://github.com/FreeRDP/FreeRDP/issues/3983

Bug#861575: libgtkd-3-0 and libvted-3-0 shlibs need a version

[Matthias Klumpp]

Hi!

I wonder why the shlibs file is messed up, since debhelper should
actually handle it correctly...
If you have an idea, let me know, otherwise I'll investigate this next week.

Cheers,
Matthias

-- 
I welcome VSRE emails. See http://vsre.info/

Bug#719913: ikiwiki: error setting wiki theme if libxml-writer-perl not installed

[Simon McVittie]

Control: tags 719913 + upstream patch pending

On Tue, 20 Jun 2017 at 23:11:47 +0100, Simon McVittie wrote:
> This appears to be a bug in the osm plugin

I believe this should avoid it:
http://source.ikiwiki.branchable.com/?p=source.git;a=commitdiff;h=5a84cd308d817c9e509e5f4baf514a3681f48dc1

S

Bug#865289: ITP: ruby-tool -- general purpose Ruby library used by Sinatra 2.0 and Mustermann

[Gunnar Wolf]

Balasankar C dijo [Tue, Jun 20, 2017 at 03:47:20PM +0530]:
> Package: wnpp
> Severity: wishlist
> Owner: Balasankar C 
> 
> * Package name: ruby-tool
>   Version : 0.2.3
>   Upstream Author : Konstantin Haase
> * URL : https://github.com/rkh/tool
> * License : Expat
>   Programming Lang: Ruby
>   Description : general purpose Ruby library used by Sinatra 2.0 and 
> Mustermann
> 
> Required for GitLab 9.2.x

Umh, the name 'tool' is as generic as 'general purpose library'. Could
you provide a description that people would find useful to know
whether they could use this library (so that it's not _only_ used as a
dependency)?

Bug#865354: java.lang.NoClassDefFoundError: org/apache/tomcat/InstanceManager

[Emmanuel Bourg]

Thank your for the report Joe. The InstanceManager class is in
/usr/share/java/tomcat8-api.jar. It looks like this jar is missing from
the classpath used by Eclipse. Did you use the version of eclipse
currently in testing/unstable?

Emmanuel Bourg

Bug#865389: plasma-desktop: incorrect German translation of icon sizes

[Heinrich Schuchardt]

Upstream bug report
https://bugs.kde.org/show_bug.cgi?id=381467

Bug#865390: nmu: fonts-fantasque-sans_1.7.1~dfsg-1

[Adam Borowski]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu

Hi!
This font has some issues when built with fontforge 20120713, that have been
solved in 20160404.  All it takes is a clean rebuild against the version in
stretch or unstable.  Obviously, it's too late to do it for stretch (the bug
is nowhere near important enough), so let's do so for buster.

#827045 has the details, but you're probably too busy to bother reading. 
I tested a binNMU at home, it worked fine for me.

nmu fonts-fantasque-sans_1.7.1~dfsg-1 . ANY . unstable . -m "Rebuild with new 
fontforge (#827045)."


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

Kernel: Linux 4.12.0-rc6-debug-00024-gff389e3ae048 (SMP w/6 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)

Bug#832187: closed by Ole Streicher <oleb...@debian.org> (Closing resolved bug)

[Ben Finney]

On 20-Jun-2017, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the astropy-utils package:
> 
> #832187: astropy-utils: Section should not be “python”
> 
> It has been closed by Ole Streicher .

Thank you for addressing this bug report.

> From: Ole Streicher 
> Subject: Closing resolved bug
>
> […]
> 
> @Ben: I am however wondering why you did not issue the override bug
> yourself (and put the maintainer into Cc:)? It was already changed
> in d/control since ages.

I do not arrogate to myself the power to unilaterally decide the
correct Section value, so it's not my place to submit the override
request.

That must be done only when the package maintainer has decided what is
correct. The maintainer can decide a Section that is different from
what I suggested, and so a pre-emptive override request would be even
more annoying to the maintainer.

So, that's why I request a maintainer should do that unilateral
action.

> Writing a bug "please write another bug, wait until it is closed, and
> then close this bug" seems to me a quite useless overhead.

I think we can both look forward to a time when a change to
‘debian/control’ is enough to change the metadata of the package.
Until that happy day, multiple changes must be coordinated.

Thank you for maintaining the package.

-- 
 \  “Probably the earliest flyswatters were nothing more than some |
  `\sort of striking surface attached to the end of a long stick.” |
_o__) —Jack Handey |
Ben Finney 


signature.asc
Description: PGP signature

Bug#865389: plasma-desktop: incorrect German translation of icon sizes

[Heinrich Schuchardt]

Package: plasma-desktop
Version: 4:5.8.6-1
Severity: minor

Dear Maintainer,

I am using KDE with the desktop showing a folder view.

When I right click on the desktop I can choose the icon size:

Tiny
Small
Small medium
Medium
Large
Huge

When I use German menus I get as choice

Winzig
Klein
Klein
Mittel
Groß
Riesig

I would not expect two sizes using the same translation.

Please, translate 'Small medium' as 'Mittelklein'.

Best reagrds

Heinrich Schuchardt

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

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

Versions of packages plasma-desktop depends on:
ii  breeze   4:5.8.5-2
ii  kactivitymanagerd5.8.4-1
ii  kde-cli-tools4:5.8.4-2
ii  kded55.28.0-1
ii  kio  5.28.0-2
ii  libc62.24-11+deb9u1
ii  libcanberra0 0.30-3
ii  libfontconfig1   2.11.0-6.7+b1
ii  libgcc1  1:6.3.0-18
ii  libkf5activities55.28.0-1
ii  libkf5activitiesstats1   5.28.0-1
ii  libkf5archive5   5.28.0-2
ii  libkf5auth5  5.28.0-2
ii  libkf5baloo5 5.28.0-2
ii  libkf5bookmarks5 5.28.0-1
ii  libkf5codecs55.28.0-1+b2
ii  libkf5completion55.28.0-1
ii  libkf5configcore55.28.0-2
ii  libkf5configgui5 5.28.0-2
ii  libkf5configwidgets5 5.28.0-2
ii  libkf5coreaddons55.28.0-2
ii  libkf5dbusaddons55.28.0-1
ii  libkf5emoticons-bin  5.28.0-1
ii  libkf5emoticons5 5.28.0-1
ii  libkf5globalaccel5   5.28.0-1
ii  libkf5guiaddons5 5.28.0-1
ii  libkf5i18n5  5.28.0-2
ii  libkf5iconthemes55.28.0-2
ii  libkf5itemmodels55.28.0-2
ii  libkf5itemviews5 5.28.0-1
ii  libkf5jobwidgets55.28.0-2
ii  libkf5kcmutils5  5.28.0-2
ii  libkf5kdelibs4support5   5.28.0-1
ii  libkf5kiocore5   5.28.0-2
ii  libkf5kiofilewidgets55.28.0-2
ii  libkf5kiowidgets55.28.0-2
ii  libkf5newstuff5  5.28.0-1
ii  libkf5notifications5 5.28.0-1
ii  libkf5notifyconfig5  5.28.0-1
ii  libkf5parts5 5.28.0-1
ii  libkf5people55.28.0-1
ii  libkf5peoplewidgets5 5.28.0-1
ii  libkf5plasma55.28.0-2
ii  libkf5plasmaquick5   5.28.0-2
ii  libkf5quickaddons5   5.28.0-1
ii  libkf5runner55.28.0-1
ii  libkf5service-bin5.28.0-1
ii  libkf5service5   5.28.0-1
ii  libkf5solid5 5.28.0-3
ii  libkf5sonnetui5  5.28.0-2
ii  libkf5wallet-bin 5.28.0-3
ii  libkf5wallet55.28.0-3
ii  libkf5widgetsaddons5 5.28.0-3
ii  libkf5windowsystem5  5.28.0-2
ii  libkf5xmlgui55.28.0-1
ii  libkfontinst54:5.8.6-1
ii  libkfontinstui5  4:5.8.6-1
ii  libkworkspace5-5 4:5.8.6-2.1
ii  libpackagekitqt5-0   0.9.6-1
ii  libphonon4qt5-4  4:4.9.0-4
ii  libpulse-mainloop-glib0  10.0-1
ii  libpulse010.0-1
ii  libqt5concurrent55.7.1+dfsg-3+b1
ii  libqt5core5a 5.7.1+dfsg-3+b1
ii  libqt5dbus5  5.7.1+dfsg-3+b1
ii  libqt5gui5   5.7.1+dfsg-3+b1
ii  libqt5network5   5.7.1+dfsg-3+b1
ii  libqt5printsupport5  5.7.1+dfsg-3+b1
ii  libqt5qml5   5.7.1-2+b2
ii  libqt5quick5 5.7.1-2+b2
ii  libqt5quickwidgets5  5.7.1-2+b2
ii  libqt5sql5   5.7.1+dfsg-3+b1
ii  libqt5svg5   5.7.1~20161021-2+b2
ii  libqt5widgets5   5.7.1+dfsg-3+b1
ii  libqt5x11extras5 

Bug#865343: linux-image-4.9.0-3-amd64: On latest kernel java exits with SIGSEGV

[Sasa Skevin]

On Tue, 20 Jun 2017, 22:52 Ben Hutchings,  wrote:

> On Tue, 2017-06-20 at 21:47 +0100, Ben Hutchings wrote:
> > Control: tag -1 - moreinfo
> > Control: notfound -1 4.9.30-2
> > Control: found -1 4.9.30-2+deb9u1
> > Control: found -1 3.16.43-2+deb8u1
> >
> > Thanks for the extra information.
>
> One more question: are these applications started using jsvc?
>

Yes. Initially it was version 1.0.12 but later upgraded to latest 1.0.15
but still issue happened.

Sasa

Bug#719913: ikiwiki: error setting wiki theme if libxml-writer-perl not installed

[Simon McVittie]

On Tue, 20 Jun 2017 at 12:36:04 +0100, Steven Chamberlain wrote:
> On first install of ikiwiki, I logged into the web interface, wanted to
> adjust the site URL and Save Changes.

Thanks, I can reproduce this now. The web interface is the key thing.

This appears to be a bug in the osm plugin, which does things in its
savestate hook that don't seem appropriate for that hook: as well as
saving state, it writes out KML/JSON/CSV waypoints. It should stop doing
that, and write its output in some other hook. Unfortunately, I've never
really understood the osm plugin, so it'll take me a while to work out
what is going on and where it should happen.

(The same issue would appear if you don't have the JSON module, I think.)

The websetup plugin ("Setup" in the web interface) triggers this because
it temporarily loads all plugins, including plugins that are not enabled
for this particular wiki; it has to do that to know what configuration
options they have.

S

Bug#865380: libtest-unixsock-perl: Build-Conflicts-Indep: libtest-simple-perl (>= 1.3), including Perl 5.26

[gregor herrmann]

On Tue, 20 Jun 2017 23:30:09 +0300, Niko Tyni wrote:

> This package Build-Conflicts-Indep: libtest-simple-perl (>= 1.3),
> for reasons that aren't immediately obvious.

The commit shows which problem the conflicts is supposed to solve but
also not really why.

I tried some combinations now:

5.24.1 Test::More::VERSION: 1.001014
5.26.0 Test::More::VERSION: 1.302073

That's the bundled Test::More versions of the respective perls, and
both builds succeeds.

Then I added a B-D-I on libtest-simple-perl (>= 1.302075), so we get
5.24.1 Test::More::VERSION: 1.302075
5.26.0 Test::More::VERSION: 1.302075

and both builds fail with

IPC Fatal Error: Leftover files in the directory 
(/tmp/test2~2701~jjTyz_/2701~0~1~2702~0~13~Test2~Event~Note.ready)!
Could not remove IPC temp dir (/tmp/test2~2701~jjTyz_) at 
/usr/share/perl5/Test2/IPC/Driver/Files.pm line 420 during global destruction.

(which is the same as mentioned in the commit which introduced the
Conflicts)

So this looks like a bug in the specific Test::More version that is
currently in the separate libtest-simple-perl, maybe
https://github.com/Test-More/test-more/issues/765


Then I tried to build libtest-simple-perl 1.302085-1 to test 
libtest-unixsock-perl
with it -- but it doesn't build neither with 5.24.1 nor with 5.26.0.
That's https://github.com/Test-More/test-more/issues/770

*sigh*

Ok, let's build ith without running tests. And then libtest-unixsock-perl
again:

5.24.1 Test::More::VERSION: 1.302085

pass

5.26.0 Test::More::VERSION: 1.302085

fails again with

IPC Fatal Error: Leftover files in the directory 
(/tmp/test2~12195~MjWYMf/12195~0~1~12204~0~13~Test2~Event~Note.ready)!
Could not remove IPC temp dir (/tmp/test2~12195~MjWYMf) at 
/usr/share/perl5/Test2/IPC/Driver/Files.pm line 420 during global destruction.


Looks like it's somehow related to Test::More (or
Test2/IPC/Driver/Files.pm) but not only.


My not very elegant proposal for libtest-unixsock-perl would be to
- drop the Build-Conflicts-Indep, and
- to skip t/15_oo_unix.t


And for libtest-simple-perl to wait for a new release.


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#864447: Pending fixes for bugs in the tomcat7 package

[pkg-java-maintainers]

tag 864447 + pending
thanks

Some bugs in the tomcat7 package are closed in revision
1ebcd5b2c822cf677b59a875172344c80d1d1ee4 in branch '  wheezy' by
Markus Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/tomcat7.git/commit/?id=1ebcd5b

Commit message:

Import Debian changes 7.0.28-4+deb7u14

tomcat7 (7.0.28-4+deb7u14) wheezy-security; urgency=high

  * Team upload.
  * Fix CVE-2017-5664.
The error page mechanism of the Java Servlet Specification requires 
that,
when an error occurs and an error page is configured for the error that
occurred, the original request and response are forwarded to the error
page. This means that the request is presented to the error page with 
the
original HTTP method. If the error page is a static file, expected
behaviour is to serve content of the file as if processing a GET 
request,
regardless of the actual HTTP method. The Default Servlet in Apache 
Tomcat
did not do this. Depending on the original request this could lead to
unexpected and undesirable results for static error pages including, if 
the
DefaultServlet is configured to permit writes, the replacement or 
removal
of the custom error page. (Closes: #864447)

Bug#865234: apt-listbugs shows up bugs which is not consistent with the version installed.

[Francesco Poli]

Control: tags -1 + moreinfo


On Tue, 20 Jun 2017 09:05:46 +0530 shirish शिरीष wrote:

[...]
> Dear Maintainer,

Hello shirish,
thanks for your bug report, which, however, is not very clear.

> While I have seen the above being exhibited by wpagui only, there may
> be other packages which might be affected by the above. See the whole
> discussion starting from
> https://lists.debian.org/debian-release/2017/06/msg00487.html to see
> what apt-listbugs shows and what the reality is.

I cannot find much of a discussion there (maybe I am just a bit sleepy
now...).

Anyway, could you please clarify which bug reports you believe is
incorrectly shown by apt-listbugs?
The three bug reports mentioned in the message you referred to seem to
show up when querying the BTS for bugs affecting the version currently
in stable, testing, and unstable of wpasupplicant:

  $ apt-listbugs list wpasupplicant/2:2.4-1
  Retrieving bug reports... Done
  Parsing Found/Fixed information... Done
  grave bugs of wpasupplicant (→ 2:2.4-1) 
   b1 - #849122 - With 2.6-2 i dont have the wifi adapter in the 
(network-manager) list available.
  serious bugs of wpasupplicant (→ 2:2.4-1) 
   b2 - #849077 - wpasupplicant: [Regression] Updating wpasupplicant makes not 
possible to connect to encrypted WiFi
   b3 - #849875 - broadcom-sta-dkms: Wifi association took too long, failing 
activation
  Summary:
   wpasupplicant(3 bugs)

However, they all seem to be found in version 2.6-2 which is now
superseded by versions with epoch 2.
What seems to have happened (see the [tracker page]) is that the
upstream version 2.4 was reintroduced into unstable (with epoch 2) and
then migrated to stretch.

[tracker page]: 

Hence, I would say that those three bugs only affect experimental and
are not in stretch, buster or sid.

Please write to the wpasupplicant maintainers and ask for confirmation
that those three bugs should be marked as found in wpa/2:2.6-2 and not
in wpa/2.6-2 (otherwise the BTS version tracking will continue to
incorrectly think that the bugs affect stable, testing, unstable, and
experimental).

Please let me know whether my guess is correct.


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
. Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE


pgpz3eZgLCIf_.pgp
Description: PGP signature

Bug#758234: debian-policy: allow packages to depend on packages of lower priority

[Ansgar Burchardt]

Hi,

Russ Allbery writes:
> ftp-master folks, we're discussing eliminating the requirement that
> packages only depend on other packages with the same or higher priority
> (so important packages would be able to depend on optional packages), and
> deprecating the extra priority entirely (so everything at extra priority
> would end up being optional over time).  This also means eliminating the
> requirement that no two packages at optional priority conflict with each
> other.

I discussed this a bit on IRC with the other ftp-masters and we came to
this summary:

0) We would like to drop the requirement for packages to not depend on
   packages of lower priority: it is better to declare only what we
   actually want included in the installation (that is at priority >=
   standard) rather than also the dependency closure.

1) We agree that the 'extra' priority can be dropped.

2) We wonder if the 'standard' priority can also be dropped: as far as
   we know, it is used only by the "standard" task and it might make
   sense to treat it the same as other tasks.
   (Depending on what works better for the installer team.)

I've Cc'ed -boot@ as this policy change affects them (I don't think they
have to read all of the way too long bug history though).

Ansgar

Bug#865387: outputs

[Aniol Martí]

# apt install libwine:i386
The following packages have unmet dependencies:
 libwine:i386 : Depends: libpulse0:i386 (>= 0.99.1) but it is not going 
to be installed
Recommends: libcups2:i386 (>= 1.4.0) but it is not 
going to be installed
Recommends: libdbus-1-3:i386 (>= 1.9.14) but it is not 
going to be installed
Recommends: libasound2-plugins:i386 but it is not going 
to be installed

E: Unable to correct problems, you have held broken packages.

# apt install libpulse0:i386
The following packages have unmet dependencies:
 libpulse0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not 
going to be installed
  Depends: libsystemd0:i386 but it is not going to be 
installed

E: Unable to correct problems, you have held broken packages.

# apt install libdbus-1-3:i386
The following packages have unmet dependencies:
 libdbus-1-3:i386 : Depends: libsystemd0:i386 (>= 209) but it is not 
going to be installed

E: Unable to correct problems, you have held broken packages.

# apt install libsystemd0:i386
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer 
required:
  adwaita-icon-theme alsa-utils apache2-bin apg attr brasero-common 
breeze-icon-theme cabextract catdoc cdrdao cheese-common 
cinnamon-control-center-data cinnamon-desktop-data cinnamon-session-common
  cmake-data coinor-libcbc3 coinor-libcgl1 coinor-libclp1 
coinor-libcoinmp1v5 coinor-libcoinutils3v5 coinor-libosi1v5 colord-data 
cracklib-runtime crda cups-common cups-server-common dconf-cli diffstat dkms
  dleyna-server dmz-cursor-theme dns-root-data docbook-xml dosfstools 
dvdauthor dvgrab enchant espeak-ng-data evince-common exfat-fuse 
exfat-utils fig2dev filezilla-common fonts-dejavu fonts-dejavu-extra
  fonts-droid-fallback fonts-freefont-ttf fonts-lato fonts-opensymbol 
fonts-wine foomatic-db-compressed-ppds freepats gconf2-common gdebi-core 
gdisk geany-common gedit-common genisoimage gimp-data
  gir1.2-atk-1.0 gir1.2-cmenu-3.0 gir1.2-cogl-1.0 gir1.2-coglpango-1.0 
gir1.2-freedesktop gir1.2-gdesktopenums-3.0 gir1.2-gdkpixbuf-2.0 
gir1.2-git2-glib-1.0 gir1.2-gst-plugins-base-1.0 gir1.2-gstreamer-1.0
  gir1.2-javascriptcoregtk-3.0 gir1.2-javascriptcoregtk-4.0 
gir1.2-json-1.0 gir1.2-nm-1.0 gir1.2-notify-0.7 
gir1.2-packagekitglib-1.0 gir1.2-pango-1.0 gir1.2-secret-1 
gir1.2-soup-2.4 gir1.2-totem-plparser-1.0
  gir1.2-upowerglib-1.0 gir1.2-xkl-1.0 gir1.2-zeitgeist-2.0 gist 
glx-alternative-mesa glx-alternative-nvidia glx-diversions 
gnome-accessibility-themes gnome-backgrounds gnome-control-center-data
  gnome-desktop3-data gnome-icon-theme gnome-mime-data 
gnome-terminal-data gnome-themes-standard-data growisofs 
gstreamer1.0-alsa gstreamer1.0-nice gtk-update-icon-cache gvfs-libs 
hddtemp hexchat-common
  hexchat-perl hexchat-plugins hexchat-python3 hoichess hp-ppd 
hplip-data hunspell-en-us hwdata icoutils imagemagick 
imagemagick-6-common imagemagick-6.q16 intltool-debian iputils-arping 
iso-flags-png-320x240
  iw javascript-common kdenlive-data keyutils klibc-utils libaacs0 
libabw-0.1-1 libaio1 libamd2 libao-common libao4 libapparmor1 libapr1 
libaprutil1 libaprutil1-dbd-sqlite3 libaprutil1-ldap libapt-pkg-perl
  libarchive-zip-perl libarchive13 libart-2.0-2 libasound2 
libasound2-data libasyncns0 libatasmart4 libatk1.0-0 libatk1.0-data 
libatkmm-1.6-1v5 libaudio2 libavahi-common-data libavahi-common3 
libavahi-core7
  libavahi-glib1 libavcodec57 libavfilter6 libavformat57 libavresample3 
libavutil55 libbabl-0.1-0 libbasicusageenvironment1 libbluetooth3 
libbluray1 libbluray2 libbonobo2-0 libbonobo2-common
  libbonoboui2-common libboost-date-time1.62.0 libbrlapi0.6 libbs2b0 
libburn4 libcacard0 libcairo-perl libcairomm-1.0-1v5 libcamd2 
libcanberra0 libcaribou-common libccolamd2 libcddb2 libcdio-cdda1
  libcdio-paranoia1 libcdr-0.1-1 libcholmod3 libchromaprint1 
libcinnamon-menu-3-0 libclone-perl libclucene-contribs1v5 
libclucene-core1v5 libclutter-1.0-common libcmis-0.5-5v5 libcogl-common 
libcogl-pango20
  libcogl-path20 libcogl20 libcolamd2 libcolord2 libcolorhug2 libcrack2 
libcrystalhd3 libdaemon0 libdbusmenu-glib4 libdbusmenu-gtk3-4 
libdc1394-22 libdca0 libdee-1.0-4 libdirectfb-1.2-9 libdiscid0
  libdjvulibre-text libdjvulibre21 libdleyna-connector-dbus-1.0-1 
libdleyna-core-1.0-3 libdotconf0 libdouble-conversion1 libdvbpsi10 
libe-book-0.1-1 libegl-nvidia0 libegl1-glvnd-nvidia libegl1-mesa
  libemail-valid-perl libenca0 libenchant1c2a libeot0 libepoxy0 
libept1.5.0 libepub0 libetonyek-0.1-1 libevdev2 libevent-2.0-5 
libexempi3 libexif12 libexiv2-14 libexporter-tiny-perl libexttextcat-2.0-0
  libexttextcat-data libfaac0 libfaad2 libfam0 libfastjson4 
libfftw3-double3 libfftw3-single3 libfile-copy-recursive-perl 
libfilezilla0 libflite1 libfontembed1 libfreehand-0.1-1 libfreerdp-cache1.1
  libfreerdp-codec1.1 libfreerdp-common1.1.0 libfreerdp-core1.1 

Bug#865387: [pkg-wine-party] Bug#865387: wine32: can't install wine32 in a 64 bits system

[Jens Reyer]

On 20.06.2017 23:51, Aniol Martí wrote:
> I'm not able to install "wine32" in Debian Sid (64 bits).
> 
> First I have added an extra arch:
> # dpkg --add-architecture i386
> # apt update
> 
> Then, I have tried to install wine32:
> # apt install wine32
> 
> But I get the following error:
> The following packages have unmet dependencies:
>  wine32:i386 : Depends: libwine:i386 (= 1.8.7-2) but it is not going to
> be installed
> E: Unable to correct problems, you have held broken packages.
> 
> Is there something I'm missing?

Go down the dependency chain and post its output
# apt install libwine:i386
# ...

Bug#865388: starlink-pal FTBFS: pdflatex: command not found

[Adrian Bunk]

Source: starlink-pal
Version: 0.9.7-1
Severity: serious

https://buildd.debian.org/status/package.php?p=starlink-pal=sid

...
libtool: link: ranlib .libs/libstarlink_pal.a
libtool: link: ( cd ".libs" && rm -f "libstarlink_pal.la" && ln -s 
"../libstarlink_pal.la" "libstarlink_pal.la" )
pdflatex sun267.tex && pdflatex sun267.tex
/bin/bash: pdflatex: command not found
Makefile:2133: recipe for target 'sun267.pdf' failed
make[2]: *** [sun267.pdf] Error 127
make[2]: Leaving directory '/«PKGBUILDDIR»'
Makefile:715: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/«PKGBUILDDIR»'
dh_auto_build: make -j1 returned exit code 2
debian/rules:7: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
d

Bug#865387: wine32: can't install wine32 in a 64 bits system

[Aniol Martí]

Package: wine32
Version: 1.8.7-2
Severity: important

Dear Maintainer,

I'm not able to install "wine32" in Debian Sid (64 bits).

First I have added an extra arch:
# dpkg --add-architecture i386
# apt update

Then, I have tried to install wine32:
# apt install wine32

But I get the following error:
The following packages have unmet dependencies:
 wine32:i386 : Depends: libwine:i386 (= 1.8.7-2) but it is not going to 
be installed

E: Unable to correct problems, you have held broken packages.

Is there something I'm missing?


Thank you,

Aniol


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

Kernel: Linux 4.9.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)

Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages wine32 depends on:
ii  libc62.24-11
ii  libwine  1.8.7-2

Versions of packages wine32 recommends:
ii  wine 1.8.7-2
ii  wine-development [wine]  2.10-1

Versions of packages wine32 suggests:
pn  wine32-preloader  

Bug#865343: linux-image-4.9.0-3-amd64: On latest kernel java exits with SIGSEGV

[Rene Engelhard]

Hi,

On Tue, Jun 20, 2017 at 09:52:05PM +0100, Ben Hutchings wrote:
> On Tue, 2017-06-20 at 21:47 +0100, Ben Hutchings wrote:
> > Control: tag -1 - moreinfo
> > Control: notfound -1 4.9.30-2
> > Control: found -1 4.9.30-2+deb9u1
> > Control: found -1 3.16.43-2+deb8u1
> > 
> > Thanks for the extra information.
> 
> One more question: are these applications started using jsvc?

LibreOffice isn't and is also affected (#865303)

Regards,

Rene

Bug#789196: debsecan: Support SUITE=buster

[Nye Liu]

And now buster/testing.

Is there an actual maintainer for this?

Perhaps an NMU is in order?

Bug#822743: dh-golang: should assist in calculating -dev packages Depends:

[Michael Hudson-Doyle]

On 20 June 2017 at 19:52, Michael Stapelberg  wrote:

> Hi,
>
> currently going through the bugs of dh-golang.
>
> Is there anything that remains to be done here?


Well, nothing at all has been done so far :-) OTOH it's a feature request
so perhaps doing nothing is the right thing...


> If so, could someone please summarize the discussion and explain what it
> is?
>

The issue is making it easier to get the dependencies of golang-*-dev
packages correct. I think my most recent suggestion was that we sort
through the Build-Depends looking for packages that install files to
/usr/share/gocode and copy them all (completely with version and
architecture constraints, if present) to a golang:Depends substvar you
could use in the control file. Does that make sense?

Cheers,
mwh

Bug#865341: pagein: Segfaults roughly every 1 in ten executions

[Ben Wiederhake]

Hello,

in version 0.00.04, which you commited to git three hours ago, the bug 
is still present, although much more seldom.


I enabled core dumping, and looked at it through gdb.
Please find attached at "bt full" for version 0.00.04-1 as gdb prints it 
for the version with debug symbols.  It appears that the error is 
("still"?) with accessing mmaps.


For comparison: core dumps with version 0.00.03 mostly have their stack 
corrupted, and the rest crashes somewhere deep in 'scanf' while trying 
to read things from the stack; so probably stack corruption, too.


Btw, can you enable debug symbols again?  One litte "-g" in the CFLAGS 
increases the binary size only slightly, and makes debugging easier.  I 
did that by hand when reproducing the bug.


Cheers,
Ben Wiederhake
PS: Today I learned how *not* to use reportbug.  I assumed --body-file 
would either accept it as the full message, or allow me to edit it once 
more.  Oh well.
user@machine:~/workspace/pagein$ gdb ./pagein core
GNU gdb (Debian 7.12-6) 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 "i686-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 ./pagein...done.
[New LWP 28377]
Core was generated by `./pagein -p 1073'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  pagein_proc_mmap (pages_touched=, prot=0xbfeeaa73 
"r--p", 
path=0xbfeeaae0 "/usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0.1004.0", 
len=, 
end=3077554176, begin=, page_size=4096, mappings=0x811c28e8) 
at pagein.c:263
263 x += *ptr;
(gdb) set pagination off
(gdb) bt full
#0  pagein_proc_mmap (pages_touched=, prot=0xbfeeaa73 
"r--p", path=0xbfeeaae0 "/usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0.1004.0", 
len=, end=3077554176, begin=, page_size=4096, 
mappings=0x811c28e8) at pagein.c:263
ptr = 0xb76fb000 
x = 
fd = 5
statbuf = {st_dev = 65025, __pad1 = 0, st_ino = 7606200, st_mode = 
33188, st_nlink = 1, st_uid = 0, st_gid = 0, st_rdev = 0, __pad2 = 0, st_size = 
132, st_blksize = 4096, st_blocks = 2696, st_atim = {tv_sec = 1497960752, 
tv_nsec = 83782983}, st_mtim = {tv_sec = 1487856812, tv_nsec = 0}, st_ctim = 
{tv_sec = 1490879804, tv_nsec = 871008154}, __glibc_reserved4 = 0, 
__glibc_reserved5 = 0}
off = 3077550080
prot_flags = 
mapped = 0xb770d000
#1  pagein_proc (mappings=0x811c28e8, page_size=4096, pid=1073, 
procs=0xbfeecf38, kthreads=0xbfeecf3c, total_pages_touched=0xbfeecf60) at 
pagein.c:337
begin = 3077541888
end = 3077554176
len = 
off = 
off_end = 
byte = 0 '\000'
mapped = 0x0
path = 
"/usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0.1004.0\000\000-le32d4.cache-4\000png.so",
 '\000' 
prot = "r--p"
path = "/proc/1073/maps", '\000' ...
buffer = "b76f9000-b76fc000 r--p 0014c000 fe:01 7606200
/usr/lib/i386-linux-gnu/libgstreamer-1.0.so.0.1004.0\n\000\000\000e32d4.cache-4\n\000ng.so\n\000)\n",
 '\000' ...
fdmem = 3
rc = 0
fpmap = 0x811c2008
pages = 26343
pages_touched = 22240
has_maps = 
#2  0x80054e0e in main (argc=, argv=) at 
pagein.c:493
ret = 
memfree_begin = 152728
memfree_end = -5227627996823549632
swapfree_begin = 1039448
swapfree_end = 0
delta = 
total_pages_touched = 0
procs = 0
total_procs = 
kthreads = 0
scale = 
usage = {ru_utime = {tv_sec = -1074868352, tv_usec = -2147137980}, 
ru_stime = {tv_sec = 0, tv_usec = -1074868204}, {ru_maxrss = -1217433600, 
__ru_maxrss_word = -1217433600}, {ru_ixrss = 10, __ru_ixrss_word = 10}, 
{ru_idrss = -1, __ru_idrss_word = -1}, {ru_isrss = -1217433600, __ru_isrss_word 
= -1217433600}, {ru_minflt = -1219166696, __ru_minflt_word = -1219166696}, 
{ru_majflt = -1217324968, __ru_majflt_word = -1217324968}, {ru_nswap = 
-1217433600, __ru_nswap_word = -1217433600}, {ru_inblock = -1074868108, 
__ru_inblock_word = -1074868108}, {ru_oublock = -1217155840, __ru_oublock_word 
= -1217155840}, {ru_msgsnd = 524288, __ru_msgsnd_word = 524288}, {ru_msgrcv = 
-1, __ru_msgrcv_word = -1}, {ru_nsignals = -2147123200, __ru_nsignals_word = 
-2147123200}, {ru_nvcsw = 3, __ru_nvcsw_word = 3}, {ru_nivcsw = -2147131877, 
__ru_nivcsw_word = -2147131877}}
pid = 
mappings = 
(gdb)

Bug#865303: libreoffice: Libreoffice crashes silently upon startup after complaining about canberra module and murrine engine

[Rene Engelhard]

tag 865303 - unreproducible
severity 865303 important
severity 865303 libreoffice: Libreoffice Java features crash with Linux 
3.16.43-2+deb8u1
reassign 865303 src:linux
found 865303 3.16.43-2+deb8u1
affects 865303 libreoffice
thanks

Hi,

On Tue, Jun 20, 2017 at 09:55:51PM +0200, Rene Engelhard wrote:
> On Tue, Jun 20, 2017 at 09:33:22PM +0200, Eduardo Casais wrote:
> > >I installed a fresh jessie inside a libvirt VM. The installer alraedy
> > >applies the security updates - thus I got the new kernel and libc6 etc.
> > >(libffi isn't used by LO)
> > >
> > >Starts fine for me...
> > >
> > >-> unreproducible
> [...]
> > As a complement to the installation of LibreOffice, following extensions had
> > been set up:
> > 
> > terminologie-1.3.1.oxt
> 
> https://extensions.libreoffice.org/extensions/correcteur-terminologique-francais
> 
> seriously? tested only with 3.5?
[...]
> They should simply be data, so no. Except maybe terminologie which I can't
> download but it links to https://github.com/portaildulibre/CTLO/ which shows
> it's Java...

OK; that was the clue. I already saw openjdk accessed in your strace but that's
the case also in normal startup if you have Java stuff.

Indeed, LOs Java stuff crash :(. Checked with "just" creating a database.
(which uses hsqldb.)

Downgrading _the kernel_ (and of course rebooting) fixes it. 

No idea whether only LOs Java stuff is affected or more JDK usage (besides
#865311...), but...

Regards,
 
Rene

Bug#739081: wine32:i386 : Depends: libwine:i386 (= 1.8.7-2) but it is not going to be installed

[Stephen Kitt]

Hi Aniol,

On Tue, 20 Jun 2017 22:43:02 +0200, Aniol Martí  wrote:
> Related to this bug: when I try to install wine32 as said in #10 I get 
> the error:
> 
> "wine32:i386 : Depends: libwine:i386 (= 1.8.7-2) but it is not going to 
> be installed"
> 
> Trying to install the dependencies, the last one is "libsystemd0:i386", 
> and obviously it tries to remove a lot of packages.

I’m not sure about “obviously”; on my system (running Stretch), I have
libsystemd0:amd64 and libsystemd0:i386 installed side by side.

Could you copy and paste the output from your attempt to install
libsystemd0:i386?

Thanks,

Stephen


pgpJtNJKzDzSX.pgp
Description: OpenPGP digital signature

Bug#865386: Overly tight permissions on the root of images made with live-wrapper

[Steve McIntyre]

Source: live-wrapper
Version: 0.6+nmu1
Severity: minor

The root directory of the ISO image is mode 0700
(i.e. drwx--). This is clearly coming through from the temporary
directory it's derived from, created using tempnam. This is rather
silly and pointless, but hardly critical. Patch coming soon.

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

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

Bug#865385: RM: python-django-authority/0.5-2

[Adrian Bunk]

Package: release.debian.org
Severity: normal
Tags: jessie
User: release.debian@packages.debian.org
Usertags: rm

As described in #822476, the version of this package in jessie
does not work with the Django 1.7 in jessie.

(More recent upstream versions would work, but the package is
 orphaned and the same package is still in unstable.)

Bug#865383: RM: rant/0.5.8-8

[Adrian Bunk]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

#831392 rant: cannot load such file -- rant/rantlib (LoadError)

This error that always happens when just attempting to run rant
is also in jessie, and already led to the removal from unstable
in #831393.

Bug#856590: systemd: Unspecified problems mounting /usr partition

[Michael Biebl]

Am 20.06.2017 um 22:54 schrieb Michael Biebl:
> Unfortunately the problem is not reproducible here (tried with a VM with
> several attached disks and a split /usr on the second disk).

I take that back. I just installed live-config-systemd in the test VM
and that completely hosed the systemd and I'm getting the exact same
error message as you.

I'll be waiting for confirmation from you that purging the
live-config-systemd package solves your problem before re-assigning the
issue.

Regards,
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#865384: Volume ID not set

[Steve McIntyre]

Source: live-wrapper
Version: 0.6+nmu1
Severity: important

live-wrapper doesn't specify a Volume ID when calling xorriso, so all
its output images will end up with the xorriso-default Volume ID
"ISOIMAGE". Patch shortly...

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

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

Bug#865275: libcgicc-dev: XHTMLDoctype.h fails to include MStreamable.h

[Thomas Pircher]

On 2017-06-20 09:04, Par-Ola Nilsson wrote:

Editing XHTMLDoctype.h and replacing <> with "" fixes the problem


Hi Par-Ola,

thanks for the report. This was also reported upstream as 
http://savannah.gnu.org/bugs/?49557

Bug#856590: systemd: Unspecified problems mounting /usr partition

[Michael Biebl]

Am 20.06.2017 um 22:54 schrieb Michael Biebl:
> Mar 29 21:23:39 abijah systemd[268]:
> /lib/systemd/system-generators/live-config-getty-generator failed with
> error code 2.
> 
> How exactly did you install the system?
> This file seems to belong to live-config-systemd, can you try and purge
> that package?

I just noticed that there are already similar bugs filed against
live-config-systemd:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855085
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827665

They look very related afaics and should probably be bumped to RC.

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#865381: unblock: glibc/2.24-12

[Emilio Pozuelo Monfort]

On 20/06/17 22:49, Aurelien Jarno wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> glibc version 2.24-12 includes an important security fix 
> (CVE-2017-1000366) that should probably fixed asap in buster. It
> contains other changes which should have no impact on
> debian-installer. Here is the full changelog:
> 
> | glibc (2.24-12) unstable; urgency=high
> | 
> |   [ Aurelien Jarno ]
> |   * debian/patches/git-updates.diff: update from upstream stable branch:
> | - Drop patches/any/cvs-remove-pid-tid-cache-clone.diff (merged 
> upstream).
> | - Remove wrong assertion on parent PID in fork.
> | - Fix 64-bit atomics on m68k.  Closes: #855692.
> |   * debian/debhelper.in/libc.templates: update the kernel 3.2 warning to
> | mention that the support limitation comes from Debian and not from
> | upstream.  Closes: #864720.
> |   * debian/rules, debian/rules.d/build.mk: do not capture the build path
> | when generating glibc-source tarball.  Closes: #861183.
> |   * debian/control.in/main: build-depends on gperf.  Closes: #847478.
> |   * debian/patches/hppa/submitted-longjmp.diff: new patch from Helge Deller
> | to fix longjmp on hppa.  Closes: #858738.
> |   * debian/sysdeps/mipsel.mk, debian/sysdeps/mips64el.mk: leave the default
> | GCC ISA level, currently MIPS32R2/MIPS64R2.
> |   * debian/patches/any/local-CVE-2017-1000366-rtld-LD_AUDIT.diff,
> | debian/patches/any/local-CVE-2017-1000366-rtld-LD_LIBRARY_PATH.diff,
> | debian/patches/any/local-CVE-2017-1000366-rtld-LD_PRELOAD.diff: add
> | patches to protect the dynamic linker against stack clashes
> | (CVE-2017-1000366).
> |   * debian/patches/any/cvs-vectorized-strcspn-guards.diff: patch backported
> | from upstream to allow usage of strcspn in ld.so.
> |   * debian/patches/any/cvs-hwcap-AT_SECURE.diff: patch backported from
> | upstream to disable HWCAP for AT_SECURE programs.
> | 
> |   [ John Paul Adrian Glaubitz ]
> |   * debian/sysdeps/sh3.mk: copy from sh4.mk.  Closes: #851867.
> | 
> |  -- Aurelien Jarno   Sun, 18 Jun 2017 20:04:53 +0200
> 
> Could you therefore please unblock this package:
> 
> unblock glibc/2.24-12

There is no block in place anymore, so this should migrate on its own once it
builds in all architectures and the age requirements are met.

Perhaps you want us to urgent this instead? For now I have increased the build
priority in armel/armhf.

Cheers,
Emilio

Bug#856590: systemd: Unspecified problems mounting /usr partition

[Michael Biebl]

Am 20.06.2017 um 12:32 schrieb Joel Cross:
> Dear Michael/Maintainers,
> 
> Just to update you on this: it has been 2 months since my last
> submission, and I am still having the same problem. Has anyone had the
> chance to look into what the cause could be here?

Unfortunately the problem is not reproducible here (tried with a VM with
several attached disks and a split /usr on the second disk).

I did notice in your journal log the following error message:

Mar 29 21:23:39 abijah systemd[268]:
/lib/systemd/system-generators/live-config-getty-generator failed with
error code 2.

How exactly did you install the system?
This file seems to belong to live-config-systemd, can you try and purge
that package?

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#865343: linux-image-4.9.0-3-amd64: On latest kernel java exits with SIGSEGV

[Ben Hutchings]

On Tue, 2017-06-20 at 21:47 +0100, Ben Hutchings wrote:
> Control: tag -1 - moreinfo
> Control: notfound -1 4.9.30-2
> Control: found -1 4.9.30-2+deb9u1
> Control: found -1 3.16.43-2+deb8u1
> 
> Thanks for the extra information.

One more question: are these applications started using jsvc?

Ben.

-- 
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
   A fail-safe circuit will destroy others.



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

Bug#865382: Stretch KDE live image is not stable

[Steve McIntyre]

Package: debian-live
Severity: important

When tested on (some) real hardware, the 9.0.0 and 9.0.1 live images
containing the KDE desktop are unstable, exhibiting crashes.

There is a segmentation fault in kmanage - the first obvious symptom
will be a failure to automatically log in. A workaround is to switch
to VT1 and wait for the desktop to start there. This has been
reproduced on hardware (using Intel graphics?), but not when testing
in a virtual machine.

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

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

Bug#865343: linux-image-4.9.0-3-amd64: On latest kernel java exits with SIGSEGV

[Ben Hutchings]

Control: tag -1 - moreinfo
Control: notfound -1 4.9.30-2
Control: found -1 4.9.30-2+deb9u1
Control: found -1 3.16.43-2+deb8u1

Thanks for the extra information.

Ben.

-- 
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
   A fail-safe circuit will destroy others.



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

Bug#865381: unblock: glibc/2.24-12

[Aurelien Jarno]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock

glibc version 2.24-12 includes an important security fix 
(CVE-2017-1000366) that should probably fixed asap in buster. It
contains other changes which should have no impact on
debian-installer. Here is the full changelog:

| glibc (2.24-12) unstable; urgency=high
| 
|   [ Aurelien Jarno ]
|   * debian/patches/git-updates.diff: update from upstream stable branch:
| - Drop patches/any/cvs-remove-pid-tid-cache-clone.diff (merged upstream).
| - Remove wrong assertion on parent PID in fork.
| - Fix 64-bit atomics on m68k.  Closes: #855692.
|   * debian/debhelper.in/libc.templates: update the kernel 3.2 warning to
| mention that the support limitation comes from Debian and not from
| upstream.  Closes: #864720.
|   * debian/rules, debian/rules.d/build.mk: do not capture the build path
| when generating glibc-source tarball.  Closes: #861183.
|   * debian/control.in/main: build-depends on gperf.  Closes: #847478.
|   * debian/patches/hppa/submitted-longjmp.diff: new patch from Helge Deller
| to fix longjmp on hppa.  Closes: #858738.
|   * debian/sysdeps/mipsel.mk, debian/sysdeps/mips64el.mk: leave the default
| GCC ISA level, currently MIPS32R2/MIPS64R2.
|   * debian/patches/any/local-CVE-2017-1000366-rtld-LD_AUDIT.diff,
| debian/patches/any/local-CVE-2017-1000366-rtld-LD_LIBRARY_PATH.diff,
| debian/patches/any/local-CVE-2017-1000366-rtld-LD_PRELOAD.diff: add
| patches to protect the dynamic linker against stack clashes
| (CVE-2017-1000366).
|   * debian/patches/any/cvs-vectorized-strcspn-guards.diff: patch backported
| from upstream to allow usage of strcspn in ld.so.
|   * debian/patches/any/cvs-hwcap-AT_SECURE.diff: patch backported from
| upstream to disable HWCAP for AT_SECURE programs.
| 
|   [ John Paul Adrian Glaubitz ]
|   * debian/sysdeps/sh3.mk: copy from sh4.mk.  Closes: #851867.
| 
|  -- Aurelien Jarno   Sun, 18 Jun 2017 20:04:53 +0200

Could you therefore please unblock this package:

unblock glibc/2.24-12

Thanks,
Aurelien

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

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

Bug#861657: minidlna: apt remove --purge minidlna does not purge user, group, /run/minidlna directory

[Jean-Marc]

On Wed, 3 May 2017 06:38:24 +0200 Jean-Marc  wrote:
> > 2. Default installation creates directory /var/lib/minidlna as home
> > directory for minidlna user and system administrator could put media
> > files in there.
> > I can't remove this directory completely on package purge, because
> > admin, not minidlnad manage files in this directory.
> > I can't remove minidlna user either, because this could lead
> > to /var/lib/minidlna have numeric owner/group. The next package
> > installed will use this free uid/gid and get access to the files.
> > Please see https://wiki.debian.org/AccountHandlingInMaintainerScripts
> > for some more explanation on the topic.
> 
> Just for info, /var/lib/minidlna directory is not present anymore.
> Anyway, I'll take a look at the wiki's page.

I briefly looked at the wiki's page.

And, apparently, there are reason to remove users accounts and reasons to not 
remove users accounts.

So, I understand you opt to keep the user/group even after purging the package.

If you do not see any reason to keep this bug open, can you, please, close it ?

Regards,


Jean-Marc 


pgp6WLFV2hyE9.pgp
Description: PGP signature

Bug#865311: #865311: security update for CVE-2017-1000364 breaks UniFi Controller

[Markus Koschany]

reassign 865311 src:linux
retitle 865311 security update for CVE-2017-1000364 breaks UniFi Controller
thanks

Am 20.06.2017 um 22:30 schrieb Charles Leclerc:
> Downgrading linux-image-3.16.0-4-amd64 to 3.16.43-2 defenitely fixes the
> problem.

Ok, then I am going to reassign this bug report to src:linux because
this looks like a kernel regression.

Summary:


Security update for CVE-2017-1000364 breaks the UniFi controller and
leads to segmentation faults when using the jsvc package.

Regards,

Markus






signature.asc
Description: OpenPGP digital signature

Bug#739081: wine32:i386 : Depends: libwine:i386 (= 1.8.7-2) but it is not going to be installed

[Aniol Martí]

Hello,

Related to this bug: when I try to install wine32 as said in #10 I get 
the error:


"wine32:i386 : Depends: libwine:i386 (= 1.8.7-2) but it is not going to 
be installed"


Trying to install the dependencies, the last one is "libsystemd0:i386", 
and obviously it tries to remove a lot of packages.



Thank you,

Aniol

Bug#865311: #865311: security update for CVE-2017-1000364 breaks UniFi Controller

[Markus Koschany]

reassign -1 src:linux
retitle -1 security update for CVE-2017-1000364 breaks UniFi Controller
thanks

Am 20.06.2017 um 22:30 schrieb Charles Leclerc:
> Downgrading linux-image-3.16.0-4-amd64 to 3.16.43-2 defenitely fixes the
> problem.

Ok, then I am going to reassign this bug report to src:linux because
this looks like a kernel regression.

Summary:


Security update for CVE-2017-1000364 breaks the UniFi controller and
leads to segmentation faults when using the jsvc package.

Regards,

Markus




signature.asc
Description: OpenPGP digital signature

Bug#865380: libtest-unixsock-perl: Build-Conflicts-Indep: libtest-simple-perl (>= 1.3), including Perl 5.26

[Niko Tyni]

Package: libtest-unixsock-perl
Version: 0.1-1
Severity: important
User: debian-p...@lists.debian.org
Usertags: perl-5.26-transition

This package Build-Conflicts-Indep: libtest-simple-perl (>= 1.3),
for reasons that aren't immediately obvious.

This was OK-ish for stretch, where src:perl had an old enough Test-Simple
so the Build-Conflicts-Indep just kept the newer separate package
away. However, Perl 5.26 bundles a newer Test-Simple, and the change to
versioned Provides there means the build dependencies/conflicts can't
be satisfied at all anymore.

There's an example build log at
 
http://perl.debian.net/rebuild-logs/perl-5.26-throwaway/libtest-unixsock-perl_0.1-1/libtest-unixsock-perl_0.1-1_amd64-2017-05-21T14:10:46Z.build

and the server also hosts a repository of packages binNMU'd for Perl
5.26 that can be used for testing purposes; see .
-- 
Niko Tyni   nt...@debian.org

Bug#865354: java.lang.NoClassDefFoundError: org/apache/tomcat/InstanceManager

[Joe Pfeiffer]

Yes --

snowball:569$ dpkg -l "*eclipse*" | grep ii
ii  eclipse 3.8.1-10 all  Extensible Tool Platform 
and Java IDE
ii  eclipse-jdt 3.8.1-10 all  Eclipse Java Development 
Tools (JDT)
ii  eclipse-pde 3.8.1-10 amd64Eclipse Plug-in 
Development Environment (PDE)
ii  eclipse-platform3.8.1-10 amd64Eclipse platform without 
development plug-ins
ii  eclipse-platform-data   3.8.1-10 all  Eclipse platform without 
development plug-ins (data)
ii  eclipse-rcp 3.8.1-10 amd64Eclipse Rich Client 
Platform (RCP)

So...  should this bug be reported against eclipse (or, I suppose,
eclipse-platform-data)?  And can you suggest a workaround?

Emmanuel Bourg writes:
>Thank your for the report Joe. The InstanceManager class is in
>/usr/share/java/tomcat8-api.jar. It looks like this jar is missing from
>the classpath used by Eclipse. Did you use the version of eclipse
>currently in testing/unstable?
>
>Emmanuel Bourg

-- 
Joe Pfeiffer   575.525.2764 (H)
1440 Tierra del Sol Dr 575.496.3501 (C)
Las Cruces, NM 88007-5548  

Bug#865379: Package removal ahead

[Ole Streicher]

Source: iausofa-c
Severity: serious

As we discussed in the debian-astro mailing list, this package is
subject to be removed in the Buster cycle. This mail is the last call to
either switch to the free "erfa" package with the same API (except that
the prefix is replaced by "era"), or to scream loudly and take over.

If there is no such response within a week, I will file a request to
remove this package.

Best regards

Ole

Bug#865376: [Pkg-lirc-maint] Bug#865376: lirc: When upgrading from Jessie to Stretch, an old file /etc/init.d/lirc is not deleted

[Alec Leamas]

On 20/06/17 22:09, Mikulas Patocka wrote:


In Debian Jessie, lirc is started with the /etc/init.d/lirc script
In Debian Stretch, lirc is started with the /etc/init.d/lircd script


This is not the whole truth. The old lirc script actually controlled all 
of the the lirc services, lircd being one of them.



The old file /etc/init.d/lirc should be deleted during the upgrade.


Yes. This is a plain bug.

However, the lirc /etc/init.d scripts are maintained on a "patches 
welcome" basis. Upstream is systemd oriented, and to control lirc using 
the old sysV scripts is problematic (e.g., the socket activation of 
lircd does not work which might lead to subtle boot problems). Also, 
using sysV is not really documented.


So, I'd happily apply a patch for this if someone provides it, but 
otherwise probably leave it as is.


Cheers!

--alec

Bug#865378: guake: WM_CLASS is unhelpful ("Main.py")

[Matthew Woodcraft]

Package: guake
Version: 0.8.8-1
Severity: normal

In Jessie (guake 0.4.4), guake's WM_CLASS X property (according to xprop) was:
WM_CLASS(STRING) = "guake", "Guake"

In Stretch, it's the less informative
WM_CLASS(STRING) = "guake", "Main.py"

This makes it less convenient to configure window managers to give Guake
special treatment.


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

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

Versions of packages guake depends on:
ii  gconf2   3.2.6-4+b1
ii  libgtk2.0-0  2.24.31-2
ii  notification-daemon  3.20.0-1+b1
ii  python   2.7.13-2
ii  python-dbus  1.2.4-1+b1
ii  python-gconf 2.28.1+dfsg-1.2
ii  python-glade22.24.0-5.1
ii  python-keybinder 0.3.1-1
ii  python-notify0.1.1-4
ii  python-vte   1:0.28.2-5+b2
ii  python-xdg   0.25-4
ii  python2.72.7.13-2

guake recommends no packages.

guake suggests no packages.

-- no debconf information

Bug#864639: nvidia-kernel-dkms: please support parallel builds

[Andras Korn]

On Thu, Jun 15, 2017 at 02:25:42PM +0200, Andreas Beckmann wrote:

> On 2017-06-12 08:27, Andras Korn wrote:
> > even if dkms would pass make(1) a -j flag. (Also, while I'm sure there once
> > was a reason for setting CCACHE_DISABLE=1, does it still apply?)
> 
> I don't remember the details ... #582748 ... looks like this bug in
> ccache 2.4 was fixed in ccache 3.0 (which was in squeeze).

Then I'd suggest dropping CCACHE_DISABLE because ccache can help speed up
builds a lot.

> > I haven't tested it, but maybe the following would work:
> > 
> > [ -x /usr/bin/nproc ] && JOBS="-j$(nproc)"
> > MAKE[0]="unset ARCH; env CCACHE_DISABLE=1 NV_VERBOSE=1 \
> > make $JOBS modules KERNEL_UNAME=${kernelver}"
> 
> Let's just honor the -j option from dkms:
> 
> MAKE[0]="unset ARCH; env CCACHE_DISABLE=1 NV_VERBOSE=1 \
> make ${parallel_jobs+-j$parallel_jobs} modules
> KERNEL_UNAME=${kernelver}"

This looks good, provided the file is sourced (dkms doesn't currently export
the parallel_jobs variable, so that a child process wouldn't see it).

András

-- 
  Yoda of Borg, I am. Assimilated you will be, hmmm?

Bug#865377: dolphin: Devices list not updated after ejecting Media (external DVD drive)

[Maria]

Package: dolphin
Version: 4:16.08.3-3
Severity: normal

Dear Maintainer,

after ejecting media from my external USB DVD drive the "Devices" list is not
updated. A newly inserted disk leads to a new entry with the new name of the
disk. After doing this with e.g. 5 disks I got 5 different entries in devices.

I would expect the entry to disappear after ejecting.

Thanks for your work!



-- System Information:
Debian Release: 9.0
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500,
'testing'), (100, 'unstable')
Architecture: amd64 (x86_64)

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

Versions of packages dolphin depends on:
ii  baloo-kf5  5.28.0-2
ii  kinit  5.28.0-1
ii  kio5.28.0-2
ii  libc6  2.24-11
ii  libdolphinvcs5 4:16.08.3-3
ii  libkf5baloo5   5.28.0-2
ii  libkf5baloowidgets516.04.0-1+b1
ii  libkf5bookmarks5   5.28.0-1
ii  libkf5codecs5  5.28.0-1+b2
ii  libkf5completion5  5.28.0-1
ii  libkf5configcore5  5.28.0-2
ii  libkf5configgui5   5.28.0-2
ii  libkf5configwidgets5   5.28.0-2
ii  libkf5coreaddons5  5.28.0-2
ii  libkf5crash5   5.28.0-1
ii  libkf5dbusaddons5  5.28.0-1
ii  libkf5filemetadata35.28.0-1+b2
ii  libkf5i18n55.28.0-2
ii  libkf5iconthemes5  5.28.0-2
ii  libkf5itemviews5   5.28.0-1
ii  libkf5jobwidgets5  5.28.0-2
ii  libkf5kcmutils55.28.0-2
ii  libkf5kiocore5 5.28.0-2
ii  libkf5kiofilewidgets5  5.28.0-2
ii  libkf5kiowidgets5  5.28.0-2
ii  libkf5newstuff55.28.0-1
ii  libkf5notifications5   5.28.0-1
ii  libkf5parts5   5.28.0-1
ii  libkf5service-bin  5.28.0-1
ii  libkf5service5 5.28.0-1
ii  libkf5solid5   5.28.0-3
ii  libkf5textwidgets5 5.28.0-1
ii  libkf5widgetsaddons5   5.28.0-3
ii  libkf5windowsystem55.28.0-2
ii  libkf5xmlgui5  5.28.0-1
ii  libphonon4qt5-44:4.9.0-4
ii  libqt5core5a   5.7.1+dfsg-3+b1
ii  libqt5dbus55.7.1+dfsg-3+b1
ii  libqt5gui5 5.7.1+dfsg-3+b1
ii  libqt5widgets5 5.7.1+dfsg-3+b1
ii  libqt5xml5 5.7.1+dfsg-3+b1
ii  libstdc++6 6.3.0-18
ii  phonon4qt5 4:4.9.0-4

Versions of packages dolphin recommends:
ii  kio-extras  4:16.08.3-1
ii  ruby1:2.3.3

Versions of packages dolphin suggests:
ii  dolphin-plugins  4:16.08.3-1

Bug#864906: apt-cudf: gives invalid solutions involving mixed versioned/unversioned provides

[Ralf Treinen]

Hi James,

On Fri, Jun 16, 2017 at 09:22:41PM +0100, James Cowgill wrote:
> Package: apt-cudf
> Version: 5.0.1-8
> Severity: normal
> 
> Hi,
> 
> This bug has arisen after I started looking at why pdl 1:2.018-1~exp1
> has been failing to install its dependencies in experimental.
> 
> https://buildd.debian.org/status/package.php?p=pdl=experimental
> 
> The failures only happen when the aspcud solver is used. When the normal
> APT solver is used, everything works fine.
> 
> The error in pdl seems to revolve around the versioned provides of
> perl-base which currently confuse apt-cudf because perl-base in sid does
> NOT use versioned provides, but perl-base in experimental does.

thanks for the bug report, and for having worked out the nice example
edsp file. The problem is related to versionend Provides, almost as 
you suspected. 

The semantics of CUDF is that *unversionend* Provides provide all
possible versions of a virtual package, that is eggplant(=1) in your
example will satisfy not only a dependency on cantelope, but also any
versionend dependency on cantalope, whatever the version constraint.
That choice seemed reasonable to us at the time when we designed the format,
but we didn't think of a scenario of gradually moving from unversioned
provides to versionend provides.

I have the impression that we have encountered that problem before and
that we had solved it. Maybe it is solved in dose-debcheck, but not
in apt-cudf? I will try to look into this, but it will take a few days.

-Ralf.

Bug#865374: libdigest-sha3-perl: sha3sum perl v5.24.1 and v5.20.0 create a different checksum for the same input

[Niko Tyni]

Control: forwarded -1 https://rt.cpan.org/Public/Bug/Display.html?id=110364

On Tue, Jun 20, 2017 at 09:50:20PM +0200, Honovere wrote:
> Package: libdigest-sha3-perl
> Version: 0.25-1+b1
> Severity: important
> 
> Dear Maintainer,
> 
> checksums created with sha3sum for the exact same input with Debian 8 and 9 
> are different. They should be identical.

Hi, this seems to expected behaviour. Quoting the upstream author in

 https://rt.cpan.org/Public/Bug/Display.html?id=110364

  Yes, the outputs are different. As of version 0.23 the Digest::SHA3
  module reflects the then-recent updates made to FIPS 202 which called
  for the use of domain separation bits (ref. the Changes file). These
  updates caused changes to all digest outputs, as expected.

  To my knowledge the current Digest::SHA3 module passes all official,
  published test vectors, including those with partial-byte inputs. If
  you know of any exceptions, let me know

So it looks like the standard is/was still evolving.
-- 
Niko Tyni   nt...@debian.org

Bug#865273: libqt5webengine5: Make 5.9 available in experimental

[Jiri Horner]

On Tue, Jun 20, 2017 at 11:45:18AM +0200, Sandro Knauß wrote:

Hey,


would it be possible to make available qtwebengine 5.9 in experimental with
the rest of the Qt stack? This package seems to be the only one omitted.


well we try to update it as fast as possible, but QtWebEngine is not very easy
to package, that's why it is not uploaded right now. But in our git repo you
find a preversion of the package ( to build locally):
https://anonscm.debian.org/cgit/pkg-kde/qt/qtwebengine.git/commit/?
h=experimental



Thanks I have missed that. I will build that locally. I understand that 
qtwebengine is quite a beast. Thanks for all your work to get this packaged in 
debian, it makes my life much easier.



I'd like to test my app in debian with Qt 5.9.

I'm curious, what app your are packaging, that uses QtWebEngine 5.9?



It does not require 5.9, it runs fine with 5.7 in sid. I just want to make sure 
that it will continue to run fine with 5.9.


Cheers,
Jiri

Bug#853700: vifm: Fixed in 0.9-1

[Ondrej Novy]

Hi,

vifm should be buildable in gcc-7 now. You requested to not close this
bug (until
the package can be build in a follow-up test rebuild), so I'm keeping it
open.

Thanks.

-- 
Best regards
 Ondřej Nový

Bug#865376: lirc: When upgrading from Jessie to Stretch, an old file /etc/init.d/lirc is not deleted

[Mikulas Patocka]

Package: lirc
Version: 0.9.4c-9
Severity: normal

Dear Maintainer,

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

   * What led up to the situation?

In Debian Jessie, lirc is started with the /etc/init.d/lirc script
In Debian Stretch, lirc is started with the /etc/init.d/lircd script

When upgrading from Jessie to Stretch, the old script /etc/init.d/lirc is not
deleted,
leaving the system with two scripts to start lirc. Both of these scripts are
symlinked
to /etc/rc?.d/ directories, this results in lirc not working and failures being
reported
during shutdown.

The problem goes away if the lirc package in Stretch is purged and re-installed
(the purge
operation deletes both of the scripts in /etc/init.d)

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Install lirc in Jessie, configure it, and then upgrade to Stretch

   * What was the outcome of this action?

lirc doesn't work and there are two files in init.d
/etc/init.d/lirc
/etc/init.d/lircd

   * What outcome did you expect instead?

The old file /etc/init.d/lirc should be deleted during the upgrade.



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

Kernel: Linux 4.4.72 (SMP w/12 CPU cores; PREEMPT)
Locale: LANG=cs_CZ.utf8, LC_CTYPE=cs_CZ.utf8 (charmap=UTF-8), 
LANGUAGE=cs_CZ.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

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

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

Versions of packages lirc suggests:
pn  ir-keytable  
pn  lirc-compat-remotes  
pn  lirc-doc 
pn  lirc-drv-irman   
pn  lirc-x   
ii  setserial2.17-50

-- no debconf information

Bug#865375: gnome-software-plugin-flatpak: clicking on a application on http://flatpak.org/apps.html says "file is not supported"

[Cedric BRINER]

Package: gnome-software-plugin-flatpak
Version: 3.22.5-1
Severity: normal

Hi,

Flatpak could ease the way that user install software. I've installed gnome-
software-plugin-flatpak, wishing that gnome-software will be able to install
clicked link on http://flatpak.org/apps.html. Gnome-software tells me in
french:
'''
Désolé, ça n'a pas marché.
Le fichier n'est pas pris en charge
'''

which could be translated as
'''
Sorry, that didn't work.
The file is not supported
'''





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

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

Versions of packages gnome-software-plugin-flatpak depends on:
ii  flatpak 0.8.6-1
ii  gnome-software  3.25.1-1
ii  libc6   2.24-11
ii  libflatpak0 0.8.6-1
ii  libglib2.0-02.50.3-2

gnome-software-plugin-flatpak recommends no packages.

gnome-software-plugin-flatpak suggests no packages.

-- no debconf information

Bug#865303: libreoffice: Libreoffice crashes silently upon startup after complaining about canberra module and murrine engine

[Rene Engelhard]

Hi,

On Tue, Jun 20, 2017 at 09:33:22PM +0200, Eduardo Casais wrote:
> >I installed a fresh jessie inside a libvirt VM. The installer alraedy
> >applies the security updates - thus I got the new kernel and libc6 etc.
> >(libffi isn't used by LO)
> >
> >Starts fine for me...
> >
> >-> unreproducible
[...]
> As a complement to the installation of LibreOffice, following extensions had
> been set up:
> 
> terminologie-1.3.1.oxt

https://extensions.libreoffice.org/extensions/correcteur-terminologique-francais

seriously? tested only with 3.5?

> Portuguese spelling dictionaries and thesaurus 15.7.4.1
> German ch-frami spelling hyphenation thesaurus 2013.3.12.06
> Dictionnaire français 5.3 Synonymes 2.3 Césures 3.0
> Español España y América Latina ortografia 0.8 separación 0.2 sinónimos
> 24/02/2013
> 
> I have no idea whether these add-ons rely upon a library that changed with
> the Debian update, causing the crash.

They should simply be data, so no. Except maybe terminologie which I can't
download but it links to https://github.com/portaildulibre/CTLO/ which shows
it's Java...

What happens if you remove that terminologie?

Sorry, we can't support any random extension out there especially when
they themselves claim it's tested only with 3.5 and you use 4.3.3...

Regards,

Rene

Bug#865343: linux-image-4.9.0-3-amd64: On latest kernel java exits with SIGSEGV

[Sasa Skevin]

On Tue, Jun 20, 2017 at 9:01 PM Ben Hutchings  wrote:

> >
> > I'm administering several Debian servers of which some are Jessie and
> > some are Stretch. On both of them after upgrading to latest kernel that
> > was released yesterday (4.9 on Stretch and 3.16 on Jessie), Java web
> > applications do not work any more. They stop with SIGSEGV in the Java
> > startup process.
>
> So I think you meant to report this against versions 3.16.43-2+deb8u1
> and 4.9.30-2+deb9u1, not 4.9.30-2.  Is that right?
>

Correct.


> > Have tried more different Java web applications and while booting all of
> > them break with SIGSEGV while Java internaly loads rt.jar.
> >
> > Have tried with Oracle Java 1.8.0_130, Oracje Java 1.8.0_131 and latest
> > OpenJDK 8 and the same error happens.
> >
> > Even the servers on which this is tried are from different hosting
> > companies.
> [...]
>
> Does this go away if you add the kernel parameter "stack_guard_gap=1"?
> (That should effectively revert the fix for CVE-2017-1000364.)
>

Yes, it goes away with this kernel parameter.


> Has the stack limit for these applications been changed from the
> default (e.g. "ulimit -s unlimited" in a startup script)?
>

No, they are on default values.

Sasa

Bug#865057: stretch-pu: package open-iscsi/2.0.874-2

[Cyril Brulebois]

Hi,

Cyril Brulebois  (2017-06-19):
> After a quick review, that looks good to me. Thanks for keeping the
> changes minimal in unstable, which indeed can help test this further.
> 
> Also thanks for keeping track of this without my chasing you with my 9.1
> todo list. ;)
> 
> I'll report back once I've tested this change from unstable, just to be
> sure; release team: please wait a bit before letting this go through pu.

Release team: looks good to me.


KiBi.


signature.asc
Description: Digital signature

Bug#865374: libdigest-sha3-perl: sha3sum perl v5.24.1 and v5.20.0 create a different checksum for the same input

[Honovere]

Package: libdigest-sha3-perl
Version: 0.25-1+b1
Severity: important

Dear Maintainer,

checksums created with sha3sum for the exact same input with Debian 8 and 9 are 
different. They should be identical.

Example commands taken from manpage sha3sum:


Debian 8:
libdigest-sha3-perl v0.22-2
perl v5.20.0

$ perl -e "print qq(abc)" | sha3sum
c30411768506ebe1c2871b1ee2e87d38df342317300a9b97a95ec6a8  -

$ perl -e "print qq(0001100)" | sha3sum -0 -a 384
eaa09c53230f6e9a071f770b99e633f24dc35d2fca4a93687b0d7baba808d9a26cc43f63f617159f2fb52bb01fa237a5
 ^-


Debian 9:
libdigest-sha3-perl v0.25-1+b1
perl v5.24.1

$ perl -e "print qq(abc)" | sha3sum
e642824c3f8cf24ad09234ee7d3c766fc9a3a5168d0c94ad73b46fdf  -

$ perl -e "print qq(0001100)" | sha3sum -0 -a 384
b5a8cb0bf073b6b68d95cd33f5b09289670120bb931fc838b830d2592268b9e145a09088172b96eafb0093ef9a85df08
 ^-


(Checksums created with sha512sum are identical for same input with Debian 8 
and 9.)

Thanks and kind regards!


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

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

Versions of packages libdigest-sha3-perl depends on:
ii  libc6   2.24-11+deb9u1
ii  perl5.24.1-3
ii  perl-base [perlapi-5.24.1]  5.24.1-3

libdigest-sha3-perl recommends no packages.

libdigest-sha3-perl suggests no packages.

-- no debconf information

Bug#865373: autoconf2.13_2.13-67 is unusable due to missing symlink

[Mikulas Patocka]

Package: autoconf2.13
Version: 2.13-67
Severity: important

Dear Maintainer,

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

   * What led up to the situation?

After upgrading to Debian Stretch, autoheader2.13 doesn't work.
It is missing the symlink /usr/share/autoconf2.13/acconfig.h ->
/etc/autoconf2.13/acconfig.h
(this symlink is present in autoconf2.13_2.13-63 and previous versions of the
package)

When I create the symlink with this command, autoheader2.13 works:
# ln -s /etc/autoconf2.13/acconfig.h /usr/share/autoconf2.13/acconfig.h

Please, add the symlink to the package and release a new version.

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

Download the links browser source
http://links.twibright.com/download/links-2.14.tar.bz2
Unpack it
Run autoheader2.13 in the source directory

   * What was the outcome of this action?

$ autoheader2.13
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
sed: can't read /usr/share/autoconf2.13/acconfig.h: No such file or directory
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `C_BIG_ENDIAN' is not covered by
/usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `C_LITTLE_ENDIAN' is not covered by
/usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `DEBUGLEVEL' is not covered by
/usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `DONT_INCLUDE_SETJMP' is not covered by
/usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `ENABLE_UTF8' is not covered by
/usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `G' is not covered by
/usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `GRDRV_ATHEOS' is not covered by
/usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `GRDRV_DIRECTFB' is not covered by
/usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `GRDRV_FB' is not covered by
/usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `GRDRV_GRX' is not covered by
/usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `GRDRV_PMSHELL' is not covered by
/usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `GRDRV_SVGALIB' is not covered by
/usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `GRDRV_X' is not covered by
/usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `HAVE_BEGINTHREAD' is not covered by
/usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `HAVE_BZIP2' is not covered by
/usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `HAVE_CLOCK_GETTIME' is not covered by
/usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `HAVE_CRYPTO_SET_MEM_FUNCTIONS_1' is not
covered by /usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `HAVE_CRYPTO_SET_MEM_FUNCTIONS_2' is not
covered by /usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `HAVE_DOPRNT' is not covered by
/usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `HAVE_ERRNO' is not covered by
/usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: /usr/share/autoconf2.13/acconfig.h: No such file or directory
/usr/bin/autoheader2.13: Symbol `HAVE_GETHOSTBYNAME' is not covered by
/usr/share/autoconf2.13/acconfig.h ./acconfig.h
grep: 

Bug#848931: source-only builds and .buildinfo

[Sean Whitton]

Hello Ian,

On Tue, Jun 20, 2017 at 06:10:49PM +0100, Ian Jackson wrote:
> In the absence of objections to my analysis, I suggest we proceed on
> the following basis:
> 
> A .buildinfo file is not useful for a source-only upload which is
> veried to be identical to the intended source as present in the
> uploader's version control (eg, by the use of dgit).
> 
> Therefore, dgit should not include .buildinfos in source-only uploads
> it performs.  If dgit sees that a lower-layer tool like
> dpkg-buildpackage provided a .buildinfo for a source-only upload, dgit
> should strip it out of .changes.

Thank you for this text.

I think that dgit should strip the .buildinfo when it built the source
package itself, as part of a build-source or push-source run, but what
about when the user supplies a .changes, with -C, to push-source?

I don't think that dgit should modify the .changes in that case, because
it is counterintuitive when the user has provided a particular .changes
they want dgit to verify and then upload.  Maybe it should refuse to
push if the .buildinfo is present, though?  Possibly with a
--deliberately-include-buildinfo to override.

W.r.t. building source packages, do you still think that we should be
using dpkg-source to build it, or just continue invoking
`dpkg-buildpackage -S -us`?  This is relevant for both build-source and
push-source.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#865372: firefox-esr: 45.9.0esr-1~deb8u1 to 52.2.0esr-1~deb8u1 breaks profiles

[flaz]

Package: firefox-esr
Version: 45.9.0esr-1~deb8u1
Severity: important

   * What led up to the situation?
security upgrade from 45.9.0esr-1~deb8u1 to 52.2.0esr-1~deb8u1
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Launched Firefox : opens default profile. Opened a new profile from the default
profile window. The new window-profile can't be used : no browsing, installed
extensions unavailable, stored bookmarks unvisible…
   * What was the outcome of this action?
Opened a new browser window but uneffective
   * What outcome did you expect instead?
An effective browser window with all the settings, bookmarks en plugins tied to
this profile.

Downgrading to firefox-esr: 45.9.0esr-1~deb8u1 restores everything : no profile
data is lost running 52.2.0esr-1~deb8u1 though it can't use this date (except
for default profile).



-- Package-specific info:

-- Extensions information
Name: Adblock Plus
Location: ${PROFILE_EXTENSIONS}/{d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}.xpi
Status: user-disabled

Name: DOM Inspector
Location: ${PROFILE_EXTENSIONS}/inspec...@mozilla.org
Status: user-disabled

Name: DrupalForFirebug
Location: ${PROFILE_EXTENSIONS}/drupalforfire...@drupal.org.xpi
Status: user-disabled

Name: Firebug
Location: ${PROFILE_EXTENSIONS}/fire...@software.joehewitt.com.xpi
Status: enabled

Name: Firefox Hello Beta
Location: ${PROFILE_EXTENSIONS}/l...@mozilla.org.xpi
Status: enabled

Name: FireTray
Location: 
/usr/share/mozilla/extensions/{ec8030f7-c20a-464f-9b0e-13a3a9e97384}/{9533f794-00b4-4354-aa15-c2bbda6989f8}
Package: xul-ext-firetray
Status: user-disabled

Name: Français Language Pack locale
Location: 
/usr/lib/firefox-esr/browser/extensions/langpack...@firefox-esr.mozilla.org.xpi
Package: firefox-esr-l10n-fr
Status: enabled

Name: HTTPS Everywhere
Location: ${PROFILE_EXTENSIONS}/https-everywhere-...@eff.org.xpi
Status: enabled

Name: Markdown Viewer
Location: ${PROFILE_EXTENSIONS}/markdownvie...@thiht.fr.xpi
Status: enabled

Name: Password Exporter
Location: ${PROFILE_EXTENSIONS}/{B17C1C5A-04B1-11DB-9804-B622A1EF5492}.xpi
Status: enabled

Name: Pencil
Location: ${PROFILE_EXTENSIONS}/pen...@evolus.vn.xpi
Status: app-disabled

Name: ProfileSwitcher
Location: ${PROFILE_EXTENSIONS}/{fa8476cf-a98c-4e08-99b4-65a69cb4b7d4}.xpi
Status: enabled

Name: Quick Locale Switcher
Location: ${PROFILE_EXTENSIONS}/{25A1388B-6B18-46c3-BEBA-A81915D0DE8F}.xpi
Status: user-disabled

Name: Qwant for Firefox
Location: ${PROFILE_EXTENSIONS}/qwantcomforfire...@jetpack.xpi
Status: enabled

Name: ScrapBook
Location: ${PROFILE_EXTENSIONS}/{53A03D43-5363-4669-8190-99061B2DEBA5}.xpi
Status: user-disabled

Name: Screengrab (fix version)
Location: ${PROFILE_EXTENSIONS}/{02450914-cdd9-410f-b1da-db004e18c671}.xpi
Status: enabled

Name: Selenium Builder
Location: ${PROFILE_EXTENSIONS}/seleniumbuil...@saucelabs.com
Status: app-disabled

Name: Selenium IDE
Location: ${PROFILE_EXTENSIONS}/{a6fd85ed-e919-4a43-a5af-8da18bda539f}.xpi
Status: enabled

Name: Selenium IDE: C# Formatters
Location: ${PROFILE_EXTENSIONS}/csharpformatt...@seleniumhq.org.xpi
Status: app-disabled

Name: Selenium IDE: Java Formatters
Location: ${PROFILE_EXTENSIONS}/javaformatt...@seleniumhq.org.xpi
Status: app-disabled

Name: Selenium IDE: Python Formatters
Location: ${PROFILE_EXTENSIONS}/pythonformatt...@seleniumhq.org.xpi
Status: app-disabled

Name: Selenium IDE: Ruby Formatters
Location: ${PROFILE_EXTENSIONS}/rubyformatt...@seleniumhq.org.xpi
Status: app-disabled

Name: Thème par défaut theme
Location: 
/usr/lib/firefox-esr/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}.xpi
Package: firefox-esr
Status: enabled

Name: uBlock Origin
Location: ${PROFILE_EXTENSIONS}/ublo...@raymondhill.net.xpi
Status: enabled

-- Plugins information
Name: IcedTea-Web Plugin (using IcedTea-Web 1.5.3 (1.5.3-1))
Location: /usr/lib/jvm/java-7-openjdk-amd64/jre/lib/amd64/IcedTeaPlugin.so
Package: icedtea-7-plugin:amd64
Status: enabled

Name: LibreOffice Plug-in
Location: /usr/lib/libreoffice/program/libnpsoplugin.so
Package: browser-plugin-libreoffice
Status: enabled

Name: Shockwave Flash (13.1.2.3)
Location: /usr/lib/mozilla/plugins/libfreshwrapper.so
Package: freshplayerplugin
Status: disabled

Name: Shockwave Flash (11.2.202.635)
Location: /usr/lib/flashplugin-nonfree/libflashplayer.so
Status: disabled

Name: Skype Buttons for Kopete
Location: /usr/lib/mozilla/plugins/skypebuttons.so
Package: kopete
Status: disabled


-- Addons package information
ii  browser-plugin 1:4.3.3-2+de amd64office productivity suite -- Mozi
ii  firefox-esr45.9.0esr-1~ amd64Mozilla Firefox web browser - Ext
ii  firefox-esr-l1 45.9.0esr-1~ all  French language package for Firef
ii  freshplayerplu 0.1.0+git201 amd64PPAPI-host NPAPI-plugin adapter
ii  icedtea-7-plug 1.5.3-1  amd64web browser plugin based on OpenJ
ii  kopete 4:4.14.1-2   amd64instant messaging and chat applic
ii  xul-ext-firetr 0.5.3~rc1+df 

Bug#865371: Shorewall doesn't start at boot time on Stretch

[Robert Solomon]

Package: shorewall
Version: 5.0.15.6-1

Editing /etc/default/shorewall: startup=

Does not prevent or cause shorewall to start at boot.

Instead systemctl enable (or disable) shorewall must be run.

Debian Linux v. 9.0, clean install.

I suggest that this behavior or the docs be modified.

I have added a note to this page: https://wiki.debian.org/HowTo/shorewall

ty,

Bob

-- 

Robert Solomon
Facilities Manager
Integral Yoga Institute
227 West Thirteenth Street
New York  NY 10011
p: 212 929 0585 x 25 f: 212 675 3674 c: 914 403 0908

Bug#865303: libreoffice: Libreoffice crashes silently upon startup after complaining about canberra module and murrine engine

[Eduardo Casais]

On Tue, 20 Jun 2017 20:32:48 +0200 Rene Engelhard  wrote:

tag 865303 + unreproducible
retitle 865303 libreoffice: Libreoffice crashes silently upon startup
thanks

Hi,

...

I installed a fresh jessie inside a libvirt VM. The installer alraedy
applies the security updates - thus I got the new kernel and libc6 etc.
(libffi isn't used by LO)

Starts fine for me...

-> unreproducible

Regards,

Rene


As a complement to the installation of LibreOffice, following extensions 
had been set up:


terminologie-1.3.1.oxt
Portuguese spelling dictionaries and thesaurus 15.7.4.1
German ch-frami spelling hyphenation thesaurus 2013.3.12.06
Dictionnaire français 5.3 Synonymes 2.3 Césures 3.0
Español España y América Latina ortografia 0.8 separación 0.2 sinónimos 
24/02/2013


I have no idea whether these add-ons rely upon a library that changed 
with the Debian update, causing the crash.


Sincerely

E.Casais

Bug#862514: Gcc creates illegal instructions when combining C + ASM on arm on sid

[Gianfranco Costamagna]

control: severity -1 serious

breaking packages is serious enough to me
https://bugs.launchpad.net/ubuntu/+source/meson/+bug/1698463

is an example of affected package.

Raising the severity accordingly

G.

On Sun, 14 May 2017 00:09:42 +0300 Jussi Pakkanen  wrote:
> Package: gcc
> Version: 6.3.0-4
> 
> Gcc creates binaries that fail with "invalid instruction". To
> reproduce create the following main.c:
> 
>  int get_retval(void);
> 
> int main(int argc, char **argv) {
>   return get_retval();
> }
> 
> and the following retval-arm.S
> 
> .text
> .globl get_retval
> 
> get_retval:
> mov r0, #0
> bx  lr
> 
> Compile like this:
> 
> gcc -o prog main.c retval-arm.S
> 
> The result crashes. However if you add -march=armv7 the executable
> works (-march=native crashes also).
> 
> This only happens on GCC using the version in Sid. It works when using
> any version of Clang and also when using GCC in Jessie.
> 
> Originally reported here: https://github.com/mesonbuild/meson/issues/1776
> 
> 



signature.asc
Description: OpenPGP digital signature

Bug#847768: hoichess: please make the build reproducible

[Holger Ruckdeschel]

On Mon, 19 Jun 2017 21:59:00 -0300, Samuel Henrique wrote:

> I see on the changelog of 0.20.0:
> 
> > * Included reproducible-build patch from Debian package
> >hoichess_0.19.0-3.
> >  
> 
> ​Although, 0.21.0 still has other reproducibility problems[1], could you
> help us with that?

Hello Samuel,

I have applied the attached change to my source, it will be included in the
next releases. You could still replace this by the Debian package version
as suggested by Daniel Shahaf. In this case, I kindly ask you to add e.g.
"-debian" to the version string to avoid confusion.

Best regards,
Holger
Index: src/build/print_version_str
===
--- src/build/print_version_str	(revision 2536)
+++ src/build/print_version_str	(revision 2537)
@@ -6,7 +6,6 @@
 	mydir=`dirname "$0"`
 	basedir="$mydir"/..
 fi
-progname="hoichess"
 
 svn info "$basedir" >/dev/null 2>&1
 if [ $? -eq 0 ]; then
@@ -19,17 +18,7 @@
 
 	version_str="$branch-$rev-svn"
 else
-	dirname=`cd "$basedir" && pwd | xargs basename`
-	case "$dirname" in
-		"$progname"-*)
-			version=`echo "$dirname" | sed -e "s/^$progname-//"`
-			;;
-		*)
-			version="unknown"
-			;;
-	esac
-
-	version_str="$version"
+	version_str=`awk '/^Version/ {print $2; exit}' "$basedir/ChangeLog"`
 fi
 
 echo "$version_str"

Bug#865370: Please provide oldstable.html for RC bugs in jessie

[Adrian Bunk]

Package: bugs.debian.org
Severity: normal

At https://bugs.debian.org/release-critical/ please
add a new subpage other/oldstable.html with a link
"Only bugs relevant to oldstable" (similar to the
setup for stable and testing).

Thanks in advance

Bug#856274: news

[Nicolas Boulenguez]

Package: gnat-5,gnat-6,gnat-7
Followup-For: Bug #856274

Small reproducer:
# 'package P is end P;' > p.a
# /usr/bin/gnatchop p.a

On gnat-5/5.4.1-11, the work-around fixes the issue.
Without it, gcc-5-5 is searched but not found.

On gnat-6/6.3.0-18, the work-around has no effect.
ARCH-gcc-6-6 is searched but not found.

Bug#865343: linux-image-4.9.0-3-amd64: On latest kernel java exits with SIGSEGV

[Ben Hutchings]

Control: tag -1 moreinfo

On Tue, 2017-06-20 at 17:37 +0200, Sasa Skevin wrote:
> Package: src:linux
> Version: 4.9.30-2
> Severity: important
> 
> Dear Maintainer,
> 
> I'm administering several Debian servers of which some are Jessie and
> some are Stretch. On both of them after upgrading to latest kernel that
> was released yesterday (4.9 on Stretch and 3.16 on Jessie), Java web
> applications do not work any more. They stop with SIGSEGV in the Java
> startup process.

So I think you meant to report this against versions 3.16.43-2+deb8u1
and 4.9.30-2+deb9u1, not 4.9.30-2.  Is that right?

> Have tried more different Java web applications and while booting all of
> them break with SIGSEGV while Java internaly loads rt.jar.
> 
> Have tried with Oracle Java 1.8.0_130, Oracje Java 1.8.0_131 and latest
> OpenJDK 8 and the same error happens.
> 
> Even the servers on which this is tried are from different hosting
> companies.
[...]

Does this go away if you add the kernel parameter "stack_guard_gap=1"?
(That should effectively revert the fix for CVE-2017-1000364.)

Has the stack limit for these applications been changed from the
default (e.g. "ulimit -s unlimited" in a startup script)?

Ben.

-- 
Ben Hutchings
Klipstein's 4th Law of Prototyping and Production:
A fail-safe circuit will destroy
others.


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

Bug#814977: small reproducer

[Nicolas Boulenguez]

Package: gnat-5
Followup-For: Bug #814977
Control: found -1 5.4.1-11

Related to #814978 and #856274.

Here is an easy way to reproduce.
# echo 'package P is end P;' > p.a
# /usr/bin/gnatchop p.a

Bug#865311:

[Martin Burmester]

Hello,

this is widely discussed in the ubiquity Forum [1] because it breakes the UniFi 
Controller.

Consensus seems to be that the kernel upgrade with the fix for CVE-2017-1000364 
caused the issue.

Strech seems to be affected as well.

Cheers,
Martin

[1] 
https://community.ubnt.com/t5/UniFi-Wireless/Unifi-Controller-on-Debian-9/td-p/1967180

Bug#758234: debian-policy: allow packages to depend on packages of lower priority

[Ansgar Burchardt]

Hi,

Russ Allbery writes:
> Andreas Henriksson writes:
>> Even if ftp-masters where really keen on actively managing the overrides
>> file I wonder what purpose this would serve?
>
>> As already mentioned previously in this bug backlog it would just be a
>> waste of ftp-master time.
>
>> Either way, I'm adding ftpmaster to CC now.
>
> Thanks!  Let's just ask directly.
>
> ftp-master folks, we're discussing eliminating the requirement that
> packages only depend on other packages with the same or higher priority
> (so important packages would be able to depend on optional packages), and
> deprecating the extra priority entirely (so everything at extra priority
> would end up being optional over time).  This also means eliminating the
> requirement that no two packages at optional priority conflict with each
> other.
>
> Some parts of this have more consensus than others, so I'm not sure we'll
> do all of these things.  But one question that keeps coming up is whether
> y'all care or have strong opinions about any of this.
>
> Do you care about any of these topics as ftp-master and the current
> effective owners of archive priorities?  Or would you be fine with just
> going with whatever decision the Policy discussion produces?

I do care to document current practice.  That's why I filed the bug
report ;-)

About packages depending on packages of lower priority:

There are some examples in [1] showing that a) nobody does the work to
maintain consistent priorities (see the libraries) and that b) doing so
is a bad idea anyway (see init and also the --exclude bit in [2]).

So I think there are both technical and social reasons to drop the
requirement.

  [1] https://bugs.debian.org/758234#81
  [2] https://bugs.debian.org/758234#99

About the extra priority:

First of all, most packages should be Priority: optional.  It might be
worth stating that in Policy more strongly ("Your package should usually
be at 'Priority: optional'").  The "[...] are only likely to be useful
if you already know what they are or have specialized requirements"
seems to be unclear at times (for example, most "-dev" packages or math
software or emacs extensions or "debian-policy" can be argued to only be
useful if you already know what they are[3]).

The optional/extra difference is only used for informative purposes as
far as I know: they should be handled mostly the same
(required/important/standard however have special meaning for
debootstrap).  So I understand why one might want to merge both.

I still think it has some minor uses, like showing which of several
alternative implementations might be preferred (if such a designated
alternative exists) by making that optional and the others extra.  Or
designated packages that are truly not useful for general systems (like
debug symbols).

However if no preferred implementation exists, I believe having all of
them at Priority: optional and conflict with each other is fine.

  [3] Most description of Priority levels are unclear or current
  practice differs a bit.  For example, does one expect to find
  vi(m) on any Unix-like system? ed? make?

  Does "standard" include a text-mode MUA? emacs? vim? A small TeX
  installation (optional has the full TeX distro after all)? make?
  dirmngr? gcc?

  I don't have an improved version though. Maybe state that it is
  mostly relevant to debootstrap (or "what the installer will
  install")?

Ansgar
 - speaking only for himself