Bug#822586: cherrytree: depends on python-gtksourceview2 which is deprecated

[Kurobeats .]

python-appindicator has been removed as a dependency in commit
112c786f42835142a1b4ca0a47c6d351e26dc406

https://github.com/giuspen/cherrytree/commit/112c786f42835142a1b4ca0a47c6d351e26dc406

kuro.

Bug#910874: marked as done (unattended-upgrades removes packages even if)

[Debian Bug Tracking System]

Your message dated Thu, 22 Nov 2018 02:13:13 +
with message-id 
and subject line Bug#910874: fixed in unattended-upgrades 1.8
has caused the Debian Bug report #910874,
regarding unattended-upgrades removes packages even if
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.)


-- 
910874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unattended-upgrades
Version: 0.93.1+nmu1
Severity: serious

Even if I have configured 'Remove-Unused-Dependencies "false";' in
apt.conf.d/50unattended-upgrades:


// Do automatic removal of new unused dependencies after the upgrade
// (equivalent to apt-get autoremove)
Unattended-Upgrade::Remove-Unused-Dependencies "false";

it DOES remove packages (see below) as long as apt is configured as:

APT::AutoRemove::RecommendsImportant "false";

In my understanding this shouldn't be the case.

Here is the output of unattended-upgrade:

unattended-upgrade -d -v --dry-run
Initial blacklisted packages:
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are: ['o=Debian,n=stretch,l=Debian-Security',
'o=Debian,n=stretch,l=Debian-Security']
Checking: icedove ([, ])
pkg 'enigmail' now marked delete
sanity check failed
Checking: icedove-l10n-de ([, ])
pkg 'enigmail' now marked delete
sanity check failed
Checking: iceowl-extension ([, ])
pkg 'enigmail' now marked delete
sanity check failed
Checking: libsnmp-base ([, ])
Checking: libsnmp30 ([])
Checking: lightning ([, ])
pkg 'enigmail' now marked delete
sanity check failed
Checking: thunderbird ([])
pkg 'enigmail' now marked delete
sanity check failed
Checking: thunderbird-l10n-de ([, ])
pkg 'enigmail' now marked delete
sanity check failed
pkgs that look like they should be upgraded: libsnmp-base
libsnmp30
Fetched 0 B in 0s (0 B/s)


fetch.run() result: 0
http://security.debian.org/pool/updates/main/n/net-snmp/libsnmp-base_5.7.3+dfsg-1.7+deb9u1_all.deb'
ID:0 ErrorText: ''>
check_conffile_prompt('/var/cache/apt/archives/libsnmp-base_5.7.3+dfsg-1.7+deb9u1_all.deb')
found pkg: libsnmp-base
No conffiles in deb
'/var/cache/apt/archives/libsnmp-base_5.7.3+dfsg-1.7+deb9u1_all.deb'
(There is no member named 'conffiles')
http://security.debian.org/pool/updates/main/n/net-snmp/libsnmp30_5.7.3+dfsg-1.7+deb9u1_amd64.deb'
ID:0 ErrorText: ''>
check_conffile_prompt('/var/cache/apt/archives/libsnmp30_5.7.3+dfsg-1.7+deb9u1_amd64.deb')
found pkg: libsnmp30
No conffiles in deb
'/var/cache/apt/archives/libsnmp30_5.7.3+dfsg-1.7+deb9u1_amd64.deb'
(There is no member named 'conffiles')
blacklist: []
whitelist: []
Option --dry-run given, *not* performing real actions
Packages that will be upgraded: libsnmp-base libsnmp30
Writing dpkg log to
'/var/log/unattended-upgrades/unattended-upgrades-dpkg.log'
found partition of size 2 (['libsnmp-base', 'libsnmp30'])
found leaf package libsnmp-base
applying set ['libsnmp-base']
apt-listchanges: Reading changelogs...
/usr/bin/dpkg --status-fd 9 --no-triggers --unpack --auto-deconfigure
/var/cache/apt/archives/libsnmp-base_5.7.3+dfsg-1.7+deb9u1_all.deb
/usr/bin/dpkg --status-fd 9 --configure --pending
left to upgrade {'libsnmp30'}
found partition of size 2 (['libsnmp-base', 'libsnmp30'])
applying set ['libsnmp-base', 'libsnmp30']
apt-listchanges: Reading changelogs...
/usr/bin/dpkg --status-fd 9 --no-triggers --unpack --auto-deconfigure
/var/cache/apt/archives/libsnmp-base_5.7.3+dfsg-1.7+deb9u1_all.deb
/var/cache/apt/archives/libsnmp30_5.7.3+dfsg-1.7+deb9u1_amd64.deb
/usr/bin/dpkg --status-fd 9 --configure --pending
left to upgrade set()
All upgrades installed
marking acpid for remove
marking acpi-support-base for remove
marking libao-common for remove
marking gstreamer1.0-plugins-ugly for remove
marking libsidplay1v5 for remove
marking dvdauthor for remove
marking libfreerdp-plugins-standard for remove
marking growisofs for remove
marking genisoimage for remove
marking brasero-cdrkit for remove
marking libopencore-amrnb0 for remove
marking libperl4-corelibs-perl for remove
marking cdrdao for remove
marking dmz-cursor-theme for remove
marking libopencore-amrwb0 for remove
marking libao4 for remove
marking wodim for remove
Packages that are auto removed: 'acpi-support-base acpid brasero-cdrkit
cdrdao dmz-cursor-theme dvdauthor genisoimage growisofs
gstreamer1.0-plugins-ugly libao-common libao4
libfreerdp-plugins-standard libopencore-amrnb0 libopencore-amrwb0
libperl4-corelibs-perl libsidplay1v5 wodim'
echo 'acpi-support-base:all deinstall' | /usr/bin/dpkg --set-selections
echo 'acpid:amd64 deinstall' | /usr/bin/dpkg 

Bug#885742: linsmith: GTK+ 3 / GooCanvas port may be available upstream

[Jeremy Bicha]

On Tue, Nov 20, 2018 at 9:23 AM Graham Inggs  wrote:
> Is there a RFA bug for libgnome?  Perhaps someone would like to adopt it
> in order to prevent the removal of working software from Debian.

I am sorry for the inconvenience.

The list of packages using libgnome is so small now (basically it's
gjots2, gnome-commander, revelation, xword & linsmith. gjots2 has been
ported for years but the Debian maintainer has been reluctant to ship
the new version.) and libgnome has been abandoned upstream for so long
(7 years) that I don't feel letting someone adopt it makes sense.

As things stand now, linsmith will need to be ported away from
libgnome by early February if we want linsmith to be present in the
Buster release next year. By that point, it will have been removed
from Testing for an entire year.

Thanks,
Jeremy Bicha

Bug#906609: fixed in gnucash 1:3.3-1

[Chris Lamb]

Hi Dmitry,

> It has been uploaded in 1:3.3-2 back in October.

Thanks!

