Bug#904796: chromium for arm64 lacks security updates

[Mikulas Patocka]

On Thu, 2 Aug 2018, Riku Voipio wrote:


tags 904796 + patch upstream
thanks

On Mon, Jul 30, 2018 at 01:37:57AM +, Riku Voipio wrote:

On Sat, Jul 28, 2018 at 05:23:14PM -0400, Michael Gilbert wrote:

Chromium on arm64 in Debian Stretch stopped receiving security updates.
Chromium for i386, amd64 and armhf received updates for versions 67 and
68, however chromium for arm64 is stuck on version 66.



There was a build error in crashpad on arm64 introduced by upstream
chromium 67.  A patch fixing that has been included with the last two
security uploads, so I'm not sure why those builds would have failed.


Security build logs are not available, so I missed that. I'll try to reproduce.


The issue seems to be binutils in stable not supporting LR = x30 alias. I've
built a fixed version. I'm travelling now, but once I get back, I'll test the
fix and submit patch upstream. Similar issue for armhf, but we don't have
chromium/armhf on stable, so it's not as important.


There is "chromium:armhf" version "68.0.3440.75-1~deb9u1" in the Debian 
Stretch repository. (it doesn't work on arm64, it complains that it can't 
spawn the GPU process - the 32-bit syscall emulation is likely incomplete)



Riku

Bug#904902: marked as done (util-linux: trying to overwrite '/usr/share/bash-completion/completions/su')

[Debian Bug Tracking System]

Your message dated Fri, 03 Aug 2018 09:50:08 +
with message-id 
and subject line Bug#905303: fixed in util-linux 2.32-0.4
has caused the Debian Bug report #905303,
regarding util-linux: trying to overwrite 
'/usr/share/bash-completion/completions/su'
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.)


-- 
905303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: util-linux
Version: 2.32-0.3
Severity: important

Hello,

Upgrading to util-linux 2.32-0.3 does not work while bash-completion
1:2.1-4.3 is installed:

Preparing to unpack .../util-linux_2.32-0.3_hurd-i386.deb ...
Unpacking util-linux (2.32-0.3) over (2.29.2-1) ...
Replacing files in old package login (1:4.4-4.1) ...
dpkg: error processing archive 
/var/cache/apt/archives/util-linux_2.32-0.3_hurd-i386.deb (--unpack):
 trying to overwrite '/usr/share/bash-completion/completions/su', which is also 
in package bash-completion 1:2.1-4.3
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Selecting previously unselected package fdisk.
dpkg: considering deconfiguration of util-linux, which would be broken by 
installation of fdisk ...
dpkg: no, util-linux is essential, will not deconfigure
 it in order to enable installation of fdisk
dpkg: error processing archive 
/var/cache/apt/archives/fdisk_2.32-0.3_hurd-i386.deb (--unpack):
 installing fdisk would break existing software
Errors were encountered while processing:
 /var/cache/apt/archives/util-linux_2.32-0.3_hurd-i386.deb
 /var/cache/apt/archives/fdisk_2.32-0.3_hurd-i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Best regards,
Göran
--- End Message ---
--- Begin Message ---
Source: util-linux
Source-Version: 2.32-0.4

We believe that the bug you reported is fixed in the latest version of
util-linux, 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 905...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Henriksson  (supplier of updated util-linux 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: Fri, 03 Aug 2018 10:55:29 +0200
Source: util-linux
Binary: util-linux util-linux-locales mount bsdutils fdisk fdisk-udeb libblkid1 
libblkid1-udeb libblkid-dev libfdisk1 libfdisk1-udeb libfdisk-dev libmount1 
libmount1-udeb libmount-dev libsmartcols1 libsmartcols1-udeb libsmartcols-dev 
libuuid1 uuid-runtime libuuid1-udeb uuid-dev util-linux-udeb setpriv rfkill
Architecture: source
Version: 2.32-0.4
Distribution: unstable
Urgency: medium
Maintainer: LaMont Jones 
Changed-By: Andreas Henriksson 
Description:
 bsdutils   - basic utilities from 4.4BSD-Lite
 fdisk  - collection of partitioning utilities
 fdisk-udeb - Manually partition a hard drive (fdisk) (udeb)
 libblkid-dev - block device ID library - headers and static libraries
 libblkid1  - block device ID library
 libblkid1-udeb - stripped down block device ID library, for debian-installer 
(udeb)
 libfdisk-dev - fdisk partitioning library - headers and static libraries
 libfdisk1  - fdisk partitioning library
 libfdisk1-udeb - stripped down fdisk partitioning library, for 
debian-installer (udeb)
 libmount-dev - device mounting library - headers and static libraries
 libmount1  - device mounting library
 libmount1-udeb - stripped down device mounting library, for debian-installer 
(udeb)
 libsmartcols-dev - smart column output alignment library - headers and static 
librar
 libsmartcols1 - smart column output alignment library
 libsmartcols1-udeb - stripped down smart column output aligment library, for 
debian-in (udeb)
 libuuid1   - Universally Unique ID library
 libuuid1-udeb - stripped down Universally Unique ID library, for 
debian-installer (udeb)
 mount  - tools for mounting and manipulating filesystems
 rfkill - tool for enabling and disabling wireless devices
 setpriv- tool to run a program with different Linux privilege settings
 util-linux - miscellaneous system utilities
 util-linux-locales - locales files for util-linux
 util-linux-udeb - stripped down miscellaneous system utilities, for 
debian-installe (udeb)
 uuid-

Bug#899441: marked as done (aspell-ar: Invalid maintainer address debian-arabic-packa...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Fri, 03 Aug 2018 09:49:03 +
with message-id 
and subject line Bug#899441: fixed in aspell-ar 0.0.20060329-6
has caused the Debian Bug report #899441,
regarding aspell-ar: Invalid maintainer address 
debian-arabic-packa...@lists.alioth.debian.org
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.)


-- 
899441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:aspell-ar
Version: 0.0.20060329-5
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of aspell-ar,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package aspell-ar since the list address
debian-arabic-packa...@lists.alioth.debian.org used in the Maintainer:
field was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
debian-arabic-packa...@lists.alioth.debian.org is 6.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: aspell-ar
Source-Version: 0.0.20060329-6

We believe that the bug you reported is fixed in the latest version of
aspell-ar, 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 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lior Kaplan  (supplier of updated aspell-ar 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: Fri, 03 Aug 2018 11:56:04 +0300
Source: aspell-ar
Binary: aspell-ar
Architecture: source
Version: 0.0.20060329-6
Distribution: unstable
Urgency: medium
Maintainer: Lior Kaplan 
Changed-By: Lior Kaplan 
Description:
 aspell-ar  - Arabic dictionary for aspell
Closes: 899441
Changes:
 aspell-ar (0.0.20060329-6) unstable; urgency=medium
 .
   * Update maintainer address (Closes: #899441)
Checksums-Sha1:
 08a5473eed6f02f46286953f190dd6188e8960b3 1950 aspell-ar_0.0.20060329-6.dsc
 b195a1043dd3e05bf1bac3a1d02a7b943e394bf7 2488 
aspell-ar_0.0.20060329-6.debian.tar.xz
 7f0e22c68382e4dd12314e023553a0b6a4a51b9e 5638 
aspell-ar_0.0.20060329-6_amd64.buildinfo
Checksums-Sha256:
 18803bd587c00d41e953e65295ff12a5a7238ca622acc836b57e4c20401f1526 1950 
aspell-ar_0.0.20060329-6.dsc
 46d40f89caef9ff9321bf093dcefce3f63ac80fdc5f0763a1bae03b811ed04c5 2488 
aspell-ar_0.0.20060329-6.debian.tar.xz
 c6c6e5148ac96b29663d1f61dc594b25066161737cff154b698545f60d5f9f86 5638 
aspell-ar_0.0.20060329-6_amd64.buildinfo
Files:
 dedbee9c8b63bf51b91dc2d03b03f3fa 1950 text optional 
aspell-ar_0.0.20060329-6.dsc
 8be134ebe332bf39ac59cc112a959924 2488 text optional 
aspell-ar_0.0.20060329-6.debian.tar.xz
 52963e3fbfbec1e7c0361a437eeff904 5638 text

Bug#905303: marked as done (`/usr/share/bash-completion/completions/su` is owned by both util-linux and bash-completion)

[Debian Bug Tracking System]

Your message dated Fri, 03 Aug 2018 09:50:08 +
with message-id 
and subject line Bug#905303: fixed in util-linux 2.32-0.4
has caused the Debian Bug report #905303,
regarding `/usr/share/bash-completion/completions/su` is owned by both 
util-linux and bash-completion
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.)


-- 
905303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: util-linux
Version: 2.32-0.3
Severity: critical

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello util-linux maintainer,

Looping in the bash-completion maintainer too.

On a Stretch system with:
  util-linux_2.32-0.3
  bash-completion_1:2.1-4.3

I get an error performing a full-upgrade to Testing, as both packages
own `/usr/share/bash-completion/completions/su`:

```
Preparing to unpack .../util-linux_2.32-0.3_amd64.deb ...
Unpacking util-linux (2.32-0.3) over (2.29.2-1+deb9u1) ...
Replacing files in old package login (1:4.4-4.1) ...
dpkg: error processing archive 
/var/cache/apt/archives/util-linux_2.32-0.3_amd64.deb (--unpack):
 trying to overwrite '/usr/share/bash-completion/completions/su', which is 
also in package bash-completion 1:2.1-4.3   
 
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
dpkg: considering deconfiguration of util-linux, which would be broken by 
installation of login ...
dpkg: no, util-linux is essential, will not deconfigure
 it in order to enable installation of login
dpkg: error processing archive 
/var/cache/apt/archives/login_1%3a4.5-1.1_amd64.deb (--unpack):
 installing login would break existing software
Errors were encountered while processing:
 /var/cache/apt/archives/util-linux_2.32-0.3_amd64.deb
 /var/cache/apt/archives/login_1%3a4.5-1.1_amd64.deb
```



After a brief look at both source packages, I can see that meanwhile the last
util-linux doesn't ship that file, bash-completion does. Also, util-linux
declares a Break and Conflicts with specific versions of bash-completion, so I
have assumed that the bug report goes indeed against util-linux.

Please don't hesitate to reassign or reduce severity if needed.


Kind regards,
Víctor Cuadrado



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

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

Versions of packages util-linux depends on:
ii  fdisk  2.32-0.3
ii  libaudit1  1:2.8.3-1+b1
ii  libblkid1  2.32-0.3
ii  libc6  2.27-5
ii  libmount1  2.32-0.3
ii  libpam0g   1.1.8-3.7
ii  libselinux12.8-1+b1
ii  libsmartcols1  2.32-0.3
ii  libsystemd0239-7
ii  libtinfo6  6.1+20180714-1
ii  libudev1   239-7
ii  libuuid1   2.32-0.3
ii  login  1:4.5-1.1
ii  zlib1g 1:1.2.11.dfsg-1

util-linux recommends no packages.

Versions of packages util-linux suggests:
ii  dosfstools  4.1-2
ii  kbd 2.0.4-3
ii  util-linux-locales  2.32-0.3

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEELLKv6mdE0z94m2FAIj8VylqvDngFAltjVJEACgkQIj8Vylqv
Dnge/Af7BhE6AP0QyxzqiBHCu9atZkAzIIYp5QImB7A0T6Jdtp75xmFiNaEafbbI
HkHHvp7T373VeEFN+WoGCcv1atsPNrnuixa5WnEVBg5lbgzQWVOQ/HWtBDlHxybg
MdgzDhZJGM/LMR+UZiIfJdy2YpOsVq4i40ezTgZwRqTn6JjZyPtQtBEjQwxTF6rQ
KeK8rZqxVnkSVX19l710AAeLWPiDjglYE+msxUAqPn5/AJbdt52+AV1+NyQm0z7y
lPbcVxv7SP5cxHNJU5co5nHaJbNli21ebEVABoh+fC3kqWtbOunlI0wlYHL+NX7b
nzioou4jaj91PP3gk/DfH33bN7fJug==
=NKh+
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: util-linux
Source-Version: 2.32-0.4

We believe that the bug you reported is fixed in the latest version of
util-linux, 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 905...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance 

Bug#905191: marked as done (libecm1-dev: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

[Debian Bug Tracking System]

Your message dated Fri, 03 Aug 2018 10:04:13 +
with message-id 
and subject line Bug#905191: fixed in gmp-ecm 7.0.4+ds-3
has caused the Debian Bug report #905191,
regarding libecm1-dev: unhandled symlink to directory conversion: 
/usr/share/doc/PACKAGE
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.)


-- 
905191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905191
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libecm1-dev
Version: 7.0.4+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old version of the package shipped a
symlink but that was later replaced by a real (and non-empty)
directory. This kind of overwriting another package's files cannot be
detected by dpkg.

This was observed on the following upgrade paths:

  stretch -> buster

For /usr/share/doc/PACKAGE this may not be problematic as long as both
packages are installed, ship byte-for-byte identical files and are
upgraded in lockstep. But once one of the involved packages gets
removed, the other one will lose its documentation files, too,
including the copyright file, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/#copyright-information

For other overwritten locations anything interesting may happen.

Note that dpkg intentionally does not replace directories with symlinks
and vice versa, you need the maintainer scripts to do this.
See in particular the end of point 4 in
https://www.debian.org/doc/debian-policy/#details-of-unpack-phase-of-installation-or-upgrade

It is recommended to use the dpkg-maintscript-helper commands
'dir_to_symlink' and 'symlink_to_dir' (available since dpkg 1.17.14)
to perform the conversion, ideally using d/$PACKAGE.maintscript.
Do not forget to add 'Pre-Depends: ${misc:Pre-Depends}' in d/control.
See dpkg-maintscript-helper(1) and dh_installdeb(1) for details.


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

