Bug#812746: linux-image-4.3.0-0.bpo.1-amd64: r8169 suspend to ram regression: rtl_counters_cond == 1

[Jens Thiele]

Package: src:linux
Version: 4.3.3-7~bpo8+1
Severity: normal

Dear Maintainer,

after suspend to ram there are lots of error messages from the r8169
module and there are some strange side-effects (multiload_applet
produces 100% cpu load trying to read network interface statistics ...)

as workaround one can ifdown eth0 ; ifup eth0

This did not happen with debian kernels 3.16 and 4.2

-- Package-specific info:
** Version:
Linux version 4.3.0-0.bpo.1-amd64 (debian-ker...@lists.debian.org) (gcc version 
4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.3.3-7~bpo8+1 (2016-01-19)

** Command line:
BOOT_IMAGE=/vmlinuz-4.3.0-0.bpo.1-amd64 root=/dev/mapper/vgcrypt-root ro quiet

** Not tainted

** Kernel log:
[87191.684889] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87191.711031] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87191.737560] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87191.764204] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87191.790541] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87191.817158] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87191.844254] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87191.871205] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87191.898666] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87192.607134] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87192.633512] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87192.659716] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87192.685914] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87192.712076] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87192.738680] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87192.765161] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87192.791691] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87192.818177] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87192.844925] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87192.871450] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87192.898064] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87193.056904] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87193.654671] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87193.731372] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87193.809806] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87193.890007] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87193.960441] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87193.998441] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87194.026292] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87194.052599] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87194.079552] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87194.107711] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87194.134736] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87194.161505] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87194.607960] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87194.63] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87194.660696] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87194.686992] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87194.713216] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87194.739487] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87194.766093] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87194.792401] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87194.818772] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87194.845632] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87194.873207] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87194.899828] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87195.609418] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87195.636005] r8169 :02:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, 
delay: 10).
[87195.662384] r8169 

Bug#810968: [debian-mysql] Bug#810968: mariadb-server-10.0: Logrotate exists 1 if a non-debian mysqld is running (e.g. containerized mysqld)

[Otto Kekäläinen]

> 2) Check the parent process id being 1
>In this case parent of the parent because of mysqld_safe
># test $(ps -o ppid= -p $(ps -o ppid= -p $PID)) -eq 1
>This would work in most cases I can think of. mysqld run by a user
>or a container would not be started by the init. But seems like a
>rather complex solution to a fairly simple problem.

Option 2 seems OK. Alternatively we could check processed owned by user 'mysql'.

Yes, the solution might be a bit complex, but I am fine with it as
long as the bash code is well documented and as clean as possible, so
that potential regressions/bugs in future are easy to track down and
new people are confident in tweaking the code. Try avoiding long
oneliners and short-cut code style (to the extend possible, it is
after all bash scripting).

Bug#650601: libpng is ready for transtion

[Cyril Brulebois]

Tobias Frost  (2016-01-25):
> Dear release-team,
> 
> Now that all NMUs are in DELAYED for all fixables.
> I think we are ready to throw the switch. 

You haven't answered <20160106232316.ga28...@mraw.org>.

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#650601: libpng is ready for transtion

[Cyril Brulebois]

Aníbal Monsalve Salazar  (2016-01-26):
> On Tue, 2016-01-26 10:23:13 +0100, Tobias Frost wrote:
> > this is a question for you:
> >
> > https://lists.debian.org/debian-devel/2016/01/msg00248.html
> >
> > {quote}
> > Speaking of this particular udeb, I've just spotted libpng16-16-udeb has
> > a Conflicts against libpng12-0-udeb. I'm not sure why, and the changelog
> > doesn't seem to explain either. libpng16-16 and libpng12-0 seems to be
> > co-installable, so I'm not sure why their respective udebs shouldn't be.
> > {/quote}
> 
> The Conflicts against libpng12-0-udeb can be removed.

Looks fair on principle, thanks.

Has anyone tested a debian installer build where some packages were
built against libpng12-0-udeb and some other against libpng16-16-udeb?
Does that work? Or are we looking at a giant transition where everything
must switch to libpng16 at once?

Mraw,
KiBi.


signature.asc
Description: Digital signature

Bug#812749: RFA: magic -- VLSI layout tool

[stigge]

Package: wnpp
Severity: normal

I'm not regularly using this package. Therefore, looking for a new maintainer. 
Upstream releases regularly.

Bug#784688: Thousands of "xen:balloon: Cannot add additional memory (-17) messages" despite dom0 ballooning disabled

[Ian Campbell]

On Mon, 2016-01-25 at 20:36 +0200, KSB wrote:
> > Do you have a package version which you know to be good? How confident
> > are
> > you that it is ok (sometimes the problem is intermittent)?
> > 
> > Lastly, is there any chance you upgraded the Xen packages at the same
> > time?
> > I'm starting to wonder if maybe this is not a kernel issue.
> > 
> Sorry, but there is chance, sadly.

This is actually useful, because it shows that the issue occurs even with
Xen 4.6, which I think rules out a Xen side issue (otherwise we'd have had
lots more reports from 4.4 through to 4.6) and points to a kernel side
issue.

> But I checked logs more thoroughly and found it even on more recent
> kernels:
> 1) Lot of messages on 3.14-2-amd64 with xen-4.6, 13 domU's.

Just to be clear, "Lots" here means "hundreds or thousands"? I think it is
expected to see one or two around the time a VM is started or stopped, so
with 13 domUs a couple of dozen messages wouldn't seem out of line to me.

> 2) 4.3.0-1-amd64 xen-4.6, only two messages shortly after boot, only 1 
> domU running:
> [   12.473778] xen:balloon: Cannot add additional memory (-17)
> [   21.673298] xen:balloon: Cannot add additional memory (-17)
> uptime 17 days.
> 
> Previous on same machine was 4.2.0-1-amd64 with more (-17)'s

Was it running xen-4.6 when it was running 4.2.0 or was that also older?

Also 4.2.0-1-amd64 here (and all the other numbers you gave) is the ABI,
not the package version. The package versions is either in dpkg or you can
find it in /proc/version:

Linux version 4.1.0-2-amd64 (debian-ker...@lists.debian.org) (gcc version 4.9.3 
(Debian 4.9.3-3) ) #1 SMP Debian 4.1.6-1 (2015-08-23)
  ^^^ABI^^^ 
  ^^^VERSION

> 3) 4.3.0-1-amd64, one month, several reboots, average 4 domU's, and no 
> messages

Any idea which Xen?

> 4) 3.16.0-4-amd64, xen-4.1, 22 domU's, uptime 188 days, in last month I 
> see only
> Jan 7 14:12:08
> Jan 7 14:12:08
> Jan 7 14:12:08
> Jan 7 14:12:08
> Jan 7 14:27:47
> Jan 7 14:27:47
> Jan 7 14:27:47
> Jan 7 14:27:48
> and this is roughly the time last machine was created(started).
> 
> 
> 

Bug#807200: freefem++: diff for NMU version 3.38.1-1.1

[Mattia Rizzolo]

Control: tags 807200 + pending

Dear maintainer,

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

Regards.

-- 
regards,
Mattia Rizzolo

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

 changelog |   10 ++
 control   |2 +-
 2 files changed, 11 insertions(+), 1 deletion(-)

