Bug#772479: irssi-plugin-xmpp does not work at all on buster

[Adrian Bunk]

Control: block -1 by 811445

On Fri, Sep 14, 2018 at 04:19:31PM -0400, Antoine Beaupré wrote:
> On 2018-09-14 14:41:03, Daniel Kahn Gillmor wrote:
> > Control: severity 772479 grave
> >
> > I've got these packages installed:
> >
> > ii  irssi 1.1.1-1  amd64terminal based IRC client
> > ii  irssi-plugin-xmpp 0.54-2   amd64XMPP plugin for irssi
> >
> > and if i launch a new irssi installation and do:
> >
> > /load xmpp
> >
> > then it responds with:
> >
> > 13:10 -!- Irssi: xmpp/core is ABI version 7 but Irssi is version 13, cannot 
> > load
> > 13:10 -!- Irssi: Error loading module xmpp/fe: 
> >   /usr/lib/x86_64-linux-gnu/irssi/modules/libfe_xmpp.so: undefined 
> >   symbol: xmpp_subscription
> >
> > so irssi-plugin-xmpp does not work at all, rendering this bug report
> > severity grave. :(
> 
> I think this needs a binNMU.
> 
> Alternatively, we could just rebuild to ship what's pending in git and
> do some administrativa. Upstream has no new release but two minor
> bugfixes/commits.

It also needs a proper narrowly versioned dependency.

Running irssi-plugin-otr or irssi-plugin-xmpp from stretch with irssi 
from stretch-backports is likely similarly broken.

The proper solution requires #811445 fixed, otherwise every plugin
has to implement its own dependency generation.

> a.

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

Processed: Re: Bug#772479: irssi-plugin-xmpp does not work at all on buster

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 811445
Bug #772479 [irssi-plugin-xmpp] irssi-plugin-xmpp needs rebuild on new uploads 
of irssi
772479 was not blocked by any bugs.
772479 was not blocking any bugs.
Added blocking bug(s) of 772479: 811445

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

Bug#908833: colmap: FTBFS (dh_auto_configure fails)

[Juhani Numminen]

On Fri, 14 Sep 2018 18:03:11 + Santiago Vila  wrote:

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

At reproducible-builds.org, the first error message is this:


-- Found installed version of Eigen: /usr/lib/cmake/eigen3
CMake Error at /usr/lib/cmake/Ceres/CeresConfig.cmake:88 (message):
  Failed to find Ceres - Found Eigen dependency, but the version of Eigen
  found (3.3.5) does not exactly match the version of Eigen Ceres was
  compiled with (3.3.4).  This can cause subtle bugs by triggering violations
  of the One Definition Rule.  See the Wikipedia article
  http://en.wikipedia.org/wiki/One_Definition_Rule for more details
Call Stack (most recent call first):
  /usr/lib/cmake/Ceres/CeresConfig.cmake:223 (ceres_report_not_found)
  CMakeLists.txt:73 (find_package)


CMake Error at CMakeLists.txt:73 (find_package):
  Found package configuration file:

/usr/lib/cmake/Ceres/CeresConfig.cmake

  but it set Ceres_FOUND to FALSE so package "Ceres" is considered to be NOT
  FOUND.


-- Configuring incomplete, errors occurred!


This seems to be caused by build dependency libceres-dev.
Related bugs: #883619, #868355.


Regards,
Juhani

Bug#906730: calendar-exchange-provider: Add-on is not compatible with Thunderbird 60.0

[Mechtilde Stehmann]

Hello,

Up to now there is no new version of exchangecalendar available, where this
issue is fixed.

In the meantime another project arise: TbSync. ITP #902333, #906853

This is packaged and uploaded to New Queue.

The development of exchangecalendar will be observed.

-- 
Mechtilde Stehmann
## Debian Developer
## Loook, calender-exchange-provider, libreoffice-canzeley-client
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F



signature.asc
Description: OpenPGP digital signature

Bug#907493: ghostscript breaks cups autopkgtest: test times out

[Paul Gevers]

Hi Jonas,

On 14-09-18 22:26, Jonas Smedegaard wrote:
> Another release of Ghostscript is now in experimental.  Can someone 
> please test if those autopkgtests still fail?

9.25~dfsg-1~exp1 passed the cups test.

https://ci.debian.net/data/autopkgtest/testing/amd64/c/cups/994233/log.gz

Paul



signature.asc
Description: OpenPGP digital signature

Bug#905548: marked as done (python-pysam: FTBFS - tests fail: AttributeError: 'module' object has no attribute 'HAVE_LIBCURL')

[Debian Bug Tracking System]

Your message dated Sat, 15 Sep 2018 07:35:09 +0200
with message-id <20180915053509.jj6mk7wjcpzaw...@an3as.eu>
and subject line Closing with new version
has caused the Debian Bug report #905548,
regarding python-pysam: FTBFS - tests fail: AttributeError: 'module' object has 
no attribute 'HAVE_LIBCURL'
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.)


-- 
905548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pysam
Version: 0.15.0.1+ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi,

python-pysam FTBFS on all architectures with testsuite errors. I can
also reproduce this on amd64 in a clean pbuilder environment.

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

=== FAILURES ===
 TestEmptyHeader.test_bam_without_seq_in_header 

self = 

def test_bam_without_seq_in_header(self):
>   s = pysam.AlignmentFile(os.path.join(BAM_DATADIR, 
> "example_no_seq_in_header.bam"))

tests/AlignmentFile_test.py:1406: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
pysam/libcalignmentfile.pyx:734: in 
pysam.libcalignmentfile.AlignmentFile.__cinit__
???
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

>   ???
E   IOError: [Errno 2] could not open alignment file 
`/<>/python-pysam-0.15.0.1+ds/.pybuild/cpython2_2.7_pysam/build/tests/pysam_data/example_no_seq_in_header.bam`:
 No such file or directory

pysam/libcalignmentfile.pyx:933: IOError
___ TestRemoteFileHTTP.testFetchAll 

self = 

def setUp(self):
>   if not pysam.config.HAVE_LIBCURL or not check_url(self.url):
E   AttributeError: 'module' object has no attribute 'HAVE_LIBCURL'

tests/tabix_test.py:1049: AttributeError
 TestRemoteFileHTTP.testHeader _

self = 

def setUp(self):
>   if not pysam.config.HAVE_LIBCURL or not check_url(self.url):
E   AttributeError: 'module' object has no attribute 'HAVE_LIBCURL'

tests/tabix_test.py:1049: AttributeError
__ TestRemoteFileHTTPWithHeader.testFetchAll ___

self = 

def setUp(self):
>   if not pysam.config.HAVE_LIBCURL or not check_url(self.url):
E   AttributeError: 'module' object has no attribute 'HAVE_LIBCURL'

tests/tabix_test.py:1088: AttributeError
___ TestRemoteFileHTTPWithHeader.testHeader 

self = 

def setUp(self):
>   if not pysam.config.HAVE_LIBCURL or not check_url(self.url):
E   AttributeError: 'module' object has no attribute 'HAVE_LIBCURL'

tests/tabix_test.py:1088: AttributeError
=== warnings summary ===
.pybuild/cpython2_2.7_pysam/build/tests/AlignmentFile_test.py::TestTruncatedBAM::testTruncatedBam2
  
/<>/python-pysam-0.15.0.1+ds/.pybuild/cpython2_2.7_pysam/build/tests/AlignmentFile_test.py:1441:
 UserWarning: no BGZF EOF marker; file may be truncated
ignore_truncation=True)

.pybuild/cpython2_2.7_pysam/build/tests/samtools_test.py::SamtoolsTest::testStatements
  
/<>/python-pysam-0.15.0.1+ds/.pybuild/cpython2_2.7_pysam/build/tests/samtools_test.py:140:
 UserWarning: versions of pysam.samtools and samtools differ: 1.9 != 1.7
samtools_version))

-- Docs: http://doc.pytest.org/en/latest/warnings.html
 5 failed, 903 passed, 17 skipped, 2 warnings in 94.95 seconds =
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/<>/python-pysam-0.15.0.1+ds/.pybuild/cpython2_2.7_pysam/build; 
python2.7 -m pytest tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 2.7 returned 
exit code 13
make[1]: *** [debian/rules:31: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>/python-pysam-0.15.0.1+ds'
make: *** [debian/rules:24: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


Network access (beyond localhost) is not available during build.


Andreas
--- End Message ---
--- Begin Message ---
Hi,

I had fixed this issue in the upload of 0.15.0.1+ds-2 to unstable
without noticing the bug.  Thus closing.

Kind regards

  Andreas.

-- 
http://fam-tille.de--- End Message ---

Bug#908463: [Pkg-privacy-maintainers] Bug#908463: torbrowser-launcher: Fails to start "Web Content" processes due to outdated AppArmor policy

[intrigeri]

Roger Shimizu:
> On Mon, Sep 10, 2018 at 11:58 PM, gregor herrmann  wrote:
>> On Mon, 10 Sep 2018 10:43:32 -0400, Antoine Beaupré wrote:
>> After upgrading to 0.2.9-4, adequate complains:
>>
>> torbrowser-launcher: obsolete-conffile 
>> /etc/apparmor.d/local/torbrowser.Tor.tor
>> torbrowser-launcher: obsolete-conffile 
>> /etc/apparmor.d/local/torbrowser.Browser.plugin-container
>> torbrowser-launcher: obsolete-conffile 
>> /etc/apparmor.d/local/torbrowser.Browser.firefox

> Sorry, I don't have these errors when upgrading package.

To reproduce, I think you need 1. adequate installed;
2. upgrading from a specific version of the package.

Cheers,
-- 
intrigeri

Bug#897696: marked as done (abinit: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Sat, 15 Sep 2018 07:44:28 +0300
with message-id 

and subject line Bug fixed in the latest version
has caused the Debian Bug report #897696,
regarding abinit: 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.)


-- 
897696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:abinit
Version: 8.0.8-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/abinit_8.0.8-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

[...]
Making all in 65_paw
make[5]: Entering directory '/<>/src/65_paw'
gfortran -DHAVE_CONFIG_H -I. -I../..  -I../../src/61_ionetcdf 
-I../../src/61_ionetcdf -I../../src/32_util -I../../src/32_util 
-I../../src/61_occeig -I../../src/61_occeig -I../../src/28_numeric_noabirule 
-I../../src/28_numeric_noabirule -I../../src/44_abitypes_defs 
-I../../src/44_abitypes_defs -I../../src/42_libpaw -I../../src/42_libpaw 
-I../../src/51_manage_mpi -I../../src/51_manage_mpi -I../../src/62_ctqmc 
-I../../src/62_ctqmc -I../../src/16_hideleave -I../../src/16_hideleave 
-I../../src/56_io_mpi -I../../src/56_io_mpi -I../../src/43_wvl_wrappers 
-I../../src/43_wvl_wrappers -I../../src/56_recipspace -I../../src/56_recipspace 
-I../../src/45_geomoptim -I../../src/45_geomoptim 
-I../../src/52_fft_mpi_noabirule -I../../src/52_fft_mpi_noabirule 
-I../../src/56_xc -I../../src/56_xc -I../../src/27_toolbox_oop 
-I../../src/27_toolbox_oop -I../../src/64_psp -I../../src/64_psp 
-I../../src/41_geometry -I../../src/41_geometry -I../../src/01_linalg_ext 
-I../../src/01_linalg_ext -I../../src/53_ffts 
 -I../../src/53_ffts -I../../src/12_hide_mpi -I../../src/12_hide_mpi 
-I../../src/11_memory_mpi -I../../src/11_memory_mpi -I../../src/10_defs 
-I../../src/10_defs -I../../src/14_hidewrite -I../../src/14_hidewrite 
-I../../src/18_timing -I../../src/18_timing -I../../src/57_iovars 
-I../../src/57_iovars -I../../src/64_atompaw -I../../src/64_atompaw 
-I../../src/incs -I../../src/incs -I/<>/fallbacks/exports/include  
 -ffree-form -J/<>/src/mods  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -c -o 
m_paw_pwaves_lmn.o m_paw_pwaves_lmn.F90
gfortran -DHAVE_CONFIG_H -I. -I../..  -I../../src/61_ionetcdf 
-I../../src/61_ionetcdf -I../../src/32_util -I../../src/32_util 
-I../../src/61_occeig -I../../src/61_occeig -I../../src/28_numeric_noabirule 
-I../../src/28_numeric_noabirule -I../../src/44_abitypes_defs 
-I../../src/44_abitypes_defs -I../../src/42_libpaw -I../../src/42_libpaw 
-I../../src/51_manage_mpi -I../../src/51_manage_mpi -I../../src/62_ctqmc 
-I../../src/62_ctqmc -I../../src/16_hideleave -I../../src/16_hideleave 
-I../../src/56_io_mpi -I../../src/56_io_mpi -I../../src/43_wvl_wrappers 
-I../../src/43_wvl_wrappers -I../../src/56_recipspace -I../../src/56_recipspace 
-I../../src/45_geomoptim -I../../src/45_geomoptim 
-I../../src/52_fft_mpi_noabirule -I../../src/52_fft_mpi_noabirule 
-I../../src/56_xc -I../../src/56_xc -I../../src/27_toolbox_oop 
-I../../src/27_toolbox_oop -I../../src/64_psp -I../../src/64_psp 
-I../../src/41_geometry -I../../src/41_geometry -I../../src/01_linalg_ext 
-I../../src/01_linalg_ext -I../../src/53_ffts 
 -I../../src/53_ffts -I../../src/12_hide_mpi -I../../src/12_hide_mpi 
-I../../src/11_memory_mpi -I../../src/11_memory_mpi -I../../src/10_defs 
-I../../src/10_defs -I../../src/14_hidewrite -I../../src/14_hidewrite 
-I../../src/18_timing -I../../src/18_timing -I../../src/57_iovars 
-I../../src/57_iovars -I../../src/64_atompaw -I../../src/64_atompaw 
-I.

Bug#876581: marked as done (libiptcdata FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer available)

[Debian Bug Tracking System]

Your message dated Sat, 15 Sep 2018 03:19:24 +
with message-id 
and subject line Bug#876581: fixed in libiptcdata 1.0.5-1
has caused the Debian Bug report #876581,
regarding libiptcdata FTBFS with gtk-doc-tools 1.26: gtkdoc-mktmpl is no longer 
available
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.)


-- 
876581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libiptcdata
Version: 1.0.4-6
Severity: serious
Tags: buster sid

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

...
gtk-doc: Rebuilding template files
cd /build/1st/libiptcdata-1.0.4/./docs/reference && gtkdoc-mktmpl 
--module=libiptcdata 
/bin/bash: gtkdoc-mktmpl: command not found
Makefile:600: recipe for target 'tmpl-build.stamp' failed
make[4]: *** [tmpl-build.stamp] Error 127
--- End Message ---
--- Begin Message ---
Source: libiptcdata
Source-Version: 1.0.5-1

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