0m29.3s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/libecm1-dev/AUTHORS (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/AUTHORS (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/NEWS.gz (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/NEWS.gz (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/README.gz (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/README.gz (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/README.lib.gz (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/README.lib.gz (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/changelog.Debian.gz (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/changelog.Debian.gz (libecm1-dev-common)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/changelog.gz (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/changelog.gz (libecm1-dev-common)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/copyright (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/copyright (libecm1-dev-common)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/examples (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/examples (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/examples/Makefile (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/examples/Makefile (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common
  /usr/share/doc/libecm1-dev/examples/ecmfactor.c (libecm1-dev:amd64) != 
/usr/share/doc/libecm1-dev-common/examples/ecmfactor.c (?)
/usr/share/doc/libecm1-dev -> libecm1-dev-common


cheers,

Andreas


libecm1-dev_7.0.4+ds-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gmp-ecm
Source-Version: 7.0.4+ds-3

We believe that the bug you reported is fixed in the latest version of
gmp-ecm, 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 905...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jerome Benoit  (supplier of updated 

Bug#899931: marked as done (aspell-ar-large: Invalid maintainer address debian-arabic-packa...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Fri, 03 Aug 2018 10:33:58 +
with message-id 
and subject line Bug#899931: fixed in aspell-ar-large 1.2-0-4
has caused the Debian Bug report #899931,
regarding aspell-ar-large: Invalid maintainer address 
debian-arabic-packa...@lists.alioth.debian.org
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.)


-- 
899931: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899931
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:aspell-ar-large
Version: 1.2-0-3
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of aspell-ar-large,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package aspell-ar-large since the list address
debian-arabic-packa...@lists.alioth.debian.org used in the Maintainer:
field was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
debian-arabic-packa...@lists.alioth.debian.org is 6.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: aspell-ar-large
Source-Version: 1.2-0-4

We believe that the bug you reported is fixed in the latest version of
aspell-ar-large, 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 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lior Kaplan  (supplier of updated aspell-ar-large 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: Fri, 03 Aug 2018 12:45:32 +0300
Source: aspell-ar-large
Binary: aspell-ar-large
Architecture: source
Version: 1.2-0-4
Distribution: unstable
Urgency: medium
Maintainer: Lior Kaplan 
Changed-By: Lior Kaplan 
Description:
 aspell-ar-large - Large Arabic dictionary for aspell
Closes: 777284 899931
Changes:
 aspell-ar-large (1.2-0-4) unstable; urgency=medium
 .
   * Update maintainer address (Closes: #899931)
   * Remove timpstamp from genenreated files (Closes: #777284)
Checksums-Sha1:
 d1f636017a3af81552fe67154d8da016815ceb71 1961 aspell-ar-large_1.2-0-4.dsc
 22a16cca10acb8fad3d458b25b0031b4aebadb08 3576 
aspell-ar-large_1.2-0-4.debian.tar.xz
 ac5f2411d1154dc9e85467aa5805c2f3f10fd08e 5645 
aspell-ar-large_1.2-0-4_amd64.buildinfo
Checksums-Sha256:
 a040a305fcfe9f056bfeb35f5b4759b9d4c5be0ac4b3aa86834a9af0fc07b25e 1961 
aspell-ar-large_1.2-0-4.dsc
 882ef85856a002fac7cb1fea76828076b4cb9a1960b4c06bae872ce5a0d1c757 3576 
aspell-ar-large_1.2-0-4.debian.tar.xz
 592fb5e272da745121ec18e3cf8c179718fbd3838c7fc0a02ddaaaec0329943b 5645 
aspell-ar-large_1.2-0-4_amd64.buildinfo
Files:
 36e09407d9a222a5be387457b20b211d 1961 text optional aspell-ar-large_1.2-0-4.dsc
 11a71f3c20c862519ee142159031606

Processed: Re: Bug#905300: gfan: FTBFS on 32bit architectures: test 0602ResultantFanProjection hangs

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 jen...@imf.au.dk
Bug #905300 [src:gfan] gfan: FTBFS on 32bit architectures: test 
0602ResultantFanProjection hangs
Set Bug forwarded-to-address to 'jen...@imf.au.dk'.

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

Bug#905300: gfan: FTBFS on 32bit architectures: test 0602ResultantFanProjection hangs

[Doug Torrance]

Control: forwarded -1 jen...@imf.au.dk

Hello!

I am one of the maintainers of gfan in Debian.  We recently received the 
following bug report.  In particular, one of the tests introduced in 
version 0.6 hangs on 32-bit systems:


On 08/02/2018 01:46 PM, Andreas Beckmann wrote:

Source: gfan
Version: 0.6.2-1~exp1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

gfan/experimental FTBFS on all 32bit architectures since a test hangs:

https://buildd.debian.org/status/package.php?p=gfan&suite=experimental

[...]
Running command:"cat testsuite/0602ResultantFanProjection/outputNew"
E: Build killed with signal TERM after 150 minutes of inactivity


Thanks!
Doug Torrance

Bug#905338: snapper-gui: Namespace GtkSource not available

[Mykola Nikishov]

Package: snapper-gui
Version: 0git.960a94834f-1
Severity: grave
Justification: renders package unusable

--8<---cut here---start->8---
$ snapper-gui
Traceback (most recent call last):
  File "/usr/bin/snapper-gui", line 11, in 
load_entry_point('snappergui==0.1', 'gui_scripts', 'snapper-gui')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 476, in 
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2700, 
in load_entry_point
return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2318, 
in load
return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2324, 
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3/dist-packages/snappergui/__init__.py", line 5, in 

gi.require_version("GtkSource", "3.0")
  File "/usr/lib/python3/dist-packages/gi/__init__.py", line 130, in 
require_version
raise ValueError('Namespace %s not available' % namespace)
ValueError: Namespace GtkSource not available
--8<---cut here---end--->8---

Installing gir1.2-gtksource-3.0 fixes this.

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

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

Versions of packages snapper-gui depends on:
ii  python3  3.6.6-1

snapper-gui recommends no packages.

snapper-gui suggests no packages.

-- no debconf information

Processed: your mail

[Debian Bug Tracking System]

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

> tags 902190 fixed-upstream
Bug #902190 [vcftools] vcftools: CVE-2018-11099 CVE-2018-11129 CVE-2018-11130
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Processed: Re: Bug#905327: Some apps hang randomly

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #905327 [kde-style-qtcurve-qt5] Some apps hang randomly
Severity set to 'grave' from 'important'

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

Bug#904579: marked as done (python3-mastodon: fails to install with Python 3.7)

[Debian Bug Tracking System]

Your message dated Fri, 03 Aug 2018 12:19:17 +
with message-id 
and subject line Bug#904579: fixed in python-mastodon 1.3.0-1
has caused the Debian Bug report #904579,
regarding python3-mastodon: fails to install with Python 3.7
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.)


-- 
904579: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-mastodon
Version: 1.2.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

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 python3-mastodon (1.2.2-1) ...
File "/usr/lib/python3/dist-packages/mastodon/Mastodon.py", line 1384
  def stream_user(self, listener, async=False):
  ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-mastodon (--configure):
   installed python3-mastodon package post-installation script subprocess 
returned error exit status 1


"async" has become a reserved keyword in Python 3.7


cheers,

Andreas


python3-mastodon=1.2.2-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: python-mastodon
Source-Version: 1.3.0-1

We believe that the bug you reported is fixed in the latest version of
python-mastodon, 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 904...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated python-mastodon 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: Fri, 03 Aug 2018 21:51:10 +1000
Source: python-mastodon
Binary: python3-mastodon
Architecture: source all
Version: 1.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Craig Small 
Changed-By: Craig Small 
Description:
 python3-mastodon - Library for the Mastodon API (Python 3)
Closes: 904579
Changes:
 python-mastodon (1.3.0-1) unstable; urgency=medium
 .
   * New upstream release
   * async option changed to run_async Closes: #904579
   * Remove dependency on http_ece
Checksums-Sha1:
 ce304ebea5a061ff4f000d716a8f33bcca7f 2064 python-mastodon_1.3.0-1.dsc
 81e7a857bbc0559dadccc2a5b92da81d6caacb54 292752 
python-mastodon_1.3.0.orig.tar.xz
 44e093ef56dca0a4922dffa79a451be3fbbc74b4 3024 
python-mastodon_1.3.0-1.debian.tar.xz
 4feaadb715033059e04c6b6f9987bd756c7a79ae 6360 
python-mastodon_1.3.0-1_amd64.buildinfo
 4f1e6fe2a3ef0a5cbadd867f7b5d7814e2f68b49 23584 python3-mastodon_1.3.0-1_all.deb
Checksums-Sha256:
 1a29ebf432c13e61047be6601c2a4377943182bc811dfe51ea71cdaff75aeec7 2064 
python-mastodon_1.3.0-1.dsc
 b68feea3787f3950562f0c974504497a445e548ea4cc1d063875833f2265d87d 292752 
python-mastodon_1.3.0.orig.tar.xz
 0c65ec8252cf6880f3503cd4e09b3f5b0d0e7120e92c4efa09eda28426898d69 3024 
python-mastodon_1.3.0-1.debian.tar.xz
 591926964ee2a14caf82eb74977513d517179464c435742bb8f7fd118e3d1940 6360 
python-mastodon_1.3.0-1_amd64.buildinfo
 8e2c51586fb96fa384ffedb32b2d52c4735f3dc29b524993cc130ae4755eaa46 23584 
python3-mastodon_1.3.0-1_all.deb
Files:
 fc3cdd40222ceabdd29b56b818bab133 2064 python optional 
python-mastodon_1.3.0-1.dsc
 67ada06397ba57a64b53b4a2f89b0252 292752 python optional 
python-mastodon_1.3.0.orig.tar.xz
 44da0d877d52d65b2e78b888778a7c82 3024 python optional 
python-mastodon_1.3.0-1.debian.tar.xz
 98803181a9d47d06d876d2b9a8f8d4d6 6360 python optional 
python-mastodon_1.3.0-1_amd64.buildinfo
 452f6e8bdb92fa261e3c7b6d4b8ea887 23584 python optional 
python3-mastodon_1.3.0-1_all.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXT3w9TizJ8CqeneiAiFmwP88hOMFAltkRQAACgkQAiFmwP88
hOM8Pw/+Pz7yy7uFnGzrN1HN5EV5e7fzU/4RqZsZLXy6Nk8SwjcIXW9aaEKCFv/m
BuFehHhxy6zeSnYhD+y2hye++pT1hamlgk+xhthZGmRe3hUkjsaiC1R38Y54F9ey
oUGXOqqGh/uqb0s9prDQ9iGtNKlBR9/3l5/elL1BIo5YdbX2loUfyBM/PSjph4hJ
JM4dIJ/QZ7r8/1vS89aCs0PaOzOwtToPVY9IGHo6+19vtN/joZ6mkAI5rUtp/df1
AMgxEYgORJGvgtY6soNbVeI5msy139y6JMDcUD9XYaDl47DJmZGsjyirD6om9PMw
W80jU6WHXrvR4w

Bug#905343: mlbstreamer: missing Depends: python3-distutils

[Andreas Beckmann]

Package: mlbstreamer
Version: 0.0.10-2
Severity: serious

$ mlbplay
Traceback (most recent call last):
  File "/usr/bin/mlbplay", line 11, in 
load_entry_point('mlbstreamer==0.0.10', 'console_scripts', 'mlbplay')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 476, in 
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2700, 
in load_entry_point
return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2318, 
in load
return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2324, 
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3/dist-packages/mlbstreamer/play.py", line 16, in 

from . import config
  File "/usr/lib/python3/dist-packages/mlbstreamer/config.py", line 13, in 

import distutils.spawn
ModuleNotFoundError: No module named 'distutils.spawn'


Andreas

Bug#905186: marked as done (uim-qt5-immodule: missing Breaks+Replaces: uim-qt5 (<< 1:1.8.6+gh20161003.0.d63dadd-5~exp1))

[Debian Bug Tracking System]

Your message dated Fri, 03 Aug 2018 12:53:50 +
with message-id 
and subject line Bug#905186: fixed in uim 1:1.8.8-3
has caused the Debian Bug report #905186,
regarding uim-qt5-immodule: missing Breaks+Replaces: uim-qt5 (<< 
1:1.8.6+gh20161003.0.d63dadd-5~exp1)
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.)


-- 
905186: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905186
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: uim-qt5-immodule
Version: 1:1.8.8-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'stretch'.
It installed fine in 'stretch', then the upgrade to 'buster' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/#overwriting-files-and-replacing-packages-replaces

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

  Selecting previously unselected package uim-qt5-immodule:amd64.
  Preparing to unpack .../32-uim-qt5-immodule_1%3a1.8.8-2_amd64.deb ...
  Unpacking uim-qt5-immodule:amd64 (1:1.8.8-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-sqVbwc/32-uim-qt5-immodule_1%3a1.8.8-2_amd64.deb 
(--unpack):
   trying to overwrite 
'/usr/lib/x86_64-linux-gnu/qt5/plugins/platforminputcontexts/libuimplatforminputcontextplugin.so',
 which is also in package uim-qt5 1:1.8.6+gh20161003.0.d63dadd-2
  Preparing to unpack .../33-uim-qt5_1%3a1.8.8-2_amd64.deb ...
  Unpacking uim-qt5 (1:1.8.8-2) over (1:1.8.6+gh20161003.0.d63dadd-2) ...

The other *-immodule packages might have similar problems.


cheers,

Andreas


task-japanese-desktop_3.44.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: uim
Source-Version: 1:1.8.8-3

We believe that the bug you reported is fixed in the latest version of
uim, 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 905...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
HIGUCHI Daisuke (VDR dai)  (supplier of updated uim 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: Fri, 03 Aug 2018 21:26:06 +0900
Source: uim
Binary: uim uim-plugins uim-data libuim8 libuim-scm0 libuim-custom2 libuim-dev 
uim-gtk2.0 uim-gtk2.0-immodule uim-gtk3 uim-gtk3-immodule uim-qt5 
uim-qt5-immodule uim-xim uim-fep uim-anthy uim-skk uim-el uim-tcode
Architecture: source amd64 all
Version: 1:1.8.8-3
Distribution: unstable
Urgency: medium
Maintainer: HIGUCHI Daisuke (VDR dai) 
Changed-By: HIGUCHI Daisuke (VDR dai) 
Description:
 libuim-custom2 - Universal Input Method - uim-custom API library
 libuim-dev - Universal Input Method - development files
 libuim-scm0 - Universal Input Method - uim-scm API library
 libuim8- Universal Input Method - uim library
 uim- Universal Input Method - main binary package
 uim-anthy  - Universal Input Method - Anthy support metapackage
 uim-data   - Universal Input Method - data files
 uim-el - Universal Input Method - Emacs front end
 uim-fep- Universal Input Method - front end processor
 uim-gtk2.0 - Universal Input Method - GTK+2.x front end
 uim-gtk2.0-immodule - Universal Input Method - GTK+2.x IM-module
 uim-gtk3   - Universal Input Method - GTK+3.x front end
 uim-gtk3-immodule - Universal Input Method - GTK+3.x IM module
 uim-plugins - Universal Input Method - plugin files
 uim-qt5- Universal Input Method - Qt 5.x front end
 uim-qt5-immodule - Universal Input Method - Qt 5.x IM module
 uim-skk- Universal Input Method - SKK support metapackage
 uim-tcode  - Universal Input Method - T-Code support metapackage
 uim-xim- Universal Input Method - XIM compatibility interface
Closes: 905186
Changes:
 uim (1:1.8.8-3) unstable; urgency=medium
 .
   [ HIGUCHI Daisuke (VDR dai) ]
   * d/control: set Breaks+Replaces: uim-qt5 to uim-qt5-immodule
 (Closes: #905186).
Checksums-Sha1:
 1ce31116226513253d25252763f5be08bf2b4720 3212 uim_1.8.8-3.dsc
 d7dd74839f7fc67d42c9a55720368a32af2bd541 35736 uim_1.8.8-3.debian.tar.xz
 d42027b9dbb9621d69e8da74ee1bb7f366cd1487 28692 
libuim-

Bug#903533: yapf FTBFS with Python 3.7 as supported version

[Ana Custura]

Hi Nicholas,

I'm on it

Ana


On 03/08/18 00:41, Nicholas D Steeves wrote:
> I hope this bug is fixed before 21 Aug, because yapf is marked for
> autoremoval on the 23rd, and this will result in elpy's autoremoval
> that same day.
>
> Cheers,
> Nicholas




signature.asc
Description: OpenPGP digital signature

Bug#900997: (no subject)

[Gerhard A. Dittes]

Hi,

I've just reported this one upstream (as for me it seems that it hasn't been 
happened so far):

https://bugs.kde.org/show_bug.cgi?id=397125

Regards, Gerardo

Processed: raise severity of #901148 to critical because it affect usability of over packages

[Debian Bug Tracking System]

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

> severity 901148 critical
Bug #901148 [timidity] timidity: upgrading to 2.14.0-2 broke sound via 
pulseaudio
Bug #902330 [timidity] timidity: upgrading to 2.14.0-2 broke sound via 
pulseaudio
Severity set to 'critical' from 'important'
Severity set to 'critical' from 'important'
> found 901148 2.14.0-8
Bug #901148 [timidity] timidity: upgrading to 2.14.0-2 broke sound via 
pulseaudio
Bug #902330 [timidity] timidity: upgrading to 2.14.0-2 broke sound via 
pulseaudio
Marked as found in versions timidity/2.14.0-8.
Marked as found in versions timidity/2.14.0-8.
> thanks
Stopping processing here.

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

Processed: Re: Bug#905327: Some apps hang randomly

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #905327 [kde-style-qtcurve-qt5] Some apps hang randomly
Bug 905327 cloned as bug 905354
> reassign -2 kde-style-qtcurve-qt4 1.8.18+git20160320-3d8622c-5
Bug #905354 [kde-style-qtcurve-qt5] Some apps hang randomly
Bug reassigned from package 'kde-style-qtcurve-qt5' to 'kde-style-qtcurve-qt4'.
No longer marked as found in versions qtcurve/1.8.18+git20160320-3d8622c-5.
Ignoring request to alter fixed versions of bug #905354 to the same values 
previously set
Bug #905354 [kde-style-qtcurve-qt4] Some apps hang randomly
Marked as found in versions qtcurve/1.8.18+git20160320-3d8622c-5.

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

Bug#905327: Some apps hang randomly

[Andrey Rahmatullin]

Control: clone -1 -2
Control: reassign -2 kde-style-qtcurve-qt4 1.8.18+git20160320-3d8622c-5

On Fri, Aug 03, 2018 at 04:54:13PM +0500, Andrey Rahmatullin wrote:
> Actually, it seems that any Qt5 app with a menu bar is easily hanged by
> moving the pointer over the menu bar for some time (tested with kmag).
Qt4 apps just segfault.


-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#905356: python3-gnocchiclient: missing Depends: python3-distutils

[Andreas Beckmann]

Package: python3-gnocchiclient
Version: 7.0.1-4
Severity: serious

$ python3-gnocchi
Traceback (most recent call last):
  File "/usr/bin/python3-gnocchi", line 6, in 
from gnocchiclient.shell import main
  File "/usr/lib/python3/dist-packages/gnocchiclient/shell.py", line 36, in 

from gnocchiclient.v1 import resource_cli
  File "/usr/lib/python3/dist-packages/gnocchiclient/v1/resource_cli.py", line 
14, in 
import distutils.util
ModuleNotFoundError: No module named 'distutils.util'


Andreas

Processed: Re: Bug#905145: jakarta-jmeter: FTBFS with Java 9 due to Swing changes

[Debian Bug Tracking System]

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

> tags 905145 + sid buster
Bug #905145 {Done: Emmanuel Bourg } [src:jakarta-jmeter] 
jakarta-jmeter: FTBFS with Java 9 due to Swing changes
Added tag(s) buster and sid.
>
End of message, stopping processing here.

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

Bug#902190: marked as done (vcftools: CVE-2018-11099 CVE-2018-11129 CVE-2018-11130)

[Debian Bug Tracking System]

Your message dated Fri, 03 Aug 2018 15:07:09 +
with message-id 
and subject line Bug#902190: fixed in vcftools 0.1.16-1
has caused the Debian Bug report #902190,
regarding vcftools: CVE-2018-11099 CVE-2018-11129 CVE-2018-11130
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.)


-- 
902190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902190
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: vcftools
Severity: grave
Tags: security

Please see
http://seclists.org/fulldisclosure/2018/May/43
https://github.com/vcftools/vcftools/issues/109

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: vcftools
Source-Version: 0.1.16-1

We believe that the bug you reported is fixed in the latest version of
vcftools, 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 902...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated vcftools 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: Fri, 03 Aug 2018 16:20:50 +0200
Source: vcftools
Binary: vcftools
Architecture: source
Version: 0.1.16-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 vcftools   - Collection of tools to work with VCF files
Closes: 902190
Changes:
 vcftools (0.1.16-1) unstable; urgency=medium
 .
   * New upstream version dealing with CVE-2018-11099, CVE-2018-11129 and
 CVE-2018-11130
 Closes: #902190
   * Point Vcs fields to salsa.debian.org
   * Standards-Version: 4.1.5
   * Remove unneeded get-orig-source target
   * Fix interpreter line in Perl scripts
Checksums-Sha1:
 f71094d6b75385fc84a5c76cb918ec1d40c985b7 2065 vcftools_0.1.16-1.dsc
 f80b58da5ac19bbafb2404d4878374dcbd6c98a7 244585 vcftools_0.1.16.orig.tar.gz
 d3ddc8663ca0a24ce7e2e457acfef7cc67373650 13708 vcftools_0.1.16-1.debian.tar.xz
Checksums-Sha256:
 2e0fa0c54974a3979458647cb5697811fb244b6611cb9cfb2128d95636a67f71 2065 
vcftools_0.1.16-1.dsc
 8255da4c9627b63fa43a006234fb4a1d160c63207a3f6df68ff9149f50cfb81e 244585 
vcftools_0.1.16.orig.tar.gz
 fab0b91d5f95ca2aecc567424062e683c76bb7be043105aeec630d6711d12a88 13708 
vcftools_0.1.16-1.debian.tar.xz
Files:
 084296c3981b72e9a14b2ae249beb043 2065 science optional vcftools_0.1.16-1.dsc
 4b96ec3a1dedeb879a71ecb0c4578548 244585 science optional 
vcftools_0.1.16.orig.tar.gz
 ed0db4fc2872988ba0452e28c06c131c 13708 science optional 
vcftools_0.1.16-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAltkaZcRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtE9Uw//cQqwOuCrD1mkNTwarNdBGhzd//CUZXDk
LMPT+DCVF7zmLRG8RhAhT/c0tAPgwe8frRFu39g8endvzurGKrXgt995VvYi4Ck5
zBQqVVwmIVMGPkLFJp8HqG4ry7soR+UMvYGB5v6psELmNsdTvhjMqPoxFykt9vTW
B8OEJ7oFbYfDkhaVGONhdaM/cmPj9HQUaT9SmQEJ8W3nfHlVzJMEWS+WJkB3wRaO
be0HN0CDu5CSruvErg/R3DOXnahKKbxLuekvVJVjj/r5pDRUMxRvfOwOPlRbsnzq
s3ua9LgUyX4/XIQIVi3F9kbgJeboXZjzpTanpma2UyJ6hUPflex2BMC8bTi4+HSP
GDpGhp6+sRLsNmwBwOyYV+eVpllZ9Lng3bT/uucmqJJvVcBoyRoIhp61K4t1sjqs
MD2v4OIJ1Hi5JGKeoYghGSSGog2tOcWSojSagMkrPr3fc59Yt6vB0XwH94Ov4DXA
E9uXE5tV3LFnUldtuKLJnJ8VDV0q0j1zHtxheLD2izkJZ8TLceXhdV57lC6HfIHC
lwsOufV0dOoqtKayR6Iv1zxyuvUJcWGbT1xSEt/OszsTNBpytVGlrZkxDqOZ++j/
ijteAO1kHK1onI9G/BeqC++ToNm1EkLNDB8UatbhHzBDEWYDFJFxKEl9PHvexYD5
z7louMvC378=
=Trlt
-END PGP SIGNATURE End Message ---

Bug#904121: marked as done (mysql-5.7: Security fixes from the July 2018 CPU)

[Debian Bug Tracking System]

Your message dated Fri, 03 Aug 2018 15:06:12 +
with message-id 
and subject line Bug#904121: fixed in mysql-5.7 5.7.23-1
has caused the Debian Bug report #904121,
regarding mysql-5.7: Security fixes from the July 2018 CPU
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.)


-- 
904121: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904121
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mysql-5.7
Version: 5.7.21-1
Severity: grave
Tags: security upstream

Hi

Details at
http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html#AppendixMSQL

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: mysql-5.7
Source-Version: 5.7.23-1

We believe that the bug you reported is fixed in the latest version of
mysql-5.7, 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 904...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lars Tangvald  (supplier of updated mysql-5.7 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, 30 Jul 2018 09:13:54 +0200
Source: mysql-5.7
Binary: libmysqlclient20 libmysqld-dev libmysqlclient-dev mysql-client-core-5.7 
mysql-client-5.7 mysql-server-core-5.7 mysql-server-5.7 mysql-server 
mysql-client mysql-testsuite mysql-testsuite-5.7 mysql-source-5.7
Architecture: source
Version: 5.7.23-1
Distribution: unstable
Urgency: high
Maintainer: Debian MySQL Maintainers 
Changed-By: Lars Tangvald 
Description:
 libmysqlclient-dev - MySQL database development files
 libmysqlclient20 - MySQL database client library
 libmysqld-dev - MySQL embedded database development files
 mysql-client - MySQL database client (metapackage depending on the latest 
versio
 mysql-client-5.7 - MySQL database client binaries
 mysql-client-core-5.7 - MySQL database core client binaries
 mysql-server - MySQL database server (metapackage depending on the latest 
versio
 mysql-server-5.7 - MySQL database server binaries and system database setup
 mysql-server-core-5.7 - MySQL database server binaries
 mysql-source-5.7 - MySQL source
 mysql-testsuite - MySQL regression tests
 mysql-testsuite-5.7 - MySQL 5.7 testsuite
Closes: 904121
Changes:
 mysql-5.7 (5.7.23-1) unstable; urgency=high (security fixes)
 .
   * Imported upstream version 5.7.23 to fix security issues:
 - 
http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html
 - CVE-2018-0739 CVE-2018-2767 CVE-2018-3054 CVE-2018-3056
 - CVE-2018-3058 CVE-2018-3060 CVE-2018-3061 CVE-2018-3062
 - CVE-2018-3064 CVE-2018-3065 CVE-2018-3066 CVE-2018-3070
 - CVE-2018-3071 CVE-2018-3077 CVE-2018-3081
 (Closes: #904121)
   * Moved internal test binaries out of usr/bin
 The client binaries mysqltest and mysql_client_test are only
 meant to be used by the mysql test suite, and are no longer
 installed in /usr/bin
Checksums-Sha1:
 f6c1208522cb835aa3c7f1a9423e34299162753b 3240 mysql-5.7_5.7.23-1.dsc
 e88edced7261412e66fc5570ed375bb3a36494bf 49025014 mysql-5.7_5.7.23.orig.tar.gz
 d5bfaf65dd4ef45462e45b570b2c703b245eb181 154320 
mysql-5.7_5.7.23-1.debian.tar.xz
Checksums-Sha256:
 75eeffb07127f5369d8ba60817ea446e90ac30bd2b82e057d38224e64dd06f9e 3240 
mysql-5.7_5.7.23-1.dsc
 d05700ec5c1c6dae9311059dc1713206c29597f09dbd237bf0679b3c6438e87a 49025014 
mysql-5.7_5.7.23.orig.tar.gz
 4378e37edd7493a477c34682027a180b647a8d375083f6679bba918ab65c8305 154320 
mysql-5.7_5.7.23-1.debian.tar.xz
Files:
 a6168eba126fdbdac50cd4e7b80ccb4d 3240 database optional mysql-5.7_5.7.23-1.dsc
 de108e7ff350aa10402a3e707a4b4c75 49025014 database optional 
mysql-5.7_5.7.23.orig.tar.gz
 4b2329bca1e24e6659f829e95d9ae402 154320 database optional 
mysql-5.7_5.7.23-1.debian.tar.xz

-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQIcBAEBCgAGBQJbZGr+AAoJEOVkucJ1vdUuJzAQAIv1dkBwme8gD9dOPW2p06Kn
rBEySXtWJ8xF6LhlZM95MwADYlXIhAQrRuVu9a26IXEEh3A7PUQWxnqkXeOlszYp
kjIIg0OGp/FNkB0i5AaC1rKBOKa/vwXpu6WXdMzI9f25NFwJ6lHgkovd1NNBwVqC
tTS1pgYPQUuWuQAfHh/TJlTvXdJaAKHF+1nnMS/sCCCq0bM2OothzasZezZBc/1W
2P26VjmCaDaMWcT18xkCmTBjLHoZY1DhsAGyEs7ugNJtPvgoMpFoDaNmtk69vrwk
fuN7TWUYyuzS9lTo2CFVFeFBN7zFI2mUSHVo2UF3I784eLk9NQEkB7KDh+mHB23X
iO2CzM9tFB4G

Bug#890907: marked as done (cjose FTBFS on big endian: test failure)

[Debian Bug Tracking System]

Your message dated Fri, 03 Aug 2018 15:19:00 +
with message-id 
and subject line Bug#890907: fixed in cjose 0.6.0+dfsg1-2~exp2
has caused the Debian Bug report #890907,
regarding cjose FTBFS on big endian: test failure
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.)


-- 
890907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890907
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cjose
Version: 0.6.0+dfsg1-1
Severity: serious

https://buildd.debian.org/status/package.php?p=cjose&suite=sid

...
FAIL: check_cjose
=

Running suite(s): CJOSE
 version
 util
 base64
 concatkdf
 jwk
 jwe
 jws
 header
95%: Checks: 62, Failures: 3, Errors: 0
check_version.c:12:P:version:test_cjose_version_define:0: Passed
check_version.c:18:P:version:test_cjose_version_fn:0: Passed
check_util.c:104:P:core:test_cjose_set_allocators:0: Passed
check_util.c:237:P:core:test_cjose_set_allocators_ex:0: Passed
check_base64.c:105:P:core:test_cjose_base64_encode:0: Passed
check_base64.c:205:P:core:test_cjose_base64url_encode:0: Passed
check_base64.c:317:P:core:test_cjose_base64_decode:0: Passed
check_base64.c:428:P:core:test_cjose_base64url_decode:0: Passed
check_concatkdf.c:102:P:concatkdf:test_cjose_concatkdf_otherinfo_noextra:0: 
Passed
check_concatkdf.c:127:P:concatkdf:test_cjose_concatkdf_otherinfo_apuapv:0: 
Passed
check_concatkdf.c:159:F:concatkdf:test_cjose_concatkdf_derive_simple:0: 
Assertion 'derived==expected' failed: keylen==%, derived==0x20, 
expected==0x566eb950
check_concatkdf.c:190:F:concatkdf:test_cjose_concatkdf_derive_ikm:0: Assertion 
'derived==expected' failed: keylen==%, derived==0x20, expected==0x566ebb80
check_concatkdf.c:224:F:concatkdf:test_cjose_concatkdf_derive_moreinfo:0: 
Assertion 'derived==expected' failed: keylen==%, derived==0x20, 
expected==0x566ebd50
check_jwk.c:62:P:core:test_cjose_jwk_name_for_kty:0: Passed
check_jwk.c:155:P:core:test_cjose_jwk_create_RSA_spec:0: Passed
check_jwk.c:194:P:core:test_cjose_jwk_create_RSA_random:0: Passed
check_jwk.c:223:P:core:test_cjose_jwk_create_EC_P256_spec:0: Passed
check_jwk.c:244:P:core:test_cjose_jwk_create_EC_P256_random:0: Passed
check_jwk.c:274:P:core:test_cjose_jwk_create_EC_P384_spec:0: Passed
check_jwk.c:295:P:core:test_cjose_jwk_create_EC_P384_random:0: Passed
check_jwk.c:325:P:core:test_cjose_jwk_create_EC_P521_spec:0: Passed
check_jwk.c:346:P:core:test_cjose_jwk_create_EC_P521_random:0: Passed
check_jwk.c:370:P:core:test_cjose_jwk_create_oct_spec:0: Passed
check_jwk.c:388:P:core:test_cjose_jwk_create_oct_random:0: Passed
check_jwk.c:401:P:core:test_cjose_jwk_create_oct_random_inval:0: Passed
check_jwk.c:437:P:core:test_cjose_jwk_retain_release:0: Passed
check_jwk.c:450:P:core:test_cjose_jwk_get_kty:0: Passed
check_jwk.c:474:P:core:test_cjose_jwk_to_json_oct:0: Passed
check_jwk.c:512:P:core:test_cjose_jwk_to_json_ec:0: Passed
check_jwk.c:580:P:core:test_cjose_jwk_to_json_rsa:0: Passed
check_jwk.c:747:P:core:test_cjose_jwk_import_json_valid:0: Passed
check_jwk.c:864:P:core:test_cjose_jwk_import_json_invalid:0: Passed
check_jwk.c:1029:P:core:test_cjose_jwk_import_valid:0: Passed
check_jwk.c:1151:P:core:test_cjose_jwk_import_invalid:0: Passed
check_jwk.c:1174:P:core:test_cjose_jwk_import_underflow_length:0: Passed
check_jwk.c:1204:P:core:test_cjose_jwk_import_no_zero_termination:0: Passed
check_jwk.c:1246:P:core:test_cjose_jwk_import_with_base64url_padding:0: Passed
check_jwk.c:1288:P:core:test_cjose_jwk_EC_import_with_priv_export_with_pub:0: 
Passed
check_jwk.c:1324:P:core:test_cjose_jwk_hkdf:0: Passed
check_jwk.c:1416:P:core:test_cjose_jwk_get_and_set_kid:0: Passed
check_jwe.c:180:P:core:test_cjose_jwe_self_encrypt_self_decrypt:0: Passed
check_jws.c:135:P:core:test_cjose_jws_self_sign_self_verify:0: Passed
check_jws.c:135:P:core:test_cjose_jws_self_sign_self_verify_short:0: Passed
check_jws.c:135:P:core:test_cjose_jws_self_sign_self_verify_empty:0: Passed
check_jws.c:135:P:core:test_cjose_jws_self_sign_self_verify_many:0: Passed
check_jws.c:603:P:core:test_cjose_jws_verify_hs256:0: Passed
check_jws.c:708:P:core:test_cjose_jws_verify_rs256:0: Passed
check_jws.c:767:P:core:test_cjose_jws_verify_rs384:0: Passed
check_jws.c:853:P:core:test_cjose_jws_verify_ec256:0: Passed
check_jws.c:258:P:core:test_cjose_jws_sign_with_bad_header:0: Passed
check_jws.c:320:P:core:test_cjose_jws_sign_with_bad_key:0: Passed
check_jws.c:363:P:core:test_cjose_jws_sign_with_bad_content:0: Passed
check_jws.c:393:P:core:test_cjose_jws_import_export_compare:0: Passed
check_jws.c:436:P:core:test_cjose_jws_import_invalid_serialization:0: Passed

Bug#904434: marked as done (intel-mkl: FTBFS in C locale)

[Debian Bug Tracking System]

Your message dated Fri, 03 Aug 2018 15:49:30 +
with message-id 
and subject line Bug#904434: fixed in intel-mkl 2018.3.222-2
has caused the Debian Bug report #904434,
regarding intel-mkl: FTBFS in C locale
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.)


-- 
904434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: intel-mkl
Version: 2018.3.222-1

Hi,

thank you so much for packaging intel-mkl, it basically doubles the
performance of our R number crunchers.

However, when locally rebuilding the package I saw that it wants to
check the md5sum of the upstream tarball. This fails when building
binary packages only, which should be possible.

Regards,
Daniel
--- End Message ---
--- Begin Message ---
Source: intel-mkl
Source-Version: 2018.3.222-2

We believe that the bug you reported is fixed in the latest version of
intel-mkl, 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 904...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Mo Zhou  (supplier of updated intel-mkl 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: Fri, 03 Aug 2018 15:11:56 +
Source: intel-mkl
Binary: intel-mkl intel-mkl-cluster intel-mkl-doc intel-mkl-full 
intel-mkl-linktool libmkl-full-dev libmkl-dev libmkl-interface-dev 
libmkl-threading-dev libmkl-computational-dev libmkl-cluster-dev libmkl-locale 
libmkl-rt libmkl-meta-interface libmkl-intel-lp64 libmkl-intel-ilp64 
libmkl-intel libmkl-gf-lp64 libmkl-gf-ilp64 libmkl-gf libmkl-meta-threading 
libmkl-intel-thread libmkl-tbb-thread libmkl-gnu-thread libmkl-pgi-thread 
libmkl-sequential libmkl-meta-computational libmkl-core libmkl-def libmkl-mc 
libmkl-mc3 libmkl-avx libmkl-avx2 libmkl-avx512 libmkl-avx512-mic 
libmkl-vml-def libmkl-vml-mc libmkl-vml-mc2 libmkl-vml-mc3 libmkl-vml-avx 
libmkl-vml-avx2 libmkl-vml-avx512 libmkl-vml-avx512-mic libmkl-vml-cmpt 
libmkl-p4 libmkl-p4m libmkl-p4m3 libmkl-vml-ia libmkl-vml-p4 libmkl-vml-p4m 
libmkl-vml-p4m2 libmkl-vml-p4m3 libmkl-meta-cluster libmkl-scalapack-lp64 
libmkl-scalapack-ilp64 libmkl-cdft-core libmkl-blacs-intelmpi-lp64 
libmkl-blacs-intelmpi-ilp64
 libmkl-blacs-openmpi-lp64 libmkl-blacs-openmpi-ilp64 libmkl-blacs-sgimpt-lp64
 libmkl-blacs-sgimpt-ilp64
Architecture: source
Version: 2018.3.222-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Mo Zhou 
Description:
 intel-mkl  - Intel® Math Kernel Library (Intel® MKL)
 intel-mkl-cluster - Intel® Math Kernel Library (Intel® MKL) (Cluster)
 intel-mkl-doc - Intel® Math Kernel Library (Intel® MKL) (Doc)
 intel-mkl-full - Intel® Math Kernel Library (Intel® MKL) (Full)
 intel-mkl-linktool - Intel(R) Math Kernel Library (Intel(R) MKL) Link Tool v4.7
 libmkl-avx - Intel® MKL: Kernel library for Intel® AVX enabled processors
 libmkl-avx2 - Intel® MKL: Kernel library for Intel® AVX2 enabled processors
 libmkl-avx512 - Intel® MKL: Kernel library for Intel® AVX-512 enabled 
processors
 libmkl-avx512-mic - Intel® MKL : Kernel library for Intel® AVX-512 Xeon Phi 
processor
 libmkl-blacs-intelmpi-ilp64 - Intel® MKL : ILP64 BLACS routines for Intel® MPI 
and MPICH2+
 libmkl-blacs-intelmpi-lp64 - Intel® MKL : LP64 BLACS routines for Intel® MPI 
and MPICH2+
 libmkl-blacs-openmpi-ilp64 - Intel® MKL : ILP64 version of BLACS routines for 
Open MPI
 libmkl-blacs-openmpi-lp64 - Intel® MKL : LP64 version of BLACS routines for 
Open MPI
 libmkl-blacs-sgimpt-ilp64 - Intel® MKL : ILP64 version of BLACS routines for 
SGI MPT
 libmkl-blacs-sgimpt-lp64 - Intel® MKL : LP64 version of BLACS routines for SGI 
MPI Toolkit
 libmkl-cdft-core - Intel® MKL : Cluster version of FFT functions
 libmkl-cluster-dev - Static libs of intel-MKL: Cluster
 libmkl-computational-dev - Static libs of intel-MKL: Computational Layer
 libmkl-core - Intel® MKL: Library dispatcher of Computational Layer
 libmkl-def - Intel® MKL: Default kernel library
 libmkl-dev - Intel® Math Kernel Library (Intel® MKL) (Dev)
 libmkl-full-dev - Intel® Math Kernel Library (Intel® MKL) (Full Version Dev)
 libmkl-gf  - Intel® MKL: (ia32) Interf

Bug#905367: cccolutils: FTBFS in sid

[Santiago Vila]

Package: src:cccolutils
Version: 1.4-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch --with python3 --buildsystem=pybuild
   dh_update_autotools_config -a -O--buildsystem=pybuild
   dh_autoreconf -a -O--buildsystem=pybuild
   dh_auto_configure -a -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -a -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python3.7 setup.py build 
running build
running build_ext
building 'cccolutils' extension
creating build
creating build/temp.linux-amd64-3.7
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/usr/include/python3.7m -c cccolutils.c -o 
build/temp.linux-amd64-3.7/cccolutils.o
cccolutils.c:17:10: fatal error: Python.h: No such file or directory
 #include 
  ^~
compilation terminated.
error: command 'x86_64-linux-gnu-gcc' failed with exit status 1
E: pybuild pybuild:338: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3.7 setup.py build 
dh_auto_build: pybuild --build -i python{version} -p "3.7 3.6" returned exit 
code 13
make: *** [debian/rules:8: build-arch] Error 25
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder,
but it also fails here:

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

Seems like a missing build-depends somewhere.

Thanks.

Bug#905369: mshr: FTBFS in sid

[Santiago Vila]

Package: src:mshr
Version: 2017.2.0+dfsg1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
dh build-indep --buildsystem=cmake \
  --with python2,python3
   dh_update_autotools_config -i -O--buildsystem=cmake
   dh_autoreconf -i -O--buildsystem=cmake
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/mshr-2017.2.0+dfsg1'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
for v in python3.6 python3.7  python2.7; do \
dh_auto_configure 
--builddirectory=/<>/mshr-2017.2.0+dfsg1/debian/build-$v -- \
   -D PYTHON_EXECUTABLE:FILEPATH=/usr/bin/$v \

[... snipped ...]

[ 80%] Linking CXX shared library libmshr.so
/usr/bin/cmake -E cmake_link_script CMakeFiles/mshr.dir/link.txt --verbose=1
/usr/bin/c++ -fPIC -fpermissive -std=c++0x -Wall -O3 -DNDEBUG -Wl,-z,relro 
-shared -Wl,-soname,libmshr.so.2017.2 -o libmshr.so.2017.2.0 
CMakeFiles/mshr.dir/src/ASCFileReader.cpp.o 
CMakeFiles/mshr.dir/src/CSGCGALDomain2D.cpp.o 
CMakeFiles/mshr.dir/src/CSGCGALDomain3D.cpp.o 
CMakeFiles/mshr.dir/src/CSGCGALMeshGenerator2D.cpp.o 
CMakeFiles/mshr.dir/src/CSGCGALMeshGenerator3D.cpp.o 
CMakeFiles/mshr.dir/src/CSGGeometries3D.cpp.o 
CMakeFiles/mshr.dir/src/CSGGeometry.cpp.o 
CMakeFiles/mshr.dir/src/CSGOperators.cpp.o 
CMakeFiles/mshr.dir/src/CSGPrimitives2D.cpp.o 
CMakeFiles/mshr.dir/src/CSGPrimitives3D.cpp.o 
CMakeFiles/mshr.dir/src/DolfinMeshUtils.cpp.o 
CMakeFiles/mshr.dir/src/GlobalInitializer.cpp.o 
CMakeFiles/mshr.dir/src/MeshGenerator.cpp.o 
CMakeFiles/mshr.dir/src/Meshes.cpp.o 
CMakeFiles/mshr.dir/src/OFFFileReader.cpp.o 
CMakeFiles/mshr.dir/src/STLFileReader.cpp.o 
CMakeFiles/mshr.dir/src/SurfaceConsistency.cpp.o 
CMakeFiles/mshr.dir/src/SurfaceReconstruction.cpp.o 
CMakeFiles/mshr.dir/src/TetgenMes
 hGenerator3D.cpp.o /usr/lib/x86_64-linux-gnu/libboost_system.so 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so 
/usr/lib/x86_64-linux-gnu/libboost_program_options.so 
/usr/lib/x86_64-linux-gnu/libgmp.so /usr/lib/x86_64-linux-gnu/libmpfr.so -ltet 
/usr/lib/x86_64-linux-gnu/libdolfin.so.2018.1.0 
/usr/lib/x86_64-linux-gnu/libboost_system.so 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so 
/usr/lib/x86_64-linux-gnu/libboost_program_options.so 
/usr/lib/x86_64-linux-gnu/libgmp.so /usr/lib/x86_64-linux-gnu/libmpfr.so -ltet 
/usr/lib/x86_64-linux-gnu/libboost_timer.so 
/usr/lib/x86_64-linux-gnu/hdf5/openmpi/libhdf5.so 
/usr/lib/x86_64-linux-gnu/libsz.so /usr/lib/x86_64-linux-gnu/libz.so 
/usr/lib/x86_64-linux-gnu/libdl.so -lm 
/usr/lib/slepcdir/slepc3.9/x86_64-linux-gnu-real/lib/libslepc_real.so 
/usr/lib/petscdir/petsc3.9/x86_64-linux-gnu-real/lib/libpetsc_real.so 
/usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so 
/usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so 
/usr/bin/cmake -E cmake_symlink_library libmshr.so.2017.2.0 libmshr.so.2017.2 
libmshr.so
make[4]: Leaving directory 
'/<>/mshr-2017.2.0+dfsg1/debian/build-python2.7'
[ 80%] Built target mshr
make -f CMakeFiles/mshrable.dir/build.make CMakeFiles/mshrable.dir/depend
make[4]: Entering directory 
'/<>/mshr-2017.2.0+dfsg1/debian/build-python2.7'
cd /<>/mshr-2017.2.0+dfsg1/debian/build-python2.7 && /usr/bin/cmake 
-E cmake_depends "Unix Makefiles" /<>/mshr-2017.2.0+dfsg1 
/<>/mshr-2017.2.0+dfsg1 
/<>/mshr-2017.2.0+dfsg1/debian/build-python2.7 
/<>/mshr-2017.2.0+dfsg1/debian/build-python2.7 
/<>/mshr-2017.2.0+dfsg1/debian/build-python2.7/CMakeFiles/mshrable.dir/DependInfo.cmake
 --color=
Scanning dependencies of target mshrable
make[4]: Leaving directory 
'/<>/mshr-2017.2.0+dfsg1/debian/build-python2.7'
make -f CMakeFiles/mshrable.dir/build.make CMakeFiles/mshrable.dir/build
make[4]: Entering directory 
'/<>/mshr-2017.2.0+dfsg1/debian/build-python2.7'
[ 84%] Building CXX object CMakeFiles/mshrable.dir/app/mshrable.cpp.o
/usr/bin/c++  -DDOLFIN_VERSION=\"2018.1.0\" -DHAS_CHOLMOD -DHAS_HDF5 -DHAS_MPI 
-DHAS_PETSC -DHAS_SCOTCH -DHAS_SLEPC -DHAS_UMFPACK -DHAS_ZLIB -DNDEBUG 
-DTETLIBRARY -D_FORTIFY_SOURCE=2 -I/<>/mshr-2017.2.0+dfsg1/include 
-I/include -I/usr/include/x86_64-linux-gnu -isystem /usr/include/eigen3 
-isystem /usr/include/hdf5/openmpi -isystem 
/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -isystem 
/usr/lib/x86_64-linux-gnu/openmpi/include -isystem 
/usr/lib/slepcdir/slepc3.9/x86_64-linux-gnu-real/include -isystem 
/usr/lib/petscdir/petsc3.9/x86_64-linux-gnu-real/include -isystem 
/usr/include/suitesparse -isystem /usr/include/superlu -isystem 
/usr/include/superlu-dist -isystem /usr/include/hypre -isystem 
/usr/include/scotch  -fpermissive -std=c++0x -Wall -O3 -DNDEBUG   -std=c++11 -o 
CMakeFiles

Bug#905368: libstatgen: FTBFS in sid

[Santiago Vila]

Package: src:libstatgen
Version: 1.0.14-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
make -j1 "INSTALL=install --strip-program=true"
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>/samtools'
ln -s ../samtools/bgzf.h ../include/bgzf.h
ln -s ../samtools/knetfile.h ../include/knetfile.h
ln -s ../samtools/khash.h ../include/khash.h

[... snipped ...]

ln -s ../general/SmithWaterman.h ../include/SmithWaterman.h
ln -s ../general/Sort.h ../include/Sort.h
ln -s ../general/STLUtilities.h ../include/STLUtilities.h
ln -s ../general/StatGenStatus.h ../include/StatGenStatus.h
ln -s ../general/StringAlias.h ../include/StringAlias.h
ln -s ../general/StringArray.h ../include/StringArray.h
ln -s ../general/StringBasics.h ../include/StringBasics.h
ln -s ../general/StringHash.h ../include/StringHash.h
ln -s ../general/StringMap.h ../include/StringMap.h
ln -s ../general/Tabix.h ../include/Tabix.h
ln -s ../general/UncompressedFileType.h ../include/UncompressedFileType.h
ln -s ../general/Constant.h ../include/Constant.h
ln -s ../general/CSG_MD5.h ../include/CSG_MD5.h
ln -s ../general/Generic.h ../include/Generic.h
ln -s ../general/GenomeSequenceHelpers.h ../include/GenomeSequenceHelpers.h
ln -s ../general/GreedyTupleAligner.h ../include/GreedyTupleAligner.h
ln -s ../general/InplaceMerge.h ../include/InplaceMerge.h
ln -s ../general/LongHash.h ../include/LongHash.h
ln -s ../general/LongInt.h ../include/LongInt.h
ln -s ../general/MathConstant.h ../include/MathConstant.h
ln -s ../general/PackedVector.h ../include/PackedVector.h
ln -s ../general/PedigreeAlleles.h ../include/PedigreeAlleles.h
ln -s ../general/Performance.h ../include/Performance.h
ln -s ../general/ReusableVector.h ../include/ReusableVector.h
ln -s ../general/SimpleStats.h ../include/SimpleStats.h
ln -s ../general/TrimSequence.h ../include/TrimSequence.h
ln -s ../general/UnitTest.h ../include/UnitTest.h
g++  -O4 -fPIC -pipe -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now -Werror -Wno-format-truncation  
-Wno-strict-overflow  -I../include -I.   -D__ZLIB_AVAILABLE__ 
-D_FILE_OFFSET_BITS=64 -D__STDC_LIMIT_MACROS  -o obj/BaseAsciiMap.o -c 
BaseAsciiMap.cpp -DVERSION="\"1.0.0\""
g++  -O4 -fPIC -pipe -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now -Werror -Wno-format-truncation  
-Wno-strict-overflow  -I../include -I.   -D__ZLIB_AVAILABLE__ 
-D_FILE_OFFSET_BITS=64 -D__STDC_LIMIT_MACROS  -o obj/BaseQualityHelper.o -c 
BaseQualityHelper.cpp -DVERSION="\"1.0.0\""
g++  -O4 -fPIC -pipe -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now -Werror -Wno-format-truncation  
-Wno-strict-overflow  -I../include -I.   -D__ZLIB_AVAILABLE__ 
-D_FILE_OFFSET_BITS=64 -D__STDC_LIMIT_MACROS  -o obj/BaseUtilities.o -c 
BaseUtilities.cpp -DVERSION="\"1.0.0\""
g++  -O4 -fPIC -pipe -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now -Werror -Wno-format-truncation  
-Wno-strict-overflow  -I../include -I.   -D__ZLIB_AVAILABLE__ 
-D_FILE_OFFSET_BITS=64 -D__STDC_LIMIT_MACROS  -o obj/BasicHash.o -c 
BasicHash.cpp -DVERSION="\"1.0.0\""
g++  -O4 -fPIC -pipe -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now -Werror -Wno-format-truncation  
-Wno-strict-overflow  -I../include -I.   -D__ZLIB_AVAILABLE__ 
-D_FILE_OFFSET_BITS=64 -D__STDC_LIMIT_MACROS  -o obj/BgzfFileType.o -c 
BgzfFileType.cpp -DVERSION="\"1.0.0\""
g++  -O4 -fPIC -pipe -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now -Werror -Wno-format-truncation  
-Wno-strict-overflow  -I../include -I.   -D__ZLIB_AVAILABLE__ 
-D_FILE_OFFSET_BITS=64 -D__STDC_LIMIT_MACROS  -o obj/BgzfFileTypeRecovery.o -c 
BgzfFileTypeRecovery.cpp -DVERSION="\"1.0.0\""
g++  -O4 -fPIC -pipe -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wl,-z,relro -Wl,-z,now -Werror -Wno-format-truncation  
-Wno-strict-overflow  -I../include -I.   -D__ZLIB_AVAILABLE__ 
-D_FILE_OFFSET_BITS=64 -D__STDC_LIMIT_MACROS  -o obj/CharBuffer.o -c 
CharBuffer.cpp -DVERSION="\"1.0.0\""
g++  -O4 -fPIC -pipe -Wall -Wdate-time -D_FORTIFY_SOURC

Bug#905370: octave-queueing: FTBFS in sid

[Santiago Vila]

Package: src:octave-queueing
Version: 1.2.5-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=octave --with=octave
   dh_update_autotools_config -i -O--buildsystem=octave
   dh_autoreconf -i -O--buildsystem=octave
   dh_octave_version -i -O--buildsystem=octave
Checking the Octave version... ok
   dh_auto_configure -i -O--buildsystem=octave
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
[ ! -f doc/Makefile ] || make -C doc html pdf info
make[2]: Entering directory '/<>/doc'
fig2dev -L png -m 3 qn_open_single.fig qn_open_single.png
fig2dev -L png -m 3 qn_closed_single.fig qn_closed_single.png
fig2dev -L png -m 3 qn_web_model.fig qn_web_model.png

[... snipped ...]

6 tests, 1 passed, 0 known failure, 0 skipped
[inst/ctmc_check_Q.m]
> /<>/inst/ctmc_check_Q.m
* test
 Q = [0];
 [result err] = ctmc_check_Q(Q);
 assert( result, 1 );
 assert( err, "" );
! test failed
'ctmc_check_Q' undefined near line 4 column 16
* test
 N = 10;
 Q = ctmc_bd(rand(1,N-1),rand(1,N-1));
 [result err] = ctmc_check_Q(Q);
 assert( result, N );
 assert( err, "" );
! test failed
'ctmc_bd' undefined near line 4 column 6
* test
 Q = [1 2 3; 4 5 6];
 [result err] = ctmc_check_Q(Q);
 assert( result, 0 );
 assert( index(err, "square") > 0 );
! test failed
'ctmc_check_Q' undefined near line 4 column 16
* test
 N = 10;
 Q = ctmc_bd(rand(1,N-1),rand(1,N-1));
 Q(2,1) = -1;
 [result err] = ctmc_check_Q(Q);
 assert( result, 0 );
 assert( index(err, "infinitesimal") > 0 );
! test failed
'ctmc_bd' undefined near line 4 column 6
* test
 N = 10;
 Q = ctmc_bd(rand(1,N-1),rand(1,N-1));
 Q(1,1) += 7;
 [result err] = ctmc_check_Q(Q);
 assert( result, 0 );
 assert( index(err, "infinitesimal") > 0 );
! test failed
'ctmc_bd' undefined near line 4 column 6
5 tests, 0 passed, 0 known failure, 0 skipped
Checking C++ files ...
Summary: 267 tests, 6 passed, 3 known failures, 0 skipped
Some tests failed.  Giving up...
make: *** [debian/rules:5: binary-indep] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


The build was made with "dpkg-buildpackage -A" in my autobuilder.
Most probably, it will also fail here in reproducible builds:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/octave-queueing.html

Thanks.

Bug#903808: marked as done (leela-zero: Not functional without downloading extra resources)

[Debian Bug Tracking System]

Your message dated Fri, 03 Aug 2018 16:04:28 +
with message-id 
and subject line Bug#903808: fixed in leela-zero 0.15-4
has caused the Debian Bug report #903808,
regarding leela-zero: Not functional without downloading extra resources
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.)


-- 
903808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903808
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: leela-zero
Severity: serious
Justification: Policy 2.2.1

Dear Maintainer,

When I try to run leela-zero, it tells me there's no weights file, and
I need to download extra file to make it functional.

Thus I think this package breaks the policy 2.2.1

> In addition, the packages in main
>  * must not require or recommend a package outside of main for compilation
>or execution (thus, the package must not declare a Pre-Depends, Depends,
>Recommends, Build-Depends, Build-Depends-Indep, or Build-Depends-Arch
>relationship on a non-main package unless that package is only listed
>as a non-default alternative for a package in main),

> The contrib archive area contains supplemental packages intended to work
> with the Debian distribution, but which require software outside of the
> distribution to either build or function.

So I think you can include the weights file in package, or
provide tool to generate this file(I think these are in upstream
training dir), or leave this package to contrib.

From -devel discussion, the pre-trained file may have problem to
distribute, but I think you can distribute some "idiot" module, to make the
program functional(not just print error/help info).


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: leela-zero
Source-Version: 0.15-4

We believe that the bug you reported is fixed in the latest version of
leela-zero, 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 903...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ximin Luo  (supplier of updated leela-zero 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: Fri, 03 Aug 2018 08:52:37 -0700
Source: leela-zero
Binary: leela-zero
Architecture: source
Version: 0.15-4
Distribution: unstable
Urgency: medium
Maintainer: Ximin Luo 
Changed-By: Ximin Luo 
Description:
 leela-zero - Go engine with no human-provided knowledge, modeled after the Alp
Closes: 903808
Changes:
 leela-zero (0.15-4) unstable; urgency=medium
 .
   * Describe how to create a dummy network file that doesn't involve using
 non-Debian software. (Closes: #903808)
Checksums-Sha1:
 485c8ed349eb7f81df61c7808182d6c2cacad28f 1492 leela-zero_0.15-4.dsc
 c7a75a5b69efb2970228313f3c9db424dbae253b 7788 leela-zero_0.15-4.debian.tar.xz
 8bc3ded354f555071fb468b05cb49685add1644c 7286 
leela-zero_0.15-4_source.buildinfo
Checksums-Sha256:
 4b132e6f89c23d57585ea500a0275cb732b74df6b7afcaad343b46758b670b4d 1492 
leela-zero_0.15-4.dsc
 3164a0a151f2759950d01f530317fe44e786f205a30004bf069bd5ec158eeb6c 7788 
leela-zero_0.15-4.debian.tar.xz
 668f73c5bbe9890247074a5ee316314d47442e864b2a5e722d737500750726ae 7286 
leela-zero_0.15-4_source.buildinfo
Files:
 1420febaaf544220a204fb2800781cbd 1492 games optional leela-zero_0.15-4.dsc
 c9d1bd2c2f909c1f5c6ba571d82a0bf4 7788 games optional 
leela-zero_0.15-4.debian.tar.xz
 07ee1b56dc7be362956fc95a7203f6d9 7286 games optional 
leela-zero_0.15-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQReYinNQ9GpZ9TYcRrrH8jaRfspMAUCW2R6qQAKCRDrH8jaRfsp
MLlnAQDvAlRjTNtA9TJ4M3QvMQHNIsGeBiCf/r1nzFDj1eSlNgEAynjvTbj1ckxP
yP83t+7E5VsnM2i7zs5fqghDGiPl/A0=
=QD9w
-END PGP SIGNATURE End Message ---

Processed: reassign 866436 to keysync

[Debian Bug Tracking System]

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

> # This is not a bug in the source package (no b-d on python-imaging) but in 
> the binary package
> reassign 866436 keysync 0.2.2-1
Bug #866436 [src:keysync] keysync: depends on obsolete python-imaging (replace 
with python3-pil or python-pil)
Bug reassigned from package 'src:keysync' to 'keysync'.
No longer marked as found in versions keysync/0.2.2-1.
Ignoring request to alter fixed versions of bug #866436 to the same values 
previously set
Bug #866436 [keysync] keysync: depends on obsolete python-imaging (replace with 
python3-pil or python-pil)
Marked as found in versions keysync/0.2.2-1.
> thanks
Stopping processing here.

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

Bug#905372: network-manager-strongswan FTBFS: error: macro "G_UNAVAILABLE" passed 3 arguments, but takes just 2

[Helmut Grohne]

Source: network-manager-strongswan
Version: 1.4.4-1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap

network-manager-strongswan fails to build from source. A build on amd64
ends with:

| libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -I/usr/include/libnm -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-DNM_VERSION_MIN_REQUIRED=NM_VERSION_1_2 
-DNM_VERSION_MAX_ALLOWED=NM_VERSION_1_2 -pthread -I/usr/include/libnma 
-I/usr/include/libnm -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo 
-I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 
-I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-DUIDIR=\"/usr/share/gnome-vpn-properties/strongswan\" -DG_DISABLE_DEPRECATED 
-DGDK_DISABLE_DEPRECATED -Wall -Werror -std=gnu89 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wshadow -Wmissing-declarations -Wmissing-prototypes 
-Wdeclaration-after-statement -Wfloat-equal -Wno-unused-parameter 
-Wno-sign-compare -fno-strict-aliasing -c nm-strongswan.c  -fPIC -DPIC -o 
.libs/libnm_vpn_plugin_strongswan_la-nm-strongswan.o
| In file included from /usr/include/libnm/NetworkManager.h:46,
|  from nm-strongswan.c:37:
| /usr/include/libnm/nm-device-ovs-port.h:45:1: error: macro "G_UNAVAILABLE" 
passed 3 arguments, but takes just 2
|  NM_AVAILABLE_IN_1_12_2
|  ^~
| /usr/include/libnm/nm-device-ovs-port.h:46:1: error: expected ';' before 
'const'
|  const GPtrArray *nm_device_ovs_port_get_slaves (NMDeviceOvsPort *device);
|  ^
| In file included from /usr/include/libnm/NetworkManager.h:47,
|  from nm-strongswan.c:37:
| /usr/include/libnm/nm-device-ovs-bridge.h:45:1: error: macro "G_UNAVAILABLE" 
passed 3 arguments, but takes just 2
|  NM_AVAILABLE_IN_1_12_2
|  ^~
| /usr/include/libnm/nm-device-ovs-bridge.h:46:1: error: expected ';' before 
'const'
|  const GPtrArray *nm_device_ovs_bridge_get_slaves (NMDeviceOvsBridge *device);
|  ^
| make[3]: *** [Makefile:559: libnm_vpn_plugin_strongswan_la-nm-strongswan.lo] 
Error 1
| make[3]: Leaving directory '/<>/properties'
| make[2]: *** [Makefile:533: all-recursive] Error 1
| make[2]: Leaving directory '/<>'
| make[1]: *** [Makefile:423: all] Error 2
| make[1]: Leaving directory '/<>'
| dh_auto_build: make -j1 returned exit code 2
| make: *** [debian/rules:4: build] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

The reproducible people see a similar failure:

https://tests.reproducible-builds.org/debian/rbuild/buster/i386/network-manager-strongswan_1.4.4-1.rbuild.log.gz

Since their failure is in buster, this suggests that some dependency has
changed and made network-manager-strongswan fail. I don't know which one
though.

Helmut

Bug#888374: marked as done (gmerlin-avdecoder: FTBFS with FFmpeg 4.0)

[Debian Bug Tracking System]

Your message dated Fri, 03 Aug 2018 16:49:03 +
with message-id 
and subject line Bug#888374: fixed in gmerlin-avdecoder 1.2.0~dfsg-10
has caused the Debian Bug report #888374,
regarding gmerlin-avdecoder: FTBFS with FFmpeg 4.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.)


-- 
888374: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888374
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gmerlin-avdecoder
Version: 1.2.0~dfsg-9
Severity: important
User: debian-multime...@lists.debian.org
Usertags: ffmpeg-3.5-transition

Hi,

Your package FTBFS with the upcoming version 3.5 of FFmpeg. In FFmpeg 3.5,
there are a number of API changes which will cause many packages to FTBFS.
For this reason I have uploaded an early development snapshot to experimental
before the 3.5 release in an attempt to fix some of these a bit quicker.
While 3.5 has not been finalized and the ABI is not stable yet, there should
not be any significant API breakages before the release.

Incomplete list of changes (based on looking at common build failures):
- Some fields in AVCodecContext have been removed and replaced with private
  options which can be set using the av_opt_set* APIs
- Most CODEC_* constants have been renamed to AV_CODEC_*
- The buffer constants FF_INPUT_BUFFER_PADDING_SIZE and FF_MIN_BUFFER_SIZE
  have been renamed to AV_INPUT_BUFFER_PADDING_SIZE and
  AV_INPUT_BUFFER_MIN_SIZE.
- The old resampling API provided by libavcodec has been removed. Use
  libswresample instead.
- The libavfilter/avfiltergraph.h header has been removed, include
  libavfilter/avfilter.h instead.
- The AVFrac structure (representing mixed rational numbers) has been
  removed.

Build log:
https://people.debian.org/~jcowgill/ffmpeg-3.5-20180122/gmerlin-avdecoder_amd64.build

Thanks,
James
--- End Message ---
--- Begin Message ---
Source: gmerlin-avdecoder
Source-Version: 1.2.0~dfsg-10

We believe that the bug you reported is fixed in the latest version of
gmerlin-avdecoder, 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 888...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated 
gmerlin-avdecoder 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: Fri, 03 Aug 2018 18:12:00 +0200
Source: gmerlin-avdecoder
Binary: libgmerlin-avdec1 libgmerlin-avdec-dev libgmerlin-avdec-doc 
gmerlin-plugins-avdecoder
Architecture: source
Version: 1.2.0~dfsg-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Sebastian Ramacher 
Description:
 gmerlin-plugins-avdecoder - avdecoder plugins for Gmerlin
 libgmerlin-avdec-dev - general multimedia decoding library (development files)
 libgmerlin-avdec-doc - general multimedia decoding library (documentation)
 libgmerlin-avdec1 - general multimedia decoding library
Closes: 888374
Changes:
 gmerlin-avdecoder (1.2.0~dfsg-10) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Felipe Sateler ]
   * Change maintainer address to debian-multime...@lists.debian.org
 .
   [ Peter Michael Green ]
   * Fix FTBFS with ffmpeg 4.0 (Closes: #888374)
 + Fixup renamed constants
 + Disable vdpau, struct vdpau_render_state has disappeard and I have no
   idea what if anything it can be replaced with.
   * Remove po/de.gmo in clean target, it seems that the build process changes
 it.
 .
   [ Sebastian Ramacher ]
   * debian/control:
 - Bump Standards-Version.
 - Remove libvdpau-dev from B-D.
   * debian/rules: Remove -dbgsym migration code. The -dbgsym package is
 already present in stable.
Checksums-Sha1:
 ca611dbd8bd49359c0e8830853646b14b8174c48 2859 
gmerlin-avdecoder_1.2.0~dfsg-10.dsc
 d24649a2080f4cc3159f4299b0ecaaadbd9c8758 27420 
gmerlin-avdecoder_1.2.0~dfsg-10.debian.tar.xz
Checksums-Sha256:
 4f928eb20d45f40ffe27f7dbbe715ee62b5846b2852e2234b94eb8aeaf47548d 2859 
gmerlin-avdecoder_1.2.0~dfsg-10.dsc
 c2c1241ef1fdf92b2ec6b78afa713cf74b1221a75d5eba52cd98c6105763fe83 27420 
gmerlin-avdecoder_1.2.

Processed: tagging 897779

[Debian Bug Tracking System]

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

> tags 897779 + ftbfs
Bug #897779 [src:lhapdf] lhapdf: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 888331

[Debian Bug Tracking System]

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

> tags 888331 + ftbfs
Bug #888331 [src:vdr-plugin-softhddevice] vdr-plugin-softhddevice: FTBFS with 
FFmpeg 4.0
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 897727

[Debian Bug Tracking System]

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

> tags 897727 + ftbfs
Bug #897727 [src:cp2k] cp2k: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 897855

[Debian Bug Tracking System]

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

> tags 897855 + ftbfs
Bug #897855 [src:sarg] sarg: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 897860

[Debian Bug Tracking System]

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

> tags 897860 + ftbfs
Bug #897860 [src:simulavr] simulavr: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 897777

[Debian Bug Tracking System]

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

> tags 89 + ftbfs
Bug #89 [src:kvmtool] kvmtool: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 897752

[Debian Bug Tracking System]

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

> tags 897752 + ftbfs
Bug #897752 [src:freefem3d] freefem3d: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 897722

[Debian Bug Tracking System]

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

> tags 897722 + ftbfs
Bug #897722 [src:clsparse] clsparse: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 897840

[Debian Bug Tracking System]

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

> tags 897840 + ftbfs
Bug #897840 [src:python-escript] python-escript: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 897890

[Debian Bug Tracking System]

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

> tags 897890 + ftbfs
Bug #897890 [src:yp-tools] yp-tools: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 897760

[Debian Bug Tracking System]

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

> tags 897760 + ftbfs
Bug #897760 [src:gltron] gltron: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 897875

[Debian Bug Tracking System]

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

> tags 897875 + ftbfs
Bug #897875 [src:tempest-for-eliza] tempest-for-eliza: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 897731

[Debian Bug Tracking System]

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

> tags 897731 + ftbfs
Bug #897731 [src:cssc] cssc: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 897795

[Debian Bug Tracking System]

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

> tags 897795 + ftbfs
Bug #897795 [src:librcsb-core-wrapper] librcsb-core-wrapper: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 897764

[Debian Bug Tracking System]

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

> tags 897764 + ftbfs
Bug #897764 [src:guymager] guymager: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 897801

[Debian Bug Tracking System]

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

> tags 897801 + ftbfs
Bug #897801 [src:linbox] linbox: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 897711

[Debian Bug Tracking System]

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

> tags 897711 + ftbfs
Bug #897711 [src:auto-07p] auto-07p: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: Re: Bug#897876: theseus: ftbfs with GCC-8

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 gcc-8
Bug #897876 [src:theseus] theseus: ftbfs with GCC-8
Bug reassigned from package 'src:theseus' to 'gcc-8'.
No longer marked as found in versions theseus/3.3.0-6.
Ignoring request to alter fixed versions of bug #897876 to the same values 
previously set
> affects -1 src:theseus
Bug #897876 [gcc-8] theseus: ftbfs with GCC-8
Added indication that 897876 affects src:theseus
> forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86835
Bug #897876 [gcc-8] theseus: ftbfs with GCC-8
Set Bug forwarded-to-address to 
'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86835'.

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

Bug#897876: theseus: ftbfs with GCC-8

[Adrian Bunk]

Control: reassign -1 gcc-8
Control: affects -1 src:theseus
Control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86835

On Fri, May 04, 2018 at 12:23:55PM +, Matthias Klose wrote:
>...
> /usr/bin/gcc -O3 -ffast-math -fstrict-aliasing -funroll-loops 
> -fomit-frame-pointer -Wall -Werror -pedantic -std=c99 -Wno-unused-result 
> -pthread  -c logistic_dist.c
> logistic_dist.c: In function 'evallogisticML':
> logistic_dist.c:172:1: error: 'reciptmp.16' is used uninitialized in this 
> function [-Werror=uninitialized]
>  evallogisticML(const double *x, const int n,
>  ^~
> cc1: all warnings being treated as errors
> make[3]: *** [Makefile:68: logistic_dist.o] Error 1
>...

This is caused by gcc miscompiling the code, reassigning.

cu
Adrian

-- 

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

Bug#897796: marked as done (libreswan: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Fri, 3 Aug 2018 20:33:11 +0300
with message-id <20180803173310.GA10690@localhost>
and subject line Re: Bug#897796: libreswan: ftbfs with GCC-8
has caused the Debian Bug report #897796,
regarding libreswan: ftbfs with GCC-8
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.)


-- 
897796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897796
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libreswan
Version: 3.23-4
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/libreswan_3.23-4_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-8/porting_to.html

[...]
-o ../../OBJ.linux.x86_64/programs/pluto/db_ops.o \
-c /<>/programs/pluto/db_ops.c
cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -I /<>/programs/pluto/linux-copy 
-DNETKEY_SUPPORT -DPFKEY -I/<>/include/unbound -DHAVE_LIBCAP_NG 
-std=gnu99 -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector-all 
-fno-strict-aliasing -fPIE -DPIE -DUSE_DNSSEC 
-DDEFAULT_DNSSEC_ROOTKEY_FILE=\"/usr/share/dns/root.key\" -DUSE_NIC_OFFLOAD 
-DHAVE_LABELED_IPSEC -DLIBCURL -DUSE_LINUX_AUDIT -DUSE_SYSTEMD_WATCHDOG 
-DLIBLDAP -DHAVE_NM -DXAUTH_HAVE_PAM -DUSE_MD5 -DUSE_SHA2 -DUSE_SHA1 -DUSE_AES 
-DUSE_3DES -DUSE_CAMELLIA -DUSE_SERPENT -DUSE_TWOFISH -DUSE_CAST 
-DDEFAULT_RUNDIR=\"/run/pluto\" -DFIPSPRODUCTCHECK=\"/etc/system-fips\" 
-DIPSEC_CONF=\"/etc/ipsec.conf\" -DIPSEC_CONFDDIR=\"/etc/ipsec.d\" 
-DIPSEC_NSSDIR=\"/var/lib/ipsec/nss\" -DIPSEC_CONFDIR=\"/etc\" 
-DIPSEC_EXECDIR=\"/usr/lib/ipsec\" -DIPSEC_SBINDIR=\"/usr/sbin\" 
-DIPSEC_VARDIR=\"/var\" -DPOLICYGROUPSDIR=\"/etc/ipsec.d/policies\" 
-DIPSEC_SECRETS_FI
 LE=\"/etc/ipsec.secrets\" -DFORCE_PR_ASSERT -DUSE_FORK=1 -DUSE_VFORK=0 
-DUSE_DAEMON=0 -DUSE_PTHREAD_SETSCHEDPRIO=1 -DGCC_LINT 
-DALLOW_MICROSOFT_BAD_PROPOSAL -Werror -Wall -Wextra -Wformat 
-Wformat-nonliteral -Wformat-security -Wundef -Wmissing-declarations 
-Wredundant-decls -Wnested-externs -I/<>/ports/linux/include  
-I/<>/include -I/<>/lib/libcrypto 
-I/<>/linux/include -I/usr/include/nss -I/usr/include/nspr 
-pthread -std=gnu99 -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 
-fstack-protector-all -fno-strict-aliasing -fPIE -DPIE -DUSE_DNSSEC 
-DDEFAULT_DNSSEC_ROOTKEY_FILE=\"/usr/share/dns/root.key\" -DUSE_NIC_OFFLOAD 
-DHAVE_LABELED_IPSEC -DLIBCURL -DUSE_LINUX_AUDIT -DUSE_SYSTEMD_WATCHDOG 
-DLIBLDAP -DHAVE_NM -DXAUTH_HAVE_PAM -DUSE_MD5 -DUSE_SHA2 -DUSE_SHA1 -DUSE_AES 
-DUSE_3DES -DUSE_CAMELLIA -DUSE_SERPENT -DUSE_TWOFISH -DUSE_CAST 
-DDEFAULT_RUNDIR=\"/run/pluto\" -DFIPSPRODUCTCHECK=\"/etc/system-fips\" 
-DIPSEC_CONF=\"/etc/ipsec.co
 nf\" -DIPSEC_CONFDDIR=\"/etc/ipsec.d\" -DIPSEC_NSSDIR=\"/var/lib/ipsec/nss\" 
-DIPSEC_CONFDIR=\"/etc\" -DIPSEC_EXECDIR=\"/usr/lib/ipsec\" 
-DIPSEC_SBINDIR=\"/usr/sbin\" -DIPSEC_VARDIR=\"/var\" 
-DPOLICYGROUPSDIR=\"/etc/ipsec.d/policies\" 
-DIPSEC_SECRETS_FILE=\"/etc/ipsec.secrets\" -DFORCE_PR_ASSERT -DUSE_FORK=1 
-DUSE_VFORK=0 -DUSE_DAEMON=0 -DUSE_PTHREAD_SETSCHEDPRIO=1 -DGCC_LINT 
-DALLOW_MICROSOFT_BAD_PROPOSAL -Werror -Wall -Wextra -Wformat 
-Wformat-nonliteral -Wformat-security -Wundef -Wmissing-declarations 
-Wredundant-decls -Wnested-externs -I/<>/ports/linux/include 
-I/<>/linux/include -I../../include -I/usr/include/nss 
-I/usr/include/nspr  -I /<>/programs/pluto/linux-copy 
-DNETKEY_SUPPORT -DPFKEY -I/<>/include/unbound -DHAVE_LIBCAP_NG 
-std=gnu99 -g -O2 -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector-all 
-fno-strict-aliasing -fPIE -DPIE -DUSE_DNSSEC 
-DDEFAULT_DNSSEC_ROOTKEY_FILE

Bug#781538: debian-boot: Total trash on reboot of RAID1 partitions

[zul Ana]

On Mon, 30 Mar 2015 19:08:21 +0100 Chris Bell 
wrote:
> Package: debian-boot
> Version: jessie rc1
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
>
>
>* What led up to the situation?
>  / was installed on first RAID1 pair of partitions,
> 2nd RAID1 pair not used at first,
> /srv on 3rd RAID1 pair.
> I had a problem during configuration, and attempted to re-boot.
> A single-line message appeared
>
> Recovering Journal.
>
> Gave up waiting and installed a new / on to the second RAID1
> pair with the first as /oldroot and the third as /srv.
> Continued with configuration until forced to shut down.
>
> On re-boot the same 0ne-line message appeared
>
> Recovering Journal.
>
> I waited again, but there was no other message or any mention
> of mdadm, so eventually gave up and looked using a knoppix
> disk to find around 10 bytes on each of the 6 partitions (3 pairs)
>
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
> I did not see any mention of mdadm starting, nor was there any
> oportunity to escape (apart from crashing out again)
>
>* What was the outcome of this action?
> Two disks that had been fully tested before use now totally wiped.
> All I can do is attempt data recovery using testdisk
>
>* What outcome did you expect instead?
> I expected the system to start mdadm and then boot as usual.
>
> -- System Information:
> Sent from another system!
> Pentium 3 used as a moderate resource but reliable residential
> mailserver/archiver to run 24/7
>
> # -- System Information:
> # Debian Release: 7.8
> #   APT prefers stable-updates
> #   APT policy: (500, 'stable-updates'), (500, 'stable')
> # Architecture: amd64 (x86_64)
>
> # Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores)
> # Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
> # Shell: /bin/sh linked to /bin/dash
>
>
>

Processed: tagging 886187

[Debian Bug Tracking System]

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

> tags 886187 + pending
Bug #886187 [src:zapping] zapping: Depends on libgnomeui
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#905379: hangs after "'NoneType' object has no attribute 'installEventFilter'"

[Ryan Kavanagh]

Package: anki
Version: 2.1.0+dfsg~rc2-2
Severity: grave
Justification: renders package unusable

Anki presents a dialog with the following error message at startup and
then hangs after the dialog is dismissed:

Error during startup:
Traceback (most recent call last):
  File "/usr/share/anki/aqt/main.py", line 50, in __init__
self.setupUI()
  File "/usr/share/anki/aqt/main.py", line 75, in setupUI
self.setupMainWindow()
  File "/usr/share/anki/aqt/main.py", line 585, in setupMainWindow
tweb =3D self.toolbarWeb =3D aqt.webview.AnkiWebView()
  File "/usr/share/anki/aqt/webview.py", line 114, in __init__
self.focusProxy().installEventFilter(self)
AttributeError: 'NoneType' object has no attribute 'installEventFilter'

Sending ^c after waiting for a minute or so of waiting produces the
error:

Exception ignored in: 
Traceback (most recent call last):
  File "/usr/lib/python3.6/threading.py", line 1294, in _shutdown
t.join()
  File "/usr/lib/python3.6/threading.py", line 1056, in join
self._wait_for_tstate_lock()
  File "/usr/lib/python3.6/threading.py", line 1072, in _wait_for_tstate_lock
elif lock.acquire(block, timeout):
KeyboardInterrupt

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

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

Versions of packages anki depends on:
ii  libjs-jquery3.2.1-1
ii  libjs-jquery-flot   0.8.3+dfsg-1
ii  libjs-jquery-ui 1.12.1+dfsg-5
ii  libjs-mathjax   2.7.4+dfsg-1
ii  libqt5core5a5.11.1+dfsg-6
ii  python3 3.6.6-1
ii  python3-bs4 4.6.0-1
ii  python3-decorator   4.3.0-1
ii  python3-markdown2.6.9-1
ii  python3-pyaudio 0.2.11-1+b2
ii  python3-pyqt5   5.11.2+dfsg-1+b1
ii  python3-pyqt5.qtwebchannel  5.11.2+dfsg-1+b1
ii  python3-pyqt5.qtwebengine   5.11.2+dfsg-1+b1
ii  python3-requests2.18.4-2
ii  python3-send2trash  1.4.2-2

Versions of packages anki recommends:
ii  python3-matplotlib  2.2.2-4+b1

Versions of packages anki suggests:
pn  dvipng   
ii  lame 3.100-2+b1
ii  mplayer  2:1.3.0-8+b2

-- no debconf information

-- 
|)|/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac |  BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature

Processed: severity of 905332 is grave

[Debian Bug Tracking System]

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

> # increasing severity to RC since it will be adressed in DSA but should avoid 
> regression stretch -> buster
> severity 905332 grave
Bug #905332 {Done: Ferenc Wágner } [src:xml-security-c] 
src:xml-security-c: Default KeyInfo resolver doesn't check for empty element 
content
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#899606: NMU madplay to fix maintainer field

[Paul Gevers]

Dear madplay maintainers,

It is my intent to upload madplay to the achieve in about 10 days
containing the changes in the attached debdiff.

Paul
diff -u madplay-0.15.2b/debian/changelog madplay-0.15.2b/debian/changelog
--- madplay-0.15.2b/debian/changelog
+++ madplay-0.15.2b/debian/changelog
@@ -1,3 +1,11 @@
+madplay (0.15.2b-8.3) unstable; urgency=medium
+
+  * Non-maintainer upload
+  * Set maintainer field to madp...@packages.debian.org to have a valid
+address (Closes: #899606)
+
+ -- Paul Gevers   Fri, 03 Aug 2018 20:42:59 +0200
+
 madplay (0.15.2b-8.2) unstable; urgency=medium
 
   * Non-maintainer upload (Closes: #885724)
diff -u madplay-0.15.2b/debian/control madplay-0.15.2b/debian/control
--- madplay-0.15.2b/debian/control
+++ madplay-0.15.2b/debian/control
@@ -2,7 +2,7 @@
 Priority: optional
 Section: sound
 Build-Depends: cdbs, debhelper (>= 4.1.0), gettext, zlib1g-dev, libmad0-dev 
(>= 0.15.0), libid3tag0-dev (>= 0.15.0), autotools-dev, libtool, autoconf, 
automake, libasound2-dev
-Maintainer: Mad Maintainers 
+Maintainer: Mad Maintainers 
 Uploaders: Sam Clegg , Kurt Roeckx 
 Standards-Version: 3.6.1
 Homepage: https://www.underbit.com/products/mad/


signature.asc
Description: OpenPGP digital signature

Processed: tagging 897846

[Debian Bug Tracking System]

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

> tags 897846 + ftbfs
Bug #897846 [src:rheolef] rheolef: ftbfs with GCC-8
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: fixed 903324 in 1.11.1-1

[Debian Bug Tracking System]

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

> fixed 903324 1.11.1-1
Bug #903324 [src:adasockets] adasockets: FTBFS in buster/sid (dh_installdocs: 
Cannot find "README.Debian")
Marked as fixed in versions adasockets/1.11.1-1.
> thanks
Stopping processing here.

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

Processed: affects 902762

[Debian Bug Tracking System]

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

> affects 902762 src:vtk7
Bug #902762 [src:py-ubjson] py-ubjson FTBFS with Python 3.7: NameError: name 
'TYPE_INT8' is not defined
Bug #904661 [src:py-ubjson] vtk7 FTBFS due to uninstallable build dependencies
Added indication that 902762 affects src:vtk7
Added indication that 904661 affects src:vtk7
> thanks
Stopping processing here.

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

Processed: tagging 902459

[Debian Bug Tracking System]

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

> tags 902459 + patch
Bug #902459 [src:faumachine] faumachine: FTBFS in buster/sid (error: 
'faum_dsdt' undeclared)
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#902459: faumachine: FTBFS in buster/sid (error: 'faum_dsdt' undeclared)

[Stefan Potyra]

Hi,

I was also able to reproduce the problem you reported after fixing the
relocation error.

Attached is a debdiff; I committed all changes upstream as well.

Feel free to upload, I'll also ask my regular sponsor, but he's still on
vacation for some time.

Cheers,
  Stefan.
diff -Nru faumachine-20180503/debian/changelog 
faumachine-20180503/debian/changelog
--- faumachine-20180503/debian/changelog2018-05-07 20:49:15.0 
+0200
+++ faumachine-20180503/debian/changelog2018-08-03 20:50:14.0 
+0200
@@ -1,3 +1,13 @@
+faumachine (20180503-2) unstable; urgency=medium
+
+  * Cherry-pick upstream fixes for DBTS: 902459 (Closes: #902459):
++ Add 01-handle-R_X86_64_PLT32.patch to handle new relocations
+  emitted by newer gcc/ld.
++ Add 02-new-iasl.patch to handle changed output of newer
+  iasl verions.
+
+ -- Stefan Potyra   Fri, 03 Aug 2018 20:50:14 +0200
+
 faumachine (20180503-1) unstable; urgency=medium
 
   * New upstream release, highlights:
diff -Nru faumachine-20180503/debian/patches/01-handle-R_X86_64_PLT32.patch 
faumachine-20180503/debian/patches/01-handle-R_X86_64_PLT32.patch
--- faumachine-20180503/debian/patches/01-handle-R_X86_64_PLT32.patch   
1970-01-01 01:00:00.0 +0100
+++ faumachine-20180503/debian/patches/01-handle-R_X86_64_PLT32.patch   
2018-08-03 20:48:11.0 +0200
@@ -0,0 +1,17 @@
+Description: Fix relocation of R_X86_64_PLT32
+Origin: Upstream, c760351c46a9ed1283419df4384dedfa2b4089ad
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902459
+Applied-Upstream: c760351c46a9ed1283419df4384dedfa2b4089ad
+
+Index: faumachine-20180503/chips/qemu/dyngen.c
+===
+--- faumachine-20180503.orig/chips/qemu/dyngen.c
 faumachine-20180503/chips/qemu/dyngen.c
+@@ -2969,6 +2969,7 @@ void gen_code(const char *name, host_ulo
+ reloc_offset, name_, addend);
+ break;
+ case R_X86_64_PC32:
++  case R_X86_64_PLT32:
+ fprintf(outfile, "*(uint32_t *)(gen_code_ptr + 
%d) = %s - (long)(gen_code_ptr + %d) + %d;\n", 
+ reloc_offset, name_, reloc_offset, addend);
+ break;
diff -Nru faumachine-20180503/debian/patches/02-new-iasl.patch 
faumachine-20180503/debian/patches/02-new-iasl.patch
--- faumachine-20180503/debian/patches/02-new-iasl.patch1970-01-01 
01:00:00.0 +0100
+++ faumachine-20180503/debian/patches/02-new-iasl.patch2018-08-03 
20:49:09.0 +0200
@@ -0,0 +1,44 @@
+Description: Adapt to changed iasl output
+Origin: Upstream, cdf517b9a4e9790240f0fb5833e944742dde35be
+Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902459
+Applied-Upstream: cdf517b9a4e9790240f0fb5833e944742dde35be
+
+diff --git a/roms/mb_ga_686dlx_bios/Makefile.am 
b/roms/mb_ga_686dlx_bios/Makefile.am
+index 10913863e..5e388a4f7 100644
+--- a/roms/mb_ga_686dlx_bios/Makefile.am
 b/roms/mb_ga_686dlx_bios/Makefile.am
+@@ -180,9 +180,13 @@ debug:
+ 
+ if HAVE_IASL
+ faum-dsdt.h: faum-dsdt.asl
+-  $(IASL) -p faum-dsdt -on -tc $<
+-  $(RM) faum-dsdt.aml
+-  mv faum-dsdt.hex $@
++  $(IASL) -p faumdsdt -on -tc $<
++  $(RM) faumdsdt.aml
++  sed \
++  -e 's/faumdsdt_aml_code/faum_dsdt/' \
++  -e 's/AmlCode/faum_dst/' \
++  < faumdsdt.hex > $@
++  $(RM) faumdsdt.hex
+ else
+ faum-dsdt.h: ./faum-dsdt.h.shipped
+   cp $< $@
+diff --git a/roms/mb_template_bios/acpi-tables.c 
b/roms/mb_template_bios/acpi-tables.c
+index 0f605fee2..4caca8350 100644
+--- a/roms/mb_template_bios/acpi-tables.c
 b/roms/mb_template_bios/acpi-tables.c
+@@ -92,12 +92,10 @@ struct acpi_dsdt {
+ /* 
+  * Include DSDT, generated by Intel ASL Compiler (iasl)
+  * iasl generates a "unsigned char AmlCode[]" in "faum-dsdt.h", which
+- * is renamed to faum_dsdt by the preprocessor.
++ * is renamed to faum_dsdt by using sed.
+  */
+-#define AmlCode faum_dsdt
+ static const
+ #include "faum-dsdt.h"
+-#undef AmlCode
+ 
+ /* Fixed ACPI Control Structure */
+ static const struct acpi_facs {
diff -Nru faumachine-20180503/debian/patches/series 
faumachine-20180503/debian/patches/series
--- faumachine-20180503/debian/patches/series   1970-01-01 01:00:00.0 
+0100
+++ faumachine-20180503/debian/patches/series   2018-08-03 20:50:08.0 
+0200
@@ -0,0 +1,2 @@
+01-handle-R_X86_64_PLT32.patch
+02-new-iasl.patch

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 905368 https://github.com/statgen/libStatGen/issues/19
Bug #905368 [src:libstatgen] libstatgen: FTBFS in sid
Warning: Unknown package 'src:libstatgen'
Set Bug forwarded-to-address to 
'https://github.com/statgen/libStatGen/issues/19'.
Warning: Unknown package 'src:libstatgen'
>
End of message, stopping processing here.

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

Bug#905382: cgit: CVE-2018-14912: directory traversal vulnerability

[Salvatore Bonaccorso]

Source: cgit
Version: 1.1+git2.10.2-3
Severity: grave
Tags: patch security upstream

Hi,

The following vulnerability was published for cgit.

CVE-2018-14912[0]:
| cgit_clone_objects in CGit before 1.2.1 has a directory traversal
| vulnerability when `enable-http-clone=1` is not turned off, as
| demonstrated by a cgit/cgit.cgi/git/objects/?path=../ request.

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-2018-14912
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14912
[1] https://bugs.chromium.org/p/project-zero/issues/detail?id=1627
[2] https://lists.zx2c4.com/pipermail/cgit/2018-August/004176.html
[3] 
https://git.zx2c4.com/cgit/commit/?id=53efaf30b50f095cad8c160488c74bba3e3b2680

Regards,
Salvatore

Bug#905384: libmuscle1 provides libmuscle-3.7-1 but doesn't ship the library

[Adrian Bunk]

Package: libmuscle1
Version: 3.7+4565-4
Severity: grave

libmuscle-3.7-1 in stretch ships libMUSCLE-3.7.so.1
libmuscle1 in unstable ships libMUSCLE.so.1

It is not clear to me whether or not this library name change
was intended, but providing libmuscle-3.7-1 in libmuscle1 is
currently wrong and the root cause of bugs like #904690.

Bug#905386: libedlib: FTBFS in sid

[Santiago Vila]

Package: src:libedlib
Version: 1.2.3-1
Severity: serious
Tags: ftbfs

Hello Andreas.

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


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DCMAKE_BUILD_TYPE=Release
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_BUILD_TYPE=Release ..
-- The CXX compiler identification is GNU 8.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features

[... snipped ...]

file-rename 's/_static\.a/.a/' `find debian -name libedlib_static.a`
d-shlibmove --commit \
--multiarch \
--devunversioned \
--exclude-la \
--movedev debian/tmp/usr/include/* usr/include \
debian/tmp/usr/lib/*.so
Library package automatic movement utility
set -e
install -d -m 755 debian/libedlib-dev/usr/lib/x86_64-linux-gnu
install -d -m 755 debian/libedlib0/usr/lib/x86_64-linux-gnu
mv debian/tmp/usr/lib/libedlib.a debian/libedlib-dev/usr/lib/x86_64-linux-gnu
mv debian/tmp/usr/lib/libedlib.so debian/libedlib-dev/usr/lib/x86_64-linux-gnu
mv /<>/debian/tmp/usr/lib/libedlib.so.0 
debian/libedlib0/usr/lib/x86_64-linux-gnu
mv /<>/debian/tmp/usr/lib/libedlib.so.1.2.3 
debian/libedlib0/usr/lib/x86_64-linux-gnu
PKGDEV=libedlib-dev
PKGSHL=libedlib0
install -d -m 755 debian/libedlib-dev/usr/include
mv debian/tmp/usr/include/edlib.h debian/libedlib-dev/usr/include
make[1]: Leaving directory '/<>'
   dh_installdocs -a
   dh_installchangelogs -a
   dh_installman -a
   dh_perl -a
   dh_link -a
   dh_strip_nondeterminism -a
   dh_compress -a
   dh_fixperms -a
   dh_missing -a
   dh_strip -a
   dh_makeshlibs -a
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libedlib0/DEBIAN/symbols doesn't match 
completely debian/libedlib0.symbols
--- debian/libedlib0.symbols (libedlib0_1.2.3-1_amd64)
+++ dpkg-gensymbolsd4Wcuf   2018-08-03 21:20:30.459354753 +
@@ -2,7 +2,8 @@
  
_ZN18EqualityDefinitionC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPK17EdlibEqualityPairi@Base
 1.2.3
  
_ZN18EqualityDefinitionC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPK17EdlibEqualityPairi@Base
 1.2.3
  _ZNSt6vectorIcSaIcEE12emplace_backIJcEEEvDpOT_@Base 1.2.3
- _ZNSt6vectorIiSaIiEE12emplace_backIJiEEEvDpOT_@Base 1.2.3
+#MISSING: 1.2.3-1# _ZNSt6vectorIiSaIiEE12emplace_backIJiEEEvDpOT_@Base 1.2.3
+ 
_ZNSt6vectorIiSaIiEE17_M_realloc_insertIJiEEEvN9__gnu_cxx17__normal_iteratorIPiS1_EEDpOT_@Base
 1.2.3-1
  edlibAlign@Base 1.2.3
  edlibAlignmentToCigar@Base 1.2.3
  edlibDefaultAlignConfig@Base 1.2.3
dh_makeshlibs: failing due to earlier errors
make: *** [debian/rules:10: binary-arch] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess returned 
exit status 2


The build was made with "dpkg-buildpackage -B" in my autobuilder,
but it also fails here:

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

Thanks.

Bug#905387: spoa: FTBFS in sid

[Santiago Vila]

Package: src:spoa
Version: 1.1.3-1
Severity: serious
Tags: ftbfs

Hello Andreas.

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


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- -DCMAKE_BUILD_TYPE=Release -Dspoa_build_executable=ON 
-Dspoa_build_tests=ON
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_BUILD_TYPE=None 
-DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var 
-DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_BUILD_TYPE=Release -Dspoa_build_executable=ON 
-Dspoa_build_tests=ON ..
-- The CXX compiler identification is GNU 8.2.0
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features

[... snipped ...]

- 
_ZN4spoa19SimdAlignmentEngine10initializeINS_14InstructionSetIsvPKcRKSt10unique_ptrINS_5GraphESt14default_deleteIS7_EEjjj@Base
 1.1.3
+#MISSING: 1.1.3-1# 
_ZN4spoa19SimdAlignmentEngine10initializeINS_14InstructionSetIivPKcRKSt10unique_ptrINS_5GraphESt14default_deleteIS7_EEjjj@Base
 1.1.3
+#MISSING: 1.1.3-1# 
_ZN4spoa19SimdAlignmentEngine10initializeINS_14InstructionSetIsvPKcRKSt10unique_ptrINS_5GraphESt14default_deleteIS7_EEjjj@Base
 1.1.3
  
_ZN4spoa19SimdAlignmentEngine25align_sequence_with_graphEPKcjRKSt10unique_ptrINS_5GraphESt14default_deleteIS4_EE@Base
 1.1.3
- 
_ZN4spoa19SimdAlignmentEngine5alignINS_14InstructionSetIiSt6vectorISt4pairIiiESaIS6_EEPKcjRKSt10unique_ptrINS_5GraphESt14default_deleteISC_EE@Base
 1.1.3
- 
_ZN4spoa19SimdAlignmentEngine5alignINS_14InstructionSetIsSt6vectorISt4pairIiiESaIS6_EEPKcjRKSt10unique_ptrINS_5GraphESt14default_deleteISC_EE@Base
 1.1.3
+#MISSING: 1.1.3-1# 
_ZN4spoa19SimdAlignmentEngine5alignINS_14InstructionSetIiSt6vectorISt4pairIiiESaIS6_EEPKcjRKSt10unique_ptrINS_5GraphESt14default_deleteISC_EE@Base
 1.1.3
+#MISSING: 1.1.3-1# 
_ZN4spoa19SimdAlignmentEngine5alignINS_14InstructionSetIsSt6vectorISt4pairIiiESaIS6_EEPKcjRKSt10unique_ptrINS_5GraphESt14default_deleteISC_EE@Base
 1.1.3
  _ZN4spoa19SimdAlignmentEngine7reallocEjjj@Base 1.1.3
  _ZN4spoa19SimdAlignmentEngine8preallocEjj@Base 1.1.3
  _ZN4spoa19SimdAlignmentEngineC1ENS_13AlignmentTypeEaaa@Base 1.1.3
@@ -66,8 +66,9 @@
  _ZNK4spoa5Graph23is_topologically_sortedEv@Base 1.1.3
  
_ZNK4spoa5Graph38initialize_multiple_sequence_alignmentERSt6vectorIjSaIjEE@Base 
1.1.3
  _ZNK4spoa5Graph8subgraphEjjRSt6vectorIiSaIiEE@Base 1.1.3
- 
_ZNSt10_HashtableIjjSaIjENSt8__detail9_IdentityESt8equal_toIjESt4hashIjENS1_18_Mod_range_hashingENS1_20_Default_ranged_hashENS1_20_Prime_rehash_policyENS1_17_Hashtable_traitsILb0ELb1ELb121_M_insert_unique_nodeEmmPNS1_10_Hash_nodeIjLb0EEE@Base
 1.1.3
- 
_ZNSt10_HashtableIjjSaIjENSt8__detail9_IdentityESt8equal_toIjESt4hashIjENS1_18_Mod_range_hashingENS1_20_Default_ranged_hashENS1_20_Prime_rehash_policyENS1_17_Hashtable_traitsILb0ELb1ELb19_M_rehashEmRKm@Base
 1.1.3
+#MISSING: 1.1.3-1# 
_ZNSt10_HashtableIjjSaIjENSt8__detail9_IdentityESt8equal_toIjESt4hashIjENS1_18_Mod_range_hashingENS1_20_Default_ranged_hashENS1_20_Prime_rehash_policyENS1_17_Hashtable_traitsILb0ELb1ELb121_M_insert_unique_nodeEmmPNS1_10_Hash_nodeIjLb0EEE@Base
 1.1.3
+ 
_ZNSt10_HashtableIjjSaIjENSt8__detail9_IdentityESt8equal_toIjESt4hashIjENS1_18_Mod_range_hashingENS1_20_Default_ranged_hashENS1_20_Prime_rehash_policyENS1_17_Hashtable_traitsILb0ELb1ELb121_M_insert_unique_nodeEmmPNS1_10_Hash_nodeIjLb0EEEm@Base
 1.1.3-1
+#MISSING: 1.1.3-1# 
_ZNSt10_HashtableIjjSaIjENSt8__detail9_IdentityESt8equal_toIjESt4hashIjENS1_18_Mod_range_hashingENS1_20_Default_ranged_hashENS1_20_Prime_rehash_policyENS1_17_Hashtable_traitsILb0ELb1ELb19_M_rehashEmRKm@Base
 1.1.3
  _ZNSt11_Deque_baseIjSaIjEE17_M_initialize_mapEm@Base 1.1.3
  _ZNSt11_Deque_baseIjSaIjEED1Ev@Base 1.1.3
  _ZNSt11_Deque_baseIjSaIjEED2Ev@Base 1.1.3
@@ -86,16 +87,17 @@
  
_ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJRS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 1.1.3
  
_ZNSt6vectorISt10shared_ptrIN4spoa4EdgeEESaIS3_EE17_M_realloc_insertIJRS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base
 1.1.3
  
_ZNSt6vectorISt10unique_ptrIN4spoa4NodeESt14default_deleteIS2_EESaIS5_EE17_M_realloc_insertIJS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 1.1.3
- _ZNSt6vectorISt4pairIiiESaIS1_EE12emplace_backIJRKjiEEEvDpOT_@Base 1.1.3
- _ZNSt6vectorISt4pairIiiESaIS1_EE12emplace_backIJiRiEEEvDpOT_@Base 1.1.3
- _ZNSt6vectorISt4pairIiiESaIS1_EE12emplace_backIJjiEEEvDpOT_@Base 1.1.3
+#MISSING: 1.1.3-1# 
_ZNSt6vectorISt4pairIiiE

Bug#897773: marked as done (ilmbase: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Sat, 4 Aug 2018 00:42:49 +0300
with message-id <20180803214249.GA13058@localhost>
and subject line Re: Bug#897773: ilmbase: ftbfs with GCC-8
has caused the Debian Bug report #897773,
regarding ilmbase: ftbfs with GCC-8
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.)


-- 
897773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897773
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ilmbase
Version: 2.2.1-2
Severity: normal
Tags: sid buster
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-8/g++-8, but succeeds to build with gcc-7/g++-7. The
severity of this report will be raised before the buster release.

The full build log can be found at:
http://aws-logs.debian.net/2018/05/01/gcc8/ilmbase_2.2.1-2_unstable_gcc8.log.gz
The last lines of the build log are at the end of this report.

To build with GCC 8, either set CC=gcc-8 CXX=g++-8 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-8/porting_to.html

[...]
makeInfinite() for type V2f
makeInfinite() for type V2d
makeInfinite() for type V3s
makeInfinite() for type V3i
makeInfinite() for type V3f
makeInfinite() for type V3d
makeInfinite() for type V4s
makeInfinite() for type V4i
makeInfinite() for type V4f
makeInfinite() for type V4d
extendBy() point for type V2s
extendBy() point for type V2i
extendBy() point for type V2f
extendBy() point for type V2d
extendBy() point for type V3s
extendBy() point for type V3i
extendBy() point for type V3f
extendBy() point for type V3d
extendBy() point for type V4s
extendBy() point for type V4i
extendBy() point for type V4f
extendBy() point for type V4d
extendBy() box for type V2s


Testsuite summary for IlmBase 2.2.1

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

See ImathTest/test-suite.log

make[5]: *** [Makefile:728: test-suite.log] Error 1
make[5]: Leaving directory '/<>/ImathTest'
make[4]: *** [Makefile:836: check-TESTS] Error 2
make[4]: Leaving directory '/<>/ImathTest'
make[3]: *** [Makefile:907: check-am] Error 2
make[3]: Leaving directory '/<>/ImathTest'
make[2]: *** [Makefile:459: check-recursive] Error 1
make[2]: Leaving directory '/<>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
make[1]: *** [debian/rules:36: override_dh_auto_test] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:62: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2
--- End Message ---
--- Begin Message ---
On Fri, May 04, 2018 at 12:22:00PM +, Matthias Klose wrote:
>...
> makeInfinite() for type V2f
> makeInfinite() for type V2d
> makeInfinite() for type V3s
> makeInfinite() for type V3i
> makeInfinite() for type V3f
> makeInfinite() for type V3d
> makeInfinite() for type V4s
> makeInfinite() for type V4i
> makeInfinite() for type V4f
> makeInfinite() for type V4d
> extendBy() point for type V2s
> extendBy() point for type V2i
> extendBy() point for type V2f
> extendBy() point for type V2d
> extendBy() point for type V3s
> extendBy() point for type V3i
> extendBy() point for type V3f
> extendBy() point for type V3d
> extendBy() point for type V4s
> extendBy() point for type V4i
> extendBy() point for type V4f
> extendBy() point for type V4d
> extendBy() box for type V2s
> 
> 
> Testsuite summary for IlmBase 2.2.1
> 

Bug#904133: in telegram-destkop marked as pending

[Nicholas Guriev]

Control: tag -1 pending

Hello,

Bug #904133 in telegram-destkop reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below, and you can check the diff of the fix at:

https://salsa.debian.org/debian/telegram-desktop/commit/53e93da1bb352eb25457afe9dc16336587cdacd7


Disable LTO at all

 * Unfortunately, this mode results to many FTBFS on 32-bit machines.
 * Nevertheless, on amd64 it reduces size of resulting binary by 22%.
 * Now less debug info is generated only for Release builds.

Closes: #904133



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/904133

Processed: Bug#904133 in telegram-destkop marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #904133 [src:telegram-desktop] telegram-desktop: FTBFS with memory 
exhaustion on many targets
Added tag(s) pending.

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

Bug#902467: [pkg-go] Bug#902467: golang-github-kardianos-osext: FTBFS in buster/sid (failing tests)

[Anthony Fok]

HI Shengjing,

On Thu, Aug 2, 2018 at 8:49 AM, Shengjing Zhu  wrote:
> Hi Go team,
>
> On Tue, Jun 26, 2018 at 10:52:52PM +, Santiago Vila wrote:
>> === RUN   TestExecutableDelete
>> --- FAIL: TestExecutableDelete (0.00s)
>>   osext_test.go:135: Child returned 
>> "/tmp/go-build962600465/b001/osext.test (deleted)", not the same file as 
>> "/tmp/go-build962600465/b001/osext.test"
>> FAIL
>> FAIL  github.com/kardianos/osext  0.004s
>>
>
> I think this test doesn't make any sense, we should just skip this test.

That would be the _pragmatic_ thing to do, especially when several
packages still depends on this package, but...

> Reading this test logic, it first reads its self executable path, then
> start it self, then remove original file. It of cause prints the
> "/tmp/go-buildnnn/b001/osext.test (deleted)".
>   ^

Well, yes and no... this error is intermittent (random?), and on
Debian CI and Ubuntu Autopkgtest, the test _usually_ passes:

* https://ci.debian.net/packages/g/golang-github-kardianos-osext/unstable/amd64/
* https://autopkgtest.ubuntu.com/packages/golang-github-kardianos-osext

The corresponding GitHub issue at
https://github.com/kardianos/osext/issues/21 hints at a possible race
condition in the test.

For some reasons, however, I have been unable to reproduce this test
FAIL on my own machine.

> Besides in go >= 1.8, this package's Executable function just fallback
> to go system os package.

So, yes, skipping TestExecutableDelete is the entirely pragmatic thing
to do, but there is this little voice in my gut urging me to learn to
diagnose what exactly triggers this intermittent test failure, and if
it is indeed a race condition, how to fix it?  :-)

Cheers,
Anthony

Bug#904715: startxfce4 fails

[Ian MacKinnell]

Replaced nouveau with nvidia-driver and nvidia-kernel-dkms.

Xfce4 working fine now.

Bug#889878: closed by Picca Frédéric-Emmanuel (Bug#889878: fixed in hkl 5.0.0.2449-1)

[Bernhard Übelacker]

Hello,
tried have a look at this crash.

The hkl-5.0.0.2449/Documentation/figures/.libs/sirius executable makes
use of makecontext/swapcontext to execute function trajectory_gen_generator__.

But it looks like the argument given to makecontext got truncated to 32 bits.

So I looked for HAVE_POINTER_SAFE_MAKECONTEXT that is currently defined as 0.
hkl-5.0.0.2449/hkl/ccan/ccan_config.h
That file looks like generated by configurator executable.
hkl-5.0.0.2449/hkl/ccan/configurator.c
./configurator gcc  > ccan_config.h.tmp && mv ccan_config.h.tmp 
ccan_config.h


Extracted the test for HAVE_POINTER_SAFE_MAKECONTEXT into test.c.
But unfortunately that one is also crashing and therefore configurator defines 
to 0.

[Sa Aug  4 02:11:49 2018] configurator.ou[17970]: segfault at 55c8595ccff8 ip 
7f8b36e50fc0 sp 55c8595cd000 error 7 in ld-2.27.so[7f8b36e42000+1e000]
[Sa Aug  4 02:12:27 2018] sirius[20492]: segfault at 38093728 ip 
5649371a701f sp 564938092f40 error 4 in sirius[56493717c000+2c000]


$ gcc -g -O0 test.c -o test
$ gdb -q --args ./test
Reading symbols from ./test...done.
(gdb) run
Starting program: /home/benutzer/hkl/try1/test 

Program received signal SIGSEGV, Segmentation fault.
0x77fe4fc0 in _dl_name_match_p (name=0x4421 "libc.so.6", 
map=map@entry=0x77ffe170) at dl-misc.c:283
283 dl-misc.c: Datei oder Verzeichnis nicht gefunden.
(gdb) bt
#0  0x77fe4fc0 in _dl_name_match_p (name=0x4421 "libc.so.6", 
map=map@entry=0x77ffe170) at dl-misc.c:283
#1  0x77fde64e in do_lookup_x 
(undef_name=undef_name@entry=0x4442 "setcontext", 
new_hash=new_hash@entry=3641973206, old_hash=old_hash@entry=0x8140 
, ref=0x4390, 
result=result@entry=0x8150 , scope=, 
i=, version=0x77fbe560, flags=1, skip=, 
type_class=1, undef_map=0x77ffe170) at dl-lookup.c:541
#2  0x77fdf217 in _dl_lookup_symbol_x (undef_name=0x4442 
"setcontext", undef_map=0x77ffe170, ref=ref@entry=0x81e8 
, symbol_scope=0x77ffe4c8, version=0x77fbe560, 
type_class=type_class@entry=1, flags=1, skip_map=) at 
dl-lookup.c:813
#3  0x77fe38c3 in _dl_fixup (l=, reloc_arg=) at ../elf/dl-runtime.c:112
#4  0x77fea3c3 in _dl_runtime_resolve_fxsave () at 
../sysdeps/x86_64/dl-trampoline.h:125
#5  0x51b5 in fn (p=0x8080 , q=0x7f7f) 
at test.c:11
#6  0x77e4c600 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x in ?? ()
(gdb) list test.c:1,+23
1   #include 
2   #include 
3   static int worked = 0;
4   static char stack[1024];
5   static ucontext_t a, b;
6   static void fn(void *p, void *q) {
7   void *cp = &worked;
8   void *cq = (void *)(~((ptrdiff_t)cp));
9   if ((p == cp) && (q == cq))
10  worked = 1;
11  setcontext(&b);
12  }
13  int main(void) {
14  void *ap = &worked;
15  void *aq = (void *)(~((ptrdiff_t)ap));
16  getcontext(&a);
17  a.uc_stack.ss_sp = stack;
18  a.uc_stack.ss_size = sizeof(stack);
19  makecontext(&a, (void (*)(void))fn, 2, ap, aq);
20  swapcontext(&b, &a);
21  return worked ? 0 : 1;
22  }
23


This test is crashing also at a stretch amd64 VM, but is
working in a jessie amd64 VM.

By using swapcontext instead of setcontext (like in attached
patch) the test succeeds, HAVE_POINTER_SAFE_MAKECONTEXT get defined
to 1, and the package could be built successfully, at least in my
buster amd64 VM.

Kind regards,
Bernhard







export LD_LIBRARY_PATH=/home/benutzer/hkl/try1/hkl-5.0.0.2449/hkl/.libs
benutzer@debian:~/hkl/try1/hkl-5.0.0.2449/Documentation/figures$ gdb --q --args 
.libs/sirius
directory /home/benutzer/hkl/try1/hkl-5.0.0.2449/hkl
directory /home/benutzer/hkl/try1/hkl-5.0.0.2449/hkl/api2
directory /home/benutzer/hkl/try1/hkl-5.0.0.2449/hkl/ccan/coroutine
directory /home/benutzer/hkl/try1/hkl-5.0.0.2449/hkl/ccan/generator
set height 0
set width 0
set pagination off
b main
run
b coroutine.c:226
record
cont




(gdb) bt
#0  0x55592c97 in coroutine_init_ (cs=cs@entry=0x555c5fd0, 
fn=fn@entry=0x55594000 , 
arg=arg@entry=0x555c6730, stack=stack@entry=0x555c5fb8) at 
coroutine/coroutine.c:210
#1  0x55592d93 in generator_new_ (fn=0x55594000 
, retsize=) at 
generator/generator.c:41
#2  0x55594585 in trajectory_gen (tconfig=...) at hkl2.c:246
#3  0x55594639 in Trajectory_solve (tconfig=..., gconfig=..., 
sconfig=..., move=1) at hkl2.c:288
#4  0x555697cc in main () at sirius.c:161
(gdb) list coroutine.c:193,+20
193 #if HAVE_UCONTEXT
194 void coroutine_init_(struct coroutine_state *cs,
195  void (*fn)(void *), void *arg,
196  struct coroutine_stack *stack)
197 {
198 getcontext (&cs->uc);
199
200  

Bug#903533: yapf FTBFS with Python 3.7 as supported version

[Nicholas D Steeves]

On Fri, Aug 03, 2018 at 01:56:53PM +0100, Ana Custura wrote:
> Hi Nicholas,
> 
> I'm on it
> 
> Ana

Thank you Ana :-)

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#904524: marked as done (kdump-tools: fails to install with --install-recommends)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 02:38:25 +
with message-id 
and subject line Bug#904524: fixed in makedumpfile 1:1.6.4-2
has caused the Debian Bug report #904524,
regarding kdump-tools: fails to install with --install-recommends
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.)


-- 
904524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904524
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kdump-tools
Version: 1:1.6.3-2
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...):

  Setting up kdump-tools (1:1.6.3-2) ...
  
  Creating config file /etc/default/kdump-tools with new version
  dpkg: error processing package kdump-tools (--configure):
   installed kdump-tools package post-installation script subprocess returned 
error exit status 1


This only seems to happen on installation/upgrades with
--install-recommends enabled.


cheers,

Andreas


kdump-tools_1:1.6.3-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: makedumpfile
Source-Version: 1:1.6.4-2

We believe that the bug you reported is fixed in the latest version of
makedumpfile, 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 904...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thadeu Lima de Souza Cascardo  (supplier of updated 
makedumpfile 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, 26 Jul 2018 10:02:40 -0300
Source: makedumpfile
Binary: makedumpfile kdump-tools
Architecture: source
Version: 1:1.6.4-2
Distribution: unstable
Urgency: medium
Maintainer: Louis Bouchard 
Changed-By: Thadeu Lima de Souza Cascardo 
Description:
 kdump-tools - scripts and tools for automating kdump (Linux crash dumps)
 makedumpfile - VMcore extraction tool
Closes: 904524
Changes:
 makedumpfile (1:1.6.4-2) unstable; urgency=medium
 .
   * Ignore uninstalled kernels when doing the kernel postinst. (Closes: 
#904524)
Checksums-Sha1:
 c633181091f15f6a2e7265fb163a03bc7c28bd45 2293 makedumpfile_1.6.4-2.dsc
 acb3eb1a9b9e8bd76ff48c8faf36f52edae5da8f 35564 
makedumpfile_1.6.4-2.debian.tar.xz
Checksums-Sha256:
 a89efd74d33c0a123c8ec598d199125bac7a9745121205a0366b5a5d76dc0c54 2293 
makedumpfile_1.6.4-2.dsc
 d39607d0300af0d9d640ba21b95d4b42821b518fad715e8e56bb7c918c2ae850 35564 
makedumpfile_1.6.4-2.debian.tar.xz
Files:
 da357b0471a9c1d0f1eed991767436e6 2293 devel optional makedumpfile_1.6.4-2.dsc
 3ce5720ac6212216de1a8dc27c6dd01c 35564 devel optional 
makedumpfile_1.6.4-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE34E7Im3TmixTD299CrplA3L9lXEFAltlBakACgkQCrplA3L9
lXFUehAAkmG7KPmD9h+0mrjjBj36G06vOVDzAx6JxG28xOkGbwC972rzP3cWQwc3
PrCedOfwsg4oUQMpAMFh7aQihnWhZNMl+vfaV8gplAPdcICS0RxjJEq2X+9PdVJ6
hAx8Xyynh7UsafWq3s3q0bOJ8IlpRQUua7rxs/xjn5p4XtlsPpTeLbj3/jYyxDAe
C4q17qJ1GWAKsK/UKrGChknxtqluY79K9c4b8VxK8aYZGaevmz3kk1R+K5G1h8ts
ZuMKdGuWVsku5c3bmN/gAooSZ/djkUHxDlAsyYloxtSTS+rXqvfwZbVyXul/qQO2
CQ3FF044riT1Raqveyh1Fn8tw5f7qUqPL7/HuYFeHgJv1693RfT4fUJ1PLeiB4g2
j3wO2HkDJ1bJ8yG7xMJJOeQbO4lZFhi1+k5S1TKqlx/0oRc1uB3jHRBSjhmikj01
rvbHn9LLNsveWnnLm+Dnljk5MHZXt3K0P0+FlrkUDmHb5Z9qEiDPCDNJ+28Qhrg9
HCJGjssxGuYNDgYWu05PC3/i0TIxr1CehowLgXSG+Lt74nauGQsOAS0iAn7PaewB
t1Ak8LE+WO9Run9I8jZaoJX7CIs7HHmhjwaEf4lE+qgFbZ+CwSUWvIl8DRcIv+LF
+BB8F21s958D6pMwD/eijFc5r0M/b4WYST6QUlMvu0oG4yCI0cY=
=hhha
-END PGP SIGNATURE End Message ---

Bug#899606: NMU madplay to fix maintainer field

[Kurt Roeckx]

On Fri, Aug 03, 2018 at 08:50:37PM +0200, Paul Gevers wrote:
> Dear madplay maintainers,
> 
> It is my intent to upload madplay to the achieve in about 10 days
> containing the changes in the attached debdiff.

Just upload it


Kurt

Bug#903514: gimp won't launch

[James Van Zandt]

Thanks, Benedict - the same solution worked for me.

Specifically:

   sudo apt-get install libopenblas-base- libopenblas-dev- \
 libblas3 liblapack3 libblas-dev liblapack-dev

Unfortunately julia and libjulia0.6 were also removed here, since they
depend on libopenblas-base.  I intend to report this as a bug, and request
that they depend instead on the virtual packages libblas.so.3 and
liblapack.so.3 (which can also be provided by liblapack3 and libblas3,
resp.).

Processed: lower severity of GCC issue

[Debian Bug Tracking System]

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

> severity 897876  important
Bug #897876 [gcc-8] theseus: ftbfs with GCC-8
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Bug#899850: marked as done (aspell-fa: Invalid maintainer address debian-arabic-packa...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 03:18:54 +
with message-id 
and subject line Bug#899850: fixed in aspell-fa 0.11-0-4
has caused the Debian Bug report #899850,
regarding aspell-fa: Invalid maintainer address 
debian-arabic-packa...@lists.alioth.debian.org
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.)


-- 
899850: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899850
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:aspell-fa
Version: 0.11-0-3
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of aspell-fa,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package aspell-fa since the list address
debian-arabic-packa...@lists.alioth.debian.org used in the Maintainer:
field was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
debian-arabic-packa...@lists.alioth.debian.org is 6.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: aspell-fa
Source-Version: 0.11-0-4

We believe that the bug you reported is fixed in the latest version of
aspell-fa, 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 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lior Kaplan  (supplier of updated aspell-fa 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: Sat, 04 Aug 2018 04:02:37 +0300
Source: aspell-fa
Binary: aspell-fa
Architecture: source
Version: 0.11-0-4
Distribution: unstable
Urgency: medium
Maintainer: Lior Kaplan 
Changed-By: Lior Kaplan 
Description:
 aspell-fa  - Persian dictionary for GNU Aspell
Closes: 899850
Changes:
 aspell-fa (0.11-0-4) unstable; urgency=medium
 .
   * Update maintainer address (Closes: #899850)
Checksums-Sha1:
 aa2720407a9d7b3886f11f6bb9670d7e90b88746 1911 aspell-fa_0.11-0-4.dsc
 de19f8483e9f6cb3fb194231666b12729d9aba23 2648 aspell-fa_0.11-0-4.debian.tar.xz
 13f87f399df713fe4004bfcc0181b45b22070c53 5590 
aspell-fa_0.11-0-4_amd64.buildinfo
Checksums-Sha256:
 c1c3a3dcad2c8057647f4db1c2251da04705c3781c76772b1a131889d22be1aa 1911 
aspell-fa_0.11-0-4.dsc
 99ff8400c76407bfe8919ae32b8886473769b3620abb8a719e2107b07195a64d 2648 
aspell-fa_0.11-0-4.debian.tar.xz
 6181fdb9ec35ebe1224531ae0d45163b761ec5b907935c93c3b28e5a4e34292a 5590 
aspell-fa_0.11-0-4_amd64.buildinfo
Files:
 20320f00ad2370ffaa83a0b88108448b 1911 text optional aspell-fa_0.11-0-4.dsc
 91c349c419590a6d7798304f8c00 2648 text optional 
aspell-fa_0.11-0-4.debian.tar.xz
 9885bb853d22b34dd6be115b5694e975 5590 text optional 
aspell-fa_0.11-0-4_amd64.buildinfo

-BEGIN PGP SIGNATURE

Bug#902631: devscripts: CI fails in unstable due to Python 3.7

[Stuart Prescott]

Hi Sandro,

thanks for this update

On Thursday, 2 August 2018 12:39:18 AEST Sandro Tosi wrote:
> there are currently 2 source packages:
> 
> astroid: on the 1.x branch, builds python-astroid and python3-astroid
> pylint: on the 1.x branch, builds pylint (depends on python-astroid),
> pylint3 (depends on python3-astroid), pylint-doc
> 
> the only way forward to keep compat with python2 while supporting 3.7 i see
> is:
> 
> astroid: uses the 2.x branch, builds only python3-astroid
> pylint: uses the 2.x branch, builds only pylint3, pylint-doc
> NEW astroid2: remains on the 1.x branch, builds only python-astroid
> NEW pylint2: remains on the 1.x branch, builds only pylint (depending
> on python-astroid)
> 
> astroid2 and pylint2 will be dropped after buster is released, keeping
> only astroid and pylint in bullseye

I think this is a perfectly sensible way of proceeding.

> adding ftpmasters in the loop as a headsup since this plan would
> require a bit of coordination to reduce users disruption during the
> migration of the bin pkgs from one src pkg to the new ones.

I don't think there is actually any assistance required from the ftpmasters 
beyond accepting the NEW package. I've not found the relevant document, but my 
understanding is that a source package can take over the binary packages from 
another source package by simply uploading the new one to NEW, and once it is 
accepted, upload the old one without the extra stanzas in d/control.
 
> what people feel about it? just to make it clear: i'm not really
> excited about the package duplication, although it's the only viable
> solution i can see for now. comments/suggestions welcome

We've got a few examples of this in the archive where there is no polyglot 
version of a module or package and so two versions are shipped. We've even had 
some modules like that since wheezy. These are all transitional in the sense 
that the extra packages will disappear from Debian soon enough.

Please let me know if I can be of assistance with this work.

cheers
Stuart

-- 
Stuart Prescotthttp://www.nanonanonano.net/   stu...@nanonanonano.net
Debian Developer   http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7

Bug#904690: marked as done (progressivemauve: broken in buster: error while loading shared libraries: libMUSCLE-3.7.so.1)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 03:48:55 +
with message-id 
and subject line Bug#904690: fixed in libmuscle 3.7+4565-5
has caused the Debian Bug report #904690,
regarding progressivemauve: broken in buster: error while loading shared 
libraries: libMUSCLE-3.7.so.1
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.)


-- 
904690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: progressivemauve
Version: 1.2.0+4713+dfsg-1
Severity: grave
Justification: renders package unusable

Triggered by the failure of the autopkgtest reference¹ I installed
progressivemauve on my buster system. It can't even start.

paul@testavoira ~ $ progressiveMauve
progressiveMauve: error while loading shared libraries: libMUSCLE-3.7.so.1: 
cannot open shared object file: No such file or directory
paul@testavoira ~ $ progressiveMauve -h
progressiveMauve: error while loading shared libraries: libMUSCLE-3.7.so.1: 
cannot open shared object file: No such file or directory

progressivemauve is part of the auto-libgenome transition² which linked me to
the build log which show that it failed to rebuild for libmuscle (I actually
didn't look up why it was binNMUd for that). The current state of
progressivemauve in buster is broken. Please investigate how to fix it.

Paul

¹ https://ci.debian.net/packages/p/progressivemauve/testing/amd64/
² https://release.debian.org/transitions/html/auto-libgenome.html

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

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

Versions of packages progressiveMauve depends on:
ii  libboost-filesystem1.62.0   1.62.0+dfsg-8
ii  libboost-iostreams1.62.01.62.0+dfsg-8
ii  libboost-program-options1.62.0  1.62.0+dfsg-8
ii  libboost-system1.62.0   1.62.0+dfsg-8
ii  libc6   2.27-3
ii  libgcc1 1:8.1.0-10
ii  libgenome-1.3-0v5   1.3.1-10
ii  libmems-1.6-1v5 1.6.0+4725-4
ii  libmuscle1 [libmuscle-3.7-1]3.7+4565-4
ii  libstdc++6  8.1.0-10

progressiveMauve recommends no packages.

progressiveMauve suggests no packages.

-- no debconf information



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libmuscle
Source-Version: 3.7+4565-5

We believe that the bug you reported is fixed in the latest version of
libmuscle, 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 904...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libmuscle 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: Sat, 04 Aug 2018 05:12:53 +0200
Source: libmuscle
Binary: libmuscle-dev libmuscle1
Architecture: source
Version: 3.7+4565-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libmuscle-dev - multiple alignment development library for protein sequences
 libmuscle1 - multiple alignment library for protein sequences
Closes: 904690
Changes:
 libmuscle (3.7+4565-5) unstable; urgency=medium
 .
   * Provide link to old versioned lib
 Closes: #904690
Checksums-Sha1:
 d605008a2ceb9e64c5e575710bd7da7515941e48 2073 libmuscle_3.7+4565-5.dsc
 3433bfafe300fd0c9b2dfcd474313efa6f29cd5f 11904 
libmuscle_3.7+4565-5.debian.tar.xz
Checksums-Sha256:
 6794196ba02d78804f6ef4acbe83d04f905488c50d6a151ac7db66d7f4818c92 2073 
libmuscle_3.7+4565-5.dsc
 4f572e9825092b2c81d7283611a3383bad5805bef5ccc26b426d5815c79ff505 11904 
libmuscle_3.7+4565-5.debian.tar.xz
Files:
 cf86d271449672cd38d379fa006c73bc 2073 science optional libmuscle_3.7+4565-5.dsc
 6e40e1b0ede47b0d5c96726470e300f6 11904 science optional 
libmuscle_3.7+4565-5.debian.tar.xz

-BEGIN PG

Processed: your mail

[Debian Bug Tracking System]

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

> severity 904711 grave
Bug #904711 [src:wolfssl] wolfssl: no 
Severity set to 'grave' from 'important'
> tags 904711 confirmed pending
Bug #904711 [src:wolfssl] wolfssl: no 
Added tag(s) pending and confirmed.
> tags 904710 confirmed pending
Bug #904710 [src:wolfssl] wolfssl: tls 1.3 not built
Added tag(s) confirmed and pending.
> thanks
Stopping processing here.

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

Bug#904711: On Mentors

[Felix Lechner]

Hi, I am waiting for a sponsor to upload the fixed version. If you are
in a hurry, please build from Mentors
(https://mentors.debian.net/package/wolfssl). Thank you!

Bug#905403: graphite-api ftbfs

[Matthias Klose]

Package: src:graphite-api
Version: 1.1.3-3
Severity: serious
Tags: sid buster

missing build dependencies?

running build_ext
tests (unittest.loader._FailedTest) ... ERROR

==
ERROR: tests (unittest.loader._FailedTest)
--
ImportError: Failed to import test module: tests
Traceback (most recent call last):
  File "/usr/lib/python3.6/unittest/loader.py", line 153, in loadTestsFromName
module = __import__(module_name)
  File "/<>/tests/__init__.py", line 15, in 
from graphite_api.app import app
  File "/<>/graphite_api/app.py", line 24, in 
from .render.glyph import GraphTypes
  File "/<>/graphite_api/render/glyph.py", line 15, in 
import cairocffi as cairo
  File "/usr/lib/python3/dist-packages/cairocffi/__init__.py", line 18, in 

from ._ffi import ffi
  File "/usr/lib/python3/dist-packages/cairocffi/_ffi.py", line 3, in 
from xcffib._ffi import ffi as _ffi0
ModuleNotFoundError: No module named 'xcffib'


--
Ran 1 test in 0.000s

FAILED (errors=1)
Test failed: 
error: Test failed: 
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1:
python3.6 setup.py test
dh_auto_test: pybuild --test -i python{version} -p 3.6 returned exit code 13
make: *** [debian/rules:6: build] Error 25

Bug#904711: marked as done (wolfssl: no )

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 06:04:05 +
with message-id 
and subject line Bug#904711: fixed in wolfssl 3.15.3+dfsg-2
has caused the Debian Bug report #904711,
regarding wolfssl: no 
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.)


-- 
904711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wolfssl
Severity: important

Dear Maintainer,

When compiling the examples:

gcc -o client-tls-perf client-tls-perf.c -Wall -I/usr/local/include -Os 
-L/usr/local/lib -lm -lwolfssl
client-tls-perf.c:28:10: fatal error: wolfssl/options.h: No such file or 
directory
 #include 

This options.h file shares the config wolfssl was built with, and must be 
shipped.

-- System Information:
Debian Release: 9.4
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: arm64 (aarch64)

Kernel: Linux 4.15.11-mainline-rev1 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: wolfssl
Source-Version: 3.15.3+dfsg-2

We believe that the bug you reported is fixed in the latest version of
wolfssl, 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 904...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Felix Lechner  (supplier of updated wolfssl 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: Fri, 03 Aug 2018 20:32:42 -0700
Source: wolfssl
Binary: libwolfssl18 libwolfssl-dev
Architecture: source amd64
Version: 3.15.3+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Felix Lechner 
Changed-By: Felix Lechner 
Description:
 libwolfssl-dev - Development files for the wolfSSL encryption library
 libwolfssl18 - wolfSSL encryption library
Closes: 904710 904711
Changes:
 wolfssl (3.15.3+dfsg-2) unstable; urgency=medium
 .
   * Ship wolfssl/control.h (Closes: #904711)
   * Enabled TLS 1.3 (Closes: #904710)
Checksums-Sha1:
 3215252c26ebfd4a93dc412bb4a30216ffc0dfdf 1860 wolfssl_3.15.3+dfsg-2.dsc
 62e706da9c4ffcb6397f8f1825bcc7c145d9ea85 4297490 
wolfssl_3.15.3+dfsg.orig.tar.gz
 5a37795cd0a28f6ad00b6e629fdac2eb24910aff 17176 
wolfssl_3.15.3+dfsg-2.debian.tar.xz
 34df9bfeb28e833a251a54102bc1f0f4d20bb00f 693684 
libwolfssl-dev_3.15.3+dfsg-2_amd64.deb
 d3bac9571a4e9016b449cdc084d9e48cf332edbf 1550176 
libwolfssl18-dbgsym_3.15.3+dfsg-2_amd64.deb
 0a837f14ccf377f57fc00b3f370924cf862dbbf1 470100 
libwolfssl18_3.15.3+dfsg-2_amd64.deb
 0731d59dac6038bd1eac8ba75bc944d146eecb4c 6068 
wolfssl_3.15.3+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 ac93702c4e45df71ef59c8c61a9ee86adadc1e97b3169672c7f4a090c1fe05a8 1860 
wolfssl_3.15.3+dfsg-2.dsc
 1483f124a221989414d4f650b9b7f09b3714ee8c13b12e5871d774f899da756d 4297490 
wolfssl_3.15.3+dfsg.orig.tar.gz
 50754389d81803c0f20841e7d8d7e4ce2143de0af7bcd3c48aeabb1e283b359a 17176 
wolfssl_3.15.3+dfsg-2.debian.tar.xz
 e71d76ad27934a77f3ab959247f705b92710768043d21a93f07be408eabcda34 693684 
libwolfssl-dev_3.15.3+dfsg-2_amd64.deb
 22fba255b0fd5e9e25c00bfc3ffcbe225b0bfd8290b84c8b45d1339a7d99b6c5 1550176 
libwolfssl18-dbgsym_3.15.3+dfsg-2_amd64.deb
 18a46828be4fa4e93ece735248fa823fda3a1964ec7c9640fd26386be7f51fa5 470100 
libwolfssl18_3.15.3+dfsg-2_amd64.deb
 cede5a03c15e6644398a26416cec2633615b6c0e24fc0cfb4690615420333758 6068 
wolfssl_3.15.3+dfsg-2_amd64.buildinfo
Files:
 7b5b7e0c706bf4ef5fee1084dab90983 1860 libs optional wolfssl_3.15.3+dfsg-2.dsc
 91ae11cc9591833624e4066dc293139c 4297490 libs optional 
wolfssl_3.15.3+dfsg.orig.tar.gz
 9143906d87b2e15a80e6151c6c5e16be 17176 libs optional 
wolfssl_3.15.3+dfsg-2.debian.tar.xz
 3c5de475953d9f94604e59ed0b430cf2 693684 libdevel optional 
libwolfssl-dev_3.15.3+dfsg-2_amd64.deb
 ac75c747812ca2143066ab56f372af27 1550176 debug optional 
libwolfssl18-dbgsym_3.15.3+dfsg-2_amd64.deb
 688cbf493d5ee122668394d2e47f2598 470100 libs optional 
libwolfssl18_3.15.3+dfsg-2_amd64.deb
 f884c40

Bug#905369: marked as done (mshr: FTBFS in sid)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 06:03:52 +
with message-id 
and subject line Bug#905369: fixed in mshr 2018.1.0+dfsg1-2
has caused the Debian Bug report #905369,
regarding mshr: FTBFS in sid
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.)


-- 
905369: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905369
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mshr
Version: 2017.2.0+dfsg1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
dh build-indep --buildsystem=cmake \
  --with python2,python3
   dh_update_autotools_config -i -O--buildsystem=cmake
   dh_autoreconf -i -O--buildsystem=cmake
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/mshr-2017.2.0+dfsg1'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
for v in python3.6 python3.7  python2.7; do \
dh_auto_configure 
--builddirectory=/<>/mshr-2017.2.0+dfsg1/debian/build-$v -- \
   -D PYTHON_EXECUTABLE:FILEPATH=/usr/bin/$v \

[... snipped ...]

[ 80%] Linking CXX shared library libmshr.so
/usr/bin/cmake -E cmake_link_script CMakeFiles/mshr.dir/link.txt --verbose=1
/usr/bin/c++ -fPIC -fpermissive -std=c++0x -Wall -O3 -DNDEBUG -Wl,-z,relro 
-shared -Wl,-soname,libmshr.so.2017.2 -o libmshr.so.2017.2.0 
CMakeFiles/mshr.dir/src/ASCFileReader.cpp.o 
CMakeFiles/mshr.dir/src/CSGCGALDomain2D.cpp.o 
CMakeFiles/mshr.dir/src/CSGCGALDomain3D.cpp.o 
CMakeFiles/mshr.dir/src/CSGCGALMeshGenerator2D.cpp.o 
CMakeFiles/mshr.dir/src/CSGCGALMeshGenerator3D.cpp.o 
CMakeFiles/mshr.dir/src/CSGGeometries3D.cpp.o 
CMakeFiles/mshr.dir/src/CSGGeometry.cpp.o 
CMakeFiles/mshr.dir/src/CSGOperators.cpp.o 
CMakeFiles/mshr.dir/src/CSGPrimitives2D.cpp.o 
CMakeFiles/mshr.dir/src/CSGPrimitives3D.cpp.o 
CMakeFiles/mshr.dir/src/DolfinMeshUtils.cpp.o 
CMakeFiles/mshr.dir/src/GlobalInitializer.cpp.o 
CMakeFiles/mshr.dir/src/MeshGenerator.cpp.o 
CMakeFiles/mshr.dir/src/Meshes.cpp.o 
CMakeFiles/mshr.dir/src/OFFFileReader.cpp.o 
CMakeFiles/mshr.dir/src/STLFileReader.cpp.o 
CMakeFiles/mshr.dir/src/SurfaceConsistency.cpp.o 
CMakeFiles/mshr.dir/src/SurfaceReconstruction.cpp.o 
CMakeFiles/mshr.dir/src/TetgenMes
 hGenerator3D.cpp.o /usr/lib/x86_64-linux-gnu/libboost_system.so 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so 
/usr/lib/x86_64-linux-gnu/libboost_program_options.so 
/usr/lib/x86_64-linux-gnu/libgmp.so /usr/lib/x86_64-linux-gnu/libmpfr.so -ltet 
/usr/lib/x86_64-linux-gnu/libdolfin.so.2018.1.0 
/usr/lib/x86_64-linux-gnu/libboost_system.so 
/usr/lib/x86_64-linux-gnu/libboost_filesystem.so 
/usr/lib/x86_64-linux-gnu/libboost_program_options.so 
/usr/lib/x86_64-linux-gnu/libgmp.so /usr/lib/x86_64-linux-gnu/libmpfr.so -ltet 
/usr/lib/x86_64-linux-gnu/libboost_timer.so 
/usr/lib/x86_64-linux-gnu/hdf5/openmpi/libhdf5.so 
/usr/lib/x86_64-linux-gnu/libsz.so /usr/lib/x86_64-linux-gnu/libz.so 
/usr/lib/x86_64-linux-gnu/libdl.so -lm 
/usr/lib/slepcdir/slepc3.9/x86_64-linux-gnu-real/lib/libslepc_real.so 
/usr/lib/petscdir/petsc3.9/x86_64-linux-gnu-real/lib/libpetsc_real.so 
/usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi_cxx.so 
/usr/lib/x86_64-linux-gnu/openmpi/lib/libmpi.so 
/usr/bin/cmake -E cmake_symlink_library libmshr.so.2017.2.0 libmshr.so.2017.2 
libmshr.so
make[4]: Leaving directory 
'/<>/mshr-2017.2.0+dfsg1/debian/build-python2.7'
[ 80%] Built target mshr
make -f CMakeFiles/mshrable.dir/build.make CMakeFiles/mshrable.dir/depend
make[4]: Entering directory 
'/<>/mshr-2017.2.0+dfsg1/debian/build-python2.7'
cd /<>/mshr-2017.2.0+dfsg1/debian/build-python2.7 && /usr/bin/cmake 
-E cmake_depends "Unix Makefiles" /<>/mshr-2017.2.0+dfsg1 
/<>/mshr-2017.2.0+dfsg1 
/<>/mshr-2017.2.0+dfsg1/debian/build-python2.7 
/<>/mshr-2017.2.0+dfsg1/debian/build-python2.7 
/<>/mshr-2017.2.0+dfsg1/debian/build-python2.7/CMakeFiles/mshrable.dir/DependInfo.cmake
 --color=
Scanning dependencies of target mshrable
make[4]: Leaving directory 
'/<>/mshr-2017.2.0+dfsg1/debian/build-python2.7'
make -f CMakeFiles/mshrable.dir/build.make CMakeFiles/mshrable.dir/build
make[4]: Entering directory 
'/<>/mshr-2017.2.0+dfsg1/debian/build-python2.7'
[ 84%] Building CXX object CMakeFiles/mshrable.dir/app/mshrable.cpp.o
/usr/bin/c++  -

Bug#842815: Help needed for HDF5 1.10 transition of libsis-jhdf5-java

[Andreas Tille]

Hello Bernd,

On Mon, May 28, 2018 at 09:18:28AM +0200, Bernd Rinn wrote:
> Hello Andreas,
> 
> On 05/27/2018 07:12 AM, Andreas Tille wrote:
> > Hello Bernd,
> > 
> > sorry for nagging again but we now have another Dependency from
> > sis-jhdf5 which makes a fix for this issue even more interesting.  As I
> > said before I would also try a patch if you might hesitate to issue a
> > completely new release.
> 
> It is embarrassing to admit that I still haven't found the time to port
> JHDF5 to HDF5 1.10.
> 
> If you can come up with a patch to bridge to time that would be greatly
> appreciated!

Since I personally do not even know what HDF5 is I can not help myself
and as far as Gilles Filippini stated[1] chances are pretty low that we
from Debian will be able to come up with a patch.  What do you think
about the remark

   Have you considered using libhdf5-java[2] or libjhdf5-java instead?

Well, several projects are using libsis-hdf5-java but it might be to
join forces with one single Java library which keeps up with current
development.  I have no idea in how far libsis-hdf5-java is different
for the other libs but could you somehow imagine to unify the interface
and join forces?

Kind regards

  Andreas.

[1] https://lists.debian.org/debian-science/2018/05/msg00112.html
[2] https://support.hdfgroup.org/HDF5/
[3] 

> > On Wed, Sep 06, 2017 at 12:50:56PM +0200, Andreas Tille wrote:
> >> Hello Bernd,
> >>
> >> On Wed, 23 Nov 2016 06:54:21 +0100, you wrote
> >>> the migration of JHDF5 to HDF5 1.10 is ongoing and mostly depend on me
> >>> having a block of time I can spend on it. Your analysis of the work that
> >>> needs to be done is right from what I can see. The plan is to switch to
> >>> using the JNI library from the HDF group wherever possible (it may still
> >>> be necessary to have a small JNI library though as some calls appear to
> >>> be missing).
> >>>
> >>> I will keep you updated.
> >>
> >> Is there any news, may be only a patch for the existing version we
> >> could try to fix the Debian package?
> >>
> >> Kind regards
> >>
> >>Andreas.
> >>
> >> -- 
> >> http://fam-tille.de
> >>
> >> ___
> >> Debian-med-packaging mailing list
> >> debian-med-packag...@lists.alioth.debian.org
> >> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging
> >>
> > 
> 
> -- 
> Dr. Bernd Rinn
> Head Scientific IT Services
> ETH Zurich IT Services
> SIB Swiss Institute of Bioinformatics
> Weinbergstr. 11 (WEC D 19), 8092 Zürich, Switzerland, +41 44 632 0608
> Mattenstr. 26 (BSB 1.01), 4058 Basel, Switzerland, +41 61 387 3130
> 



-- 
http://fam-tille.de

Bug#899447: marked as done (aspell-ku: Invalid maintainer address debian-arabic-packa...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 06:19:08 +
with message-id 
and subject line Bug#899447: fixed in aspell-ku 0.20-0-7
has caused the Debian Bug report #899447,
regarding aspell-ku: Invalid maintainer address 
debian-arabic-packa...@lists.alioth.debian.org
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.)


-- 
899447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:aspell-ku
Version: 0.20-0-6
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of aspell-ku,

as you've probably heard, Debian's alioth services are shutting down.
This affects your package aspell-ku since the list address
debian-arabic-packa...@lists.alioth.debian.org used in the Maintainer:
field was not transferred to the alioth-lists service that provides a
continuation for the lists in the @lists.alioth.debian.org domain.

Addresses that were not migrated have been disabled some time  ago. As
a result your package is now in violation of a "must" in the Debian
policy (3.3, working email address), making it unfit for release.

Please fix this before long. Among other reasons, keep in mind bug
reports and important notifications about your package might not reach
you.

Your options:

* Upload another version with a new maintainer address of your choice,

* Migrate the list to the new system. This is still possible,
  please appoint a Debian developer as a list owner first, then
  contact the alioth lists migration team 
  and provide all the necessary information.

  More information about the new service can be found here:
  

* More options, even if imperfect, can be found at
  


The first option is probably suitable only if the address was used just
in a small number of packages since this requires an upload for each of
them. To our knowledge, the usage count of
debian-arabic-packa...@lists.alioth.debian.org is 6.

The second option is available for a limited time only, by end of
May 2018 the most. So if you're interested in going this way, start the
process as soon as possible.

Note, as mails to the maintainer address will not get through, this
bugreport is Cc'ed (X-Debbugs-CC:) to all uploaders of the package.

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: aspell-ku
Source-Version: 0.20-0-7

We believe that the bug you reported is fixed in the latest version of
aspell-ku, 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 899...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Lior Kaplan  (supplier of updated aspell-ku 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: Sat, 04 Aug 2018 08:00:24 +0300
Source: aspell-ku
Binary: aspell-ku
Architecture: source
Version: 0.20-0-7
Distribution: unstable
Urgency: medium
Maintainer: Lior Kaplan 
Changed-By: Lior Kaplan 
Description:
 aspell-ku  - Kurdish dictionary for aspell
Closes: 899447
Changes:
 aspell-ku (0.20-0-7) unstable; urgency=medium
 .
   * Update maintainer address (Closes: #899447)
Checksums-Sha1:
 4cc99759fd13cffa3f4beb6d4b76e20e19d1ee1c 1906 aspell-ku_0.20-0-7.dsc
 94590e7d49c2f02f717fe4fcc50f956ed7a16fae 2660 aspell-ku_0.20-0-7.debian.tar.xz
 d152c619ff650237e59fec51cb1526c4409e1aa4 5587 
aspell-ku_0.20-0-7_amd64.buildinfo
Checksums-Sha256:
 9d9bc1080625db29a390d295017db75b282657c341bae678cd4b6a9249b26bb4 1906 
aspell-ku_0.20-0-7.dsc
 ed5a0731e5f3c9ee07d32e066647461cb39410504867f467dafba99a75c180f7 2660 
aspell-ku_0.20-0-7.debian.tar.xz
 5be6d5d4758b9d09905831e94a64bb9e0f22dbd6b28ba09722f0928d8a71ff4d 5587 
aspell-ku_0.20-0-7_amd64.buildinfo
Files:
 505d15bf4f13f042f5461740f872fbe8 1906 text optional aspell-ku_0.20-0-7.dsc
 dd33c329fd52bc15f334cb407ef4d69b 2660 text optional 
aspell-ku_0.20-0-7.debian.tar.xz
 ff62437014e089314d02483daaf5e098 5587 text optional 
aspell-ku_0.20-0-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

i

Bug#904769: marked as done (tmuxp: missing dependency on python3-pkg-resources)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 06:34:26 +
with message-id 
and subject line Bug#904769: fixed in tmuxp 1.4.0-2
has caused the Debian Bug report #904769,
regarding tmuxp: missing dependency on python3-pkg-resources
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.)


-- 
904769: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904769
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tmuxp
Version: 1.4.0-1
Severity: serious

$ tmuxp
Traceback (most recent call last):
  File "/usr/bin/tmuxp", line 6, in 
from pkg_resources import load_entry_point
ModuleNotFoundError: No module named 'pkg_resources'


Andreas
--- End Message ---
--- Begin Message ---
Source: tmuxp
Source-Version: 1.4.0-2

We believe that the bug you reported is fixed in the latest version of
tmuxp, 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 904...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastien Delafond  (supplier of updated tmuxp 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: Sat, 04 Aug 2018 08:05:09 +0200
Source: tmuxp
Binary: tmuxp python-tmuxp python3-tmuxp
Architecture: source
Version: 1.4.0-2
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Delafond 
Changed-By: Sebastien Delafond 
Description:
 python-tmuxp - tmux session manager (Python 2)
 python3-tmuxp - tmux session manager (Python 3)
 tmuxp  - tmux session manager
Closes: 904769
Changes:
 tmuxp (1.4.0-2) unstable; urgency=medium
 .
   * Depend on python3-pkg-resources (Closes: #904769)
Checksums-Sha1:
 97fe7fabb3e0e753c1cc4a67132b875ee04bebee 1749 tmuxp_1.4.0-2.dsc
 db18c26285c2188e88a06295ea63261d36d28145 2860 tmuxp_1.4.0-2.debian.tar.xz
 44ed1d159d48effe1c97edd69b00e039c854c684 7257 tmuxp_1.4.0-2_amd64.buildinfo
Checksums-Sha256:
 3dbfc1dfcff25b17ab7e1c100fec1b62cb1207b0d59c35acf3ffd642a2fe9040 1749 
tmuxp_1.4.0-2.dsc
 e31bda4e7835c5b31d905f163d042b93d973451fc53b3f8961dbd4fdc0e0d09d 2860 
tmuxp_1.4.0-2.debian.tar.xz
 2d5037f36df2183d7230f92f4854f0dcd3ea9d5f8247ac6dc8bb571874e330b6 7257 
tmuxp_1.4.0-2_amd64.buildinfo
Files:
 0df20d62f7b1f9d8984a78784cb1dfe3 1749 utils optional tmuxp_1.4.0-2.dsc
 7db7e155cf3c11cccd901a5b7f7a480a 2860 utils optional 
tmuxp_1.4.0-2.debian.tar.xz
 4885ceb61fa00aefb25547819fc74539 7257 utils optional 
tmuxp_1.4.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEAqSkbVtrXP4xJMh3EL6Jg/PVnWQFAltlQrIACgkQEL6Jg/PV
nWSGvgf9GcJ7DoPGLutCuhPz+H0b7j/H8lf7XrrP2Acjcbj1aCwvxuXGaxAOpBVC
UfdyNuHOY1YjEnQbKqN+XRcceDVcKvVpzmoFxap+dQsR8jVLYdL9l5rjIjJMgq4A
LuZW/bwaiw60nF/G8IoOZMvjFZZItpoIr3d/wqiuJCKRgH2um6C+Ws+pJqEcLf33
a7iXEPSjDHXIALA5ETmCRF29UMIC1p/+KbIgPQvhJ1JOz9O+9SJfbu53Q45jMH61
xp+aBIrTbWIALjBr40M8M9dVGFpf8xGsJE+gNdqjaqKAR/xTtwKeAh77PrbEncAy
lqA53AR4gv9YY4Eisz5I8MOpkyz2Bw==
=1Gj+
-END PGP SIGNATURE End Message ---

Bug#905343: marked as done (mlbstreamer: missing Depends: python3-distutils)

[Debian Bug Tracking System]

Your message dated Sat, 04 Aug 2018 06:33:54 +
with message-id 
and subject line Bug#905343: fixed in mlbstreamer 0.0.10-3
has caused the Debian Bug report #905343,
regarding mlbstreamer: missing Depends: python3-distutils
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.)


-- 
905343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mlbstreamer
Version: 0.0.10-2
Severity: serious

$ mlbplay
Traceback (most recent call last):
  File "/usr/bin/mlbplay", line 11, in 
load_entry_point('mlbstreamer==0.0.10', 'console_scripts', 'mlbplay')()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 476, in 
load_entry_point
return get_distribution(dist).load_entry_point(group, name)
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2700, 
in load_entry_point
return ep.load()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2318, 
in load
return self.resolve()
  File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 2324, 
in resolve
module = __import__(self.module_name, fromlist=['__name__'], level=0)
  File "/usr/lib/python3/dist-packages/mlbstreamer/play.py", line 16, in 

from . import config
  File "/usr/lib/python3/dist-packages/mlbstreamer/config.py", line 13, in 

import distutils.spawn
ModuleNotFoundError: No module named 'distutils.spawn'


Andreas
--- End Message ---
--- Begin Message ---
Source: mlbstreamer
Source-Version: 0.0.10-3

We believe that the bug you reported is fixed in the latest version of
mlbstreamer, 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 905...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Sebastien Delafond  (supplier of updated mlbstreamer 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: Sat, 04 Aug 2018 08:00:57 +0200
Source: mlbstreamer
Binary: mlbstreamer
Architecture: source
Version: 0.0.10-3
Distribution: unstable
Urgency: medium
Maintainer: Sebastien Delafond 
Changed-By: Sebastien Delafond 
Description:
 mlbstreamer - Interface to the MLB.TV media offering
Closes: 905343
Changes:
 mlbstreamer (0.0.10-3) unstable; urgency=medium
 .
   * Depend on python3-distutils (Closes: #905343)
Checksums-Sha1:
 278c61761385f4846fef868faa629e418603d409 1574 mlbstreamer_0.0.10-3.dsc
 c3d4927ba550adade17101b7f497c32a4ca151df 1544 
mlbstreamer_0.0.10-3.debian.tar.xz
 df3bef4156ccacd6025ebb4685ee37796a184dc3 6305 
mlbstreamer_0.0.10-3_amd64.buildinfo
Checksums-Sha256:
 7e548a51b65a2de8bbe3e0fb85cc1eb6ed5bbaf11d002c7970b643ce5153e52b 1574 
mlbstreamer_0.0.10-3.dsc
 2074969dc7b455e40bedb8a639da4d76a5e84a42545764a2d0460388ae64fdf5 1544 
mlbstreamer_0.0.10-3.debian.tar.xz
 f9302ba2d6e3daef60d7795d306e8814f570b41f00935c0ee9abcf4c9ef6b13c 6305 
mlbstreamer_0.0.10-3_amd64.buildinfo
Files:
 750bcd2ad1240b2c9f8250706a55512b 1574 video optional mlbstreamer_0.0.10-3.dsc
 011b5eaf2daada9465ef26098e43c18e 1544 video optional 
mlbstreamer_0.0.10-3.debian.tar.xz
 99f0037b6723dedd082cd7bb003e6490 6305 video optional 
mlbstreamer_0.0.10-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEAqSkbVtrXP4xJMh3EL6Jg/PVnWQFAltlQjwACgkQEL6Jg/PV
nWQKiAgAsyyCMXWt4XLitu6iKK1awfZAMaYDaSY0rGrAg6rBPxD3pYcMuai18wT5
RzLBJUawrM2bBbSrIatn2oAjfSzFewno5b6WN5EYz4l/WUIQIZR4rdMGpHAjV7w0
XOGLYuFiORqIJ/6UYXxGAetco0VyK3XPrMkKvQTOGj0ClDLvH3EtM0vOyMXj0bf2
+qizLetoG7NIXbEvC+TaOJcpvj7W0TcNkjj4KzcMam3lFGVaqNrfRWLd0vQ/U6Jc
yVx5/soNva5eUdcaknLy/YxbqC3DuOoExIEYnrwik7HsbzuRPrkS6MTSztyNJvRu
o8UXgV6Vu1m+6oRo6y/eMbQWdXTnNg==
=ohO6
-END PGP SIGNATURE End Message ---

Bug#905408: libreoffice: missed radiobuttons and checkbox in forms

[Kamil Jonca]

Source: libreoffice
Version: 3a6.1.0~rc2-3
Severity: grave
Justification: renders package unusable

I found that in my database forms, at version 6.1 libreoffice, all checkboxes 
and radiobuttons are missing. 
Only their labels exist, but no field to enter/check value. 
Simplest way to observe it is to run: 
soffice -base
and try to choose 'open existing database file'
In 6.0x everything is ok.


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

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

Bug#903325: delayed/10

[Sébastien Delafond]

Hi,

I have just uploaded blinker 1.4+dfsg1-0.2, fixing this FTBFS, to
DELAYED/10. Don't hesitate to cancel or reschedule it if you need to.

Cheers,

--Seb

Bug#905325: knot-resolver: CVE-2018-10920: Improper input validation bug in DNS resolver component

[Salvatore Bonaccorso]

Source: knot-resolver
Version: 2.3.0-4
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for knot-resolver.

CVE-2018-10920[0]:
| Improper input validation bug in DNS resolver component of Knot
| Resolver before 2.4.1 allows remote attacker to poison cache.

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-2018-10920
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-10920
[1] https://www.knot-resolver.cz/2018-08-02-knot-resolver-2.4.1.html

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#902467: golang-github-kardianos-osext: FTBFS in buster/sid (failing tests)

[Shengjing Zhu]

Hi team,

Here is the patch to skip this test.

-- 
Shengjing Zhu
diff -Nru 
golang-github-kardianos-osext-0.0~git20170510.0.ae77be6/debian/changelog 
golang-github-kardianos-osext-0.0~git20170510.0.ae77be6/debian/changelog
--- golang-github-kardianos-osext-0.0~git20170510.0.ae77be6/debian/changelog
2018-04-30 23:23:20.0 +0800
+++ golang-github-kardianos-osext-0.0~git20170510.0.ae77be6/debian/changelog
2018-08-03 15:17:22.0 +0800
@@ -1,3 +1,10 @@
+golang-github-kardianos-osext (0.0~git20170510.0.ae77be6-6) unstable; 
urgency=medium
+
+  * Team upload.
+  * Skip TestExecutableDelete(false test).
+
+ -- Shengjing Zhu   Fri, 03 Aug 2018 15:17:22 +0800
+
 golang-github-kardianos-osext (0.0~git20170510.0.ae77be6-5) unstable; 
urgency=medium
 
   [ Alexandre Viau ]
diff -Nru 
golang-github-kardianos-osext-0.0~git20170510.0.ae77be6/debian/patches/0001-skip-testexecutabledelete.patch
 
golang-github-kardianos-osext-0.0~git20170510.0.ae77be6/debian/patches/0001-skip-testexecutabledelete.patch
--- 
golang-github-kardianos-osext-0.0~git20170510.0.ae77be6/debian/patches/0001-skip-testexecutabledelete.patch
 1970-01-01 08:00:00.0 +0800
+++ 
golang-github-kardianos-osext-0.0~git20170510.0.ae77be6/debian/patches/0001-skip-testexecutabledelete.patch
 2018-08-03 15:14:30.0 +0800
@@ -0,0 +1,26 @@
+Description: Skip TestExecutableDelete
+Author: Shengjing Zhu 
+
+Reading this test logic, it first reads its self executable path, then
+start it self, then remove original file. It of cause prints the
+"/tmp/go-buildnnn/b001/osext.test (deleted)".
+  ^
+In go >= 1.8, this package's Executable function just fallback
+to go system os package. I think there's no need to test it.
+
+Origin: other
+Bug: https://github.com/kardianos/osext/issues/21
+Bug-Debian: https://bugs.debian.org/902467
+Forwarded: no
+Last-Update: 2018-08-03
+
+--- golang-github-kardianos-osext-0.0~git20170510.0.ae77be6.orig/osext_test.go
 golang-github-kardianos-osext-0.0~git20170510.0.ae77be6/osext_test.go
+@@ -80,6 +80,7 @@ func TestExecutableMatch(t *testing.T) {
+ }
+ 
+ func TestExecutableDelete(t *testing.T) {
++  t.Skip()
+   if runtime.GOOS != "linux" {
+   t.Skip()
+   }
diff -Nru 
golang-github-kardianos-osext-0.0~git20170510.0.ae77be6/debian/patches/series 
golang-github-kardianos-osext-0.0~git20170510.0.ae77be6/debian/patches/series
--- 
golang-github-kardianos-osext-0.0~git20170510.0.ae77be6/debian/patches/series   
1970-01-01 08:00:00.0 +0800
+++ 
golang-github-kardianos-osext-0.0~git20170510.0.ae77be6/debian/patches/series   
2018-08-03 15:15:49.0 +0800
@@ -0,0 +1 @@
+0001-skip-testexecutabledelete.patch


signature.asc
Description: PGP signature

Bug#905326: glslang: Incomplete debian/copyright?

[Chris Lamb]

Source: glslang
Version: 6.2.2596-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Timo Aaltonen , 
ftpmas...@debian.org

Hi,

I just ACCEPTed glslang from NEW but noticed it was missing 
attribution in debian/copyright for at least ARM.

This is in no way exhaustive so please check over the entire package 
carefully and address these on your next upload.


Regards,

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

Bug#904630: marked as done (python-kubernetes needs an update for Python 3.7)

[Debian Bug Tracking System]

Your message dated Fri, 3 Aug 2018 10:25:35 +0200
with message-id <20180803082535.ga28...@msg.df7cb.de>
and subject line Re: Bug#904630: python-kubernetes needs an update for Python 
3.7
has caused the Debian Bug report #904630,
regarding python-kubernetes needs an update for Python 3.7
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.)


-- 
904630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904630
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:python-kubernetes
Version: 7.0.0~a1-1
Severity: serious
Tags: sid buster

According to the Debian changelog, this needs an update ...

Setting up python3-kubernetes (4.0.0-2) ...
  File "/usr/lib/python3/dist-packages/kubernetes/client/api_client.py", line 
281
response_type=None, auth_settings=None, async=None,
^
SyntaxError: invalid syntax

  File
"/usr/lib/python3/dist-packages/kubernetes/client/apis/admissionregistration_api.py",
line 120
async=params.get('async'),
^
SyntaxError: invalid syntax

  File
"/usr/lib/python3/dist-packages/kubernetes/client/apis/admissionregistration_v1alpha1_api.py",
line 132
async=params.get('async'),
^
SyntaxError: invalid syntax
--- End Message ---
--- Begin Message ---
Version: 7.0.0~a1-1

Re: Matthias Klose 2018-07-26 
> According to the Debian changelog, this needs an update ...
> 
> Setting up python3-kubernetes (4.0.0-2) ...

Right, but you installed the old version.

Christoph--- End Message ---

Bug#903352: NMU upload to DELAYED=3

[Andreas Tille]

Hi,

I've uploaded to DELAYED=3 and commited my changes to Git.

What do you think about maintaining this package in Python
team?

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#905303: `/usr/share/bash-completion/completions/su` is owned by both util-linux and bash-completion

[Andreas Henriksson]

Control: severity -1 serious
Control: tags -1 + pending

Hello Víctor Cuadrado Juan,

Thanks for your bug report. (Reply inline below.)

On Thu, Aug 02, 2018 at 08:59:33PM +0200, Víctor Cuadrado Juan wrote:
> Package: util-linux
> Version: 2.32-0.3
> Severity: critical
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
> 
> Hello util-linux maintainer,
> 
> Looping in the bash-completion maintainer too.
> 
> On a Stretch system with:
   ^^^ (important detail highlighted)

>   util-linux_2.32-0.3
>   bash-completion_1:2.1-4.3
> 
> I get an error performing a full-upgrade to Testing, as both packages
> own `/usr/share/bash-completion/completions/su`:
> 
> ```
> Preparing to unpack .../util-linux_2.32-0.3_amd64.deb ...
> Unpacking util-linux (2.32-0.3) over (2.29.2-1+deb9u1) ...
> Replacing files in old package login (1:4.4-4.1) ...
> dpkg: error processing archive 
> /var/cache/apt/archives/util-linux_2.32-0.3_amd64.deb (--unpack):
>  trying to overwrite '/usr/share/bash-completion/completions/su', which 
> is also in package bash-completion 1:2.1-4.3  
>   
> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
> dpkg: considering deconfiguration of util-linux, which would be broken by 
> installation of login ...
> dpkg: no, util-linux is essential, will not deconfigure
>  it in order to enable installation of login
> dpkg: error processing archive 
> /var/cache/apt/archives/login_1%3a4.5-1.1_amd64.deb (--unpack):
>  installing login would break existing software
> Errors were encountered while processing:
>  /var/cache/apt/archives/util-linux_2.32-0.3_amd64.deb
>  /var/cache/apt/archives/login_1%3a4.5-1.1_amd64.deb
> ```
> 
> 
> 
> After a brief look at both source packages, I can see that meanwhile
> the last util-linux doesn't ship that file, bash-completion does.

Yes, except switch places of util-linux and bash-completion in your
sentence. ;)

I'll bump the version used in the Breaks/Replaces relationship in the
next upload. It's ofcourse easy enough to work around this issue, since
it only effects partial upgrades, by making sure you upgrade both
util-linux and bash-completion to both use the versions from
unstable/testing.

> Also, util-linux declares a Break and Conflicts with specific versions
> of bash-completion, so I have assumed that the bug report goes indeed
> against util-linux.
> 
> Please don't hesitate to reassign or reduce severity if needed.

Technically, 'serious' is the correct severity as this is a debian
policy violation. (Critical would be if the update would lead to
for example your harddrive dying because of the update which could
lead to data loss.)
Also for correctness, you should include a 'Justification:' field
in your bug report citing which section of debian policy you're
arguing isn't followed.
In practice is doesn't really matter though. Any severity >= serious
is considered "RC" (release critical), which has some implications
on testing migration.

Regards,
Andreas Henriksson

Processed: Re: `/usr/share/bash-completion/completions/su` is owned by both util-linux and bash-completion

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #905303 [util-linux] `/usr/share/bash-completion/completions/su` is owned 
by both util-linux and bash-completion
Severity set to 'serious' from 'critical'
> tags -1 + pending
Bug #905303 [util-linux] `/usr/share/bash-completion/completions/su` is owned 
by both util-linux and bash-completion
Added tag(s) pending.

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