> > gnucash has been out of testing for a while, alas. :(
> 
> :(

grep-excuses claims:

missing build on armel: gnucash, python-gnucash (from 1:2.6.19-1)
missing build on mips: gnucash, python-gnucash (from 1:2.6.19-1)

Is there a bug for this? (Would you like one?)


Best wishes,

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

Processed: tagging 913507

[Debian Bug Tracking System]

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

> tags 913507 + ftbfs
Bug #913507 [src:ncmpcpp] ncmpcpp FTBFS with ICU 63.1
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 911888

[Debian Bug Tracking System]

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

> tags 911888 + ftbfs
Bug #911888 [src:mongo-cxx-driver-legacy] [mongo-cxx-driver-legacy] FTBFS with 
boost1.67
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#914063: marked as done (tagpy FTBFS with boost 1.67)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 22:45:26 +
with message-id 
and subject line Bug#914063: fixed in tagpy 2013.1-6.1
has caused the Debian Bug report #914063,
regarding tagpy FTBFS with boost 1.67
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.)


-- 
914063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914063
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tagpy
Version: 2013.1-6
Severity: serious
Tags: ftbfs

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

...
x86_64-linux-gnu-g++ -pthread -shared -Wl,-Bsymbolic-functions -Wl,-z,relro 
-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-A8UpPM/python2.7-2.7.15=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
build2.7/temp.linux-x86_64-2.7/src/wrapper/basics.o 
build2.7/temp.linux-x86_64-2.7/src/wrapper/id3.o 
build2.7/temp.linux-x86_64-2.7/src/wrapper/rest.o -ltag -lboost_python-py27 -o 
build2.7/lib.linux-x86_64-2.7/_tagpy.so
/usr/bin/ld: cannot find -lboost_python-py27
collect2: error: ld returned 1 exit status
error: command 'x86_64-linux-gnu-g++' failed with exit status 1
make[1]: *** [debian/rules:23: override_dh_auto_build-2.7] Error 1


The Ubuntu diff seems to contain a fix.
--- End Message ---
--- Begin Message ---
Source: tagpy
Source-Version: 2013.1-6.1

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

Debian distribution maintenance software
pp.
Anton Gladky  (supplier of updated tagpy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 21 Nov 2018 18:51:00 +0100
Source: tagpy
Binary: python-tagpy python3-tagpy
Architecture: source
Version: 2013.1-6.1
Distribution: unstable
Urgency: medium
Maintainer: Michal Čihař 
Changed-By: Anton Gladky 
Description:
 python-tagpy - Python module for manipulating tags in music files
 python3-tagpy - Python 3 module for manipulating tags in music files
Closes: 914063
Changes:
 tagpy (2013.1-6.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix compilation against boost1.67. (Closes: #914063)
Checksums-Sha1:
 ab2a52eda4124996f780bfe775ef4bb93fba1e92 2240 tagpy_2013.1-6.1.dsc
 7d3556af208d671e3e0e6d6a4adb8affc2f1b7b3 6264 tagpy_2013.1-6.1.debian.tar.xz
 72130ca250aa2a2763a6ed346686901e6afe7439 5981 tagpy_2013.1-6.1_source.buildinfo
Checksums-Sha256:
 cfae11f810cee343a23932f8f683df1fc9dabc32b8275980a9545a9b5829cd12 2240 
tagpy_2013.1-6.1.dsc
 f67348808927b8686e4a46b2b5f134522db076de089ec7493e054998cfb18a52 6264 
tagpy_2013.1-6.1.debian.tar.xz
 a872b27b4608c77faf8e8f6b116a0831e2698a4db87fe08def23386944b70430 5981 
tagpy_2013.1-6.1_source.buildinfo
Files:
 27f0b1d5b3a108381c13a8bd81747e90 2240 python extra tagpy_2013.1-6.1.dsc
 b04f12bbdf7b952bec48a1585eff635d 6264 python extra 
tagpy_2013.1-6.1.debian.tar.xz
 f7cd4ea3aa1966eb984ca392c97407e5 5981 python extra 
tagpy_2013.1-6.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAlv1nAgACgkQ0+Fzg8+n
/wY6Wg//ezBMVRQ6Zv2JKX6eS0yqA+/cVvfok+vo8U3lcBZji5Qq+oZ69oJILan3
0WYGsce/UXe2wIGBMPIfw+m27JyXfYIaFGAYTYJYxAl54NsH4ggZbyZj7IQQkJVD
by+hLSSBxMQiG1dq3HPiRpbARdNMW84Wa8E2/iO57vsJSIgMzcXyEsl83ZLQzPQe
kTZu93dwhr/BwTD5Goo3RwSXX//DcQ5/XHvH9+/28yOsC3jv3li72tlIs1TtEkp0
PmoufU/LZHQtGoU33cOEWCeW+uPMgg7R9Vnu7HWtDpo3e7vkdEkCvErGPA+7l/T1
Jf9FuDeUGq8ISBCzMYAvLMELGGwKGWUFlzk4+3KQq2MQ8Imw8/z6Jfsb6crNYSAZ
QfEOcTNLrhQyTy0JlaXN/Z5UjnUoD+UTJVDa3xPEDI3jxHUs0Wx6viaNgtu0x+Z6
GTtnDmRXJiUsCY0UtZ16z+uPxFXVSDmuDed3eDyBulG9t4XAMysd7gq/4F2msdJD
AG2f9KoMVJ8UN4OmPP2NyYWVxmZcgxpzPDJNbxtvZ+Kics8gsURCBCwfsr415fs7
8/wT+TWC1ucJ8x7O/OVe3kQfvjAbOHrfrFjc4ZeVKE1P7wSrIU4410InS19sglKF
jpBFujbsSJDSKZHoRzyL4WQTS/juocOQL7byn/OetOYMWdDjCEg=
=ss4N
-END PGP SIGNATURE End Message ---

Bug#906609: fixed in gnucash 1:3.3-1

[Dmitry Smirnov]

On Thursday, 22 November 2018 3:23:37 AM AEDT Chris Lamb wrote:
> This has been merged upstream; can we make a new upload to Debian?

It has been uploaded in 1:3.3-2 back in October.


> gnucash has been out of testing for a while, alas. :(

:(


-- 
Cheers,
 Dmitry Smirnov.

---

Honesty is a gift we can give to others. It is also a source of power and
an engine of simplicity. Knowing that we will attempt to tell the truth,
whatever the circumstances, leaves us with little to prepare for. We can
simply be ourselves.
-- Sam Harris


signature.asc
Description: This is a digitally signed message part.

Processed: tagging 911882

[Debian Bug Tracking System]

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

> tags 911882 + ftbfs
Bug #911882 [src:gnss-sdr] [gnss-sdr] package does not build with boost1.67
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 913980

[Debian Bug Tracking System]

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

> tags 913980 + ftbfs
Bug #913980 [src:anytun] FTBFS against boost1.67
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#914307: src:pyqwt5: Should not ship with buster

[Scott Kitterman]

Package: src:pyqwt5
Version: 5.2.1~cvs20091107+dfsg-8
Severity: serious
Justification: 2

This package is scheduled for removal before buster is released.  Most, but
not all of the rdepends are already out of testing for one reason or another,
but it would be good to get pyqwt5 removed from testing sooner rather than
later to make sure they don't re-enter.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886779

Bug#914063: diff NMU for tagpy_2013.1-6.1

[Michal Čihař]

Hi

On Wed, 2018-11-21 at 18:56 +0100, Anton Gladky wrote:
> tags 914063 +pending +patch
> thanks
> 
> Dear maintainer,
> 
> I have prepared an NMU (versioned as 2013.1-6.1) and
> uploaded to DELAYED/5.
> 
> Please fell free to tell me if I should delay it longer, cancel
> or reschedule.
> 
> Diff is attached.

Thanks for the NMU, it looks good. Feel free to upload without delay.

Best regards
-- 
Michal Čihař | https://cihar.com/ | https://weblate.org/



signature.asc
Description: This is a digitally signed message part

Bug#891728: marked as done (ptlib FTBFS with glibc 2.26)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 21:51:05 +
with message-id 
and subject line Bug#911595: Removed package(s) from unstable
has caused the Debian Bug report #891728,
regarding ptlib FTBFS with glibc 2.26
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.)


-- 
891728: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891728
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ptlib
Version: 2.10.11~dfsg-2.1
Severity: serious
Tags: buster sid

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

...
ptlib/unix/channel.cxx: In member function 'virtual PBoolean 
PChannel::Read(const VectorOfSlice&)':
ptlib/unix/channel.cxx:239:40: error: '::readv' has not been declared
   if (ConvertOSError(lastReadCount = ::readv(os_handle, [0], 
slices.size()), LastReadError))
^
ptlib/unix/channel.cxx:239:40: note: suggested alternative: 'read'
   if (ConvertOSError(lastReadCount = ::readv(os_handle, [0], 
slices.size()), LastReadError))
^
read
ptlib/unix/channel.cxx: In member function 'virtual PBoolean 
PChannel::Write(const VectorOfSlice&)':
ptlib/unix/channel.cxx:258:22: error: '::writev' has not been declared
   while ((result = ::writev(os_handle, [0], slices.size())) < 0) {
  ^~
ptlib/unix/channel.cxx:258:22: note: suggested alternative: 'write'
   while ((result = ::writev(os_handle, [0], slices.size())) < 0) {
  ^~
  write
--- End Message ---
--- Begin Message ---
Version: 2.10.11~dfsg-2.1+rm

Dear submitter,

as the package ptlib has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/911595

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#859558: marked as done (ptlib: Please migrate to openssl1.1 in buster)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 21:51:05 +
with message-id 
and subject line Bug#911595: Removed package(s) from unstable
has caused the Debian Bug report #859558,
regarding ptlib: Please migrate to openssl1.1 in buster
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.)


-- 
859558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859558
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ptlib
Version: 2.10.11~dfsg-2
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/ptlib_2.10.11~dfsg-2_amd64-20160529-1512

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

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

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


Kurt
--- End Message ---
--- Begin Message ---
Version: 2.10.11~dfsg-2.1+rm

Dear submitter,

as the package ptlib has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/911595

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#892747: marked as done (python-tempest-lib FTBFS: ImportError: cannot import name mockpatch)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 21:47:14 +
with message-id 
and subject line Bug#897022: Removed package(s) from unstable
has caused the Debian Bug report #892747,
regarding python-tempest-lib FTBFS: ImportError: cannot import name mockpatch
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.)


-- 
892747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892747
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-tempest-lib
Version: 0.14.0-3
Severity: serious

Some recent change in unstable makes python-tempest-lib FTBFS:

https://tests.reproducible-builds.org/debian/history/python-tempest-lib.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-tempest-lib.html

...
==
FAIL: 
unittest2.loader._FailedTest.tempest_lib.tests.services.compute.test_agents_client
unittest2.loader._FailedTest.tempest_lib.tests.services.compute.test_agents_client
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: 
tempest_lib.tests.services.compute.test_agents_client
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "tempest_lib/tests/services/compute/test_agents_client.py", line 17, in 

from tempest_lib.tests.services.compute import base
  File "tempest_lib/tests/services/compute/base.py", line 17, in 
from oslotest import mockpatch
ImportError: cannot import name mockpatch


==
FAIL: 
unittest2.loader._FailedTest.tempest_lib.tests.services.compute.test_aggregates_client
unittest2.loader._FailedTest.tempest_lib.tests.services.compute.test_aggregates_client
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: 
tempest_lib.tests.services.compute.test_aggregates_client
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "tempest_lib/tests/services/compute/test_aggregates_client.py", line 17, 
in 
from tempest_lib.tests.services.compute import base
  File "tempest_lib/tests/services/compute/base.py", line 17, in 
from oslotest import mockpatch
ImportError: cannot import name mockpatch


==
FAIL: 
unittest2.loader._FailedTest.tempest_lib.tests.services.compute.test_availability_zone_client
unittest2.loader._FailedTest.tempest_lib.tests.services.compute.test_availability_zone_client
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: 
tempest_lib.tests.services.compute.test_availability_zone_client
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "tempest_lib/tests/services/compute/test_availability_zone_client.py", 
line 17, in 
from tempest_lib.tests.services.compute import base
  File "tempest_lib/tests/services/compute/base.py", line 17, in 
from oslotest import mockpatch
ImportError: cannot import name mockpatch
...
==
FAIL: unittest2.loader._FailedTest.tempest_lib.tests.test_rest_client
unittest2.loader._FailedTest.tempest_lib.tests.test_rest_client
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: tempest_lib.tests.test_rest_client
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 

Bug#910795: marked as done (libopal3.10.10: package uninstallable)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 21:50:22 +
with message-id 
and subject line Bug#911594: Removed package(s) from unstable
has caused the Debian Bug report #888357,
regarding libopal3.10.10: package uninstallable
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.)


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

Dear Maintainer,

now that libx264-152 is not available anymore, libopal3.10.10 became 
uninstallable. It can only be used by people retaining on their system 
a copy of an unmaintained version of an old library.
Please recompile libopal3.10.10 against newer libraries.

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

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

Versions of packages libopal3.10.10 depends on:
pn  libavcodec57 | libavcodec-extra57  
ii  libavutil557:3.4.3-1
ii  libc6  2.27-6
ii  libcapi20-31:3.27-3
ii  libgcc11:8.2.0-7
ii  libgsm11.0.13-4+b2
ii  libogg01.3.2-1+b1
ii  libpt2.10.11   2.10.11~dfsg-2.1
ii  libspandsp20.0.6+dfsg-0.1
ii  libspeex1  1.2~rc1.2-1+b2
ii  libspeexdsp1   1.2~rc1.2-1+b2
ii  libsrtp0   1.4.5~20130609~dfsg-2
ii  libssl1.0.21.0.2o-1
ii  libstdc++6 8.2.0-7
ii  libtheora0 1.1.1+dfsg.1-14+b1
ii  libtiff5   4.0.9-6
pn  libx264-152

libopal3.10.10 recommends no packages.

libopal3.10.10 suggests no packages.
--- End Message ---
--- Begin Message ---
Version: 3.10.10~dfsg2-2.1+rm

Dear submitter,

as the package opal has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/911594

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#888357: marked as done (opal: FTBFS with FFmpeg 4.0)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 21:50:22 +
with message-id 
and subject line Bug#911594: Removed package(s) from unstable
has caused the Debian Bug report #888357,
regarding opal: FTBFS with FFmpeg 4.0
to be marked as done.

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

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


-- 
888357: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888357
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opal
Version: 3.10.10~dfsg2-2.1
Severity: important
User: debian-multime...@lists.debian.org
Usertags: ffmpeg-3.5-transition

Hi,

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

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

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

Thanks,
James
--- End Message ---
--- Begin Message ---
Version: 3.10.10~dfsg2-2.1+rm

Dear submitter,

as the package opal has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/911594

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#886948: marked as done (ekiga-plugin-evolution: unhandled symlink to directory conversion: /usr/share/doc/PACKAGE)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 21:48:11 +
with message-id 
and subject line Bug#911593: Removed package(s) from unstable
has caused the Debian Bug report #886948,
regarding ekiga-plugin-evolution: unhandled symlink to directory conversion: 
/usr/share/doc/PACKAGE
to be marked as done.

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

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


-- 
886948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886948
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ekiga-plugin-evolution
Version: 4.0.1-9
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

This was observed on the following upgrade paths:

  stretch -> sid

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

For other overwritten locations anything interesting may happen.

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

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


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

1m25.7s ERROR: FAIL: silently overwrites files via directory symlinks:
  /usr/share/doc/ekiga-plugin-evolution/changelog.Debian.gz 
(ekiga-plugin-evolution) != /usr/share/doc/ekiga/changelog.Debian.gz (ekiga)
/usr/share/doc/ekiga-plugin-evolution -> ekiga
  /usr/share/doc/ekiga-plugin-evolution/changelog.gz (ekiga-plugin-evolution) 
!= /usr/share/doc/ekiga/changelog.gz (ekiga)
/usr/share/doc/ekiga-plugin-evolution -> ekiga
  /usr/share/doc/ekiga-plugin-evolution/copyright (ekiga-plugin-evolution) != 
/usr/share/doc/ekiga/copyright (ekiga)
/usr/share/doc/ekiga-plugin-evolution -> ekiga


cheers,

Andreas


ekiga-plugin-evolution_4.0.1-9.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 4.0.1-9+rm

Dear submitter,

as the package ekiga has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/911593

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#846758: marked as done (t38modem: FTBFS: ld: final link failed: Bad value)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 21:49:52 +
with message-id 
and subject line Bug#911596: Removed package(s) from unstable
has caused the Debian Bug report #846758,
regarding t38modem: FTBFS: ld: final link failed: Bad value
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.)


-- 
846758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846758
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: t38modem
Version: 2.0.0-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161202 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /usr/bin/ld: pmodeme.o: relocation R_X86_64_PC32 against symbol 
> `_ZNK17PStringDictionaryI7PStringE5GetAtERKS0_' can not be used when making a 
> shared object; recompile with -fPIC
> /usr/bin/ld: final link failed: Bad value
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/12/02/t38modem_2.0.0-4_unstable.log

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

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

Dear submitter,

as the package t38modem has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/911596

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#882268: marked as done (networking-ovs-dpdk FTBFS: AttributeError: 'module' object has no attribute 'VIF_TYPE_VHOST_USER')

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 21:46:44 +
with message-id 
and subject line Bug#914071: Removed package(s) from unstable
has caused the Debian Bug report #882268,
regarding networking-ovs-dpdk FTBFS: AttributeError: 'module' object has no 
attribute 'VIF_TYPE_VHOST_USER'
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.)


-- 
882268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=882268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: networking-ovs-dpdk
Version: 2015.1.1+git20151118.35ac4c7-1
Severity: serious

Some recent change in unstable makes networking-ovs-dpdk FTBFS:

https://tests.reproducible-builds.org/debian/history/networking-ovs-dpdk.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/networking-ovs-dpdk.html

...
==
FAIL: 
unittest2.loader._FailedTest.networking_ovs_dpdk.tests.unit.driver.test_mech_dpdk_ovs
unittest2.loader._FailedTest.networking_ovs_dpdk.tests.unit.driver.test_mech_dpdk_ovs
--
_StringException: Traceback (most recent call last):
ImportError: Failed to import test module: 
networking_ovs_dpdk.tests.unit.driver.test_mech_dpdk_ovs
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 456, in 
_find_test_path
module = self._get_module_from_name(name)
  File "/usr/lib/python2.7/dist-packages/unittest2/loader.py", line 395, in 
_get_module_from_name
__import__(name)
  File "networking_ovs_dpdk/tests/unit/driver/test_mech_dpdk_ovs.py", line 27, 
in 
class OVSDPDKMechanismBaseTestCase(base.AgentMechanismBaseTestCase):
  File "networking_ovs_dpdk/tests/unit/driver/test_mech_dpdk_ovs.py", line 28, 
in OVSDPDKMechanismBaseTestCase
VIF_TYPE = portbindings.VIF_TYPE_VHOST_USER
AttributeError: 'module' object has no attribute 'VIF_TYPE_VHOST_USER'


--
Ran 1 test in 3.646s

FAILED (failures=1)
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
--- End Message ---
--- Begin Message ---
Version: 2015.1.1+git20151118.35ac4c7-1+rm

Dear submitter,

as the package networking-ovs-dpdk has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/914071

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Processed: Bug #913599 in ceph marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #913599 [src:ceph] ceph: FTBFS on armel: #error "NEON intrinsics not 
available with the soft-float ABI.  Please use -mfloat-abi=softfp or 
-mfloat-abi=hard"
Ignoring request to alter tags of bug #913599 to the same tags previously set

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

Bug#913599: Bug #913599 in ceph marked as pending

[Gaudenz Steinlin]

Control: tag -1 pending

Hello,

Bug #913599 in ceph 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/ceph-team/ceph/commit/fa7d0d84f736d0b8450572f3192a43ff7b3252c4


Use -mfloat-abi=softfp on armel for NEON instructions

There was already a patch to do the same for Jewel, but it got removed
when the build system changed to cmake because it patched an autotools
file which was no longer present. This adds the same logic to the new
cmake based build system.

Closes: #913599



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/913599

Bug#914221: marked as done (libwxgtk3.0-dev: Broken wx-config)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 21:26:51 +
with message-id 
and subject line Bug#914086: fixed in wxwidgets3.0 3.0.4+dfsg-7
has caused the Debian Bug report #914086,
regarding libwxgtk3.0-dev: Broken wx-config
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.)


-- 
914086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libwxgtk3.0-dev
Version: 3.0.4+dfsg-5
Severity: grave
Justification: renders package unusable

Dear Maintainer,

wx-config is broken. I already posted a bug report here
https://trac.wxwidgets.org/ticket/18270 , as suggested, posting it here.

   * What led up to the situation?
Upgraded libwxgtk3.0-dev on 2018-11-19

   * What exactly did you do (or not do) that was effective (or ineffective)?
Copy/Pasting wx-config from a Sid system which has not been upgraded
solves the issues

   * What was the outcome of this action?
A working wx-config

   * What outcome did you expect instead?
wx-config included in package should work

Seems to be related to : https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=914086



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

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

Versions of packages libwxgtk3.0-dev depends on:
ii  libgl1-mesa-dev [libgl-dev]  18.2.5-1
ii  libglu1-mesa-dev [xlibmesa-glu-dev]  9.0.0-2.1
ii  libwxbase3.0-dev 3.0.4+dfsg-5
ii  libwxgtk3.0-0v5  3.0.4+dfsg-5
ii  wx-common3.0.4+dfsg-5
ii  wx3.0-headers3.0.4+dfsg-5

libwxgtk3.0-dev recommends no packages.

Versions of packages libwxgtk3.0-dev suggests:
ii  gettext0.19.8.1-9
pn  wx3.0-doc  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: wxwidgets3.0
Source-Version: 3.0.4+dfsg-7

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

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

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

Debian distribution maintenance software
pp.
Olly Betts  (supplier of updated wxwidgets3.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 22 Nov 2018 08:53:08 +1300
Source: wxwidgets3.0
Binary: libwxbase3.0-0v5 libwxbase3.0-dev libwxgtk3.0-0v5 libwxgtk3.0-dev 
libwxgtk-media3.0-0v5 libwxgtk-media3.0-dev libwxgtk3.0-gtk3-0v5 
libwxgtk3.0-gtk3-dev libwxgtk-media3.0-gtk3-0v5 libwxgtk-media3.0-gtk3-dev 
libwxgtk-webview3.0-gtk3-0v5 libwxgtk-webview3.0-gtk3-dev wx-common 
wx3.0-headers wx3.0-i18n wx3.0-examples wx3.0-doc
Architecture: source
Version: 3.0.4+dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: wxWidgets Maintainers 
Changed-By: Olly Betts 
Description:
 libwxbase3.0-0v5 - wxBase library (runtime) - non-GUI support classes of 
wxWidgets t
 libwxbase3.0-dev - wxBase library (development) - non-GUI support classes of 
wxWidge
 libwxgtk-media3.0-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ media 
library runt
 libwxgtk-media3.0-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ media 
library deve
 libwxgtk-media3.0-gtk3-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 3 
media library ru
 libwxgtk-media3.0-gtk3-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 3 
media library de
 libwxgtk-webview3.0-gtk3-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 
3 webview library
 libwxgtk-webview3.0-gtk3-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 
3 webview library
 libwxgtk3.0-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ runtime)
 libwxgtk3.0-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ development)
 libwxgtk3.0-gtk3-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 3 
runtime)
 libwxgtk3.0-gtk3-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 3 
development)
 

Bug#914086: marked as done (/usr/lib/*/wx/config/*: potentially broken if built on a merged-/usr system and run on a non-merged-/usr system)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 21:26:51 +
with message-id 
and subject line Bug#914086: fixed in wxwidgets3.0 3.0.4+dfsg-7
has caused the Debian Bug report #914086,
regarding /usr/lib/*/wx/config/*: potentially broken if built on a merged-/usr 
system and run on a non-merged-/usr system
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.)


-- 
914086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wxwidgets3.0
Version: 3.0.4+dfsg-4
Severity: normal
User: m...@linux.it
Usertags: usrmerge
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Steps to reproduce:

* Have two chroots, containers or complete systems, one with merged /usr
  and one not
* Build wxwidgets3.0 on the system with merged /usr
* Install and use wxwidgets3.0 on the system without merged /usr

Expected result:

* The package is functionally equivalent to the package you'd get if it
  had been built on a system without merged /usr
* The absolute paths of standard tools in /bin or /sbin do not appear in
  the package's content as paths in /usr/bin or /usr/sbin
* Everything works as intended

Actual result:

* /usr/lib/*/wx/config/* contain EGREP="/usr/bin/grep -E"
* If those scripts invoke ${EGREP} (I assume they do, but I haven't
  actually checked) it will not work on non-merged-/usr systems, where
  /bin/grep exists but /usr/bin/grep does not

A merged-/usr system can be obtained by installing with
debootstrap >= 1.0.102 or debootstrap --merged-usr, or by installing the
usrmerge package. A non-merged-/usr system can be obtained by installing
with debootstrap --no-merged-usr (or upgrading from an older release) and
not installing usrmerge.

Recent tests on tests.reproducible-builds.org use unmerged /usr for the
first build and merged /usr for the second, as a way to detect some
issues in this class.

This bug can probably be fixed by passing EGREP="/bin/grep -E" as an
additional command-line argument when invoking configure.

smcv
--- End Message ---
--- Begin Message ---
Source: wxwidgets3.0
Source-Version: 3.0.4+dfsg-7

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

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

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

Debian distribution maintenance software
pp.
Olly Betts  (supplier of updated wxwidgets3.0 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 22 Nov 2018 08:53:08 +1300
Source: wxwidgets3.0
Binary: libwxbase3.0-0v5 libwxbase3.0-dev libwxgtk3.0-0v5 libwxgtk3.0-dev 
libwxgtk-media3.0-0v5 libwxgtk-media3.0-dev libwxgtk3.0-gtk3-0v5 
libwxgtk3.0-gtk3-dev libwxgtk-media3.0-gtk3-0v5 libwxgtk-media3.0-gtk3-dev 
libwxgtk-webview3.0-gtk3-0v5 libwxgtk-webview3.0-gtk3-dev wx-common 
wx3.0-headers wx3.0-i18n wx3.0-examples wx3.0-doc
Architecture: source
Version: 3.0.4+dfsg-7
Distribution: unstable
Urgency: medium
Maintainer: wxWidgets Maintainers 
Changed-By: Olly Betts 
Description:
 libwxbase3.0-0v5 - wxBase library (runtime) - non-GUI support classes of 
wxWidgets t
 libwxbase3.0-dev - wxBase library (development) - non-GUI support classes of 
wxWidge
 libwxgtk-media3.0-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ media 
library runt
 libwxgtk-media3.0-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ media 
library deve
 libwxgtk-media3.0-gtk3-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 3 
media library ru
 libwxgtk-media3.0-gtk3-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 3 
media library de
 libwxgtk-webview3.0-gtk3-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 
3 webview library
 libwxgtk-webview3.0-gtk3-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 
3 webview library
 libwxgtk3.0-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ runtime)
 libwxgtk3.0-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ development)
 libwxgtk3.0-gtk3-0v5 - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 3 
runtime)
 libwxgtk3.0-gtk3-dev - wxWidgets Cross-platform C++ GUI toolkit (GTK+ 3 
development)
 wx-common  - wxWidgets Cross-platform C++ GUI toolkit (common support 

Processed: bug 911898 is forwarded to https://bugzilla.mozilla.org/show_bug.cgi?id=1507035

[Debian Bug Tracking System]

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

> forwarded 911898 https://bugzilla.mozilla.org/show_bug.cgi?id=1507035
Bug #911898 [firefox-esr] firefox-esr: SIGSEGV on startup on ppc64el
Set Bug forwarded-to-address to 
'https://bugzilla.mozilla.org/show_bug.cgi?id=1507035'.
> thanks
Stopping processing here.

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

Bug#911875: marked as done (proftpd-basic (mod_sftp) is missing important upstream fixes for an OpenSSL API change)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 20:11:38 +
with message-id 
and subject line Bug#911875: fixed in proftpd-dfsg 1.3.6-3
has caused the Debian Bug report #911875,
regarding proftpd-basic (mod_sftp) is missing important upstream fixes for an 
OpenSSL API change
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.)


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



Package: proftpd-basic
Version: 1.3.6-2+b1

The distribution of proftpd mod_sftp presently in Buster/Sid is critically 
flawed. Clients that use DSA and ECDSA keys may have issues connecting.
This was caused by an OpenSSL API change (upstream states OpenSSL 1.1.x is 
affected).

Specifically, the position of the signature struct pointer passed 
DSA_SIG_get0() and ECDSA_SIG_get0() had been altered in OpenSSL (moved from 
position #2 to position #0), causing key exchanges and other signing-based 
processes to break in mod_sftp.

The fix should be as straightforward as cherry picking the upstream commit. I 
will be testing this patch with the debian source code shortly.
--- End Message ---
--- Begin Message ---
Source: proftpd-dfsg
Source-Version: 1.3.6-3

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

Debian distribution maintenance software
pp.
Francesco Paolo Lovergine  (supplier of updated 
proftpd-dfsg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 21 Nov 2018 14:30:08 +0100
Source: proftpd-dfsg
Binary: proftpd-basic proftpd-dev proftpd-doc proftpd-mod-mysql 
proftpd-mod-pgsql proftpd-mod-ldap proftpd-mod-odbc proftpd-mod-sqlite 
proftpd-mod-geoip proftpd-mod-snmp
Architecture: source amd64 all
Version: 1.3.6-3
Distribution: unstable
Urgency: medium
Maintainer: ProFTPD Maintainance Team 

Changed-By: Francesco Paolo Lovergine 
Description:
 proftpd-basic - Versatile, virtual-hosting FTP daemon - binaries
 proftpd-dev - Versatile, virtual-hosting FTP daemon - development files
 proftpd-doc - Versatile, virtual-hosting FTP daemon - documentation
 proftpd-mod-geoip - Versatile, virtual-hosting FTP daemon - GeoIP module
 proftpd-mod-ldap - Versatile, virtual-hosting FTP daemon - LDAP module
 proftpd-mod-mysql - Versatile, virtual-hosting FTP daemon - MySQL module
 proftpd-mod-odbc - Versatile, virtual-hosting FTP daemon - ODBC module
 proftpd-mod-pgsql - Versatile, virtual-hosting FTP daemon - PostgreSQL module
 proftpd-mod-snmp - Versatile, virtual-hosting FTP daemon - SNMP module
 proftpd-mod-sqlite - Versatile, virtual-hosting FTP daemon - SQLite3 module
Closes: 608881 897168 911875 913824
Changes:
 proftpd-dfsg (1.3.6-3) unstable; urgency=medium
 .
   [ Hilmar Preuße ]
   * Pick github_pr_710 from upstream:
 [PATCH] Issue #674: Update mod_sftp to handle changed APIs in OpenSSL
 (Closes: #911875).
   * [PATCH] Bug#4356: Fix infinite loop by actually iterating properly
 for the next configuration record.
   * Pick github_pr_594 from upstream:
 [PATCH] Issue #593: If the IgnoreExtendedAttributes FSOption is used,
 then do not include the EXTENDED attribute flag in the SFTP ATTRS
 responses (Closes: #913824).
 .
   * Run configure w/ --disable-xattr only on kfreebsd to fix FTBFS.
 (Closes: #897168)
   * Do create /run/proftpd also in postinst, if not exists yet.
 (Closes: #608881)
   * New Proftp module package: proftpd-mod-snmp.
   * Add "Enhances: proftpd-basic" to all modules built by this package.
   * d/rules: remove clean code, which is covered by upstreams Makefile.
   * Lintian:
 W: maintainer-script-should-not-parse-etc-passwd-or-group
 E: wrong-path-for-interpreter
 .
   [ Francesco Paolo Lovergine ]
   * Policy bumped to 4.2.1. No changes required.
Checksums-Sha1:
 76c7ecb9d18f727a9088c30cad8182d81d22d505 2836 proftpd-dfsg_1.3.6-3.dsc
 6b380b6cf910ba73e1cf03f5633010a1cd615e23 76056 
proftpd-dfsg_1.3.6-3.debian.tar.xz
 59c1464ad39fb36abad5217be9252851736703f7 3133164 
proftpd-basic-dbgsym_1.3.6-3_amd64.deb
 

Bug#914086: closed by Olly Betts (Bug#914086: fixed in wxwidgets3.0 3.0.4+dfsg-6)

[Olly Betts]

Control: reopen -1
Control: found -1 3.0.4+dfsg-6
Control: severity -1 serious

The fix in -6 unfortunately doesn't work as configure doesn't honour
an explicitly set EGREP.  Setting GREP works though so will upload -7
with that.

> Severity: grave
> Justification: renders package unusable

The package is still usable for existing programs built against previous
versions.  It should also work perfectly on a merged-usr system.

Cheers,
Olly

Processed: Re: Bug#914086 closed by Olly Betts (Bug#914086: fixed in wxwidgets3.0 3.0.4+dfsg-6)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #914086 {Done: Olly Betts } [src:wxwidgets3.0] 
/usr/lib/*/wx/config/*: potentially broken if built on a merged-/usr system and 
run on a non-merged-/usr system
Bug #914221 {Done: Olly Betts } [src:wxwidgets3.0] 
libwxgtk3.0-dev: Broken wx-config
'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 wxwidgets3.0/3.0.4+dfsg-6.
No longer marked as fixed in versions wxwidgets3.0/3.0.4+dfsg-6.
> found -1 3.0.4+dfsg-6
Bug #914086 [src:wxwidgets3.0] /usr/lib/*/wx/config/*: potentially broken if 
built on a merged-/usr system and run on a non-merged-/usr system
Bug #914221 [src:wxwidgets3.0] libwxgtk3.0-dev: Broken wx-config
Marked as found in versions wxwidgets3.0/3.0.4+dfsg-6.
Marked as found in versions wxwidgets3.0/3.0.4+dfsg-6.
> severity -1 serious
Bug #914086 [src:wxwidgets3.0] /usr/lib/*/wx/config/*: potentially broken if 
built on a merged-/usr system and run on a non-merged-/usr system
Bug #914221 [src:wxwidgets3.0] libwxgtk3.0-dev: Broken wx-config
Severity set to 'serious' from 'grave'
Severity set to 'serious' from 'grave'

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

Bug#914153: Update to version 2.3.0-3 breaks Megaglest

[Frank Heckenbach]

Hi,

> Em qua, 21 de nov de 2018 às 15:15, Frank Heckenbach
>  escreveu:
> >
> > > I think that we should revert this change for the time being, though,
> > > because if it was working in this way for about a decade and the
> > > programs using FTGL worked "fine" despite having some bug there,
> >
> > Sorry, they did *NOT* all work fine, see my bug report.
> 
> I agree with that, that's why I said "fine" with quotes included.  I
> thought about adding "(for some value of 'fine')", but stopped short
> :-)
> 
> However, from how I understand it, having completely blank rectangles
> in the position of letters (which happens with critterding and
> darkradiant for example) is worse than what happened before in your
> original report -- it would perhaps be the worst case scenario of what
> could happen before.

For some value of "worse". For me, it could as well draw unicorn
rainbows; shipping my software with wrong colour effects is simply
inacceptable.

> Is there a way to easily determine when the applications are buggy by
> searching the code?  Maybe we can find an upper limit to the
> problematic applications, or provide patches, if feasible.

The upper limit is of course, all applications that use FTGL and
render letter (which is probably the same as all applications that
use FTGL at all). As things can be resolved differently in the
caller (which is basically the purpose of the change), I don't think
there's an easy way to check it automatically.

> > - A slightly more complex solution would be a flag to select the
> >   behaviour. Of course, it would need to be a runtime flag. It may
> >   default to the old behaviour, but that should be deprecated (and
> >   print a strong depreciation message -- unfortunately that would
> >   have to be at runtime too AFAICS, or is there a way to warn at
> >   compile time when a program, say, does *not* reference a
> >   particular function?).
> 
> I am not familiar with OpenGL stuff.  Is there a way to detect if a
> "Blending Mode" is provided at runtime, when the function is called,
> and if not, provide a default one like the one before, and possibly
> emitting errors for it to raise attention (both compile time and
> runtime)?

All I know is that OpenGL state is a complex beast, and even if
there's a way to query relevant info, it wouldn't be recommended as
it adds a round-trip and thus latency. OpenGL is supposed to be used
unidirectionally as much as possible. And it would smell like a
kludge anyway.

> Another option would be to have an extra argument in the function, say:
> 
>   inline FTPoint FTBitmapFontImpl::RenderI(const T* string,
>const int len,
>FTPoint position,
>FTPoint spacing,
>int renderMode,
>bool disableBlend = false);

Apart from the (slight) runtime overhead, this seems to make it hard
to change the default to the new behaviour later.

> Or perhaps a new function to enable/disable globally if the library is
> initialised, or an env flag, or similar.

That's more like what I had in mind. But if the default is the old
behaviour if this function is not called, and we want to deprecate
this, we can only warn at runtime (unless, as I said, there's a way
to find out at compile time that the function is not referenced --
sure, one could reference the function without calling it, but that
would be malicious, not worth worrying about).

> And I think that the default would have to be the old behaviour, yes,
> because after many years behaving in that way the applications must
> have learned to adapt or cope, and no one knows that they have to use
> a different flag or invoke the method with an extra parameter.

For some value of "the applications". You're talking about Debian
only again, of course, but there are other applications that have
come to expect the new behaviour (obviously at least mine and the
patch author's ones, possibly more -- there's a number of forks of
FTGL on github, probably by people who use(d) it).

> I realise that maybe this is not what you like because applications
> will ever remain buggy, but reallistically,

The same applies vice-versa for applications that rely on the new
behaviour if we make the old one the default.

The problem is we have different semantics already (and for almost
10 years apparently).

Perhaps the only sane way out is to add *two* new versions of each
rendering function, one with each behaviour, and deprecate the old
ones entirely. This will require changes in all applications (if
only to select the correct one of the two which should be easy if
ones knows which branch of the library they used before), but at
least it will be clear at compile time.

> some might even be
> abandoned upstream, so they could remain unusable forever.

If they're abandoned, what's their expected lifetime 

Bug#844861: marked as done (wsjtx: FTBFS: ld: final link failed: Nonrepresentable section on output)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 19:00:15 +
with message-id 
and subject line Bug#844861: fixed in wsjtx 1.8.0+repack-1
has caused the Debian Bug report #844861,
regarding wsjtx: FTBFS: ld: final link failed: Nonrepresentable section on 
output
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.)


-- 
844861: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=844861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wsjtx
Version: 1.1.r3496-3.2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20161118 qa-ftbfs
Justification: FTBFS on amd64

Hi,

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

Relevant part (hopefully):
> /usr/bin/ld: libjt9.a(fano232.o): relocation R_X86_64_32 against 
> `.rodata.str1.8' can not be used when making a shared object; recompile with 
> -fPIC
> /usr/bin/ld: final link failed: Nonrepresentable section on output
> collect2: error: ld returned 1 exit status

The full build log is available from:
   http://aws-logs.debian.net/2016/11/18/wsjtx_1.1.r3496-3.2_unstable.log

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

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

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

Debian distribution maintenance software
pp.
Enrico Rossi  (supplier of updated wsjtx package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 31 Aug 2018 14:26:06 +0200
Source: wsjtx
Binary: wsjtx wsjtx-doc
Architecture: source amd64 all
Version: 1.8.0+repack-1
Distribution: unstable
Urgency: low
Maintainer: Debian Hamradio Maintainers 
Changed-By: Enrico Rossi 
Description:
 wsjtx  - Weak-signal amateur radio communications
 wsjtx-doc  - Documentation and examples for the WSJT-X package
Closes: 752446 844861 850675 875235
Changes:
 wsjtx (1.8.0+repack-1) unstable; urgency=low
 .
   [ Enrico Rossi ]
   * port and adapt upstream patch to fix recent gfortran interop
 with ISO C.
   * Removed on-line fonts in Docs.
   * Update patches with descriptions.
   * Upgrade debian/copyright to 1.0
 .
   [ Dave Hibberd ]
   * New Upstream Release (Closes: #752446, #850675, #844861)
   * Patches refreshed
 - 0006 updated to strip out things to not build or install
   * debian/rules rewritten
   * dh compatibility brought to 11
 .
   [ Iain Learmonth ]
   * Tweaks for QT5 compatibility (Closes: #875235)
Checksums-Sha1:
 975bc8f7e4652f8217aef01c43bc195c6db1226e 2021 wsjtx_1.8.0+repack-1.dsc
 833b0688e0021173d393972c5755dea4f707d6de 26384550 
wsjtx_1.8.0+repack.orig.tar.gz
 c1c9a6ad7930c0a3b81059d68c0f08a1690159ac 18580 
wsjtx_1.8.0+repack-1.debian.tar.xz
 fc6bae748a8a1109512ea6d0fddf80e5d88454e9 17875220 
wsjtx-dbgsym_1.8.0+repack-1_amd64.deb
 40f19fcbce13a2e1d0d4f121b76e393665004960 11812512 
wsjtx-doc_1.8.0+repack-1_all.deb
 8956119973ce3281ab1e3f12163a593598748a42 15235 
wsjtx_1.8.0+repack-1_amd64.buildinfo
 bbce1c7805850a1900d1eb1ff7ada2b552ae1a36 5017708 wsjtx_1.8.0+repack-1_amd64.deb
Checksums-Sha256:
 1302990d69a96be9c3eba6e1efd72ea9aecb89f760ce2d2302a23399e7fb6ef8 2021 
wsjtx_1.8.0+repack-1.dsc
 6f78fb4997eacdc7b05e51676701addd46b1499cd63de72004e0be27a3cfb96e 26384550 
wsjtx_1.8.0+repack.orig.tar.gz
 4a2626feeed4ae301b15db59c82e8ff3f48c12e03119809fb792088c41ee82ef 18580 
wsjtx_1.8.0+repack-1.debian.tar.xz
 9826486ab93810270a11360764185b2e77ba9d94c40e46ee1fcf423df0e6b557 17875220 
wsjtx-dbgsym_1.8.0+repack-1_amd64.deb
 1944c196175d75015c407ddada89ef77f036d46fb066110342444f19edc26af1 11812512 
wsjtx-doc_1.8.0+repack-1_all.deb
 bc4a7968149686e19dc5daf13096bb781531168b9e28591259c555e8aad20b7b 15235 
wsjtx_1.8.0+repack-1_amd64.buildinfo
 

Bug#914065: marked as done (nheko FTBFS: Could not find a package configuration file provided by "MatrixClient")

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 18:50:37 +
with message-id 
and subject line Bug#914065: fixed in nheko 0.6.1-3
has caused the Debian Bug report #914065,
regarding nheko FTBFS: Could not find a package configuration file provided by 
"MatrixClient"
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.)


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

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

...
Build type set to 'RelWithDebInfo'
-- Version: 0.6.1
-- Boost version: 1.67.0
-- Found the following Boost libraries:
--   atomic
--   chrono
--   date_time
--   iostreams
--   random
--   regex
--   system
--   thread
-- Found ZLIB: /usr/lib/aarch64-linux-gnu/libz.so (found version "1.2.11") 
-- Found OpenSSL: /usr/lib/aarch64-linux-gnu/libcrypto.so (found version 
"1.1.1")  
CMake Error at CMakeLists.txt:251 (find_package):
  By not providing "FindMatrixClient.cmake" in CMAKE_MODULE_PATH this project
  has asked CMake to find a package configuration file provided by
  "MatrixClient", but CMake did not find one.

  Could not find a package configuration file provided by "MatrixClient"
  (requested version 0.1.0) with any of the following names:

MatrixClientConfig.cmake
matrixclient-config.cmake

  Add the installation prefix of "MatrixClient" to CMAKE_PREFIX_PATH or set
  "MatrixClient_DIR" to a directory containing one of the above files.  If
  "MatrixClient" provides a separate development package or SDK, be sure it
  has been installed.


-- Configuring incomplete, errors occurred!
--- End Message ---
--- Begin Message ---
Source: nheko
Source-Version: 0.6.1-3

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

Debian distribution maintenance software
pp.
Hubert Chathi  (supplier of updated nheko 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: Tue, 20 Nov 2018 10:08:17 -0500
Source: nheko
Binary: nheko
Architecture: source amd64
Version: 0.6.1-3
Distribution: unstable
Urgency: medium
Maintainer: Matrix Packaging Team 

Changed-By: Hubert Chathi 
Description:
 nheko  - desktop IM client for the Matrix protocol
Closes: 914065
Changes:
 nheko (0.6.1-3) unstable; urgency=medium
 .
   * debian/rules: make cmake write to a dummy home directory. (Closes:
 #914065)
Checksums-Sha1:
 ec680d4cc76db70a52523281e44081efdc7b8df8 2463 nheko_0.6.1-3.dsc
 0d5c3a8fdd4c61c5d166d2d4d5fb5ad400575c9b 10048 nheko_0.6.1-3.debian.tar.xz
 e372cd8ea036f2091f3abc2b281c19abb9679b92 50124908 
nheko-dbgsym_0.6.1-3_amd64.deb
 6b33e06474e5cb07cad07bd7df03cdfdbf56796d 14281 nheko_0.6.1-3_amd64.buildinfo
 ccfdde3225809bc15f2a2a85e2266125b04e7599 4135324 nheko_0.6.1-3_amd64.deb
Checksums-Sha256:
 8077f670034576a93b95974a670482cdaa407c1da5f910b6c35d4d65367bd49e 2463 
nheko_0.6.1-3.dsc
 6c5a16cc9fb8754fd618883505a02fba6b44ff9cecda9140299f691c1cdf10fc 10048 
nheko_0.6.1-3.debian.tar.xz
 6e6b8653811cc75d38473cdf88c7c3b6f3ee87e20d518cfc58e4c96ac28a2361 50124908 
nheko-dbgsym_0.6.1-3_amd64.deb
 221121dec5eabf0f5c6b5d2f46f63378d7cbacd912d8f2a6c04d5d6e1d1ef87f 14281 
nheko_0.6.1-3_amd64.buildinfo
 72e70841cb2c777bdce55b32fd9d77c41e7e8a4ef35be84a815fdfcb29ece395 4135324 
nheko_0.6.1-3_amd64.deb
Files:
 9c92b72633e4f29155c75a7c620c1933 2463 net optional nheko_0.6.1-3.dsc
 f636509c1fdf7f94379a12c6d3cc45ce 10048 net optional nheko_0.6.1-3.debian.tar.xz
 3e2f989e418ed09e15546ff0abef7c8e 50124908 debug optional 
nheko-dbgsym_0.6.1-3_amd64.deb
 03c53fc7af2252668eb67abd16ceb4ee 14281 net optional 
nheko_0.6.1-3_amd64.buildinfo
 dc27020c0c392c994dc23096f7c5 4135324 net optional nheko_0.6.1-3_amd64.deb

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEE3juhvb4UN2X4rCw4rXmvZUDjNa8FAlv1oOcACgkQrXmvZUDj
Na+ZDQf8CRy8QcpajkkHRTUne9dNoTqII5rfEpZ3qxg4cxk7oPI04Iis9G8q8ZwH
G97JJ/SWapjy/j8B4POJQ8/3qvcCYpNymGh2QQEE2y6fILzijNr6YzC2iStg900U
Gn/qwXRFHIT2Em7q5/BELdI/dgXEIhH7zYxdjhHIMAOxMis2VRR0ODCM5wuzCIuQ

Processed: Re: Bug#914291: jaxrs-api: copyright file wrong

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #914291 [src:jaxrs-api] jaxrs-api: copyright file wrong
Severity set to 'normal' from 'serious'

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

Bug#914291: jaxrs-api: copyright file wrong

[Emmanuel Bourg]

Control: severity -1 normal

The license changed in the version 2.1.1 because the project was donated
to the Eclipse Foundation. There is no code change between the version
2.1 under the CDDL+GPL and the version 2.1.1 under the EPL+GPL. So it's
still correct to state that the code is licensed under the CDDL.

Processed: Re: Bug#914291: jaxrs-api: copyright file wrong

[Debian Bug Tracking System]

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

> severity 914291 serious
Bug #914291 [src:jaxrs-api] jaxrs-api: copyright file wrong
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

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

Bug#914288: marked as done (libpgplot-perl: FTBFS and autopkgtest fail with new giza-dev: test waits for input)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 18:20:41 +
with message-id 
and subject line Bug#914288: fixed in libpgplot-perl 1:2.21-8
has caused the Debian Bug report #914288,
regarding libpgplot-perl: FTBFS and autopkgtest fail with new giza-dev: test 
waits for input
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.)


-- 
914288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libpgplot-perl
Version: 1:2.21-7
Severity: serious
Justification: fails to build from source (but built successfully in the past)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As first noted on ci.d.n: With

- -libcpgplot0 1.0.0-2
+libcpgplot0 1.1.0-1
- -libgiza0 1.0.0-2
+libgiza0 1.1.0-1
- -libpgplot0 1.0.0-2
+libpgplot0 1.1.0-1

libpgplot-perl's hangs, waiting for some input:


   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/libpgplot-perl-2.21'
PGPLOT_DEV="/XSERVE" xvfb-run -a dh_auto_test
make V=1 -j1 test TEST_VERBOSE=1
make[2]: Entering directory '/build/libpgplot-perl-2.21'
"/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- PGPLOT.bs 
blib/arch/auto/PGPLOT/PGPLOT.bs 644
PERL_DL_NONLAZY=1 "/usr/bin/perl" "-Iblib/lib" "-Iblib/arch" test.pl
== Running test1.p ==

Testing simple point plot...

PGPLOT module version 2.21

PGPLOT giza-1.1.0 library

%giza - ERROR - giza_newpage_prompt: Failed to read character from stdin
== Running test2.p ==


Testing advanced point and line plot routines...

PGPLOT module version 2.21

PGPLOT giza-1.1.0 library

Entering interactive cursor test...
Enter some points with the cursor


Cheers
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlv1hbNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZIHQ/9E1M0r8pG4oeu8x7wdXIUgCh+YijlQsuBS8C00N3n8f8wx4klBiw68GWk
wU905ZwkuibwZCyV/SRNgDiy2xMRr8yJ6Phtj/sWobx6rGT/HgqiLKRuW54i9Ef6
OSGEzsxUuALLpEn+oD/1kK3MnRCPnKtu3uc+jc3a7WMlsthkz/kp3tPTORN/jQfr
H8ooFCGsvoKxei0bSTRqs6TrZPoZH70I4QeeVxXnSMqIWuzISImEBHFQrMI+cydI
ipaf1Qj69LBqZlRPOwaJeMOZFCo26533VO8nwJVOTjJ+kExEW1GFeiQyKsZxbUU6
pK8y2l51sxwc6/IDr2Rm8e8pfNuMm5AoJdflQiAVwmEeEeJSzXdGAIm5yXwo7/WV
ifiGIjVOGJO0fq+WNVI0UHJtL4x/KcJu9o2ZL5J9BTa7ZWoV/PmmbwlYvBOwbuMb
IqRHBdV/046Z9AMLH0GFxgWfpRbJB1Sfz/g6q5b5mBoDSc0YxNQZJk4Qx7Q2UtLT
1W9CAaJbj3CJ1NVB1EmXLnIzCVDbLO/usPC4sH9tDVepwfE0RtYWI4Ex0OwnrIbW
FVETK4pSO2rpX9s1q1j07hz4qQwbdgu0jX/z0LoADtM1DkVQ7/ndreK6jjUd3d5D
CC3VNCQSU0i09TBJuXe4IbY6sHq10vj0z07xbsy0p9r18iv5HPg=
=1fYN
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libpgplot-perl
Source-Version: 1:2.21-8

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libpgplot-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 21 Nov 2018 18:57:15 CET
Source: libpgplot-perl
Binary: libpgplot-perl
Architecture: source
Version: 1:2.21-8
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Description: 
 libpgplot-perl - perl interface to the pgplot plotting library
Closes: 914288
Changes:
 libpgplot-perl (1:2.21-8) unstable; urgency=medium
 .
   [ Salvatore Bonaccorso ]
   * Update Vcs-* headers for switch to salsa.debian.org
 .
   [ gregor herrmann ]
   * Add patch to disable interactive tests. (Closes: #914288)
   * Update years of packaging copyright.
   * Declare compliance with Debian Policy 4.2.1.
   * Bump debhelper compatibility level to 10.
   * Remove trailing whitespace from debian/*.
Checksums-Sha256: 
 31e94e39d81cefed669dc5dca15abf0b5b13bcf27b1cc4159177b3188b53c08e 2272 
libpgplot-perl_2.21-8.dsc
 70e04a816c00262a5481749df6e0735b534cd25c027d58a55ec610bfafb1a63d 6436 
libpgplot-perl_2.21-8.debian.tar.xz
 5e885a252f2b795517befb67c2d415ef13e4ac4abf1282b0dc651f23a1afd547 8013 

Bug#914153: Update to version 2.3.0-3 breaks Megaglest

[Manuel A. Fernandez Montecelo]

Hi,

Em qua, 21 de nov de 2018 às 15:15, Frank Heckenbach
 escreveu:
>
> > I think that we should revert this change for the time being, though,
> > because if it was working in this way for about a decade and the
> > programs using FTGL worked "fine" despite having some bug there,
>
> Sorry, they did *NOT* all work fine, see my bug report.

I agree with that, that's why I said "fine" with quotes included.  I
thought about adding "(for some value of 'fine')", but stopped short
:-)

However, from how I understand it, having completely blank rectangles
in the position of letters (which happens with critterding and
darkradiant for example) is worse than what happened before in your
original report -- it would perhaps be the worst case scenario of what
could happen before.

So in short, critterding is completely unusable now in Debian
unstable, probably megaglest can be considered unusable too, and
darkradiant is at least affected (there's a window rendering stuff
that contains what I assume are blank rectangles that are supposed to
be letters).

Others like zaz seem unaffected.


> > there's no need to change this now and break applications with only a
> > few weeks to fix this in 15+ other packages before the freeze.
>
> For me, there was very much a need to change. This was one of the
> reasons I started working on ftgl at all if you remember. Without
> either fix (sammy's or mine), ftgl is useless to me, so I'm not
> gonna do this in my repo.

Yes, I was talking exclusively in Debian, carrying some extra patch or so.


> So what can we actually do now?
>
> - If you view it as an ABI breaking change, I can bump the version
>   to 3.0.0, just let me know. (This would mean that programs using
>   the library would need to be rechecked anyway, right? So if we
>   document this prominently, they'll know what to look for, both in
>   source code and in program behaviour.)

Theoretically an ABI change gets solved with a simple recompilation,
and from what I understand it this is more like an API change (it
doesn't break when compiling but the results are not good so as to
make some programs unusable).  So more than an ABI change this is
worse because it needs fixes in the code.

Since in Debian we cannot fix this in one sweep, and we need other
maintainers to help to bring their packages to compliance, this is
tricky.

The worst case is if there are popular applications that are installed
by 3rd parties and that we don't even have in Debian, in which case we
break those too.  Not sure if this is the case, but it can
theoretically happen.


> - If you insist on a version without either of those bugfixes, do
>   this in your code, but then I'm out, sorry. For me this will mean
>   at least 2 more years working with an out-of-distro version (and I
>   fear it would get neglected again, so maybe more like 10 more
>   years or forever), so I'd have no reason to care about the distro
>   version.

Let's try to avoid that, it's not good neither for FTGL nor Debian nor
the people involved :)


> - Otherwise just let the other packages find and fix the resulting
>   bugs, like the saying goes "better ask for forgiveness than for
>   permission".

The problem with this solution is that those packages that are broken
and which maybe cannot be fixed, will be unusable in Debian for a full
cycle.

Is there a way to easily determine when the applications are buggy by
searching the code?  Maybe we can find an upper limit to the
problematic applications, or provide patches, if feasible.


> - A slightly more complex solution would be a flag to select the
>   behaviour. Of course, it would need to be a runtime flag. It may
>   default to the old behaviour, but that should be deprecated (and
>   print a strong depreciation message -- unfortunately that would
>   have to be at runtime too AFAICS, or is there a way to warn at
>   compile time when a program, say, does *not* reference a
>   particular function?).

I am not familiar with OpenGL stuff.  Is there a way to detect if a
"Blending Mode" is provided at runtime, when the function is called,
and if not, provide a default one like the one before, and possibly
emitting errors for it to raise attention (both compile time and
runtime)?

Another option would be to have an extra argument in the function, say:

  inline FTPoint FTBitmapFontImpl::RenderI(const T* string,
   const int len,
   FTPoint position,
   FTPoint spacing,
   int renderMode,
   bool disableBlend = false);

Or perhaps a new function to enable/disable globally if the library is
initialised, or an env flag, or similar.

And I think that the default would have to be the old behaviour, yes,
because after many years behaving in that way the applications must
have learned to adapt or cope, and no one knows that they have 

Bug#914291: jaxrs-api: copyright file wrong

[Markus Koschany]

Control: severity -1 normal

Am 21.11.18 um 18:15 schrieb Thorsten Glaser:
> Source: jaxrs-api
> Version: 2.1.2-2
> Severity: serious
> Justification: Policy 2.3, 12.5, possibly 2.1
> 
> In an internal Java™ project of $dayjob I was checking licences
> of updated components and found that javax.ws.rs:javax.ws.rs-api
> 2.1.1 has a new, different, licence I am unfamiliar with. I de‐
> cided to see whether it’s in Debian and what its thoughts on it
> are.
> 
> The Debian source package for the same component, however, has
> still the old licence listed. I looked into the source code, and
> lo and behold, it carries the NEW one. (This means that the DD
> who uploaded it did not read the diff between the versions care‐
> fully enough).
> 
> Broken copyright information is at least RC and serious. If the
> new licence (EPLv2 something) is not DFSG-free this makes it
> grave and grounds for archive and snapshot removal.

Further investigation into the issue would have yielded the following:

The project is still dual-licensed under EPL-2.0 and
GPL-2+-with-class-path-exception. See the NOTICE file. The EPL license
is very similar to CDDL. There is also a EPL FAQ that answers most of
the common licensing questions:

https://www.eclipse.org/legal/epl-2.0/faq.php#h.nmhx2u70socl

In any case since it is available under GPL-2+with-class-path-exception
we comply with the Debian Policy. Thus I am downgrading the severity to
normal because it is a documentation bug and not a serious Policy violation.

Markus



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#914291: jaxrs-api: copyright file wrong

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #914291 [src:jaxrs-api] jaxrs-api: copyright file wrong
Severity set to 'normal' from 'serious'

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

Bug#914288: Bug #914288 in libpgplot-perl marked as pending

[gregor herrmann]

Control: tag -1 pending

Hello,

Bug #914288 in libpgplot-perl 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/perl-team/modules/packages/libpgplot-perl/commit/e3338ffe4abcc9dfa5c5c1d337821dc03a45e5f8


Add patch to disable interactive tests.

Closes: #914288



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/914288

Bug#914288: libpgplot-perl: FTBFS and autopkgtest fail with new giza-dev: test waits for input

[gregor herrmann]

On Wed, 21 Nov 2018 17:20:03 +0100, gregor herrmann wrote:

> libpgplot-perl's hangs, waiting for some input:

> Entering interactive cursor test...
> Enter some points with the cursor

I've now added a patch which disables the interactive parts of
test2.p and test9.p.


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#914063: diff NMU for tagpy_2013.1-6.1

[Anton Gladky]

tags 914063 +pending +patch
thanks

Dear maintainer,

I have prepared an NMU (versioned as 2013.1-6.1) and
uploaded to DELAYED/5.

Please fell free to tell me if I should delay it longer, cancel
or reschedule.

Diff is attached.

Best regards

Anton


nmu.debdiff
Description: Binary data

Processed: diff NMU for tagpy_2013.1-6.1

[Debian Bug Tracking System]

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

> tags 914063 +pending +patch
Bug #914063 [src:tagpy] tagpy FTBFS with boost 1.67
Added tag(s) pending.
Bug #914063 [src:tagpy] tagpy FTBFS with boost 1.67
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: Bug #914288 in libpgplot-perl marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #914288 [src:libpgplot-perl] libpgplot-perl: FTBFS and autopkgtest fail 
with new giza-dev: test waits for input
Added tag(s) pending.

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

Bug#913032: marked as done (minieigen fails its autopkg tests with a deprecation warning)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 17:49:37 +
with message-id 
and subject line Bug#913032: fixed in minieigen 0.50.3+dfsg1-7
has caused the Debian Bug report #913032,
regarding minieigen fails its autopkg tests with a deprecation warning
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.)


-- 
913032: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913032
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:minieigen
Version: 0.50.3+dfsg1-5
Severity: serious
Tags: sid buster

minieigen fails its autopkg tests with a deprecation warning, when run with
Python 3.7.  A quick fix is to override that, but maybe better fix it properly.


autopkgtest [04:47:37]: test minieigentest3: [---
Test Python3
testMatrix3Test (__main__.SimpleTests) ... ok
testQuaternion (__main__.SimpleTests) ... ok
testVector2i (__main__.SimpleTests) ... ok
testVector3 (__main__.SimpleTests) ... minieigentest.py:38: DeprecationWarning:
Please use assertEqual instead.
  self.failUnlessEqual(b3m[0][0],1)
minieigentest.py:39: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(b3m[0][1],4)
minieigentest.py:40: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(b3m[0][2],7)
minieigentest.py:41: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(b3m[1][0],2)
minieigentest.py:42: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(b3m[1][1],5)
minieigentest.py:43: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(b3m[1][2],8)
minieigentest.py:44: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(b3m[2][0],3)
minieigentest.py:45: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(b3m[2][1],6)
minieigentest.py:46: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(b3m[2][2],9)
minieigentest.py:49: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(c3m[0],1)
minieigentest.py:50: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(c3m[1],5)
minieigentest.py:51: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(c3m[2],9)
minieigentest.py:53: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(a3m.maxAbsCoeff(),9)
minieigentest.py:58: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(q1[3],1)
minieigentest.py:61: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(q2[3],1)
minieigentest.py:65: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(m3q[0][0],1)
minieigentest.py:66: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(m3q[1][2],-1)
minieigentest.py:70: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(q4.norm(),1)
minieigentest.py:10: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(c2i[0],5)
minieigentest.py:11: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(c2i[1],6)
minieigentest.py:15: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(c2i[0],10)
minieigentest.py:16: DeprecationWarning: Please use assertEqual instead.
  self.failUnlessEqual(c2i[1],12)
minieigentest.py:23: DeprecationWarning: Please use assertAlmostEqual instead.
  self.failUnlessAlmostEqual(c3r[0],5.2)
minieigentest.py:24: DeprecationWarning: Please use assertAlmostEqual instead.
  self.failUnlessAlmostEqual(c3r[1],6.2)
minieigentest.py:25: DeprecationWarning: Please use assertAlmostEqual instead.
  self.failUnlessAlmostEqual(c3r[2],9.5)
minieigentest.py:29: DeprecationWarning: Please use assertAlmostEqual instead.
  self.failUnlessAlmostEqual(c3r[0],15.6)
minieigentest.py:30: DeprecationWarning: Please use assertAlmostEqual instead.
  self.failUnlessAlmostEqual(c3r[1],18.6)
minieigentest.py:31: DeprecationWarning: Please use assertAlmostEqual instead.
  self.failUnlessAlmostEqual(c3r[2],28.5)
ok

--
Ran 4 tests in 0.007s

OK
Python3 run: OK
--- End Message ---
--- Begin Message ---
Source: minieigen
Source-Version: 0.50.3+dfsg1-7

We believe that the bug you reported is fixed in the latest version of
minieigen, 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 913...@bugs.debian.org,

Bug#914291: jaxrs-api: copyright file wrong

[Thorsten Glaser]

Source: jaxrs-api
Version: 2.1.2-2
Severity: serious
Justification: Policy 2.3, 12.5, possibly 2.1

In an internal Java™ project of $dayjob I was checking licences
of updated components and found that javax.ws.rs:javax.ws.rs-api
2.1.1 has a new, different, licence I am unfamiliar with. I de‐
cided to see whether it’s in Debian and what its thoughts on it
are.

The Debian source package for the same component, however, has
still the old licence listed. I looked into the source code, and
lo and behold, it carries the NEW one. (This means that the DD
who uploaded it did not read the diff between the versions care‐
fully enough).

Broken copyright information is at least RC and serious. If the
new licence (EPLv2 something) is not DFSG-free this makes it
grave and grounds for archive and snapshot removal.

Bug#906609: fixed in gnucash 1:3.3-1

[Chris Lamb]

[resending due to archived bug]

Hi Dmitry et al.,

> It was entirely my fault to miss that but I'm not uploading the fix yet due 
> to unrelated FTBFS on i386 that I hope to address when upstream fixes it:
> 
>   https://bugs.gnucash.org/show_bug.cgi?id=796878

This has been merged upstream; can we make a new upload to Debian?
gnucash has been out of testing for a while, alas. :(

(Not tagging /this/ bug as "fixed-upstream" as it's a separate issue AIUI...)


Best wishes,

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

Processed: Re: gnucash: FTBFS on mips/sid: Segmentation fault

[Debian Bug Tracking System]

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

> unarchive 906609
Bug #906609 {Done: Dmitry Smirnov } [src:gnucash] gnucash: 
FTBFS on mips/sid: Segmentation fault
Unarchived Bug 906609
> thanks
Stopping processing here.

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

Processed: your mail

[Debian Bug Tracking System]

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

> severity 913540 normal
Bug #913540 [shadowsocks-libev] "crypto: stream: repeat IV detected" after 
upgrading to newest version.
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.

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

Bug#914288: libpgplot-perl: FTBFS and autopkgtest fail with new giza-dev: test waits for input

[gregor herrmann]

Source: libpgplot-perl
Version: 1:2.21-7
Severity: serious
Justification: fails to build from source (but built successfully in the past)

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

As first noted on ci.d.n: With

- -libcpgplot0 1.0.0-2
+libcpgplot0 1.1.0-1
- -libgiza0 1.0.0-2
+libgiza0 1.1.0-1
- -libpgplot0 1.0.0-2
+libpgplot0 1.1.0-1

libpgplot-perl's hangs, waiting for some input:


   debian/rules override_dh_auto_test
make[1]: Entering directory '/build/libpgplot-perl-2.21'
PGPLOT_DEV="/XSERVE" xvfb-run -a dh_auto_test
make V=1 -j1 test TEST_VERBOSE=1
make[2]: Entering directory '/build/libpgplot-perl-2.21'
"/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- PGPLOT.bs 
blib/arch/auto/PGPLOT/PGPLOT.bs 644
PERL_DL_NONLAZY=1 "/usr/bin/perl" "-Iblib/lib" "-Iblib/arch" test.pl
== Running test1.p ==

Testing simple point plot...

PGPLOT module version 2.21

PGPLOT giza-1.1.0 library

%giza - ERROR - giza_newpage_prompt: Failed to read character from stdin
== Running test2.p ==


Testing advanced point and line plot routines...

PGPLOT module version 2.21

PGPLOT giza-1.1.0 library

Entering interactive cursor test...
Enter some points with the cursor


Cheers
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlv1hbNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgZIHQ/9E1M0r8pG4oeu8x7wdXIUgCh+YijlQsuBS8C00N3n8f8wx4klBiw68GWk
wU905ZwkuibwZCyV/SRNgDiy2xMRr8yJ6Phtj/sWobx6rGT/HgqiLKRuW54i9Ef6
OSGEzsxUuALLpEn+oD/1kK3MnRCPnKtu3uc+jc3a7WMlsthkz/kp3tPTORN/jQfr
H8ooFCGsvoKxei0bSTRqs6TrZPoZH70I4QeeVxXnSMqIWuzISImEBHFQrMI+cydI
ipaf1Qj69LBqZlRPOwaJeMOZFCo26533VO8nwJVOTjJ+kExEW1GFeiQyKsZxbUU6
pK8y2l51sxwc6/IDr2Rm8e8pfNuMm5AoJdflQiAVwmEeEeJSzXdGAIm5yXwo7/WV
ifiGIjVOGJO0fq+WNVI0UHJtL4x/KcJu9o2ZL5J9BTa7ZWoV/PmmbwlYvBOwbuMb
IqRHBdV/046Z9AMLH0GFxgWfpRbJB1Sfz/g6q5b5mBoDSc0YxNQZJk4Qx7Q2UtLT
1W9CAaJbj3CJ1NVB1EmXLnIzCVDbLO/usPC4sH9tDVepwfE0RtYWI4Ex0OwnrIbW
FVETK4pSO2rpX9s1q1j07hz4qQwbdgu0jX/z0LoADtM1DkVQ7/ndreK6jjUd3d5D
CC3VNCQSU0i09TBJuXe4IbY6sHq10vj0z07xbsy0p9r18iv5HPg=
=1fYN
-END PGP SIGNATURE-

Bug#913005: marked as done (ruby-rack: CVE-2018-16471: Possible XSS vulnerability in Rack)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 15:22:59 +
with message-id 
and subject line Bug#913005: fixed in ruby-rack 2.0.5-2
has caused the Debian Bug report #913005,
regarding ruby-rack: CVE-2018-16471: Possible XSS vulnerability in Rack
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.)


-- 
913005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rack
Version: 1.6.4-4
Severity: grave
Tags: patch security upstream

Hi,

The following vulnerability was published for ruby-rack.

CVE-2018-16471[0]:
Possible XSS vulnerability in Rack

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16471
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16471
[1] https://www.openwall.com/lists/oss-security/2018/11/05/2

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: ruby-rack
Source-Version: 2.0.5-2

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated ruby-rack package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 21 Nov 2018 14:58:29 +0100
Source: ruby-rack
Binary: ruby-rack
Built-For-Profiles: nocheck
Architecture: source all
Version: 2.0.5-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Chris Lamb 
Description:
 ruby-rack  - modular Ruby webserver interface
Closes: 913005
Changes:
 ruby-rack (2.0.5-2) experimental; urgency=medium
 .
   * CVE-2018-16471: Prevent a possible XSS vulnerability where a malicious
 request could impact the HTTP/HTTPS scheme returned to the underlying
 application. (Closes: #913005
   * debian/control:
 - Add myself to Uploaders.
 - Bump Standards-Version to 4.2.1.
 - wrap-and-sort -sa.
   * Drop trailing whitespace in debian/changelog.
   * Use HTTPS URI in debian/copyright.
Checksums-Sha1:
 5ebc148ef6992f21d8bca693675fd2aaee711696 2215 ruby-rack_2.0.5-2.dsc
 e0cfe0f01942e3cdbbe9c8b68da81f1ea92e9279 6732 ruby-rack_2.0.5-2.debian.tar.xz
 132d1da95ab2ab3eb80ef9c3a1747468b140be95 89904 ruby-rack_2.0.5-2_all.deb
 2f53a82e25cabea5b6c2fc9ffd8be57d210f08a9 8786 ruby-rack_2.0.5-2_amd64.buildinfo
Checksums-Sha256:
 bae89416932fcc034315b0df5d00dee72b0b376c99c87c0d258c558706fb20e1 2215 
ruby-rack_2.0.5-2.dsc
 a7aab6889051d4c7e5347c5584d6a017539cf5bb7bf4e77227c3848f624fffb0 6732 
ruby-rack_2.0.5-2.debian.tar.xz
 8dbc3b1de9aa67645e3b0ac37ff9005f946d39625e72637ffca19e14659ef7bd 89904 
ruby-rack_2.0.5-2_all.deb
 ab1d791580c1601710171d77c7f200cf1f050e208bda79b01441d96dd91097b4 8786 
ruby-rack_2.0.5-2_amd64.buildinfo
Files:
 d97bf253f071e1545767bac1447907e6 2215 ruby optional ruby-rack_2.0.5-2.dsc
 c297a664ead9f6f685891d6ee8473e91 6732 ruby optional 
ruby-rack_2.0.5-2.debian.tar.xz
 f765f4dc2d74787a3215b749cf653683 89904 ruby optional ruby-rack_2.0.5-2_all.deb
 440c3f30d4a047f93b6870178d96d3b3 8786 ruby optional 
ruby-rack_2.0.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAlv1cuQACgkQHpU+J9Qx
HljHBA/9HCa9Xq7RNw33GsQJ1ShcX6EuR3/MQG+8aEcz2pS1Xrcq2lE1nldC+/dh
fAoVowq4jgS7ngQYoz4Kw9lLgtN5CzS/oYVnkS09KewNwi1UZwW9j72iNSkLNwl6
dZXlMScmQbSBVtQIpmlvRezCXudxPDVVFqSL/6+njQ+nmqWKHb+vtCdZqnSjmvPc
WM/j7V3diUoJTIvAq554EvN3osZkxKqBGNzqi2DXKYcg4oj+a2o1pK7L/SHyJLjg
lYDmUIymxFPvI5lJhu3d6M+zOrRjkdqHXJJdecmQ456HQAS10CrXvdO3h1PJeFwX
9+FvhhEAvEC7LtzyM8pKyE7DPXuXWDv9RGRPwmRD7JeFScaviHDSzgeIKtt2yT8J
5uLcHsOCJ/AQoFqeP6msxa8JBU5Q0ZIRxBA9ollj6a15P7aEiUxDzRCllLR2T7pN
2+S02W9uL6ua/H0JNumwarQrsPW2qt5W6/4FvGZgkAiXP0o3O685DPjAa1dlmi0i
VxO/PU5/I5A989DYsJiaczVI8m32jAFTUvr1F1o1fSnx4L7v3yEOkISnQRzFpA/K
a9DWd+QtbihYS0f/p+cpKDe35bRh9Qp/nVa+rBRR9DGw+AQ6p0m9YY0h0n9U/NaG
d3rUatqbuqTcBWEOmCNAEde15Z16b5Nnfu+f7wej8wHtr3L42bc=
=Ipwp

Bug#914269: google-i18n-address FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 11

[Adrian Bunk]

Control: tags -1 - help

On Wed, Nov 21, 2018 at 10:01:41AM -0500, Daniel Kahn Gillmor wrote:
> Control: tags 914269 + confirmed help
> 
> I see this error in my cowbuilder instance as well, but i don't see the
> error when i build by hand on a buster/sid system.
> 
> more confusingly, this error crops up in python3.6, but not when
> using python3.7 -- so i don't understand what the issue is, or how to
> debug it further.
> 
> I welcome any pointers.

Fails:
LC_ALL=C dpkg-buildpackage

Builds:
LC_ALL=C.UTF-8 dpkg-buildpackage

Python 3.7 has a workaround for C locale.

In debian/rules add:
export LC_ALL=C.UTF-8

>   --dkg

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#914269: google-i18n-address FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 11

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - help
Bug #914269 [src:google-i18n-address] google-i18n-address FTBFS: 
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 11
Removed tag(s) help.

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

Processed: Re: Bug#914269: google-i18n-address FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 11

[Debian Bug Tracking System]

Processing control commands:

> tags 914269 + confirmed help
Bug #914269 [src:google-i18n-address] google-i18n-address FTBFS: 
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 11
Added tag(s) confirmed and help.

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

Bug#902511: marked as done (node-wrap-ansi: FTBFS in buster/sid (Cannot find module 'strip-ansi'))

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 14:56:13 +
with message-id 
and subject line Bug#902511: fixed in node-wrap-ansi 4.0.0-1
has caused the Debian Bug report #902511,
regarding node-wrap-ansi: FTBFS in buster/sid (Cannot find module 'strip-ansi')
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.)


-- 
902511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902511
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-wrap-ansi
Version: 3.0.1-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
   dh_update_autotools_config -i
   debian/rules override_dh_auto_test
make[1]: Entering directory '/<>'
mocha -u tdd --reporter spec
module.js:549
throw err;
^

Error: Cannot find module 'strip-ansi'
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object. (/<>/test.js:6:17)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at /usr/lib/nodejs/mocha/lib/mocha.js:231:27
at Array.forEach ()
at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:228:14)
at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:536:10)
at Object. (/usr/lib/nodejs/mocha/bin/_mocha:573:18)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:191:16)
at bootstrap_node.js:612:3
debian/rules:13: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:8: 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/node-wrap-ansi.html

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: node-wrap-ansi
Source-Version: 4.0.0-1

We believe that the bug you reported is fixed in the latest version of
node-wrap-ansi, 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.
Paolo Greppi  (supplier of updated node-wrap-ansi 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 21 Nov 2018 15:07:33 +0100
Source: node-wrap-ansi
Binary: node-wrap-ansi
Architecture: source all
Version: 4.0.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Paolo Greppi 
Description:
 node-wrap-ansi - Wordwrap a string with ANSI escape codes
Closes: 902511
Changes:
 node-wrap-ansi (4.0.0-1) unstable; urgency=medium
 .
   * New upstream version
   * Honor DEB_BUILD_OPTIONS
   * Fix nodejs binary
   * Bump standard version
   * Update copyright
   * Update Vcs fields for migration to https://salsa.debian.org/
   * Add missing build deps (Closes: #902511)
   * Bump debhelper version and get rid of dependency on dh-buildinfo
Checksums-Sha1:
 7228b771da750b492f8d7f903b98fe996a250407 2160 node-wrap-ansi_4.0.0-1.dsc
 

Bug#914269: google-i18n-address FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 11

[Daniel Kahn Gillmor]

Control: tags 914269 + confirmed help

I see this error in my cowbuilder instance as well, but i don't see the
error when i build by hand on a buster/sid system.

more confusingly, this error crops up in python3.6, but not when
using python3.7 -- so i don't understand what the issue is, or how to
debug it further.

I welcome any pointers.

  --dkg


signature.asc
Description: PGP signature

Bug#914268: marked as done (llvm-toolchain-7: baseline violation on armhf)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 14:55:36 +
with message-id 
and subject line Bug#914268: fixed in llvm-toolchain-7 1:7.0.1~+rc2-5
has caused the Debian Bug report #914268,
regarding llvm-toolchain-7: baseline violation on armhf
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.)


-- 
914268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: llvm-toolchain-7
Version: 1:7.0.1~+rc2-1~exp1
Severity: grave
Control: block 912164 by -1
Control: affects -1 src:rust-pulldown-cmark src:mesa src:cargo

LLVM now violates the armhf baseline by using NEON,
this can be reproduced as easy as:

(sid_armhf-dchroot)bunk@abel:~$ llvm-config-7
Illegal instruction
(sid_armhf-dchroot)bunk@abel:~$

gdb confirms that this is due to NEON usage.


Additionally, this also causes FTBFS on some of our buildds:
https://buildd.debian.org/status/fetch.php?pkg=rust-pulldown-cmark=armhf=0.2.0-1=1542734241=0
https://buildd.debian.org/status/fetch.php?pkg=cargo=armhf=0.31.0-4=1542700136=0
https://buildd.debian.org/status/fetch.php?pkg=mesa=armhf=18.2.5-2=1542760450=0

It might even result in silently misbuilt packages, just imagine
mesa would have disabled the feature instead of AC_MSG_ERROR.


Note that these mentioned buildd problems are just the visible
tip of the iceberg, the baseline violation is a problem that
must be fixed even when the buildds change.
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-7
Source-Version: 1:7.0.1~+rc2-5

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

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

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-7 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 21 Nov 2018 09:45:00 +0100
Source: llvm-toolchain-7
Binary: clang-7 clang-tools-7 clang-format-7 clang-tidy-7 clang-7-doc 
libclang1-7 libclang-7-dev libclang-common-7-dev libfuzzer-7-dev python-clang-7 
clang-7-examples libllvm7 llvm-7 llvm-7-runtime llvm-7-dev llvm-7-tools 
libllvm-7-ocaml-dev llvm-7-doc llvm-7-examples lld-7 liblld-7 liblld-7-dev 
lldb-7 liblldb-7 python-lldb-7 liblldb-7-dev libomp-7-dev libomp5-7 
libomp-7-doc libc++1-7 libc++-7-dev libc++abi1-7 libc++abi-7-dev
Architecture: source
Version: 1:7.0.1~+rc2-5
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Description:
 clang-7- C, C++ and Objective-C compiler
 clang-7-doc - C, C++ and Objective-C compiler - Documentation
 clang-7-examples - Clang examples
 clang-format-7 - Tool to format C/C++/Obj-C code
 clang-tidy-7 - clang-based C++ linter tool
 clang-tools-7 - clang-based tools for C/C++ developments
 libc++-7-dev - LLVM C++ Standard library (development files)
 libc++1-7  - LLVM C++ Standard library
 libc++abi-7-dev - LLVM low level support for a standard C++ library 
(development fi
 libc++abi1-7 - LLVM low level support for a standard C++ library
 libclang-7-dev - clang library - Development package
 libclang-common-7-dev - clang library - Common development package
 libclang1-7 - C interface to the clang library
 libfuzzer-7-dev - Library for coverage-guided fuzz testing
 liblld-7   - LLVM-based linker, library
 liblld-7-dev - LLVM-based linker, header files
 liblldb-7  - Next generation, high-performance debugger, library
 liblldb-7-dev - Next generation, high-performance debugger, header files
 libllvm-7-ocaml-dev - Modular compiler and toolchain technologies, OCaml 
bindings
 libllvm7   - Modular compiler and toolchain technologies, runtime library
 libomp-7-dev - LLVM OpenMP runtime - dev package
 libomp-7-doc - LLVM OpenMP runtime - Documentation
 libomp5-7  - LLVM OpenMP runtime
 lld-7  - LLVM-based linker
 lldb-7 - Next generation, high-performance debugger
 llvm-7 - Modular compiler and toolchain technologies
 llvm-7-dev - Modular compiler and toolchain technologies, libraries and header
 llvm-7-doc - Modular compiler and toolchain technologies, documentation
 

Bug#906386: marked as done (multistrap: FTBFS in buster/sid (po4a-build: Command not found))

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 14:55:55 +
with message-id 
and subject line Bug#906386: fixed in multistrap 2.2.10
has caused the Debian Bug report #906386,
regarding multistrap: FTBFS in buster/sid (po4a-build: Command not found)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with bash-completion
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
   dh_auto_build -i
make -j1
make[1]: Entering directory '/<>'
po4a-build
make[1]: po4a-build: Command not found
make[1]: *** [Makefile:10: docbuild] Error 127
make[1]: Leaving directory '/<>'
dh_auto_build: make -j1 returned exit code 2
make: *** [debian/rules:3: build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-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/multistrap.html

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

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

Thanks.
--- End Message ---
--- Begin Message ---
Source: multistrap
Source-Version: 2.2.10

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

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

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

Debian distribution maintenance software
pp.
Johannes 'josch' Schauer  (supplier of updated multistrap 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 21 Nov 2018 15:00:46 +0100
Source: multistrap
Binary: multistrap
Architecture: source
Version: 2.2.10
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Johannes 'josch' Schauer 
Description:
 multistrap - multiple repository bootstrap based on apt
Closes: 906386
Changes:
 multistrap (2.2.10) unstable; urgency=medium
 .
   * Orphaning the package, See #914282
   * Include and use a copy of the ancient po4a-build script. (Closes: #906386)
Checksums-Sha1:
 773e183a4d3d2073e4fbf19f539a570dd48eb128 1708 multistrap_2.2.10.dsc
 dfdcfc4ab027facef1ec00cf6bcb26315878954b 126116 multistrap_2.2.10.tar.xz
Checksums-Sha256:
 10b6461ac04bba40f37f6c0a39bab388969bcd3ccfd71b69a5f9f5434a84a088 1708 
multistrap_2.2.10.dsc
 2d5e809547bdbd2c1eb0f85d312da3d35e9efe8010e9047200334378c6708aa3 126116 
multistrap_2.2.10.tar.xz
Files:
 c56bdfc60fd628d267c150dc1dfcdd91 1708 utils optional multistrap_2.2.10.dsc
 bd10f9c0e325d97565df1dec9018eb1b 126116 utils optional multistrap_2.2.10.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEElFhU6KL81LF4wVq58sulx4+9g+EFAlv1ZVUACgkQ8sulx4+9
g+FYmA//WTInAeOg/bgoD5pWRkBFpAFlLzXkDWaSJH4FmmAXIWtsg3VSuJ8eklpQ
8YrbiAaaJLu9T3eRGG0LxDFHZEmpzTLztuaieyt28olnwNViAs94A++p2VXY1Onr
h/eliaq35pVTtQGJcbTeoRI/pCySIpBrQO8bIgN6mK2nc5Ep7hvdRZ432nlu0/15
Sf6Ji7Mi27xePwHlIGkpU2onFQUXHHdq+ssNEaR3K0jbbO6N4/7xS/LmAh+5b9yB
dg1xWRYIyT4pmCGJwlC1Q9Vr+5XC5QVGOSe3RSZjlVdwB9OcDPIKudlhBVtZ+eGW
KaXC7NflyjAHE8u9qdWUj/kGU+gPLtKwwlKmmIDXoF4zurPdYqaz8zTe3bu9fy2X
qctISWdMBz4lwomKw+YPbrNT5TathZWfdqHKreIb+JXD1Bg701lf1Od1qGWY/enO
b97nMhc1kn/9sOkIcZUF8Hwt1OszNPeef3XicA3Y0Ivpqs8lBoDbeJONSjeKgkFY
j+af0QKBe7jx4qwNvq2kOMT+SJyDlU38lUhyUPtHiHr8pXcOzSHslnbVN80w/V9X
FoEgTpHbFYlaQ72Cyw2DSbM9NCHfyUjZVe0pEQ0S+kLKXydTBw3LKupOJzf/+KX/
+8XNJUMMC8OLTOiYvAw+q444Qgs1MLgWy/IykHm4seFNVV6NCOk=
=NmFk
-END PGP SIGNATURE End Message ---

Bug#914153: Update to version 2.3.0-3 breaks Megaglest

[Frank Heckenbach]

Hi,

> I think that we should revert this change for the time being, though,
> because if it was working in this way for about a decade and the
> programs using FTGL worked "fine" despite having some bug there,

Sorry, they did *NOT* all work fine, see my bug report. And if we
apply my patch from 742469 instead, that might break programs in
other ways (and will require yet another breaking change in the
future, when we apply sammy's patch properly).

> there's no need to change this now and break applications with only a
> few weeks to fix this in 15+ other packages before the freeze.

For me, there was very much a need to change. This was one of the
reasons I started working on ftgl at all if you remember. Without
either fix (sammy's or mine), ftgl is useless to me, so I'm not
gonna do this in my repo.

> Otherwise we have to get the fix in several of this packages, which is
> way more difficult, specially if not well maintained in Debian,
> upstream or both.

As I said, it's a messy situation. A bug that was actually fixed in
2009, not applied downstream, rediscovered by me in 2014, and
accidentally pulled downstream by syncing from the repo you pointed
me do early this year (which I had (naively?) assumed to be mostly
in sync with your version). I'm used to bugs in Debian getting
ignored for years and the wontfixed (or silenly buried), but that
mess seems to be special even in comparison.

So what can we actually do now?

- If you view it as an ABI breaking change, I can bump the version
  to 3.0.0, just let me know. (This would mean that programs using
  the library would need to be rechecked anyway, right? So if we
  document this prominently, they'll know what to look for, both in
  source code and in program behaviour.)

- If you insist on a version without either of those bugfixes, do
  this in your code, but then I'm out, sorry. For me this will mean
  at least 2 more years working with an out-of-distro version (and I
  fear it would get neglected again, so maybe more like 10 more
  years or forever), so I'd have no reason to care about the distro
  version.

- Otherwise just let the other packages find and fix the resulting
  bugs, like the saying goes "better ask for forgiveness than for
  permission".

- A slightly more complex solution would be a flag to select the
  behaviour. Of course, it would need to be a runtime flag. It may
  default to the old behaviour, but that should be deprecated (and
  print a strong depreciation message -- unfortunately that would
  have to be at runtime too AFAICS, or is there a way to warn at
  compile time when a program, say, does *not* reference a
  particular function?).

Cheers,
Frank

Processed: Re: Bug#913910: atop crashed with "Malloc failed for 1826553824 deviated tasks"

[Debian Bug Tracking System]

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

> severity #913910 normal
Bug #913910 [atop] atop crashed with "Malloc failed for 1826553824 deviated 
tasks"
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.

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

Bug#913910: atop crashed with "Malloc failed for 1826553824 deviated tasks"

[Marc Haber]

severity #913910 normal
thanks

On Mon, Nov 19, 2018 at 09:58:04AM +0100, Vincent Lefevre wrote:
> Raising to grave, because as soon as the system is slightly loaded
> (e.g. executing a "configure" script), atop fails.

Sorry, disagreed, you're the only one reporting this.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Leimen, Germany|  lose things."Winona Ryder | Fon: *49 6224 1600402
Nordisch by Nature |  How to make an American Quilt | Fax: *49 6224 1600421

Processed: Fwd: Processed (with 1 error): Re: Update to version 2.3.0-3 breaks Megaglest

[Debian Bug Tracking System]

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

> severity 914153 serious
Bug #914153 [libftgl2] Update to version 2.3.0-3 breaks Megaglest
Severity set to 'serious' from 'normal'
> stop
Stopping processing here.

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

Processed: severity of 911882 is serious

[Debian Bug Tracking System]

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

> severity 911882 serious
Bug #911882 [src:gnss-sdr] [gnss-sdr] package does not build with boost1.67
Severity set to 'serious' from 'wishlist'
> thanks
Stopping processing here.

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

Bug#914254: marked as done (bacula: fails to restore properly)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 12:04:29 +
with message-id 
and subject line Bug#914254: fixed in bacula 9.2.2-3
has caused the Debian Bug report #914254,
regarding bacula: fails to restore properly
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.)


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

On 20.11.18 21:59, Sven Hartge wrote:

[...] when "-u root -g root -k" is set, even though the process runs as
root, it doesn't have the proper capabilities anymore.
--- End Message ---
--- Begin Message ---
Source: bacula
Source-Version: 9.2.2-3

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

Debian distribution maintenance software
pp.
Carsten Leonhardt  (supplier of updated bacula package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 21 Nov 2018 11:53:57 +0100
Source: bacula
Binary: bacula bacula-common bacula-common-sqlite3 bacula-common-pgsql 
bacula-common-mysql bacula-director bacula-director-sqlite3 
bacula-director-mysql bacula-director-pgsql bacula-client bacula-fd 
bacula-server bacula-sd bacula-bscan bacula-console bacula-console-qt 
bacula-director-common
Architecture: source
Version: 9.2.2-3
Distribution: unstable
Urgency: high
Maintainer: Debian Bacula Team 
Changed-By: Carsten Leonhardt 
Description:
 bacula - network backup service - metapackage
 bacula-bscan - network backup service - bscan tool
 bacula-client - network backup service - client metapackage
 bacula-common - network backup service - common support files
 bacula-common-mysql - network backup service - MySQL common files
 bacula-common-pgsql - network backup service - PostgreSQL common files
 bacula-common-sqlite3 - network backup service - SQLite v3 common files
 bacula-console - network backup service - text console
 bacula-console-qt - network backup service - Bacula Administration Tool
 bacula-director - network backup service - Director daemon
 bacula-director-common - transitional package
 bacula-director-mysql - network backup service - MySQL storage for Director
 bacula-director-pgsql - network backup service - PostgreSQL storage for 
Director
 bacula-director-sqlite3 - network backup service - SQLite 3 storage for 
Director
 bacula-fd  - network backup service - file daemon
 bacula-sd  - network backup service - storage daemon
 bacula-server - network backup service - server metapackage
Closes: 914254
Changes:
 bacula (9.2.2-3) unstable; urgency=high
 .
   [ Sven Hartge ]
   * Regression fix for SysVinit: During a restore the FD wouldn't be able
 to set files to their original owners/groups when using parameter "-k",
 even when running as root:root, because the code removes all
 capabilities except CAP_DAC_READ_SEARCH.
 Rework the init-script to only use "-k" when the runtime user is not
 root. (Closes: #914254)
Checksums-Sha1:
 3868ac2dac7630ebaf430bacc97f2befe6e174bc 3598 bacula_9.2.2-3.dsc
 376c0e4411557d2ec89f40b3b91bd02560093007 76108 bacula_9.2.2-3.debian.tar.xz
 57d9ff9a7f62d1829e1248323ae2b91b7ab5aee5 10756 bacula_9.2.2-3_source.buildinfo
Checksums-Sha256:
 c8611d168f4c6c46e14ffba3c15d88b93ef97933f723d1b7f51a40dc6aca26e0 3598 
bacula_9.2.2-3.dsc
 fa425e80883e0a5b59994bd187bcf33882df8cc4b706296ada92e3874b062076 76108 
bacula_9.2.2-3.debian.tar.xz
 285aa60100cbbb2842506cbcf4d06a24bfe3ab44eb98edbca2ffd6dbcbbfb45c 10756 
bacula_9.2.2-3_source.buildinfo
Files:
 45848fa23a3a0200644089906d759ea3 3598 admin optional bacula_9.2.2-3.dsc
 0cfe156cdb0425a0e93434d121468a7f 76108 admin optional 
bacula_9.2.2-3.debian.tar.xz
 9fa1e7db63573a59afe06f53a45e2327 10756 admin optional 
bacula_9.2.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEETxO/995XSygF6EUmKrIctfbulV4FAlv1SGYPHGxlb0BkZWJp
YW4ub3JnAAoJECqyHLX27pVeCEwQAKSFgZiICC3ZxkSdxgJQRA5MgpDAJ7JNMYet
kEq5qPEUy4tjEXdt/V7a+Pq3aZ7Y6sT8n3Xky9Id2M2b2GS6MNsC3mRRqHPQ7A6V

Bug#914273: symfony fails a lot of autopkg tests, even on amd64

[Karlos GNU CON KERNEL LINUX]

Processed: block 909120 with 911793

[Debian Bug Tracking System]

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

> block 909120 with 911793
Bug #909120 {Done: Emmanuel Promayon 
} [src:camitk] camitk FTBFS: tests 
segfault
909120 was not blocked by any bugs.
909120 was not blocking any bugs.
Added blocking bug(s) of 909120: 911793
> thanks
Stopping processing here.

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

Bug#914273: symfony fails a lot of autopkg tests, even on amd64

[Matthias Klose]

Package: src:symfony
Version: 3.4.17+dfsg-1
Severity: serious
Tags: sid buster
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

please see
https://ci.debian.net/data/packages/unstable/amd64/s/symfony/latest-autopkgtest/log.gz

for the failed tests

Processed: reassign 911830 to src:scikit-learn

[Debian Bug Tracking System]

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

> reassign 911830 src:scikit-learn 0.20.0+dfsg-1
Bug #911830 [src:python3-sklearn] FTBFS on multiple architectures
Warning: Unknown package 'src:python3-sklearn'
Bug reassigned from package 'src:python3-sklearn' to 'src:scikit-learn'.
No longer marked as found in versions python3-sklearn/0.20.0+dfsg-1.
Ignoring request to alter fixed versions of bug #911830 to the same values 
previously set
Bug #911830 [src:scikit-learn] FTBFS on multiple architectures
Marked as found in versions scikit-learn/0.20.0+dfsg-1.
> thanks
Stopping processing here.

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

Processed: reassign 911830 to src:python3-sklearn

[Debian Bug Tracking System]

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

> reassign 911830 src:python3-sklearn 0.20.0+dfsg-1
Bug #911830 [python3-sklearn] FTBFS on multiple architectures
Bug reassigned from package 'python3-sklearn' to 'src:python3-sklearn'.
Warning: Unknown package 'src:python3-sklearn'
Warning: Unknown package 'src:python3-sklearn'
No longer marked as found in versions scikit-learn/0.20.0+dfsg-1.
Warning: Unknown package 'src:python3-sklearn'
Warning: Unknown package 'src:python3-sklearn'
Ignoring request to alter fixed versions of bug #911830 to the same values 
previously set
Warning: Unknown package 'src:python3-sklearn'
Bug #911830 [src:python3-sklearn] FTBFS on multiple architectures
Warning: Unknown package 'src:python3-sklearn'
The source 'python3-sklearn' and version '0.20.0+dfsg-1' do not appear to match 
any binary packages
Marked as found in versions python3-sklearn/0.20.0+dfsg-1.
Warning: Unknown package 'src:python3-sklearn'
> thanks
Stopping processing here.

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

Processed: block 907806 with 911830

[Debian Bug Tracking System]

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

> block 907806 with 911830
Bug #907806 {Done: Yangfl } [src:scikit-learn] 
scikit-learn: FTBFS in buster/sid (could not import 'distributed')
907806 was not blocked by any bugs.
907806 was not blocking any bugs.
Added blocking bug(s) of 907806: 911830
> thanks
Stopping processing here.

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

Bug#914270: ruby-sprockets-rails FTBFS: test failure

[Adrian Bunk]

Source: ruby-sprockets-rails
Version: 2.3.2+git-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=ruby-sprockets-rails=all=2.3.2%2Bgit-1=1542787326=0

...
┌──┐
│ Run tests for ruby2.5 from debian/ruby-tests.rake│
└──┘

RUBYLIB=/<>/ruby-sprockets-rails-2.3.2+git/debian/ruby-sprockets-rails/usr/lib/ruby/vendor_ruby:.
 
GEM_PATH=debian/ruby-sprockets-rails/usr/share/rubygems-integration/all:/var/lib/gems/2.5.0:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all
 ruby2.5 -S rake -f debian/ruby-tests.rake
/usr/bin/ruby2.5 -w -I"test"  
"/usr/lib/ruby/vendor_ruby/rake/rake_test_loader.rb" "test/test_helper.rb" 
"test/test_railtie.rb" "test/test_task.rb" -v
/usr/lib/ruby/vendor_ruby/active_support/core_ext/hash/slice.rb:21: warning: 
method redefined; discarding old slice
/usr/lib/ruby/vendor_ruby/active_support/core_ext/hash/keys.rb:8: warning: 
method redefined; discarding old transform_keys
/usr/lib/ruby/vendor_ruby/active_support/core_ext/hash/keys.rb:19: warning: 
method redefined; discarding old transform_keys!
/usr/lib/ruby/vendor_ruby/active_support/core_ext/enumerable.rb:20: warning: 
method redefined; discarding old sum
/usr/lib/ruby/vendor_ruby/active_support/core_ext/object/duplicable.rb:111: 
warning: BigDecimal.new is deprecated; use Kernel.BigDecimal method instead.
Run options: -v --seed 32539

# Running:

AutomaticDependenciesFromHelpersTest#test_ignores_missing_dependencies = 0.37 s 
= .
AutomaticDependenciesFromHelpersTest#test_dependency_added = 0.06 s = .
AutomaticDependenciesFromHelpersTest#test_truth = 0.08 s = .
HelperTest#test_truth = 0.05 s = .
PrecompileHelperTest#test_truth = 0.06 s = .
PrecompileHelperTest#test_debug_mode = 0.07 s = .
PrecompileHelperTest#test_asset_not_precompiled_error = 0.12 s = .
PrecompileHelperTest#test_non_javascripts_and_stylesheets = 0.06 s = .
PrecompileHelperTest#test_public_folder_fallback_works_correctly = 0.07 s = .
DebugDigestHelperTest#test_javascript_include_tag = 0.10 s = .
DebugDigestHelperTest#test_asset_digest_path = 0.06 s = .
DebugDigestHelperTest#test_stylesheet_link_tag = 0.11 s = .
DebugDigestHelperTest#test_stylesheet_path = 0.06 s = .
DebugDigestHelperTest#test_javascript_path = 0.07 s = .
DebugDigestHelperTest#test_asset_url = 0.07 s = .
DebugDigestHelperTest#test_asset_digest = 0.06 s = .
DebugDigestHelperTest#test_truth = 0.07 s = .
RelativeHostHelperTest#test_truth = 0.06 s = .
RelativeHostHelperTest#test_stylesheet_path = 0.06 s = .
RelativeHostHelperTest#test_asset_url = 0.08 s = .
RelativeHostHelperTest#test_javascript_path = 0.06 s = .
NoHostHelperTest#test_javascript_include_tag = 0.06 s = .
NoHostHelperTest#test_javascript_path = 0.07 s = .
NoHostHelperTest#test_stylesheet_link_tag = 0.06 s = .
NoHostHelperTest#test_truth = 0.05 s = .
NoHostHelperTest#test_stylesheet_path = 0.07 s = .
DebugHelperTest#test_truth = 0.06 s = .
DebugHelperTest#test_stylesheet_path = 0.07 s = .
DebugHelperTest#test_javascript_include_tag = 0.10 s = .
DebugHelperTest#test_javascript_path = 0.06 s = .
DebugHelperTest#test_stylesheet_link_tag = 0.10 s = .
DebugManifestHelperTest#test_truth = 0.06 s = .
DebugManifestHelperTest#test_javascript_path = 0.05 s = .
DebugManifestHelperTest#test_absolute_asset_path_error = 0.07 s = .
DebugManifestHelperTest#test_asset_digest = 0.05 s = .
DebugManifestHelperTest#test_javascript_include_tag = 0.06 s = .
DebugManifestHelperTest#test_stylesheet_link_tag = 0.07 s = .
DebugManifestHelperTest#test_asset_digest_path = 0.06 s = .
DebugManifestHelperTest#test_stylesheet_path = 0.07 s = .
TestTask#test_clean = 0.01 s = .
TestTask#test_clobber = 
/<>/ruby-sprockets-rails-2.3.2+git/debian/ruby-sprockets-rails/usr/lib/ruby/vendor_ruby/sprockets/rails/task.rb:53:
 warning: instance variable @cache_path not initialized
0.01 s = .
TestTask#test_precompile = 0.01 s = .
TestTask#test_precompile_without_manifest = 0.01 s = .
NoDigestHelperTest#test_asset_url = 0.07 s = .
NoDigestHelperTest#test_stylesheet_link_tag = 0.08 s = .
NoDigestHelperTest#test_stylesheet_path = 0.06 s = .
NoDigestHelperTest#test_asset_digest = DEPRECATED: Use assert_nil if expecting 
nil from /<>/ruby-sprockets-rails-2.3.2+git/test/test_helper.rb:275. 
This will fail in Minitest 6.
DEPRECATED: Use assert_nil if expecting nil from 
/<>/ruby-sprockets-rails-2.3.2+git/test/test_helper.rb:276. This will 
fail in Minitest 6.
0.06 s = .
NoDigestHelperTest#test_javascript_include_tag = 0.08 s = .
NoDigestHelperTest#test_javascript_path = 0.06 s = .
NoDigestHelperTest#test_truth = 0.06 s = .
DigestHelperTest#test_asset_digest = 0.07 s = .
DigestHelperTest#test_javascript_include_tag = 0.07 s = .
DigestHelperTest#test_asset_digest_path = 0.07 s = .
DigestHelperTest#test_javascript_path = 

Bug#914269: google-i18n-address FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 11

[Adrian Bunk]

Source: google-i18n-address
Version: 2.3.2-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=google-i18n-address=all=2.3.2-2=1542749879=0

...
=== FAILURES ===
___ test_downloader_country[None-file_names0-data0] 

tmpdir = local('/tmp/pytest-of-buildd/pytest-1/test_downloader_country_None_f0')
country = None, file_names = ('pl.json', 'us.json', 'all.json')
data = {'all.json': {'PL': 'dat\u0105', 'US': 'data'}, 'pl.json': {'PL': 
'dat\u0105'}, 'us.json': {'US': 'data'}}

@pytest.mark.parametrize('country, file_names, data', [
(None, ('pl.json', 'us.json', 'all.json'), {
'pl.json': {'PL': 'dat\u0105'},
'us.json': {'US': 'data'},
'all.json': {'PL': 'dat\u0105', 'US': 'data'}}),
('PL', ('pl.json', 'all.json'), {
'pl.json': {'PL': 'dat\u0105'},
'all.json': {'PL': 'dat\u0105'}})])
def test_downloader_country(tmpdir, country, file_names, data):
data_dir = tmpdir.join('data')
download(country)
for file_name in file_names:
assert data_dir.join(file_name).exists()
>   assert json.load(
data_dir.join(file_name), encoding='utf-8') == data[file_name]

tests/test_downloader.py:47: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3.6/json/__init__.py:296: in load
return loads(fp.read(),
/usr/lib/python3/dist-packages/py/_path/common.py:171: in read
return f.read()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 
input = b'{"PL": "dat\xc4\x85"}', final = True

def decode(self, input, final=False):
>   return codecs.ascii_decode(input, self.errors)[0]
E   UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 
11: ordinal not in range(128)

/usr/lib/python3.6/encodings/ascii.py:26: UnicodeDecodeError
 test_downloader_country[PL-file_names1-data1] _

tmpdir = local('/tmp/pytest-of-buildd/pytest-1/test_downloader_country_PL_fil0')
country = 'PL', file_names = ('pl.json', 'all.json')
data = {'all.json': {'PL': 'dat\u0105'}, 'pl.json': {'PL': 'dat\u0105'}}

@pytest.mark.parametrize('country, file_names, data', [
(None, ('pl.json', 'us.json', 'all.json'), {
'pl.json': {'PL': 'dat\u0105'},
'us.json': {'US': 'data'},
'all.json': {'PL': 'dat\u0105', 'US': 'data'}}),
('PL', ('pl.json', 'all.json'), {
'pl.json': {'PL': 'dat\u0105'},
'all.json': {'PL': 'dat\u0105'}})])
def test_downloader_country(tmpdir, country, file_names, data):
data_dir = tmpdir.join('data')
download(country)
for file_name in file_names:
assert data_dir.join(file_name).exists()
>   assert json.load(
data_dir.join(file_name), encoding='utf-8') == data[file_name]

tests/test_downloader.py:47: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
/usr/lib/python3.6/json/__init__.py:296: in load
return loads(fp.read(),
/usr/lib/python3/dist-packages/py/_path/common.py:171: in read
return f.read()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

self = 
input = b'{"PL": "dat\xc4\x85"}', final = True

def decode(self, input, final=False):
>   return codecs.ascii_decode(input, self.errors)[0]
E   UnicodeDecodeError: 'ascii' codec can't decode byte 0xc4 in position 
11: ordinal not in range(128)

/usr/lib/python3.6/encodings/ascii.py:26: UnicodeDecodeError
= 2 failed, 41 passed in 1.04 seconds ==
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: cd 
/<>/.pybuild/cpython3_3.6_i18address/build; python3.6 -m pytest 
tests
dh_auto_test: pybuild --test --test-pytest -i python{version} -p "3.7 3.6" 
returned exit code 13
make: *** [debian/rules:5: binary-indep] Error 25

Bug#914268: llvm-toolchain-7: baseline violation on armhf

[Adrian Bunk]

Source: llvm-toolchain-7
Version: 1:7.0.1~+rc2-1~exp1
Severity: grave
Control: block 912164 by -1
Control: affects -1 src:rust-pulldown-cmark src:mesa src:cargo

LLVM now violates the armhf baseline by using NEON,
this can be reproduced as easy as:

(sid_armhf-dchroot)bunk@abel:~$ llvm-config-7
Illegal instruction
(sid_armhf-dchroot)bunk@abel:~$

gdb confirms that this is due to NEON usage.


Additionally, this also causes FTBFS on some of our buildds:
https://buildd.debian.org/status/fetch.php?pkg=rust-pulldown-cmark=armhf=0.2.0-1=1542734241=0
https://buildd.debian.org/status/fetch.php?pkg=cargo=armhf=0.31.0-4=1542700136=0
https://buildd.debian.org/status/fetch.php?pkg=mesa=armhf=18.2.5-2=1542760450=0

It might even result in silently misbuilt packages, just imagine
mesa would have disabled the feature instead of AC_MSG_ERROR.


Note that these mentioned buildd problems are just the visible
tip of the iceberg, the baseline violation is a problem that
must be fixed even when the buildds change.

Processed: llvm-toolchain-7: baseline violation on armhf

[Debian Bug Tracking System]

Processing control commands:

> block 912164 by -1
Bug #912164 [release.debian.org] transition: llvm-defaults
912164 was blocked by: 912563 912561 912162 893189 912564 912163
912164 was blocking: 912163
Added blocking bug(s) of 912164: 914268
> affects -1 src:rust-pulldown-cmark src:mesa src:cargo
Bug #914268 [src:llvm-toolchain-7] llvm-toolchain-7: baseline violation on armhf
Added indication that 914268 affects src:rust-pulldown-cmark, src:mesa, and 
src:cargo

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

Bug#914175: lightning is not installable after binNMUs

[Holger Schröder]

Same here, upgrade wants to remove lightning


...

Bug#913005: marked as done (ruby-rack: CVE-2018-16471: Possible XSS vulnerability in Rack)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 09:53:04 +
with message-id 
and subject line Bug#913005: fixed in ruby-rack 1.6.4-6
has caused the Debian Bug report #913005,
regarding ruby-rack: CVE-2018-16471: Possible XSS vulnerability in Rack
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.)


-- 
913005: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-rack
Version: 1.6.4-4
Severity: grave
Tags: patch security upstream

Hi,

The following vulnerability was published for ruby-rack.

CVE-2018-16471[0]:
Possible XSS vulnerability in Rack

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16471
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16471
[1] https://www.openwall.com/lists/oss-security/2018/11/05/2

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: ruby-rack
Source-Version: 1.6.4-6

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated ruby-rack package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 21 Nov 2018 10:44:19 +0100
Source: ruby-rack
Binary: ruby-rack
Built-For-Profiles: nocheck
Architecture: source all
Version: 1.6.4-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Chris Lamb 
Description:
 ruby-rack  - modular Ruby webserver interface
Closes: 913005
Changes:
 ruby-rack (1.6.4-6) unstable; urgency=medium
 .
   * CVE-2018-16471: Prevent a possible XSS vulnerability where a malicious
 request could impact the HTTP/HTTPS scheme returned to the underlying
 application. (Closes: #913005)
   * Drop trailing whitespace in debian/changelog.
   * debian/control:
 - Add myself to Uploaders.
 - wrap-and-sort -sa.
   * Use HTTPS URI in debian/copyright.
Checksums-Sha1:
 98c3b87bb6571f6af285a3274a41ba4e46c866f0 2226 ruby-rack_1.6.4-6.dsc
 1f03db9df519104cef4af179684731d3c899cf6a 8484 ruby-rack_1.6.4-6.debian.tar.xz
 c4ca91360b85877d7f084a3ad6cf7aa5cd9ddc92 88788 ruby-rack_1.6.4-6_all.deb
 4bfd86838cf777aaf6a0d4377ae5f6798346001f 8756 ruby-rack_1.6.4-6_amd64.buildinfo
Checksums-Sha256:
 0f515bbff85074c959b2c7988672822db7c5e310c85ab142d4c6005838da93ab 2226 
ruby-rack_1.6.4-6.dsc
 3b9f28019295f14d91fc0cbc555e14ea3cc6eff92832093c53e1d4d335e445ad 8484 
ruby-rack_1.6.4-6.debian.tar.xz
 bd555ea1378073edd8d83e5ffcf700b20210aa8ad40cedc4b80560fac49f9ba8 88788 
ruby-rack_1.6.4-6_all.deb
 ff787d785b495943e30c603f091e107d14759b32be3aa42c128b8193cb464fa1 8756 
ruby-rack_1.6.4-6_amd64.buildinfo
Files:
 da54d39f2df83680dd7151730b3c8ac1 2226 ruby optional ruby-rack_1.6.4-6.dsc
 ed171b59dc44c0060aef74017052b923 8484 ruby optional 
ruby-rack_1.6.4-6.debian.tar.xz
 f4310539f83b611d9d0d9f58c9f75428 88788 ruby optional ruby-rack_1.6.4-6_all.deb
 bffd852f43e17bac0c180f5c0ae713d6 8756 ruby optional 
ruby-rack_1.6.4-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwv5L0nHBObhsUz5GHpU+J9QxHlgFAlv1KU8ACgkQHpU+J9Qx
Hlijxg/+N0kIxzDDcwJWGi0cne0Nn877M+HfLZKXWME3ZdaCoujSNBEK3UCrqQiY
sefsr6IBhj8CrMVfh8swtgfMGnNBaWZ53abhJyuwrVOEoYL9HSjKO2k1YlNlpSU+
YELhlqmtKDXwvNNBqGcGxfPQ4wLU2W5eXMaxYeFY2TnrsxMVZDsOQOwiM1Q3qqVE
8LoFFiJAjXreTeOIQjBWVrr1iFD4JfKEsBu1twnArZC5b5zeIDK8KXRfc0fJFcgx
7xOd1FASf0A3d9b00vCESv0dVq41IEKKGKAA2Ti878mYPPlLeppDQoVlT41HDzof
HWAA2shAwc/bJPJXiTX6JQXTowvOhMyDT0/hdtdi9EB0EBmdFz9I5BG9TGwd/JuX
9JH6twgsoKsshFn9xFEUlBGQb7CA9LrPxVQWWSlE8zGv99FdDFTn43zGXf8u80k+
AWeBe7vFmiuKJEDxB0jFjjvPZS/a0vq5Vx53nnTv6U83JRRxM1VuU8ctIC1s0CJd
QUsfKq2G7fSW56CaDAfRhEH5uoYF6pvqEa2fZLLMEGddharBdLFPGQ7idzTESvvi
z2VUcN3pVWKPqAu6mlzL+2CjCKCyljrxQyprajc6LFGHqXRHideIei4bN23vedaV
HyZIyytT0dSVqiPHRSYDaX3ZTayPDi5A6opyzjQtLuLLZ0F9wbo=
=Pklj
-END PGP SIGNATURE End Message ---

Bug#913005: Bug #913005 in ruby-rack marked as pending

[Chris Lamb]

Control: tag -1 pending

Hello,

Bug #913005 in ruby-rack 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-rack/commit/d9656d3c58c18c89c579354a145de3e65f42b26b


CVE-2018-16471: Prevent a possible XSS vulnerability where a malicious request 
could impact the HTTP/HTTPS scheme returned to the underlying application. 
(Closes: #913005)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/913005

Processed: Bug #913005 in ruby-rack marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #913005 [src:ruby-rack] ruby-rack: CVE-2018-16471: Possible XSS 
vulnerability in Rack
Ignoring request to alter tags of bug #913005 to the same tags previously set

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

Bug#913708: marked as done (node-mapnik ftbfs in unstable)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 09:20:33 +
with message-id 
and subject line Bug#913708: fixed in node-mapnik 3.7.2+dfsg-3
has caused the Debian Bug report #913708,
regarding node-mapnik ftbfs in unstable
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.)


-- 
913708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913708
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:node-mapnik
Version:
Severity: serious
Tags: sid buster

node-mapnik ftbfs in unstable, with

/usr/include/vector_tile_geometry_encoder_pbf.ipp:305:48:   required from here
/usr/include/vector_tile_geometry_encoder_pbf.ipp:70:35: error: call of
overloaded 'encode_geometry_pbf(const mapbox::geometry::empty&,
protozero::pbf_writer&, int32_t&, int32_t&)' is ambiguous
 return encode_geometry_pbf(geom, feature_, x_, y_);
~~~^~~~
/usr/include/vector_tile_geometry_encoder_pbf.ipp:204:27: note: candidate: 'bool
mapnik::vector_tile_impl::encode_geometry_pbf(const
mapbox::geometry::multi_point&, protozero::pbf_writer&, int32_t&,
int32_t&)'
 MAPNIK_VECTOR_INLINE bool
encode_geometry_pbf(mapbox::geometry::multi_point const& geom,
   ^~~
/usr/include/vector_tile_geometry_encoder_pbf.ipp:232:27: note: candidate: 'bool
mapnik::vector_tile_impl::encode_geometry_pbf(const
mapbox::geometry::line_string&, protozero::pbf_writer&, int32_t&,
int32_t&)'
 MAPNIK_VECTOR_INLINE bool
encode_geometry_pbf(mapbox::geometry::line_string const& line,
   ^~~
/usr/include/vector_tile_geometry_encoder_pbf.ipp:246:27: note: candidate: 'bool
mapnik::vector_tile_impl::encode_geometry_pbf(const
mapbox::geometry::multi_line_string&, protozero::pbf_writer&,
int32_t&, int32_t&)'
 MAPNIK_VECTOR_INLINE bool
encode_geometry_pbf(mapbox::geometry::multi_line_string const& 
geom,
   ^~~
/usr/include/vector_tile_geometry_encoder_pbf.ipp:265:27: note: candidate: 'bool
mapnik::vector_tile_impl::encode_geometry_pbf(const
mapbox::geometry::polygon&, protozero::pbf_writer&, int32_t&, 
int32_t&)'
 MAPNIK_VECTOR_INLINE bool
encode_geometry_pbf(mapbox::geometry::polygon const& poly,
   ^~~
/usr/include/vector_tile_geometry_encoder_pbf.ipp:279:27: note: candidate: 'bool
mapnik::vector_tile_impl::encode_geometry_pbf(const
mapbox::geometry::multi_polygon&, protozero::pbf_writer&, int32_t&,
int32_t&)'
 MAPNIK_VECTOR_INLINE bool
encode_geometry_pbf(mapbox::geometry::multi_polygon const& geom,
   ^~~
/usr/include/vector_tile_geometry_encoder_pbf.ipp:299:27: note: candidate: 'bool
mapnik::vector_tile_impl::encode_geometry_pbf(const
mapbox::geometry::geometry&, protozero::pbf_writer&,
int32_t&, int32_t&)'
 MAPNIK_VECTOR_INLINE bool
encode_geometry_pbf(mapbox::geometry::geometry const& geom,
   ^~~
In file included from /usr/include/vector_tile_processor.ipp:3,
 from /usr/include/vector_tile_processor.hpp:210,
 from ../src/mapnik_map.cpp:15:
/usr/include/vector_tile_geometry_feature.hpp: In instantiation of 'void
mapnik::vector_tile_impl::geometry_to_feature_pbf_visitor::operator()(const T&)
[with T = mapbox::geometry::empty]':
--- End Message ---
--- Begin Message ---
Source: node-mapnik
Source-Version: 3.7.2+dfsg-3

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

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated node-mapnik package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 21 Nov 2018 09:21:49 +0100
Source: node-mapnik
Binary: node-mapnik
Architecture: source amd64
Version: 3.7.2+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Bas Couwenberg 
Description:
 node-mapnik - bindings to the Mapnik tile rendering library for Node.js
Closes: 911344 913708
Changes:
 node-mapnik 

Bug#910736: marked as done (ruby-progressbar: installs files with generic names in /usr/bin)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 09:05:23 +
with message-id 
and subject line Bug#910736: fixed in ruby-progressbar 1.9.0-2
has caused the Debian Bug report #910736,
regarding ruby-progressbar: installs files with generic names in /usr/bin
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.)


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

Hello,

The new package ruby-progressbar version 1.9.0-1 installs the files:
/usr/bin/setup
/usr/bin/console

I think it should not install these files with too generic names.

thanks,


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

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

Versions of packages ruby-progressbar depends on:
ii  ruby1:2.5.1
ii  ruby2.1 [ruby-interpreter]  2.1.5-4
ii  ruby2.2 [ruby-interpreter]  2.2.4-1

ruby-progressbar recommends no packages.

ruby-progressbar suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ruby-progressbar
Source-Version: 1.9.0-2

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

Debian distribution maintenance software
pp.
Cédric Boutillier  (supplier of updated ruby-progressbar 
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: Tue, 20 Nov 2018 22:55:41 +0100
Source: ruby-progressbar
Binary: ruby-progressbar
Architecture: source
Version: 1.9.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Cédric Boutillier 
Description:
 ruby-progressbar - Text progress bar library for Ruby
Closes: 910736
Changes:
 ruby-progressbar (1.9.0-2) unstable; urgency=medium
 .
   * Do not install files bin/console and bin/setup (Closes: #910736)
Checksums-Sha1:
 7385cd54e7fc0fb13aa03d00c8f2cf625bf29df5 1819 ruby-progressbar_1.9.0-2.dsc
 16174f365fa1f95da0e6a25b0440b1d9fce8a0ab 6044 
ruby-progressbar_1.9.0-2.debian.tar.xz
 feae80e7a6cc8ead7489ee343baeb187954a784f 13650 
ruby-progressbar_1.9.0-2_source.buildinfo
Checksums-Sha256:
 528406f8788d98a3ec54355246d77b2f2e3ddb3e22e4b5110ae0766ad743f836 1819 
ruby-progressbar_1.9.0-2.dsc
 299b99fcaca09677f7fa1099d0cfc425f46e67264bc64487155755548720e0f0 6044 
ruby-progressbar_1.9.0-2.debian.tar.xz
 166a42e6d1cad36b02ddb4b26307ac002af139eda7f8c6c113c7abe5b12dae73 13650 
ruby-progressbar_1.9.0-2_source.buildinfo
Files:
 f0d6b365434d9f37fccde3a66f35bca1 1819 ruby optional 
ruby-progressbar_1.9.0-2.dsc
 df55dc4eb8e4ef37a95411992cb107e2 6044 ruby optional 
ruby-progressbar_1.9.0-2.debian.tar.xz
 7662b42deb3ab1a6071ff9ed3cb212cf 13650 ruby optional 
ruby-progressbar_1.9.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEnM1rMZ2/jkCrGr0aia+CtznNIXoFAlv1HEEACgkQia+CtznN
IXpxfwf9GDWShI9/SoNJytLXhCkFKGtbOMNXZJ7fHZt5AimctLBDWUyzCu0slapo
J7uZQoKM7EpVbXRA6fswRJM/t+R26hQhPJev7yo+GlW0y1dXwQB1KIuBeQXqJTKf
khnMyhHd0xCiJixYgDvqMTclZZpUdLJ1FzhsJz8JB2H0CtCL64o0TNEfZ+ga+4vi
xM/3yBl7SNVyhDU0whRZcj++cR92t+Mwqv4tzVB36F8IjcGGPB9ohz2Js+p96Ipt
klEvUZDAsARd4YaBQ43j2DWdFMN3i8TXsP12iE+j0aHYYDQ9ACFWapnTs+PryRSl
DqBDJ/dLu18mGDhuDZ1Bjd/AeMIqvQ==
=P2lQ
-END PGP SIGNATURE End Message ---

Bug#912060: marked as done (botch FTBFS: W504 line break after binary operator)

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 09:04:35 +
with message-id 
and subject line Bug#912060: fixed in botch 0.21-7
has caused the Debian Bug report #912060,
regarding botch FTBFS: W504 line break after binary operator
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.)


-- 
912060: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912060
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: botch
Version: 0.21-6
Severity: serious
Tags: ftbfs

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

...
   debian/rules override_dh_auto_test-arch
make[1]: Entering directory '/build/1st/botch-0.21'
/usr/bin/make test
make[2]: Entering directory '/build/1st/botch-0.21'
# FIXME: add more tests
#./tests.py
#OCAMLPATH=/build/1st/botch-0.21/dose/_build ocamlbuild -classic-display 
-use-ocamlfind -cflags "-w +a-4-9-24" tests.native
#./tests.native
pyflakes3 tools/*.py
# E402 is triggered by the sys.path.append() statement in front of import of 
utils
# see https://github.com/PyCQA/pycodestyle/issues/264
pycodestyle --ignore=E402,E722 tools/*.py
tools/add-arch.py:33:22: W504 line break after binary operator
tools/build-order-from-zero.py:170:27: W504 line break after binary operator
tools/build-order-from-zero.py:203:27: W504 line break after binary operator
tools/buildgraph2packages.py:46:22: W504 line break after binary operator
tools/calcportsmetric.py:56:22: W504 line break after binary operator
tools/calcportsmetric.py:57:22: W504 line break after binary operator
tools/calcportsmetric.py:58:22: W504 line break after binary operator
tools/calcportsmetric.py:59:22: W504 line break after binary operator
tools/calcportsmetric.py:63:14: W504 line break after binary operator
tools/calcportsmetric.py:64:14: W504 line break after binary operator
tools/calcportsmetric.py:68:14: W504 line break after binary operator
tools/calcportsmetric.py:69:14: W504 line break after binary operator
tools/check-ma-same-versions.py:49:22: W504 line break after binary operator
tools/check-ma-same-versions.py:50:22: W504 line break after binary operator
tools/checkfas.py:31:22: W504 line break after binary operator
tools/checkfas.py:32:22: W504 line break after binary operator
tools/checkfas.py:35:30: W504 line break after binary operator
tools/checkfas.py:38:30: W504 line break after binary operator
tools/checkfas.py:39:30: W504 line break after binary operator
tools/convert-arch.py:34:22: W504 line break after binary operator
tools/dose2html.py:111:15: W504 line break after binary operator
tools/dose2html.py:112:15: W504 line break after binary operator
tools/dose2html.py:114:15: W504 line break after binary operator
tools/dose2html.py:115:15: W504 line break after binary operator
tools/dose2html.py:116:15: W504 line break after binary operator
tools/dose2html.py:139:11: W504 line break after binary operator
tools/dose2html.py:140:11: W504 line break after binary operator
tools/dose2html.py:141:11: W504 line break after binary operator
tools/dose2html.py:142:11: W504 line break after binary operator
tools/dose2html.py:143:11: W504 line break after binary operator
tools/dose2html.py:147:11: W504 line break after binary operator
tools/dose2html.py:174:19: W504 line break after binary operator
tools/dose2html.py:206:11: W504 line break after binary operator
tools/dose2html.py:207:11: W504 line break after binary operator
tools/dose2html.py:208:11: W504 line break after binary operator
tools/dose2html.py:209:11: W504 line break after binary operator
tools/dose2html.py:210:11: W504 line break after binary operator
tools/dose2html.py:216:9: W504 line break after binary operator
tools/dose2html.py:258:19: W504 line break after binary operator
tools/dose2html.py:340:11: W504 line break after binary operator
tools/dose2html.py:341:11: W504 line break after binary operator
tools/dose2html.py:348:15: W504 line break after binary operator
tools/dose2html.py:366:15: W504 line break after binary operator
tools/dose2html.py:521:25: W504 line break after binary operator
tools/dose2html.py:527:30: W504 line break after binary operator
tools/dose2html.py:530:30: W504 line break after binary operator
tools/dose2html.py:569:13: W504 line break after binary operator
tools/dose2html.py:570:13: W504 line break after binary operator
tools/droppable-diff.py:11:22: W504 line break after binary operator
tools/droppable-union.py:10:51: W504 line break after binary operator
tools/droppable-union.py:11:51: W504 line break after binary operator
tools/droppable-union.py:12:51: W504 line break after binary operator

Processed: closing 914262

[Debian Bug Tracking System]

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

> close 914262 2.47-5
Bug #914262 [xkeycaps] Segfaults on "Write Output" if more than 8 keysyms per 
key are present
Marked as fixed in versions xkeycaps/2.47-5.
Bug #914262 [xkeycaps] Segfaults on "Write Output" if more than 8 keysyms per 
key are present
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#914262: closing 914262

[Christoph Berg]

close 914262 2.47-5
thanks

Processed: tagging 883525, tagging 878598

[Debian Bug Tracking System]

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

> tags 883525 + help
Bug #883525 [pdf2htmlex] pdf2htmlex: FTBFS with poppler 0.61.1
Added tag(s) help.
> tags 878598 + help
Bug #878598 [src:pdf2htmlex] pdf2htmlex FTBFS on amd64/arm64: AssertionError: 
cannot execute pdf2htmlEX
Added tag(s) help.
> thanks
Stopping processing here.

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

Processed: Bug #910736 in ruby-progressbar marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #910736 [ruby-progressbar] ruby-progressbar: installs files with generic 
names in /usr/bin
Added tag(s) pending.

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

Bug#910736: Bug #910736 in ruby-progressbar marked as pending

[Cédric Boutillier]

Control: tag -1 pending

Hello,

Bug #910736 in ruby-progressbar 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-progressbar/commit/f5b96e0a465e29716d7756c438b8bef3ce5363c7


Do not install files bin/console and bin/setup (Closes: #910736)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/910736

Bug#910220: marked as done (libdmtx-dev: copyright file missing after upgrade (policy 12.5))

[Debian Bug Tracking System]

Your message dated Wed, 21 Nov 2018 08:49:22 +
with message-id 
and subject line Bug#910220: fixed in libdmtx 0.7.5-2
has caused the Debian Bug report #910220,
regarding libdmtx-dev: 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.)


-- 
910220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libdmtx-dev
Version: 0.7.5-1
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/ch-docs.html#copyright-information

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

This was observed on the following upgrade paths:

  stretch -> buster

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

0m25.9s ERROR: WARN: Inadequate results from running adequate!
  libdmtx-dev:amd64: missing-copyright-file /usr/share/doc/libdmtx-dev/copyright

  MISSING COPYRIGHT FILE: /usr/share/doc/libdmtx-dev/copyright
  # ls -lad /usr/share/doc/libdmtx-dev
  drwxr-xr-x 2 root root 40 Aug 19 07:34 /usr/share/doc/libdmtx-dev
  # ls -la /usr/share/doc/libdmtx-dev/
  total 0
  drwxr-xr-x  2 root root   40 Aug 19 07:34 .
  drwxr-xr-x 91 root root 1940 Aug 19 07:34 ..


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/ch-maintainerscripts.html#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


libdmtx-dev_0.7.5-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libdmtx
Source-Version: 0.7.5-2

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

Debian distribution maintenance software
pp.
Roberto Lumbreras  (supplier of updated libdmtx package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 21 Nov 2018 08:29:23 +0100
Source: libdmtx
Binary: libdmtx0a libdmtx-dev
Architecture: source amd64
Version: 0.7.5-2
Distribution: unstable
Urgency: low
Maintainer: Roberto Lumbreras 
Changed-By: Roberto Lumbreras 
Description:
 libdmtx-dev - Data Matrix barcodes (development files and static libraries)
 libdmtx0a  - Data Matrix barcodes (runtime library)
Closes: 910220
Changes:
 libdmtx (0.7.5-2) unstable; urgency=low
 .
   * Proper fix for simple_test compiler warnings.
   * Misc fixes for lintian warnings.
   * Fix for copyright file missing after upgrade. (Closes: #910220)
Checksums-Sha1:
 83a9b10524f5ab788908a3c202e7b35e79a8a690 1783 libdmtx_0.7.5-2.dsc
 725e9914eb0f8da4235c1588fa1e31d6fe966daa 9636 libdmtx_0.7.5-2.debian.tar.xz
 5545fb09d4d5560df2b2d247d99d8d0e0e7fdef6 48104 libdmtx-dev_0.7.5-2_amd64.deb
 f472f44ab2f5863ac8ae4a61918eef431559d885 101012 
libdmtx0a-dbgsym_0.7.5-2_amd64.deb
 d0b876482bdd30cceedf0c75396246ada60f6921 55656 libdmtx0a_0.7.5-2_amd64.deb
 565f864d70fa2496890275550efb06b1a257de04 6325 libdmtx_0.7.5-2_amd64.buildinfo
Checksums-Sha256:
 2363f204af33a6dcd684c20a501f12593df55965db4133bece4a9fc30a147cae 1783 
libdmtx_0.7.5-2.dsc
 588e29f3b494c29c6262c1481d03c6219096e8434114da79e6fc177df503284d 9636 
libdmtx_0.7.5-2.debian.tar.xz
 29772f9486b640e9af62b007bdb09111f8599f41ea04c8056405ecd8193787da 48104 
libdmtx-dev_0.7.5-2_amd64.deb
 4008759971d17ab30ccc62e1a477db8d92e1a0aba5612584bda109f11530a7c3 101012 
libdmtx0a-dbgsym_0.7.5-2_amd64.deb
 

Bug#914262: Segfaults on "Write Output" if more than 8 keysyms per key are present

[Christoph Berg]

Package: xkeycaps
Version: 2.47-4.1
Severity: grave
Tags: stretch patch

The code only deals with 8 names per key, but unfortunately doesn't expose that
number as a constant that is easily changed. Clip to 8 so we don't segfault.

 Program received signal SIGSEGV, Segmentation fault.
 strlen () at ../sysdeps/x86_64/strlen.S:106
 106   ../sysdeps/x86_64/strlen.S: Datei oder Verzeichnis nicht gefunden.
 (gdb) bt
 #0  strlen () at ../sysdeps/x86_64/strlen.S:106
 #1  0x76a2fa45 in __GI__IO_fputs (
 str=str@entry=0x7fff000a ,
 fp=fp@entry=0x559f6da0) at iofputs.c:33
 #2  0x555dc2a4 in fprintf (__fmt=0x555e49e1 "%s", 
__stream=)
 at /usr/include/x86_64-linux-gnu/bits/stdio2.h:97
 #3  button_write (button=, client_data=,
 call_data=) at commands.c:629
 #4  0x77944aad in ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6
 #5  0x77944f15 in ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6
 #6  0x77945bdd in _XtTranslateEvent () from 
/usr/lib/x86_64-linux-gnu/libXt.so.6
 #7  0x7791def2 in XtDispatchEventToWidget () from 
/usr/lib/x86_64-linux-gnu/libXt.so.6
 #8  0x7791e8dd in ?? () from /usr/lib/x86_64-linux-gnu/libXt.so.6
 #9  0x7791e9b9 in XtDispatchEvent () from 
/usr/lib/x86_64-linux-gnu/libXt.so.6
 #10 0x555d2d96 in xkeycaps_main_loop (app=0x559a81a0, 
keyboard=)
 at xkeycaps.c:232
 #11 main (argc=, argv=) at xkeycaps.c:355
 (gdb) f 3
 #3  button_write (button=, client_data=,
 call_data=) at commands.c:629
 629 fprintf (out, "%s", differences[i].names[j]);
 (gdb) p i
 $1 = 1
 (gdb) p j
 $2 = 9
 (gdb) p differences
 $3 = {{key = 0x55a0dde0, count = 3, names = {0x76e13fc6 
<_XkeyTable+134> "Escape",
   0x555e4448 "NoSymbol", 0x76e13fc6 <_XkeyTable+134> "Escape", 0x0,
   0x1d7 ,
   0x1000 ,
   0x8 ,
   0x5a42ab91 }}, {key = 
0x55a0dfa0,
 count = 10, names = {0x76e144be <_XkeyTable+1406> "F1",
   0x76e144be <_XkeyTable+1406> "F1", 0x76e144be <_XkeyTable+1406> 
"F1",
   0x76e144be <_XkeyTable+1406> "F1", 0x76e144be <_XkeyTable+1406> 
"F1",
   0x76e144be <_XkeyTable+1406> "F1",
   0x76e1dfaf <_XkeyTable+41071> "XF86Switch_VT_1",
   0x76e144be <_XkeyTable+1406> "F1"}}, {key = 0x55a0e160, count = 
10, names = {
   0x76e144c7 <_XkeyTable+1415> "F2", 0x76e144c7 <_XkeyTable+1415> 
"F2",
   0x76e144c7 <_XkeyTable+1415> "F2", 0x76e144c7 <_XkeyTable+1415> 
"F2",
   0x76e144c7 <_XkeyTable+1415> "F2", 0x76e144c7 <_XkeyTable+1415> 
"F2",
   0x76e1dfc5 <_XkeyTable+41093> "XF86Switch_VT_2",
   0x76e144c7 <_XkeyTable+1415> "F2"}},

--- a/commands.c
+++ b/commands.c
@@ -440,6 +440,7 @@ button_write (button, client_data, call_
 keysyms = XGetKeyboardMapping (XtDisplay (widget),
key->key.keycode,
1, );
+if (count > 8) count = 8; /* FIXME: we are only prepared for 8 
names per key, clip here */
 if (! keysyms) count = 0;
 all [all_count].key = key;
 for (; count > 0; count--)


Christoph

Bug#914183: shutter: No way to install shutter in debian buster

[Ludovic CHEVALIER]

OK. Thanks for your answer.