Debian distribution maintenance software
pp.
Ian Wienand  (supplier of updated libiptcdata package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 12 Sep 2018 22:03:08 +1000
Source: libiptcdata
Binary: libiptcdata0-dev libiptcdata0-dbg libiptcdata-doc libiptcdata-bin 
libiptcdata0 python-iptcdata
Architecture: source amd64 all
Version: 1.0.5-1
Distribution: unstable
Urgency: medium
Maintainer: Ian Wienand 
Changed-By: Ian Wienand 
Description:
 libiptcdata-bin - Library to parse IPTC metadata (programs)
 libiptcdata-doc - Library to parse IPTC metadata (documentation)
 libiptcdata0 - Library to parse IPTC metadata
 libiptcdata0-dbg - Library to parse IPTC metadata (debug files)
 libiptcdata0-dev - Library to parse IPTC metadata (development files)
 python-iptcdata - Python bindings for the iptcdata library
Closes: 876581
Changes:
 libiptcdata (1.0.5-1) unstable; urgency=medium
 .
   * New upstream release
   * Fixes gtk-doc build (Closes: #876581)
   * Update vcs and upstream details in control.in
   * Update to compat level 10
   * Remove unnecessary
   * debian/mk/docbook-manage.mk, debian/mk/po4a.mk,
 debian/xml-man/en/iptc.xml,
 debian/xml-man/en/refentryinfo.xml,
 debian/xml-man/p04a/p04a.cfg : remove to simplify things,
 just add the generated man page (hasn't changed in 10 years).
   * debian/iptc.1 : add copy of generated man page, install
   * debian/source/format: add 3.0 (quilt)
   * libiptcdata0-dbg: move to optional from extras
   * libiptcdata0-dev: install .pc file to multiarch location
   * Re-enable --enable-gtk-doc; should work with latest upstream
   * Remove now unnecessary autotools deps
Checksums-Sha1:
 7e299c79095d40b82019e3368eb4b8f61c034852 2336 libiptcdata_1.0.5-1.dsc
 409d0fafd56f128b81e144e5632637f1b614fdc1 586983 libiptcdata_1.0.5.orig.tar.gz
 ecc35595758ce5bd2827b1bcc147f8013793804c 6508 libiptcdata_1.0.5-1.debian.tar.xz
 55942364c61ec760f6522bf776fe5f7a0efaff86 23940 
libiptcdata-bin_1.0.5-1_amd64.deb
 05b5ccba574fd95c496cf641a06d0c6cec0dafc3 28112 libiptcdata-doc_1.0.5-1_all.deb
 935997d5a5063a80eb813616507bc261fdb1a9fe 99084 
libiptcdata0-dbg_1.0.5-1_amd64.deb
 dca2216a47b7579b72d73334edf03fbde572f736 18368 
libiptcdata0-dev_1.0.5-1_amd64.deb
 c238be2dc7a86b33fc6574a35f29f4dbdd68f8ad 29144 libiptcdata0_1.0.5-1_amd64.deb
 6eca0cd565bef9164815323a383234f4957fe7cf 10933 
libiptcdata_1.0.5-1_amd64.buildinfo
 3d9d03260ffcc26657f97bf22a3a134bf8cd588b 22936 
python-iptcdata_1.0.5-1_amd64.deb
Checksums-Sha256:
 70c9363d53cc53132eb041b9e93a23b64bd27316ce2ea9ff427d9171bac9d2f0 2336 
libiptcdata_1.0.5-1.dsc
 ea18481bc7f420a0dcb3a9540847e21ec12872c059dcd999e0ee024b4bf8f01e 586983 
libiptcdata_1.0.5.orig.tar.gz
 2090c28b6dc72e2355acf1dd5c5aea40f1eaed97e219d88f166edfd2b2e1e934 6508 
libiptcdata_1.0.5-1.debian.tar.xz
 d5a55ab01471994a958bb501578d5ba3bfc6de3bbc5e9aa6d331eda443a6ad39 23940 
libiptcdata-bin_1.0.5-1_amd64.deb
 a7917e20ed1fd3afda69ab3755f1d9de7a484a26b4254a2dbab9acc38767 28112 
libiptcdat

Bug#908461: marked as done (Fwd: YouTube API has changed. Please update to latest version.)

[Debian Bug Tracking System]

Your message dated Sat, 15 Sep 2018 02:42:04 +
with message-id 
and subject line Bug#908461: fixed in youtube-dl 2018.09.10-1
has caused the Debian Bug report #908461,
regarding Fwd: YouTube API has changed. Please update to latest version.
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.)


-- 
908461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Package: youtube-dl
Version: 2018.06.18
Severity: important

Dear maintainer,

youtube-dl is no longer able to download YouTube videos since the
YouTube API has changed. The fix has been released in the version
2018.09.08.

Fix: https://github.com/rg3/youtube-dl/pull/17464

Please make a new release to get this utility working again.

- -- 
Regards,
Joseph Nuthalapati

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE4rQIdbX3Xc6j+BCYU5jwCi+kPDUFAluWIwMACgkQU5jwCi+k
PDUg3RAAoTtkol9cGsQGJO2x7uQyV4obFFqsc9EsfpEvySj+v5H8W1gqDCkjM6YO
n9FN+ontu5iyIxiiHAwqb21wXVPYKiHakQ8tJ7xnBapvc5tKcpqzQzHURX15PAiz
zc1zsJwiLI4MQ2tBBvVTrf+BxhiXKKss0WbV47TG5EJfPuceG36U8w6hI3ijEK9P
VY6eI9GNl47it674KoLBdPoPPvKWxD1sw0db26WNxkSNTfOpdm2LMh8/EozdAHmo
N6JArZw1KAo9sAMPaazuNaHGF9F7wEniID/4xpVDtwSSQWvZKMQjUZ9mb22DVNIc
JhvvWVOKEuRfxlHYQrbtg6Aek+oSTrw+9Wrbvz/XHD/g4UiuGdkygAvM8jlPfqbH
Dc68kG3/9Efdc88MvglofpT3BQf4unh9EjKnkTzOmAlEfKpVQl8xbcE9eVhSBgn0
QUpw8YDaAfRrpo14maOZAC1Hvra5TaMIk8e+nWHMbAMzhpQfLdfFdbjrOf0l8J7y
Hea05Ta5brk0yWrJh9p2SrQktJdN13ME4v2+GYfBsFmKtHYX7EGZAuwAMpjKS5pm
tIquHzCQrPL2OqIh9gDV6a84IEknIpdAoF63kUsE/bDfby3S8YyuvtOaQ5w489lP
IrSi5YKsoISxii2f60T72HiVxLQeJIBxbjU4fTlOXzz1bOwvVSo=
=2aYv
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: youtube-dl
Source-Version: 2018.09.10-1

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

Debian distribution maintenance software
pp.
Rogério Brito  (supplier of updated youtube-dl 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: SHA384

Format: 1.8
Date: Fri, 14 Sep 2018 23:11:59 -0300
Source: youtube-dl
Binary: youtube-dl
Architecture: source all
Version: 2018.09.10-1
Distribution: unstable
Urgency: medium
Maintainer: Rogério Brito 
Changed-By: Rogério Brito 
Description:
 youtube-dl - downloader of videos from YouTube and other sites
Closes: 904619 907722 908461
Changes:
 youtube-dl (2018.09.10-1) unstable; urgency=medium
 .
   * ACK NMU by Clint Adams. Thanks!
   * New upstream version 2018.09.10. Closes: #908461, #907722, #904619.
   * debian/patch:
 + Refresh all patches to avoid FTBFS.
   * debian/control:
 + Set 'Rules-Requires-Root: no'.
 + Mark compliance with Debian policy 4.2.1. No further changes needed.
 + Update list of extractors in long description.
Checksums-Sha1:
 7f2b50c56407a1be55b7475ae8f95d5fc0196fe2 2268 youtube-dl_2018.09.10-1.dsc
 51f57296f6cbec056520ab03d92710a4a91ad0f0 3036301 
youtube-dl_2018.09.10.orig.tar.gz
 8514effb21bd67828b6546b6993c90118e3b3731 879 
youtube-dl_2018.09.10.orig.tar.gz.asc
 fa7f25653635f1e82e38484d188e58c63f98ac9d 29464 
youtube-dl_2018.09.10-1.debian.tar.xz
 75ad2b15093e2bd34f120107d9fae36968795ea2 1008960 
youtube-dl_2018.09.10-1_all.deb
 b616f9a2cf364238a20378628b9b88aa47854247 6546 
youtube-dl_2018.09.10-1_amd64.buildinfo
Checksums-Sha256:
 b638aade74046f6325c273c1c1871ceaba87da2036f6c2f4d7bfd96240ea51ef 2268 
youtube-dl_2018.09.10-1.dsc
 08eab35a5eaa249bf0a90de15369f4494e87e416f940f539f982e5562241ed89 3036301 
youtube-dl_2018.09.10.orig.tar.gz
 1276f2e5a1dc9fde818fb61d68a9ac14dfa7c3ff0f7ec8186aa1eac261c42f55 879 
youtube-dl_2018.09.10.orig.tar.gz.asc
 c11c1a25095daa1c1602a8f925a9c60e387a862107ed23b2818197818b2fd9eb 29464 
youtube-dl_2018.09.10-1.debian.tar.xz
 643b31b7fa9e2376c230ca6e0d94449d77a33917410e7aacbce627ed92bb9a5d 1008960 
youtube-dl_2018.09.10-1_all.deb
 fc9d4b2cd41e90e7fbf9ab4fa62709a7cc532fe434132a2f23374dd62c2ed0ed 6546 
youtube-dl_2018.09.10-1_amd64.buildinfo
Files:
 7dcb819b97c6d351db2518bfff71fbaa 2268 web optional youtube-dl_2018.09.10-1.dsc
 01b6cb97e12ac84a214c8

Bug#908463: [Pkg-privacy-maintainers] Bug#908463: torbrowser-launcher: Fails to start "Web Content" processes due to outdated AppArmor policy

[Roger Shimizu]

On Mon, Sep 10, 2018 at 11:58 PM, gregor herrmann  wrote:
> On Mon, 10 Sep 2018 10:43:32 -0400, Antoine Beaupré wrote:
>
>> Disabling the apparmor profiles fix this:
>>
>> aa-complain torbrowser.Tor.tor
>> aa-complain torbrowser.Browser.firefox
>
> After upgrading to 0.2.9-4, adequate complains:
>
> torbrowser-launcher: obsolete-conffile 
> /etc/apparmor.d/local/torbrowser.Tor.tor
> torbrowser-launcher: obsolete-conffile 
> /etc/apparmor.d/local/torbrowser.Browser.plugin-container
> torbrowser-launcher: obsolete-conffile 
> /etc/apparmor.d/local/torbrowser.Browser.firefox

Sorry, I don't have these errors when upgrading package.


# dpkg -i torbrowser-launcher_0.2.9-4_amd64.deb
(Reading database ... 272719 files and directories currently installed.)
Preparing to unpack torbrowser-launcher_0.2.9-4_amd64.deb ...
Unpacking torbrowser-launcher (0.2.9-4) over (0.2.9-3) ...
Setting up torbrowser-launcher (0.2.9-4) ...
Installing new version of config file
/etc/apparmor.d/torbrowser.Browser.firefox ...
Processing triggers for desktop-file-utils (0.23-1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for man-db (2.7.6.1-2) ...


> After getting rid of them, I have a starting torbrowser again.
>
> Looks like some dpkg-maintscript-helper(1) magic is needed here ...

Could you provide an example, or even patch?
Thanks!

BTW. I have pushed not-released-yet 0.2.9-5 to branch debian/sid on salsa.
Maybe you can simply build the package by git-buildpackage, and test
the latest appamor profile from intrigeri.

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#908733: redshift: Unable to run, unable to connect to geoclue, unable to get location from provider, free desktop access denied geolocation. disalbed for uid 1000

[Ritesh Raj Sarraf]

Please fix your geoclue2 setup. Custom configs for redshift work perfect
and so does properly set geoclue2 setup.



s3nt fr0m a $martph0ne, excuse typ0s

On Thu, Sep 13, 2018, 15:09 Ervin  wrote:

> Package: redshift
> Version: 1.11-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate
> ***
>
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
>* What outcome did you expect instead?
>
> *** End of the template - remove these template lines ***
>
>
>
> -- System Information:
> Debian Release: 9.5
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages redshift depends on:
> ii  libc6   2.24-11+deb9u3
> ii  libdrm2 2.4.74-1
> ii  libglib2.0-02.50.3-2
> ii  libx11-62:1.6.4-3
> ii  libxcb-randr0   1.12-1
> ii  libxcb-render0  1.12-1
> ii  libxcb1 1.12-1
> ii  libxxf86vm1 1:1.1.4-1+b2
>
> Versions of packages redshift recommends:
> ii  geoclue-2.0  2.4.5-1
>
> redshift suggests no packages.
>
> -- no debconf information
>

Bug#908733: marked as done (redshift: Unable to run, unable to connect to geoclue, unable to get location from provider, free desktop access denied geolocation. disalbed for uid 1000)

[Debian Bug Tracking System]

Your message dated Sat, 15 Sep 2018 06:28:20 +0530
with message-id 

and subject line Re: Bug#908733: redshift: Unable to run, unable to connect to 
geoclue, unable to get location from provider, free desktop access denied 
geolocation. disalbed for uid 1000
has caused the Debian Bug report #908733,
regarding redshift: Unable to run, unable to connect to geoclue, unable to get 
location from provider, free desktop access denied geolocation. disalbed for 
uid 1000
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.)


-- 
908733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: redshift
Version: 1.11-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

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

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

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



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

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

Versions of packages redshift depends on:
ii  libc6   2.24-11+deb9u3
ii  libdrm2 2.4.74-1
ii  libglib2.0-02.50.3-2
ii  libx11-62:1.6.4-3
ii  libxcb-randr0   1.12-1
ii  libxcb-render0  1.12-1
ii  libxcb1 1.12-1
ii  libxxf86vm1 1:1.1.4-1+b2

Versions of packages redshift recommends:
ii  geoclue-2.0  2.4.5-1

redshift suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Please fix your geoclue2 setup. Custom configs for redshift work perfect
and so does properly set geoclue2 setup.



s3nt fr0m a $martph0ne, excuse typ0s

On Thu, Sep 13, 2018, 15:09 Ervin  wrote:

> Package: redshift
> Version: 1.11-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate
> ***
>
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
>  ineffective)?
>* What was the outcome of this action?
>* What outcome did you expect instead?
>
> *** End of the template - remove these template lines ***
>
>
>
> -- System Information:
> Debian Release: 9.5
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
> LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages redshift depends on:
> ii  libc6   2.24-11+deb9u3
> ii  libdrm2 2.4.74-1
> ii  libglib2.0-02.50.3-2
> ii  libx11-62:1.6.4-3
> ii  libxcb-randr0   1.12-1
> ii  libxcb-render0  1.12-1
> ii  libxcb1 1.12-1
> ii  libxxf86vm1 1:1.1.4-1+b2
>
> Versions of packages redshift recommends:
> ii  geoclue-2.0  2.4.5-1
>
> redshift suggests no packages.
>
> -- no debconf information
>
--- End Message ---

Bug#906466: Upload pending

[Felix Lechner]

Control: severity 906466 normal

Hi,

A pending upload is expected to resolve this bug report. To prevent
auto removal, I am downgrading the severity to normal. Thank you!

Felix Lechner

Processed: Upload pending

[Debian Bug Tracking System]

Processing control commands:

> severity 906466 normal
Bug #906466 {Done: Felix Lechner } [src:gocryptfs] 
gocryptfs: FTBFS in buster/sid
Severity set to 'normal' from 'serious'

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

Bug#906466: marked as done (gocryptfs: FTBFS in buster/sid)

[Debian Bug Tracking System]

Your message dated Sat, 15 Sep 2018 00:19:10 +
with message-id 
and subject line Bug#906466: fixed in gocryptfs 1.4.3-7
has caused the Debian Bug report #906466,
regarding gocryptfs: FTBFS in buster/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.)


-- 
906466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906466
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gocryptfs
Version: 1.4.3-6
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
I: gocryptfs_1.4.3
dh build-arch --buildsystem=golang --with=golang
   dh_update_autotools_config -a -O--buildsystem=golang
   dh_autoreconf -a -O--buildsystem=golang
   dh_auto_configure -a -O--buildsystem=golang
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
I: gocryptfs_1.4.3
dh_auto_build -- -ldflags "-X main.GitVersion=1.4.3 -X 
main.GitVersionFuse=0.0~git20171124.0.14c3015 -X main.BuildDate=2018-07-12"
cd obj-x86_64-linux-gnu && go install 
-gcflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" 
-asmflags=\"-trimpath=/<>/obj-x86_64-linux-gnu/src\" -v -p 1 
-ldflags "-X main.GitVersion=1.4.3 -X 
main.GitVersionFuse=0.0~git20171124.0.14c3015 -X main.BuildDate=2018-07-12" 
github.com/rfjakob/gocryptfs github.com/rfjakob/gocryptfs/gocryptfs-xray 
github.com/rfjakob/gocryptfs/internal/configfile 
github.com/rfjakob/gocryptfs/internal/contentenc 
github.com/rfjakob/gocryptfs/internal/cryptocore 
github.com/rfjakob/gocryptfs/internal/ctlsock 
github.com/rfjakob/gocryptfs/internal/exitcodes 
github.com/rfjakob/gocryptfs/internal/fusefrontend 
github.com/rfjakob/gocryptfs/internal/fusefrontend_reverse 
github.com/rfjakob/gocryptfs/internal/nametransform 
github.com/rfjakob/gocryptfs/internal/nametransform/dirivcache 
github.com/rfjakob/gocryptfs/internal/openfiletable 
github.com/rfjakob/gocryptfs/internal/pathiv 
github.com/rfjakob/gocryptfs/internal/prefer_openssl github.com/rfjako
 b/gocryptfs/internal/readpassword 
github.com/rfjakob/gocryptfs/internal/serialize_reads 
github.com/rfjakob/gocryptfs/internal/siv_aead 
github.com/rfjakob/gocryptfs/internal/speed 
github.com/rfjakob/gocryptfs/internal/stupidgcm 
github.com/rfjakob/gocryptfs/internal/syscallcompat 
github.com/rfjakob/gocryptfs/internal/tlog
github.com/hanwen/go-fuse/splice
golang.org/x/sys/unix
github.com/hanwen/go-fuse/fuse

[... snipped ...]

PASS
ok  github.com/rfjakob/gocryptfs/internal/speed 0.002s [no tests to run]
=== RUN   TestEncryptDecrypt
--- PASS: TestEncryptDecrypt (0.05s)
=== RUN   TestInplaceSeal
--- PASS: TestInplaceSeal (0.02s)
=== RUN   TestInplaceOpen
--- PASS: TestInplaceOpen (0.02s)
=== RUN   TestCorruption
--- PASS: TestCorruption (0.00s)
PASS
ok  github.com/rfjakob/gocryptfs/internal/stupidgcm 0.099s
=== RUN   TestEmulateOpenat
--- PASS: TestEmulateOpenat (0.00s)
=== RUN   TestEmulateRenameat
--- PASS: TestEmulateRenameat (0.00s)
=== RUN   TestEmulateUnlinkat
--- PASS: TestEmulateUnlinkat (0.00s)
=== RUN   TestEmulateMknodat
--- PASS: TestEmulateMknodat (0.00s)
=== RUN   TestEmulateFchmodat
--- PASS: TestEmulateFchmodat (0.00s)
=== RUN   TestEmulateFchownat
--- SKIP: TestEmulateFchownat (0.00s)
emulate_test.go:204: TODO
=== RUN   TestEmulateSymlinkat
--- PASS: TestEmulateSymlinkat (0.00s)
=== RUN   TestEmulateMkdirat
--- PASS: TestEmulateMkdirat (0.00s)
=== RUN   TestEmulateFstatat
--- PASS: TestEmulateFstatat (0.00s)
=== RUN   TestGetdents
--- FAIL: TestGetdents (0.01s)
getdents_test.go:20: testing native getdents
getdents_test.go:86: random: g.Ino=6506, r.Ino=6507
=== RUN   TestOpenNofollow
--- PASS: TestOpenNofollow (0.00s)
=== RUN   TestReadlinkat
--- PASS: TestReadlinkat (0.00s)
FAIL
FAILgithub.com/rfjakob/gocryptfs/internal/syscallcompat 0.009s
?   github.com/rfjakob/gocryptfs/internal/tlog  [no test files]
dh_auto_test: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 1 
github.com/rfjakob/gocryptfs github.com/rfjakob/gocryptfs/gocryptfs-xray 
github.com/rfjakob/gocryptfs/internal/configfile 
github.com/rfjakob/gocryptfs/internal/contentenc 
github.com/rfjakob/gocryptfs/internal/cryptocore 
github.com/rfjakob/gocryptfs/internal/ctlsock 
github.com/rfjakob/gocryptfs/internal/exitcodes 
github.com/rfjakob/gocryptfs/internal/fusefrontend 
github.com/rfjakob/gocryptfs/internal/fusefrontend_reverse 
github.com/rfjakob/gocryptfs/internal/nametransform 
github.com/rfjakob/gocryptfs/internal/nametransform/

Bug#908810: marked as done (libpulse0: can't upgrade pulseaudio packages (version misalignment))

[Debian Bug Tracking System]

Your message dated Fri, 14 Sep 2018 23:35:21 +
with message-id 
and subject line Bug#906504: fixed in pulseaudio 12.2-2
has caused the Debian Bug report #906504,
regarding libpulse0: can't upgrade pulseaudio packages (version misalignment)
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.)


-- 
906504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpulse0
Severity: normal

Dear Maintainer,
pulseaudio packages can not be updated due to version misalignment.
Thanks.

--- details ---

root@OFFICE:~$ apt-get upgrade
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze
Lettura informazioni sullo stato... Fatto
Calcolo dell'aggiornamento... Fatto
I seguenti pacchetti sono stati mantenuti alla versione attuale:
  libpulse-dev libpulse-mainloop-glib0 libpulse0 libpulsedsp
pulseaudio pulseaudio-equalizer
  pulseaudio-module-bluetooth pulseaudio-module-jack
pulseaudio-module-lirc pulseaudio-utils
0 aggiornati, 0 installati, 0 da rimuovere e 10 non aggiornati.


root@OFFICE:~$ apt-get install libpulse-dev libpulse-mainloop-glib0
libpulse0 libpulsedsp pulseaudio pulseaudio-equalizer
pulseaudio-module-bluetooth
pulseaudio-module-jack pulseaudio-module-lirc pulseaudio-utils
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze
Lettura informazioni sullo stato... Fatto
I seguenti pacchetti sono stati installati automaticamente e non sono più
richiesti:
  libcapi20-3:i386 libexif12:i386 libgd3:i386 libgphoto2-6:i386
libgphoto2-port12:i386 libjbig0:i386   libjpeg62-turbo:i386
libltdl7:i386 libncurses6:i386 libtiff5:i386 libtinfo6:i386
libusb-1.0-0:i386
  libvkd3d1:i386 libvulkan1:i386 libwayland-client0:i386
libwayland-cursor0:i386 libwayland-egl1:i386   libwebp6:i386
libxcursor1:i386 libxinerama1:i386 libxkbcommon0:i386
libxpm4:i386 libxrandr2:i386 libxrender1:i386 libxss1:i386
Usare "apt autoremove" per rimuoverli.
Pacchetti suggeriti:
  paprefs avahi-daemon
Pacchetti raccomandati:
  rtkit
I seguenti pacchetti saranno RIMOSSI:
  libpulse0:i386 libsdl2-2.0-0:i386 libwine:i386 libwine-development:i386
pulseaudio-esound-compat
  wine32:i386 wine32-development:i386 wine32-development-preloader:i386
wine32-preloader:i386
I seguenti pacchetti saranno aggiornati:
  libpulse-dev libpulse-mainloop-glib0 libpulse0 libpulsedsp
pulseaudio pulseaudio-equalizer
  pulseaudio-module-bluetooth pulseaudio-module-jack
pulseaudio-module-lirc pulseaudio-utils
10 aggiornati, 0 installati, 9 da rimuovere e 0 non aggiornati.
È necessario scaricare 1.890 kB di archivi.
Dopo quest'operazione, verranno liberati 400 MB di spazio su disco.
Continuare? [S/n] n
Interrotto.


root@OFFICE:~$ apt-cache policy  libpulse0 libpulse0:i386
libpulse0:
  Installato: 12.0-1
  Candidato:  12.2-1
  Tabella versione:
 12.2-1 700
700 http://mirror.de.leaseweb.net/debian sid/main amd64 Packages
 *** 12.0-1 600
600 http://mirror.de.leaseweb.net/debian testing/main amd64 Packages
100 /var/lib/dpkg/status
 10.0-1+deb9u1 500
500 http://mirror.de.leaseweb.net/debian stable/main amd64 Packages
libpulse0:i386:
  Installato: 12.0-1
  Candidato:  12.0-1
  Tabella versione:
 *** 12.0-1 700
600 http://mirror.de.leaseweb.net/debian testing/main i386 Packages
700 http://mirror.de.leaseweb.net/debian sid/main i386 Packages
100 /var/lib/dpkg/status
 10.0-1+deb9u1 500
500 http://mirror.de.leaseweb.net/debian stable/main i386 Packages



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

