Bug#931852: [armel/marvell] cmdline mtd partition map without effect

2019-07-16 Thread Chris Laif
On Tue, Jul 16, 2019 at 1:22 AM Ben Hutchings  wrote:
> On Mon, 2019-07-15 at 09:31 +0200, Chris Laif wrote:
> > On Sat, Jul 13, 2019 at 11:37 PM Ben Hutchings  wrote:
> > > On Thu, 2019-07-11 at 15:11 +0200, Chris Laif wrote:
> > This seems to break backwards compatibility for a lot of devices
> > (Google shows lots of hits for "mtdparts=" and only a handful for
> > "cmdlinepart.mtdparts", so I think nobody is using the latter).
> >
> > I wonder what's the best way to have a both Stretch and Buster
> > compatible cmdline. A quick test shows that "cmdlinepart.mtdparts"
> > works with Stretch, too (even Stretch does not have a seperate
> > "cmdlinepart" module). Do you have any recommendations?
>
> I think that "cmdlinepart.mtdparts" will work whether or not the driver
> is actually a module.  But I accept it would be better if "mtdparts"
> also continued to work when the driver is a module.
>

Thanks. Do you know if the acceptance of 'mtdparts' with/without
prefix is specific to the Debian kernel or if it is a decision by the
upstream kernel devs? I remember that some months ago one of the beta
Buster kernels accepted the 'mtdparts' variable, I /think/ the
incompatible change has been introduced during finalisation of Buster.

