Bug#855103: Rendering fails on wayland/hidpi

[Sjoerd Simons]

Package: libwebkit2gtk-4.0-37
Version: 2.14.4-1
Severity: grave

Hey,

Both epiphany and evolution show blank output when trying to render
website/e-mails. Downgrading libwebkit2gtk-4.0-37 to 2.14.3 seems to solve the
issue.

>From some notes on #debian-gnome this might be caused by:
  https://bugs.webkit.org/show_bug.cgi?id=168128

Which has just received a patch :)

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

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

Versions of packages libwebkit2gtk-4.0-37 depends on:
ii  libatk1.0-0 2.22.0-1
ii  libc6   2.24-9
ii  libcairo2   1.14.8-1
ii  libegl1-mesa [libegl1-x11]  13.0.4-1
ii  libenchant1c2a  1.6.0-11+b1
ii  libfontconfig1  2.11.0-6.7
ii  libfreetype62.6.3-3+b1
ii  libgcc1 1:6.3.0-6
ii  libgdk-pixbuf2.0-0  2.36.4-1
ii  libgl1-mesa-glx [libgl1]13.0.4-1
ii  libglib2.0-02.50.2-2
ii  libgnutls30 3.5.8-3
ii  libgstreamer-plugins-base1.0-0  1.10.3-1
ii  libgstreamer1.0-0   1.10.3-1
ii  libgtk-3-0  3.22.7-2
ii  libharfbuzz-icu01.4.2-1
ii  libharfbuzz0b   1.4.2-1
ii  libhyphen0  2.8.8-5
ii  libicu5757.1-5
ii  libjavascriptcoregtk-4.0-18 2.14.4-1
ii  libjpeg62-turbo 1:1.5.1-2
ii  libnotify4  0.7.7-1
ii  libpango-1.0-0  1.40.3-3
ii  libpng16-16 1.6.28-1
ii  libsecret-1-0   0.18.5-2
ii  libsoup2.4-12.56.0-2
ii  libsqlite3-03.16.2-2
ii  libstdc++6  6.3.0-6
ii  libwayland-client0  1.12.0-1
ii  libwayland-egl1-mesa [libwayland-egl1]  13.0.4-1
ii  libwayland-server0  1.12.0-1
ii  libwebp60.5.2-1
ii  libx11-62:1.6.4-3
ii  libxcomposite1  1:0.4.4-2
ii  libxdamage1 1:1.1.4-2+b1
ii  libxml2 2.9.4+dfsg1-2.2
ii  libxslt1.1  1.1.29-2
ii  zlib1g  1:1.2.8.dfsg-5

Versions of packages libwebkit2gtk-4.0-37 recommends:
ii  gstreamer1.0-plugins-base  1.10.3-1
ii  gstreamer1.0-plugins-good  1.10.3-1
pn  libwebkit2gtk-4.0-37-gtk2  

libwebkit2gtk-4.0-37 suggests no packages.

-- no debconf information

Bug#831541: theano: single GradientError and WrongValues in tests on s390x, ppc64 and sparc

[Rebecca N. Palmer]

Found the problem: the affected functions ( 
https://sources.debian.net/src/theano/0.8.2-4/theano/sparse/opt.py/#L862 
, 
https://sources.debian.net/src/theano/0.8.2-4/theano/sparse/opt.py/#L1902 
) cast a pointer-to-intptr_t (64 bit) to a pointer-to-int (32-bit).


Which isn't just broken on big-endian systems, it's a strict aliasing 
violation *everywhere* (i.e. technically undefined behaviour with 
optimization on, which it is by default, though it appears to work in 
practice).


(I expect to post a patch tonight: the obvious has a potential overflow 
issue, and it also needs a c_code_cache_version change to make the fix 
be used in existing installs).

Bug#847311: amavisd-new: After the last Debian update Amavis does not read data type float from Mysql DB correctly. All fields are "0".

[Brian May]

Upstream has asked for some rather detailed information:

https://github.com/perl5-dbi/DBD-mysql/issues/78

The information I asked for will do for now, then we can decide if this
more extensive information is required.
-- 
Brian May 

Bug#854341: libchado-perl: FTBFS: The following enviroment variables not detected: CHADO_DB_USERNAME

[Andreas Tille]

tags 854341 help
thanks

Hi,

I admit I have no idea how to fix this.  Help from people with
Perl background would be really appreciated.

On Mon, Feb 06, 2017 at 03:40:09PM +0100, Andreas Tille wrote:
> ...
> 
> I'm running later into
> 
> ...
>dh_auto_install -O--buildsystem=perl_makemaker
> make -j4 install DESTDIR=/build/libchado-perl-1.31/debian/tmp 
> AM_UPDATE_INFO_DIR=no PREFIX=/usr
> make[1]: Entering directory '/build/libchado-perl-1.31'
> "/usr/bin/perl" "/build/libchado-perl-1.31/install_util/conf_install.pl" 
> 'GMOD_ROOT=/build/libchado-perl-1.31/debian/libchado-perl/usr/share/gmod/chado'
>  'VERSION=1.31'
> "/usr/bin/perl" "/build/libchado-perl-1.31/install_util/src_install.pl" 
> 'GMOD_ROOT=/build/libchado-perl-1.31/debian/libchado-perl/usr/share/gmod/chado'
> couldn't open 
> /build/libchado-perl-1.31/debian/libchado-perl/usr/share/gmod/chado/conf 
> directory for reading:No such file or directory
> Makefile:1222: recipe for target 'src_install' failed
> 
> 
> which is pretty strange since
> 
> # ls -l 
> /build/libchado-perl-1.31/debian/libchado-perl/usr/share/gmod/chado/conf
> total 8
> -rw-r--r-- 1 pbuilder pbuilder 221 Feb  6 11:06 gmod-chado.conf
> -rw-r--r-- 1 pbuilder pbuilder 167 Feb  6 11:06 gmod.conf
> 
> 
> 
> > Glancing quickly at Makefile.PL and debian/rules it looks like the
> > variable names have changed (eg. was DBUSER, etc.).
> 
> The variable names have not changed in any recent upload and as you can
> see DBUSER etc are used.
> 
> Does anybody else have some idea?

Kind regards

   Andreas. 

-- 
http://fam-tille.de

Processed: Re: Bug#854341: libchado-perl: FTBFS: The following enviroment variables not detected: CHADO_DB_USERNAME

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 854341 help
Bug #854341 [src:libchado-perl] libchado-perl: FTBFS: The following enviroment 
variables not detected: CHADO_DB_USERNAME
Added tag(s) help.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
854341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: found 854000 in 1.12-3.1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 854000 1.12-3.1
Bug #854000 [src:libplist] CVE-2017-5834 CVE-2017-5835 CVE-2017-5836
Marked as found in versions libplist/1.12-3.1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
854000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 854000

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 854000 + upstream
Bug #854000 [src:libplist] CVE-2017-5834 CVE-2017-5835 CVE-2017-5836
Added tag(s) upstream.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
854000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#835949: linux-grsec: non-standard gcc/g++ used for build (gcc-5)

[Hideki Yamane]

On Mon, 29 Aug 2016 16:15:34 +0200 Yves-Alexis Perez  wrote:
> I follow src:linux package on this, so I'll do the switch when they do it (and
> will close this bug at that point).

 It seems that src:linux was fixed
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835957

-- 
Regards,

 Hideki Yamane

Bug#849504: Data corruption with copy-on-write and multiple threads

[Wouter Verhelst]

Hi Niels,

On Sun, Feb 12, 2017 at 08:52:00AM +, Niels Thykier wrote:
> Any news on this bug?

I'm going to release (upstream) nbd 3.15.2 later this week (probably on
thursday), which contains the fix:

https://github.com/NetworkBlockDevice/nbd/compare/nbd-3.15.1...master

This patch series includes:

- The fix for this bug, commit a43a2d8;
- Several minor documentation fixes (e.g., fixed the sorting of a listing in a
  man page);
- A better fix for the issue of nbd-client-udeb being compiled against GnuTLS
  that does not break the build on kFreeBSD etc;
- The ability to change the GnuTLS priority string, to follow TLS best
  practices and allow people to lock down the TLS configuration

I would like to update nbd to that version; but if the release team
prefers, I can cherry-pick a43a2d8 onto 3.15.1 and upload that instead.

-- 
< ron> I mean, the main *practical* problem with C++, is there's like a dozen
   people in the world who think they really understand all of its rules,
   and pretty much all of them are just lying to themselves too.
 -- #debian-devel, OFTC, 2016-02-12

Processed: Re: Bug#760414: [ola] This a serious bug

[Debian Bug Tracking System]

Processing control commands:

> severity -1 wishlist
Bug #760414 [ola] [ola] Some sources are not included in your package
Severity set to 'wishlist' from 'serious'

-- 
760414: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#760414: [ola] This a serious bug

[Wouter Verhelst]

control: severity -1 wishlist

On Sun, Feb 12, 2017 at 03:50:15PM +0100, Bastien ROUCARIÈS wrote:
> Package: ola
> control: severity -1 serious
> 
> This a serious  bug. See ftpmaster statement

You are not a member of the ftpmaster team. I have explained my opinion
on this matter, and unless someone who is a member of the ftpmaster team
changes the severity of this bug, it is going to remain as wishlist. If
they do, all I'll be doing at this stage of the release is to just pick
the relevant upstream non-minified javascript libraries and add them to
the diff.gz.

Just to reiterate, this is my position:

- The javascript libraries in question *are* free (whether in source or
  minified form);