diff -Nru freefem++-3.38.1/debian/changelog freefem++-3.38.1/debian/changelog
--- freefem++-3.38.1/debian/changelog	2015-09-01 21:16:58.0 +
+++ freefem++-3.38.1/debian/changelog	2016-01-26 11:13:59.0 +
@@ -1,3 +1,13 @@
+freefem++ (3.38.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Bas Couwenberg ]
+  * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev.
+Closes: #807200
+
+ -- Mattia Rizzolo   Tue, 26 Jan 2016 11:13:42 +
+
 freefem++ (3.38.1-1) unstable; urgency=medium
 
   * Imported Upstream version 3.38.1 (Closes: #793237)
diff -Nru freefem++-3.38.1/debian/control freefem++-3.38.1/debian/control
--- freefem++-3.38.1/debian/control	2015-08-30 22:41:24.0 +
+++ freefem++-3.38.1/debian/control	2016-01-26 11:13:40.0 +
@@ -10,7 +10,7 @@
  libxpm-dev, libmumps-scotch-dev, libmumps-ptscotch-dev,
  libfltk1.3-dev | libfltk-dev, freeglut3-dev, ghostscript, imagemagick,
  texlive, texlive-extra-utils, texlive-latex-extra, texlive-font-utils, 
- libfftw3-dev, libgsl0-dev,
+ libfftw3-dev, libgsl-dev,
  libhypre-dev, 
  libarpack2-dev, libsuitesparse-dev,
  libmumps-dev, libblacs-mpi-dev, libscalapack-mpi-dev,


signature.asc
Description: PGP signature

Bug#812745: ruby-fog-xenserver and ruby-fog: error when trying to install together

[Ralf Treinen]

Package: ruby-fog,ruby-fog-xenserver
Version: ruby-fog/1.34.0-2
Version: ruby-fog-xenserver/0.2.3-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-01-26
Architecture: amd64
Distribution: sid

Hi,

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



Extracting templates from packages: 55%
Extracting templates from packages: 100%
Preconfiguring packages ...
Selecting previously unselected package libyaml-0-2:amd64.
(Reading database ... 10941 files and directories currently installed.)
Preparing to unpack .../libyaml-0-2_0.1.6-3_amd64.deb ...
Unpacking libyaml-0-2:amd64 (0.1.6-3) ...
Selecting previously unselected package gcc-5-base:amd64.
Preparing to unpack .../gcc-5-base_5.3.1-7_amd64.deb ...
Unpacking gcc-5-base:amd64 (5.3.1-7) ...
Setting up gcc-5-base:amd64 (5.3.1-7) ...
(Reading database ... 10955 files and directories currently installed.)
Preparing to unpack .../libstdc++6_5.3.1-7_amd64.deb ...
Unpacking libstdc++6:amd64 (5.3.1-7) over (4.8.2-19) ...
Processing triggers for libc-bin (2.21-7) ...
Setting up libstdc++6:amd64 (5.3.1-7) ...
Processing triggers for libc-bin (2.21-7) ...
Selecting previously unselected package libssl1.0.2:amd64.
(Reading database ... 10969 files and directories currently installed.)
Preparing to unpack .../libssl1.0.2_1.0.2e-1_amd64.deb ...
Unpacking libssl1.0.2:amd64 (1.0.2e-1) ...
Selecting previously unselected package libgcrypt20:amd64.
Preparing to unpack .../libgcrypt20_1.6.4-5_amd64.deb ...
Unpacking libgcrypt20:amd64 (1.6.4-5) ...
Selecting previously unselected package libicu55:amd64.
Preparing to unpack .../libicu55_55.1-7_amd64.deb ...
Unpacking libicu55:amd64 (55.1-7) ...
Selecting previously unselected package libxml2:amd64.
Preparing to unpack .../libxml2_2.9.3+dfsg1-1_amd64.deb ...
Unpacking libxml2:amd64 (2.9.3+dfsg1-1) ...
Selecting previously unselected package openssl.
Preparing to unpack .../openssl_1.0.2e-1_amd64.deb ...
Unpacking openssl (1.0.2e-1) ...
Selecting previously unselected package ca-certificates.
Preparing to unpack .../ca-certificates_20160104_all.deb ...
Unpacking ca-certificates (20160104) ...
Selecting previously unselected package libffi6:amd64.
Preparing to unpack .../libffi6_3.2.1-4_amd64.deb ...
Unpacking libffi6:amd64 (3.2.1-4) ...
Selecting previously unselected package libgmp10:amd64.
Preparing to unpack .../libgmp10_2%3a6.1.0+dfsg-2_amd64.deb ...
Unpacking libgmp10:amd64 (2:6.1.0+dfsg-2) ...
Selecting previously unselected package libxslt1.1:amd64.
Preparing to unpack .../libxslt1.1_1.1.28-2.1_amd64.deb ...
Unpacking libxslt1.1:amd64 (1.1.28-2.1) ...
Selecting previously unselected package rubygems-integration.
Preparing to unpack .../rubygems-integration_1.10_all.deb ...
Unpacking rubygems-integration (1.10) ...
Selecting previously unselected package ruby-power-assert.
Preparing to unpack .../ruby-power-assert_0.2.6-1_all.deb ...
Unpacking ruby-power-assert (0.2.6-1) ...
Selecting previously unselected package ruby-test-unit.
Preparing to unpack .../ruby-test-unit_3.1.7-1_all.deb ...
Unpacking ruby-test-unit (3.1.7-1) ...
Selecting previously unselected package ruby-minitest.
Preparing to unpack .../ruby-minitest_5.8.4-1_all.deb ...
Unpacking ruby-minitest (5.8.4-1) ...
Selecting previously unselected package libruby2.2:amd64.
Preparing to unpack .../libruby2.2_2.2.4-1_amd64.deb ...
Unpacking libruby2.2:amd64 (2.2.4-1) ...
Selecting previously unselected package ruby2.2.
Preparing to unpack .../ruby2.2_2.2.4-1_amd64.deb ...
Unpacking ruby2.2 (2.2.4-1) ...
Selecting previously unselected package ruby.
Preparing to unpack .../ruby_1%3a2.2.4_all.deb ...
Unpacking ruby (1:2.2.4) ...
Selecting previously unselected package ruby-blankslate.
Preparing to unpack .../ruby-blankslate_3.1.3-1_all.deb ...
Unpacking ruby-blankslate (3.1.3-1) ...
Selecting previously unselected package ruby-builder.
Preparing to unpack .../ruby-builder_3.2.2-4_all.deb ...
Unpacking ruby-builder (3.2.2-4) ...
Selecting previously unselected package ruby-cfpropertylist.
Preparing to unpack .../ruby-cfpropertylist_2.2.8-1_all.deb ...
Unpacking ruby-cfpropertylist (2.2.8-1) ...
Selecting previously unselected package ruby-excon.
Preparing to unpack .../ruby-excon_0.45.1-2_all.deb ...
Unpacking ruby-excon (0.45.1-2) ...
Selecting previously unselected package ruby-fission.
Preparing to unpack .../ruby-fission_0.5.0-2_all.deb ...
Unpacking ruby-fission (0.5.0-2) ...
Selecting previously unselected package ruby-formatador.
Preparing to unpack .../ruby-formatador_0.2.1-2_all.deb ...
Unpacking ruby-formatador (0.2.1-2) ...
Selecting previously unselected package ruby-mime-types.
Preparing to unpack .../ruby-mime-types_2.6.1-1_all.deb ...
Unpacking ruby-mime-types (2.6.1-1) ...
Selecting previously unselected package ruby-net-ssh.
Preparing to unpack .../ruby-net-ssh_1%3a2.9.2-2_all.deb ...
Unpacking 

Bug#812744: RM: xchat-xsys -- RoQA; depends on to-be-removed package

[Esa Peuha]

Package: ftp.debian.org

Bug #811007 requests the removal of xchat since its upstream is dead
and the actively maintained fork hexchat is already in Debian. As
hexchat already has a plugin that does the same thing as xchat-xsys
for xchat, there is no reason to keep xchat-xsys.

Bug#812743: libsdformat4-dev and libsdformat3-dev: error when trying to install together

[Ralf Treinen]

Package: libsdformat3-dev,libsdformat4-dev
Version: libsdformat3-dev/3.06.00-3
Version: libsdformat4-dev/4.0.0-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-01-26
Architecture: amd64
Distribution: sid

Hi,

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



Extracting templates from packages: 42%
Extracting templates from packages: 85%
Extracting templates from packages: 100%
Selecting previously unselected package libgmp10:amd64.
(Reading database ... 10941 files and directories currently installed.)
Preparing to unpack .../libgmp10_2%3a6.1.0+dfsg-2_amd64.deb ...
Unpacking libgmp10:amd64 (2:6.1.0+dfsg-2) ...
Selecting previously unselected package libmpfr4:amd64.
Preparing to unpack .../libmpfr4_3.1.3-2_amd64.deb ...
Unpacking libmpfr4:amd64 (3.1.3-2) ...
Selecting previously unselected package libmpc3:amd64.
Preparing to unpack .../libmpc3_1.0.3-1_amd64.deb ...
Unpacking libmpc3:amd64 (1.0.3-1) ...
Selecting previously unselected package gcc-5-base:amd64.
Preparing to unpack .../gcc-5-base_5.3.1-7_amd64.deb ...
Unpacking gcc-5-base:amd64 (5.3.1-7) ...
Processing triggers for libc-bin (2.21-7) ...
Setting up gcc-5-base:amd64 (5.3.1-7) ...
(Reading database ... 10971 files and directories currently installed.)
Preparing to unpack .../libgcc1_1%3a5.3.1-7_amd64.deb ...
Unpacking libgcc1:amd64 (1:5.3.1-7) over (1:4.8.2-19) ...
Processing triggers for libc-bin (2.21-7) ...
Setting up libgcc1:amd64 (1:5.3.1-7) ...
Processing triggers for libc-bin (2.21-7) ...
(Reading database ... 10971 files and directories currently installed.)
Preparing to unpack .../libstdc++6_5.3.1-7_amd64.deb ...
Unpacking libstdc++6:amd64 (5.3.1-7) over (4.8.2-19) ...
Processing triggers for libc-bin (2.21-7) ...
Setting up libstdc++6:amd64 (5.3.1-7) ...
Processing triggers for libc-bin (2.21-7) ...
Selecting previously unselected package libboost-iostreams1.58.0:amd64.
(Reading database ... 10985 files and directories currently installed.)
Preparing to unpack .../libboost-iostreams1.58.0_1.58.0+dfsg-4.1_amd64.deb ...
Unpacking libboost-iostreams1.58.0:amd64 (1.58.0+dfsg-4.1) ...
Selecting previously unselected package binutils.
Preparing to unpack .../binutils_2.25.90.20160101-2_amd64.deb ...
Unpacking binutils (2.25.90.20160101-2) ...
Selecting previously unselected package libisl15:amd64.
Preparing to unpack .../libisl15_0.16.1-1_amd64.deb ...
Unpacking libisl15:amd64 (0.16.1-1) ...
Selecting previously unselected package cpp-5.
Preparing to unpack .../cpp-5_5.3.1-7_amd64.deb ...
Unpacking cpp-5 (5.3.1-7) ...
Selecting previously unselected package cpp.
Preparing to unpack .../cpp_4%3a5.3.1-1_amd64.deb ...
Unpacking cpp (4:5.3.1-1) ...
Selecting previously unselected package libcc1-0:amd64.
Preparing to unpack .../libcc1-0_5.3.1-7_amd64.deb ...
Unpacking libcc1-0:amd64 (5.3.1-7) ...
Selecting previously unselected package libgomp1:amd64.
Preparing to unpack .../libgomp1_5.3.1-7_amd64.deb ...
Unpacking libgomp1:amd64 (5.3.1-7) ...
Selecting previously unselected package libitm1:amd64.
Preparing to unpack .../libitm1_5.3.1-7_amd64.deb ...
Unpacking libitm1:amd64 (5.3.1-7) ...
Selecting previously unselected package libatomic1:amd64.
Preparing to unpack .../libatomic1_5.3.1-7_amd64.deb ...
Unpacking libatomic1:amd64 (5.3.1-7) ...
Selecting previously unselected package libasan2:amd64.
Preparing to unpack .../libasan2_5.3.1-7_amd64.deb ...
Unpacking libasan2:amd64 (5.3.1-7) ...
Selecting previously unselected package liblsan0:amd64.
Preparing to unpack .../liblsan0_5.3.1-7_amd64.deb ...
Unpacking liblsan0:amd64 (5.3.1-7) ...
Selecting previously unselected package libtsan0:amd64.
Preparing to unpack .../libtsan0_5.3.1-7_amd64.deb ...
Unpacking libtsan0:amd64 (5.3.1-7) ...
Selecting previously unselected package libubsan0:amd64.
Preparing to unpack .../libubsan0_5.3.1-7_amd64.deb ...
Unpacking libubsan0:amd64 (5.3.1-7) ...
Selecting previously unselected package libcilkrts5:amd64.
Preparing to unpack .../libcilkrts5_5.3.1-7_amd64.deb ...
Unpacking libcilkrts5:amd64 (5.3.1-7) ...
Selecting previously unselected package libmpx0:amd64.
Preparing to unpack .../libmpx0_5.3.1-7_amd64.deb ...
Unpacking libmpx0:amd64 (5.3.1-7) ...
Selecting previously unselected package libquadmath0:amd64.
Preparing to unpack .../libquadmath0_5.3.1-7_amd64.deb ...
Unpacking libquadmath0:amd64 (5.3.1-7) ...
Selecting previously unselected package libgcc-5-dev:amd64.
Preparing to unpack .../libgcc-5-dev_5.3.1-7_amd64.deb ...
Unpacking libgcc-5-dev:amd64 (5.3.1-7) ...
Selecting previously unselected package gcc-5.
Preparing to unpack .../gcc-5_5.3.1-7_amd64.deb ...
Unpacking gcc-5 (5.3.1-7) ...
Selecting previously unselected package gcc.
Preparing to unpack .../gcc_4%3a5.3.1-1_amd64.deb ...
Unpacking gcc (4:5.3.1-1) ...
Selecting previously unselected package libc-dev-bin.
Preparing to unpack 

Bug#812742: libirstlm-dev and libduo-dev: error when trying to install together

[Ralf Treinen]

Package: libduo-dev,libirstlm-dev
Version: libduo-dev/1.9.11-1+b1
Version: libirstlm-dev/5.80.03-1
Severity: serious
User: trei...@debian.org
Usertags: edos-file-overwrite

Date: 2016-01-26
Architecture: amd64
Distribution: sid

Hi,

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


Preconfiguring packages ...
Selecting previously unselected package gcc-5-base:amd64.
(Reading database ... 10941 files and directories currently installed.)
Preparing to unpack .../gcc-5-base_5.3.1-7_amd64.deb ...
Unpacking gcc-5-base:amd64 (5.3.1-7) ...
Setting up gcc-5-base:amd64 (5.3.1-7) ...
(Reading database ... 10948 files and directories currently installed.)
Preparing to unpack .../libstdc++6_5.3.1-7_amd64.deb ...
Unpacking libstdc++6:amd64 (5.3.1-7) over (4.8.2-19) ...
Processing triggers for libc-bin (2.21-7) ...
Setting up libstdc++6:amd64 (5.3.1-7) ...
Processing triggers for libc-bin (2.21-7) ...
Selecting previously unselected package libssl1.0.2:amd64.
(Reading database ... 10962 files and directories currently installed.)
Preparing to unpack .../libssl1.0.2_1.0.2e-1_amd64.deb ...
Unpacking libssl1.0.2:amd64 (1.0.2e-1) ...
Selecting previously unselected package libirstlm0:amd64.
Preparing to unpack .../libirstlm0_5.80.03-1_amd64.deb ...
Unpacking libirstlm0:amd64 (5.80.03-1) ...
Selecting previously unselected package libirstlm-dev.
Preparing to unpack .../libirstlm-dev_5.80.03-1_amd64.deb ...
Unpacking libirstlm-dev (5.80.03-1) ...
Selecting previously unselected package libduo3:amd64.
Preparing to unpack .../libduo3_1.9.11-1+b1_amd64.deb ...
Unpacking libduo3:amd64 (1.9.11-1+b1) ...
Selecting previously unselected package libduo-dev.
Preparing to unpack .../libduo-dev_1.9.11-1+b1_amd64.deb ...
Unpacking libduo-dev (1.9.11-1+b1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libduo-dev_1.9.11-1+b1_amd64.deb (--unpack):
 trying to overwrite '/usr/include/util.h', which is also in package 
libirstlm-dev 5.80.03-1
Processing triggers for libc-bin (2.21-7) ...
Processing triggers for man-db (2.7.5-1) ...
Errors were encountered while processing:
 /var/cache/apt/archives/libduo-dev_1.9.11-1+b1_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


This is a serious bug as it makes installation fail, and violates
sections 7.6.1 and 10.1 of the policy. An optimal solution would
consist in only one of the packages installing that file, and renaming
or removing the file in the other package. Depending on the
circumstances you might also consider Replace relations or file
diversions. If the conflicting situation cannot be resolved then, as a
last resort, the two packages have to declare a mutual
Conflict. Please take into account that Replaces, Conflicts and
diversions should only be used when packages provide different
implementations for the same functionality.

Here is a list of files that are known to be shared by both packages
(according to the Contents file for sid/amd64, which may be
slightly out of sync):

  /usr/include/util.h

This bug has been filed against both packages. If you, the maintainers of
the two packages in question, have agreed on which of the packages will
resolve the problem please reassign the bug to that package. You may then
also register in the BTS that the other package is affected by the bug.

-Ralf.

PS: for more information about the detection of file overwrite errors
of this kind see http://qa.debian.org/dose/file-overwrites.html.

Bug#650601: libpng is ready for transtion

[Aníbal Monsalve Salazar]

On Tue, 2016-01-26 10:23:13 +0100, Tobias Frost wrote:
>> Tobias Frost  (2016-01-25):
>>> Dear release-team,
>>>
>>> Now that all NMUs are in DELAYED for all fixables.
>>> I think we are ready to throw the switch.
>>
>> You haven't answered <20160106232316.ga28...@mraw.org>.
>>
>> Mraw,
>> KiBi.
>>
>
> Nobuhiro, Anibal,
>
> this is a question for you:
>
> https://lists.debian.org/debian-devel/2016/01/msg00248.html
>
> {quote}
> Speaking of this particular udeb, I've just spotted libpng16-16-udeb has
> a Conflicts against libpng12-0-udeb. I'm not sure why, and the changelog
> doesn't seem to explain either. libpng16-16 and libpng12-0 seems to be
> co-installable, so I'm not sure why their respective udebs shouldn't be.
> {/quote}

The Conflicts against libpng12-0-udeb can be removed.


signature.asc
Description: Digital signature

Bug#812754: RFA: ptpd -- Precision Time Protocol daemon

[stigge]

Package: wnpp
Severity: normal

I'm not using this package regularly. Therefore, looking for a new maintainer.

Bug#812753: RFA: pstoedit -- PostScript and PDF files to editable vector graphics converter

[stigge]

Package: wnpp
Severity: normal

I'm not regularly using this package. Therefore, looking for a new maintainer.

Bug#812541: More information

[Ritesh Raj Sarraf]

Control: tag -1 +fixed-upstream

On Tue, 2016-01-26 at 14:41 +0530, Ritesh Raj Sarraf wrote:
> The problem is with faulty devices, that report power saving
> capabilities, that they don't implement well.

I've switched defaults to blacklisting USB class devices. This should
definitely improve the current state.

The same will be part of the next release, very soon. Until then, you
can modify it be self.

https://github.com/rickysarraf/laptop-mode-tools/commit/57e2cf44d70e948
ce4ec4123a9bec3c6dddc67e3

-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."



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

Bug#770129: RFP: html5tidy -- “tidy” HTML 5 in the wild to well-formed XML or HTML

[Daniel James]

Hi Jim,

> I support closing this bug. There is already an existing request to update
> the current tidy package from current source.

I'd agree, please close this bug as a duplicate of:

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

Cheers!

Daniel

Bug#807180: ardesia: diff for NMU version 1.1-2.1

[Mattia Rizzolo]

Control: tags 807180 + pending

Dear maintainer,

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

Regards.

-- 
regards,
Mattia Rizzolo

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

 changelog |   10 ++
 control   |2 +-
 2 files changed, 11 insertions(+), 1 deletion(-)

diff -Nru ardesia-1.1/debian/changelog ardesia-1.1/debian/changelog
--- ardesia-1.1/debian/changelog	2014-08-16 03:10:12.0 +
+++ ardesia-1.1/debian/changelog	2016-01-26 11:04:28.0 +
@@ -1,3 +1,13 @@
+ardesia (1.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Bas Couwenberg ]
+  * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev.
+Closes: #807180
+
+ -- Mattia Rizzolo   Tue, 26 Jan 2016 11:04:09 +
+
 ardesia (1.1-2) unstable; urgency=medium
 
   [ Frédéric Bonnard ]
diff -Nru ardesia-1.1/debian/control ardesia-1.1/debian/control
--- ardesia-1.1/debian/control	2014-08-16 03:10:12.0 +
+++ ardesia-1.1/debian/control	2016-01-26 11:04:06.0 +
@@ -6,7 +6,7 @@
 	intltool,
 	pkg-config,
 	libgtk-3-dev,
-	libgsl0-dev,
+	libgsl-dev,
 	libxml2-dev,
 	libgsf-1-dev
 Standards-Version: 3.9.5


signature.asc
Description: PGP signature

Bug#810203: netpbm-free: diff for NMU version 2:10.0-15.3

[Gianfranco Costamagna]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Control: tags -1 -pending

Hi, I'm canceling the NMU because of #648131

cheers,

Gianfranco

On Thu, 21 Jan 2016 14:50:59 + (UTC) Gianfranco Costamagna
 wrote:
> Control: tags 810203 + patch
> Control: tags 810203 + pending
> 
> Dear maintainer,
> 
> I've prepared an NMU for netpbm-free (versioned as 2:10.0-15.3) and
> uploaded it to DELAYED/7. Please feel free to tell me if I
> should delay it longer.
> 
> Regards.
> diff -u netpbm-free-10.0/debian/changelog netpbm-free-10.0/debian/chan
gelog
> --- netpbm-free-10.0/debian/changelog
> +++ netpbm-free-10.0/debian/changelog
> @@ -1,3 +1,11 @@
> +netpbm-free (2:10.0-15.3) unstable; urgency=medium
> +
> +  * Non-maintainer upload.
> +  * Change libpng12-dev b-d to libpng-dev to ease libpng transition
> +(Closes: #810203)
> +
> + -- Gianfranco Costamagna   Thu, 21 Jan 201
6 15:48:28 +0100
> +
> netpbm-free (2:10.0-15.2) unstable; urgency=medium
> 
> * Non-maintainer upload.
> diff -u netpbm-free-10.0/debian/control netpbm-free-10.0/debian/contro
l
> --- netpbm-free-10.0/debian/control
> +++ netpbm-free-10.0/debian/control
> @@ -4,7 +4,7 @@
> Maintainer: Andreas Barth 
> Uploaders: Steve McIntyre <93...@debian.org>
> Standards-Version: 3.8.4
> -Build-Depends: libtiff5-dev, libjpeg-dev, debhelper (>= 7), libpng12-
dev, zlib1g-dev, flex, quilt
> +Build-Depends: libtiff5-dev, libjpeg-dev, debhelper (>= 7), libpng-de
v, zlib1g-dev, flex, quilt
> Homepage: http://netpbm.alioth.debian.org
> Vcs-Browser: http://git.debian.org/?p=collab-maint/netpbm.git
> Vcs-Git: git://anonscm.debian.org/collab-maint/netpbm.git
> 
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWp1NfAAoJEPNPCXROn13ZmV0P/0vZowhiR7LBContEMMOCPF9
f35QQt9aeIQVBPu/WU2ZDJkmVRMdRHnCW2ssIeqLA1TFXJUYoJuMyWPMp08S74iE
DWrNqvDgQ0J06s+vMoy5lvk18fu1LV+wRkwiiHIvgQRfBaYWPNgpr7w+cKZl5Pvy
U1Z4xgSkwr0YBM02WKpSTv0lNnb2Z1Ids2hs6JnF/q0K75HPMSjT0v8dPghYTxhL
X+duBqFpTgm5OY9f/lxUQB5qWOFF31wAVMcJ9HQZNwM8rPBFJ5RKIMt7AMoLlF5i
5eopEzPYGyylO8iaP5W3Ouv8ZmrnwFFtRqhTuEu58zNQI4C2uuvKlWVfhujV7OON
C4UwL9YzR6kt3JQAiTiyLRdMuBEWnzaQ2ENYNbcl2/jHZHNf0appJHE+CkGeJnAC
Wn+xYdvfVJvrYR3fHEIbFYygKjNghVIjV4cfC0wD33R6sGnt7WsQT+iHtG5IV6vZ
WPEIYosohs8jxlVh1dQouD/V656ldzahCsJg4XV8rs/NczGm951f/9v98b/MOfnG
F12mxarHAWklW3XC2YmXkU59He0DpqDLA0OM9GgUzvNwH182JTuks4JrjtDRV2zi
UGMfZS4uo/QiziE5Nspz7NJvIf8ZrCP6fOMKeY8I/6ti/X/9AN1V4+EFFnrMObNx
9yExc+kxhRmqOfx8Dzsj
=Y7es
-END PGP SIGNATURE-

Bug#456822: aptitude incorecctly reports that packages are not a Debian package

[Manuel A. Fernandez Montecelo]

Control: tags -1 + pending


Hi Patrick,

2008-02-13 09:20 Patrick Schoenfeld:

Hi Daniel,

sorry for the late reply.

Daniel Burrows wrote:

Losing Origin information by changing your sources.list is a bit of a
corner case.  I suppose I could heuristically check all the packages to
see if any Debian packages existed in the cache, or (better) if any
packages at all had an Origin tag.  However, note that this wouldn't
help if you had any package at all with Origin: Debian in your cache
prior to changing sources.list.


Okay, so I think we both agree that the problem is a corner case.
Then probably the real problem to solve is how the corner case is handled.


  Another option would be to just change the message to say that either
it's not a Debian package or you need to run "update".  But I believe
this would just confuse people into thinking they needed to run update
when in fact this is almost never going to help.


I agree that this wouldn't be so optimal. However there must be a possibility 
to detect this case where sources.list has been changed, or not? Couldn't you 
print two different messages depending on weither this is the case or not?


I changed this message to suggest an "update", so marking as +pending.

Thanks for the report.

--
Manuel A. Fernandez Montecelo 

Bug#650601: libpng is ready for transtion

[Tobias Frost]

> Tobias Frost  (2016-01-25):
>> Dear release-team,
>>
>> Now that all NMUs are in DELAYED for all fixables.
>> I think we are ready to throw the switch. 
>
> You haven't answered <20160106232316.ga28...@mraw.org>.
>
> Mraw,
> KiBi.
>

Nobuhiro, Anibal,

this is a question for you:

https://lists.debian.org/debian-devel/2016/01/msg00248.html

{quote}
Speaking of this particular udeb, I've just spotted libpng16-16-udeb has
a Conflicts against libpng12-0-udeb. I'm not sure why, and the changelog
doesn't seem to explain either. libpng16-16 and libpng12-0 seems to be
co-installable, so I'm not sure why their respective udebs shouldn't be.
{/quote}

Bug#785054: Please remove dependency on dpsyco

[Esa Peuha]

On Mon, May 11, 2015 Ola Lundqvist  wrote:

> I would like you to kindly remove the dependency on dpsyco-devel. I have
> attached a patch for that. The reason is that I have requested the removal
> of psyco source and this reverse dependency prevents that from happening.
> See bug #784869.

> I know it is my own fault that we have this dependency as I have added it
> myself sometime many years ago. I do not see the point of having it anymore.

> Please let me know if you want me to NMU the change.

Given how long this bug has been open and how trivial the patch is,
I think you can just go ahead and NMU harden-doc.

Bug#812751: RFA: olsrd -- optimized link-state routing daemon (unik-olsrd)

[stigge]

Package: wnpp
Severity: normal

I'm not using this package regularly. Therefore, looking for a new maintainer. 
The package is maintained in an svn repository at alioth.

Bug#812747: reproducing bug: probably a epiphany bug

[Wim Bertels]

Hallo,

i fixed this problem by removing the state files of epiphany

~/.config/epiphany$ rm session_state.xml*

And then tried to reproduce the bug,
i doenst always happen,
but after trying 5 times the bug was there again,
again after removing the state files of epiphany,
the debian-reference command works fine again.

So this is a epiphany bug

reassign 812747 epiphany-browser

-- 
mvg,
Wim



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

Bug#812757: RFA: swisswatch -- Swiss Railway Clock for the X Window System

[stigge]

Package: wnpp
Severity: normal

I'm not using this package regularly. Therefore, looking for a new maintainer. 
I don't know about any new upstream release since the 1990s.

Bug#812756: lintian: please make -v imply --no-tag-display-limit

[Thorsten Glaser]

Package: lintian
Version: 2.5.40.2
Severity: wishlist

Hi,

please make -v imply the new option --no-tag-display-limit
for those of us who wish to see everything and have muscle
memory (or pbuilder hook scripts ;-) for calling
lintian -vIiE --pedantic [--color] *.changes

Thanks!

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages lintian depends on:
ii  binutils  2.25.90.20160101-2
ii  bzip2 1.0.6-8
ii  diffstat  1.60-1
ii  file  1:5.25-2
ii  gettext   0.19.7-2
ii  hardening-includes2.8+nmu2
ii  intltool-debian   0.35.0+20060710.4
ii  libapt-pkg-perl   0.1.29+b5
ii  libarchive-zip-perl   1.56-2
ii  libclass-accessor-perl0.34-1
ii  libclone-perl 0.38-1+b1
ii  libdigest-sha-perl5.95-2+b1
ii  libdpkg-perl  1.18.3
ii  libemail-valid-perl   1.198-1
ii  libfile-basedir-perl  0.07-1
ii  libipc-run-perl   0.94-1
ii  liblist-moreutils-perl0.413-1+b1
ii  libparse-debianchangelog-perl 1.2.0-8
ii  libperl5.22 [libdigest-sha-perl]  5.22.1-4
ii  libtext-levenshtein-perl  0.13-1
ii  libtimedate-perl  2.3000-2
ii  liburi-perl   1.71-1
ii  man-db2.7.5-1
ii  patchutils0.3.4-1
ii  perl  5.22.1-4
ii  t1utils   1.39-2
ii  xz-utils  5.1.1alpha+20120614-2.1

Versions of packages lintian recommends:
ii  dpkg 1.18.4
pn  libperlio-gzip-perl  
ii  perl 5.22.1-4
ii  perl-modules-5.22 [libautodie-perl]  5.22.1-4

Versions of packages lintian suggests:
ii  binutils-multiarch 2.25.90.20160101-2
pn  dpkg-dev   
ii  libhtml-parser-perl3.72-1
pn  libtext-template-perl  
ii  libyaml-perl   1.15-1

-- no debconf information

Bug#812758: RFA: vtun -- virtual tunnel over TCP/IP networks

[stigge]

Package: wnpp
Severity: normal

I'm not using this package regularly. Therefore, looking for a new maintainer.

Bug#731709: grub-efi UEFI support based on debian-cd work complete (repos)

[Michal Suchanek]

On 25 January 2016 at 21:33, adrian15  wrote:
>
>
> El 25/01/16 a las 16:12, Michal Suchanek escribió:
>>
>> On 25 January 2016 at 03:05, adrian15  wrote:
>>>
>>> El 24/01/16 a las 16:51, Michal Suchanek escribió:
>>
>>
>>> What you are describing here is what it's actually implemented in my
>>> patch
>>> (Well, actually the first patch version because the current one enforces
>>> bootloader roles).
>>
>>
>> Actually, no.
>>
>> Nowhere in the description is any bootloader designated primary or
>> secondary or first or second. On purpose.
>
> Neither it is on my patch (initial implementation). Yes, the term
> PRIMARY_BOOTLOADER is used there for reusing old code. But using:
>
> --bootloaders=syslinux,grub-efi
>
> did not enforce syslinux to be in the first place or grub-efi to be in the
> second place.
>
> That's the specific part I meant.
>
>>
>>> So what about primary and secondary terms? Or first or
>>> second terms?
>>
>>
>> Both are broken and confusing.
>
> Ok...
>>>
>>>
>>> These terms are used in two places:
>>> * Internal variables and functions to handle bootloaders
>>> * Information shown to the final user
>>>
>>> I'm most convinced to use the first and non-first notation. So that the
>>> old
>>> code that referred to LB_BOOTLOADER can just refer to:
>>> LB_FIRST_BOOTLOADER.
>>
>>
>> For what piece of code we have does it make sense to reference
>> LB_FIRST_BOOTLOADER when not also referencing LB_SECOND_BOOTLOADER?
>> Will that be extended to LB_THIRD_BOOTLOADER once x86 grows support
>> for coreboot or l-b grows support for some other platform with many
>> firmware variants?
>>
>> If you set bootloaders like
>>
>> LB_BOOTLOADERS="syslinux grub-efi"
>>
>> then you can just do
>>
>> for bootloader in $LB_BOOTLOADERS ; do some $bootloader foo
>
> Mostly what current path does but with commas instead.

IIRC multivalue options use mostly spaces for separator in l-b so far.

>>
>>
>> after you check that you have at most two bootloaders and if you have
>> more than one then only the latter one ends with -efi.
>
>
> This is not a good approach. You are requesting the bootloaders to end in
> "-efi". The current approach is to name them based on the Debian package
> name. These packages do not need to end in "-efi".

It so happens that bootloaders that support efi are packaged as
packages with -efi suffix (well, except elilo). Maybe there is some
intent there?

However, grub-pc is now split in grub-pc scripts that are meant to
install the bootloader in the system which you probably don't want and
grub-pc-bin which just includes the binaries. The situation is even
more complicated with the 32bit and 64bit efi packages. Also expect
that at some point the maintainers figure out some new completely
awesome way to split the bootloader into packages and then the package
sets will be different in stable/testing/oldstable.

So naming the l-b option *exactly* like the package is not that good idea.

>
> My use case is the following one. The final user requests:
>
> --bootloaders=grub-efi,syslinux
>
> so I show him:
>
> "Warning. You are using: syslinux as a non first bootloader. This might work
> but it is not advised."
>
> How do I know that I have to output this message?

for bootloader in $BOOTLOADERS ; do

# some bootloader foo

if echo $BIOS_BOOTLOADERS | grep "${bootloader}" >/dev/null; then
# a fixed list of bootloaders that load through legacy BIOS -
currently should be "syslinux grub-pc" although grub is not well
supported
case $MEDIA_TYPE in # or whatever the variable
iso*)
case "${BOOTLOADERS}" in
"${bootloader}"*);;
*) echo "Warning: it is recommended to specify
$bootloader first in bootloader list so it gets installed as first
el-torito boot entry."
;;
esac ;;
esac
fi
done


>
> Because I compare the internal variable:
>
> LB_FIRST_BOOTLOADER="grub-efi"
>
> with the bootloader name "syslinux" and I see they are not the same one.
>
> So, as you see I need to use:
>
> "non first bootloader" term

Why that has to be a term? Just say it should come first in the list
of bootloaders if specified at all.

> and
> LB_FIRST_BOOTLOADER variable.

what for?

>
> So...
>
> 1) I don't mind renaming "non first bootloader" or LB_FIRST_BOOTLOADER to
> another terminology which makes more technical sense.
> 2) I prefer this approach over yours (Michal) because it's the own
> bootloader which decides if it is more suited for "first bootloader" or not.

How does it decide that? It can install equally well in 1st, 2nd or
10th el-torito record. The only reason we want BIOS record first is


1) some tools for butchering bootable CDs expect it to be first.

2) it's the traditional place for it (since it was the only record for
a long time) and some ancient BIOSes might potentially break if it's
not first because somebody missed there *can* be 

Bug#812541: More information

[Ritesh Raj Sarraf]

On Mon, 2016-01-25 at 19:02 +0200, Stanimir Stoyanov wrote:
> Okay, I removed the usb-autosuspend.conf file and checked out the 
> runtime-pm. Well, this is not a bug but a perfectly working program
> with 
> bad configuration...
> 
> LM/NOLM_SUSPEND_RUNTIME is set by default to 1 with a timeout of 2 
> seconds! This is really wrong and annoying in my opinion for default 
> configuration.

The problem is with faulty devices, that report power saving
capabilities, that they don't implement well.

As for why Runtime Power Management is effective even on AC, is because
you don't want to melt down your devices by running them at full power.

I don't have the relevant documentation accessible right now, but the
defaults for runtime-pm in the kernel too were to dynamically scale
in/out the capability than running at full power and generating too
much heat.


So the defaults are set that way for a reason. If you just blacklist
your faulty device, you should be good.


-- 
Ritesh Raj Sarraf
RESEARCHUT - http://www.researchut.com
"Necessity is the mother of invention."



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

Bug#812752: phonon: please depend on phonon-backend-gstreamer on hurd

[Samuel Thibault]

Package: phonon
Version: 4:4.8.3-2
Severity: important

Hello,

Most of KDE is currently not buildable on hurd-i386 because phonon tries
to pull phonon-backend-vlc, which is currently not installable due to
the missing libldb-dev support on hurd for now (the person working on
this is still working on this, but it seems to be taking months).

Could you change the dependencies to phonon-backend-gstreamer on hurd
to avoid the issue so we can get to build kde again?  I have attached a
proposed patch.

Thanks,
Samuel

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

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

Versions of packages phonon depends on:
ii  debconf [debconf-2.0]1.5.58
ii  libphonon4   4:4.8.3-2
ii  phonon-backend-vlc [phonon-backend]  0.8.2-1

phonon recommends no packages.

Versions of packages phonon suggests:
pn  phonon-backend-gstreamer  
ii  phonon-backend-vlc0.8.2-1

-- debconf information excluded

-- 
Samuel
 Moralité : le modem et le cablerouteur font comme les filles, ils
 papotent toute la journée.
 -+- RB in NPC : Et en plus, ils ne parlent que de bits -+-
--- debian/rules.orig   2016-01-26 10:55:18.426115433 +0100
+++ debian/rules2016-01-26 10:56:11.575941501 +0100
@@ -8,8 +8,15 @@
 libpkgs_gen_strict_local_shlibs = $(libpkgs_all_packages)
 include /usr/share/pkg-kde-tools/qt-kde-team/2/library-packages.mk
 
+DEB_HOST_ARCH_OS := $(shell dpkg-architecture -qDEB_HOST_ARCH_OS)
+
+ifeq ($(DEB_HOST_ARCH_OS),hurd)
+RECOMMENDED_PHONON4_QT4_BACKEND := phonon-backend-gstreamer
+RECOMMENDED_PHONON4_QT5_BACKEND := phonon4qt5-backend-gstreamer
+else
 RECOMMENDED_PHONON4_QT4_BACKEND := phonon-backend-vlc
 RECOMMENDED_PHONON4_QT5_BACKEND := phonon4qt5-backend-vlc
+endif
 
 override_dh_auto_clean:
$(overridden_command)

Bug#807229: votca-tools: diff for NMU version 1.2.4-1.1

[Mattia Rizzolo]

Control: tags 807229 + pending

Dear maintainer,

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

Regards.

-- 
regards,
Mattia Rizzolo

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

 changelog |   13 +
 control   |2 +-
 2 files changed, 14 insertions(+), 1 deletion(-)

diff -Nru votca-tools-1.2.4/debian/changelog votca-tools-1.2.4/debian/changelog
--- votca-tools-1.2.4/debian/changelog	2014-09-05 21:04:29.0 +
+++ votca-tools-1.2.4/debian/changelog	2016-01-26 10:39:14.0 +
@@ -1,3 +1,16 @@
+votca-tools (1.2.4-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Bas Couwenberg ]
+  * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev.
+Closes: #807229
+
+  [ Mattia Rizzolo ]
+  * move debian/upstream to debian/upstream/metadata
+
+ -- Mattia Rizzolo   Tue, 26 Jan 2016 10:38:47 +
+
 votca-tools (1.2.4-1) unstable; urgency=low
 
   * Version bump 
diff -Nru votca-tools-1.2.4/debian/control votca-tools-1.2.4/debian/control
--- votca-tools-1.2.4/debian/control	2014-09-05 21:03:50.0 +
+++ votca-tools-1.2.4/debian/control	2016-01-26 10:37:16.0 +
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Debichem Team 
 Uploaders: Christoph Junghans , Michael Banck 
-Build-Depends: debhelper (>= 9.0.0), cmake, libfftw3-dev, libgsl0-dev, txt2tags, libboost-program-options-dev, libexpat1-dev, libsqlite3-dev, pkg-config
+Build-Depends: debhelper (>= 9.0.0), cmake, libfftw3-dev, libgsl-dev, txt2tags, libboost-program-options-dev, libexpat1-dev, libsqlite3-dev, pkg-config
 Standards-Version: 3.9.5
 Homepage: http://www.votca.org
 Vcs-Browser: http://anonscm.debian.org/viewvc/debichem/unstable/votca-tools/
File /tmp/atg6tpHQvt/votca-tools-1.2.4/debian/upstream is a regular file while file /tmp/nSfQXQSgFM/votca-tools-1.2.4/debian/upstream is a directory


signature.asc
Description: PGP signature

Bug#807217: ngraph-gtk: diff for NMU version 6.06.13-5.1

[Mattia Rizzolo]

Control: tags 807217 + pending

Dear maintainer,

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

Regards.

-- 
regards,
Mattia Rizzolo

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

 changelog |   10 ++
 control   |2 +-
 2 files changed, 11 insertions(+), 1 deletion(-)

diff -Nru ngraph-gtk-6.06.13/debian/changelog ngraph-gtk-6.06.13/debian/changelog
--- ngraph-gtk-6.06.13/debian/changelog	2014-06-15 11:09:33.0 +
+++ ngraph-gtk-6.06.13/debian/changelog	2016-01-26 10:49:40.0 +
@@ -1,3 +1,13 @@
+ngraph-gtk (6.06.13-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Bas Couwenberg ]
+  * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev.
+Closes: #807217
+
+ -- Mattia Rizzolo   Tue, 26 Jan 2016 10:43:45 +
+
 ngraph-gtk (6.06.13-5) unstable; urgency=medium
 
   * debian/rules
diff -Nru ngraph-gtk-6.06.13/debian/control ngraph-gtk-6.06.13/debian/control
--- ngraph-gtk-6.06.13/debian/control	2014-03-31 13:18:20.0 +
+++ ngraph-gtk-6.06.13/debian/control	2016-01-26 10:43:38.0 +
@@ -3,7 +3,7 @@
 Priority: extra
 Maintainer: Koichi Akabe 
 Uploaders: Ito Hiroyuki 
-Build-Depends: debhelper (>= 9.0.0), dh-autoreconf, libgtk-3-dev, libgsl0-dev, libreadline6-dev, ruby (>= 1:2.0.0), ruby-dev (>= 1:2.0.0)
+Build-Depends: debhelper (>= 9.0.0), dh-autoreconf, libgtk-3-dev, libgsl-dev, libreadline6-dev, ruby (>= 1:2.0.0), ruby-dev (>= 1:2.0.0)
 Standards-Version: 3.9.5
 Homepage: http://homepage3.nifty.com/slokar/ngraph/ngraph-gtk.html
 


signature.asc
Description: PGP signature

Bug#797210: [debian-mysql] mariadb-10.0: mariadb-server does not ship a debconf set for creating a adminitrative user (like mysql-server do)

[Otto Kekäläinen]

2016-01-26 12:38 GMT+02:00 Carsten Schoenert :
>> I skimmed through
>> https://people.debian.org/~seanius/policy/dbconfig-common.html/ but
>> didn't really get the hang of it. The docs are written for "consumers"
>> and not "providers" like the mariadb-10.0 package maintainers would
>> need to read about.
>
> I don't get this point, what do you mean between consumer and provider?
> As a package maintainer you need to ensure thet the user who is installing
> your package is guided through the installation so the package is
> completely configured and running after the installation.

I mean the docs linked above is meant for people installing packages
(consuming them). I don't find it helpful for myself as the package
producer. The docs don't tell me how a database must be packaged to be
compatible with dbconfig. Or maybe they do somewhere but I don't get
it. Maybe reading some example code from somewhere or seeing a
copy-paste of them the installer fails would help here.

I will not close this bug just yet. I am interested in getting
mariadb-server compatible with dbconfig - I just have no idea how to
do it as I don't understand how dbconfig works.

If the fix is obivious to somebody else, having this issue open and
waiting for somebody to send a patch in would server a cause.

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Jakub Wilk]

* Pilisi Gergely , 2016-01-22, 14:55:

export DEB_BUILD_MAINT_OPTIONS = hardening=+all
export CPPFLAGS=$(shell dpkg-buildflags --get CPPFLAGS)
export CFLAGS=$(shell dpkg-buildflags --get CFLAGS)
export CXXFLAGS=$(shell dpkg-buildflags --get CXXFLAGS)
export LDFLAGS=$(shell dpkg-buildflags --get LDFLAGS)


Note that $(shell) constructs are not affected by variables exported in 
the same makefile.



export CCFLAGS=$(shell dplg-buildflags --get CFLAGS)


Typo: s/dplg/dpkg/.


What is wrong with that? :(


blhc(1) is invaluable for debugging hardening issues.

--
Jakub Wilk

Bug#812252: less not any more registered as "pager" alternative

[Frederik Möllers]

Hi,

I've created a patch which moves the update-alternatives commands to the
correct scripts and which also implements the strategy mentiones in
message 5 of bug #694051. Applying it to the source directory should
solve all problems related to these two bugs.

Cheers,
Frederik
diff -urN less-481.old/debian/less.postinst less-481/debian/less.postinst
--- less-481.old/debian/less.postinst	2016-01-11 13:08:57.0 +0100
+++ less-481/debian/less.postinst	2016-01-26 12:04:54.124486691 +0100
@@ -1,12 +1,66 @@
-#!/bin/sh
+#! /bin/sh
+# postinst script for less
+#
+# see: dh_installdeb(1)
+
 set -e
 
-if [ "$1" = 'configure' ]; then
-  for file in lessfile lesspipe lesskey lessecho less; do
-if [ ! -e /usr/bin/$file ]; then
-  ln -s /bin/$file /usr/bin/$file
-fi
-  done
-fi
+# summary of how this script can be called:
+#*  `configure' 
+#*  `abort-upgrade' 
+#*  `abort-remove' `in-favour' 
+#  
+#*  `abort-deconfigure' `in-favour'
+#`removing'
+#   
+# for details, see /usr/doc/packaging-manual/
+#
+# quoting from the policy:
+# Any necessary prompting should almost always be confined to the
+# post-installation script, and should be protected with a conditional
+# so that unnecessary prompting doesn't happen if a package's
+# installation fails and the `postinst' is called with `abort-upgrade',
+# `abort-remove' or `abort-deconfigure'.
+
+case "$1" in
+configure)
+update-alternatives --quiet --install /usr/bin/pager pager \
+	/bin/less 77 --slave /usr/share/man/man1/pager.1.gz \
+	pager.1.gz /usr/share/man/man1/less.1.gz
+
+  # This change needs to get into one stable release.
+  # See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694051
+update-alternatives --quiet --remove pager /usr/bin/less
+
+  # Purge the debconf database we no longer need.
+  if [ -e /usr/share/debconf/confmodule ]; then
+. /usr/share/debconf/confmodule
+db_version 2.0
+db_purge
+  fi
+
+  # install links in /bin
+  for file in lessfile lesspipe lesskey lessecho less; do
+if [ ! -e /usr/bin/$file ]; then
+  ln -s /bin/$file /usr/bin/$file
+fi
+  done
+
+;;
+
+abort-upgrade|abort-remove|abort-deconfigure)
+
+;;
+
+*)
+echo "postinst called with unknown argument \`$1'" >&2
+exit 0
+;;
+esac
+
+# dh_installdeb will replace this with shell code automatically
+# generated by other debhelper scripts.
 
 #DEBHELPER#
+
+exit 0
diff -urN less-481.old/debian/less.postrm less-481/debian/less.postrm
--- less-481.old/debian/less.postrm	2016-01-11 13:08:57.0 +0100
+++ less-481/debian/less.postrm	2016-01-26 12:06:27.928916149 +0100
@@ -9,4 +9,9 @@
   done
 fi
 
+if [ "$1" = 'remove' -o "$1" = 'disappear' ]
+then
+update-alternatives --quiet --remove pager /bin/less
+fi
+
 #DEBHELPER#
diff -urN less-481.old/debian/less.prerm less-481/debian/less.prerm
--- less-481.old/debian/less.prerm	1970-01-01 01:00:00.0 +0100
+++ less-481/debian/less.prerm	2016-01-26 12:01:23.683327144 +0100
@@ -0,0 +1,37 @@
+#! /bin/sh
+# prerm script for less
+#
+# see: dh_installdeb(1)
+
+set -e
+
+# summary of how this script can be called:
+#*  `remove'
+#*  `upgrade' 
+#*  `failed-upgrade' 
+#*  `remove' `in-favour'  
+#*  `deconfigure' `in-favour'
+#`removing'
+#   
+# for details, see /usr/doc/packaging-manual/
+
+case "$1" in
+remove)
+update-alternatives --quiet --remove pager /bin/less
+;;
+upgrade|failed-upgrade|deconfigure)
+;;
+*)
+echo "prerm called with unknown argument \`$1'" >&2
+exit 0
+;;
+esac
+
+# dh_installdeb will replace this with shell code automatically
+# generated by other debhelper scripts.
+
+#DEBHELPER#
+
+exit 0
+
+
diff -urN less-481.old/debian/postinst less-481/debian/postinst
--- less-481.old/debian/postinst	2014-09-08 06:08:25.0 +0200
+++ less-481/debian/postinst	1970-01-01 01:00:00.0 +0100
@@ -1,59 +0,0 @@
-#! /bin/sh
-# postinst script for less
-#
-# see: dh_installdeb(1)
-
-set -e
-
-# summary of how this script can be called:
-#*  `configure' 
-#*  `abort-upgrade' 
-#*  `abort-remove' `in-favour' 
-#  
-#*  `abort-deconfigure' `in-favour'
-#`removing'
-#   
-# for details, see /usr/doc/packaging-manual/
-#
-# quoting from the policy:
-# Any necessary prompting should almost always be confined to the
-# post-installation script, and should be protected with a conditional
-# so that unnecessary prompting doesn't happen if a package's
-# installation fails and the `postinst' is called with `abort-upgrade',
-# `abort-remove' or 

Bug#797210: [debian-mysql] mariadb-10.0: mariadb-server does not ship a debconf set for creating a adminitrative user (like mysql-server do)

[Otto Kekäläinen]

2016-01-26 13:53 GMT+02:00 Carsten Schoenert :
> Don't care about packages that need to set up databases, just provide
> with mariadb-server all possible authentication methods and guide the
> user while installing your package.
> And maybe provide a dbconfig way to add later new user/password/host
> combinations to the server with dpkg-reconfigure $foo.

Any script can now basically just run (as root on new installs where
unix_socket auth is on) something like
$ mysql -u root -e "CREATE user.."
and equivalent GRANT with database names, hostnames etc. They all
depend on the scenario. Therefor I am not sure if it makes sense to
add some dpkg-hooks for that.

If there was an old scenario that stopped working, maybe for backwards
compatiblity if would be justified to support at least that. But I did
not yet find the instructions on how what to run and how to
"reproduce" a failing situation that we could start tinkering with.
Will I see the failure if I run 'apt-get install zarafa', is that
where you stumbled across this issue in the first place?

Bug#812769: util-linux: no need to call grep

[Jörg-Volker Peetz]

Package: util-linux
Version: 2.27.1-2
Severity: wishlist

Dear Maintainer(s),

just a little nitpick regarding the fix of #791511 and the use of sed:

this line

if sed '3!d' /etc/adjtime | grep -q '^UTC$'; then

can be done without calling grep like

if [ `sed -n '3!d; /^UTC$/p' /etc/adjtime` ]; then

Regards,
Jörg-Volker.

Bug#807226: sip-tester: diff for NMU version 1:3.2-1.1

[Mattia Rizzolo]

Control: tags 807226 + pending

Dear maintainer,

I've prepared an NMU for sip-tester (versioned as 1:3.2-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

-- 
regards,
Mattia Rizzolo

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

 changelog |   10 ++
 control   |2 +-
 2 files changed, 11 insertions(+), 1 deletion(-)

diff -Nru sip-tester-3.2/debian/changelog sip-tester-3.2/debian/changelog
--- sip-tester-3.2/debian/changelog	2011-11-03 10:57:43.0 +
+++ sip-tester-3.2/debian/changelog	2016-01-26 12:16:25.0 +
@@ -1,3 +1,13 @@
+sip-tester (1:3.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Bas Couwenberg ]
+  * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev.
+Closes: #807226
+
+ -- Mattia Rizzolo   Tue, 26 Jan 2016 12:16:10 +
+
 sip-tester (1:3.2-1) unstable; urgency=low
 
   [ Paul Belanger ]
diff -Nru sip-tester-3.2/debian/control sip-tester-3.2/debian/control
--- sip-tester-3.2/debian/control	2011-11-03 10:56:09.0 +
+++ sip-tester-3.2/debian/control	2016-01-26 12:16:08.0 +
@@ -8,7 +8,7 @@
  libncurses5-dev,
  libnet1-dev,
  libpcap-dev,
- libgsl0-dev,
+ libgsl-dev,
 Build-Conflicts: libssl-dev
 Standards-Version: 3.8.4
 Homepage: http://sourceforge.net/projects/sipp/


signature.asc
Description: PGP signature

Bug#812770: pm-utils: randomly fail to resume from suspend to ram

[LudovicLemarinel]

Package: pm-utils
Version: 1.4.1-15
Severity: important


Hi,

I've recently bought a new laptop (Lenovo G70-70, model 80HW)
Since I own it, any debian version I've tested (stable and testing) 
were leading to the same problem :
I can put the computer to suspend-to-ram, but when I wake-up it, it will
randomly either :
- Reboot
- Kernel Panic (CAPS LOCK blinking, no more control, black screen without 
backlight)
- seem awake (black screen, no backlight, keyboard not responsive)
- resume properly : screen is on, everything is OK.

I've noticed that it will resume correctly more often if I resume it a few 
seconds/minutes after having putted it
on suspend, and it will always fail after a whole night.

I've also tried TuxOnIce suspend-to-disk, but had the same behavior (good 
resume if powered on just after suspend, fail if wait for a night...)

I've tried to blacklist mei_me and mei modules, while in singleuser mode, but 
no more success...

I'm ready to test patches, and other things !


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

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

Versions of packages pm-utils depends on:
ii  powermgmt-base  1.31+nmu1

Versions of packages pm-utils recommends:
ii  ethtool  1:4.2-1
ii  hdparm   9.43-2
ii  kbd  2.0.3-2
ii  procps   2:3.3.11-3
ii  vbetool  1.1-3

Versions of packages pm-utils suggests:
ii  cpufrequtils008-1
pn  radeontool  
ii  wireless-tools  30~pre9-8

-- no debconf information

Bug#812771: dput-ng: use lintian by default

[Hideki Yamane]

Package: dput-ng
Severity: wishlist
Tags: patch

Hi,

 I'd like to sent tiny patch to make dupload/dput/dput-ng enabled lintian
 by default. It intend to use lintian for many maintainers, at least.
 Maybe some of them just make it disabled again, but more maintainers
 would see their lintian report.

 It doesn't do any harm IMHO, but if this change make something wrong,
 you can just revert it. It is kind of experiment, you don't need to 
 feel fear for that change :)

-- 
Regards,

 Hideki Yamane henrich @ debian.or.jp/org
 http://wiki.debian.org/HidekiYamane
diff -Nru dput-ng-1.10/debian/changelog dput-ng-1.10+nmu1/debian/changelog
--- dput-ng-1.10/debian/changelog	2015-08-19 01:06:53.0 +0900
+++ dput-ng-1.10+nmu1/debian/changelog	2016-01-25 15:58:40.0 +0900
@@ -1,3 +1,10 @@
+dput-ng (1.10+nmu1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * enable lintian hook by default. 
+
+ -- Hideki Yamane   Mon, 25 Jan 2016 15:58:20 +0900
+
 dput-ng (1.10) unstable; urgency=medium
 
   * The "Goodbyte python-support" release
diff -Nru dput-ng-1.10/skel/profiles/DEFAULT.json dput-ng-1.10+nmu1/skel/profiles/DEFAULT.json
--- dput-ng-1.10/skel/profiles/DEFAULT.json	2015-08-19 01:01:06.0 +0900
+++ dput-ng-1.10+nmu1/skel/profiles/DEFAULT.json	2016-01-25 15:57:13.0 +0900
@@ -12,6 +12,6 @@
 "passive_ftp": true,
 "post_upload_command": "",
 "pre_upload_command": "",
-"run_lintian": false,
+"run_lintian": true,
 "scp_compress": true
 }
diff -Nru dput-ng-1.10/skel/profiles/ftp-master.json dput-ng-1.10+nmu1/skel/profiles/ftp-master.json
--- dput-ng-1.10/skel/profiles/ftp-master.json	2015-08-19 01:01:06.0 +0900
+++ dput-ng-1.10+nmu1/skel/profiles/ftp-master.json	2016-01-25 15:57:39.0 +0900
@@ -1,4 +1,7 @@
 {
+"+hooks": [
+"lintian"
+],
 "fqdn": "ftp.upload.debian.org",
 "incoming": "/pub/UploadQueue/",
 "login": "anonymous",
diff -Nru dput-ng-1.10/skel/profiles/mentors.json dput-ng-1.10+nmu1/skel/profiles/mentors.json
--- dput-ng-1.10/skel/profiles/mentors.json	2015-08-19 01:01:06.0 +0900
+++ dput-ng-1.10+nmu1/skel/profiles/mentors.json	2016-01-25 15:58:10.0 +0900
@@ -3,6 +3,9 @@
 "check-debs",
 "allowed-distribution"
 ],
+"+hooks": [
+"lintian"
+],
 "allowed_distributions": ".*",
 "fqdn": "mentors.debian.net",
 "incoming": ".",
diff -Nru dput-ng-1.10/skel/profiles/ssh-upload.json dput-ng-1.10+nmu1/skel/profiles/ssh-upload.json
--- dput-ng-1.10/skel/profiles/ssh-upload.json	2015-08-19 01:01:06.0 +0900
+++ dput-ng-1.10+nmu1/skel/profiles/ssh-upload.json	2016-01-25 15:57:46.0 +0900
@@ -1,4 +1,7 @@
 {
+"+hooks": [
+"lintian"
+],
 "fqdn": "ssh.upload.debian.org",
 "incoming": "/srv/upload.debian.org/UploadQueue/",
 "login": "*",
diff -Nru dput-ng-1.10/tests/dputng/profiles/DEFAULT.json dput-ng-1.10+nmu1/tests/dputng/profiles/DEFAULT.json
--- dput-ng-1.10/tests/dputng/profiles/DEFAULT.json	2015-08-19 01:01:06.0 +0900
+++ dput-ng-1.10+nmu1/tests/dputng/profiles/DEFAULT.json	2016-01-25 15:57:13.0 +0900
@@ -12,6 +12,6 @@
 "passive_ftp": true,
 "post_upload_command": "",
 "pre_upload_command": "",
-"run_lintian": false,
+"run_lintian": true,
 "scp_compress": true
 }

Bug#812772: dput: use lintian by default

[Hideki Yamane]

Package: dput
Severity: wishlist
Tags: patch

Hi,

 I'd like to sent tiny patch to make dupload/dput/dput-ng enabled lintian
 by default. It intend to use lintian for many maintainers, at least.
 Maybe some of them just make it disabled again, but more maintainers
 would see their lintian report.

 It doesn't do any harm IMHO, but if this change make something wrong,
 you can just revert it. It is kind of experiment, you don't need to 
 feel fear for that change :)

-- 
Regards,

 Hideki Yamane henrich @ debian.or.jp/org
 http://wiki.debian.org/HidekiYamane
>From 2fd507b75661c8ec2b9be07e8eaf613bdaddb854 Mon Sep 17 00:00:00 2001
From: Hideki Yamane 
Date: Mon, 25 Jan 2016 15:23:42 +0900
Subject: [PATCH] use lintian by default

It prevents more lintian error in archive, and will improve quality
of package
---
 debian/control | 3 ++-
 dput   | 2 +-
 dput.cf| 2 +-
 3 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/debian/control b/debian/control
index f16a1e6..b8f3019 100644
--- a/debian/control
+++ b/debian/control
@@ -10,7 +10,8 @@ Vcs-Browser: http://anonscm.debian.org/gitweb/?p=collab-maint/dput.git
 Package: dput
 Architecture: all
 Depends: python (>= 2.5), gnupg
-Suggests: openssh-client, lintian, mini-dinstall, rsync
+Recommends: lintian
+Suggests: openssh-client, mini-dinstall, rsync
 Description: Debian package upload tool
  dput allows you to put one or more Debian packages into the archive.  This
  package also includes a dcut utility which can be used to generate and / or
diff --git a/dput b/dput
index 8b6c105..2447138 100755
--- a/dput
+++ b/dput
@@ -101,7 +101,7 @@ def read_configs(extra_config, debug):
 config.set('DEFAULT', 'allow_dcut', '0')
 config.set('DEFAULT', 'distributions', '')
 config.set('DEFAULT', 'allowed_distributions', '')
-config.set('DEFAULT', 'run_lintian', '0')
+config.set('DEFAULT', 'run_lintian', '1')
 config.set('DEFAULT', 'run_dinstall', '0')
 config.set('DEFAULT', 'check_version', '0')
 config.set('DEFAULT', 'scp_compress', '0')
diff --git a/dput.cf b/dput.cf
index 9296262..b334fd3 100644
--- a/dput.cf
+++ b/dput.cf
@@ -7,7 +7,7 @@ method			= ftp
 hash			= md5
 allow_unsigned_uploads	= 0
 allow_dcut		= 0
-run_lintian		= 0
+run_lintian		= 1
 run_dinstall		= 0
 check_version		= 0
 scp_compress		= 0
-- 
2.7.0

Bug#811428: [debian-mysql] Bug#811428: Bug#811428: mysql-5.5: Multiple security fixes from the January 2016 CPU

[Salvatore Bonaccorso]

Hi Lars,

On Tue, Jan 26, 2016 at 01:11:45AM -0800, Lars Tangvald wrote:
> Wheezy package has been built and tested
> 
> At the moment it's just on my personal github at
> https://github.com/ltangvald/mysql-5.5/tree/debian/wheezy, but we
> should get it uploaded to Alioth soon.
> Attaching the debdiff and debian/ diff.

Thank you looks good to me.

I haven't seen the same for jessie, but assuming it is basically the
same and matching what you showed me initially from git, let's go
ahead with an upload.

Please remember to do the jessie-security first (built with -sa) and
then after ~20 minutes the wheezy-security one (explicitly without
-sa, and not including the orig source tarball; this is due to some
limitation in the archive software).

The upload needs to be signed by a a key in the DD keyring.

I will then wait for the builds and then take care of releasing the
packages with a DSA.

Regards,
Salvatore


signature.asc
Description: Digital signature

Bug#812740: RM: polarssl/experimental -- RoQA; superseded by mbedtls

[James Cowgill]

Package: ftp.debian.org
Severity: normal

Hi,

Please can you remove my polarssl NMU from experimental as well. It's
no longer needed now that everything's been ported to mbedtls.

Thanks,
James

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

Bug#810968: [debian-mysql] Bug#810968: mariadb-server-10.0: Logrotate exists 1 if a non-debian mysqld is running (e.g. containerized mysqld)

[Lennart Weller]

Well okay I didn't know the config files were being split up.
There are two options of the top of my head:

1) As you said. Just assume the pid file location
2) Check the parent process id being 1
   In this case parent of the parent because of mysqld_safe
   # test $(ps -o ppid= -p $(ps -o ppid= -p $PID)) -eq 1
   This would work in most cases I can think of. mysqld run by a user
   or a container would not be started by the init. But seems like a
   rather complex solution to a fairly simple problem.