Kernel: Linux 4.18.7-custom (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=it_IT, LC_CTYPE=it_IT (charmap=ISO-8859-1), LANGUAGE=it
(charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Source: pulseaudio
Source-Version: 12.2-2

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

Debian distribution maintenance software
pp.
Felipe Sateler  (supplier of updated pulseaudio 

Bug#906504: marked as done (pulseaudio: FTBFS in buster/sid (failing tests))

[Debian Bug Tracking System]

Your message dated Fri, 14 Sep 2018 23:35:21 +
with message-id 
and subject line Bug#906504: fixed in pulseaudio 12.2-2
has caused the Debian Bug report #906504,
regarding pulseaudio: FTBFS in buster/sid (failing tests)
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.)


-- 
906504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906504
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pulseaudio
Version: 11.1-5
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules binary-arch
dh binary-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
configure.ac:89: warning: AC_COMPILE_IFELSE was called before 
AC_USE_SYSTEM_EXTENSIONS
../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded from...
configure.ac:89: the top level
configure.ac:89: warning: AC_COMPILE_IFELSE was called before 
AC_USE_SYSTEM_EXTENSIONS
../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded from...
configure.ac:89: the top level
configure.ac:89: warning: AC_COMPILE_IFELSE was called before 
AC_USE_SYSTEM_EXTENSIONS
../../lib/autoconf/specific.m4:368: AC_USE_SYSTEM_EXTENSIONS is expanded from...
configure.ac:89: the top level
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.

[... snipped ...]

# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

FAIL: volume-test
=

Running suite(s): Volume
Attenuation of sample 1 against 32767: -90.3087 dB
Smallest possible attenuation > 0 applied to 32767: 0
max deviation: 1 n=283
0%: Checks: 1, Failures: 1, Errors: 0
tests/volume-test.c:148:F:volume:volume_test:0: Assertion 'mdn <= 253' failed
FAIL volume-test (exit status: 1)


Testsuite summary for pulseaudio 11.1

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

See src/test-suite.log
Please report to pulseaudio-discuss (at) lists (dot) freedesktop (dot) org

make[6]: *** [Makefile:10665: test-suite.log] Error 1
make[6]: Leaving directory '/<>/src'
make[5]: *** [Makefile:10773: check-TESTS] Error 2
make[5]: Leaving directory '/<>/src'
make[4]: *** [Makefile:11089: check-am] Error 2
make[4]: Leaving directory '/<>/src'
make[3]: *** [Makefile:11091: check] Error 2
make[3]: Leaving directory '/<>/src'
make[2]: *** [Makefile:808: check-recursive] Error 1
make[2]: Leaving directory '/<>'
make[1]: *** [Makefile:1099: check] Error 2
make[1]: Leaving directory '/<>'
dh_auto_test: make -j1 check VERBOSE=1 returned exit code 2
make: *** [debian/rules:35: binary-arch] Error 2
dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2


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

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

where you can get a full build log if you need it.

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: pulseaudio
Source-Version: 12.2-2

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

Debian distribution maintenance software
pp.
Felipe Sateler  (supplier of updated pulseaudio 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, 14 Sep 2018 20:16:14 -0300
Source: pulseaudio
Binary: pulseaudio pulseaudio-utils pulseaudio-module-zeroconf 
pulseaudio-module-jack pulseaudio-modu

Bug#906504: Bug #906504 in pulseaudio marked as pending

[Felipe Sateler]

Control: tag -1 pending

Hello,

Bug #906504 in pulseaudio 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/pulseaudio-team/pulseaudio/commit/0b8f91adb022d4baf6d6a7ae74e7edc48fdd214a


Allow rounding without having to allow a random number of errors in 
tests/volume-test.c (Closes: #906504)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/906504

Processed: Bug #906504 in pulseaudio marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #906504 [src:pulseaudio] pulseaudio: FTBFS in buster/sid (failing tests)
Bug #908810 [src:pulseaudio] libpulse0: can't upgrade pulseaudio packages 
(version misalignment)
Added tag(s) pending.
Added tag(s) pending.

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

Bug#907079: Not using SNI

[Sebastian Andrzej Siewior]

control: tags -1 patch
https://github.com/jcristau/imaplib2/commit/a7ce7da1d573849ac2e1d740d8f3238e0ad8d88c

Sebastian

Processed: Re: Not using SNI

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #907079 [python-imaplib2] Not using SNI
Added tag(s) patch.

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

Bug#888340: marked as done (gmerlin-encoders: FTBFS with FFmpeg 4.0)

[Debian Bug Tracking System]

Your message dated Fri, 14 Sep 2018 22:05:26 +
with message-id 
and subject line Bug#888340: fixed in gmerlin-encoders 1.2.0-10
has caused the Debian Bug report #888340,
regarding gmerlin-encoders: 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.)


-- 
888340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gmerlin-encoders
Version: 1.2.0-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-encoders_amd64.build

Thanks,
James
--- End Message ---
--- Begin Message ---
Source: gmerlin-encoders
Source-Version: 1.2.0-10

We believe that the bug you reported is fixed in the latest version of
gmerlin-encoders, 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.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
gmerlin-encoders 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, 14 Sep 2018 22:47:28 +0200
Source: gmerlin-encoders
Binary: gmerlin-encoders-ffmpeg gmerlin-encoders-good gmerlin-encoders-extra
Architecture: source
Version: 1.2.0-10
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Description:
 gmerlin-encoders-extra - MJPEG encoders for Gmerlin
 gmerlin-encoders-ffmpeg - ffmpeg encoders for Gmerlin
 gmerlin-encoders-good - patent-free encoders for Gmerlin
Closes: 888340
Changes:
 gmerlin-encoders (1.2.0-10) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field
   * d/control: Deprecating priority extra as per policy 4.0.1
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Felipe Sateler ]
   * Change maintainer address to debian-multime...@lists.debian.org
 .
   [ IOhannes m zmölnig ]
   * Remove d/control.in
   * Add patch to allow compilation with FFmpeg-4.0 (Closes: #888340)
   * State that the build process does not require "root"
   * Bump standards-version to 4.2.1
Checksums-Sha1:
 237b07ecde91b29e332b0bc4c20e2eae6256aba8 2526 gmerlin-encoders_1.2.0-10.dsc
 519846cf074d8642a289b46aee2ae5b697dec9a1 16204 
gmerlin-encoders_1.2.0-10.debian.tar.xz
 24e646d3566a5d525476dbf213ad84eab364d358 13891 
gmerlin-encoders_1.2.0-10_amd64.buildinfo
Checksums-Sha256:
 806a54b1052dc39342463ff011797ef93a2c4c86efe208d9559eafa3ec9b8808 2526 
gmerlin-encoders_1.2.0-10.dsc
 7e6f3ab0c77266cabd9dffd5f68f39d5473fe5a03e73ffb68f968d8903ff7187 16204 
gmerlin-encoders_1.2.0-10.debian.tar.xz
 16729acecee132606389075585aa329d2535e421ced826ef5f21cbac1e2bbc85 13891 
gmerlin-encoders_1.2.0-10_amd64.buildinfo
Files:
 4ac77ebf43d7b2cf6727a517914c40c2 2526 libs optional 
gmerlin-encoders_1.2.0-10.dsc
 25295d5d38df98eea0255ba4eb08cff7 16204 libs optional 
gmerlin-encoders_1.2.0-10.debian.tar.xz
 146be903128a70a3324b53150bfb910

Bug#907493: ghostscript breaks cups autopkgtest: test times out

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2018-08-31 01:25:24)
> Quoting Paul Gevers (2018-08-29 20:24:49)
> > Control: tags -1 moreinfo
> > 
> > Hi,
> > 
> > On 29-08-18 20:20, Jonas Smedegaard wrote:
> > > Thanks - that is indeed helpful, but provides only the _cups_ commands.
> > > 
> > > Inside those are some Ghostscript command (and some data) which I would 
> > > need to check if/what fails with Ghostscript.
> > 
> > Both of them are "ELF 64-bit LSB shared object" so it would help if the
> > cups maintainers could help here.
> 
> Do the freshly released experimental Ghostscript release help anything?

Another release of Ghostscript is now in experimental.  Can someone 
please test if those autopkgtests still fail?

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#895320: ps2pdf crashes

[Jonas Smedegaard]

A new release of ghostscript is now in experimental.

Could you please help test if that succeeds?

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Processed: forcibly merging 908396 908821

[Debian Bug Tracking System]

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

> forcemerge 908396 908821
Bug #908396 [firefox-esr] firefox-esr: stopped working after upgrade from 59 to 
60
Bug #908449 [firefox-esr] (no subject)
Bug #908821 [firefox-esr] firefox-esr: updated version and firefox crasehst at 
start
908821 was not blocked by any bugs.
908821 was not blocking any bugs.
Added blocking bug(s) of 908821: 908561
Marked as found in versions firefox-esr/60.2.0esr-1.
Bug #908449 [firefox-esr] (no subject)
Marked as found in versions firefox-esr/60.2.0esr-1~deb9u2; no longer marked as 
found in versions 60.2.0esr-1~deb9u2.
Marked as found in versions firefox-esr/60.2.0esr-1~deb9u2; no longer marked as 
found in versions 60.2.0esr-1~deb9u2.
Merged 908396 908449 908821
> thanks
Stopping processing here.

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

Bug#908567: marked as done (libssl 1.1.1 TLS_MAX_VERSION ABI breakage)

[Debian Bug Tracking System]

Your message dated Fri, 14 Sep 2018 23:40:34 +0200
with message-id <20180914214033.jwmdjc2itlh5p...@breakpoint.cc>
and subject line Re: Bug#908567: libssl 1.1.1 TLS_MAX_VERSION ABI breakage
has caused the Debian Bug report #908567,
regarding libssl 1.1.1 TLS_MAX_VERSION ABI breakage
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.)


-- 
908567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libssl1.1
Version: 1.1.1~~pre9-1
Severity: important

I'm on buster and with the latest updates from yesterday came 
qtbase-opensource-src 5.11.1+dfsg-7
and SSL started to fail in Qt5 programs. This was reported in bug 907774 ~ 2 
weeks ago.

Basically libssl 1.1.1 (in whatever 1.1.1 version - my guess is 1.1.1~~pre9-1 
from the changelog)
changed the definition of TLS_MAX_VERSION from TLS1_2_VERSION to 
TLS1_3_VERSION, which will start to
break all software in buster using that symbol, until libssl1.1 moves to buster.
--- End Message ---
--- Begin Message ---
On 2018-09-11 20:53:28 [+0200], To Adrian Bunk wrote:
> On 2018-09-11 16:11:02 [+0300], Adrian Bunk wrote:
> > Dmitry already implemented my short-term workaround:
> > https://tracker.debian.org/news/986618/accepted-qtbase-opensource-src-5111dfsg-8-source-into-unstable/
> > 
> > When this has been built on all release architectures openssl can bump 
> > the version requirement.
> > 
> > Even more cautious would be to wait until testing migration of Qt.
> 
> now after what happens I consider this issue (#908567) fixed since the
> only affected package by this is fixed. Also adding versioned depends is
> not easy as I expected it in the morning without too much mess around
> it.

closing then.

> > cu
> > Adrian
Sebastian--- End Message ---

Bug#907912: marked as done (llvm-toolchain-7: FTBFS linking libopenmp)

[Debian Bug Tracking System]

Your message dated Fri, 14 Sep 2018 23:33:35 +0200
with message-id <91cca305-45ef-0fed-c6b7-d7e875ea0...@physik.fu-berlin.de>
and subject line Re: Bug#907912 closed by Sylvestre Ledru 
 (Bug#907912: fixed in llvm-toolchain-7 1:7~+rc3-1)
has caused the Debian Bug report #907912,
regarding llvm-toolchain-7: FTBFS linking libopenmp
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.)


-- 
907912: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907912
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-7
Version: 1:7~svn331965-1
Severity: normal
User: debian-sp...@lists.debian.org
Usertags: sparc64

Hi!

llvm-toolchain-7 currently fails to build from source on the
following architectures because the embedded libomp doesn't
support them:

 - powerpc
 - powerpcspe
 - riscv64
 - sparc64

And possibly:

 - armel
 - mips
 - mipsel

Although the latter three might be fixable by linking against
libatomic but I haven't looked into the details yet. Either way,
disabling libomp for the former four architectures or, better,
enabling it for supported architectures only, should fix the
FTBFS on multiple architectures.

Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---
On 9/11/18 12:44 AM, John Paul Adrian Glaubitz wrote:
> This didn’t work for some reason:
> 
>> https://buildd.debian.org/status/package.php?p=llvm-toolchain-7&suite=sid
> 
> In my testbuilds, LLVM built fine on sparc64 with OpenMP disabled.

I lost track which of the many changes fixed this, but I think this
issue was because of the inverted ifeq logic for OPENMP_ENABLE.

Either way, closing as it has been fixed now.

Adrian

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

Processed: Bug #888340 in gmerlin-encoders marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #888340 [src:gmerlin-encoders] gmerlin-encoders: FTBFS with FFmpeg 4.0
Added tag(s) pending.

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

Bug#888340: Bug #888340 in gmerlin-encoders marked as pending

[IOhannes zmölnig]

Control: tag -1 pending

Hello,

Bug #888340 in gmerlin-encoders 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/multimedia-team/gmerlin-encoders/commit/d9cfd6cd7dff0cf123d3c03ccc47d4b4a4780806


Added patch to allow compilation with FFmpeg-4.0

Closes: #888340

TODO: test it...



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/888340

Bug#907460: marked as done (kdepim-runtime: /usr/bin/akonadi_imap_resource keeps crashing preventing kmail to work)

[Debian Bug Tracking System]

Your message dated Fri, 14 Sep 2018 22:18:22 +0200
with message-id <24813804.ZMVVbvx5Cr@merkaba>
and subject line Re: Bug#907460: kdepim-runtime: /usr/bin/akonadi_imap_resource 
keeps crashing preventing kmail to work
has caused the Debian Bug report #907460,
regarding kdepim-runtime: /usr/bin/akonadi_imap_resource keeps crashing 
preventing kmail to work
to be marked as done.

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

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


-- 
907460: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907460
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kdepim-runtime
Version: 4:18.07.90-1
Severity: grave
Justification: renders package unusable

I manged to install expetimental kdepim today but when starting
kmail I cannot acces to my ipmap account on exhange server (works
with TB on same machine).

I keep having crash traces in my out when started from konsole:

terminate called after throwing an instance of 'Akonadi::PayloadException'
  what():  Akonadi::PayloadException: Wrong payload type (requested: 
sp(0); present: sp(2))
ProtocolException thrown:Timeout while waiting for 
dataorg.kde.pim.akonadicontrol: ProcessControl: Application 
"/usr/bin/akonadi_imap_resource" stopped unexpectedly ( "Process crashed" )
org.kde.pim.akonadicontrol: Application '/usr/bin/akonadi_imap_resource' 
crashed! 1 restarts left.


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

Kernel: Linux 4.14.67 (SMP w/4 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF8), LANGUAGE=en_US:en (charmap=UTF-8) (ignored: LC_ALL set to 
en_US.UTF8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages kdepim-runtime depends on:
ii  akonadi-server   4:18.07.90-1
ii  kio  5.49.0-1
ii  kio-ldap 18.07.90-1
ii  kio-sieve4:18.07.90-1
ii  libc62.27-5
ii  libgcc1  1:8.2.0-4
ii  libkf5akonadiagentbase5  4:18.07.90-1
ii  libkf5akonadicalendar5abi1   4:18.07.90-1
ii  libkf5akonadicontact54:18.07.90-1
ii  libkf5akonadicore5abi2   4:18.07.90-1
ii  libkf5akonadimime5   4:18.07.90-1
ii  libkf5akonadinotes5  4:18.07.90-1
ii  libkf5akonadiwidgets5abi14:18.07.90-1
ii  libkf5alarmcalendar5abi1 4:18.07.90-1
ii  libkf5calendarcore5abi2  4:18.07.90-1
ii  libkf5codecs55.49.0-1
ii  libkf5completion55.49.0-1
ii  libkf5configcore55.49.0-1
ii  libkf5configgui5 5.49.0-1
ii  libkf5configwidgets5 5.49.0-1
ii  libkf5contacts5  4:18.07.90-1
ii  libkf5coreaddons55.49.0-1
ii  libkf5dbusaddons55.49.0-1
ii  libkf5i18n5  5.49.0-1
ii  libkf5identitymanagement518.07.90-1
ii  libkf5imap5  18.07.90-1
ii  libkf5itemmodels55.49.0-1
ii  libkf5jobwidgets55.49.0-1
ii  libkf5kdelibs4support5   5.49.0-1
ii  libkf5kiocore5   5.49.0-1
ii  libkf5kiowidgets55.49.0-1
ii  libkf5mailtransport5 18.07.90-2
ii  libkf5mailtransportakonadi5  18.07.90-2
ii  libkf5mbox5  18.07.90-1
ii  libkf5mime5abi1  18.07.90-1
ii  libkf5notifications5 5.49.0-1
ii  libkf5notifyconfig5  5.49.0-1
ii  libkf5service-bin5.49.0-1
ii  libkf5service5   5.49.0-1
ii  libkf5textwidgets5   5.49.0-1
ii  libkf5wallet-bin 5.49.0-1
ii  libkf5wallet55.49.0-1
ii  libkf5widgetsaddons5 5.49.0-1
ii  libkf5windowsystem5  5.49.0-1
ii  libkf5xmlgui55.49.0-1
ii  libkolabxml1v5   1.1.6-3+b1
ii  libkpimgapicalendar5 18.07.90-1
ii  libkpimgapicontacts5 18.07.90-1
ii  libkpimgapicore5abi1 18.07.90-1
ii  libkpimgapitasks518.07.90-1
ii  libkpimkdav5abi2 18.07.90-1
ii  libqt5core5a 5.11.1+dfsg-7
ii  libqt5dbus5  5.11.1+dfsg-7
ii  libqt5gui5   5.11.1+dfsg-7
ii  libqt5network5   5.11.1+dfsg-7
ii  libqt5texttospeech5  5.11.1-2
ii  libqt5webenginecore5 5.11.1+dfsg-5
ii  libqt5webenginewidgets5  5.11.1+dfsg-5
ii  libqt5widgets5   5.11.1+dfsg-7
ii  libqt5xml5   5.11.1+dfsg-7
ii  libsasl2-2   2.1.27~101-g0780600+dfsg-3.1
ii  libstdc++6   8.2.0-4

kdepim-runtime recommends no 

Bug#772479: irssi-plugin-xmpp does not work at all on buster

[Antoine Beaupré]

On 2018-09-14 14:41:03, Daniel Kahn Gillmor wrote:
> Control: severity 772479 grave
>
> I've got these packages installed:
>
> ii  irssi 1.1.1-1  amd64terminal based IRC client
> ii  irssi-plugin-xmpp 0.54-2   amd64XMPP plugin for irssi
>
> and if i launch a new irssi installation and do:
>
> /load xmpp
>
> then it responds with:
>
> 13:10 -!- Irssi: xmpp/core is ABI version 7 but Irssi is version 13, cannot 
> load
> 13:10 -!- Irssi: Error loading module xmpp/fe: 
>   /usr/lib/x86_64-linux-gnu/irssi/modules/libfe_xmpp.so: undefined 
>   symbol: xmpp_subscription
>
> so irssi-plugin-xmpp does not work at all, rendering this bug report
> severity grave. :(

I think this needs a binNMU.

Alternatively, we could just rebuild to ship what's pending in git and
do some administrativa. Upstream has no new release but two minor
bugfixes/commits.

a.

-- 
The United States is a nation of laws:
badly written and randomly enforced.
- Frank Zappa

Bug#875116: Bug #875116 in pyqwt3d marked as pending

[Gudjon I. Gudjonsson]

Control: tag -1 pending

Hello,

Bug #875116 in pyqwt3d 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/python-team/modules/pyqwt3d/commit/41f317713bf3896a323b9ee4a732a80b5d640c38


New upstream source (Closes: #812138)

* New upstream source (Closes: #812138)
* Remove Qt4/python2 version (Closes: #699032, #875116)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/875116

Processed: Bug #875116 in pyqwt3d marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #875116 [src:pyqwt3d] [pyqwt3d] Future Qt4 removal from Buster
Added tag(s) pending.

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

Processed: Bug #812138 in pyqwt3d marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #812138 [pyqwt3d] pyqwt3d: FTBFS with GCC 6: narrowing conversion
Ignoring request to alter tags of bug #812138 to the same tags previously set

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

Processed: Bug #812138 in pyqwt3d marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #812138 [pyqwt3d] pyqwt3d: FTBFS with GCC 6: narrowing conversion
Added tag(s) pending.

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

Bug#812138: Bug #812138 in pyqwt3d marked as pending

[Gudjon I. Gudjonsson]

Control: tag -1 pending

Hello,

Bug #812138 in pyqwt3d 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/python-team/modules/pyqwt3d/commit/41f317713bf3896a323b9ee4a732a80b5d640c38


New upstream source (Closes: #812138)

* New upstream source (Closes: #812138)
* Remove Qt4/python2 version (Closes: #699032, #875116)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/812138

Bug#812138: Bug #812138 in pyqwt3d marked as pending

[Gudjon I. Gudjonsson]

Control: tag -1 pending

Hello,

Bug #812138 in pyqwt3d 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/python-team/modules/pyqwt3d/commit/41f317713bf3896a323b9ee4a732a80b5d640c38


New upstream source (Closes: #812138)

* New upstream source (Closes: #812138)
* Remove Qt4/python2 version (Closes: #699032, #875116)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/812138

Bug#906472: horst: FTBFS in buster/sid (unable to open 'stdarg.h')

[Uwe Kleine-König]

Hello,

[Cc += sparse mailing list]

On Fri, Sep 14, 2018 at 05:04:09PM +0300, Adrian Bunk wrote:
> Control: reassign -1 sparse 0.5.2-1
> Control: affects -1 src:horst
> 
> On Sat, Aug 25, 2018 at 10:09:47PM +0200, Christoph Biedl wrote:
> > Santiago Vila wrote...
> > 
> > >   make -j1 check
> > > make[1]: Entering directory '/<>'
> > > sparse -g -O2 -fdebug-prefix-map=/<>=. 
> > > -fstack-protector-strong -Wformat -Werror=format-security -std=gnu99 
> > > -Wall -Wextra -g -I. -DDO_DEBUG -I/usr/include/libnl3 *.[ch]
> > > /usr/include/err.h:25:11: error: unable to open 'stdarg.h'
> > 
> > To reproduce this it's important to remove gcc-7 from the build chroot
> > (apt purge libgcc-7-dev ; apt --purge autoremove).
> > 
> > Problem is, sparse appearently uses hardcoded paths and looks for
> > stdarg.h in (among other places)
> > 
> > | /usr/lib/gcc/x86_64-linux-gnu/7//include/stdarg.h
> > |   ^
> > 
> > ... which fails.
> > 
> > Solution is to rebuild sparse, building horst was successful then.
> > If this is true (please check!), the interesting question is why this
> > wasn't a problem in earlier gcc version bumps.

I think this is a known limitation of sparse and there are three
ways to fix this (in my order of preference):

 a) let horst use cgcc -no-compile instead of sparse; or
 b) let sparse depend on libgcc-7-dev (or whatever provides the
necessary files); or
 c) use autodetection which gcc is used and pick its files.

I'm not sure if a) fixes the problem. It fixed another problem we had
with horst's usage of sparse in the past though[1].

The downside of c) is that running this autodetection on every call to
sparse is probably slowing down sparse a bit which isn't nice.

Best regards
Uwe

[1] https://bugs.debian.org/873508


signature.asc
Description: PGP signature

Bug#908820: marked as done (pcl FTBFS on some 32bit architectures: virtual memory exhausted)

[Debian Bug Tracking System]

Your message dated Fri, 14 Sep 2018 19:49:43 +
with message-id 
and subject line Bug#908820: fixed in pcl 1.8.1+dfsg1-6
has caused the Debian Bug report #908820,
regarding pcl FTBFS on some 32bit architectures: virtual memory exhausted
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.)


-- 
908820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pcl
Version: 1.8.1+dfsg1-4
Severity: serious
Tags: ftbfs patch

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

...
[ 41%] Built target pcl_openni_fast_mesh
virtual memory exhausted: Cannot allocate memory
make[3]: *** 
[sample_consensus/CMakeFiles/pcl_sample_consensus.dir/build.make:118: 
sample_consensus/CMakeFiles/pcl_sample_consensus.dir/src/sac_model_cone.cpp.o] 
Error 1


Note that the regression is actually not in pcl,
but gcc using more money.

The following addresses this by reducing the amount
of debug information when building for 32bit architectures:

--- debian/rules.old2018-09-13 18:24:33.134097776 +
+++ debian/rules2018-09-13 18:25:23.897428251 +
@@ -11,9 +11,8 @@
 CFLAGS+=$(CPPFLAGS)
 CXXFLAGS+=$(CPPFLAGS)
 
-DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH)
-ifneq (,$(filter $(DEB_BUILD_ARCH),mips mipsel))
-   CXXFLAGS+=--param ggc-min-expand=20
+ifeq (32,$(DEB_HOST_ARCH_BITS))
+   CXXFLAGS+=-g1
 endif
 
 ifeq ($(shell dpkg-vendor --derives-from Ubuntu && echo yes),yes)
--- End Message ---
--- Begin Message ---
Source: pcl
Source-Version: 1.8.1+dfsg1-6

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated pcl 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, 14 Sep 2018 21:27:30 +0200
Source: pcl
Binary: libpcl-dev libpcl-apps1.8 libpcl-common1.8 libpcl-features1.8 
libpcl-filters1.8 libpcl-io1.8 libpcl-kdtree1.8 libpcl-keypoints1.8 
libpcl-ml1.8 libpcl-octree1.8 libpcl-outofcore1.8 libpcl-people1.8 
libpcl-recognition1.8 libpcl-registration1.8 libpcl-sample-consensus1.8 
libpcl-search1.8 libpcl-segmentation1.8 libpcl-stereo1.8 libpcl-surface1.8 
libpcl-tracking1.8 libpcl-visualization1.8 pcl-tools libpcl-doc
Architecture: source
Version: 1.8.1+dfsg1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Jochen Sprickerhof 
Description:
 libpcl-apps1.8 - Point Cloud Library - apps library
 libpcl-common1.8 - Point Cloud Library - common library
 libpcl-dev - Point Cloud Library - development files
 libpcl-doc - Point Cloud Library - documentation
 libpcl-features1.8 - Point Cloud Library - features library
 libpcl-filters1.8 - Point Cloud Library - filters library
 libpcl-io1.8 - Point Cloud Library - I/O library
 libpcl-kdtree1.8 - Point Cloud Library - kdtree library
 libpcl-keypoints1.8 - Point Cloud Library - keypoints library
 libpcl-ml1.8 - Point Cloud Library - ml library
 libpcl-octree1.8 - Point Cloud Library - octree library
 libpcl-outofcore1.8 - Point Cloud Library - outofcore library
 libpcl-people1.8 - Point Cloud Library - people library
 libpcl-recognition1.8 - Point Cloud Library - recognition library
 libpcl-registration1.8 - Point Cloud Library - registration library
 libpcl-sample-consensus1.8 - Point Cloud Library - sample consensus library
 libpcl-search1.8 - Point Cloud Library - search library
 libpcl-segmentation1.8 - Point Cloud Library - segmentation library
 libpcl-stereo1.8 - Point Cloud Library - stereo library
 libpcl-surface1.8 - Point Cloud Library - surface library
 libpcl-tracking1.8 - Point Cloud Library - tracking library
 libpcl-visualization1.8 - Point Cloud Library - visualization library
 pcl-tools  - Point Cloud Library - point cloud processing tools
Closes: 908820
Changes:
 pcl (1.8.1+dfsg1-6) unstable; urgency=medium
 .
   [ Jochen Sprickerhof ]
   * use --max-parallel=2 for Ubuntu
   * Add patch for pcl_2d-1.8.pc
 .
   [ Adrian Bunk ]
   * Reduce the amount of debug in

Bug#908705:

[Damián Barberón]

The patches pushed recently from the upstream fixes this. See 


https://gitlab.gnome.org/Jehan/glib/commit/8519368c0eb26ce353e5e1ffd4d23fe8353848dc

Bug#906337: marked as done (bioperl-run: FTBFS in buster/sid (autobuilder hangs))

[Debian Bug Tracking System]

Your message dated Fri, 14 Sep 2018 18:49:39 +
with message-id 
and subject line Bug#906337: fixed in bioperl-run 1.7.2-4
has caused the Debian Bug report #906337,
regarding bioperl-run: FTBFS in buster/sid (autobuilder hangs)
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.)


-- 
906337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bioperl-run
Version: 1.7.2-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep
   dh_update_autotools_config -i
   dh_autoreconf -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- --install_scripts 
perl -I. Build.PL --installdirs vendor --config "optimize=-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2" --config 
"ld=x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro" 
--install_scripts
Checking prerequisites...
  recommends:
*  Bio::FeatureIO is not installed
*  Config::Any is not installed
*  File::Sort is not installed


[... snipped ...]

ok 106 - An object of class 'Bio::SeqFeature::Generic' isa 
'Bio::SeqFeature::Generic'
ok 107 - An object of class 'Bio::SeqFeature::Generic' isa 
'Bio::SeqFeature::Generic'
ok 108 - An object of class 'Bio::SeqFeature::Generic' isa 
'Bio::SeqFeature::Generic'
ok 109 - An object of class 'Bio::SeqFeature::Generic' isa 
'Bio::SeqFeature::Generic'
ok 110 - An object of class 'Bio::SeqFeature::Generic' isa 
'Bio::SeqFeature::Generic'
ok 111 - An object of class 'Bio::SeqFeature::Generic' isa 
'Bio::SeqFeature::Generic'
ok
# Required executable for Bio::Tools::Run::Hmmer is not present
t/Hmmer.t . 
1..27
ok 1 - use Bio::Tools::Run::Hmmer;
ok 2 - use Bio::SeqIO;
ok 3 - use Bio::AlignIO;
ok 4 - An object of class 'Bio::Tools::Run::Hmmer' isa 'Bio::Tools::Run::Hmmer'
ok 5
ok 6
ok 7
ok 8 # skip Required executable for Bio::Tools::Run::Hmmer is not present
ok 9 # skip Required executable for Bio::Tools::Run::Hmmer is not present
ok 10 # skip Required executable for Bio::Tools::Run::Hmmer is not present
ok 11 # skip Required executable for Bio::Tools::Run::Hmmer is not present
ok 12 # skip Required executable for Bio::Tools::Run::Hmmer is not present
ok 13 # skip Required executable for Bio::Tools::Run::Hmmer is not present
ok 14 # skip Required executable for Bio::Tools::Run::Hmmer is not present
ok 15 # skip Required executable for Bio::Tools::Run::Hmmer is not present
ok 16 # skip Required executable for Bio::Tools::Run::Hmmer is not present
ok 17 # skip Required executable for Bio::Tools::Run::Hmmer is not present
ok 18 # skip Required executable for Bio::Tools::Run::Hmmer is not present
ok 19 # skip Required executable for Bio::Tools::Run::Hmmer is not present
ok 20 # skip Required executable for Bio::Tools::Run::Hmmer is not present
ok 21 # skip Required executable for Bio::Tools::Run::Hmmer is not present
ok 22 # skip Required executable for Bio::Tools::Run::Hmmer is not present
ok 23 # skip Required executable for Bio::Tools::Run::Hmmer is not present
ok 24 # skip Required executable for Bio::Tools::Run::Hmmer is not present
ok 25 # skip Required executable for Bio::Tools::Run::Hmmer is not present
ok 26 # skip Required executable for Bio::Tools::Run::Hmmer is not present
ok 27 # skip Required executable for Bio::Tools::Run::Hmmer is not present
ok
--
MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
with errorcode 1.

NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.
--
E: Build killed with signal TERM after 60 minutes of inactivity


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

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/bioperl-run.html

where you can get a full build log if you need it.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that thi

Bug#903579: FWIW I have filed the bug on Debian's behalf

[Sandro Tosi]

> While I know barely anything about python, I did however file the bug
> as shared by Bas and maintained by Sandro Tosi as
> https://bugs.python.org/issue34684?@template=item&@pagesize=50&@startwith=0

as you said, you dont know much about python, so please refrain from
engaging in conversations with upstream projects. in particular
CPython is definitely not the right project to open a bug to, most
likely there's no right project and it's something that Debian will
have to handle internally.

if you want to spam the debian bts with your reports, just do that
(well, we can agree some of your reports tend to be really low quality
so you may prefer to engage in discussion in user-support forum first,
such as mailing lists and forum listed at
https://www.debian.org/support) but please dont report bugs upstream
if you're not 100% sure that's the right thing to do.

> @Sandro Tosi maybe you could enlighten upstream more about the issue
> and see if a fix is possible.

there's nothing to enlighten here, CPython is the wrong recipient for this.

Thanks,

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
G+: https://plus.google.com/u/0/+SandroTosi

Processed: Re: Bug#772479: irssi-plugin-xmpp does not work at all on buster

[Debian Bug Tracking System]

Processing control commands:

> severity 772479 grave
Bug #772479 [irssi-plugin-xmpp] irssi-plugin-xmpp needs rebuild on new uploads 
of irssi
Severity set to 'grave' from 'important'

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

Bug#908835: dom4j: FTBFS because of javadoc error

[Markus Koschany]

Source: dom4j
Version: 2.1.1-1
Severity: serious

I just stumbled upon this bug. Apparently the last upload was never
built on our buildd. There is some kind of javadoc error:

javadoc: error - Error fetching URL: file:/usr/share/doc/default-jdk/api/

I may look into this later but filing a bug report now, so that it won't
get lost.

Markus

Bug#908833: colmap: FTBFS (dh_auto_configure fails)

[Santiago Vila]

Package: src:colmap
Version: 3.4-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   dh_auto_configure -a
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" ..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done

[... snipped ...]

  ^
In file included from /usr/lib/gcc/x86_64-linux-gnu/8/include/immintrin.h:41,
 from 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:2:
/usr/lib/gcc/x86_64-linux-gnu/8/include/avxintrin.h:365:1: error: inlining 
failed in call to always_inline '__m256 _mm256_sub_ps(__m256, __m256)': target 
specific option mismatch
 _mm256_sub_ps (__m256 __A, __m256 __B)
 ^
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:7:35: note: 
called from here
   __m256 c = _mm256_sub_ps(a, b);
  ~^~
In file included from /usr/lib/gcc/x86_64-linux-gnu/8/include/immintrin.h:41,
 from 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:2:
/usr/lib/gcc/x86_64-linux-gnu/8/include/avxintrin.h:1248:1: error: inlining 
failed in call to always_inline '__m256 _mm256_set_ps(float, float, float, 
float, float, float, float, float)': target specific option mismatch
 _mm256_set_ps (float __A, float __B, float __C, float __D,
 ^
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:6:35: note: 
called from here
   __m256 b = _mm256_set_ps(1.0, 3.0, 5.0, 7.0, 9.0, 11.0, 13.0, 15.0);
  ~^~~
In file included from /usr/lib/gcc/x86_64-linux-gnu/8/include/immintrin.h:41,
 from 
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:2:
/usr/lib/gcc/x86_64-linux-gnu/8/include/avxintrin.h:1248:1: error: inlining 
failed in call to always_inline '__m256 _mm256_set_ps(float, float, float, 
float, float, float, float, float)': target specific option mismatch
 _mm256_set_ps (float __A, float __B, float __C, float __D,
 ^
/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.cxx:5:35: note: 
called from here
   __m256 a = _mm256_set_ps(2.0, 4.0, 6.0, 8.0, 10.0, 12.0, 14.0, 16.0);
  ~^~~~
make[2]: *** [CMakeFiles/cmTC_d200f.dir/build.make:66: 
CMakeFiles/cmTC_d200f.dir/src.cxx.o] Error 1
make[2]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'
make[1]: *** [Makefile:121: cmTC_d200f/fast] Error 2
make[1]: Leaving directory 
'/<>/obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp'

Return value: 1
Source file was:

#include 
#include 
int main() {
  __m256 a = _mm256_set_ps(2.0, 4.0, 6.0, 8.0, 10.0, 12.0, 14.0, 16.0);
  __m256 b = _mm256_set_ps(1.0, 3.0, 5.0, 7.0, 9.0, 11.0, 13.0, 15.0);
  __m256 c = _mm256_sub_ps(a, b);
  float* f = (float*)&c;
  return 0;
}
dh_auto_configure: 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" .. returned exit code 1
make: *** [debian/rules:28: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2


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

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

where you can get a full build log if you need it.

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

Thanks.

Bug#903579: FWIW I have filed the bug on Debian's behalf

[shirish शिरीष]

Dear all,

While I know barely anything about python, I did however file the bug
as shared by Bas and maintained by Sandro Tosi as
https://bugs.python.org/issue34684?@template=item&@pagesize=50&@startwith=0

@Sandro Tosi maybe you could enlighten upstream more about the issue
and see if a fix is possible.

-- 
  Regards,
  Shirish Agarwal  शिरीष अग्रवाल
  My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
EB80 462B 08E1 A0DE A73A  2C2F 9F3D C7A4 E1C4 D2D8

Bug#908824: libnet-server-mail-perl FTBFS: t/starttls.t failure

[gregor herrmann]

On Fri, 14 Sep 2018 17:29:59 +0200, Xavier wrote:

> I'll take a look to recent SSL problems (and Net::SMTP dependencies) to
> try to understand.

My first idea was that the problems with IO::Socket::SSL and OpenSSL
1.1.1 might be the cause for this failure; but as it doesn't happen
in my sid chroot I'm out of ideas ...
 

Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#908304: marked as done (ghostscript: CVE-2018-16510)

[Debian Bug Tracking System]

Your message dated Fri, 14 Sep 2018 17:04:43 +
with message-id 
and subject line Bug#908304: fixed in ghostscript 9.25~dfsg-1~exp1
has caused the Debian Bug report #908304,
regarding ghostscript: CVE-2018-16510
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.)


-- 
908304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ghostscript
Version: 9.22~dfsg-3
Severity: grave
Tags: patch security upstream
Justification: user security hole
Forwarded: https://bugs.ghostscript.com/show_bug.cgi?id=699671

Hi,

The following vulnerability was published for ghostscript.

CVE-2018-16510[0]:
| An issue was discovered in Artifex Ghostscript before 9.24. Incorrect
| exec stack handling in the "CS" and "SC" PDF primitives could be used
| by remote attackers able to supply crafted PDFs to crash the
| interpreter or possibly have unspecified other impact.

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-16510
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16510
[1] https://bugs.ghostscript.com/show_bug.cgi?id=699671
[2] 
http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=ea735ba37dc0fd5f5622d031830b9a559dec1cc9

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: ghostscript
Source-Version: 9.25~dfsg-1~exp1

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated ghostscript 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, 14 Sep 2018 18:39:11 +0200
Source: ghostscript
Binary: ghostscript ghostscript-x ghostscript-doc libgs9 libgs9-common 
libgs-dev ghostscript-dbg
Architecture: source
Version: 9.25~dfsg-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Printing Team 
Changed-By: Jonas Smedegaard 
Description:
 ghostscript - interpreter for the PostScript language and for PDF
 ghostscript-dbg - interpreter for the PostScript language and for PDF - Debug 
symbo
 ghostscript-doc - interpreter for the PostScript language and for PDF - 
Documentati
 ghostscript-x - interpreter for the PostScript language and for PDF - X11 
support
 libgs-dev  - interpreter for the PostScript language and for PDF - Development
 libgs9 - interpreter for the PostScript language and for PDF - Library
 libgs9-common - interpreter for the PostScript language and for PDF - common 
file
Closes: 907703 908300 908303 908304 908305
Changes:
 ghostscript (9.25~dfsg-1~exp1) experimental; urgency=medium
 .
   [ upstream ]
   * New bugfix release(s).
 Closes: Bug#907703, #908300, #908303, #908304, #908305
 (CVE-2018-16509, CVE-2018-16543, CVE-2018-16510, CVE-2018-16585).
 Thanks to Salvatore Bonaccorso.
 .
   * Update copyright info:
 + Stop exclude image containing non-DFSG ICC profile when
   repackaging upstream source: Fixed upstream.
 + Fix cover license FTL.
   * Set Rules-Requires-Root: no.
   * Update symbols:
 + Drop commented out obsolete symbols.
 + Flag as optional symbols not declared in public header files.
   * Avoid privacy breach linking documentation to jquery:
 + Add patch 2009 to use local jquery.
 + Add symlink from relative link to system-shared jquery library.
 + Have ghostscript-doc depend on libjs-jquery.
   * Avoid privacy breach linking documentation to font:
 + Avoid linking to remote fonts in documentation.
   * Avoid privacy breach linking documentation with Google:
 + Strip googletagmanager code from documentation.
Checksums-Sha1:
 3bffe18729eeac8146b0e8567478db9334fecbb2 2765 ghostscript_9.25~dfsg-1~exp1.dsc
 6801ed2321af28a60cad6b39da07813b9d4c8840 1752 
ghostscript_9.25~dfsg.orig.tar.xz
 87bc40e0b7ead6664482a4a2e3105c3ab02bcf1b 106640 
ghostscr

Bug#908305: marked as done (ghostscript: CVE-2018-16585)

[Debian Bug Tracking System]

Your message dated Fri, 14 Sep 2018 17:04:43 +
with message-id 
and subject line Bug#908305: fixed in ghostscript 9.25~dfsg-1~exp1
has caused the Debian Bug report #908305,
regarding ghostscript: CVE-2018-16585
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.)


-- 
908305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ghostscript
Version: 9.20~dfsg-3.2
Severity: grave
Tags: patch security upstream
Justification: user security hole
Forwarded: https://bugs.ghostscript.com/show_bug.cgi?id=699663
Control: fixed -1 9.20~dfsg-3.2+deb9u3

Hi,

The following vulnerability was published for ghostscript.

CVE-2018-16585[0]:
| An issue was discovered in Artifex Ghostscript before 9.24. The
| .setdistillerkeys PostScript command is accepted even though it is not
| intended for use during document processing (e.g., after the startup
| phase). This leads to memory corruption, allowing remote attackers able
| to supply crafted PostScript to crash the interpreter or possibly have
| unspecified other impact.

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-16585
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16585
[1] 
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=1497d65039885a52b598b137dd8622bd4672f9be
[2] 
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=971472c83a345a16dac9f90f91258bb22dd77f22
[3] https://bugs.ghostscript.com/show_bug.cgi?id=699663

Please adjust the affected versions in the BTS as needed.

Regards,
Salvtore
--- End Message ---
--- Begin Message ---
Source: ghostscript
Source-Version: 9.25~dfsg-1~exp1

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated ghostscript 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, 14 Sep 2018 18:39:11 +0200
Source: ghostscript
Binary: ghostscript ghostscript-x ghostscript-doc libgs9 libgs9-common 
libgs-dev ghostscript-dbg
Architecture: source
Version: 9.25~dfsg-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Printing Team 
Changed-By: Jonas Smedegaard 
Description:
 ghostscript - interpreter for the PostScript language and for PDF
 ghostscript-dbg - interpreter for the PostScript language and for PDF - Debug 
symbo
 ghostscript-doc - interpreter for the PostScript language and for PDF - 
Documentati
 ghostscript-x - interpreter for the PostScript language and for PDF - X11 
support
 libgs-dev  - interpreter for the PostScript language and for PDF - Development
 libgs9 - interpreter for the PostScript language and for PDF - Library
 libgs9-common - interpreter for the PostScript language and for PDF - common 
file
Closes: 907703 908300 908303 908304 908305
Changes:
 ghostscript (9.25~dfsg-1~exp1) experimental; urgency=medium
 .
   [ upstream ]
   * New bugfix release(s).
 Closes: Bug#907703, #908300, #908303, #908304, #908305
 (CVE-2018-16509, CVE-2018-16543, CVE-2018-16510, CVE-2018-16585).
 Thanks to Salvatore Bonaccorso.
 .
   * Update copyright info:
 + Stop exclude image containing non-DFSG ICC profile when
   repackaging upstream source: Fixed upstream.
 + Fix cover license FTL.
   * Set Rules-Requires-Root: no.
   * Update symbols:
 + Drop commented out obsolete symbols.
 + Flag as optional symbols not declared in public header files.
   * Avoid privacy breach linking documentation to jquery:
 + Add patch 2009 to use local jquery.
 + Add symlink from relative link to system-shared jquery library.
 + Have ghostscript-doc depend on libjs-jquery.
   * Avoid privacy breach linking documentation to font:
 + Avoid linking to remote fonts in documentation.
   * Avoid privacy breach linking documentation with Google:
 + Strip googletagmana

Bug#907703: marked as done (ghostscript: CVE-2018-16509)

[Debian Bug Tracking System]

Your message dated Fri, 14 Sep 2018 17:04:43 +
with message-id 
and subject line Bug#907703: fixed in ghostscript 9.25~dfsg-1~exp1
has caused the Debian Bug report #907703,
regarding ghostscript: CVE-2018-16509
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.)


-- 
907703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ghostscript
Version: 9.22~dfsg-3
Severity: grave
Tags: patch security upstream
Control: found -1 9.20~dfsg-1

There is one more followup fix needed:

http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=79cccf641486
https://bugs.ghostscript.com/show_bug.cgi?id=699654

Decoupling this from #907332 as issues there adressed, should ease a
bit tracking for fixes.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: ghostscript
Source-Version: 9.25~dfsg-1~exp1

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated ghostscript 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, 14 Sep 2018 18:39:11 +0200
Source: ghostscript
Binary: ghostscript ghostscript-x ghostscript-doc libgs9 libgs9-common 
libgs-dev ghostscript-dbg
Architecture: source
Version: 9.25~dfsg-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Printing Team 
Changed-By: Jonas Smedegaard 
Description:
 ghostscript - interpreter for the PostScript language and for PDF
 ghostscript-dbg - interpreter for the PostScript language and for PDF - Debug 
symbo
 ghostscript-doc - interpreter for the PostScript language and for PDF - 
Documentati
 ghostscript-x - interpreter for the PostScript language and for PDF - X11 
support
 libgs-dev  - interpreter for the PostScript language and for PDF - Development
 libgs9 - interpreter for the PostScript language and for PDF - Library
 libgs9-common - interpreter for the PostScript language and for PDF - common 
file
Closes: 907703 908300 908303 908304 908305
Changes:
 ghostscript (9.25~dfsg-1~exp1) experimental; urgency=medium
 .
   [ upstream ]
   * New bugfix release(s).
 Closes: Bug#907703, #908300, #908303, #908304, #908305
 (CVE-2018-16509, CVE-2018-16543, CVE-2018-16510, CVE-2018-16585).
 Thanks to Salvatore Bonaccorso.
 .
   * Update copyright info:
 + Stop exclude image containing non-DFSG ICC profile when
   repackaging upstream source: Fixed upstream.
 + Fix cover license FTL.
   * Set Rules-Requires-Root: no.
   * Update symbols:
 + Drop commented out obsolete symbols.
 + Flag as optional symbols not declared in public header files.
   * Avoid privacy breach linking documentation to jquery:
 + Add patch 2009 to use local jquery.
 + Add symlink from relative link to system-shared jquery library.
 + Have ghostscript-doc depend on libjs-jquery.
   * Avoid privacy breach linking documentation to font:
 + Avoid linking to remote fonts in documentation.
   * Avoid privacy breach linking documentation with Google:
 + Strip googletagmanager code from documentation.
Checksums-Sha1:
 3bffe18729eeac8146b0e8567478db9334fecbb2 2765 ghostscript_9.25~dfsg-1~exp1.dsc
 6801ed2321af28a60cad6b39da07813b9d4c8840 1752 
ghostscript_9.25~dfsg.orig.tar.xz
 87bc40e0b7ead6664482a4a2e3105c3ab02bcf1b 106640 
ghostscript_9.25~dfsg-1~exp1.debian.tar.xz
 4209318532b3776f8a51cb79e2275ef8fa8129e7 11818 
ghostscript_9.25~dfsg-1~exp1_amd64.buildinfo
Checksums-Sha256:
 799f47facbc6ef2b11d9846a23330c74c8cc7d60163d9e2b0fd7c6831839bdde 2765 
ghostscript_9.25~dfsg-1~exp1.dsc
 d35949fe5c4e827d9468f29d395dd05c273d2482c703259084c8aff0a0ca6d82 1752 
ghostscript_9.25~dfsg.orig.tar.xz
 6b3006bbcc6528aa1034fc1d73bf5fbd0451e9dc12607b6a67e25df062f5 106640 
ghostscript_9.25~dfsg-1~exp1.debian.tar.xz
 fe0c26419a55e60d679231e5df4a281f27c62865b4f57c16dc25b14bea5467a6 11818 
ghostscript_9.25~dfsg-1~exp1_amd64.buildinfo
Files:
 e728b22207588f4f237e7d0b209934d0 2765 text optional 
ghostscript

Bug#908303: marked as done (ghostscript: CVE-2018-16543)

[Debian Bug Tracking System]

Your message dated Fri, 14 Sep 2018 17:04:43 +
with message-id 
and subject line Bug#908303: fixed in ghostscript 9.25~dfsg-1~exp1
has caused the Debian Bug report #908303,
regarding ghostscript: CVE-2018-16543
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.)


-- 
908303: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908303
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ghostscript
Version: 9.20~dfsg-3.2
Severity: grave
Tags: patch security upstream
Justification: user security hole
Forwarded: https://bugs.ghostscript.com/show_bug.cgi?id=699670
Control: fixed -1 9.20~dfsg-3.2+deb9u4

Hi,

The following vulnerability was published for ghostscript.

CVE-2018-16543[0]:
| In Artifex Ghostscript before 9.24, gssetresolution and gsgetresolution
| allow attackers to have an unspecified impact.

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-16543
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16543
[1] 
http://git.ghostscript.com/?p=ghostpdl.git;a=commit;h=5b5536fa88a9e885032bc0df3852c3439399a5c0

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: ghostscript
Source-Version: 9.25~dfsg-1~exp1

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated ghostscript 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, 14 Sep 2018 18:39:11 +0200
Source: ghostscript
Binary: ghostscript ghostscript-x ghostscript-doc libgs9 libgs9-common 
libgs-dev ghostscript-dbg
Architecture: source
Version: 9.25~dfsg-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Printing Team 
Changed-By: Jonas Smedegaard 
Description:
 ghostscript - interpreter for the PostScript language and for PDF
 ghostscript-dbg - interpreter for the PostScript language and for PDF - Debug 
symbo
 ghostscript-doc - interpreter for the PostScript language and for PDF - 
Documentati
 ghostscript-x - interpreter for the PostScript language and for PDF - X11 
support
 libgs-dev  - interpreter for the PostScript language and for PDF - Development
 libgs9 - interpreter for the PostScript language and for PDF - Library
 libgs9-common - interpreter for the PostScript language and for PDF - common 
file
Closes: 907703 908300 908303 908304 908305
Changes:
 ghostscript (9.25~dfsg-1~exp1) experimental; urgency=medium
 .
   [ upstream ]
   * New bugfix release(s).
 Closes: Bug#907703, #908300, #908303, #908304, #908305
 (CVE-2018-16509, CVE-2018-16543, CVE-2018-16510, CVE-2018-16585).
 Thanks to Salvatore Bonaccorso.
 .
   * Update copyright info:
 + Stop exclude image containing non-DFSG ICC profile when
   repackaging upstream source: Fixed upstream.
 + Fix cover license FTL.
   * Set Rules-Requires-Root: no.
   * Update symbols:
 + Drop commented out obsolete symbols.
 + Flag as optional symbols not declared in public header files.
   * Avoid privacy breach linking documentation to jquery:
 + Add patch 2009 to use local jquery.
 + Add symlink from relative link to system-shared jquery library.
 + Have ghostscript-doc depend on libjs-jquery.
   * Avoid privacy breach linking documentation to font:
 + Avoid linking to remote fonts in documentation.
   * Avoid privacy breach linking documentation with Google:
 + Strip googletagmanager code from documentation.
Checksums-Sha1:
 3bffe18729eeac8146b0e8567478db9334fecbb2 2765 ghostscript_9.25~dfsg-1~exp1.dsc
 6801ed2321af28a60cad6b39da07813b9d4c8840 1752 
ghostscript_9.25~dfsg.orig.tar.xz
 87bc40e0b7ead6664482a4a2e3105c3ab02bcf1b 106640 
ghostscript_9.25~dfsg-1~exp1.debian.tar.xz
 4209318532b3776f8a51cb79e2275ef8fa8129e7 11818 
ghostscript_9.25~dfsg-1~exp1_amd64.buildinfo
Checksums-Sha256:
 799f47fa

Bug#908300: marked as done (ghostscript: Regression from a054156d425b4dbdaaa9fda4b5f1182b27598c2b commit ("Fix handling of pre-SAFER opened files"))

[Debian Bug Tracking System]

Your message dated Fri, 14 Sep 2018 17:04:43 +
with message-id 
and subject line Bug#908300: fixed in ghostscript 9.25~dfsg-1~exp1
has caused the Debian Bug report #908300,
regarding ghostscript: Regression from a054156d425b4dbdaaa9fda4b5f1182b27598c2b 
commit ("Fix handling of pre-SAFER opened files")
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.)


-- 
908300: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908300
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ghostscript
Version: 9.22~dfsg-3
Severity: serious
Tags: patch upstream
Justification: regression

Hi

It was reported a regression while testing the security update, which
resulted in the increment to +deb9u4, which included the fix. The
regression was spotted while
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=a054156d425b4dbdaaa9fda4b5f1182b27598c2b;hp=0d3901189f245232f0161addf215d7268c4d05a3
is applied:

https://github.com/apple/cups/issues/5392

There is an upstream fix for it:

http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=150c8f69646b854a99f35f27edaae012eb2e900f

(which might require
http://git.ghostscript.com/?p=ghostpdl.git;a=commitdiff;h=5b5536fa88a9e885032bc0df3852c3439399a5c
as well).

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: ghostscript
Source-Version: 9.25~dfsg-1~exp1

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated ghostscript 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, 14 Sep 2018 18:39:11 +0200
Source: ghostscript
Binary: ghostscript ghostscript-x ghostscript-doc libgs9 libgs9-common 
libgs-dev ghostscript-dbg
Architecture: source
Version: 9.25~dfsg-1~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Printing Team 
Changed-By: Jonas Smedegaard 
Description:
 ghostscript - interpreter for the PostScript language and for PDF
 ghostscript-dbg - interpreter for the PostScript language and for PDF - Debug 
symbo
 ghostscript-doc - interpreter for the PostScript language and for PDF - 
Documentati
 ghostscript-x - interpreter for the PostScript language and for PDF - X11 
support
 libgs-dev  - interpreter for the PostScript language and for PDF - Development
 libgs9 - interpreter for the PostScript language and for PDF - Library
 libgs9-common - interpreter for the PostScript language and for PDF - common 
file
Closes: 907703 908300 908303 908304 908305
Changes:
 ghostscript (9.25~dfsg-1~exp1) experimental; urgency=medium
 .
   [ upstream ]
   * New bugfix release(s).
 Closes: Bug#907703, #908300, #908303, #908304, #908305
 (CVE-2018-16509, CVE-2018-16543, CVE-2018-16510, CVE-2018-16585).
 Thanks to Salvatore Bonaccorso.
 .
   * Update copyright info:
 + Stop exclude image containing non-DFSG ICC profile when
   repackaging upstream source: Fixed upstream.
 + Fix cover license FTL.
   * Set Rules-Requires-Root: no.
   * Update symbols:
 + Drop commented out obsolete symbols.
 + Flag as optional symbols not declared in public header files.
   * Avoid privacy breach linking documentation to jquery:
 + Add patch 2009 to use local jquery.
 + Add symlink from relative link to system-shared jquery library.
 + Have ghostscript-doc depend on libjs-jquery.
   * Avoid privacy breach linking documentation to font:
 + Avoid linking to remote fonts in documentation.
   * Avoid privacy breach linking documentation with Google:
 + Strip googletagmanager code from documentation.
Checksums-Sha1:
 3bffe18729eeac8146b0e8567478db9334fecbb2 2765 ghostscript_9.25~dfsg-1~exp1.dsc
 6801ed2321af28a60cad6b39da07813b9d4c8840 1752 
ghostscript_9.25~dfsg.orig.tar.xz
 87bc40e0b7ead6664482a4a2e3105c3ab02bcf1b 106640 
ghostscript_9.25~dfsg-1~exp1.debian.tar.xz
 4209318532b3776f8a51cb79e2275ef8fa8129e7 11818 
ghostscript_9.25~dfsg-1~exp1_amd64.buildinfo
Checksums-Sha256:
 799f47facbc6ef2b11d9846a23330c74c8cc7d60163d9e2b0fd7c6831839bdde 

Bug#908784: nethack: license incompatibility results in non-distributable binaries

[Vincent Cheng]

Hi James,

On Thu, Sep 13, 2018 at 2:51 PM James Cowgill  wrote:
>
> Source: nethack
> Version: 3.4.3-14
> Severity: serious
> X-Debbugs-CC: vch...@debian.org
>
> Hi,
>
> While reviewing the copyright file for the NetHack 3.6.1 upload, I
> noticed that the debian directory (and its patches) are marked as under
> the GPL-2.0. Unfortunately NetHack's special NGPL license is not
> compatible with the GPL (both are copyleft with some conflicting terms),
> so I have come to the conclusion that Debian's version of NetHack is not
> distributable in binary form at all.
>
> Thankfully I think this can be resolved fairly smoothly. If I look at
> the package history, I see that before 3.4.3-14 everything was licensed
> under the NGPL (except for the lisp patches). In this version, the
> copyright file was changed to relicense(?!) the debian/ directory under
> the GPL. Vincent and I are the only people who have claimed copyright
> since that point, and I am fine with licensing my stuff under the NGPL,
> so Vincent is the only person who needs asking.
>
> Vincent, can all your changes to the nethack package be licensed under
> the NGPL instead of the GPL-2.0?

Yes, I'm fine with licensing my changes to nethack under the NGPL as well.

Regards,
Vincent

Bug#907493: Timeout in autopkgtest also in Ubuntu Cosmic with Ghostscript 9.24

[Jonas Smedegaard]

Quoting Till Kamppeter (2018-09-14 14:52:28)
> On Ubuntu the timeouts in the CUPS autopkgtest do not happen any more 
> with Ghostscript 9.25 which got released yesterday and is highly 
> recommended by upstream to fix the regressions in 9.24.

Thanks Till, quite helpful!

I am working on Ghostscript 9.25, expecting a release later today.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#908824: libnet-server-mail-perl FTBFS: t/starttls.t failure

[Xavier]

Hi all,

looking at CPAN reports [1], no bug found by CPAN testers even on Gregor
machine [2] ;-) (except on Windows, which is a known problem).

I'll take a look to recent SSL problems (and Net::SMTP dependencies) to
try to understand.

Cheers,
Xavier

[1] http://matrix.cpantesters.org/?dist=Net-Server-Mail+0.25
[2]
http://www.cpantesters.org/cpan/report/85f34480-b7e8-11e8-913e-4c12c844a040

Bug#908827: mesa: Fails to build on Stretch, missing min build dep

[Andrea Vettorello]

Source: mesa
Version: 18.2.0-1
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

Mesa 18.2.0-1 fails to build on Stretch, I can't find the relevant bug report
on freedesktop.org but now it requires xcb-proto >= 1.13.

After compiling and installing xcb-proto and libxcb 1.13-1 from unstable, the
package was built succesfully.



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

Kernel: Linux 4.19.0-rc2-test1 (SMP w/8 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)

Processed: severity of 908821 is serious

[Debian Bug Tracking System]

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

> severity 908821 serious
Bug #908821 [firefox-esr] firefox-esr: updated version and firefox crasehst at 
start
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#884032: marked as done (burp FTBFS: FAIL: runner)

[Debian Bug Tracking System]

Your message dated Fri, 14 Sep 2018 15:04:29 +
with message-id 
and subject line Bug#884032: fixed in burp 2.1.30-1
has caused the Debian Bug report #884032,
regarding burp FTBFS: FAIL: runner
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.)


-- 
884032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: burp
Version: 2.0.54-4
Severity: serious

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

...
make  check-TESTS
make[2]: Entering directory '/<>'
make[3]: Entering directory '/<>'
FAIL: runner
===
   Burp 2.0.54: ./test-suite.log
===

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

.. contents:: :depth: 2

FAIL: runner


Running suite(s): alloc
 asfd
 attribs
 base64
 client_acl
 client_auth
 client_extra_comms
 client_extrameta
 client_find
 client_monitor
 client_monitor_json_input
 client_monitor_lline
 client_monitor_status_client_ncurses
 client_protocol1_backup_phase2
 client_protocol2_backup_phase2
 client_protocol2_rabin_read
 client_restore
 client_xattr
 cmd
 conf
 conffile
 fzp
 hexmap
 lock
 pathcmp
 protocol1_handy
 protocol1_rs_buf
 protocol2_blist
 protocol2_blk
 protocol2_rabin_rabin
 protocol2_rabin_rconf
 protocol2_rabin_win
 sbuf_protocol2
 server_auth
 server_ca
 server_backup_phase3
 server_bu_get
 server_delete
 server_extra_comms
 server_list
 server_manio
 server_monitor_browse
 server_monitor_cache
 server_monitor_cstat
 server_monitor_json_output
 server_protocol1_backup_phase2
 server_protocol1_backup_phase4
0.4
0.3
 server_protocol1_bedup
 server_protocol1_blocklen
 server_protocol1_dpth
 server_protocol1_fdirs
 server_protocol1_restore
 server_protocol2_backup_phase2
 server_protocol2_backup_phase4
 server_protocol2_champ_chooser_champ_chooser
 server_protocol2_champ_chooser_champ_server
 server_protocol2_champ_chooser_dindex
 server_protocol2_champ_chooser_hash
 server_protocol2_champ_chooser_scores
 server_protocol2_champ_chooser_sparse
 server_protocol2_dpth
 server_restore
 server_resume
 server_run_action
 server_sdirs
 slist
99%: Checks: 324, Failures: 3, Errors: 0
utest/client/test_extrameta.c:102:F:Core:test_extrametas:0: Assertion 
'!set_extrameta( NULL, path, expected, strlen(expected), NULL )' failed
utest/client/protocol2/test_rabin_read.c:80:F:Core:test_rabin_read:0: Assertion 
'!set_xattr( NULL, sb->path.buf, x.write, strlen(x.write), metasymbol, NULL )' 
failed
utest/client/test_xattr.c:149:F:Core:test_xattrs:0: Assertion '!set_xattr( 
NULL, path, x.write, strlen(x.write), metasymbol, NULL )' failed
FAIL runner (exit status: 1)


Testsuite summary for Burp 2.0.54

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

See ./test-suite.log
Please report to https://github.com/grke/burp/issues

Makefile:7953: recipe for target 'test-suite.log' failed
make[3]: *** [test-suite.log] Error 1
make[3]: Leaving directory '/<>'
Makefile:8059: recipe for target 'check-TESTS' failed
make[2]: *** [check-TESTS] Error 2
make[2]: Leaving directory '/<>'
Makefile:8264: recipe for target 'check-am' failed
make[1]: *** [check-am] Error 2
make[1]: Leaving directory '/<>'
dh_auto_test: make -j3 check VERBOSE=1 returned exit code 2
debian/rules:7: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2
--- End Message ---
--- Begin Message ---
Source: burp
Source-Version: 2.1.30-1

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

Debian distribution maintenance software
pp.
Calogero Lo Leggio (kalos)  (supplier of updated burp 
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: T

Bug#908136: src:h2o: FTBFS on amd64

[Apollon Oikonomopoulos]

On 15:53 Fri 14 Sep , Apollon Oikonomopoulos wrote:
> The tests in t/50reverse-proxy-proxy-protocol.t and 
> t/40session-ticket.t report no session reuse with OpenSSL 1.1.1 and 
> need further investigation.

t/40session-ticket.t is a false positive: in TLSv1.3 session information 
is sent after the handshake has finished, and the way s_client is 
invoked in the test means that it can exit before it receives the 
session data. Until this is fixed upstream, I patched the test to always 
use TLSv1.2.

t/50reverse-proxy-session-resumption.t needs further investigation, but 
it seems that H2O's client code doesn't support session resumption for 
TLSv1.3 upstreams (which is H2O itself in the test case). I'm tempted to 
just disable the test even if resumption is indeed broken for TLSv1.3 
upstreams.

Bug#906461: florence: diff for NMU version 0.6.3-1.1

[Jérémy Bobbio]

Hi!

On 14/09/2018 15:51, Adrian Bunk wrote:
> I've prepared an NMU for florence (versioned as 0.6.3-1.1) and uploaded 
> it to DELAYED/14. Please feel free to tell me if I should cancel it.

Thanks!

Feel free to upload it right away or even take over the package.
I sadly still haven't found enough time and energy to adjust packages to
my current (non-)involvement in Debian.

--
Lunar



signature.asc
Description: OpenPGP digital signature

Bug#907370: marked as done (TypeError: object of type 'int' has no len())

[Debian Bug Tracking System]

Your message dated Fri, 14 Sep 2018 14:40:57 +
with message-id 
and subject line Bug#907370: fixed in python-sh 1.12.14-1.1
has caused the Debian Bug report #907370,
regarding TypeError: object of type 'int' has no len()
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.)