- They are shipped by (ola's) upstream as unmodified convenience copies
  of the (javascript library's) upstream minified versions of said
  javascript libraries;
- They are *also* shipped by Debian in the relevant libjs-* packages;
- The relevant libjs-* packages are what is in fact being used by the
  ola package.

I have yet to see a convincing argument how all of the above *combined*
constitutes either a DFSG violation, or something that fails SC#4.

If the FTP team explains to me why that is a DFSG violation, I'll add
the "missing" files. If they don't, things will remain as they are (and
if they don't but do change severities, I'll ask the TC to rule).

Alternatively, if someone can convince me that it fails SC#4 in some
way, I'll consider "fixing" this bug.

Meanwhile, please stop playing BTS severity pingpong.

Thanks.


-- 
< ron> I mean, the main *practical* problem with C++, is there's like a dozen
   people in the world who think they really understand all of its rules,
   and pretty much all of them are just lying to themselves too.
 -- #debian-devel, OFTC, 2016-02-12

Bug#855096: unison: segfaults after connection has been established

[Norbert Preining]

Package: unison
Version: 2.48.3-1
Severity: grave
Justification: renders package unusable

Hi everyone,

since short time unison (gtk and text mode) is crashing with 
sigsegv after the connection has been started.

Core was generated by `unison bulldog-home'.
Program terminated with signal SIGSEGV, Segmentation fault.

gdb didn't help as there is no debug package neither in the normal archives
nor in the debug-sid archive.

Calling unison with -debug all I get at the end:

[update] Loading archive from 
/home/norbert/.unison/arf0168c12ac8c1cc3e65ee115fd63d9b3
[server: update] Loading archive from 
/home/norbert/.unison/ar40f7a1363152c2a5aa375f92b6e8fd18
Growing heap to 700852k bytes
Growing page table to 2048 entries
Growing page table to 4096 entries
Growing page table to 8192 entries
Growing page table to 16384 entries
Growing page table to 32768 entries
Growing page table to 65536 entries
Growing page table to 131072 entries
Growing page table to 262144 entries
[server: update] Setting archive for //bulldog//home/norbert
[server: remote] Connection closed by the client
Segmentation fault (core dumped)

Hope that helps

Norbert

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

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

Versions of packages unison depends on:
ii  libc6  2.24-9

Versions of packages unison recommends:
ii  openssh-client [ssh-client]  1:7.4p1-6

Versions of packages unison suggests:
ii  unison-all  2.48+2

-- no debconf information

Bug#855094: initramfs-tools-core: Error on upgrade if cryptsetup is installed, but a current busybox isn't

[Jan Echternach]

Package: initramfs-tools-core
Version: 0.127
Severity: serious
Justification: Policy 3.5

I tried a partial upgrade of initramfs-tools, but it failed, complaining that
busybox was too old, see console messages below. The version of busybox
installed at that time was 1:1.22.0-9+deb8u1. I solved this problem by
upgrading busybox to version 1:1.22.0-19+b1.

I investigated this a bit and found that
/usr/share/initramfs-tools/conf-hooks.d/cryptsetup, which belongs to the
cryptsetup package, sets BUSYBOX=Y (both the current stable and testing
versions of cryptsetup do that).

I think this error could also occur on a complete upgrade if busybox is not
installed because neither initramfs-tools nor cryptsetup depends on busybox.


  # apt-get install initramfs-tools{,-core}/unstable
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Selected version '0.127' (Debian:testing, Debian:unstable [all]) for 
'initramfs-tools'
  Selected version '0.127' (Debian:testing, Debian:unstable [all]) for 
'initramfs-tools-core'
  [...]
  Preparing to unpack .../klibc-utils_2.0.4-9_i386.deb ...
  Adding 'diversion of /usr/share/initramfs-tools/hooks/klibc to 
/usr/share/initramfs-tools/hooks/klibc^i-t by klibc-utils'
  Unpacking klibc-utils (2.0.4-9) over (2.0.4-2) ...
  Preparing to unpack .../libklibc_2.0.4-9_i386.deb ...
  Unpacking libklibc (2.0.4-9) over (2.0.4-2) ...
  Preparing to unpack .../initramfs-tools_0.127_all.deb ...
  '/etc/initramfs-tools/initramfs.conf' -> 
'/etc/initramfs-tools/initramfs.conf.dpkg-remove'
  Unpacking initramfs-tools (0.127) over (0.120+deb8u2) ...
  dpkg: warning: unable to delete old directory '/var/lib/initramfs-tools': 
Directory not empty
  Selecting previously unselected package initramfs-tools-core.
  Preparing to unpack .../initramfs-tools-core_0.127_all.deb ...
  Unpacking initramfs-tools-core (0.127) ...
  Setting up libklibc (2.0.4-9) ...
  Processing triggers for man-db (2.7.0.2-5) ...
  Setting up klibc-utils (2.0.4-9) ...
  Setting up initramfs-tools-core (0.127) ...
  removed '/etc/initramfs-tools/initramfs.conf.dpkg-remove'
  Setting up initramfs-tools (0.127) ...
  Installing new version of config file /etc/kernel/postinst.d/initramfs-tools 
...
  update-initramfs: deferring update (trigger activated)
  Removing obsolete conffile /etc/bash_completion.d/initramfs-tools ...
  Processing triggers for initramfs-tools (0.127) ...
  update-initramfs: Generating /boot/initrd.img-3.16.0-4-amd64
  E: busybox or busybox-static, version 1:1.22.0-17~ or later, is required but 
not installed
  update-initramfs: failed for /boot/initrd.img-3.16.0-4-amd64 with 1.
  dpkg: error processing package initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   initramfs-tools
  E: Sub-process /usr/bin/dpkg returned an error code (1)


-- System Information:
Debian Release: 8.7
  APT prefers stable
  APT policy: (813, 'stable'), (812, 'oldstable'), (600, 'unstable-debug'), 
(600, 'unstable'), (550, 'testing-debug'), (550, 'testing'), (510, 
'experimental-debug'), (510, 'experimental')
Architecture: i386 (x86_64)
Foreign Architectures: amd64

Kernel: Linux 4.9.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages initramfs-tools-core depends on:
ii  cpio   2.11+dfsg-4.1+deb8u1
ii  klibc-utils2.0.4-9
ii  kmod   18-3
ii  module-init-tools  18-3
ii  udev   215-17+deb8u6

Versions of packages initramfs-tools-core recommends:
ii  busybox  1:1.22.0-19+b1

Versions of packages initramfs-tools-core suggests:
pn  bash-completion  

-- no debconf information

Bug#831540: marked as done (theano: assertion error in test_fit_int64 on i386 and hurd/kreebsd-i386)

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2017 23:49:36 +
with message-id 
and subject line Bug#831540: fixed in theano 0.8.2-5~exp1
has caused the Debian Bug report #831540,
regarding theano: assertion error in test_fit_int64 on i386 and 
hurd/kreebsd-i386
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
831540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831540
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: theano
Version: 0.8.2-2
Severity: normal

There is a single assertion error in the tests running on Python 3.5 on i386 
[1]:


FAIL: test_fit_int64 (theano.tensor.tests.test_basic.T_long_tensor)
--
Traceback (most recent call last):
  File "/«PKGBUILDDIR»/theano/tensor/tests/test_basic.py", line 6675, in 
test_fit_int64
assert vector_ct.dtype == 'int64'
AssertionError

--
Ran 2995 tests in 6746.401s


The same single error occurs on kfreebsd-i386 [2], and hurd-i386 [3].

This is a regression from 0.8.2-2 (0.8.2-1 was build with `FAST_COMPILE`).
dh_auto_tests is temporarily failsafed, this is going to be removed when this
problem is solved.

Thanks,
DS

[1] 
https://buildd.debian.org/status/fetch.php?pkg=theano=i386=0.8.2-2=1468619301

[2] 
https://buildd.debian.org/status/fetch.php?pkg=theano=kfreebsd-i386=0.8.2-2=1468626553

[3] 
https://buildd.debian.org/status/fetch.php?pkg=theano=hurd-i386=0.8.2-2=1468689994

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

Kernel: Linux 4.5.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: theano
Source-Version: 0.8.2-5~exp1

We believe that the bug you reported is fixed in the latest version of
theano, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 831...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Stender  (supplier of updated theano package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 13 Feb 2017 23:53:19 +0100
Source: theano
Binary: python-theano python3-theano theano-doc
Architecture: source amd64 all
Version: 0.8.2-5~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Daniel Stender 
Description:
 python-theano - CPU/GPU math expression compiler for Python
 python3-theano - CPU/GPU math expression compiler for Python 3
 theano-doc - CPU/GPU math expression compiler for Python (docs)
Closes: 831540
Changes:
 theano (0.8.2-5~exp1) experimental; urgency=medium
 .
   * add fix-test_fit_int64-for-python3-32bit.patch (Closes: #831540)
 [thanks to Rebecca N. Palmer].
   * deb/rules: remove test failsafes completely.
Checksums-Sha1:
 d2474c0d08f39100cc08e0ad12dcd587ddae747f 2711 theano_0.8.2-5~exp1.dsc
 a240e2e8f84b3051ff54dc019926c303565b7f5f 5440296 theano_0.8.2.orig.tar.xz
 6dab3c1ec5036a85dd2b0dbd21b6dfa511d879d6 359072 
theano_0.8.2-5~exp1.debian.tar.xz
 5a5f646f2b0a9dd44f6574b0975d09d8e795920e 1951818 
python-theano_0.8.2-5~exp1_amd64.deb
 f86707e7015a6dd47b13af651496aba585d5a918 1952280 
python3-theano_0.8.2-5~exp1_amd64.deb
 0528dbff9d44c1e9708848cfa537ab751fc9bccd 2732704 
theano-doc_0.8.2-5~exp1_all.deb
 3c6c5f2812c1ee126b9fe6011fc170876e810cf0 10085 
theano_0.8.2-5~exp1_amd64.buildinfo
Checksums-Sha256:
 ac267c20f4d6cc8f3cbcc67181388b969ebc6519452e0ef9f57df0d40490488e 2711 
theano_0.8.2-5~exp1.dsc
 f672151b90f0085d6fcd255d82305c3b825f0fe5a3128cf65ddcb33d7e7ced06 5440296 
theano_0.8.2.orig.tar.xz
 9dc85a5c2df85010b2fe65b8b6e739af6716b5c7747e9cae75d819075dd31572 359072 
theano_0.8.2-5~exp1.debian.tar.xz
 1362cd0fad00574a7d5ce41ae8cee06e1f7b91c117cd041d7c79ebea3ebb20cb 1951818 
python-theano_0.8.2-5~exp1_amd64.deb
 

Bug#740998: Bug#854801: No network after netinst Stretch RC2

[Pierre Ynard]

> in finish-install /e/n/i will never be properly populated for a wireless
> installation without network-manager, although I think ifupdown would be
> capable to do this (not tested, but have a look at
> https://anonscm.debian.org/cgit/d-i/netcfg.git/tree/write_interface.c).
> I guess the justification is that people using wireless usually would
> want a GUI to roam between networks, and a interface stanza would
> prevent even a (later installed) network-manager from touching the
> interface.

That makes sense. Maybe it could still output commented-out
configuration into /e/n/i, to make it easier in case people do end up
editing the file to set up their network, for whatever reason.

> a) go for Cyril's suggestion and just install rdnssd in finish-install
> if network-manager is not getting installed there (but honestly I have
> no idea of the netcfg code base)
> b) drop the Conflicts and make the rdnssd merge-hook a no-op if
> network-manager is installed/running.

I think trying to manage this conflict between two basic packages is
asking for trouble. rdnssd doesn't depend on /usr, I think in some
cases it can still be beneficial for bootstrap when network-manager
might not be available. There is already a distro-specific patch for
/etc/rdnssd/merge-hook to add a resolvconf by-pass, another one could
be added checking if network-manager is installed/available/running/in
charge of /etc/resolv.conf. I've never used network-manager personally
so I wouldn't quite know what's best to check exactly.

-- 
Pierre Ynard
"Une âme dans un corps, c'est comme un dessin sur une feuille de papier."

Bug#854720: marked as done (sidedoor-sudo: postinst uses /usr/share/doc content (Policy 12.3): /usr/share/doc/sidedoor/examples/sudoers)

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2017 23:04:05 +
with message-id 
and subject line Bug#854720: fixed in sidedoor 0.2.0-3
has caused the Debian Bug report #854720,
regarding sidedoor-sudo: postinst uses /usr/share/doc content (Policy 12.3): 
/usr/share/doc/sidedoor/examples/sudoers
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
854720: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sidedoor-sudo
Version: 0.2.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3: "Packages must not require the existence of any files in
/usr/share/doc/ in order to function."
https://www.debian.org/doc/debian-policy/ch-docs.html#s12.3

These files must be moved to /usr/share/$PACKAGE and may be symlinked
from /usr/share/doc/$PACKAGE.

This piuparts test prevents the installation of (most) files into
/usr/share/doc with 'dpkg --path-exclude=...'.

>From the attached log (scroll to the bottom...):

  Selecting previously unselected package sidedoor-sudo.
  (Reading database ... 
(Reading database ... 4686 files and directories currently installed.)
  Preparing to unpack .../sidedoor-sudo_0.2.0-2_all.deb ...
  Unpacking sidedoor-sudo (0.2.0-2) ...
  Setting up sidedoor-sudo (0.2.0-2) ...
  Error: The new file /usr/share/doc/sidedoor/examples/sudoers does not exist!
  dpkg: error processing package sidedoor-sudo (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   sidedoor-sudo


Cheers,

Andreas


sidedoor-sudo_0.2.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: sidedoor
Source-Version: 0.2.0-3

We believe that the bug you reported is fixed in the latest version of
sidedoor, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 854...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dara Adib  (supplier of updated sidedoor package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 09 Feb 2017 15:37:43 -0500
Source: sidedoor
Binary: sidedoor sidedoor-sudo
Architecture: source all
Version: 0.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Dara Adib 
Changed-By: Dara Adib 
Description:
 sidedoor   - SSH connection daemon
 sidedoor-sudo - SSH connection daemon - sudoers entry
Closes: 854720
Changes:
 sidedoor (0.2.0-3) unstable; urgency=medium
 .
   * Move sudoers example to sidedoor-sudo package.
 Thanks Andreas Beckmann. (Closes: #854720)
Checksums-Sha1:
 0d871b0da00138beecfcdfd60a3ff34c96208b0d 1868 sidedoor_0.2.0-3.dsc
 ded131213c0b9546c9d6e7ca667db4f377b65bcb 6244 sidedoor_0.2.0-3.debian.tar.xz
 158f6885e24107b6b844841d3a2bd831cfc27d94 3152 sidedoor-sudo_0.2.0-3_all.deb
 53b74d11f65f0454b29fbe70cbe55a3e19062bdd 12300 sidedoor_0.2.0-3_all.deb
 d05a0629d878ae8e967c59d965f1f9ea26a38811 4614 sidedoor_0.2.0-3_amd64.buildinfo
Checksums-Sha256:
 6d48bdf9c2409d0ae989a2d86b3ca2624cd69ce9e5f6edce9af0a9ea12a47f9f 1868 
sidedoor_0.2.0-3.dsc
 7879bd6e095866dcf9cd0334cb17503b6ffa59cd8b4bbb589bd18b9ef5446a11 6244 
sidedoor_0.2.0-3.debian.tar.xz
 eda433b4d759599dbb06710f68708bd03aa264934cfd4fb19b4725009415c273 3152 
sidedoor-sudo_0.2.0-3_all.deb
 bbacf579e48de6dadda734b07b2c393702e541f4c207523ff181e3512d3364e5 12300 
sidedoor_0.2.0-3_all.deb
 1c57e91ca994c3cc0d1bd031dace3b1964bcf930441f6e156fc47a4161bf2e7d 4614 
sidedoor_0.2.0-3_amd64.buildinfo
Files:
 b8ab4b72a443c2e87f4fc88bf9b43257 1868 net optional sidedoor_0.2.0-3.dsc
 79140cbf39f8f20d7dd97ca96db3ea32 6244 net optional 
sidedoor_0.2.0-3.debian.tar.xz
 a188d291d3d33f1f94763fd88dac705d 3152 net optional 
sidedoor-sudo_0.2.0-3_all.deb
 634b707c2ebda672825fdeb8714f3484 12300 net optional sidedoor_0.2.0-3_all.deb
 3ecd62e82174ba81bdeada4c3a0060d0 4614 net optional 
sidedoor_0.2.0-3_amd64.buildinfo

Processed: FTBFS is RC

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 850692 serious
Bug #850692 [pyrit] pyrit: failed with 'BitEnumField' object has no attribute 
'names'
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
850692: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850692
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#849132: google-perftools FTBFS on i386: FAIL: profiler_unittest.sh

[Adrian Bunk]

Control: reopen -1

On Mon, Feb 13, 2017 at 08:05:45PM +0100, Ivo De Decker wrote:
> Hi,
> 
> On Sun, Jan 29, 2017 at 07:19:00AM +, Niels Thykier wrote:
> > Are there any news on the FTBFS bug? It has been stalling the fix for
> > #838562 for about 40 days.
> 
> The latest attempt succeeded, but it's unclear what changed.
> 
> https://buildd.debian.org/status/fetch.php?pkg=google-perftools=i386=2.5-2=1486843465=0

https://buildd.debian.org/status/logs.php?pkg=google-perftools=i386

This test seems to fail "randomly" (it already failed on 2016-02-20).

Reopening, since this has to be handled properly to avoid nasty 
surprises in DSAs.

> Cheers,
> 
> Ivo

cu
Adrian

-- 

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

Processed: Re: google-perftools FTBFS on i386: FAIL: profiler_unittest.sh

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #849132 {Done: Ivo De Decker } [src:google-perftools] 
google-perftools FTBFS on i386: FAIL: profiler_unittest.sh
Bug reopened
Ignoring request to alter fixed versions of bug #849132 to the same values 
previously set

-- 
849132: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#740998: Bug#854801: No network after netinst Stretch RC2

[Bernhard Schmidt]

Hi

On 13.02.2017 18:24, Paul Schlüter wrote:
> Am Montag, den 13.02.2017, 10:31 +0100 schrieb Bernhard Schmidt:
>> @Paul: Can you share the installer log (/var/log/installer/syslog) and
>> the content of your /etc/network/interfaces after installation? I'll try
>> to get that information myself tonight, I don't have RDNSS here in the
>> office network unfortunately.
> 
> Hi Bernhard,
> 
> please find attached
> 
> - installer-log.gz: /var/log/installer/syslog
> - interfaces: original (and current) /etc/network/interfaces
> 
> (I reverted my modification of "interfaces" after the installation of
> network-manager-gnome).

So, I've tried to reproduce the issue and failed. I'm in a qemu VM on a
network that provides IPv6 SLAAC with RDNSS and IPv4 DHCP. I have booted
using the RC2-netinst-amd64 image and installed the XFCE desktop task.

As expected I ended up with rdnssd installed (no network-manager), but
/etc/network/interfaces is properly populated and I got network
connectivity.

I think I have found the source of your problem. According to your logs
you are installing on a WiFi interface (wlp2s0). The first attempt to
write your /etc/network/interfaces shows correct stanzas for the interface

Feb  9 06:32:45 netcfg[6883]: DEBUG: Network config complete
Feb  9 06:32:45 netcfg[6883]: DEBUG: No interface given; clearing
/etc/network/interfaces
Feb  9 06:32:45 netcfg[6883]: DEBUG: Writing informative header
Feb  9 06:32:45 netcfg[6883]: DEBUG: Success!
Feb  9 06:32:45 netcfg[6883]: DEBUG: Writing loopback interface
Feb  9 06:32:45 netcfg[6883]: DEBUG: Success!
Feb  9 06:32:45 netcfg[6883]: DEBUG: Writing DHCP stanza for wlp2s0
Feb  9 06:32:45 netcfg[6883]: INFO: Detected wlp2s0 as a hotpluggable device
Feb  9 06:32:45 netcfg[6883]: DEBUG: Writing SLAAC stanza for wlp2s0
Feb  9 06:32:45 netcfg[6883]: DEBUG: Writing wireless options for wlp2s0
Feb  9 06:32:45 netcfg[6883]: DEBUG: Success!

but the second attempt in finish-install.d only writes the loopback

Feb  9 07:27:06 finish-install: info: Running
/usr/lib/finish-install.d/55netcfg-copy-config
Feb  9 07:27:06 netcfg[30397]: INFO: Starting netcfg v.1.141
Feb  9 07:27:06 netcfg[30397]: DEBUG: No interface given; clearing
/etc/network/interfaces
Feb  9 07:27:06 netcfg[30397]: DEBUG: Writing informative header
Feb  9 07:27:06 netcfg[30397]: DEBUG: Success!
Feb  9 07:27:06 netcfg[30397]: DEBUG: Writing loopback interface
Feb  9 07:27:06 netcfg[30397]: DEBUG: Success!
Feb  9 07:27:06 finish-install: info: Running
/usr/lib/finish-install.d/60cleanup

I think the code to blame is here

https://anonscm.debian.org/cgit/d-i/netcfg.git/tree/finish-install.d/55netcfg-copy-config#n42

> # Check for preseeding. If the value of the question is empty then set
> # default options. Document automatic selection changes in the template.
> if [ -z "$RET" ]; then
>   if $NM_IS_INSTALLED; then
>   db_set netcfg/target_network_config $CONFIG_NM
>   else
>   if [ "$NETCFG_CONNECTION_TYPE" = "wired" ]; then
>   db_set netcfg/target_network_config $CONFIG_INTERFACES
>   else # wireless
>   db_set netcfg/target_network_config $CONFIG_LOOPBACK
>   fi
>   fi
> fi

in finish-install /e/n/i will never be properly populated for a wireless
installation without network-manager, although I think ifupdown would be
capable to do this (not tested, but have a look at
https://anonscm.debian.org/cgit/d-i/netcfg.git/tree/write_interface.c).
I guess the justification is that people using wireless usually would
want a GUI to roam between networks, and a interface stanza would
prevent even a (later installed) network-manager from touching the
interface.

rdnssd just triggers this more often because it will prevent
network-manager installations on the desktop tasks normally using the
wireless connectivity.

But, all in all, I think network-manager should take precedence over
rdnssd. So we can either

a) go for Cyril's suggestion and just install rdnssd in finish-install
if network-manager is not getting installed there (but honestly I have
no idea of the netcfg code base)
b) drop the Conflicts and make the rdnssd merge-hook a no-op if
network-manager is installed/running.

Bernhard

Processed: spice: diff for NMU version 0.12.8-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 854336 + pending
Bug #854336 [src:spice] CVE-2016-9577 CVE-2016-9578
Added tag(s) pending.

-- 
854336: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854336
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#854336: spice: diff for NMU version 0.12.8-2.1

[Markus Koschany]

Control: tags 854336 + pending

Dear maintainer,

I've prepared an NMU for spice (versioned as 0.12.8-2.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

I am attaching the debdiff to this bug report.

Regards,

Markus
diff -Nru spice-0.12.8/debian/changelog spice-0.12.8/debian/changelog
--- spice-0.12.8/debian/changelog	2017-01-06 14:50:55.0 +0100
+++ spice-0.12.8/debian/changelog	2017-02-13 21:42:01.0 +0100
@@ -1,3 +1,17 @@
+spice (0.12.8-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add CVE-2016-9577-and-CVE-2016-9578.patch:
+- CVE-2016-9577: A buffer overflow vulnerability in
+  main_channel_alloc_msg_rcv_buf was found that occurs when reading large
+  messages due to missing buffer size check.
+- CVE-2016-9578: A vulnerability was discovered in the server's
+  protocol handling. An attacker able to connect to the spice server could
+  send crafted messages which would cause the process to crash.
+  (Closes: #854336)
+
+ -- Markus Koschany   Mon, 13 Feb 2017 21:42:01 +0100
+
 spice (0.12.8-2) unstable; urgency=medium
 
   * Build on all little-endian architectures (Closes: #734218)
diff -Nru spice-0.12.8/debian/patches/CVE-2016-9577-and-CVE-2016-9578.patch spice-0.12.8/debian/patches/CVE-2016-9577-and-CVE-2016-9578.patch
--- spice-0.12.8/debian/patches/CVE-2016-9577-and-CVE-2016-9578.patch	1970-01-01 01:00:00.0 +0100
+++ spice-0.12.8/debian/patches/CVE-2016-9577-and-CVE-2016-9578.patch	2017-02-13 21:42:01.0 +0100
@@ -0,0 +1,54 @@
+From: Markus Koschany 
+Date: Mon, 13 Feb 2017 21:38:02 +0100
+Subject: CVE-2016-9577 and CVE-2016-9578
+
+Bug-Debian: https://bugs.debian.org/854336
+Origin: http://pkgs.fedoraproject.org/cgit/rpms/spice.git/commit/?id=d919d639ae5f83a9735a04d843eed675f9357c0d
+---
+ server/main_channel.c |  3 +++
+ server/reds.c | 11 ++-
+ 2 files changed, 13 insertions(+), 1 deletion(-)
+
+diff --git a/server/main_channel.c b/server/main_channel.c
+index 0ecc9df..1fc3915 100644
+--- a/server/main_channel.c
 b/server/main_channel.c
+@@ -1026,6 +1026,9 @@ static uint8_t *main_channel_alloc_msg_rcv_buf(RedChannelClient *rcc,
+ 
+ if (type == SPICE_MSGC_MAIN_AGENT_DATA) {
+ return reds_get_agent_data_buffer(mcc, size);
++} else if (size > sizeof(main_chan->recv_buf)) {
++/* message too large, caller will log a message and close the connection */
++return NULL;
+ } else {
+ return main_chan->recv_buf;
+ }
+diff --git a/server/reds.c b/server/reds.c
+index 61bf735..4c60f58 100644
+--- a/server/reds.c
 b/server/reds.c
+@@ -2110,6 +2110,14 @@ static void reds_handle_read_link_done(void *opaque)
+ link_mess->num_channel_caps = GUINT32_FROM_LE(link_mess->num_channel_caps);
+ link_mess->num_common_caps = GUINT32_FROM_LE(link_mess->num_common_caps);
+ 
++/* Prevent DoS. Currently we defined only 13 capabilities,
++ * I expect 1024 to be valid for quite a lot time */
++if (link_mess->num_channel_caps > 1024 || link_mess->num_common_caps > 1024) {
++reds_send_link_error(link, SPICE_LINK_ERR_INVALID_DATA);
++reds_link_free(link);
++return;
++}
++
+ num_caps = link_mess->num_common_caps + link_mess->num_channel_caps;
+ caps = (uint32_t *)((uint8_t *)link_mess + link_mess->caps_offset);
+ 
+@@ -2202,7 +2210,8 @@ static void reds_handle_read_header_done(void *opaque)
+ 
+ reds->peer_minor_version = header->minor_version;
+ 
+-if (header->size < sizeof(SpiceLinkMess)) {
++/* the check for 4096 is to avoid clients to cause arbitrary big memory allocations */
++if (header->size < sizeof(SpiceLinkMess) || header->size > 4096) {
+ reds_send_link_error(link, SPICE_LINK_ERR_INVALID_DATA);
+ spice_warning("bad size %u", header->size);
+ reds_link_free(link);
diff -Nru spice-0.12.8/debian/patches/series spice-0.12.8/debian/patches/series
--- spice-0.12.8/debian/patches/series	2017-01-06 14:50:42.0 +0100
+++ spice-0.12.8/debian/patches/series	2017-02-13 21:42:01.0 +0100
@@ -1 +1,2 @@
 stop-linking-with-libcacard.diff
+CVE-2016-9577-and-CVE-2016-9578.patch

Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS

[Michael Biebl]

Am 10.02.2017 um 09:49 schrieb Tilo Villwock:
> 
> Bug report filed:
> 
> https://bugzilla.gnome.org/show_bug.cgi?id=778430

Upstream provided a patch at
https://bugzilla.gnome.org/show_bug.cgi?id=778430#c10

Would be great if you can test with this patch applied and report back.

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#847311: amavisd-new: After the last Debian update Amavis does not read data type float from Mysql DB correctly. All fields are "0".

[Brian May]

Henrique de Moraes Holschuh  writes:

> LOC, could you send (to this bug report) a dump of the *schema* for the
> relevant tables (the ones returning 0 instead of the correct float) ?

LOC, please connect to the database using the mysql client, and type in
the following commands. Send back the results.

desc spamfilter_users;
desc spamfilter_policy;
SELECT *,spamfilter_users.id FROM spamfilter_users LEFT JOIN spamfilter_policy 
ON
spamfilter_users.policy_id=spamfilter_policy.id WHERE spamfilter_users.email IN 
('recei...@domain2.com','@domain2.com','@.domain2.com','@.com','@.') ORDER BY 
spamfilter_users.priority DESC;

(I don't have a mysql server handy to test this on, however the first
two should dump the database schema and the last should reproduce the
failing query)

Can I also confirm that absolutely nothing is writing to these tables?


> Maybe ISPConfig is not creating them exactly the same way amavisd-
> new would...

I see schema information at
https://git.ispconfig.org/ispconfig/ispconfig3/blob/0f9fa27a6c7026f77c7d857c971b1db1b709f583/install/sql/ispconfig3.sql
- according the git blame this hasn't changed within 6 years (line
endings were changed).  I would like confirmation that this matches what
is installed on the LOC's system. The above commands should answer that.
-- 
Brian May 

Bug#855076: giac: FTBFS: .../giac-doc/...: No such file or directory

[Aaron M. Ucko]

Source: giac
Version: 1.2.3.25+dfsg1-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Builds of giac covering only its architecture-dependent binary
packages have been failing:

  find debian/giac-doc/usr/share/giac/examples/ \
\( -name '*.cas' -o -name '*.xws' -o -name '*.cxx' \) -exec chmod -x '{}' \;
  find: 'debian/giac-doc/usr/share/giac/examples/': No such file or directory
  debian/rules:26: recipe for target 'override_dh_fixperms' failed
  make[1]: *** [override_dh_fixperms] Error 1
  make[1]: Leaving directory '/«BUILDDIR»/giac-1.2.3.25+dfsg1'
  debian/rules:7: recipe for target 'binary-arch' failed
  make: *** [binary-arch] Error 2

(On some architectures, the build fails earlier, due to unrelated
issues I'll report separately.)

Please conditionalize the debian/rules commands that work with
giac-doc appropriately, for instance by renaming override_dh_fixperms
to override_dh_fixperms-indep.

Thanks!

FTR, even though giac is new to Debian, I'm classifying this bug as a
regression because it would affect potential binNMUs.

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

Processed: Re: jarisplayer: FTBFS:

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 855066 src/jaris/player/Player.hx:1533: characters 17-33 : Only 
> inline or read-only (default, never) fields can be used as a pattern
Bug #855066 [src:jarisplayer] jarisplayer: FTBFS: 
Changed Bug title to 'src/jaris/player/Player.hx:1533: characters 17-33 : Only 
inline or read-only (default, never) fields can be used as a pattern' from 
'jarisplayer: FTBFS: '.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
855066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: retitle 835531

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 835531 theano: fail of test_csr_correct_output_faster_than_scipy at 
> times (FTBFS)
Bug #835531 [src:theano] theano: FTBFS on amd64 (fail of 
test_csr_correct_output_faster_than_scipy)
Changed Bug title to 'theano: fail of test_csr_correct_output_faster_than_scipy 
at times (FTBFS)' from 'theano: FTBFS on amd64 (fail of 
test_csr_correct_output_faster_than_scipy)'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
835531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#855066: jarisplayer: FTBFS:

[Chris Lamb]

Source: jarisplayer
Version: 2.0.17~dfsg-3
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

jarisplayer fails to build from source in unstable/amd64:

  […]

  find -type f -name '*.metadata_dump' -delete
  haxe -main jaris.Main -swf player.swf -cp src -D no-pattern-matching -dce full
  src/jaris/player/Player.hx:1533: characters 17-33 : Only inline or read-only 
(default, never) fields can be used as a pattern
  debian/rules:58: recipe for target 'debian/stamp-swf-build' failed
  make: *** [debian/stamp-swf-build] Error 1
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

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


jarisplayer.2.0.17~dfsg-3.unstable.amd64.log.txt.gz
Description: Binary data

Processed: theano: FTBFS on amd64 (fail of test_csr_correct_output_faster_than_scipy)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #835531 [src:theano] theano: FTBFS on amd64 (fail of 
test_csr_correct_output_faster_than_scipy)
Severity set to 'serious' from 'important'

-- 
835531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#854859: Pending fixes for bugs in the lemonldap-ng package

[Xavier]

On 12/02/2017 14:51, gregor herrmann wrote:
> On Sun, 12 Feb 2017 13:15:49 +0100, Xavier wrote:
> 
>>> You probably want to create debian/lemonldap-ng-doc.maintscript (and drop
>>> debian/lemonldap-ng-doc.preinst), with the following content:
>>>
>>> symlink_to_dir /usr/share/doc/lemonldap-ng-doc/pages/documentation/current 
>>> 1.3 1.9.7-3~
>>>
>>> (based solely on the commit diff, I didn't look further into your package)
>>>
>>
>> Thanks, it's ok now with:
>>
>> dir_to_symlink
>> /usr/share/doc/lemonldap-ng-doc/pages/documentation/current 1.3 1.4.6
>> lemonldap-ng-doc
> 
> I think this is wrong, and Andreas' proposal looks right to me:
> 1) The switch is from a symlink to a dir
> 2) The version where this is _handled_ is now, i.e. 1.9.7-3~
> 3) The package name is not needed (but shouldn't hurt)
> 
> 
> Now some testing would be good but my piuparts-fu is not good enough
> to test this uprade between a package in the archive and a locally
> built package ... So I tried manually in a jessie chroot, installed
> lemonldap-ng-doc, and then upgraded to 1.9.7-2 from the archive / 1.9.7-3
> with Xavier's version / 1.9.7-3 with Andreas' version, but all three
> end up like this (that's from the 3rd one):
> 
> # dpkg -i 
> /home/gregoa/src/git-pkg-perl/meta/packages/build-area/lemonldap-ng-doc_1.9.7-3_all.deb
> (Reading database ... 11584 files and directories currently installed.)
> Preparing to unpack .../lemonldap-ng-doc_1.9.7-3_all.deb ...
> Unpacking lemonldap-ng-doc (1.9.7-3) over (1.3.3-1) ...
> dpkg: warning: unable to delete old directory 
> '/usr/share/doc/lemonldap-ng-doc/pages/documentation/1.3/applications': 
> Directory not empty
> dpkg: warning: unable to delete old directory 
> '/usr/share/doc/lemonldap-ng-doc/pages/documentation/1.3': Directory not empty
> Setting up lemonldap-ng-doc (1.9.7-3) ...
> 
> # ls -la /usr/share/doc/lemonldap-ng-doc/pages/documentation/current  
>
> lrwxrwxrwx 1 root root 3 Oct 15  2014 
> /usr/share/doc/lemonldap-ng-doc/pages/documentation/current -> 1.3
> 
> *headscratch*
> 
> Oh, there are no traces of the maintscript stuff in
> lemonldap-ng-doc_1.9.7-3_all.deb!
> 
> *looking carefully*
> 
> debian/lemonldap-ng-doc.mainscript --> main_T_script
> 
> Yeah, this looks much better. Scripts in the deb, no warnings, and
> /usr/share/doc/lemonldap-ng-doc/pages/documentation/current is a
> directory.
> 
> Pushed to git, waiting with an upload for a test/sanity check of you
> guys.

Oups, thank you very much ! Works fine now

Bug#849132: marked as done (google-perftools FTBFS on i386: FAIL: profiler_unittest.sh)

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2017 20:05:45 +0100
with message-id <20170213190543.ga16...@ugent.be>
and subject line Re: google-perftools FTBFS on i386: FAIL: profiler_unittest.sh
has caused the Debian Bug report #849132,
regarding google-perftools FTBFS on i386: FAIL: profiler_unittest.sh
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
849132: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849132
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: google-perftools
Version: 2.5-2
Severity: serious

https://buildd.debian.org/status/logs.php?pkg=google-perftools=i386

...
PASS: profile_handler_unittest
rm -f profiler_unittest.sh
cp -p ./src/tests/profiler_unittest.sh profiler_unittest.sh
FAIL: profiler_unittest.sh
PASS: tcmalloc_and_profiler_unittest

Testsuite summary for gperftools 2.5

# TOTAL: 47
# PASS:  46
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to gperfto...@googlegroups.com

Makefile:5903: recipe for target 'test-suite.log' failed
make[3]: *** [test-suite.log] Error 1
--- End Message ---
--- Begin Message ---
Hi,

On Sun, Jan 29, 2017 at 07:19:00AM +, Niels Thykier wrote:
> Are there any news on the FTBFS bug? It has been stalling the fix for
> #838562 for about 40 days.

The latest attempt succeeded, but it's unclear what changed.

https://buildd.debian.org/status/fetch.php?pkg=google-perftools=i386=2.5-2=1486843465=0

Cheers,

Ivo--- End Message ---

Processed: tagging 854890, unblock 854576 with 854890

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 854890 - moreinfo
Bug #854890 [release.debian.org] unblock: pre-approval for libreoffice/5.2.5-2
Removed tag(s) moreinfo.
> unblock 854576 with 854890
Bug #854576 {Done: Rene Engelhard } [libreoffice-dev] 
libreoffice-dev: fails to upgrade libreoffice-dev-doc from jessie with 
--install-recommends enabled
854576 was blocked by: 854890
854576 was not blocking any bugs.
Removed blocking bug(s) of 854576: 854890
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
854576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854576
854890: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854890
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#854576: libreoffice-dev: fails to upgrade libreoffice-dev-doc from jessie with --install-recommends enabled

[Rene Engelhard]

Hi,

On Mon, Feb 13, 2017 at 02:46:27PM +0100, Rene Engelhard wrote:
> Hi,
> 
> On Sun, Feb 12, 2017 at 12:13:07PM +0100, Andreas Beckmann wrote:
> > > /usr/share/doc/libreoffice/sdk would also be possible AFAICS since it's
> > > no symlink and has (afaicr) never been used for the docs.
> > 
> > That would work as well ...
> 
> Unfortunately not:
> 
> In a chroot with jessie and apt-get install libreoffice libreoffice-dev 
> libreoffice-dev-doc, then dist-upgraded:
> 
> Preparing to unpack .../libreoffice_5.2.5-2_amd64.deb ...
> dpkg-maintscript-helper: error: directory '/usr/share/doc/libreoffice' 
> contains files not owned by package libreoffice, cannot switch to symlink
> dpkg: error processing archive 
> /home/rene/Debian/Pakete/LibreOffice/libreoffice/apt/./libreoffice_5.2.5-2_amd64.deb
>  (--unpack):
>  subprocess new pre-installation script returned error exit status 1
> 
> Given libreoffice does contain nothing as it's a metapackage I'd say one could
> remove libreoffice.maintscript and make it not being linked (-N for 
> --link-doc):
> % dpkg -L libreoffice
> /.
> /usr
> /usr/share
> /usr/share/bug
> /usr/share/bug/libreoffice
> /usr/share/bug/libreoffice/control
> /usr/share/bug/libreoffice/presubj
> /usr/share/doc
> /usr/share/doc/libreoffice

OK, it got working that way by reverting the dir_to_symlink thing (and to do
a symlink_to_dir thingy to already-there stretch/sid upgrades) and doing the
-N above.

Will upload soonish.

Regards,

Rene

Bug#850958: marked as done (ldc on ppc64el is broken)

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2017 20:12:09 +0200
with message-id <1487009529.31472.27.ca...@freevec.org>
and subject line Bug fixed in latest ldc ppc64le binNMU
has caused the Debian Bug report #850958,
regarding ldc on ppc64el is broken
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
850958: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850958
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: terminix
Version: 1.4.0-1
Severity: serious

Your package failed to build on ppc64el, preventing testing migration:

make[3]: Entering directory '/«PKGBUILDDIR»'
ldmd2 -O -inline -release -g -version=StdLoggerDisableTrace 
-I/usr/include/d/gtkd-3/ -L-lvted-3 -L-L/usr/lib/powerpc64le-linux-gnu/ 
-L-lgtkd-3 -L-ldl -c source/app.d source/gx/gtk/actions.d source/gx/gtk/cairo.d 
source/gx/gtk/clipboard.d source/gx/gtk/dialog.d source/gx/gtk/resource.d 
source/gx/gtk/settings.d source/gx/gtk/threads.d source/gx/gtk/util.d 
source/gx/gtk/vte.d source/gx/gtk/x11.d source/gx/i18n/l10n.d 
source/gx/terminix/application.d source/gx/terminix/appwindow.d 
source/gx/terminix/closedialog.d source/gx/terminix/cmdparams.d 
source/gx/terminix/colorschemes.d source/gx/terminix/common.d 
source/gx/terminix/constants.d source/gx/terminix/encoding.d 
source/gx/terminix/prefdialog.d source/gx/terminix/preferences.d 
source/gx/terminix/profileeditor.d source/gx/terminix/session.d 
source/gx/terminix/sessionswitcher.d source/gx/terminix/shortcuts.d 
source/gx/terminix/sidebar.d source/gx/terminix/terminal/actions.d 
source/gx/terminix/terminal/advpaste.d source/gx/terminix/terminal/exvte.d 
source/gx/terminix/terminal/layout.d source/gx/terminix/terminal/password.d 
source/gx/terminix/terminal/search.d source/gx/terminix/terminal/terminal.d 
source/gx/util/array.d source/gx/util/string.d source/secret/Collection.d 
source/secret/Item.d source/secret/Prompt.d source/secret/Schema.d 
source/secret/SchemaAttribute.d source/secret/Secret.d source/secret/Service.d 
source/secret/Value.d source/secretc/secret.d source/secretc/secrettypes.d 
source/x11/X.d source/x11/Xlib.d -ofterminix.o
Makefile:1034: recipe for target 'terminix.o' failed
make[3]: *** [terminix.o] Segmentation fault

Full logs at:

https://buildd.debian.org/status/package.php?p=terminix=sid

Emilio

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (800, 'unstable'), (700, 'experimental'), (650, 'testing'), (500, 
'unstable-debug'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf

Kernel: Linux 4.8.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
The latest binNMU seems to fix all build-failures for affected D
packages.

Konstantinos

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

Bug#852337: marked as done (ldc FTBFS on ppc64el: Failed to compile empty program using D compiler '/usr/bin/ldmd2')

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2017 20:12:09 +0200
with message-id <1487009529.31472.27.ca...@freevec.org>
and subject line Bug fixed in latest ldc ppc64le binNMU
has caused the Debian Bug report #850958,
regarding ldc FTBFS on ppc64el: Failed to compile empty program using D 
compiler '/usr/bin/ldmd2'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
850958: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850958
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ldc
Version: 1:1.1.0+b6-2
Severity: serious

https://buildd.debian.org/status/logs.php?pkg=ldc=ppc64el

...
-- Found host D compiler /usr/bin/ldmd2, with default flags ''
-- Host D compiler version: 
-- Found LLVM: /usr/lib/llvm-3.9 (found suitable version "3.9.1", minimum 
required is "3.5") 
-- Found LibConfig: /usr/include  
-- The ASM compiler identification is GNU
-- Found assembler: /usr/bin/cc
-- LDC version identifier: 1.1.0
-- Building LDC with PGO support
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Looking for setupterm in tinfo
-- Looking for setupterm in tinfo - found
CMake Error at cmake/Modules/ExtractDMDSystemLinker.cmake:40 (message):
  Failed to compile empty program using D compiler '/usr/bin/ldmd2'
Call Stack (most recent call first):
  CMakeLists.txt:559 (include)


-- Configuring incomplete, errors occurred!
...
--- End Message ---
--- Begin Message ---
The latest binNMU seems to fix all build-failures for affected D
packages.

Konstantinos

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

Bug#852263: marked as done (mustache-d FTBFS on ppc64el: Unknown compiler "ldc2")

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2017 20:12:09 +0200
with message-id <1487009529.31472.27.ca...@freevec.org>
and subject line Bug fixed in latest ldc ppc64le binNMU
has caused the Debian Bug report #850958,
regarding mustache-d FTBFS on ppc64el: Unknown compiler "ldc2"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
850958: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850958
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mustache-d
Version: 0.1.3-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=mustache-d=ppc64el=0.1.3-1=1484949441=0

...
make[1]: Entering directory '/«PKGBUILDDIR»'
mkdir build
(cd build && meson --prefix=/usr --buildtype=plain ..)
WARNING: You are using 'ANSI_X3.4-1968' which is not a a Unicode-compatible 
locale.
WARNING: You might see errors if you use UTF-8 strings as filenames, as 
strings, or as file contents.
WARNING: Please switch to a UTF-8 locale for your platform.
The Meson build system
Version: 0.37.1
Source dir: /«PKGBUILDDIR»
Build dir: /«PKGBUILDDIR»/build
Build type: native build
Project name: mustache-d

Meson encountered an error in file meson.build, line 1, column 0:
Unknown compiler "ldc2"
debian/rules:15: recipe for target 'override_dh_auto_configure' failed
make[1]: *** [override_dh_auto_configure] Error 1
--- End Message ---
--- Begin Message ---
The latest binNMU seems to fix all build-failures for affected D
packages.

Konstantinos

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

Bug#855058: gtk-vnc FTBFS on amd64/mipsel/mips64el/s390x: vncconnectiontest.c:64:test_send_u16: assertion failed

[Adrian Bunk]

Source: gtk-vnc
Version: 0.6.0-3
Severity: serious

https://buildd.debian.org/status/package.php?p=gtk-vnc

...
.. contents:: :depth: 2

FAIL: vncconnectiontest
===

/conn/validation/rre: OK
/conn/validation/copyrect: OK
/conn/validation/hextile: OK
/conn/validation/unexpectedcmap: **
ERROR:../../../src/vncconnectiontest.c:64:test_send_u16: assertion failed: 
(g_output_stream_write_all(os, , 2, NULL, NULL, NULL))
FAIL vncconnectiontest (exit status: 134)


Testsuite summary for gtk-vnc 0.6.0

# TOTAL: 1
# PASS:  0
# SKIP:  0
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See src/test-suite.log
Please report to https://bugzilla.gnome.org/enter_bug.cgi?product=gtk-vnc

Makefile:1754: recipe for target 'test-suite.log' failed
make[6]: *** [test-suite.log] Error 1

Bug#848764: marked as done (theano: test failures with Numpy 1.12)

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2017 17:48:36 +
with message-id 
and subject line Bug#848764: fixed in theano 0.8.2-4
has caused the Debian Bug report #848764,
regarding theano: test failures with Numpy 1.12
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
848764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: theano
Version: 0.8.2-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161219 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> self.with_linker(gof.PerformLinker(), scalar.and_, dtype=dtype)
>   File "/<>/theano/tensor/tests/test_elemwise.py", line 455, in 
> with_linker
> (f_xv, zv, xsh, tosum))
> AssertionError: (array(1, dtype=int8), array(-1, dtype=int8), (5, 0), [0, 1])
> 
> --
> Ran 2995 tests in 5904.778s
> 
> FAILED (SKIP=113, errors=3, failures=2)
> 0.0581646137166
> 0.0581646137166
> 0.0581646137166
> 0.0581646137166
> E: pybuild pybuild:276: test: plugin custom failed with: exit code=1: 
> PYTHONPATH=. python2.7 bin/theano-nose -v
> dh_auto_test: pybuild --test --test-nose -i python{version} -p 2.7 returned 
> exit code 13
> debian/rules:23: recipe for target 'override_dh_auto_test' failed

The full build log is available from:
   http://aws-logs.debian.net/2016/12/19/theano_0.8.2-3_unstable.log

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
Source: theano
Source-Version: 0.8.2-4

We believe that the bug you reported is fixed in the latest version of
theano, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 848...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Daniel Stender  (supplier of updated theano package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 13 Feb 2017 15:04:06 +0100
Source: theano
Binary: python-theano python3-theano theano-doc
Architecture: source amd64 all
Version: 0.8.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Daniel Stender 
Description:
 python-theano - CPU/GPU math expression compiler for Python
 python3-theano - CPU/GPU math expression compiler for Python 3
 theano-doc - CPU/GPU math expression compiler for Python (docs)
Closes: 848764
Changes:
 theano (0.8.2-4) unstable; urgency=medium
 .
   * add fixes-for-numpy-1.12.patch (Closes: #848764) [thanks to
 Rebecca N. Palmer].
Checksums-Sha1:
 ad6d0e6be50aedaf68ba64fd6dde3d7d12231d13 2691 theano_0.8.2-4.dsc
 a240e2e8f84b3051ff54dc019926c303565b7f5f 5440296 theano_0.8.2.orig.tar.xz
 4cb7574134c81aedf2f99179a8687f9e34cb83d2 358788 theano_0.8.2-4.debian.tar.xz
 35dc38d5eb51412a9225a2d3ac6ad594b3aaae08 1951994 
python-theano_0.8.2-4_amd64.deb
 bf4757650e7dc91f268927a1ed56f9cfe308abc2 1951828 
python3-theano_0.8.2-4_amd64.deb
 84a80aead3e05a665401847cb5be8acc8d4240f1 2732350 theano-doc_0.8.2-4_all.deb
 1d9a0709e6ec6d7d0a13b38e46d605ff282d8993 10012 theano_0.8.2-4_amd64.buildinfo
Checksums-Sha256:
 0216ba9310803163ae828185fb8ca7f090c652f4c121f125a8c2e4f119030f15 2691 
theano_0.8.2-4.dsc
 f672151b90f0085d6fcd255d82305c3b825f0fe5a3128cf65ddcb33d7e7ced06 5440296 
theano_0.8.2.orig.tar.xz
 333db29157324e4b25c9bddedde02e9d4ea96107f3c2e864f8e1ebaf3eb3 358788 
theano_0.8.2-4.debian.tar.xz
 dec5994934da1a988b0077c7fb666f044c12262b62b2acd79a6c9f950fc8aeab 1951994 
python-theano_0.8.2-4_amd64.deb
 d0e95f63862ff4174c369b2cc41286407266fc5cb4ae15d844b3e6ed584760b6 1951828 
python3-theano_0.8.2-4_amd64.deb
 

Bug#854592: [pkg-php-pear] Bug#854592: dokuwiki: Unable to login, missing usr/share/php/Crypt/AES.php

[David Prévot]

Hi,

On 13/02/2017 06:21, Joost van den Berg wrote:

> unfortunately the patch does not solve the problem.
> I believe that the patch generates the wrong
> links to phpseclib/Crypt/AES.php instead of
> ../phpseclib/Crypt/AES.php .

Then it sounds like this bug was incorrectly reassigned to
php-phpseclib: either dokuwiki should depend on version 1 of phpseclib
via the php-seclib package and have the files where expected, or it is
able to use version 2 via the php-phpseclib package installed where it
belongs. In any way, please, do keep both packages installable together,
the proposed patch is not acceptable.

Either way, dokuwiki should be able to use the provided autoloader:
- /usr/share/php/phpseclib/autoload.php for php-phpseclib
- /usr/share/php/phpseclib.autoloader.php for php-seclib

Regards

David



signature.asc
Description: OpenPGP digital signature

Processed: [bts-link] source package network-manager

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> #
> # bts-link upstream status pull for source package network-manager
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #854078 (http://bugs.debian.org/854078)
> # Bug title: network-manager: nm-online returns before network devices got an 
> address
> #  * http://bugzilla.gnome.org/show_bug.cgi?id=777831
> #  * remote status changed: NEW -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 854078 + fixed-upstream
Bug #854078 [network-manager] network-manager: nm-online returns before network 
devices got an address
Added tag(s) fixed-upstream.
> usertags 854078 - status-NEW
Usertags were: status-NEW.
Usertags are now: .
> usertags 854078 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
854078: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854078
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#849064: src:gkremldk: maintainer address bounces

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #849064 [src:gkremldk] src:gkremldk: maintainer address bounces
Severity set to 'serious' from 'important'

-- 
849064: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849064
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 833212 pending
Bug #833212 [src:libevent] libevent: Uses obsolete compressor for .deb data.tar 
member
Added tag(s) pending.
> tags 853799 pending
Bug #853799 [src:libevent] Please update to stable libevent 2.1 series
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
833212: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833212
853799: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#847311: amavisd-new: After the last Debian update Amavis does not read data type float from Mysql DB correctly. All fields are "0".

[Henrique de Moraes Holschuh]

Brian, could you forward the debug dump to upstream?  I don't have my
github login handy ATM...


Also, some interesting points:



On Mon, Feb 13, 2017, at 14:13, LOC wrote:

> 

> About the DB schema, someone asked before, I'm using ISPConfig 3.1, so
> the whole amavis configuration is done by that.
>  




This could be quite relevant.



LOC, could you send (to this bug report) a dump of the *schema* for the
relevant tables (the ones returning 0 instead of the correct float) ?


Maybe ISPConfig is not creating them exactly the same way amavisd-
new would...


--

  Henrique de Moraes Holschuh 

Bug#852130: marked as done (redmine: fails to install, purge and install again)

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2017 16:49:47 +
with message-id 
and subject line Bug#852130: fixed in redmine 3.3.1-3
has caused the Debian Bug report #852130,
regarding redmine: fails to install, purge and install again
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
852130: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852130
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: redmine
Version: 3.3.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install,
remove (but not purge), and install again.
Before the second installation the package is in config-files-remaining
state. The configuration is remaining from the last version that was
successfully configured - which is the same version that is going to be
installed again.

Like a plain failure on initial install this makes the package too buggy
for a release, thus the severity.

>From the attached log (scroll to the bottom...):
(this is from the second installation, the first one succeeded)

  Selecting previously unselected package redmine.
  (Reading database ... 
(Reading database ... 15736 files and directories currently installed.)
  Preparing to unpack .../redmine_3.3.1-2_all.deb ...
  Unpacking redmine (3.3.1-2) ...
  Setting up redmine (3.3.1-2) ...
  dbconfig-common: writing config to 
/etc/dbconfig-common/redmine/instances/default.conf
  
  Creating config file /etc/dbconfig-common/redmine/instances/default.conf with 
new version
  Not replacing deleted config file /etc/redmine/default/database.yml
  creating database redmine_default: success.
  verifying database redmine_default exists: success.
  rake aborted!
  Cannot load `Rails.application.database_configuration`:
  Could not load database configuration. No such file - 
["/usr/share/redmine/instances/default/config/database.yml"]
  /usr/share/redmine/lib/plugins/acts_as_activity_provider/init.rb:2:in `block 
in '
  /usr/share/redmine/config/initializers/00-core_plugins.rb:12:in `eval'
  /usr/share/redmine/config/initializers/00-core_plugins.rb:12:in `block in 
'
  /usr/share/redmine/config/initializers/00-core_plugins.rb:2:in `each'
  /usr/share/redmine/config/initializers/00-core_plugins.rb:2:in `'
  /usr/share/redmine/config/environment.rb:14:in `'
  Could not load database configuration. No such file - 
["/usr/share/redmine/instances/default/config/database.yml"]
  /usr/share/redmine/lib/plugins/acts_as_activity_provider/init.rb:2:in `block 
in '
  /usr/share/redmine/config/initializers/00-core_plugins.rb:12:in `eval'
  /usr/share/redmine/config/initializers/00-core_plugins.rb:12:in `block in 
'
  /usr/share/redmine/config/initializers/00-core_plugins.rb:2:in `each'
  /usr/share/redmine/config/initializers/00-core_plugins.rb:2:in `'
  /usr/share/redmine/config/environment.rb:14:in `'
  Tasks: TOP => db:migrate => environment
  (See full trace by running task with --trace)
  dpkg: error processing package redmine (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   redmine
  E: Sub-process /usr/bin/dpkg returned an error code (1)


cheers,

Andreas


redmine_3.3.1-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: redmine
Source-Version: 3.3.1-3

We believe that the bug you reported is fixed in the latest version of
redmine, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 852...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated redmine package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 13 Feb 2017 14:19:50 -0200
Source: redmine
Binary: redmine redmine-mysql redmine-pgsql redmine-sqlite
Architecture: source
Version: 3.3.1-3
Distribution: unstable
Urgency: medium
Maintainer: Antonio Terceiro 
Changed-By: Antonio Terceiro 
Description:
 redmine- flexible project management web application
 redmine-mysql - 

Bug#854723: marked as done (diffoscope: CVE-2017-0359: writes to arbitrary locations on disk based on the contents of an untrusted archive)

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2017 16:33:35 +
with message-id 
and subject line Bug#854723: fixed in diffoscope 77
has caused the Debian Bug report #854723,
regarding diffoscope: CVE-2017-0359: writes to arbitrary locations on disk 
based on the contents of an untrusted archive
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
854723: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: diffoscope
Version: 67
Severity: grave
Tags: patch security
Justification: user security hole

Dear Maintainer,

5fdfe91e71f1c520d902350b18f793b8c69d9118 introduced a security hole where
diffoscope may write to arbitrary locations on disk depending on the contents
of an untrusted archive. For example, comparing the following two files:

https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=843811;filename=libBrokenLocale.a.0;msg=5
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=2;bug=843811;filename=libBrokenLocale.a.1;msg=5

Traceback (most recent call last):
  File "/home/infinity0/xx/diffoscope/diffoscope/main.py", line 281, in main
sys.exit(run_diffoscope(parsed_args))
[..]
  File 
"/home/infinity0/xx/diffoscope/diffoscope/comparators/utils/libarchive.py", 
line 174, in extract
self.ensure_unpacked()
  File 
"/home/infinity0/xx/diffoscope/diffoscope/comparators/utils/libarchive.py", 
line 219, in ensure_unpacked
os.makedirs(os.path.dirname(dst), exist_ok=True)
  File "/usr/lib/python3.5/os.py", line 241, in makedirs
mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: '/SYM64'

Note that this could easily have been something like /home/infinity0/.profile.

I have pushed a nearly-complete fix to git (after version 75 was just released)
which prevents the writes. However reads are still done using the uncleaned
names, but this is a much less severe issue. So, if I don't supply a fix for
the second lesser issue soon, the existing fix should be released ASAP.

X

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

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

Versions of packages diffoscope depends on:
ii  python3-libarchive-c   2.1-3.1
ii  python3-magic  1:5.29-3
ii  python3-pkg-resources  33.1.1-1
pn  python3:any

Versions of packages diffoscope recommends:
ii  acl2.2.52-3
ii  apktool2.2.1+dfsg-2
ii  binutils-multiarch 2.27.90.20170124-2
ii  bzip2  1.0.6-8.1
ii  caca-utils 0.99.beta19-2+b1
ii  colord 1.3.3-2
ii  cpio   2.11+dfsg-6
ii  default-jdk [java-sdk] 2:1.8-58
ii  default-jdk-headless   2:1.8-58
ii  enjarify   1:1.0.3-3
ii  fontforge-extras   0.3-4
ii  fp-utils   3.0.0+dfsg-10
ii  fp-utils-3.0.0 [fp-utils]  3.0.0+dfsg-10
ii  genisoimage9:1.1.11-3
ii  gettext0.19.8.1-2
ii  ghc8.0.1-17
ii  ghostscript9.20~dfsg-2
ii  gnupg  2.1.18-3
ii  jsbeautifier   1.6.4-6
ii  llvm   1:3.8-34+b1
ii  mono-utils 4.6.2.7+dfsg-1
ii  openjdk-8-jdk [java-sdk]   8u121-b13-2
ii  openssh-client 1:7.4p1-6
ii  pdftk  2.02-4+b1
ii  poppler-utils  0.48.0-2
ii  python3-argcomplete1.8.1-1
ii  python3-debian 0.1.30
ii  python3-guestfs1:1.34.3-7
ii  python3-progressbar2.3-4
ii  python3-rpm4.12.0.2+dfsg1-1
ii  python3-tlsh   3.4.4+20151206-1+b1
ii  rpm2cpio   4.12.0.2+dfsg1-1
ii  sng1.1.0-1+b1
ii  sqlite33.16.2-2
ii  squashfs-tools 1:4.3-3
ii  unzip  6.0-21
ii  vim-common 2:8.0.0197-1
ii  xxd2:8.0.0197-1
ii  xz-utils   5.2.2-1.2

Versions of packages diffoscope suggests:
ii  libjs-jquery  3.1.1-2

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: diffoscope
Source-Version: 77

We believe that the bug you reported is fixed in the 

Processed: Re: Bug#855050: systemd: systemctl regressions, assertion failure with "--user enable" without HOME, and more

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #855050 [systemd] systemd: systemctl regressions, assertion failure with 
"--user enable" without HOME, and more
Added tag(s) pending.
> severity -1 important
Bug #855050 [systemd] systemd: systemctl regressions, assertion failure with 
"--user enable" without HOME, and more
Severity set to 'important' from 'serious'

-- 
855050: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855050
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#855050: systemd: systemctl regressions, assertion failure with "--user enable" without HOME, and more

[Martin Pitt]

Control: tag -1 pending
Control: severity -1 important

Raphaël Hertzog [2017-02-13 16:39 +0100]:
> Severity: serious

That seems grossly inflated, adjusting.

> Any invocation of "systemctl --user enable/disable" will fail if
> XDG_RUNTIME_DIR is not set while it's strictly not required to do
> its job.
> 
> The same pull request also fixes other regressions where you can't
> properly track processes of a unit that has been removed or even
> disable that dropped unit.
> 
> https://github.com/systemd/systemd/pull/5303

I cherry-picked some appropriate ones which are relatively straightforward and
safe for the freeze:

  https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=7864ad6a6
  
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=cb8df0e367064

Martin

Bug#847311: amavisd-new: After the last Debian update Amavis does not read data type float from Mysql DB correctly. All fields are "0".

[LOC]

Hello Henrique, 
thank you for the response and guide to modify amavisd-new, I have done that 
and restarted amavis with
"/etc/init.d/amavis debug".
The results are in the attachment, hope it will help.

 
About the DB schema, someone asked before, I'm using ISPConfig 3.1, so the 
whole amavis configuration is done by that.
 
Best regards
Jakub Novak


__
> Od: Henrique de Moraes Holschuh 
> Komu: 847...@bugs.debian.org
> Datum: 12.02.2017 17:26
> Předmět: Re: Bug#847311: amavisd-new: After the last Debian update Amavis
>
On Sun, 12 Feb 2017, Brian May wrote:
> >> https://github.com/perl5-dbi/DBD-mysql/issues/78 

> 
> Please read the latest message on the above report...


Jakub,

This issue is a nasty problem between amavisd-new and DBD-mysql.  It is
yet not clear which program is at fault, or if it is an ABI break gone
bad, etc.

The upstream bug report is at:
https://github.com/perl5-dbi/DBD-mysql/issues/78 


The amavisd-new Debian maintainers and DBD upstream are having trouble
to reproduce the issue, although we do have breakage reports also from
in Fedora, Gentoo and FreeBSD.  There is cleary some factor we're
missing.


Upstream DBD asks (in the issue linked above):

"So I see only option now, enabling DBI tracing in that problematic
amavis code and sending stderr trace output for later inspection.
Tracing can be enabled by DBI->trace(2); and disabled by DBI->trace(0);"


Would you be willing to reproduce the issue you reported with the
changes requested by upstream?

AFAIK, you just need to add:

  $conn_h->trace(2);

around line 20211 in /usr/sbin/amavisd-new (I think right after
or right before the

  $conn_h->begin_work_nontransaction;  # (re)connect if not connected

line would work best.


It is probably best to disable the tracing at the end of the function, by 
adding:

  $conn_h->trace(0);

right before the line reading "section_time('lookup_sql');" around line
number 20262.


If that doesn't work, try using DBI->trace(2); and DBI->trace(0);
instead.


Since the trace information goes to stderr, it would probably be best to
debug amavis by running it in "foreground" mode, and diverting stderr
to a file...

Thanks!

--
 Henrique Holschuh

Feb 12 20:28:14.535 mailserver.domain2.com /usr/sbin/amavisd-new[6693]: 
Net::Server: 2017/02/12-20:28:14 CONNECT TCP Peer: "[127.0.0.1]:37442" Local: 
"[127.0.0.1]:10024"
Feb 12 20:28:14.536 mailserver.domain2.com /usr/sbin/amavisd-new[6693]: loaded 
base policy bank
Feb 12 20:28:14.538 mailserver.domain2.com /usr/sbin/amavisd-new[6693]: 
lookup_ip_acl (inet_acl) arr.obj: key="127.0.0.1" matches "127.0.0.1", result=1
Feb 12 20:28:14.538 mailserver.domain2.com /usr/sbin/amavisd-new[6693]: 
process_request: fileno sock=15, STDIN=0, STDOUT=1
Feb 12 20:28:14.538 mailserver.domain2.com /usr/sbin/amavisd-new[6693]: 
get_deadline switch_to_my_time(new request) - deadline in 480.0 s, set to 
288.000 s
Feb 12 20:28:14.538 mailserver.domain2.com /usr/sbin/amavisd-new[6693]: 
prolong_timer switch_to_my_time(new request): timer 288, was 0, deadline in 
480.0 s
Feb 12 20:28:14.539 mailserver.domain2.com /usr/sbin/amavisd-new[6693]: 
process_request: suggested_protocol="" on a TCP socket
Feb 12 20:28:14.540 mailserver.domain2.com /usr/sbin/amavisd-new[6693]: 
(06693-01) SMTP> 220 [127.0.0.1] ESMTP amavisd-new service ready
Feb 12 20:28:14.540 mailserver.domain2.com /usr/sbin/amavisd-new[6693]: 
(06693-01) switch_to_client_time 480 s, smtp response sent
Feb 12 20:28:14.540 mailserver.domain2.com /usr/sbin/amavisd-new[6693]: 
(06693-01) idle_proc, 4: was busy, 5.3 ms, total idle 0.000 s, busy 0.005 s
Feb 12 20:28:14.540 mailserver.domain2.com /usr/sbin/amavisd-new[6693]: 
(06693-01) smtp readline: read 20 bytes, new size: 20
Feb 12 20:28:14.540 mailserver.domain2.com /usr/sbin/amavisd-new[6693]: 
(06693-01) idle_proc, 5: was idle, 0.2 ms, total idle 0.000 s, busy 0.005 s
Feb 12 20:28:14.541 mailserver.domain2.com /usr/sbin/amavisd-new[6693]: 
(06693-01) SMTP< EHLO mailserver.domain2.com\r\n
Feb 12 20:28:14.541 mailserver.domain2.com /usr/sbin/amavisd-new[6693]: 
(06693-01) get_deadline switch_to_my_time(rx SMTP EHLO) - deadline in 480.0 s, 
set to 288.000 s
Feb 12 20:28:14.541 mailserver.domain2.com /usr/sbin/amavisd-new[6693]: 
(06693-01) prolong_timer switch_to_my_time(rx SMTP EHLO): timer 288, was 480, 
deadline in 480.0 s
Feb 12 20:28:14.542 mailserver.domain2.com /usr/sbin/amavisd-new[6693]: 
(06693-01) ESMTP> 250-[127.0.0.1]
Feb 12 20:28:14.542 mailserver.domain2.com /usr/sbin/amavisd-new[6693]: 
(06693-01) ESMTP> 250-VRFY
Feb 12 20:28:14.542 mailserver.domain2.com /usr/sbin/amavisd-new[6693]: 
(06693-01) ESMTP> 250-PIPELINING
Feb 12 20:28:14.542 mailserver.domain2.com /usr/sbin/amavisd-new[6693]: 
(06693-01) ESMTP> 250-SIZE
Feb 12 20:28:14.542 mailserver.domain2.com 

Processed: Re: Bug#853921: fonts-android-udeb: broken rendering for Korean glyphs in debian-installer

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #853921 [fonts-android-udeb] fonts-android-udeb: broken rendering for 
Korean glyphs in debian-installer
Added tag(s) patch.

-- 
853921: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#853921: fonts-android-udeb: broken rendering for Korean glyphs in debian-installer

[Cyril Brulebois]

Control: tag -1 patch

Cyril Brulebois  (2017-02-02):
> We'll need to have a fix for stretch, otherwise that means no Korean
> support in d-i, which doesn't seem reasonable.
> 
> I might try and check whether the needed codepoints are present in the
> new version (through fontforge) but I'm no expert at all… Maybe that's
> just some fontconfig stuff that needs adjusting.
> 
> I can easily test any patches against fonts-android, since building
> d-i against local packages only takes a minute here; so feel free to
> use me as a puppet to experiment fixes. ;-)

Switching from the Full to the non-Full variant of this font seems to be
the way to go, at least at the moment, see Changwoo Ryu's reply and mine:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853917#32
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853917#37

You'll find attached a patch against sid to implement this change. I've
initially worked with your git repository, but I think it's missing at
least a tag for the recent upload.

I'm fine with NMUing your package if that saves you time. Please let me
know what you prefer.


KiBi.
diff -Nru fonts-android-6.0.1r16/debian/changelog fonts-android-6.0.1r16/debian/changelog
--- fonts-android-6.0.1r16/debian/changelog	2016-02-14 07:47:12.0 +0100
+++ fonts-android-6.0.1r16/debian/changelog	2017-02-13 16:33:09.0 +0100
@@ -1,3 +1,11 @@
+fonts-android (1:6.0.1r16-2) UNRELEASED; urgency=medium
+
+  * Switch from DroidSansFallbackFull.ttf to DroidSansFallback.ttf in the
+fonts-android-udeb package, which fixes missing Korean glyphs for use
+within the Debian Installer (Closes: #853921).
+
+ -- Cyril Brulebois   Mon, 13 Feb 2017 16:32:50 +0100
+
 fonts-android (1:6.0.1r16-1) unstable; urgency=medium
 
   * Imported Upstream version 6.0.1r16
diff -Nru fonts-android-6.0.1r16/debian/fonts-android-udeb.install fonts-android-6.0.1r16/debian/fonts-android-udeb.install
--- fonts-android-6.0.1r16/debian/fonts-android-udeb.install	2016-02-14 07:47:12.0 +0100
+++ fonts-android-6.0.1r16/debian/fonts-android-udeb.install	2017-02-13 16:33:41.0 +0100
@@ -1 +1 @@
-DroidSansFallbackFull.ttf	usr/share/fonts/truetype/droid
+DroidSansFallback.ttf	usr/share/fonts/truetype/droid


signature.asc
Description: Digital signature

Bug#855050: systemd: systemctl regressions, assertion failure with "--user enable" without HOME, and more

[Raphaël Hertzog]

Package: systemd
Version: 232-15
Severity: serious
User: de...@kali.org
Usertags: origin-kali

I opened this upstream: https://github.com/systemd/systemd/issues/5260
and I would like to get this fixed in Debian stretch. This is a regression
compared to former versions. 

Any invocation of "systemctl --user enable/disable" will fail if
XDG_RUNTIME_DIR is not set while it's strictly not required to do
its job.

The same pull request also fixes other regressions where you can't
properly track processes of a unit that has been removed or even
disable that dropped unit.

https://github.com/systemd/systemd/pull/5303

The commit I need most is this one:
https://github.com/systemd/systemd/pull/5303/commits/c3c7eb7d7debbe2b2e708fb8d4d11f06869e0d0a

(while Lennart wrongly tagged another commit as fixing my issue)

-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser 3.115
ii  libacl1 2.2.52-3
ii  libapparmor12.11.0-2
ii  libaudit1   1:2.6.7-1
ii  libblkid1   2.29.1-1
ii  libc6   2.24-9
ii  libcap2 1:2.25-1
ii  libcryptsetup4  2:1.7.3-3
ii  libgcrypt20 1.7.6-1
ii  libgpg-error0   1.26-2
ii  libidn111.33-1
ii  libip4tc0   1.6.0+snapshot20161117-5
ii  libkmod223-2
ii  liblz4-10.0~r131-2
ii  liblzma55.2.2-1.2
ii  libmount1   2.29.1-1
ii  libpam0g1.1.8-3.5
ii  libseccomp2 2.3.1-2.1
ii  libselinux1 2.6-3
ii  libsystemd0 232-15
ii  mount   2.29.1-1
ii  util-linux  2.29.1-1

Versions of packages systemd recommends:
ii  dbus1.10.14-1
ii  libpam-systemd  232-15

Versions of packages systemd suggests:
ii  policykit-10.105-17
pn  systemd-container  
pn  systemd-ui 

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.127
ii  udev 232-15

-- no debconf information

Bug#843467: libxbase64-1: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE

[Jörg Frings-Fürst]

Hello Andreas,

since 2016-12-24 is the version 3.1.2-11 into testing.

with this version I have tested with

- sudo piuparts --basetgz=../../jessie-amd64-base.tgz -d jessie -d stretch 
*.changes
- sudo piuparts  --basetgz=../../sid-amd64-base.tgz *.changes

without any errors.

The debian puiparts service[1] are always successfully-tested. 

Please can you test again?

Many thanks.

CU
Jörg


[1] https://piuparts.debian.org/sid/maintainer/d/deb...@jff-webhosting.net.html
-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema: SYR8SJXB

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.


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

Bug#854592: dokuwiki: Unable to login, missing usr/share/php/Crypt/AES.php

[Joost van den Berg]

Hi,

unfortunately the patch does not solve the problem.
I believe that the patch generates the wrong
links to phpseclib/Crypt/AES.php instead of
../phpseclib/Crypt/AES.php . Please find my modified
patch attached which results in:

ls /usr/share/php/Crypt/ -l
totaal 0
lrwxrwxrwx 1 root root 26 feb 13 06:25 AES.php -> ../phpseclib/Crypt/AES.php
lrwxrwxrwx 1 root root 27 feb 13 06:25 Base.php -> 
../phpseclib/Crypt/Base.php
lrwxrwxrwx 1 root root 31 feb 13 06:25 Blowfish.php -> 
../phpseclib/Crypt/Blowfish.php

lrwxrwxrwx 1 root root 26 feb 13 06:25 DES.php -> ../phpseclib/Crypt/DES.php
lrwxrwxrwx 1 root root 27 feb 13 06:25 Hash.php -> 
../phpseclib/Crypt/Hash.php
lrwxrwxrwx 1 root root 29 feb 13 06:25 Random.php -> 
../phpseclib/Crypt/Random.php

lrwxrwxrwx 1 root root 26 feb 13 06:25 RC2.php -> ../phpseclib/Crypt/RC2.php
lrwxrwxrwx 1 root root 26 feb 13 06:25 RC4.php -> ../phpseclib/Crypt/RC4.php
lrwxrwxrwx 1 root root 31 feb 13 06:25 Rijndael.php -> 
../phpseclib/Crypt/Rijndael.php

lrwxrwxrwx 1 root root 26 feb 13 06:25 RSA.php -> ../phpseclib/Crypt/RSA.php
lrwxrwxrwx 1 root root 32 feb 13 06:25 TripleDES.php -> 
../phpseclib/Crypt/TripleDES.php
lrwxrwxrwx 1 root root 30 feb 13 06:25 Twofish.php -> 
../phpseclib/Crypt/Twofish.php


After applying the modified patch,
apaches error_log now complains:

[Mon Feb 13 15:38:31.195635 2017] [:error] [pid 11065]
[client 127.0.0.1:36936] PHP Fatal error:
Class 'phpseclib\\Crypt\\Rijndael' not found in
/usr/share/php/phpseclib/Crypt/AES.php on line 59,
referer: 
http://localhost/dokuwiki/doku.php?id=start=login=0ed612230c760db559e


So although the file Crypt/AES.php is now found, it
cannot import other classes from there any further.

Joost


diff -Nru php-phpseclib-2.0.4/debian/changelog php-phpseclib-2.0.4/debian/changelog
--- php-phpseclib-2.0.4/debian/changelog	2016-10-21 10:34:04.0 +0900
+++ php-phpseclib-2.0.4/debian/changelog	2017-02-13 14:25:16.0 +0900
@@ -1,3 +1,13 @@
+php-phpseclib (2.0.4-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/rules
+- fix breakage of PATH difference (Closes: #854592) 
+  * debian/control
+- fix insecure Vcs-* field
+
+ -- Hideki Yamane   Mon, 13 Feb 2017 14:25:16 +0900
+
 php-phpseclib (2.0.4-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru php-phpseclib-2.0.4/debian/control php-phpseclib-2.0.4/debian/control
--- php-phpseclib-2.0.4/debian/control	2016-10-21 10:34:04.0 +0900
+++ php-phpseclib-2.0.4/debian/control	2017-02-13 14:25:16.0 +0900
@@ -6,8 +6,8 @@
 Build-Depends: debhelper (>= 9), phpab, pkg-php-tools (>= 1.7~)
 Standards-Version: 3.9.8
 Homepage: http://phpseclib.sourceforge.net/
-Vcs-Git: git://anonscm.debian.org/pkg-php/phpseclib.git
-Vcs-Browser: http://anonscm.debian.org/gitweb/?p=pkg-php/phpseclib.git
+Vcs-Git: https://anonscm.debian.org/cgit/pkg-php/phpseclib.git
+Vcs-Browser: https://anonscm.debian.org/git/pkg-php/phpseclib.git
 
 Package: php-phpseclib
 Architecture: all
diff -Nru php-phpseclib-2.0.4/debian/rules php-phpseclib-2.0.4/debian/rules
--- php-phpseclib-2.0.4/debian/rules	2016-10-21 10:34:04.0 +0900
+++ php-phpseclib-2.0.4/debian/rules	2017-02-13 14:25:16.0 +0900
@@ -11,6 +11,11 @@
 override_dh_install:
 	dh_install -Xopenssl.cnf
 
+override_dh_link:
+	(cd $(CURDIR)/debian/php-phpseclib/usr/share/php; \
+ for dir in `find . -type d -print`; do mkdir -p `echo $$dir | sed -e s%./phpseclib/%%`; done ;\
+ for file in `find . -name '*.php' -print`; do ln -sf `echo $$file| sed -e s%^./%../%` `echo $$file | sed -e s%./phpseclib/%%`; done)
+
 override_dh_installchangelogs:
 	dh_installchangelogs debian/upstream/changelog
 


smime.p7s
Description: S/MIME-cryptografische ondertekening

Bug#855048: qgis: Ships an unsupported copy of QtWebkit in public Python path without any transition

[Bas Couwenberg]

Control: severity -1 important

On 2017-02-13 15:57, Raphaël Hertzog wrote:

python-qt4 dropped support for QtWebkit it's because it was not
possible to provide security support for it (cf #784514). You disabled
that support in response to that bug.

But later you decided to re-enable it using an embedded copy, the net
result is that python-qgis is now shipping files that used to be
shipped by python-qt4:
/usr/lib/python2.7/dist-packages/PyQt4/QtWebKit.x86_64-linux-gnu.so


Yes, because QGIS without QtWebKit loses most plugins and other 
functionality demanded by users.



There are two problems:

1/ the upgrade is not safe, you can have conflicts with python-qt4 if
python-qgis is upgraded before python-qt4 (even more likely in Kali
where we kept QtWebkit a while longer in python-qt4)


Adding Breaks/Replaces is no problem.


2/ if QtWebkit cannot be suppported in python-qt4, it also cannot be
supported in python-qgis


It doesn't have to be supported to be included.


IMO you should disable that embedded copy usage or at least get a prior
ack from the security team.


NAK, the QtWebKit support stays as it's in the interest of our users.

Upstream added the QtWebKit support for Python because the C++ package 
(qtwebkit) is still available and only the in development 3.x branch of 
QGIS has support for Qt5.


The debian-security-support package already warns about no security 
support for qtwebkit so that doesn't change anything wrt QtWebKit 
support in QGIS.


Kind Regards,

Bas

Processed: Re: Bug#855048: qgis: Ships an unsupported copy of QtWebkit in public Python path without any transition

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #855048 [src:qgis] qgis: Ships an unsupported copy of QtWebkit in public 
Python path without any transition
Severity set to 'important' from 'serious'

-- 
855048: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855048
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#854616: marked as done (scdaemon cannot access yubikey using ccid driver without pcscd)

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2017 15:18:52 +
with message-id 
and subject line Bug#854616: fixed in gnupg2 2.1.18-5
has caused the Debian Bug report #854616,
regarding scdaemon cannot access yubikey using ccid driver without pcscd
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
854616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: scdaemon
Version: 2.1.18-3
Severity: grave

In Bug#854005, I have described a distinct issue I have experience
with my Yubikey since the upgrade of the GnuPG suite from 2.1.17 to
2.1.18, and in the case of pcscd, from 1.8.19-1 to 1.8.20-1.

I am not sure what exactly is going on here. What I know is that I was
able to configure my Yubikey to work in Jessie with GnuPG using a
procedure I have documented here:

https://anarc.at/blog/2015-12-14-yubikey-howto/

After installing a new workstation with Debian stretch, things were
still working until the 2.1.18 release.

The symptom is this:

[996]anarcat@curie:~$ LANG=C gpg --card-status
gpg: selecting openpgp failed: No such device
gpg: OpenPGP card not available: No such device

At first, adding "disable-ccid" to scdaemon.conf fixes the issue. But
after a while, the behavior returns.

I have noticed that pcscd is gone when that happens. After advice
received in 854005, I have tried to uninstall pcscd to try and let
scdaemon handle the device. This also fails. Here's a trace of me
purging pcscd, restarting gpg-agent and trying to connect to the card.

[1001]anarcat@curie:~$ sudo apt purge pcscd
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances   
Lecture des informations d'état... Fait
Le paquet suivant a été installé automatiquement et n'est plus nécessaire :
  libccid
Veuillez utiliser « sudo apt autoremove » pour le supprimer.
Les paquets suivants seront ENLEVÉS :
  pcscd*
0 mis à jour, 0 nouvellement installés, 1 à enlever et 23 non mis à jour.
Après cette opération, 205 ko d'espace disque seront libérés.
Souhaitez-vous continuer ? [O/n] 
(Lecture de la base de données... 291154 fichiers et répertoires déjà 
installés.)
Suppression de pcscd (1.8.20-1) ...
Warning: Stopping pcscd.service, but it can still be activated by:
  pcscd.socket
Traitement des actions différées (« triggers ») pour man-db (2.7.6.1-2) ...
(Lecture de la base de données... 291142 fichiers et répertoires déjà 
installés.)
Purge des fichiers de configuration de pcscd (1.8.20-1) ...
Traitement des actions différées (« triggers ») pour systemd (232-15) ...
[master ab8bc2d] committing changes in /etc after apt run
 Author: Antoine Beaupré 
 10 files changed, 155 deletions(-)
 delete mode 100755 init.d/pcscd
 delete mode 12 rc0.d/K01pcscd
 delete mode 12 rc1.d/K01pcscd
 delete mode 12 rc2.d/S01pcscd
 delete mode 12 rc3.d/S01pcscd
 delete mode 12 rc4.d/S01pcscd
 delete mode 12 rc5.d/S01pcscd
 delete mode 12 rc6.d/K01pcscd
 delete mode 12 systemd/system/sockets.target.wants/pcscd.socket
[1002]anarcat@curie:~$ systemctl --user stop gpg-agent
Warning: Stopping gpg-agent.service, but it can still be activated by:
  gpg-agent.socket
  gpg-agent-ssh.socket
  gpg-agent-extra.socket
  gpg-agent-browser.socket
[1003]anarcat@curie:~$ ps axf | grep gpg
27310 pts/4S+ 0:00  \_ grep gpg
[1004]anarcat@curie:~$ LANG=C gpg --card-status
gpg: selecting openpgp failed: No such device
gpg: OpenPGP card not available: No such device

Here's the output proving gpg is stopped:

fév 08 12:22:09 curie systemd[1199]: Stopping GnuPG cryptographic agent and 
passphrase cache... 
fév 08 12:22:09 curie systemd[1199]: Stopped GnuPG cryptographic agent and 
passphrase cache. 
fév 08 12:22:09 curie gpg-agent[21736]: scdaemon[21738] SIGTERM received - 
shutting down ... 
fév 08 12:22:09 curie gpg-agent[21736]: SIGTERM received - shutting down ... 
fév 08 12:22:09 curie gpg-agent[21736]: gpg-agent (GnuPG) 2.1.18scdaemon[21738] 
scdaemon (GnuPG) 2.1.18 stopped 
fév 08 12:22:09 curie gpg-agent[21736]:  stopped

Here's the error when i try to access the card then:

fév 08 12:24:20 curie systemd[1199]: Started GnuPG cryptographic agent and 
passphrase cache. 
fév 08 12:24:20 curie gpg-agent[27960]: gpg-agent (GnuPG) 2.1.18 starting in 
supervised mode. 
fév 08 12:24:20 curie gpg-agent[27960]: using fd 3 for std socket 
(/run/user/1000/gnupg/S.gpg-agent) 
fév 08 12:24:20 curie gpg-agent[27960]: using fd 4 for ssh socket 
(/run/user/1000/gnupg/S.gpg-agent.ssh) 
fév 08 

Bug#854616: marked as pending

[Daniel Kahn Gillmor]

tag 854616 pending
thanks

Hello,

Bug #854616 reported by you has been fixed in the Git repository. You can
see the changelog below, and you can check the diff of the fix at:

http://git.debian.org/?p=pkg-gnupg/gnupg2.git;a=commitdiff;h=4c91bae

---
commit 4c91bae777022f7ffd2ac4fa69837d59653eeb8f
Author: Daniel Kahn Gillmor 
Date:   Mon Feb 13 09:41:56 2017 -0500

prepare new debian release

diff --git a/debian/changelog b/debian/changelog
index edd953b..bca7302 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+gnupg2 (2.1.18-5) unstable; urgency=medium
+
+  [ Daniel Kahn Gillmor ]
+  * Xsession.d/90gpg-agent: use simpler and more direct gpgconf
+invocations for socket names.
+
+  [ NIIBE Yutaka ]
+  * scdaemon.udev: Add Yubikey and Nitrokey (Closes: #648331, 734889).
+  * scdaemon fix for PC/SC (Closes: #852702, #854005, #854595, #854616).
+
+ -- Daniel Kahn Gillmor   Mon, 13 Feb 2017 09:15:07 
-0500
+
 gnupg2 (2.1.18-4) unstable; urgency=medium
 
   [ Daniel Kahn Gillmor ]

Processed: Bug#854616 marked as pending

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tag 854616 pending
Bug #854616 [scdaemon] scdaemon cannot access yubikey using ccid driver without 
pcscd
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
854616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#855048: qgis: Ships an unsupported copy of QtWebkit in public Python path without any transition

[Raphaël Hertzog]

Source: qgis
Version: 2.14.11+dfsg-1
Severity: serious
Tags: security
User: de...@kali.org
Usertags: origin-kali

python-qt4 dropped support for QtWebkit it's because it was not
possible to provide security support for it (cf #784514). You disabled
that support in response to that bug.

But later you decided to re-enable it using an embedded copy, the net
result is that python-qgis is now shipping files that used to be
shipped by python-qt4:
/usr/lib/python2.7/dist-packages/PyQt4/QtWebKit.x86_64-linux-gnu.so

There are two problems:

1/ the upgrade is not safe, you can have conflicts with python-qt4 if
python-qgis is upgraded before python-qt4 (even more likely in Kali
where we kept QtWebkit a while longer in python-qt4)

2/ if QtWebkit cannot be suppported in python-qt4, it also cannot be
supported in python-qgis

IMO you should disable that embedded copy usage or at least get a prior
ack from the security team.

Cheers,

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

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

Processed: Re: [Piuparts-devel] Bug#855038: All test ends with "INFO: SKIP: All tests. Package cannot be tested with piuparts:"

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #855038 [piuparts] All test ends with "INFO: SKIP: All tests. Package 
cannot be tested with piuparts:"
Severity set to 'serious' from 'important'

-- 
855038: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855038
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#854576: libreoffice-dev: fails to upgrade libreoffice-dev-doc from jessie with --install-recommends enabled

[Rene Engelhard]

Hi,

On Sun, Feb 12, 2017 at 12:13:07PM +0100, Andreas Beckmann wrote:
> > /usr/share/doc/libreoffice/sdk would also be possible AFAICS since it's
> > no symlink and has (afaicr) never been used for the docs.
> 
> That would work as well ...

Unfortunately not:

In a chroot with jessie and apt-get install libreoffice libreoffice-dev 
libreoffice-dev-doc, then dist-upgraded:

Preparing to unpack .../libreoffice_5.2.5-2_amd64.deb ...
dpkg-maintscript-helper: error: directory '/usr/share/doc/libreoffice' contains 
files not owned by package libreoffice, cannot switch to symlink
dpkg: error processing archive 
/home/rene/Debian/Pakete/LibreOffice/libreoffice/apt/./libreoffice_5.2.5-2_amd64.deb
 (--unpack):
 subprocess new pre-installation script returned error exit status 1

Given libreoffice does contain nothing as it's a metapackage I'd say one could
remove libreoffice.maintscript and make it not being linked (-N for --link-doc):
% dpkg -L libreoffice
/.
/usr
/usr/share
/usr/share/bug
/usr/share/bug/libreoffice
/usr/share/bug/libreoffice/control
/usr/share/bug/libreoffice/presubj
/usr/share/doc
/usr/share/doc/libreoffice

Regards,

Rene

Bug#848764: theano: test failures with Numpy 1.12

[Ole Streicher]

Hi Daniel,

the remaining numpy-1.12 failurtes can be resolved with this patch:

https://github.com/Theano/Theano/commit/a95f8af1b4c54a8ffa77fcd5f44cfdcb1772cf22

Cheers

Ole

Processed: retitle 854723 to diffoscope: CVE-2017-0359: writes to arbitrary locations on disk based on the contents of an untrusted archive

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> retitle 854723 diffoscope: CVE-2017-0359: writes to arbitrary locations on 
> disk based on the contents of an untrusted archive
Bug #854723 [diffoscope] diffoscope writes to arbitrary locations on disk based 
on the contents of an untrusted archive
Changed Bug title to 'diffoscope: CVE-2017-0359: writes to arbitrary locations 
on disk based on the contents of an untrusted archive' from 'diffoscope writes 
to arbitrary locations on disk based on the contents of an untrusted archive'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
854723: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#854838: kde-full: When kde-full is installed, upgrading from jessie to stretch is extremely hard (if not impossible for beginners)

[Maximiliano Curia]

Control: severity -1 normal

¡Hola Julien!

El 2017-02-11 a las 00:28 +0100, Julien Aubin escribió:
Package: kde-full 
Version: 5:92 
Severity: critical 
Justification: breaks the whole system


If anything is "apt upgrade" in jessie the one blame here, please see bellow.

This bug only appears when upgrading a jessie system to stretch, but is a 
release blocker at least w/ amd64 arch with foreign i386 arch enabled.


As per documentation, dist upgrade from jessie to stretch should work as 
follows :
1/ update sources.list 
2/ apt update 
3/ apt upgrade 
4/ apt dist-upgrade


The issue actually lies at the apt upgrade step, as it is reported that package 
kdepimlibs-data breaks several other packages, so the upgrade cannot be 
performed.


The upgrade in apt doesn't behaves in the same way as the upgrade in apt-get. 
The first one tries to install the new packages that the new versions depend 
on, while the one in apt tries to avoid installing and removing packages.


apt-get upgrade should take care of upgrading the packages that don't bring 
new dependencies (about half of my test installation).


I'll blame the upgrade procedure you are trying to follow, is it documented as 
such somewhere?


After that, apt-get dist-upgrade seems to do almost everything else, but it 
tried to remove aptitude, so:

apt-get dist-upgrade aptitude libcwidget3v5

Would do the right thing for me. As a general recommendation, it's always a 
good idea to check the list of new packages and the list of packages to 
remove.


In another instance of the test computer I tried upgrading kde first, and:
apt install kde-full

Seems to do the right thing.

So then you have either to attempt to fix manually the issue, or with a dist- 
upgrade, but in both situations the result is the same : the situation becomes 
completely messy, with many broken packages you have to fix manually with dpkg 
commands. It is not impossible to run the upgrade this way, but anyway it is 
painful.


I don't see how kde-full could fix apt's upgrade behavior in jessie, I think 
that the behavior in stretch is better, but even so, nothing from the kde-full 
side. Please use apt-get upgrade to upgrade the upgradable parts in a jessie 
system.


Happy hacking,
--
"There are only two things wrong with C++: The initial concept and the
implementation."
-- Bertrand Meyer
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Processed: Re: Bug#854838: kde-full: When kde-full is installed, upgrading from jessie to stretch is extremely hard (if not impossible for beginners)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #854838 [kde-full] kde-full: When kde-full is installed, upgrading from 
jessie to stretch is extremely hard (if not impossible for beginners)
Severity set to 'normal' from 'critical'

-- 
854838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Add an affects

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> affects 854592 dokuwiki
Bug #854592 [php-phpseclib] dokuwiki: Unable to login, missing 
usr/share/php/Crypt/AES.php
Added indication that 854592 affects dokuwiki
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
854592: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: your mail

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 852960 + patch
Bug #852960 [src:rt-app] rt-app FTBFS on mips64el/ppc64el: error: conflicting 
types for 'timespec_to_nsec'
Added tag(s) patch.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
852960: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#854849: marked as done (sqlite3.go's bind func causes cgo pointer panic.)

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2017 11:03:32 +
with message-id 
and subject line Bug#854849: fixed in golang-github-mattn-go-sqlite3 
1.1.0~dfsg1-3
has caused the Debian Bug report #854849,
regarding sqlite3.go's bind func causes cgo pointer panic.
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
854849: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-jinzhu-gorm
Version: 0.0~git20151012.0.20e37a0-1
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org

Dear Maintainer,

golang-github-jinzhu-gorm fails to build from source in unstable/amd64:

  [..]

  dh build --buildsystem=golang --with=golang
 dh_testdir -O--buildsystem=golang
 dh_update_autotools_config -O--buildsystem=golang
 dh_auto_configure -O--buildsystem=golang
 dh_auto_build -O--buildsystem=golang
go install -v github.com/jinzhu/gorm
  github.com/lib/pq/hstore
  github.com/qor/inflection
  github.com/jinzhu/gorm
 dh_auto_test -O--buildsystem=golang
go test -v github.com/jinzhu/gorm
  testing sqlite3...
  === RUN   TestRegisterCallback
  --- PASS: TestRegisterCallback (0.00s)
  === RUN   TestRegisterCallbackWithOrder
  --- PASS: TestRegisterCallbackWithOrder (0.00s)
  === RUN   TestRegisterCallbackWithComplexOrder
  --- PASS: TestRegisterCallbackWithComplexOrder (0.00s)
  === RUN   TestReplaceCallback
  [info] replacing callback `create` from 
/home/lamby/temp/cdt.20160331130655.2UxfTVyVK1/golang-github-jinzhu-gorm-0.0~git20151012.0.20e37a0/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/callback_test.go:94
  --- PASS: TestReplaceCallback (0.00s)
  === RUN   TestRemoveCallback
  [info] removing callback `create` from 
/home/lamby/temp/cdt.20160331130655.2UxfTVyVK1/golang-github-jinzhu-gorm-0.0~git20151012.0.20e37a0/obj-x86_64-linux-gnu/src/github.com/jinzhu/gorm/callback_test.go:107
  --- PASS: TestRemoveCallback (0.00s)
  === RUN   TestCloneSearch
  --- PASS: TestCloneSearch (0.00s)
  === RUN   TestHasOneAndHasManyAssociation
  --- PASS: TestHasOneAndHasManyAssociation (0.12s)
  === RUN   TestRelated
  --- PASS: TestRelated (0.02s)
  === RUN   TestManyToMany
  --- PASS: TestManyToMany (0.47s)
  === RUN   TestForeignKey
  --- PASS: TestForeignKey (0.00s)
  === RUN   TestRunCallbacks
  --- PASS: TestRunCallbacks (0.06s)
  === RUN   TestCallbacksWithErrors
  --- PASS: TestCallbacksWithErrors (0.06s)
  === RUN   TestCreate
  --- PASS: TestCreate (0.04s)
  === RUN   TestCreateWithNoGORMPrimayKey
  --- PASS: TestCreateWithNoGORMPrimayKey (0.02s)
  === RUN   TestCreateWithNoStdPrimaryKeyAndDefaultValues
  --- PASS: TestCreateWithNoStdPrimaryKeyAndDefaultValues (0.04s)
  === RUN   TestAnonymousScanner
  --- PASS: TestAnonymousScanner (0.02s)
  === RUN   TestAnonymousField
  --- PASS: TestAnonymousField (0.02s)
  === RUN   TestSelectWithCreate
  --- PASS: TestSelectWithCreate (0.05s)
  === RUN   TestOmitWithCreate
  --- PASS: TestOmitWithCreate (0.04s)
  === RUN   TestCustomizeColumn
  --- PASS: TestCustomizeColumn (0.07s)
  === RUN   TestCustomColumnAndIgnoredFieldClash
  --- PASS: TestCustomColumnAndIgnoredFieldClash (0.02s)
  === RUN   TestDdlErrors
  testing sqlite3...
  --- PASS: TestDdlErrors (0.00s)
  === RUN   TestDelete
  --- PASS: TestDelete (0.06s)
  === RUN   TestInlineDelete
  --- PASS: TestInlineDelete (0.07s)
  === RUN   TestSoftDelete
  --- PASS: TestSoftDelete (0.07s)
  === RUN   TestSaveAndQueryEmbeddedStruct
  --- PASS: TestSaveAndQueryEmbeddedStruct (0.06s)
  === RUN   TestCalculateField
  --- PASS: TestCalculateField (0.00s)
  === RUN   TestJoinTable
  
  (no such table: person_addresses) 
  [2016-03-31 13:07:14]  
  --- PASS: TestJoinTable (0.14s)
  === RUN   TestStringPrimaryKey
  --- PASS: TestStringPrimaryKey (0.03s)
  === RUN   TestExceptionsWithInvalidSql
  
  (no such table: ) 
  [2016-03-31 13:07:14]  
  
  (no such column: aaa) 
  [2016-03-31 13:07:14]  
  --- PASS: TestExceptionsWithInvalidSql (0.00s)
  
  (no such column: sdsd.zaaa) 
  [2016-03-31 13:07:14]  
  === RUN   TestSetTable
  
  (no such table: invalid_table) 
  [2016-03-31 13:07:14]  
  
  (no such table: deleted_users) 
  [2016-03-31 13:07:14]  
  --- PASS: TestSetTable (0.20s)
  === RUN   

Processed: severity of 854355 is normal, tagging 854355

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> severity 854355 normal
Bug #854355 [kmail] /usr/bin/kmail: Unable to send emails - Could not compose 
message: Inappropriate ioctl for device
Severity set to 'normal' from 'grave'
> tags 854355 + unreproducible
Bug #854355 [kmail] /usr/bin/kmail: Unable to send emails - Could not compose 
message: Inappropriate ioctl for device
Added tag(s) unreproducible.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
854355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#854355: Acknowledgement (/usr/bin/kmail: Unable to send emails - Could not compose message: Inappropriate ioctl for device)

[Maximiliano Curia]

Control: tag -1 + moreinfo

¡Hola Dennis!

El 2017-02-06 a las 13:01 +0100, Dennis Schridde escribió:
The reason for this seems to be gnupg related: When I start KMail from a 
terminal and try to send a message, a text ssh-askpass dialogue is shown on 
the terminal. If I enter my gnupg key password there, the email is being send 
without any problems.



My assumption is now that ksshaskpass is somewhat broken.



ksshaskpass/testing,unstable,now 4:5.8.4-1 amd64 [installed,automatic]


The program launched by gnupg to ask the passphrase is pinentry (which is an 
alternative). What's your pinentry and pinentry-x11?


$ ls -l /etc/alternatives/pinentry*

Is the problem reproducible for you, if you set pinentry to pinentry-qt?

Happy hacking,
--
"It is practically impossible to teach good programming to students that have
had a prior exposure to BASIC: as potential programmers they are mentally
mutilated beyond hope of regeneration."
-- Edsger W. Dijkstra
Saludos /\/\ /\ >< `/


signature.asc
Description: PGP signature

Processed: Re: Bug#854355: Acknowledgement (/usr/bin/kmail: Unable to send emails - Could not compose message: Inappropriate ioctl for device)

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + moreinfo
Bug #854355 [kmail] /usr/bin/kmail: Unable to send emails - Could not compose 
message: Inappropriate ioctl for device
Added tag(s) moreinfo.

-- 
854355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#850149: shotwell: Freezes when trying to open an image in fullscreen mode

[Debian Bug Tracking System]

Processing control commands:

> severity 850149 grave
Bug #850149 [shotwell] shotwell: Freezes when trying to open an image in 
fullscreen mode
Severity set to 'grave' from 'normal'

-- 
850149: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850149
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#740998: Bug#854801: No network after netinst Stretch RC2

[Emilio Pozuelo Monfort]

On 10/02/17 17:17, Cyril Brulebois wrote:
> Paul Schlüter  (2017-02-10):
>> * The touchpad behaves strange: I can move the mouse pointer but cannot
>>   click. However, this may be a hardware problem.
> 
> We've had several such reports but bug triaging still needs to happen… :/

Are you doing tap-to-click, or actual clicks on physical buttons? If the former,
this may be related to #853869, which I intend to fix soon.

Cheers,
Emilio

Bug#852380: marked as done (ekeyd: Does not start after luasocket upgrade)

[Debian Bug Tracking System]

Your message dated Mon, 13 Feb 2017 09:48:29 +
with message-id 
and subject line Bug#852380: fixed in ekeyd 1.1.5-6.2
has caused the Debian Bug report #852380,
regarding ekeyd: Does not start after luasocket upgrade
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
852380: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852380
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ekeyd
Version: 1.1.5-6.1
Severity: grave
Tags: patch
Justification: renders package unusable

After the recent upgrade of the lua-socket package to version
3.0~rc1+git+ac3201d-2, ekeyd no longer starts if Unix domain sockets are
used (for either the control or EGD socket). Instead, it exits with this
error message:

Unable to run configuration file:
control.lua:755: control.lua:526: attempt to index global 'socket' (a nil value)

This is due to an incompatible change in the lua-socket API for Unix domain 
sockets.

I have attached a patch which allows ekeyd to work with both the old and
new versions of lua-socket, as well as an upcoming change that has not
yet been packaged in Debian. (Git commit 3a33c37b;
https://github.com/diegonehab/luasocket/commit/3a33c37b9ce852d0b3531e82c6ffdb47bb937f0a.)

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

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

Versions of packages ekeyd depends on:
ii  libc62.24-8
ii  liblua5.1-0  5.1.5-8.1+b2
ii  lua-socket   3.0~rc1+git+ac3201d-2
ii  lua5.1   5.1.5-8.1+b2

Versions of packages ekeyd recommends:
ii  udev  232-8

Versions of packages ekeyd suggests:
pn  munin-node  

-- Configuration Files:
/etc/entropykey/ekeyd.conf changed [not included]
/etc/entropykey/keyring [Errno 13] Permission denied: '/etc/entropykey/keyring'

-- no debconf information
From: Courtney Bane 
Date: Mon, 23 Jan 2017 20:30:59 -0600
Subject: Fix compatibility problems with Unix domain sockets in newer
 versions of luasocket.

---
 host/control.lua | 14 --
 host/ekeydctl.in |  7 ---
 2 files changed, 12 insertions(+), 9 deletions(-)

diff --git a/host/control.lua b/host/control.lua
index 7b9b1b8..22d700f 100644
--- a/host/control.lua
+++ b/host/control.lua
@@ -38,11 +38,11 @@ local PROTOCOL_VERSION = "1"
 local dos_callcount = 0
 
 -- Libraries we need
-require "socket"
+socket = require "socket"
 
 local have_unix_domain_sockets = false
 function tryload_unix()
-   require "socket.unix"
+   socket.unix = require "socket.unix"
have_unix_domain_sockets = true
 end
 
@@ -521,14 +521,15 @@ end
 
 if have_unix_domain_sockets then
function UnixControlSocket(sockname)
+  local sock = socket.unix.stream or socket.unix.tcp or socket.unix
   -- Add a UDS control socket to the set of control sockets available
   -- First, try and connect, so we can abort if it's present.
-  if socket.unix():connect(sockname) then
+  if sock():connect(sockname) then
 	 error("Control socket " .. sockname .. " already present. Is ekeyd already running?")
   end
   -- Okay, clean up (ignoring errors) and create a fresh socket
   unlink(sockname)
-  local u = socket.unix()
+  local u = sock()
   assert(u:bind(sockname))
   assert(u:listen())
   addctlsocket(u, "U:" .. sockname)
@@ -554,12 +555,13 @@ end _ "TCPControlSocket"
 if have_unix_domain_sockets then
function EGDUnixSocket(sockname, modestr, user, group)
   SetFoldedOutput()
-  if socket.unix():connect(sockname) then
+  local sock = socket.unix.stream or socket.unix.tcp or socket.unix
+  if sock():connect(sockname) then
 	 error("EGD socket " .. sockname .. " already present. Is ekeyd/EGD already running?")
   end
   -- Add a UDS control socket to the set of control sockets available
   unlink(sockname)
-  local u = socket.unix()
+  local u = sock()
   assert(u:bind(sockname))
   assert(u:listen())
   addctlsocket(u, "U:" .. sockname, false, egd_ctlread)
diff --git a/host/ekeydctl.in b/host/ekeydctl.in
index 9292ac6..802cf38 100755
--- a/host/ekeydctl.in
+++ b/host/ekeydctl.in
@@ -1,11 +1,11 @@
 #!/usr/bin/env lua@LUA_V@
 -- -*- Lua -*-
 
-require "socket"
+local socket = require "socket"
 
 -- Try to load the UNIX domain sockets support
 pcall(function()
-	 require 

Bug#740998: Bug#854801: No network after netinst Stretch RC2

[Bernhard Schmidt]

Hi,
> 
> I've cc'd quite a number of folks/lists to make sure the netcfg part is
> tackled sooner than later (plus a few others for information).
> 
> Paul Schlüter  (2017-02-10):
>> * Packages network-manager-gnome (recommended by task-xfce-desktop) and
>>   net-tools were not installed;
>>   the installed package rdnssd is in conflict to network-manager.
>>   (=> To setup a network connection I had to edit /etc/network/interfaces)
> 
> This seems due to the Conflicts added in rdnssd indeed, because of:
>   https://bugs.debian.org/740998
> 
> Unfortunately it doesn't seem like debian-boot@ people were available at
> the time to give some feedback…
> 
> I think we need to be a bit more careful in this particular section of
> src:netcfg's netcfg/autoconfig.c:
> | /* And now we cleanup from rdnssd */
> | if (ipv6) {
> | read_rdnssd_nameservers(interface);
> | if (nameserver_count(interface) > 0) {
> | di_exec_shell_log("apt-install rdnssd");
> | }
> | }
> 
> since that interferes with n-m's getting installed. Something we could do
> in netcfg would be:
> 
>  1. Stop installing rdnssd forcefully at this point, and only set a flag
> for later use.
>  2. In finish-install.d/55netcfg-copy-config, where the /e/n/i and other
> settings copy is performed, we could check that flag and n-m's
> status; if the flag is set and n-m wasn't installed, install rdnssd.
> This should let n-m get installed even if netcfg detected that
> rdnssd /could/ be needed, and should let rdnssd get installed when
> n-m wasn't.
> 
> Comments/better ideas?

I think that is a good idea, but reading the code I'm not quite sure
where the reported problem comes from.

netcfg installs rdnssd when an IPv6 router advertisement with RDNSS
(recursive DNS nameservers) is found during installation. Tasks
generally only recommend network-manager(-gnome) as far as I can tell,
so the conflict will keep rdnssd installed and network-manager uninstalled.

However the code in finish-install.d/55netcfg-copy-config only mangles
/e/n/i if network-manager is really there, so in this particular case
Paul should have ended up with a traditional /e/n/i and ifupdown.

@Paul: Can you share the installer log (/var/log/installer/syslog) and
the content of your /etc/network/interfaces after installation? I'll try
to get that information myself tonight, I don't have RDNSS here in the
office network unfortunately.

Bernhard



signature.asc
Description: OpenPGP digital signature

Processed: Re: dokuwiki: Unable to login, missing usr/share/php/Crypt/AES.php

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 php-phpseclib
Bug #854592 [dokuwiki] dokuwiki: Unable to login, missing 
usr/share/php/Crypt/AES.php
Bug reassigned from package 'dokuwiki' to 'php-phpseclib'.
No longer marked as found in versions dokuwiki/0.0.20160626.a-1.
Ignoring request to alter fixed versions of bug #854592 to the same values 
previously set
> tags -1 +patch
Bug #854592 [php-phpseclib] dokuwiki: Unable to login, missing 
usr/share/php/Crypt/AES.php
Added tag(s) patch.

-- 
854592: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854592
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#854592: dokuwiki: Unable to login, missing usr/share/php/Crypt/AES.php

[Hideki Yamane]

control: reassign -1 php-phpseclib
control: tags -1 +patch

Hi,

On Wed, 08 Feb 2017 14:51:56 +0100 Joost van den Berg  wrote:
> Package: dokuwiki

> [Wed Feb 08 14:15:06.653356 2017] [:error] [pid 8818] [client 127.0.0.1:44858]
> PHP Warning:  require(/usr/share/php/Crypt/AES.php):
> failed to open stream: No such file or directory in 
> /usr/share/dokuwiki/inc/load.php on line 109,
> referer: 
> http://localhost/dokuwiki/doku.php?id=start=login=dc1ed9d
> [Wed Feb 08 14:15:06.653406 2017] [:error] [pid 8818] [client 127.0.0.1:44858]
> PHP Fatal error:  require(): Failed opening required 
> '/usr/share/php/Crypt/AES.php'
> (include_path='.:/usr/share/php') in /usr/share/dokuwiki/inc/load.php on line 
> 109,
> referer: 
> http://localhost/dokuwiki/doku.php?id=start=login=dc1ed9d
>
> Here below I see dokuwiki depends on
> pn php-seclib 
> however the dependency seems to be satisfied by
> php-phpseclib 2.0.4-1 that was already installed on my system.

php-phpseclib "Provides: php-seclib", however, its path is different from
php-seclib - /usr/share/php/Crypt/ vs /usr/share/php/phpseclib/Crypt/ ,
see below.

(snip)
php-seclib: /usr/share/php/Crypt/AES.php
php-seclib: /usr/share/php/Crypt/Base.php
php-seclib: /usr/share/php/Crypt/Blowfish.php
php-seclib: /usr/share/php/Crypt/DES.php
php-seclib: /usr/share/php/Crypt/Hash.php
php-seclib: /usr/share/php/Crypt/RC2.php
php-seclib: /usr/share/php/Crypt/RC4.php
php-seclib: /usr/share/php/Crypt/RSA.php
php-seclib: /usr/share/php/Crypt/Random.php
php-seclib: /usr/share/php/Crypt/Rijndael.php
php-seclib: /usr/share/php/Crypt/TripleDES.php
php-seclib: /usr/share/php/Crypt/Twofish.php
(snip)

(snip)
php-phpseclib: /usr/share/php/phpseclib/Crypt/AES.php
php-phpseclib: /usr/share/php/phpseclib/Crypt/Base.php
php-phpseclib: /usr/share/php/phpseclib/Crypt/Blowfish.php
php-phpseclib: /usr/share/php/phpseclib/Crypt/DES.php
php-phpseclib: /usr/share/php/phpseclib/Crypt/Hash.php
php-phpseclib: /usr/share/php/phpseclib/Crypt/RC2.php
php-phpseclib: /usr/share/php/phpseclib/Crypt/RC4.php
php-phpseclib: /usr/share/php/phpseclib/Crypt/RSA.php
php-phpseclib: /usr/share/php/phpseclib/Crypt/Random.php
php-phpseclib: /usr/share/php/phpseclib/Crypt/Rijndael.php
php-phpseclib: /usr/share/php/phpseclib/Crypt/TripleDES.php
php-phpseclib: /usr/share/php/phpseclib/Crypt/Twofish.php
(snip)


I've created a patch to add symlink for it as below.
Could you check it, please?

lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/Crypt/AES.php -> phpseclib/Crypt/AES.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/Crypt/Base.php -> phpseclib/Crypt/Base.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/Crypt/Blowfish.php -> phpseclib/Crypt/Blowfish.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/Crypt/DES.php -> phpseclib/Crypt/DES.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/Crypt/Hash.php -> phpseclib/Crypt/Hash.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/Crypt/RC2.php -> phpseclib/Crypt/RC2.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/Crypt/RC4.php -> phpseclib/Crypt/RC4.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/Crypt/RSA.php -> phpseclib/Crypt/RSA.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/Crypt/Random.php -> phpseclib/Crypt/Random.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/Crypt/Rijndael.php -> phpseclib/Crypt/Rijndael.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/Crypt/TripleDES.php -> phpseclib/Crypt/TripleDES.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/Crypt/Twofish.php -> phpseclib/Crypt/Twofish.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/File/ANSI.php -> phpseclib/File/ANSI.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/File/ASN1/Element.php ->
phpseclib/File/ASN1/Element.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/File/ASN1.php -> phpseclib/File/ASN1.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/File/X509.php -> phpseclib/File/X509.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/Math/BigInteger.php -> phpseclib/Math/BigInteger.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/Net/SCP.php -> phpseclib/Net/SCP.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/Net/SFTP/Stream.php -> phpseclib/Net/SFTP/Stream.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/Net/SFTP.php -> phpseclib/Net/SFTP.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/Net/SSH1.php -> phpseclib/Net/SSH1.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/Net/SSH2.php -> phpseclib/Net/SSH2.php
lrwxrwxrwx root/root 0 2017-02-13 14:25
./usr/share/php/System/SSH/Agent/Identity.php ->
phpseclib/System/SSH/Agent/Identity.php
lrwxrwxrwx root/root  

Processed: tagging 854866

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 854866 + moreinfo
Bug #854866 [solaar] solaar: Solaar did not have permissions to open my receiver
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
854866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems