Bug#856533: [Pkg-freeipa-devel] Bug#856533: freeipa-server: is_running() takes at most 2 arguments (3 given)

[Timo Aaltonen]

On 02.03.2017 08:01, Village Idiot wrote:
> Package: freeipa-server
> Version: 4.4.3-3
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation?
>   Created brand new VM from debian-8.7.1-amd64-netinst.iso > installed 
> only base system > updated sources.list to use Sid archive plus experimental 
> > used aptitude to update/upgrade > reboot > used aptitude to install 
> freeipa-server including dependancies > ran ipa-server-install
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>   Durring install config I approved configuring BIND > Directory Manager 
> password and IPA admin password were both set to 12345678 to avoid "special 
> characters" issue > other settings left as default
>* What was the outcome of this action?
>   Config NTP daemon [error] TypeError: is_running() takes at most 2 
> arguments (3 given)
> install terminates and sends me to the /var/log/ipaserver-install.log 
> for more information

This is already fixed in git. Note that server install will fail anyway
because libresteasy-java and tomcat8 updates broke dogtag. That won't
get fixed anytime soon I'm afraid.


-- 
t

Processed: notfound 856536 in 2.0.25-1+deb8u1, found 856536 in 2.0.25-1+deb8u2, found 856536 in 2.0.32-1

[Debian Bug Tracking System]

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

> notfound 856536 2.0.25-1+deb8u1
Bug #856536 [src:munin] munin: regression from DSA-3794-2: spams munin logs 
with unitialized warnings: [PERL WARNING] Use of uninitialized value $size_x in 
string eq at /usr/lib/munin/cgi/munin-cgi-graph line 453
No longer marked as found in versions munin/2.0.25-1+deb8u1.
> found 856536 2.0.25-1+deb8u2
Bug #856536 [src:munin] munin: regression from DSA-3794-2: spams munin logs 
with unitialized warnings: [PERL WARNING] Use of uninitialized value $size_x in 
string eq at /usr/lib/munin/cgi/munin-cgi-graph line 453
Marked as found in versions munin/2.0.25-1+deb8u2.
> found 856536 2.0.32-1
Bug #856536 [src:munin] munin: regression from DSA-3794-2: spams munin logs 
with unitialized warnings: [PERL WARNING] Use of uninitialized value $size_x in 
string eq at /usr/lib/munin/cgi/munin-cgi-graph line 453
Marked as found in versions munin/2.0.32-1.
> thanks
Stopping processing here.

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

Bug#856536: munin: regression from DSA-3794-2: spams munin logs with unitialized warnings: [PERL WARNING] Use of uninitialized value $size_x in string eq at /usr/lib/munin/cgi/munin-cgi-graph line 453

[Salvatore Bonaccorso]

Source: munin
Version: 2.0.25-1+deb8u1
Severity: serious
Tags: upstream

Only after releasing the DSA, I noticed that the update introduced
another regression, causing to spam the munin logs for
munin-cgi-graph.log with:

[...]
2017/03/02 06:53:56 [PERL WARNING] Use of uninitialized value $size_x in string 
eq at /usr/lib/munin/cgi/munin-cgi-graph line 453.
[...]

We possibly should release another regression update for
jessie-security, and have the fix included as well for stretch.

Apologies, I only noticed after the DSA release that the update caused
another problem, while less grave than the previous ones, spamming the
logs with warnings is probably unaceptable (thus the severity
serious).

Salvatore

Bug#856533: freeipa-server: is_running() takes at most 2 arguments (3 given)

[Village Idiot]

Package: freeipa-server
Version: 4.4.3-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
Created brand new VM from debian-8.7.1-amd64-netinst.iso > installed 
only base system > updated sources.list to use Sid archive plus experimental > 
used aptitude to update/upgrade > reboot > used aptitude to install 
freeipa-server including dependancies > ran ipa-server-install
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
Durring install config I approved configuring BIND > Directory Manager 
password and IPA admin password were both set to 12345678 to avoid "special 
characters" issue > other settings left as default
   * What was the outcome of this action?
Config NTP daemon [error] TypeError: is_running() takes at most 2 
arguments (3 given)
install terminates and sends me to the /var/log/ipaserver-install.log 
for more information
   * What outcome did you expect instead?

Personal note:
While I have been a Debian user for more than a decade I have never 
submitted a bug report.  If I'm not providing enough info or the right info 
please help me be more efficient for you.

*** End of the template - remove these template lines ***


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

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

Versions of packages freeipa-server depends on:
ii  389-ds-base  1.3.5.15-2
ii  acl  2.2.52-3+b1
ii  apache2  2.4.25-3
ii  certmonger   0.78.6-4
ii  custodia 0.1.0-6
ii  fonts-font-awesome   4.7.0~dfsg-2
ii  freeipa-admintools   4.4.3-3
ii  freeipa-client   4.4.3-3
ii  freeipa-common   4.4.3-3
ii  init-system-helpers  1.47
ii  krb5-admin-server1.15-1
ii  krb5-kdc 1.15-1
ii  krb5-kdc-ldap1.15-1
ii  krb5-otp 1.15-1
ii  krb5-pkinit  1.15-1
ii  ldap-utils   2.4.44+dfsg-3
ii  libapache2-mod-auth-gssapi   1.4.1-1+b1
ii  libapache2-mod-nss   1.0.14-1
ii  libapache2-mod-wsgi  4.5.11-1
ii  libc62.24-9
ii  libcomerr2   1.43.4-2
ii  libjs-dojo-core  1.11.0+dfsg-1
ii  libjs-jquery 3.1.1-2
ii  libk5crypto3 1.15-1
ii  libkrad0 1.15-1
ii  libkrb5-31.15-1
ii  libldap-2.4-22.4.44+dfsg-3
ii  libnspr4 2:4.13.1-1
ii  libnss3  2:3.29.1-1
ii  libnss3-tools2:3.29.1-1
ii  libsasl2-modules-gssapi-mit  2.1.27~101-g0780600+dfsg-2
ii  libssl1.11.1.0e-1
ii  libsss-nss-idmap01.15.0-3
ii  libtalloc2   2.1.8-1
ii  libtevent0   0.9.31-1
ii  libunistring00.9.6+really0.9.3-0.1
ii  libuuid1 2.29.1-1
ii  libverto10.2.4-2.1
ii  memcached1.4.33-1
ii  ntp  1:4.2.8p9+dfsg-2.1
ii  oddjob   0.34.3-4
ii  p11-kit  0.23.4-1
ii  pki-ca   10.3.5-6
ii  pki-kra  10.3.5-6
ii  python-dateutil  2.5.3-2
ii  python-gssapi1.2.0-1
ii  python-ipaserver 4.4.3-3
ii  python-ldap  2.4.28-0.1
ii  python-systemd   233-1
pn  python:any   
ii  samba-libs   2:4.5.4+dfsg-1
ii  slapi-nis0.56.1-1
ii  softhsm2 2.2.0-3
ii  systemd-sysv 232-18

Versions of packages freeipa-server recommends:
ii  freeipa-server-dns  4.4.3-3

freeipa-server suggests no packages.

-- no debconf information
2017-03-02T05:06:49Z DEBUG Logging to /var/log/ipaserver-install.log
2017-03-02T05:06:49Z DEBUG ipa-server-install was invoked with arguments [] and 
options: {'no_dns_sshfp': None, 'ignore_topology_disconnect': None, 'verbose': 
False, 'ip_addresses': None, 'domainlevel': None, 'mkhomedir': None, 
'no_pkinit': None, 'http_cert_files': None, 'no_ntp': None, 'subject': None, 
'no_forwarders': None, 'external_ca_type': None, 'ssh_trust_dns': None, 
'domain_name': None, 'idmax': None, 'http_cert_name': None, 
'dirsrv_cert_files': None, 'no_dnssec_validation': None, 
'ca_signing_algorithm': None, 'no_reverse': None, 'pkinit_cert_files': None, 
'unattended': False, 'auto_reverse': None, 'auto_forwarders': None, 
'no_host_dns': None, 'no_sshd': None, 'no_ui_redirect': None, 

Bug#856199: fixed in vbrfix 0.24+dfsg-1

[Rogério Brito]

Dear Adrian,

On Feb 26 2017, Adrian Bunk wrote:
> Source: vbrfix
> Source-Version: 0.24+dfsg-1

Thank you very much for taking care of vbrfix. I just forgot about this
package that I used to maintain and didn't point the Vcs-* fields to the
proper place (which are in collab-maint).

If you want to, I can improve (slightly, because my time is kinda limited
right now) the packaging (yes, even after I orphaned it).

Once again, thanks for taking care of the older packages in Debian.


Cheers,

-- 
Rogério Brito : rbrito@{ime.usp.br,gmail.com} : GPG key 4096R/BCFC
http://cynic.cc/blog/ : github.com/rbrito : profiles.google.com/rbrito
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br

Bug#856450: marked as done (texlive-lang-japanese: /usr/bin/kanji-config-updmap{,-sys} are not provided.)

[Debian Bug Tracking System]

Your message dated Thu, 02 Mar 2017 04:22:03 +
with message-id 
and subject line Bug#856450: fixed in texlive-lang 2016.20170123-4
has caused the Debian Bug report #856450,
regarding texlive-lang-japanese: /usr/bin/kanji-config-updmap{,-sys} are not 
provided.
to be marked as done.

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

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


-- 
856450: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856450
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: texlive-lang-japanese
Version: 2016.20170123-3
Severity: serious

Dear Norbert, 

Two scripts, /usr/bin/kanji-config-updmap{,-sys}, are not provided
because of "debian/scripts.lst" doesn't follow upstream renaming:
jfontmaps -> ptex-fontmaps.

As you know, these scripts are very important for Japanese TeX users.
Please upload fixed version, and consider send unblock request.

Tiny patch attached.

Best Wishes,
Youhei


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

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

Versions of packages texlive-lang-japanese depends on:
ii  fonts-ipaexfont-gothic  00301-3
ii  fonts-ipaexfont-mincho  00301-3
ii  fonts-ipafont-gothic00303-16
ii  fonts-ipafont-mincho00303-16
ii  ruby1:2.3.3
ii  tex-common  6.06
ii  texlive-base2016.20170123-4
ii  texlive-binaries2016.20160513.41080.dfsg-1
ii  texlive-lang-cjk2016.20170123-3

texlive-lang-japanese recommends no packages.

texlive-lang-japanese suggests no packages.

Versions of packages tex-common depends on:
ii  dpkg  1.18.22
ii  ucf   3.0036

Versions of packages tex-common suggests:
ii  debhelper  10.2.5

Versions of packages texlive-lang-japanese is related to:
ii  tex-common6.06
ii  texlive-binaries  2016.20160513.41080.dfsg-1

-- no debconf information
From 3183110d13d29dc24f0f20c5902fca2a1134b77a Mon Sep 17 00:00:00 2001
From: Youhei SASAKI 
Date: Wed, 1 Mar 2017 15:58:17 +0900
Subject: [PATCH] Follow upstream renaming: jfontmaps -> ptex-fontmaps

Signed-off-by: Youhei SASAKI 
---
 debian/scripts.lst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/debian/scripts.lst b/debian/scripts.lst
index 38f510b1..2c5963d7 100644
--- a/debian/scripts.lst
+++ b/debian/scripts.lst
@@ -63,9 +63,9 @@ fragmaster/fragmaster.pl
 getmap/getmapdl.lua
 glossaries/makeglossaries
 glossaries/makeglossaries-lite.lua
-jfontmaps/kanji-config-updmap-sys.sh
-jfontmaps/kanji-config-updmap.pl
-jfontmaps/kanji-fontmap-creator.pl
+ptex-fontmaps/kanji-config-updmap-sys.sh
+ptex-fontmaps/kanji-config-updmap.pl
+ptex-fontmaps/kanji-fontmap-creator.pl
 kotex-utils/jamo-normalize.pl
 kotex-utils/komkindex.pl
 kotex-utils/ttf2kotexfont.pl
-- 
2.11.0

--- End Message ---
--- Begin Message ---
Source: texlive-lang
Source-Version: 2016.20170123-4

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

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

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

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texlive-lang 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 02 Mar 2017 11:03:58 +0900
Source: texlive-lang
Binary: texlive-lang-african texlive-lang-arabic texlive-lang-cjk 
texlive-lang-korean texlive-lang-chinese texlive-lang-japanese 
texlive-lang-cyrillic texlive-lang-czechslovak texlive-lang-english 
texlive-lang-european texlive-lang-french texlive-lang-german 
texlive-lang-greek texlive-lang-indic texlive-lang-italian texlive-lang-other 
texlive-lang-polish texlive-lang-portuguese texlive-lang-spanish 
texlive-lang-all
Architecture: source all
Version: 2016.20170123-4
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Maintainers 
Changed-By: Norbert Preining 

Bug#849777: Pending fixes for bugs in the shutter package

[pkg-perl-maintainers]

tag 849777 + pending
thanks

Some bugs in the shutter package are closed in revision
fb12f0fa979002ad8a3616d082332c7b25d20218 in branch 'master' by
Dominique Dumont

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-perl/packages/shutter.git/commit/?id=fb12f0f

Commit message:

add patch to fix CVE-2016-10081 (Closes: #849777)

Processed: Pending fixes for bugs in the shutter package

[Debian Bug Tracking System]

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

> tag 849777 + pending
Bug #849777 {Done: Dominique Dumont } [src:shutter] shutter: 
CVE-2016-10081: Insecure use of perl exec()
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: severity of 854792 is normal

[Debian Bug Tracking System]

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

> severity 854792 normal
Bug #854792 [accountsservice] fails when there are two users with the same UID
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.

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

Bug#856526: sauce: fails to install: cdb.site-annoy (no existing data) couldn't load file "chiark_tcl_cdb-1.so"

[Andreas Beckmann]

Package: sauce
Version: 0.9.0+nmu3
Severity: serious
Tags: sid stretch
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Setting up sauce (0.9.0+nmu3) ...
  Checking for SAUCE databases in /var/lib/sauce ...
   cdb.site-annoy (no existing data) couldn't load file "chiark_tcl_cdb-1.so": 
chiark_tcl_cdb-1.so: cannot open shared object file: No such file or directory

  while executing

  "load chiark_tcl_cdb-1.so"

  (file "/usr/share/sauce/convertdb" line 22)

  dpkg: error processing package sauce (--configure):
   subprocess installed post-installation script returned error exit status 1


This was observed on i386, I couldn't reproduce it on amd64.


cheers,

Andreas


sauce_0.9.0+nmu3.log.gz
Description: application/gzip

Bug#856525: pkgconf: fails to install: Can't locate Dpkg/Arch.pm in @INC

[Andreas Beckmann]

Package: pkgconf
Version: 0.9.12-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package pkgconf.
  (Reading database ... 
(Reading database ... 4406 files and directories currently installed.)
  Preparing to unpack .../pkgconf_0.9.12-4_amd64.deb ...
  Adding 'diversion of /usr/bin/pkg-config to /usr/bin/pkg-config.real by 
pkgconf'
  Adding 'diversion of /usr/share/aclocal/pkg.m4 to 
/usr/share/aclocal/pkg.real.m4 by pkgconf'
  Adding 'diversion of /usr/share/man/man1/pkg-config.1.gz to 
/usr/share/man/man1/pkg-config.real.1.gz by pkgconf'
  Adding 'diversion of /usr/share/pkg-config-crosswrapper to 
/usr/share/pkg-config-crosswrapper.real by pkgconf'
  Unpacking pkgconf (0.9.12-4) ...
  Setting up pkgconf (0.9.12-4) ...
  Can't locate Dpkg/Arch.pm in @INC (you may need to install the Dpkg::Arch 
module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 
/usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
/usr/share/pkgconf-dpkghook line 14.
  BEGIN failed--compilation aborted at /usr/share/pkgconf-dpkghook line 14.
  dpkg: error processing package pkgconf (--configure):
   subprocess installed post-installation script returned error exit status 2
  Errors were encountered while processing:
   pkgconf


cheers,

Andreas


pkgconf_0.9.12-4.log.gz
Description: application/gzip

Bug#856416: grub-efi-amd64: Updating grub-efi-amd64:amd64 to 2.02~beta3-5 is aborted with half-installed package and reboot

[John Paul Adrian Glaubitz]

Hi Reiner!

On 03/01/2017 07:46 PM, Reiner Nix wrote:
>> This looks more like a local configuration issue at first sight rather than
>> a bug in the grub2 package. Did you try to reproduce this issue on a freshly
>> installed system?
> Sorry, I did not try to reproduce this bug on another system.

That would be important though in this case.

>> I'm also not sure I understand how the configure process was interrupted? 
>> Did it
>> just abort on its own or did you hit "Ctrl+C" or did your machine crash?
>>
>> I'm tagging this "moreinfo" because it's currently not obvious how and when
>> the configure process for grub2 was interrupted.
> 
> While running apt-get upgrade, and installing the package, the system crashed.

The crash could be completely unrelated to grub2 and possibly an issue with
your hardware. And if your machine crashes while dpkg is configuring packages,
it is virtually inevitable not to end up with half-broken packages.

> Before it did not display any other message than the usual apt-get / dpkg 
> message to install X86-64-efi
> and in the next second it rebooted automatically not caused by any user 
> activity or job.
> Before the reboot it did not execute the standard shutdown jobs.
> The reboot was just as if the system started with power on.

Could be an issue with your power supply maybe.

> Also there was no reasonable additional load, just my desktop environment 
> (KDE) and email program were running idle 
> indeed at the first time I was not present at the desk. When coming back I 
> noticed that the system displayed the login screen while I did not logout.
> 
> Some time later I tried to continue the update using 'dpkg --configure -a'.
> So I discovered that the update could not be completed but run into reboot.
> 
> This was reproducible unless on the next day the configuration could be 
> completed.

Reproducible in what way? Did the system crash-reboot once more when you tried
to run "dpkg --configure -a"?

> Hope this clarifies the situation a bit. 
> Give me a note when I could provide any other details like log files etc.

I'm currently a bit reluctant to blame grub2 here. This should really be
tested with a fresh installation to try to reproduce it. It's unlikely
to be a bug if we cannot reproduce it.

> Please find below an extract from the dpkg.log showing the lines regarding 
> grub-efi-amd64.

The log just indicates the fallout from the crash and is something to be
expected. The actual question is why your machine crashed while dpkg
was configuring packages and if it's actually reproducible.

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#850216: mysql-server-5.6: Listens on * by default after installation (related to use of alternatives)

[Robie Basak]

Hi Otto,

On Thu, Mar 02, 2017 at 01:04:16AM +0200, Otto Kekäläinen wrote:
> Sorry for the late reply. I think that the urgent security slip was
> already fixed by updating mariadb-10.1 to have the correct conflicts.

I believe this is incorrect. The only commit addressing this is
https://anonscm.debian.org/git/pkg-mysql/mariadb-10.1.git/commit/?id=75fa84af6bdf84ff95bd0cabb2a8966330d77154,
right? That drops a Depends line only. It'll stop users hitting it by
default, which they were on upgrade from jessie I think since
default-mysql-server became MariaDB. However, if users do install
mariadb-common while mysql-server-5.7 (or 5.6) is still installed, I
believe the security issue will still happen.

> from happening again, but then again we already have quite a lot of
> virtual and metapackages, and this feels a bit of over-engineering and
> I am afraid that while solving the issue it also adds to the stuff we
> need to maintain and document etc. Due to backwards compatiblity we
> might have to maintain in parallel anyway the direct conflicts plus
> the usage of this new metapackage.

As above, I don't think we have a direct conflicts right now. If we did
have one, this matter would be less urgent.

Another approach might be to do it entirely in code in
src:mysql-defaults. Since we have a wrapper that both MySQL and MariaDB
packaging use, we might be able to do something in there. However, I'm
not sure what we'd do if mysql-server-5.7 and mariadb-common both want
the symlink, since whatever we choose one of the two variants will
somehow be broken.

> Please allow for some more time for me to think about this before
> introducing new metapackages.

Sure. Unless I'm mistaken though, can we add the mariadb-common
Conflicts: mysql-server-5.6, mysql-server-5.7 now?

> > This presumably can't go in during the stretch freeze, so is it time to
> > branch off in git for stretch across mysql-defaults, mysql-5.7 (maybe
> > not needed as it's not in stretch) and mariadb-10.1 as needed, so we can
> > start committing changes for post-stretch?
> 
> Personally I'd like to focus my time right now on 'stand-by' for
> potential issues that might still pop up during the freeze. I didn't
> find a nice overview of how many RC bugs there still are for Stretch
> or such (mostly browsing https://release.debian.org/), but I assume
> the release is near and then we can for sure branch off maintenance
> branches.

OK, but I think the Conflicts should go into stretch at least.

Robie


signature.asc
Description: PGP signature

Bug#855935: Bug#850216: mysql-server-5.6: Listens on * by default after installation (related to use of alternatives)

[Otto Kekäläinen]

Hello!

2017-02-23 16:27 GMT+02:00 Robie Basak :
> The rule would be: any package that arranges a /etc/mysql/my.cnf
> symlink, usually via /usr/share/mysql-common/configure-symlinks, MUST
> Provide and Conflict mysql-my-cnf, with the exception of mysql-common.

Sorry for the late reply. I think that the urgent security slip was
already fixed by updating mariadb-10.1 to have the correct conflicts.

I can see the point in introducing a new metapackage to prevent it
from happening again, but then again we already have quite a lot of
virtual and metapackages, and this feels a bit of over-engineering and
I am afraid that while solving the issue it also adds to the stuff we
need to maintain and document etc. Due to backwards compatiblity we
might have to maintain in parallel anyway the direct conflicts plus
the usage of this new metapackage.

Please allow for some more time for me to think about this before
introducing new metapackages.

> This presumably can't go in during the stretch freeze, so is it time to
> branch off in git for stretch across mysql-defaults, mysql-5.7 (maybe
> not needed as it's not in stretch) and mariadb-10.1 as needed, so we can
> start committing changes for post-stretch?

Personally I'd like to focus my time right now on 'stand-by' for
potential issues that might still pop up during the freeze. I didn't
find a nice overview of how many RC bugs there still are for Stretch
or such (mostly browsing https://release.debian.org/), but I assume
the release is near and then we can for sure branch off maintenance
branches.

Bug#856521: libwala-java-doc: uninstallable in sid: unsatisfiable Depends: default-java-doc

[Andreas Beckmann]

Package: libwala-java-doc
Version: 1.3.9-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is not
installable in sid:

# apt-get install libwala-java-doc
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libwala-java-doc : Depends: default-java-doc but it is not installable
E: Unable to correct problems, you have held broken packages.

# apt-get install default-java-doc
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Package default-java-doc is not available, but is referred to by another 
package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'default-java-doc' has no installation candidate


Cheers,

Andreas

Bug#851987: rt-extension-spawnlinkedticketinqueue: Obsolete with RT 4.4

[Andreas Beckmann]

On Mon, 23 Jan 2017 22:32:44 +0900 Satoru KURASHIKI 
wrote:
> Will RT4.4 be in stretch?

Yes, that migrated to testing.

> After testing migration, I will file RM request.

Please go ahead.


Andreas

Bug#856519: libgeda-dev: uninstallable after binNMU: Depends: libgeda-common (= 1:1.8.2-5+b1) but 1:1.8.2-5 is to be installed

[Andreas Beckmann]

Package: libgeda-dev
Version: 1:1.8.2-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

# apt-get install libgeda-dev
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libgeda-dev : Depends: libgeda-common (= 1:1.8.2-5+b1) but 1:1.8.2-5 is to be 
installed
E: Unable to correct problems, you have held broken packages.


libgeda-common is an arch:all package, but there seems to be a
  Depends: libgeda-common (= ${binary:Version})
somewhere, which should rather be a
  Depends: libgeda-common (= ${source:Version})


Cheers,

Andreas

Processed: Add the fixed version

[Debian Bug Tracking System]

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

> fixed 856350 3.0.2+dfsg-3
Bug #856350 {Done: Olly Betts } [wxwidgets3.0] wx3.0-headers 
shouldn't require C++11 in stretch
There is no source info for the package 'wxwidgets3.0' at version 
'3.0.2+dfsg-3' with architecture ''
Unable to make a source version for version '3.0.2+dfsg-3'
Marked as fixed in versions 3.0.2+dfsg-3.
> thanks
Stopping processing here.

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

Bug#852258: rt-authen-externalauth: FTBFS: Your installed version of RT (4.4.1-2) is too new

[Tom Jampen]

On 01.03.2017 21:20, Andreas Beckmann wrote:
> On Wed, 25 Jan 2017 07:51:04 +0100 Tom Jampen  wrote:
>> request-tracker as of version 4.4 includes rt-authen-externalauth's
>> functionality. So let's see whether rt 4.4 makes it into stretch.
> 
> That made it into stretch, so rt-authen-externalauth can be removed from
> unstable?

I'm sorry, I didn't realized it had only been removed from testing and
not from unstable. You are right, it should be removed.

Regards
Tom

Processed (with 1 error): Swap cloned bugs around

[Debian Bug Tracking System]

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

> retitle 856350 wx3.0-headers shouldn't require C++11 in stretch
Bug #856350 {Done: Olly Betts } [src:qutemol] qutemol must be 
made C++11 compatible
Changed Bug title to 'wx3.0-headers shouldn't require C++11 in stretch' from 
'qutemol must be made C++11 compatible'.
> severity 856350 serious
Bug #856350 {Done: Olly Betts } [src:qutemol] wx3.0-headers 
shouldn't require C++11 in stretch
Severity set to 'serious' from 'important'
> tags 856350 + patch
Bug #856350 {Done: Olly Betts } [src:qutemol] wx3.0-headers 
shouldn't require C++11 in stretch
Added tag(s) patch.
> reassign 856350 wxwidgets3.0 3.0.2+dfsg-2
Bug #856350 {Done: Olly Betts } [src:qutemol] wx3.0-headers 
shouldn't require C++11 in stretch
Bug reassigned from package 'src:qutemol' to 'wxwidgets3.0'.
No longer marked as found in versions qutemol/0.4.1~cvs2008-6.
No longer marked as fixed in versions wxwidgets3.0/3.0.2+dfsg-3.
Bug #856350 {Done: Olly Betts } [wxwidgets3.0] wx3.0-headers 
shouldn't require C++11 in stretch
There is no source info for the package 'wxwidgets3.0' at version 
'3.0.2+dfsg-2' with architecture ''
Unable to make a source version for version '3.0.2+dfsg-2'
Marked as found in versions 3.0.2+dfsg-2.
> fixed 856350 wxwidgets3.0 3.0.2+dfsg-3
Unknown command or malformed arguments to command.
> affects 856350 src:qutemol
Bug #856350 {Done: Olly Betts } [wxwidgets3.0] wx3.0-headers 
shouldn't require C++11 in stretch
Added indication that 856350 affects src:qutemol
> retitle 856406 qutemol must be made C++11 compatible
Bug #856406 [wx3.0-headers] wx3.0-headers shouldn't require C++11 in stretch
Changed Bug title to 'qutemol must be made C++11 compatible' from 
'wx3.0-headers shouldn't require C++11 in stretch'.
> severity 856406 important
Bug #856406 [wx3.0-headers] qutemol must be made C++11 compatible
Severity set to 'important' from 'serious'
> tags 856406 - patch
Bug #856406 [wx3.0-headers] qutemol must be made C++11 compatible
Removed tag(s) patch.
> reassign 856406 qutemol 0.4.1~cvs2008-6
Bug #856406 [wx3.0-headers] qutemol must be made C++11 compatible
Bug reassigned from package 'wx3.0-headers' to 'qutemol'.
No longer marked as found in versions wxwidgets3.0/3.0.2+dfsg-2.
Ignoring request to alter fixed versions of bug #856406 to the same values 
previously set
Bug #856406 [qutemol] qutemol must be made C++11 compatible
Marked as found in versions qutemol/0.4.1~cvs2008-6.
> affects 856406 - src:qutemol
Bug #856406 [qutemol] qutemol must be made C++11 compatible
Removed indication that 856406 affects src:qutemol
> thanks
Stopping processing here.

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

Bug#856455: marked as done (munin: Zooming doesn't work)

[Debian Bug Tracking System]

Your message dated Wed, 01 Mar 2017 21:48:52 +
with message-id 
and subject line Bug#856455: fixed in munin 2.0.32-1
has caused the Debian Bug report #856455,
regarding munin: Zooming doesn't work
to be marked as done.

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

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


-- 
856455: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856455
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: munin
Version: 2.0.31-1
Severity: important

Dear Maintainer,

I don't know since when but zooming in graph doesn't work.

Apparently the guilty in an empty value for --upper-limit

I see in /var/log/munin/munin-cgi-graph.log

2017/03/01 09:16:21 [WARNING] Could not draw graph 
"/var/lib/munin/cgi-tmp/munin-cgi-graph/marillat.net/karl.marillat.net/diskstats_iops/mmcblk0-pinpoint=1485504486,1488355686.png?_limit=_limit=_x=800_y=400":
 
/var/lib/munin/cgi-tmp/munin-cgi-graph/marillat.net/karl.marillat.net/diskstats_iops/mmcblk0-pinpoint=1485504486,1488355686.png?_limit=_limit=_x=800_y=400
2017/03/01 09:20:23 [RRD ERROR] Unable to graph 
/var/lib/munin/cgi-tmp/munin-cgi-graph/marillat.net/karl.marillat.net/diskstats_iops/mmcblk0-pinpoint=1488247686,1488355686.png?_limit=_limit=_x=800_y=400
 : option -u - Cannot convert '' to float
2017/03/01 09:20:23 [RRD ERROR] rrdtool 'graph' 
'/var/lib/munin/cgi-tmp/munin-cgi-graph/marillat.net/karl.marillat.net/diskstats_iops/mmcblk0-pinpoint=1488247686,1488355686.png?_limit=_limit=_x=800_y=400'
 \
'--title' \
'IOs for /dev/mmcblk0 - from Tue Feb 28 03:08:06 2017 to Wed Mar  1 
09:08:06 2017' \
'--start' \
'1488247686' \
'--end' \
'1488355686' \
'--base' \
'1000' \
'--vertical-label' \
'Units read (-) / write (+)' \
'--slope-mode' \
'--height' \
'400' \
'--width' \
'800' \
'--rigid' \
'--imgformat' \
'PNG' \
'--font' \
'DEFAULT:0:DejaVuSans,DejaVu Sans,DejaVu LGC Sans,Bitstream Vera Sans' \
'--font' \
'LEGEND:7:DejaVuSansMono,DejaVu Sans Mono,DejaVu LGC Sans 
Mono,Bitstream Vera Sans Mono,monospace' \
'--color' \
'BACK#F0F0F0' \
'--color' \
'FRAME#F0F0F0' \
'--color' \
'CANVAS#FF' \
'--color' \
'FONT#66' \
'--color' \
'AXIS#CFD6F8' \
'--color' \
'ARROW#CFD6F8' \
'--border' \
'0' \
'-W' \
'Munin 2.0.31-1' \

'DEF:aavgwrrqsz=/var/lib/munin/marillat.net/karl.marillat.net-diskstats_iops-mmcblk0-avgwrrqsz-g.rrd:42:MAX'
 \

'DEF:iavgwrrqsz=/var/lib/munin/marillat.net/karl.marillat.net-diskstats_iops-mmcblk0-avgwrrqsz-g.rrd:42:MIN'
 \

'DEF:gavgwrrqsz=/var/lib/munin/marillat.net/karl.marillat.net-diskstats_iops-mmcblk0-avgwrrqsz-g.rrd:42:AVERAGE'
 \

'DEF:aavgrdrqsz=/var/lib/munin/marillat.net/karl.marillat.net-diskstats_iops-mmcblk0-avgrdrqsz-g.rrd:42:MAX'
 \

'DEF:iavgrdrqsz=/var/lib/munin/marillat.net/karl.marillat.net-diskstats_iops-mmcblk0-avgrdrqsz-g.rrd:42:MIN'
 \

'DEF:gavgrdrqsz=/var/lib/munin/marillat.net/karl.marillat.net-diskstats_iops-mmcblk0-avgrdrqsz-g.rrd:42:AVERAGE'
 \

'DEF:awrio=/var/lib/munin/marillat.net/karl.marillat.net-diskstats_iops-mmcblk0-wrio-g.rrd:42:MAX'
 \

'DEF:iwrio=/var/lib/munin/marillat.net/karl.marillat.net-diskstats_iops-mmcblk0-wrio-g.rrd:42:MIN'
 \

'DEF:gwrio=/var/lib/munin/marillat.net/karl.marillat.net-diskstats_iops-mmcblk0-wrio-g.rrd:42:AVERAGE'
 \

'DEF:ardio=/var/lib/munin/marillat.net/karl.marillat.net-diskstats_iops-mmcblk0-rdio-g.rrd:42:MAX'
 \

'DEF:irdio=/var/lib/munin/marillat.net/karl.marillat.net-diskstats_iops-mmcblk0-rdio-g.rrd:42:MIN'
 \

'DEF:grdio=/var/lib/munin/marillat.net/karl.marillat.net-diskstats_iops-mmcblk0-rdio-g.rrd:42:AVERAGE'
 \
'CDEF:crdio=grdio' \
'CDEF:cwrio=gwrio' \
'COMMENT: ' \
'COMMENT:Cur (-/+)' \
'COMMENT:Min (-/+)' \
'COMMENT:Avg (-/+)' \
'COMMENT:Max (-/+) \j' \
'LINE1:gwrio#00CC00:IO/sec' \
'GPRINT:crdio:LAST:%6.2lf%s/\g' \
'GPRINT:cwrio:LAST:%6.2lf%s' \
'GPRINT:irdio:MIN:%6.2lf%s/\g' \
'GPRINT:iwrio:MIN:%6.2lf%s' \
'GPRINT:grdio:AVERAGE:%6.2lf%s/\g' \
'GPRINT:gwrio:AVERAGE:%6.2lf%s' \
'GPRINT:ardio:MAX:%6.2lf%s/\g' \
'GPRINT:awrio:MAX:%6.2lf%s\j' \
'CDEF:cavgrdrqsz=gavgrdrqsz' \
'CDEF:cavgwrrqsz=gavgwrrqsz' \
 

Bug#749272: varnish doesn't source /etc/default/varnish when started with systemd

[Stig Sandbeck Mathisen]

Stig Sandbeck Mathisen  writes:

> Michael Stapelberg  writes:
>
>> Yet another alternative might be (and it pains me to say that, but
>> maybe it’s required to not break people’s setups) to have the service
>> file start a wrapper shell script which evaluates
>> /etc/default/varnish before starting varnish.
>
> That could actually be done when upgrading the package from whatever
> is in stable currently.
>
> For instance: If upgrading from 4.0.2-1, add a
> /etc/systemd/system/varnish.service.d/upgrade.conf with such a shell
> wrapper for people upgrading from the version in current stable.

Hm, after bootstrapping a stable debian installation, it looks like the
varnish systemd unit on stable didn't use an environment file at all.

It did, however, have ExecReload= set, using the reload-vcl script which
I'm not very content with.

Therefore, I think this issue can be resolved with just removing
"ExecReload=/usr/share/varnish/reload-vcl" from the systemd unit again,
and not have a "reload" action at all.

This has also been discussed previously at
https://github.com/varnishcache/pkg-varnish-cache/issues/30 for the
upstream packaging.

-- 
Stig Sandbeck Mathisen
https://fnord.no/

Bug#852258: rt-authen-externalauth: FTBFS: Your installed version of RT (4.4.1-2) is too new

[Andreas Beckmann]

On Wed, 25 Jan 2017 07:51:04 +0100 Tom Jampen  wrote:
> request-tracker as of version 4.4 includes rt-authen-externalauth's
> functionality. So let's see whether rt 4.4 makes it into stretch.

That made it into stretch, so rt-authen-externalauth can be removed from
unstable?

Andreas

Bug#749272: varnish doesn't source /etc/default/varnish when started with systemd

[Michael Stapelberg]

That sounds like a good idea!

On Wed, Mar 1, 2017 at 9:04 PM, Stig Sandbeck Mathisen 
wrote:

> Michael Stapelberg  writes:
>
> > Yet another alternative might be (and it pains me to say that, but
> > maybe it’s required to not break people’s setups) to have the service
> > file start a wrapper shell script which evaluates /etc/default/varnish
> > before starting varnish.
>
> That could actually be done when upgrading the package from whatever is
> in stable currently.
>
> For instance: If upgrading from 4.0.2-1, add a
> /etc/systemd/system/varnish.service.d/upgrade.conf with such a shell
> wrapper for people upgrading from the version in current stable.
>
> Oh, and "ick!", but thanks. :)
>
> I'd really like to avoid keeping /etc/default/* around for new installs.
>
> --
> Stig Sandbeck Mathisen
> https://fnord.no/
>



-- 
Best regards,
Michael

Processed: tagging 856455

[Debian Bug Tracking System]

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

> tags 856455 + fixed-upstream
Bug #856455 [munin] munin: Zooming doesn't work
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#749272: varnish doesn't source /etc/default/varnish when started with systemd

[Stig Sandbeck Mathisen]

Michael Stapelberg  writes:

> Yet another alternative might be (and it pains me to say that, but
> maybe it’s required to not break people’s setups) to have the service
> file start a wrapper shell script which evaluates /etc/default/varnish
> before starting varnish.

That could actually be done when upgrading the package from whatever is
in stable currently.

For instance: If upgrading from 4.0.2-1, add a
/etc/systemd/system/varnish.service.d/upgrade.conf with such a shell
wrapper for people upgrading from the version in current stable.

Oh, and "ick!", but thanks. :)

I'd really like to avoid keeping /etc/default/* around for new installs.

-- 
Stig Sandbeck Mathisen
https://fnord.no/

Processed: tagging 856455

[Debian Bug Tracking System]

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

> tags 856455 + pending
Bug #856455 [munin] munin: Zooming doesn't work
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 856455

[Debian Bug Tracking System]

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

> tags 856455 + patch
Bug #856455 [munin] munin: Zooming doesn't work
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: severity of 856455 is serious

[Debian Bug Tracking System]

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

> # functional regression unsuitable for stretch
> severity 856455 serious
Bug #856455 [munin] munin: Zooming doesn't work
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Processed: severity of 856485 is important

[Debian Bug Tracking System]

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

> severity 856485 important
Bug #856485 [xpra] xpra: terminating xpra server destroys current X session
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#856187: marked as done (entropybroker 2.8 : 100% cpu load in master/slave setup)

[Debian Bug Tracking System]

Your message dated Wed, 01 Mar 2017 19:48:39 +
with message-id 
and subject line Bug#856187: fixed in entropybroker 2.8-3
has caused the Debian Bug report #856187,
regarding entropybroker 2.8 : 100% cpu load in master/slave setup
to be marked as done.

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

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


-- 
856187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: entropybroker
Version: 2.8-2
Severity: grave
Tags: upstream
Justification: renders package unusable

Dear Maintainer,

upstream fixed an issue (https://github.com/flok99/entropybroker/issues/5) that 
may lead the system to a 100% CPU load.
I will try to package this new version (2.9) as it contains this fix and your 
patches for debian.

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

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

Versions of packages entropybroker depends on:
ii  init-system-helpers  1.47
ii  libasound2   1.1.3-5
ii  libc62.24-9
ii  libcrypto++6 5.6.4-6
ii  libftdi1 0.20-4
ii  libgcc1  1:6.3.0-6
ii  libgd3   2.2.4-2
ii  libpcsclite1 1.8.20-1
ii  libpng16-16  1.6.28-1
ii  libstdc++6   6.3.0-6
ii  libusb-1.0-0 2:1.0.21-1
ii  zlib1g   1:1.2.8.dfsg-5

entropybroker recommends no packages.

entropybroker suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: entropybroker
Source-Version: 2.8-3

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

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

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

Debian distribution maintenance software
pp.
Thorsten Alteholz  (supplier of updated entropybroker 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 01 Mar 2017 19:35:00 +0100
Source: entropybroker
Binary: entropybroker
Architecture: source amd64
Version: 2.8-3
Distribution: sid
Urgency: medium
Maintainer: Thorsten Alteholz 
Changed-By: Thorsten Alteholz 
Description:
 entropybroker - infrastructure for distributing random numbers (entropy data)
Closes: 856187
Changes:
 entropybroker (2.8-3) unstable; urgency=medium
 .
   * fix for correct handling of ppoll (Closes: #856187)
Checksums-Sha1:
 3c85ee8ef5359240e893914b5e0b51b21bc00153 2061 entropybroker_2.8-3.dsc
 b977e1523c10f68b37c000c5eee3a3ddd9c3c6bb 150959 entropybroker_2.8.orig.tar.gz
 0ae8eaf6d5c878b62935a129a7f278ca7d2d68c2 18880 
entropybroker_2.8-3.debian.tar.xz
 795fe351e8610355ca9e8a8135742a100f9d70ec 15467686 
entropybroker-dbgsym_2.8-3_amd64.deb
 4d5399deea78690e5130fe216aebf7dc3fbf5cb9 7003 
entropybroker_2.8-3_amd64.buildinfo
 0d289e4ead8738b89ce3c84d439ef4f3cdf91b24 618000 entropybroker_2.8-3_amd64.deb
Checksums-Sha256:
 798dd499088e60653719071d4315a2c5df68910ff5bf851ef5c1953e40c3379b 2061 
entropybroker_2.8-3.dsc
 95b5dc87bb619ead54061937c256493592def16839d7131feed8b3b78dbe2579 150959 
entropybroker_2.8.orig.tar.gz
 223dae41eae34d5575fd6e931ee9c0cd3b7f8d94c590f492d16cdaf2915068a4 18880 
entropybroker_2.8-3.debian.tar.xz
 d5c6fbe933fe804ec095b75ccd4e67da093aaf47855da6314132ad9cac68f4f4 15467686 
entropybroker-dbgsym_2.8-3_amd64.deb
 8547e75ab30216c121a4370ef494abf0a5d3d97622c68ba73523f869a99de942 7003 
entropybroker_2.8-3_amd64.buildinfo
 e256f8bcee4af6e53ccfa190592da0ae4db7ee7ff5a2293c9ca81e396dd0a431 618000 
entropybroker_2.8-3_amd64.deb
Files:
 99d812df4e2ca31447163385702b0ba5 2061 utils optional entropybroker_2.8-3.dsc
 1f9d1d05e32a514b99ea4c8b92c9d6c9 150959 utils optional 
entropybroker_2.8.orig.tar.gz
 8afa4c635bf0e4ea714b13a575f9d805 18880 utils optional 
entropybroker_2.8-3.debian.tar.xz
 c57a2a36212e1cc5823d4437036c18c3 15467686 debug extra 
entropybroker-dbgsym_2.8-3_amd64.deb
 c1ca6a4dd2ed7c0e60587b9835acec09 

Bug#856187: (no subject)

[Thorsten Alteholz]

Hi Fabrice,

On Mon, 27 Feb 2017, Fabrice Dagorn wrote:

here is a patch for your 2.8-2 package fixing this bug.
Sorry for #856198, I thought it would help.


thanks for the patch, but I am afraid you forgot the fix in utils.cpp, 
didn't you?


  Thorsten

Bug#856269: ruby-zip: FTBFS on stable

[Salvatore Bonaccorso]

Hi Antonio,

On Tue, Feb 28, 2017 at 08:21:23AM -0300, Antonio Terceiro wrote:
> On Tue, Feb 28, 2017 at 08:08:21AM +0100, Salvatore Bonaccorso wrote:
> > Control: tags 856269 + pending
> > 
> > Dear maintainer,
> > 
> > I've prepared an NMU for ruby-zip (versioned as 1.2.0-1.1) and
> > uploaded it to DELAYED/5. Please feel free to tell me if I
> > should delay it longer.
> 
> thanks - I have just imported the diff to the git repository
> 
> are you also doing a stable update?

Does the build failure as in the attached build log rings some bells
on your end?

Regards,
Salvatore


ruby-zip_1.1.6-1+deb8u1_amd64.build.gz
Description: application/gzip

Bug#855925: marked as done (sugar-irc-activity: FTBFS: unsatisfiable build-dependencies: python-sugar-0.88, python-sugar-toolkit-0.88)

[Debian Bug Tracking System]

Your message dated Wed, 01 Mar 2017 19:04:28 +
with message-id 
and subject line Bug#855925: fixed in sugar-irc-activity 8-1.3
has caused the Debian Bug report #855925,
regarding sugar-irc-activity: FTBFS: unsatisfiable build-dependencies: 
python-sugar-0.88, python-sugar-toolkit-0.88
to be marked as done.

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

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


-- 
855925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sugar-irc-activity
Version: 8-1.2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170221 qa-ftbfs
Justification: FTBFS in stretch on amd64

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: devscripts (>= 2.10.7~), cdbs (>= 0.4.90~), 
> dh-buildinfo, debhelper (>= 6), python (>= 2.6.6-3~), python-sugar-0.88 | 
> python-sugar, python-sugar-toolkit-0.88 | python-sugar-toolkit, unzip
> Filtered Build-Depends: devscripts (>= 2.10.7~), cdbs (>= 0.4.90~), 
> dh-buildinfo, debhelper (>= 6), python (>= 2.6.6-3~), python-sugar-0.88, 
> python-sugar-toolkit-0.88, unzip
> dpkg-deb: building package 'sbuild-build-depends-sugar-irc-activity-dummy' in 
> '/<>/resolver-DHctYl/apt_archive/sbuild-build-depends-sugar-irc-activity-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-sugar-irc-activity-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-DHctYl/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-DHctYl/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-DHctYl/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-DHctYl/apt_archive ./ Sources [572 B]
> Get:5 copy:/<>/resolver-DHctYl/apt_archive ./ Packages [641 B]
> Fetched 2176 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install sugar-irc-activity build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-sugar-irc-activity-dummy : Depends: python-sugar-0.88 
> but it is not installable
>  Depends: 
> python-sugar-toolkit-0.88 but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2017/02/21/sugar-irc-activity_8-1.2_testing.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Tomasz Buchert  (supplier of updated sugar-irc-activity 
package)

(This message was generated automatically at their request; if you
believe that there is a 

Bug#856416: grub-efi-amd64: Updating grub-efi-amd64:amd64 to 2.02~beta3-5 is aborted with half-installed package and reboot

[Reiner Nix]

Hi Adrian!

> This looks more like a local configuration issue at first sight rather than
> a bug in the grub2 package. Did you try to reproduce this issue on a freshly
> installed system?
Sorry, I did not try to reproduce this bug on another system.
However my system is quite young. Setup from scratch was started on 20.10.2016 
using a new pc.

The grub configuration was never changed manually, any maintenance was done 
using apt-get.


> I'm also not sure I understand how the configure process was interrupted? Did 
> it
> just abort on its own or did you hit "Ctrl+C" or did your machine crash?
> 
> I'm tagging this "moreinfo" because it's currently not obvious how and when
> the configure process for grub2 was interrupted.

While running apt-get upgrade, and installing the package, the system crashed.
Before it did not display any other message than the usual apt-get / dpkg 
message to install X86-64-efi
and in the next second it rebooted automatically not caused by any user 
activity or job.
Before the reboot it did not execute the standard shutdown jobs.
The reboot was just as if the system started with power on.

Also there was no reasonable additional load, just my desktop environment (KDE) 
and email program were running idle 
indeed at the first time I was not present at the desk. When coming back I 
noticed that the system displayed the login screen while I did not logout.

Some time later I tried to continue the update using 'dpkg --configure -a'.
So I discovered that the update could not be completed but run into reboot.

This was reproducible unless on the next day the configuration could be 
completed.

Hope this clarifies the situation a bit. 
Give me a note when I could provide any other details like log files etc.

Please find below an extract from the dpkg.log showing the lines regarding 
grub-efi-amd64.

Thanks for your help,
Reiner

--- extract from /var/log/dpkg.log ---
2017-02-05 19:17:30 configure grub-efi-amd64:amd64 2.02~beta3-4 
2017-02-05 19:17:30 status unpacked grub-efi-amd64:amd64 2.02~beta3-4
2017-02-05 19:17:30 status unpacked grub-efi-amd64:amd64 2.02~beta3-4
2017-02-05 19:17:30 status unpacked grub-efi-amd64:amd64 2.02~beta3-4
2017-02-05 19:17:30 status half-configured grub-efi-amd64:amd64 2.02~beta3-4
2017-02-05 19:17:43 status installed grub-efi-amd64:amd64 2.02~beta3-4
(...)
2017-02-27 12:18:35 upgrade grub-efi-amd64:amd64 2.02~beta3-4 2.02~beta3-5
2017-02-27 12:18:35 status half-configured grub-efi-amd64:amd64 2.02~beta3-4
2017-02-27 12:18:35 status unpacked grub-efi-amd64:amd64 2.02~beta3-4
2017-02-27 12:18:35 status half-installed grub-efi-amd64:amd64 2.02~beta3-4
2017-02-27 12:18:35 status half-installed grub-efi-amd64:amd64 2.02~beta3-4
2017-02-27 12:18:35 status unpacked grub-efi-amd64:amd64 2.02~beta3-5
2017-02-27 12:18:35 status unpacked grub-efi-amd64:amd64 2.02~beta3-5
2017-02-27 12:18:35 upgrade grub-efi-amd64-bin:amd64 2.02~beta3-4 2.02~beta3-5
2017-02-27 12:18:35 status half-configured grub-efi-amd64-bin:amd64 2.02~beta3-4
2017-02-27 12:18:35 status unpacked grub-efi-amd64-bin:amd64 2.02~beta3-4
2017-02-27 12:18:35 status half-installed grub-efi-amd64-bin:amd64 2.02~beta3-4
2017-02-27 12:18:35 status half-installed grub-efi-amd64-bin:amd64 2.02~beta3-4
2017-02-27 12:18:36 status unpacked grub-efi-amd64-bin:amd64 2.02~beta3-5
2017-02-27 12:18:36 status unpacked grub-efi-amd64-bin:amd64 2.02~beta3-5
(...)
2017-02-27 12:20:09 configure grub-efi-amd64-bin:amd64 2.02~beta3-5 
2017-02-27 12:20:09 status unpacked grub-efi-amd64-bin:amd64 2.02~beta3-5
2017-02-27 12:20:09 status half-configured grub-efi-amd64-bin:amd64 2.02~beta3-5
2017-02-27 12:20:09 status installed grub-efi-amd64-bin:amd64 2.02~beta3-5
(...)
2017-02-27 12:20:56 configure grub-efi-amd64:amd64 2.02~beta3-5 
2017-02-27 12:20:56 status unpacked grub-efi-amd64:amd64 2.02~beta3-5
2017-02-27 12:20:57 status unpacked grub-efi-amd64:amd64 2.02~beta3-5
2017-02-27 12:20:57 status unpacked grub-efi-amd64:amd64 2.02~beta3-5
2017-02-27 12:20:57 status half-configured grub-efi-amd64:amd64 2.02~beta3-5
2017-02-27 12:49:58 startup packages configure
2017-02-27 12:49:58 configure grub-efi-amd64:amd64 2.02~beta3-5 
2017-02-27 12:49:58 status half-configured grub-efi-amd64:amd64 2.02~beta3-5
2017-02-27 12:51:26 startup packages configure
2017-02-27 12:51:32 startup packages configure
2017-02-27 12:51:32 configure grub-efi-amd64:amd64 2.02~beta3-5 
2017-02-27 12:51:32 status half-configured grub-efi-amd64:amd64 2.02~beta3-5
2017-02-27 13:53:22 startup packages configure
2017-02-27 13:53:22 configure grub-efi-amd64:amd64 2.02~beta3-5 
2017-02-27 13:53:22 status half-configured grub-efi-amd64:amd64 2.02~beta3-5
2017-02-28 21:16:13 startup packages configure
2017-02-28 21:16:13 configure grub-efi-amd64:amd64 2.02~beta3-5 
2017-02-28 21:16:13 status half-configured grub-efi-amd64:amd64 2.02~beta3-5
2017-02-28 21:16:20 status installed grub-efi-amd64:amd64 2.02~beta3-5
---

Bug#856478: marked as done (Spurious key repeats)

[Debian Bug Tracking System]

Your message dated Wed, 01 Mar 2017 18:34:53 +
with message-id 
and subject line Bug#856478: fixed in gtk+3.0 3.22.9-2
has caused the Debian Bug report #856478,
regarding Spurious key repeats
to be marked as done.

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

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


-- 
856478: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgtk-3-0
Version: 3.22.9-1
Severity: grave
Tags: upstream


Hey,

In the wayland session ever since upgrading to 3.22.9 i'm getting spurious key
repeats in some applications.

This is likely to be https://bugzilla.gnome.org/show_bug.cgi?id=779374



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

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

Versions of packages libgtk-3-0 depends on:
ii  adwaita-icon-theme  3.22.0-1
ii  hicolor-icon-theme  0.15-1
ii  libatk-bridge2.0-0  2.22.0-1
ii  libatk1.0-0 2.22.0-1
ii  libc6   2.24-9
ii  libcairo-gobject2   1.14.8-1
ii  libcairo2   1.14.8-1
ii  libcolord2  1.3.3-2
ii  libcups22.2.1-8
ii  libepoxy0   1.3.1-2
ii  libfontconfig1  2.11.0-6.7+b1
ii  libfreetype62.6.3-3+b2
ii  libgdk-pixbuf2.0-0  2.36.5-2
ii  libglib2.0-02.50.3-1
ii  libgtk-3-common 3.22.9-1
ii  libjson-glib-1.0-0  1.2.2-1+b1
ii  libpango-1.0-0  1.40.4-1
ii  libpangocairo-1.0-0 1.40.4-1
ii  libpangoft2-1.0-0   1.40.4-1
ii  librest-0.7-0   0.8.0-2
ii  libsoup2.4-12.56.0-2
ii  libwayland-client0  1.12.0-1
ii  libwayland-cursor0  1.12.0-1
ii  libwayland-egl1-mesa [libwayland-egl1]  13.0.5-1
ii  libx11-62:1.6.4-3
ii  libxcomposite1  1:0.4.4-2
ii  libxcursor1 1:1.1.14-1+b1
ii  libxdamage1 1:1.1.4-2+b1
ii  libxext62:1.3.3-1
ii  libxfixes3  1:5.0.3-1
ii  libxi6  2:1.7.9-1
ii  libxinerama12:1.1.3-1+b1
ii  libxkbcommon0   0.7.1-1
ii  libxml2 2.9.4+dfsg1-2.2
ii  libxrandr2  2:1.5.1-1
ii  shared-mime-info1.8-1

Versions of packages libgtk-3-0 recommends:
ii  libgtk-3-bin  3.22.8-1

Versions of packages libgtk-3-0 suggests:
ii  gvfs 1.30.3-1
ii  librsvg2-common  2.40.16-1+b1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gtk+3.0
Source-Version: 3.22.9-2

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

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated gtk+3.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 01 Mar 2017 15:50:14 +
Source: gtk+3.0
Binary: libgtk-3-0 libgtk-3-0-udeb libgtk-3-common libgtk-3-bin libgtk-3-dev 
libgtk-3-doc gtk-3-examples gir1.2-gtk-3.0 gtk-update-icon-cache libgail-3-0 
libgail-3-dev libgail-3-doc
Architecture: source
Version: 3.22.9-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: 

Bug#830444: marked as done (osptoolkit: FTBFS: src/osptransapi.c:1041:13: error: non-floating-point argument in call to function '__builtin_isnan')

[Debian Bug Tracking System]

Your message dated Wed, 01 Mar 2017 17:33:47 +
with message-id 
and subject line Bug#830444: fixed in osptoolkit 4.13.0-1
has caused the Debian Bug report #830444,
regarding osptoolkit: FTBFS: src/osptransapi.c:1041:13: error: 
non-floating-point argument in call to function '__builtin_isnan'
to be marked as done.

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

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


-- 
830444: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: osptoolkit
Version: 4.11.3+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160707 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory '/«BUILDDIR»/osptoolkit-4.11.3+dfsg'
> libtool --mode=compile gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -DOSP_ALLOW_DUP_TXN 
> -DOSP_NO_DELETE_CHECK -DOSP_SDK -D_REENTRANT -D_POSIX_THREADS 
> -DOPENSSL_NO_KRB5 -D_GNU_SOURCE -Iinclude -Ienroll -Itest  -Wall  -o 
> src/osppkcs1.lo -c src/osppkcs1.c
> libtool: compile:  gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -DOSP_ALLOW_DUP_TXN 
> -DOSP_NO_DELETE_CHECK -DOSP_SDK -D_REENTRANT -D_POSIX_THREADS 
> -DOPENSSL_NO_KRB5 -D_GNU_SOURCE -Iinclude -Ienroll -Itest -Wall -c 
> src/osppkcs1.c  -fPIC -DPIC -o src/.libs/osppkcs1.o
> libtool: compile:  gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -DOSP_ALLOW_DUP_TXN 
> -DOSP_NO_DELETE_CHECK -DOSP_SDK -D_REENTRANT -D_POSIX_THREADS 
> -DOPENSSL_NO_KRB5 -D_GNU_SOURCE -Iinclude -Ienroll -Itest -Wall -c 
> src/osppkcs1.c -fPIE -o src/osppkcs1.o >/dev/null 2>&1
> libtool --mode=compile gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -DOSP_ALLOW_DUP_TXN 
> -DOSP_NO_DELETE_CHECK -DOSP_SDK -D_REENTRANT -D_POSIX_THREADS 
> -DOPENSSL_NO_KRB5 -D_GNU_SOURCE -Iinclude -Ienroll -Itest  -Wall  -o 
> src/osppkcs8.lo -c src/osppkcs8.c
> libtool: compile:  gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -DOSP_ALLOW_DUP_TXN 
> -DOSP_NO_DELETE_CHECK -DOSP_SDK -D_REENTRANT -D_POSIX_THREADS 
> -DOPENSSL_NO_KRB5 -D_GNU_SOURCE -Iinclude -Ienroll -Itest -Wall -c 
> src/osppkcs8.c  -fPIC -DPIC -o src/.libs/osppkcs8.o
> libtool: compile:  gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -DOSP_ALLOW_DUP_TXN 
> -DOSP_NO_DELETE_CHECK -DOSP_SDK -D_REENTRANT -D_POSIX_THREADS 
> -DOPENSSL_NO_KRB5 -D_GNU_SOURCE -Iinclude -Ienroll -Itest -Wall -c 
> src/osppkcs8.c -fPIE -o src/osppkcs8.o >/dev/null 2>&1
> libtool --mode=compile gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -DOSP_ALLOW_DUP_TXN 
> -DOSP_NO_DELETE_CHECK -DOSP_SDK -D_REENTRANT -D_POSIX_THREADS 
> -DOPENSSL_NO_KRB5 -D_GNU_SOURCE -Iinclude -Ienroll -Itest  -Wall  -o 
> src/osppkcs7.lo -c src/osppkcs7.c
> libtool: compile:  gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -DOSP_ALLOW_DUP_TXN 
> -DOSP_NO_DELETE_CHECK -DOSP_SDK -D_REENTRANT -D_POSIX_THREADS 
> -DOPENSSL_NO_KRB5 -D_GNU_SOURCE -Iinclude -Ienroll -Itest -Wall -c 
> src/osppkcs7.c  -fPIC -DPIC -o src/.libs/osppkcs7.o
> libtool: compile:  gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -DOSP_ALLOW_DUP_TXN 
> -DOSP_NO_DELETE_CHECK -DOSP_SDK -D_REENTRANT -D_POSIX_THREADS 
> -DOPENSSL_NO_KRB5 -D_GNU_SOURCE -Iinclude -Ienroll -Itest -Wall -c 
> src/osppkcs7.c -fPIE -o src/osppkcs7.o >/dev/null 2>&1
> libtool --mode=compile gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fPIE 
> -fstack-protector-strong -Wformat -Werror=format-security -DOSP_ALLOW_DUP_TXN 
> -DOSP_NO_DELETE_CHECK -DOSP_SDK -D_REENTRANT -D_POSIX_THREADS 
> -DOPENSSL_NO_KRB5 -D_GNU_SOURCE -Iinclude -Ienroll -Itest  -Wall  -o 
> src/ospcryptowrap.lo -c src/ospcryptowrap.c
> libtool: compile:  gcc -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -fstack-protector-strong -Wformat -Werror=format-security -DOSP_ALLOW_DUP_TXN 
> -DOSP_NO_DELETE_CHECK -DOSP_SDK -D_REENTRANT -D_POSIX_THREADS 
> -DOPENSSL_NO_KRB5 -D_GNU_SOURCE -Iinclude -Ienroll -Itest -Wall -c 
> src/ospcryptowrap.c  -fPIC -DPIC -o src/.libs/ospcryptowrap.o
> libtool: compile:  gcc 

Bug#828482: marked as done (osptoolkit: FTBFS with openssl 1.1.0)

[Debian Bug Tracking System]

Your message dated Wed, 01 Mar 2017 17:33:47 +
with message-id 
and subject line Bug#828482: fixed in osptoolkit 4.13.0-1
has caused the Debian Bug report #828482,
regarding osptoolkit: FTBFS with openssl 1.1.0
to be marked as done.

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

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


-- 
828482: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: osptoolkit
Version: 3.4.2-1.2
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/osptoolkit_3.4.2-1.2_amd64-20160529-1503

On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail.  There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.

There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.

If you have problems making things work, feel free to contact us.


Kurt
--- End Message ---
--- Begin Message ---
Source: osptoolkit
Source-Version: 4.13.0-1

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

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

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

Debian distribution maintenance software
pp.
TransNexus  (supplier of updated osptoolkit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 13 Feb 2017 04:40:51 -0500
Source: osptoolkit
Binary: osptoolkit libosptk4 libosptk-dev
Architecture: source
Version: 4.13.0-1
Distribution: unstable
Urgency: medium
Maintainer: TransNexus 
Changed-By: TransNexus 
Description:
 libosptk-dev - OSP Toolkit development library and header files
 libosptk4  - OSP Toolkit shared library
 osptoolkit - Open source client side development kit for Open Settlement Proto
Closes: 828482 830444
Changes:
 osptoolkit (4.13.0-1) unstable; urgency=medium
 .
   * New upstream release
   * Fix FTBFS with openssl 1.1.0 (Closes: #828482).
   * Fix non-floating-point argument in '__builtin_isana' (Closes: #830444).
   * Update debhelper compatibility level from 9 to 10.
Checksums-Sha1:
 2308316303e63d063dfa4d718072b8e2bc01bc29 1951 osptoolkit_4.13.0-1.dsc
 6d9d9208621df3291d364837fa7cefeddba86bb4 422064 osptoolkit_4.13.0.orig.tar.gz
 61ebe1230c211b00919fee01968d7728d9e70462 17336 
osptoolkit_4.13.0-1.debian.tar.xz
 dc6c8a94c763c8d613887bd795ce9ada4cf6a352 5798 
osptoolkit_4.13.0-1_amd64.buildinfo
Checksums-Sha256:
 51f4058b3a82d84a6700496d3c893d24b4cda14a818d67f4907a78a9fd714cff 1951 
osptoolkit_4.13.0-1.dsc
 e12771340b5c33f22d006a7cc03c952be8a11e9af1d531136ecadcfa2a8d2483 422064 
osptoolkit_4.13.0.orig.tar.gz
 cdf14b65b48efba13a80b5892cc7339249d7dfe13ac9dde1ca781d1b891fbb3f 17336 
osptoolkit_4.13.0-1.debian.tar.xz
 090fbad2200e52717a727219e78b67dfb3a1d07aee5758d42001ed5755ad70e2 5798 
osptoolkit_4.13.0-1_amd64.buildinfo
Files:
 ac5dd8330d29a8e3fdccfe4183540d5f 1951 utils optional osptoolkit_4.13.0-1.dsc
 456c59a7c1c9049f797c471f760546c8 422064 utils optional 
osptoolkit_4.13.0.orig.tar.gz
 fc19c3d2b2686e66919bb46133660ce4 17336 utils optional 
osptoolkit_4.13.0-1.debian.tar.xz
 a967e3e862f022bf8608e01b6af160ac 5798 utils optional 
osptoolkit_4.13.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAli3A6cACgkQCBa54Yx2
K61h0xAAtVcDpV2LZ+A7mVHCpLkeL8hR/w5XnNGHeIMttJl0R85lYLgEG0ObWcY1
r2yTW8WlwxWwddfrdqg3cKTi63Cy3U3Bt3F89TeeIDIwjqBCBgd1q6KvBIvpw/AW
YjhU1Jq1QsPcyhLEbNDkdg6JWpbekpdpqX/R64dZMW8XBqQJambUELReu+GKrbgo
O0yY/A8E0cSYNSiPHCdNiMzFXY0mClVec0B3Ah4flkgb8OG+jAKbJjnHO3ZiG3vl
eOEhcqzHaPaHq5eJmXDp8GeG20NvAkj5ooroVQUF4ThidiwX9wqqUxnoBG5Lo5/o
+iUqh/SHGXqaWpLbGt9XwX68qvGxf4q0zgwyqpW1GxPXjKWpJcvFawIni/f/o7Dp
ZIiu2ns1HQ/+YorX0grdLP4UyFA8aUIlbBKhDT3+VibKu0jBNZqjqe+OGyEWPT3d

Bug#856424: marked as done (libvcflib-tools: vcflib cannot find its programs in /usr/lib/vcflib/binaries)

[Debian Bug Tracking System]

Your message dated Wed, 01 Mar 2017 17:19:21 +
with message-id 
and subject line Bug#856424: fixed in libvcflib 1.0.0~rc1+dfsg1-3
has caused the Debian Bug report #856424,
regarding libvcflib-tools: vcflib cannot find its programs in 
/usr/lib/vcflib/binaries
to be marked as done.

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

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


-- 
856424: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libvcflib-tools
Version: 1.0.0~rc1+dfsg1-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

* What led up to the situation?

I installed libvcflib-tools on testing/stretch. When I ran 'vcflib', I
saw this:

$ vcflib
Usage: /usr/bin/vcflib 


   Existing programs are:   



  ls: cannot access '/usr/lib/vcflib/bin': No such file 
or directory

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

For now, I created a symlink from /usr/lib/vcflib/binaries to
/usr/lib/vcflib/bin.

* What was the outcome of this action?

Now vcflib can find its programs:

$ vcflib
Usage: /usr/bin/vcflib 
  Existing programs are:
abba-baba  LD plotHaps   vcf2dag
[...]

It looks like the 'keep_R_files' patch from September 2016 changed the
path to which programs are installed, while trying to keep the R
scripts from being purged by 'make clean'.

These R scripts reside in a 'scripts' directory upstream; maybe moving
them in the Debian package as well, reverting BIN_DIR in the Makefile,
and installing them from the scripts directory would fix this.

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

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

Versions of packages libvcflib-tools depends on:
ii  libc6  2.24-9
ii  libdisorder0   0.0.2-1
ii  libfastahack0  0.0+20160702-1
ii  libgcc11:6.3.0-6
ii  libgomp1   6.3.0-6
ii  libhts11.3.2-2
ii  libsmithwaterman0  0.0+20160702-1
ii  libstdc++6 6.3.0-6
ii  libtabixpp01.0.0-2
ii  libvcflib1 1.0.0~rc1+dfsg1-1
ii  zlib1g 1:1.2.8.dfsg-5

libvcflib-tools recommends no packages.

libvcflib-tools suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: libvcflib
Source-Version: 1.0.0~rc1+dfsg1-3

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libvcflib package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 01 Mar 2017 15:43:05 +0100
Source: libvcflib
Binary: libvcflib1 libvcflib-dev libvcflib-tools
Architecture: source amd64
Version: 1.0.0~rc1+dfsg1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libvcflib-dev - C++ library for parsing and manipulating VCF files 
(development)
 libvcflib-tools - C++ library for parsing and manipulating VCF files (tools)
 libvcflib1 - C++ library for parsing and manipulating VCF files
Closes: 856424
Changes:
 libvcflib (1.0.0~rc1+dfsg1-3) unstable; urgency=medium
 .
   * Fix location of binary tools
 Closes: 

Bug#855932: marked as done (sugar-physics-activity: FTBFS: unsatisfiable build-dependencies: python-sugar-0.88, python-sugar-toolkit-0.88)

[Debian Bug Tracking System]

Your message dated Wed, 01 Mar 2017 17:19:30 +
with message-id 
and subject line Bug#855932: fixed in sugar-physics-activity 7+dfsg-1.3
has caused the Debian Bug report #855932,
regarding sugar-physics-activity: FTBFS: unsatisfiable build-dependencies: 
python-sugar-0.88, python-sugar-toolkit-0.88
to be marked as done.

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

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


-- 
855932: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sugar-physics-activity
Version: 7+dfsg-1.2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170221 qa-ftbfs
Justification: FTBFS in stretch on amd64

Hi,

During a rebuild of all packages in stretch (in a stretch chroot, not a
sid chroot), your package failed to build on amd64.

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: devscripts (>= 2.10.7~), dh-buildinfo, debhelper (>= 
> 7.0.1), cdbs (>= 0.4.90~), python (>= 2.6.6-3~), python-sugar-0.88 | 
> python-sugar, python-sugar-toolkit-0.88 | python-sugar-toolkit, unzip
> Filtered Build-Depends: devscripts (>= 2.10.7~), dh-buildinfo, debhelper (>= 
> 7.0.1), cdbs (>= 0.4.90~), python (>= 2.6.6-3~), python-sugar-0.88, 
> python-sugar-toolkit-0.88, unzip
> dpkg-deb: building package 
> 'sbuild-build-depends-sugar-physics-activity-dummy' in 
> '/<>/resolver-bRQkUw/apt_archive/sbuild-build-depends-sugar-physics-activity-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-sugar-physics-activity-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-bRQkUw/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-bRQkUw/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-bRQkUw/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-bRQkUw/apt_archive ./ Sources [578 B]
> Get:5 copy:/<>/resolver-bRQkUw/apt_archive ./ Packages [646 B]
> Fetched 2187 B in 0s (0 B/s)
> Reading package lists...
> W: No sandbox user '_apt' on the system, can not drop privileges
> Reading package lists...
> 
> Install sugar-physics-activity build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-sugar-physics-activity-dummy : Depends: 
> python-sugar-0.88 but it is not installable
>  Depends: 
> python-sugar-toolkit-0.88 but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   
http://aws-logs.debian.net/2017/02/21/sugar-physics-activity_7+dfsg-1.2_testing.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Tomasz Buchert  (supplier of updated sugar-physics-activity 
package)

Bug#749272: varnish doesn't source /etc/default/varnish when started with systemd

[Stig Sandbeck Mathisen]

Michael Stapelberg  writes:

> Hi,
>
> Gregory Colpart  writes:
>> tags 749272 - wontfix
>> severity 749272 serious
>> retitle 749272 varnish doesn't source /etc/default/varnish when started but 
>> uses it when reloaded
>
> This bug’s severity now results in varnish and, transitively,
> freeradius being removed from testing, so it warrants timely
> action. Whether that’s a downgrade or a fix is up to the package
> maintainers (ssm?).
>
> FWIW, I think the request to load environment variable files is
> reasonable. It’s not idiomatic for systemd, but it is a widely used
> technique in Debian and will smoothen the transition for our users.

A problem with /etc/default/varnish is that it is a shell script
fragment, with examples using interpolation, and not just key=value
statements.  If someone has used "Alternative 3" for Varnish from that
file, the "reload" script will still fail when using systemd.

I think a fix for this issue may be:

* remove the reload action from systemd.

* Possibly patch the reload script to ensure it does not attempt to run
  when using systemd, by checking for the presence of
  "/run/systemd/system" and exit with a message if it is present.

I wrote that reload-vcl script long ago, and it has developed other
problems as varnish has developed, and probably needs to be rewritten
from scratch.

It needs to synchronize its varnishd command line option parser with
what varnishd may possibly use, and that was last done a long time ago.

"What should the varnish service actually reload when told to reload"
has multiple options.  The VCL file used when starting up?  The compiled
VCL from starting up? The VCL file last loaded, etc.

-- 
Stig Sandbeck Mathisen
https://fnord.no/

Bug#749272: varnish doesn't source /etc/default/varnish when started with systemd

[Michael Stapelberg]

Yet another alternative might be (and it pains me to say that, but maybe
it’s required to not break people’s setups) to have the service file start
a wrapper shell script which evaluates /etc/default/varnish before starting
varnish.

On Wed, Mar 1, 2017 at 7:29 AM, Stig Sandbeck Mathisen 
wrote:

> Michael Stapelberg  writes:
>
> > Hi,
> >
> > Gregory Colpart  writes:
> >> tags 749272 - wontfix
> >> severity 749272 serious
> >> retitle 749272 varnish doesn't source /etc/default/varnish when started
> but uses it when reloaded
> >
> > This bug’s severity now results in varnish and, transitively,
> > freeradius being removed from testing, so it warrants timely
> > action. Whether that’s a downgrade or a fix is up to the package
> > maintainers (ssm?).
> >
> > FWIW, I think the request to load environment variable files is
> > reasonable. It’s not idiomatic for systemd, but it is a widely used
> > technique in Debian and will smoothen the transition for our users.
>
> A problem with /etc/default/varnish is that it is a shell script
> fragment, with examples using interpolation, and not just key=value
> statements.  If someone has used "Alternative 3" for Varnish from that
> file, the "reload" script will still fail when using systemd.
>
> I think a fix for this issue may be:
>
> * remove the reload action from systemd.
>
> * Possibly patch the reload script to ensure it does not attempt to run
>   when using systemd, by checking for the presence of
>   "/run/systemd/system" and exit with a message if it is present.
>
> I wrote that reload-vcl script long ago, and it has developed other
> problems as varnish has developed, and probably needs to be rewritten
> from scratch.
>
> It needs to synchronize its varnishd command line option parser with
> what varnishd may possibly use, and that was last done a long time ago.
>
> "What should the varnish service actually reload when told to reload"
> has multiple options.  The VCL file used when starting up?  The compiled
> VCL from starting up? The VCL file last loaded, etc.
>
> --
> Stig Sandbeck Mathisen
> https://fnord.no/
>



-- 
Best regards,
Michael

Bug#856485: xpra: terminating xpra server destroys current X session

[John Paul Adrian Glaubitz]

Hi!

> I recommend to include current xpra version v1.0.3.

That's not possible at this stage of the Stretch freeze.

Either cherry-pick the patch which fixes this problem or the package
gets removed from testing. Importing a new upstream release is not
allowed at by the release team at this point.

Cheers,
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

Processed: Re: Bug#856424: libvcflib-tools: vcflib cannot find its programs in /usr/lib/vcflib/binaries

[Debian Bug Tracking System]

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

> tags 856424 pending
Bug #856424 [libvcflib-tools] libvcflib-tools: vcflib cannot find its programs 
in /usr/lib/vcflib/binaries
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#856210: libdebian-installer: please parse SHA256 field and add it to di_* structs

[Bastian Blank]

On Wed, Mar 01, 2017 at 02:25:12PM +0100, Julien Cristau wrote:
> Changing semantics of an existing struct member is classic ABI breakage.
>  This does very much need a SONAME bump.

Technically yes.  But this one is noe used uncontrolled outside.  So it
works without.

Bastian

-- 
Warp 7 -- It's a law we can live with.

Bug#856489: opendmarc: defaults file vanished

[Dominik George]

Package: opendmarc
Version: 1.3.2~Beta1-2
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

The /etc/defaults/opendmarc file has vanished, although it is still
referenced in README.Debian. The systemd service file also shows no
signs of ever reading this file.

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

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

Versions of packages opendmarc depends on:
ii  adduser 3.115
ii  libbsd0 0.8.3-1
ii  libc6   2.24-9
ii  libmilter1.0.1  8.15.2-8
ii  libopendmarc2   1.3.2~Beta1-2
ii  libspf2-2   1.2.10-7+b1
ii  lsb-base9.20161125
ii  publicsuffix20170223.0049-1

Versions of packages opendmarc recommends:
pn  libdbd-mysql-perl 
ii  libdbi-perl   1.636-1+b1
ii  libhttp-message-perl  6.11-1
ii  libopendbx1   1.4.6-11
ii  libopendbx1-mysql 1.4.6-11
ii  libswitch-perl2.17-2
ii  perl  5.24.1-1
pn  perl:any  

opendmarc suggests no packages.

- -- Configuration Files:
/etc/default/opendmarc [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/etc/default/opendmarc'
/etc/opendmarc.conf changed [not included]

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQJ4BAEBCABiFiEEPJ1UpHV1wCb7F/0mt5o8FqDE8pYFAli24HQxGmh0dHBzOi8v
d3d3LmRvbWluaWstZ2VvcmdlLmRlL2dwZy1wb2xpY3kudHh0LmFzYxIcbmlrQG5h
dHVyYWxuZXQuZGUACgkQt5o8FqDE8pblhxAAuQwlHprMZv3veerum2PQpijOHkQh
mTowKgbLdlIVz4K7S9VSgWEFkjlLEvd3Yg5ivcEq9cuu0Lr+LmFAsZILkooHXY4C
kvKrsHetRa//lAiozm6WFhqPn7QELKwW5usKbxOy/cdrV9e7a7WZPAjjHwhztQYR
5UGNrHVBhl4Aox7w0qINmbxeamxpj3JKYJIN4IPSezpfkM4AaCnhTsA2TNw1ONhZ
PxPDfZ7Zs2145sCgkzHIv3sV7QRN6TstMQzlWhG+JungnohJhFdrTCOk1zH9SvaP
wOHw+l5H70fElw2ugzTjdi5LpK7pGzqlLFgLoKpf0aJnATAfHwsAGrz+eguhIGfT
kxY9PVWoPPjt/uOfczpZ6HrVDXYKQIxs9xD7wnDKpX7urhYgNn9TKUZ9Cc+imqYI
GDUom0XyB8Y/dD2FF7EihM4/s8vquBMdq+UWzd2ucf6A0QROjaNq1lr3XpOuaI9+
nS8EqASprymQxwvAR6umRX4ilkwMshai0qWZWxC1L2m0uAXBy+Y1jDSUYmJJPc/3
dxbq6O74K1W+Y3Ny0cco8wF8SwGd56M+rwcAJsSYCRvTQwkQJSsWbyaFJAJMj6UB
iBf/Zqnb6nDUrhx7EVcoG4BbYIrtXdIMu4uC5Bx54a7JYv/V/nEcU+i2SH/lBufh
DGEZwPM/jR6YxVg=
=tWkp
-END PGP SIGNATURE-

Bug#856488: opendmarc: does not honor Socket config key anymore

[Dominik George]

Package: opendmarc
Version: 1.3.2~Beta1-2
Severity: grave
Justification: renders package unusable

At some point, OpenDMARC stopped honouring the Socket option in its
config file. This results in 127.0.0.1:12302 never being bound with the
configuration file attached.

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

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

Versions of packages opendmarc depends on:
ii  adduser 3.115
ii  libbsd0 0.8.3-1
ii  libc6   2.24-9
ii  libmilter1.0.1  8.15.2-8
ii  libopendmarc2   1.3.2~Beta1-2
ii  libspf2-2   1.2.10-7+b1
ii  lsb-base9.20161125
ii  publicsuffix20170223.0049-1

Versions of packages opendmarc recommends:
pn  libdbd-mysql-perl 
ii  libdbi-perl   1.636-1+b1
ii  libhttp-message-perl  6.11-1
ii  libopendbx1   1.4.6-11
ii  libopendbx1-mysql 1.4.6-11
ii  libswitch-perl2.17-2
ii  perl  5.24.1-1
pn  perl:any  

opendmarc suggests no packages.

-- Configuration Files:
/etc/default/opendmarc [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/etc/default/opendmarc'
/etc/opendmarc.conf changed:
PidFile /var/run/opendmarc.pid
RejectFailures false
Syslog true
UMask 0002
UserID opendmarc:opendmarc
PublicSuffixList /usr/share/publicsuffix/
Socket inet:12302@127.0.0.1

-- no debconf information

Bug#856485: xpra: terminating xpra server destroys current X session

[mviereck]

Package: xpra
Version: 0.17.6+dfsg-1
Severity: critical
Justification: causes serious data loss

Dear Maintainer,

steps to reproduce:
1. start xpra server
  xpra start :20 --start-child=xterm --exit-with-children
2. attach to server
  xpra attach :20
3. terminate xpra server (in this case by closing xterm)

The above steps destroy current X session, leaving a black screen with some 
startup messages.
This does not happen with current xpra v1.0.3-r15051 from xpra repository.

This bug may be related to debian bug #855980 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855980
Bug report on xpra website: http://xpra.org/trac/ticket/1451

I recommend to include current xpra version v1.0.3. 



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

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

Versions of packages xpra depends on:
ii  adduser   3.115
ii  libavcodec57  7:3.2.4-1
ii  libavutil55   7:3.2.4-1
ii  libc6 2.24-9
ii  libgtk2.0-0   2.24.31-2
ii  libswscale4   7:3.2.4-1
ii  libvpx4   1.6.1-2
ii  libx11-6  2:1.6.4-3
ii  libx264-148   2:0.148.2748+git97eaef2-1
ii  libxcomposite11:0.4.4-2
ii  libxdamage1   1:1.1.4-2+b1
ii  libxext6  2:1.3.3-1
ii  libxfixes31:5.0.3-1
ii  libxkbfile1   1:1.0.9-2
ii  libxrandr22:1.5.1-1
ii  libxtst6  2:1.2.3-1
ii  python2.7.13-2
ii  python-gi-cairo   3.22.0-2
ii  python-gtk2   2.24.0-5.1
ii  python-rencode1.0.5-1
pn  python:any
ii  x11-xserver-utils 7.7+7
ii  xserver-xorg-input-void   1:1.4.1-1+b2
ii  xserver-xorg-video-dummy  1:0.3.8-1

Versions of packages xpra recommends:
ii  keyboard-configuration 1.160
ii  ksshaskpass [ssh-askpass]  4:5.8.4-1
ii  openssh-client 1:7.4p1-6
ii  python-dbus1.2.4-1
ii  python-gtkglext1   1.1.0-9.1
ii  python-lz4 0.8.2+dfsg-2
ii  python-lzo 1.08-1
ii  python-pil 4.0.0-4

Versions of packages xpra suggests:
ii  cups-common2.2.1-8
ii  cups-filters   1.11.6-3
pn  cups-pdf   
ii  gstreamer1.0-plugins-bad   1.10.3-1
ii  gstreamer1.0-plugins-base  1.10.3-1
ii  gstreamer1.0-plugins-good  1.10.3-1
ii  gstreamer1.0-plugins-ugly  1.10.3-1
pn  openssh-server 
ii  pulseaudio 10.0-1
ii  pulseaudio-utils   10.0-1
pn  python-avahi   
pn  python-cups
ii  python-gst-1.0 1.10.3-1
pn  python-netifaces   
pn  python-opencv  
pn  python-pyopencl
pn  python-yaml
pn  v4l2loopback-dkms  

-- no debconf information

Bug#856210: libdebian-installer: please parse SHA256 field and add it to di_* structs

[Steven Chamberlain]

Control: tags -1 - patch

I've no more desire to work on this bug, sorry.

Thanks for the feedback that was given, but it has already been more
effort than I have time or patience to contribute.

For what should be essentially, s/md5/sha256/ in a few places, the
required procedures and personal interactions beyond that, is just too
much.  That is the real "debacle";  it is not surprising to me now, that
this did not happen yet in 10 years, or that no enthusiastic new
contributor had already done this.

Regards,
-- 
Steven Chamberlain
ste...@pyro.eu.org


signature.asc
Description: Digital signature

Processed: Re: Bug#856210: libdebian-installer: please parse SHA256 field and add it to di_* structs

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - patch
Bug #856210 [src:libdebian-installer] libdebian-installer: please parse SHA256 
field and add it to di_* structs
Removed tag(s) patch.

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

Bug#856479: marked as done (srst2: insecure handling of system calls)

[Debian Bug Tracking System]

Your message dated Wed, 01 Mar 2017 13:49:16 +
with message-id 
and subject line Bug#856479: fixed in srst2 0.2.0-4
has caused the Debian Bug report #856479,
regarding srst2: insecure handling of system calls
to be marked as done.

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

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


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

Hi,

srst2 uses os.popen with unquotet strings allowing users to inject
system calls by preparing specifically designed fasta sequence names
containing '(', ')', ';' characters and others.

A patch fixing this is just in packaging SVN and will be uploaded
right after the bug is published.

Kind regards

  Andreas.

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

Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: srst2
Source-Version: 0.2.0-4

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated srst2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 01 Mar 2017 14:23:12 +0100
Source: srst2
Binary: srst2
Architecture: source amd64
Version: 0.2.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 srst2  - Short Read Sequence Typing for Bacterial Pathogens
Closes: 856479
Changes:
 srst2 (0.2.0-4) unstable; urgency=medium
 .
   * Do not fail if search string contains special shell characters
 Closes: #856479
Checksums-Sha1:
 dabf6e186d872ffe98ddcdb18f74e253dfb3288e 2120 srst2_0.2.0-4.dsc
 473534c01dc07936861f9a6ed3340b393e466fc6 9144 srst2_0.2.0-4.debian.tar.xz
 a39dd678252580fff8057aa394dd1951901bbf01 6109 srst2_0.2.0-4_amd64.buildinfo
 b25f62ae9e29dc7119ac76ee6c0c977e2189eaeb 60526 srst2_0.2.0-4_amd64.deb
Checksums-Sha256:
 b931e6031f6cae834d583a424fa237ff71568b1b2788905238dced8618911676 2120 
srst2_0.2.0-4.dsc
 8bf33c24c87d94e36d337e422009a41a3def007ae780484e424865f3892667bd 9144 
srst2_0.2.0-4.debian.tar.xz
 e156155b64a80db9e467e787c9ca53fc1fbf83f84c77709674f0d3d0d5ccc689 6109 
srst2_0.2.0-4_amd64.buildinfo
 a7657978a2094676ddfe144a020eb7d5c5f008058f66a7fcb2551f0165b0d207 60526 
srst2_0.2.0-4_amd64.deb
Files:
 083bfd8f0f0130c842983e8b745a5595 2120 science optional srst2_0.2.0-4.dsc
 3b67b50c9df03eec43afef3713fd 9144 science optional 
srst2_0.2.0-4.debian.tar.xz
 a1dce05680da41a578ec2f4f1b06f525 6109 science optional 
srst2_0.2.0-4_amd64.buildinfo
 ef52463297650aeafd64ca4a8e6f3373 60526 science optional srst2_0.2.0-4_amd64.deb

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAli2zHQRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtHUrw/8C4g94Ws8dd7XM1l8uJQgkgloW3FPow/h
lk1tXxu2AIlxrnKjICXG4BuzatXsvzr/9JvJdPaXh8PyAxswnmZo363E8xypm2qx
0DMuAxoUrH7x8wJ8T8yC/lxggbJoqY+eCFuseTiVh2+juFOtkowlPfOb4ei3jkJU
2442dwoySX0wSmo9yWE7WvqP6uAJldcQCYSr+c0t7rHTDMKP8Jh+pSFeejV4T5vJ
WsMIA0oVPknLWnS/OyIDnyhlmexjQxD/ZjoLeOV1tJ0EIe85K5/ziQbrVqLWeD1K
DJs3xO0kmlnNnIB/cDGIyJMddiBFW7y1hMqbEhqT+p+miT+vx8bcS7jZ04huJG/x
UW8Vd6YwASGtF3MprzoBRIWSzlfg/ihiuxtLh39ig8yoCDSHMbW1L7pfLkRjo/FH
A9/2FNQKXtxcKlv659x1IaY5EGvtZ3mU93cFlvx5LoYta8TX9euB7iWt9DTr2pbH
ktcS6jeyweXp1Movmi9DfPLe2iPHj6GPHBotM+INPeVrEeM51xnrY4ufkjh1D+QI
6JeK5RCXRzTjz9boiq7qGD2IfvhwoYB2zb1ZkyEzp9ijleeIEubGN7207PCsR23F
BxFi+Ll4Y4Ij/1cC1IPmRjHPZr7KtyVmnhCIyrOU+a1mzUFoduPRsml/oIVLufYs
Pz8pd2fVfgg=
=IhGV
-END PGP SIGNATURE End Message ---

Bug#856210: libdebian-installer: please parse SHA256 field and add it to di_* structs

[Julien Cristau]

On 02/27/2017 04:40 PM, Steven Chamberlain wrote:
> Bastian Blank wrote:
>> This change breaks the existing ABI and therefor needs an ABI bump, but
>> it is missing from the patch.
> 
> The attached patch tries to bump the soname to 5.  This makes the diff
> much larger, but the code changes are the same.
> 
> I think libdebian-installer-extra nowadays gets a soname bump at the
> same time as libdebian-installer (whereas in the past it was possible to
> set a different soname for each).
> 
> (If we really wanted, we could maybe avoid the ABI bump:  no library
> functions are being added/removed, only the name and meaning of a struct
> member (a pointer, which remains the same length).  The
> dynamically-sized buffer it points to, would change from storing an MD5
> to a SHA256 hash, and would only cause a regression where something is
> still trying to validate MD5).
> 
Changing semantics of an existing struct member is classic ABI breakage.
 This does very much need a SONAME bump.

Cheers,
Julien

Bug#855494: mgltools-pmv: runPmv does not start

[Andreas Tille]

Hi Ghislain,

On Wed, Mar 01, 2017 at 09:59:28AM +, Ghislain Vaillant wrote:
> 
> Not too surprising considering that the numpy.oldnumeric modules was removed
> since Numpy 1.9 [1], so it has been broken for a long time without people
> noticing.

Thanks for your research into this.

> We could port the code base to the current Numpy API, but I am not sure
> whether we will have enough of a user-base to validate it (see above) and
> how much effort it will take. Besides, the software did not receive updates
> for years so we would probably be maintaining this effort on our own.

As far as I understood Steffen upstream is not dead but does not that
frequent releases.
 
> Based on this 2 comments, one might ask whether it is worth maintaining a
> package for this piece of software.

Steffen, could you please comment on this?

I admit, I'm personally not that motivated saving non-free software.

Kind regards

  Andreas.

> [1] https://docs.scipy.org/doc/numpy/reference/routines.oldnumeric.html

-- 
http://fam-tille.de

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

[Wouter Verhelst]

Hi Niels,

On Sat, Feb 25, 2017 at 08:40:00AM +, Niels Thykier wrote:
> Ok, please go ahead with the upload.

Done today. Sorry about the delay, I was out of the country.

> The only question I have is about this bit here:
> 
> > +  if (s->hostname && *s->hostname)
> > +{
> > +  if (!gnutls_x509_crt_check_hostname (cert, s->hostname))
> > +   {
> > + debugout (s,
> > +   "The certificate's owner does not match hostname '%s'\n",
> > +   s->hostname);
> > + return GNUTLS_E_CERTIFICATE_ERROR;
> > +   }
> > +}
> 
> When is the "s->hostname" is blank / NULL ?

s->hostname may be set on the command line to override the autodetected
hostname. If that's the case, this is only a sanity check to ensure that
the client certificate matches the client's hostname as specified. The
server has other checks for ensuring these names are valid.

It should not have any security impact on the client.

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

Bug#856479: srst2: insecure handling of system calls

[Andreas Tille]

Package: srst2
Version: 0.2.0-3
Severity: grave
Tags: patch security
Justification: user security hole

Hi,

srst2 uses os.popen with unquotet strings allowing users to inject
system calls by preparing specifically designed fasta sequence names
containing '(', ')', ';' characters and others.

A patch fixing this is just in packaging SVN and will be uploaded
right after the bug is published.

Kind regards

  Andreas.

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

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

Bug#856478: Spurious key repeats

[Sjoerd Simons]

Package: libgtk-3-0
Version: 3.22.9-1
Severity: grave
Tags: upstream


Hey,

In the wayland session ever since upgrading to 3.22.9 i'm getting spurious key
repeats in some applications.

This is likely to be https://bugzilla.gnome.org/show_bug.cgi?id=779374



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

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

Versions of packages libgtk-3-0 depends on:
ii  adwaita-icon-theme  3.22.0-1
ii  hicolor-icon-theme  0.15-1
ii  libatk-bridge2.0-0  2.22.0-1
ii  libatk1.0-0 2.22.0-1
ii  libc6   2.24-9
ii  libcairo-gobject2   1.14.8-1
ii  libcairo2   1.14.8-1
ii  libcolord2  1.3.3-2
ii  libcups22.2.1-8
ii  libepoxy0   1.3.1-2
ii  libfontconfig1  2.11.0-6.7+b1
ii  libfreetype62.6.3-3+b2
ii  libgdk-pixbuf2.0-0  2.36.5-2
ii  libglib2.0-02.50.3-1
ii  libgtk-3-common 3.22.9-1
ii  libjson-glib-1.0-0  1.2.2-1+b1
ii  libpango-1.0-0  1.40.4-1
ii  libpangocairo-1.0-0 1.40.4-1
ii  libpangoft2-1.0-0   1.40.4-1
ii  librest-0.7-0   0.8.0-2
ii  libsoup2.4-12.56.0-2
ii  libwayland-client0  1.12.0-1
ii  libwayland-cursor0  1.12.0-1
ii  libwayland-egl1-mesa [libwayland-egl1]  13.0.5-1
ii  libx11-62:1.6.4-3
ii  libxcomposite1  1:0.4.4-2
ii  libxcursor1 1:1.1.14-1+b1
ii  libxdamage1 1:1.1.4-2+b1
ii  libxext62:1.3.3-1
ii  libxfixes3  1:5.0.3-1
ii  libxi6  2:1.7.9-1
ii  libxinerama12:1.1.3-1+b1
ii  libxkbcommon0   0.7.1-1
ii  libxml2 2.9.4+dfsg1-2.2
ii  libxrandr2  2:1.5.1-1
ii  shared-mime-info1.8-1

Versions of packages libgtk-3-0 recommends:
ii  libgtk-3-bin  3.22.8-1

Versions of packages libgtk-3-0 suggests:
ii  gvfs 1.30.3-1
ii  librsvg2-common  2.40.16-1+b1

-- no debconf information

Bug#856470: libzypp: FTBFS on mips*

[James Cowgill]

Source: libzypp
Version: 16.4.3-1
Severity: serious
Tags: sid stretch

Hi,

libzypp FTBFS on mips* due to errors in Arch.cc:
> /«PKGBUILDDIR»/zypp/Arch.cc:153:46: error: expected unqualified-id before 
> numeric constant
>namespace { static inline const IdString & _##A () { static IdString 
> __str(#A); return __str; } } \
>   ^
> /«PKGBUILDDIR»/zypp/Arch.cc:215:3: note: in expansion of macro 'DEF_BUILTIN'
>DEF_BUILTIN( mips );
>^~~
> /«PKGBUILDDIR»/zypp/Arch.cc:153:46: error: expected initializer before 
> numeric constant
>namespace { static inline const IdString & _##A () { static IdString 
> __str(#A); return __str; } } \
>   ^
> /«PKGBUILDDIR»/zypp/Arch.cc:215:3: note: in expansion of macro 'DEF_BUILTIN'
>DEF_BUILTIN( mips );
>^~~
> /«PKGBUILDDIR»/zypp/Arch.cc:154:29: error: expression cannot be used as a 
> function
>const Arch Arch_##A( _##A() )
>  ^
> /«PKGBUILDDIR»/zypp/Arch.cc:215:3: note: in expansion of macro 'DEF_BUILTIN'
>DEF_BUILTIN( mips );
>^~~
> /«PKGBUILDDIR»/zypp/Arch.cc: In constructor 
> 'zypp::{anonymous}::ArchCompatSet::ArchCompatSet()':
> /«PKGBUILDDIR»/zypp/Arch.cc:357:27: error: expression cannot be used as a 
> function
>   defCompatibleWith( _mips(),  _noarch() );
>^
> zypp/CMakeFiles/zypp.dir/build.make:4889: recipe for target 
> 'zypp/CMakeFiles/zypp.dir/Arch.cc.o' failed

This is because, for historical reasons, the mips toolchain defines
"mips = 1" and "_mips = 1". Either "-Umips -U_mips" need to be added to
the CFLAGS on MIPS or the code in Arch.cc needs to be changed to avoid
the use of the "mips" and "_mips" identifiers.

Thanks,
James



signature.asc
Description: OpenPGP digital signature

Bug#852929: scalable-cyrfonts: FTBFS: LaTeX requires e-TeX.

[Anton Zinoviev]

On Sun, Feb 26, 2017 at 07:54:28PM +0100, Sascha Steinbiss wrote:
> 
> Switching to ‘luatex' instead of ‘tex’ fixed the issue for me. Please 
> see attached patch. However, I would be happy if someone could take a 
> second look. I don’t usually write Cyrillic ;)

Thanks.  I am uploading the package now. :)

Anton Zinoviev

Bug#852929: marked as done (scalable-cyrfonts: FTBFS: LaTeX requires e-TeX.)

[Debian Bug Tracking System]

Your message dated Wed, 01 Mar 2017 10:34:51 +
with message-id 
and subject line Bug#852929: fixed in scalable-cyrfonts 4.17
has caused the Debian Bug report #852929,
regarding scalable-cyrfonts: FTBFS: LaTeX requires e-TeX.
to be marked as done.

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

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


-- 
852929: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852929
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scalable-cyrfonts
Version: 4.16+nmu1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20170128 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> make[2]: Entering directory 
> '/<>/scalable-cyrfonts-4.16+nmu1/fontinst'
> cp ../t2/cyrfinst/t2c.etx ../t2/cyrfinst/lcy-hi.etx ../t2/cyrfinst/t2a.etx 
> ../t2/cyrfinst/ot2.etx ../t2/cyrfinst/x2.etx ../t2/cyrfinst/6r.etx 
> ../t2/cyrfinst/lcy.etx ../t2/cyrfinst/t2b.etx 
> ../t2/cyrfinst/derivatives/x2c.etx ../t2/cyrfinst/derivatives/lcyij.etx 
> ../t2/cyrfinst/derivatives/t2ac.etx ../t2/cyrfinst/derivatives/lcycij.etx 
> ../t2/cyrfinst/derivatives/t2bij.etx ../t2/cyrfinst/derivatives/ot2ij.etx 
> ../t2/cyrfinst/derivatives/lcyj.etx ../t2/cyrfinst/derivatives/lcyci.etx 
> ../t2/cyrfinst/derivatives/lcyc.etx ../t2/cyrfinst/derivatives/t2cc.etx 
> ../t2/cyrfinst/derivatives/t2bj.etx ../t2/cyrfinst/derivatives/t2ccj.etx 
> ../t2/cyrfinst/derivatives/ot2c.etx ../t2/cyrfinst/derivatives/ot2cj.etx 
> ../t2/cyrfinst/derivatives/t2aj.etx ../t2/cyrfinst/derivatives/lcyitt.etx 
> ../t2/cyrfinst/derivatives/lcyctt.etx ../t2/cyrfinst/derivatives/x2j.etx 
> ../t2/cyrfinst/derivatives/t2bc.etx ../t2/cyrfinst/derivatives/t2cij.etx 
> ../t2/cyrfinst/derivatives/x2ij.etx ../t2/cyrfinst/derivatives/lcycj.etx 
> ../t2/cyrfinst/derivatives/ot2i.etx ../t2/cyrfinst/derivatives/x2i.etx 
> ../t2/cyrfinst/derivatives/t2ci.etx ../t2/cyrfinst/derivatives/ot2j.etx 
> ../t2/cyrfinst/derivatives/t2bcj.etx ../t2/cyrfinst/derivatives/t2aij.etx 
> ../t2/cyrfinst/derivatives/t2ai.etx ../t2/cyrfinst/derivatives/lcytt.etx 
> ../t2/cyrfinst/derivatives/x2cj.etx ../t2/cyrfinst/derivatives/t2bi.etx 
> ../t2/cyrfinst/derivatives/t2cj.etx ../t2/cyrfinst/derivatives/lcyi.etx 
> ../t2/cyrfinst/derivatives/t2acj.etx ../t2/cyrfinst/cyrillic.mtx 
> ../t2/cyrfinst/etc/fnstcorr.tex ../t2/cyrfinst/etc/cyralias.tex .
> cp ../6r.etx . 
> cp /usr/share/fonts/type1/gsfonts/s05l.afm psyr.afm
> for j in ../texfonts/*.afm; do \
>   ../shortenafm $j >`basename $j`; \
> done
> touch copyafms
> touch copyall
> cp /usr/share/texlive/texmf-dist/web2c/texmf.cnf .
> cat 99cyrfonts-build.cnf >> texmf.cnf
> perl makemtx.perl ftm 8a 6w >ftm-mtx.tex
> perl makemtx.perl fhv 8a 6w >fhv-mtx.tex
> perl makemtx.perl fcr 8a 6w >fcr-mtx.tex
> perl makemtx.perl fag 8a 6w >fag-mtx.tex
> perl makemtx.perl fbk 8a 6w >fbk-mtx.tex
> perl makemtx.perl fsb 8a 6w >fsb-mtx.tex
> perl makemtx.perl fpl 8a 6w >fpl-mtx.tex
> perl makemtx.perl fta 8a 6w >fta-mtx.tex
> perl makemtx.perl fsj 8a 6w >fsj-mtx.tex
> perl makemtx.perl fzc 8a 6w >fzc-mtx.tex
> set -e && for i in ftm-mtx.tex fhv-mtx.tex fcr-mtx.tex fag-mtx.tex 
> fbk-mtx.tex fsb-mtx.tex fpl-mtx.tex fta-mtx.tex fsj-mtx.tex fzc-mtx.tex; do\
>   latex $i; \
> done
> This is pdfTeX, Version 3.14159265-2.6-1.40.17 (TeX Live 2016/Debian) 
> (preloaded format=latex)
>  restricted \write18 enabled.
> entering extended mode
> (./ftm-mtx.tex
> LaTeX2e <2017/01/01>
> Babel <3.9r> and hyphenation patterns for 3 language(s) loaded.
> (/usr/share/texlive/texmf-dist/tex/fontinst/base/fontinst.sty
> 
> LaTeX Warning: You have requested package `',
>but the package provides `fontinst'.
> 
> No file fontinst.rc.
> ) (./fnstcorr.tex) (./cyralias.tex) (./psyr.afm)
> Metrics written on psyr.mtx.
> (./psyr.mtx)
> Raw font written on psyr.pl.
> (./psyr.mtx)
> Transformed metrics written on psyro.mtx.
> (./psyro.mtx)
> Raw font written on psyro.pl.
> (./ftmr8a.afm)
> Metrics written on ftmr8a.mtx.
> (./ftmr8a.mtx)
> Raw font written on ftmr8a.pl.
> (/usr/share/texlive/texmf-dist/tex/fontinst/latinetx/8r.etx) (./ftmr8a.mtx)
> Transformed metrics written on ftmr8r.mtx.
> (./ftmr8r.mtx)
> Raw font written on ftmr8r.pl.
> (./ftmr6w.afm)
> Metrics written on ftmr6w.mtx.
> (./ftmr6w.mtx)
> Raw font written on ftmr6w.pl.
> (./6r.etx) (./ftmr6w.mtx)
> Transformed metrics written on ftmr6r.mtx.
> (./ftmr6r.mtx)
> Raw font written on ftmr6r.pl.
> (./ftmri8a.afm)
> Metrics written on ftmri8a.mtx.
> 

Bug#849504: marked as done (Data corruption with copy-on-write and multiple threads)

[Debian Bug Tracking System]

Your message dated Wed, 01 Mar 2017 10:34:16 +
with message-id 
and subject line Bug#849504: fixed in nbd 1:3.15.2-1
has caused the Debian Bug report #849504,
regarding Data corruption with copy-on-write and multiple threads
to be marked as done.

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

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


-- 
849504: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=849504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nbd-server
Version: 1:3.12-1
Severity: serious
Forwarded: https://github.com/NetworkBlockDevice/nbd/issues/43

A bug was reported upstream in nbd upstream when combining copy-on-write
and multiple threads. The latter was a new feature for nbd 3.12, and the
bug was always present since that implementation of multiple threads, so
filing this bug on the version that introduced it into Debian.

We should not release Debian with this bug present; however, I don't
want to fix this right now, or 1:3.15.1-1 will miss the freeze cutoff.
I'll upload a package as soon as that version migrates to testing.

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

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

Versions of packages nbd-server depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.59
ii  libc6  2.24-8
ii  libglib2.0-0   2.50.2-2
ii  libgnutls303.5.7-3
ii  ucf3.0036

nbd-server recommends no packages.

nbd-server suggests no packages.

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: nbd
Source-Version: 1:3.15.2-1

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

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

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

Debian distribution maintenance software
pp.
Wouter Verhelst  (supplier of updated nbd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 22 Feb 2017 00:09:31 +0100
Source: nbd
Binary: nbd-server nbd-client nbd-client-udeb
Architecture: source amd64
Version: 1:3.15.2-1
Distribution: unstable
Urgency: medium
Maintainer: Wouter Verhelst 
Changed-By: Wouter Verhelst 
Description:
 nbd-client - Network Block Device protocol - client
 nbd-client-udeb - Network Block Device protocol - client for Debian Installer 
(udeb)
 nbd-server - Network Block Device protocol - server
Closes: 849504 852288
Changes:
 nbd (1:3.15.2-1) unstable; urgency=medium
 .
   * New upstream release
 - Fixes data corruption with multiple threads and copyonwrite enabled;
   Closes: #852288, #849504. Why did I create multiple bugs for this?
   Ah well, no matter.
Checksums-Sha1:
 a6440f017236e54d9e4431d6c46c0fb92f8a7b23 1992 nbd_3.15.2-1.dsc
 b45cdb7ab9bd7f03055c1e23e7934cba019dd486 1035356 nbd_3.15.2.orig.tar.gz
 46c7796c398f8098ea274b107bb2b9b26bd1ef28 91409 nbd_3.15.2-1.diff.gz
 bf1c7736498716e2c92705860f701b36f54f537a 33892 
nbd-client-dbgsym_3.15.2-1_amd64.deb
 5425f81b75883ac61f38befe23c639d657e042ae 10862 
nbd-client-udeb_3.15.2-1_amd64.udeb
 0a7b5268774d7d2cfd0285e5259b74ee96b4f3bd 56016 nbd-client_3.15.2-1_amd64.deb
 835bb727f110352e3fe2e708f77c76b1f21add18 73556 
nbd-server-dbgsym_3.15.2-1_amd64.deb
 e089475747e2863fefd4eb4db7f6be3addb43e77 74496 nbd-server_3.15.2-1_amd64.deb
 6046081b9c0dd49f850290fa225edb05ac63fbb8 7165 nbd_3.15.2-1_amd64.buildinfo
Checksums-Sha256:
 b443e254181235acf1cb37a6d1258fee9ca06f831f3d68360391ed54f66e849f 1992 
nbd_3.15.2-1.dsc
 0155e6fd142853ad60172906393e4329ad648656342fb7a3b35de97ce4a82c88 1035356 
nbd_3.15.2.orig.tar.gz
 55dd7d175a30dff7848cf43dec295c0adf647643b7e094fc58fe379414c24570 91409 
nbd_3.15.2-1.diff.gz
 

Bug#852288: marked as done (Data corruption when multiple threads are allowed and copyonwrite is enabled)

[Debian Bug Tracking System]

Your message dated Wed, 01 Mar 2017 10:34:16 +
with message-id 
and subject line Bug#852288: fixed in nbd 1:3.15.2-1
has caused the Debian Bug report #852288,
regarding Data corruption when multiple threads are allowed and copyonwrite is 
enabled
to be marked as done.

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

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


-- 
852288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nbd-server
Version: 1:3.12-0
Severity: grave
Tags: upstream
Forwarded: https://github.com/NetworkBlockDevice/nbd/issues/43

There's a data corruption bug in nbd which has existed since the
upstream release of 3.12. We should not release nbd in stretch with that
bug.

I have a preliminary fix, but it needs some testing. However, I'm
currently swamped with other work, and this has gone to the backburner a
bit. Since I don't want to forget about this issue, filing a bugreport
in the Debian BTS should help.

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

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

Versions of packages nbd-server depends on:
ii  adduser3.115
ii  debconf [debconf-2.0]  1.5.60
ii  libc6  2.24-9
ii  libglib2.0-0   2.50.2-2
ii  libgnutls303.5.8-1
ii  ucf3.0036

nbd-server recommends no packages.

nbd-server suggests no packages.

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: nbd
Source-Version: 1:3.15.2-1

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

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

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

Debian distribution maintenance software
pp.
Wouter Verhelst  (supplier of updated nbd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 22 Feb 2017 00:09:31 +0100
Source: nbd
Binary: nbd-server nbd-client nbd-client-udeb
Architecture: source amd64
Version: 1:3.15.2-1
Distribution: unstable
Urgency: medium
Maintainer: Wouter Verhelst 
Changed-By: Wouter Verhelst 
Description:
 nbd-client - Network Block Device protocol - client
 nbd-client-udeb - Network Block Device protocol - client for Debian Installer 
(udeb)
 nbd-server - Network Block Device protocol - server
Closes: 849504 852288
Changes:
 nbd (1:3.15.2-1) unstable; urgency=medium
 .
   * New upstream release
 - Fixes data corruption with multiple threads and copyonwrite enabled;
   Closes: #852288, #849504. Why did I create multiple bugs for this?
   Ah well, no matter.
Checksums-Sha1:
 a6440f017236e54d9e4431d6c46c0fb92f8a7b23 1992 nbd_3.15.2-1.dsc
 b45cdb7ab9bd7f03055c1e23e7934cba019dd486 1035356 nbd_3.15.2.orig.tar.gz
 46c7796c398f8098ea274b107bb2b9b26bd1ef28 91409 nbd_3.15.2-1.diff.gz
 bf1c7736498716e2c92705860f701b36f54f537a 33892 
nbd-client-dbgsym_3.15.2-1_amd64.deb
 5425f81b75883ac61f38befe23c639d657e042ae 10862 
nbd-client-udeb_3.15.2-1_amd64.udeb
 0a7b5268774d7d2cfd0285e5259b74ee96b4f3bd 56016 nbd-client_3.15.2-1_amd64.deb
 835bb727f110352e3fe2e708f77c76b1f21add18 73556 
nbd-server-dbgsym_3.15.2-1_amd64.deb
 e089475747e2863fefd4eb4db7f6be3addb43e77 74496 nbd-server_3.15.2-1_amd64.deb
 6046081b9c0dd49f850290fa225edb05ac63fbb8 7165 nbd_3.15.2-1_amd64.buildinfo
Checksums-Sha256:
 b443e254181235acf1cb37a6d1258fee9ca06f831f3d68360391ed54f66e849f 1992 
nbd_3.15.2-1.dsc
 0155e6fd142853ad60172906393e4329ad648656342fb7a3b35de97ce4a82c88 1035356 
nbd_3.15.2.orig.tar.gz
 55dd7d175a30dff7848cf43dec295c0adf647643b7e094fc58fe379414c24570 91409 
nbd_3.15.2-1.diff.gz
 0489c53acd3852b814daeab87de51ffc3f9418883445a6a275ecdddb6ddce6a6 33892 
nbd-client-dbgsym_3.15.2-1_amd64.deb
 

Bug#852929: scalable-cyrfonts: FTBFS: LaTeX requires e-TeX.

[Sascha Steinbiss]

Hi Anton,

>> Switching to ‘luatex' instead of ‘tex’ fixed the issue for me. Please 
>> see attached patch. However, I would be happy if someone could take a 
>> second look. I don’t usually write Cyrillic ;)
> 
> Thanks.  I am uploading the package now. :)

Great, thanks! One more RC bug down.

Cheers
Sascha

Bug#855227: marked as done (qemu: CVE-2017-2630: nbd: oob stack write in client routine drop_sync)

[Debian Bug Tracking System]

Your message dated Wed, 01 Mar 2017 10:04:15 +
with message-id 
and subject line Bug#855227: fixed in qemu 1:2.8+dfsg-3
has caused the Debian Bug report #855227,
regarding qemu: CVE-2017-2630: nbd: oob stack write in client routine drop_sync
to be marked as done.

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

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


-- 
855227: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855227
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qemu
Version: 1:2.8+dfsg-2
Severity: grave
Tags: patch security upstream
Justification: user security hole

Hi,

the following vulnerability was published for qemu.

CVE-2017-2630[0]:
nbd: oob stack write in client routine drop_sync

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-2630
[1] https://lists.gnu.org/archive/html/qemu-devel/2017-02/msg01246.html
[2] http://www.openwall.com/lists/oss-security/2017/02/15/2

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:2.8+dfsg-3

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

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

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

Debian distribution maintenance software
pp.
Michael Tokarev  (supplier of updated qemu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 28 Feb 2017 11:40:18 +0300
Source: qemu
Binary: qemu qemu-system qemu-block-extra qemu-system-common qemu-system-misc 
qemu-system-arm qemu-system-mips qemu-system-ppc qemu-system-sparc 
qemu-system-x86 qemu-user qemu-user-static qemu-user-binfmt qemu-utils 
qemu-guest-agent qemu-kvm
Architecture: source
Version: 1:2.8+dfsg-3
Distribution: unstable
Urgency: high
Maintainer: Debian QEMU Team 
Changed-By: Michael Tokarev 
Description:
 qemu   - fast processor emulator
 qemu-block-extra - extra block backend modules for qemu-system and qemu-utils
 qemu-guest-agent - Guest-side qemu-system agent
 qemu-kvm   - QEMU Full virtualization on x86 hardware
 qemu-system - QEMU full system emulation binaries
 qemu-system-arm - QEMU full system emulation binaries (arm)
 qemu-system-common - QEMU full system emulation binaries (common files)
 qemu-system-mips - QEMU full system emulation binaries (mips)
 qemu-system-misc - QEMU full system emulation binaries (miscellaneous)
 qemu-system-ppc - QEMU full system emulation binaries (ppc)
 qemu-system-sparc - QEMU full system emulation binaries (sparc)
 qemu-system-x86 - QEMU full system emulation binaries (x86)
 qemu-user  - QEMU user mode emulation binaries
 qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user
 qemu-user-static - QEMU user mode emulation binaries (static version)
 qemu-utils - QEMU utilities
Closes: 839986 846497 853002 853006 853996 854032 854729 854730 854731 854893 
855159 855227 855611 855616 855659 855791
Changes:
 qemu (1:2.8+dfsg-3) unstable; urgency=high
 .
   * urgency high due to security fixes
 .
   [ Michael Tokarev ]
   * serial-fix-memory-leak-in-serial-exit-CVE-2017-5579.patch
 Closes: #853002, CVE-2017-5579
   * cirrus-ignore-source-pitch-as-needed-in-blit_is_unsafe.patch
 (needed for the next patch, CVE-2017-2620 fix)
   * cirrus-add-blit_is_unsafe-to-cirrus_bitblt_cputovideo-CVE-2017-2620.patch
 Closes: #855791, CVE-2017-2620
   * nbd_client-fix-drop_sync-CVE-2017-2630.diff
 Closes: #855227, CVE-2017-2630
   * sd-sdhci-check-transfer-mode-register-in-multi-block-CVE-2017-5987.patch
 Closes: #855159, CVE-2017-5987
   * vmxnet3-fix-memory-corruption-on-vlan-header-stripping-CVE-2017-6058.patch
 Closes: #855616, CVE-2017-6058
   * 3 CVE fixes from upstream for #853996:
 sd-sdhci-check-data-length-during-dma_memory_read-CVE-2017-5667.patch
 megasas-fix-guest-triggered-memory-leak-CVE-2017-5856.patch
 

Bug#855791: marked as done (qemu: CVE-2017-2620: cirrus_bitblt_cputovideo does not check if memory region is safe)

[Debian Bug Tracking System]

Your message dated Wed, 01 Mar 2017 10:04:15 +
with message-id 
and subject line Bug#855791: fixed in qemu 1:2.8+dfsg-3
has caused the Debian Bug report #855791,
regarding qemu: CVE-2017-2620: cirrus_bitblt_cputovideo does not check if 
memory region is safe
to be marked as done.

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

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


-- 
855791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855791
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qemu
Version: 1:2.8+dfsg-2
Severity: grave
Tags: upstream security patch

Hi,

the following vulnerability was published for qemu.

CVE-2017-2620[0]:
display: cirrus: out-of-bounds access issue while in cirrus_bitblt_cputovideo

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2017-2620
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-2620
[1] https://lists.gnu.org/archive/html/qemu-devel/2017-02/msg04700.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:2.8+dfsg-3

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

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

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

Debian distribution maintenance software
pp.
Michael Tokarev  (supplier of updated qemu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 28 Feb 2017 11:40:18 +0300
Source: qemu
Binary: qemu qemu-system qemu-block-extra qemu-system-common qemu-system-misc 
qemu-system-arm qemu-system-mips qemu-system-ppc qemu-system-sparc 
qemu-system-x86 qemu-user qemu-user-static qemu-user-binfmt qemu-utils 
qemu-guest-agent qemu-kvm
Architecture: source
Version: 1:2.8+dfsg-3
Distribution: unstable
Urgency: high
Maintainer: Debian QEMU Team 
Changed-By: Michael Tokarev 
Description:
 qemu   - fast processor emulator
 qemu-block-extra - extra block backend modules for qemu-system and qemu-utils
 qemu-guest-agent - Guest-side qemu-system agent
 qemu-kvm   - QEMU Full virtualization on x86 hardware
 qemu-system - QEMU full system emulation binaries
 qemu-system-arm - QEMU full system emulation binaries (arm)
 qemu-system-common - QEMU full system emulation binaries (common files)
 qemu-system-mips - QEMU full system emulation binaries (mips)
 qemu-system-misc - QEMU full system emulation binaries (miscellaneous)
 qemu-system-ppc - QEMU full system emulation binaries (ppc)
 qemu-system-sparc - QEMU full system emulation binaries (sparc)
 qemu-system-x86 - QEMU full system emulation binaries (x86)
 qemu-user  - QEMU user mode emulation binaries
 qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user
 qemu-user-static - QEMU user mode emulation binaries (static version)
 qemu-utils - QEMU utilities
Closes: 839986 846497 853002 853006 853996 854032 854729 854730 854731 854893 
855159 855227 855611 855616 855659 855791
Changes:
 qemu (1:2.8+dfsg-3) unstable; urgency=high
 .
   * urgency high due to security fixes
 .
   [ Michael Tokarev ]
   * serial-fix-memory-leak-in-serial-exit-CVE-2017-5579.patch
 Closes: #853002, CVE-2017-5579
   * cirrus-ignore-source-pitch-as-needed-in-blit_is_unsafe.patch
 (needed for the next patch, CVE-2017-2620 fix)
   * cirrus-add-blit_is_unsafe-to-cirrus_bitblt_cputovideo-CVE-2017-2620.patch
 Closes: #855791, CVE-2017-2620
   * nbd_client-fix-drop_sync-CVE-2017-2630.diff
 Closes: #855227, CVE-2017-2630
   * sd-sdhci-check-transfer-mode-register-in-multi-block-CVE-2017-5987.patch
 Closes: #855159, CVE-2017-5987
   * vmxnet3-fix-memory-corruption-on-vlan-header-stripping-CVE-2017-6058.patch
 Closes: #855616, CVE-2017-6058
   * 3 CVE fixes from upstream for #853996:
 sd-sdhci-check-data-length-during-dma_memory_read-CVE-2017-5667.patch
 megasas-fix-guest-triggered-memory-leak-CVE-2017-5856.patch
 

Bug#853006: marked as done (qemu: CVE-2016-9602: 9p: virtfs allows guest to access host filesystem)

[Debian Bug Tracking System]

Your message dated Wed, 01 Mar 2017 10:04:15 +
with message-id 
and subject line Bug#853006: fixed in qemu 1:2.8+dfsg-3
has caused the Debian Bug report #853006,
regarding qemu: CVE-2016-9602: 9p: virtfs allows guest to access host filesystem
to be marked as done.

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

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


-- 
853006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853006
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qemu
Version: 1:2.8+dfsg-1
Severity: grave
Tags: security upstream

Hi,

the following vulnerability was published for qemu.

Rationale: I'm raising the issue for now as grave severity, since a
privileged user inside guest could use this flaw to access host file
system beyond the shared folder and potentially escalating their
privileges on a host. But note as well, that the original proposed
patch is not fixing the issue, so upstream is still working on a
fix[1].

CVE-2016-9602[0]:
9p: virtfs allows guest to access host filesystem

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2016-9602
[1] http://www.openwall.com/lists/oss-security/2017/01/17/14
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1413929

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:2.8+dfsg-3

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

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

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

Debian distribution maintenance software
pp.
Michael Tokarev  (supplier of updated qemu package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 28 Feb 2017 11:40:18 +0300
Source: qemu
Binary: qemu qemu-system qemu-block-extra qemu-system-common qemu-system-misc 
qemu-system-arm qemu-system-mips qemu-system-ppc qemu-system-sparc 
qemu-system-x86 qemu-user qemu-user-static qemu-user-binfmt qemu-utils 
qemu-guest-agent qemu-kvm
Architecture: source
Version: 1:2.8+dfsg-3
Distribution: unstable
Urgency: high
Maintainer: Debian QEMU Team 
Changed-By: Michael Tokarev 
Description:
 qemu   - fast processor emulator
 qemu-block-extra - extra block backend modules for qemu-system and qemu-utils
 qemu-guest-agent - Guest-side qemu-system agent
 qemu-kvm   - QEMU Full virtualization on x86 hardware
 qemu-system - QEMU full system emulation binaries
 qemu-system-arm - QEMU full system emulation binaries (arm)
 qemu-system-common - QEMU full system emulation binaries (common files)
 qemu-system-mips - QEMU full system emulation binaries (mips)
 qemu-system-misc - QEMU full system emulation binaries (miscellaneous)
 qemu-system-ppc - QEMU full system emulation binaries (ppc)
 qemu-system-sparc - QEMU full system emulation binaries (sparc)
 qemu-system-x86 - QEMU full system emulation binaries (x86)
 qemu-user  - QEMU user mode emulation binaries
 qemu-user-binfmt - QEMU user mode binfmt registration for qemu-user
 qemu-user-static - QEMU user mode emulation binaries (static version)
 qemu-utils - QEMU utilities
Closes: 839986 846497 853002 853006 853996 854032 854729 854730 854731 854893 
855159 855227 855611 855616 855659 855791
Changes:
 qemu (1:2.8+dfsg-3) unstable; urgency=high
 .
   * urgency high due to security fixes
 .
   [ Michael Tokarev ]
   * serial-fix-memory-leak-in-serial-exit-CVE-2017-5579.patch
 Closes: #853002, CVE-2017-5579
   * cirrus-ignore-source-pitch-as-needed-in-blit_is_unsafe.patch
 (needed for the next patch, CVE-2017-2620 fix)
   * cirrus-add-blit_is_unsafe-to-cirrus_bitblt_cputovideo-CVE-2017-2620.patch
 Closes: #855791, CVE-2017-2620
   * nbd_client-fix-drop_sync-CVE-2017-2630.diff
 Closes: #855227, CVE-2017-2630
   * sd-sdhci-check-transfer-mode-register-in-multi-block-CVE-2017-5987.patch
 Closes: #855159, CVE-2017-5987
   * 

Bug#855494: mgltools-pmv: runPmv does not start

[Ghislain Vaillant]

On Sun, 19 Feb 2017 09:00:07 +0100 Andreas Tille  wrote:

Package: mgltools-pmv
Version: 1.5.7-1
Severity: grave
Justification: renders package unusable

Hi,

I intended to reproduce #855485 but I was running into a different
problem:

$ runPmv
Run PMV from  /usr/lib/python2.7/dist-packages/Pmv
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/Pmv/__init__.py", line 378, in runPmv
from Pmv.moleculeViewer import MoleculeViewer
  File "/usr/lib/python2.7/dist-packages/Pmv/moleculeViewer.py", line 16, in 

from MolKit.molecule import Atom, AtomSet, BondSet, Molecule , MoleculeSet
  File "/usr/lib/python2.7/dist-packages/MolKit/molecule.py", line 26, in 

from numpy.oldnumeric import sum, array, less_equal, take, nonzero, argsort
ImportError: No module named oldnumeric


Not too surprising considering that the numpy.oldnumeric modules was 
removed since Numpy 1.9 [1], so it has been broken for a long time 
without people noticing.


We could port the code base to the current Numpy API, but I am not sure 
whether we will have enough of a user-base to validate it (see above) 
and how much effort it will take. Besides, the software did not receive 
updates for years so we would probably be maintaining this effort on our 
own.


Based on this 2 comments, one might ask whether it is worth maintaining 
a package for this piece of software.


[1] https://docs.scipy.org/doc/numpy/reference/routines.oldnumeric.html

Cheers,
Ghis

Processed: tagging 853006

[Debian Bug Tracking System]

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

> tags 853006 + pending
Bug #853006 [src:qemu] qemu: CVE-2016-9602: 9p: virtfs allows guest to access 
host filesystem
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#856457: sogo-connector: FTBFS: python: can't open file '/usr/lib/icedove-devel/sdk/bin/typelib.py': [Errno 2] No such file or directory

[Chris Lamb]

Source: sogo-connector
Version: 31.0.3-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Dear Maintainer,

sogo-connector fails to build from source in unstable/amd64:

  […]

 dh_auto_configure
 debian/rules override_dh_auto_build
  make[1]: Entering directory '«BUILDDIR»'
  # rebuilding the *.xpt file
  cd components; \
make clean && make
  make[2]: Entering directory '«BUILDDIR»/components'
  rm -f sogo-connector.xpt NotificationManager.xpt SyncProgressManager.xpt 
ContextManager.xpt
  make[2]: Leaving directory '«BUILDDIR»/components'
  make[2]: Entering directory '«BUILDDIR»/components'
  python /usr/lib/icedove-devel/sdk/bin/typelib.py -o NotificationManager.xpt 
NotificationManager.idl -I /usr/lib/icedove-devel/idl
  python: can't open file '/usr/lib/icedove-devel/sdk/bin/typelib.py': [Errno 
2] No such file or directory
  Makefile:13: recipe for target 'NotificationManager.xpt' failed
  make[2]: *** [NotificationManager.xpt] Error 2
  make[2]: Leaving directory '«BUILDDIR»/components'
  debian/rules:11: recipe for target 'override_dh_auto_build' failed
  make[1]: *** [override_dh_auto_build] Error 2
  make[1]: Leaving directory '«BUILDDIR»'
  debian/rules:8: recipe for target 'build' failed
  make: *** [build] Error 2
  dpkg-buildpackage: error: debian/rules build gave error exit status 2

  […]

The full build log is attached.


Regards,

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


sogo-connector.31.0.3-2.unstable.amd64.log.txt.gz
Description: Binary data