January 26 2016 9:18 AM, "Otto Kekäläinen"  wrote:
> Thanks Lennart, the patch is much nicer to read now.
> 
> It seems to rely on the fact that it should find the line 'pid-file =
> /var/run/mysqld/mysqld.pid' in the file /etc/mysql/my.cnf
> 
> However, since the new mysql/mariadb config decoupling effort (driven
> by Ubuntu developers) the file /etc/mysql/my.cnf is no longer the main
> config file itself, and does not contain the pid line.
> 
> The actual line is now found in:
> grep pid /etc/mysql/mariadb.conf.d/*
> /etc/mysql/mariadb.conf.d/50-server.cnf:pid-file =
> /var/run/mysqld/mysqld.pid
> 
> Ironically simply assuming the exact location
> /var/run/mysqld/mysqld.pid would be more reliable than grepping the
> configs :)
> 
> I am glad the fix works in your situation in Debian Jessie.
> Unfortunately we need to think a bit more to come up with a universal
> solution.. I am happy to review any alternative solutions/patches
> anybody posts to this issue.

Bug#812759: RFA: whiteboard -- simple collaborative text editor for the web

[stigge]

Package: wnpp
Severity: normal

I'm not using this package regularly. Therefore, looking for a new maintainer.

Bug#812763: libadns1: Please provide Tor support

[Justus Winter]

Package: libadns1
Version: 1.5.0~rc1-1
Severity: wishlist
Tags: patch

Dear Maintainer,

please provide Tor support in libadns.  For your convenience I created
a branch with the relevant patches without any whitespace changes.
Please see the six topmost patches here:

http://git.gnupg.org/cgi-bin/gitweb.cgi?p=adns.git;a=shortlog;h=refs/heads/justus/tor

Thanks,
Justus

-- System Information:
Debian Release: 8.3
  APT prefers stable
  APT policy: (900, 'stable'), (350, 'unstable'), (300, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.18.0-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libadns1 depends on:
ii  libc6  2.19-18+deb8u2

libadns1 recommends no packages.

Versions of packages libadns1 suggests:
pn  adns-tools  

-- no debconf information

Bug#808694: x11proto-fonts: FTBFS: dh_install: x11proto-fonts-dev missing files (usr/share/doc/fontsproto/*.txt), aborting

[Andreas Boll]

This issue has been fixed in xutils-dev 1:7.7+4. See also #613674.

Thanks,
Andreas

On Mon, Dec 21, 2015 at 08:30:04PM +, Chris West (Faux) wrote:
> Source: x11proto-fonts
> Version: 2.1.3-1
> Severity: serious
> Justification: fails to build from source
> Tags: sid stretch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> The package fails to build:
> 
> make[1]: Leaving directory '/x11proto-fonts-2.1.3/build'
> dh_testdir
> dh_testroot
> dh_installdocs
> dh_installman
> find debian/tmp/usr/share/doc/fontsproto -name '*.xml' -delete
> dh_install --sourcedir=debian/tmp --fail-missing --exclude .db
> dh_install: x11proto-fonts-dev missing files 
> (usr/share/doc/fontsproto/*.txt), aborting
> debian/rules:70: recipe for target 'binary-indep' failed
> make: *** [binary-indep] Error 255
> dpkg-buildpackage: error: debian/rules binary gave error exit status 2
> 
> Full build log:
> https://reproducible.debian.net/rb-pkg/unstable/amd64/x11proto-fonts.html
> 
> -- System Information:
> Debian Release: stretch/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)


signature.asc
Description: Digital signature

Bug#811571: [Python-apps-team] Bug#811571: ocrfeeder: Unicode characters break exports

[Alberto Garcia]

Control: tags -1 moreinfo

On Tue, Jan 19, 2016 at 06:44:31PM -0500, Douglas Calvert wrote:
> Package: ocrfeeder
> Version: 0.8.1-2
> Severity: normal
> 
> Exporting is aborted if tesseract identifies any unicode
> character. Sample output:

Can you share a document that you can use to reproduce that bug? I
just tried with an image containing accented non-ascii characters and
I can export it just fine to PDF, TXT, HTML and ODT.

Berto

Bug#812747: debian-reference: Segmentation fault: when previous session ended with external link

[wim]

Package: debian-reference
Version: 2.58
Severity: normal

Hallo,

Simulation:
1. start $ debian-reference
2. go to an external page in the browser that is opened : 
eg 
file:///usr/share/debian-reference/ch06.en.html#_mail_transport_agent_mta 
this is http://packages.debian.org/jessie/exim4 for example
3. close the browser
4. start debian-reference again, > segmentation fault

Error given:
"
(WebKitWebProcess:31125): GLib-CRITICAL **: g_main_loop_run: assertion 'loop != 
NULL' failed
Received an unexpected URL from the web process: 
'file:///usr/share/debian-reference/ch06.en.html#_mail_transport_agent_mta'
Received an invalid message "WebProcessProxy.AddBackForwardItem" from the web 
process.
Received an unexpected URL from the web process: 
'file:///usr/share/debian-reference/index.html'
Received an invalid message "WebProcessProxy.AddBackForwardItem" from the web 
process.
Segmentation fault
Error receiving IPC message on socket -1 in process 31985: Ongeldige 
bestandsdescriptor
"

browser that gets opened 'epifany'

hth,
Wim


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

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

Versions of packages debian-reference depends on:
ii  debian-reference-en  2.58

Versions of packages debian-reference recommends:
pn  debian-reference-fr  
pn  debian-reference-it  
pn  debian-reference-ja  
pn  debian-reference-pt  

debian-reference suggests no packages.

-- no debconf information

Bug#812748: TypeError: argument of type '__main__.GLocalFile' is not iterable

[Sven Arvidsson]

Package: soundconverter
Version: 3.0.0~alpha1+git20151209-1
Severity: normal

I get this error when converting a FLAC file to Ogg Vorbis:

Traceback (most recent call last):
  File "/usr/share/soundconverter/python/soundconverter/ui.py", line 1322, in 
on_convert_button_clicked
self.do_convert()
  File "/usr/share/soundconverter/python/soundconverter/ui.py", line 1304, in 
do_convert
self.converter.add(sound_file)
  File "/usr/share/soundconverter/python/soundconverter/gstreamer.py", line 
692, in add
c.init()
  File "/usr/share/soundconverter/python/soundconverter/gstreamer.py", line 
531, in init
log('Creating folder: \'%s\'' % beautify_uri(dirname))
  File "/usr/share/soundconverter/python/soundconverter/fileoperations.py", 
line 35, in beautify_uri
return unquote_filename(uri).split('file://')[-1]
  File "/usr/share/soundconverter/python/soundconverter/fileoperations.py", 
line 31, in unquote_filename
return urllib.parse.unquote(filename)
  File "/usr/lib/python3.5/urllib/parse.py", line 537, in unquote
if '%' not in string:
TypeError: argument of type '__main__.GLocalFile' is not iterable

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

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

Versions of packages soundconverter depends on:
ii  gir1.2-gconf-2.0   3.2.6-3
ii  gir1.2-glib-2.01.46.0-3
ii  gir1.2-gstreamer-1.0   1.6.3-1
ii  gir1.2-gtk-3.0 3.18.6-1
ii  gstreamer1.0-plugins-base  1.6.3-1
ii  gstreamer1.0-plugins-good  1.6.3-1
ii  python3-gi 3.18.2-2
pn  python3:any

Versions of packages soundconverter recommends:
ii  gir1.2-notify-0.7   0.7.6-2
ii  gstreamer1.0-libav  1.6.3-1

Versions of packages soundconverter suggests:
ii  gstreamer1.0-plugins-ugly  1.6.3-1

-- no debconf information

Bug#812750: wine: Gecko integration is broken

[Ralf Jung]

Package: wine
Version: 1.8-6
Severity: important

Dear Maintainer,

>From all I can tell, the Gecko integration is entirely broken. There is no 
>wine-gecko packaged in Debian
(the recommendation of libwine-gecko-2.40 is unsatisfiable), no download window 
appears to fetch wine-gecko
from the WineHQ servers instead, and even if I do that manually and put the msi 
files into
/usr/share/wine/gecko, wine does not even bother to install them. The docs 
(confusingly) say I should
put the file into /usr/share/wine-development/gecko, but that does not work 
either.

This breaks each and every windows application that needs the embedded browser.

Pleaswe make it possible to use gecko with the wine packages.

Kind regards,
Ralf

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

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

Versions of packages wine depends on:
ii  wine32  1.8-6
ii  wine64  1.8-6

wine recommends no packages.

Versions of packages wine suggests:
pn  dosbox   
pn  wine-binfmt  

Versions of packages wine is related to:
ii  fonts-wine1.8-6
ii  libwine   1.8-6
pn  libwine-dbg   
pn  libwine-dev   
ii  wine  1.8-6
ii  wine321.8-6
pn  wine32-preloader  
pn  wine32-tools  
ii  wine641.8-6
pn  wine64-preloader  
pn  wine64-tools  

-- no debconf information

Bug#812755: RFA: spass -- An automated theorem prover for first-order logic with equality

[stigge]

Package: wnpp
Severity: normal

I'm not using this package regularly. Therefore, looking for a new maintainer. 
There was no upstream release since 2010.

Bug#812731: RM: mate-system-tools -- RoM; abandoned upstream

[Mike Gabriel]

Hi Adam,

On  Di 26 Jan 2016 11:25:10 CET, Adam D. Barratt wrote:


On 2016-01-26 10:15, Mike Gabriel wrote:

Hi Adam,

On  Di 26 Jan 2016 10:58:41 CET, Adam D. Barratt wrote:


On 2016-01-26 8:25, Mike Gabriel wrote:

[...]

A removal request has also been
sent to the ftpmasters for the package version found in unstable.


In that case there's no need for an explicit removal from testing.  
 Once the unstable removal is processed it will automatically  
become  a candidate for removal from testing.

[...]

"""
Removals from the oldstable, stable and testing distributions should
be requested by e-mailing the (Stable) Release Managers
debian-rele...@lists.debian.org or filing a bug against the
release.debian.org pseudo-package (using the same format described in
this document; additionally, you should be nice by usertagging your
bugs with usertag rm and user release.debian@packages.debian.org).
"""

Whereas this may be true during the freeze phase, it doesn't seem to
apply to non-freeze phases of Debian testing, right?


It applies at any time where the package should be removed from  
testing but not also from unstable. Freeze is a common time when  
that will happen, but it's not the only one (e.g. if a maintainer  
feels that their package is not release-quality and does not wish to  
wait for an autoremoval to kick in but plans to fix it in unstable  
eventually, if the package should not be included in the release but  
is being kept in unstable for compatibility reasons, if it is  
blocking a transition and the maintainer is happy for it not to be  
in testing for a short while, etc.)


(It should now say to file a bug for {,old}stable removals as well, however.)

Regards,

Adam


thanks for explaining the details on this.

;-)
Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/mailxchange/kronolith/fb.php?u=m.gabriel%40das-netzwerkteam.de


pgpoVqicbHwg8.pgp
Description: Digitale PGP-Signatur

Bug#802659: dbus-python: Please drop recommends on PyQt4 packages

[Dmitry Shachnev]

Hi Simon,

On Wed, Jan 20, 2016 at 09:15:24AM +, Simon McVittie wrote:
> Sorry for the delay in responding to this; dbus-python hasn't been high
> on my priority list.

No problem!

> On Thu, 22 Oct 2015 at 12:29:54 +0300, Dmitry Shachnev wrote:
>>   Drop obsolete recommendations of Qt 4 packages
> ...
>>   * python3-dbus.mainloop.qt is a package providing support for Qt (4.x) main
>> loop. However, Qt uses GLib main loops on UNIX systems by default, so 
>> this
>> package is needed very rarely and we should not recommend it.
>
> I'd be happy enough to do this, but I'd like to give the Qt/KDE
> maintainers (Cc'd) the opportunity to object first, so that if I get
> bug reports asking me to revert the change because someone feels that
> python[3]-gi is insufficiently desktop-neutral, I can point the bug
> reporter to the relevant discussion and close the bug.

The list you added is mostly for robots, the one we actually use is what I
CCed now. Though I was filing this bug with my Qt/PyQt co-maintainer hat,
so that's probably not much needed :)

> The library can be used without main loop support, and it doesn't
> really care which main loop glue you use (options are currently GLib,
> (GLib via) Qt, or E); but the majority of its functionality relies
> on having *some* main loop glue for dbus-python, and then running a
> compatible main loop in your program.  I included the Recommends so
> that "apt install python{,3}-dbus" would give users enough modules to
> run locally-written programs similar to dbus-python's own examples.
> See  for further context.

My point was that Qt main loop is usually used on Windows / OS X but *not*
on Debian. Here, Qt is compiled with GLib support and will use GLib main
loop unless explicitly asked not to do so (via QT_NO_GLIB=1 env variable).
That is a very rare use case and I don't see why one will ever need it.

So I still think these packages should not be recommended. If they are,
(Py)Qt developers will have a false assumption that they probably need them.

> (Anything that specifically imports dbus.mainloop.whatever should of course
> continue to depend on the appropriate package.)
>
> This main loop glue nonsense is an artefact of dbus-python trying hard
> to be non-desktop-specific. With hindsight, that was a bad idea, and
> these days I much prefer self-contained D-Bus implementations/bindings
> (GDBus, QtDBus, sd-bus) that assume a particular main-loop framework
> and can benefit from being properly integrated with it.
>
>>   * python-qt4-dbus is a replacement for dbus-python; if one uses one 
>> package,
>> he will not need the other.
>
> Really? It looks a lot like a direct equivalent of python3-dbus.mainloop.qt
> to me:
> 
> % dpkg -L python-qt4-dbus
> [... the usual /usr/share/doc noise ...]
> [... some directories ... ]
> /usr/lib/python2.7/dist-packages/dbus/mainloop/qt.so
>
> Its name is presumably for historical reasons; if it was created today,
> it would be named python-dbus.mainloop.qt.

Oh, sorry, you are right and I was indeed confused by the name.

> At the time dbus-python was written, PyQt did not bind QtDBus; now it
> does (which I believe was partially a response to how long it took to
> make dbus-python work in Python 3), and I would advise developers who are
> using Python with Qt to consider using the QtDBus bindings in preference
> to dbus-python. dbus-python is not actually a great API, and has
> several historical design mistakes, which we can't correct because its
> most significant advantage over other D-Bus bindings/implementations
> is compatibility with older versions of itself. I haven't tried QtDBus
> but I suspect it may be better, or at least present a more Qt-like API.

dbus-python is still useful for those who need a simple Python API and don't
want to depend on bigger libraries like Qt and GLib/Gtk.

>>   In the description of python-dbus-dev, replace dbus.mainloop.qt with
>>   dbus.mainloop.pyqt5, which is the modern successor of dbus.mainloop.qt.
>
> Done in git, thanks.
>
>>   Also, drop the alternative recommendation for python-gobject-2. That
>>   package has been deprecated for a long time and we want to remove it from
>>   the archive as soon as possible.
>
> Also done, thanks.

Thanks!

> I'll apply the remaining changes (losing the Qt equivalents from
> Recommends) if there's consensus that this is what people who like
> Qt want me to do.

If you don't remove these packages from Recommends, then at least please
replace them with their modern PyQt5 alternatives, i.e.:

python-qt4-dbus → python-dbus.mainloop.pyqt5
python3-dbus.mainloop.qt → python3-dbus.mainloop.pyqt5

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#812761: ITP: flif -- Free Lossless Image Format (FLIF) encoder/decoder

[Jon Sneyers]

Package: wnpp
Severity: wishlist
Owner: Jon Sneyers 

* Package name: flif
  Version : 0.2.0
  Upstream Author : Jon Sneyers 
* URL : http://flif.info/
* License : Currently: GPLv3+ (encoder), LGPLv3+ (decoder)
(will probably change soon to more permissive license)
  Programming Lang: C++
  Description : Free Lossless Image Format (FLIF) encoder/decoder
 FLIF is a lossless image (and animation) format.
 It tends to compress better than other image compression formats.
 This is the reference implementation of the FLIF encoder/decoder.
 The command-line utility 'flif' converts FLIF to/from PNG or PNM.



The source package would have multiple binary packages:
- flif (command line tool)
- libflif (shared library)
- viewflif (simple image/animation viewer)
- gif2flif (shell script)
- apng2flif (shell script)

I am trying to put all necessary Debian packaging config files directly
in the upstream git repository, at:  https://github.com/FLIF-hub/FLIF

Version 0.2.0 of flif has not actually been released yet, the most recent
version is 0.2.0rc5, which may or may not become 0.2.
At some point in February 2016, I expect to go from "release candidate" to
the actual "release".
This will be the first 'stable' release (in the sense that the file format
will remain compatible). I hope to have flif included in the Debian archive
when this release will be announced.

I am new at Debian packaging, so while I _think_ most of the packaging
work is done, it would help to have a more experienced co-maintainer
who can check and improve my effort at packaging.
Also I will certainly need a sponsor.

Bug#797210: [debian-mysql] mariadb-10.0: mariadb-server does not ship a debconf set for creating a adminitrative user (like mysql-server do)

[Carsten Schoenert]

Hello Otto,

shame on me, I marked this email to answer but didn't have done this
yet.

On Sat, Jan 02, 2016 at 12:07:15AM +0200, Otto Kekäläinen wrote:
> I have updated the README, see
> https://github.com/ottok/mariadb-10.0/commit/817a2fbe6bdeb76f7f076f745574ae3a865f35f4

Guido Guenther pointed me also to the available unix socket on the local
machine, that's much better than a SQL root user with a password people
mostly forget. So yes, this README is better now.

> Unfortunately I don't understand dbconfig-common enough to know what I
> should do to accomodate the automation.

Well, a possible solution can be to create a dbconfig-common dialogue
that's asking the user if he wants to set up a root user. And a short
explanation in this dialogue where such a setup is appropriate and then
it's not.

> Where does it fall short now?  On new installs you can just run as
> root mysqld and execute whatever you want, it is very simple.

Ack

> I skimmed through
> https://people.debian.org/~seanius/policy/dbconfig-common.html/ but
> didn't really get the hang of it. The docs are written for "consumers"
> and not "providers" like the mariadb-10.0 package maintainers would
> need to read about.

I don't get this point, what do you mean between consumer and provider?
As a package maintainer you need to ensure thet the user who is installing
your package is guided through the installation so the package is
completely configured and running after the installation.

For mariadb-server this means the user should be noticed about the
"normal" unix socket authentication mechanism and the alternative
classical user/password possibility.
This must can be done via dbconfig-common but should be available in the
documentation so a user like me (I'm not very experienced in setting up
databases) will now what to do.

> Feel free to send in pull requests / git merge requests if you have
> ideas for improvement. I promise to review them quickly.

I'm corrently a little bit short on time so I can't provide more usefull
pieces.
Once the zarafa [1] package is gone into experiemental we will get more
experience on setting up automatically the needed database and I can
provide some suggestions. This workes already but the database may be
running on another host for example.

For now feel free to close this report as you expanded the README about
this topic.

[1] https://ftp-master.debian.org/new/zarafa_7.2.1~RC51272+dfsg1-1.html

Regards
Carsten

Bug#808141: sponsorship-requests: Dear mentors, I am looking for a sponsor for my package eclipse-titan.

[Pilisi Gergely]

Hi,

2016-01-25 18:27 GMT+01:00 Mattia Rizzolo :

>
> So, given that those are still warnings (that would be nice to get rid
> of), and that are for sure not blockers, what would you think about
>
uploading it as it's now and work on it on a later time?
>

I think that's a good idea, we will sort it out later. The latest upload is
available on the mentors site.
Anyway this whole procedure was a really important experience, some
modification will be done on the upstream side to.
So I hope with the next release we will move forward much faster. Thank you
for being so patient with me. :)

BR,
Gergely

Bug#808164: [rt.debian.org #6115] AutoReply: Please add Ondřej Nový's key to the DM keyring

[Aníbal Monsalve Salazar]

Control: package debian-maintainers
Control: tags -1 + pending

Hello Ondřej Nový,

Your DM application was accepted and the corresponding RT ticket is
posted at https://rt.debian.org/Ticket/Display.html?id=6115

Currently, rt.debian.org isn't accessible for the general public. It
was so sometime ago. Maybe one of your advocates will look at your RT
ticket for you, after it has been taken by a keyring maintainer. See
http://wiki.debian.org/rt.debian.org

Not urgent but please try to get more OpenPGP signatures from DDs and
sign theirs keys as well. :-)

Thank you for your contribution to the Debian Project.

Cheers,

Aníbal

On Tue, 2016-01-26 11:47:25 +, Debian Keyring requests (Incoming) via RT 
wrote:
> This message has been automatically generated in response to the
> creation of a trouble ticket regarding
>
>   "Please add Ondřej Nový's key to the DM keyring",
>
> a summary of which appears below the dashed line.
>
> There is no need to reply to this message right now.  Your ticket has
> been assigned an ID of [rt.debian.org #6115].
>
> Please include the string
>
>   [rt.debian.org #6115]
>
> in the subject line of all future correspondence about this issue. To
> do so, you may reply to this message.
>
> -
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> keyring-maint:
>   please add key ID 3D983C52EB85980C46A56090357312559D1E064B
> to the DM keyring
>   please notify 808164-d...@bugs.debian.org
> 
> Changed-By: Anibal Monsalve Salazar 
> Date: Tue, 26 Jan 2016 11:11:14 +
> BTS: https://bugs.debian.org/808164
> Comment: Add Ondřej Nový as a Debian Maintainer
> Agreement: https://lists.debian.org/debian-newmaint/2015/12/msg7.html
> Advocates:
>   zigo - https://lists.debian.org/debian-newmaint/2015/12/msg9.html
> KeyCheck:
>   pub   4096R/9D1E064B 2015-09-14 [expires: 2019-09-14]
> Key fingerprint = 3D98 3C52 EB85 980C 46A5  6090 3573 1255 9D1E 064B
>   uid  Ondřej Nový 
>   sig! AC6B43FE 2015-11-02  Thomas Goirand 
>   sig!39D1E064B 2015-09-14  Ondřej Nový 
>   uid  Ondřej Nový 
>   sig! AC6B43FE 2015-11-02  Thomas Goirand 
>   sig!39D1E064B 2015-09-14  Ondřej Nový 
>   sub   4096R/FE740077 2015-09-14 [expires: 2019-09-14]
>   sig! 9D1E064B 2015-09-14  Ondřej Nový 
>   .
>   Key is OpenPGP version 4 or greater.
>   Key has 4096 bits.
>   Valid "e" flag, expires Sat 14 Sep 2019 15:23:15 UTC.
>   Valid "s" flag, expires Sat 14 Sep 2019 15:23:15 UTC.
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1
> 
> iQIcBAEBCgAGBQJWp1wBAAoJEHxWrP6UeJfY+9EP/ibMJa+rc8vpF58REeD3265D
> ExiOmcTaTCpTuXYb+ZyVqpNmPP9OjjFKPFyNpg+wYRUAZ8mJmyZPDOtK6NBxdN89
> Q+ddNNscHABlrkjdv6iQpE3ub8I918Sd7sKJ6uCSASW9RABgvqwlob98GPIsRwWg
> ghXiVTOyhUmU73kbKbdJ3TKxjpWsy3Hklrn2An0MVwo0ISdU6KtEtf1GOrko+kJ1
> fZPDuevpfXdu8rYcutGjPRSI9uv+vERpPRXhfa0OUV7kPVUjm9RSrRAJbVm1Uxp0
> aY28fGnwTF4vrg3AIFQUREJvp8nIUyn9KpUmxT5nnHaap9JVEwSY+jBJnfwZXjzt
> nGJIKzwf8uW7Z6WJIseJ93TRSUByQ+FN/2WSxHQi/hzRBYHbet1CcEcDX018Ly9l
> jMfJvlJTl6tlhjLp6oZnQ7hlLqJib+gYDd/wtaUmsLDxQeF0AQnl6oN07t2Bd5E4
> qXwCNISFG78TJ3UpvInsCo20aI7sK05RjqX1F7BZtsLmq7I/9ovRax0OZWY2wY1H
> f59q5NhngLKZyKcVpS5cwudSrZtmYnxUckpsCZNHKvcVToIUbr2zu/ov3Xk239GG
> JwkWq+2viCtFX+w1kSRz762cGAdaAo/kj28+rZtNdLXJTZrmOqHC/oEIv64Ii6ld
> J/o/8RgXUWj441oC9Ew2
> =bpyO
> -END PGP SIGNATURE-


signature.asc
Description: Digital signature

Bug#812767: r-bioc-genefilter: conflicting declarations of function gf_distance

[Michael Tautschnig]

Package: r-bioc-genefilter
Version: 1.52.0-1
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error. Please note that we
use our research compiler tool-chain (using tools from the cbmc package), which
permits extended reporting on type inconsistencies at link time.

g++ -shared -L/usr/lib/R/lib -Wl,-z,relro -o genefilter.so half_range_mode.o 
init.o nd.o pAUC.o rowPAUCs.o rowttests.o ttest.o -lgfortran -lm -lquadmath 
-L/usr/lib/R/lib -lR

file nd.c line 270: error: conflicting parameter counts of function 
declarations `gf_distance'
old definition in module `init' file genefilter.h line 5
void (double *, double *, signed int *, signed int *, double *, signed int *, 
signed int *)
new definition in module `nd' file nd.c line 270
void (double *x, signed int *nr, signed int *nc, signed int *g, double *d, 
signed int *iRow, signed int *nInterest, signed int *nResults, signed int 
*method, double *wval)

/usr/share/R/share/make/shlib.mk:6: recipe for target 'genefilter.so' failed
make[1]: *** [genefilter.so] Error 1
make[1]: Leaving directory 
'/srv/jenkins-slave/workspace/sid-goto-cc-r-bioc-genefilter/r-bioc-genefilter-1.52.0/src'

It seems the declaration in genefilter.h and the definition in nd.c are highly
inconsistent as not only the number, but also the individual types do not match
up. This will cause misaligned stack accesses.

Best,
Michael



signature.asc
Description: PGP signature

Bug#812768: python-whoosh: FTBFS - tests fail with "No such file or directory: ... english-words.10.gz"

[Michael Tautschnig]

Package: python-whoosh
Version: 2.7.0-1
Severity: serious
Usertags: goto-cc

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.

[...]
tests/test_sorting.py ..
tests/test_spans.py ...
tests/test_spelling.py F.
tests/test_tables.py .
tests/test_vectors.py .
tests/test_weightings.py ..
tests/test_writing.py .

=== FAILURES ===
___ test_levenshtein ___
Traceback (most recent call last):
  File 
"/srv/jenkins-slave/workspace/sid-goto-cc-python-whoosh/python-whoosh-2.7.0/.pybuild/pythonX.Y_2.7/build/tests/test_automata.py",
 line 188, in test_levenshtein
wordfile = gzip.open(path, "rb")
  File "/usr/lib/python2.7/gzip.py", line 34, in open
return GzipFile(filename, mode, compresslevel)
  File "/usr/lib/python2.7/gzip.py", line 94, in __init__
fileobj = self.myfileobj = __builtin__.open(filename, mode or 'rb')
IOError: [Errno 2] No such file or directory: 
'/srv/jenkins-slave/workspace/sid-goto-cc-python-whoosh/python-whoosh-2.7.0/.pybuild/pythonX.Y_2.7/build/tests/english-words.10.gz'
___ test_levenshtein_prefix 
Traceback (most recent call last):
  File 
"/srv/jenkins-slave/workspace/sid-goto-cc-python-whoosh/python-whoosh-2.7.0/.pybuild/pythonX.Y_2.7/build/tests/test_automata.py",
 line 209, in test_levenshtein_prefix
wordfile = gzip.open(path, "rb")
  File "/usr/lib/python2.7/gzip.py", line 34, in open
return GzipFile(filename, mode, compresslevel)
  File "/usr/lib/python2.7/gzip.py", line 94, in __init__
fileobj = self.myfileobj = __builtin__.open(filename, mode or 'rb')
IOError: [Errno 2] No such file or directory: 
'/srv/jenkins-slave/workspace/sid-goto-cc-python-whoosh/python-whoosh-2.7.0/.pybuild/pythonX.Y_2.7/build/tests/english-words.10.gz'
 test_wordfile _
Traceback (most recent call last):
  File 
"/srv/jenkins-slave/workspace/sid-goto-cc-python-whoosh/python-whoosh-2.7.0/.pybuild/pythonX.Y_2.7/build/tests/test_spelling.py",
 line 84, in test_wordfile
wordfile = gzip.open(path, "rb")
  File "/usr/lib/python2.7/gzip.py", line 34, in open
return GzipFile(filename, mode, compresslevel)
  File "/usr/lib/python2.7/gzip.py", line 94, in __init__
fileobj = self.myfileobj = __builtin__.open(filename, mode or 'rb')
IOError: [Errno 2] No such file or directory: 
'/srv/jenkins-slave/workspace/sid-goto-cc-python-whoosh/python-whoosh-2.7.0/.pybuild/pythonX.Y_2.7/build/tests/english-words.10.gz'
 3 failed, 556 passed in 31.08 seconds =
E: pybuild pybuild:274: test: plugin distutils failed with: exit code=1: cd 
/srv/jenkins-slave/workspace/sid-goto-cc-python-whoosh/python-whoosh-2.7.0/.pybuild/pythonX.Y_2.7/build;
 python2.7 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 --dir . 
returned exit code 13
debian/rules:5: recipe for target 'build' failed
make: *** [build] Error 25


The full build log is attached; please do let me know if the problem is
unreproducible, in which case I shall try to investigate further.

Best,
Michael


python-whoosh-build-log.txt.gz
Description: application/gunzip


signature.asc
Description: PGP signature

Bug#812741: neovim: Please don't build-depend on luajit on unsupported architectures

[John Paul Adrian Glaubitz]

Package: neovim
Version: 0.1.1-3
Severity: important
User: debian-sp...@lists.debian.org
Usertags: sparc64

Hello!

neovim is currently BD-Uninstallable on a number of architectures which
are not supported by luajit [1]. I would therefore like to ask to limit
the list of architectures for which neovim build-depends on libluajit-5.1-dev,
similar to what haskell-hslua does [2].

Thanks,
Adrian

> [1] https://buildd.debian.org/status/package.php?p=neovim=experimental
> [2] 
> https://anonscm.debian.org/cgit/pkg-haskell/DHG_packages.git/tree/p/haskell-hslua/debian/control

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

Bug#812626: libfreecontact-perl: FTBFS - Parse errors: Bad plan. You planned 10 tests but ran 6.

[Andreas Tille]

Hi Perl team,

do you have any idea what change might have caused the failures of the
test suite?

Feel free to commit proposed changes to Debian Med Git if this might
simplify your workflow.

Kind regards

Andreas.

On Mon, Jan 25, 2016 at 04:39:25PM +, Michael Tautschnig wrote:
> Package: libfreecontact-perl
> Version: 0.08-4
> Severity: serious
> Usertags: goto-cc
> 
> During a rebuild of all Debian packages in a clean sid chroot (using 
> cowbuilder
> and pbuilder) the build failed with the following error.
> 
> [...]
> make[1]: Leaving directory 
> '/srv/jenkins-slave/workspace/sid-goto-cc-libfreecontact-perl/libfreecontact-perl-0.08'
>dh_auto_test -O--parallel
>   make -j1 test TEST_VERBOSE=1
> make[1]: Entering directory 
> '/srv/jenkins-slave/workspace/sid-goto-cc-libfreecontact-perl/libfreecontact-perl-0.08'
> Running Mkbootstrap for FreeContact ()
> chmod 644 "FreeContact.bs"
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
> "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 
> 'blib/arch')" t/*.t
> t/01FreeContact.t .. 
> 1..3
> ok 1 - use FreeContact;
> ok 2 - FreeContact->can(...)
> ok 3 - FreeContact::Predictor->can(...)
> ok
> will use 1 OMP threads
> SSE2 veczweight, wchunk = 32
> total weight (variation) of alignment = 620.777515304633
> 
> seq weight loop for 1000 seqs took 0.012224 secs
> will use 1 OMP threads
> calculated column aa frequencies, gap cols = 4
> calculated pair frequency table in 0.192089 secs
> collected apc_mean[MI] = 0.174031486973761
> aa freq sum (cell) = 0.97158936352, pairfreq sum (cell) = 
> 0.94420985606
> formed covariance matrix (122/126,4)
> LU factorization took 9.17976 secs, inverted matrix (incl LUf) in 23.7932 secs
> density of inverse covariance matrix = 1 (cksum 346842.2)
> went back to gapped (126) wwi matrix
> collected apc_mean[l1norm] = 117.987054769839
> collected apc_mean[fro] = 3.35437751555787
> all done in 24.6311 secs
> will use 1 OMP threads
> SSE2 veczweight, wchunk = 32
> total weight (variation) of alignment = 561.595172234625
> t/02test.t . 
> 1..10
> ok 1 - use FreeContact;
> ok 2 - An object of class 'FreeContact::Predictor' isa 
> 'FreeContact::Predictor'
> ok 3
> ok 4
> ok 5 - precision test
> ok 6 - timing results test
> Failed 4/10 subtests
> 
> Test Summary Report
> ---
> t/02test.t   (Wstat: 11 Tests: 6 Failed: 0)
>   Non-zero wait status: 11
>   Parse errors: Bad plan.  You planned 10 tests but ran 6.
> Files=2, Tests=9, 25 wallclock secs ( 0.06 usr  0.00 sys + 24.63 cusr  0.22 
> csys = 24.91 CPU)
> Result: FAIL
> Failed 1/2 test programs. 0/9 subtests failed.
> Makefile:995: recipe for target 'test_dynamic' failed
> make[1]: *** [test_dynamic] Error 255
> make[1]: Leaving directory 
> '/srv/jenkins-slave/workspace/sid-goto-cc-libfreecontact-perl/libfreecontact-perl-0.08'
> dh_auto_test: make -j1 test TEST_VERBOSE=1 returned exit code 2
> debian/rules:8: recipe for target 'build' failed
> make: *** [build] Error 2
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
> I: Copying back the cached apt archive contents
> I: new cache content libextutils-xspp-perl_0.1800-2_all.deb added
> I: new cache content libfreecontact-dev_1.0.21-4_amd64.deb added
> I: new cache content libfreecontact0v5_1.0.21-4_amd64.deb added
> I: unmounting /srv/jenkins-slave/workspace/sid-goto-cc-libfreecontact-perl 
> filesystem
> I: unmounting /run/shm filesystem
> I: unmounting dev/pts filesystem
> I: unmounting run/shm filesystem
> I: unmounting proc filesystem
>  -> Cleaning COW directory
>   forking: rm -rf /srv/jenkins-slave/cow/cow.42349
> 
> 
> The full build log is attached; please do let me know if the problem is
> unreproducible, in which case I shall try to investigate further.
> 
> Best,
> Michael





> ___
> Debian-med-packaging mailing list
> debian-med-packag...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging


-- 
http://fam-tille.de

Bug#812731: RM: mate-system-tools -- RoM; abandoned upstream

[Mike Gabriel]

Hi Adam,

On  Di 26 Jan 2016 10:58:41 CET, Adam D. Barratt wrote:


On 2016-01-26 8:25, Mike Gabriel wrote:

Package: release.debian.org
X-Debbugs-Cc: pkg-mate-t...@lists.alioth.debian.org

Dear release team,

please remove mate-system-tools from Debian testing (aka stretch). It
is not continued upstream anymore. A removal request has also been
sent to the ftpmasters for the package version found in unstable.


In that case there's no need for an explicit removal from testing.  
Once the unstable removal is processed it will automatically become  
a candidate for removal from testing.


Regards,

Adam


ah, ok. Then probably it is required to update the section "Removals  
from testing, stable and oldstable" on this [1] wiki page.


There it currently says:

"""
Removals from the oldstable, stable and testing distributions should  
be requested by e-mailing the (Stable) Release Managers  
debian-rele...@lists.debian.org or filing a bug against the  
release.debian.org pseudo-package (using the same format described in  
this document; additionally, you should be nice by usertagging your  
bugs with usertag rm and user release.debian@packages.debian.org).

"""

Whereas this may be true during the freeze phase, it doesn't seem to  
apply to non-freeze phases of Debian testing, right?


Greets,
Mike

[1] https://wiki.debian.org/ftpmaster_Removals
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/mailxchange/kronolith/fb.php?u=m.gabriel%40das-netzwerkteam.de


pgpiifinfrEgN.pgp
Description: Digitale PGP-Signatur

Bug#811451: linux-grsec-base: Some useful confs

[Yves-Alexis Perez]

On lun., 2016-01-25 at 22:24 +, ban...@openmailbox.org wrote:
> > So at one point one should draw a line. It's dead easy to edit the 
> > config, so
> > one has just to make sure people can find the information. I don't 
> > really want
> > to make a debconf script for that, but it could be a possibility too.
> 
> After testing in KVM with custom settings the VM couldn't boot. Can you 
> please compile the grsec patch with host virtualization (KVM) support?

I don't touch any KVM settings so it /should/ work as is. Without more
information I can't do anything. Also please try not to report new stuff on
existing bugs.

Regards,
-- 
Yves-Alexis



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

Bug#812207: linux: AUFS can hang up; Please update to v20160111 or later

[Roger Shimizu]

On Tue, Jan 26, 2016 at 10:36 AM, Ben Hutchings  wrote:
> On Thu, 21 Jan 2016 15:08:17 + Akihiro Suda  wrote:
>
> Please use 'reportbug kernel' to report any future kernel bugs, as that
> will select the correct package name automatically.

I didn't find this command to report bug in wiki [0][1], which is
better to add them.

[0]: https://wiki.debian.org/DebianKernel
[1]: https://wiki.debian.org/DebianKernelReportingBugs

-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 17B3ACB1

Bug#806498: x11proto-core: FTBFS: dh_install: x11proto-core-dev missing files (usr/share/doc/x11proto-core-dev/*.txt), aborting

[Andreas Boll]

This issue has been fixed in xutils-dev 1:7.7+4. See also #613674.

Thanks,
Andreas

On Fri, Nov 27, 2015 at 11:31:12PM +, Chris West (Faux) wrote:
> Source: x11proto-core
> Version: 7.0.27-1
> Severity: serious
> Justification: fails to build from source
> Tags: sid 
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: ftbfs
> X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org
> 
> Dear Maintainer,
> 
> The package fails to build:
> 
> make[2]: Leaving directory '/x11proto-core-7.0.27/build'
> make[1]: Leaving directory '/x11proto-core-7.0.27'
>debian/rules override_dh_install
> make[1]: Entering directory '/x11proto-core-7.0.27'
> find debian/tmp/usr/share/doc/x11proto-core-dev -name '*.xml' -delete
> find debian/tmp/usr/share/doc/x11proto-core-dev -name '*.db' -delete
> find debian/tmp/usr/share/doc/x11proto-core-dev -name '*.ps' -delete
> dh_install --fail-missing
> dh_install: x11proto-core-dev missing files 
> (usr/share/doc/x11proto-core-dev/*.txt), aborting
> debian/rules:17: recipe for target 'override_dh_install' failed
> make[1]: *** [override_dh_install] Error 255
> 
> Full build log:
> https://reproducible.debian.net/rb-pkg/unstable/amd64/x11proto-core.html
> 
> -- System Information:
> Debian Release: stretch/sid
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)


signature.asc
Description: Digital signature

Bug#807186: bist: diff for NMU version 0.5.2-1.1

[Mattia Rizzolo]

Control: tags 807186 + pending

Dear maintainer,

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

Regards.

-- 
regards,
Mattia Rizzolo

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

 changelog |   10 ++
 control   |2 +-
 2 files changed, 11 insertions(+), 1 deletion(-)

diff -Nru bist-0.5.2/debian/changelog bist-0.5.2/debian/changelog
--- bist-0.5.2/debian/changelog	2012-04-09 08:48:42.0 +
+++ bist-0.5.2/debian/changelog	2016-01-26 11:47:31.0 +
@@ -1,3 +1,13 @@
+bist (0.5.2-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Bas Couwenberg ]
+  * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev.
+Closes: #807186
+
+ -- Mattia Rizzolo   Tue, 26 Jan 2016 11:47:21 +
+
 bist (0.5.2-1) unstable; urgency=low
 
   * New upstream version
diff -Nru bist-0.5.2/debian/control bist-0.5.2/debian/control
--- bist-0.5.2/debian/control	2012-04-09 08:48:42.0 +
+++ bist-0.5.2/debian/control	2016-01-26 11:47:18.0 +
@@ -15,7 +15,7 @@
  , libplot-dev
  , libexpat1-dev
  , libxpm-dev
- , libgsl0-dev
+ , libgsl-dev
  , libcurl4-gnutls-dev
 Standards-Version: 3.9.3
 Homepage: https://gna.org/projects/bist/


signature.asc
Description: PGP signature

Bug#807202: gjay: diff for NMU version 0.3.2-1.2

[Mattia Rizzolo]

Control: tags 807202 + pending

Dear maintainer,

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

Regards.

-- 
regards,
Mattia Rizzolo

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

 changelog |   10 ++
 control   |2 +-
 2 files changed, 11 insertions(+), 1 deletion(-)

diff -Nru gjay-0.3.2/debian/changelog gjay-0.3.2/debian/changelog
--- gjay-0.3.2/debian/changelog	2014-09-10 21:44:34.0 +
+++ gjay-0.3.2/debian/changelog	2016-01-26 12:19:32.0 +
@@ -1,3 +1,13 @@
+gjay (0.3.2-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Bas Couwenberg ]
+  * Update build dependencies for GSL 2, change libgsl0-dev to libgsl-dev.
+Closes: #807202
+
+ -- Mattia Rizzolo   Tue, 26 Jan 2016 12:19:09 +
+
 gjay (0.3.2-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru gjay-0.3.2/debian/control gjay-0.3.2/debian/control
--- gjay-0.3.2/debian/control	2014-09-10 21:44:12.0 +
+++ gjay-0.3.2/debian/control	2016-01-26 12:19:02.0 +
@@ -2,7 +2,7 @@
 Section: sound
 Priority: extra
 Maintainer: Craig Small 
-Build-Depends: debhelper (>= 7), autotools-dev, libgtk2.0-dev, libgsl0-dev, audacious-dev, libflac-dev, libvorbis-dev, libmpdclient-dev, libaudclient-dev
+Build-Depends: debhelper (>= 7), autotools-dev, libgtk2.0-dev, libgsl-dev, audacious-dev, libflac-dev, libvorbis-dev, libmpdclient-dev, libaudclient-dev
 Standards-Version: 3.9.1
 Homepage: http://gjay.sourceforge.net/
 


signature.asc
Description: PGP signature

Bug#812742: libirstlm-dev and libduo-dev: error when trying to install together

[Balint Reczey]

Control: tags -1 confirmed

Hi Ralf,

Thank you for the bug report.

On Tue, 26 Jan 2016 10:06:07 +0100 Ralf Treinen  wrote:
> Package: libduo-dev,libirstlm-dev
> Version: libduo-dev/1.9.11-1+b1
> Version: libirstlm-dev/5.80.03-1
> Severity: serious
> User: trei...@debian.org
> Usertags: edos-file-overwrite
> 
> Date: 2016-01-26
> Architecture: amd64
> Distribution: sid
> 
> Hi,
> 
> automatic installation tests of packages that share a file and at the
> same time do not conflict by their package dependency relationships has
> detected the following problem:
> 
...

> dpkg: error processing archive 
> /var/cache/apt/archives/libduo-dev_1.9.11-1+b1_amd64.deb (--unpack):
>  trying to overwrite '/usr/include/util.h', which is also in package 
> libirstlm-dev 5.80.03-1
This is indeed a serious bug, the file's name is too generic.
Maybe it is too generic for being in libduo-dev, too, but this is up to
its maintainer.

Moving all include files under /usr/include/irstlm/ seems to be the
appropriate solution.

Cheers,
Balint

Bug#812681: [help] Bug#812681: mira: FTBFS with flex >= 2.6]

[Gianfranco Costamagna]

Hi, ettercap has some flex code, does it helps?


I don't understand flex either, sorry :(

cheers,

G.





Il Lunedì 25 Gennaio 2016 22:07, Andreas Tille  ha scritto:
Hi,

sorry, I have no idea about fley and need help to fix this problem.

Any hint would be welcome.

Kind regards

 Andreas.

- Forwarded message from Michael Tautschnig  -

During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error. It should be noted
right away that this may be one of first attempts building with flex 2.6.
Notably, the flex NEWS says:

"C++ scanners now use references instead of pointers. See the manual for 
details."

[...]
g++ -DPACKAGE_NAME=\"mira\" -DPACKAGE_TARNAME=\"mira\" 
-DPACKAGE_VERSION=\"4.9.5_2\" -DPACKAGE_STRING=\"mira\ 4.9.5_2\" 
-DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DPACKAGE=\"mira\" 
-DVERSION=\"4.9.5_2\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 
-DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 
-DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DENABLE64=1 
-DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DYYTEXT_POINTER=1 -DSTDC_HEADERS=1 
-DHAVE__BOOL=1 -DHAVE_STDBOOL_H=1 -Drestrict=__restrict -DHAVE_STDLIB_H=1 
-DHAVE_MALLOC=1 -DHAVE_STDLIB_H=1 -DHAVE_REALLOC=1 
-DLSTAT_FOLLOWS_SLASHED_SYMLINK=1 -DHAVE_STRFTIME=1 -DHAVE_MEMSET=1 
-DHAVE_FSEEKO=1 -DHAVE_ISBLANK=1 -DHAVE_BOOST=/\*\*/ -DHAVE_BOOST_THREAD=/\*\*/ 
-DHAVE_BOOST_REGEX=/\*\*/ -DHAVE_BOOST_SYSTEM=/\*\*/ 
-DHAVE_BOOST_FILESYSTEM=/\*\*/ -DHAVE_BOOST_IOSTREAMS=/\*\*/ -DHAVE_LIBRT=1 
-DHAVE_GZOFFSET=1 -DBOUNDTRACKFLAG=1 -DBUGTRACKFLAG=1 -I.  -I../../src  
-Wdate-time  -DPUBLICQUIET -DAJ_Linux64 -g -O0 -fstack-protector-strong 
-Wformat -Werror=format-security  -I/usr/include -O3 -funroll-loops -pthread 
-I/usr/include -I/usr/include -Werror=uninitialized -Werror=return-type 
-Werror=parentheses -Werror=unused-value -std=c++14 -c -o exp_flexer.o 
exp_flexer.cc
exp_flexer.cc: In member function 'virtual int EXPFlexLexer::yylex()':
exp_flexer.cc:766:9: error: no match for 'operator=' (operand types are 
'std::istream {aka std::basic_istream}' and 'std::istream* {aka 
std::basic_istream*}')
yyin = & std::cin;
 ^