Kernel docs 
(https://www.kernel.org/doc/html/v4.19/admin-guide/kernel-parameters.html)
refer to the 'mtdparts' variable (without prefix).

Chris



Bug#932164: ITP: r-cran-timereg -- GNU R flexible regression models for survival data

2019-07-16 Thread Andreas Tille
Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-timereg -- GNU R flexible regression models for survival 
data
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: r-cran-timereg
  Version : 1.9.3
  Upstream Author : Thomas Scheike with contributions from Torben Martinussen, 
Jeremy
* URL : https://cran.r-project.org/package=timereg
* License : GPL-2+
  Programming Lang: GNU R
  Description : GNU R flexible regression models for survival data
 Programs for Martinussen and Scheike (2006), `Dynamic Regression
 Models for Survival Data', Springer Verlag.  Plus more recent developments.
 Additive survival model, semiparametric proportional odds model, fast
 cumulative residuals, excess risk models and more. Flexible competing risks
 regression including GOF-tests. Two-stage frailty modelling. PLS for the
 additive risk model. Lasso in the 'ahaz' package.

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-timereg



Bug#932165: ITP: r-cran-mets -- GNU R analysis of multivariate event times

2019-07-16 Thread Andreas Tille
Package: wnpp
Severity: wishlist

Subject: ITP: r-cran-mets -- GNU R analysis of multivariate event times
Package: wnpp
Owner: Andreas Tille 
Severity: wishlist

* Package name: r-cran-mets
  Version : 1.2.5
  Upstream Author : Klaus K. Holst and Thomas Scheike
* URL : https://cran.r-project.org/package=mets
* License : GPL-2+
  Programming Lang: GNU R
  Description : GNU R analysis of multivariate event times
 Implementation of various statistical models for multivariate
 event history data . Including multivariate
 cumulative incidence models , and  bivariate random
 effects probit models (Liability models) .
 Also contains two-stage binomial modelling that can do pairwise odds-ratio
 dependence modelling based marginal logistic regression models. This is an
 alternative to the alternating logistic regression approach (ALR).

Remark: This package is maintained by Debian R Packages Maintainers at
   https://salsa.debian.org/r-pkg-team/r-cran-mets



Bug#932166: RFA: cairo-ocaml -- OCaml bindings for Cairo

2019-07-16 Thread Stéphane Glondu
Package: wnpp
Severity: normal

Hello,

Currently, cairo-ocaml has no human maintainers. It is maintained by the
Debian OCaml team because of the need of transition coordination, but
needs more love and a dedicated maintainer.

A potential maintainer should get familiar with [1], and in particular
with our policy and practices, and get subscribed to our mailing-list.

[1] http://wiki.debian.org/Teams/OCamlTaskForce


Cheers,

-- 
Stéphane



Bug#932167: mirror listing update for ftp.univ-pau.fr

2019-07-16 Thread Joris Caravati
Package: mirrors
Severity: minor
User: mirr...@packages.debian.org
Usertags: mirror-list

Submission-Type: update
Site: ftp.univ-pau.fr
Type: leaf
Archive-architecture: amd64 arm64 armhf i386
Archive-http: /debian/
Maintainer: Joris Caravati 
Country: FR France




Trace Url: http://ftp.univ-pau.fr/debian/project/trace/
Trace Url: http://ftp.univ-pau.fr/debian/project/trace/ftp-master.debian.org
Trace Url: http://ftp.univ-pau.fr/debian/project/trace/ftp.univ-pau.fr



Bug#932168: Correct verion of libc-dev not found on security.debian.org

2019-07-16 Thread David Hansmann
Package: linux-libc-dev
Version: latest

Hi all,

when running a docker build using

FROM tomcat:8.5-jre8
RUN apt-get update && apt-get -y install locales
RUN locale-gen de_DE.UTF-8
RUN dpkg-reconfigure locales
ENV LANG de_DE.UTF-8
ENV LANGUAGE de_DE:en
ENV LC_ALL de_DE.UTF-8
RUN apt-get -y install gcc g++ libc6-dev-i386 g++-multilib

the dependencies fail since the weekend. Reason:

Fetched 53.0 MB in 8s (6156 kB/s)
E: Failed to fetch 
http://security.debian.org/debian-security/pool/updates/main/l/linux/linux-libc-dev_4.9.168-1+deb9u2_amd64.deb
  404  Not Found
E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?
The command '/bin/sh -c apt-get -y install gcc g++ libc6-dev-i386 
g++-multilib' returned a non-zero code: 100

The issue is the deb9u2, which is missing (but present on mirrors) - only 
deb9u3 is there.

It would be nice if you could provide a workaround if this takes longer to fix.

Best regards and keep up the great work,

David



--
David Hansmann
Core Architect

Smartsteuer GmbH * Lister Meile 27 * 30161 Hannover
Fon +49 (0) 511 / 790 90 316

E-Mail david.hansm...@smartsteuer.de
Web www.smartsteuer.de
Facebook https://www.facebook.com/smartsteuer

Handelsregister HRB 200898 * Amtsgericht Hannover
Gesch?ftsf?hrer Dr. Carsten Thies, Bj?rn Waide


Bug#932169: dante-server: systemd fails to start danted service

2019-07-16 Thread Anatoly A. Kazantsev
Package: dante-server
Version: 1.4.2+dfsg-6
Severity: important

Dear Maintainer,

Systemd couldn't start danted service after I upgraded to buster from
stretch (which itself was upgraded from the previous release).

journalctl -xe showed following:

Jul 16 07:31:39 s0 systemd[1]: Starting SOCKS (v4 and v5) proxy daemon 
(danted)...
-- Subject: A start job for unit danted.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit danted.service has begun execution.
--
-- The job identifier is 601246.
Jul 16 07:31:39 s0 systemd[8289]: danted.service: Failed to set up mount 
namespacing: No such file or directory
Jul 16 07:31:39 s0 systemd[8289]: danted.service: Failed at step NAMESPACE 
spawning /bin/sh: No such file or directory
-- Subject: Process /bin/sh could not be executed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The process /bin/sh could not be executed and failed.
--
-- The error number returned by this process is ERRNO.
Jul 16 07:31:39 s0 systemd[1]: danted.service: Control process exited, 
code=exited, status=226/NAMESPACE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStartPre= process belonging to unit danted.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 226.
Jul 16 07:31:39 s0 systemd[1]: danted.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit danted.service has entered the 'failed' state with result 
'exit-code'.
Jul 16 07:31:39 s0 systemd[1]: Failed to start SOCKS (v4 and v5) proxy daemon 
(danted).
-- Subject: A start job for unit danted.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit danted.service has finished with a failure.
--
-- The job identifier is 601246 and the job result is failed.

After some research I found out that the problem is in following line
of /lib/systemd/system/danted.service file:

ReadOnlyDirectories=/bin /etc /lib /lib64 /sbin /usr /var

Because my system doesn't have /lib64 directory. Changing /lib64 to -/lib64
in the service lets systemd start the deamon.

But I'm not sure if /lib64 is optional directory on Debian in general
or on some architectures or it should have been created during previous
release upgrades or it's just me :-)

-- System Information:
Debian Release: 10.0
  APT prefers stable
  APT policy: (990, 'stable'), (100, 'testing')
Architecture: armhf (armv7l)
Foreign Architectures: i386

Kernel: Linux 4.9.182-mainline-rev1 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set$
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages dante-server depends on:
ii  init-system-helpers  1.56+nmu1
ii  libc62.28-10
ii  libpam0g 1.3.1-5
ii  libwrap0 7.6.q-28
ii  lsb-base 10.2019051400

dante-server recommends no packages.

dante-server suggests no packages.

-- Configuration Files:
/etc/danted.conf changed [not included]

-- no debconf information



Bug#928499: mirror listing update for mirror.schoemaker.systems

2019-07-16 Thread Julien Cristau
Hi,

Thanks for mirroring Debian!

On Mon, May  6, 2019 at 07:56:36 +, Quentin Schoemaker wrote:

> Trace Url: 
> http://mirror.schoemaker.systems/debian/project/trace/mirror.schoemaker.systems
> 
I notice you're using ftp.nl.debian.org as upstream.  The only service
we guarantee on ftp.CC.debian.org is http on /debian/, not rsync; you
may want to update your config to use the host currently serving as
ftp.nl.debian.org (debian.snt.utwente.nl).

Cheers,
Julien



Bug#932170: bird2: FTBFS (dh_installinit: --name=bird option specified, but init script not found)

2019-07-16 Thread Santiago Vila
Package: src:bird2
Version: 2.0.4-1
Severity: serious
Tags: ftbfs

Dear maintainer:

I tried to build this package in sid but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -g -O2 -fno-strict-aliasing 
-fno-strict-overflow -fPIC" LDFLAGS="-Wl,-z,relro -Wl,-z,now -g -O2 
-fno-strict-aliasing -fno-strict-overflow -fPIC -Wl,-z,defs -Wl,--as-needed" 
dh_auto_configure -- --prefix=/usr --sysconfdir=/etc/bird 
--mandir=\${prefix}/share/man --infodir=\${prefix}/share/info 
--localstatedir=/var --runstatedir=/run/bird --docdir=\${prefix}/share/bird2 
--enable-client --with-protocols=all
./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking 
--prefix=/usr --sysconfdir=/etc/bird --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --localstatedir=/var --runstatedir=/run/bird 
--docdir=\${prefix}/share/bird2 --enable-client --with-protocols=all
configure: WARNING: unrecognized options: --disable-silent-rules, 
--disable-maintainer-mode, --disable-dependency-tracking
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no

[... snipped ...]

[61] [62] [63] [64] [65] [66] [67] [68] [69] [70]
Chapter 7.
[71] (obj/doc//bird.aux) )
(see the transcript file for additional information)
Output written on obj/doc//bird.pdf (71 pages, 393856 bytes).
Transcript written on obj/doc//bird.log.
rm obj/doc/bird.tex obj/doc/prog.tex obj/doc/bird.sgml
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   dh_auto_test -i
make -j1 test VERBOSE=1
make[1]: Entering directory '/<>'
/bin/sh: 1: git: not found
rm -f obj/filter/tree_test.ok obj/filter/filter_test.ok obj/filter/trie_test.ok 
obj/lib/heap_test.ok obj/lib/buffer_test.ok obj/lib/event_test.ok 
obj/lib/flowspec_test.ok obj/lib/bitops_test.ok obj/lib/patmatch_test.ok 
obj/lib/fletcher16_test.ok obj/lib/slist_test.ok obj/lib/checksum_test.ok 
obj/lib/lists_test.ok obj/lib/mac_test.ok obj/lib/ip_test.ok 
obj/lib/hash_test.ok obj/lib/printf_test.ok obj/nest/a-set_test.ok 
obj/nest/a-path_test.ok
gcc -Iobj -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -g -O2 -fno-strict-aliasing -fno-strict-overflow -fPIC 
-pthread -MMD -MP -o obj/filter/tree_test.o -c filter/tree_test.c
gcc -Iobj -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -g -O2 -fno-strict-aliasing -fno-strict-overflow -fPIC 
-pthread -MMD -MP -o obj/test/birdtest.o -c test/birdtest.c
gcc -Iobj -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -g -O2 -fno-strict-aliasing -fno-strict-overflow -fPIC 
-pthread -MMD -MP -o obj/test/bt-utils.o -c test/bt-utils.c
gcc -Wl,-z,relro -Wl,-z,now -g -O2 -fno-strict-aliasing -fno-strict-overflow 
-fPIC -Wl,-z,defs -Wl,--as-needed -pthread -o obj/filter/tree_test 
obj/filter/tree_test.o obj/conf/cf-parse.tab.o obj/conf/cf-lex.o 
obj/conf/conf.o obj/filter/filter.o obj/filter/f-util.o obj/filter/tree.o 
obj/filter/trie.o obj/lib/bitops.o obj/lib/checksum.o obj/lib/event.o 
obj/lib/flowspec.o obj/lib/idm.o obj/lib/ip.o obj/lib/lists.o obj/lib/mac.o 
obj/lib/md5.o obj/lib/mempool.o obj/lib/net.o obj/lib/patmatch.o 
obj/lib/printf.o obj/lib/resource.o obj/lib/sha1.o obj/lib/sha256.o 
obj/lib/sha512.o obj/lib/slab.o obj/lib/slists.o obj/lib/tbf.o obj/lib/timer.o 
obj/lib/xmalloc.o obj/nest/a-path.o obj/nest/a-set.o obj/nest/cli.o 
obj/nest/cmds.o obj/nest/iface.o obj/nest/locks.o obj/nest/neighbor.o 
obj/nest/password.o obj/nest/proto.o obj/nest/rt-attr.o obj/nest/rt-dev.o 
obj/nest/rt-fib.o obj/nest/rt-show.o obj/nest/rt-table.o obj/test/birdtest.o 
obj/test/bt-utils.o obj/proto/bfd/bfd.o obj/proto/bfd/io.o obj/proto
 /bfd/packets.o obj/proto/babel/babel.o obj/proto/babel/packets.o 
obj/proto/bgp/attrs.o obj/proto/bgp/bgp.o obj/proto/bgp/packets.o 
obj/proto/mrt/mrt.o obj/proto/ospf/dbdes.o obj/proto/ospf/hello.o 
obj/proto/ospf/iface.o obj/proto/ospf/lsack.o obj/proto/ospf/lsalib.o 
obj/proto/ospf/lsreq.o obj/proto/ospf/lsupd.o obj/proto/ospf/neighbor.o 
obj/proto/ospf/ospf.o obj/proto/ospf/packet.o obj/proto/ospf/rt.o 
obj/proto/ospf/topology.o obj/proto/perf/perf.o obj/proto/pipe/p

Bug#932171: nemo fails to mount encrypted block device (luks)

2019-07-16 Thread Florian Lohoff
Package: nemo
Version: 3.8.5-1+b1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Dear Maintainer,

i connected a USB drive which contains a Luks based encrypted
block device. Prior to updateing to Buster i got a popup, entered
the passphrase and everything was fine.

Now i enter the passphrase and i get an Error popup

 Unable to mount 4.0 TB Encrypted

 Error unlocking /dev/sdb2: The function 'bd_crypto_luks_open_blob'
 called but not implemented!'


cryptsetup is installed (I am running cryptoroot aswell)

flo@p4:~$ dpkg -l | grep cryptsetup
ii  cryptsetup  2:2.1.0-5   all  transitional dummy 
package for cryptsetup-{run,initramfs}
ii  cryptsetup-bin  2:2.1.0-5   amd64disk encryption 
support - command line tools
ii  cryptsetup-initramfs2:2.1.0-5   all  disk encryption 
support - initramfs integration
ii  cryptsetup-run  2:2.1.0-5   amd64disk encryption 
support - startup scripts
ii  libcryptsetup12:amd64   2:2.1.0-5   amd64disk encryption 
support - shared library
ii  libcryptsetup4:amd642:1.7.3-4   amd64disk encryption 
support - shared library

Flo

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages nemo depends on:
ii  cinnamon-desktop-data  3.8.1-2
ii  desktop-file-utils 0.23-4
ii  gsettings-desktop-schemas  3.28.1-1
ii  gvfs   1.38.1-5
ii  libatk1.0-02.30.0-2
ii  libc6  2.28-10
ii  libcairo-gobject2  1.16.0-4
ii  libcairo2  1.16.0-4
ii  libcinnamon-desktop4   3.8.1-2
ii  libexempi8 2.5.0-2
ii  libexif12  0.6.21-5.1
ii  libgail-3-03.24.5-1
ii  libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii  libglib2.0-0   2.58.3-2
ii  libglib2.0-data2.58.3-2
ii  libgtk-3-0 3.24.5-1
ii  libnemo-extension1 3.8.5-1+b1
ii  libnotify4 0.7.7-4
ii  libpango-1.0-0 1.42.4-6
ii  libpangocairo-1.0-01.42.4-6
ii  libselinux12.8-1+b1
ii  libx11-6   2:1.6.7-1
ii  libxapp1   1.2.2-1
ii  libxml22.9.4+dfsg1-7+b3
ii  nemo-data  3.8.5-1
ii  shared-mime-info   1.10-1

Versions of packages nemo recommends:
ii  cinnamon-l10n3.8.2-1
ii  gvfs-backends1.38.1-5
ii  gvfs-fuse1.38.1-5
ii  librsvg2-common  2.44.10-2.1
ii  nemo-fileroller  3.8.0-2

Versions of packages nemo suggests:
ii  eog  3.28.4-2+b1
ii  evince [pdf-viewer]  3.30.2-3
ii  gv [pdf-viewer]  1:3.7.4-2
ii  totem3.30.0-4
ii  vlc [mp3-decoder]3.0.7-1
ii  xdg-user-dirs0.17-2

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEdb9o7oebX2papQ/KkN1BIMsJ8i8FAl0th9wACgkQkN1BIMsJ
8i9+Ug/+IwSYVrmtEPdwTBBG/seRuR8wjxu2+BBlHVnYd0/60VfEGaN6cYnEn6Xy
/vztzJDc9LIXTHeV49uFw1tqrOXuqwLTCZEoH4nTlD4jgpkzns1nv6eLBVjgIxO0
AUh8vQiOgXG9oGVWd9HV47iOpIr2ios/DO1qKLb+3VBWwfh27rBrp4XxTSw4NHHM
9/6AYcUoyryDUXaBwrYN17G2UJNTboNvzTK9AU74VZoPF0RzQ0Ce6p7Oe+z3DAC3
GH6i4ioISUAs/bS1c7ge+XiTf7jQzHkrKAMCIBFTDT5UqJRkOgKmMqPYkJikgXOH
XlqJBysvZlB/LW3zqspQLc0kihnfJmd17fxe57SFrXNf5hSV82U9EWHdDj3WJIVd
cq/gd6+FlegSUVGzDAVl9gZhPgdcG8AkY91Bixug6bOMQD08l+5B2q3MxUPA6LpH
FDDLo7IBtN4MVkjzF+bKz7+208rVJ88da0Vwcubi9o+rTh/4mPZU9C+Dmo+Nmb/P
f2cFYlEjZq9B01b0C5uHXz13VteWSh17BGGfxKlbGmYoJ1UX8cocWSdMC0kiK6hE
TytRt95FSbwgQVY375yL6vH3KLthI6K/kvxcskI7Jag+DNYui+gMHlEz9jDxcqcI
9WGkTE7rPYdnmu3hNuS5UMqqwudeha5U23Pv1CtREBcBCrs9e7k=
=crjM
-END PGP SIGNATURE-



Bug#932172: dh-cargo: please refresh json timestamps

2019-07-16 Thread Gianfranco Costamagna
Package: dh-cargo
Version: 18
Severity: serious
Tags: patch

https://patches.ubuntu.com/d/dh-cargo/dh-cargo_18ubuntu1.patch

Because of a Debian dak bug, no files with timestamp around 1970 was
rejected by it, so as soon as the dak patch is merged, every rust
package will fail to upload.
e.g.
ls -l /usr/share/cargo/registry/which-2.0.1/.cargo_vcs_info.json
-rw-r--r-- 1 root root 74 Jan  1  1970 
/usr/share/cargo/registry/which-2.0.1/.cargo_vcs_info.json

and so on for every file that apt-file gives you

This is what might happen in dak once the bug is fixed:
DEBUG Considering changefile 
32677/ubuntu/rust-which_2.0.1-1ubuntu1_s390x.changes
DEBUG Finding fresh policy
INFO Processing upload rust-which_2.0.1-1ubuntu1_s390x.changes
INFO Upload was rejected:
INFOlibrust-which-dev_2.0.1-1ubuntu1_s390x.deb: has 1 file(s) with a time 
stamp too far in the past (e.g. 
usr/share/cargo/registry/which-2.0.1/.cargo_vcs_info.json [Thu Jan  1 00:00:00 
1970]).
INFO Committing the transaction and any mails associated with this upload.

(this happens in Ubuntu)

dak patch: https://deb.li/Ynw1

Please accept the trivial patch ASAP

@@ -175,6 +175,7 @@ sub install {

 sub clean {
 my $this=shift;
+doit("touch", "--no-create", ".cargo_vcs_info.json");
 doit("/usr/share/cargo/bin/cargo", "clean", @_);
 doit("rm", "-rf", $this->get_sourcepath(".cargo-checksum.json"));
 doit("rm", "-rf", "debian/cargo_registry");

+dh-cargo (16ubuntu1) disco; urgency=medium
+
+  * Touch .cargo_vcs_info.json to update timestamp, as otherwise the file
+has unix creation time of 0 which is rejected by the archive in the
+.debs.
+
+ -- Dimitri John Ledkov   Tue, 22 Jan 2019 17:50:10 +



Bug#930391: frei0r-plugins-dev: Missing header files in /usr/include directory

2019-07-16 Thread Debian/GNU
hi,

On 11.06.19 21:57, Laurent BRULET wrote:
> The unique present header file is frei0r.h which allows to build C plugins
> only,
> and with limited functionality.

i fail to see how the latter can be true.
frei0r is a C-only API, the frei0r.hpp header is only a convenience wrapper.
so it doesn't have any extra "functionality" (but of course, it provides
extra convenience ;-))

given that the frei0r README.md uses the C++-header in its inline
example, i guess it's appropriate to include this header.

> Note : The problem is also present in upstream distribution.

would you mind reporting the issue yourself? ideally with a PR, so the
kudos are appropriate... (if not, i can of course do it for you).

   https://github.com/dyne/frei0r

zhmds
IOhannes



Bug#932171: Acknowledgement (nemo fails to mount encrypted block device (luks))

2019-07-16 Thread Florian Lohoff
On Tue, Jul 16, 2019 at 08:27:05AM +, Debian Bug Tracking System wrote:
> If you wish to submit further information on this problem, please
> send it to 932...@bugs.debian.org.

Bug has already be seen in 18.04

https://github.com/pop-os/pop/issues/163

The solution (which works) is to install 

apt install libblockdev-crypto2
systemctl restart udisks2.service

As this worked on stretch and didnt after an upgrade this is 
a regression. I guess its not really nemos reponsibility to have
a dependency on libblockdev-crypto2 but rather udisks2 which 
currently only Recommends libblockdev-crypto2.

But the error message is so misleading that the normal user would
not be able for fix this.

Flo
-- 
Florian Lohoff f...@zz.de
UTF-8 Test: The 🐈 ran after a 🐁, but the 🐁 ran away


signature.asc
Description: PGP signature


Bug#931843: please document csp header requirements

2019-07-16 Thread Katharina Drexel
Complementation: I found a way to configure the apache csp headers for
netdata.
Please add the configuration snippet to your documentation:

Header always set Content-Security-Policy "default-src 'unsafe-inline'
http://localhost:1 https: 'self' 'unsafe-eval'; script-src
'unsafe-inline' https: 'self' 'unsafe-eval'; style-src https: 'self'
'unsafe-inline'"

Thanks
Katharina



Bug#932170: bird2: FTBFS (dh_installinit: --name=bird option specified, but init script not found)

2019-07-16 Thread Santiago Vila
reassign 932170 debhelper
forcemerge 932073 932170
affects 932170 src:bird2
thanks

> If this is really a bug in one of the build-depends, please use reassign and 
> affects,
> so that this is still visible in the BTS web page for this package.

I think that's actually the case.

Thanks.



Bug#932173: release-notes: grep should be egrep in section 4.6.1 for buster

2019-07-16 Thread Stefan Kangas
Package: release-notes
Severity: minor

In Section 4.6.1 of the Release Notes for buster, this command is suggested:

dpkg -l "linux-image*" | grep ^ii | grep -i meta

I believe this should be:

dpkg -l "linux-image*" | egrep ^ii | grep -i meta

Best regards,
Stefan Kangas



Bug#932174: xfce4-settings: Should depend on GTK3 variant of garcon

2019-07-16 Thread Simon Frei
Package: xfce4-settings
Version: 4.13.5-1
Severity: normal

This is about the packages in experimental, i.e. 4.13.
I noticed that both libxfce4ui-1-0 and -2-0 are installed on my system and 
checking showed it's due to xfce4-settings depending on libgarcon-1-0. I assume 
it should depend on libgarcon-gtk3-1-0 (like e.g. xfce4-panel does).

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

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

Versions of packages xfce4-settings depends on:
ii  libc62.28-10
ii  libcairo21.16.0-4
ii  libexo-2-0   0.12.5-1
ii  libfontconfig1   2.13.1-2
ii  libgarcon-1-00.6.2-1
ii  libgarcon-common 0.6.2-1
ii  libgdk-pixbuf2.0-0   2.38.1+dfsg-1
ii  libglib2.0-0 2.58.3-2
ii  libgtk-3-0   3.24.5-1
ii  libnotify4   0.7.7-4
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libupower-glib3  0.99.10-1
ii  libx11-6 2:1.6.7-1
ii  libxcursor1  1:1.1.15-2
ii  libxfce4ui-2-0   4.13.4-2
ii  libxfce4util74.13.3-1
ii  libxfconf-0-34.13.4-1
ii  libxi6   2:1.7.9-1
ii  libxklavier165.4-4
ii  libxrandr2   2:1.5.1-1
ii  xfconf   4.12.1-1

Versions of packages xfce4-settings recommends:
ii  x11-utils  7.7+4

xfce4-settings suggests no packages.

-- no debconf information



Bug#914783: fixed in znc 1.7.4-2

2019-07-16 Thread Gianfranco Costamagna
control: reopen -1
control: notfixed -1
control: severity -1 serious
control: tags -1 patch
control: affects -1 znc-backlog

>* Switch to the cmake build system.
>  Closes: #914783

thanks for doing it, but due to a missing runtime dependency on cmake, now 
reverse dependencies are FTBFS because of missing cmake


The attached patch should fix the issue.

thanks for considering it

Gianfranco

+znc (1.7.4-2.11) unstable; urgency=medium
+
+  * Add cmake dependency also as runtime dependency for reverse-dependencies 
(Closes: #914783)
+
+ -- Gianfranco Costamagna   Tue, 16 Jul 2019 
11:30:29 +0200
+
 znc (1.7.4-2) unstable; urgency=medium
 
   * Switch to the cmake build system.
diff -Nru znc-1.7.4/debian/control znc-1.7.4/debian/control
--- znc-1.7.4/debian/control2019-07-11 12:03:16.0 +
+++ znc-1.7.4/debian/control2019-07-16 09:30:28.0 +
@@ -49,6 +49,7 @@
 Architecture: any
 Depends: ${misc:Depends},
  ${python3:Depends},
+ cmake,
  znc (>= ${binary:Version}),
  libicu-dev,
  libssl-dev,



Bug#931135: German translation made me laugh during a meeting

2019-07-16 Thread Guillem Jover
Hi!

On Wed, 2019-06-26 at 21:06:19 +0200, Stefan Potyra wrote:
> Package: dpkg-dev
> Version: 1.19.6
> Severity: minor
> Tags: l10n

> the following translation in the "FEATURE AREAS" -> "qa" might need some
> improvement:
> 
> LANG=C man dpkg-buildflags
> ___snip___
>canary This  setting  (disabled  by  default) adds dummy canary
>options to the build flags, so that the build logs can be checked
>for how the build flags propagate and to allow finding any omission
>of normal build flag settings.  The only currently supported
>flags are CPPFLAGS, CFLAGS, OBJCFLAGS, CXXFLAGS and OBJCXXFLAGS with
>flags set to -D__DEB_CANARY_flag_random-id__, and LDFLAGS set
>to -Wl,-z,deb-canary-random-id.
> __snip__
> 
> LANG=de_DE.UTF-8 man dpkg-buildflags
> __snip__
>   canary Diese  Einstellung  (standardmäßig  deaktiviert)  fügt 
>   Pseudo-Kanarienvögel-Optionen  zu  den  Bauschaltern  hinzu, 
>   so  dass die Bauprotokolle überprüft werden können, wie die
>   Bauschalter sich fortpflanzen. Dies erlaubt, Auslassungen in den
>   normalen Bauschaltereinstellungen zu finden. Derzeit werden nur
>   die Schalter CPPFLAGS, CFLAGS,  OBJCFLAGS,  CXXFLAGS  und 
>   OBJCXXFLAGS  unterstützt,  wobei  die  Schalter  auf
>   -D__DEB_CANARY_Schalter_Zufallskennung__  gesetzt  werden,
>   und  LDFLAGS,  das  auf -Wl,-z,deb-canary-Zufallskennung gesetzt wird.
> __snip__
> 
> Not too sure, if we should fix this or just keep it as an easter egg :).
> 
> From https://www.oocities.org/spunk/birds.htm#canary:

Helge, could you handle this, please? :)

Thanks,
Guillem



Bug#932175: stretch-pu: package openssh/1:7.4p1-10+deb9u7

2019-07-16 Thread Moritz Muehlenhoff
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu

This update for OpenSSH fixes a dead lock in AuthorizedKeysCommand (#905226).

The fixed package is running fine on a formerly affected Stretch system
(https://phabricator.wikimedia.org)

(I'm not the maintainer, but acked by Colin in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905226#27)

Debdiff below.

Cheers,
Moritz

diff -Nru openssh-7.4p1/debian/changelog openssh-7.4p1/debian/changelog
--- openssh-7.4p1/debian/changelog  2019-03-01 17:19:28.0 +0100
+++ openssh-7.4p1/debian/changelog  2019-07-15 15:32:09.0 +0200
@@ -1,3 +1,11 @@
+openssh (1:7.4p1-10+deb9u7) stretch; urgency=medium
+
+  * Fix deadlock when the keys/principals command produces a lot of
+output and a key is matched early (upstream commit
+ddd3d34e5c7979ca6f4a3a98a7d219a4ed3d98c2). (Closes: #905226)
+
+ -- Moritz Mühlenhoff   Mon, 15 Jul 2019 15:32:09 +0200
+
 openssh (1:7.4p1-10+deb9u6) stretch-security; urgency=high
 
   * Non-maintainer upload by the Security Team.
diff -Nru 
openssh-7.4p1/debian/patches/fix-deadlock-in-keys-principals-command.patch 
openssh-7.4p1/debian/patches/fix-deadlock-in-keys-principals-command.patch
--- openssh-7.4p1/debian/patches/fix-deadlock-in-keys-principals-command.patch  
1970-01-01 01:00:00.0 +0100
+++ openssh-7.4p1/debian/patches/fix-deadlock-in-keys-principals-command.patch  
2019-07-15 15:31:41.0 +0200
@@ -0,0 +1,37 @@
+From ddd3d34e5c7979ca6f4a3a98a7d219a4ed3d98c2 Mon Sep 17 00:00:00 2001
+From: "d...@openbsd.org" 
+Date: Fri, 30 Dec 2016 22:08:02 +
+Subject: [PATCH] upstream commit
+
+fix deadlock when keys/principals command produces a lot of
+output and a key is matched early; bz#2655, patch from jboning AT gmail.com
+
+Upstream-ID: e19456429bf99087ea994432c16d00a642060afe
+---
+ auth2-pubkey.c | 8 +++-
+ 1 file changed, 7 insertions(+), 1 deletion(-)
+
+diff --git a/auth2-pubkey.c b/auth2-pubkey.c
+index 20f3309e1..70c021589 100644
+--- a/auth2-pubkey.c
 b/auth2-pubkey.c
+@@ -727,6 +727,9 @@ match_principals_command(struct passwd *user_pw, const 
struct sshkey *key)
+ 
+   ok = process_principals(f, NULL, pw, cert);
+ 
++  fclose(f);
++  f = NULL;
++
+   if (exited_cleanly(pid, "AuthorizedPrincipalsCommand", command) != 0)
+   goto out;
+ 
+@@ -1050,6 +1053,9 @@ user_key_command_allowed2(struct passwd *user_pw, Key 
*key)
+ 
+   ok = check_authkeys_file(f, options.authorized_keys_command, key, pw);
+ 
++  fclose(f);
++  f = NULL;
++
+   if (exited_cleanly(pid, "AuthorizedKeysCommand", command) != 0)
+   goto out;
+ 
diff -Nru openssh-7.4p1/debian/patches/series 
openssh-7.4p1/debian/patches/series
--- openssh-7.4p1/debian/patches/series 2019-03-01 17:19:28.0 +0100
+++ openssh-7.4p1/debian/patches/series 2019-07-15 15:31:41.0 +0200
@@ -44,3 +44,4 @@
 have-progressmeter-force-update-at-beginning-and-end-transfer.patch
 check-filenames-in-scp-client.patch
 scp-handle-braces.patch
+fix-deadlock-in-keys-principals-command.patch


Bug#932176: RM: libcommons-launcher-java -- ROM; No longer used, dead upstream

2019-07-16 Thread Emmanuel Bourg
Package: ftp.debian.org
Severity: normal

Hi,

Please remove the libcommons-launcher-java package. It's no longer used
in Debian and has been abandonned upstream for 10+ years.

Thank you,

Emmanuel Boureg



Bug#932177: Please include apparmor profile directly in the package

2019-07-16 Thread Laurent Bigonville
Package: apt-cacher-ng
Version: 3.2-2
Severity: wishlist

Hi,

Currectly, the apparmor-profiles-extra package includes a profile for
apt-cacher-ng (/etc/apparmor.d/usr.sbin.apt-cacher-ng)

IMVHO, it would be better if it was included (and maintained) directly
inside the apt-cacher-ng.

Could you please see at moving the profile in this package?

Kind regards,

Laurent Bigonville

-- Package-specific info:

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

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

Versions of packages apt-cacher-ng depends on:
ii  adduser3.118
ii  debconf [debconf-2.0]  1.5.72
ii  dpkg   1.19.7
ii  libbz2-1.0 1.0.6-9.2
ii  libc6  2.28-10
ii  libgcc11:9.1.0-8
ii  liblzma5   5.2.4-1
ii  libssl1.1  1.1.1c-1
ii  libstdc++6 9.1.0-8
ii  libsystemd0241-6+b1
ii  libwrap0   7.6.q-28
ii  lsb-base   10.2019051400
ii  zlib1g 1:1.2.11.dfsg-1

apt-cacher-ng recommends no packages.

Versions of packages apt-cacher-ng suggests:
ii  avahi-daemon  0.7-4+b1
pn  doc-base  
ii  libfuse2  2.9.9-1

-- Configuration Files:
/etc/apt-cacher-ng/security.conf [Errno 13] Permission non accordée: 
'/etc/apt-cacher-ng/security.conf'

-- debconf information excluded


Bug#931901: Ping to Ben Hutchings, identifying possible source of problem

2019-07-16 Thread Phil Reynolds
On Tue, 16 Jul 2019 00:15:44 +0100
Ben Hutchings  wrote:

> I suspect that this bug is a duplicate of bug #928510, for which the
> fix missed the buster release (but we can fix it in a point release). 
> If you run "update-initramfs -u" and reboot, does that fix the
> problem?

Ah, that does indeed resolve the matter.

This was a strange one, to my eyes... but now I know what was really
going on. I now have X and the 4.19 kernel at the same time.

Many thanks for your efforts - hopefully I won't need to install on any
similar machines before this is fixed properly but I will treat this as
a "release note" if I do.

-- 
Phil Reynolds
mail: phil-deb2...@tinsleyviaduct.com



Bug#931852: [armel/marvell] cmdline mtd partition map without effect

2019-07-16 Thread Ben Hutchings
On Tue, 2019-07-16 at 09:02 +0200, Chris Laif wrote:
> On Tue, Jul 16, 2019 at 1:22 AM Ben Hutchings  wrote:
> > On Mon, 2019-07-15 at 09:31 +0200, Chris Laif wrote:
> > > On Sat, Jul 13, 2019 at 11:37 PM Ben Hutchings  
> > > wrote:
> > > > On Thu, 2019-07-11 at 15:11 +0200, Chris Laif wrote:
> > > This seems to break backwards compatibility for a lot of devices
> > > (Google shows lots of hits for "mtdparts=" and only a handful for
> > > "cmdlinepart.mtdparts", so I think nobody is using the latter).
> > > 
> > > I wonder what's the best way to have a both Stretch and Buster
> > > compatible cmdline. A quick test shows that "cmdlinepart.mtdparts"
> > > works with Stretch, too (even Stretch does not have a seperate
> > > "cmdlinepart" module). Do you have any recommendations?
> > 
> > I think that "cmdlinepart.mtdparts" will work whether or not the driver
> > is actually a module.  But I accept it would be better if "mtdparts"
> > also continued to work when the driver is a module.
> > 
> 
> Thanks. Do you know if the acceptance of 'mtdparts' with/without
> prefix is specific to the Debian kernel or if it is a decision by the
> upstream kernel devs? I remember that some months ago one of the beta
> Buster kernels accepted the 'mtdparts' variable, I /think/ the
> incompatible change has been introduced during finalisation of Buster.
> 
> Kernel docs 
> (https://www.kernel.org/doc/html/v4.19/admin-guide/kernel-parameters.html)
> refer to the 'mtdparts' variable (without prefix).

The difference in behaviour between the built-in and modular builds of
the driver, is not specific to Debian.

The change to building this driver as a module was our decision,
however.  That change was made in version 4.16-1~exp1, over a year ago.

Ben.

-- 
Ben Hutchings
If God had intended Man to program,
we'd have been born with serial I/O ports.



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


Bug#932178: RM: libcommons-modeler-java -- ROM; No longer used, dead upstream

2019-07-16 Thread Emmanuel Bourg
Package: ftp.debian.org
Severity: normal

Hi,

Please remove the libcommons-modeler-java package. It's no longer used
in Debian and has been abandonned upstream for 10+ years.

Thank you,

Emmanuel Bourg



Bug#895534: closed by Debian FTP Masters

2019-07-16 Thread Luca Falavigna
Hi Simon,

Il giorno gio 11 lug 2019 alle ore 23:24 Simon McVittie
 ha scritto:
> I asked for multiple binary packages to be overridden, including but not
> limited to libgtkgl2.0-1:

When fixing overrides, dak can cope with just one override at a time
and then it sends bug mail to -close with just one package listed.
If you look at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895534,
you will see subsequent messages were sent to -close, but probably
weren't mailed because bug was already closed once.

> > libgtkgl2.0-1:oldlibs/optional
> > libgtkgl2.0-dev:oldlibs/optional
> > libgtkglext1-dev:oldlibs/optional
> > libgtkglext1-doc:oldlibs/optional
> > libgtkglext1:oldlibs/optional
> > libgtkglextmm-x11-1.2-0v5:oldlibs/optional
> > libgtkglextmm-x11-1.2-dev:oldlibs/optional
> > python-gtkglext1:oldlibs/optional
>
> Do the ftp team prefer to receive a separate bug report for each binary
> package that is deprecated and should be overridden into oldlibs?

You did it the right way :)

-- 
Cheers,
Luca



Bug#928032: Default configuration for USBGuard

2019-07-16 Thread Antoine Beaupré
On 2019-07-15 11:09:55, Thiébaud Weksteen wrote:
> Hi Birger, Antoine,
>
> Thanks for getting 0.7.5 ready. For the difference between "allow" and
> "keep" on PresentDevicePolicy, the standard use case is handled
> similarly (i.e., user installing USBGuard for the 1st time, no
> customisation). The difference is slightly more subtle for hosts that
> have changed the sysfs attributes directly, for some reason. In this
> case, "keep" would respect whatever state was declared. Because of
> this and as Antoine suggested, I think this is a better option.
>
> On generate-policy vs PresentDevicePolicy, I would argue that the
> simplest option is the best. By running generate-policy, you are
> parsing all current devices, generating rules and then applying these
> rules. There might be (unlikely) a bug in the rule generation which
> ends up blocking a device (e.g., missing attribute or so). The
> PresentDevicePolicy=keep is just a simpler alternative.
>
> It might be useful to write down some Debian-specific documentation on
> how to setup the daemon to be more restrictive? The wiki might be a
> good place for that?

Problem with PresentDevicePolicy=keep is that it might break on reboot
or setup changes (e.g. moving laptop from office to home).

That said, I'd expect such docs to live in
/usr/share/doc/usbguard/README.Debian or something similar, that way if
my USB ethernet controller gets blockd, i can still read it. :) But wiki
is also good because people can contribute more easily.

Either way, docs are good. :) And one can point to the other.

a.
-- 
On ne peut s'empêcher de vieillir, mais on peut s'empêcher de devenir
vieux.
- Henri Matisse



Bug#932179: dh-r: dh-update-R does not support debhelper-compat

2019-07-16 Thread Andreas Tille
Package: dh-r
Version: 20190411
Severity: normal


Hi,

in r-cran-irkernel in commit 170e3cbd Gordon Ball has removed
debian/compat and replaced debhelper by

   debhelper-compat (= 12)

While I'm not sure whether this is a good idea regarding backports it
breaks the routine-update script which always calls dh-update-R.  In
this script in line 117[1] debian/compat is parsed to obtain debhelper
version - which fails since that file does not exist any more if
debhelper-compat is used.  Since there is not even proper error handling
in line 122 an invalid string is created.

For the moment I can cope with the r-cran-irkernel package update by
simply reverting the change and re-introduce debian/compat.  But in
the long term dh-update-R should be able to cope with valid control
file syntax.

Kind regards

 Andreas.

[1] 
https://salsa.debian.org/r-pkg-team/dh-r/blob/master/scripts/dh-update-R#L117


-- System Information:
Debian Release: 10.0
  APT prefers testing
  APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages dh-r depends on:
ii  dctrl-tools 2.24-3
ii  debhelper   12.1.1
ii  libfile-which-perl  1.23-1
ii  libswitch-perl  2.17-2
ii  r-base-dev  3.5.2-1

Versions of packages dh-r recommends:
ii  devscripts  2.19.5

dh-r suggests no packages.

-- no debconf information



Bug#930113: tor: please provide runscript file

2019-07-16 Thread Dmitry Bogatov


control: retitle -1 tor: please provide runscript file -- second call

Hello, dear maintainer.

This bug, requesting addition of runscript file into package was filed
some time ago, and got no response. It is quite unfortunate, since
your review of could have provided valuable advice how to improve
proposed patch.

But, after all, we all volonteers here. So hereby I inform you,
following advice in Developer reference, section 5.11, that I plan to
do non-maintainer upload in two weeks or so.

Upload will be into DELAYED/15, so you still have plenty of time
to make comments and take action.

Thank you for your work on Debian.

Best regards.

Previous version of patch contained bug, that is fixed by patch below.
Also, there is successful automatic check on Salsa¹

 ¹ https://salsa.debian.org/kaction/tor-runscript/-/jobs/222478

From 1b139e7b57d725ef94851118bc010c81ecb932ce Mon Sep 17 00:00:00 2001
From: Dmitry Bogatov 
Date: Thu, 6 Jun 2019 10:00:28 +
Subject: [PATCH] Add integration for runit init

---
 debian/control|  3 +-
 debian/rules  |  1 +
 debian/tor.install|  2 ++
 debian/tor.runit  |  1 +
 debian/tor.runscript/conf/MAX_FILEDESCRIPTORS |  1 +
 debian/tor.runscript/run  | 32 +++
 6 files changed, 39 insertions(+), 1 deletion(-)
 create mode 100644 debian/tor.runit
 create mode 100644 debian/tor.runscript/conf/MAX_FILEDESCRIPTORS
 create mode 100644 debian/tor.runscript/run

diff --git a/debian/control b/debian/control
index 74ba641..e240b05 100644
--- a/debian/control
+++ b/debian/control
@@ -2,7 +2,7 @@ Source: tor
 Section: net
 Priority: optional
 Maintainer: Peter Palfrader 
-Build-Depends: debhelper (>= 9.20160114), quilt, libssl-dev, zlib1g-dev, 
libevent-dev (>= 1.1), asciidoc (>= 8.2), docbook-xml, docbook-xsl, xmlto, 
dh-apparmor, libseccomp-dev [amd64 i386], dh-systemd [linux-any], 
libsystemd-dev [linux-any], pkg-config [linux-any], libcap-dev [linux-any], 
dh-autoreconf, liblzma-dev, libzstd-dev
+Build-Depends: debhelper (>= 9.20160114), quilt, libssl-dev, zlib1g-dev, 
libevent-dev (>= 1.1), asciidoc (>= 8.2), docbook-xml, docbook-xsl, xmlto, 
dh-apparmor, libseccomp-dev [amd64 i386], dh-systemd [linux-any], 
libsystemd-dev [linux-any], pkg-config [linux-any], libcap-dev [linux-any], 
dh-autoreconf, liblzma-dev, libzstd-dev, dh-runit (>= 2.8.8)
 Build-Conflicts: libnacl-dev, libseccomp-dev [!amd64 !i386]
 Standards-Version: 3.9.8
 Homepage: https://www.torproject.org/
@@ -14,6 +14,7 @@ Architecture: any
 Depends: ${shlibs:Depends}, adduser, ${misc:Depends}, lsb-base
 Pre-Depends: ${misc:Pre-Depends}
 Conflicts: libssl0.9.8 (<< 0.9.8g-9)
+Breaks: ${runit:Breaks}
 Recommends: logrotate, tor-geoipdb, torsocks
 Suggests: mixmaster, torbrowser-launcher, socat, tor-arm, apparmor-utils, 
tor-arm, obfs4proxy
 Description: anonymizing overlay network for TCP
diff --git a/debian/rules b/debian/rules
index 710d166..22c093a 100755
--- a/debian/rules
+++ b/debian/rules
@@ -26,6 +26,7 @@ endif
$@ \
--with quilt \
--with autoreconf \
+   --with runit \
$(dhoptions) \
--builddirectory=build \
--parallel
diff --git a/debian/tor.install b/debian/tor.install
index 97da1ca..566d16a 100644
--- a/debian/tor.install
+++ b/debian/tor.install
@@ -11,3 +11,5 @@ debian/systemd/tor.service lib/systemd/system
 debian/systemd/tor@.service lib/systemd/system
 debian/systemd/tor@default.service lib/systemd/system
 debian/systemd/tor-generator lib/systemd/system-generators
+
+debian/tor.runscript/conf/* /etc/tor/conf
diff --git a/debian/tor.runit b/debian/tor.runit
new file mode 100644
index 000..5ca5bca
--- /dev/null
+++ b/debian/tor.runit
@@ -0,0 +1 @@
+debian/tor.runscript name=tor,logscript,since=0.3.5.8-1+runit
diff --git a/debian/tor.runscript/conf/MAX_FILEDESCRIPTORS 
b/debian/tor.runscript/conf/MAX_FILEDESCRIPTORS
new file mode 100644
index 000..252cb66
--- /dev/null
+++ b/debian/tor.runscript/conf/MAX_FILEDESCRIPTORS
@@ -0,0 +1 @@
+8192
diff --git a/debian/tor.runscript/run b/debian/tor.runscript/run
new file mode 100644
index 000..bd7c126
--- /dev/null
+++ b/debian/tor.runscript/run
@@ -0,0 +1,32 @@
+#!/usr/bin/env /lib/runit/invoke-run
+readonly daemon=/usr/bin/tor
+exec 2>&1
+
+# This directory is referenced in /usr/share/tor/tor-service-defaults-torrc
+# and must exist.
+readonly authdir=/run/tor
+if test ! -d "${authdir}"; then
+   mkdir -m 02755 "${authdir}"
+   chown debian-tor:debian-tor "${authdir}"
+   ! [ -x /sbin/restorecon ] || /sbin/restorecon "${authdir}"
+fi
+
+ulimit -n "${MAX_FILEDESCRIPTORS}"
+
+# default invocation
+set -- "${daemon}" \
+   --defaults-torrc /usr/share/tor/tor-service-defaults-torrc \
+   -f /etc/tor/torrc

Bug#672155: qmail: notification about NMU

2019-07-16 Thread Dmitry Bogatov

Hello.

Month ago or so I sent patches to fix these bugs (on which is
important). There were no response.

So hereby, according to advice in Developer Reference 5.11 I inform you
that I just made non-maintainer upload to DELAYED/15.

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 15 Jul 2019 19:54:50 +
Source: netqmail
Architecture: source
Version: 1.06-6.1
Distribution: unstable
Urgency: medium
Maintainer: Gerrit Pape 
Changed-By: Dmitry Bogatov 
Closes: 672155 866038
Changes:
 netqmail (1.06-6.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * [fdc8794a] Setup Gitlab continous integration
   * [73e52807] Fix quotation in postinst (Closes: #866038)
   * [2fc47776] Make package piupart-clean (Closes: #672155)
Checksums-Sha1:
 a47586a2c702e4715e3c3bb256c4265777c50553 1741 netqmail_1.06-6.1.dsc
 1157a0635c0bb5c5cd234d3cfc5700278ffcc8ed 28278 netqmail_1.06-6.1.diff.gz
Checksums-Sha256:
 a4b74dd7ca022d211e429ae56373ec31de121ffcfc5e4eebe08bfed5997a0ca7 1741 
netqmail_1.06-6.1.dsc
 acc3b7306bf3aab468b5a79ab11250aeb6aa6b746e73b6fbc4411adc30a0b254 28278 
netqmail_1.06-6.1.diff.gz
Files:
 5a3cc259dc3013cfda524c2d6e0dc924 1741 mail extra netqmail_1.06-6.1.dsc
 a9e19c389530faf257cec0af5fbdb2b1 28278 mail extra netqmail_1.06-6.1.diff.gz

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEhnHVzDbtdH7ktKj4SBLY3qgmEeYFAl0s2mETHGthY3Rpb25A
ZGViaWFuLm9yZwAKCRBIEtjeqCYR5mIuD/0ZPXprwVeBNj23RabFTO/dkYtaFEII
vOagN6guVeXUJtCa1h+n93RVhkFbiAVKKBZqi9k/2PiLENc18wWgRusPHDPoSxJt
lEWGvoOAECQYsrfmd+EsK4/BcHToEPwqLfl8Oq7C1Il5ZkHKbOi9n5/uJvhhZZdF
tz6+5MD5yCDaFFEm/1sNPGKVNd75p3KcgQRoRaYjbCkYbZuOPPvXhdxLcx1g+oDk
gwiD57JvgREhCFpYffkNhFDgmy1AFwTcsz/Ds90nswsRrahB2mJT/wLKq/To+d2e
+e93xdZcWtcPi1evEXwoZSkVyRr6QZTjqA1SLVfPwigB4zrwchBJmTOg0Fy+j0gr
uHEzIzhznL2A/NagDLr0gz9jUGCpc3C1HXi2aUcRLGLW2DweBKcaxjcj2uL69HPo
moAJ5LvluUFsFr4avDbWszAG73IR+oiDsm66z6vC3aAKvo3g9DmIdyuhiyESKKQ+
CNJ0ngWGWrqPZdFqdM/FlB9MNPKY1y51VQ6xrQ1zZUrTwsEVLDD+fkCc150AQVCq
STVYT35hIZw88qCLL/uflam0PYAWnP3kk1kcZqWHHNzjZvrHH/PVet/Axg2akaXG
sfV/RbMwRoPnaQFKo015z+g4EhH4YjJWdK8MI4i0SU9DX7ANk1AkNn7j6xKyNtRT
bwamjDT3wuRDOA==
=oyRs
-END PGP SIGNATURE-
-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.


pgphwtoO4DKKY.pgp
Description: PGP signature


Bug#462389: Bug#932073: dh_installinit fails with "--name=foo option specified, but init script not found"

2019-07-16 Thread Dmitry Bogatov


[2019-07-14 17:59] Niels Thykier 
> > debhelper 12.2 fixes #462389 and makes dh_installinit fail when the
> > --name'd init script does not exist. This behaviour change makes at
> > least openssh and util-linux FTBFS. These are two high popcon example
> > packages. I expect more.
> > [...]
> > 
> > It is unclear to me whether it can be fixed in debhelper at all. Yet I
> > am filing the bug to have something recorded. If you determine that this
> > should be fixed in the individual packages, please clone and reassign.
> > 
> > Helmut
> > 
>
> Hi Dmitry,
>
> This report seems to be a regression related to your patch from #462389.

Definitely regression.

From a7288f30a003759b186389b93d336bef90491062 Mon Sep 17 00:00:00 2001
From: Dmitry Bogatov 
Date: Mon, 15 Jul 2019 16:08:01 +
Subject: [PATCH] Fix logic error in --name sanity check

Commit [e5fc959e], resolving #462389 changed behaviour of `--name' option of
dh_installinit. Before this change, if `debian/{package}.{name}.init' is 
missing,
this option was silently ignored. This change made it error.

This change was incorrect, since it demanded presence of 
`debian/{package}.{name}.init'
file for /every/ binary package.

This commit instead throws error only if `debian/{package}.{name}.init' does
not exist for /all/ binary {package} names. Regression test is added.

Closes: #932073
---
 dh_installinit | 10 ++
 t/dh_installinit/debian/bar.other.init |  4 
 t/dh_installinit/dh_installinit.t  |  2 ++
 3 files changed, 12 insertions(+), 4 deletions(-)
 create mode 100644 t/dh_installinit/debian/bar.other.init

diff --git a/dh_installinit b/dh_installinit
index 6a490370..cd038af1 100755
--- a/dh_installinit
+++ b/dh_installinit
@@ -232,6 +232,12 @@ init(options => {
 
 my %snippet_options = ('snippet-order' => 'service');
 
+if (my $name = $dh{NAME}) {
+   if (!grep { -f "debian/$_.${name}.init" } @{$dh{DOPACKAGES}}) {
+   error("--name=$dh{NAME} option specified, but init script not 
found");
+   }
+}
+
 foreach my $package (@{$dh{DOPACKAGES}}) {
my $tmp=tmpdir($package);
 
@@ -311,10 +317,6 @@ foreach my $package (@{$dh{DOPACKAGES}}) {
my $init=pkgfile($package,$scriptsrc) || pkgfile($package,"init") ||
pkgfile($package,"init.d");
 
-   if (!$init && defined $dh{NAME}) {
-   error("--name=$dh{NAME} option specified, but init script not 
found");
-   }
-
if ($init ne '' && ! $dh{ONLYSCRIPTS}) {
install_dir("$tmp/etc/init.d");
install_prog($init,"$tmp/etc/init.d/$script");
diff --git a/t/dh_installinit/debian/bar.other.init 
b/t/dh_installinit/debian/bar.other.init
new file mode 100644
index ..ea948c58
--- /dev/null
+++ b/t/dh_installinit/debian/bar.other.init
@@ -0,0 +1,4 @@
+#!/bin/sh
+cat << 'EOF'
+I am init script to be installed into package "bar" into /etc/init.d/other 
path.
+EOF
\ No newline at end of file
diff --git a/t/dh_installinit/dh_installinit.t 
b/t/dh_installinit/dh_installinit.t
index afe3821f..3b6bc038 100755
--- a/t/dh_installinit/dh_installinit.t
+++ b/t/dh_installinit/dh_installinit.t
@@ -12,6 +12,7 @@ our @TEST_DH_EXTRA_TEMPLATE_FILES = (qw(
 debian/changelog
 debian/control
 debian/foo.service
+debian/bar.other.init
 ));
 
 plan(tests => 2);
@@ -30,6 +31,7 @@ each_compat_from_and_above_subtest(11, sub {
 
ok(run_dh_tool('dh_installinit'));
ok(! run_dh_tool({'quiet' => 1}, 'dh_installinit', '--name=missing'));
+   ok(  run_dh_tool({'queit' => 1}, 'dh_installinit', '--name=other'));
ok(! -e "debian/foo/lib/systemd/system/foo.service");
ok(!find_script('foo', 'postinst'));
ok(run_dh_tool('dh_clean'));


-- 
Note, that I send and fetch email in batch, once in a few days.
Please, mention in body of your reply when you add or remove recepients.



Bug#930113: tor: please provide runscript file

2019-07-16 Thread Peter Palfrader
On Tue, 16 Jul 2019, Dmitry Bogatov wrote:

> 
> control: retitle -1 tor: please provide runscript file -- second call
> 
> Hello, dear maintainer.
> 
> This bug, requesting addition of runscript file into package was filed
> some time ago, and got no response. It is quite unfortunate, since
> your review of could have provided valuable advice how to improve
> proposed patch.
> 
> But, after all, we all volonteers here. So hereby I inform you,
> following advice in Developer reference, section 5.11, that I plan to
> do non-maintainer upload in two weeks or so.
> 
> Upload will be into DELAYED/15, so you still have plenty of time
> to make comments and take action.

don't.

-- 
|  .''`.   ** Debian **
  Peter Palfrader   | : :' :  The  universal
 https://www.palfrader.org/ | `. `'  Operating System
|   `-https://www.debian.org/



Bug#914783: fixed in znc 1.7.4-2

2019-07-16 Thread Patrick Matthäi
Thanks, that was already fixed in my svn for the next upload:

* Add VERSION_EXTRA string again.
* Add cmake dependency to znc-dev package.

Am 16.07.2019 um 11:34 schrieb Gianfranco Costamagna:
> control: reopen -1
> control: notfixed -1
> control: severity -1 serious
> control: tags -1 patch
> control: affects -1 znc-backlog
>
>>* Switch to the cmake build system.
>>  Closes: #914783
> thanks for doing it, but due to a missing runtime dependency on cmake, now 
> reverse dependencies are FTBFS because of missing cmake
>
>
> The attached patch should fix the issue.
>
> thanks for considering it
>
> Gianfranco
>
> +znc (1.7.4-2.11) unstable; urgency=medium
> +
> +  * Add cmake dependency also as runtime dependency for reverse-dependencies 
> (Closes: #914783)
> +
> + -- Gianfranco Costamagna   Tue, 16 Jul 2019 
> 11:30:29 +0200
> +
>  znc (1.7.4-2) unstable; urgency=medium
>  
>* Switch to the cmake build system.
> diff -Nru znc-1.7.4/debian/control znc-1.7.4/debian/control
> --- znc-1.7.4/debian/control  2019-07-11 12:03:16.0 +
> +++ znc-1.7.4/debian/control  2019-07-16 09:30:28.0 +
> @@ -49,6 +49,7 @@
>  Architecture: any
>  Depends: ${misc:Depends},
>   ${python3:Depends},
> + cmake,
>   znc (>= ${binary:Version}),
>   libicu-dev,
>   libssl-dev,

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/



Bug#932180: lyx: No print menu

2019-07-16 Thread Joerg Hau
Package: lyx
Version: 2.3.2-1
Severity: important

Fresh install of Debian 10 (VirtualBox). This system has a printer configured. 
However, Lyx offers no "Print" menu.

Steps to reproduce:
- fresh install of Debian 10
- use Apper to install LyX (this will install a lot of options)
- open any document in Lyx, e.g. Help > Tutorial
- try to print (it used to be in File > Print)

It would appear that you have to export to PDF first, then print thre PDF 
through some other application. 

What am I missing?


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

Kernel: Linux 4.19.0-5-amd64 (SMP w/1 CPU core)
Kernel taint flags: TAINT_CRAP
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lyx depends on:
ii  libc62.28-10
ii  libenchant1c2a   1.6.0-11.1+b1
ii  libgcc1  1:8.3.0-6
ii  libmagic11:5.35-4
ii  libmythes-1.2-0  2:1.2.4-3
ii  libqt5core5a 5.11.3+dfsg1-1
ii  libqt5gui5   5.11.3+dfsg1-1
ii  libqt5svg5   5.11.3-2
ii  libqt5widgets5   5.11.3+dfsg1-1
ii  libstdc++6   8.3.0-6
ii  lyx-common   2.3.2-1
ii  xdg-utils1.1.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages lyx recommends:
ii  dvipng   1.15-1.1
ii  fonts-lyx2.3.2-1
ii  ghostscript  9.27~dfsg-2
ii  imagemagick  8:6.9.10.23+dfsg-2.1
ii  imagemagick-6.q16 [imagemagick]  8:6.9.10.23+dfsg-2.1
ii  okular [pdf-viewer]  4:17.12.2-2.2
ii  poppler-utils0.71.0-5
ii  preview-latex-style  11.91-2
ii  psutils  1.17.dfsg-4
ii  texlive-fonts-recommended2018.20190227-2
ii  texlive-generic-extra2018.20190227-2
ii  texlive-generic-recommended  2018.20190227-2
ii  texlive-latex-extra  2018.20190227-2
ii  texlive-latex-recommended2018.20190227-2
ii  texlive-science  2018.20190227-2

Versions of packages lyx suggests:
pn  chktex  
pn  gnuhtml2latex   
pn  groff   
pn  latex2rtf   
pn  librsvg2-bin | inkscape 
pn  libtiff-tools   
pn  linuxdoc-tools  
pn  noweb   
pn  rcs 
pn  sgmltools-lite  
ii  texlive-plain-generic [tex4ht]  2018.20190227-2
pn  texlive-xetex   
pn  writer2latex
pn  wv  

-- no debconf information



Bug#924049:

2019-07-16 Thread Mateusz Mikołajczyk
Yes, that is correct, I've read the gitlab entries yesterday. But if you
read them you will find that this is basically a stalemate [gnome calendar
does not support ics files and therefore cannot have the mime but mime is
required to select it on the settings panel] and the problem still persist
- means - despite the fact that you have installed appropriate software
(gnome-calendar) you cannot use it (in terms of integration). Therefore I
thought that it would be more benefitial for the OP if I'd give a (agreed,
hacky) way of OP being able to select the calendar app rather than leaving
the bug without resolution.

regards,

-- 
pozdrawiam serdecznie,
Mateusz Mikołajczyk, a.k.a. toudi


Bug#932181: e2tools: New potential upstream for e2tools available?

2019-07-16 Thread Theodore Y. Ts'o
Package: e2tools
Version: 0.0.16-6.1+b2
Severity: wishlist

The original source for e2tools has disappeared (the home.earthlink.net
pages is dead), but it looks like there is activity at:

https://github.com/ndim/e2tools

Hans has modernized the package, fixing the FSF's address in the
copyright notices, updated the autoconf file, fixed various compiler
warnings, added man pages (taken from Debian, in fact), etc.  

Also note that e2tools actually *does* work on ext4 file systems
(although e2cp is creating indirect-mapped blocks by default, which is
unfortunate).  So the package description should be updated as well.

I'd suggest reaching out to Hans and Keith Sheffield (assuming his
pobox.com e-mail is still working) to make sure they are amenable to
upstream switch.


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (900, 'testing'), (900, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.1.0-00062-gc804857673ae (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), 
LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages e2tools depends on:
ii  e2fslibs1.45.3-1
ii  libc6   2.28-10
ii  libcomerr2  1.45.3-1

e2tools recommends no packages.

e2tools suggests no packages.

-- no debconf information



Bug#932182: vlc: Floating point exception crash playing certain DVDs

2019-07-16 Thread Sergio Gelato
Source: vlc
Version: 3.0.7-0+deb9u1

(Also reproducible on buster's 3.0.7-1.)

vlc reproducibly crashes early on when trying to play a certain DVD in my 
collection. (Other DVDs play normally.) Judging from the backtrace (see below), 
this may be fixed by upstream commit 90989df9e3aab300c2d09a8eb9c0570e4cba4efa:
vout: opengl: converter: prevent FPE with cropped empty spu
This seems to cherry-pick cleanly, I'll be building and testing a modified 
package soon.

Report #929491 may be about the same problem but doesn't contain enough detail 
for me to be certain.

I've censored out the DVD title and serial number for privacy.

Reading symbols from /usr/bin/vlc...Reading symbols from 
/usr/lib/debug/.build-id/e9/f58f04722b8df7835baf5420050c3f691bc510.debug...done.
done.
(gdb) run dvd://1
Starting program: /usr/bin/vlc dvd://1
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
VLC media player 3.0.7 Vetinari (revision 3.0.7-0-g86cee31099)
[New Thread 0x7fffe984e700 (LWP 6978)]
[New Thread 0x7fffef216700 (LWP 6979)]
[New Thread 0x7fffe4e3a700 (LWP 6980)]
[5575a0e0] main libvlc: Running vlc with the default interface. Use 
'cvlc' to use vlc without interface.
[New Thread 0x7fffe41f0700 (LWP 6981)]
[New Thread 0x7fffc6967700 (LWP 6982)]
[New Thread 0x7fffc5d51700 (LWP 6983)]
[New Thread 0x7fffc51f9700 (LWP 6985)]
[New Thread 0x7fffb7fff700 (LWP 6986)]
[New Thread 0x7fffbc11a700 (LWP 6987)]
libdvdnav: Using dvdnav version 5.0.3
[New Thread 0x7fffb53c4700 (LWP 6988)]
[New Thread 0x7fffb52c3700 (LWP 6989)]
[Thread 0x7fffb52c3700 (LWP 6989) exited]
[Thread 0x7fffb53c4700 (LWP 6988) exited]
libdvdnav: DVD Title: 
libdvdnav: DVD Serial Number: 
libdvdnav: DVD Title (Alternative): 
libdvdnav: DVD disk reports itself with Region mask 0x. Regions: 1 2 3 
4 5 6 7 8

libdvdread: Attempting to retrieve all CSS keys
libdvdread: This can take a _long_ time, please be patient

libdvdread: Get key for /VIDEO_TS/VIDEO_TS.VOB at 0x0134
libdvdread: Elapsed time 0
libdvdread: Get key for /VIDEO_TS/VTS_01_0.VOB at 0x017e
libdvdread: Elapsed time 0
libdvdread: Get key for /VIDEO_TS/VTS_01_1.VOB at 0x01b7
libdvdread: Elapsed time 0
libdvdread: Get key for /VIDEO_TS/VTS_02_0.VOB at 0x29e4
libdvdread: Elapsed time 0
libdvdread: Get key for /VIDEO_TS/VTS_02_1.VOB at 0x29eb
libdvdread: Elapsed time 0
libdvdread: Found 2 VTS's
libdvdread: Elapsed time 0
[New Thread 0x7fffb53c4700 (LWP 6996)]
[New Thread 0x7fffb52c3700 (LWP 6997)]
[New Thread 0x7fff98122700 (LWP 6998)]
[New Thread 0x7fffb4791700 (LWP 6999)]
[New Thread 0x7fff95163700 (LWP 7000)]
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
libva info: va_openDriver() returns -1
[7fffa0005da0] glconv_vaapi_x11 gl error: vaInitialize: unknown libva error
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
libva info: va_openDriver() returns -1
[7fffa0005da0] glconv_vaapi_drm gl error: vaInitialize: unknown libva error
libva info: VA-API version 0.39.4
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
libva info: va_openDriver() returns -1
[7fffa0005da0] glconv_vaapi_drm gl error: vaInitialize: unknown libva error
[7fffa81896d0] avcodec decoder: Using G3DVL VDPAU Driver Shared Library 
version 1.0 for hardware decoding
[7fffa81896d0] main decoder error: buffer deadlock prevented

Thread 17 "vlc" received signal SIGFPE, Arithmetic exception.
[Switching to Thread 0x7fff95163700 (LWP 7000)]
0x7fff94e5cf13 in upload_plane (pixels=0x7fff8c002e40, visible_pitch=0, 
pitch=, height=, width=0, tex_idx=0, 
tc=0x7fffa004f190) at video_output/opengl/converter_sw.c:496
496 video_output/opengl/converter_sw.c: No such file or directory.
(gdb) bt
#0  0x7fff94e5cf13 in upload_plane (pixels=0x7fff8c002e40, visible_pitch=0, 
pitch=, height=, width=0, tex_idx=0, 
tc=0x7fffa004f190) at video_output/opengl/converter_sw.c:496
#1  0x7fff94e5cf13 in tc_common_update (tc=0x7fffa004f190, 
textures=0x7fffa00aacd0, tex_width=0x7fffa00aacd4, tex_height=0x7fffa00aacd8, 
pic=0x7fff8c002c50, plane_offset=0x7fff951626e0) at 
video_output/opengl/converter_sw.c:519
#2  0x7fff94e5851d in vout_display_opengl_Prepare (vgl=0x7fffa00c51f0, 
picture=picture@entry=0x7fffa05cffa0, 
subpicture=subpicture@entry=0x7fffa0551c10)
at video_output/opengl/vout_helper.c:1231
#3  0x7fff94e5e1d6 in PictureRender (vd=, 
pic=0x7fffa05cffa0, subpicture=0x7fffa0551c10) at 
video_output/opengl/display.c:210
#4  0x771656bc in vout_display_Prepare (subpicture=, 
picture=0x7fffa05cffa0, vd=0x7fffa054e6c0) at ../include/vlc_vout_wrapper.h:47
#5  0x771656bc in ThreadDisplayRenderPicture 
(vo

Bug#932162: xorg logs with nomodeset

2019-07-16 Thread Henry J. Douglas
Booted with nomodeset i915.modeset=0 and here are the results.

No display either. LightDM doesn't start, Xorg doesn't start.
[30.131] 
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[30.131] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
[30.131] Current Operating System: Linux alq11 4.19.0-5-amd64 #1 SMP Debian 
4.19.37-5 (2019-06-19) x86_64
[30.131] Kernel command line: BOOT_IMAGE=/vmlinuz-4.19.0-5-amd64 
root=/dev/mapper/alq11--vg-root ro quiet nomodeset i915.modeset=0
[30.131] Build Date: 05 March 2019  08:11:12PM
[30.131] xorg-server 2:1.20.4-1 (https://www.debian.org/support) 
[30.131] Current version of pixman: 0.36.0
[30.131]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[30.131] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[30.131] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jul 16 09:12:39 
2019
[30.132] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[30.132] (==) No Layout section.  Using the first Screen section.
[30.132] (==) No screen section available. Using defaults.
[30.132] (**) |-->Screen "Default Screen Section" (0)
[30.132] (**) |   |-->Monitor ""
[30.133] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[30.133] (==) Automatically adding devices
[30.133] (==) Automatically enabling devices
[30.133] (==) Automatically adding GPU devices
[30.133] (==) Max clients allowed: 256, resource mask: 0x1f
[30.133] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[30.133]Entry deleted from font path.
[30.134] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[30.134] (==) ModulePath set to "/usr/lib/xorg/modules"
[30.134] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[30.134] (II) Loader magic: 0x55b6a15a0e20
[30.134] (II) Module ABI versions:
[30.134]X.Org ANSI C Emulation: 0.4
[30.134]X.Org Video Driver: 24.0
[30.134]X.Org XInput driver : 24.1
[30.134]X.Org Server Extension : 10.0
[30.136] (++) using VT number 7

[30.136] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[30.139] (--) PCI:*(0@0:2:0) 8086:22b1:1028:0725 rev 33, Mem @ 
0x9000/16777216, 0x8000/268435456, I/O @ 0xf000/64, BIOS @ 
0x/131072
[30.139] (II) LoadModule: "glx"
[30.139] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[30.142] (II) Module glx: vendor="X.Org Foundation"
[30.142]compiled for 1.20.4, module version = 1.0.0
[30.142]ABI class: X.Org Server Extension, version 10.0
[30.142] (==) Matched modesetting as autoconfigured driver 0
[30.142] (==) Matched fbdev as autoconfigured driver 1
[30.142] (==) Matched vesa as autoconfigured driver 2
[30.142] (==) Assigned the driver to the xf86ConfigLayout
[30.142] (II) LoadModule: "modesetting"
[30.142] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[30.142] (II) Module modesetting: vendor="X.Org Foundation"
[30.142]compiled for 1.20.4, module version = 1.20.4
[30.142]Module class: X.Org Video Driver
[30.142]ABI class: X.Org Video Driver, version 24.0
[30.142] (II) LoadModule: "fbdev"
[30.143] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[30.143] (II) Module fbdev: vendor="X.Org Foundation"
[30.143]compiled for 1.20.0, module version = 0.5.0
[30.143]Module class: X.Org Video Driver
[30.143]ABI class: X.Org Video Driver, version 24.0
[30.143] (II) LoadModule: "vesa"
[30.143] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[30.143] (II) Module vesa: vendor="X.Org Foundation"
[30.143]compiled for 1.20.1, module version = 2.4.0
[30.143]Module class: X.Org Video Driver
[30.143]ABI class: X.Org Video Driver, version 24.0
[30.143] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[30.144] (II) FBDEV: driver for framebuffer: fbdev
[30.144] (II) VESA: driver for VESA chipsets: vesa
[30.144] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not 
permitted)
[30.144] (EE) open /dev/dri/card0: No such file or directory
[30.144] (WW) Falling back to old probe method for modesetting
[30.144] (EE) open /dev/dri/card0: No such file or directory
[30.1

Bug#932097: xorg logs with nomodeset

2019-07-16 Thread Henry J. Douglas
Booted with nomodeset i915.modeset=0 and here are the results.

No display either. LightDM doesn't start, Xorg doesn't start.
[30.131] 
X.Org X Server 1.20.4
X Protocol Version 11, Revision 0
[30.131] Build Operating System: Linux 4.9.0-8-amd64 x86_64 Debian
[30.131] Current Operating System: Linux alq11 4.19.0-5-amd64 #1 SMP Debian 
4.19.37-5 (2019-06-19) x86_64
[30.131] Kernel command line: BOOT_IMAGE=/vmlinuz-4.19.0-5-amd64 
root=/dev/mapper/alq11--vg-root ro quiet nomodeset i915.modeset=0
[30.131] Build Date: 05 March 2019  08:11:12PM
[30.131] xorg-server 2:1.20.4-1 (https://www.debian.org/support) 
[30.131] Current version of pixman: 0.36.0
[30.131]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[30.131] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[30.131] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jul 16 09:12:39 
2019
[30.132] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[30.132] (==) No Layout section.  Using the first Screen section.
[30.132] (==) No screen section available. Using defaults.
[30.132] (**) |-->Screen "Default Screen Section" (0)
[30.132] (**) |   |-->Monitor ""
[30.133] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[30.133] (==) Automatically adding devices
[30.133] (==) Automatically enabling devices
[30.133] (==) Automatically adding GPU devices
[30.133] (==) Max clients allowed: 256, resource mask: 0x1f
[30.133] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist.
[30.133]Entry deleted from font path.
[30.134] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
built-ins
[30.134] (==) ModulePath set to "/usr/lib/xorg/modules"
[30.134] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[30.134] (II) Loader magic: 0x55b6a15a0e20
[30.134] (II) Module ABI versions:
[30.134]X.Org ANSI C Emulation: 0.4
[30.134]X.Org Video Driver: 24.0
[30.134]X.Org XInput driver : 24.1
[30.134]X.Org Server Extension : 10.0
[30.136] (++) using VT number 7

[30.136] (II) systemd-logind: logind integration requires -keeptty and 
-keeptty was not provided, disabling logind integration
[30.139] (--) PCI:*(0@0:2:0) 8086:22b1:1028:0725 rev 33, Mem @ 
0x9000/16777216, 0x8000/268435456, I/O @ 0xf000/64, BIOS @ 
0x/131072
[30.139] (II) LoadModule: "glx"
[30.139] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[30.142] (II) Module glx: vendor="X.Org Foundation"
[30.142]compiled for 1.20.4, module version = 1.0.0
[30.142]ABI class: X.Org Server Extension, version 10.0
[30.142] (==) Matched modesetting as autoconfigured driver 0
[30.142] (==) Matched fbdev as autoconfigured driver 1
[30.142] (==) Matched vesa as autoconfigured driver 2
[30.142] (==) Assigned the driver to the xf86ConfigLayout
[30.142] (II) LoadModule: "modesetting"
[30.142] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[30.142] (II) Module modesetting: vendor="X.Org Foundation"
[30.142]compiled for 1.20.4, module version = 1.20.4
[30.142]Module class: X.Org Video Driver
[30.142]ABI class: X.Org Video Driver, version 24.0
[30.142] (II) LoadModule: "fbdev"
[30.143] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
[30.143] (II) Module fbdev: vendor="X.Org Foundation"
[30.143]compiled for 1.20.0, module version = 0.5.0
[30.143]Module class: X.Org Video Driver
[30.143]ABI class: X.Org Video Driver, version 24.0
[30.143] (II) LoadModule: "vesa"
[30.143] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[30.143] (II) Module vesa: vendor="X.Org Foundation"
[30.143]compiled for 1.20.1, module version = 2.4.0
[30.143]Module class: X.Org Video Driver
[30.143]ABI class: X.Org Video Driver, version 24.0
[30.143] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[30.144] (II) FBDEV: driver for framebuffer: fbdev
[30.144] (II) VESA: driver for VESA chipsets: vesa
[30.144] xf86EnableIOPorts: failed to set IOPL for I/O (Operation not 
permitted)
[30.144] (EE) open /dev/dri/card0: No such file or directory
[30.144] (WW) Falling back to old probe method for modesetting
[30.144] (EE) open /dev/dri/card0: No such file or directory
[30.1

Bug#932183: libapache2-mod-wsgi-py3: sys.getfilesystemencoding() regression

2019-07-16 Thread Sebastian Rittau

Package: libapache2-mod-wsgi-py3
Version: 4.6.5-1
Severity: normal

Dear Maintainer,

apologies in advance if this gets reported twice.


Since upgrading from Debian 9 to Debian 10, our WSGI app starts
reporting UnicodeEncodeErrors when trying to access file names containing
umlauts. Consider the following file:

--

import os
import sys

def application(env, sr):
    print(sys.getfilesystemencoding())
    print(os.environ)
    with open("/tmp/föo", "w"):
    pass
    sr("200 OK", [("Content-Type", "text/plain")])
    return [b"Ok"]

--

This will log the following (snipping Apache log stuff):

--

ascii
environ({'APACHE_RUN_DIR': '/var/run/apache2', 'APACHE_PID_FILE': 
'/var/run/apache2/apache2.pid', 'JOURNAL_STREAM': '9:3328729', 'PATH': 
'/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin', 
'INVOCATION_ID': '9002aec454134616ab90af90af7c3c79', 'APACHE_LOCK_DIR': 
'/var/lock/apache2', 'LANG': 'de_DE.UTF-8', 'APACHE_RUN_USER': 
'www-data', 'APACHE_RUN_GROUP': 'www-data', 'APACHE_LOG_DIR': 
'/var/log/apache2', 'PWD': '/', 'LC_ALL': 'de_DE.UTF-8', 'HOME': 
'/var/www'})
mod_wsgi (pid=851): Exception occurred processing WSGI script 
'/srv/intranet.example.com/foo.wsgi'.

Traceback (most recent call last):
  File "/srv/intranet.example.com/foo.wsgi", line 7, in application
    with open("/tmp/f\xc3\xb6o", "w"):
UnicodeEncodeError: 'ascii' codec can't encode character '\\xf6' in 
position 6: ordinal not in range(128)


--

As can be seen from the first line, sys.getfilesystemencoding() returns
ASCII, despite the environment variables LANG and LC_ALL being set
correctly. (de_DE.UTF-8 also exists as a locale.) This is the corresponding
config:

--

    WSGIApplicationGroup intranet.example.com
    WSGIDaemonProcess intranet.example.com display-name=%{GROUP} 
lang='de_DE.UTF-8' locale='de_DE.UTF-8' 
python-path=/usr/local/virtualenv/intranet/lib/python3.7/site-packages/ 
processes=8 threads=50

    WSGIProcessGroup intranet.example.com

--

Potentially related to #872887.

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)

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

Versions of packages libapache2-mod-wsgi-py3 depends on:
ii  apache2-bin [apache2-api-20120211]  2.4.38-3
ii  libc6   2.28-10
ii  libpython3.7    3.7.3-2
ii  python3 3.7.3-1

libapache2-mod-wsgi-py3 recommends no packages.

libapache2-mod-wsgi-py3 suggests no packages.

-- no debconf information



Bug#932097: xorg logs with nomodeset

2019-07-16 Thread Henry J. Douglas
Ignore last message. Wrong bug report.

Em ter, 16 de jul de 2019 09:19, Henry J. Douglas 
escreveu:

> Booted with nomodeset i915.modeset=0 and here are the results.
>
> No display either. LightDM doesn't start, Xorg doesn't start.
>


Bug#932184: pbuilder: ADDITIONAL_BUILDRESULTS handling might iterate over debug output

2019-07-16 Thread Michael Prokop
Package: pbuilder
Version: 0.230.4
Severity: normal

Hi,

if ADDITIONAL_BUILDRESULTS is set and log level is set to debug mode
(`LOGLEVEL=D`), then pbuilder iterates over the debug output, e.g.:

| I: copying local configuration
| E: Failed autobuilding of package
| I: Trying to save additional result 'D:'
| cp: cannot stat 'D:': No such file or directory
| I: Trying to save additional result 'checking'
| cp: cannot stat 'checking': No such file or directory
| I: Trying to save additional result '[../*lintian.txt]...'
| cp: cannot stat '[../*lintian.txt]...': No such file or directory
| I: Trying to save additional result 'D:'
| cp: cannot stat 'D:': No such file or directory
| I: Trying to save additional result 'checking'
| cp: cannot stat 'checking': No such file or directory
| I: Trying to save additional result '[../*lintian.txt]...'
| cp: cannot stat '[../*lintian.txt]...': No such file or directory

The underlying reason is, that the export_additional_buildresults
function relies on output of the _find_additional_buildresults
helper function. The _find_additional_buildresults function outputs its
logging on stdout as well though, so when "log.d" is executed (which
it is under LOGLEVEL=D), then export_additional_buildresults()
operates on unexpected data.

Quoting the relevant code snippet from pbuilder-buildpackage-funcs:

| function _find_additional_buildresults() {
| local file f
| local root="${BUILDPLACE}${BUILDDIR}/${BUILDSUBDIR}"
| for file in "${ADDITIONAL_BUILDRESULTS[@]}"; do
| log.d "checking [$file]..."
| echo "$root/$file" | perl -ne 'print "$_\n" foreach glob($_)' | \
| while read f ; do
| if [ -e "$f" ]; then
| echo "$f"
| else
| log.w "file [$file] not found"
| fi
| done
| done
| }
|
| function export_additional_buildresults() {
| local file
| for file in $(_find_additional_buildresults); do
| log.i "Trying to save additional result '${file}'"
| cp -a "${file}" "${BUILDRESULT}" || true
| done
| }

regards
-mika-



Bug#906304: [Pkg-shadow-devel] Bug#906304: login: Failure to load desktop after login

2019-07-16 Thread Bálint Réczey
Control: notfound -1 1:4.4-4.1

Closing per submitter's request, please reopen if the issue shows up again.


on Mon, Jul 15, 2019, 23:02 Bálint Réczey  wrote:
>
> Control: tags -1 moreinfo
>
> Hi Cody,
>
> Cody Jackson  ezt írta (időpont: 2018. aug. 16.,
> Cs, 21:57):
> >
> > Package: login
> > Version: 1:4.4-4.1
> > Severity: important
> >
> > Dear Maintainer,
> >
> >* What led up to the situation?
> > Updating kernal from 4.9.0-6 to 4.9.0-7 using apt-get dist-upgrade
> >
> >* What exactly did you do (or not do) that was effective (or
> >  ineffective)?
> > My once per month apt-get dist-upgrade
> >
> >
> >
> >* What was the outcome of this action?
> >
> > When I started the OS with the new kernal. I was able to login, but then 
> > the screen went blank indefinitely. I tried shutting down and updating 
> > again. I also submitted a bug report to the kernal team, but it wasn't the 
> > right package.
> >* What outcome did you expect instead?
> >
> > The new kernal version to let me log in and use the desktop.
>
> Well, I believe the linux package would have still been better than
> login, which is for _console_ logins, but please tell if your issue
> was resolved because then we can close this bug instead of reassigning
> it.
>
> Thanks,
> Balint
>



Bug#932186: auto-multiple-choice depends on cruft package.

2019-07-16 Thread peter green

Package: mediawiki2latex
Version: 7.33-1
Tags: bullseye, sid
Severity: serious

mediawiki2latex depends on texlive-generic-recommended which is no longer built 
by texlive-base. texlive-generic-reccomended seems to be a transitional package 
so presumablly you just need to update your dependency.



Bug#932185: auto-multiple-choice depends on cruft package.

2019-07-16 Thread peter green

Package: auto-multiple-choice
Version: 1.4.0-1
Tags: bullseye, sid

Auto-multiple choice depends on texlive-generic-recommended which is no longer 
built by texlive-base. texlive-generic-reccomended seems to be a transitional 
package so presumablly you just need to update your dependency.



Bug#932187: stex depends on cruft package.

2019-07-16 Thread peter green

Package: stex
Version: 1.2.1+git20171204.g5e4f0ca-3
Tags: bullseye, sid
Severity: serious

stex depends on texlive-generic-recommended which is no longer built by 
texlive-base. texlive-generic-reccomended seems to be a transitional package so 
presumablly you just need to update your dependency.



Bug#932188: libapache2-mod-wsgi-py3: sys.getfilesystemencoding() regression

2019-07-16 Thread Sebastian Rittau
Package: libapache2-mod-wsgi-py3
Version: 4.6.5-1
Severity: normal

Dear Maintainer,

since upgrading from Debian 9 to Debian 10, our WSGI app starts
reporting UnicodeEncodeErrors when trying to access file names containing
umlauts. Consider the following file:

--

import os
import sys

def application(env, sr):
print(sys.getfilesystemencoding())
print(os.environ)
with open("/tmp/föo", "w"):
pass
sr("200 OK", [("Content-Type", "text/plain")])
return [b"Ok"]

--

This will log the following (snipping Apache log stuff):

--

ascii
environ({'APACHE_RUN_DIR': '/var/run/apache2', 'APACHE_PID_FILE': 
'/var/run/apache2/apache2.pid', 'JOURNAL_STREAM': '9:3328729', 'PATH': 
'/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin', 
'INVOCATION_ID': '9002aec454134616ab90af90af7c3c79', 'APACHE_LOCK_DIR': 
'/var/lock/apache2', 'LANG': 'de_DE.UTF-8', 'APACHE_RUN_USER': 'www-data', 
'APACHE_RUN_GROUP': 'www-data', 'APACHE_LOG_DIR': '/var/log/apache2', 'PWD': 
'/', 'LC_ALL': 'de_DE.UTF-8', 'HOME': '/var/www'})
mod_wsgi (pid=851): Exception occurred processing WSGI script 
'/srv/intranet.example.com/foo.wsgi'.
Traceback (most recent call last):
  File "/srv/intranet.example.com/foo.wsgi", line 7, in application
with open("/tmp/f\xc3\xb6o", "w"):
UnicodeEncodeError: 'ascii' codec can't encode character '\\xf6' in position 6: 
ordinal not in range(128)

--

As can be seen from the first line, sys.getfilesystemencoding() returns
ASCII, despite the environment variables LANG and LC_ALL being set
correctly. (de_DE.UTF-8 also exists as a locale.) This is the corresponding
config:

--

WSGIApplicationGroup intranet.example.com
WSGIDaemonProcess intranet.example.com display-name=%{GROUP} 
lang='de_DE.UTF-8' locale='de_DE.UTF-8' 
python-path=/usr/local/virtualenv/intranet/lib/python3.7/site-packages/ 
processes=8 threads=50
WSGIProcessGroup intranet.example.com

--

Potentially related to #872887.

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libapache2-mod-wsgi-py3 depends on:
ii  apache2-bin [apache2-api-20120211]  2.4.38-3
ii  libc6   2.28-10
ii  libpython3.73.7.3-2
ii  python3 3.7.3-1

libapache2-mod-wsgi-py3 recommends no packages.

libapache2-mod-wsgi-py3 suggests no packages.

-- no debconf information



Bug#932189: gedit: Stretch to Buster: highlight misspelled words is broken

2019-07-16 Thread Martin-Éric Racine
Package: gedit
Version: 3.30.2-2
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Since upgrading to Buster, the option to highlight misspelled words is broken. 
If the option is selected, the whole text (not just misspelled words) is 
highlighted. Unseöecting the option and re-selecting it does not fix it.

- -- Package-specific info:
Active plugins:
  - 'spell'
  -  'modelines'
  -  'filebrowser'
  -  'time'
  -  'docinfo'

No plugin installed in $HOME.

Module versions:
  pkg-config unavailable


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

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

Versions of packages gedit depends on:
ii  gedit-common   3.30.2-2
ii  gir1.2-glib-2.01.58.3-2
ii  gir1.2-gtk-3.0 3.24.5-1
ii  gir1.2-gtksource-3.0   3.24.9-2
ii  gir1.2-pango-1.0   1.42.4-6
ii  gir1.2-peas-1.01.22.0-4
ii  gsettings-desktop-schemas  3.28.1-1
ii  iso-codes  4.2-1
ii  libatk1.0-02.30.0-2
ii  libc6  2.28-10
ii  libcairo-gobject2  1.16.0-4
ii  libcairo2  1.16.0-4
ii  libenchant1c2a 1.6.0-11.1+b1
ii  libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii  libgirepository-1.0-1  1.58.3-2
ii  libglib2.0-0   2.58.3-2
ii  libgspell-1-1  1.6.1-2
ii  libgtk-3-0 3.24.5-1
ii  libgtksourceview-3.0-1 3.24.9-2
ii  libpango-1.0-0 1.42.4-6
ii  libpangocairo-1.0-01.42.4-6
ii  libpeas-1.0-0  1.22.0-4
ii  libx11-6   2:1.6.7-1
ii  libxml22.9.4+dfsg1-7+b3
ii  python33.7.3-1
ii  python3-gi 3.30.4-1
ii  python3-gi-cairo   3.30.4-1
ii  python3.7  3.7.3-2

Versions of packages gedit recommends:
ii  yelp3.31.90-1
ii  zenity  3.30.0-2

Versions of packages gedit suggests:
ii  gedit-plugins  3.30.1-3

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAl0tz0wACgkQrh+Cd8S0
17bsCg//bm1Dr1wUHGFz7djmULj+Bu3L9aUCZc/7PyraMLataDQFEYKQVhHuF/Pb
EA/7CaoJoH23eF3UdTlZRBnpou9X/ZnZFUUpbOgmFzhBC4WrETpWVEOy+PZHBa8Y
9MoDDXAA4zdxXiPDfB3rfSZJ3YOaOXzEhijp/7gM1hmW1G4swPVEwWcL8w3umMrS
930ovIUEFBOBwk5ow2zbkaycRM+utT0bni97sOcE2nHg4nem6R04ensLvjwFkBQ0
VdprRyozoA9pmY+IzGYWBYwQ11UknRSBQbEmNenI1uWti17UsA52PsYDeIhIy8vI
URz1F5/0JbPvQ3o7tgTZpLuFXPAooxHlbm4fF6RYyRW5U1fqWlV4Z+WK1My5XPeU
1hitdOh94+eGVDtsEu6e1chnocBsng5A3GI3z9w9494/t5uHNy7esJjbLiKC5p2X
jr8FVYU4gcxCCZ7QwrsrMbU4iwZk2Mt2rulhksHKNJVpZEqpVAvJTj+4DEs+tWX2
20O6V+XMHV0Dt8LoYo3ZY+r91KdVyng3qhxkXsdWA+0uuYH9y6P4wn/Vf4fvKu7e
q6KyoCHGe3icV4/yKyxTdk/NpbM8h20CZrK2FYIPnDgyEOgrrwNRlk7T0pw0dusr
pXrbz9eTg5/4YqvLQdX86ZbBeK82LmbY/IqW6AslmQsEdg2pSWw=
=uM4Q
-END PGP SIGNATURE-


Bug#932190: ruby-jekyll-gist: missing dependency on ruby-octokit

2019-07-16 Thread Morrell, Phil
Package: ruby-jekyll-gist
Version: 1.5.0-1
Severity: grave
Justification: renders package unusable

I installed jekyll, but am unable to run it on a project with the jekyll-gist
plugin enabled in _config.yml:

$ sudo apt install jekyll
$ jekyll
Traceback (most recent call last):
11: from /usr/bin/jekyll:9:in `'
10: from /usr/lib/ruby/vendor_ruby/jekyll/plugin_manager.rb:50:in
`require_from_bundler'
 9: from /usr/share/rubygems-
integration/all/gems/bundler-1.17.3/lib/bundler.rb:107:in `setup'
 8: from /usr/share/rubygems-
integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:20:in `setup'
 7: from /usr/share/rubygems-
integration/all/gems/bundler-1.17.3/lib/bundler/runtime.rb:108:in `block in
definition_method'
 6: from /usr/share/rubygems-
integration/all/gems/bundler-1.17.3/lib/bundler/definition.rb:226:in
`requested_specs'
 5: from /usr/share/rubygems-
integration/all/gems/bundler-1.17.3/lib/bundler/definition.rb:237:in
`specs_for'
 4: from /usr/share/rubygems-
integration/all/gems/bundler-1.17.3/lib/bundler/definition.rb:170:in `specs'
 3: from /usr/share/rubygems-
integration/all/gems/bundler-1.17.3/lib/bundler/definition.rb:258:in `resolve'
 2: from /usr/share/rubygems-
integration/all/gems/bundler-1.17.3/lib/bundler/resolver.rb:22:in `resolve'
 1: from /usr/share/rubygems-
integration/all/gems/bundler-1.17.3/lib/bundler/resolver.rb:45:in `start'
/usr/share/rubygems-
integration/all/gems/bundler-1.17.3/lib/bundler/resolver.rb:56:in `rescue in
start':
Bundler could not find compatible versions for gem "octokit":
(Bundler::VersionConflict)
  In Gemfile:
jekyll-gist was resolved to 1.5.0, which depends on
  octokit (~> 4.2)

Could not find gem 'octokit (~> 4.2)', which is required by gem 'jekyll-gist',
in any of the sources.
$ sudo apt install ruby-octokit
$ jekyll
A subcommand is required.



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

Kernel: Linux 4.19.0-5-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ruby-jekyll-gist depends on:
ii  ruby  1:2.5.1

ruby-jekyll-gist recommends no packages.

ruby-jekyll-gist suggests no packages.

-- no debconf information


HM Land Registry’s ambition is to become the world’s leading land registry for 
speed, simplicity and an open approach to data. Our mission is: “Your land and 
property rights: guaranteed and protected”.

We check all mail and attachments for known viruses. However, you are advised 
that you open any attachments at your own risk. If you have received this email 
and it was not intended for you, please let us know, then delete it.

We welcome correspondence in English and Welsh.

To see how HM Land Registry treats your personal information, read our Personal 
information charter: 
www.gov.uk/government/organisations/land-registry/about/personal-information-charter.




Bug#932191: stex depends on cruft package.

2019-07-16 Thread peter green

Package: stex
Version: 1.2.1+git20171204.g5e4f0ca-3
Tags: bullseye, sid
Severity: serious

stex depends on texlive-generic-recommended which is no longer built by 
texlive-base. texlive-generic-reccomended seems to be a transitional package so 
presumablly you just need to update your dependency.



Bug#932192: nano: More Color Better default option

2019-07-16 Thread Bardot Jerome
Package: nano
Version: 4.3-1
Severity: wishlist

Dear Maintainer,

We need more color maybe from here enable by default :

https://github.com/scopatz/nanorc

Also add by default option like -c (line number) and -s ispell .

There maybe no easy way to auto select the spell program.

If not ignore it.

also --softwrap but this one should be discuss.

thx



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

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages nano depends on:
ii  libc6 2.28-10
ii  libncursesw6  6.1+20181013-2
ii  libtinfo6 6.1+20181013-2
ii  zlib1g1:1.2.11.dfsg-1

nano recommends no packages.

Versions of packages nano suggests:
ii  spell  1.0-24

-- debconf-show failed



Bug#917354: News on this?

2019-07-16 Thread Yves-Alexis Perez
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi,

is there any update on this issue? I'm bitten by this one because my system is
mostly always in “degraded” state according to systemd. Consequence (as
outlined in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916122#18) is
that cgroup aren't used by pbuilder.

Regards,
- -- 
Yves-Alexis
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAl0t0pkACgkQ3rYcyPpX
RFvQhQgAmUGpKwLwdo9ljBZlzGPtgQhRI8irTD4//Le6OWWJGWEoh9OKl4mO5RNp
wDotPW1WlOyyaBlrSX4xaX4tFrvwNdZdfK6AtYzRkVMcqbgshF1fGwSMc5SC8pHE
mkAjXY1FfYCZzuNzcqpATNCCCYxCwCsISpaoH+wJ1S+oVF2axNLvU5zAyRGgvlY4
oduEIzmv/z7iQ/qL5wUyxgQ/pbV01f6WtL5hqPAoxeaW/HfgJHYNNXBC/wBL1O/4
DTfm/J6j+M2ilUL8tFdj8N3ETenqa+1ZVtno4sHybqGQy4PK97WP0yFwPhAKMt0g
ZYKYvMhTqHCRO2Yo/1jGGIS3paGeDA==
=BLL5
-END PGP SIGNATURE-



Bug#932012: Please upload backport for stretch

2019-07-16 Thread gregor herrmann
On Sat, 13 Jul 2019 14:48:39 -0700, Felix Lechner wrote:

> Future versions of Lintian will likely require version 0.20, which is
> not available in stretch. Will you please upload the backported
> package from Mentors [1] to stretch-backports?

So either mentors or stupid or me or both:

% dget -x 
https://mentors.debian.net/debian/pool/main/libi/libio-async-loop-epoll-perl/libio-async-loop-epoll-perl_0.20-1~bpo9+1.dsc
dget: retrieving 
https://mentors.debian.net/debian/pool/main/libi/libio-async-loop-epoll-perl/libio-async-loop-epoll-perl_0.20-1~bpo9+1.dsc
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
100  2602  100  26020 0   3738  0 --:--:-- --:--:-- --:--:--  3738
dget: retrieving 
https://mentors.debian.net/debian/pool/main/libi/libio-async-loop-epoll-perl/libio-async-loop-epoll-perl_0.20.orig.tar.gz
  % Total% Received % Xferd  Average Speed   TimeTime Time  Current
 Dload  Upload   Total   SpentLeft  Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 404 Not Found
dget: curl libio-async-loop-epoll-perl_0.20.orig.tar.gz 
https://mentors.debian.net/debian/pool/main/libi/libio-async-loop-epoll-perl/libio-async-loop-epoll-perl_0.20.orig.tar.gz
 failed
dpkg-source: info: extracting libio-async-loop-epoll-perl in 
libio-async-loop-epoll-perl-0.20
cp: cannot stat './libio-async-loop-epoll-perl_0.20.orig.tar.gz': No such file 
or directory
dpkg-source: error: cp ./libio-async-loop-epoll-perl_0.20.orig.tar.gz to 
./libio-async-loop-epoll-perl_0.20.orig.tar.gz subprocess returned exit status 1

And manually:

% wget 
https://mentors.debian.net/debian/pool/main/libi/libio-async-loop-epoll-perl/libio-async-loop-epoll-perl_0.20-1~bpo9+1.dsc
--2019-07-16 10:28:58--  
https://mentors.debian.net/debian/pool/main/libi/libio-async-loop-epoll-perl/libio-async-loop-epoll-perl_0.20-1~bpo9+1.dsc
Resolving mentors.debian.net (mentors.debian.net)... 185.22.221.46
Connecting to mentors.debian.net (mentors.debian.net)|185.22.221.46|:443... 
connected.
HTTP request sent, awaiting response... 200 OK
Length: 2602 (2.5K) [text/plain]
Saving to: ‘libio-async-loop-epoll-perl_0.20-1~bpo9+1.dsc’

libio-async-loop-epoll-perl_0.20-1~bpo9+1.dsc
100%[>]
   2.54K  --.-KB/sin 0s  

2019-07-16 10:28:59 (65.5 MB/s) - 
‘libio-async-loop-epoll-perl_0.20-1~bpo9+1.dsc’ saved [2602/2602]

% wget 
https://mentors.debian.net/debian/pool/main/libi/libio-async-loop-epoll-perl/libio-async-loop-epoll-perl_0.20-1~bpo9+1.debian.tar.gz
--2019-07-16 10:29:23--  
https://mentors.debian.net/debian/pool/main/libi/libio-async-loop-epoll-perl/libio-async-loop-epoll-perl_0.20-1~bpo9+1.debian.tar.gz
Resolving mentors.debian.net (mentors.debian.net)... 185.22.221.46
Connecting to mentors.debian.net (mentors.debian.net)|185.22.221.46|:443... 
connected.
HTTP request sent, awaiting response... 404 Not Found
2019-07-16 10:29:24 ERROR 404: Not Found.


So the .dsc refers to libio-async-loop-epoll-perl_0.20.orig.tar.gz
and libio-async-loop-epoll-perl_0.20-1~bpo9+1.debian.tar.xz and both
don't seem to exist on mentors.


Cheers,
gregor

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


signature.asc
Description: Digital Signature


Bug#707574: not used anymore

2019-07-16 Thread Changwoo Ryu
Control: reassign -1 ftp.debian.org
Control: retitle -1 RM: ko.tex-extra-hlfont -- replaced by recent
texlive, orphaned 6 years, no rdepends

I'm almost sure this package is not used anymore. CJKtex merged ko.tex
years ago (texlive-lang-korean package) and its legacy fonts are not
used in recent documents.



Bug#932118: r-cran-rjsonio up for removal?

2019-07-16 Thread Andreas Tille
On Tue, Jul 16, 2019 at 09:33:08AM +0200, Dylan Aïssi wrote:
> > Opinions?
> 
> r-cran-rjsonio is also orphaned by upstream [1]:
> 
> > Maintainer: ORPHANED
> 
> This is another reason to remove it from our repositories.

 #932118
 RM: r-cran-rjsonio -- ROM; Non-free, no active Uploader, rarely used

Thanks for the additional input

  Andreas.
 
> [1] https://cloud.r-project.org/package=RJSONIO

-- 
http://fam-tille.de



Bug#774330: ntfs-3g: Input/output error when accessing files in mounted partition

2019-07-16 Thread raphael . jolly
The problem is back in Buster (can mount filesystem but get I/O Errors).
Version of ntfs-3g is 2017.3.23AR.3-3.



Bug#932193: buster-pu: package netdata/1.12.0-1+deb10u1

2019-07-16 Thread Daniel Baumann
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu

Hi,

attached is the diff for netdata with cherry-picked patches from later
Debian uploads to disable spying on users and a couple of other
important things.

Thanks,
Daniel
diff --git a/debian/changelog b/debian/changelog
index b2d9488..360d5e6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,21 @@
+netdata (1.12.0-1+deb10u1) buster; urgency=medium
+
+  [ Lennart Weller ]
+  * Add patch to remove Google Analytics from generated docs
+
+  [ Daniel Baumann ]
+  * Removing currently usless depends on bash as it's still an essential
+package.
+  * Adding missing GPL-3-only license stanza in copyright file.
+  * Opting out by default from sending anonymous statistics (phone home).
+  * Downgrading nodejs depends in netdata-plugins-nodejs to recommends as
+not all architectures have nodejs at the moment.
+
+  [ Federico Ceratto ]
+  * Add patch to remove Sign In button
+
+ -- Daniel Baumann   Tue, 16 Jul 2019 15:41:56 +0200
+
 netdata (1.12.0-1) unstable; urgency=medium
 
   * Merging upstream version 1.12.0.
diff --git a/debian/control b/debian/control
index 15ab266..c93e7ff 100644
--- a/debian/control
+++ b/debian/control
@@ -97,7 +97,6 @@ Section: net
 Architecture: all
 Multi-Arch: foreign
 Depends:
- bash,
  netdata-core (>= ${source:Version}) | netdata-core-no-sse (>= ${source:Version}),
  ${misc:Depends},
 Suggests:
@@ -120,8 +119,9 @@ Architecture: all
 Multi-Arch: foreign
 Depends:
  netdata-core (>= ${source:Version}) | netdata-core-no-sse (>= ${source:Version}),
- nodejs,
  ${misc:Depends},
+Recommends:
+ nodejs,
 Provides:
  netdata-plugins,
 Enhances:
diff --git a/debian/copyright b/debian/copyright
index 8c73f0a..2abec45 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -183,7 +183,7 @@ Files:
  collectors/python.d.plugin/python_modules/third_party/boinc_client.py
 Copyright: 2013 Rodrigo Silva (MestreLion) 
2017 Austin S. Hemmelgarn
-License: GPL-3.0
+License: GPL-3
 
 Files:
  collectors/python.d.plugin/python_modules/third_party/mcrcon.py
@@ -246,6 +246,21 @@ License: LGPL-2.1
  General Public License, version 2, can be found in
  /usr/share/common-licenses/LGPL-2.
 
+License: GPL-3
+ This program is free software: you can redistribute it and/or modify it under
+ the terms of the GNU General Public License as published by the Free Software
+ Foundation, version 3 of the License.
+ .
+ This program is distributed in the hope that it will be useful, but WITHOUT ANY
+ WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A
+ PARTICULAR PURPOSE. See the GNU General Public License for more details.
+ .
+ You should have received a copy of the GNU General Public License along with
+ this program. If not, see .
+ .
+ On Debian systems, the complete text of the GNU General Public
+ License version 3 can be found in /usr/share/common-licenses/GPL-3.
+
 License: GPL-3+
  This program is free software: you can redistribute it and/or modify it under
  the terms of the GNU General Public License as published by the Free Software
diff --git a/debian/patches/debian/0009-remove-googleanalytics.patch b/debian/patches/debian/0009-remove-googleanalytics.patch
new file mode 100644
index 000..aa6f0e9
--- /dev/null
+++ b/debian/patches/debian/0009-remove-googleanalytics.patch
@@ -0,0 +1,11 @@
+Author: Lennart Weller 
+Subject: Remove googleanalytics
+
+diff -Naurp netdata.orig/docs/generator/custom/themes/material/partials/footer.html netdata/docs/generator/custom/themes/material/partials/footer.html
+--- netdata.orig/docs/generator/custom/themes/material/partials/footer.html
 netdata/docs/generator/custom/themes/material/partials/footer.html
+@@ -51,4 +51,3 @@
+ 
+   
+ 
+-!function(e,a,t,n,o,c,i){e.GoogleAnalyticsObject=o,e.ga=e.ga||function(){(e.ga.q=e.ga.q||[]).push(arguments)},e.ga.l=1*new Date,c=a.createElement(t),i=a.getElementsByTagName(t)[0],c.async=1,c.src="https://www.google-analytics.com/analytics.js",i.parentNode.insertBefore(c,i)}(window,document,"script",0,"ga"),ga("create","UA-64295674-3",""),ga("set","anonymizeIp",!0),ga("send","pageview","/doc"+window.location.pathname);var links=document.getElementsByTagName("a");if(Array.prototype.map.call(links,function(a){a.host!=document.location.host&&a.addEventListener("click",function(){var e=a.getAttribute("data-md-action")||"follow";ga("send","event","outbound",e,a.href)})}),document.forms.search){var query=document.forms.search.query;query.addEventListener("blur",function(){if(this.value){var e=document.location.pathname;ga("send","pageview",e+"?q="+this.value)}})}
diff --git a/debian/patches/debian/0010-remove-login.patch b/debian/patches/debian/0010-remove-login.patch
new file mode 100644
index 000..74b5e06
--- /dev/null
+++ b/

Bug#932194: Please add support to python3

2019-07-16 Thread Sakirnth Nagarasa
Package: python-vtk6
Version: 6.3.0+dfsg2-2

Hi,

Could you please add support to python3?

Thanks,

Saki


Bug#932195: RM: ko.tex-unfonts -- not used anymore, replaced by texlive-lang-korean, no rdepends

2019-07-16 Thread Changwoo Ryu
Package: ftp.debian.org
Severity: normal

I'm almost sure this package is not used anymore. CJKtex merged ko.tex
years ago (texlive-lang-korean package) and its legacy fonts are not
used in recent documents.

The current maintainer, A Lee, is not active anymore.



Bug#932196: Load legacy iptables module 'iptable_filter' on nftables system

2019-07-16 Thread Jérémie LEGRAND
Subject: Load legacy iptables module 'iptable_filter' on nftables system
Package: netfilter-persistent
Version: 1.0.11
Severity: minor
File: /usr/sbin/netfilter-persistent

Dear Maintainer,

When using 'netfilter-persistent save' to dump rules on disk, the kernel module 
'iptable_filter' is loaded.
But this is for the 'legacy' iptables. On Debian 10, they now use the 'nft' 
flavor.

This has the side effect to add a warning to each following 'iptables' command 
we type, adding at the end:
  # Warning: iptables-legacy tables present, use iptables-legacy to see them
on stderr.

The corresponding code is in 
/usr/share/netfilter-persistent/plugins.d/15-ip4tables
modprobe -b -q iptable_filter || true

You can test by typing:
iptables -L # no warning
modprobe -b -q iptable_filter
iptables -L # warning at the end

I think you can check for nft loaded modules before trying to load the 
iptable_filter, or at least
check if /proc/net/ip_tables_names file already exists. If yes, no need to load 
the module.


Best regards,



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

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

Versions of packages netfilter-persistent depends on:
ii  lsb-base  10.2019051400

netfilter-persistent recommends no packages.

Versions of packages netfilter-persistent suggests:
ii  iptables-persistent  1.0.11

-- no debconf information


Bug#932197: Please switch to Python 3

2019-07-16 Thread Thomas Goirand
Source: nipype
Version: 1.1.9-1
Severity: important

Hi,

I'd like to switch python-xvfbwrapper to Python 3 only, and noticed that
nipype only has Python 2 support. Python 2 is going to be removed from
Sid/Testing.

Please switch nipype to Python 3 only.

Cheers,

Thomas Goirand (zigo)



Bug#932019: dwz: Fail with Couldn't find DIE referenced by DW_OP_GNU_parameter_ref (mips arches only)

2019-07-16 Thread Matthias Klose
On 14.07.19 08:56, Christian Marillat wrote:
> Package: dwz
> Version: 0.12.20190711-1
> Severity: normal
> 
> Dear Maintainer,
> 
> Seems to be an old bug, reported upstream in 2012 :
> 
> https://www.sourceware.org/bugzilla/show_bug.cgi?id=14191
> 
> A patch is available in this red-hat bug report :
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=1507468

no, that's apparently different.

But it's now fixed upstream.



Bug#923322: plasma-browser-integration: Incorrect installation directory for chrome config file

2019-07-16 Thread Scarlett Gately Moore
maxy gave an ok for a MR but I am unclear exactly what needs to be done. I 
don't like the sound of tricky!
@mitya57 can you prepare this or point me to an example?
Thanks,
Scarlett

-- 
Scarlett Gately Moore ( Formerly Clark )
Software engineer @ Blue Systems
KDE Developer/Sysadmin
Debian Contributor / Developer in training.
IRC sgmoore

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


Bug#929982: chromium: stretch/updates security version won't display google's Oswald font.

2019-07-16 Thread Ben Wagner
This is actually an issue with FreeType 2.6.3.

The problem seen here was introduced with [[truetype] Another GX
sanity test.][1] in FreeType VER-2-6-2 and fixed with [[truetype] More
fixes for handling of GX deltas.][2] in FreeType VER-2-7. This will
affect Chromium and Firefox as they are using the [system FreeType
which on debian 9 appears to be based on 2.6.3][3]. This should not
affect Google Chrome since it ships its own version of FreeType.

To fix this issue the FreeType package maintainers should apply
[[truetype] More fixes for handling of GX deltas.][2] to FreeType from
2.6.2 to 2.6.5. This appears to cherry-pick cleanly onto VER-2-6-3,
and I've verified that doing so fixes this issue.


  [1]: 
https://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=052f6c5649f7a46e599742eb6f47fa91d090f77e
  [2]: 
https://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=4e659d7eadb2cb17c28f1c23ac77cebd7b7e3e33
  [3]: https://packages.debian.org/source/stretch/freetype
  [4]: https://savannah.nongnu.org/bugs/index.php?56601



Bug#932198: fusiondirectory does not bind to LDAP server after upgrade from stretch to buster

2019-07-16 Thread Robert Middleton
Package: fusiondirectory
Version: 1.2.3-4
Severity: normal

Dear Maintainer,

Upgrading from stretch to buster results in a broken fusiondirectory 
installation.  fusiondirectory fails to bind to the LDAP server.

The error that is reported is as follows:

```
Fatal error
FATAL: Error when connecting the LDAP. Server said 'Could not bind to 
cn=admin,dc=ldap,dc=example,dc=com ((unknown error code), while operating on '' 
using LDAP server 'ldap://localhost:389')'.

Please fix the above error and reload the page. 
```

I was able to get to the setup page by renaming the 
/etc/fusiondirectory/fusiondirectory.conf file, however when I get to the setup 
page for the LDAP connection and fill in the user information, attempting to 
bind as the user fails.

Note that installing on a clean system(which leads to bug #931959) does let 
fusiondirectory bind to the LDAP server without a problem, but only after 
running fusiondirectory-insert-schema -m /etc/ldap/schema/core-fd-conf.schema. 
This leads me to believe this problem is related to the upgrade procedure.

I possibly had an error earlier with not having the mbstring PHP module, due to 
not installing it for PHP7.3, however the setup did warn me about this.

Note that I also get the following error when attemping to read the config:

# fusiondirectory-setup --check-ldap --show-config
! Failed to bind to LDAP server: decode error 17<=>30 0 8  at 
/usr/share/perl5/Convert/ASN1/_decode.pm line 113.

This command works fine on the clean system when it is configured to read from 
the remote LDAP server.


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

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

Versions of packages fusiondirectory depends on:
ii  apache2 [httpd] 2.4.38-3
ii  debconf [debconf-2.0]   1.5.71
ii  fusiondirectory-smarty3-acl-render  1.2.3-4
ii  gettext 0.19.8.1-9
ii  javascript-common   11
ii  libarchive-extract-perl 0.80-1
ii  libcrypt-cbc-perl   2.33-2
ii  libfile-copy-recursive-perl 0.44-1
ii  libjs-prototype 1.7.1-3
ii  libjs-scriptaculous 1.9.0-2
ii  libnet-ldap-perl1:0.6500+dfsg-1
ii  libpath-class-perl  0.37-1
ii  libperl5.24 [libdigest-sha-perl]5.24.1-3+deb9u5
ii  libterm-readkey-perl2.38-1
ii  libxml-twig-perl1:3.50-1.1
ii  openssl 1.1.1c-1
ii  php 2:7.3+69
ii  php-cas 1.3.6-1
ii  php-curl2:7.3+69
ii  php-fpdf3:1.8.1.dfsg-2
ii  php-gd  2:7.3+69
ii  php-imagick 3.4.3-4.1
ii  php-imap2:7.3+69
ii  php-ldap2:7.3+69
ii  php-recode  2:7.3+69
ii  php7.0 [php]7.0.33-0+deb9u3
ii  php7.0-cli [php-cli]7.0.33-0+deb9u3
ii  php7.0-gd [php-gd]  7.0.33-0+deb9u3
ii  php7.0-imap [php-imap]  7.0.33-0+deb9u3
ii  php7.0-ldap [php-ldap]  7.0.33-0+deb9u3
ii  php7.0-mbstring [php-mbstring]  7.0.33-0+deb9u3
ii  php7.0-recode [php-recode]  7.0.33-0+deb9u3
ii  php7.3 [php]7.3.4-2
ii  php7.3-cli [php-cli]7.3.4-2
ii  php7.3-curl [php-curl]  7.3.4-2
ii  php7.3-gd [php-gd]  7.3.4-2
ii  php7.3-imap [php-imap]  7.3.4-2
ii  php7.3-ldap [php-ldap]  7.3.4-2
ii  php7.3-mbstring [php-mbstring]  7.3.4-2
ii  php7.3-recode [php-recode]  7.3.4-2
ii  schema2ldif 1.3-3
ii  smarty-gettext  1.6.1-1
ii  smarty3 3.1.33+20180830.1.3a78a21f+selfpack1-1

fusiondirectory recommends no packages.

Versions of packages fusiondirectory suggests:
pn  argonaut-server 
ii  fusiondirectory-schema  1.2.3-4
ii  slapd   2.4.47+dfsg-3

-- debconf information:
* fusiondirectory/upgrade-confirm: true
  fusiondirectory/upgrade-canceled:



Bug#932199: insserv: warning: could not find all dependencies for $portmap

2019-07-16 Thread Thorsten Glaser
Package: insserv
Version: 1.20.0-1
Severity: important

Upgrading my system:

[…]
Preparing to unpack .../107-insserv_1.20.0-1_x32.deb ...
Unpacking insserv (1.20.0-1) over (1.14.0-5.4) ...
[…]
etting up inetutils-syslogd (2:1.9.4-8) ...
Installing new version of config file /etc/init.d/inetutils-syslogd ...
insserv: warning: could not find all dependencies for $portmap
insserv: warning: could not find all dependencies for $portmap
Restarting system log daemon syslogd.
Stopping system log daemon: syslogd.
Starting system log daemon: syslogd.
Setting up libgnutls30:i386 (3.6.8-2) ...
[…]

And, indeed, I do not have portmap installed.

tglase@tglase:~ $ sudo fgrep -r \$portmap /etc/init.d/ 
/etc/init.d/umountnfs.sh:# Should-Stop:   $network $portmap nfs-common
/etc/init.d/mountnfs.sh:# Should-Start:  $network $portmap nfs-common  
udev-mtab
/etc/init.d/README:# Should-Start:  $portmap
/etc/init.d/README:# Should-Stop:   $portmap

/etc/init.d/mountnfs.sh is from initscripts (= 2.93-8).
Perhaps it ought to be moved to nfs-common or so? That
being said, nfs-common does not Depends on portmap either…

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages insserv depends on:
ii  libc6  2.28-10

insserv recommends no packages.

Versions of packages insserv suggests:
pn  bootchart2  

-- no debconf information


Bug#931629: nmu: rebuild packages for binutils 2.32.51.x

2019-07-16 Thread Matthias Klose
On 15.07.19 16:36, Paul Gevers wrote:
> Hi Matthias,
> 
> On 08-07-2019 14:57, Matthias Klose wrote:
>> Please binNUM these packages for the recent binutils upload to unstable:
>>
>> boinc-app-eah-brp 0.20170426+dfsg-10
>> naev 0.7.0-2
>> tulip 4.8.0dfsg-2
>> wcc 0.0.2+dfsg-3 (amd64 only)
> 
> boinc-app-eah-brp can't be rebuild (#887880).
> tulip can't be rebuild (#853688, filed by you).
> 
> binNMU'ed wcc and naev.
> 
> Thanks.
> 
> Just one request, can you enlighten me as to where these strict
> dependencies on libutils come from?

because of potential incompatibilities with new upstream versions, such that
binutils itself ftbfs when the soname is not bumped.   Note that binutils
doesn't provide a stable ABI and API for the shared libs, therefore the
recommendation to statically link with those libs if you need to.



Bug#688412: configuration error?

2019-07-16 Thread Matus UHLAR - fantomas

Hello,

does it make sense to use /etc/default/tmpfs when /tmp mount is configured
in fstab? I'd say use either one, not both.

I don't have objections if anyone wants to "fix" this in scripts though.

--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Depression is merely anger without enthusiasm.



Bug#932200: Heap Buffer Overflow in libmad0

2019-07-16 Thread Jordy
Package: libmad0

Version: latest


I found a security vulnerability in libmad, I could not contact the vendor so I 
figured I'd just send it to you guys as it's a dependency for a lot of packages 
(At Least 68).

A heap overflow or heap overrun is a type of buffer overflow that occurs in the 
heap data area. Heap overflows are exploitable in a different manner to that of 
stack-based overflows. Memory on the heap is dynamically allocated by the 
application at run-time and typically contains program data. Exploitation is 
performed by corrupting this data in specific ways to cause the application to 
overwrite internal structures such as linked list pointers. The canonical heap 
overflow technique overwrites dynamic memory allocation linkage (such as malloc 
meta data) and uses the resulting pointer exchange to overwrite a program 
function pointer.

An accidental overflow may result in data corruption or unexpected behavior by 
any process which uses the affected memory area.

A deliberate exploit may result in data at a specific location being altered in 
an arbitrary way, or in arbitrary code being executed

The vulnerability in this case takes place in the mad_bit_read() function in 
libmad. The issue was found whilst fuzzing the library. In the attachments you 
can find the reproducer and the ASAN crash log and the harness, on Ubuntu 
atleast 68 packages are dependant on libmad so I think the amount of affected 
packages will be similar on Debian.

Kind Regards,

Jordy Zomer#include 
#include 

#include "mad.h"

struct buffer {
unsigned char const *start;
unsigned long length;
};

static
enum mad_flow input(void *data,
struct mad_stream *stream)
{
struct buffer *buffer = (struct buffer*) data;

if (!buffer->length)
return MAD_FLOW_STOP;

mad_stream_buffer(stream, buffer->start, buffer->length);

buffer->length = 0;

return MAD_FLOW_CONTINUE;
}

extern "C" int LLVMFuzzerTestOneInput(const uint8_t *Data, size_t Size) {
struct buffer buffer;
struct mad_decoder decoder;

/* initialize our private message structure */

buffer.start  = Data;
buffer.length = Size;

  /* configure input, output, and error functions */

mad_decoder_init(&decoder, &buffer,
input, 0 /* header */,
0 /* filter */,
0 /* output */,
0, 0 /* message */);

  /* start decoding */

  mad_decoder_run(&decoder, MAD_DECODER_MODE_SYNC);

/* release the decoder */

mad_decoder_finish(&decoder);

return 0;
}


libmad-heap-buffer-overflow-c53-f36-c2d.repro
Description: Binary data
INFO: Seed: 977723447
INFO: Loaded 0 modules (0 guards): 
Loading corpus dir: /samples/
Loaded 1024/1222 files from /samples/
#0  READ units: 1222
#1222   INITED cov: 1305 bits: 7362 indir: 7 corp: 614/523Kb exec/s: 611 rss: 
98Mb
=
==19511==ERROR: AddressSanitizer: heap-buffer-overflow on address 
0x6174083c at pc 0x7f3b040c9c2e bp 0x7ffcf1a68cb0 sp 0x7ffcf1a68ca8
READ of size 1 at 0x6174083c thread T0
#0 0x7f3b040c9c2d in mad_bit_read (/usr/lib/libmad.so.0+0x7c2d)
#1 0x7f3b040f2f36 in II_samples (/usr/lib/libmad.so.0+0x30f36)
#2 0x7f3b040f1c53 in mad_layer_II (/usr/lib/libmad.so.0+0x2fc53)
#3 0x7f3b040d86c4 in mad_frame_decode (/usr/lib/libmad.so.0+0x166c4)
#4 0x7f3b040e6e4b in run_sync (/usr/lib/libmad.so.0+0x24e4b)
#5 0x7f3b040e5a9e in mad_decoder_run (/usr/lib/libmad.so.0+0x23a9e)
#6 0x50e2bd in LLVMFuzzerTestOneInput 
(/src/libmad-0.15.1b/libmad-fuzzer+0x50e2bd)
#7 0x4f85f4 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, 
unsigned long) /src/Fuzzer/FuzzerLoop.cpp:536:13
#8 0x4f87e4 in fuzzer::Fuzzer::RunOne(unsigned char const*, unsigned long) 
/src/Fuzzer/FuzzerLoop.cpp:488:3
#9 0x4f98ce in fuzzer::Fuzzer::MutateAndTestOne() 
/src/Fuzzer/FuzzerLoop.cpp:722:30
#10 0x4f9ae7 in fuzzer::Fuzzer::Loop() /src/Fuzzer/FuzzerLoop.cpp:755:5
#11 0x4f1ca4 in fuzzer::FuzzerDriver(int*, char***, int (*)(unsigned char 
const*, unsigned long)) /src/Fuzzer/FuzzerDriver.cpp:530:3
#12 0x4ef6f0 in main /src/Fuzzer/FuzzerMain.cpp:20:10
#13 0x7f3b02e4f82f in __libc_start_main 
(/lib/x86_64-linux-gnu/libc.so.6+0x2082f)
#14 0x41b258 in _start (/src/libmad-0.15.1b/libmad-fuzzer+0x41b258)

0x6174083c is located 0 bytes to the right of 700-byte region 
[0x61740580,0x6174083c)
allocated by thread T0 here:
#0 0x4ecad0 in operator new[](unsigned long) 
(/src/libmad-0.15.1b/libmad-fuzzer+0x4ecad0)
#1 0x4f8537 in fuzzer::Fuzzer::ExecuteCallback(unsigned char const*, 
unsigned long) /src/Fuzzer/FuzzerLoop.cpp:527:23

SUMMARY: AddressSanitizer: heap-buffer-overflow (/usr/lib/libmad.so.0+0x7c2d) 
in mad_bit_read
Shadow bytes around the buggy address:
  0x0c2e80b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
  0x0c2e80c0: 00 00 00 00 00 00 00 00 00 00 00

Bug#932012: Please upload backport for stretch

2019-07-16 Thread Felix Lechner
On Tue, Jul 16, 2019 at 6:34 AM gregor herrmann  wrote:
>
> So the .dsc refers to libio-async-loop-epoll-perl_0.20.orig.tar.gz
> and libio-async-loop-epoll-perl_0.20-1~bpo9+1.debian.tar.xz and both
> don't seem to exist on mentors.

This is a tiny package. I only did 'dch --bpo' and 'debuild'. Could
you try that in your git repo?

I confirmed it builds on stretch.



Bug#908745: libgtk3-perl: avoid using deprecated gdk_pixbuf_new_from_inline()

2019-07-16 Thread intrigeri
Hi Simon!

Simon McVittie:
> In Perl I think that would be spelled something like:

> sub Gtk3::Gdk::Pixbuf::new_from_data {
>   my ($class, $data, $colorspace, $has_alpha, $bits_per_sample, $width, 
> $height, $rowstride) = @_;
>   return Gtk3::Gdk::Pixbuf->new_from_bytes(GLib::Bytes->new($data),
>$colorspace, $has_alpha,
>$bits_per_sample, $width,
>$height, $rowstride);
> }

Thank you. I've built upon your work and submitted
https://gitlab.gnome.org/GNOME/perl-gtk3/merge_requests/2 upstream.

I don't feel confident enough to upload this change to Debian before
upstream reviews it.

Cheers,
-- 
intrigeri



Bug#688412: configuration error?

2019-07-16 Thread Thorsten Glaser
On Tue, 16 Jul 2019, Matus UHLAR - fantomas wrote:

> does it make sense to use /etc/default/tmpfs when /tmp mount is
> configured in fstab? I'd say use either one, not both.

I’ve only seen it in fstab in ancient systems, etch/lenny or so;
anything newer uses /etc/default/tmpfs.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**



Bug#932134: libossim1: Segmentation fault in ossimTiffProjectionFactory

2019-07-16 Thread Guillaume Pasero

  
  
Unfortunately, the bug is still present in 2.8.2, same backtrace.
I'll see if there is a workaround for OTB.
Regards,

On 7/15/19 9:01 PM, Sebastiaan
  Couwenberg wrote:


  We could try upgrading ossim to 2.8.2. maybe that contains a fix.

-- 
  

  
  
  Guillaume PASERO
Responsable technique
Business Unit ESPACE & GeoInformation -
  Département Payload Data & Applications

CS Systèmes d'Information
Parc de la Grande Plaine - 5, Rue Brindejonc des
Moulinais - BP 15872
31506 Toulouse Cedex 05 - FRANCE
+33 561 17 64 21 - guillaume.pas...@c-s.fr
  
  

  

  



Bug#932201: wine64 should also look for /usr/lib/wine/wineserver64 if WINESERVER is not set

2019-07-16 Thread Daniel Kahn Gillmor
Package: wine64
Version: 4.0-2
Severity: normal

wine64(1) says:

WINESERVER
  Specifies  the  path  and  name of the wineserver binary. If not
  set, Wine will try to load /usr/lib/wine/wineserver, and if this
  doesn't exist it will then look for a file named "wineserver" in
  the path and in a few other likely locations.

But wine64 only ships with /usr/lib/wine/wineserver64.

I'm finding that i need to set WINESERVER=/usr/lib/wine/wineserver64
in libgpg-error's debian/tests/windows (an autopkgtest where we ensure
that we can build a static windows executable against libgpg-error on
debian), otherwise i get "could not exec wineserver".

It seems like wine64 should be smart enough to try
/usr/lib/wine/wineserver64.

 (aside about the overall problem space of using wine in autopkgtest:
  i think if i installed the "wine" package, and then just invoked
  /usr/bin/wine directly, instead of wine64, it would work correctly
  for me, but the problem with that is that "wine" sends a warning to
  stderr about wanting wine32 installed upon every invocation, which
  isn't possible on a non-multiarch system (and all the continuous
  integration systems i've used thus far are non-multiarch).  And
  messages to stderr are indicators to autopkgtest that the test is a
  failure.  I could suppress the warning by setting WINEDEBUG=-all,
  but i *don't* want to suppress any other warnings that wine might
  produce.  So if you see a better way around this, so that i can use
  wine in autopkgtest more easily, please don't hesitate to suggest
  it)

--dkg



-- Package-specific info:
/usr/bin/wine points to /usr/bin/wine-stable.

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

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

Versions of packages wine64 depends on:
ii  libc62.28-10
ii  libwine  4.0-2

Versions of packages wine64 recommends:
ii  wine4.0-2
pn  wine32  

Versions of packages wine64 suggests:
pn  wine64-preloader  

Versions of packages wine64 is related to:
pn  fonts-wine  
ii  wine4.0-2
pn  wine32  
ii  wine64  4.0-2

-- no debconf information



Bug#688412: configuration error?

2019-07-16 Thread Matus UHLAR - fantomas

On Tue, 16 Jul 2019, Matus UHLAR - fantomas wrote:

does it make sense to use /etc/default/tmpfs when /tmp mount is
configured in fstab? I'd say use either one, not both.


On 16.07.19 16:43, Thorsten Glaser wrote:

I’ve only seen it in fstab in ancient systems, etch/lenny or so;
anything newer uses /etc/default/tmpfs.


IIRC people using systemd were advised to use fstab to manipulate /tmp
mount options.

--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
The early bird may get the worm, but the second mouse gets the cheese.



Bug#932000: In testing

2019-07-16 Thread Greg Hudson
Candidate patch here:

https://github.com/krb5/krb5/pull/954



Bug#929968: Add missing C_CAN module

2019-07-16 Thread Uwe Kleine-König
Control: tag -1 + pending

Hello,

I merged your PR and added a changelog entry for it.

Best regards
Uwe


signature.asc
Description: PGP signature


Bug#932208: RM: grib-api/1.28.0-2

2019-07-16 Thread Alastair McKinstry
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: rm

grib-api should be removed from Debian.
It is obsolete upstream, being replaced by eccodes (already in buster).

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

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



Bug#688412: configuration error?

2019-07-16 Thread Thorsten Glaser
On Tue, 16 Jul 2019, Matus UHLAR - fantomas wrote:

> IIRC people using systemd were advised to use fstab to manipulate /tmp
> mount options.

Yes, but systemd does not use /etc/default/tmpfs, so…

//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**



Bug#932209: [ALSA] alsa-state.service starts daemon due to wrong ConditionPathExists

2019-07-16 Thread sch0rsch

Package: alsa-utils
Version: 1.1.8-2

Expected behaviour:
- alsa-state.service starts, if state-daemon.conf exists.
- alsa-restore.service starts, if state-daemon.conf does NOT exist.

Actual behaviour:
- Both systemd units start if state-daemon.conf exists.
- So alsactl daemon is always started on boot and can only prevent this 
via "systemctl mask alsa-state" currently.


This does not match the explaining comments in both both systemd units 
and it does not match version 1.1.3-1 (current Stretch package), nor the 
source code, that was last changed 2017, so I could not open a pull 
request to fix: 
https://salsa.debian.org/alsa-team/alsa-utils/blob/debian/master/alsactl/alsa-state.service.in


I am not sure how this wrong code could find its way into 
Buster+Bullseye+Sid repos, but it did: 
https://deb.debian.org/debian/pool/main/a/alsa-utils/alsa-utils_1.1.8-2_amd64.deb



> systemctl cat alsa-state.service
# /lib/systemd/system/alsa-state.service

# Note that two different ALSA card state management schemes exist and they
# can be switched using a file exist check - /etc/alsa/state-daemon.conf .
#

[Unit]
Description=Manage Sound Card State (restore and store)
Documentation=man:alsactl(1)
ConditionPathExists=!/etc/alsa/state-daemon.conf
After=sysinit.target

[Service]
Type=simple
ExecStart=-/usr/sbin/alsactl -E HOME=/run/alsa -s -n 19 -c rdaemon
ExecStop=-/usr/sbin/alsactl -E HOME=/run/alsa -s kill save_and_quit

> systemctl cat alsa-restore.service
# /lib/systemd/system/alsa-restore.service
#
# Note that two different ALSA card state management schemes exist and they
# can be switched using a file exist check - /etc/alsa/state-daemon.conf .
#

[Unit]
Description=Save/Restore Sound Card State
Documentation=man:alsactl(1)
ConditionPathExists=!/etc/alsa/state-daemon.conf
ConditionPathExistsGlob=/dev/snd/control*
After=alsa-state.service

[Service]
Type=oneshot
RemainAfterExit=true
ExecStart=-/usr/sbin/alsactl -E HOME=/run/alsa restore
ExecStop=-/usr/sbin/alsactl -E HOME=/run/alsa store


Best regards



Bug#688412: configuration error?

2019-07-16 Thread Matus UHLAR - fantomas

On Tue, 16 Jul 2019, Matus UHLAR - fantomas wrote:

IIRC people using systemd were advised to use fstab to manipulate /tmp
mount options.


On 16.07.19 17:18, Thorsten Glaser wrote:

Yes, but systemd does not use /etc/default/tmpfs, so…


...which is exactly why I found it strange to have /tmp in fstab and yet
expect using /etc/default/tmpfs.

in case of /tmp in fstab, options should be in fstab too.

In case of systemd, /tmp should be in fstab (and /etc/default/tmpfs won't be
used)

--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Eagles may soar, but weasels don't get sucked into jet engines.



Bug#932184: pbuilder: ADDITIONAL_BUILDRESULTS handling might iterate over debug output

2019-07-16 Thread Thorsten Glaser
Michael Prokop dixit:

>helper function. The _find_additional_buildresults function outputs its
>logging on stdout as well though, so when "log.d" is executed (which
   ^^^
This is clearly a bug, stderr is for logging ;-)

bye,
//mirabilos
-- 
 ch: good, you corrected yourself. ppl tend to tweet such news
immediately, sth. like "grml devs seem to be buyable" dileks: we
_are_. if you throw enough money in our direction, things will happen
 everyone is buyable, it's just a matter of priceand now
comes [mira] and uses this as a signature ;0   -- they asked for it…



Bug#932012: Please upload backport for stretch

2019-07-16 Thread Felix Lechner
On Tue, Jul 16, 2019 at 6:34 AM gregor herrmann  wrote:
>
> So the .dsc refers to libio-async-loop-epoll-perl_0.20.orig.tar.gz
> and libio-async-loop-epoll-perl_0.20-1~bpo9+1.debian.tar.xz and both
> don't seem to exist on mentors.

I built and uploaded it again, this time from testing instead of
stretch. Can you please try again?



Bug#932210: libimage-exiftool-perl: Exiftool does not start

2019-07-16 Thread pierre
Package: libimage-exiftool-perl
Version: 11.16-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

Launch the program from cli

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

$ exiftool -v (or any other options)

   * What was the outcome of this action?

"Open" is not exported by the Image::ExifTool module
Can't continue after import errors at /usr/local/bin/exiftool line 33.
BEGIN failed--compilation aborted at /usr/local/bin/exiftool line 33.

   * What outcome did you expect instead?

exiftoo to work

   * Extra informations

Tried to reinstall exiftoo as well as perl but that did not solve the problem.
It was working before upgrade to buster.


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

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

Versions of packages libimage-exiftool-perl depends on:
ii  perl  5.28.1-6

Versions of packages libimage-exiftool-perl recommends:
ii  libarchive-zip-perl1.64-1
ii  libposix-strptime-perl 0.13-1+b5
ii  libunicode-linebreak-perl  0.0.20190101-1

libimage-exiftool-perl suggests no packages.

-- no debconf information



Bug#932210: libimage-exiftool-perl: Exiftool does not start

2019-07-16 Thread Phil Harvey
Line 33 of "exiftool" version 11.16 should be:

sub SigInt();

However, line 30 is:

use Image::ExifTool qw{:Public};

which may generate the observed message if "Open" is added to the list.

It looks like you are running a modified version of "exiftool", and not the 
distributed 11.16 version.

- Phil


Bug#932211: gedit: Stretch to Buster: cursor is gone

2019-07-16 Thread Martin-Éric Racine
Package: gedit
Version: 3.30.2-2
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Since upgrading to Buster, the cursor is no longer visible in gedit.

- -- Package-specific info:
Active plugins:
  - 'spell'
  -  'modelines'
  -  'filebrowser'
  -  'time'
  -  'docinfo'

No plugin installed in $HOME.

Module versions:
  pkg-config unavailable


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

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

Versions of packages gedit depends on:
ii  gedit-common   3.30.2-2
ii  gir1.2-glib-2.01.58.3-2
ii  gir1.2-gtk-3.0 3.24.5-1
ii  gir1.2-gtksource-3.0   3.24.9-2
ii  gir1.2-pango-1.0   1.42.4-6
ii  gir1.2-peas-1.01.22.0-4
ii  gsettings-desktop-schemas  3.28.1-1
ii  iso-codes  4.2-1
ii  libatk1.0-02.30.0-2
ii  libc6  2.28-10
ii  libcairo-gobject2  1.16.0-4
ii  libcairo2  1.16.0-4
ii  libenchant1c2a 1.6.0-11.1+b1
ii  libgdk-pixbuf2.0-0 2.38.1+dfsg-1
ii  libgirepository-1.0-1  1.58.3-2
ii  libglib2.0-0   2.58.3-2
ii  libgspell-1-1  1.6.1-2
ii  libgtk-3-0 3.24.5-1
ii  libgtksourceview-3.0-1 3.24.9-2
ii  libpango-1.0-0 1.42.4-6
ii  libpangocairo-1.0-01.42.4-6
ii  libpeas-1.0-0  1.22.0-4
ii  libx11-6   2:1.6.7-1
ii  libxml22.9.4+dfsg1-7+b3
ii  python33.7.3-1
ii  python3-gi 3.30.4-1
ii  python3-gi-cairo   3.30.4-1
ii  python3.7  3.7.3-2

Versions of packages gedit recommends:
ii  yelp3.31.90-1
ii  zenity  3.30.0-2

Versions of packages gedit suggests:
ii  gedit-plugins  3.30.1-3

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAl0t9OAACgkQrh+Cd8S0
17aB3RAAudBGm0pUNS4XO+RT9PYCGGfYrBM/Msx4L3fE+UTM9+8yrcGGaiuTWJzl
z/YzXt2WZtaJ0IF578QWoVMrDOBvv6Mx08Zfd9X4aUEBQHt0O9scTVrApLs+/0oL
jw3lzFbBv+9rXzHJPysSlxAyqyYyymR6xeb12PfCOsNDBC2ffe9gghDmYojm/wBG
fdp5pYHF+UznzMLfV9hoynU6bmZl153TF4tXzLx9VKCq/IJ5KSSHIurBqRMIXarF
gnJFttDrSq9l6nLGEhNurDbS2e0HiZnGc+9EBVb0u/clBCpFeDJrDdebO3WOrPzj
r4GEbP3b3HuWON7qZ4uGFQv0/EJSKln8AHG2A6daxLwSBO/C87sfWa6SqaWX+G1l
wNLtLozuyfGteqlj4krHj4aZXMR69f6Q0mNUbIcOMsNzdHOYQlgRNrR7wgvXd0QP
86dPMtzW9HYhkDref/0Q+CyqlIVfBlGNZAf3bPFVDvr8u0jLFgi/EDnZwOW4m5Wr
e7Lew26DVfJHSvCjYsJ7WBa9B1y+pNs2JF24cGLRpJ6oNmK+zXLTlf1eC1nf69du
zcLVPTNS64PLcr8Pb6OSoK+yOTWtxW5+eBQH5awIaA8sCXJd5GVTNZOb+hb3xIaA
46ZzsS/2ZC6tBIPa1vRMMdLGlajGrii0CCGLkGDi/USQ0Qs15SA=
=QJUE
-END PGP SIGNATURE-



Bug#932143: mariadb-10.3.16 migration excuses indicate need for manual cleanup?

2019-07-16 Thread Mattia Rizzolo
Control: tag -1 moreinfo

On Mon, Jul 15, 2019 at 11:18:27PM +0300, Otto Kekäläinen wrote:
> Currently the excuses at
> https://qa.debian.org/excuses.php?package=mariadb-10.3 state:
> 
> old binaries left on amd64: libmariadbclient18 (from 1:10.3.13-1) (but
> ignoring cruft, so nevermind)

> This has been there for many months now and does not seem to clean up
> the cruft automatically (or remove the error message).
> 
> Could the ftp-masters please take a look and manually resolve it?

No, it's not something for ftp-master to manually kick.

You can check with `dak rm` how there are still reverse dependencies
using it.  Fix them and the package will be removed completely.

Checking reverse dependencies...
# Broken Depends:
amarok: amarok
dballe: libdballe7
mosquitto-auth-plugin: mosquitto-auth-plugin
mysql++: libmysql++3v5
mysql-workbench: mysql-workbench
opensips: opensips-lua-module
  opensips-mysql-module
quickfix: libquickfix16 [i386]
stardict: stardict-tools

Dependency problem found.


(yes, they are all broken packages not in testing.)

-- 
regards,
Mattia Rizzolo

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


signature.asc
Description: PGP signature


Bug#932149: Early segfault in steal-ctty on Xen DomU install

2019-07-16 Thread Martin Samuelsson

Control: retitle -1 Buster install requires more ram than documented

If increasing the memory allocation for the target machine from 512MB to 
1024MB the error goes away.


This is unexpected since the section 3.4 of Buster's Installation Guide for 
amd64 states that the requirement of an installed system is 256MB, and that 
the actual installer should require only 170MB. Section 6.3.1.1 also states 
"One of the first things debian-installer does, is to check available 
memory."


Fair enough though, there is conflicting information in section 2.5, Memory 
and Disk Space Requirements, where the figure is 550MB and no claim is made 
there that d-i attempts to detect insufficient available memory.


Attempting to boot with kernel parameter lowmem set to 1 or 2 makes no 
difference. Insufficient ram results in seg fault and errors about missing 
console files regardless of lowmem's value.


Ideally this should be addressed both with updates to the documentation and 
with error handling notifying the user that resource shortage is causing the 
problems.


Maybe a pragmatic fix could be to check for available ram early and halt the 
installation process with a clear message if needed?

--
/Martin



Bug#875894: #875894 Fix

2019-07-16 Thread Tim Dufrane
Appears to be from lack of null checking on the pst_file object. Quick and
dirty fix:

--- a/src/libpst.c  Wed Aug 01 08:49:01 2018 -0700
+++ b/src/libpst.c  Tue Jul 16 12:16:41 2019 -0400
@@ -409,6 +409,11 @@

 int pst_close(pst_file *pf) {
 DEBUG_ENT("pst_close");
+if (pf == NULL) {
+DEBUG_RET();
+return 0;
+}
+
 if (!pf->fp) {
 DEBUG_RET();
 return 0;

Anyone know how I can submit changes to the main HG repository? Don't see
any contact info around. Or if someone could submit these changes on my
behalf that would be great.


Bug#928032: Default configuration for USBGuard

2019-07-16 Thread Birger Schacht
Hi,

On 7/16/19 12:47 PM, Antoine Beaupré wrote:
> On 2019-07-15 11:09:55, Thiébaud Weksteen wrote:

>> On generate-policy vs PresentDevicePolicy, I would argue that the
>> simplest option is the best. By running generate-policy, you are
>> parsing all current devices, generating rules and then applying these
>> rules. There might be (unlikely) a bug in the rule generation which
>> ends up blocking a device (e.g., missing attribute or so). The
>> PresentDevicePolicy=keep is just a simpler alternative.
>>
>> It might be useful to write down some Debian-specific documentation on
>> how to setup the daemon to be more restrictive? The wiki might be a
>> good place for that?
> 
> Problem with PresentDevicePolicy=keep is that it might break on reboot
> or setup changes (e.g. moving laptop from office to home).

You mean that usbguard doesn't honor the rules when it is started on
boot? That would be my fear- because the default from the kernel is to
allow devices and if we set PresentDevicePolicy to keep, it doesn't look
at the rules defined in the rules file at boot time. That means if I
forbid a device, after the next reboot the device would be allowed.

cheers,
Birger



Bug#932162: Tested with GDM

2019-07-16 Thread Henry J. Douglas
Installed gdm3 and set it as default.

Everything works and I can reach the Xfce desktop.

Issue seems related to LightDM.

Em ter, 16 de jul de 2019 09:21, Henry J. Douglas 
escreveu:

> Booted with nomodeset i915.modeset=0 and here are the results.
>
> No display either. LightDM doesn't start, Xorg doesn't start.
>


Bug#932210: Fwd: Bug#932210: libimage-exiftool-perl: Exiftool does not start

2019-07-16 Thread Phil Harvey
> From: Pierre AUSSAGUEL 
> Subject: Re: Bug#932210: libimage-exiftool-perl: Exiftool does not start
> Date: July 16, 2019 at 12:26:43 PM EDT
> To: Phil Harvey 
> 
> Le 16/07/2019 à 18:14, Phil Harvey a écrit :
>> Somehow you've got a very old version (9.76) in /usr/local/bin
>> This explains the problem.  Delete this old version and replace it with the 
>> most current one (if it doesn't already exist somewhere else in the path).
> 
> # rm /usr/local/bin/exiftool
> # apt reinstall libimage-exiftool-perl
> # exiftool -v
> bash: /usr/local/bin/exiftool: Aucun fichier ou dossier de ce type
> 
> I dont understand ... isn't libimage-exiftool-perl supposed to provide the 
> file ?
> 
> I solved the problem by placing a symlink in /usr/local/bin from 
> /usr/bin/exiftool
> 
> Thank for your help
> 
> I think the package should be modified to remove the old file and make the 
> symlink or any other better solution.
> 



Bug#932212: squid: Squid negotiate wrapper crashes under load

2019-07-16 Thread James Zuelow
Package: squid
Version: 4.6-1
Severity: important

Dear Maintainer,

We maintain a pair of Squid proxies running on Debian, in a failover
setup using ucarp.  These proxies are configured to use the negotiate
wrapper for proxy authentication, using Kerberos with a failover to
NTLM.

We upgraded the secondary from Stretch to Buster and tested
functionality - everything seemed to work, but unfortunately we did not
stress test it enough as we only used a small group of IT staff to test
functionality.

After upgrading the primary, users started seeing authentication popups,
and Internet access through the proxy slowed to a crawl.  Initial
investigation showed that there was a lack of file descriptors.  After 
resolving that issue, the problem with the proxies remained.  Searching
the cache log showed numerous “Too few negotiateauthenticator processes are 
running”
events in the log.  It appears that when the proxy is under load -
between 80 and 100 requests per second at our site - the negotiate
wrapper crashes, sometimes as rapidly as every 15 seconds.

Doing a quick Google, I found this:  
https://github.com/diladele/websafety-issues/issues/1141

Which refers to this:  https://bugs.squid-cache.org/show_bug.cgi?id=4936

The second link refers to Squid bug 4936.  Based on the dates of the
Squid bug report, I guessed that 4936 is present in Buster's version of
Squid.  After a brief discussion on the squid users mailing list 
( 
http://squid-web-proxy-cache.1019090.n4.nabble.com/Debian-Buster-Squid-4-6-1-amd64-quot-Too-few-negotiateauthenticator-processes-are-running-quot-td4687976.html
 )
it appears that it is.

Right now we are working around the issue with an http_access allow all
directive that pre-empts our authentication.  However, without
authentication we also lose the ability to track individual user
activity on the Internet.  This is an important organizational goal.

Also based on the dates of the Squid bug fix and the information from
the Debian package tracker, I believe that 4.6-2 in Sid would be
affected as well.

Thank you!

James 

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

Kernel: Linux 4.19.0-5-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages squid depends on:
ii  adduser  3.118
ii  libc62.28-10
ii  libcap2  1:2.25-2
ii  libcom-err2  1.44.5-1
ii  libdb5.3 5.3.28+dfsg1-0.5
ii  libdbi-perl  1.642-1+b1
ii  libecap3 1.0.1-3.2
ii  libexpat12.2.6-2
ii  libgcc1  1:8.3.0-6
ii  libgnutls30  3.6.7-4
ii  libgssapi-krb5-2 1.17-3
ii  libkrb5-31.17-3
ii  libldap-2.4-22.4.47+dfsg-3
ii  libltdl7 2.4.6-9
ii  libnetfilter-conntrack3  1.0.7-1
ii  libnettle6   3.4.1-1
ii  libpam0g 1.3.1-5
ii  libsasl2-2   2.1.27+dfsg-1
ii  libstdc++6   8.3.0-6
ii  libxml2  2.9.4+dfsg1-7+b3
ii  logrotate3.14.0-4
ii  lsb-base 10.2019051400
ii  netbase  5.6
ii  squid-common 4.6-1

Versions of packages squid recommends:
ii  ca-certificates  20190110
ii  libcap2-bin  1:2.25-2

Versions of packages squid suggests:
pn  resolvconf   
ii  smbclient2:4.9.5+dfsg-5
ii  squid-cgi4.6-1
pn  squid-purge  
ii  squidclient  4.6-1
pn  ufw  
ii  winbind  2:4.9.5+dfsg-5

-- Configuration Files:
/etc/init.d/squid changed:
NAME=squid
DESC="Squid HTTP Proxy"
DAEMON=/usr/sbin/squid
PIDFILE=/var/run/$NAME.pid
CONFIG=/etc/squid/squid.conf
SQUID_ARGS="-YC -f $CONFIG"
[ ! -f /etc/default/squid ] || . /etc/default/squid
. /lib/lsb/init-functions
PATH=/bin:/usr/bin:/sbin:/usr/sbin
[ -x $DAEMON ] || exit 0
ulimit -n 65535
find_cache_dir () {
w=" " # space tab
res=`$DAEMON -k parse -f $CONFIG 2>&1 |
grep "Processing:" |
sed s/.*Processing:\ // |
sed -ne '

s/^['"$w"']*'$1'['"$w"']\+[^'"$w"']\+['"$w"']\+\([^'"$w"']\+\).*$/\1/p;
t end;
d;
:end q'`
[ -n "$res" ] || res=$2
echo "$res"
}
grepconf () {
w=" " # space tab
res=`$DAEMON -k parse -f $CONFIG 2>&1 |
grep "Processing:" |
sed s/.*Processing:\ // |
sed -ne '
s/^['"$w"']*'$1'['"$w"']\+\([^'"$w"']\+\).*$/\1/p;
t end;
d;
:end q'`
[ -n "$res" ] || res=$2
echo "$res"
}
create_run_

Bug#932200: Heap Buffer Overflow in libmad0

2019-07-16 Thread Kurt Roeckx
On Tue, Jul 16, 2019 at 10:25:20AM -0400, Jordy wrote:
> Package: libmad0
> 
> 
> I found a security vulnerability in libmad, I could not contact the vendor so 
> I figured I'd just send it to you guys as it's a dependency for a lot of 
> packages (At Least 68).

Have you actually tried this with the latest version of libmad
shipped in Debian? The upstream version contains various bugs that
have a CVE assigned that have been fixed in Debian.

After the last fix I did, I also ran a fuzzer on it myzelf for a
few weeks that didn't find anything with code that looks a lot
like your code.


Kurt



Bug#932213: blhc: Avoid triggering warnings for CC_FOR_BUILD compilations

2019-07-16 Thread Daniel Kahn Gillmor
Package: blhc
Version: 0.09-1
Severity: wishlist
Control: -1 affects + src:libgpg-error src:libassuan

libgpg-error and libassuan both use $(CC_FOR_BUILD) to compile helper
tools during build, like header generators.

Those helper programs are never redistributed, and probably do not
need all the hardening options.

Nonetheless, blhc reports them as dpkg-buildflags-missing.  see, for
example:

https://qa.debian.org/bls/packages/l/libgpg-error.html

