Bug#925444: smokeping: --pid-dir doesn't worj as expected

[BERTRAND Joël]

Package: smokeping
Version: 2.7.3-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I have restarted a server last sunday and I have seen that smokeping doesn't
start anymore.

In systemd config file, smokeping is launched with --pid-dir=/run/smokeping and
systemd complains about non existent pid file.

I have tried to launch smokeping in command line :
[~] > /usr/sbin/smokeping --pid-dpid-dir=/run/smokepingir=/run/smokeping

and pid file is created in... /run and not in /run/smokeping, that confuses
systemd.

Best regards,

JB

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

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

Versions of packages smokeping depends on:
ii  adduser  3.118
ii  debianutils  4.8.6.1
ii  fping4.2-1
ii  libcgi-fast-perl 1:2.13-1
ii  libconfig-grammar-perl   1.12-2
ii  libdigest-hmac-perl  1.03+dfsg-2
ii  libjs-cropper1.2.2-1
ii  libjs-prototype  1.7.1-3
ii  libjs-scriptaculous  1.9.0-2
ii  librrds-perl 1.7.1-1
ii  libsnmp-session-perl 1.14~git20130523.186a005-4
ii  liburi-perl  1.76-1
ii  libwww-perl  6.36-1
ii  lsb-base 10.2019031300
ii  perl 5.28.1-4
ii  sendmail-bin [mail-transport-agent]  8.15.2-12
ii  ucf  3.0038+nmu1

Versions of packages smokeping recommends:
ii  apache2 [httpd-cgi]  2.4.38-2
ii  dnsutils 1:9.11.5.P4+dfsg-1
ii  echoping 6.0.2-10
ii  libsocket6-perl  0.29-1+b1

Versions of packages smokeping suggests:
pn  curl   
pn  libauthen-radius-perl  
ii  libio-socket-ssl-perl  2.060-3
ii  libnet-dns-perl1.19-1
pn  libnet-ldap-perl   
ii  libnet-telnet-perl 3.04-1
ii  openssh-client 1:7.9p1-9

-- Configuration Files:
/etc/smokeping/basepage.html changed [not included]
/etc/smokeping/config.d/Alerts changed [not included]
/etc/smokeping/config.d/General changed [not included]
/etc/smokeping/config.d/Presentation changed [not included]
/etc/smokeping/config.d/Probes changed [not included]
/etc/smokeping/config.d/Slaves changed [not included]
/etc/smokeping/config.d/Targets changed [not included]
/etc/smokeping/config.d/pathnames changed [not included]
/etc/smokeping/smokemail changed [not included]
/etc/smokeping/smokeping_secrets [Errno 13] Permission non accordée: 
'/etc/smokeping/smokeping_secrets'

-- no debconf information

Bug#924938: unblock: healpix-java/3.40-1

[Ole Streicher]

Dear Jonathan,

as there is already the new version with the version number in unstable,
would you agree to manage an upload via testing-proposed-updates? The
upload would be really small, containing mainly a change of the build
dependency and an additional entry for the JAVA classpath in d/rules.

Ole Streicher

(Debian Astro Team)

On Sat, 23 Mar 2019 16:32:12 + Jonathan Wiltshire 
wrote:
> Control: tag -1 moreinfo
>
> On Mon, Mar 18, 2019 at 01:01:18PM -0400, Leo Singer wrote:
> > Please unblock package healpix-java.
> >
> > The package fixes the important bug #923752, "healpix-java: FTBFS in
> > buster/sid". Note that aladin and topcat depend on healpix-java.
>
> Unfortunately it also includes an unreviewable new upstream release. Please
> revert that and include just the bug fix.
>
> Thanks,
>
> --
> Jonathan Wiltshire  j...@debian.org
> Debian Developer http://people.debian.org/~jmw
>
> 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51
>
>
>

Bug#924856: wxpython4.0: FTBFS: sip: /<>/wxpython4.0-4.0.4+dfsg/src/wacky_ints.sip:20: Invalid type for %MappedType

[Dmitry Shachnev]

Hi Drew!

On Mon, Mar 25, 2019 at 01:19:55PM +0800, Drew Parsons wrote:
> Indeed, the changelog for sip4 4.19.14+dfsg-1 itself says: 
> Bump API version to 12.6.
>
> Dimitry, if you know you are uploading an incompatible release, then
> for goodness' sake use the Transitions procedure, 
> https://wiki.debian.org/Teams/ReleaseTeam/Transitions

Sorry for the breakage this has caused.

However minor API version bumps are supposed to introduce new API but not
break existing one. They are needed to make sure packages built against sip
get proper dependencies. When the major version changes, we indeed use
transitions.

See .

I will look at this bug a bit later.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#860716: shim fails to load MokManager (mmx64.efi) in the case of self-signed grub

[Mikhail Kshevetskiy]

On Sat, 23 Mar 2019 18:05:23 +
Steve McIntyre  wrote:

> I'm hoping that our current set of packages will fix this bug, as
> we've moved to a much newer upstream version of shim which includes
> the commit you point at. Once we have our new shim signed with the
> Microsoft CA, could you retry your test and confirm please?

yes, I'll retest it.

Bug#923759: One step ahead but compile errors (Was: netlib-java contains nealy empty jar)

[Andreas Tille]

Hi again,

Dominik Stadler commented here:

  
https://salsa.debian.org/java-team/netlib-java/commit/da4055377617ea59e92675088be41600e16a326d#note_70898

on my patch.  I admit I feel really bad about my patch since I do not
want to override an existing compile target.  So I rephrase:  Why is the
compile target that seems to be "hidden" in nbproject/build-impl.xml not
executed any more and how can I get back the status of 0.9.3-3 which was
building nicely?

I seriously need help on this matter.

Kind regards

   Andreas.


On Thu, Mar 21, 2019 at 01:55:46PM +0100, Andreas Tille wrote:
> Hi,
> 
> On Tue, Mar 12, 2019 at 10:58:33AM +0100, Andreas Tille wrote:
> > I realised that
> > 
> > /usr/share/java/netlib-java-0.9.3.jar
> > 
> > is nearly empty, specifically
> > 
> > /org/netlib/arpack
> > /org/netlib/blas
> > /org/netlib/lapack
> > 
> > do not contain any classes.
> > ...
> > and the previous version on snapshots[1] contains a proper jar file with
> > all classes I suspect some issue with a change in the Java VM.
> > Unfortunately I have no idea how to fix this and hope Debian Java team
> > can help here.
> 
> I went a bit further into the build system of netlib-java and found out
> that build.xml is lacking a compile target.  I added this in my last
> commit[2] and need to admit that I have no idea why the package has ever
> build before.
> 
> Unfortunately the build now leaves me with some errors:
> 
> ...
> compile:
> [javac] Compiling 3 source files
> [javac] 
> /build/netlib-java-0.9.3/src/org/netlib/generate/JavaGenerator.java:48: 
> error: package org.netlib.util does not exist
> [javac] import org.netlib.util.StringW;
> [javac]   ^
> [javac] 
> /build/netlib-java-0.9.3/src/org/netlib/generate/JavaGenerator.java:49: 
> error: package org.netlib.util does not exist
> [javac] import org.netlib.util.booleanW;
> [javac]   ^
> [javac] 
> /build/netlib-java-0.9.3/src/org/netlib/generate/JavaGenerator.java:50: 
> error: package org.netlib.util does not exist
> [javac] import org.netlib.util.doubleW;
> [javac]   ^
> [javac] 
> /build/netlib-java-0.9.3/src/org/netlib/generate/JavaGenerator.java:51: 
> error: package org.netlib.util does not exist
> [javac] import org.netlib.util.floatW;
> [javac]   ^
> [javac] 
> /build/netlib-java-0.9.3/src/org/netlib/generate/JavaGenerator.java:52: 
> error: package org.netlib.util does not exist
> [javac] import org.netlib.util.intW;
> [javac]   ^
> [javac] 
> /build/netlib-java-0.9.3/src/org/netlib/generate/JavaGenerator.java:104: 
> error: cannot find symbol
> [javac] classDefs.put(intW.class, "intW");
> [javac]   ^
> [javac]   symbol:   class intW
> [javac]   location: class JavaGenerator
> [javac] 
> /build/netlib-java-0.9.3/src/org/netlib/generate/JavaGenerator.java:105: 
> error: cannot find symbol
> [javac] classDefs.put(doubleW.class, "doubleW");
> [javac]   ^
> [javac]   symbol:   class doubleW
> [javac]   location: class JavaGenerator
> [javac] 
> /build/netlib-java-0.9.3/src/org/netlib/generate/JavaGenerator.java:106: 
> error: cannot find symbol
> [javac] classDefs.put(booleanW.class, "booleanW");
> [javac]   ^
> [javac]   symbol:   class booleanW
> [javac]   location: class JavaGenerator
> [javac] 
> /build/netlib-java-0.9.3/src/org/netlib/generate/JavaGenerator.java:107: 
> error: cannot find symbol
> [javac] classDefs.put(floatW.class, "floatW");
> [javac]   ^
> [javac]   symbol:   class floatW
> [javac]   location: class JavaGenerator
> [javac] 
> /build/netlib-java-0.9.3/src/org/netlib/generate/JavaGenerator.java:108: 
> error: cannot find symbol
> [javac] classDefs.put(StringW.class, "StringW");
> [javac]   ^
> [javac]   symbol:   class StringW
> [javac]   location: class JavaGenerator
> [javac] 10 errors
> 
> BUILD FAILED
> /build/netlib-java-0.9.3/build.xml:30: Compile failed; see the compiler error 
> output for details.
> 
> Total time: 1 second
> make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1
> 
> 
> Any hint how to get rid of these?
> 
> Kind regards
> 
>Andreas.
> 
> 
> 
> > [1] 
> > https://snapshot.debian.org/archive/debian/20160625T105051Z/pool/main/n/netlib-java/libnetlib-java_0.9.3-3_all.deb
> [2] 
> https://salsa.debian.org/java-team/netlib-java/blob/master/debian/patches/add_compile_target.patch
> 
> -- 
> http://fam-tille.de
> 
> 

-- 
http://fam-tille.de

Bug#925436: unblock: fwupdate/12-4

[Ansgar Burchardt]

Steve McIntyre writes:
> Please unblock package fwupdate

Please also unblock

  fwupdate-amd64-signed/12+4
  fwupdate-arm64-signed/12+4
  fwupdate-armhf-signed/12+4
  fwupdate-i386-signed/12+4

at the same time.

Ansgar

Bug#925435: unblock: fwupd/1.2.5-2

[Ansgar Burchardt]

Steve McIntyre writes:
> Please unblock package fwupd

Please also unblock

  fwupd-amd64-signed/1.2.5+2
  fwupd-arm64-signed/1.2.5+2
  fwupd-armhf-signed/1.2.5+2
  fwupd-i386-signed/1.2.5+2

at the same time.

Ansgar

Bug#925423: elpa-debian-el: unable to report a bug in package reportbug

[Salman Mohammadi]

Dear David,


The content of the variable *message-send-mail-function* as you have
correctly guessed is *message-send-mail-with-mailclient*.

I don't know how to test this feature (e.g. sending using smtp) without
spamming BTS.


I should also add that I have this bug only with *reportbug* package and
not other packages, that I have previously tried.


On Sun, 24 Mar 2019 22:19:58 -0300 David Bremner  wrote:

> Salman Mohammadi  writes:
>
> > Package: elpa-debian-el
> > Version: 37.8
> > Severity: important
> >
> > Dear Maintainer,
> >
> > I'm unable to report a bug which is affecting the package *reportbug*.
> >
> > Steps to reproduce:
> >
> > 1. M-x debian-bug
> > 2. Report a bug for a [P]ackage or [F]ile: P
> > 3. package name: reportbug
> > 4. Severity: normal
> > 5. (Very) brief summary of problem: dummy bug
> >
> >
> > but When I click on *Send Message*, a new window in Mozilla Thunderbird
> > will be shown with the following content:
> >
> >
> > --=-=-=
> > Content-Type: text/plain
> >
> > Package: reportbug
> > Version: 7.5.2
> > Severity: normal
>
> This seems to be an upstream bug in emacs. What is your setting of the
> variable message-send-mail-function (you can check with C-h v)?
>
> If, as I suspect, it is message-send-mail-with-mailclient, then I think
> I understand the problem you are seeing. Basically that function only
> supports text/plain messages, while debian-bug sends it MIME.
>
> If possible, I'd suggest using a different value of
> message-send-mail-function (I think it's initialized from
> send-mail-function).
>
> d
>
>

