Bug#902519: marked as done (radio-beam: FTBFS in buster/sid (failing tests))

[Debian Bug Tracking System]

Your message dated Mon, 06 Aug 2018 06:48:53 +
with message-id 
and subject line Bug#902519: fixed in radio-beam 0.2-2
has caused the Debian Bug report #902519,
regarding radio-beam: 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.)


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

Dear maintainer:

I tried to build this package in buster with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with python2,python3 --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py config 
/usr/lib/python2.7/dist-packages/astropy_helpers/setup_helpers.py:102: 
AstropyDeprecationWarning: Direct use of the adjust_compiler function in 
setup.py is deprecated and can be removed from your setup.py.  This 
functionality is now incorporated directly into the build_ext command.
  'command.', AstropyDeprecationWarning)
running config
I: pybuild base:217: python3.6 setup.py config 
running config
/usr/lib/python3/dist-packages/astropy_helpers/setup_helpers.py:90: 
AstropyDeprecationWarning: Direct use of the adjust_compiler function in 
setup.py is deprecated and can be removed from your setup.py.  This 
functionality is now incorporated directly into the build_ext command.
  'command.', AstropyDeprecationWarning)
   dh_auto_build -i -O--buildsystem=pybuild

[... snipped ...]

radio_beam/tests/test_beams.py::test_beams_from_fits_bintable PASSED [ 94%]
radio_beam/tests/test_beams.py::test_indexing PASSED [ 94%]
radio_beam/tests/test_beams.py::test_average_beams PASSED[ 95%]
radio_beam/tests/test_beams.py::test_largest_beams[beams0-majors0-minors0-pas0] 
PASSED [ 95%]
radio_beam/tests/test_beams.py::test_largest_beams[beams1-majors1-minors1-pas1] 
PASSED [ 95%]
radio_beam/tests/test_beams.py::test_smallest_beams[beams0-majors0-minors0-pas0]
 PASSED [ 96%]
radio_beam/tests/test_beams.py::test_smallest_beams[beams1-majors1-minors1-pas1]
 PASSED [ 96%]
radio_beam/tests/test_beams.py::test_extrema_beams[beams0-majors0-minors0-pas0] 
PASSED [ 97%]
radio_beam/tests/test_beams.py::test_extrema_beams[beams1-majors1-minors1-pas1] 
PASSED [ 97%]
radio_beam/tests/test_beams.py::test_beams_with_invalid[majors0] PASSED  [ 97%]
radio_beam/tests/test_beams.py::test_beams_with_invalid[majors1] PASSED  [ 98%]
radio_beam/tests/test_beams.py::test_beams_iter PASSED   [ 98%]
radio_beam/tests/test_kernels.py::test_gauss_kernel PASSED   [ 99%]
radio_beam/tests/test_kernels.py::test_tophat_kernel PASSED  [ 99%]
docs/index.rst FAILED[100%]

=== FAILURES ===
___ [doctest] docs/index.rst ___
020 
021 Create a beam from scratch::
022 
023 >>> from astropy import units as u
024 >>> my_beam = Beam(0.5*u.arcsec)
025 
026 
027 Use a beam for Jy -> K conversion::
028 
029 >>> (1*u.Jy).to(u.K, u.brightness_temperature(my_beam, 25*u.GHz))
Expected:

Got:


/tmp/radio_beam-test-9fxEB_/lib/python2.7/site-packages/docs/index.rst:29: 
DocTestFailure
=== warnings summary ===
None
  [pytest] section in setup.cfg files is deprecated, use [tool:pytest] instead.

-- Docs: http://doc.pytest.org/en/latest/warnings.html
= 1 failed, 237 passed, 2 skipped, 1 warnings in 1.33 seconds ==
debian/rules:14: recipe for target 'test-python2.7' failed
make[1]: *** [test-python2.7] Error 1
make[1]: Leaving directory '/<>'
debian/rules:10: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
status 2


The above is how the build ends in my autobuilder and it's not
necessarily the relevant part.

The failure is not, however, related to using dpkg-buildpackage -A,
as it also fails in reproducible builds:

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

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

Bug#905555: emacs-nox: fails to upgrade from 47.0

[Sven Joachim]

Package: emacs-nox
Version: 1:25.2+1-9
Severity: serious

Upgrading emacs-nox from 47.0 failed in a chroot for me:

,
| # apt-get dist-upgrade
| Reading package lists... Done
| Building dependency tree   
| Reading state information... Done
| Calculating upgrade... Done
| The following package was automatically installed and is no longer required:
|   emacs25-nox
| Use 'sudo apt autoremove' to remove it.
| The following packages will be REMOVED:
|   emacs25-bin-common emacs25-common
| The following NEW packages will be installed:
|   emacs-bin-common emacs-common
| The following packages will be upgraded:
|   emacs-nox emacs25-nox emacsen-common
| 3 upgraded, 2 newly installed, 2 to remove and 0 not upgraded.
| Need to get 0 B/16.3 MB of archives.
| After this operation, 78.8 kB disk space will be freed.
| Do you want to continue? [Y/n] 
| debconf: delaying package configuration, since apt-utils is not installed
| (Reading database ... 15154 files and directories currently installed.)
| Preparing to unpack .../emacs25-nox_1%3a25.2+1-9_all.deb ...
| Remove emacsen-common for emacs25
| emacsen-common: Handling removal of emacsen flavor emacs25
| Unpacking emacs25-nox (1:25.2+1-9) over (25.2+1-6+b3) ...
| (Reading database ... 15146 files and directories currently installed.)
| Removing emacs25-bin-common (25.2+1-6+b3) ...
| Removing emacs25-common (25.2+1-6) ...
| dpkg: warning: while removing emacs25-common, directory 
'/usr/share/icons/hicolor/scalable/mimetypes' not empty so not removed
| dpkg: warning: while removing emacs25-common, directory 
'/usr/share/icons/hicolor/scalable/apps' not empty so not removed
| dpkg: warning: while removing emacs25-common, directory 
'/usr/share/icons/hicolor/48x48/apps' not empty so not removed
| dpkg: warning: while removing emacs25-common, directory 
'/usr/share/icons/hicolor/32x32/apps' not empty so not removed
| dpkg: warning: while removing emacs25-common, directory 
'/usr/share/icons/hicolor/24x24/apps' not empty so not removed
| dpkg: warning: while removing emacs25-common, directory 
'/usr/share/icons/hicolor/16x16/apps' not empty so not removed
| dpkg: warning: while removing emacs25-common, directory 
'/usr/share/icons/hicolor/128x128/apps' not empty so not removed
| (Reading database ... 12537 files and directories currently installed.)
| Preparing to unpack .../emacsen-common_3.0.2_all.deb ...
| Unpacking emacsen-common (3.0.2) over (2.0.8) ...
| dpkg: warning: unable to delete old directory '/etc/emacs/site-start.d': 
Directory not empty
| dpkg: warning: unable to delete old directory '/etc/emacs': Directory not 
empty
| Selecting previously unselected package emacs-common.
| Preparing to unpack .../emacs-common_1%3a25.2+1-9_all.deb ...
| Unpacking emacs-common (1:25.2+1-9) ...
| Selecting previously unselected package emacs-bin-common.
| Preparing to unpack .../emacs-bin-common_1%3a25.2+1-9_i386.deb ...
| Unpacking emacs-bin-common (1:25.2+1-9) ...
| Preparing to unpack .../emacs-nox_1%3a25.2+1-9_i386.deb ...
| dpkg-query: no packages found matching emacs-nox:i386
| dpkg-query: package 'emacs-nox' is not installed
| Use dpkg --info (= dpkg-deb --info) to examine archive files,
| and dpkg --contents (= dpkg-deb --contents) to list their contents.
| dpkg-maintscript-helper: error: file '/usr/share/doc/emacs-nox' not owned by 
package 'emacs-nox:i386'
| dpkg-query: package 'emacs-nox' is not installed
| Use dpkg --info (= dpkg-deb --info) to examine archive files,
| and dpkg --contents (= dpkg-deb --contents) to list their contents.
| dpkg-maintscript-helper: error: file '/usr/share/doc/emacs-nox/copyright' not 
owned by package 'emacs-nox:i386'
| dpkg-query: package 'emacs-nox' is not installed
| Use dpkg --info (= dpkg-deb --info) to examine archive files,
| and dpkg --contents (= dpkg-deb --contents) to list their contents.
| dpkg-maintscript-helper: error: file '/usr/share/doc/emacs-nox/changelog.gz' 
not owned by package 'emacs-nox:i386'
| dpkg-maintscript-helper: error: directory '/usr/share/doc/emacs-nox' contains 
files not owned by package emacs-nox:i386, cannot switch to symlink
| dpkg: error processing archive 
/var/cache/apt/archives/emacs-nox_1%3a25.2+1-9_i386.deb (--unpack):
|  new emacs-nox package pre-installation script subprocess returned error exit 
status 1
| Errors were encountered while processing:
|  /var/cache/apt/archives/emacs-nox_1%3a25.2+1-9_i386.deb
| E: Sub-process /usr/bin/dpkg returned an error code (1)
`

The "dpkg-query: no packages found matching emacs-nox:i386" error
message looks suspicious, this really should not happen.


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

Kernel: Linux 4.18.0-rc8-nouveau (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via 

Bug#902958: marked as done (obfs4proxy: switch Build-Depends to golang-golang-x-crypto-dev)

[Debian Bug Tracking System]

Your message dated Mon, 06 Aug 2018 04:48:50 +
with message-id 
and subject line Bug#902958: fixed in obfs4proxy 0.0.7-4
has caused the Debian Bug report #902958,
regarding obfs4proxy: switch Build-Depends to golang-golang-x-crypto-dev
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.)


-- 
902958: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902958
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: obfs4proxy
Version: 0.0.7-3
Severity: serious

The transitional package golang-go.crypto-dev is gone. Please adjust
the Build-Depends and use golang-golang-x-crypto-dev instead.


Andreas
--- End Message ---
--- Begin Message ---
Source: obfs4proxy
Source-Version: 0.0.7-4

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

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

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

Debian distribution maintenance software
pp.
Ulrike Uhlig  (supplier of updated obfs4proxy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 06 Aug 2018 06:22:13 +0200
Source: obfs4proxy
Binary: obfs4proxy
Architecture: source amd64
Version: 0.0.7-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers 

Changed-By: Ulrike Uhlig 
Description:
 obfs4proxy - pluggable transport proxy for Tor, implementing obfs4
Closes: 902958
Changes:
 obfs4proxy (0.0.7-4) unstable; urgency=medium
 .
   * Team upload.
   * debian/control:
 - Switch to golang-golang-x-crypto-dev (Closes: #902958).
 - Update VCS fields to Salsa.
 - Update priority.
Checksums-Sha1:
 cff50fbb5fae2c90f562d3f050e14a5551ba8d49 2211 obfs4proxy_0.0.7-4.dsc
 9f98d0d55e82c4c7dfd01afa0b23f0c9d5d5cb31 20112 obfs4proxy_0.0.7-4.debian.tar.xz
 ecc129dd85f5716e69d25ce98b6ab477f6686dd9 6319 
obfs4proxy_0.0.7-4_amd64.buildinfo
 cc7298e29f7b04fc9ef8aac291e18a08d7d447d3 1264344 obfs4proxy_0.0.7-4_amd64.deb
Checksums-Sha256:
 b1b9adf3dc2b56255404a33dfe3c3b55ab8fc9e200ddcdd452a22babae63dc25 2211 
obfs4proxy_0.0.7-4.dsc
 694ad723f68dc118a86196850b2cc1e7eef931ff6fda08070ee37f9c65615da1 20112 
obfs4proxy_0.0.7-4.debian.tar.xz
 5366ea4df8ef614d7bdd2864e582eed413a256d177a04b8d35f2755c25b55a70 6319 
obfs4proxy_0.0.7-4_amd64.buildinfo
 0b68f16d8cd68a1d765e2660a4657a3b0585a89fd7497961b94a62ba5e62e0ef 1264344 
obfs4proxy_0.0.7-4_amd64.deb
Files:
 4431a42dc1eb5859c5f9162a489d92e1 2211 net optional obfs4proxy_0.0.7-4.dsc
 262ea3d13396938ff0fc8fc5bf17fa3d 20112 net optional 
obfs4proxy_0.0.7-4.debian.tar.xz
 1aff6300aea725c592613030c8424376 6319 net optional 
obfs4proxy_0.0.7-4_amd64.buildinfo
 0b5f16aba6d33674a71df1925be81c32 1264344 net optional 
obfs4proxy_0.0.7-4_amd64.deb

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEE7eP0RD800mGVFNeQsUuww42GHPEFAltn0CoSHHVscmlrZUBk
ZWJpYW4ub3JnAAoJELFLsMONhhzxePwP/2Vi4891elCcPf14iL710Zk+fVJbaHrt
GKnssHvSyOVzUfJkLHGA5O7ZjkS7N6atBL45ulDU9VnLdfWKMs4pNjK9ziQTNwL8
BVxIFOL7HhVuxk4UBOMbhd8CaJpse6Ctq1Ge/i9p6enuKHpgSbocT4ynd8Dtz6SN
Mx+4XJbzsIC3aopb/G0drXLqeM8AI1QPEQSwoGQSr9wTAo+UTwSBFNoRrjOsCuBM
bCJ0lCyUkb/TpjdWQ+XnvSQ5EG05QebaJhSjxY4a13Ielr1SUMWvA0/Ig54E+drP
XU8hrQvTxkqpyBgzD/972Em7O9tKKQ65euorneCG4Kvgl1+CIlt6xzDIgtrVWhXQ
8U0VXCx/9oeEyQYv2aqWyp1RFR7qgFsvPOj6cxVhJDVZa34+73fJwRX8Q477hDpT
YJd4HW76Ru11b+ApQmwvu6Ex9oaEhRXjoTbkj4uRME0i6WEza6vufCjWdPFV9vm0
xkt/WAA9fgXKjYPJ0c40RLcOv8XrXL1Vh4ARdybi3/Gv2bhrL2tniYuM0QszNXcd
6Do4X62PMe0YU6QALf5sNPBF+Rps+PUS1jeIfLNPzN6dbzoDtVou9p/M30ICl64a
bgeKoPo6DCskh+qOgUEdMlGVXZYO2S0kUAB7z/DRbTMPTY+NxvVtb0RwSmGOrTIs
Cd5mNwxB/QF/
=2Q47
-END PGP SIGNATURE End Message ---

Bug#898535: closed by Chow Loong Jin (Bug#898535: fixed in tinyxml2 6.2.0+dfsg-2)

[Chow Loong Jin]

On Sun, Aug 05, 2018 at 01:38:31PM +0200, Joachim Reichel wrote:
> On 03.08.2018 06:03, Debian Bug Tracking System wrote:
> > Changes:
> >  tinyxml2 (6.2.0+dfsg-2) unstable; urgency=medium
> >  .
> >* [7fdca1f] Rename package for abi break (Closes: #898535)
> 
> How do you plan to deal with the breakage that results from the renaming? Did
> you already ask for binNMUs?

No I haven't, but I plan to.

> I do not see a bug report that requests a
> transition slot, nor any discussion on debian-release.

Whoops, I was just going to binNMU all rdeps and be done with it since
it was a pretty short list. Considering that the current libtinyxml2-6
has already broken ABI, should I have requested and waited for a
transition slot instead?

-- 
Kind regards,
Loong Jin


signature.asc
Description: PGP signature

Bug#905413: marked as done (libgamemode0-dev: missing Depends: libgamemode0 (= ${binary:Version}))

[Debian Bug Tracking System]

Your message dated Mon, 06 Aug 2018 03:00:10 +
with message-id 
and subject line Bug#905413: fixed in gamemode 1.2-3
has caused the Debian Bug report #905413,
regarding libgamemode0-dev: missing Depends: libgamemode0 (= ${binary: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.)


-- 
905413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905413
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgamemode0-dev
Version: 1.2-2
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + libgamemodeauto0-dev

Hi,

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

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

0m27.4s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libgamemode.so -> libgamemode.so.0

Similar problems in libgamemodeauto0-dev which misses a
  Depends: libgamemodeauto0 (= ${binary:Version})

0m26.9s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libgamemodeauto.so -> libgamemodeauto.so.0


BTW, why do the -dev packages contain the SOVERSION in their name?
Usually the -dev packages omit the SOVERSION, then the rdepends do
not need updating if the SOVERSION changes.

Canonical -dev packages would be called libgamemode-dev, libgamemodeauto-dev


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: gamemode
Source-Version: 1.2-3

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

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

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

Debian distribution maintenance software
pp.
Jonathan Carter  (supplier of updated gamemode 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: Sun, 05 Aug 2018 16:33:16 +0200
Source: gamemode
Binary: gamemode libgamemode0 libgamemode-dev libgamemodeauto0 
libgamemodeauto-dev
Architecture: source amd64
Version: 1.2-3
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Carter 
Changed-By: Jonathan Carter 
Description:
 gamemode   - Optimise Linux system performance on demand
 libgamemode-dev - Optimise Linux system performance on demand
 libgamemode0 - Optimise Linux system performance on demand
 libgamemodeauto-dev - Optimise Linux system performance on demand
 libgamemodeauto0 - Optimise Linux system performance on demand
Closes: 905413
Changes:
 gamemode (1.2-3) unstable; urgency=medium
 .
   * Fix -dev package names and relationships (Closes: #905413)
Checksums-Sha1:
 c75e133bf7f3a3d30df77b6afd9eb5a417596da5 1928 gamemode_1.2-3.dsc
 c482a56a05666f7667ab415298024465d2b1d4f4 67406 gamemode_1.2-3.tar.gz
 dcbdab703afcd0ad40235e6ce075fa4292b6f907 46352 gamemode-dbgsym_1.2-3_amd64.deb
 2b8528a5a1f2e041aa168d34c401718dcccfbd6a 9231 gamemode_1.2-3_amd64.buildinfo
 fa13d8bf4dfb521507edb5368b84e59a698234c9 21612 gamemode_1.2-3_amd64.deb
 1a6a58593f939fde8b3af3654f6b53df762f260a 5504 libgamemode-dev_1.2-3_amd64.deb
 89b9fdd1ac81c6140f057832a9e4485da2197236 13804 
libgamemode0-dbgsym_1.2-3_amd64.deb
 f96531d1b0625898cc4d7b49e3d69b711f14eafe 8492 libgamemode0_1.2-3_amd64.deb
 3610d000479482673753c41a3919920938a075d9 3660 
libgamemodeauto-dev_1.2-3_amd64.deb
 c429e2f1652656e57b69530bcdf34bfc7f8d24cf 7764 
libgamemodeauto0-dbgsym_1.2-3_amd64.deb
 1caba37d545fae44be155ee3b2e65267519f86c9 6280 libgamemodeauto0_1.2-3_amd64.deb
Checksums-Sha256:
 7dc1418ed859a535d39b1d0ece354ab2cae3dfa871c392581af4b2e225c1df4b 1928 
gamemode_1.2-3.dsc
 e6955457008f687799bf88a0d5c474f48219e1f8d45b08e64f3c9f5ddcc11ae3 67406 
gamemode_1.2-3.tar.gz
 7244ab50d6a2ca5d7dc2d11d558f96bb8775450b6e0958bbf52c183536984c0d 46352 
gamemode-dbgsym_1.2-3_amd64.deb
 2fdb1e70e122f1a0ca708f0a50bd269e1ed0082f81cd38fcec98fa96f152f602 9231 
gamemode_1.2-3_amd64.buildinfo
 7e815f873ea720bed6fd35b17f68b3c9696cb325b39411eba1874390ab1752de 21612 
gamemode_1.2-3_amd64.deb
 12601391fdb024a18b526ad6aeb47a058748059b685b672c8a6af38c6fc18283 5504 
libgamemode-dev_1.2-3_amd64.deb
 e4c31cd4c564695e9a71e5c313024199aaf0280c8e7abec207a0a39c968c33b6 13804 
libgamemode0-dbgsym_1.2-3_amd64.deb
 7d8a61b9ee7abb498bbfe7553ca0aab954f0b21c5e983e39c56c61d3983f1807 8492 
libgame

Bug#905188: cryptsetup-initramfs: fails to install, remove, distupgrade, and install again

[Andreas Beckmann]

Followup-For: Bug #905188
Control: found -1 2:2.0.4-1
Control: tag -1 - moreinfo

That needs more work and testing ...
right now the package fails to install in sid.

  Selecting previously unselected package cryptsetup-initramfs.
  (Reading database ... 
(Reading database ... 5042 files and directories currently installed.)
  Preparing to unpack .../cryptsetup-initramfs_2%3a2.0.4-1_all.deb ...
  md5sum: /etc/cryptsetup-initramfs/conf-hook: No such file or directory
  /var/lib/dpkg/tmp.ci/preinst: 54: /var/lib/dpkg/tmp.ci/preinst: cannot create 
/etc/cryptsetup-initramfs/conf-hook.dpkg-new: Directory nonexistent
  dpkg: error processing archive 
/var/cache/apt/archives/cryptsetup-initramfs_2%3a2.0.4-1_all.deb (--unpack):
   new cryptsetup-initramfs package pre-installation script subprocess returned 
error exit status 2
  Errors were encountered while processing:
   /var/cache/apt/archives/cryptsetup-initramfs_2%3a2.0.4-1_all.deb


Andreas

Processed: Re: cryptsetup-initramfs: fails to install, remove, distupgrade, and install again

[Debian Bug Tracking System]

Processing control commands:

> found -1 2:2.0.4-1
Bug #905188 {Done: Guilhem Moulin } [cryptsetup-initramfs] 
cryptsetup-initramfs: fails to install, remove, distupgrade, and install again
Marked as found in versions cryptsetup/2:2.0.4-1; no longer marked as fixed in 
versions cryptsetup/2:2.0.4-1 and reopened.
> tag -1 - moreinfo
Bug #905188 [cryptsetup-initramfs] cryptsetup-initramfs: fails to install, 
remove, distupgrade, and install again
Removed tag(s) moreinfo.

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

Bug#905552: gamemode: Incomplete debian/copyright?

[Chris Lamb]

Source: gamemode
Version: 1.2-3
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Jonathan Carter , ftpmas...@debian.org

Hi,

I just ACCEPTed gamemode from NEW but noticed it was missing 
attribution in debian/copyright for at least what looks like a
inih code copy under the subprojects dir.

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


Regards,

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

Bug#905522: ghdl: Incomplete debian/copyright?

[Chris Lamb]

[adding Thorsten Alteholz  to CC]

Hi Andreas,

> > I just ACCEPTed ghdl from NEW but the FTP team noticed it was missing the
> > entire text of the CC license.
> 
> First, thanks for the ACCEPT.
> 
> The missing text of the CC license was the reason the package was
> rejected months ago. I included the full text in debian/copyright, among
> many other changes that came with using a more recent upstream which
> changes the library organization. Is there really still something
> missing (and what) or is this maybe some outdated ftpmaster notes for
> ghdl sticking around?

This is possible.

CCing in Thorsten Alteholz and quoting in full; as it was his note.
Thorsten, can you comment here?


Best wishes,

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

Bug#903789: marked as done (wine64-development: missing version 3.12-2?)

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 23:34:49 +
with message-id 
and subject line Bug#903789: fixed in wine-development 3.13-3
has caused the Debian Bug report #903789,
regarding wine64-development: missing version 3.12-2?
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.)


-- 
903789: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903789
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wine64-development
Version: 3.12-1
Severity: normal

I installed wine64-development, then when I tried to install the 
wine-development metapackage it failed due to requiring version >= 3.12-2. 
That's the current version of wine32-development, but wine64-development is 
still at 3.12-1 for some reason.

-- Package-specific info:
/usr/bin/wine does not exist.

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

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

Versions of packages wine64-development depends on:
ii  libc62.27-4
ii  libwine-development  3.12-1

Versions of packages wine64-development recommends:
pn  wine-development
pn  wine32-development  

Versions of packages wine64-development suggests:
pn  libwine-gecko-2.47
pn  wine64-development-preloader  

Versions of packages wine64-development is related to:
ii  fonts-wine  3.0.2-2
pn  wine-development
pn  wine32-development  
ii  wine64-development  3.12-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: wine-development
Source-Version: 3.13-3

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

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

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated wine-development 
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: Sun, 05 Aug 2018 23:15:10 +
Source: wine-development
Binary: wine-development wine32-development wine64-development 
wine32-development-preloader wine64-development-preloader 
wine32-development-tools wine64-development-tools libwine-development 
libwine-development-dev
Architecture: source
Version: 3.13-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party 
Changed-By: Michael Gilbert 
Description:
 libwine-development - Windows API implementation - library
 libwine-development-dev - Windows API implementation - development files
 wine-development - Windows API implementation - standard suite
 wine32-development - Windows API implementation - 32-bit binary loader
 wine32-development-preloader - Windows API implementation - prelinked 32-bit 
binary loader
 wine32-development-tools - Windows API implementation - 32-bit developer tools
 wine64-development - Windows API implementation - 64-bit binary loader
 wine64-development-preloader - Windows API implementation - prelinked 64-bit 
binary loader
 wine64-development-tools - Windows API implementation - 64-bit developer tools
Closes: 903789
Changes:
 wine-development (3.13-3) unstable; urgency=medium
 .
   * Fix build errors on arm64 (closes: #903789).
Checksums-Sha1:
 9a679dbe9c9d88718e654f6f216d2cb819b994d2 4755 wine-development_3.13-3.dsc
 5230a03a7be5987c3ac9b1a32dd32fb91f3b7daf 190208 
wine-development_3.13-3.debian.tar.xz
 92ea475eb75d167f4d7ab62cc092f6595e0c1703 19802 
wine-development_3.13-3_source.buildinfo
Checksums-Sha256:
 fb7b6b259aeac694095b37d9a204cb3313a73286f6775af06ae643e4c4e37597 4755 
wine-development_3.13-3.dsc
 45b66b2adeac6d09e41fdd55fd637d5b3c96aa57145b70f90cfd77b2238fde5c 190208 
wine-development_3.13-3.debian.tar.xz
 a243056c51ce7123372404af7a65574b3d47fae52de63f1eed07b690f311e6a8 19802 
wine-development_3.13-3_source.buildinfo
Files:
 4552a7115cf5a34da5a20bb4dd504cf3 4755 otherosfs optional 
wine-development_3.13-3.dsc
 8244c0bc0a92ce8facf1a2b99b9075f7 190208 othero

Bug#903966: marked as done (wine-development: FTBFS on most architectures)

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 23:34:49 +
with message-id 
and subject line Bug#903789: fixed in wine-development 3.13-3
has caused the Debian Bug report #903789,
regarding wine-development: FTBFS on most architectures
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.)


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

This package failed to build on the build daemons
on amd64 and arm*.

On amd64:

  row_server_p.c: In function '__finally_IWineRowServer_AddRefRows_Stub':
  row_server_p.c:7751:35: error: passing argument 1 of 
'__frame->_StubMsg.pfnFree' discards 'const' qualifier from pointer target type 
[-Werror=discarded-array-qualifiers]
   __frame->_StubMsg.pfnFree(__frame->rghRows);
   ^~~
  row_server_p.c:7751:35: note: expected 'void *' but argument is of type 
'const HROW (*)[] {aka const long unsigned int (*)[]}'

On arm*:

  ptrace.c:167:12: error: 'get_ptrace_tid' defined but not used 
[-Werror=unused-function]
   static int get_ptrace_tid( struct thread *thread )

-- 
Niko Tyni   nt...@debian.org
--- End Message ---
--- Begin Message ---
Source: wine-development
Source-Version: 3.13-3

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

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

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated wine-development 
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: Sun, 05 Aug 2018 23:15:10 +
Source: wine-development
Binary: wine-development wine32-development wine64-development 
wine32-development-preloader wine64-development-preloader 
wine32-development-tools wine64-development-tools libwine-development 
libwine-development-dev
Architecture: source
Version: 3.13-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party 
Changed-By: Michael Gilbert 
Description:
 libwine-development - Windows API implementation - library
 libwine-development-dev - Windows API implementation - development files
 wine-development - Windows API implementation - standard suite
 wine32-development - Windows API implementation - 32-bit binary loader
 wine32-development-preloader - Windows API implementation - prelinked 32-bit 
binary loader
 wine32-development-tools - Windows API implementation - 32-bit developer tools
 wine64-development - Windows API implementation - 64-bit binary loader
 wine64-development-preloader - Windows API implementation - prelinked 64-bit 
binary loader
 wine64-development-tools - Windows API implementation - 64-bit developer tools
Closes: 903789
Changes:
 wine-development (3.13-3) unstable; urgency=medium
 .
   * Fix build errors on arm64 (closes: #903789).
Checksums-Sha1:
 9a679dbe9c9d88718e654f6f216d2cb819b994d2 4755 wine-development_3.13-3.dsc
 5230a03a7be5987c3ac9b1a32dd32fb91f3b7daf 190208 
wine-development_3.13-3.debian.tar.xz
 92ea475eb75d167f4d7ab62cc092f6595e0c1703 19802 
wine-development_3.13-3_source.buildinfo
Checksums-Sha256:
 fb7b6b259aeac694095b37d9a204cb3313a73286f6775af06ae643e4c4e37597 4755 
wine-development_3.13-3.dsc
 45b66b2adeac6d09e41fdd55fd637d5b3c96aa57145b70f90cfd77b2238fde5c 190208 
wine-development_3.13-3.debian.tar.xz
 a243056c51ce7123372404af7a65574b3d47fae52de63f1eed07b690f311e6a8 19802 
wine-development_3.13-3_source.buildinfo
Files:
 4552a7115cf5a34da5a20bb4dd504cf3 4755 otherosfs optional 
wine-development_3.13-3.dsc
 8244c0bc0a92ce8facf1a2b99b9075f7 190208 otherosfs optional 
wine-development_3.13-3.debian.tar.xz
 0917562ce462c4c82aaad0462ba8ab9e 19802 otherosfs optional 
wine-development_3.13-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQQzBAEBCgAdFiEEluhy7ASCBulP9FUWuNayzQLW9HMFAltnhkUACgkQuNayzQLW
9HPl0h/8C0cCaGhYZxxEYImLtxskEKbZgon1W3vRofxZM+HfrTW+H0Sk8xG/cAJf
GBVQoxUrugpvV7AOzlmKpEYqjEWaidglrYFIz3sTo653hHfEJsCdHGLtotDW0+Nr
YFwFBAeSxvQwusLWUAiWwskbkjTpAzS/tH5iAZZBsS9WRB/DgDM6DpYIBJwVYlL5
biV3TCg4EpqgFoULeHOUYIljG8YD2sFZ3wMScplFq8

Bug#897767: closed by Mo Zhou (Bug#897767: fixed in highwayhash 0~20180209-g14dedec-5)

[Lumin]

control: retitle -1 non-x86 symbols out of date
control: severity -1 normal

This non-x86 arches are not my priorities currently. It doesn't deserve
another RFS bug to the mentors list, and it can be easily fixed by me when
I get my Debian Developer account.

On Mon, Aug 6, 2018 at 00:45 Adrian Bunk  wrote:

> Control: reopen -1
>
> On Mon, Jul 23, 2018 at 01:54:03AM +, Debian Bug Tracking System wrote:
> >...
> >  highwayhash (0~20180209-g14dedec-5) unstable; urgency=medium
> >  .
> >* Refresh symbols to avoid FTBFS with GCC-8 (Closes: #897767)
> >...
>
> unfortunately this fixed it only for amd64, the package still FTBFS
> on arm64/ppc64el/x32:
> https://buildd.debian.org/status/package.php?p=highwayhash
>
> 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
>
-- 
Best,

Processed: Re: Bug#897767: closed by Mo Zhou (Bug#897767: fixed in highwayhash 0~20180209-g14dedec-5)

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 non-x86 symbols out of date
Bug #897767 [src:highwayhash] highwayhash: ftbfs with GCC-8
Changed Bug title to 'non-x86 symbols out of date' from 'highwayhash: ftbfs 
with GCC-8'.
> severity -1 normal
Bug #897767 [src:highwayhash] non-x86 symbols out of date
Severity set to 'normal' from 'serious'

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

Bug#905548: python-pysam: FTBFS - tests fail: AttributeError: 'module' object has no attribute 'HAVE_LIBCURL'

[Andreas Beckmann]

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

Bug#905414: marked as done (libosmo-sccp-dev: missing Depends: libosmomtp0 (= ${binary:Version}))

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 21:33:55 +
with message-id 
and subject line Bug#905414: fixed in libosmo-sccp 0.9.0-3~exp1
has caused the Debian Bug report #905414,
regarding libosmo-sccp-dev: missing Depends: libosmomtp0 (= ${binary: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.)


-- 
905414: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905414
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libosmo-sccp-dev
Version: 0.9.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

0m31.3s ERROR: FAIL: Broken symlinks:
  /usr/lib/x86_64-linux-gnu/libosmomtp.so -> libosmomtp.so.0.0.0


cheers,

Andreas


libosmo-sccp-dev_0.9.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libosmo-sccp
Source-Version: 0.9.0-3~exp1

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

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

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

Debian distribution maintenance software
pp.
Ruben Undheim  (supplier of updated libosmo-sccp 
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: Sun, 05 Aug 2018 22:40:43 +0200
Source: libosmo-sccp
Binary: libosmo-sccp-dev libosmo-sigtran0 libosmo-sigtran-doc 
libosmo-sigtran-dev libosmosccp0 libosmomtp0 libosmoxua0 osmo-stp
Architecture: source
Version: 0.9.0-3~exp1
Distribution: experimental
Urgency: medium
Maintainer: Debian Mobcom Maintainers 

Changed-By: Ruben Undheim 
Description:
 libosmo-sccp-dev - Development files for libsccp, libmtp and libxua
 libosmo-sigtran-dev - Development headers for the Osmocom SIGTRAN library
 libosmo-sigtran-doc - Documentation for the Osmocom SIGTRAN library
 libosmo-sigtran0 - Osmocom SIGTRAN library (SCCP, SUA, M3UA and more)
 libosmomtp0 - Message Transfer Part for Signaling System 7
 libosmosccp0 - Library for Signalling Connection Control Part (SCCP)
 libosmoxua0 - Osmocom SCCP support library for generating and parsing messages
 osmo-stp   - Osmocom SIGTRAN STP (Signaling Transfer Point)
Closes: 905414
Changes:
 libosmo-sccp (0.9.0-3~exp1) experimental; urgency=medium
 .
   * debian/control:
 - Add missing dependency for libosmo-sccp-dev: libosmomtp0 (=
   ${binary:Version}) (Closes: #905414)
 - New standards version 4.2.0 - no changes
   * debian/patches/0005-Patch-the-pkconfig-file-for-libosmo-xua.patch
 - The new autopkgtest reveiled a problem in one of the pkg-config files.
   Fix.
   * debian/patches: Refreshed patches using gbp-pq
   * debian/tests:
 - Added a test to verify that it is possible to link to the library.
Checksums-Sha1:
 2981f7e5456c94a1145b586ebdd6107df478c18a 2827 libosmo-sccp_0.9.0-3~exp1.dsc
 61a1a5af3dd108f7b7d56ff1843d596da272214b 8140 
libosmo-sccp_0.9.0-3~exp1.debian.tar.xz
Checksums-Sha256:
 fa7b754269a9e0813004368d76035a5d64e4a6a3794731030be138f01500f2c0 2827 
libosmo-sccp_0.9.0-3~exp1.dsc
 03169efb087c67492e02ef70c89c9f6714571b620a7a4e8edf18499c9311309d 8140 
libosmo-sccp_0.9.0-3~exp1.debian.tar.xz
Files:
 c4e9025d155c1f662fff863813fb938d 2827 libs optional 
libosmo-sccp_0.9.0-3~exp1.dsc
 13c23f90693304c6f3daecb0372b7034 8140 libs optional 
libosmo-sccp_0.9.0-3~exp1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJMBAEBCAA2FiEENHTECWcp7QxRgH085pgix+ApWM0FAltnZx4YHHJ1YmVuLnVu
ZGhlaW1AZ21haWwuY29tAAoJEOaYIsfgKVjNVKkP/1pB5gBI2fEFyngcv/POMAii
4Py89GsL3U4jG36p2vl/sYcAlj9gdwRT9NrobS9EAiC1pJySLqXVhVA2LxFsU0tw
YMhvT21VuU42zEU+zOE6zvaLHnQfANrKlTjXY3jzOx+akak7yt0ickrdgJfbiU+d
QU9F/EQqFUWko0X8poYTtmIqdTXC8qYB4HTMh1XI+uPKh32NF82HzFvv4QIkJn//
IkzS8Go8IFW1C9aLfSSDmGnkZtN80bH0mWFXrNYfUD4ZKcbGnH6Fc16jfn25+QHN
SnPKwDjdHdHm7bX/mQ4aCp/f4rpZpX4InM/6MDiyslmaSuFNLWIS2k2JUYXHyVs6
42Mf9Wg0RkKEgFQX9xqWx18LuEXdwK/p2byA9SC06GAGiYc1ZXQlXuqu+9RM/Pwu
BnEZe3Yq3EpxqlQeysnTiLr7cY6VNSsppT6lCtHcMt2sG9DlFDnl86RJtmJBVgCV
OtxuRN21+8gfGtZfqqrTs+hvAcv3buxLvKignJ0Yooze6j+Q6RQ2XHdUCwT0ed2q
LZ/pCLW2To9ryd5T5PMc5lgOCTY1+gdqnx1ghLEUsJ+b9O7nXsU107YOset+3HPl
kWqnx/A9xH

Processed: found 858954 in 0.7.4.0, found 782155 in 2.02+dfsg1-5, found 782156 in 2.02+dfsg1-5 ...

[Debian Bug Tracking System]

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

> found 858954 0.7.4.0
Bug #858954 [diaspora-common] diaspora-common: unowned directories after purge: 
/var/cache/diaspora/, /var/lib/diaspora-common/, /var/log/diaspora/
Marked as found in versions diaspora-installer/0.7.4.0.
> found 782155 2.02+dfsg1-5
Bug #782155 [grub-pc] grub-pc: unowned files after purge (policy 6.8, 10.8): 
/boot/grub/unicode.pf2
Marked as found in versions grub2/2.02+dfsg1-5.
> found 782156 2.02+dfsg1-5
Bug #782156 [grub-xen] grub-xen: unowned files after purge (policy 6.8, 10.8): 
/boot/grub/{locale, x86_64-xen}/* and some more
Marked as found in versions grub2/2.02+dfsg1-5.
> severity 905249 serious
Bug #905249 [src:cjs] cjs: Fails to build, symbols mismatch
Severity set to 'serious' from 'important'
> tags 905249 + ftbfs
Bug #905249 [src:cjs] cjs: Fails to build, symbols mismatch
Added tag(s) ftbfs.
> affects 904514 + libej0
Bug #904514 [python3-expeyes] python3-expeyes: fails to install: Exception: 
cannot get content of python-expeyes
Added indication that 904514 affects libej0
> severity 866737 serious
Bug #866737 [lighttpd] Enable Mod command fails on Stretch
Severity set to 'serious' from 'normal'
> severity 887450 serious
Bug #887450 [lighttpd] lighttpd missing dependency on perl5 for mod scripts
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
782155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782155
782156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782156
858954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858954
866737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866737
887450: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887450
904514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904514
905249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905249
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#887382: marked as done (prevent Clojure 1.9.0 alpha from migrating to testing)

[Debian Bug Tracking System]

Your message dated Sun, 5 Aug 2018 16:15:29 -0400
with message-id <20180805201529.GC3576@feralas>
and subject line Release clojure1.9 on the masses
has caused the Debian Bug report #887382,
regarding prevent Clojure 1.9.0 alpha from migrating to testing
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.)


-- 
887382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887382
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: clojure
Version: 1.9.0~alpha15-1
Severity: serious

This alpha version of Clojure 1.9.0 was uploaded to facilitate packaging
the official 1.9.0 release. As such, I need to prevent it from migrating
to testing for now.


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
This is ready to migrate down to testing now.

I was waiting for two things:

- ensure 1.9 and 1.8 can be simultaneously installed (required fixing
  the alternatives logic)
- piuparts tests actually passed

These are both fixed so let us loose 1.9 on the world of testing
users.

- e


signature.asc
Description: Digital signature
--- End Message ---

Bug#905542: xserver-xorg-video-nouveau: segmentation fault on startup every time

[Eric Cooper]

Thanks, I can confirm that rolling back to xserver-xorg-core 2:1.19.6-1
fixes the problem for me for now.

On Sun, Aug 5, 2018 at 3:55 PM Sven Joachim  wrote:

> Control: reassign -1 xserver-xorg-core
> Control: forcemerge 900550 -1
>
> On 2018-08-05 15:43 -0400, Eric Cooper wrote:
>
> > Package: xserver-xorg-video-nouveau
> > Version: 1:1.0.15-3
> > Severity: important
> >
> > I did an "apt-get upgrade" today that installed new
> > xserver-xorg-{core,nouveau} packages. Now X does not start on my system.
> > The same segmentation fault occurs every time I run "startx".
> > [...]
> > [   301.726] (EE)
> > [   301.726] (EE) Backtrace:
> > [   301.726] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4d)
> [0x56123945b8dd]
> > [   301.726] (EE) 1: /usr/lib/xorg/Xorg (0x5612392a8000+0x1b7599)
> [0x56123945f599]
> > [   301.726] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0
> (0x7f1b1ca8+0x128e0) [0x7f1b1ca928e0]
> > [   301.726] (EE) 3: /usr/lib/xorg/Xorg (miRenderColorToPixel+0xe)
> [0x5612393cfbde]
> > [   301.726] (EE) 4: /usr/lib/xorg/modules/libexa.so
> (0x7f1b19a8d000+0xf13b) [0x7f1b19a9c13b]
> > [   301.726] (EE) 5: /usr/lib/xorg/Xorg (0x5612392a8000+0x13a8b6)
> [0x5612393e28b6]
> > [   301.726] (EE) 6: /usr/lib/xorg/Xorg (0x5612392a8000+0x12ec1c)
> [0x5612393d6c1c]
> > [   301.726] (EE) 7: /usr/lib/xorg/Xorg (0x5612392a8000+0x5b008)
> [0x561239303008]
> > [   301.726] (EE) 8: /usr/lib/xorg/Xorg (0x5612392a8000+0x5f008)
> [0x561239307008]
> > [   301.726] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6
> (__libc_start_main+0xe7) [0x7f1b1c8e5b17]
> > [   301.727] (EE) 10: /usr/lib/xorg/Xorg (_start+0x2a) [0x5612392f0d0a]
> > [   301.727] (EE)
> > [   301.727] (EE) Segmentation fault at address 0x8
> > [   301.727] (EE)
> > Fatal server error:
> > [   301.727] (EE) Caught signal 11 (Segmentation fault). Server aborting
>
> This is bug #900550 in xserver-xorg-core, a fix is pending in git[1].
>
> Cheers,
>Sven
>
>
> 1.
> https://salsa.debian.org/xorg-team/xserver/xorg-server/commit/aa7aaeb5223830a3670dc658152e28f125c17de8
>

Processed: Re: Bug#905542: xserver-xorg-video-nouveau: segmentation fault on startup every time

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 xserver-xorg-core
Bug #905542 [xserver-xorg-video-nouveau] xserver-xorg-video-nouveau: 
segmentation fault on startup every time
Bug reassigned from package 'xserver-xorg-video-nouveau' to 'xserver-xorg-core'.
No longer marked as found in versions xserver-xorg-video-nouveau/1:1.0.15-3.
Ignoring request to alter fixed versions of bug #905542 to the same values 
previously set
> forcemerge 900550 -1
Bug #900550 [xserver-xorg-core] xserver-xorg-core: X server segfaults for 
xfce4+nouveau after 2:1.19.6-1 -> 2:1.20.0-2 upgrade
Bug #903708 [xserver-xorg-core] xfce4: xfce fails to start with all methods
Bug #904715 [xserver-xorg-core] startxfce4 fails
Bug #905542 [xserver-xorg-core] xserver-xorg-video-nouveau: segmentation fault 
on startup every time
Severity set to 'serious' from 'important'
Added indication that 905542 affects xfce4,xfce4-session
Marked as found in versions xorg-server/2:1.20.0-2.
Added tag(s) patch.
Bug #903708 [xserver-xorg-core] xfce4: xfce fails to start with all methods
Removed indication that 903708 affects xfce4-session and xfce4
Added indication that 903708 affects xfce4,xfce4-session
Removed indication that 900550 affects xfce4 and xfce4-session
Added indication that 900550 affects xfce4,xfce4-session
Removed indication that 904715 affects xfce4 and xfce4-session
Added indication that 904715 affects xfce4,xfce4-session
Bug #904715 [xserver-xorg-core] startxfce4 fails
Merged 900550 903708 904715 905542

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

Processed: Re: spyder-unittest: autopkgtest fails with python3.7 in supported versions

[Debian Bug Tracking System]

Processing control commands:

> tags -1 ftbfs
Bug #905541 [src:spyder-unittest] spyder-unittest: autopkgtest fails with 
python3.7 in supported versions
Added tag(s) ftbfs.
> severity -1 serious
Bug #905541 [src:spyder-unittest] spyder-unittest: autopkgtest fails with 
python3.7 in supported versions
Severity set to 'serious' from 'normal'

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

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

[Bernd Rinn]

Hello Andreas,

There are some good news: For porting JHDF5 to HDF 1.10, I got help from
Gerd Heber. I have been fixing some looes ends in the last couple of
days and now the porting is now. I still want to do some improvements to
the library (not dependent on the underlying HDF5 version) and need to
work on the Windows build, but there is nothing that would keep you from
updating the port in Debian unstable. The build procedure for Linux
won't change anymore.

The current version of JHDF5 building on top of HDF5 1.10.3-pre1, you
will find in (branch master):

https://sissource.ethz.ch/sispub/jhdf5

I plan to do in about 2 weeks time a JHDF5 pre-release to get feedback
from users outside my organization. The release should then be based on
HDF5 1.10.3 once that version has been released by the HDF group. If you
have anyone who could test the pre-release version or your port, please
feel free to forward this email to him or her.

All the best,
Bernd

On 08/04/2018 08:06 AM, Andreas Tille wrote:
> Hello Bernd,
> 
> On Mon, May 28, 2018 at 09:18:28AM +0200, Bernd Rinn wrote:
>> Hello Andreas,
>>
>> On 05/27/2018 07:12 AM, Andreas Tille wrote:
>>> Hello Bernd,
>>>
>>> sorry for nagging again but we now have another Dependency from
>>> sis-jhdf5 which makes a fix for this issue even more interesting.  As I
>>> said before I would also try a patch if you might hesitate to issue a
>>> completely new release.
>>
>> It is embarrassing to admit that I still haven't found the time to port
>> JHDF5 to HDF5 1.10.
>>
>> If you can come up with a patch to bridge to time that would be greatly
>> appreciated!
> 
> Since I personally do not even know what HDF5 is I can not help myself
> and as far as Gilles Filippini stated[1] chances are pretty low that we
> from Debian will be able to come up with a patch.  What do you think
> about the remark
> 
>Have you considered using libhdf5-java[2] or libjhdf5-java instead?
> 
> Well, several projects are using libsis-hdf5-java but it might be to
> join forces with one single Java library which keeps up with current
> development.  I have no idea in how far libsis-hdf5-java is different
> for the other libs but could you somehow imagine to unify the interface
> and join forces?
> 
> Kind regards
> 
>   Andreas.
> 
> [1] https://lists.debian.org/debian-science/2018/05/msg00112.html
> [2] https://support.hdfgroup.org/HDF5/
> [3] 
> 
>>> On Wed, Sep 06, 2017 at 12:50:56PM +0200, Andreas Tille wrote:
 Hello Bernd,

 On Wed, 23 Nov 2016 06:54:21 +0100, you wrote
> the migration of JHDF5 to HDF5 1.10 is ongoing and mostly depend on me
> having a block of time I can spend on it. Your analysis of the work that
> needs to be done is right from what I can see. The plan is to switch to
> using the JNI library from the HDF group wherever possible (it may still
> be necessary to have a small JNI library though as some calls appear to
> be missing).
>
> I will keep you updated.

 Is there any news, may be only a patch for the existing version we
 could try to fix the Debian package?

 Kind regards

Andreas.

 -- 
 http://fam-tille.de

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

>>>
>>
>> -- 
>> Dr. Bernd Rinn
>> Head Scientific IT Services
>> ETH Zurich IT Services
>> SIB Swiss Institute of Bioinformatics
>> Weinbergstr. 11 (WEC D 19), 8092 Zürich, Switzerland, +41 44 632 0608
>> Mattenstr. 26 (BSB 1.01), 4058 Basel, Switzerland, +41 61 387 3130
>>
> 
> 
> 

-- 
Dr. Bernd Rinn
Head Scientific IT Services
ETH Zurich IT Services
SIB Swiss Institute of Bioinformatics
Weinbergstr. 11 (WEC D 19), 8092 Zürich, Switzerland, +41 44 632 0608
Mattenstr. 26 (BSB 1.01), 4058 Basel, Switzerland, +41 61 387 3130



smime.p7s
Description: S/MIME Cryptographic Signature

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

[Bernd Rinn]

Hello Andreas,

There are some good news: For porting JHDF5 to HDF 1.10, I got help from
Gerd Heber. I have been fixing some looes ends in the last couple of
days and now the porting is now. I still want to do some improvements to
the library (not dependent on the underlying HDF5 version) and need to
work on the Windows build, but there is nothing that would keep you from
updating the port in Debian unstable. The build procedure for Linux
won't change anymore.

The current version of JHDF5 building on top of HDF5 1.10.3-pre1, you
will find in (branch master):

https://sissource.ethz.ch/sispub/jhdf5

I plan to do in about 2 weeks time a JHDF5 pre-release to get feedback
from users outside my organization. The release should then be based on
HDF5 1.10.3 once that version has been released by the HDF group. If you
have anyone who could test the pre-release version or your port, please
feel free to forward this email to him or her.

All the best,
Bernd

On 08/04/2018 08:06 AM, Andreas Tille wrote:
> Hello Bernd,
> 
> On Mon, May 28, 2018 at 09:18:28AM +0200, Bernd Rinn wrote:
>> Hello Andreas,
>>
>> On 05/27/2018 07:12 AM, Andreas Tille wrote:
>>> Hello Bernd,
>>>
>>> sorry for nagging again but we now have another Dependency from
>>> sis-jhdf5 which makes a fix for this issue even more interesting.  As I
>>> said before I would also try a patch if you might hesitate to issue a
>>> completely new release.
>>
>> It is embarrassing to admit that I still haven't found the time to port
>> JHDF5 to HDF5 1.10.
>>
>> If you can come up with a patch to bridge to time that would be greatly
>> appreciated!
> 
> Since I personally do not even know what HDF5 is I can not help myself
> and as far as Gilles Filippini stated[1] chances are pretty low that we
> from Debian will be able to come up with a patch.  What do you think
> about the remark
> 
>Have you considered using libhdf5-java[2] or libjhdf5-java instead?
> 
> Well, several projects are using libsis-hdf5-java but it might be to
> join forces with one single Java library which keeps up with current
> development.  I have no idea in how far libsis-hdf5-java is different
> for the other libs but could you somehow imagine to unify the interface
> and join forces?
> 
> Kind regards
> 
>   Andreas.
> 
> [1] https://lists.debian.org/debian-science/2018/05/msg00112.html
> [2] https://support.hdfgroup.org/HDF5/
> [3] 
> 
>>> On Wed, Sep 06, 2017 at 12:50:56PM +0200, Andreas Tille wrote:
 Hello Bernd,

 On Wed, 23 Nov 2016 06:54:21 +0100, you wrote
> the migration of JHDF5 to HDF5 1.10 is ongoing and mostly depend on me
> having a block of time I can spend on it. Your analysis of the work that
> needs to be done is right from what I can see. The plan is to switch to
> using the JNI library from the HDF group wherever possible (it may still
> be necessary to have a small JNI library though as some calls appear to
> be missing).
>
> I will keep you updated.

 Is there any news, may be only a patch for the existing version we
 could try to fix the Debian package?

 Kind regards

Andreas.

 -- 
 http://fam-tille.de

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

>>>
>>
>> -- 
>> Dr. Bernd Rinn
>> Head Scientific IT Services
>> ETH Zurich IT Services
>> SIB Swiss Institute of Bioinformatics
>> Weinbergstr. 11 (WEC D 19), 8092 Zürich, Switzerland, +41 44 632 0608
>> Mattenstr. 26 (BSB 1.01), 4058 Basel, Switzerland, +41 61 387 3130
>>
> 
> 
> 

-- 
Dr. Bernd Rinn
Head Scientific IT Services
ETH Zurich IT Services
SIB Swiss Institute of Bioinformatics
Weinbergstr. 11 (WEC D 19), 8092 Zürich, Switzerland, +41 44 632 0608
Mattenstr. 26 (BSB 1.01), 4058 Basel, Switzerland, +41 61 387 3130



smime.p7s
Description: S/MIME Cryptographic Signature

Bug#905539: gcc-7 FTBFS with isl 0.20

[Helmut Grohne]

Source: gcc-7
Version: 7.3.0-27
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap

Hi Matthias,

I'm not sure whether you're aware already, but I felt that it was best
to just document that gcc-7 fails to build against isl 0.20. I tried to
check the vcs on whether this is already pending, but since alioth is
offline finding the vcs is difficult. Maybe you could also update the
Vcs fields. Build log symptom:

| ../../src/gcc/graphite-optimize-isl.c: In function 'isl_schedule_node* 
get_schedule_for_node_st(isl_schedule_node*, void*)':
| ../../src/gcc/graphite-optimize-isl.c:57:52: error: 'isl_space_dim' was not 
declared in this scope
|unsigned dims = isl_space_dim (space, isl_dim_set);

Helmut

Bug#904514: closed by Georges Khaznadar (Bug#904514: fixed in expeyes 4.4.3+dfsg-3)

[Andreas Beckmann]

Control: found -1 4.4.3+dfsg-3

On 2018-08-05 01:51, Debian Bug Tracking System wrote:
>* promoted the recommendation python3-expeyes <- udev to a dependency.

udev was a red herring. This change can be reverted.


The problem is most likely this code from the postinst:

## this was not managed properly by debian/rules:
if which py3compile >/dev/null 2>&1; then
py3compile -p python-expeyes
fi

I can totally confirm your comment. Why does python3-expeyes try to do
anything at all with the python2 variant ?


Andreas

Processed: Re: Bug#904514 closed by Georges Khaznadar (Bug#904514: fixed in expeyes 4.4.3+dfsg-3)

[Debian Bug Tracking System]

Processing control commands:

> found -1 4.4.3+dfsg-3
Bug #904514 {Done: Georges Khaznadar } [python3-expeyes] 
python3-expeyes: fails to install: Exception: cannot get content of 
python-expeyes
Marked as found in versions expeyes/4.4.3+dfsg-3; no longer marked as fixed in 
versions expeyes/4.4.3+dfsg-3 and reopened.

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

Bug#897746: marked as done (etsf-io: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Sun, 5 Aug 2018 21:23:27 +0300
with message-id <20180805182327.GA3971@localhost>
and subject line Re: Bug#897746: etsf-io: ftbfs with GCC-8
has caused the Debian Bug report #897746,
regarding etsf-io: 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.)


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
groupleveldocdir=''
host_alias=''
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='${prefix}/share/info'
install_sh='${SHELL} /<>/config/install-sh'
libdir='${prefix}/lib/x86_64-linux-gnu'
libexecdir='${prefix}/lib/x86_64-linux-gnu'
localedir='${datarootdir}/locale'
localstatedir='/var'
lowleveldocdir=''
mandir='${prefix}/share/man'
mkdir_p='$(MKDIR_P)'
moduledir=''
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
runstatedir='/run'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''
tutorialsdocdir=''
utilsdocdir=''

## --- ##
## confdefs.h. ##
## --- ##

/* confdefs.h */
#define PACKAGE_NAME "ETSF - IO library"
#define PACKAGE_TARNAME "etsf_io"
#define PACKAGE_VERSION "1.0.4"
#define PACKAGE_STRING "ETSF - IO library 1.0.4"
#define PACKAGE_BUGREPORT "https://bugs.launchpad.net/etsf-io";
#define PACKAGE_URL ""
#define PACKAGE "etsf_io"
#define VERSION "1.0.4"
#define FC_GCC 1
#define HAVE_FC_EXIT 1
#define HAVE_FC_FLUSH 1

configure: exit 1
dh_auto_configure: ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking 
--docdir=\${prefix}/share/doc/libetsf-io-doc --with-moduledir=\${includedir} 
"FCFLAGS=-O2 -fPIC" returned exit code 1
make[1]: *** [debian/rules:9: override_dh_auto_configure] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:6: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2
--- End Message ---
--- Begin Message ---
Whatever caused this problem, it has disappeared:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/etsf-io.html

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--- End Message ---

Bug#888556: Acknowledgement (libetsf-io-doc: fails to upgrade from 'testing' - trying to overwrite /usr/share/doc/libetsf-io-dev/AUTHORS)

[Adrian Bunk]

On Fri, Feb 02, 2018 at 12:28:09AM +0100, Andreas Beckmann wrote:
> This is probably fixed in latest debhelper, #888294

No, doesn't seem so.

$ debdiff libetsf-io-doc_1.0.4-1.1_all.deb libetsf-io-doc_1.0.4-2_all.deb 
...
Files in second .deb but not in first
-
-rw-r--r--  root/root   /usr/share/doc/libetsf-io-dev/AUTHORS
-rw-r--r--  root/root   /usr/share/doc/libetsf-io-dev/README
-rw-r--r--  root/root   /usr/share/doc/libetsf-io-dev/TODO

Files in first .deb but not in second
-
-rw-r--r--  root/root   /usr/share/doc/libetsf-io-doc/AUTHORS
-rw-r--r--  root/root   /usr/share/doc/libetsf-io-doc/README
-rw-r--r--  root/root   /usr/share/doc/libetsf-io-doc/TODO
...


This looks related to the dh_installdocs changes in compat 11.


> 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#897807: marked as done (mclibs: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Sun, 5 Aug 2018 21:06:13 +0300
with message-id <20180805180613.GA30815@localhost>
and subject line Re: Bug#897807: mclibs: ftbfs with GCC-8
has caused the Debian Bug report #897807,
regarding mclibs: 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.)


-- 
897807: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897807
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mclibs
Version: 20061220+dfsg3-3.1
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/mclibs_20061220+dfsg3-3.1_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

[...]
#0  0x7f41439101ed in ???
#1  0x7f414390f433 in ???
#2  0x7f414272eeff in ???
#3  0x7f414285375d in ???
#4  0x7f414277fe8d in ???
#5  0x7f414390f998 in ???
#6  0x7f4143afdc35 in ???
#7  0x7f4143b0d1e7 in ???
#8  0x41b12c in ???
#9  0x41abea in ???
#10  0x4019b9 in euexam
at 
/<>/mclibs-20061220+dfsg3/src/mclibs/eurodec/eudtest/main.F:15
#11  0x40182e in main
at 
/<>/mclibs-20061220+dfsg3/src/mclibs/eurodec/eudtest/main.F:30
Segmentation fault
Test result = 139
make[4]: *** [Makefile:485: test] Error 139
make[4]: Leaving directory 
'/<>/mclibs-20061220+dfsg3/build/mclibs/eurodec/eudtest'
make[3]: *** [Makefile:649: test] Error 2
make[3]: Leaving directory 
'/<>/mclibs-20061220+dfsg3/build/mclibs/eurodec'
make[2]: *** [Makefile:455: test] Error 2
make[2]: Leaving directory '/<>/mclibs-20061220+dfsg3/build/mclibs'
make[2]: Entering directory '/<>/mclibs-20061220+dfsg3/build/phtools'
making Makefiles in /phtools/wicoexam...
testing in /phtools/wicoexam...
make[3]: Entering directory 
'/<>/mclibs-20061220+dfsg3/build/phtools/wicoexam'
gfortran wicoex.F
rm -f wicot
Linking with cern libraries
-L/<>/mclibs-20061220+dfsg3/shlib 
-L/<>/mclibs-20061220+dfsg3/lib -lphtools -lmathlib -lpacklib 
-lkernlib -llapack -lm -lnsl -lcrypt -ldl -lgfortran
gfortran -g -o wicot -O3 -D_FORTIFY_SOURCE=2 -fno-range-check -fno-automatic 
-fno-second-underscore -fstack-protector --param=ssp-buffer-size=4  
-Wl,-z,relro   -L/<>/mclibs-20061220+dfsg3/src/lib wicoex.o  
`cernlib -dy packlib phtools`  \
 || rm -f wicot
/usr/bin/x86_64-linux-gnu-ld: warning: libgfortran.so.4, needed by 
/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/libmathlib.so, may 
conflict with libgfortran.so.5
/usr/bin/x86_64-linux-gnu-ld: warning: libgfortran.so.4, needed by 
/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/libmathlib.so, may 
conflict with libgfortran.so.5
Testing phtools
  ... using wicot
  Winston Cone LENGTH =   19.165445973633908 
  photon transmitted - IERR=0
  output coordinate -0.15073983363882368   0.31095801896913977 
  output direction  0.15002616295945720  -0.96634440051597126  
-0.20897523781321703 
  total path length   19.626024629316667 
  total number of bounces   2
Test result = 0
make[3]: Leaving directory 
'/<>/mclibs-20061220+dfsg3/build/phtools/wicoexam'
make[2]: Leaving directory '/<>/mclibs-20061220+dfsg3/build/phtools'
*** Failed test suite!!! ***
make[1]: *** [/usr/share/cernlib/cernlib.mk:197: stampdir/cernlib-test-pass] 
Error 1
make[1]: Leaving directory '/<>/mclibs-20061220+dfsg3'
make: *** [/usr/share/cernlib/cernlib-debian.mk:122: build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2
--- End Message ---
--- Begin Message ---
On Fri, May 04, 2018 at 12:22:38PM +, Matthias Klose wrote:
>...
> #0  0x7f41439101ed in ???
> #1  0x7f414390f433 in ???
> #2  0x7f414272eeff

Bug#905522: ghdl: Incomplete debian/copyright?

[Andreas Bombe]

On Sun, Aug 05, 2018 at 03:58:00PM +0100, Chris Lamb wrote:
> Source: ghdl
> Version: 0.35+git20180503+dfsg-1
> Severity: serious
> Justication: Policy 12.5
> X-Debbugs-CC: Andreas Bombe , ftpmas...@debian.org, Thorsten 
> Alteholz 
> 
> Hi,
> 
> I just ACCEPTed ghdl from NEW but the FTP team noticed it was missing the
> entire text of the CC license.

First, thanks for the ACCEPT.

The missing text of the CC license was the reason the package was
rejected months ago. I included the full text in debian/copyright, among
many other changes that came with using a more recent upstream which
changes the library organization. Is there really still something
missing (and what) or is this maybe some outdated ftpmaster notes for
ghdl sticking around?

Bug#896305: marked as done (python-laditools: laditools fails to import)

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 16:49:59 +
with message-id 
and subject line Bug#896305: fixed in laditools 1.1.0-3.1
has caused the Debian Bug report #896305,
regarding python-laditools: laditools fails to import
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.)


-- 
896305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-laditools
Version: 1.1.0-2
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-laditools importing the module laditools
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/laditools/__init__.py", line 25, in 

from .config import LadiConfiguration
  File "/usr/lib/python2.7/dist-packages/laditools/config.py", line 22, in 

from xdg import BaseDirectory as basedir
ImportError: No module named xdg

The vast majority of import failures is attributed to missing dependencies.
Often times that manifests as an ImportError or ModuleNotFoundError.
Typically, dependencies should be inserted by dh-python via ${python:Depends}
or ${python3:Depends}. Thus a missing dependency can be caused by incomplete
install_requires in setup.py. Sometimes a missing dependency of a dependency
is the cause, in such cases this bug should be reassigned.

Helmut
--- End Message ---
--- Begin Message ---
Source: laditools
Source-Version: 1.1.0-3.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated laditools package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 04 Aug 2018 22:02:00 +0300
Source: laditools
Binary: laditools python-laditools
Architecture: source
Version: 1.1.0-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Adrian Bunk 
Description:
 laditools  - Linux Audio Desktop Integration Tools
 python-laditools - Python module to control and monitor the LADI system
Closes: 896305
Changes:
 laditools (1.1.0-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Move the python-xdg dependency from laditools to python-laditools.
 (Closes: #896305)
Checksums-Sha1:
 1b96cf70bff70c7f44d0eab982d29a70974701d9 2124 laditools_1.1.0-3.1.dsc
 da58dd1c842407736d9229918d4f645809b5c8da 6076 laditools_1.1.0-3.1.debian.tar.xz
Checksums-Sha256:
 1e74dfc7ecf3ffcc39a1bac5188c2e7a72b4733c446d5857d8a0998c62fca8c0 2124 
laditools_1.1.0-3.1.dsc
 3db36441eee985413c6cc0f431e492d118e6d9b016b7ed972228592882466f2f 6076 
laditools_1.1.0-3.1.debian.tar.xz
Files:
 5a96b34c43b391062e4192c6457fbe95 2124 sound optional laditools_1.1.0-3.1.dsc
 add744053d1c4a9d95c7ee6d08050e99 6076 sound optional 
laditools_1.1.0-3.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAltl+NwACgkQiNJCh6LY
mLGV6A//eEsFDU3TXlNoBDxT+VJMq81vYpXf2su0AL9XCVc4nDZ0N5+d6/V/ScJn
ANwytMIP+txkx6asHFKExroArW+zskk1MjX/4mVUBZiuahTfjk8P96SAiMayR0xf
ouonxpEeOoXYaGp/dfP4gHAFPJVieoaqXdrfo9Rd9LnJZtZz0J2S4rgY3qbHzpGN
JvM6fgq1RHM0MGrEqV5+PsaXPwNZXiF3xB2/nxgGie9B+Xv1WO75YKcgP9IWmusn
nzlzMkh41w/AnVcV0KypnrL6TONu13JaZCnx8xnRpyuWDSOcwZCi5nLOS+gzQJ8N
kLfjwUhR/aA45MI52rSQXzexm9Z4QEXcA+O5r/jRRZ0Nh9emOZOFzO4KfhuUFywk
Hx+Es7cCpMRSaHjFodMFGAS89vB4ORyNPN+yYlg+GPUC8xehPI+0PloP3fHrK1hP
unxcAov1mMRqVStMojo6E9LC6Q9z/mF2pM4W1lnIOF04Hj9qIxNTDpTvpaNa7ffG
cyWO9alpqPRkymsAVtY2VDl2g8xHk2vLSA3019+m0DTsdjSemAeUH1o/adFM500R
JMIO4gzaUJCxSocAWyYZLoOcqrKaIf9zITMg+qLXCo/saMqC25lKe8CNsjnv2X75
/rhvQw9uz3K9S6bgZB6G3GeqiAzU3b4GXvVUjt2IQfqxw5Jfq0o=
=0RYF
-END PGP SIGNATURE End Message ---

Processed: Fixed in upstream 1.2.5

[Debian Bug Tracking System]

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

> tags 903527 fixed-upstream
Bug #903527 [python3-motor] python3-motor fails to install with Python 3.7 as 
suported version
Added tag(s) fixed-upstream.
> forwarded 903527 
> https://github.com/mongodb/motor/commit/aced74e749bd22efdeef891e1f345ec1923403ae
Bug #903527 [python3-motor] python3-motor fails to install with Python 3.7 as 
suported version
Set Bug forwarded-to-address to 
'https://github.com/mongodb/motor/commit/aced74e749bd22efdeef891e1f345ec1923403ae'.
> thanks
Stopping processing here.

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

Bug#897767: closed by Mo Zhou (Bug#897767: fixed in highwayhash 0~20180209-g14dedec-5)

[Adrian Bunk]

Control: reopen -1

On Mon, Jul 23, 2018 at 01:54:03AM +, Debian Bug Tracking System wrote:
>...
>  highwayhash (0~20180209-g14dedec-5) unstable; urgency=medium
>  .
>* Refresh symbols to avoid FTBFS with GCC-8 (Closes: #897767)
>...

unfortunately this fixed it only for amd64, the package still FTBFS
on arm64/ppc64el/x32:
https://buildd.debian.org/status/package.php?p=highwayhash

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#897767 closed by Mo Zhou (Bug#897767: fixed in highwayhash 0~20180209-g14dedec-5)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #897767 {Done: Mo Zhou } [src:highwayhash] 
highwayhash: ftbfs with GCC-8
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions highwayhash/0~20180209-g14dedec-5.

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

Bug#903330: glogg: diff for NMU version 1.1.4-1.1

[Adrian Bunk]

Control: tags 903330 + patch
Control: tags 903330 + pending

Dear maintainer,

I've prepared an NMU for glogg (versioned as 1.1.4-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 glogg-1.1.4/debian/changelog glogg-1.1.4/debian/changelog
--- glogg-1.1.4/debian/changelog	2017-08-11 21:24:53.0 +0300
+++ glogg-1.1.4/debian/changelog	2018-08-05 19:33:01.0 +0300
@@ -1,3 +1,11 @@
+glogg (1.1.4-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/docs: Adjust for upstream README -> README.md rename.
+(Closes: #903330)
+
+ -- Adrian Bunk   Sun, 05 Aug 2018 19:33:01 +0300
+
 glogg (1.1.4-1) unstable; urgency=medium
 
   * New upstream version 1.1.4 (closes: #853422)
diff -Nru glogg-1.1.4/debian/docs glogg-1.1.4/debian/docs
--- glogg-1.1.4/debian/docs	2017-08-11 21:24:53.0 +0300
+++ glogg-1.1.4/debian/docs	2018-08-05 19:32:55.0 +0300
@@ -1,3 +1,3 @@
-README
+README.md
 TODO
 doc/*.html

Processed: glogg: diff for NMU version 1.1.4-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 903330 + patch
Bug #903330 [src:glogg] glogg: FTBFS in buster/sid (dh_installdocs: Cannot find 
"README")
Added tag(s) patch.
> tags 903330 + pending
Bug #903330 [src:glogg] glogg: FTBFS in buster/sid (dh_installdocs: Cannot find 
"README")
Added tag(s) pending.

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

Bug#905486: marked as done (patch FTBFS: uses automake-1.15, which is no longer available)

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 16:19:38 +
with message-id 
and subject line Bug#905486: fixed in patch 2.7.6-3
has caused the Debian Bug report #905486,
regarding patch FTBFS: uses automake-1.15, which 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.)


-- 
905486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: patch
Version: 2.7.6-2
Severity: serious
Tags: ftbfs patch

patch fails to build from source on amd64 in unstable. A build log ends
as follows:

| make[3]: Leaving directory '/<>/src'
| Making all in tests
| make[3]: Entering directory '/<>/tests'
|  cd .. && /bin/bash /<>/build-aux/missing automake-1.15 --gnu 
tests/Makefile
| /<>/build-aux/missing: line 81: automake-1.15: command not found
| WARNING: 'automake-1.15' is missing on your system.
|  You should only need it if you modified 'Makefile.am' or
|  'configure.ac' or m4 files included by 'configure.ac'.
|  The 'automake' program is part of the GNU Automake package:
|  
|  It also requires GNU Autoconf, GNU m4 and Perl in order to run:
|  
|  
|  
| make[3]: *** [Makefile:1361: Makefile.in] Error 127
| make[3]: Leaving directory '/<>/tests'
| make[2]: *** [Makefile:1325: all-recursive] Error 1
| make[2]: Leaving directory '/<>'
| make[1]: *** [Makefile:1225: all] Error 2
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:38: build-stamp] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

It seems that patch requires automake-1.15, but does not list it in
Build-Depends. Actually automake-1.15 is replaced by automake-1.16 now,
so there is no way to use that version in Debian anymore. Autoreconfing
fixes the issue though.

Helmut
diff --minimal -Nru patch-2.7.6/debian/changelog patch-2.7.6/debian/changelog
--- patch-2.7.6/debian/changelog2018-04-06 17:20:36.0 +0200
+++ patch-2.7.6/debian/changelog2018-08-05 11:53:06.0 +0200
@@ -1,3 +1,10 @@
+patch (2.7.6-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS: dh_autoreconf (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 05 Aug 2018 11:53:06 +0200
+
 patch (2.7.6-2) unstable; urgency=high
 
   * Backport patches from upstream Git tree:
diff --minimal -Nru patch-2.7.6/debian/control patch-2.7.6/debian/control
--- patch-2.7.6/debian/control  2018-04-06 17:20:36.0 +0200
+++ patch-2.7.6/debian/control  2018-08-05 11:53:06.0 +0200
@@ -2,7 +2,7 @@
 Section: vcs
 Priority: standard
 Maintainer: Laszlo Boszormenyi (GCS) 
-Build-Depends: debhelper (>= 11), ed
+Build-Depends: debhelper (>= 11), ed, dh-autoreconf
 Standards-Version: 4.1.3
 Homepage: http://savannah.gnu.org/projects/patch/
 #Vcs-Git: git://git.debian.org/collab-maint/patch.git
diff --minimal -Nru patch-2.7.6/debian/rules patch-2.7.6/debian/rules
--- patch-2.7.6/debian/rules2014-08-10 20:07:30.0 +0200
+++ patch-2.7.6/debian/rules2018-08-05 11:53:05.0 +0200
@@ -26,6 +26,7 @@
 configure: configure-stamp
 configure-stamp:
dh_testdir
+   dh_autoreconf
CFLAGS="$(CFLAGS)" ac_cv_sys_long_file_names=yes ac_cv_path_ED=ed \
./configure $(CONFFLAGS) --prefix=/usr 
--mandir=\$${prefix}/share/man
touch configure-stamp
@@ -45,6 +46,7 @@
dh_testdir
[ ! -f Makefile ] || $(MAKE) distclean
dh_clean build-stamp configure-stamp .version
+   dh_autoreconf_clean
 
 install: build
dh_testdir
--- End Message ---
--- Begin Message ---
Source: patch
Source-Version: 2.7.6-3

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

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

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated patch 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: Sun, 05 Aug 

Bug#897797: marked as done (libsmithwaterman: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 16:04:58 +
with message-id 
and subject line Bug#897797: fixed in libsmithwaterman 0.0+git20160702.2610e25-5
has caused the Debian Bug report #897797,
regarding libsmithwaterman: 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.)


-- 
897797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libsmithwaterman
Version: 0.0+git20160702.2610e25-3
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/libsmithwaterman_0.0+git20160702.2610e25-3_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

[...]
   dh_installdocs -a -O--no-parallel
   dh_installchangelogs -a -O--no-parallel
   dh_installman -a -O--no-parallel
   dh_perl -a -O--no-parallel
   dh_link -a -O--no-parallel
   dh_strip_nondeterminism -a -O--no-parallel
   dh_compress -a -O--no-parallel
   dh_fixperms -a -O--no-parallel
   dh_missing -a -O--no-parallel
   dh_strip -a -O--no-parallel
   dh_makeshlibs -a -O--no-parallel
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libsmithwaterman0/DEBIAN/symbols doesn't match 
completely debian/libsmithwaterman0.symbols
--- debian/libsmithwaterman0.symbols 
(libsmithwaterman0_0.0+git20160702.2610e25-3_amd64)
+++ dpkg-gensymbolsZYza9J   2018-05-02 13:29:00.735154786 +
@@ -50,7 +50,7 @@
  (arch=!mips !mipsel)_ZNKSt5ctypeIcE8do_widenEc@Base 0.0+git20160702.2610e25
  _ZNSt6vectorI11IndelAlleleSaIS0_EE12emplace_backIJS0_EEEvDpOT_@Base 
0.0+git20160702.2610e25
  
_ZNSt6vectorI11IndelAlleleSaIS0_EE17_M_realloc_insertIJRKS0_EEEvN9__gnu_cxx17__normal_iteratorIPS0_S2_EEDpOT_@Base
 0.0+git20160702.2610e25
- 
_ZNSt6vectorI11IndelAlleleSaIS0_EE17_M_realloc_insertIJS0_EEEvN9__gnu_cxx17__normal_iteratorIPS0_S2_EEDpOT_@Base
 0.0+git20160702.2610e25
+#MISSING: 0.0+git20160702.2610e25-3# 
_ZNSt6vectorI11IndelAlleleSaIS0_EE17_M_realloc_insertIJS0_EEEvN9__gnu_cxx17__normal_iteratorIPS0_S2_EEDpOT_@Base
 0.0+git20160702.2610e25
  _ZNSt6vectorI11IndelAlleleSaIS0_EED1Ev@Base 0.0+git20160702.2610e25
  _ZNSt6vectorI11IndelAlleleSaIS0_EED2Ev@Base 0.0+git20160702.2610e25
  
_ZNSt6vectorISt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiSt4lessIS6_ESaISt4pairIKS6_iEEESaISD_EE12emplace_backIJSD_EEEvDpOT_@Base
 0.0+git20160702.2610e25
@@ -59,16 +59,19 @@
  
_ZNSt6vectorISt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEiSt4lessIS6_ESaISt4pairIKS6_iEEESaISD_EED2Ev@Base
 0.0+git20160702.2610e25
  
_ZNSt6vectorISt4pairIiNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcSaIS7_EE12emplace_backIJS7_EEEvDpOT_@Base
 0.0+git20160702.2610e25
  
_ZNSt6vectorISt4pairIiNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcSaIS7_EE17_M_realloc_insertIJRKS7_EEEvN9__gnu_cxx17__normal_iteratorIPS7_S9_EEDpOT_@Base
 0.0+git20160702.2610e25
- 
_ZNSt6vectorISt4pairIiNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcSaIS7_EE17_M_realloc_insertIJS7_EEEvN9__gnu_cxx17__normal_iteratorIPS7_S9_EEDpOT_@Base
 0.0+git20160702.2610e25
+#MISSING: 0.0+git20160702.2610e25-3# 
_ZNSt6vectorISt4pairIiNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcSaIS7_EE17_M_realloc_insertIJS7_EEEvN9__gnu_cxx17__normal_iteratorIPS7_S9_EEDpOT_@Base
 0.0+git20160702.2610e25
  
_ZNSt6vectorISt4pairIiNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcSaIS7_EED1Ev@Base
 0.0+git20160702.2610e25
  
_ZNSt6vecto

Bug#905522: ghdl: Incomplete debian/copyright?

[Chris Lamb]

Source: ghdl
Version: 0.35+git20180503+dfsg-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Andreas Bombe , ftpmas...@debian.org, Thorsten 
Alteholz 

Hi,

I just ACCEPTed ghdl from NEW but the FTP team noticed it was missing the
entire text of the CC license.


Regards,

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

Bug#868409: verbiste: Please drop the (build-)dependency against gnome-vfs

[Nicholas D Steeves]

Hi Tomasz,

On Thu, Aug 02, 2018 at 11:42:17PM +0800, Tomasz Buchert wrote:
> On 27/07/18 13:04, Nicholas D Steeves wrote:
> > [...]
> 
> Hey all,
> sorry for extremely long lag in fixing this...
> 
> Anyway, I went with Nicholas' suggestion and added verbiste-gtk,
> whereas verbiste-gnome is now transitional. Feel free to review it:
> https://salsa.debian.org/debian/verbiste

Strictly speaking, that's Andreas' suggestion ;-)

> As for verbiste-el, I've created https://bugs.debian.org/905290. I'd
> actually ask for help with this, I'm pretty bad at emacs
> packaging. Pull requests are welcome! :D

I started work on this and will follow up at the new bug.

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#905482: marked as done (fwupd-amd64-signed-template: invalid Depends (syntax error))

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 14:40:36 +
with message-id 
and subject line Bug#905482: fixed in fwupd 1.1.0-7
has caused the Debian Bug report #905482,
regarding fwupd-amd64-signed-template: invalid Depends (syntax error)
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.)


-- 
905482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fwupd-amd64-signed-template
Version: 1.1.0-6
Severity: serious

There is still one syntax error in the `Depends` field of the source
package template (the `}`):

Depends: ..., fwupd (= 1.1.0-6})
 ^^^

This resulted in a build failure for fwupd-amd64-signed[1].

Ansgar

  [1] 
https://buildd.debian.org/status/fetch.php?pkg=fwupd-amd64-signed&arch=amd64&ver=1.1.0%2B6&stamp=1533456833&raw=0
--- End Message ---
--- Begin Message ---
Source: fwupd
Source-Version: 1.1.0-7

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

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

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

Debian distribution maintenance software
pp.
Mario Limonciello  (supplier of updated fwupd 
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: Sun, 05 Aug 2018 08:34:37 -0500
Source: fwupd
Binary: libfwupd2 fwupd fwupd-tests fwupd-doc libfwupd-dev gir1.2-fwupd-2.0 
fwupd-amd64-signed-template fwupd-i386-signed-template 
fwupd-armhf-signed-template fwupd-arm64-signed-template
Architecture: source amd64 all
Version: 1.1.0-7
Distribution: unstable
Urgency: medium
Maintainer: Debian EFI 
Changed-By: Mario Limonciello 
Description:
 fwupd  - Firmware update daemon
 fwupd-amd64-signed-template - Template for signed fwupd package
 fwupd-arm64-signed-template - Template for signed fwupd package
 fwupd-armhf-signed-template - Template for signed fwupd package
 fwupd-doc  - Firmware update daemon documentation (HTML format)
 fwupd-i386-signed-template - Template for signed fwupd package
 fwupd-tests - Test suite for firmware update daemon
 gir1.2-fwupd-2.0 - GObject introspection data for libfwupd
 libfwupd-dev - development files for libfwupd
 libfwupd2  - Firmware update daemon library
Closes: 905482
Changes:
 fwupd (1.1.0-7) unstable; urgency=medium
 .
   * Correct another syntax error in SB signing template (Closes: #905482)
Checksums-Sha1:
 57dd9e642699314df8b032590d97e7a0fe23f5a4 3590 fwupd_1.1.0-7.dsc
 ac7f174ea83a95d97219752154fd25d53bced729 17688 fwupd_1.1.0-7.debian.tar.xz
 da97af64e80ecbeb663aff9cec73e0cfd62b 13970 
fwupd-amd64-signed-template_1.1.0-7_amd64.deb
 442db9876a2ae5e5504611074c9a8568d65562e3 1999304 fwupd-dbgsym_1.1.0-7_amd64.deb
 5283cd7531f53ad2457e084ca507aff50b2c1756 63710 fwupd-doc_1.1.0-7_all.deb
 7b1ad9ece55834bc31ba93cfaa10fad2a5ce8418 9812 
fwupd-tests-dbgsym_1.1.0-7_amd64.deb
 45eeb98a92cf5656da8dbef138e81be6e17878a3 22124 fwupd-tests_1.1.0-7_amd64.deb
 7598bf637280307e5ec113bf5a2d3863059e3787 16800 fwupd_1.1.0-7_amd64.buildinfo
 9a70554a8dae0e2e58de34af235fc3bc14eb254e 1708860 fwupd_1.1.0-7_amd64.deb
 19740cf41c35a789ef6895adae1f580305bd59fc 17866 
gir1.2-fwupd-2.0_1.1.0-7_amd64.deb
 da90250c1fb24fddf5d6481fac97804fcfecefa0 30072 libfwupd-dev_1.1.0-7_amd64.deb
 714ee6e60e2c7c69bfac8fb7f9b1a5ff45c8b87d 114676 
libfwupd2-dbgsym_1.1.0-7_amd64.deb
 e5febae8e43172ec5f1cc21cb80064827ecd6737 56046 libfwupd2_1.1.0-7_amd64.deb
Checksums-Sha256:
 c292394058fa9ff9fe62d32b6d9d92f3f5180fd79072837aaf76159db259e397 3590 
fwupd_1.1.0-7.dsc
 089237100909a60b9a35da8e43b87ce6a05d44b44d7f8daf3e41d0386c05140d 17688 
fwupd_1.1.0-7.debian.tar.xz
 20229ba8ad958b11566f7689016cca2de40335b2b514f241364f53af061b162d 13970 
fwupd-amd64-signed-template_1.1.0-7_amd64.deb
 a26b8316ce0e2fd4bdb407a631ac62a69421c0de760714e2390a1ab6cf554f81 1999304 
fwupd-dbgsym_1.1.0-7_amd64.deb
 0919e559f386accb5d423f4ad7920646fb28beb0bc821874f3a59f156cfa2f6e 63710 
fwupd-doc_1.1.0-7_all.deb
 6e8d73bd305d05aa096b75d9f8ac9f6a9309d41a653e9f343d389b429b2777bc 9812 
fwupd-tests-dbgsym_1.1.0-7_amd64.deb
 778f9769df5d682296372045e3f39c6f993a7e8cdd8f7fb942781c8d087f8e03 22124 
fwupd-tests_1.1.0-7_

Processed: Re: libgit2 FTBFS on armhf internal compil,er error: Segmentation fault

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #904004 {Done: Ximin Luo } [libgit2] libgit2 FTBFS on 
armhf, ppc64el, mips64el randomly
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions libgit2/0.27.0+dfsg.1-0.9.

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

Bug#904004: libgit2 FTBFS on armhf internal compil,er error: Segmentation fault

[Ximin Luo]

Control: reopen -1 

The patch I just uploaded fixed the problem on my x86-64 box and plummer the 
ppc64el porterbox.

However the same test still segfaults on armhf even with gcc-8.

I'll try to get another stacktrace and notify upstream.

X

Ximin Luo:
> Control: forwarded -1 https://github.com/libgit2/libgit2/issues/4753
> 
> The segfault happens on all architectures and we were just unlucky that it 
> happened on the ones that we saw.
> 
> I've filed an upstream issue with a stack trace, will continue debugging 
> later.
> 
> X
> 
> Pirate Praveen:
>> On 18/07/18 6:39 PM, John Paul Adrian Glaubitz wrote:
>>> I don't think your last upload was a good idea as you apparently
>>> didn't test your change on all affected architectures. The testsuite
>>> still fails on mips64el and ppc64el.
>>
>> The previous upload was failing only on amrhf so thought fixing that
>> would be enough.
>>
>>> Please take advantage of the porterboxes we have in Debian [1] rather
>>> than just uploading a new version over and over again to test new
>>> changes.
>>
>> ok.
>>


-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#903341: marked as done (ruby-rubymail: FTBFS in buster/sid (dh_installdocs: Cannot find "README"))

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 13:49:24 +
with message-id 
and subject line Bug#903341: fixed in ruby-rubymail 1.1.3-2
has caused the Debian Bug report #903341,
regarding ruby-rubymail: FTBFS in buster/sid (dh_installdocs: Cannot find 
"README")
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.)


-- 
903341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ruby-rubymail
Version: 1.1.3-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 --buildsystem=ruby --with ruby
   dh_update_autotools_config -i -O--buildsystem=ruby
   dh_auto_configure -i -O--buildsystem=ruby
dh_ruby --configure
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build
dh_ruby --build
   dh_ruby --build
rake rdoc
Parsing sources...
  5% [ 1/19]  ChangeLog
 10% [ 2/19]  README.md

[... snipped ...]

test_transparency_absolute_05:  .: (0.000842)
test_transparency_absolute_06:  .: (0.002141)
test_transparency_message_01:   .: (0.001448)
test_transparency_message_02:   .: (0.001710)
test_transparency_message_03:   .: (0.001168)
test_transparency_message_04:   .: (0.000559)
test_transparency_message_05:   .: (0.000655)
test_transparency_message_06:   .: (0.001684)
test_transparency_nested_multipart: .: (0.001611)
test_transparency_rfc822:   .: (0.001081)
test_transparency_simple_mime:  .: (0.001027)
  TestTestBase: 
test_cleandir:  .: (0.000897)
test_file_contains: .: (0.000511)
test_name:  .: (0.000259)
test_ruby_program:  .: (0.000272)
test_scratch_dir:   .: (0.000263)
test_scratch_filename:  .: (0.000313)
test_string_as_file:.: (0.000787)
  TextRMailMBoxReader: 
test_mbox_chunksize:.: (0.012013)
test_mbox_odd:  .: (0.000415)
test_mbox_randomly: .: (0.086029)
test_mbox_s_new:.: (0.000324)
test_mbox_simple:   .: (0.000422)
  TextRMailParserPushbackReader: 
test_pushback:  .: (0.000352)

Finished in 0.727013135 seconds.
---
168 tests, 24214 assertions, 0 failures, 0 errors, 0 pendings, 0 omissions, 0 
notifications
100% passed
---
231.08 tests/s, 33306.14 assertions/s

┌──────────────────────────────────────────────────────────────────────────────┐
│ dh_ruby --install finished  
 │
└──────────────────────────────────────────────────────────────────────────────┘

# Remove script files from ruby-rubymail-doc
rm -rf /<>/debian/ruby-rubymail-doc/usr/lib
make[1]: Leaving directory '/<>'
   dh_install -i -O--buildsystem=ruby
   dh_installdocs -i -O--buildsystem=ruby
dh_installdocs: Cannot find (any matches for) "README" (tried in .)

debian/rules:6: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep subprocess 
returned exit status 2


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

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

[ Note: There has been a recent change in debhelper behaviour, the current
  beh

Processed: Bug #903341 in ruby-rubymail marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #903341 [src:ruby-rubymail] ruby-rubymail: FTBFS in buster/sid 
(dh_installdocs: Cannot find "README")
Added tag(s) pending.

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

Bug#903341: Bug #903341 in ruby-rubymail marked as pending

[Antonio Terceiro]

Control: tag -1 pending

Hello,

Bug #903341 in ruby-rubymail 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/ruby-team/ruby-rubymail/commit/1f0fd108d44adee93885046c7acfc71923aed3e1


debian/ruby-rubymail.docs: s/README/README.md/ (Closes: #903341)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/903341

Bug#904004: marked as done (libgit2 FTBFS on armhf, ppc64el, mips64el randomly)

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 13:34:08 +
with message-id 
and subject line Bug#904004: fixed in libgit2 0.27.0+dfsg.1-0.9
has caused the Debian Bug report #904004,
regarding libgit2 FTBFS on armhf, ppc64el, mips64el randomly
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.)


-- 
904004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: libgit2
version: 0.27.0+dfsg.1-0.7
severity: serious

On harris.debian.org (armhf porterbox) I got this error.

/home/praveen/libgit2-0.27.0+dfsg.1/tests/checkout/tree.c: In function
'test_che
ckout_tree__target_directory_from_bare':
/home/praveen/libgit2-0.27.0+dfsg.1/tests/checkout/tree.c:911:1:
internal compil
er error: Segmentation fault
 }
 ^
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.
The bug is not reproducible, so it is likely a hardware or OS problem.
make[4]: *** [tests/CMakeFiles/libgit2_clar.dir/build.make:860:
tests/CMakeFiles/libgit2_clar.dir/checkout/tree.c.o] Error 1
make[4]: Leaving directory
'/home/praveen/libgit2-0.27.0+dfsg.1/build-debian-release'


On buildd, the segfault was during tests

https://buildd.debian.org/status/fetch.php?pkg=libgit2&arch=armhf&ver=0.27.0%2Bdfsg.1-0.7&stamp=1531458851&raw=0





signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: libgit2
Source-Version: 0.27.0+dfsg.1-0.9

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

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

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

Debian distribution maintenance software
pp.
Ximin Luo  (supplier of updated libgit2 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: Sun, 05 Aug 2018 06:14:33 -0700
Source: libgit2
Binary: libgit2-dev libgit2-27
Architecture: source
Version: 0.27.0+dfsg.1-0.9
Distribution: unstable
Urgency: medium
Maintainer: Russell Sim 
Changed-By: Ximin Luo 
Description:
 libgit2-27 - low-level Git library
 libgit2-dev - low-level Git library (development files)
Closes: 904004
Changes:
 libgit2 (0.27.0+dfsg.1-0.9) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix random segfaults in threads::diff. (Closes: #904004)
   * Don't specifically use gcc-8 now that it's already the Debian default.
Checksums-Sha1:
 b797adfff20dce2fba7a2dec3d1501f3b71dfce5 1507 libgit2_0.27.0+dfsg.1-0.9.dsc
 fa67d8c65f5625be474addecc341087c6958304b 22604 
libgit2_0.27.0+dfsg.1-0.9.debian.tar.xz
 51b363c3292b23bb92b6a2c7b842a7e9dc0ed6e1 6409 
libgit2_0.27.0+dfsg.1-0.9_source.buildinfo
Checksums-Sha256:
 3942795b70c1dcdffdea3746d1efd0233659a9aeaf2fa9d08d5c319c267b2909 1507 
libgit2_0.27.0+dfsg.1-0.9.dsc
 4b71249476c413252092f566050b532d5857233ba4fd3c96ce92989f76c7855f 22604 
libgit2_0.27.0+dfsg.1-0.9.debian.tar.xz
 7bc2f29a6bf5c85c5f28168dd07c658e70d5d63cde5c581237391fbeaedb5786 6409 
libgit2_0.27.0+dfsg.1-0.9_source.buildinfo
Files:
 899c0997c9cac864324df86d996a451e 1507 libs optional 
libgit2_0.27.0+dfsg.1-0.9.dsc
 10ef77c7900c702e4a015d93233d36e9 22604 libs optional 
libgit2_0.27.0+dfsg.1-0.9.debian.tar.xz
 9ce0fe6eeea8a5821d9cedbb734fb271 6409 libs optional 
libgit2_0.27.0+dfsg.1-0.9_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQReYinNQ9GpZ9TYcRrrH8jaRfspMAUCW2b4gwAKCRDrH8jaRfsp
MMfNAP4hjeBDIvNQX/Z3K4b6sZNOtJsQz40M5yJ+iGOoTQv4sQD5AWHyyewIl7+p
xSLw3AlJVF6vXOZXUnLAeGucaqgMxw8=
=H72n
-END PGP SIGNATURE End Message ---

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

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 13:19:25 +
with message-id 
and subject line Bug#905372: fixed in network-manager 1.12.2-2
has caused the Debian Bug report #905372,
regarding network-manager-strongswan FTBFS: error: macro "G_UNAVAILABLE" passed 
3 arguments, but takes just 2
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.)


-- 
905372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905372
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: network-manager-strongswan
Version: 1.4.4-1
Severity: serious
Tags: ftbfs
User: helm...@debian.org
Usertags: rebootstrap

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

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

The reproducible people see a similar failure:

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

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

Helmut
--- End Message ---
--- Begin Message ---
Source: network-manager
Source-Version: 1.12.2-2

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

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

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated network-manager package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
ad

Processed: affects 905372

[Debian Bug Tracking System]

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

> affects 905372 src:network-manager-strongswan
Bug #905372 [libnm-dev] network-manager-strongswan FTBFS: error: macro 
"G_UNAVAILABLE" passed 3 arguments, but takes just 2
Added indication that 905372 affects src:network-manager-strongswan
> thanks
Stopping processing here.

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

Bug#899778: marked as done (nam: Invalid maintainer address pkg-netsim-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 13:04:23 +
with message-id 
and subject line Bug#899778: fixed in nam 1.15-5
has caused the Debian Bug report #899778,
regarding nam: Invalid maintainer address 
pkg-netsim-de...@lists.alioth.debian.org
to be marked as done.

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

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


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

Dear uploader of nam,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: nam
Source-Version: 1.15-5

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

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

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

Debian distribution maintenance software
pp.
Aron Xu  (supplier of updated nam 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: Sun, 05 Aug 2018 20:48:39 +0800
Source: nam
Binary: nam nam-examples nam-dbg
Architecture: source amd64 all
Version: 1.15-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Network Simulators Team 

Changed-By: Aron Xu 
Description:
 nam- Network Animator for network simulation
 nam-dbg- debug symboles of nam
 nam-examples - examples of nam
Closes: 899778
Changes:
 nam (1.15-5) unstable; urgency=medium
 .
   * Team upload.
   * Use tracker.d.o address (Closes: #899778)
Checksums-Sha1:
 927918c9e9cfaa75cdba2cc36dfde746ec17b79a 1772 nam_1.15-5.dsc
 7ea46e5b01d653cc7e75e7de2ee82ee377f0e474 9192 nam_1.15-5.debian.tar.xz
 f7f108373cf1299f812d7a7ee1ecd1bbea9abb1c 864684 nam-dbg_1.15-5_amd64.deb
 909ba190482c78a099be1e2e8eb7cbc69e8e0967 3390508 nam-examples_1.15-5_all.deb
 e010b92b514f8340617f3aa04cbf78240d7843fe 8299 nam_1.15-5_amd64.buildinfo
 0dc92267a694472fbb6a2c9acdbc4a19769c4b21 209308 nam_1.15-5_amd64.deb
Checksums-Sha256:
 f4f0e355291f55997dfd87458deab960458ca4dc6b0b656a1a506c57d938b985 1772 
nam_1.15-5.dsc
 01c7cca93f74139dcc4cfd3523a91f48b5867cf8ebeb80c6e4bdd6f8893f20eb 9192 
nam_1.15-5.debian.tar.xz
 44d5af042b2be461240c9c7e00c3e9ee495ac01a541fb694e757ff12554ce7e0 864684 
nam-dbg_1.15-5_amd64.deb
 4e72b2c2d2eda6391a47ad599afeeab5da54396b8b917d658f59ddbcbd1da6bb 3390508 
n

Processed: tagging 905472

[Debian Bug Tracking System]

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

> tags 905472 + sid buster
Bug #905472 [src:libtextwrap] libtextwrap FTBFS: cannot find -ltextwrap
Ignoring request to alter tags of bug #905472 to the same tags previously set
> thanks
Stopping processing here.

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

Bug#903698: sphinxbase: build appears broken for multiple python3 versions

[Andreas Beckmann]

Followup-For: Bug #903698
Control: tag -1 sid buster

Since this bug seems to require more than one supported python 3.x
version to show up, I'm tagging it sid+buster, because we have only
one python 3.x version in (old)stable.

Please fix the tags if I misunderstood something.


Andreas

Processed: Re: sphinxbase: build appears broken for multiple python3 versions

[Debian Bug Tracking System]

Processing control commands:

> tag -1 sid buster
Bug #903698 [dh-python] sphinxbase: build appears broken for multiple python3 
versions
Added tag(s) buster and sid.

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

Processed: reassign

[Debian Bug Tracking System]

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

> reassign 905372 libnm-dev 1.12.2-1
Bug #905372 [src:network-manager-strongswan] network-manager-strongswan FTBFS: 
error: macro "G_UNAVAILABLE" passed 3 arguments, but takes just 2
Bug reassigned from package 'src:network-manager-strongswan' to 'libnm-dev'.
No longer marked as found in versions network-manager-strongswan/1.4.4-1.
Ignoring request to alter fixed versions of bug #905372 to the same values 
previously set
Bug #905372 [libnm-dev] network-manager-strongswan FTBFS: error: macro 
"G_UNAVAILABLE" passed 3 arguments, but takes just 2
Marked as found in versions network-manager/1.12.2-1.
>
End of message, stopping processing here.

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

Bug#897884: marked as done (vzquota: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 12:04:53 +
with message-id 
and subject line Bug#897884: fixed in vzquota 3.1-4
has caused the Debian Bug report #897884,
regarding vzquota: 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.)


-- 
897884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897884
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:vzquota
Version: 3.1-3
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/vzquota_3.1-3_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

[...]
dpkg-buildpackage: info: source version 3.1-3
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Ola Lundqvist 
 dpkg-source --before-build vzquota-3.1
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean
   dh_auto_clean
make -j1 clean
make[1]: Entering directory '/<>'
make[2]: Entering directory '/<>/src'
rm -f common.o quota_io.o syscall.o main.o stat.o quotaon.o quotacheck.o 
common.o quota_io.o syscall.o quotacheck.o vzdqcheck.o common.o quota_io.o 
syscall.o vzdqdump.o common.o quota_io.o syscall.o vzdqload.o vzquota vzdqcheck 
vzdqdump vzdqload .depend core *.log
find . -regex '.*[~#].*' | xargs rm -f
make[2]: Leaving directory '/<>/src'
make[2]: Entering directory '/<>/man'
rm -f  vzdqdump.8 vzdqcheck.8 vzquota.8
make[2]: Leaving directory '/<>/man'
make[1]: Leaving directory '/<>'
   dh_clean
 debian/rules build-arch
dh build-arch
   dh_update_autotools_config -a
   dh_auto_configure -a
   dh_auto_build -a
make -j1
make[1]: Entering directory '/<>'
make[2]: Entering directory '/<>/src'
cc -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -pipe -I../include -std=gnu99 -g -O2 -Wall 
-Werror -Wformat -D_FILE_OFFSET_BITS=64 -D_LINUX_QUOTA_VERSION=6 
-D_LARGEFILE64_SOURCE -DVARDIR=\"/var/lib\"  common.c -o common.o
cc -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -pipe -I../include -std=gnu99 -g -O2 -Wall 
-Werror -Wformat -D_FILE_OFFSET_BITS=64 -D_LINUX_QUOTA_VERSION=6 
-D_LARGEFILE64_SOURCE -DVARDIR=\"/var/lib\"  quota_io.c -o quota_io.o
cc -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -pipe -I../include -std=gnu99 -g -O2 -Wall 
-Werror -Wformat -D_FILE_OFFSET_BITS=64 -D_LINUX_QUOTA_VERSION=6 
-D_LARGEFILE64_SOURCE -DVARDIR=\"/var/lib\"  syscall.c -o syscall.o
cc -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -pipe -I../include -std=gnu99 -g -O2 -Wall 
-Werror -Wformat -D_FILE_OFFSET_BITS=64 -D_LINUX_QUOTA_VERSION=6 
-D_LARGEFILE64_SOURCE -DVARDIR=\"/var/lib\"  main.c -o main.o
cc -c -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -pipe -I../include -std=gnu99 -g -O2 -Wall 
-Werror -Wformat -D_FILE_OFFSET_BITS=64 -D_LINUX_QUOTA_VERSION=6 
-D_LARGEFILE64_SOURCE -DVARDIR=\"/var/lib\"  stat.c -o stat.o
stat.c: In function 'print_ugid_status':
stat.c:199:13: error: passing argument 1 to restrict-qualified parameter 
aliases with argument 3 [-Werror=restrict]
 sprintf(status, "%s%sdirty", status, (strlen(status)) ? "," : "");
 ^~   ~~
stat.c:199:26: error: 'dirty' directive writing 5 bytes into a region of size 
between 0 and 256 [-Werror=format-overflow=]
 sprintf(status, "%s%sdirty", status, (strlen(status)) ? "," : "");
  ^
stat.c:199:5: note: 'sprintf

Bug#905492: linux-image-4.17.0-1-amd64: Hard drive powers off during boot

[Salvatore Bonaccorso]

Control: severity -1 important
Control: tags -1 + moreinfo

Hi Loreno,

On Sun, Aug 05, 2018 at 01:23:30PM +0200, Loreno Heer wrote:
> Package: src:linux
> Version: 4.17.8-1
> Severity: critical
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
> *** Reporter, please consider answering these questions, where appropriate ***
> 
>* What led up to the situation? Upgrade to new kernel 4.17 made system 
> unbootable.
>* What exactly did you do (or not do) that was effective (or
>  ineffective)? Upgrade to kernel 4.17
>* What was the outcome of this action? Hard drive powers off during boot 
> and makes the system unbootable
>* What outcome did you expect instead?

Can you check, does, does adding the kernel parameters

dm_mod.use_blk_mq=0 scsi_mod.use_blk_mq=0

help in your case?

Regards,
Salvatore

Processed: Re: Bug#905492: linux-image-4.17.0-1-amd64: Hard drive powers off during boot

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #905492 [src:linux] linux-image-4.17.0-1-amd64: Hard drive powers off 
during boot
Severity set to 'important' from 'critical'
> tags -1 + moreinfo
Bug #905492 [src:linux] linux-image-4.17.0-1-amd64: Hard drive powers off 
during boot
Added tag(s) moreinfo.

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

Bug#905486: patch FTBFS: uses automake-1.15, which is no longer available

[GCS]

Control: tags -1 +pending

Hi Helmut,

On Sun, Aug 5, 2018 at 12:03 PM Helmut Grohne  wrote:
> patch fails to build from source on amd64 in unstable. A build log ends
> as follows:
>
> | make[3]: Leaving directory '/<>/src'
> | Making all in tests
> | make[3]: Entering directory '/<>/tests'
> |  cd .. && /bin/bash /<>/build-aux/missing automake-1.15 --gnu 
> tests/Makefile
> | /<>/build-aux/missing: line 81: automake-1.15: command not 
> found
 Good catch, thanks! I plan to fix it a bit different way.

Cheers,
Laszlo/GCS

Processed: Re: Bug#905486: patch FTBFS: uses automake-1.15, which is no longer available

[Debian Bug Tracking System]

Processing control commands:

> tags -1 +pending
Bug #905486 [src:patch] patch FTBFS: uses automake-1.15, which is no longer 
available
Added tag(s) pending.

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

Bug#898535: closed by Chow Loong Jin (Bug#898535: fixed in tinyxml2 6.2.0+dfsg-2)

[Joachim Reichel]

On 03.08.2018 06:03, Debian Bug Tracking System wrote:
> Changes:
>  tinyxml2 (6.2.0+dfsg-2) unstable; urgency=medium
>  .
>* [7fdca1f] Rename package for abi break (Closes: #898535)

How do you plan to deal with the breakage that results from the renaming? Did
you already ask for binNMUs? I do not see a bug report that requests a
transition slot, nor any discussion on debian-release.

  Joachim

Bug#905492: video of boot

[Loreno Heer]

video of boot: https://we.tl/tEGWko3GTP

Bug#905492: linux-image-4.17.0-1-amd64: Hard drive powers off during boot

[Loreno Heer]

Package: src:linux
Version: 4.17.8-1
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

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

   * What led up to the situation? Upgrade to new kernel 4.17 made system 
unbootable.
   * What exactly did you do (or not do) that was effective (or
 ineffective)? Upgrade to kernel 4.17
   * What was the outcome of this action? Hard drive powers off during boot and 
makes the system unbootable
   * What outcome did you expect instead?

Using an older kernel 4.16 everything works as expected.

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


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: SAMSUNG ELECTRONICS CO., LTD.
product_name: N150/N210/N220 
product_version: Not Applicable
chassis_vendor: SAMSUNG ELECTRONICS CO., LTD.
chassis_version: N/A 
bios_vendor: Phoenix Technologies Ltd.
bios_version: 01KG.M073.20100329.JIP
board_vendor: SAMSUNG ELECTRONICS CO., LTD.
board_name: N150/N210/N220 
board_version: Not Applicable

** Network interface configuration:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx DMI Bridge [8086:a010]
Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a011] (prog-if 00 [VGA 
controller])
Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: i915
Kernel modules: i915

00:02.1 Display controller [0380]: Intel Corporation Atom Processor 
D4xx/D5xx/N4xx/N5xx Integrated Graphics Controller [8086:a012]
Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 

00:1b.0 Audio device [0403]: Intel Corporation NM10/ICH7 Family High Definition 
Audio Controller [8086:27d8] (rev 02)
Subsystem: Samsung Electronics Co Ltd Notebook N150P [144d:c072]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 
1 [8086:27d0] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.1 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 
2 [8086:27d2] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.2 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 
3 [8086:27d4] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: shpchp

00:1c.3 PCI bridge [0604]: Intel Corporation NM10/ICH7 Family PCI Express Port 
4 [8086:27d6] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport
Kernel modules: sh

Bug#897771: marked as done (ifhp: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 11:19:21 +
with message-id 
and subject line Bug#891556: fixed in ifhp 3.5.20-16
has caused the Debian Bug report #891556,
regarding ifhp: 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.)


-- 
891556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ifhp
Version: 3.5.20-15
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/ifhp_3.5.20-15_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

[...]
config.status: creating config.h
./config.status: 1: cd: can't cd to /sbuild-nonexistent
config.status: executing default-1 commands
config.status: creating po/POTFILES
config.status: creating po/Makefile
touch configure-stamp
dh_testdir
/usr/bin/make LDFLAGS=`dpkg-buildflags --get LDFLAGS`
make[1]: Entering directory '/<>'
rm -f ifhp.conf
sed \
-e "s,.CAT@,/bin/cat,g" \
-e "s,.FILTER_DIR@,/usr/lib/ifhp,g" \
-e "s,.A2PS@,/usr/bin/a2ps,g" \
-e "s,.GS@,/usr/bin/gs,g" \
-e "s,.GZIP@,/bin/gzip,g" \
-e "s,.FILEUTIL@,/usr/bin/file,g" \
-e "s,.PAGE_SIZE@,letter,g" \
-e "s,.FONT_DIR@,/usr/libexec/filters/fonts,g" \
-e "s,.DEVFD3@,/dev/fd/3,g" \
-e "s,.FOOMATIC@,1,g" \
-e "s,.FOOMATIC_RIP@,/usr/bin/foomatic-rip,g" \
./ifhp.conf.in >ifhp.conf
if [ "src" = po ] ; then \
for i in po/Makefile* ; do \
if [ -f "$i" ] ; then \
if grep '^mkinstalldirs.*=.*case' $i ; then \
echo "fixing broken $i which causes wrong path to mkinstalldirs 
to be used"; \
perl -spi -e 's:^mkinstalldirs\s*=\s*.*:mkinstalldirs = 
\$(SHELL) \$(MKINSTALLDIRS):' $i; \
fi \
fi \
done \
fi
if [ "src" != po -o "no" != "no" ] ; then \
cd src; /usr/bin/make localedir=/usr/share/locale \
DESTDIR= all ; \
fi
make[2]: Entering directory '/<>/src'
gcc -g -W -Wall -Werror -Wno-unused  -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wno-unused-parameter -Wno-implicit-fallthrough -g -W 
-Wall -Werror -Wno-unused  -DHAVE_CONFIG_H -I. -I.. -I.  
-DIFHP_CONF=\"/etc/ifhp.conf\" -DLOCALEDIR=\"/usr/share/locale\"   -c -o ifhp.o 
ifhp.c
ifhp.c: In function 'Find_sub_value':
ifhp.c:2803:3: error: 'strncpy' specified bound 128 equals destination size 
[-Werror=stringop-truncation]
   strncpy(copy,id+1,sizeof(copy));
   ^~~
cc1: all warnings being treated as errors
make[2]: *** [: ifhp.o] Error 1
make[2]: Leaving directory '/<>/src'
make[1]: *** [Makefile:52: src] Error 2
make[1]: Leaving directory '/<>'
make: *** [debian/rules:33: build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2
--- End Message ---
--- Begin Message ---
Source: ifhp
Source-Version: 3.5.20-16

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated ifhp package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact th

Bug#891556: marked as done (ifhp: FTBFS with GCC 8 - error: 'strncpy' specified bound 128 equals destination size)

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 11:19:21 +
with message-id 
and subject line Bug#891556: fixed in ifhp 3.5.20-16
has caused the Debian Bug report #891556,
regarding ifhp: FTBFS with GCC 8 - error: 'strncpy' specified bound 128 equals 
destination size
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.)


-- 
891556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891556
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ifhp
Version: 3.5.20-15
Severity: important
User: debian-...@lists.debian.org
Usertag: ftbfs-gcc-8

Hi,

I recently performed an (unofficial) archive rebuild with GCC 8 on
mips64el. The main purpose of the rebuild was to discover mips toolchain
regressions, however I noticed this error in the logs which might be
interesting to you:

> ifhp.c: In function 'Find_sub_value':
> ifhp.c:2803:3: error: 'strncpy' specified bound 128 equals destination size 
> [-Werror=stringop-truncation]
>strncpy(copy,id+1,sizeof(copy));
>^~~
> cc1: all warnings being treated as errors
> : recipe for target 'ifhp.o' failed
> make[2]: *** [ifhp.o] Error 1
> make[2]: Leaving directory '/<>/src'
> Makefile:51: recipe for target 'src' failed
> make[1]: *** [src] Error 2
> make[1]: Leaving directory '/<>'
> debian/rules:32: recipe for target 'build-stamp' failed
> make: *** [build-stamp] Error 2
> dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
> status 2

As you probably know, you need to be careful using strncpy.

Instead of:
 char out[SIZE];
 strncpy(out, in, SIZE);

You need to do:
 char out[SIZE]
 strncpy(out, in, SIZE - 1);
 out[SIZE - 1] = '\0';

See strcpy(3)

James





signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: ifhp
Source-Version: 3.5.20-16

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated ifhp 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: Sun, 05 Aug 2018 12:44:49 +0200
Source: ifhp
Binary: ifhp
Architecture: source
Version: 3.5.20-16
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Adam Borowski 
Description:
 ifhp   - Printer filter for HP LaserJet printers
Closes: 891556
Changes:
 ifhp (3.5.20-16) unstable; urgency=medium
 .
   * QA upload.
   * Fix FTBFS due to strncpy. Closes: #891556.
Checksums-Sha1:
 d05f72d2a892cef1312dc3f06e2c8a47028ea022 1771 ifhp_3.5.20-16.dsc
 70f2205de69b386f2f9ae447be3b9e3801c068b0 89536 ifhp_3.5.20-16.debian.tar.xz
 dc73874be5a5b5e57ac6e15f3bc6492a4ff31f65 6725 ifhp_3.5.20-16_source.buildinfo
Checksums-Sha256:
 16aa6072ef99d062db01b39418c44818cbcc7b50593ce1ed05cee98fd801 1771 
ifhp_3.5.20-16.dsc
 fe8309a2d990234b8e6b21ce67017105b84a84a984f3e1b7f73fde9d7c9aa8ae 89536 
ifhp_3.5.20-16.debian.tar.xz
 96a29416257b1607d0586838c27937559e27542b4eae5aca82d21dfe39a80af9 6725 
ifhp_3.5.20-16_source.buildinfo
Files:
 7bd999a9bf9ac43fd9b6751bba356a25 1771 net extra ifhp_3.5.20-16.dsc
 4d26d9d5d61b421301d5c465589e3751 89536 net extra ifhp_3.5.20-16.debian.tar.xz
 0b1ab18fc730b17443dbe3867f8f91e6 6725 net extra ifhp_3.5.20-16_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEkjZVexcMh/iCHArDweDZLphvfH4FAltm1aEUHGtpbG9ieXRl
QGFuZ2JhbmQucGwACgkQweDZLphvfH72OxAAum23djskMcRlzOZI8+yhyWeK6I0t
wbNGJ0arUuQQcZKWFypZFPpIccclpAWVbv8AJW7XIzY7sNy2Arqtauq0oYke76QW
59f7tz5jL0l6CdkYnXiKAuqQ49Ighs/yoT9beL3NI4Us880VD81wNnJQ4Vo6g9Wt
Jteib6cuP2suUIF00QN0Dy1XEbnwvBqaOqdROyNt6VmmRp3eBYLTP3CwcDwxpYN2
gkgMNYoim9+88caV1Eis/JXvrwagSJCoqv9VSE7Z3b0nT/zCfiaoX613GzP3KZdu
OU7GUBaCFQnSk/2wlmFU4rhNFJ6qvhreFw310omwzw217T0eq1L8e6gaGDIGrw1G
L0rsCzKNu0Vjari/MC0nDJXUQCe8r2/TZ0DMEhQduwh+0HovoB7mrRyRII5MS0ks
wvLVl/HYKzd9BBnfLiL1nZoxQlYBUcRaTTgRkqLNGjX3BtYXhEXSntiBhcGQ8Wgj
njS9JwqROqPestZNl0Gx3uTOjclyF3zFslMpEmc8YhlosCJV8VKp+HnxeRh785kr
xGVDbEN5ywc4N2/E6u7VeZKMByTBsrrcAL38UgEvim0oGk8AVQ7/HqYu/yWq9qAW
+ra/2sgDByNiKaLfJ3/xh/MpPd4eYFdOtiPbx4uhIUCAt4+RbjfY0ZYhYyTVczSX
GM1O1A2

Bug#904111: clamav-daemon causing deadlocks/blocking I/O

[Sebastian Andrzej Siewior]

On 2018-07-27 23:56:53 [+0200], To Marc Dequènes wrote:
> On 2018-07-25 22:03:46 [+0200], To Marc Dequènes wrote:
> > > I just tried loading Adam's configuration on another system to test the
> > > ScanOnAccess, copied a clamav test file in one of the protected directory
> > > and hit the problem. After that the whole machine becomes totally
> > > unresponsive in a few seconds.
> 
> bootet Stretch with 0.100.0+dfsg-0+deb9u2. Using the attached
> clamd.conf. I see
> |clamd (810): Using fanotify permission checks may lead to deadlock; tainting 
> kernel
> 
> in the kernel log. I can copy the test-files but I can't read them. I
> can delete them.  The system is still working. I have
>   linux-image-4.9.0-7-amd64 4.9.110-1
> installed and I have btrfs as rootfs on that box. What could I miss
> there in order to reproduce this?

I didn't manage to reproduce it yet. My plan was to to gather enough
informations to reproduce it and forward it upstream.
Is there anything wrong / different with my setup compared to your?
Maybe different filesystem or something like that (if everything else is
the same).

Sebastian

Bug#899561: marked as done (kcm-fcitx: Invalid maintainer address pkg-ime-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 11:04:04 +
with message-id 
and subject line Bug#899561: fixed in kcm-fcitx 0.5.5-2
has caused the Debian Bug report #899561,
regarding kcm-fcitx: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
to be marked as done.

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

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


-- 
899561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:kcm-fcitx
Version: 0.5.5-1
Severity: serious
User: ad...@alioth-lists.debian.net
Usertag: alioth-lists-maintainer

Dear uploader of kcm-fcitx,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: kcm-fcitx
Source-Version: 0.5.5-2

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang <073p...@gmail.com> (supplier of updated kcm-fcitx package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 03 Aug 2018 20:55:49 +0800
Source: kcm-fcitx
Binary: kde-config-fcitx
Architecture: source
Version: 0.5.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang <073p...@gmail.com>
Description:
 kde-config-fcitx - KDE configuration module for Fcitx
Closes: 899561
Changes:
 kcm-fcitx (0.5.5-2) unstable; urgency=medium
 .
   * Team upload.
   * debian/control:
 + Apply "wrap-and-sort -abst".
 + Set maintainer to debian-input-method mailing list (Closes: #899561).
 + Update YunQiang Su's email address and use the @debian.org one.
 + debian/control: Bump debhelper compat to v11.
 + Bump Standards-Version to 4.2.0 (no changes needed).
 + Update Vcs fields and use git repo under Salsa platform.
 + Update homepage field and use the repo on gitlab.com.
   * debian/rules: Modernize rules file and explicitly include architecture.mk.
Checksums-Sha1:
 869a790255eac490089db22e7005bf71d1070d38 2179 kcm-fcitx_0.5.5-2.dsc
 9aad637ae680737b707da97a206d0441f377a2d4 2812 kcm-fcitx_0.5.5-2.debian.tar.xz
 4b304e6ca1f76cb5ff1afb3ec915b6f990ab86df 6612 
kcm-fcitx_0.5.5-2_source.buildinfo
Checksums-Sha256:
 315cfb167a98cae88b4826a85a6eb2c84ab2d1628f889169f54cd13d8c7a9b63 2179 

Bug#905441: marked as done (hunspell-bg: make conflicts versioned to allow installation of transitional myspell-bg package)

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 10:21:08 +
with message-id 
and subject line Bug#905441: fixed in libreoffice-dictionaries 1:6.1.0~rc2-2
has caused the Debian Bug report #905441,
regarding hunspell-bg: make conflicts versioned to allow installation of 
transitional myspell-bg package
to be marked as done.

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

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


-- 
905441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hunspell-bg
Version: 1:6.0.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + myspell-bg

Hi,

during a test with piuparts I noticed your package prevents installation
of the transitional myspell-bg package (which in turn depends on
hunspell-bg) because of the unversioned conflict with it.

Please make the conflict versioned: 
  Conflicts: myspell-bg (<< 4.1-5)
or better switch to Breaks:
  Breaks: myspell-bg (<< 4.1-5)
to avoid a lintian warning on versioned Conflicts.
In case the old myspell-bg and the current hunspell-bg have file
conflicts, add a matching Replaces:
  Replaces: myspell-bg (<< 4.1-5)


cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: libreoffice-dictionaries
Source-Version: 1:6.1.0~rc2-2

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

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

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

Debian distribution maintenance software
pp.
Mattia Rizzolo  (supplier of updated 
libreoffice-dictionaries 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: Sun, 05 Aug 2018 11:52:14 +0200
Source: libreoffice-dictionaries
Binary: libreoffice-lightproof-pt-br myspell-hr myspell-pl hyphen-af 
hunspell-af mythes-ar hyphen-bg hunspell-bg mythes-bg hunspell-bn hunspell-bs 
hyphen-ca mythes-ca hyphen-cs hunspell-cs mythes-cs hyphen-da hunspell-da 
mythes-da hunspell-de-at-frami hunspell-de-ch-frami hunspell-de-de-frami 
hyphen-de hyphen-el hunspell-el hunspell-en-za mythes-en-us hyphen-en-gb 
hunspell-en-gb hyphen-es hunspell-es mythes-es hyphen-fr mythes-fr hunspell-gd 
hyphen-gl hunspell-gl mythes-gl hunspell-gu hunspell-gug mythes-gug hunspell-he 
hunspell-hi hyphen-hr hunspell-hr hyphen-hu hunspell-hu mythes-hu hyphen-id 
hunspell-id mythes-id hyphen-is hunspell-is mythes-is hyphen-it hunspell-it 
mythes-it hunspell-kmr hunspell-lo hyphen-lt hunspell-lt mythes-lv hunspell-ne 
mythes-ne hyphen-nl hyphen-no hunspell-no mythes-no hunspell-oc hunspell-pl 
hyphen-pt-br hunspell-pt-br hyphen-pt-pt hunspell-pt-pt mythes-pt-pt hyphen-ro 
hunspell-ro mythes-ro hunspell-ru mythes-ru hunspell-si hyphen-sk
 hunspell-sk mythes-sk hyphen-sl hunspell-sl mythes-sl hyphen-sr hunspell-sr 
hyphen-sv hunspell-sv mythes-sv hunspell-sw hunspell-te hunspell-th hyphen-uk 
hunspell-uk mythes-uk hunspell-vi
 hyphen-zu
Architecture: source
Version: 1:6.1.0~rc2-2
Distribution: unstable
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Mattia Rizzolo 
Description:
 hunspell-af - Afrikaans dictionary for hunspell
 hunspell-bg - Bulgarian dictionary for hunspell
 hunspell-bn - Bengali dictionary for hunspell
 hunspell-bs - Bosnian dictionary for hunspell
 hunspell-cs - Czech dictionary for hunspell
 hunspell-da - Danish dictionary for hunspell
 hunspell-de-at-frami - German (Austria) dictionary for hunspell ("frami" 
version)
 hunspell-de-ch-frami - German (Switzerland) dictionary for hunspell ("frami" 
version)
 hunspell-de-de-frami - German dictionary for hunspell ("frami" version)
 hunspell-el - Modern Greek dictionary for hunspell
 hunspell-en-gb - English (GB) dictionary for hunspell
 hunspell-en-za - English (South Africa) dictionary for hunspell
 hunspell-es - Spanish dictionary for hunspell
 hunspell-gd - Scottish Gaelic dictionary for hunspell
 hunspell-gl - Galician dictionary for hunspell
 hunspell-gu - Gujarati dictionary for hunspell
 hunspell-gug - Guarani dictionary for hunspell
 hunspell-he - Hebrew dictionary for hunspell
 hunspell-hi - Hindi dictionary for hunspell
 hunspell-hr - Croatian dictionary for hunspell
 h

Bug#706202: marked as done (ipvsadm: Syncid is not passed to the Daemon in the init Script)

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 10:04:20 +
with message-id 
and subject line Bug#649106: fixed in ipvsadm 1:1.29-1
has caused the Debian Bug report #649106,
regarding ipvsadm: Syncid is not passed to the Daemon in the init Script
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.)


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

Dear Maintainer,

i tried to use the SYNCID in /etc/default/ipvsadm.
This variable is not passed to the call ipvsadm --start-daemon
master/backup ... in the Init-Script (/etc/init.d/ipvsadm)

Sorry for the duplicate Report, but in the first Report, i used the
wrong email address :(

Best Regards
Ingo Rauschenberg


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

Kernel: Linux 3.2.0-4-amd64 (SMP w/32 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages ipvsadm depends on:
ii  debconf [debconf-2.0]  1.5.49
ii  libc6  2.13-38
ii  libnl1 1.1-7
ii  libpopt0   1.16-7
ii  lsb-base   4.1+Debian8

ipvsadm recommends no packages.

Versions of packages ipvsadm suggests:
pn  heartbeat   
pn  keepalived  
pn  ldirectord  

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Source: ipvsadm
Source-Version: 1:1.29-1

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

Debian distribution maintenance software
pp.
Alexander Wirt  (supplier of updated ipvsadm 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: Sun, 05 Aug 2018 09:21:46 +0200
Source: ipvsadm
Binary: ipvsadm
Architecture: source amd64
Version: 1:1.29-1
Distribution: unstable
Urgency: medium
Maintainer: Alexander Wirt 
Changed-By: Alexander Wirt 
Description:
 ipvsadm- Linux Virtual Server support programs
Closes: 649106 788345 808950 814348 903935
Changes:
 ipvsadm (1:1.29-1) unstable; urgency=medium
 .
   * [b30c9aa] New upstream version 1.29
 (Closes: #903935)
   * [f33b1cc] Bump standards version
   * [06cf313] Priority extra is now optional
   * [28cd1fe] Bump to dh11
   * [776e7b4] package doesn't build with parallel
   * [a3d3994] Add gitlab-ci file
   * [b82b9b0] Add snapshot changelog
   * [c1c00d7] Add homepage field
   * [4af29a6] Remove trailing whitespace
   * [8cdf09c] I found even more whitespace
   * [8f39cde] Verify gpg sig on upstream tarball
   * [0e9779f] use specific GPL version in copyright
   * [07d28a4] Remove obsolete lintian override
   * [6a7e974] We don't use dpatch anymore, kick README.source
   * [98911a8] Add override file - we don't have a changelog
   * [aa1dc89] Fix syncid on daemon invocation (Closes: #649106, #788345, 
#808950)
   * [7695a4a] Add a patch to enhance weight parameter to INT_MAX.
 Thanks to Francois Lallart  (Closes: #814348)
Checksums-Sha1:
 65190ed90f1accb1205f5d902f0623059e932028 1898 ipvsadm_1.29-1.dsc
 759017db7108c0392ab0ff2c102d3ef322ad93a8 46115 ipvsadm_1.29.orig.tar.gz
 a49e5071e42983a1d4078777bd7b0517cda30b01 14296 ipvsadm_1.29-1.debian.tar.xz
 3f5d15e1e97b6c91fb0dd9199b3253b5dbb132ba 26748 ipvsadm-dbgsym_1.29-1_amd64.deb
 e63a759b779d2902f57d48f1366eb47c96236b85 6021 ipvsadm_1.29-1_amd64.buildinfo
 35a388665aa203f0ffb3b089b213edf208450fab 39244 ipvsadm_1.29-1_amd64.deb
Checksums-Sha256:
 ff03bb214580c223fd9074d619a44c9c63aff3546411c5089d50525651d2a7f2 1898 
ipvsadm_1.29-1.dsc
 99ed8ce998b719de2f7b3a52ef28b38a4a016a5a05da772acfd75e64511a4c17 46115 
ipvsadm_1.29.orig.tar.gz
 bd398bcc4f906327204c676c942bc8d1e53b0d0ca461bcf237961f44cb904c70 14296 
ipvsadm_1.29-1.debian.tar.xz
 92e13f3329845b3aa6e28118ef5efcdd7e0f82f691ed4da9f06defe05a91f77f 26748 
ipvsadm-dbgsym_1.29-1_amd64.deb
 884369a65a335c95dc08c6cb7aa8b8671a2ff7afe99f108198b34fce5c5127f7 6021 
ipvsadm_1.29-1_amd64.buildinfo
 3cf067f441a16e353e17b93c51306b5ba01a195fdebbe

Bug#905486: patch FTBFS: uses automake-1.15, which is no longer available

[Helmut Grohne]

Source: patch
Version: 2.7.6-2
Severity: serious
Tags: ftbfs patch

patch fails to build from source on amd64 in unstable. A build log ends
as follows:

| make[3]: Leaving directory '/<>/src'
| Making all in tests
| make[3]: Entering directory '/<>/tests'
|  cd .. && /bin/bash /<>/build-aux/missing automake-1.15 --gnu 
tests/Makefile
| /<>/build-aux/missing: line 81: automake-1.15: command not found
| WARNING: 'automake-1.15' is missing on your system.
|  You should only need it if you modified 'Makefile.am' or
|  'configure.ac' or m4 files included by 'configure.ac'.
|  The 'automake' program is part of the GNU Automake package:
|  
|  It also requires GNU Autoconf, GNU m4 and Perl in order to run:
|  
|  
|  
| make[3]: *** [Makefile:1361: Makefile.in] Error 127
| make[3]: Leaving directory '/<>/tests'
| make[2]: *** [Makefile:1325: all-recursive] Error 1
| make[2]: Leaving directory '/<>'
| make[1]: *** [Makefile:1225: all] Error 2
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:38: build-stamp] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

It seems that patch requires automake-1.15, but does not list it in
Build-Depends. Actually automake-1.15 is replaced by automake-1.16 now,
so there is no way to use that version in Debian anymore. Autoreconfing
fixes the issue though.

Helmut
diff --minimal -Nru patch-2.7.6/debian/changelog patch-2.7.6/debian/changelog
--- patch-2.7.6/debian/changelog2018-04-06 17:20:36.0 +0200
+++ patch-2.7.6/debian/changelog2018-08-05 11:53:06.0 +0200
@@ -1,3 +1,10 @@
+patch (2.7.6-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS: dh_autoreconf (Closes: #-1)
+
+ -- Helmut Grohne   Sun, 05 Aug 2018 11:53:06 +0200
+
 patch (2.7.6-2) unstable; urgency=high
 
   * Backport patches from upstream Git tree:
diff --minimal -Nru patch-2.7.6/debian/control patch-2.7.6/debian/control
--- patch-2.7.6/debian/control  2018-04-06 17:20:36.0 +0200
+++ patch-2.7.6/debian/control  2018-08-05 11:53:06.0 +0200
@@ -2,7 +2,7 @@
 Section: vcs
 Priority: standard
 Maintainer: Laszlo Boszormenyi (GCS) 
-Build-Depends: debhelper (>= 11), ed
+Build-Depends: debhelper (>= 11), ed, dh-autoreconf
 Standards-Version: 4.1.3
 Homepage: http://savannah.gnu.org/projects/patch/
 #Vcs-Git: git://git.debian.org/collab-maint/patch.git
diff --minimal -Nru patch-2.7.6/debian/rules patch-2.7.6/debian/rules
--- patch-2.7.6/debian/rules2014-08-10 20:07:30.0 +0200
+++ patch-2.7.6/debian/rules2018-08-05 11:53:05.0 +0200
@@ -26,6 +26,7 @@
 configure: configure-stamp
 configure-stamp:
dh_testdir
+   dh_autoreconf
CFLAGS="$(CFLAGS)" ac_cv_sys_long_file_names=yes ac_cv_path_ED=ed \
./configure $(CONFFLAGS) --prefix=/usr 
--mandir=\$${prefix}/share/man
touch configure-stamp
@@ -45,6 +46,7 @@
dh_testdir
[ ! -f Makefile ] || $(MAKE) distclean
dh_clean build-stamp configure-stamp .version
+   dh_autoreconf_clean
 
 install: build
dh_testdir

Bug#649106: marked as done (Add syncid to ipvsadm configuration)

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 10:04:20 +
with message-id 
and subject line Bug#649106: fixed in ipvsadm 1:1.29-1
has caused the Debian Bug report #649106,
regarding Add syncid to ipvsadm configuration
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.)


-- 
649106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ipvsadm
Version: 1:1.25.clean-1

ipvsadm init script does not honor the syncid option when starting 
master/backup daemon. I thought about the following patches:

--- /root/ipvsadm   2011-11-17 17:23:08.0 +0100
+++ /etc/init.d/ipvsadm 2011-11-17 17:27:43.0 +0100
@@ -23,19 +23,20 @@
 DAEMON="none"  # none|master|backup|both
 IFACE="eth0"
 FAILURE=0
+SYNCID="1"
 
 start () {
 case $DAEMON in
master|backup)
log_daemon_msg "Starting IPVS Connection Synchronization Daemon" 
"$DAEMON"
-   $IPVSADM --start-daemon $DAEMON --mcast-interface $IFACE || 
log_end_msg 1
+   $IPVSADM --start-daemon $DAEMON --mcast-interface $IFACE --syncid 
$SYNCID || log_end_msg 1
log_end_msg 0
;;
both)
log_daemon_msg "Starting IPVS Connection Synchronization Daemon" 
"master"
-   $IPVSADM --start-daemon master --mcast-interface $IFACE || FAILURE=1
+   $IPVSADM --start-daemon master --mcast-interface $IFACE --syncid 
$SYNCID || FAILURE=1
log_progress_msg "backup"
-   $IPVSADM --start-daemon backup --mcast-interface $IFACE || FAILURE=1
+   $IPVSADM --start-daemon backup --mcast-interface $IFACE --syncid 
$SYNCID || FAILURE=1
if [ "$FAILURE" -eq 1 ]
then
log_end_msg 1


and add the following line to /etc/default/ipvsadm

SYNCID="1"

Greetings,

-- 
Dr. Michael Schwartzkopff
Guardinistr. 63
81375 München

Tel: (0163) 172 50 98
Fax: (089) 620 304 13


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: ipvsadm
Source-Version: 1:1.29-1

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

Debian distribution maintenance software
pp.
Alexander Wirt  (supplier of updated ipvsadm 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: Sun, 05 Aug 2018 09:21:46 +0200
Source: ipvsadm
Binary: ipvsadm
Architecture: source amd64
Version: 1:1.29-1
Distribution: unstable
Urgency: medium
Maintainer: Alexander Wirt 
Changed-By: Alexander Wirt 
Description:
 ipvsadm- Linux Virtual Server support programs
Closes: 649106 788345 808950 814348 903935
Changes:
 ipvsadm (1:1.29-1) unstable; urgency=medium
 .
   * [b30c9aa] New upstream version 1.29
 (Closes: #903935)
   * [f33b1cc] Bump standards version
   * [06cf313] Priority extra is now optional
   * [28cd1fe] Bump to dh11
   * [776e7b4] package doesn't build with parallel
   * [a3d3994] Add gitlab-ci file
   * [b82b9b0] Add snapshot changelog
   * [c1c00d7] Add homepage field
   * [4af29a6] Remove trailing whitespace
   * [8cdf09c] I found even more whitespace
   * [8f39cde] Verify gpg sig on upstream tarball
   * [0e9779f] use specific GPL version in copyright
   * [07d28a4] Remove obsolete lintian override
   * [6a7e974] We don't use dpatch anymore, kick README.source
   * [98911a8] Add override file - we don't have a changelog
   * [aa1dc89] Fix syncid on daemon invocation (Closes: #649106, #788345, 
#808950)
   * [7695a4a] Add a patch to enhance weight parameter to INT_MAX.
 Thanks to Francois Lallart  (Closes: #814348)
Checksums-Sha1:
 65190ed90f1accb1205f5d902f0623059e932028 1898 ipvsadm_1.29-1.dsc
 759017db7108c0392ab0ff2c102d3ef322ad93a8 46115 ipvsadm_1.29.orig.tar.gz
 a49e5071e42983a1d4078777bd7b0517cda30b01 14296 ipvsadm_1.29-1.debian.tar.xz
 3f5d15e1e97b6c91fb0dd9199b3253b5dbb132ba 26748 ipvsadm-dbgsym_1.29-1_amd64.deb
 e63a759b779d2902f57d48f1366eb47c96236b85 6021 ipvsadm_1.29-1_amd64.buildinfo
 35a388665aa203f0ffb3b089b213edf208450fab 39244 ipvsadm_1.29-1_amd64

Bug#905472: libtextwrap FTBFS: cannot find -ltextwrap

[Adrian Bunk]

On Sun, Aug 05, 2018 at 09:11:14AM +0200, Helmut Grohne wrote:
> Control: tags -1 + patch
> 
> On Sun, Aug 05, 2018 at 08:55:32AM +0200, Helmut Grohne wrote:
> > Scanning the recent upload history, automake-1.16 looks suspicious now.
> 
> Yes, it looks like a missing Makefile.am dependency. The attached patch
> makes it build.
> 
> Helmut

> --- libtextwrap-0.1.orig/Makefile.am
> +++ libtextwrap-0.1/Makefile.am
> @@ -9,3 +9,4 @@
>  bin_PROGRAMS = dotextwrap
>  dotextwrap_SOURCES = dotextwrap.c
>  dotextwrap_LDADD = -ltextwrap
> +EXTRA_dotextwrap_DEPENDENCIES = libtextwrap.la

That's then a race condition that also exists with older automake,
and the new automake just reshuffled the build order.

The correct fix is to fix the bug one line earlier 
with s/-ltextwrap/libtextwrap.la/

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: tagging 905472

[Debian Bug Tracking System]

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

> tags 905472 + buster sid
Bug #905472 [src:libtextwrap] libtextwrap FTBFS: cannot find -ltextwrap
Added tag(s) sid and buster.
> thanks
Stopping processing here.

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

Bug#905482: fwupd-amd64-signed-template: invalid Depends (syntax error)

[Ansgar Burchardt]

Package: fwupd-amd64-signed-template
Version: 1.1.0-6
Severity: serious

There is still one syntax error in the `Depends` field of the source
package template (the `}`):

Depends: ..., fwupd (= 1.1.0-6})
 ^^^

This resulted in a build failure for fwupd-amd64-signed[1].

Ansgar

  [1] 
https://buildd.debian.org/status/fetch.php?pkg=fwupd-amd64-signed&arch=amd64&ver=1.1.0%2B6&stamp=1533456833&raw=0

Processed: [r...@debian.org: UI regressions in "gen" plugin with LibreOffice 6.1]

[Debian Bug Tracking System]

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

> forwarded 904598 libreoff...@lists.freedesktop.org
Bug #904598 [libreoffice] libreoffice: Find/Replace dialogs' options are broken 
in gen vclplug
Set Bug forwarded-to-address to 'libreoff...@lists.freedesktop.org'.
> forwarded 905408 libreoff...@lists.freedesktop.org
Bug #905408 [src:libreoffice] libreoffice: missed radiobuttons and checkbox in 
forms with gen VCLplug
Set Bug forwarded-to-address to 'libreoff...@lists.freedesktop.org'.
> thanks
Stopping processing here.

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

Processed: affects 859831, user debian...@lists.debian.org, usertagging 859831, usertagging 902901 ...

[Debian Bug Tracking System]

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

> affects 859831 + libxmltooling-dev
Bug #859831 {Done: Ferenc Wágner } [xmltooling] xmltooling: 
Please migrate to openssl1.1 in Buster
Added indication that 859831 affects libxmltooling-dev
> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 859831 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 902901 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 902901 + libghc-polynomial-dev libghc-polynomial-prof
Bug #902901 [src:haskell-polynomial] FTBFS: Tests fail
Added indication that 902901 affects libghc-polynomial-dev and 
libghc-polynomial-prof
> usertags 892539 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 901455 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 901455 + libsbml5-octave
Bug #901455 [src:libsbml] FTBFS in sid: package com.sun.tools.doclets.standard 
is not visible
Added indication that 901455 affects libsbml5-octave
> affects 905443 + python-ballview
Bug #905443 [src:ball] ball: FTBFS - test failures
Added indication that 905443 affects python-ballview
> affects 873341 + libsbt-java
Bug #873341 [sbt] SBT is uninstallable; depends on nonexistent packages
Added indication that 873341 affects libsbt-java
> usertags 873341 piuparts
There were no usertags set.
Usertags are now: piuparts.
> found 866490 3.0.2-1.1
Bug #866490 [src:utopia-documents] utopia-documents: depends on obsolete 
python-imaging (replace with python3-pil or python-pil)
Marked as found in versions utopia-documents/3.0.2-1.1.
> usertags 902198 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 870306 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 876533 piuparts
There were no usertags set.
Usertags are now: piuparts.
> affects 877507 + libppx-optcomp-ocaml libppx-driver-ocaml 
> libppx-type-conv-ocaml libppx-sexp-conv-ocaml
Bug #877507 [src:ppx-core] ppx-core FTBFS: E: Cannot find external tool 
'ocamlbuild'
Added indication that 877507 affects libppx-optcomp-ocaml, libppx-driver-ocaml, 
libppx-type-conv-ocaml, and libppx-sexp-conv-ocaml
> usertags 877496 piuparts
Usertags were: piuparts.
Usertags are now: piuparts.
> affects 877496 + libsexplib-ocaml-dev
Bug #877496 [src:sexplib310] sexplib310 FTBFS: Error: This expression has type 
Obj.t but an expression was expected of type extension_constructor
Added indication that 877496 affects libsexplib-ocaml-dev
> usertags 881676 piuparts
Usertags were: piuparts.
Usertags are now: piuparts.
> affects 881676 + python3-elektra
Bug #881676 [src:elektra] elektra: FTBFS with current cmake: A duplicate ELSE 
command was found inside an IF block.
Ignoring request to set affects of bug 881676 to the same value previously set
> severity 904115 serious
Bug #904115 [python3-feather-format] python3-feather-format: Uninstallable in 
unstable
Severity set to 'serious' from 'important'
> usertags 904115 piuparts
There were no usertags set.
Usertags are now: piuparts.
> usertags 873501 piuparts
Usertags were: piuparts.
Usertags are now: piuparts.
> usertags 903580 piuparts
Usertags were: piuparts.
Usertags are now: piuparts.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
859831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859831
866490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866490
873341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873341
877496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877496
877507: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877507
881676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881676
901455: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901455
902901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902901
903580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903580
904115: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904115
905443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905443
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#905481: mediastreamer2: FTBFS with GCC-8

[Andreas Beckmann]

Source: mediastreamer2
Version: 1:2.16.1-2
Severity: serious
Justification: fails to build from source

Hi,

mediastreamer2 FTBFS since GCC-8 became the default compiler:

[ 38%] Building C object 
src/CMakeFiles/mediastreamer_voip-static.dir/voip/audiostream.c.o
cd /build/mediastreamer2-2.16.1/obj-x86_64-linux-gnu/src && /usr/bin/cc 
-DBCTBX_STATIC -DBZRTP_STATIC -DHAVE_CONFIG_H -DMS2_EXPORTS -DMS2_FILTERS 
-DMS2_INTERNAL -DMS2_STATIC -DORTP_STATIC -DVIDEO_ENABLED -D_TRUE_TIME 
-I/build/mediastreamer2-2.16.1/include 
-I/build/mediastreamer2-2.16.1/src/audiofilters 
-I/build/mediastreamer2-2.16.1/src/utils 
-I/build/mediastreamer2-2.16.1/src/voip 
-I/build/mediastreamer2-2.16.1/obj-x86_64-linux-gnu 
-I/build/mediastreamer2-2.16.1/obj-x86_64-linux-gnu/src -I/usr/include/libxml2 
-I/usr/include/x86_64-linux-gnu  -g -O2 
-fdebug-prefix-map=/build/mediastreamer2-2.16.1=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2-Wall 
-Wuninitialized -Wno-format-truncation -Werror -Wextra -Wno-unused-parameter 
-fno-strict-aliasing -Wno-missing-field-initializers 
-Wdeclaration-after-statement -Wstrict-prototypes -Wno-error=strict-prototypes 
-o CMakeFiles/mediastreamer_voip-static.dir/voip/audiostream.c.o   -c 
/build/mediastreamer2-2.16.1/src/voip/audiostream.c
/build/mediastreamer2-2.16.1/src/voip/audiostream.c: In function 
'audio_stream_start_from_io':
/build/mediastreamer2-2.16.1/src/voip/audiostream.c:816:52: error: cast between 
incompatible function types from 'void (*)(RtpSession *, uint32_t,  void *)' 
{aka 'void (*)(struct _RtpSession *, unsigned int,  void *)'} to 'void 
(*)(struct _RtpSession *, void *, void *, void *)' [-Werror=cast-function-type]
  
rtp_session_signal_connect(rtps,"telephone-event",(RtpCallback)on_dtmf_received,stream);
^
/build/mediastreamer2-2.16.1/src/voip/audiostream.c:817:57: error: cast between 
incompatible function types from 'bool_t (*)(RtpSession *, void *)' {aka 
'unsigned char (*)(struct _RtpSession *, void *)'} to 'void (*)(struct 
_RtpSession *, void *, void *, void *)' [-Werror=cast-function-type]
  
rtp_session_signal_connect(rtps,"payload_type_changed",(RtpCallback)audio_stream_payload_type_changed,stream);
 ^
/build/mediastreamer2-2.16.1/src/voip/audiostream.c: In function 
'audio_stream_stop':
/build/mediastreamer2-2.16.1/src/voip/audiostream.c:1783:94: error: cast 
between incompatible function types from 'void (*)(RtpSession *, uint32_t,  
void *)' {aka 'void (*)(struct _RtpSession *, unsigned int,  void *)'} to 'void 
(*)(struct _RtpSession *, void *, void *, void *)' [-Werror=cast-function-type]
  
rtp_session_signal_disconnect_by_callback(stream->ms.sessions.rtp_session,"telephone-event",(RtpCallback)on_dtmf_received);

  ^
/build/mediastreamer2-2.16.1/src/voip/audiostream.c:1784:99: error: cast 
between incompatible function types from 'bool_t (*)(RtpSession *, void *)' 
{aka 'unsigned char (*)(struct _RtpSession *, void *)'} to 'void (*)(struct 
_RtpSession *, void *, void *, void *)' [-Werror=cast-function-type]
  
rtp_session_signal_disconnect_by_callback(stream->ms.sessions.rtp_session,"payload_type_changed",(RtpCallback)audio_stream_payload_type_changed);

   ^

This seems to be caused by compiling with error and the new compiler
series emitting more diagnostics.


Andreas


mediastreamer2_1%2.16.1-2.log.gz
Description: application/gzip

Bug#896305: laditools: diff for NMU version 1.1.0-3.1

[Ross Gammon]

On 08/04/2018 09:05 PM, Adrian Bunk wrote:
> Control: tags 896305 + patch
> Control: tags 896305 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for laditools (versioned as 1.1.0-3.1) and uploaded 
> it to DELAYED/15. Please feel free to tell me if I should cancel it.
>
> cu
> Adrian
>
Thanks Adrian for fixing this, and following up on the original
incorrect fix. My spare time is very limited at the moment. I really
appreciate it.




signature.asc
Description: OpenPGP digital signature

Processed: closing 904191

[Debian Bug Tracking System]

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

> close 904191 1.9.4-3+deb8u2
Bug #904191 {Done: Salvatore Bonaccorso } [src:ant] ant: 
Incomplete fix of CVE-2018-10886
The source 'ant' and version '1.9.4-3+deb8u2' do not appear to match any binary 
packages
Marked as fixed in versions ant/1.9.4-3+deb8u2.
Bug #904191 {Done: Salvatore Bonaccorso } [src:ant] ant: 
Incomplete fix of CVE-2018-10886
Bug 904191 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#904661: vtk7 FTBFS due to uninstallable build dependencies

[Nicolas Braud-Santoni]

Hi Gert,

On Sun, Jul 29, 2018 at 01:28:58PM +0200, Gert Wollny wrote:
> python-autobahn is currently not installable with python3-all-dev
> because the latter depends on python3.7 and python-autobahn depends on
> python-ubjson, which in turn FTBFS with python-3.7. 

Thanks for the explanation.  :)


> As a side note: I think it is very uncommon to file a bug against a
> package that FTBFS because of some dependency being (temporarly) not
> installable. 

You are of course right, sorry for mis-assigning it in the first place.
I was in the middle of triaging a bunch of bugs, which is probably why
I made the mistake, but this is more an explanation than an excuse.

In any case, I'm sorry for all that, it was probably an unpleasant bug
report to receive  :(


Best,

  nicoo


signature.asc
Description: PGP signature

Bug#905477: openjk: FTBFS with GCC-8: static assertion failed: std::map must have the same value_type as its allocator

[Andreas Beckmann]

Source: openjk
Version: 0~20180414.698fe7c~dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-8


Hi,

openjk started to FTBFS after GCC 8 was made the default compiler:

[ 13%] Building CXX object 
codeJK2/game/CMakeFiles/jospgamex86_64.dir/Q3_Interface.cpp.o
cd "/build/openjk-0~20180414.698fe7c~dfsg/obj/codeJK2/game" && /usr/bin/c++  
-DARCH_STRING=\"x86_64\" -DFINAL_BUILD -DJK2_MODE -DSOURCE_DATE="\"Apr 20 
2018\"" -DSP_GAME -Djospgamex86_64_EXPORTS 
-I"/build/openjk-0~20180414.698fe7c~dfsg/codeJK2" 
-I"/build/openjk-0~20180414.698fe7c~dfsg/codeJK2/game" 
-I"/build/openjk-0~20180414.698fe7c~dfsg/shared" 
-I"/build/openjk-0~20180414.698fe7c~dfsg/lib/gsl-lite/include"  -g -O2 
-fdebug-prefix-map=/build/openjk-0~20180414.698fe7c~dfsg=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall 
-Wno-unused-parameter -Wno-missing-field-initializers -fno-strict-aliasing 
-Wno-strict-aliasing -Wno-unused-but-set-variable   -Wdate-time 
-D_FORTIFY_SOURCE=2 -DNDEBUG -msse2 -std=c++11 -Wall -Wno-invalid-offsetof 
-Wno-write-strings -Wno-comment -fsigned-char -mstackrealign -mfpmath=sse -fPIC 
  -fvisibility=hidden -o CMakeFiles/jospgamex86_64.dir/Q3_Interface.cpp.o -c 
"/build/openjk-0~20180414.698fe7c~dfsg/codeJK2/game/Q3_Interface.cpp"
In file included from /usr/include/c++/8/map:61,
 from 
/build/openjk-0~20180414.698fe7c~dfsg/codeJK2/game/../game/../../code/ui/../qcommon/../game/ghoul2_shared.h:28,
 from 
/build/openjk-0~20180414.698fe7c~dfsg/codeJK2/game/../game/../../code/ui/../qcommon/q_shared.h:512,
 from 
/build/openjk-0~20180414.698fe7c~dfsg/codeJK2/game/../game/../../code/ui/gameinfo.h:27,
 from 
/build/openjk-0~20180414.698fe7c~dfsg/codeJK2/game/../game/g_local.h:32,
 from 
/build/openjk-0~20180414.698fe7c~dfsg/codeJK2/game/g_headers.h:28,
 from 
/build/openjk-0~20180414.698fe7c~dfsg/codeJK2/game/Q3_Interface.cpp:30:
/usr/include/c++/8/bits/stl_map.h: In instantiation of 'class 
std::map, int, 
std::less >, std::allocator >':
/build/openjk-0~20180414.698fe7c~dfsg/codeJK2/game/Q3_Interface.cpp:915:11:   
required from here
/usr/include/c++/8/bits/stl_map.h:122:21: error: static assertion failed: 
std::map must have the same value_type as its allocator
   static_assert(is_same::value,
 ^~~~
make[4]: *** [codeJK2/game/CMakeFiles/jospgamex86_64.dir/build.make:469: 
codeJK2/game/CMakeFiles/jospgamex86_64.dir/Q3_Interface.cpp.o] Error 1


Andreas


openjk_0~20180414.698fe7c~dfsg-1.log.gz
Description: application/gzip

Bug#905476: poezio: Incomplete debian/copyright?

[Chris Lamb]

Source: poezio
Version: 0.11+git20180331-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: W. Martin Borgert , 
ftpmas...@debian.org

Hi,

I just ACCEPTed poezio from NEW but noticed it was missing 
attribution in debian/copyright for at least Emmanuel Gil
Peyrot 

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


Regards,

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

Bug#903779: marked as done (emacs-nox: copyright file missing after upgrade (policy 12.5))

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 07:34:12 +
with message-id 
and subject line Bug#903779: fixed in emacs 1:25.2+1-9
has caused the Debian Bug report #903779,
regarding emacs-nox: copyright file missing after upgrade (policy 12.5)
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.)


-- 
903779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs-nox
Version: 1:25.2+1-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debian-policy/#copyright-information

After the upgrade /usr/share/doc/$PACKAGE/ is just an empty directory.

This was observed on the following upgrade paths:

  sid -> experimental

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

0m25.0s ERROR: WARN: Inadequate results from running adequate!
  emacs-nox: missing-copyright-file /usr/share/doc/emacs-nox/copyright

  MISSING COPYRIGHT FILE: /usr/share/doc/emacs-nox/copyright
  # ls -lad /usr/share/doc/emacs-nox
  drwxr-xr-x 2 root root 40 May 28 18:55 /usr/share/doc/emacs-nox
  # ls -la /usr/share/doc/emacs-nox/
  total 0
  drwxr-xr-x   2 root root   40 May 28 18:55 .
  drwxr-xr-x 103 root root 2160 May 28 18:55 ..

Additional info may be available here:
https://wiki.debian.org/MissingCopyrightFile

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

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


cheers,

Andreas


emacs-nox_1:25.2+1-7.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: emacs
Source-Version: 1:25.2+1-9

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

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

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

Debian distribution maintenance software
pp.
Rob Browning  (supplier of updated emacs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 04 Aug 2018 12:29:53 -0500
Source: emacs
Binary: emacs emacs-lucid emacs-lucid-dbg emacs-nox emacs-nox-dbg emacs-gtk 
emacs-gtk-dbg emacs-bin-common emacs-common emacs-el emacs23 emacs23-lucid 
emacs23-nox emacs24 emacs24-lucid emacs24-nox emacs25 emacs25-lucid emacs25-nox
Architecture: source
Version: 1:25.2+1-9
Distribution: unstable
Urgency: medium
Maintainer: Rob Browning 
Changed-By: Rob Browning 
Description:
 emacs  - GNU Emacs editor (metapackage)
 emacs-bin-common - GNU Emacs editor's shared, architecture dependent files
 emacs-common - GNU Emacs editor's shared, architecture independent 
infrastructur
 emacs-el   - GNU Emacs LISP (.el) files
 emacs-gtk  - GNU Emacs editor (with GTK+ GUI support)
 emacs-gtk-dbg - Debugging symbols for emacs-gtk
 emacs-lucid - GNU Emacs editor (with Lucid GUI support)
 emacs-lucid-dbg - Debugging symbols for emacs-lucid
 emacs-nox  - GNU Emacs editor (without GUI support)
 emacs-nox-dbg - Debugging symbols for emacs-nox
 emacs23- GNU Emacs transitional package to emacs-gtk
 emacs23-lucid - GNU Emacs transitional package to emacs-lucid
 emacs23-nox - GNU Emacs transitional package to emacs-nox
 emacs24- GNU Emacs transitional package to emacs-gtk
 emacs24-lucid - GNU Emacs transitional package to emacs-lucid
 emacs24-nox - GNU Emacs transitional package to emacs-nox
 emacs25- GNU Emacs transitional package to emacs-gtk
 emacs25-lucid - GNU Emacs transitional package to emacs-lucid
 emacs25-nox - GNU Emacs transitional package to emacs-nox
Closes: 879020 903779 904957
Changes:
 emacs (1:25.2+1-9) unstable; urgency=mediu

Bug#897880: marked as done (upx-ucl: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 07:34:58 +
with message-id 
and subject line Bug#897880: fixed in upx-ucl 3.94-5
has caused the Debian Bug report #897880,
regarding upx-ucl: 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.)


-- 
897880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:upx-ucl
Version: 3.94-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/upx-ucl_3.94-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

[...]
g++ -DWITH_UCL -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fno-delete-null-pointer-checks -fno-strict-aliasing 
-fwrapv -funsigned-char -Wall -W -Wcast-align -Wcast-qual 
-Wmissing-declarations -Wpointer-arith -Wshadow -Wvla -Wwrite-strings -Werror 
-o compress_zlib.o -c compress_zlib.cpp
compress_zlib.cpp: In member function 'void zlib_compress_config_t::reset()':
compress_zlib.cpp:36:34: error: 'void* memset(void*, int, size_t)' clearing an 
object of non-trivial type 'struct zlib_compress_config_t'; use assignment or 
value-initialization instead [-Werror=class-memaccess]
 memset(this, 0, sizeof(*this));
  ^
In file included from compress_zlib.cpp:29:
conf.h:548:8: note: 'struct zlib_compress_config_t' declared here
 struct zlib_compress_config_t
^~
cc1plus: all warnings being treated as errors
make[3]: *** [Makefile:92: compress_zlib.o] Error 1
make[3]: Leaving directory '/<>/src'
make[3]: *** Waiting for unfinished jobs
make[3]: Entering directory '/<>/src'
g++ -DWITH_UCL -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fno-delete-null-pointer-checks -fno-strict-aliasing 
-fwrapv -funsigned-char -Wall -W -Wcast-align -Wcast-qual 
-Wmissing-declarations -Wpointer-arith -Wshadow -Wvla -Wwrite-strings -Werror 
-o compress_ucl.o -c compress_ucl.cpp
make[3]: Leaving directory '/<>/src'
make[3]: Entering directory '/<>/src'
g++ -DWITH_UCL -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fno-delete-null-pointer-checks -fno-strict-aliasing 
-fwrapv -funsigned-char -Wall -W -Wcast-align -Wcast-qual 
-Wmissing-declarations -Wpointer-arith -Wshadow -Wvla -Wwrite-strings -Werror 
-o filter.o -c filter.cpp
make[3]: Leaving directory '/<>/src'
make[3]: Entering directory '/<>/src'
g++ -DWITH_UCL -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fno-delete-null-pointer-checks -fno-strict-aliasing 
-fwrapv -funsigned-char -Wall -W -Wcast-align -Wcast-qual 
-Wmissing-declarations -Wpointer-arith -Wshadow -Wvla -Wwrite-strings -Werror 
-o except.o -c except.cpp
make[3]: Leaving directory '/<>/src'
make[3]: Entering directory '/<>/src'
g++ -DWITH_UCL -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -fno-delete-null-pointer-checks -fno-strict-aliasing 
-fwrapv -funsigned-char -Wall -W -Wcast-align -Wcast-qual 
-Wmissing-declarations -Wpointer-arith -Wshadow -Wvla -Wwrite-strings -Werror 
-o file.o -c file.cpp
make[3]: Leaving directory '/<>/src'
make[3]: Entering directory '/<>/src'
g++ -DWITH_UCL -

Bug#904957: marked as done (emacs-lucid: trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package emacs25-lucid 25.2+1-6+b3)

[Debian Bug Tracking System]

Your message dated Sun, 05 Aug 2018 07:34:12 +
with message-id 
and subject line Bug#904957: fixed in emacs 1:25.2+1-9
has caused the Debian Bug report #904957,
regarding emacs-lucid: trying to overwrite '/usr/share/emacs/25.2/etc/DOC', 
which is also in package emacs25-lucid 25.2+1-6+b3
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.)


-- 
904957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: emacs-lucid
Version: 1:25.2+1-8
Severity: serious

Dear Maintainer,

upgrading emacs25-lucid on armhf pulls in emacs-lucid, but that fails
to install as follows:

Preparing to unpack .../emacs-lucid_1%3a25.2+1-8_armhf.deb ...
Unpacking emacs-lucid (1:25.2+1-8) ...
dpkg: error processing archive 
/var/cache/apt/archives/emacs-lucid_1%3a25.2+1-8_armhf.deb (--unpack):
 trying to overwrite '/usr/share/emacs/25.2/etc/DOC', which is also in package 
emacs25-lucid 25.2+1-6+b3
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/emacs-lucid_1%3a25.2+1-8_armhf.deb

The Replaces header only contains emacs-gtk and emacs-nox, but likely
also needs emacs25-lucid. And probably also needs a "Breaks:
emacs25-lucid".

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
'buildd-unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 
'buildd-experimental'), (1, 'experimental')
Architecture: armhf (armv7l)

Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages emacs-lucid depends on:
pn  emacs-bin-common   
pn  emacs-common   
ii  libacl12.2.52-3+b1
ii  libasound2 1.1.6-1
ii  libc6  2.27-5
ii  libcairo2  1.15.10-3
ii  libdbus-1-31.12.8-3
ii  libfontconfig1 2.13.0-5
ii  libfreetype6   2.8.1-2
ii  libgdk-pixbuf2.0-0 2.36.12-1
ii  libgif75.1.4-3
ii  libglib2.0-0   2.56.1-2
ii  libgnutls303.5.19-1
ii  libgomp1   8.2.0-1
ii  libgpm21.20.7-5
ii  libice62:1.0.9-2
ii  libjpeg62-turbo1:1.5.2-2+b1
ii  libm17n-0  1.7.0-3+b2
ii  libmagickcore-6.q16-6  8:6.9.10.2+dfsg-3
ii  libmagickwand-6.q16-6  8:6.9.10.2+dfsg-3
ii  libotf00.9.13-3+b1
ii  libpng16-161.6.34-2
ii  librsvg2-2 2.40.20-2
ii  libselinux12.8-1+b1
ii  libsm6 2:1.2.2-1+b3
ii  libtiff5   4.0.9-6
ii  libtinfo6  6.1+20180714-1
ii  libx11-6   2:1.6.5-1
ii  libx11-xcb12:1.6.5-1
ii  libxcb11.13-2
ii  libxext6   2:1.3.3-1+b2
ii  libxfixes3 1:5.0.3-1
ii  libxft22.3.2-2
ii  libxinerama1   2:1.1.3-1+b3
ii  libxml22.9.4+dfsg1-7+b1
ii  libxmu62:1.1.2-2
ii  libxpm41:3.5.12-1
ii  libxrandr2 2:1.5.1-1
ii  libxrender11:0.9.10-1
ii  libxt6 1:1.1.5-1
ii  xaw3dg 1.5+E-18.3
ii  zlib1g 1:1.2.11.dfsg-1

emacs-lucid recommends no packages.

Versions of packages emacs-lucid suggests:
pn  emacs-common-non-dfsg  
--- End Message ---
--- Begin Message ---
Source: emacs
Source-Version: 1:25.2+1-9

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

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

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

Debian distribution maintenance software
pp.
Rob Browning  (supplier of updated emacs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 04 Aug 2018 12:29:53 -0500
Source: emacs
Binary: emacs emacs-lucid emacs-lucid-dbg emacs-nox emacs-nox-dbg emacs-gtk 
emacs-gtk-dbg emacs-bin-common emacs-common emacs-el emacs23 emacs23-lucid 
emacs23-nox emacs24 emacs24-lucid emacs24-nox emacs25 emacs25-lucid emacs25-nox
Architecture: sour

Bug#905409: upgrade of util-linux and login break the xhost command for other users

[Davide Prina]

Hi Andreas,

On 05/08/2018 05:40, Andreas Henriksson wrote:


$ xhost +si:localuser:temp
$ su - temp


You are right that the old su would copy over DISPLAY and XAUTHORITY
environment variables, even when you tell it to give you a new
clean environment.


probably this modification must be written in the changelog as an 
important change.



$ firefox &
Error: GDK_BACKEND does not match available displays


The error message is a bit misleading. Please just try running this
instead:

DISPLAY=:0 firefox &


thanks, this work :-)

strange, one of the first things that I have done was:
export DISPLAY=:0

probably I have mistake writing something :-(
... looking the history I found that I don't have write "export" :-(


Please feel free to submit a merge request with a util-linux.NEWS entry
addition mentioning the difference if you can come up with a nice
user-understandable description.


I'm not very good in English.

I think you can close this bug.

thanks for your help
Davide

Processed: Re: libgit2 FTBFS on armhf internal compil,er error: Segmentation fault

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/libgit2/libgit2/issues/4753
Bug #904004 [libgit2] libgit2 FTBFS on armhf, ppc64el, mips64el randomly
Changed Bug forwarded-to-address to 
'https://github.com/libgit2/libgit2/issues/4753' from 
'https://github.com/libgit2/libgit2/issues/4737'.

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

Bug#904004: libgit2 FTBFS on armhf internal compil,er error: Segmentation fault

[Ximin Luo]

Control: forwarded -1 https://github.com/libgit2/libgit2/issues/4753

The segfault happens on all architectures and we were just unlucky that it 
happened on the ones that we saw.

I've filed an upstream issue with a stack trace, will continue debugging later.

X

Pirate Praveen:
> On 18/07/18 6:39 PM, John Paul Adrian Glaubitz wrote:
>> I don't think your last upload was a good idea as you apparently
>> didn't test your change on all affected architectures. The testsuite
>> still fails on mips64el and ppc64el.
> 
> The previous upload was failing only on amrhf so thought fixing that
> would be enough.
> 
>> Please take advantage of the porterboxes we have in Debian [1] rather
>> than just uploading a new version over and over again to test new
>> changes.
> 
> ok.
> 


-- 
GPG: ed25519/56034877E1F87C35
GPG: rsa4096/1318EFAC5FBBDBCE
https://github.com/infinity0/pubkeys.git

Bug#905472: libtextwrap FTBFS: cannot find -ltextwrap

[Helmut Grohne]

Control: tags -1 + patch

On Sun, Aug 05, 2018 at 08:55:32AM +0200, Helmut Grohne wrote:
> Scanning the recent upload history, automake-1.16 looks suspicious now.

Yes, it looks like a missing Makefile.am dependency. The attached patch
makes it build.

Helmut
--- libtextwrap-0.1.orig/Makefile.am
+++ libtextwrap-0.1/Makefile.am
@@ -9,3 +9,4 @@
 bin_PROGRAMS = dotextwrap
 dotextwrap_SOURCES = dotextwrap.c
 dotextwrap_LDADD = -ltextwrap
+EXTRA_dotextwrap_DEPENDENCIES = libtextwrap.la

Processed: Re: libtextwrap FTBFS: cannot find -ltextwrap

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #905472 [src:libtextwrap] libtextwrap FTBFS: cannot find -ltextwrap
Added tag(s) patch.

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