which warns about two helpers, :

CFLAGS missing (-fstack-protector-strong -Wformat -Werror=format-security): gcc 
-g -O0 -I. -I../../src -o mkheader ../../src/mkheader.c
LDFLAGS missing (-Wl,-z,relro -Wl,-z,now): gcc -g -O0 -I. -I../../src -o 
mkheader ../../src/mkheader.c
CFLAGS missing (-g -fstack-protector-strong -Wformat -Werror=format-security): 
gcc -I. -I../../src -o mkerrcodes ../../src/mkerrcodes.c
LDFLAGS missing (-Wl,-z,relro -Wl,-z,now): gcc -I. -I../../src -o mkerrcodes 
../../src/mkerrcodes.c

We don't want to simply add all the standard buildflags to those
invocations, because if we do, we'll break the ability to
cross-compile these packages because their helper tools will likely
break.

It's possible to change the source packages by stuffing some complex
build-arch-specific buildflags down into these invocations, using
something like:


CFLAGS_FOR_BUILD=$(shell dpkg-architecture -f -a$DEB_BUILD_ARCH -c 
dpkg-buildflags --get CFLAGS)
LDFLAGS_FOR_BUILD=$(shell dpkg-architecture -f -a$DEB_BUILD_ARCH -c 
dpkg-buildflags --get CFLAGS)

And then ensuring that CFLAGS_FOR_BUILD gets passed through in the
upstream Makefile.

But this is all pretty complicated and i'm not convinced that it is
worthwhile.  It might make more sense for blhc to be able to detect
and skip these local helper tools.

--dkg

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

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

Versions of packages blhc depends on:
ii  libdpkg-perl  1.19.7

blhc recommends no packages.

blhc suggests no packages.

-- no debconf information



Bug#888479: tcsh 6.21 fixes this bug

2019-07-16 Thread Thomas Lange


Package: tcsh
Version: 6.21.00-1
Fixed: 6.21.00-1


Currently I'm building the next tcsh version, which fixed this bug.

-- 
regards Thomas



Bug#932214: wireshark: TCP statistics bad (duration, export)

2019-07-16 Thread Philipp Marek
Package: wireshark
Version: 2.6.9-1
Severity: minor

I've got a capture file going 1031 seconds, 2.7GB.

When running the TCP connection statistics and sorting by "duration", I get 
different answers; once I got 1031 (as expected), after a wireshark restart 
with the same file I only got 820 or so.

Once I tried clicking "limit to display filter" (no filter was set!),  that
had the effect of recalculating and giving a different result.


Furthermore, checking "absolute time" isn't honored in the CSV export;  the
header field correctly says "Abs time",  but the numbers are still relative
to the beginning (ie. decimal numbers >=0, instead of 12:01:55 etc.).