Bug#905177: bind9: prompting due to modified conffiles which were not modified by the user: /etc/bind/named.conf.options

[Andreas Beckmann]

Followup-For: Bug #905177

Hi,

the situation is a bit tricky for upgrades that had bind9 from squeeze
or older installed: there /etc/bind/named.conf.options was a conffile.
Which is something dpkg remembers (with an outdated md5sum). The content
of the file have been updated over time s.t. we don't need to handle
md5sums in the preinst depending on whether the first installation
happened in lenny or wheezy :-)

We cannot move the file aside in case dpkg knows it as a conffile:

  Setting up bind9 (1:9.11.5.P4+dfsg-1) ...
  Installing new version of config file /etc/apparmor.d/usr.sbin.named ...
  Installing new version of config file /etc/bind/bind.keys ...
  Installing new version of config file /etc/bind/named.conf.default-zones ...
  
  Configuration file '/etc/bind/named.conf.options'
   ==> Deleted (by you or by a script) since installation.
   ==> Package distributor has shipped an updated version.
 What would you like to do about it ?  Your options are:
  Y or I  : install the package maintainer's version
  N or O  : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
   The default action is to keep your current version.
  *** named.conf.options (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing 
package bind9 (--configure):
   end of file on stdin at conffile prompt
  Processing triggers for systemd (241-1) ...
  Processing triggers for libc-bin (2.28-8) ...
  Errors were encountered while processing:
   bind9

That's from squeeze -> wheezy -> jessie -> stretch -> buster. Notice the
  "Deleted (by you or by a script) since installation."

My proposed solution you can find in the attached patch. It passes my
tests starting from lenny as well as starting from wheezy.
I create a backup as .dpkg-old and then edit the file in-place to match
the content of the yet-to-be-installed-conffile. In that case dpkg does
not see a content conflicht, does not prompt about it and updates the
md5sum of the conffile to the new version in its database.

Andreas
>From a714533a17508d0f5f2084c15a42801458f7eeeb Mon Sep 17 00:00:00 2001
From: Andreas Beckmann 
Date: Sun, 24 Mar 2019 22:51:53 +0100
Subject: [PATCH] bind9.preinst: cope with ancient conffile named.conf.options

In squeeze and earlier /etc/bind/named.conf.options was a conffile.
On upgrades from such a version dpkg will remember it as an obsolete
conffile with an outdated md5sum. Therefore we must not move it aside in
this case (which dpkg would take as a deletion by the local admin),
instead we edit it in place to match the to-be-installed version in
order to avoid prompting and make dpkg update the md5sum.

Closes: #905177
---
 debian/bind9.preinst | 10 +-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/debian/bind9.preinst b/debian/bind9.preinst
index 464ffc627..66b06abaa 100644
--- a/debian/bind9.preinst
+++ b/debian/bind9.preinst
@@ -20,7 +20,15 @@ case "$1" in
theirs=$(md5sum /etc/bind/named.conf.options | sed 's/ .*$//')
mine=56919cbc0d819c9a303a8bdeb306b5f1
if [ "$mine" = "$theirs" ]; then
-   mv /etc/bind/named.conf.options 
/etc/bind/named.conf.options.dpkg-old
+   if [ -n "$(dpkg-query -f '${Conffiles}' -W bind9 | grep 
/etc/bind/named.conf.options)" ]; then
+   # dpkg knows /etc/bind/named.conf.options as a conffile 
(from squeeze or older)
+   # cannot move the outdated file aside to avoid dpkg 
noticing deleted-by-local-admin
+   # therefore edit it in place to make it match the 
to-be-installed version
+   cp -p /etc/bind/named.conf.options 
/etc/bind/named.conf.options.dpkg-old
+   sed -i '26{/^$/d}; 23{/auth-nxdomain no;/d}' 
/etc/bind/named.conf.options
+   else
+   mv /etc/bind/named.conf.options 
/etc/bind/named.conf.options.dpkg-old
+   fi
fi
fi
 ;;
-- 
2.11.0



bind9_1:9.11.5.P4+dfsg-1.log.gz
Description: application/gzip

Bug#925445: jessie-backports packages for amd64 have disappeared from mirrors

[Nik Wrt]

Package: aptitude
Version: 0.6.11-1+b1

Since 20 March jessie repositories (except LTS) have been removed from the 
official debian mirrors and are now archived at archive.debian.org, see 
following mailing list post

https://lists.debian.org/debian-devel-announce/2019/03/msg6.html

The post says that amd64 architecture is included in LTS, however all packages 
from jessie-backports have disappeared after aptitude update. Is this 
intentional? I have temporarily switched jessie-backports to archive.debian.org 
but it needs to disable the expiration check using -o 
Acquire::Check-Valid-Until=0

In addition I also use devuan jessie on another machine and this problem breaks 
jessie-backports for devuan, which has no archive.

Bug#924856: wxpython4.0: FTBFS: sip: /<>/wxpython4.0-4.0.4+dfsg/src/wacky_ints.sip:20: Invalid type for %MappedType

[Dmitry Shachnev]

On Mon, Mar 25, 2019 at 10:27:29AM +0300, Dmitry Shachnev wrote:
> I will look at this bug a bit later.

It looks like Scott already has a fix for that, so my help is probably not
needed:

https://github.com/wxWidgets/Phoenix/pull/1189

Next time I will try to build wxpython4.0 before uploading new sip4 releases.

--
Dmitry Shachnev


signature.asc
Description: PGP signature

Bug#925356: unblock: sane-backends/1.0.27-3.2 (pre-approval)

[John Paul Adrian Glaubitz]

Hi Jonathan!

On 3/23/19 8:47 PM, John Paul Adrian Glaubitz wrote:
> On 3/23/19 6:13 PM, Jonathan Wiltshire wrote:
>> You forgot the debdiff, but the upstream patch looks OK. Please go ahead
>> and remove the moreinfo tag when this is ready to unblock.
> 
> Uploaded and built successfully on all release architectures, should
> be good for unblock now. Removing "moreinfo".

Package is in unstable now, could you unblock it for testing now?

Thanks,
Adrian

-- 
 .''`.  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#925446: arpalert: Please fix homepage

[Ricardo Mones]

Package: arpalert
Severity: minor

Dear Maintainer,

Seems homepage of arpalert seems to have moved to:

http://www.arpalert.org/arpalert.html

while the root site remains now as author's homepage.

This also affects watch file, because src dir is forbidden and versions
have to be parsed from download section in homepage :-(

thanks in advance,

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

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

Versions of packages arpalert depends on:
ii  adduser 3.115
ii  ieee-data   20160613.1
ii  libc6   2.24-11+deb9u4
ii  libpcap0.8  1.8.1-3

arpalert recommends no packages.

arpalert suggests no packages.

Bug#925447: openjk-academy-server: broken symlink: /usr/share/doc/openjk-{academy{,-server},outcast}/rv-readme.txt -> ../openjk-common/rv-readme.txt

[Andreas Beckmann]

Package: openjk-academy-server,openjk-academy,openjk-outcast
Version: 0~20190221.8367be0~dfsg-1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package ships (or creates)
a broken symlink.

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

0m42.1s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/openjk-academy-server/rv-readme.txt -> 
../openjk-common/rv-readme.txt (openjk-academy-server)

0m46.8s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/openjk-academy/rv-readme.txt -> ../openjk-common/rv-readme.txt 
(openjk-academy)

0m45.4s ERROR: FAIL: Broken symlinks:
  /usr/share/doc/openjk-outcast/rv-readme.txt -> ../openjk-common/rv-readme.txt 
(openjk-outcast)


cheers,

Andreas


openjk-academy-server_0~20190221.8367be0~dfsg-1.log.gz
Description: application/gzip

Bug#925448: libcache-fastmmap-perl: test integration with Compress::LZ4 and Compress::Snappy

[Andrius Merkys]

Source: libcache-fastmmap-perl
Severity: wishlist

Hello,

Cache::FastMmap is capable to integrate both with Compress::LZ4 and
Compress::Snappy, however, the integration tests are run neither during
chroot build, nor the autopkgtest. A test for integration already exists
(t/13.t), but it is skipped in clean chroot due to missing dependencies
on both libcompress-*-perl modules.

I suggest making the package build-depend on both libcompress-*-perl
packages to run the tests during build. However, I don't know how to
specify autopkgtest dependencies when test suite is specified as
'Testsuite: autopkgtest-pkg-perl'.

Best,
Andrius

-- 
Andrius Merkys
Vilnius University Institute of Biotechnology, Saulėtekio al. 7, room V325
LT-10257 Vilnius, Lithuania

Bug#925449: unblock: kdenlive/18.12.3-1

[Patrick Matthäi]

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

Please unblock package kdenlive

Hello,

before my VAC I were a bit late with the upload. Please unblock kdenlive 
18.12.3-1,
it only contains updated translations:

$ diff -Naur kdenlive-18.12.2/ kdenlive-18.12.3/|diffstat
 CMakeLists.txt|2
 data/kdenlive_wipes.knsrc |2
 debian/changelog  |6
 po/ca/kdenlive.po |8 -
 po/ca@valencia/kdenlive.po|8 -
 po/da/kdenlive.po |  119 ---
 po/es/docs/kdenlive/index.docbook |  300 --
 po/gl/kdenlive.po |   59 +++
 po/id/kdenlive.po |  113 +-
 po/nl/kdenlive.po |   10 -
 po/pt_BR/kdenlive.po  |  122 +++
 po/uk/kdenlive.po |4
 po/zh_CN/kdenlive.po  |4
 13 files changed, 418 insertions(+), 339 deletions(-)

unblock kdenlive/18.12.3-1

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

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

Bug#925450: unblock: libanyevent-perl/7.140-3

[Peter Pentchev]

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

Hi,

Please unblock package libanyevent-perl if you consider it fine to.

The reason for the 7.140-3 upload was to change the default size of
the DH parameters generated by AnyEvent::TLS, since OpenSSL 1.1.1
no longer accepts < 2048. This came up in the stunnel4 tests that
I added to the Debian package; they use a Perl client/server program
and connect to or accept connections from stunnel4, and they broke
with OpenSSL 1.1.1; see https://bugs.debian.org/923448 for
the stunnel4 bug and https://bugs.debian.org/923615 for
the libanyevent-perl bug that I cloned from the former.

At the time I decided that the AnyEvent::TLS bug itself was not
that important, but I've since realized that it is actually bad -
it means that any Perl programs that depend on AnyEvent::TLS will
no longer work with OpenSSL 1.1.1 unless they override the defaults
as I did in the stunnel4 test. So IMHO libanyevent-perl 7.140-3
should migrate to testing if you agree with this reasoning; I could
also raise the severity of #923615 to provide a formal justification.

I'm attaching the debdiff between 7.140-2 and 7.140-3; the DH params
change is the only one affecting the package's behavior.

Thanks in advance for your consideration even if you decide to decline
my request, and keep up the great work!

unblock libanyevent-perl/7.140-3

G'luck,
Peter

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

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


signature.asc
Description: PGP signature

Bug#925450: unblock: libanyevent-perl/7.140-3

[Peter Pentchev]

On Mon, Mar 25, 2019 at 11:24:06AM +0200, Peter Pentchev wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: unblock
> 
> Hi,
> 
> Please unblock package libanyevent-perl if you consider it fine to.
[snip
> 
> I'm attaching the debdiff between 7.140-2 and 7.140-3; the DH params
> change is the only one affecting the package's behavior.

Right, so here it is...

G'luck,
Peter

-- 
Peter Pentchev  roam@{ringlet.net,debian.org,FreeBSD.org} p...@storpool.com
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13
diff -Nru libanyevent-perl-7.140/debian/changelog libanyevent-perl-7.140/debian/changelog
--- libanyevent-perl-7.140/debian/changelog	2018-01-05 23:08:43.0 +0200
+++ libanyevent-perl-7.140/debian/changelog	2019-03-03 00:20:08.0 +0200
@@ -1,3 +1,26 @@
+libanyevent-perl (7.140-3) unstable; urgency=medium
+
+  * Team upload.
+
+  [ Salvatore Bonaccorso ]
+  * Update Vcs-* headers for switch to salsa.debian.org
+
+  [ Laurent Baillet ]
+  * fix lintian file-contains-trailing-whitespace warning
+
+  [ Xavier Guimard ]
+  * Email change: Xavier Guimard -> y...@debian.org
+
+  [ Peter Pentchev ]
+  * Add the dh-2048 patch for compatibility with OpenSSL 1.1.
+Closes: #923615; thanks, Sebastian Andrzej Siewior, for
+the proposed fix!
+  * Bring up to compliance with Debian Policy 4.3.0:
+- add "Rules-Requires-Root: no" to the source control stanza
+  * Bump the debhelper compatibility level to 11 with no changes.
+
+ -- Peter Pentchev   Sun, 03 Mar 2019 00:20:08 +0200
+
 libanyevent-perl (7.140-2) unstable; urgency=medium
 
   [ Alex Muntada ]
@@ -275,7 +298,7 @@
   * Move libasync-interrupt-perl to Suggests
   * Add libtask-weaken-perl to Suggests
   * Run loop tests
-  * Add libevent-perl, libglib-perl, libio-async-perl, libnet-ssleay-perl, 
+  * Add libevent-perl, libglib-perl, libio-async-perl, libnet-ssleay-perl,
 libpoe-perl and perl-tk to Build-Depends (needed by tests) and Suggests
   * Run tests under xvfb (due to Tk tests), update Build-Depends accordingly
 
diff -Nru libanyevent-perl-7.140/debian/compat libanyevent-perl-7.140/debian/compat
--- libanyevent-perl-7.140/debian/compat	2018-01-05 23:08:43.0 +0200
+++ libanyevent-perl-7.140/debian/compat	2019-03-03 00:01:41.0 +0200
@@ -1 +1 @@
-10
+11
diff -Nru libanyevent-perl-7.140/debian/control libanyevent-perl-7.140/debian/control
--- libanyevent-perl-7.140/debian/control	2018-01-05 23:08:43.0 +0200
+++ libanyevent-perl-7.140/debian/control	2019-03-03 00:01:02.0 +0200
@@ -2,11 +2,11 @@
 Maintainer: Debian Perl Group 
 Uploaders: Ansgar Burchardt ,
gregor herrmann ,
-   Xavier Guimard 
+   Xavier Guimard 
 Section: perl
 Testsuite: autopkgtest-pkg-perl
 Priority: optional
-Build-Depends: debhelper (>= 10),
+Build-Depends: debhelper (>= 11),
libasync-interrupt-perl,
libcanary-stability-perl,
libev-perl,
@@ -21,10 +21,11 @@
shared-mime-info,
xauth,
xvfb
-Standards-Version: 4.1.3
-Vcs-Browser: https://anonscm.debian.org/cgit/pkg-perl/packages/libanyevent-perl.git
-Vcs-Git: https://anonscm.debian.org/git/pkg-perl/packages/libanyevent-perl.git
+Standards-Version: 4.3.0
+Vcs-Browser: https://salsa.debian.org/perl-team/modules/packages/libanyevent-perl
+Vcs-Git: https://salsa.debian.org/perl-team/modules/packages/libanyevent-perl.git
 Homepage: https://metacpan.org/release/AnyEvent
+Rules-Requires-Root: no
 
 Package: libanyevent-perl
 # needs to be and stay arch:any; constants.pl has arch-specific constants
diff -Nru libanyevent-perl-7.140/debian/copyright libanyevent-perl-7.140/debian/copyright
--- libanyevent-perl-7.140/debian/copyright	2018-01-05 23:08:43.0 +0200
+++ libanyevent-perl-7.140/debian/copyright	2019-03-02 23:00:18.0 +0200
@@ -26,7 +26,7 @@
  2009, Maximilian Gass 
  2010-2012, Nicholas Bamber 
  2011-2012, Alessandro Ghedini 
- 2012-2013, Xavier Guimard 
+ 2012-2013, Xavier Guimard 
 License: Artistic or GPL-1+
 
 License: Artistic
diff -Nru libanyevent-perl-7.140/debian/patches/dh-2048.patch libanyevent-perl-7.140/debian/patches/dh-2048.patch
--- libanyevent-perl-7.140/debian/patches/dh-2048.patch	1970-01-01 02:00:00.0 +0200
+++ libanyevent-perl-7.140/debian/patches/dh-2048.patch	2019-03-02 23:42:59.0 +0200
@@ -0,0 +1,28 @@
+Description: Use 2048-bit DH keys by default.
+ It is a sensible size nowadays; also, the Debian package of OpenSSL 1.1
+ no longer accepts smaller DH keys in its default configuration.
+Bug-Debian: https://bugs.debian.org/923615
+Forwarded: no
+Author: Sebastian Andrzej Siewior 
+Last-Update: 2019-03-02
+
+--- a/lib/AnyEvent/TLS.pm
 b/lib/AnyEvent/TLS.pm
+@@ -472,7 +472,7 @@
+ =item dh => $string
+ 
+ Specify the Diffie-Hellman parameters in PEM format directly as a st

Bug#925160: request for performance test in your environment

[Laurent Bonnaud]

On 3/24/19 2:06 PM, Osamu Aoki wrote:

> FYI: I have uploaded 0.41-1 which is essentially code clean up with
> lintian warning removal actions such as adding autopkgtest data.
> So use this 0.41-1, please.

Thanks a lot!

> I will be curious how these affects performance.

SSH connections are now almost instantaneous on my system.

> When you report, please tell us you use SSD or HDD for /usr/lib/*.

My system has a SSD.

> Also give us idea how many directories we are talking by including
> 
>  $ ls -1 /usr/lib /usr/lib/x86_64-linux-gnu|wc -l

18279

Thanks again,

-- 
Laurent.

Bug#924974: unblock (pre-approval): epiphany-browser/3.32.0-2

[Simon McVittie]

Control: tags -1 + moreinfo

On Tue, 19 Mar 2019 at 10:32:30 +, Simon McVittie wrote:
> The GNOME team would like to get epiphany-browser 3.32.0 into testing,
> replacing the current 3.31.91 (3.32 release candidate 1). This will
> maximize the period in which we can track upstream 3.32.x bugfix releases
> for buster, which seems likely to be important for a web browser.
> This also fixes RC bug #922730 (failure to run on 32-bit machines).

According to upstream, 3.32.0 is not suitable and we should be using
3.32.1.2. That version has various post-release fixes, and also restores
the bundled copy of libdazzle 3.32.x instead of using the system libdazzle
3.30.x: upstream say 3.32.x has important fixes for epiphany-browser.

I've prepared a draft package at
,
but someone who knows the package better should probably take over at
this point, so I'm marking the unblock request as moreinfo.

smcv

Bug#925451: xenomai-kernel-source: depends on kernel-package, which will not be in buster

[Ivo De Decker]

package: xenomai-kernel-source
version: 2.6.4+dfsg-1
severity: serious

Hi,

It seems xenomai-kernel-source depends on kernel-package, which will not be in
buster, (see https://bugs.debian.org/925411).

Cheers,

Ivo

Bug#924009: closed by Dimitrios Eftaxiopoulos (Bug not reproduced)

[di dit]

Hello Bernhard and Dimitrios,

> I think the issue is that freefem++s configure activate
> AVX instructions when the build CPU supports it.
>
>
> I could reproduce the crash in a Buster amd64 qemu VM, that
> unintentionally did not support AVX (while the VM host would).

I reproduced the crash with a Buster amd64 PC without AVX support
(Intel(R) Celeron(R) CPU  N3050). In other words, freefem++ crashes
here on 2 amd64 PCs without AVX but not on 2 others with AVX.
Congratulations Bernhard, I think your diagnostic is good!

Regards

Bug#925445: Aw: Bug#925445 closed by Julian Andres Klode (Re: Bug#925445: jessie-backports packages for amd64 have disappeared from mirrors)

[Nik Wrt]

Many thanks for your fast reply. How do I contact the LTS or backports people?

Bug#925423: elpa-debian-el: unable to report a bug in package reportbug

[David Bremner]

Salman Mohammadi  writes:

Control: reassign -1 emacs-common
Control: tag -1 upstream
Control: severity -1 normal

> The content of the variable *message-send-mail-function* as you have
> correctly guessed is *message-send-mail-with-mailclient*.

OK. I'm reassiging to emacs, since the problem is more general than this
one package.

> I don't know how to test this feature (e.g. sending using smtp) without
> spamming BTS.

You can change the the "To: " field in the composition buffer before
sending. I just changed my own address to test.

> I should also add that I have this bug only with *reportbug* package and
> not other packages, that I have previously tried.

I haven't checked all the details, but apparently any time the bug
script for a package (in /usr/share/bug//script) generates
information this is included as an attachement. On the whole this is
probably a good thing, most MUAs are much better at dealing with large
attachments than with miles of inline text.

Bug#925452: unblock: pkg-kde-tools/0.15.29

[Dmitry Shachnev]

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

Dear Release team, please unblock package pkg-kde-tools.

It fixes a bug of severity important: #905736.

Additionally there are some minor changes related to updating URLs from
Alioth to Salsa. These were committed to our Git, I thought these can count
as “documentation fixes”, so I did not revert them.

The debdiff between 0.15.28 and 0.15.29 is attached.

  unblock pkg-kde-tools/0.15.29

Also, can you please binNMU src:qtquickcontrols2-opensource-src against this
version of pkg-kde-tools? That will fix bug #905738 in Buster (currently it
is only fixed in experimental). If needed I can file a separate bug for that.

  nmu qtquickcontrols2-opensource-src_5.11.3+dfsg-2 . ANY . -m 'Rebuild against 
fixed pkg-kde-tools, see #905738'

--
Dmitry Shachnev
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,21 @@
+pkg-kde-tools (0.15.29) unstable; urgency=medium
+
+  [ Kunal Mehta ]
+  * Replace broken alioth URLs in man pages (Closes: #905845).
+
+  [ Simon Quigley ]
+  * Bump Standards-version to 4.1.4, no changes needed.
+  * Run wrap-and-sort.
+
+  [ Dmitry Shachnev ]
+  * Update Vcs fields for move to salsa.debian.org.
+
+  [ Andreas Ferber ]
+  * dh_qmlcdeps: don't exit on first package without qmlc files (Closes:
+#905736).
+
+ -- Dmitry Shachnev   Sun, 24 Mar 2019 13:19:34 +0300
+
 pkg-kde-tools (0.15.28) unstable; urgency=medium
 
   * Bump libdpkg-perl build-dependency too, to make the tests pass.
--- a/debian/control
+++ b/debian/control
@@ -3,15 +3,15 @@ Section: devel
 Priority: optional
 Maintainer: Debian Qt/KDE Maintainers 
 Build-Depends: cmake (>= 2.6.4), debhelper (>= 9), libdpkg-perl (>= 1.19.0~)
-Standards-Version: 4.1.1
+Standards-Version: 4.1.4
 Uploaders: Sune Vuorela ,
Modestas Vainius ,
Maximiliano Curia ,
Lisandro Damián Nicanor Pérez Meyer ,
Pino Toscano ,
-   Dmitry Shachnev ,
-Vcs-Git: https://anonscm.debian.org/git/pkg-kde/pkg-kde-tools.git
-Vcs-Browser: https://anonscm.debian.org/git/pkg-kde/pkg-kde-tools.git
+   Dmitry Shachnev 
+Vcs-Git: https://salsa.debian.org/qt-kde-team/pkg-kde-tools.git
+Vcs-Browser: https://salsa.debian.org/qt-kde-team/pkg-kde-tools
 
 Package: pkg-kde-tools
 Architecture: all
--- a/dh_qmlcdeps
+++ b/dh_qmlcdeps
@@ -75,7 +75,7 @@ foreach my $package (@{$dh{DOPACKAGES}}) {
 }
 }, $tmpdir);
 
-$qt_version_bin or exit(0);
+$qt_version_bin or next;
 my @qt_version = unpack("C4", $qt_version_bin);
 my $qt_version_str = "$qt_version[2].$qt_version[1].$qt_version[0]";
 $qt_version[2] == 5 or error("Qt version $qt_version_str is not supported");
--- a/man1/pkgkde-gensymbols.1
+++ b/man1/pkgkde-gensymbols.1
@@ -104,7 +104,7 @@ the
 .BR dpkg-gensymbols (1)
 man page.
 .SH SEE ALSO
-.BR http://pkg-kde.alioth.debian.org/symbolfiles.html
+.BR https://qt-kde-team.pages.debian.net/symbolfiles.html
 .br
 .BR https://people.redhat.com/drepper/symbol\-versioning
 .br
--- a/man1/pkgkde-symbolshelper.1
+++ b/man1/pkgkde-symbolshelper.1
@@ -85,7 +85,7 @@ pkgkde-symbolshelper batchpatch -v 1.8 foo_unstable_logs/foo_1.8-1*.build
 This man page was based text written by others from the pkg-kde
 symbols file help page.
 .SH SEE ALSO
-.BR http://pkg-kde.alioth.debian.org/symbolfiles.html
+.BR https://qt-kde-team.pages.debian.net/symbolfiles.html
 .br
 .BR https://people.redhat.com/drepper/symbol\-versioning
 .br


signature.asc
Description: PGP signature

Bug#925453: xenomai-kernel-source: ships patches for old kernel

[Ivo De Decker]

package: xenomai-kernel-source
version: 2.6.4+dfsg-1
severity: grave

Hi,

The kernel patches shipped in xenomai-kernel-source haven't been updated in a
long time, so they won't work with any kernel shipped in buster.

Please note that the package description mentions patches for a 2.6 kernel,
but the readme mentions newer kernels (3.x), so the description is probably
outdated. Still, buster will not ship with a 3.x kernel.

Cheers,

Ivo

Bug#925399: zim: Window dialog become oversized for long paths

[Raphael Hertzog]

Hello,

On Sun, 24 Mar 2019, Emmanuel Chantréau wrote:
>* What led up to the situation?
> 
> Click to rename a page
> 
>* What was the outcome of this action?
> 
> A dialog which is wider than my screen (1920 width).
> 
>* What outcome did you expect instead?
> 
> I expected a dialog with normal size.
> The problem come from the printing of the path of the page. You should
> crop it, use new lines or a scrollbar.

Can you share with us the current name of the page being renamed so that
we get an idea of how long it was?

Also can you try with zim 0.70~rc3-1 from experimental? It's rewritten
using python3 and Gtk3, and given the big change in the graphical toolkit,
it's worth ensuring that the problem also exists in that version
before reporting the bug to upstream.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Support Debian LTS: https://www.freexian.com/services/debian-lts.html
Learn to master Debian: https://debian-handbook.info/get/

Bug#925445: [Aptitude-devel] Bug#925445: Aw: Bug#925445 closed by Julian Andres Klode (Re: Bug#925445: jessie-backports packages for amd64 have disappeared from mirrors)

[Axel Beckert]

Hi Nik,

Nik Wrt wrote:
> Many thanks for your fast reply. How do I contact the LTS or backports people?

https://lists.debian.org/debian-lts/ → debian-...@lists.debian.org
https://lists.debian.org/debian-backports/ → debian-backpo...@lists.debian.org

And the latter already has your question — answered:
https://lists.debian.org/debian-backports/2019/03/msg00043.html

Please also see
https://lists.debian.org/debian-backports/2019/03/msg00039.html

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Bug#924076: tvtime: insecure use of /tmp

[Jakub Wilk]

Hi Helge!

* Helge Kreutzmann , 2019-03-23, 20:48:

+/* Create a secure private temporary directory */
+fifosdir = mkdtemp(FIFODIR "tvtimeXX");


The mkdtemp(2) man page says: "Since it will be modified, template must 
not be a string constant, but should be declared as a character array." 
This is the reason it segfaults.


Also, slash is missing between FIFODIR and "tvtime".

You would need something like this:

  char *fifosdir;
  char fifosdir_buf[] = FIFODIR "/tvtimeXX";
  fifosdir = mkdtemp(fifosdir_buf);

So (with the addition of error handling) this would fix insecure use of 
/tmp; but it also breaks communication between tvtime-command(1) and 
tvtime(1). They need to use the same fifo to communicate, but mkdtemp() 
ensures that this is never the case:


  $ tvtime-command QUIT
  Reading configuration from /etc/tvtime/tvtime.xml
  Reading configuration from /home/jwilk/.tvtime/tvtime.xml
  tvtime-command: Cannot open /tmp/tvtimeHH48wA/.TV-jwilk/tvtimefifo-borsuk: No 
such file or directory

It would be best to avoid using /tmp for fifos. tvtime already falls 
back to $HOME when /tmp couldn't be used (grep for "put the fifo in 
$HOME" in src/utils.c), to this should be a matter of disabling the /tmp 
codepath.


--
Jakub Wilk

Bug#925360: pcre2: Uses SSE2 unconditionally on i386

[Matthew Vernon]

forwarded 925360 https://bugs.exim.org/show_bug.cgi?id=2385
quit

Hi,

On 23/03/2019 18:54, Guillem Jover wrote:

> I just upgraded a server of mine to Debian buster, and roundcube's
> postinst started to crash with "Illegal instruction" messages from a
> php process, due to usage of a SSE2 instruction (PSLLDQ). This
> instruction is not required by our ISA baseline, and SSE2 is not
> present on many i386 based CPUs, such as AMD Semprons for example.

Thanks for the bug report (and the patch!). I've sent this to upstream
to see what they say; if I don't get a response in a day or two, I'll
just apply it, as it looks plausible to me :)

Regards,

Matthew

Bug#925454: RM: tomcat8 -- ROM; Replaced by tomcat9

[Emmanuel Bourg]

Package: ftp.debian.org
Severity: normal

Hi,

Please remove the tomcat8 package from testing and unstable (not experimental).
This package has been replaced by tomcat9 for Buster.

Thank you,

Emmanuel Bourg

Bug#925134: grub-efi-amd64-signed: doesn't mount cryptodisk

[Paolo Miotto]

Il 23/03/19 15:01, Colin Watson ha scritto:
> Could you please describe, in as much detail as possible, how to set up
> an environment that replicates this bug?


Hello Colin, thanks for your reply.


Installing the package grub-efi-amd64 with this command line:

   apt install --reinstall grub-efi-amd64

still removes from /boot/efi/EFI/debian/grub.cfg any line like this:

   insmod luks


But now both the vms that I've installed to replicate the bug and my 
laptop are booting correctly without that line.

I don't know why immediately after the package upgrade it didn't works 
and now it works, but I'm not able to replicate it to help who have a 
similar upgrade path.


I have a detailed description of the steps to replicate the line 
removal, but, as this is no more a issue, I don't know if you want to 
investigate further. If so, feel free to ask.


Bye.


-- 

Paolo

Bug#925455: alsa volume never saved/restored

[Laurent Bigonville]

Package: alsa-utils
Version: 1.1.8-1
Severity: important
File: /lib/systemd/system/alsa-restore.service

Hi,

On my newly installed laptop, the volume is never saved and restored

It seems that the "alsa-restore.service" is never "started/stopped"
because there is a condition not met:

$ systemctl status alsa-restore.service 
● alsa-restore.service - Save/Restore Sound Card State
   Loaded: loaded (/lib/systemd/system/alsa-restore.service; static; vendor 
preset: enabled)
   Active: inactive (dead)
Condition: start condition failed at Mon 2019-03-25 10:25:34 CET; 1h 15min ago
 Docs: man:alsactl(1)

mar 25 10:25:34 edoras systemd[1]: Condition check resulted in Save/Restore 
Sound Card State being skipped.

Looking a bit further it seems that /var/lib/alsa/asound.state doesn't
exist.

That means that we are facing a chicken-egg problem here, the file will
never be created as the service is never started (and then never
stopped).

An option might be to create an empty file in the postinst script on the
first installation. An empty file will cause the "alsa restore" command
to fail with return code 99 but the systemd service will still be marked
as "active (exited)" and the ExecStop will be executed on shutdown
meaning that the volume will be saved. (Wouldn't that cause issue with
some setup?)

AFAICS, it's a regression and we might want to get this fixed in buster,
if you think it should be the case, please make this bug RC.

Kind regards,
Laurent Bigonville

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

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

Versions of packages alsa-utils depends on:
ii  kmod  26-1
ii  libasound21.1.8-1
ii  libc6 2.28-8
ii  libfftw3-single3  3.3.8-2
ii  libncursesw6  6.1+20181013-2
ii  libsamplerate00.1.9-2
ii  libtinfo6 6.1+20181013-2
ii  lsb-base  10.2019031300
ii  whiptail  0.52.20-8

alsa-utils recommends no packages.

alsa-utils suggests no packages.

-- no debconf information

Bug#925456: calcurse: Impossible to run Calcurse with a Posteo calendar

[Cyril Augier]

Package: calcurse
Version: 4.2.1-1.1
Severity: normal

Hi !

Impossible to synchronize local calendar with Posteo remote calendar.

I first configured my configuration file with the remote calendar address and
identifiers.

Then I configured my calendar with "calcurse-caldav --init=two-way" without any
problem.

$ calcurse-caldav --init=two-way
> Connecting  to posteo.de:8443...
> Importing  new object c6111f26ece0a5f63d37b576e14f2e66.
> Importing new object 05bcf05b36d7891c92ab2d2d9748c8a2.
> Importing new object 66a556337290a7723ced1ee578422b8a.
> Importing new object 4e63a9646ed41a7b0432d1b2a5ebd572.
> Importing new object 1adbb469265326ed19e2086292e9d764.
> Importing new object c2ba6417f0aa26d3a415d1007914cc1e.
> Importing new object 521dec9ef1dc7e979722052eb58081c5.
> Importing new object eeeb556d9130782260a9282d6ef870ec.
> Importing new object 7d367494e03c6473c84019eb63b289c5.
> Importing new object b44f101e66566d2ccfb25b75dfb974a7.
> Pushing new object 148ae2dbf9f6ff39be495dbffa4c659cb84a0339 to the server.
> Pushing new object c8e23e522ab82115ec8386a17b3a6fcec3c51721 to the server.
> Pushing new object 4a742904168fc07420cda28a897d8a2df32730ab to the server.
> Pushing new object 67bd0b54cd76488c6e6349dd6585541279b8dd0b to the server.
> Pushing new object 6f59f8a4934199e88ab07efc0a54d49a26ccdf41 to the server.
> Pushing new object 8a68f461f881dce78b332f15aab41d0d6e93f64d to the server.
> Pushing new object 73a2bf3c635f7f063e53602ad19f6a68500b8d45 to the server.
> Pushing new object aa29e91a838c1c6aa364d80985f2e036b75ac47b to the server.
> Saving synchronization database to /home/cyril/.calcurse/caldav/sync.db...
> 10 items imported, 0 items removed locally.
> 8 items exported, 0 items removed from the server.

Then I can add events to local calendar. But I can't run "calcurse-caldav" to
synchronize local calendar with remote calendar.

$ calcurse-caldav
> Connecting to posteo.de:8443...
> Loading synchronization database from /home/cyril/.calcurse/caldav/sync.db...
> error: The server at posteo.de:8443 replied with HTTP status code 500
(Internal
> error: Server Error) while trying to access
/calendars/nameAccount/nameCalendar/.

I also noticed that the events I synchronized with the first command are not
correct. For example, an event from 13:00 to 14:00 does not last 1 hour but is
a full day, from 13:00 from day A to 14:00 the following day.

I tested version 4.4.0 on another distribution, the version works correctly.
Also, another user has opened an issue on Github, maybe it can help:
https://github.com/lfos/calcurse/issues/23

Thanks !



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

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

Versions of packages calcurse depends on:
ii  libc6 2.24-11+deb9u4
ii  libncursesw5  6.0+20161126-1+deb9u2
ii  libtinfo5 6.0+20161126-1+deb9u2
ii  python3   3.5.3-1

calcurse recommends no packages.

calcurse suggests no packages.

-- no debconf information

Bug#884648: Follow up on mate-panel crashes

[Alastair Irvine]

Hello.  On 02 May 2018, #884648 was updated with full backtrace info.

Is there any chance you could take a look at this before the full freeze
for Buster?

Bug#925423: elpa-debian-el: unable to report a bug in package reportbug

[Salman Mohammadi]

On Sun, 24 Mar 2019 22:19:58 -0300 David Bremner  wrote:

> If possible, I'd suggest using a different value of

> message-send-mail-function (I think it's initialized from
> send-mail-function).
>
> d
>
>

Dear David,

I assigned  *message-smtpmail-send-it* to the variable and I could send
the message with no problem without using an external mail client.

Bug#921094:

[Cyril Augier]

Hi !

I'm sorry I didn't answer.

I didn't look at the version, it was the last one available.

Bug#925455: alsa volume never saved/restored

[Laurent Bigonville]

On Mon, 25 Mar 2019 12:01:02 +0100 Laurent Bigonville  
wrote:


>
> An option might be to create an empty file in the postinst script on the
> first installation. An empty file will cause the "alsa restore" command
> to fail with return code 99 but the systemd service will still be marked
> as "active (exited)" and the ExecStop will be executed on shutdown
> meaning that the volume will be saved. (Wouldn't that cause issue with
> some setup?)

The more obvious solution would of course be to remove the condition in 
the .service file

Bug#925373: libpam-modules: Executing script from pam_motd or pam_exec produce a huge memory consumption

[Ricardo Fraile]

Setting the following line on systemd-user file stops the issue:

echo '@include null' >> /etc/pam.d/systemd-user

Someone knows why including an inexistent file can change the behaviour?


Thanks,

Bug#904998: libstdc++6: libtsdc++ with g++-8 hangs in std::local_Rb_tree_decrement

[Alastair McKinstry]

close 904998

thanks


Confirming that this bug is fixed in 8.3.0

regards

Alastair




On 30/07/2018 11:26, Alastair McKinstry wrote:

Package: libstdc++6
Version: 8.2.0-1
Severity: important

With a program I'm working on, its run
$ mpiexec -n 1 ./bin/server.exe : -n 1 ./bin/client.exe

both programs hang, with:

#0  std::local_Rb_tree_decrement (__x=0x55f54daac538) at 
../../../../../src/libstdc++-v3/src/c++98/tree.cc:99
#1  0x55f54d04eba8 in xios::CReorderDomain::registerTrans() ()
#2  0x55f54cf5953f in _GLOBAL__sub_I__ZN4xios14CReorderDomainC2Ev ()

The MPI nature of the code should be irrelevant (they're independent processes, 
not interacting at this point but running the same piece of code)
This code works with  g++ 7.3, but fails with 8.1/ 8.2

thanks
Alastair



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

Kernel: Linux 4.9.0-6-686-pae (SMP w/1 CPU core)
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_IE.UTF-8), LANGUAGE=en_IE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_IE.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libstdc++6 depends on:
ii  gcc-6-base  6.3.0-18+deb9u1
ii  libc6   2.24-11+deb9u3
ii  libgcc1 1:6.3.0-18+deb9u1

libstdc++6 recommends no packages.

libstdc++6 suggests no packages.

-- no debconf information


--
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Misentropy: doubting that the Universe is becoming more disordered.

Bug#925458: #923838: unblock: ghostwriter: Invalid Vcs-Git field in debian/control file

[Sebastien CHAVAUX]

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

Please unblock package ghostwriter 1.7.4-2, this version fixes several bugs (Debian Bug Reporting Logs - # 923838 and 
# 923837). He does not include others to my knowledge. Best regards

Bug#925457: python-jwcrypto: FTBFS ('module' object has no attribute 'decode_rfc6979_signature')

[Santiago Vila]

Package: src:python-jwcrypto
Version: 0.4.2-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.7 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython2_2.7_jwcrypto/build/jwcrypto
copying jwcrypto/jwa.py -> 
/<>/.pybuild/cpython2_2.7_jwcrypto/build/jwcrypto
copying jwcrypto/jwk.py -> 
/<>/.pybuild/cpython2_2.7_jwcrypto/build/jwcrypto
copying jwcrypto/jws.py -> 
/<>/.pybuild/cpython2_2.7_jwcrypto/build/jwcrypto
copying jwcrypto/__init__.py -> 
/<>/.pybuild/cpython2_2.7_jwcrypto/build/jwcrypto
copying jwcrypto/jwe.py -> 
/<>/.pybuild/cpython2_2.7_jwcrypto/build/jwcrypto
copying jwcrypto/tests-cookbook.py -> 
/<>/.pybuild/cpython2_2.7_jwcrypto/build/jwcrypto
copying jwcrypto/jwt.py -> 
/<>/.pybuild/cpython2_2.7_jwcrypto/build/jwcrypto
copying jwcrypto/tests.py -> 
/<>/.pybuild/cpython2_2.7_jwcrypto/build/jwcrypto
copying jwcrypto/common.py -> 
/<>/.pybuild/cpython2_2.7_jwcrypto/build/jwcrypto
I: pybuild base:217: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython3_3.7_jwcrypto/build/jwcrypto
copying jwcrypto/jwa.py -> 
/<>/.pybuild/cpython3_3.7_jwcrypto/build/jwcrypto
copying jwcrypto/jwk.py -> 
/<>/.pybuild/cpython3_3.7_jwcrypto/build/jwcrypto
copying jwcrypto/jws.py -> 
/<>/.pybuild/cpython3_3.7_jwcrypto/build/jwcrypto
copying jwcrypto/__init__.py -> 
/<>/.pybuild/cpython3_3.7_jwcrypto/build/jwcrypto
copying jwcrypto/jwe.py -> 
/<>/.pybuild/cpython3_3.7_jwcrypto/build/jwcrypto
copying jwcrypto/tests-cookbook.py -> 
/<>/.pybuild/cpython3_3.7_jwcrypto/build/jwcrypto
copying jwcrypto/jwt.py -> 
/<>/.pybuild/cpython3_3.7_jwcrypto/build/jwcrypto
copying jwcrypto/tests.py -> 
/<>/.pybuild/cpython3_3.7_jwcrypto/build/jwcrypto
copying jwcrypto/common.py -> 
/<>/.pybuild/cpython3_3.7_jwcrypto/build/jwcrypto
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:217: cd /<>/.pybuild/cpython2_2.7_jwcrypto/build; 
python2.7 -m nose -v 
test_5_10_encryption (jwcrypto.tests-cookbook.Cookbook08JWETests) ... ok
test_5_11_encryption (jwcrypto.tests-cookbook.Cookbook08JWETests) ... ok
test_5_12_encryption (jwcrypto.tests-cookbook.Cookbook08JWETests) ... ok
test_5_1_encryption (jwcrypto.tests-cookbook.Cookbook08JWETests) ... ok
test_5_2_encryption (jwcrypto.tests-cookbook.Cookbook08JWETests) ... ok
test_5_3_encryption (jwcrypto.tests-cookbook.Cookbook08JWETests) ... ok
test_5_4_encryption (jwcrypto.tests-cookbook.Cookbook08JWETests) ... ok
test_5_5_encryption (jwcrypto.tests-cookbook.Cookbook08JWETests) ... ok
test_5_6_encryption (jwcrypto.tests-cookbook.Cookbook08JWETests) ... ok
test_5_7_encryption (jwcrypto.tests-cookbook.Cookbook08JWETests) ... ok
test_5_8_encryption (jwcrypto.tests-cookbook.Cookbook08JWETests) ... ok
test_5_9_encryption (jwcrypto.tests-cookbook.Cookbook08JWETests) ... ok
test_4_1_signing (jwcrypto.tests-cookbook.Cookbook08JWSTests) ... ok
test_4_2_signing (jwcrypto.tests-cookbook.Cookbook08JWSTests) ... ok
test_4_3_signing (jwcrypto.tests-cookbook.Cookbook08JWSTests) ... ERROR
test_4_4_signing (jwcrypto.tests-cookbook.Cookbook08JWSTests) ... ok
test_4_6_signing (jwcrypto.tests-cookbook.Cookbook08JWSTests) ... ok
test_4_7_signing (jwcrypto.tests-cookbook.Cookbook08JWSTests) ... ok
test_4_8_signing (jwcrypto.tests-cookbook.Cookbook08JWSTests) ... ERROR
test_aes_128 (jwcrypto.tests.ConformanceTests) ... ok
test_aes_192 (jwcrypto.tests.ConformanceTests) ... ok
test_aes_256 (jwcrypto.tests.ConformanceTests) ... ok
test_jwe_default_recipient (jwcrypto.tests.ConformanceTests) ... ok
test_jwe_headers_as_dicts (jwcrypto.tests.ConformanceTests) ... ok
test_jwe_no_alg_in_jose_headers (jwcrypto.tests.ConformanceTests) ... ok
test_jwe_no_enc_in_jose_headers (jwcrypto.tests.ConformanceTests) ... ok
test_jwe_no_protected_header (jwcrypto.tests.ConformanceTests) ... ok
test_jws_headers_as_dicts (jwcrypto.tests.ConformanceTests) ... ok
test_jws_loopback (jwcrypto.tests.ConformanceTests) ... ok
test_key_ops_values (jwcrypto.tests.ConformanceTests) ... ok
test_unknown_key_params (jwcrypto.tests.ConformanceTests) ... ok
test_jwa_create (jwcrypto.tests.JWATests) ... ok
test_A1 (jwcrypto.tests.TestJWE) ... ok
test_A2 (jwcrypto.tests.TestJWE) ... ok
test_A3 (jwcrypto.tests.TestJWE) ... ok
test_A4 (jwcrypto.tests.TestJWE) ... ok
test_A5 (jwcrypto.tests.TestJWE) ... ok
test_create_priKeys (jwcrypto.tests.TestJWK) ... ok
test_create_pubKeys (jwcrypto.tests.TestJWK) ... ok
test_create_symKe

Bug#884648: Follow up on mate-panel crashes

[Mike Gabriel]

Hi,

On  Mo 25 Mär 2019 12:06:57 CET, Alastair Irvine wrote:


Hello.  On 02 May 2018, #884648 was updated with full backtrace info.

Is there any chance you could take a look at this before the full freeze
for Buster?


From the bug's history, I cannot see, if the issue happens on a  
buster system or just on stretch systems.


Furthermore, the coredump shows that it is caused by gtk_drag_finish.  
Both coredumps on the bug hint that your issue is triggered by some  
drag'n'drop operation. Is that so?


Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4354) 8390 139

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgp1G5VHyGuDB.pgp
Description: Digitale PGP-Signatur

Bug#925459: yelp: xkbcommon: ERROR: Key "" added to modifier map for multiple modifiers; Using Control, ignoring Lock

[Salman Mohammadi]

Package: yelp
Version: 3.31.90-1
Severity: normal

Dear Maintainer,

Running *yelp* from the command line, throws the following error
message:

xkbcommon: ERROR: Key "" added to modifier map for multiple
modifiers; Using Control, ignoring Lock
xkbcommon: ERROR: Key "" added to modifier map for multiple
modifiers; Using Control, ignoring Lock



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

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

Versions of packages yelp depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.30.1-2
ii libc6 2.28-8
ii libglib2.0-0 2.58.3-1
ii libgtk-3-0 3.24.5-1
ii libwebkit2gtk-4.0-37 2.22.6-1
ii libyelp0 3.31.90-1
ii man-db 2.8.5-2
ii python3-distro 1.3.0-1
ii yelp-xsl 3.31.90-1

Versions of packages yelp recommends:
ii fonts-dejavu 2.37-1

yelp suggests no packages.

-- no debconf information

Bug#923711: (no subject)

[Alexander Couzens]

Can you please test the attached patch if it fixes the memory leakage?

> This is also the case why not all CPU cores are used  during the run
> of mksquashfs.

This is a known bug/feature, as it removes one thread.
mksquashfs only scales the frad_thrd, deflator & removed frag_deflator
thread by the number of cpus.
https://lunarius.fe80.eu/blog/mksquash-dot-graph.html
From c0f336924df833f22be40c34faf2863f39201de3 Mon Sep 17 00:00:00 2001
From: Alexander Couzens 
Date: Mon, 25 Mar 2019 04:55:00 +0100
Subject: [PATCH] mksquashfs: fix compressor initialisation in frag_deflator

Since 97537a036043 the compressor will be initialized on every call
introducing a memory leak on every frag_deflator called.
Use a static and only initialize the stream only once, will leak only
once, as all comp_init() may leak.

Fixes: 97537a036043 ("flag_deflator: initialize the compressor()")
---
 squashfs-tools/mksquashfs.c | 14 ++
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/squashfs-tools/mksquashfs.c b/squashfs-tools/mksquashfs.c
index 935d96013a73..21c7e85e009a 100644
--- a/squashfs-tools/mksquashfs.c
+++ b/squashfs-tools/mksquashfs.c
@@ -2409,12 +2409,18 @@ void frag_deflator(struct file_buffer *file_buffer)
 	int res, c_byte, compressed_size;
 	struct file_buffer *write_buffer;
 
-	res = compressor_init(comp, &stream, block_size, 1);
-	if(res)
-		BAD_ERROR("frag_deflator:: compressor_init failed\n");
+	static int frag_deflator_comp_init = FALSE;
+	static void *frag_stream = NULL;
+
+	if (frag_deflator_comp_init == FALSE) {
+		frag_deflator_comp_init = TRUE;
+		res = compressor_init(comp, &frag_stream, block_size, 1);
+		if(res)
+			BAD_ERROR("frag_deflator:: compressor_init failed\n");
+	}
 
 	write_buffer = cache_get(fwriter_buffer, file_buffer->block);
-	c_byte = mangle2(stream, write_buffer->data, file_buffer->data,
+	c_byte = mangle2(frag_stream, write_buffer->data, file_buffer->data,
 			 file_buffer->size, block_size, noF, 1);
 	compressed_size = SQUASHFS_COMPRESSED_SIZE_BLOCK(c_byte);
 	write_buffer->size = compressed_size;
-- 
2.21.0



pgpVbCI14r7ly.pgp
Description: OpenPGP digital signature

Bug#925460: unblock: nwchem/6.8.1-5

[Andreas Tille]

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

Please unblock package nwchem


diff -Nru nwchem-6.8.1/debian/changelog nwchem-6.8.1/debian/changelog
--- nwchem-6.8.1/debian/changelog   2019-01-21 23:29:56.0 +0100
+++ nwchem-6.8.1/debian/changelog   2019-03-25 09:52:20.0 +0100
@@ -1,3 +1,11 @@
+nwchem (6.8.1-5) unstable; urgency=medium
+
+  * Team upload
+  * Fix clean target
+Closes: #924817
+
+ -- Andreas Tille   Mon, 25 Mar 2019 09:52:20 +0100
+
 nwchem (6.8.1-4) unstable; urgency=medium

   * debian/patches/15_testsuite_print_output_on_failure.patch: Fixed patch.
diff -Nru nwchem-6.8.1/debian/rules nwchem-6.8.1/debian/rules
--- nwchem-6.8.1/debian/rules   2019-01-02 16:00:09.0 +0100
+++ nwchem-6.8.1/debian/rules   2019-03-25 09:52:20.0 +0100
@@ -85,7 +85,7 @@
-(cd $(CURDIR)/doc && make realclean)
rm -rf $(CURDIR)/bin $(CURDIR)/lib $(CURDIR)/src/tools/lib
rm -rf $(CURDIR)/QA/scratchdir $(CURDIR)/QA/testoutputs
-   rm -f src/util/util_version.F src/stubs.F src/util/util_module_avail.F
+   rm -f src/util/util_version.F src/stubs.F src/util/util_module_avail.F 
src/util/util_nwchem_version.F
find $(CURDIR) -name "*.stamp" | xargs rm -f
dh_auto_clean
rm -f src/config/NWCHEM_CONFIG src/config/nwchem_config.h



unblock nwchem/6.8.1-5

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

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

Bug#925461: unblock: pypy/7.0.0+dfsg-3, backports.functools-lru-cache/1.5-3

[Stefano Rivera]

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

Please unblock pypy & backports.functools-lru-cache.

A relatively last-minute feature in pypy was namespace package support
(#920899).  Unfortunately the path I picked isn't what dh_pypy (in
dh-python) implemented, and I think Piotr's rationale for that was
reasonable. But I didn't notice the incompatibility until after the
freeze.

So, #924676 and #924677.

debdiffs attached.

unblock pypy/7.0.0+dfsg-3
unblock backports.functools-lru-cache/1.5-3

Thanks,

SR
diff -Nru pypy-7.0.0+dfsg/debian/changelog pypy-7.0.0+dfsg/debian/changelog
--- pypy-7.0.0+dfsg/debian/changelog2019-02-12 17:41:21.0 -0500
+++ pypy-7.0.0+dfsg/debian/changelog2019-03-24 11:07:07.0 -0400
@@ -1,3 +1,12 @@
+pypy (7.0.0+dfsg-3) unstable; urgency=medium
+
+  * Update watch file regex, upstream calls it pypy2.7 now.
+  * pypycompile and pypyclean now read namespaces from /usr/share/pypy/ns
+(following dh_pypy). (Closes: #924676)
+- Breaks old pypy-backports.functools-lru-cache, using the old location.
+
+ -- Stefano Rivera   Sun, 24 Mar 2019 11:07:07 -0400
+
 pypy (7.0.0+dfsg-2) unstable; urgency=medium
 
   * Remove dh_builddeb override, no longer necessary.
diff -Nru pypy-7.0.0+dfsg/debian/control pypy-7.0.0+dfsg/debian/control
--- pypy-7.0.0+dfsg/debian/control  2019-02-12 17:41:21.0 -0500
+++ pypy-7.0.0+dfsg/debian/control  2019-03-24 11:07:07.0 -0400
@@ -18,8 +18,8 @@
  procps,
  pypy [any-amd64 any-i386 armhf ppc64 ppc64el s390x] ,
  python (>= 2.6.6-11~),
- python-pycparser,
  python-docutils,
+ python-pycparser,
  python-sphinx (>= 1.0.7+dfsg),
  python2.7-dev,
  tcl-dev,
@@ -36,7 +36,9 @@
 Package: pypy
 Architecture: any
 Depends: pypy-lib (= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends}
-Breaks: pypy-dev (<< ${source:Version})
+Breaks:
+ pypy-backports.functools-lru-cache (<< 1.5-3~),
+ pypy-dev (<< ${source:Version})
 Provides: ${pypy-abi}
 Suggests: pypy-doc, pypy-tk (= ${binary:Version})
 Pre-Depends: dpkg (>= 1.15.6~), ${misc:Pre-Depends}
diff -Nru pypy-7.0.0+dfsg/debian/copyright pypy-7.0.0+dfsg/debian/copyright
--- pypy-7.0.0+dfsg/debian/copyright2019-02-12 17:41:21.0 -0500
+++ pypy-7.0.0+dfsg/debian/copyright2019-03-24 11:07:07.0 -0400
@@ -206,7 +206,7 @@
   Floris Bruynooghe
   Christopher Pope
   Tristan Arthur
-  Christian Tismer 
+  Christian Tismer
   Dan Stromberg
   Carl Meyer
   Florin Papa
diff -Nru pypy-7.0.0+dfsg/debian/pypy.dirs pypy-7.0.0+dfsg/debian/pypy.dirs
--- pypy-7.0.0+dfsg/debian/pypy.dirs2019-02-12 17:41:21.0 -0500
+++ pypy-7.0.0+dfsg/debian/pypy.dirs2019-03-24 11:07:07.0 -0400
@@ -1,2 +1,2 @@
+/usr/share/pypy/ns
 /usr/local/lib/pypy2.7/dist-packages
-/usr/lib/pypy/ns
diff -Nru pypy-7.0.0+dfsg/debian/pypy.install 
pypy-7.0.0+dfsg/debian/pypy.install
--- pypy-7.0.0+dfsg/debian/pypy.install 2019-02-12 17:41:21.0 -0500
+++ pypy-7.0.0+dfsg/debian/pypy.install 2019-03-24 11:07:07.0 -0400
@@ -2,5 +2,5 @@
 debian/scripts/pypycompile/usr/bin
 include/pypy_*.h  /usr/lib/pypy/include
 lib_pypy/_*_cffi.*.so /usr/lib/pypy/lib_pypy
-pypy/goal/pypy-c  /usr/lib/pypy/bin
 pypy/goal/libpypy-c.so/usr/lib/pypy/bin
+pypy/goal/pypy-c  /usr/lib/pypy/bin
diff -Nru pypy-7.0.0+dfsg/debian/pypy.links pypy-7.0.0+dfsg/debian/pypy.links
--- pypy-7.0.0+dfsg/debian/pypy.links   2019-02-12 17:41:21.0 -0500
+++ pypy-7.0.0+dfsg/debian/pypy.links   2019-03-24 11:07:07.0 -0400
@@ -1,2 +1,2 @@
-/usr/lib/pypy/bin/pypy-c /usr/bin/pypy
 /usr/lib/pypy/bin/libpypy-c.so /usr/lib/libpypy-c.so
+/usr/lib/pypy/bin/pypy-c /usr/bin/pypy
diff -Nru pypy-7.0.0+dfsg/debian/scripts/pypyclean 
pypy-7.0.0+dfsg/debian/scripts/pypyclean
--- pypy-7.0.0+dfsg/debian/scripts/pypyclean2019-02-12 17:41:21.0 
-0500
+++ pypy-7.0.0+dfsg/debian/scripts/pypyclean2019-03-24 11:07:07.0 
-0400
@@ -31,7 +31,7 @@
 
 def installed_namespaces():
 '''Return a dictionary of package: frozenset(namespaces)'''
-ns_dir = '/usr/lib/pypy/ns'
+ns_dir = '/usr/share/pypy/ns'
 ns_by_pkg = {}
 for pkg in os.listdir(ns_dir):
 ns_file = os.path.join(ns_dir, pkg)
diff -Nru pypy-7.0.0+dfsg/debian/scripts/pypycompile 
pypy-7.0.0+dfsg/debian/scripts/pypycompile
--- pypy-7.0.0+dfsg/debian/scripts/pypycompile  2019-02-12 17:41:21.0 
-0500
+++ pypy-7.0.0+dfsg/debian/scripts/pypycompile  2019-03-24 11:07:07.0 
-0400
@@ -45,7 +45,7 @@
 '''Iterate through a package's ns file.
 Create all necessary__init__.pys, and yield them.
 '''
-ns_file = os.path.join('/usr/lib/pypy/ns', package)
+ns_file = os.path.join('/usr/share/pypy/ns', package)
 if not os.path.exists(ns_file):
 return
 with open(ns_file) as f:
diff -Nru pypy-7.0.0+dfsg/debian/watch pypy-

Bug#921146: (no subject)

[Alexander Couzens]

Hi Laszlo,

yes, removing frag_deflator thread will reduce the CPU usage.
But on the other hand it allows reproducible-builds of the
squashfs image.

mksquashfs spawns $cpus * (frad_thrd, deflator) threads.
Before it also spawned $cpus * frag_deflator, but this work is now done
by the main thread.

Here is a graph of it
https://lunarius.fe80.eu/blog/mksquash-dot-graph.html

best,
lynxis
From c0f336924df833f22be40c34faf2863f39201de3 Mon Sep 17 00:00:00 2001
From: Alexander Couzens 
Date: Mon, 25 Mar 2019 04:55:00 +0100
Subject: [PATCH] mksquashfs: fix compressor initialisation in frag_deflator

Since 97537a036043 the compressor will be initialized on every call
introducing a memory leak on every frag_deflator called.
Use a static and only initialize the stream only once, will leak only
once, as all comp_init() may leak.

Fixes: 97537a036043 ("flag_deflator: initialize the compressor()")
---
 squashfs-tools/mksquashfs.c | 14 ++
 1 file changed, 10 insertions(+), 4 deletions(-)

diff --git a/squashfs-tools/mksquashfs.c b/squashfs-tools/mksquashfs.c
index 935d96013a73..21c7e85e009a 100644
--- a/squashfs-tools/mksquashfs.c
+++ b/squashfs-tools/mksquashfs.c
@@ -2409,12 +2409,18 @@ void frag_deflator(struct file_buffer *file_buffer)
 	int res, c_byte, compressed_size;
 	struct file_buffer *write_buffer;
 
-	res = compressor_init(comp, &stream, block_size, 1);
-	if(res)
-		BAD_ERROR("frag_deflator:: compressor_init failed\n");
+	static int frag_deflator_comp_init = FALSE;
+	static void *frag_stream = NULL;
+
+	if (frag_deflator_comp_init == FALSE) {
+		frag_deflator_comp_init = TRUE;
+		res = compressor_init(comp, &frag_stream, block_size, 1);
+		if(res)
+			BAD_ERROR("frag_deflator:: compressor_init failed\n");
+	}
 
 	write_buffer = cache_get(fwriter_buffer, file_buffer->block);
-	c_byte = mangle2(stream, write_buffer->data, file_buffer->data,
+	c_byte = mangle2(frag_stream, write_buffer->data, file_buffer->data,
 			 file_buffer->size, block_size, noF, 1);
 	compressed_size = SQUASHFS_COMPRESSED_SIZE_BLOCK(c_byte);
 	write_buffer->size = compressed_size;
-- 
2.21.0



pgpV1nLKdpTAz.pgp
Description: OpenPGP digital signature

Bug#925462: iputils-ping: ping rounds up 13.979 ms to 13.10 ms (incorrect handling of decimal overflow?)

[Ralf Jung]

Package: iputils-ping
Version: 3:20180629-2
Severity: normal

Dear Maintainer,

I just got the following output from "ping ipv6-test.com":

PING ipv6-test.com (5.135.165.173) 56(84) bytes of data.
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=1 ttl=54 time=13.7 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=2 ttl=54 time=13.10 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=3 ttl=54 time=13.6 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=4 ttl=54 time=13.6 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=5 ttl=54 time=13.6 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=6 ttl=54 time=13.6 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=7 ttl=54 time=13.6 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=8 ttl=54 time=13.8 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=9 ttl=54 time=13.6 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=10 ttl=54 time=13.7 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=11 ttl=54 time=13.6 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=12 ttl=54 time=13.6 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=13 ttl=54 time=13.6 ms
64 bytes from muscaria.t0x.net (5.135.165.173): icmp_seq=14 ttl=54 time=13.6 ms
^C
--- ipv6-test.com ping statistics ---
14 packets transmitted, 14 received, 0% packet loss, time 33ms
rtt min/avg/max/mdev = 13.586/13.671/13.979/0.156 ms

The second response looks rather curious: why would it print that with a
precision of 2 digits when everything else is printed with 1 digit?  Looking,
however, and the min/max numbers in the end, the min time is 13.586 ms -- so
there actually was no measurement of 13.10 ms!  And moreover, the maximum is
13.979 ms, so there should be a 14.0 ms in the list, but there is not.  My guess
is that ping incorrectly "rounds up" 13.979 to 13.10 (10 being "first digit
after the period + 1" = 9+1) , not realizing that it should instead increment
the number of seconds by 1 (and set the digit after the period to 0).  In other
words, it looks like decimal overflow is not handled properly.

Kind regards,
Ralf

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

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

Versions of packages iputils-ping depends on:
ii  libc6   2.28-8
ii  libcap2 1:2.25-2
ii  libidn2-0   2.0.5-1
ii  libnettle6  3.4.1-1

Versions of packages iputils-ping recommends:
ii  libcap2-bin  1:2.25-2

iputils-ping suggests no packages.

-- no debconf information

Bug#924856: wxpython4.0: FTBFS: sip: /<>/wxpython4.0-4.0.4+dfsg/src/wacky_ints.sip:20: Invalid type for %MappedType

[Scott Talbert]

On Mon, 25 Mar 2019, Dmitry Shachnev wrote:


On Mon, Mar 25, 2019 at 10:27:29AM +0300, Dmitry Shachnev wrote:

I will look at this bug a bit later.


It looks like Scott already has a fix for that, so my help is probably not
needed:

https://github.com/wxWidgets/Phoenix/pull/1189

Next time I will try to build wxpython4.0 before uploading new sip4 releases.


Yes, I think I've got it sorted out.  I'm hoping to get upstream to merge 
my pull request soon, but if not, I'll apply for an unblock request soon.


Probably I can subscribe to the sip4 package tracker and I'll at least be 
alerted when there is a new sip4 upload.  That would help.


Scott

Bug#925354: [Debian-ha-maintainers] Bug#925354: pacemaker-dev: missing Breaks+Replaces: libcrmcluster1-dev

[Valentin Vidic]

On Sat, Mar 23, 2019 at 05:19:59PM +0100, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'wheezy' to 'jessie' to 'stretch' to 'buster'.
> It installed fine in 'wheezy', and upgraded to 'jessie' and 'stretch'
> successfully,
> but then the upgrade to 'buster' failed.
> 
> In case the package was not part of an intermediate stable release,
> the version from the preceding stable release was kept installed.
> 
> From the attached log (scroll to the bottom...):
> 
>   Selecting previously unselected package pacemaker-dev:amd64.
>   Preparing to unpack .../10-pacemaker-dev_2.0.1-1_amd64.deb ...
>   Unpacking pacemaker-dev:amd64 (2.0.1-1) ...
>   dpkg: error processing archive 
> /tmp/apt-dpkg-install-UW7jMV/10-pacemaker-dev_2.0.1-1_amd64.deb (--unpack):
>trying to overwrite '/usr/include/pacemaker/crm/attrd.h', which is also in 
> package libcrmcluster1-dev 1.1.7-1
>   dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
>   Errors were encountered while processing:
>/tmp/apt-dpkg-install-UW7jMV/10-pacemaker-dev_2.0.1-1_amd64.deb

Yep, all -dev packages were merged at one point into pacemaker-dev.
Breaks+Replaces on old packages should do the trick here.

-- 
Valentin

Bug#923346: updates

[Thomas, Paul]

OK, we did find the bug in the macb driver, the main thread on netdev is here:

https://lore.kernel.org/netdev/02874ece860811409154e81da85fbb5892325...@orsmsx121.amr.corp.intel.com/

For future reference, the main issue is that the driver was doing the 
timestamping for all socks, so when a sock had NOT requested 
SOF_TIMESTAMPING_TX_HARDWARE it was getting woken up anyway because the 
timestamp is available in the error queue.

This bug can be closed, I don't know if I need to do anything else?

Thanks,

Paul

-- 
"This e-mail message and any attachments are confidential and may be 
privileged. 
If you are not the intended recipient please notify AMSC 

immediately by replying to this message or by sending a message to 
postmas...@amsc.com 
and destroy all copies of 
this message and any attachments. 
Thank you."

Bug#923346: This problem is not a ptp4l bug

[Geva, Erez]

It is more likely a specific driver in kernel issue

See mailing in the linuxptp dev mailing
https://sourceforge.net/p/linuxptp/mailman/linuxptp-devel/?viewmonth=201903&viewday=12

I recommend this bug report be removed.

Thanks
  Erez Geva

Bug#925463: pytest: Please provide a pytest binary for Python 3.x

[Joel Cross]

Source: pytest
Severity: normal

Dear Maintainer,

I noticed today that while the python3-pytest package works fine when invoked
as `python3 -m pytest`, it does not provide a binary, and the only binary
provided is as part of the `python-pytest` package which is built on Python 2.

For proper cross-version compatibility, I suggest defining a new 'pytest'
package which contains just the binary, and depends on either python-pytest or
python3-pytest. Alternatively, you could add a 'pytest3' binary to the existing
python3-pytest package.



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

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

Bug#925454: RM: tomcat8 -- ROM; Replaced by tomcat9

[Thorsten Glaser]

On Mon, 25 Mar 2019, Emmanuel Bourg wrote:

> Please remove the tomcat8 package from testing and unstable (not
> experimental). This package has been replaced by tomcat9 for Buster.

Please don’t, tomcat9 has no sysvinit script, and you did
not like any of my suggestions for it.

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

*

**!!! NEU !!!** Mit der **tarent Academy** bieten wir ab sofort auch Trainings
und Schulungen in den Bereichen Softwareentwicklung, Agiles Arbeiten und
Zukunftstechnologien an. Besuchen Sie uns
auf [www.tarent.de/academy](http://www.tarent.de/academy). Wir freuen uns auf
Ihren Kontakt.

*

Bug#925454: RM: tomcat8 -- ROM; Replaced by tomcat9

[Emmanuel Bourg]

Le 25/03/2019 à 14:22, Bastian Blank a écrit :

> Why not experimental?

I'd like to keep building up to date tomcat8 packages until Buster is
released with tomcat9.

Emmanuel Bourg

Bug#925454: RM: tomcat8 -- ROM; Replaced by tomcat9

[Bastian Blank]

On Mon, Mar 25, 2019 at 11:51:29AM +0100, Emmanuel Bourg wrote:
> Please remove the tomcat8 package from testing and unstable (not 
> experimental).
> This package has been replaced by tomcat9 for Buster.

Why not experimental?

Regards,
Bastian

-- 
The joys of love made her human and the agonies of love destroyed her.
-- Spock, "Requiem for Methuselah", stardate 5842.8

Bug#925464: new upstream release (1.3rc1)

[Antoine Beaupre]

Package: mumble
Version: 1.2.18-1+deb9u1
Severity: normal

Upstream has finally got their act together and made a release on the
1.3 branch. It's just an rc1, but maybe it would be better to ship
that with buster than the current git snapshot. That might need some
convincing with the release team, but I think it's worth the trouble.

See:

https://github.com/mumble-voip/mumble/issues/2865

A.

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

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

Versions of packages mumble depends on:
ii  libasound2 1.1.3-5
ii  libavahi-client3   0.6.32-2
ii  libavahi-common3   0.6.32-2
ii  libavahi-compat-libdnssd1  0.6.32-2
ii  libc6  2.24-11+deb9u4
ii  libg15daemon-client1   1.9.5.3-8.3+b1
ii  libgcc11:6.3.0-18+deb9u1
ii  libopus0   1.2~alpha2-1
ii  libprotobuf10  3.0.0-9
ii  libpulse0  10.0-1+deb9u1
ii  libqt4-dbus4:4.8.7+dfsg-11
ii  libqt4-network 4:4.8.7+dfsg-11
ii  libqt4-sql 4:4.8.7+dfsg-11
ii  libqt4-sql-sqlite  4:4.8.7+dfsg-11
ii  libqt4-svg 4:4.8.7+dfsg-11
ii  libqt4-xml 4:4.8.7+dfsg-11
ii  libqtcore4 4:4.8.7+dfsg-11
ii  libqtgui4  4:4.8.7+dfsg-11
ii  libsndfile11.0.27-3
ii  libspeechd20.8.6-4+deb9u1
ii  libspeex1  1.2~rc1.2-1+b2
ii  libspeexdsp1   1.2~rc1.2-1+b2
ii  libssl1.1  1.1.0j-1~deb9u1
ii  libstdc++6 6.3.0-18+deb9u1
ii  libx11-6   2:1.6.4-3+deb9u1
ii  libxi6 2:1.7.9-1
ii  lsb-release9.20161125

mumble recommends no packages.

Versions of packages mumble suggests:
pn  mumble-server  
ii  speech-dispatcher  0.8.6-4+deb9u1

-- no debconf information

Bug#924594: Build-depend on icedtea-netx instead of icedtea-netx-common

[tony mancill]

On Sun, Mar 24, 2019 at 12:29:51AM +0100, Markus Koschany wrote:
> On Thu, 14 Mar 2019 19:53:28 +0100 Matthias Klose  wrote:
> > Package: src;sweethome3d
> > Version: 6.1.2+dfsg-1
> > Severity: serious
> > Tags: sid buster
> > 
> > Build-depend on icedtea-netx instead of icedtea-netx-common (nbs).
> > 
> > Patch at
> > http://launchpadlibrarian.net/415155485/sweethome3d_6.1.2+dfsg-1_6.1.2+dfsg-1ubuntu1.diff.gz
> 
> Hi tony,
> 
> thank you for fixing the other companion packages of sweethome3d.
> Actually I wanted to downgrade the severity to normal because
> icedtea-web provides icedtea-netx-common now, so this shouldn't be
> release-critical anymore. I intended to fix it after the freeze. But I
> guess since the other sweethome3d packages are fixed now, I can upload a
> new revision of sweethome3d too to complete the work. Will do so after
> some hours of sleep.

Hi Markus,

My apologies for jumping the gun on those uploads and not coordinating
with you first.  I will confess that the recent upload of a new upstream
version of icedtea-web had me thinking that we might be aiming to have
that newer version in Buster and I didn't want that to necessarily
preclude the sweethome3d packages.  (It now seems likely that I was
confused and thus further confused the issue.  And I must have missed
the Provides of icedtea-netx-common.)

Thank you for updating sweethome3d.  At least now the set of packages is
in a consistent state.

Cheers,
tony


signature.asc
Description: PGP signature

Bug#925465: gerbera: New upstream release available (1.3.0)

[Christopher Martin]

Package: gerbera
Version: 1.1.0+dfsg-3
Severity: wishlist

Upstream has released version 1.3.0. Even if it's too late for buster,
having the new version available would be helpful.

Thanks,
Christopher Martin

Bug#923812: please don't spam the BTS

[Alexandre Viau]

Hello Jonatan,


You opened two bugs asking for syncthing to be updated.

Please don't spam the BTS uselessly.


Cheers,

-- 
Alexandre Viau
alexan...@alexandreviau.net

Bug#925454: RM: tomcat8 -- ROM; Replaced by tomcat9

[Emmanuel Bourg]

Hi Thorsten,

Le 25/03/2019 à 14:17, Thorsten Glaser a écrit :

> Please don’t, tomcat9 has no sysvinit script, and you did
> not like any of my suggestions for it.

I don't mind if tomcat8 is released with Buster, but I won't be able to
commit any time on the security fixes. Do you volunteer? The security
team might want to have a say too.

Emmanuel Bourg

Bug#925440: Are you sure?

[Gong S.]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

>This was done in 2010 already.
No, you did not. I created "/etc/mkshrc" and it is ignored by "mksh".
If I symlink "~/.mkshrc" to "/etc/mkshrc" it works, but if I removed the 
symlink the file is ignored again.
>...and ASCII is not enough to represent almost all of the languages I speak.
...and I cannot type anything beyond 0x7F easily on a standard US keyboard. In 
a place like this, please use English.
-
Please limit your reply to 7-bit ASCII.
I refuse to see your idiotic emoji in a TTY.
-BEGIN PGP SIGNATURE-
Version: ProtonMail
Comment: https://protonmail.com

wsBcBAEBCAAGBQJcmN55AAoJENi1YDlFXXQfzlIH/RzXsYcDSX35eLUr5ZWn
OLoOQ4UE4dC9lBXBdAkoQcRUgJMQ0Dp2EbysPtfhY+dtlR+yGd3SDXIH+boB
OO2pLXuzwtq+WLwqM/heJxOmpho7opONW1A7UNqd6szEGKHRT5AnRS/nlywG
tJYS/7ZHajbRy+kRdMWbZJCXE67skkcrpvnlxLnAh6PHBo/FBlkCrr1clDtp
MJju4Aj3SQkoqrLzmToitz+MNaP0d31ub8n67YDKBC1YDf7EbY5NuT/2wIwp
KclFKdpwqP/ySHfkhJnuyid6QFvxnMbksRdZVv1b+8B4IWCPyI0C/w05180p
eblpEvvdfgZim9tmswUm7kk=
=D7F6
-END PGP SIGNATURE-



publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc
Description: application/pgp-keys


publickey - pthfdr@protonmail.ch - 0xAB77ABA4.asc.sig
Description: PGP signature

Bug#925160: request for performance test in your environment

[Osamu Aoki]

Hi,

I think both of you see improvement.  (SSD and HDD)

package as installed disables im-config for wayland.

That's good but can you also tell us difference between 

IM_CONFIG_WAYLAND=disable

and 

IM_CONFIG_WAYLAND=enable

in /etc/default/im-config for YOSHINO-san's point. 

(You know what I mean, I hope)

Did you notice difference?  How much?

FYI:

If I can depend on dpkg-dev, I realize I can use be specific for
multiarch path using

$ dpkg-architecture -q DEB_HOST_MULTIARCH
x86_64-linux-gnu

Is these better way to get the primary multiarch path name?

$ pwd
/usr/lib
$ ls -1|wc -l
367
$ ls -1|grep -e "-" |wc -l
74
$ ls -1|grep -e "-.*-" |wc -l
18
$ ls -1|grep -e "x86_64-linux-gnu" |wc -l
1

So time difference should be:
  Original program run twice--> 734
  Current one has - and rn once -->  74
  If specify-->   1
There is more to improve ...

(I can't do it during the build since this is arch ALL package)

Regards,

Osamu

Bug#925082: postfix: "Chunk exceeds message size limit" when message_size_limit = 0

[James Bottomley]

On Tue, 19 Mar 2019 21:53:41 + Scott Kitterman  wrote:
> This is fixed in a new upstream release that I expect to package
> shortly.

Me too on being affected by this and waiting to the fixed version 3.4.4
being packaged.  Since postfix is actually rejecting email permanently,
shouldn't this be a grave bug?

James

Bug#925467: please make ant and ant-optional M-A: foreign

[Matthias Klose]

Package: src:ant
Version: 1.10.5-2

please make ant and ant-optional M-A: foreign. At least it's needed to
cross-build the openjdk packages.

Bug#921146: Bug#923711: squashfs-tools: Please apply frag_deflator_thread removal patch

[Alexander Couzens]

Hi lamby,

> Alas, I don't think I will be able to get to writing a patch/fix today
> as I don't fully understand the leak (or, actually, the original
> patch!) just yet.
> 
> Lynxis, do you have any quick pointers, however?

original, my patch had the problem, that it use the 
same stream (compressor context) as the main thread. This seems to be
ok, as long the compression is not lzo (I tested with lzma).

After your patch to fix lzo, the compressor will be initialized with a
new context on every fragment instead only once for all fragments.
Also important, all compressor_init's will leak, but since they are
only called once, it's not a big problem to leak some kbs.

I attached a patch to fix this to the bug #923711
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923711
It would be nice if you can test it.

Best,
lynxis

PS: If you like to write a small test script, I'm happy to add it to the
CI ;)


pgpdHlvFNaRuL.pgp
Description: OpenPGP digital signature

Bug#925468: apt: upgrading package as dependency pulls in different packages vs. doing so explicitly

[Andrew J. Buehler]

Package: apt
Version: 1.8.0
Severity: normal

Dear Maintainer,

I expect that when apt-get tries to install or upgrade a package, all else 
being equal (i.e., assuming there are not other packages involved which will 
break the obvious dependency resolution), it will pull in the same set of 
dependencies when that package is being installed as a dependency as it will do 
when that package is being explicitly specified by the user for install.

For the most part, my experience matches this expectation. However, at present, 
I am encountering a situation which does not.

When I attempt to upgrade openssh-client, it pulls in openssh-server and 
openssh-sftp-server as dependencies, and stops there. This is acceptable.

However, if I instead attempt to upgrade openssh-server, it pulls in all of 
libargon2-1, libcryptsetup12, libnss-systemd, libpam-systemd, libsystemd0, 
libsystemd0:i386, openssh-client, openssh-sftp-server, systemd, and 
systemd-sysv - which then results in removing consolekit, systemd-shim, and 
sysvinit-core.

(Worse, if I specify those three to-be-removed packages explicitly on the 
command line, it finds a dependency solution which does not remove any of them 
- so the chosen solution was unnecessarily drastic to begin with. That's a side 
issue, however, and is not the focus of this bug report.)

The dependency chain appears to arise from the facts that openssh-server 
Recommends: libpam-systemd, and Recommends are installed by default. From the 
fact that this chain does not arise when pulling in openssh-server as a 
dependency, I infer that this "install Recommends by default" policy is not 
applied when the package with the Recommends is being installed as a dependency.

This inconsistent dependency result is IMO undesirable. As the package being 
specified in the second case is one of the same packages selected as a 
dependency in the first case, the dependency solution chosen by the second case 
should be a *subset* of the packages chosen in the first case - not a superset, 
as is the case here. (Note that "the same set" is a valid subset.)

(I am not entirely enamored of the install-Recommends-by-default policy to 
begin with, but if it is going to exist, IMO it should be applied consistently; 
applying it to explicit installations but not to dependency installations seems 
almost designed to produce unexpected results.)

It would probably be at least equally appropriate to title this bug report 
"Recommends not installed by default for depended-on packages" or "Recommends 
installed by default for explicit installs, but not for dependency installs"; 
feel free to retitle as such if that seems preferable.


The commands I'm running, their output, and the version information for the 
packages involved are as follows.


aqualung:~# apt-get install openssh-client
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libpoclu-dev libpoclu1
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  openssh-server openssh-sftp-server
Suggested packages:
  keychain libpam-ssh monkeysphere ssh-askpass molly-guard rssh ufw
Recommended packages:
  default-logind | logind | libpam-systemd
The following packages will be upgraded:
  openssh-client openssh-server openssh-sftp-server
3 upgraded, 0 newly installed, 0 to remove and 1105 not upgraded.
Need to get 1,177 kB of archives.
After this operation, 28.7 kB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.


aqualung:~# apt-get install openssh-server
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages were automatically installed and are no longer required:
  cgmanager libcgmanager0 libck-connector0 libnih-dbus1 libnih1 libpoclu-dev 
libpoclu1
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  libargon2-1 libcryptsetup12 libnss-systemd libpam-systemd libsystemd0 
libsystemd0:i386 openssh-client openssh-sftp-server systemd systemd-sysv
Suggested packages:
  keychain libpam-ssh monkeysphere ssh-askpass molly-guard rssh ufw 
systemd-container policykit-1
The following packages will be REMOVED:
  consolekit systemd-shim sysvinit-core
The following NEW packages will be installed:
  libargon2-1 libcryptsetup12 libnss-systemd libpam-systemd systemd systemd-sysv
The following packages will be upgraded:
  libsystemd0 libsystemd0:i386 openssh-client openssh-server openssh-sftp-server
5 upgraded, 6 newly installed, 3 to remove and 1102 not upgraded.
Need to get 6,059 kB of archives.
After this operation, 14.6 MB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.


aqualung:~# apt-cache policy openssh-{client,server}
openssh-client:
  Installed: 1:7.9p1-4
  Candidate: 1:7.9p1-9
  Version table:
 1:7.9p1-9 500
500 http://ftp.us.debian.org/deb

Bug#924488: CUDA 10.1 is now available

[Graham Inggs]

Hi Andreas

On 2019/03/23 13:52, Andreas Beckmann wrote:

I've pushed a 10.1 branch to git and repack the upstream tarball now
differently. Most general changes were applied in 9.2/10.0 uploads...
Especially the new packages nsight-compute (since 10.0), nsight-systems
(since 10.1) will need some more testing.


Thanks for your work on this.

Are the upstream tarballs likely to change?  If I were to upload to 
Ubuntu proper and they did, it would get messy, unless you were prepared 
to add +ds1 or so to the tarball version.


I tested up to commit 17301b85 in PPA builds in Ubuntu and got the 
following failures:


amd64:

dpkg-shlibdeps: error: cannot find library libSM.so.6 needed by 
debian/nsight-systems/usr/lib/nsight-systems/Host-x86_64/libQt5XcbQpa.so.5 
(ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: 
'/usr/lib/nsight-systems/Host-x86_64')
dpkg-shlibdeps: error: cannot find library libICE.so.6 needed by 
debian/nsight-systems/usr/lib/nsight-systems/Host-x86_64/libQt5XcbQpa.so.5 
(ELF format: 'elf64-x86-64' abi: '0201003e'; RPATH: 
'/usr/lib/nsight-systems/Host-x86_64')



ppc64el:

# remove tracking images
find \
build/doc/html \
 \
build/extras/CUPTI/doc/html \
build/extras/Sanitizer/docs \
-name '*.html' -exec sed -r -i \
	-e '\,http://omniture.nvidia.com/b/ss/nvidiacudadocs/1/H.17--NS/0, { 
s,(),, }' \
	-e 's,()src(="http://w.sharethis.com/button/buttons.js"[^>]*>),,' \
	-e 's,()src(="//assets.adobedtm.com/b92787824f2e0e9b68dc2e993f9bd995339fe417/satelliteLib-7ba51e58dc61bcb0e9311aadd02a0108ab24cc6c.js"[^>]*>),,' \

{} +
find: ‘build/extras/CUPTI/doc/html’: No such file or directory
find: ‘build/extras/Sanitizer/docs’: No such file or directory


I was able to work around the amd64 failure with the following change:

--- a/debian/control
+++ b/debian/control
@@ -18,6 +18,9 @@
  libnss3-dev [!ppc64el],
  libpulse-dev [!ppc64el],
  chrpath [!ppc64el],
+# for nsight-systems
+ libsm6 [!ppc64el],
+ libice6 [!ppc64el],
 # for nvidia-openjdk-8-jre
  libasound2 [amd64],
  libgl1 [amd64],


What else is required for an upload to experimental?  My next step is to 
rebuild all reverse dependencies in my PPA.


Regards
Graham