In file included from /usr/include/c++/5/iostream:40:0,
 from exp_flexer.cc:96:
/usr/include/c++/5/istream:625:7: note: candidate: std::basic_istream<_CharT, 
_Traits>& std::basic_istream<_CharT, 
_Traits>::operator=(std::basic_istream<_CharT, _Traits>&&) [with _CharT = char; 
_Traits = std::char_traits]
   operator=(basic_istream&& __rhs)
   ^
/usr/include/c++/5/istream:625:7: note:   no known conversion for argument 1 
from 'std::istream* {aka std::basic_istream*}' to 
'std::basic_istream&&'
exp_flexer.cc:769:10: error: no match for 'operator=' (operand types are 
'std::ostream {aka std::basic_ostream}' and 'std::ostream* {aka 
std::basic_ostream*}')
yyout = & std::cout;
  ^
In file included from /usr/include/c++/5/iostream:39:0,
 from exp_flexer.cc:96:
/usr/include/c++/5/ostream:402:7: note: candidate: std::basic_ostream<_CharT, 
_Traits>& std::basic_ostream<_CharT, 
_Traits>::operator=(std::basic_ostream<_CharT, _Traits>&&) [with _CharT = char; 
_Traits = std::char_traits]
   operator=(basic_ostream&& __rhs)
   ^
/usr/include/c++/5/ostream:402:7: note:   no known conversion for argument 1 
from 'std::ostream* {aka std::basic_ostream*}' to 
'std::basic_ostream&&'
exp_flexer.cc:1260:44: error: cannot convert 'std::istream {aka 
std::basic_istream}' to 'std::istream* {aka std::basic_istream*}' 
in assignment
YY_CURRENT_BUFFER_LVALUE->yy_input_file = yyin;
^
In file included from /usr/include/c++/5/iostream:40:0,
 from exp_flexer.cc:96:
/usr/include/c++/5/istream: In constructor 
'EXPFlexLexer::EXPFlexLexer(std::istream*, std::ostream*)':
/usr/include/c++/5/istream:606:7: error: 'std::basic_istream<_CharT, 
_Traits>::basic_istream() [with _CharT = char; _Traits = 
std::char_traits]' is protected
   basic_istream()
   ^
exp_flexer.cc:1370:75: error: within this context
yyFlexLexer::yyFlexLexer( std::istream* arg_yyin, std::ostream* arg_yyout )
   ^
In file included from /usr/include/c++/5/iostream:39:0,
 from exp_flexer.cc:96:
/usr/include/c++/5/ostream:384:7: error: 'std::basic_ostream<_CharT, 
_Traits>::basic_ostream() [with _CharT = char; _Traits = 
std::char_traits]' is protected
   basic_ostream()
   ^
exp_flexer.cc:1370:75: error: within this context
yyFlexLexer::yyFlexLexer( std::istream* arg_yyin, std::ostream* arg_yyout )
   ^
exp_flexer.cc:1372:7: error: no match for 'operator=' (operand types are 
'std::istream {aka std::basic_istream}' and 'std::istream* 

Bug#803477: petsc: FTBFS against mpich

[Matthias Klose]

now rebuilt on s390x.

Bug#812838: docker.io: please package 1.9.0 or later

[Olaf Meeuwissen]

Package: docker.io
Version: 1.8.3~ds1-2
Severity: normal

Dear Maintainer,

The 1.9.0 release introduces support for `docker build` environment
variables that are not persisted.  This should finally solve all my
"build behind a proxy" issues.

See https://github.com/docker/docker/blob/master/CHANGELOG.md#builder-1
and https://github.com/docker/docker/pull/15182 for details.

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

Kernel: Linux 4.3.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages docker.io depends on:
ii  adduser  3.113+nmu3
ii  init-system-helpers  1.24
ii  iptables 1.4.21-2+b1
ii  libapparmor1 2.10-2+b2
ii  libc62.21-6
ii  libdevmapper1.02.1   2:1.02.114-1
ii  libsqlite3-0 3.9.2-1
ii  perl 5.22.1-4

Versions of packages docker.io recommends:
ii  ca-certificates  20160104
ii  cgroupfs-mount   1.2
ii  git  1:2.7.0~rc3-1
ii  xz-utils 5.1.1alpha+20120614-2.1

Versions of packages docker.io suggests:
ii  aufs-tools   1:3.2+20130722-1.1
pn  btrfs-tools  
ii  debootstrap  1.0.75
pn  lxc  
pn  rinse
pn  zfs-fuse | zfsutils  

-- Configuration Files:
/etc/default/docker changed:
DOCKER_OPTS="--bip 172.16.42.1/16 --storage-driver overlay"
export http_proxy="http://localhost:3128/;


-- no debconf information

-- 
Olaf Meeuwissen, LPIC-2   FLOSS Engineer -- EPSON AVASYS CORPORATION
   Free Software Foundation Associate Member since 2004-01-27
Support Free Software  https://my.fsf.org/donate
Support the Free Software Foundation https://my.fsf.org/join

Bug#812818: should dipy be removeed from debian?

[Yaroslav Halchenko]

On Tue, 26 Jan 2016, Mattia Rizzolo wrote:

> As of now there are 2 RC bugs, the package is not in testing, there are
> no reverse (build-)dependencies and the the popcon is resonably low.

> Please, can you consider maintaining the package?  Keeping an unusable
> thing in the archive is not going to help our users in any way.

Thanks for the buzz... we will fix it up in upcoming days

Cheers!

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

Bug#812835: boinc-client: leaks hundreds of x11 connections

[Preston Maness]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Howdy,

I'm almost positive this is a bug introduced by my pull request to add
XSS-based idle detection back into the boinc client:

https://github.com/BOINC/boinc/pull/1453

I am able to replicate the issue (seeing the number of socket
connections grow for the boinc process). Sorry about that. Looks like
I didn't have a corresponding XCloseDisplay() to go with the
XOpenDisplay(). I'm going to re-open the PR with what I hope is a fix
to this after testing it on my end.

Cheers,
Preston

On 01/26/2016 07:54 PM, Dan Merillat wrote:
> Package: boinc-client Version: 7.6.22+dfsg-1exp3 Severity:
> important
> 
> Dear Maintainer,
> 
> boinc-client caused "maximum number of clients reached" errors on
> my system. xrestop showed 248 clients. Ran 'service boinc-client
> stop' and the client count dropped to 28.
> 
> Multiple reboots had the same problem - after a few minutes the
> client list would start filling up with  clients.
> 
> I had installed boinc a long time ago, intending to use it but
> never set it up - no projects or work.  The problems began only
> after a reboot on Monday, but the last change was january 3:
> 
> 2016-01-03 00:04:52 upgrade boinc-client:amd64 7.0.15+dfsg-1 
> 7.6.22+dfsg-1
> 
> The only explanation is that there was no reboot after that
> upgrade, so perhaps the client either did not start or remained
> running the old 7.0.15 version.
> 
> I verified the boinc was the cause by purging boinc-client and 
> re-installing from experimental - after a few minutes it leaked
> again:
> 
> harik@dan:~$ sudo ls -l /proc/`pidof boinc`/fd total 0 lr-x-- 1
> boinc boinc 64 Jan 26 18:50 0 -> /dev/null lrwx-- 1 boinc boinc
> 64 Jan 26 18:50 1 -> socket:[88000] lrwx-- 1 boinc boinc 64 Jan
> 26 18:50 10 -> socket:[127916] lrwx-- 1 boinc boinc 64 Jan 26
> 18:50 100 -> socket:[129791] lrwx-- 1 boinc boinc 64 Jan 26
> 18:50 101 -> socket:[129792] lrwx-- 1 boinc boinc 64 Jan 26
> 18:50 102 -> socket:[129828] lrwx-- 1 boinc boinc 64 Jan 26
> 18:50 103 -> socket:[129836] lrwx-- 1 boinc boinc 64 Jan 26
> 18:50 104 -> socket:[130925] lrwx-- 1 boinc boinc 64 Jan 26
> 20:42 105 -> socket:[131250] lrwx-- 1 boinc boinc 64 Jan 26
> 20:42 106 -> socket:[131251] lrwx-- 1 boinc boinc 64 Jan 26
> 18:50 107 -> socket:[131252] lrwx-- 1 boinc boinc 64 Jan 26
> 18:50 108 -> socket:[131288] lrwx-- 1 boinc boinc 64 Jan 26
> 18:50 109 -> socket:[131291] ... harik@dan:~$ sudo ls -l
> /proc/`pidof boinc`/fd | grep socket | wc -l 212
> 
> Killing boinc dropped my client count from 242 to 33, and I could
> open new windows again.
> 
> -- System Information: Debian Release: stretch/sid APT prefers
> unstable APT policy: (500, 'unstable'), (500, 'testing'), (1,
> 'experimental') Architecture: amd64 (x86_64) Foreign Architectures:
> i386, armel
> 
> Kernel: Linux 4.2.0-dan (SMP w/4 CPU cores; PREEMPT) Locale:
> LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell:
> /bin/sh linked to /bin/dash Init: systemd (via
> /run/systemd/system)
> 
> Versions of packages boinc-client depends on: ii  adduser
> 3.113+nmu3 ii  ca-certificates20160104 ii  debconf
> [debconf-2.0]  1.5.58 ii  init-system-helpers1.27 ii  libboinc7
> 7.6.22+dfsg-1exp3 ii  libc6  2.21-7 ii  libcurl3
> 7.46.0-1+b1 ii  libgcc11:6-20160122-1 ii
> libstdc++6 6-20160122-1 ii  libx11-6
> 2:1.6.3-1 ii  libxss11:1.2.2-1 pn  python:any
>  ii  zlib1g 1:1.2.8.dfsg-2+b1
> 
> boinc-client recommends no packages.
> 
> Versions of packages boinc-client suggests: pn  boinc-client-fglrx
>  pn  boinc-client-nvidia-cuda   pn  boinc-client-opencl
>  ii  boinc-manager 7.6.22+dfsg-1exp3 ii
> x11-xserver-utils 7.7+5
> 
> -- Configuration Files: /etc/boinc-client/gui_rpc_auth.cfg [Errno
> 13] Permission denied: u'/etc/boinc-client/gui_rpc_auth.cfg'
> 
> -- debconf information: boinc-client/remove_boinc_dir: true
> 

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJWqFFTAAoJEFpzcfOOuHp0Mc0P/i/dUUYb8SpYLnCv42vB8eVp
Pn+I63MGaCNfMSMfWMBgxGJRuimpGwGQSN5euALT7AAoYW6kkzkyjv/hmXbxtUa3
hHgop7CpkR3ts89K+geQxxVjnFCwkTUadYDkhBU6ucvGWLvraZ39c6NZvyN0479Z
fu8YSN5VJemww6F5CBFy1lIVNBjhP2YBj7wI+VWp3xu+qkUScJyR8nSdFFbA3ksG
Is1fPR5f/0H85PcUrTebWlE0JnZ1ib/cd3s8R6sN6CJIQ8gsw3PeQqsLQNLso0te
l2MwNGwIDr6tZXh28VHwANS22n9RMAhpZlWF7CEWeClQV7v2ouhLPx1eB7xlu/oV
QddTQ21OHLf0iW1rxIKUYD670W7odebxBJ06aN2szr0btQiq/cQoYqDS5ej6Wvl+
ngLT5OP/u9sGZ2q/uItz4KxxsLohyYGXHGPe7M21y2oaMhfhyTIGs9qIaCLRMvoF
4HukBRgieuv8fMcGJxL0MqvJFk3Ui0o/OcWWQVMLhNm2jTpVVY03L5LY7Fc1793q
2lluWZvjbMp8mVzcdkp9oxYclN96mLuJbhWXJNkTUYa/RghiOyveQM1DtWnXb6jp
g1GcKJ9NoVuS/y/N8aM7eefendFZemcInIGYFZy5c1rNDyX5xOmXKAP28fuTVCq0
PLEt8pTvuY+KQNXkLJlf
=bXU9
-END PGP SIGNATURE-

Bug#812833: pan: Won't start--aborts with error

[Dominique Dumont]

Note: submitter email is unknown: 

: host mx.xmission.com[166.70.12.20] said: 550-XM-RJCT01:
Account  does not exist. [15.73.212.82] 550

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

Bug#802659: dbus-python: Please drop recommends on PyQt4 packages

[Dmitry Shachnev]

Hi Simon,

On Tue, Jan 26, 2016 at 06:49:11PM +0100, Simon McVittie wrote:
> On 26/01/16 10:37, Dmitry Shachnev wrote:
>> My point was that Qt main loop is usually used on Windows / OS X but *not*
>> on Debian. Here, Qt is compiled with GLib support and will use GLib main
>> loop unless explicitly asked not to do so (via QT_NO_GLIB=1 env variable).
>> That is a very rare use case and I don't see why one will ever need it.
>
> Am I right in thinking that Qt programs always the same external-facing
> main-loop API, and that results in callbacks being scheduled from GLib's
> GMainContext on Debian under normal circumstances, or from Qt's built-in
> equivalent of GMainContext/libevent/etc. on Windows, OS X, or with
> QT_NO_GLIB?

Right. Applications always use QCoreApplication/QEventLoop, that creates
an event dispatcher internally, which is different on different platforms.

On other platforms it may also use platform-specific dispatchers, though it
is not relevant for us.

For UNIX the logic is at:
https://code.woboq.org/qt5/qtbase/src/corelib/kernel/qcoreapplication.cpp.html#489

> dbus-python needs two things to work with a particular main-loop: it
> needs to be told how to make that main-loop monitor libdbus connections
> (a dbus.mainloop.* module), and the application author needs to actually
> be iterating that main-loop.
>
> For GLib, dbus.mainloop.glib is bundled with dbus-python, but the
> application author also needs to iterate the GLib main-loop via PyGI,
> either directly or by using a higher-level API like Gtk or GApplication.
> For Qt, dbus.mainloop.whatever replaces dbus.mainloop.glib (but on
> Debian, dbus.mainloop.glib would also work), and QApplication replaces
> PyGI (but on Debian, PyGI would also work).
>
> The "main loop" terminology for the dbus-python addons is perhaps
> unfortunate; it's really more like "event dispatcher integration glue".

I know — I have been playing with that stuff a bit in past :)

>> If you don't remove these packages from Recommends, then at least please
>> replace them with their modern PyQt5 alternatives, i.e.:
>>
>> python-qt4-dbus → python-dbus.mainloop.pyqt5
>> python3-dbus.mainloop.qt → python3-dbus.mainloop.pyqt5
>
> I've done that in git for now, while we decide whether to remove them
> altogether.

Thanks!

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#812833: pan: Won't start--aborts with error

[Dominique Dumont]

On Tuesday 26 January 2016 14:23:17 you wrote:
> ERROR:pan-tree.cc:80:GtkTreeIter PanTreeStore::get_iter(const
> PanTreeStore::Row*): assertion failed: (row) Aborted

There's already an upstream bug ticket for this issue. Unfortunately, pan 
maintenance has stalled, so a fix won't be released any time soon, unless some 
new people takes over this project.

In the meantime, you should be able to recover pan with this work-around:
* ssh into your own machine with -X option
* run pan from there.

Please tell me if this works.

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

Bug#812626: libfreecontact-perl: FTBFS - Parse errors: Bad plan. You planned 10 tests but ran 6.

[Andreas Tille]

tags 812626 unreproducible
thanks