I got a message that a 3.0.2 package is NEW (incoming), but I couldn't 
download that anywhere to test. Will do as soon as I see it.


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

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

Versions of packages wireshark depends on:
ii  wireshark-qt  2.6.8-1.1

wireshark recommends no packages.

wireshark suggests no packages.

-- no debconf information

-- 



Bug#932215: lintian: wrong exit code if specified profile does not exist

2019-07-16 Thread Michael Prokop
Package: lintian
Version: 2.16.0
Severity: normal

Hi,

STR:

| % lintian --profile doesnotexist .
| Cannot find profile doesnotexist (in /usr/share/lintian/profiles) at 
/usr/share/perl5/Lintian/Profile.pm line 144.
| Lintian::Profile::new("Lintian::Profile", "doesnotexist", 
ARRAY(0x55e94cae1aa8), HASH(0x55e94cc9e2f0)) called at /usr/bin/lintian line 215
| dplint::load_profile("doesnotexist") called at 
/usr/share/lintian/commands/lintian.pm line 1432
| main::load_profile_and_configure_tags() called at 
/usr/share/lintian/commands/lintian.pm line 650
| main::main() called at /usr/bin/lintian line 46
| eval {...} called at /usr/bin/lintian line 46
| main::__ANON__("/usr/share/lintian/commands/lintian.pm") called at 
/usr/bin/lintian line 114
| dplint::run_tool("/usr/bin/lintian", "lintian") called at 
/usr/bin/lintian line 290
| dplint::main() called at /usr/bin/lintian line 359
| % echo $?
| 255