-- 
907370: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907370
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-sh
Version: 1.11-1
Severity: grave

I found a regression in the python3-sh package. I have yet to find
exactly what is going on, but it looks to me like something changed in
Python 3.6 that broke the sh module in some way:

$ lwn get -o blog/2017-12-13-kubecon-overview.mdwn 
https://lwn.net/Articles/741301/
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python3.6/threading.py", line 916, in _bootstrap_inner
self.run()
  File "/usr/lib/python3.6/threading.py", line 864, in run
self._target(*self._args, **self._kwargs)
  File "/usr/lib/python3/dist-packages/sh.py", line 1453, in input_thread
done = stdin.write()
  File "/usr/lib/python3/dist-packages/sh.py", line 1799, in write
self.log.debug("got chunk size %d: %r", len(proc_chunk),
TypeError: object of type 'int' has no len()

The source for the `lwn` command is here:

https://gitlab.com/anarcat/lwn/blob/master/lwn.py

It's totally unclear to me, from the backtrace, from *where* exactly
sh is being called, so I am having a hard time writing a
reproducer... But I am *guessing* it's this call:

result = sh.pandoc(filter_args, _in=content)

But really, I have no frigging clue.

Any brilliant idea of what could possibly be going on here? This used
to work fine in Debian stretch (which has the same version of
python3-sh, so probably no change there).

My best guess so far is something changed in some standard library,
but I really have no idea...

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

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

Versions of packages python3-sh depends on:
ii  python3  3.6.5-3

python3-sh recommends no packages.

python3-sh suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: python-sh
Source-Version: 1.12.14-1.1

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

Debian distribution maintenance software
pp.
Antoine Beaupré  (supplier of updated python-sh package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Tue, 04 Sep 2018 09:04:49 -0400
Source: python-sh
Binary: python-sh python3-sh
Architecture: source
Version: 1.12.14-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Antoine Beaupré 
Description:
 python-sh  - Python subprocess interface
 python3-sh - Python 3 subprocess interface
Closes: 907370
Changes:
 python-sh (1.12.14-1.1) unstable; urgency=medium
 .
   [ Antoine Beaupré ]
   * Non-maintainer upload
   * New upstream version 1.12.14 (Closes: #907370)
 .
   [ Ondřej Nový ]
   * Fixed VCS URL (https)
   * d/control: Set Vcs-* to salsa.debian.org
   * d/copyright: Fix Format URL to correct one
   * d/watch: Use https protocol
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
   * Convert git repository from git-dpm to gbp layout
Checksums-Sha1:
 0a945aec99d8f3d11853cacc3ce70cae0dc4e7e8 1799 python-sh_1.12.14-1.1.dsc
 4ba53052560bedc70f8f1cd305c593f8c75f9d10 57288 python-sh_1.12.14.orig.tar.gz
 74eade71871761ec162b906ccb7f88727e5043d3 2596 
python-sh_1.12.14-1.1.debian.tar.xz
 1e73caeed19ef00eb1c84e45815ec30161df835b 6632 
python-sh_1.12.14-1.1_amd64.buildinfo
Checksums-Sha256:
 e3530a4117b85e6473c2d2c29a547832c9c

Bug#908015: marked as done (feedreader FTBFS with libsoup 2.64.0)

[Debian Bug Tracking System]

Your message dated Fri, 14 Sep 2018 17:33:37 +0300
with message-id <20180914143337.GA28645@localhost>
and subject line Re: Bug#908015: feedreader FTBFS with libsoup 2.64.0
has caused the Debian Bug report #908015,
regarding feedreader FTBFS with libsoup 2.64.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.)


-- 
908015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: feedreader
Version: 2.2-1
Severity: serious
Tags: ftbfs

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

...
[94/300] valac -C --vapidir=/build/1st/feedreader-2.2/vapi 
/build/1st/feedreader-2.2/vapi/gd-1.0.vapi 
/build/1st/feedreader-2.2/vapi/libvilistextum.vapi 
/build/1st/feedreader-2.2/vapi/gtkimageview.vapi --pkg posix --pkg goa-1.0 
--pkg libxml-2.0 --pkg libpeas-1.0 --pkg gstreamer-pbutils-1.0 --pkg 
gstreamer-1.0 --pkg webkit2gtk-4.0 --pkg rest-0.7 --pkg libsecret-1 --pkg 
gee-0.8 --pkg sqlite3 --pkg libsoup-2.4 --pkg json-glib-1.0 --pkg gtk+-3.0 
--pkg glib-2.0 --color=always --directory FeedReader@sha --basedir ../ 
--library FeedReader --header FeedReader.h --vapi ../FeedReader.vapi 
--enable-experimental --target-glib 2.50 ../src/FavIcon.vala 
../src/FeedReader.vala ../src/Password.vala ../src/SQLite.vala 
../src/Widgets/AddPopover.vala ../src/Widgets/ArticleRow.vala 
../src/Widgets/ArticleView.vala ../src/Widgets/ArticleViewHeader.vala 
../src/Widgets/ArticleViewLoadProgress.vala 
../src/Widgets/ArticleViewUrlOverlay.vala 
../src/Widgets/BackendInfoPopover.vala ../src/Widgets/CategorieRow.vala 
../src/Widgets/ColorCircle.vala ../src/Widgets/ColorPopover.vala 
../src/Widgets/ColumnView.vala ../src/Widgets/ColumnViewHeader.vala 
../src/Widgets/FeedList.vala ../src/Widgets/FeedListFooter.vala 
../src/Widgets/FeedRow.vala ../src/Widgets/FullscreenButton.vala 
../src/Widgets/FullscreenHeader.vala ../src/Widgets/HoverButton.vala 
../src/Widgets/ImagePopup.vala ../src/Widgets/InAppNotification.vala 
../src/Widgets/InfoBar.vala ../src/Widgets/LoginPage.vala 
../src/Widgets/LoginRow.vala ../src/Widgets/MainWindow.vala 
../src/Widgets/MediaPlayer.vala ../src/Widgets/MediaButton.vala 
../src/Widgets/MediaRow.vala ../src/Widgets/ModeButton.vala 
../src/Widgets/RemovePopover.vala ../src/Widgets/ResetPage.vala 
../src/Widgets/ServiceSettingsPopover.vala ../src/Widgets/ShareRow.vala 
../src/Widgets/ShortcutsWindow.vala ../src/Widgets/ServiceInfo.vala 
../src/Widgets/Setting.vala ../src/Widgets/SettingsDialog.vala 
../src/Widgets/SharePopover.vala ../src/Widgets/SimpleHeader.vala 
../src/Widgets/SpringCleanPage.vala ../src/Widgets/TagRow.vala 
../src/Widgets/TagPopover.vala ../src/Widgets/TagPopoverRow.vala 
../src/Widgets/UpdateButton.vala ../src/Widgets/WebLoginPage.vala 
../src/Widgets/ArticleList/ArticleList.vala 
../src/Widgets/ArticleList/ArticleListBox.vala 
../src/Widgets/ArticleList/ArticleListEmptyLabel.vala 
../src/Widgets/ArticleList/ArticleListScroll.vala ../src/Share/share.vala 
../src/Share/ServiceSetup.vala ../src/Share/ShareAccountInterface.vala 
../src/Logger.vala ../src/Enums.vala ../src/FuncUtils.vala 
../src/DataBaseReadOnly.vala ../src/ListUtils.vala ../src/Settings.vala 
../src/StringUtils.vala ../src/Structs.vala ../src/Utils.vala 
../src/QueryBuilder.vala ../src/ContentGrabber/grabberUtils.vala 
../src/ContentGrabber/stringPair.vala ../src/Model/Feed.vala 
../src/Model/Category.vala ../src/Model/Enclosure.vala 
../src/Model/Article.vala ../src/Model/Tag.vala ../src/Model/CachedAction.vala 
../src/Model/InterfaceState.vala ../src/Model/ShareAccount.vala 
../src/ActionCache.vala ../src/Backend/Backend.vala 
../src/DataBaseWriteAccess.vala ../src/Notification.vala 
../src/CachedActionManager.vala ../src/Backend/FeedServer.vala 
../src/Backend/FeedServerInterface.vala ../src/Backend/OPMLparser.vala 
../src/ContentGrabber/grabberConfig.vala ../src/ContentGrabber/grabber.vala 
Constants.vala libraries/libIvy/ivy.vapi
FAILED: FeedReader@sha/src/FavIcon.c FeedReader@sha/src/FeedReader.c 
FeedReader@sha/src/Password.c FeedReader@sha/src/SQLite.c 
FeedReader@sha/src/Widgets/AddPopover.c FeedReader@sha/src/Widgets/ArticleRow.c 
FeedReader@sha/src/Widgets/ArticleView.c 
FeedReader@sha/src/Widgets/ArticleViewHeader.c 
FeedReader@sha/src/Widgets/ArticleViewLoadProgress.c 
FeedReader@sha/src/Widgets/ArticleViewUrlOverlay.c 
FeedReader@sha/src/Widgets/BackendInfoPopover.c 
FeedReader@sha/src/Widgets/CategorieRow.c 
FeedReader@sha/src/Widgets/ColorCircle.c 
FeedReader@sha/src/Widgets/ColorPopover.c 
FeedReader@sha/src/Widge

Bug#853310: android-platform-system-core: ftbfs with GCC-7

[Raphael Hertzog]

Hi,

On Thu, 13 Sep 2018, 殷啟聰 | Kai-Chung Yan wrote:
> > It would have helped if you had given me the URL of the repository.
> > Anyway, I'm willing to sponsor the update (even though I don't know much
> > about Android Tools) but I have a few comments:
> 
> Thank you for the sponsor, it will help us a lot!
>
> The repository is at
> .
> Sorry about that, I thought it was too trivial.

It's not hard but I did not know the name of the team on salsa and there
are many packages in the team and the Vcs-Git in the current source
package was obviously outdated. :)