On Wed, 27 Jan 2016 gregor herrmann wrote:
> 
> On Tue, 26 Jan 2016 21:14:35 +0100, Andreas Tille wrote:
> 
> > > I cloned the git repo (very handy :)) and had a look, but I can't
> > > reproduce the test failure, not even when running them manually under
> > > high load.
> > H, I should have mentioned this: I also can not reproduce the
> > problem.
> 
> Ok, maybe the submitter can shed some light on this issue.

Michael, could you please be more verbose about the build conditions
since two people can not reproduce this independently.
   
> > > > > SSE2 veczweight, wchunk = 32
> > I get
> >   SSE2 veczweight, wchunk = 64
> > here instead (when building on amd64).
> 
> Me too.
>  
> > > I noticed that the non-perl-test output comes before t/02test.t while
> > > it comes later (after the "ok 3" of t/02test.t) for me. I thought this
> > > might be a parallelization problem but the test was run with -j1, and
> > > it also passes for me with -jN.
> > From my (limited) experience this kind of non-reproducible FTBFS are
> > often connected to parallelization.  I'm tempted to drop the --parallel
> > from d/rules.
> 
> Doesn't hurt, but since since the logs have
> make -j1 test TEST_VERBOSE=1
> this doesn't seem to have any effect anyway.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#812844: upower segfault on my ARM laptop

[Alexandre Detiste]

Package: upower
Version: 0.99.3-1+b3
Severity: important

upower does segfault every time; well the kernel is maybe a bit weird.
It's the ChromeOS one recompiled by the semi-automated Arch bootstrap
to enable features needed by systemd.


systemd[1]: Starting Daemon for power management...
systemd[1]: Started Daemon for power management.
upowerd[2045]: ** (upowerd:2045): CRITICAL **: 
dbus_g_connection_register_g_object: 
  assertion 'g_variant_is_object_path (at_path)' failed
upowerd[2045]: process 2045: arguments to dbus_message_new_signal() were 
incorrect,
   assertion "_dbus_check_is_valid_path (path)" failed in file 
../../dbus/dbus-message.c line 1433.
upowerd[2045]: This is normally a bug in some application using the D-Bus 
library.
upowerd[2045]: process 2045: arguments to dbus_message_iter_init_append() were 
incorrect, assertion "message !=
   NULL" failed in file ../../dbus/dbus-message.c line 2462. 
upowerd[2045]: This is normally a bug in some application using the D-Bus 
library.
systemd[1]: upower.service: Main process exited, code=killed, status=11/SEGV
systemd[1]: upower.service: Unit entered failed state.
systemd[1]: upower.service: Failed with result 'signal'.



This is the last device opened: (reproducible)

strace -e open -f /lib/upower/upowerd
[pid  2311] 
open("/sys/devices/soc0/sound.8/sound/card1/input5/event5/../capabilities/sw", 
O_RDONLY|O_LARGEFILE) = 14


Greets,

Alexandre


-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing'), (450, 'unstable')
Architecture: armhf (armv7l)
Foreign Architectures: i386

Kernel: Linux 3.10.18-5-ARCH (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF8, LC_CTYPE=fr_BE.UTF8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages upower depends on:
ii  dbus   1.10.6-1
ii  libc6  2.21-6
ii  libdbus-1-31.10.6-1
ii  libdbus-glib-1-2   0.106-1
ii  libglib2.0-0   2.46.2-3
ii  libgudev-1.0-0 230-2
ii  libimobiledevice6  1.2.0+dfsg-2+b1
ii  libplist3  1.12-3.1
ii  libupower-glib30.99.3-1+b3
ii  libusb-1.0-0   2:1.0.20-1
ii  udev   228-4+b1

Versions of packages upower recommends:
ii  policykit-1  0.105-14.1

upower suggests no packages.

-- no debconf information

Bug#768857: torbrowser-launcher (0.1.6-1): processes do not terminate on exit and tor browser cannot be reopened

[Γιώργος Πάλλας]

On 25/01/16 20:27, Holger Levsen wrote:

control: tags -1 + unreproducible

Hi Giorgos,

do you still see this bug with recent versions of torbrowser(-launcher)?

I've not seen in it in a very long time and am tempted to close this bug
report - what do you think?


cheers,
Holger


Hi!

Let me use it for a couple of days and I will get back to you.

Thanks!
Giorgos




smime.p7s
Description: S/MIME Cryptographic Signature

Bug#442363: ITP: php-db-dataobject -- SQL Builder, Object Interface to Database Tables

[Bhuvan Krishna]

control: owner -1 !
control: tag -1 moreinfo




signature.asc
Description: OpenPGP digital signature

Bug#650601: libpng is ready for transition

[Tobias Frost]

Am Dienstag, den 26.01.2016, 22:25 + schrieb Gianfranco Costamagna:
> Hi Tobias
> 
> > +libpng1.6 (1.6.20-1.2)
> > unstable; urgency=medium
> 
> Do you want to go on unstable or it is a typo?
> 
> Gianfranco

Typo

Bug#811451: linux-grsec-base: Some useful confs

[Yves-Alexis Perez]

On mer., 2016-01-27 at 03:36 +, ban...@openmailbox.org wrote:
> On 2016-01-26 10:15, Yves-Alexis Perez wrote:
> > 
> > I don't touch any KVM settings so it /should/ work as is. Without more
> > information I can't do anything. Also please try not to report new 
> > stuff on
> > existing bugs.
> > 
> > Regards,
> 
> Right but for virtualization support I had to choose the hypervisor 
> explicitly in menuconfig otherwise it doesn't work. Grsec defaults to 
> support for baremetal without vtx.

In case it wasn't clear:

- please open a *different* bug
- please provide a tested patch for the configuration

Regards,
-- 
Yves-Alexis



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

Bug#812207: linux: AUFS can hang up; Please update to v20160111 or later

[Akihiro Suda]

I also tested, and it works!

Thank you for patches Ben, thank you for testing Zachary, and thank
you for pointing out Roger san!

Bug#812837: Patch to provide additional functionality for using IF-MIB::ifName

[Stephane Lapie]

Here is a patch for a -N/--use-ifname option that will switch from
IF-MIB::ifDescr to IF-MIB::ifName when looking up the interface's name.

This would enable users of nagios-snmp-plugins to tune whether they want to
match interfaces based on the description, or on the name.
-- 
ラピー ステファン Lapie Stephane
株式会社朝日ネット システム第1部
〒104-0061 東京都中央区銀座4-12-15 歌舞伎座タワー21F
TEL : 03-3541-9590(代表) 03-3541-9591(直通) FAX : 03-3541-5633
E-MAIL: stephane.la...@asahinet.com
--- /tmp/check_snmp_int.pl	2016-01-27 11:24:26.144765849 +0900
+++ /tmp/check_snmp_int.pl.new	2016-01-27 11:47:40.904312037 +0900
@@ -31,6 +31,7 @@
 my $inter_table= '.1.3.6.1.2.1.2.2.1';
 my $index_table = '1.3.6.1.2.1.2.2.1.1';
 my $descr_table = '1.3.6.1.2.1.2.2.1.2';
+my $name_table = '1.3.6.1.2.1.31.1.1.1.1';
 my $oper_table = '1.3.6.1.2.1.2.2.1.8.';
 my $admin_table = '1.3.6.1.2.1.2.2.1.7.';
 my $speed_table = '1.3.6.1.2.1.2.2.1.5.';
@@ -81,6 +82,7 @@
 my $o_meg=		undef; # output in MBytes or Mbits (-M)
 my $o_gig=		undef; # output in GBytes or Gbits (-G)
 my $o_prct=		undef; # output in % of max speed  (-u)
+my $o_use_ifname=	undef;  # use IF-MIB::ifName instead of IF-MIB::ifDescr
 
 my $o_timeout=  undef; 		# Timeout (Default 5)
 # SNMP Message size parameter (Makina Corpus contrib)
@@ -190,6 +192,8 @@
Test it before, because there are known bugs (ex : trailling /)
 -r, --noregexp
Do not use regexp to match NAME in description OID
+-N, --use-ifname
+   Use IF-MIB::ifName as source for NIC name instead of IF-MIB::ifDescr
 -i, --inverse
Make critical when up
 -a, --admin
@@ -257,6 +261,7 @@
 'H:s'   => \$o_host,		'hostname:s'	=> \$o_host,
 'p:i'   => \$o_port,   		'port:i'	=> \$o_port,
 	'n:s'   => \$o_descr,   'name:s'=> \$o_descr,
+	'N'	=> \$o_use_ifname,	'use-ifname'	=> \$o_use_ifname,
 'C:s'   => \$o_community,	'community:s'	=> \$o_community,
 		'2'	=> \$o_version2,	'v2c'		=> \$o_version2,		
 	'l:s'	=> \$o_login,		'login:s'	=> \$o_login,
@@ -446,9 +451,13 @@
 	verb(" new max octets:: $oct_test");
 }
 