Whereas the manual page says that lintian returns with exit code 2
on run-time errors:

| % man lintian | less -p "EXIT STATUS"
| EXIT STATUS
|0   No policy violations or major errors detected.  (There may have 
been warnings, though.)
|
|1   Policy violations or major errors detected.
|
|2   Lintian run-time error. An error message is sent to stderr.

Maybe a non-existing profile doesn't count as run-time error(?),
but if so this might be worth mentioning in the documentation.
(At least it was non-obvious for someone contributing to
jenkins-debian-glue as well as myself when debugging this.)

Thanks for consideration!

regards
-mika-



Bug#932216: ITP: bidict -- Efficient, Pythonic bidirectional map implementation and related functionality

2019-07-16 Thread William Grzybowski
Package: wnpp
Severity: wishlist
Owner: William Grzybowski 

* Package name: bidict
  Version : 0.18.0
  Upstream Author : Joshua Bronson 
* URL : https://bidict.readthedocs.io/
* License : MPL-2.0
  Programming Lang: Python
  Description : Efficient, Pythonic bidirectional map implementation and
related functionality

Bidict:
- is in use by several teams at Google, Venmo, CERN, Bank of America Merrill
Lynch, Bloomberg, Two Sigma, and others
- has carefully designed APIs for safety, simplicity, flexibility, and
ergonomics
- is CPython-, PyPy-, Python 2-, and Python 3-compatible
- has extensive test coverage (including property-based tests an d benchmarks)
run continuously on all supported Python versions and OSes
- integrates natively with Python’s collections interfaces
is implemented in concise, well-factored, well-documented pure Python that
leverages a number of advanced language features

It can be used in many applications.
I plan to maintain it within DPMT.


Bug#559867: squirrel-sql packaging

2019-07-16 Thread Thorsten Glaser
Hi Joseph,

> Are you still working on packaging squirrel-sql for Debian?

I have a working package, but just before uploading it, the
version of a dependency in Debian was *again* replaced by an
incompatible one.

I’ll check my work laptop for the last state, perhaps it can
be made to work.

Thanks for the reminder,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

**

Mit der tarent Academy bieten wir auch Trainings und Schulungen in den
Bereichen Softwareentwicklung, Agiles Arbeiten und Zukunftstechnologien an.

Besuchen Sie uns auf www.tarent.de/academy. Wir freuen uns auf Ihren Kontakt.

**



  1   2   3   >