Anyway, I sponsored this upload targetting experimental.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

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


signature.asc
Description: PGP signature

Processed: Re: Bug#908824: libnet-server-mail-perl FTBFS: t/starttls.t failure

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + unreproducible
Bug #908824 [src:libnet-server-mail-perl] libnet-server-mail-perl FTBFS: 
t/starttls.t failure
Added tag(s) unreproducible.

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

Bug#908824: libnet-server-mail-perl FTBFS: t/starttls.t failure

[gregor herrmann]

Control: tag -1 + unreproducible

On Fri, 14 Sep 2018 16:52:38 +0300, Adrian Bunk wrote:

> Source: libnet-server-mail-perl
> Version: 0.25-1
> Severity: serious
> Tags: ftbfs
> 
> https://buildd.debian.org/status/fetch.php?pkg=libnet-server-mail-perl&arch=all&ver=0.25-1&stamp=1536904015&raw=0

Thanks for the bug report.
 
> ...
> Test Summary Report
> ---
> t/starttls.t (Wstat: 9 Tests: 3 Failed: 0)
>   Non-zero wait status: 9
>   Parse errors: No plan found in TAP output
> Files=4, Tests=33,  2 wallclock secs ( 0.05 usr  0.04 sys +  0.67 cusr  0.20 
> csys =  0.96 CPU)
> Result: FAIL
> Failed 1/4 test programs. 0/33 subtests failed.
> make[1]: *** [Makefile:861: test_dynamic] Error 255

Hm, the package builds for me.


The buildd failure is:

# Error: TLS handshake failed SSL connect attempt failed at t/starttls.t line 
116.
# kill 9, 17145 (server)
t/starttls.t .. 
ok 1 - Accepted client for Test01: STARTTLS support
ok 2 - Accepted client for Test02: STARTTLS invalid parameters
ok 3 - Accepted client for Test03: STARTTLS handshake
All 3 subtests passed 


Line 116 in the test is:

   112  my $rv =
   113IO::Socket::SSL->start_SSL( $s,
   114  SSL_verify_mode => IO::Socket::SSL::SSL_VERIFY_NONE, );
   115  
   116  ( defined $rv && ref $rv eq 'IO::Socket::SSL' )
   117or die "TLS handshake failed " . IO::Socket::SSL::errstr();



Cheers,
gregor

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


signature.asc
Description: Digital Signature

Processed: Re: Bug#906472: horst: FTBFS in buster/sid (unable to open 'stdarg.h')

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 sparse 0.5.2-1
Bug #906472 [src:horst] horst: FTBFS in buster/sid (unable to open 'stdarg.h')
Bug reassigned from package 'src:horst' to 'sparse'.
No longer marked as found in versions horst/5.0-2.
Ignoring request to alter fixed versions of bug #906472 to the same values 
previously set
Bug #906472 [sparse] horst: FTBFS in buster/sid (unable to open 'stdarg.h')
Marked as found in versions sparse/0.5.2-1.
> affects -1 src:horst
Bug #906472 [sparse] horst: FTBFS in buster/sid (unable to open 'stdarg.h')
Added indication that 906472 affects src:horst

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

Bug#906472: horst: FTBFS in buster/sid (unable to open 'stdarg.h')

[Adrian Bunk]

Control: reassign -1 sparse 0.5.2-1
Control: affects -1 src:horst

On Sat, Aug 25, 2018 at 10:09:47PM +0200, Christoph Biedl wrote:
> Santiago Vila wrote...
> 
> > make -j1 check
> > make[1]: Entering directory '/<>'
> > sparse -g -O2 -fdebug-prefix-map=/<>=. 
> > -fstack-protector-strong -Wformat -Werror=format-security -std=gnu99 -Wall 
> > -Wextra -g -I. -DDO_DEBUG -I/usr/include/libnl3 *.[ch]
> > /usr/include/err.h:25:11: error: unable to open 'stdarg.h'
> 
> To reproduce this it's important to remove gcc-7 from the build chroot
> (apt purge libgcc-7-dev ; apt --purge autoremove).
> 
> Problem is, sparse appearently uses hardcoded paths and looks for
> stdarg.h in (among other places)
> 
> | /usr/lib/gcc/x86_64-linux-gnu/7//include/stdarg.h
> |   ^
> 
> ... which fails.
> 
> Solution is to rebuild sparse, building horst was successful then.
> If this is true (please check!), the interesting question is why this
> wasn't a problem in earlier gcc version bumps.

Thanks for the analysis, reassigning to sparse.

> Christoph

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#908824: libnet-server-mail-perl FTBFS: t/starttls.t failure

[Adrian Bunk]

Source: libnet-server-mail-perl
Version: 0.25-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=libnet-server-mail-perl&arch=all&ver=0.25-1&stamp=1536904015&raw=0

...
Test Summary Report
---
t/starttls.t (Wstat: 9 Tests: 3 Failed: 0)
  Non-zero wait status: 9
  Parse errors: No plan found in TAP output
Files=4, Tests=33,  2 wallclock secs ( 0.05 usr  0.04 sys +  0.67 cusr  0.20 
csys =  0.96 CPU)
Result: FAIL
Failed 1/4 test programs. 0/33 subtests failed.
make[1]: *** [Makefile:861: test_dynamic] Error 255

Bug#906461: florence: diff for NMU version 0.6.3-1.1

[Adrian Bunk]

Control: tags 906461 + pending

Dear maintainer,

I've prepared an NMU for florence (versioned as 0.6.3-1.1) and uploaded 
it to DELAYED/14. Please feel free to tell me if I should cancel it.

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