-# Get desctiption table
+# Get description table
+my $query_table = $descr_table;
+if (defined($o_use_ifname)) {
+	$query_table = $name_table;
+}
 my $resultat = $session->get_table( 
-	Baseoid => $descr_table 
+	Baseoid => $query_table
 );
 
 if (!defined($resultat)) {

Bug#746011: trackballs: updated for guile-2.0

[Rob Browning]

Hi, I've just uploaded a 1.1.4-4.2 NMU to Debian which includes an
initial conversion to Guile 2.0.

You can find the relevant patches in the debian/patches/ directory, or
here:

  https://git.debian.org/?p=users/rlb/trackballs.git

The patches that show up in debian/patches are also separate commits in
the (unnamed) branch that's merged in to sid.  If it's useful, I'd also
be happy to send you a patch series (suitable for "git am").

Thanks
-- 
Rob Browning
rlb @defaultvalue.org and @debian.org
GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A
GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4

Bug#812782: dpkg: Please add hardened1-linux-amd64 port

[Balint Reczey]

Hi,

On Tue, 26 Jan 2016 15:23:43 +0100 Balint Reczey
 wrote:
...
> I'm working towards making the port ready for being accepted to Debian
> and the attached patch is the one adding the port to dpkg.

I forgot adding one more patch in my previous email.

Cheers,
Balint
>From 4428399dc197cd57a06a56640496443ff8ad90a3 Mon Sep 17 00:00:00 2001
From: Balint Reczey 
Date: Wed, 27 Jan 2016 04:35:01 +0100
Subject: [PATCH] Fix tests after adding hardened1-linux-

---
 scripts/t/Dpkg_Arch.t | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/t/Dpkg_Arch.t b/scripts/t/Dpkg_Arch.t
index b57a0cf..dcfd193 100644
--- a/scripts/t/Dpkg_Arch.t
+++ b/scripts/t/Dpkg_Arch.t
@@ -98,7 +98,7 @@ is(gnutriplet_to_debarch(undef), undef, 'undef gnutriplet');
 is(gnutriplet_to_debarch('unknown-unknown-unknown'), undef, 'unknown gnutriplet');
 is(gnutriplet_to_debarch('x86_64-linux-gnu'), 'amd64', 'known gnutriplet');
 
-is(scalar get_valid_arches(), 417, 'expected amount of known architectures');
+is(scalar get_valid_arches(), 446, 'expected amount of known architectures');
 
 {
 local $ENV{CC} = 'false';
-- 
2.1.4

Bug#812839: gitlab: Fails to install. Should gitlab depend on ruby-influxdb?

[Viktor Malyarchuk]

Package: gitlab
Version: 8.4.0+dfsg~rc2-2
Severity: important

Dear Maintainer,

on a system with nginx present (see #812724) gitlab still fails to install with

Verifying we have all required libraries...
Could not find influxdb-0.2.3 in any of the sources
dpkg: error processing package gitlab (--configure):
 subprocess installed post-installation script returned error exit status 7

Should gitlab depend on ruby-influxdb?

Best regards,
Viktor

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

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

Versions of packages gitlab depends on:
ii  adduser3.113+nmu3
ii  asciidoctor1.5.3-1
ii  bc 1.06.95-9+b1
ii  debconf [debconf-2.0]  1.5.58
ii  gitlab-shell   2.6.10-1
ii  gitlab-workhorse   0.5.0-1
ii  libjs-chartjs  1.0.2-1
ii  libjs-clipboard1.4.2-1
ii  libjs-fuzzaldrin-plus  0.3.1-1
ii  libjs-graphael 0.5+dfsg-1
ii  libjs-jquery-cookie10-2
ii  libjs-jquery-history   10-2
ii  libjs-jquery-nicescroll3.6.6-1
ii  nodejs 5.5.0~dfsg-1
ii  postgresql 9.5+172
ii  postgresql-client-9.5 [postgresql-client]  9.5.0-2
ii  redis-server   2:3.2~rc1-3
ii  ruby   1:2.2.4
ii  ruby-ace-rails-ap  3.0.3-2
ii  ruby-activerecord-deprecated-finders   1.0.4-1
ii  ruby-activerecord-session-store0.1.1-2
ii  ruby-acts-as-taggable-on   3.5.0-2
ii  ruby-addressable   2.3.8-1
ii  ruby-after-commit-queue1.3.0-1
ii  ruby-allocations   1.0.3-1
ii  ruby-asana 0.4.0-1
ii  ruby-babosa1.0.2-1
ii  ruby-bootstrap-sass3.3.5.1-3
ii  ruby-browser   1.0.1-1
ii  ruby-cal-heatmap-rails 3.5.1+dfsg-1
ii  ruby-carrierwave   0.10.0+gh-1
ii  ruby-charlock-holmes   0.7.3+dfsg-2
ii  ruby-coffee-rails  4.1.0-2
ii  ruby-colored   1.2-2
ii  ruby-colorize  0.7.7-1
ii  ruby-creole0.5.0-2
ii  ruby-d3-rails  3.5.6+dfsg-1
ii  ruby-default-value-for 3.0.1-1
ii  ruby-devise3.5.2-3
ii  ruby-devise-async  0.9.0-1
ii  ruby-devise-two-factor 2.0.0-1
ii  ruby-diffy 3.0.6-1
ii  ruby-doorkeeper2.2.1-1
ii  ruby-dropzonejs-rails  0.7.1-1
ii  ruby-email-reply-parser0.5.8-1
ii  ruby-enumerize 1.0.0-1
ii  ruby-fog   1.34.0-2
ii  ruby-fogbugz   0.2.1-2
ii  ruby-font-awesome-rails4.3.0.0-1
ii  ruby-gemnasium-gitlab-service  0.2.6-1
ii  ruby-github-linguist   4.7.2-1
ii  ruby-github-markup 1.3.3+dfsg-1
ii  ruby-gitlab-emoji  0.2.1-1
ii  ruby-gitlab-flowdock-git-hook  1.0.1-1
ii  ruby-gitlab-git7.2.22-1
ii  ruby-gollum-lib4.1.0-3
ii  ruby-gon   6.0.1-1
ii  ruby-grack 2.0.2-1
ii  ruby-grape 0.13.0-1
ii  ruby-grape-entity  0.4.5-1
ii  ruby-haml-rails0.9.0-4
ii  ruby-hipchat   1.5.2-1
ii  ruby-html-pipeline 1.11.0-1
ii  ruby-httparty  0.13.5-1
ii  ruby-jquery-atwho-rails1.3.2-2
ii  ruby-jquery-rails  4.0.5-1
ii  ruby-jquery-scrollto-rails 1.4.3+dfsg-1
ii  ruby-jquery-turbolinks 2.1.0~dfsg-1
ii  ruby-jquery-ui-rails   5.0.5-3
ii  ruby-kaminari  0.16.3-1
ii  ruby-mail-room 0.6.1-1
ii  ruby-method-source 0.8.2-2
ii  ruby-mousetrap-rails   

Bug#812841: gitlab: Fails to install with 'invoke-rc.d: initscript gitlab, action "start" failed'.

[Viktor Malyarchuk]

Package: gitlab
Version: 8.4.0+dfsg~rc2-2
Severity: important

Dear Maintainer,

on a system with nginx (see #812724) and ruby-influxdb (see #812839) present 
gitlab still fails to install with

---
Administrator account created:

login.root
password..5iveL!fe
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
mkdir -p /var/lib/gitlab/repositories/: OK
mkdir -p /usr/share/gitlab/.ssh: OK
chmod 700 /usr/share/gitlab/.ssh: OK
touch /usr/share/gitlab/.ssh/authorized_keys: OK
chmod 600 /usr/share/gitlab/.ssh/authorized_keys: OK
chmod ug+rwX,o-rwx /var/lib/gitlab/repositories/: OK
Precompiling assets...
Job for gitlab.service failed because the control process exited with error 
code. See "systemctl status gitlab.service" and "journalctl -xe" for details.
invoke-rc.d: initscript gitlab, action "start" failed.
dpkg: error processing package gitlab (--configure):
 subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
 gitlab
E: Sub-process /usr/bin/dpkg returned an error code (1)
---

---
sudo systemctl status gitlab.service -l
● gitlab.service - LSB: GitLab git repository management
   Loaded: loaded (/etc/init.d/gitlab; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2016-01-26 22:14:03 CST; 19min 
ago
 Docs: man:systemd-sysv-generator(8)
  Process: 2485 ExecStart=/etc/init.d/gitlab start (code=exited, 
status=1/FAILURE)

Jan 26 22:14:03 radiance systemd[1]: Starting LSB: GitLab git repository 
management...
Jan 26 22:14:03 radiance su[2492]: Successful su for gitlab by root
Jan 26 22:14:03 radiance su[2492]: + ??? root:gitlab
Jan 26 22:14:03 radiance su[2492]: pam_unix(su:session): session opened for 
user gitlab by (uid=0)
Jan 26 22:14:03 radiance gitlab[2485]: Starting gitlab (via systemctl): 
gitlab.serviceFailed to start gitlab.service: Interactive authentication 
required.
Jan 26 22:14:03 radiance gitlab[2485]: failed!
Jan 26 22:14:03 radiance systemd[1]: gitlab.service: Control process exited, 
code=exited status=1
Jan 26 22:14:03 radiance systemd[1]: Failed to start LSB: GitLab git repository 
management.
Jan 26 22:14:03 radiance systemd[1]: gitlab.service: Unit entered failed state.
Jan 26 22:14:03 radiance systemd[1]: gitlab.service: Failed with result 
'exit-code'.
---

---
sudo journalctl -xe
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit UNIT has finished shutting down.
Jan 26 22:40:15 radiance systemd[3216]: Received SIGRTMIN+24 from PID 3234 
(kill).
Jan 26 22:40:15 radiance systemd[3217]: pam_unix(systemd-user:session): session 
closed for user gitlab
Jan 26 22:40:15 radiance systemd[1]: Stopped User Manager for UID 1000.
-- Subject: Unit user@1000.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit user@1000.service has finished shutting down.
Jan 26 22:40:15 radiance systemd[1]: Removed slice User Slice of gitlab.
-- Subject: Unit user-1000.slice has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit user-1000.slice has finished shutting down.
Jan 26 22:40:15 radiance sudo[2975]: pam_unix(sudo:session): session closed for 
user root
Jan 26 22:40:22 radiance sudo[3245]:   viktor : TTY=pts/1 ; PWD=/home/viktor ; 
USER=root ; COMMAND=/bin/journalctl -xe
Jan 26 22:40:22 radiance sudo[3245]: pam_unix(sudo:session): session opened for 
user root by viktor(uid=0)
---

Thank you very much for bringing gitlab to Debian!

Best regards,
Viktor


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

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

Versions of packages gitlab depends on:
ii  adduser3.113+nmu3
ii  asciidoctor1.5.3-1
ii  bc 1.06.95-9+b1
ii  debconf [debconf-2.0]  1.5.58
ii  gitlab-shell   2.6.10-1
ii  gitlab-workhorse   0.5.0-1
ii  libjs-chartjs  1.0.2-1
ii  libjs-clipboard1.4.2-1
ii  libjs-fuzzaldrin-plus  0.3.1-1
ii  libjs-graphael 0.5+dfsg-1
ii  libjs-jquery-cookie10-2
ii  libjs-jquery-history   10-2
ii  libjs-jquery-nicescroll

Bug#812835: boinc-client: leaks hundreds of x11 connections

[Preston Maness]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Howdy all,

I've got a new PR open for upstream:

https://github.com/BOINC/boinc/pull/1478

And I've attached the patch in the meantime. The patch just closes the
connections that are opened to the Xservers. I had erroneously thought
that dropping out of scope of the function in hostinfo_unix.cpp would
close the connection automatically. With this patch, I don't see the
boinc client pilling up X11 connections like it was before.

Cheers,
Preston

On 01/26/2016 11:10 PM, Preston Maness wrote:
> Howdy,
> 
> I'm almost positive this is a bug introduced by my pull request to
> add XSS-based idle detection back into the boinc client:
> 
> https://github.com/BOINC/boinc/pull/1453
> 
> I am able to replicate the issue (seeing the number of socket 
> connections grow for the boinc process). Sorry about that. Looks
> like I didn't have a corresponding XCloseDisplay() to go with the 
> XOpenDisplay(). I'm going to re-open the PR with what I hope is a
> fix to this after testing it on my end.
> 
> Cheers, Preston
> 
> On 01/26/2016 07:54 PM, Dan Merillat wrote:
>> Package: boinc-client Version: 7.6.22+dfsg-1exp3 Severity: 
>> important
> 
>> Dear Maintainer,
> 
>> boinc-client caused "maximum number of clients reached" errors
>> on my system. xrestop showed 248 clients. Ran 'service
>> boinc-client stop' and the client count dropped to 28.
> 
>> Multiple reboots had the same problem - after a few minutes the 
>> client list would start filling up with  clients.
> 
>> I had installed boinc a long time ago, intending to use it but 
>> never set it up - no projects or work.  The problems began only 
>> after a reboot on Monday, but the last change was january 3:
> 
>> 2016-01-03 00:04:52 upgrade boinc-client:amd64 7.0.15+dfsg-1 
>> 7.6.22+dfsg-1
> 
>> The only explanation is that there was no reboot after that 
>> upgrade, so perhaps the client either did not start or remained 
>> running the old 7.0.15 version.
> 
>> I verified the boinc was the cause by purging boinc-client and 
>> re-installing from experimental - after a few minutes it leaked 
>> again:
> 
>> harik@dan:~$ sudo ls -l /proc/`pidof boinc`/fd total 0 lr-x--
>> 1 boinc boinc 64 Jan 26 18:50 0 -> /dev/null lrwx-- 1 boinc
>> boinc 64 Jan 26 18:50 1 -> socket:[88000] lrwx-- 1 boinc
>> boinc 64 Jan 26 18:50 10 -> socket:[127916] lrwx-- 1 boinc
>> boinc 64 Jan 26 18:50 100 -> socket:[129791] lrwx-- 1 boinc
>> boinc 64 Jan 26 18:50 101 -> socket:[129792] lrwx-- 1 boinc
>> boinc 64 Jan 26 18:50 102 -> socket:[129828] lrwx-- 1 boinc
>> boinc 64 Jan 26 18:50 103 -> socket:[129836] lrwx-- 1 boinc
>> boinc 64 Jan 26 18:50 104 -> socket:[130925] lrwx-- 1 boinc
>> boinc 64 Jan 26 20:42 105 -> socket:[131250] lrwx-- 1 boinc
>> boinc 64 Jan 26 20:42 106 -> socket:[131251] lrwx-- 1 boinc
>> boinc 64 Jan 26 18:50 107 -> socket:[131252] lrwx-- 1 boinc
>> boinc 64 Jan 26 18:50 108 -> socket:[131288] lrwx-- 1 boinc
>> boinc 64 Jan 26 18:50 109 -> socket:[131291] ... harik@dan:~$
>> sudo ls -l /proc/`pidof boinc`/fd | grep socket | wc -l 212
> 
>> Killing boinc dropped my client count from 242 to 33, and I
>> could open new windows again.
> 
>> -- System Information: Debian Release: stretch/sid APT prefers 
>> unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 
>> 'experimental') Architecture: amd64 (x86_64) Foreign
>> Architectures: i386, armel
> 
>> Kernel: Linux 4.2.0-dan (SMP w/4 CPU cores; PREEMPT) Locale: 
>> LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: 
>> /bin/sh linked to /bin/dash Init: systemd (via 
>> /run/systemd/system)
> 
>> Versions of packages boinc-client depends on: ii  adduser 
>> 3.113+nmu3 ii  ca-certificates20160104 ii  debconf 
>> [debconf-2.0]  1.5.58 ii  init-system-helpers1.27 ii
>> libboinc7 7.6.22+dfsg-1exp3 ii  libc6  2.21-7 ii
>> libcurl3 7.46.0-1+b1 ii  libgcc11:6-20160122-1
>> ii libstdc++6 6-20160122-1 ii  libx11-6 2:1.6.3-1 ii
>> libxss11:1.2.2-1 pn  python:any  ii  zlib1g
>> 1:1.2.8.dfsg-2+b1
> 
>> boinc-client recommends no packages.
> 
>> Versions of packages boinc-client suggests: pn
>> boinc-client-fglrx  pn  boinc-client-nvidia-cuda   pn
>> boinc-client-opencl  ii  boinc-manager
>> 7.6.22+dfsg-1exp3 ii x11-xserver-utils 7.7+5
> 
>> -- Configuration Files: /etc/boinc-client/gui_rpc_auth.cfg
>> [Errno 13] Permission denied:
>> u'/etc/boinc-client/gui_rpc_auth.cfg'
> 
>> -- debconf information: boinc-client/remove_boinc_dir: true
> 
> 
> 

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJWqFmwAAoJEFpzcfOOuHp0Zm8P/jjPT7xYllLqpFr90DuxvCJZ
FHpfp10C2rbO752iqmAuYhbsWqIVo4y3AxKVKH5bOS+0OxAIeoIPm7BLDFwGeJOT
opkZEPHho7gpcWbE3EXT3FAW9MCWbbOQGn3aJPR3y9VQdsUtiNJHtcG1L8vcnX0Q
eEksLLRaGspV/HKg9UVwpEC7eIK02Bid/1GZHPgmroWucn8ix/mwl1V/xt5lcAq8
gnVlfIhmmQ1UTxI88UTeOOSVFNPQPuJ2WIRWjwZ7+GKv8HjHGuN6oaoT9sOFcn5Y

Bug#812842: EnableLogging=1 doesn't have any effect

[Jon Forsberg]

Package: usb-modeswitch
Version: 2.2.0+repack0-2

According to the comments in /etc/usb_modeswitch.conf, setting
EnableLogging=1 should make i
produce a logfile in /var/log. When I invoke usb_modeswitch it does work
(switches mode of
my 3G dongle) but no logfile is created in /var/log.

This is how I invoke it:

usb_modeswitch --default-vendor=0x12d1 --default-product=0x1446 -J -Q

This is the config file:

# cat /etc/usb_modeswitch.conf

# Configuration for the usb_modeswitch package, a mode switching tool for
# USB devices providing multiple states or modes
#
# Evaluated by the wrapper script /usr/sbin/usb_modeswitch_dispatcher
#
# To enable an option, set it to "1", "yes" or "true" (case doesn't matter)
# Everything else counts as "disable"


# Disable automatic mode switching globally (e.g. to access the original
# install storage)

DisableSwitching=0


# Enable logging (results in a extensive report file in /var/log, named
# "usb_modeswitch_" and probably others

EnableLogging=1


# Optional increase of "delay_use" for the usb-storage driver; there are
hints
# that a recent kernel default change to 1 sec. may lead to problems,
particu-
# larly with USB 3.0 ports. Set this to at least 3 (seconds) in that case.
# Does nothing if the current system value is same or higher

#SetStorageDelay=4

Bug#812821: nmu: pam_1.1.8-3.1+deb8u1

[Adam D. Barratt]

Control: tags -1 + jessie

On Tue, 2016-01-26 at 15:28 -0800, Tianon Gravi wrote:
> Due to some kind of mistake in my amd64 build environment (details being
> tracked down in #812566) the amd64 build of pam_1.1.8-3.1+deb8u1 is the
> only one that got the intended man page update, but this causes
> co-installability issues (as detailed in #812566).  Getting a binNMU of
> amd64 in the meantime would be great so that at least the packages line
> up properly while we figure out what happened. :(
> 
> nmu pam_1.1.8-3.1+deb8u1 . amd64 . jessie . -m "Rebuild with correct build 
> environment"

libpam0g is "Multi-Arch: same" so this will need to be binNMUed on all
architectures (at least both of i386 and amd64) or we'll just end up
with a different set of installability issues.

Regards,

Adam

Bug#812821: nmu: pam_1.1.8-3.1+deb8u1

[Adam D. Barratt]

On Wed, 2016-01-27 at 05:48 +, Adam D. Barratt wrote:
> Control: tags -1 + jessie
> 
> On Tue, 2016-01-26 at 15:28 -0800, Tianon Gravi wrote:
> > Due to some kind of mistake in my amd64 build environment (details being
> > tracked down in #812566) the amd64 build of pam_1.1.8-3.1+deb8u1 is the
> > only one that got the intended man page update, but this causes
> > co-installability issues (as detailed in #812566).  Getting a binNMU of
> > amd64 in the meantime would be great so that at least the packages line
> > up properly while we figure out what happened. :(
> > 
> > nmu pam_1.1.8-3.1+deb8u1 . amd64 . jessie . -m "Rebuild with correct build 
> > environment"
> 
> libpam0g is "Multi-Arch: same" so this will need to be binNMUed on all
> architectures (at least both of i386 and amd64) or we'll just end up
> with a different set of installability issues.

Is it just the manpage that's the issue? i.e. do the packages published
as part of the point release include the actual security fix?

Regards,

Adam

Bug#812840: Configures initramfs SSH login with locked root account

[martin f krafft]

Package: dropbear
Version: 2014.65-1
Severity: normal

After installing dropbear and adding DROPBEAR=y to initramfs.conf,
the system starts with dropbear listening on port 22/tcp alright.
Yay!

Even the SSH authorized_keys file is pre-populated, which is also
a nice touch.

Unfortunately, though, root login does not work. The reason is
discerned from running dropbear with -F -E and then seeing

  [149] Jan 27 04:05:09 User account 'root' is locked

I had a look around, and I think the problem is simply that
/etc/passwd defines /root as root's homedir, whereas initramfs
mounts the target system there at some stage! Changing the homedir
to /root/root enables logging in, but obviously requires /root to be
mounted.

Maybe the best would be to create /roothome during setup for the
purpose of this package?

Note that this applies to the stable package, i.e. before the
dropbox-initramfs split-off.

-- 
 .''`.   martin f. krafft  @martinkrafft
: :'  :  proud Debian developer
`. `'`   http://people.debian.org/~madduck
  `-  Debian - when you have better things to do than fixing systems


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

Bug#812791: xserver-xorg-core: Kills DM controlled session when opening X from another tty

[Julien Cristau]

On Tue, Jan 26, 2016 at 16:51:27 +0100, Agustin Martin wrote:

> Package: xserver-xorg-core
> Version: 2:1.17.3-2
> Severity: normal
> 
> Dear Maintainers,
> 
> I am having a strange problem apparently starting with 2:1.17.2-3.
> 
> I often have a display-manager controlled X session for one user and open
> another X session in a free tty for a different user with startx.
> 
> This has been working for a long time. However, after a recent testing
> upgrade including xserver-xorg-core 2:1.17.2-3 this started to fail
> (failure happened before in a sid box, but there were more upgrades to
> look when trying to locate which change might be responsible).
> 
> When I have a display-mamager controlled X session and, without leaving the
> session, switch to a free tty, login as another user and start an X session
> with startx original X session gets killed and I am sent to DM greeter.
> 
Please provide the log from both X processes.

Thanks,
Julien

Bug#812843: iceweasel: Many notifications are not shown with libnotify enabled

[Matthew Gabeler-Lee]

Package: iceweasel
Version: 44.0-1
Severity: normal

I find that many HTML5 style notifications aren't shown in iceweasel (not
new in this version, just finally got motivated to dig a little due to the
notification enhancements advertised in this version).

Most notification demo sites work, but notably gmail only sometimes works,
and most annoyingly, google calendar _never_ works.

Searching in bugzilla, I find these reports that look similar, but I'm not
sure how to dig in further to find out if one of them matches my case:

https://bugzilla.mozilla.org/show_bug.cgi?id=1236150
https://bugzilla.mozilla.org/show_bug.cgi?id=726594
https://bugzilla.mozilla.org/show_bug.cgi?id=1162788

Installing this extension to disable libnotify usage makes notifications
from my "problem" sites work properly, though naturaully now with XUL
instead of libnotify appearance.

https://addons.mozilla.org/en-US/firefox/addon/disable-system-alerts/

It's also worth noting that there are new notification control options as of
44.0 in the XUL version that don't seem to be accessible from the libnotify
version.

-- Package-specific info:

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

Name: Add-on Compatibility Reporter
Location: ${PROFILE_EXTENSIONS}/compatibil...@addons.mozilla.org.xpi
Status: enabled

Name: All-in-One Gestures
Location: ${PROFILE_EXTENSIONS}/{8b86149f-01fb-4842-9dd8-4d7eb02fd055}
Status: enabled

Name: bug489729(Disable detach and tear off tab)
Location: ${PROFILE_EXTENSIONS}/bug489729@alice0775
Status: enabled

Name: Cookie Monster
Location: ${PROFILE_EXTENSIONS}/{45d8ff86-d909-11db-9705-005056c8}.xpi
Status: enabled

Name: Default theme
Location: 
/usr/lib/iceweasel/browser/extensions/{972ce4c6-7e08-4474-a285-3208198ce6fd}
Package: iceweasel
Status: enabled

Name: Disable System Alerts
Location: 
${PROFILE_EXTENSIONS}/disable-system-ale...@matthew.noorenberghe.com.xpi
Status: enabled

Name: dtv jira tweaks userstyle
Status: enabled

Name: Element Hiding Helper for Adblock Plus
Location: ${PROFILE_EXTENSIONS}/elemhidehel...@adblockplus.org.xpi
Status: enabled

Name: Google Privacy
Location: ${PROFILE_EXTENSIONS}/{ea61041c-1e22-4400-99a0-aea461e69d04}.xpi
Status: enabled

Name: Hide right hand pane in Gmail userstyle
Status: enabled

Name: Hide Tab Bar With One Tab
Location: ${PROFILE_EXTENSIONS}/{e5bbc237-c99b-4ced-a061-0be27703295f}.xpi
Status: enabled

Name: Linkification
Location: ${PROFILE_EXTENSIONS}/{35106bca-6c78-48c7-ac28-56df30b51d2a}.xpi
Status: enabled

Name: Master Password+
Location: ${PROFILE_EXTENSIONS}/masterpasswordtimeoutplus@vano
Status: enabled

Name: meta-q-override
Location: ${PROFILE_EXTENSIONS}/jid1-7osji9sxtay...@jetpack.xpi
Status: enabled

Name: msdn tweaks userstyle
Status: enabled

Name: PasswordMaker
Location: ${PROFILE_EXTENSIONS}/{5872365e-67d1-4afd-9480-fd293bebd20d}.xpi
Status: enabled

Name: Referrer Control
Location: ${PROFILE_EXTENSIONS}/referrercont...@qixinglu.com.xpi
Status: enabled

Name: ReloadEvery
Location: ${PROFILE_EXTENSIONS}/{888d99e7-e8b5-46a3-851e-1ec45da1e644}.xpi
Status: enabled

Name: Saved Password Editor
Location: ${PROFILE_EXTENSIONS}/savedpasswordedi...@daniel.dawson.xpi
Status: enabled

Name: Send Tab to Device
Location: ${PROFILE_EXTENSIONS}/jid1-mdjma7if6lo...@jetpack.xpi
Status: enabled

Name: SPDY indicator
Location: ${PROFILE_EXTENSIONS}/spdyindica...@chengsun.github.com.xpi
Status: enabled

Name: Stylish
Location: ${PROFILE_EXTENSIONS}/{46551EC9-40F0-4e47-8E18-8E5CF550CFB8}.xpi
Status: enabled

Name: Stylish Sync
Location: ${PROFILE_EXTENSIONS}/{0e3fc079-afbb-4a00-87e5-9486062d0f9c}.xpi
Status: enabled

Name: SuperStop
Location: ${PROFILE_EXTENSIONS}/supers...@gavinsharp.com.xpi
Status: enabled

Name: User Agent Switcher
Location: ${PROFILE_EXTENSIONS}/{e968fc70-8f95-4ab9-9e79-304de2a71ee1}.xpi
Status: enabled

Name: Video DownloadHelper
Location: ${PROFILE_EXTENSIONS}/{b9db16a4-6edc-47ec-a1f4-b86292ed211d}.xpi
Status: enabled

Name: xda-developers forum - suppress minimum page width userstyle
Status: enabled

-- Plugins information
Name: Gnome Shell Integration
Location: /usr/lib/mozilla/plugins/libgnome-shell-browser-plugin.so
Package: gnome-shell
Status: enabled

Name: Google Talk Plugin
Location: /opt/google/talkplugin/libnpgoogletalk.so
Package: google-talkplugin
Status: enabled

Name: Google Talk Plugin Video Renderer
Location: /opt/google/talkplugin/libnpo1d.so
Package: google-talkplugin
Status: enabled


-- Addons package information
ii  gnome-shell3.18.1-1 amd64graphical shell for the GNOME des
ii  google-talkplu 5.41.0.0-1   amd64Google Talk Plugin
ii  iceweasel  44.0-1   amd64Web browser based on Firefox

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

Bug#812796: tokyocabinet ftbfs on ppc64el, failing to run the tests

[Tobias Frost]

Control: Retitle -1 tokyocabinet: testsuite sometimes failes
Control: Severity -1 normal
Control: Tags -1 unreproducible help


Hi Matthias,

this is some spurious error I've seen before. A give-back will fixed
that everytime until now... Unfortunatly I'm not able to reproduce it
here, even after looping the testsuite endlessly for an day or so.. 
so nothing I can do at the moment
(I'll do an upload for the parallel, so no gb will be needed)

So let me reduce the severity and tag it help.. Maybe someone is more
lucky than me in repproducing


--
tobi

Am Dienstag, den 26.01.2016, 17:45 +0100 schrieb Matthias Klose:
> Package: src:tokyocabinet
> Version: 1.4.48-4
> Severity: serious
> Tags: sid stretch
> 
> seen in 20160126 unstable:
> 
> AA@A01A2A9CA515D7E849493@98@24787308E46B9E6@44B098 (3850)
> AB3@475D023A21312976ECAA2728AD10C64778CAB06279C468 (3900)
> AC9AAD2EEE@CEC9124524674647@619B17A@EB85A53@01D832 (3950)
> 4DACD34D4B742@C0@02C0DA@9848492@C42@37E520E5480B40 (4000)
> 4E02000@@44331A6C3A845B@1AE8@0CB7DD@D974C048272CB4Makefile:236:
> recipe for 
> target 'check-hdb' failed
> make[2]: *** [check-hdb] Segmentation fault
> make[2]: Leaving directory '/home/doko/tmp/tokyocabinet-1.4.48'
> Makefile:166: recipe for target 'check' failed
> make[1]: *** [check] Error 2
> make[1]: Leaving directory '/home/doko/tmp/tokyocabinet-1.4.48'
> dh_auto_test: make -j1 check returned exit code 2
> debian/rules:9: recipe for target 'build-arch' failed
> make: *** [build-arch] Error 2

Bug#812470: kernel-package: cannot produce debs anymore

[Manoj Srivastava]

Hi,

Yes, I think I broke things pretty badly. I think kernel-package
 has bitrotted a bit in the last few years, and needs some care. I am
 going to see if I can steal from the upstream  method of making debian
 packages, and move the resulting rules files to use debhelper, and get
 this back to a useable state.

manoj
-- 
We cannot do everything at once, but we can do something at once. Calvin
Coolidge
Manoj Srivastava    
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20  05B6 CF48 9438 C577 9A1C


smime.p7s
Description: S/MIME cryptographic signature

Bug#812706: mate-system-tools: FTBFS using clang instead of gcc

[Mike Gabriel]

Hi Arthur,

On  Di 26 Jan 2016 00:36:53 CET, Arthur Marble wrote:


Package: mate-system-tools
Severity: minor
Tags: patch
User: pkg-llvm-t...@lists.alioth.debian.org
Usertags: clang-ftbfs

Hello,

Using the rebuild infrastructure, your package fails to build with clang
(instead of gcc).

Detected this kind of error:
http://clang.debian.net/status.php?version=3.6.0=NO_RETURN

Full build log is available here:
http://clang.debian.net/logs/2015-03-25/mate-system-tools_1.8.1+dfsg1-2_unstable_clang.log

I have attached a patch to fix this error.


Regards,
--Arthur Marble


actually we have to remove mate-system-tools from testing/unstable as  
it is deprecated.


I will close this bug, once the package has been effectively removed  
from the archive.


Mike
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/mailxchange/kronolith/fb.php?u=m.gabriel%40das-netzwerkteam.de


pgpR5BnNqHtpG.pgp
Description: Digitale PGP-Signatur

Bug#812621: Bug#812695: pygame-sdl2: FTBFS: format not a string literal and no format arguments

[Gianfranco Costamagna]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Hi, we uploaded libsdl2 a few days ago, and now we are uploading
image, mixer, ttf and all the related packages.

This API breakage shouldn't have been possible (according to upstream,
no packages should use internal sdl2 functions, and in case they do,
they asked us to report them upstream, so they can have a look and
provide patches)

so, if you say the code is autogenerated, please just wait for our
"internal" transition to finish, and then I guess a simple binNMU
would be already enough to fix the issue.

libsdl2-net and libsdl2-gfx are already in unstable, libsdl2-image
will go in unstable today, while libsdl2-ttf and libsdl2-mixer are on
Manuel todo list.

Please revert your "hack" on pygame-sdl2, and let us know if it still
is a problem after we finished the internal sdl2 transition.

thanks a lot for the ping and the good report to you both!

cheers,

Gianfranco


On Mon, 25 Jan 2016 23:38:28 -0500 u...@debian.org (Aaron M. Ucko) wrote
:
> Markus Koschany  writes:
> 
>> Thanks for the report. I believe this is some sort of regression
>> in SDL2 2.0.4. Four days ago pygame-sdl2 built fine with SDL2
>> 2.0.2. pygame_sdl2.error.c is auto-generated at build-time and
>> the error message,(__pyx_t_3) is controlled by SDL_GetError(), so
>> there is not much I can do here. I will disable this specific
>> -format hardening check for now and re-enable it as soon as this
>> issue is resolved in src:libsdl2 and related packages.
> 
> Ah, yes, I see that SDL_SetError hadn't previously been annotated
> as printf-like.  It would be best if whatever generated
> pygame_sdl2.error.c (cython?) respected this annotation itself.
> 
> At any rate, thanks for the quick response and workaround!
> 
> -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) 
> http://www.mit.edu/~amu/ |
> http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
> 
> 
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCAAGBQJWpy9tAAoJEPNPCXROn13Z+wMQAI6LzrNYVgCPomnZbSpiTQV5
SieWBAqJqRbDkvBf5t4z+4/M7REyRqH/xcx66cIdaBIYiXPluO4u+DG2/XjKKpM4
q2fkJlbF7b4tLBDRzZ2yuXydsWoQLqg7u4JnCxfQstwN8Z7+R3wnhe3MVBB1iaZj
vvAj4O7mFjrUJwCwXeoucSnEhcycyvkEbAmGsLiIhjbdK0nplBwLryc4bBx2rO7i
vt7OMfBKAgTBY+GNDkaeLVXEgTWJpvkevciW88ptuAggmNxiM8QtOTpQ73m7ngBt
JMSF9HvS7AZz9bPhcA7tcIaTIjeLjhwBSQ4GkotDZ2X/aWq9u9+MEnGygubNIrMB
Ymwr6MBCC9uBNt/4uS15NQbz0iGSvrsn8k3oKS4egWW7uHoBqPHEJnbeReULhyki
R7vTrYy1OvGtcrfi/98c+SnxT5AgY2+wnKJd0veLVdERo8etaFQx1rYI7Ie+8Xa5
UqNCSMWaoY8Fawee/lluT3f4kYT8e8/keitJe38h+MK/qOFiJc8kHCFFVAlCcGEP
8KjQQ/V79oDf4iC+s+9n54/RtMYWxpjnNmcx+FzM2YNPHiEAget4ibrpQQHrWPLO
SFud94EzCrSzmvvHpYf1H4wOKeqCaHxNr3FAo/fLltDmvU94FWA5/B3Cu7RYzeo2
VLqh9CsTw2C4L7/wt6q8
=gX22
-END PGP SIGNATURE-

Bug#812269: Closing bug

[Anton Gladky]

reassign 812269 oce 0.15-7
fixed 812269 0.15-8
thanks