diff -Nru florence-0.6.3/debian/changelog florence-0.6.3/debian/changelog
--- florence-0.6.3/debian/changelog	2014-11-07 13:24:29.0 +0200
+++ florence-0.6.3/debian/changelog	2018-09-14 16:45:57.0 +0300
@@ -1,3 +1,10 @@
+florence (0.6.3-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix the Makefile dependencies. (Closes: #906461)
+
+ -- Adrian Bunk   Fri, 14 Sep 2018 16:45:57 +0300
+
 florence (0.6.3-1) unstable; urgency=medium
 
   * New upstream release. (Closes: #764455)
diff -Nru florence-0.6.3/debian/patches/makefile-dependencies.patch florence-0.6.3/debian/patches/makefile-dependencies.patch
--- florence-0.6.3/debian/patches/makefile-dependencies.patch	1970-01-01 02:00:00.0 +0200
+++ florence-0.6.3/debian/patches/makefile-dependencies.patch	2018-08-18 01:25:51.0 +0300
@@ -0,0 +1,15 @@
+Description: Fix the Makefile dependencies
+Author: Adrian Bunk 
+Bug-Debian: https://bugs.debian.org/906461
+
+--- florence-0.6.3.orig/src/Makefile.am
 florence-0.6.3/src/Makefile.am
+@@ -16,7 +16,7 @@ florence_CPPFLAGS = -I$(top_srcdir) -DIC
+-DDATADIR="\"$(datadir)/florence\"" $(DEPS_CFLAGS) $(GTK3_CFLAGS)\
+$(LIBGNOME_CFLAGS) $(LIBNOTIFY_CFLAGS) $(XTST_CFLAGS) $(AT_SPI2_CFLAGS) $(INCLUDES)
+ florence_LDADD = $(DEPS_LIBS) $(LIBM) $(X11_LIBS) $(LIBGNOME_LIBS) $(LIBNOTIFY_LIBS)\
+-   $(XTST_LIBS) $(AT_SPI2_LIBS) $(GTK3_LIBS) -lflorence-1.0
++   $(XTST_LIBS) $(AT_SPI2_LIBS) $(GTK3_LIBS) libflorence-1.0.la
+ 
+ libflorence_1_0_la_SOURCES = lib/florence.c
+ library_includedir=$(includedir)/florence-1.0
diff -Nru florence-0.6.3/debian/patches/series florence-0.6.3/debian/patches/series
--- florence-0.6.3/debian/patches/series	2014-11-07 13:24:23.0 +0200
+++ florence-0.6.3/debian/patches/series	2018-08-18 01:25:22.0 +0300
@@ -1,2 +1,3 @@
 0001-Add-nonet-option-to-xmllint-and-xsltproc-calls.patch
 0002-Add-missing-links-on-libflorence.patch
+makefile-dependencies.patch

Processed: florence: diff for NMU version 0.6.3-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 906461 + pending
Bug #906461 [src:florence] florence: FTBFS in buster/sid (ld: cannot find 
-lflorence-1.0)
Added tag(s) pending.

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

Bug#908820: pcl FTBFS on some 32bit architectures: virtual memory exhausted

[Adrian Bunk]

Source: pcl
Version: 1.8.1+dfsg1-4
Severity: serious
Tags: ftbfs patch

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

...
[ 41%] Built target pcl_openni_fast_mesh
virtual memory exhausted: Cannot allocate memory
make[3]: *** 
[sample_consensus/CMakeFiles/pcl_sample_consensus.dir/build.make:118: 
sample_consensus/CMakeFiles/pcl_sample_consensus.dir/src/sac_model_cone.cpp.o] 
Error 1


Note that the regression is actually not in pcl,
but gcc using more money.

The following addresses this by reducing the amount
of debug information when building for 32bit architectures:

--- debian/rules.old2018-09-13 18:24:33.134097776 +
+++ debian/rules2018-09-13 18:25:23.897428251 +
@@ -11,9 +11,8 @@
 CFLAGS+=$(CPPFLAGS)
 CXXFLAGS+=$(CPPFLAGS)
 
-DEB_BUILD_ARCH ?= $(shell dpkg-architecture -qDEB_BUILD_ARCH)
-ifneq (,$(filter $(DEB_BUILD_ARCH),mips mipsel))
-   CXXFLAGS+=--param ggc-min-expand=20
+ifeq (32,$(DEB_HOST_ARCH_BITS))
+   CXXFLAGS+=-g1
 endif
 
 ifeq ($(shell dpkg-vendor --derives-from Ubuntu && echo yes),yes)

Processed: Re: Bug#908136: src:h2o: FTBFS on amd64

[Debian Bug Tracking System]

Processing control commands:

> tags -1 confirmed upstream
Bug #908136 [src:h2o] src:h2o: FTBFS on amd64
Added tag(s) upstream and confirmed.

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

Bug#908136: src:h2o: FTBFS on amd64

[Apollon Oikonomopoulos]

Control: tags -1 confirmed upstream

Hi,

On 15:42 Thu 06 Sep , Chris Hofstaedtler wrote:
> Package: src:h2o
> Version: 2.2.5+dfsg1-6
> Severity: serious
> 
> Dear Maintainer,
> 
> when trying to build h2o from source on amd64, inside sbuild, it fails:
> 
> h2o server (pid:14780) is ready to serve requests
> fetch-ocsp-response (using OpenSSL 1.1.1-pre9 (beta) 21 Aug 2018)
> failed to extract ocsp URI from examples/h2o/server.crt
> [OCSP Stapling] disabled for certificate file:examples/h2o/server.crt
> 
> #   Failed test at t/50reverse-proxy-session-resumption.t line 118.
> #  got: '0'
> # expected: '1'
> killing /<>/obj-x86_64-linux-gnu/h2o... received SIGTERM, 
> gracefully shutting down
> killed (got 0)
> killing /<>/obj-x86_64-linux-gnu/h2o... received SIGTERM, 
> gracefully shutting down
> killed (got 0)
> # Looks like you failed 1 test of 5.
> 
> #   Failed test 'lifetime'
> #   at t/50reverse-proxy-session-resumption.t line 121.
> 
> And further failures.
> Please also see the attached build log.

Thanks for the report! It looks like the tests in t/50access-log.t and 
t/40ssl-cipher-suite.t are failing when h2o is built against OpenSSL 
1.1.1, because they don't expect OpenSSL to support TLSv1.3 and are 
confused by TLSv1.3-related output (mostly cipher names).

The tests in t/50reverse-proxy-proxy-protocol.t and t/40session-ticket.t 
report no session reuse with OpenSSL 1.1.1 and need further 
investigation.

That said, I intend to move away from PicoTLS and towards OpenSSL for 
TLSv1.3 support in H2O if it works hassle-free.

Cheers,
Apollon

Bug#907493: Timeout in autopkgtest also in Ubuntu Cosmic with Ghostscript 9.24

[Till Kamppeter]

An update:

On Ubuntu the timeouts in the CUPS autopkgtest do not happen any more 
with Ghostscript 9.25 which got released yesterday and is highly 
recommended by upstream to fix the regressions in 9.24.


   Till

Bug#906337: Any clue how to circumvent issues with MPI on autobuilders

[Andreas Tille]

Control: tags -1 pending

On Fri, Sep 14, 2018 at 10:33:28AM +0200, Johannes Ring wrote:
> 
> In debian/rules in dolfin, we use the following to allow test programs to
> run with OpenMPI:
> 
>   export OMPI_MCA_plm_rsh_agent=/bin/false
> 
> Maybe that will fix your problem.

This is set in bioperl-run.  Meanwhile I've found out that the issue is
caused by the phyml test and recently Graham added

export OMPI_MCA_rmaps_base_oversubscribe=1

which here solved the problem as well.

Thanks for the hint anyway

  Andreas.

-- 
http://fam-tille.de

Processed: Re: Any clue how to circumvent issues with MPI on autobuilders

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #906337 [src:bioperl-run] bioperl-run: FTBFS in buster/sid (autobuilder 
hangs)
Added tag(s) pending.

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

Processed: Re: Bug#908800: nautilus: can't use nautilus without tracker

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libtracker-sparql-2.0-0 2.1.4-1
Bug #908800 [nautilus] nautilus: can't use nautilus without tracker
Bug reassigned from package 'nautilus' to 'libtracker-sparql-2.0-0'.
No longer marked as found in versions nautilus/3.30.0-4.
Ignoring request to alter fixed versions of bug #908800 to the same values 
previously set
Bug #908800 [libtracker-sparql-2.0-0] nautilus: can't use nautilus without 
tracker
Marked as found in versions tracker/2.1.4-1.
> tags -1 -pending
Bug #908800 [libtracker-sparql-2.0-0] nautilus: can't use nautilus without 
tracker
Removed tag(s) pending.
> affects -1 brasero nautilus
Bug #908800 [libtracker-sparql-2.0-0] nautilus: can't use nautilus without 
tracker
Added indication that 908800 affects brasero and nautilus

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

Bug#908800: nautilus: can't use nautilus without tracker

[Jeremy Bicha]

Control: reassign -1 libtracker-sparql-2.0-0 2.1.4-1
Control: tags -1 -pending
Control: affects -1 brasero nautilus

On Fri, Sep 14, 2018 at 12:30 AM Youhei SASAKI  wrote:
>   (nautilus:8): Tracker-ERROR **: 13:24:19.460: Unable to find default 
> domain ontology rule /usr/share/tracker/domain-ontologies/default.rule

I cannot duplicate this bug with tracker 2.0.3-3.

I can duplicate this bug when I try to run either brasero or nautilus
with libtracker-sparql-2.0-0 upgraded to 2.1.4-1. Therefore, this is a
bug in the tracker libraries. They need to either depend on tracker or
at least that file or there is a bug where those libraries shouldn't
crash the app if that file can't be found.

There are several key features in nautilus that depend on tracker and
the UI doesn't handle tracker not being installed. The nautilus
developers consider tracker to be mandatory so I think we'll also add
Depends: tracker to nautilus.

Thanks,
Jeremy Bicha

Bug#908568: nvidia-driver: build error

[Vincent Lefevre]

On 2018-09-14 13:15:07 +0200, Andreas Beckmann wrote:
> On 2018-09-12 10:18, Vincent Lefevre wrote:
> > On 2018-09-11 19:15:25 -0700, Russ Allbery wrote:
> >> If you set IGNORE_CC_MISMATCH=1 in the environment before installing the
> >> package, does everything build and work correctly?
> > 
> > Yes, everything is fine.
> 
> It is probably very fragile. When upgrading from stretch/gcc-6 to 
> sid/gcc-6 the whole toolchain gets updated, too (binutils ...).
> 
> I have (for an older stretch kernel and cannot reboot to the current 
> one, but that should not matter) for 396.45 two modules - one built in a 
> mixed sid environment, unloadable, and a working one built in clean 
> stretch.
[...]

And indeed, these problems do not seem to come from a different
GCC version, but from different binutils. Note that between what
was used to build the kernel and what was used to build the modules,
it is possible to have matching GCC versions but different binutils
versions, and conversely. Thus for the binutils issue, testing the
GCC version is the wrong test. It may happen that differing GCC
versions means different binutils versions with an up-to-date sid,
but this is not guaranteed.

Note that according to the Debian changelog:

linux (4.14~rc5-1~exp1) experimental; urgency=medium
[...]
  * Compile with gcc-7 on all architectures
[...]
 -- Ben Hutchings   Tue, 17 Oct 2017 23:37:52 +0100

and to unstable on 30 Nov 2017. At that time, it was GCC 7.2.

GCC 7.3 appeared on 23 Jan 2018. So, after this upgrade, the build
of the NVIDIA kernels module would be refused due to mismatch GCC
versions, until the release of the next kernel on 14 Feb 2018 (and
previous kernels would no longer be usable as a fallback). There
were no issues because at that time, __GNUC_MINOR__ was ignored,
as you should know:

nvidia-graphics-drivers (352.79-8) unstable; urgency=medium

  [ Andreas Beckmann ]
  * cc_version_check-gcc5.patch: New, ignore __GNUC_MINOR__ mismatch from
GCC 5 onwards.
[...]
 -- Andreas Beckmann   Tue, 07 Jun 2016 01:49:35 +0200

which is what you removed in the latest version:

nvidia-graphics-drivers (390.87-1) unstable; urgency=medium
[...]
  [ Andreas Beckmann ]
  * Remove cc_version_check-gcc5.patch and re-enable strict version checks,
using mismatching compiler versions may create unloadable modules due to
mismatching symvers.
[...]
 -- Andreas Beckmann   Mon, 10 Sep 2018 15:24:08 +0200

This doesn't even solve the real issue, since if the modules are
not built, they cannot be loaded anyway. Thus this is not really
useful. Users should just be aware that when there is a major
change in binutils, things may break. :(

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#907460: kdepim-runtime: /usr/bin/akonadi_imap_resource keeps crashing preventing kmail to work

[Nicos Gollan]

On Wednesday, 12 September 2018 11:30:39 CEST Nicos Gollan wrote:
> I'm seeing the same problem with version 17.12.3-2 (tracking
> testing/unstable). The akonadi_imap_resource shows in akonadiconsole with
> many connection tasks and creates a lot of aborted connection attempts
> (sockets in TIME_WAIT) while thrashing wildly. There is no useful logging
> anywhere.

IMAP access is working again after this update:

Start-Date: 2018-09-14  11:40:19
Commandline: apt dist-upgrade
Requested-By: ngollan (1000)
Upgrade: libmpx2:amd64 (8.2.0-5, 8.2.0-6),
 qtbase5-dev-tools:amd64 (5.11.1+dfsg-7, 5.11.1+dfsg-8),
 libqt5test5:amd64 (5.11.1+dfsg-7, 5.11.1+dfsg-8),
 libobjc-8-dev:amd64 (8.2.0-5, 8.2.0-6),
 openafs-krb5:amd64 (1.8.1-1, 1.8.2-1),
 qt5-gtk-platformtheme:amd64 (5.11.1+dfsg-7, 5.11.1+dfsg-8),
 lib32stdc++6:amd64 (8.2.0-5, 8.2.0-6),
 libqt5opengl5-dev:amd64 (5.11.1+dfsg-7, 5.11.1+dfsg-8),
 libobjc4:amd64 (8.2.0-5, 8.2.0-6),
 cpp-8:amd64 (8.2.0-5, 8.2.0-6),
 cantor-backend-kalgebra:amd64 (4:17.08.3-1+b1, 4:18.08.1-1),
 gcc-8-base:amd64 (8.2.0-5, 8.2.0-6),
 gcc-8-base:i386 (8.2.0-5, 8.2.0-6),
 qt5-default:amd64 (5.11.1+dfsg-7, 5.11.1+dfsg-8),
 libitm1:amd64 (8.2.0-5, 8.2.0-6),
 libqt5dbus5:amd64 (5.11.1+dfsg-7, 5.11.1+dfsg-8),
 libqt5sql5-sqlite:amd64 (5.11.1+dfsg-7, 5.11.1+dfsg-8),
 libnuma1:amd64 (2.0.11-2.2, 2.0.12-1),
 krosspython:amd64 (4:17.08.3-1+b1, 4:18.08.1-1),
 libgtksourceview-3.0-common:amd64 (3.24.8-1, 3.24.9-1),
 libqt5widgets5:amd64 (5.11.1+dfsg-7, 5.11.1+dfsg-8),
 libasan5:amd64 (8.2.0-5, 8.2.0-6),
 network-manager-gnome:amd64 (1.8.16-1, 1.8.18-1),
 libquadmath0:amd64 (8.2.0-5, 8.2.0-6),
 kio-extras:amd64 (4:17.08.3-2+b1, 4:18.08.1-1),
 juk:amd64 (4:18.04.0-1, 4:18.08.1-1),
 libqt5xml5:amd64 (5.11.1+dfsg-7, 5.11.1+dfsg-8),
 libqt5printsupport5:amd64 (5.11.1+dfsg-7, 5.11.1+dfsg-8),
 libgcc1:amd64 (1:8.2.0-5, 1:8.2.0-6),
 libgcc1:i386 (1:8.2.0-5, 1:8.2.0-6),
 libqt5concurrent5:amd64 (5.11.1+dfsg-7, 5.11.1+dfsg-8),
 lib32gcc1:amd64 (1:8.2.0-5, 1:8.2.0-6),
 libinput-bin:amd64 (1.11.3-1, 1.12.0-1),
 libgcc-8-dev:amd64 (8.2.0-5, 8.2.0-6),
 libqt5gui5:amd64 (5.11.1+dfsg-7, 5.11.1+dfsg-8),
 libtsan0:amd64 (8.2.0-5, 8.2.0-6),
 libubsan1:amd64 (8.2.0-5, 8.2.0-6),
 g++-8:amd64 (8.2.0-5, 8.2.0-6),
 gir1.2-gtksource-3.0:amd64 (3.24.8-1, 3.24.9-1),
 aptitude-common:amd64 (0.8.10-9, 0.8.11-3),
 qt5-qmake:amd64 (5.11.1+dfsg-7, 5.11.1+dfsg-8),
 libgfortran5:amd64 (8.2.0-5, 8.2.0-6),
 gcc-8:amd64 (8.2.0-5, 8.2.0-6),
 lintian:amd64 (2.5.101, 2.5.102),
 libnma0:amd64 (1.8.16-1, 1.8.18-1),
 liblsan0:amd64 (8.2.0-5, 8.2.0-6),
 libgomp1:amd64 (8.2.0-5, 8.2.0-6),
 libqt5core5a:amd64 (5.11.1+dfsg-7, 5.11.1+dfsg-8),
 cantor-backend-qalculate:amd64 (4:17.08.3-1+b1, 4:18.08.1-1),
 emacsen-common:amd64 (3.0.2, 3.0.3),
 libfftw3-long3:amd64 (3.3.8-1, 3.3.8-2),
 libdb5.3:amd64 (5.3.28+dfsg1-0.1, 5.3.28+dfsg1-0.2),
 libgtksourceview-3.0-1:amd64 (3.24.8-1, 3.24.9-1),
 qtbase5-dev:amd64 (5.11.1+dfsg-7, 5.11.1+dfsg-8),
 libfftw3-double3:amd64 (3.3.8-1, 3.3.8-2),
 cantor:amd64 (4:17.08.3-1+b1, 4:18.08.1-1),
 libqt5opengl5:amd64 (5.11.1+dfsg-7, 5.11.1+dfsg-8),
 code:amd64 (1.27.1-1536226049, 1.27.2-1536736588),
 libnss3:amd64 (2:3.38-1, 2:3.39-1),
 libatomic1:amd64 (8.2.0-5, 8.2.0-6),
 kio-extras-data:amd64 (4:17.08.3-2, 4:18.08.1-1),
 libqt5network5:amd64 (5.11.1+dfsg-7, 5.11.1+dfsg-8),
 libcc1-0:amd64 (8.2.0-5, 8.2.0-6),
 libstdc++6:amd64 (8.2.0-5, 8.2.0-6),
 libstdc++6:i386 (8.2.0-5, 8.2.0-6),
 aptitude:amd64 (0.8.10-9, 0.8.11-3),
 qt5-qmake-bin:amd64 (5.11.1+dfsg-7, 5.11.1+dfsg-8),
 libnspr4:amd64 (2:4.19-3, 2:4.20-1),
 libstdc++-8-dev:amd64 (8.2.0-5, 8.2.0-6),
 libqt5sql5:amd64 (5.11.1+dfsg-7, 5.11.1+dfsg-8),
 libinput10:amd64 (1.11.3-1, 1.12.0-1),
 aptitude-doc-en:amd64 (0.8.10-9, 0.8.11-3),
 libfftw3-single3:amd64 (3.3.8-1, 3.3.8-2),
 libqt5sql5-mysql:amd64 (5.11.1+dfsg-7, 5.11.1+dfsg-8)
End-Date: 2018-09-14  11:42:01

Processed: Bug #908800 in nautilus marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #908800 [nautilus] nautilus: can't use nautilus without tracker
Added tag(s) pending.

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

Bug#908800: Bug #908800 in nautilus marked as pending

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #908800 in nautilus 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/gnome-team/nautilus/commit/852c9614e51b0746fa3e5fe3d9bd4217091d17e7


Depend on tracker instead of Suggests. It is no longer optional.

Closes: #908800



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/908800

Processed: severity of 908815 is serious

[Debian Bug Tracking System]

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

> severity 908815 serious
Bug #908815 [libdmtx0a] [libdmtx0a] Structs in dmtx.h have changed without new 
ABI number
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#908568: nvidia-driver: build error

[Andreas Beckmann]

On 2018-09-12 10:18, Vincent Lefevre wrote:
> On 2018-09-11 19:15:25 -0700, Russ Allbery wrote:
>> If you set IGNORE_CC_MISMATCH=1 in the environment before installing the
>> package, does everything build and work correctly?
> 
> Yes, everything is fine.

It is probably very fragile. When upgrading from stretch/gcc-6 to 
sid/gcc-6 the whole toolchain gets updated, too (binutils ...).

I have (for an older stretch kernel and cannot reboot to the current 
one, but that should not matter) for 396.45 two modules - one built in a 
mixed sid environment, unloadable, and a working one built in clean 
stretch.


# insmod ./sid/lib/modules/4.9.0-6-amd64/nvidia/nvidia-current.ko
insmod: ERROR: could not insert module 
./sid/lib/modules/4.9.0-6-amd64/nvidia/nvidia-current.ko: Invalid module format

# dmesg | tail -n 1
[12261789.197235] module: nvidia: Unknown rela relocation: 4

# insmod ./stretch/lib/modules/4.9.0-6-amd64/nvidia/nvidia-current.ko

# dmesg | tail -n 3
[12261835.731804] nvidia-nvlink: Nvlink Core is being initialized, major device 
number 245
[12261835.732157] vgaarb: device changed decodes: 
PCI::01:00.0,olddecodes=none,decodes=none:owns=io+mem
[12261835.732275] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  396.45  Thu 
Jul 12 20:49:29 PDT 2018 (using threaded interrupts)

Looking with diffoscope at the modules I find this interesting
difference:

│ -Relocation section '.rela.text' at offset 0x122def8 contains 138066 entries:
│ +Relocation section '.rela.text' at offset 0x122de38 contains 138066 entries:
│  Offset Info Type   Symbol's Value  
Symbol's Name + Addend
│ -0001  8fdb0002 R_X86_64_PC32   
__fentry__ - 4
│ +0001  8fdb0004 R_X86_64_PLT32  
__fentry__ - 4
│  0015  8f76000b R_X86_64_32S    
nv_minor_num_table + 0
│ -0028  8fed0002 R_X86_64_PC32   
__x86_indirect_thunk_rax - 4
│ -0031  8fdb0002 R_X86_64_PC32   
__fentry__ - 4
│ +0028  8fed0004 R_X86_64_PLT32  
__x86_indirect_thunk_rax - 4
│ +0031  8fdb0004 R_X86_64_PLT32  
__fentry__ - 4
│  0048  8f76000b R_X86_64_32S    
nv_minor_num_table + 0
│ -006a  919e0002 R_X86_64_PC32   
__x86_indirect_thunk_r9 - 4
│ -0081  8fdb0002 R_X86_64_PC32   
__fentry__ - 4
│ -0091  8fdb0002 R_X86_64_PC32   
__fentry__ - 4
│ +006a  919e0004 R_X86_64_PLT32  
__x86_indirect_thunk_r9 - 4
│ +0081  8fdb0004 R_X86_64_PLT32  
__fentry__ - 4
│ +0091  8fdb0004 R_X86_64_PLT32  
__fentry__ - 4
...

arch/x86/include/asm/elf.h says:
#define R_X86_64_PC32   2   /* PC relative 32 bit signed */
#define R_X86_64_PLT32  4   /* 32 bit PLT address */

The same behavior I see comparing the modules built for current
driver and stretch kernel in different environments, therefore
I conclude that they won't work if built with the mismatching
toolchain (mismatching gcc may be just an indicator for the
mismatching toolchain, using a gcc6 6.4.0 built in stretch might
actually result in working modules).

--- 
nvidia-kernel-4.9.0-8-amd64_390.87-1+4.9.110-3+deb9u4_amd64_gcc-6.3.0-18+deb9u1.deb
+++ nvidia-kernel-4.9.0-8-amd64_390.87-1+4.9.110-3+deb9u4_amd64_gcc-6.4.0-20.deb

-Relocation section '.rela.text' at offset 0x253768 contains 701 entries:
+Relocation section '.rela.text' at offset 0x253708 contains 701 entries:
 Offset Info Type   Symbol's Value  
Symbol's Name + Addend
-0001  00c20002 R_X86_64_PC32   
__fentry__ - 4
+0001  00c20004 R_X86_64_PLT32  
__fentry__ - 4
 0008  000f000b R_X86_64_32S    
.data + 0
-000d  01250002 R_X86_64_PC32   
nvKmsKapiGetFunctionsTable - 4
-0016  00e50002 R_X86_64_PC32  0950 
nv_drm_probe_devices - 4
+000d  01250004 R_X86_64_PLT32  
nvKmsKapiGetFunctionsTable - 4
+0016  00e50004 R_X86_64_PLT32 0950 
nv_drm_probe_devices - 4
...

build test environment:
stretch chroot + linux-headers-amd64 module-assistant nvidia-kernel-source
m-a -t -f -l 4.9.0-8-amd64 build nvidia
add sid sources
apt-get install gcc-6/sid
m-a -t -f -l 4.9.0-8-amd64 build nvidia


Andreas

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 908810 src:pulseaudio
Bug #908810 [libpulse0] libpulse0: can't upgrade pulseaudio packages (version 
misalignment)
Bug reassigned from package 'libpulse0' to 'src:pulseaudio'.
Ignoring request to alter found versions of bug #908810 to the same values 
previously set
Ignoring request to alter fixed versions of bug #908810 to the same values 
previously set
> forcemerge 906504 908810
Bug #906504 [src:pulseaudio] pulseaudio: FTBFS in buster/sid (failing tests)
Bug #908810 [src:pulseaudio] libpulse0: can't upgrade pulseaudio packages 
(version misalignment)
Severity set to 'serious' from 'normal'
Marked as found in versions pulseaudio/12.2-1 and pulseaudio/11.1-5.
Added tag(s) ftbfs, upstream, and patch.
Merged 906504 908810
> affects 906504 libpulse0
Bug #906504 [src:pulseaudio] pulseaudio: FTBFS in buster/sid (failing tests)
Bug #908810 [src:pulseaudio] libpulse0: can't upgrade pulseaudio packages 
(version misalignment)
Added indication that 906504 affects libpulse0
Added indication that 908810 affects libpulse0
> thanks
Stopping processing here.

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

Bug#906978: marked as done (pysmi: FTBFS in buster/sid (failing tests))

[Debian Bug Tracking System]

Your message dated Fri, 14 Sep 2018 10:05:17 +
with message-id 
and subject line Bug#906978: fixed in python-pysnmp4 4.4.6-1
has caused the Debian Bug report #906978,
regarding pysmi: FTBFS in buster/sid (failing tests)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python2,python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
running config
I: pybuild base:217: python3.6 setup.py config 
running config
   dh_auto_build -i -O--buildsystem=pybuild
I: pybuild base:217: /usr/bin/python setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython2_2.7_pysmi/build/pysmi

[... snipped ...]

testTypeDeclarationGauge32ClassTestCase 
(tests.test_typedeclaration_smiv2_pysnmp.TypeDeclarationTestCase) ... ok
testTypeDeclarationGauge32SymbolTestCase 
(tests.test_typedeclaration_smiv2_pysnmp.TypeDeclarationTestCase) ... ok
testTypeDeclarationInteger32ClassTestCase 
(tests.test_typedeclaration_smiv2_pysnmp.TypeDeclarationTestCase) ... ok
testTypeDeclarationInteger32SymbolTestCase 
(tests.test_typedeclaration_smiv2_pysnmp.TypeDeclarationTestCase) ... ok
testTypeDeclarationIpAddressClassTestCase 
(tests.test_typedeclaration_smiv2_pysnmp.TypeDeclarationTestCase) ... ok
testTypeDeclarationIpAddressSymbolTestCase 
(tests.test_typedeclaration_smiv2_pysnmp.TypeDeclarationTestCase) ... ok
testTypeDeclarationObjectIdentifierClassTestCase 
(tests.test_typedeclaration_smiv2_pysnmp.TypeDeclarationTestCase) ... ok
testTypeDeclarationObjectIdentifierSymbolTestCase 
(tests.test_typedeclaration_smiv2_pysnmp.TypeDeclarationTestCase) ... ok
testTypeDeclarationOctetStringClassTestCase 
(tests.test_typedeclaration_smiv2_pysnmp.TypeDeclarationTestCase) ... ok
testTypeDeclarationOctetStringSymbolTestCase 
(tests.test_typedeclaration_smiv2_pysnmp.TypeDeclarationTestCase) ... ok
testTypeDeclarationOpaqueClassTestCase 
(tests.test_typedeclaration_smiv2_pysnmp.TypeDeclarationTestCase) ... ok
testTypeDeclarationOpaqueSymbolTestCase 
(tests.test_typedeclaration_smiv2_pysnmp.TypeDeclarationTestCase) ... ok
testTypeDeclarationTimeTicksClassTestCase 
(tests.test_typedeclaration_smiv2_pysnmp.TypeDeclarationTestCase) ... ok
testTypeDeclarationTimeTicksSymbolTestCase 
(tests.test_typedeclaration_smiv2_pysnmp.TypeDeclarationTestCase) ... ok
testTypeDeclarationUnsigned32ClassTestCase 
(tests.test_typedeclaration_smiv2_pysnmp.TypeDeclarationTestCase) ... ok
testTypeDeclarationUnsigned32SymbolTestCase 
(tests.test_typedeclaration_smiv2_pysnmp.TypeDeclarationTestCase) ... ok

==
ERROR: testObjectTypeSyntax 
(tests.test_objecttype_smiv2_pysnmp.ObjectTypeBitsTestCase)
--
Traceback (most recent call last):
  File "tests/test_objecttype_smiv2_pysnmp.py", line 365, in 
testObjectTypeSyntax
self.ctx['testObjectType'].getSyntax().clone(('set',)), str2octs('@'),
  File "/usr/lib/python2.7/dist-packages/pysnmp/proto/rfc1902.py", line 202, in 
clone
return univ.OctetString.clone(self, *args, 
**kwargs).setFixedLength(self.getFixedLength())
  File "/usr/lib/python2.7/dist-packages/pyasn1/type/base.py", line 349, in 
clone
return self.__class__(value, **initilaizers)
  File "/usr/lib/python2.7/dist-packages/pysnmp/proto/rfc1902.py", line 603, in 
__new__
Bits = cls.withNamedBits(**kwargs.pop('namedValues'))
  File "/usr/lib/python2.7/dist-packages/pysnmp/proto/rfc1902.py", line 642, in 
withNamedBits
class X(cls):
  File "/usr/lib/python2.7/dist-packages/pysnmp/proto/rfc1902.py", line 643, in 
X
namedValues = cls.namedValues + namedval.NamedValues(*values.items())
  File "/usr/lib/python2.7/dist-packages/pyasn1/type/namedval.py", line 166, in 
__add__
return self.__class__(*tuple(self.items()) + tuple(namedValues.items()))
  File "/usr/lib/python2.7/dist-packages/pyasn1/type/namedval.py", line 74, in 
__init__
raise error.PyAsn1Error('Duplicate name %s' % (name,))
PyAsn1Error: Duplicate name notification

Bug#908786: marked as done (mothur-mpi contains the same binary as mothur)

[Debian Bug Tracking System]

Your message dated Fri, 14 Sep 2018 10:04:48 +
with message-id 
and subject line Bug#908786: fixed in mothur 1.40.5-2
has caused the Debian Bug report #908786,
regarding mothur-mpi contains the same binary as mothur
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.)


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

$ sha256sum /usr/bin/mothur*
316ea8bcabce032371788425c98c5da62a353de20a1b6174582cad5a49a06153  
/usr/bin/mothur
316ea8bcabce032371788425c98c5da62a353de20a1b6174582cad5a49a06153  
/usr/bin/mothur-mpi
$ 


USEMPI seems to be no longer an upstream option,
so both builds produce the same binary.
--- End Message ---
--- Begin Message ---
Source: mothur
Source-Version: 1.40.5-2

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated mothur 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, 14 Sep 2018 10:29:24 +0200
Source: mothur
Binary: mothur
Architecture: source amd64
Version: 1.40.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 mothur - sequence analysis suite for research on microbiota
Closes: 908786
Changes:
 mothur (1.40.5-2) unstable; urgency=medium
 .
   * Upstream dropped MPI support since it is slower and requires dual
 maintenance (see README.Debian)  Thus dropping MPI support from
 Debian package
 Closes: #908786
   * Remove Tim Booth from Uploaders (Tim, thanks for your work on this
 package)
   * Drop unneeded get-orig-source target
   * Standards-Version: 4.2.1
Checksums-Sha1:
 1eb60fa3acb73bcddd78fe540839f05272f23ebb 2084 mothur_1.40.5-2.dsc
 ae6379e6f92ba05f95f55ae7aae114f3a89e08b6 19888 mothur_1.40.5-2.debian.tar.xz
 172142d9f3600db04c54bca1a92950a6667fa543 143643522 
mothur-dbgsym_1.40.5-2_amd64.deb
 caa39512ca4552c0a92b29a6be832d93429d9efc 8484 mothur_1.40.5-2_amd64.buildinfo
 4fd6f13aa4cc8d8484329f833d08b4a6cf8457d1 4580974 mothur_1.40.5-2_amd64.deb
Checksums-Sha256:
 2b6a8c9f6da760a421f546be75b0dd50054343e3ee9f1f2589874d3c4277c118 2084 
mothur_1.40.5-2.dsc
 9179a6426b28957327aa3a45c9153b1d623f72807e345a43d5ec82823365bf62 19888 
mothur_1.40.5-2.debian.tar.xz
 7c8107ae965566052fa08fb4634a9ece0713832932c88e56a99f4a43dd4f86d7 143643522 
mothur-dbgsym_1.40.5-2_amd64.deb
 0a701752e118ab0220cc5b3f7a94c0e7e2460b79bfa62576c5d0412155249bde 8484 
mothur_1.40.5-2_amd64.buildinfo
 a0c0eb753d63dd6adb07fe7484946422302d6bf72370ca63a232c4c92991ee39 4580974 
mothur_1.40.5-2_amd64.deb
Files:
 82ebdbe900e9128291d1175dd5ba068d 2084 science optional mothur_1.40.5-2.dsc
 9becd5936f65815bdea02b94c537b751 19888 science optional 
mothur_1.40.5-2.debian.tar.xz
 749427af34496f49776d9abc3c8ae145 143643522 debug optional 
mothur-dbgsym_1.40.5-2_amd64.deb
 61bc6ca73402de2f307a9066c0786552 8484 science optional 
mothur_1.40.5-2_amd64.buildinfo
 21eba9b5e687c3a5ac9ba52273558f24 4580974 science optional 
mothur_1.40.5-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlubgPkRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtG22RAAkIDCNzljbKyDIZ6O6v7ZXUAl5mS5aKJe
lMa5/KbYmu7LNwFsJD2C5xB4p8o4E76GQwW3xKGvLNUrBwDNqd8n9IHkaJt9rnhn
BkN0n0WlpZmIEh/lp7K4YBii2Y/mI43u/GySrntrTcAFVlhjxisiGIK+SLoJyJg0
qJW97FM8JkywYvq8L86NjzdqeSVld28H3Q7Ymd7K5fYAlATdnxr6weelCngQph4z
r4edHtxcuWQUQ5u+SoMUBxrRyDlCqpg67LY/plSK6Bo2FNtCfTNvVPGkeJuhX7Lo
VaM+5km4KgTmwFVZ9cLS9zvCZ4bkiVsehBFYLeZg1VSfEZrU0/UCWdJ9CXMecBNN
TB2qCqXAiWzQOqpP6iDoAl6ZsVts0PiZF5f5siNGTm7pkxfl5kncPfs2FGEYwC8X
IeqldAjO6TT4MbxIx4FVA86aZ2MCCpiBN9JK51ptNFDz235wikFAxlrnYm17dV4E
K/Z4uAz4lnIz4D83yADWAENuvBpQHFwL9R0NIkaOa4xtMa6H4PQWLv/C3DAfmW7O
1ndah+iIHtr6CG8RQVMFb0+GAmQdqf/4m9Ze5ClHzHkXgE3lV9DuPNYqqC9rCg5k
WyAda8fI0rHrus3Kwyu7Yk4n/790GvCV7KrawZn1tHtbKCIa3AvhdZGtTJJ51Bh8
/e+fq5RUULk=
=RP5M
-END PGP SIGNATURE End Message ---

Bug#907432: [pkg-go] Bug#907432: golang-github-cloudflare-redoctober: FTBFS (too many arguments in call to activation.Listeners)

[Arnaud Rebillout]

On 09/14/2018 04:56 PM, Shengjing Zhu wrote:

> And for redoctober, it only has one line using go-systemd, it's
>
> activation.Listeners(true)
>
> From the go-systemd commit comment, they just removed the arg, and
> assume it's default is true.
>

Oh, I didn't notice it was that trivial. Thanks.

Bug#907432: [pkg-go] Bug#907432: golang-github-cloudflare-redoctober: FTBFS (too many arguments in call to activation.Listeners)

[Shengjing Zhu]

On Fri, Sep 14, 2018 at 4:45 PM Arnaud Rebillout
 wrote:
>
> The only reverse dependency for this package is golang-cfssl (also from
> cloudflare).
>
> Upstream never issued a release for redoctober.
>
> Hence we could just assume that redoctober is part of golang-cfssl's
> codebase, keep it embedded in golang-cfssl, and stop packaging it
> separately like we do now.
>
> That would solve the FTBFS, since the part of redoctober that is
> embedded in cfssl doesn't need systemd-go (which is causing the build
> failure mentioned in this bug).
>
> Otherwise we wait for upstream to update its embedded copy of
> systemd-go, but I have no idea how long it will take. Their copy of
> systemd-go is 2 years old. Last commit on redoctober was 6 months ago. I
> don't expect anything to happen anytime soon.
>

For easy bugs, you can always send PR to push upstream,

The bug you mentions with system-go, is caused this upstream commit,
https://github.com/coreos/go-systemd/commit/65cc0ad826177f0ec9f0ee87c1bc5718b0d8ec97#diff-03580c8a576b0bff1bd9c4e7dab211da

And for redoctober, it only has one line using go-systemd, it's

activation.Listeners(true)

>From the go-systemd commit comment, they just removed the arg, and
assume it's default is true.

-- 
Best regards,
Shengjing Zhu

Bug#908459: theseus FTBFS with gcc 8

[Adrian Bunk]

On Fri, Sep 14, 2018 at 10:50:36AM +0200, Fabian Klötzl wrote:
> 
> On 11.09.2018 15:58, Adrian Bunk wrote:
> > Control: reopen -1
> > 
> > Some builds were still running into #897876 due to the buildd chroots
> > only regenerated twice per week (which is not something you should be
> > worried about), but the armhf/i386 and ppc64el FTBFS look more like
> > actual problems that need fixing in theseus.
> 
> Unfortunately, fixing this will take a while longer. I first have to figure
> out how to build an arm vm because I don't want to debug remotely via the
> autobuilds. ☺

i386 looks like the same problem as arm,
  debootstrap --arch=i386 sid i386-sid
would be one way to create a root filesystem for that you can then
chroot into.

> Best,
> Fabian

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#908459: theseus FTBFS with gcc 8

[Fabian Klötzl]

On 11.09.2018 15:58, Adrian Bunk wrote:

Control: reopen -1

Some builds were still running into #897876 due to the buildd chroots
only regenerated twice per week (which is not something you should be
worried about), but the armhf/i386 and ppc64el FTBFS look more like
actual problems that need fixing in theseus.


Unfortunately, fixing this will take a while longer. I first have to 
figure out how to build an arm vm because I don't want to debug remotely 
via the autobuilds. ☺


Best,
Fabian

Bug#908786: mothur-mpi contains the same binary as mothur

[Adrian Bunk]

On Fri, Sep 14, 2018 at 10:33:44AM +0200, Andreas Tille wrote:
> Control: tags -1 pending
> 
> Hi Adrian,

Hi Andreas,

> On Fri, Sep 14, 2018 at 01:39:34AM +0300, Adrian Bunk wrote:
> > USEMPI seems to be no longer an upstream option,
> > so both builds produce the same binary.
> 
> Very good catch!  Thanks for this.  In fact the MPI code was removed
> 2015-08-19 so we ship the non-functional MPI uselessly since about three
> years. :-(

from looking at the source code the package in stable is likely functional.

> I'm about to build a fixed package (just droping mothur-mpi).
> 
> There is no need to fiddle around with severities since it will be fixed
> soon.  I just would like to know your motivation to file the bug as
> serious since I would have done with normal in this case since I can not
> really see what is broken.

There were two reasons:

1. Something is pretty broken, as it turns out the mothur-mpi package
is useless. If in doubt I prefer to err on the RC side since this has
a better chance of someone actually looking at the bug.

2. "apt-get install mothur-dbgsym mothur-mpi-dbgsym" results in an error
from dpkg, the lintian warning for that is how I actually found this bug.

> Kind regards
> 
> Andreas.

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#907432: golang-github-cloudflare-redoctober: FTBFS (too many arguments in call to activation.Listeners)

[Arnaud Rebillout]

The only reverse dependency for this package is golang-cfssl (also from
cloudflare).

Upstream never issued a release for redoctober.

Hence we could just assume that redoctober is part of golang-cfssl's
codebase, keep it embedded in golang-cfssl, and stop packaging it
separately like we do now.

That would solve the FTBFS, since the part of redoctober that is
embedded in cfssl doesn't need systemd-go (which is causing the build
failure mentioned in this bug).

Otherwise we wait for upstream to update its embedded copy of
systemd-go, but I have no idea how long it will take. Their copy of
systemd-go is 2 years old. Last commit on redoctober was 6 months ago. I
don't expect anything to happen anytime soon.

Cheers,

  Arnaud

Processed: Re: Bug#908786: mothur-mpi contains the same binary as mothur

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #908786 [mothur-mpi] mothur-mpi contains the same binary as mothur
Added tag(s) pending.

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

Bug#908786: mothur-mpi contains the same binary as mothur

[Andreas Tille]

Control: tags -1 pending

Hi Adrian,

On Fri, Sep 14, 2018 at 01:39:34AM +0300, Adrian Bunk wrote:
> USEMPI seems to be no longer an upstream option,
> so both builds produce the same binary.

Very good catch!  Thanks for this.  In fact the MPI code was removed
2015-08-19 so we ship the non-functional MPI uselessly since about three
years. :-(

I'm about to build a fixed package (just droping mothur-mpi).

There is no need to fiddle around with severities since it will be fixed
soon.  I just would like to know your motivation to file the bug as
serious since I would have done with normal in this case since I can not
really see what is broken.

Kind regards

Andreas.

-- 
http://fam-tille.de

Bug#906337: Any clue how to circumvent issues with MPI on autobuilders

[Johannes Ring]

On Fri, Sep 14, 2018 at 9:21 AM, Andreas Tille  wrote:

> Control: tags -1 help
>
> Hi,
>
> in the bug log of #906337 the test suite aborts with
>
> ...
> --
> MPI_ABORT was invoked on rank 0 in communicator MPI_COMM_WORLD
> with errorcode 1.
>
> NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
> You may or may not see output from other processes, depending on
> exactly when Open MPI kills them.
> --
> E: Build killed with signal TERM after 60 minutes of inactivity
> 
> 
> ...
>
>
> Since I have no experience with MPI but I know that on Debian Science
> are people with experience hanging around, I take the freedom to ask
> here for help.  I suspect that the test suite assumes some MPI features
> which are not available on any autobuilder machine.  Any idea what to
> do in this case?
>

In debian/rules in dolfin, we use the following to allow test programs to
run with OpenMPI:

  export OMPI_MCA_plm_rsh_agent=/bin/false

Maybe that will fix your problem.

Johannes

Processed: Fixed upstream

[Debian Bug Tracking System]

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

> tags 906400 fixed-upstream patch
Bug #906400 [src:pytest-qt] pytest-qt: FTBFS in buster/sid (failing tests)
Added tag(s) patch and fixed-upstream.
> forwarded 906400 
> https://github.com/pytest-dev/pytest-qt/commit/111e09bf0574e12601432bf7a452719339235460#diff-b94032559ed411057d5b63e05c573e54
Bug #906400 [src:pytest-qt] pytest-qt: FTBFS in buster/sid (failing tests)
Set Bug forwarded-to-address to 
'https://github.com/pytest-dev/pytest-qt/commit/111e09bf0574e12601432bf7a452719339235460#diff-b94032559ed411057d5b63e05c573e54'.
> thanks
Stopping processing here.

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

Processed: Issues possibly due to new pandas version

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #906419 [src:lmfit-py] lmfit-py: FTBFS: test failure
Added tag(s) help.

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

Bug#906381: Issues possibly due to new pandas version

[Andreas Tille]

Control: tags -1 help

Hi,

I tried my luck by injecting the latest upstream version.  This needs a
new dependency python-asteval (#907283, just uploaded to new queue).
Unfortunately this does not help at all and we surely should contact
upstream about this and so it is better to refer to the latest upstream.

Frédéric, can you confirm that you have contact to upstream and will
care for this issue?

Kind regards

   Andreas.

-- 
http://fam-tille.de