Bug#886664: marked as done (node-d3-timer FTBFS: test failure)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 08:43:43 +
with message-id 
and subject line Bug#886664: fixed in node-d3-timer 1.0.7-5
has caused the Debian Bug report #886664,
regarding node-d3-timer FTBFS: test failure
to be marked as done.

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

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


-- 
886664: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886664
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-d3-timer
Version: 1.0.7-3
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=node-d3-timer=all=1.0.7-3=1515230593=0

...
not ok 11 should be in range
  ---
operator: inRange
expected: [ 440, 460 ]
actual:   466
at: Test.tape.Test.inRange (/<>/test/inRange.js:4:8)
stack: |-
  Error: should be in range
  at Test.assert [as _assert] (/usr/lib/nodejs/tape/lib/test.js:224:54)
  at Test.bound [as _assert] (/usr/lib/nodejs/tape/lib/test.js:76:32)
  at Test.tape.Test.inRange (/<>/test/inRange.js:4:8)
  at Test.bound [as inRange] (/usr/lib/nodejs/tape/lib/test.js:76:32)
  at /<>/test/interval-test.js:35:44
  at Array.forEach ()
  at /<>/test/interval-test.js:35:12
  at tick (/<>/build/d3-timer.js:308:5)
  at timerFlush (/<>/build/d3-timer.js:157:48)
  at Timeout.wake [as _onTimeout] 
(/<>/build/d3-timer.js:167:5)
  ...
...
1..106
# tests 106
# pass  105
# fail  1

debian/rules:16: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 123
--- End Message ---
--- Begin Message ---
Source: node-d3-timer
Source-Version: 1.0.7-5

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-d3-timer package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Jan 2019 08:44:29 +0100
Source: node-d3-timer
Binary: node-d3-timer
Architecture: source
Version: 1.0.7-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Closes: 886664
Description: 
 node-d3-timer - efficient queue to manage thousands of concurrent animations
Changes:
 node-d3-timer (1.0.7-5) unstable; urgency=medium
 .
   * Team upload
   * Disable more test due to debci poor perf (Closes: #886664)
Checksums-Sha1: 
 491de9322d4be0c432b8e9aa1b09dea5a036e0f2 2126 node-d3-timer_1.0.7-5.dsc
 28f6148670c5bf2935d252d1c5659389b62d16ac 3868 
node-d3-timer_1.0.7-5.debian.tar.xz
Checksums-Sha256: 
 01e6435d4ce9063d623a98207e3a6a249827fb51beee6b09eb5ce2eb8d1ea1cc 2126 
node-d3-timer_1.0.7-5.dsc
 74d8988fec24041dfd89e19f5840ac8440851153f7d7ebf11cfc994c11db49c2 3868 
node-d3-timer_1.0.7-5.debian.tar.xz
Files: 
 d7e8a5f2e89092e2de6e76de839ee895 2126 javascript optional 
node-d3-timer_1.0.7-5.dsc
 b481d82398553c134a07ae23e920a1c6 3868 javascript optional 
node-d3-timer_1.0.7-5.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxMENUACgkQ9tdMp8mZ
7umkcw//Wzm5n5v3bkE6qhnqtvZoHB6F7AnaASAHcjYGUJkTClVc9rzIfwWNBlAm
zoPqvo2Jb4dRACQHns60zgalfoWg5mnFZIPxe4GBr9i8TFLdOIefBuzcboSOzTJT
svVsCCJRd2eptRdc+xsai9PAzlB1PVnpjCSKBHqoCnJCaLOHIS1mq8BXZ/msm4LL
KhbmIXVLKKClUMQevdkSXp2KmKpWeAzGUPg22xDFEL3zlUC6fFEIlslDPQ5ahczb
BeXj62pMjT5uZddNggWD/AczfSJxGwTfpOy8WJ4TKbXeJk1n3ar4mj9icessblqo
GoCSLa3n6SVyx1uKDF94UO8fHpVBGI+T3NqNYoefIQ7lTOE1EE0Z4rqzngePPMsZ
RgdFwaCyMYzf8ZyyI5yZu+utU9OC+4ItkCdH4sRs47v1EntGgQaAHOQVnz7AvRwY
WeDBV+hMthkkJ0vImIpgEcSj74hJbt60qY8rjNMXGRuX3ZipbZx3tboW7vVDDaBL
ws4L8EqiURWT9s2XVwbP3I40np30Ff3bYFdFhEeSH/z0+CTHli482sEQlWk6ntXR
yG4KmvtvlcQQQkDuYcNzSIY5xTfEMj/csQrX5XKEUAatM2Ks/m9bQXVrE1KOKLsV
VpbuQKtBLfZT3kZ9tVDs64fyP3UuWFEjCx5DAXxWFa6RBVO1I3E=
=KvOx
-END PGP SIGNATURE End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> close 899099 0.17+dfsg1-1
Bug #899099 [freecad] freecad crashes at start with reference to XInitThreads
Marked as fixed in versions freecad/0.17+dfsg1-1.
Bug #899099 [freecad] freecad crashes at start with reference to XInitThreads
Marked Bug as done
>
End of message, stopping processing here.

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

Bug#918799: marked as done (Please mark binary packages as "Multi-Arch: foreign")

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 10:34:15 +
with message-id 
and subject line Bug#918799: fixed in python-gnupg 0.4.4-1
has caused the Debian Bug report #918799,
regarding Please mark binary packages as "Multi-Arch: foreign"
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.)


-- 
918799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918799
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-gnupg
Version: 0.4.3-2

Dear Maintainer,

In a multi-arch setup, the "python3-gnupg" and "python-gnupg" packages
should be able to satisfy dependencies from other packages, as the
Python interpreter in combination with python-gnupg can be used
regardless of the architecture of the depending packet.

For instance, when installing an i386 package which depends on
"python3-gnupg" on amd64, the package manager should allow an already
installed python3-gnupg (along with the python3:amd64) to satisfy the
dependency.

See

for details, and "python3-six" or "python3-nose" as a somewhat similar
packages that already do this.

Regards, Rotty
--- End Message ---
--- Begin Message ---
Source: python-gnupg
Source-Version: 0.4.4-1

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

Debian distribution maintenance software
pp.
Elena Grandi  (supplier of updated python-gnupg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Jan 2019 10:47:25 +0100
Source: python-gnupg
Binary: python-gnupg python3-gnupg
Architecture: source
Version: 0.4.4-1
Distribution: unstable
Urgency: medium
Maintainer: Elena Grandi 
Changed-By: Elena Grandi 
Description:
 python-gnupg - Python wrapper for the GNU Privacy Guard (Python 2.x)
 python3-gnupg - Python wrapper for the GNU Privacy Guard (Python 3.x)
Closes: 918799
Changes:
 python-gnupg (0.4.4-1) unstable; urgency=medium
 .
   * Mark all packages Multi-Arch: foreign (closes: #918799).
   * New upstream release
   * Updated Standards-Version to 4.3.0 (no changes needed)
Checksums-Sha1:
 58bcde4e62a1ee7bfc0db5bc10f631fba2681480 1765 python-gnupg_0.4.4-1.dsc
 302d644684765fcd2daf35dcb8e780a25d0e12e1 48292 python-gnupg_0.4.4.orig.tar.gz
 2c434b34ed71b0d10c5a532f0c184a7585678961 7160 
python-gnupg_0.4.4-1.debian.tar.xz
 9858bbe320b54874c6dd71fa54ac39c304fdb82c 9964 
python-gnupg_0.4.4-1_source.buildinfo
Checksums-Sha256:
 918adc51bc5ddff74bb2f0c2d2798cdb82ecaa3ff3e398eebabcbadd7652461d 1765 
python-gnupg_0.4.4-1.dsc
 45daf020b370bda13a1429c859fcdff0b766c0576844211446f9266cae97fb0e 48292 
python-gnupg_0.4.4.orig.tar.gz
 5386cffb32e9543d52e80aadb653bd984dd523cfe99dfdcfc426fd630eea8599 7160 
python-gnupg_0.4.4-1.debian.tar.xz
 9cc190bdb088721c7280f289b4e55e8bdf80711dd30865d5cc2ebc5fe903e19e 9964 
python-gnupg_0.4.4-1_source.buildinfo
Files:
 55feb36bf2ec18e81604653c21337f5f 1765 python optional python-gnupg_0.4.4-1.dsc
 c5d54f5a1bafc412f9b5a03ee06cb82e 48292 python optional 
python-gnupg_0.4.4.orig.tar.gz
 0d9ef43657cb5cb27d4906bc19e438b6 7160 python optional 
python-gnupg_0.4.4-1.debian.tar.xz
 a11c8bb55c443b54185a4094b236cec5 9964 python optional 
python-gnupg_0.4.4-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEtvPLnIYlAkFEv4aRWawWRpiv/+UFAlxMMLcACgkQWawWRpiv
/+UojAf/TtXLe7kibcRpuSeSHByYgYq43lSSjoeMKq7Y2rePbgnGy+M45gUPJ3c9
wKjP7ao9K2FsabUWy3vt1wFcAfdjCtaiFbeA08KiI+cqfMENbmgdamJFp2B/8EHJ
BUpw1i7IkyV0RQpOKtnBlyg4Zpkx/hplFlBKbx7n6TxY7QXwy1w3pKpR9QsLDby1
drndr8irWKr38V3LdOltMgldXpDpV8xgT/11nYbILMmcHxdlbBQjRgyFxcmITHD/
djbVeFldGk3BI0Bie3on2FvUchBJZVhUVYVSRHIzM+MapL0LqQ/SxZe5amdQ19Ll
R4f5+Yhd87kh9ioCejghvJDmeohVCQ==
=etWo
-END PGP SIGNATURE End Message ---

Bug#911959: marked as done (RFS: git-lab/0.14.0-1 [ITP])

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 11:39:01 +
with message-id <20190126113901.jucjtiehtbrc5...@master.debian.org>
and subject line no longer at mentors
has caused the Debian Bug report #911959,
regarding RFS: git-lab/0.14.0-1 [ITP]
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.)


-- 
911959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: debian...@lists.debian.org
Control: block -1 by 905240
Control: block -1 by 906986
Control: block -1 by 905262

  Dear mentors,

  I am looking for a sponsor for my package "git-lab"

  Some dependencies may still be the 'sponsorship-requests' queue, or
in NEW. Please check out the blocking bugs.

 * Package name: git-lab
   Version : 0.14.0-1
   Upstream Author : Zaq? Wiedmann 
 * URL : https://github.com/zaquestion/lab
 * License : Unlicense
   Section : devel

  It builds those binary packages:

git-lab- Clone, fork, and interact with repositories on GitLab

  If you have access to Salsa, please have a look at:

https://salsa.debian.org/go-team/packages/git-lab

Otherwise (and to get the orig.tar.gz), please visit the following URL:

https://mentors.debian.net/package/git-lab


  Alternatively, one can download the package with dget using this command:

dget -x 
https://mentors.debian.net/debian/pool/main/g/git-lab/git-lab_0.14.0-1.dsc

  More information about git-lab can be obtained from https://www.example.com.

  Changes since the last upload:

  * Initial release (Closes: #898246)

  The package will be maintained as part of the Debian Go team going
forward. Thank you!

  Regards,
   Felix Lechner
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 4691--- End Message ---

Bug#920463: marked as done (texlive-base breaks fig2dev autopkgtest)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 12:39:24 +
with message-id 
and subject line Bug#920463: fixed in texlive-base 2018.20190126-1
has caused the Debian Bug report #920463,
regarding texlive-base breaks fig2dev autopkgtest
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.)


-- 
920463: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920463
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: texlive-base, fig2dev
Control: found -1 texlive-base/2018.20190122-1
Control: found -1 fig2dev/1:3.2.7a-3
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of texlive-base the autopkgtest of fig2dev fails in
testing when that autopkgtest is run with the binary packages of
texlive-base from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
texlive-base   from testing2018.20190122-1
fig2devfrom testing1:3.2.7a-3
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of texlive-base to
testing [1]. Due to the nature of this issue, I filed this bug report
against both packages. Can you please investigate the situation and
reassign the bug to the right package? If needed, please change the
bug's severity.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=texlive-base

https://ci.debian.net/data/autopkgtest/testing/amd64/f/fig2dev/1779958/log.gz
Test tikz output language.

 33: conditionally allocate \XFigu   FAILED (output.at:175)
 34: pattern with stroke color equal to fill color   ok

Create and embed bitmaps in fig-file.

 35: gif ok
 36: jpegok
 37: pcx ok
 38: png ok
 39: png with smoothing  ok
 40: ppm ok
 41: tiffok
 42: xbm ok
 43: xbm with smoothing  ok
 44: xpm skipped
(bitmaps.at:104)

Creation of temporary files.

 45: eps with acscii preview ok
 46: eps with tiff preview   ok

Embed postscript variants.

 47: epsiok
 48: postscript, created by fig2dev  ok
 49: postscript, created by latexok

## - ##
## Test results. ##
## - ##

ERROR: 46 tests were run,
1 failed unexpectedly.
3 tests were skipped.
## -- ##
## testsuite.log was created. ##
## -- ##

Please send `fig2dev/tests/testsuite.log' and all information you think
might help:

   To: 
   Subject: [fig2dev 3.2.7a] testsuite: 33 failed

You may investigate any problem if you feel able to do so, in which
case the test suite provides a good starting point.  Its output may
be found below `fig2dev/tests/testsuite.dir'.

make[1]: *** [Makefile:583: check-local] Error 1
make[1]: Leaving directory
'/tmp/autopkgtest-lxc.choif6me/downtmp/build.4Dg/src/fig2dev/tests'
make: *** [Makefile:449: check-am] Error 2
autopkgtest [04:50:27]: test fig2dev-testsuite: ---]




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: texlive-base
Source-Version: 2018.20190126-1

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

Debian distribution maintenance software
pp.
Norbert Preining  (supplier of updated texlive-base 
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-

Processed: wiggle 1.1-1 is in debian

[Debian Bug Tracking System]

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

> close 920433
Bug #920433 [sponsorship-requests] RFS: wiggle/1.1-1 [QA]
Marked Bug as done
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
920433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920433
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:

> close 886538 0.17+dfsg1-1
Bug #886538 [freecad] freecad: Error "No module named WebGui" at startup. 
Cannot see startup screen.
Bug #882510 [freecad] freecad: Python module WebGUI missing
Marked as fixed in versions freecad/0.17+dfsg1-1.
Marked as fixed in versions freecad/0.17+dfsg1-1.
Bug #886538 [freecad] freecad: Error "No module named WebGui" at startup. 
Cannot see startup screen.
Bug #882510 [freecad] freecad: Python module WebGUI missing
Marked Bug as done
Marked Bug as done
>
End of message, stopping processing here.

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

Bug#896970: marked as done (RFS: odp/1.19.0.2-1 [ITP])

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 11:37:24 +
with message-id <20190126113724.3qyowdf3crhxc...@master.debian.org>
and subject line no longer at mentors
has caused the Debian Bug report #896970,
regarding RFS: odp/1.19.0.2-1 [ITP]
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.)


-- 
896970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896970
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist


  I am looking for a sponsor for my package "odp"

 * Package name: odp
   Version : 1.19.0.0-1
   Upstream Author : Linaro / ODP community
 * URL : https://www.opendataplane.org/
 * License : [fill in]
   Section : libs

  It builds those binary packages:

 libodp-common-dev - OpenDataPlane library (common development files)
 libodp-generic-dev - OpenDataPlane reference implementation library 
(development)
 libodp-generic119 - OpenDataPlane reference implementation library (runtime)
 libodphelper-dev - OpenDataPlane helper library (development)
 libodphelper119 - OpenDataPlane helper library (runtime)
 odp-doc- OpenDataPlane library (documentation)
 odp-linux-examples - OpenDataPlane examples

  To access further information about this package, please visit the following 
URL:

  https://mentors.debian.net/package/odp


  Alternatively, one can download the package with dget using this command:

dget -x https://mentors.debian.net/debian/pool/main/o/odp/odp_1.19.0.0-1.dsc

  More information about odp can be obtained from
  https://www.opendataplane.org.


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

Kernel: Linux 4.15.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 4690--- End Message ---

Bug#918293: marked as done (node-xmpp build depends on node-node-stringprep that is currently not in buster)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 14:55:21 +0100
with message-id 

and subject line Re: node-xmpp build depends on node-node-stringprep that is 
currently not in buster
has caused the Debian Bug report #918293,
regarding node-xmpp build depends on node-node-stringprep that is currently not 
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.)


-- 
918293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-xmpp
Version: 0.3.2-3
Severity: serious
Tags: ftbfs buster sid
Control: block -1 by 895029

node-xmpp build depends on node-node-stringprep that is currently
not in buster due to #895029.
--- End Message ---
--- Begin Message ---
node-node-stringprep is fixed and should move to buster along with ongoing
nodejs transition.

Closing.
--- End Message ---

Bug#907826: marked as done (RFS: gnomint/1.3.0-1 [QA])

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 11:58:47 +
with message-id <20190126115846.tbqv7x2t6kuzq...@master.debian.org>
and subject line no longer at mentors
has caused the Debian Bug report #907826,
regarding RFS: gnomint/1.3.0-1 [QA]
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.)


-- 
907826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: important

Dear mentors,

I'm looking for a sponsor for a QA upload of "gnomint".

 * Package name: gnomint
   Version : 1.3.0-1
   Upstream Author : David Marín Carreño 
 * URL : https://gnomint.sf.net
 * License : GPL-3+
   Section : gnome

It builds this binary package:

gnomint- X.509 Certification Authority management tool for GNOME

To access further information about this package, please visit the
following URL:

  https://mentors.debian.net/package/gnomint

Alternatively, one can download the package with dget using this command:

  dget -x 
https://mentors.debian.net/debian/pool/main/g/gnomint/gnomint_1.3.0-1.dsc

Changes since the last upload:

  * QA upload.
  * New upstream release.
  * debian/compat: Set to 11.
  * debian/control: Run wrap-and-sort -ast.
(Build-Depends): Bump debhelper requirement to match the compat level.
Remove autotools-dev and libgconf2-dev.
(Standards-Version): Claim compliance with 4.2.1 as of this release.
  * debian/rules: Enable all hardening.  Remove --with autotools_dev.
(override_dh_auto_install): Remove gconf schemas stuff.
  * debian/patches/682432.patch: Refresh.
  * debian/patches/02-cflags.patch: Remove configure hunk; refresh and
remove -Werror.  Fix typo in the patch description.
  * debian/patches/01-ldd.patch:
  * debian/patches/10_gnutlsv3.diff: Delete, fixed upstream.
  * debian/patches/fix-autoreconf.patch: New, fix autoreconf failure.
  * debian/patches/gsettings-port.patch: New, migrate from GConf to
GSettings (Closes: #885817).  I believe the switch to GSettings also
closes: #631768 which was probably due to the fact that GConf does not
apply changes atomically.
  * debian/patches/export-private-key-crash.patch: New, fix crash when
exporting the private key (Closes: #855200).  Thanks to Karl E.
Jorgensen for the report.
  * debian/patches/desktop-file.patch: New, fix some lintian complaints.
  * debian/patches/spelling-errors.patch: New, self-explanatory.
  * debian/patches/series: Update.
  * debian/watch: New file.
  * debian/pixmaps/gnomint.xpm:
  * debian/gnomint.menu:
  * debian/gnomint.install: Delete.
  * debian/copyright: Declare format.
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 4692--- End Message ---

Bug#915058: marked as done (RFS: python-socketio-realtime-server/2.1.0-1 [QA])

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 11:59:48 +
with message-id <20190126115948.6tn456q4ib5kc...@master.debian.org>
and subject line no longer at mentors
has caused the Debian Bug report #915058,
regarding RFS: python-socketio-realtime-server/2.1.0-1 [QA]
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.)


-- 
915058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-socketio-realtime-server
Severity: wishlist
X-Debbugs-CC: mike.gabr...@das-netzwerkteam.de

Hi, 

Please **don't sponsor and upload** this package because my AM (Mike Gabriel)
will review it for me.

 * Package name: python-socketio-realtime-server
   Version : 2.1.0-1
   Upstream Author : Miguel Grinberg 
 * URL : https://github.com/miguelgrinberg/python-socketio
 * License : MIT
   Section : python

It builds this binary package:

  python3-socketio-realtime-server - Python implementation of the Socket.IO
realtime server

To access further information about these packages, please visit the
following URL:

https://mentors.debian.net/sponsors/rfs-howto/python-socketio-realtime-server

Alternatively, one can download the package with dget using this command:

  dget -x
https://mentors.debian.net/debian/pool/main/p/python-socketio-realtime-server/python-socketio-realtime-server_2.1.0-1.dsc

More information about kickpass can be obtained from
https://github.com/miguelgrinberg/python-socketio

Best regards,

-- 
Paulo Henrique de Lima Santana (phls)
Curitiba - Brasil
Membro da Comunidade Curitiba Livre
Site: http://www.phls.com.br
GNU/Linux user: 228719  GPG ID: 0443C450

Apoie a campanha pela igualdade de gênero #HeForShe (#ElesPorElas)  
http://www.heforshe.org/pt


pgpNVv2UsTegw.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 4693--- End Message ---

Bug#917694: marked as done (nuitka: FTBFS: build-dependency not installable: python-imaging)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 13:33:50 +0100
with message-id 

and subject line close 917694
has caused the Debian Bug report #917694,
regarding nuitka: FTBFS: build-dependency not installable: python-imaging
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.)


-- 
917694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917694
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nuitka
Version: 0.6.0.6+ds-1
Severity: serious
Justification: FTBFS on amd64
Tags: buster sid
Usertags: ftbfs-20181229 ftbfs-buster

Hi,

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

Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 9), dh-python | base-files (<< 9.6), 
> python (>= 2.6.6-2), python-all-dbg (>= 2.6.6-2), python-all-dev (>= 
> 2.6.6-2), python-setuptools, rst2pdf (>= 0.14-2), python-imaging | 
> python-pil, scons (>= 2.0.0), python3-all-dev (>= 3.2), python3-all-dbg (>= 
> 3.2), python3-setuptools, python-appdirs | base-files (<< 7.2), 
> python3-appdirs | base-files (<< 7.2), strace, chrpath, gdb
> Filtered Build-Depends: debhelper (>= 9), dh-python, python (>= 2.6.6-2), 
> python-all-dbg (>= 2.6.6-2), python-all-dev (>= 2.6.6-2), python-setuptools, 
> rst2pdf (>= 0.14-2), python-imaging, scons (>= 2.0.0), python3-all-dev (>= 
> 3.2), python3-all-dbg (>= 3.2), python3-setuptools, python-appdirs, 
> python3-appdirs, strace, chrpath, gdb
> dpkg-deb: building package 'sbuild-build-depends-nuitka-dummy' in 
> '/<>/resolver-kOsmDm/apt_archive/sbuild-build-depends-nuitka-dummy.deb'.
> dpkg-scanpackages: warning: Packages in archive but missing from override 
> file:
> dpkg-scanpackages: warning:   sbuild-build-depends-core-dummy 
> sbuild-build-depends-nuitka-dummy
> dpkg-scanpackages: info: Wrote 2 entries to output Packages file.
> Ign:1 copy:/<>/resolver-kOsmDm/apt_archive ./ InRelease
> Get:2 copy:/<>/resolver-kOsmDm/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/resolver-kOsmDm/apt_archive ./ Release.gpg
> Get:4 copy:/<>/resolver-kOsmDm/apt_archive ./ Sources [620 B]
> Get:5 copy:/<>/resolver-kOsmDm/apt_archive ./ Packages [678 B]
> Fetched 2261 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install nuitka build dependencies (apt-based resolver)
> --
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Reading state information...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-nuitka-dummy : Depends: python-imaging but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.

The full build log is available from:
   http://aws-logs.debian.net/2018/12/29/nuitka_0.6.0.6+ds-1_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 ---
close 917694

The issue has been resolved in 0.6.1 (which was not uploaded) and
fixed with upload of 0.6.1.1 which contains the fix.--- End Message ---

Bug#915328: marked as done (coinor-symphony FTBFSwith latest TeX Live: LaTeX Error: Option clash for package color.)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 13:19:15 +
with message-id 
and subject line Bug#915328: fixed in coinor-symphony 5.6.16+repack1-1.1
has caused the Debian Bug report #915328,
regarding coinor-symphony FTBFSwith latest TeX Live: LaTeX Error: Option clash 
for package color.
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.)


-- 
915328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: coinor-symphony
Version: 5.6.16+repack1-1
Severity: serious
Tags: ftbfs

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

...
make[2]: Leaving directory '/build/1st/coinor-symphony-5.6.16+repack1'
cd Doc && ( latex man ; latex man ; dvipdfm man )
This is pdfTeX, Version 3.14159265-2.6-1.40.19 (TeX Live 2019/dev/Debian) 
(preloaded format=latex)
 restricted \write18 enabled.
entering extended mode
(./man.tex
LaTeX2e <2018-04-01> patch level 5
(/usr/share/texlive/texmf-dist/tex/latex/base/book.cls
Document Class: book 2014/09/29 v1.4h Standard LaTeX document class
(/usr/share/texlive/texmf-dist/tex/latex/base/bk11.clo))
(/usr/share/texlive/texmf-dist/tex/latex/graphics/epsfig.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphicx.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/keyval.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics/graphics.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics/trig.sty)
(/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/graphics.cfg)
(/usr/share/texlive/texmf-dist/tex/latex/graphics-def/dvips.def
(/usr/share/texmf/tex/latex/html/html.sty)
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsmath.sty
For additional information on amsmath, use the `?' option.
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amstext.sty
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsgen.sty))
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsbsy.sty)
(/usr/share/texlive/texmf-dist/tex/latex/amsmath/amsopn.sty))
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amssymb.sty
(/usr/share/texlive/texmf-dist/tex/latex/amsfonts/amsfonts.sty))
(/usr/share/texlive/texmf-dist/tex/latex/preprint/fullpage.sty)
(/usr/share/texlive/texmf-dist/tex/latex/easy/easyeqn.sty
Document Style `easyeqn' v1.94 <2002/03/18>.
(/usr/share/texlive/texmf-dist/tex/latex/easy/easy.sty
Document Style `easy' v1.1 <2001/05/31>.
)) (/usr/share/texlive/texmf-dist/tex/latex/fancyvrb/fancyvrb.sty
Style option: `fancyvrb' v3.0 <2018/11/01> (tvz)
(/usr/share/texlive/texmf-dist/tex/latex/xcolor/xcolor.sty
(/usr/share/texlive/texmf-dist/tex/latex/graphics-cfg/color.cfg)))
(/usr/share/texlive/texmf-dist/tex/latex/listings/listings.sty
(/usr/share/texlive/texmf-dist/tex/latex/listings/lstmisc.sty)
(/usr/share/texlive/texmf-dist/tex/latex/listings/listings.cfg))
(/usr/share/texlive/texmf-dist/tex/latex/url/url.sty)
(/usr/share/texlive/texmf-dist/tex/latex/splitindex/splitidx.sty)

! LaTeX Error: Option clash for package color.

See the LaTeX manual or LaTeX Companion for explanation.
Type  H   for immediate help.
 ...  
  
l.85 
 
? 
! Emergency stop.
--- End Message ---
--- Begin Message ---
Source: coinor-symphony
Source-Version: 5.6.16+repack1-1.1

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated coinor-symphony package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 11 Jan 2019 13:53:51 +0200
Source: coinor-symphony
Binary: coinor-symphony coinor-libsymphony3 coinor-libsymphony-dev 
coinor-libsymphony-doc
Architecture: source
Version: 5.6.16+repack1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Adrian Bunk 
Description:
 coinor-libsymphony-dev - COIN-OR solver for mixed-integer linear programs 
(developer files
 coinor-libsymphony-doc - COIN-OR solver for mixed-integer linear programs 
(documentation)

Bug#920517: marked as done (node-gyp: depends on cruft package nodejs-dev)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 13:36:42 +
with message-id 
and subject line Bug#920517: fixed in node-gyp 3.8.0-3
has caused the Debian Bug report #920517,
regarding node-gyp: depends on cruft package nodejs-dev
to be marked as done.

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

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


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

Hi,

nodejs-dev is no longer built. Please check whether you can use
libnode-dev as a replacement.


Andreas
--- End Message ---
--- Begin Message ---
Source: node-gyp
Source-Version: 3.8.0-3

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

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated node-gyp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Jan 2019 14:23:07 +0100
Source: node-gyp
Architecture: source
Version: 3.8.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jérémy Lal 
Closes: 920517
Changes:
 node-gyp (3.8.0-3) unstable; urgency=medium
 .
   * Depends libnode-dev instead of nodejs-dev (Closes:#920517)
Checksums-Sha1:
 03d4352174383f2c138c5c488e75b6de05708e75 1975 node-gyp_3.8.0-3.dsc
 8372988e6ac444043e487dba13b4b51b9ec56c53 5676 node-gyp_3.8.0-3.debian.tar.xz
 3ddb487f1fc427c9b62bf4912e6b9cbfb1cfc7fa 6009 node-gyp_3.8.0-3_source.buildinfo
Checksums-Sha256:
 cbcd4789b46a1873f91e17d1c89e8406634fbd2b1c7ce6cfd120bccb8650e198 1975 
node-gyp_3.8.0-3.dsc
 b9f7ffd8ffdbe9b40abfc87cbf2f9a407c1ae4fb0fc70605dd811e70344b02a1 5676 
node-gyp_3.8.0-3.debian.tar.xz
 caa32dda4b13b7bef1b7b4f6676292f050d43870eb80b806715edc160303dae2 6009 
node-gyp_3.8.0-3_source.buildinfo
Files:
 2d0d9a4d29d4918a1af432fef36643ba 1975 javascript optional node-gyp_3.8.0-3.dsc
 d90d247f580a8c9faadf169dcffba5ae 5676 javascript optional 
node-gyp_3.8.0-3.debian.tar.xz
 a704e6e95db7ecc4e53730a05c600fec 6009 javascript optional 
node-gyp_3.8.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAlxMX2QSHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN03NcQALYNC2iiqMheW7jHOW1ualRiRgIroe/p
k9fkHiljW6DcxRiE53HH//CL54+IxeNxlaUwxRNJJjYprwo1ITh2nbjEwMzMCfmv
ZfGKemS5B7rsv7G3VLwfI9bjpbR7kYYzyEJYtyc/ugrf8fxIKlfVjgLOMbOnysSI
W4Tfb7To7KpnNi4a81oPVhMNLL7xW00wCAK2EC5y5fWM991gb4aG38dN4cM+8uSq
Wik5IXARWzhZTenSmTO8q47COz911CwUYg/EHlAEIwxZcqm2DCHJr/l1zEf2Dcv1
HM7xd10krXlwRaXlJkRf5249o4bE9fF44KqSFuym9mxDbN2OINcOY2oiSIkO0bZP
IBzk+ev3CRWGu52XuzPdpvfyA9R+YyjeSCp1mY3cK4kaENKVULivHVHiKoYdcJpi
w6fftC+fX7/COy550YN0aSrSIsKgGLE7IBTqu2k7JJHct8GzokoDtxxeI2Kpxd7M
Vfhx+Blj94ZH3amqrUeYqs73ktFnIUgScO0tKo2l8B1GRVGQud7P7zI9ge/JPvJq
xOIpKuOfE+Bd01Cjybu3jhi2MkEct+YcUDuXJo0ywlli/SWVIlxZ/kE4/HU1ELuy
7Z+z7IdcwmHYMNWRCaFWPNuFZHwS0CEahvW81jCEUlvCtuHk1Eg1YkAI1KAEOKiI
BgjQXWsEIiGi
=xHuz
-END PGP SIGNATURE End Message ---

Bug#920514: marked as done (node-nodedbi: switch build-depends from nodejs-dev to libnode-dev)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 13:36:52 +
with message-id 
and subject line Bug#920514: fixed in node-nodedbi 1.0.12-4
has caused the Debian Bug report #920514,
regarding node-nodedbi: switch build-depends from nodejs-dev to libnode-dev
to be marked as done.

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

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


-- 
920514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-nodedbi
Version: 1.0.12-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)

Hi,

the old transitional package nodejs-dev is no longer built, please
update your build-depends to libnode-dev.


Andreas
--- End Message ---
--- Begin Message ---
Source: node-nodedbi
Source-Version: 1.0.12-4

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-nodedbi package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Jan 2019 14:07:41 +0100
Source: node-nodedbi
Binary: node-nodedbi node-nodedbi-dbgsym
Architecture: source amd64
Version: 1.0.12-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Description:
 node-nodedbi - libdbi interface for Node.js
Closes: 920514
Changes:
 node-nodedbi (1.0.12-4) unstable; urgency=medium
 .
   * Rebuilt against libnode-dev (Closes: #920514)
Checksums-Sha1:
 aa2c0b963b6f6111ff3e01698b7e53e390abf5f5 2070 node-nodedbi_1.0.12-4.dsc
 727eead1442919e7b77124cc5596a6040af936bb 3088 
node-nodedbi_1.0.12-4.debian.tar.xz
 c7f98b00705f206913a0b560b938b53b75069df8 172916 
node-nodedbi-dbgsym_1.0.12-4_amd64.deb
 f312394de79430b5755c7eb012e18c4851101fec 9273 
node-nodedbi_1.0.12-4_amd64.buildinfo
 7274267d42cfb7428d9fa0c44e7cf4b8c0f24d7f 183548 node-nodedbi_1.0.12-4_amd64.deb
Checksums-Sha256:
 6d66e294418f7732cfd8715578d5c1b020443f41230245fc8ba1eb01e9fcd9ac 2070 
node-nodedbi_1.0.12-4.dsc
 6ee1bffe8e09aeb34da01134dbad00151ad5c5b0d63d75ccc4499c49852c9038 3088 
node-nodedbi_1.0.12-4.debian.tar.xz
 d2cd7df54c41e454c9067a935292789f74248918e64b3f05eb705df0ed03bcce 172916 
node-nodedbi-dbgsym_1.0.12-4_amd64.deb
 e4e534cf6ca0df6ac6510f09322f73f5618de02a8084540d77623e38816a 9273 
node-nodedbi_1.0.12-4_amd64.buildinfo
 e5f9d4d4f7d9a0dfa8164b01262962c799ac47c464511d1aaee8bd12a78926d0 183548 
node-nodedbi_1.0.12-4_amd64.deb
Files:
 b6d9e79bcbd68a3c9850f7799071dc50 2070 javascript optional 
node-nodedbi_1.0.12-4.dsc
 7874bd11835fbbd49dcc778846c09c1c 3088 javascript optional 
node-nodedbi_1.0.12-4.debian.tar.xz
 da0eea58eee162b5cd1d211d36db17e7 172916 debug optional 
node-nodedbi-dbgsym_1.0.12-4_amd64.deb
 87bd7bc0d91513256266080a40ebf61a 9273 javascript optional 
node-nodedbi_1.0.12-4_amd64.buildinfo
 cf58102e4b72ce3d79efbd9d2e712919 183548 javascript optional 
node-nodedbi_1.0.12-4_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxMXAwACgkQ9tdMp8mZ
7umyHA/+KsS3n8Okxw2uf9bq+wceDNYxEO+BibVeNiqLnlDI2wkqosNLrruxoh8o
5WJfs0nZQN1GCfE3zp4vuRH1WmVw/qTRh5P06uf/3fmgw7u2QbpTkE0PlU1sVjGB
5p40+6f8EKd2Vx70OiY7CwLmG4EJN5QVMUsBcZenPdDXoy716LzmbbgLCIbSqxS1
PA1YX7UPdTUWXqzZY0Fa+gWUkDN5gxaV1f5zrHUxKh/bTpzjJqPt65sEuNJRyKSE
jG9Sbcm+FDcwa7VMEpnm/BgIntnIHqm5p2rfmRU50Tu22eoBllBtlBiqcb+kdIvM
ip5cjrWC0vd9/cMVZIg7xHIOQr+7JqJFi2oeU/5mQ08iTr6/b8Uj5Wne37C6VXDp
RBOBN3G0FeYPbWuQ0QiHXI795bfjVt+kd5Ovp4tsGBeq0/l50PFjkvqZ3XJqTMCm
u6xXjMQggr5eAzEANxLZmORegfF1GyMIaC1CVJPnG/9oP+ZpeZI78PY3nlKsxhEt
VGuGjFjz91nfB6PbpZ2iaE09FGL1jP3iZqE5Ar+fDVhF7uC2zaIBuMjT4HOzOAAU
pGd/6VxDENeIgKAEw3iu0F3MdG/rfpbytcRj+g5xkFe169nzmcZzis2thQ6lb1aY
GZMy9fV6Xyl226RSWybTza01C7OCUOiVJGrbjL8uhaG0JBsY2WQ=
=AXFy
-END PGP SIGNATURE End Message ---

Bug#919935: marked as done (ITP: golang-github-protonmail-go-autostart -- A Go library to run a command after login)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 12:22:00 +
with message-id <20190126122200.rs77ogs4m2ja7...@master.debian.org>
and subject line in debian
has caused the Debian Bug report #919935,
regarding ITP: golang-github-protonmail-go-autostart -- A Go library to run a 
command after login
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.)


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

Package: wnpp
Severity: wishlist
Owner: Micah Anderson 

* Package name: golang-github-protonmail-go-autostart
  Version : 0.0~git20181114.c527205-1
  Upstream Author : 
* URL : https://github.com/ProtonMail/go-autostart
* License : MIT
  Programming Lang: Go
  Description : A Go library to run a command after login

 A Go library to run a command after login.

 This is a dependency for the package riseupvpn that is also being packaged.
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 4694--- End Message ---

Bug#829287: marked as done (RFP: cava -- terminal audio visualiser)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 12:25:14 +
with message-id <20190126122514.75fcczhmnxu74...@master.debian.org>
and subject line in debian
has caused the Debian Bug report #829287,
regarding RFP: cava -- terminal audio visualiser
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.)


-- 
829287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=829287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
X-Debbugs-Cc: debian-de...@lists.debian.org
Package: wnpp
Severity: wishlist
Owner: Nicolas Braud-Santoni 

* Package name: cava
  Version : 0.4.1
  Upstream Author : Karl Stravestrand 
* URL : http://karlstav.github.io/cava
* License : Expat
  Programming Lang: C
  Description : Curses-like audio visualizer

C.A.V.A. is a bar spectrum audio visualizer for the terminal,
using ALSA, pulseaudio or fifo buffer for input.

This program is not intended for scientific use.
It's written to look responsive and aesthetic when used on music. 
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 4696--- End Message ---

Bug#920156: marked as done (RFP: clfft -- a software library containing FFT functions written in OpenCL)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 12:23:27 +
with message-id <20190126122327.r6pfv66o5bhco...@master.debian.org>
and subject line already in debian
has caused the Debian Bug report #920156,
regarding RFP: clfft -- a software library containing FFT functions written in 
OpenCL
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.)


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

* Package name: clfft
  Version : 2.12.2
  Upstream Author : Bragadeesh Natarajan
* URL : https://github.com/clMathLibraries/clFFT
* License : Apache-2.0
  Programming Lang: C++
  Description : a software library containing FFT functions written in 
OpenCL

clFFT is a software library containing FFT functions written in OpenCL. In 
addition to GPU devices, the library also supports running on CPU devices to 
facilitate debugging and heterogeneous programming.

Introduction to clFFT

The FFT is an implementation of the Discrete Fourier Transform (DFT) that makes 
use of symmetries in the FFT definition to reduce the mathematical intensity 
required from O(N^2) to O(N log2(N)) when the sequence length N is the product 
of small prime factors. Currently, there is no standard API for FFT routines. 
Hardware vendors usually provide a set of high-performance FFTs optimized for 
their systems: no two vendors employ the same interfaces for their FFT 
routines. clFFT provides a set of FFT routines that are optimized for AMD 
graphics processors, but also are functional across CPU and other compute 
devices.

The clFFT library is an open source OpenCL library implementation of discrete 
Fast Fourier Transforms. The library:

provides a fast and accurate platform for calculating discrete FFTs.

works on CPU or GPU backends.

supports in-place or out-of-place transforms.

supports 1D, 2D, and 3D transforms with a batch size that can be greater 
than 1.

supports planar (real and complex components in separate arrays) and 
interleaved (real and complex components as a pair contiguous in memory) 
formats.

supports dimension lengths that can be any combination of powers of 2, 3, 
5, 7, 11 and 13.

Supports single and double precision floating point formats.
--- End Message ---
--- Begin Message ---
X-CrossAssassin-Score: 4695--- End Message ---

Bug#920007: marked as done (squid: basic_ncsa_auth username case sensitivity)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 23:51:04 +1300
with message-id 
and subject line 
has caused the Debian Bug report #920007,
regarding squid: basic_ncsa_auth username case sensitivity
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.)


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

Dear Maintainer,

I was configuring basic_ncsa_auth authentication in squid and could not get it 
to work.
Eventually I decided to check input of basic_ncsa_auth and replaced it with 
custom script:

#!/bin/bash
cat $@ > /tmp/args
cat > /tmp/stdin

After output examination, I learned that squid converts all characters to 
lowercase.
In my case, login had uppercase characters in it. So call to basic_ncsa_auth 
never succeeded.

In my opinion either squid should not convert characters to lowercase, or it 
should be clearly stated somewhere that uppercase characters are not allowed.

tldr: basic_ncsa_auth option does not support usernames with uppercase 
characters.

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

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

Versions of packages squid depends on:
ii  adduser  3.118
ii  libc62.28-5
ii  libcap2  1:2.25-1.2
ii  libcom-err2  1.44.5-1
ii  libdb5.3 5.3.28+dfsg1-0.2
ii  libdbi-perl  1.642-1+b1
ii  libecap3 1.0.1-3.2
ii  libexpat12.2.6-1
ii  libgcc1  1:8.2.0-14
ii  libgnutls30  3.6.5-2
ii  libgssapi-krb5-2 1.16.2-1
ii  libkrb5-31.16.2-1
ii  libldap-2.4-22.4.47+dfsg-2
ii  libltdl7 2.4.6-6
ii  libnetfilter-conntrack3  1.0.7-1
ii  libnettle6   3.4.1~rc1-1
ii  libpam0g 1.1.8-4
ii  libsasl2-2   2.1.27~rc8-1
ii  libstdc++6   8.2.0-14
ii  libxml2  2.9.4+dfsg1-7+b3
ii  logrotate3.14.0-4
ii  lsb-base 10.2018112800
ii  netbase  5.5
ii  squid-common 4.4-1

Versions of packages squid recommends:
ii  ca-certificates  20180409
ii  libcap2-bin  1:2.25-1.2

Versions of packages squid suggests:
pn  resolvconf   
ii  smbclient2:4.9.4+dfsg-1
pn  squid-cgi
pn  squid-purge  
pn  squidclient  
ii  ufw  0.36-1
pn  winbindd 

-- Configuration Files:
/etc/squid/squid.conf changed:
acl localnet src 192.168.1.0/24 # RFC 1918 local private network (LAN)
acl SSL_ports port 443
acl Safe_ports port 80  # http
acl Safe_ports port 443 # https
acl CONNECT method CONNECT
auth_param basic program /usr/lib/squid/basic_ncsa_auth /etc/squid/passwords
auth_param basic children 10 startup=0 idle=1
auth_param basic realm Squid proxy-caching web server
auth_param basic credentialsttl 6 hours
acl password proxy_auth REQUIRED
http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports
http_access allow localhost manager
http_access deny manager
include /etc/squid/conf.d/*
http_access allow password
http_access deny all
http_port 3128
coredump_dir /var/spool/squid
refresh_pattern ^ftp:   144020% 10080
refresh_pattern ^gopher:14400%  1440
refresh_pattern -i (/cgi-bin/|\?) 0 0%  0
refresh_pattern .   0   20% 4320


-- no debconf information
--- End Message ---
--- Begin Message ---
Control: notfound -1 4.4-1

Closing as this is not a bug.

Amos--- End Message ---

Bug#877331: marked as done (RFS: nix/1.11.16 [ITP])

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 11:25:42 +
with message-id <20190126112542.xdipuijps26ii...@master.debian.org>
and subject line in new
has caused the Debian Bug report #877331,
regarding RFS: nix/1.11.16 [ITP]
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.)


-- 
877331: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist

Dear Mentors,

I am looking for a sponsor for my package "nix":

* Package name: nix
  Version : 1.1.15
  Upstream Author : Eelco Dolstra
* URL : https://nixos.org/nix/
* License : LGPL v2.1
  Section : devel

It builds those binary packages:

  nix - Purely functional package manager
  
To access further information about this package, please visit the
following URL:

https://github.com/KaiHa/nix-debian/releases

If you haven't been exposed to Nix up to now, this [1] might give you a
good introduction to Nix.

It is a really impressive tool and I would be happy if it could be
included into Debian. 

[1] https://nixos.org/nix/about.html

Regards,

Kai Harries
--- End Message ---
--- Begin Message ---
The package nix is in NEW.
https://ftp-master.debian.org/new.html
-- --- End Message ---

Processed: this package is now in NEW

[Debian Bug Tracking System]

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

> close 904765
Bug #904765 [sponsorship-requests] RFS: looking-glass/0+a12-1 [ITP]
Marked Bug as done
>
End of message, stopping processing here.

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

Processed: this package is now in NEW

[Debian Bug Tracking System]

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

> close 919744
Bug #919744 [sponsorship-requests] RFS: 
golang-github-danverbraganza-varcaser/0.0~git20151108.ce61ec4-1 [ITP]
Marked Bug as done
>
End of message, stopping processing here.

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

Processed: this package is now in NEW

[Debian Bug Tracking System]

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

> close 919745
Bug #919745 [sponsorship-requests] RFS: ffcvt/1.3.1-1 [ITP]
Marked Bug as done
>
End of message, stopping processing here.

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

Bug#920513: marked as done (node-evp-bytestokey: switch build-depends from nodejs-dev to libnode-dev)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 13:21:40 +
with message-id 
and subject line Bug#920513: fixed in node-evp-bytestokey 1.0.3-5
has caused the Debian Bug report #920513,
regarding node-evp-bytestokey: switch build-depends from nodejs-dev to 
libnode-dev
to be marked as done.

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

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


-- 
920513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920513
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-evp-bytestokey
Version: 1.0.3-4
Severity: serious
Justification: fails to build from source

Hi,

the old transitional package nodejs-dev is no longer built, please
update your build-depends to libnode-dev.


Andreas
--- End Message ---
--- Begin Message ---
Source: node-evp-bytestokey
Source-Version: 1.0.3-5

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

Debian distribution maintenance software
pp.
Xavier Guimard  (supplier of updated node-evp-bytestokey 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Jan 2019 13:59:56 +0100
Source: node-evp-bytestokey
Binary: node-evp-bytestokey
Architecture: source all
Version: 1.0.3-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Xavier Guimard 
Description:
 node-evp-bytestokey - secure key derivation algorithm in pure javascript
Closes: 920513
Changes:
 node-evp-bytestokey (1.0.3-5) unstable; urgency=medium
 .
   * Team upload
   * Rebuilt against libnode-dev (Closes: #920513)
   * Declare compliance with policy 4.3.0
   * Remove useless dependency versions
   * Add upstream/metadata
Checksums-Sha1:
 a70650bd65f2624076d58081aeb23c6d5833a9da 2457 node-evp-bytestokey_1.0.3-5.dsc
 c510290a6ead3df0d55aff185083fa6aa9211b2a 3532 
node-evp-bytestokey_1.0.3-5.debian.tar.xz
 6734bb18981b824c57d5e4ef2274b7f973984a06 4768 
node-evp-bytestokey_1.0.3-5_all.deb
 94382b50157fc277a51e6ce5d628a972cf00b06a 10285 
node-evp-bytestokey_1.0.3-5_amd64.buildinfo
Checksums-Sha256:
 2293a94dea690535130a757767556eefae9ee53a5a05ea6f82d4d5745411c290 2457 
node-evp-bytestokey_1.0.3-5.dsc
 600c262755d2d5a528193c9418caf8e48dedfc5de32a596592eadb65495f681f 3532 
node-evp-bytestokey_1.0.3-5.debian.tar.xz
 8aa8d46f16c9d4dca2e9bfbef05e1b02f488abe9c70164ab8c529d067e6084a3 4768 
node-evp-bytestokey_1.0.3-5_all.deb
 e557c705011ef41e8bae3fa9cbfbf2bb4769eb7f405751b213a6fae6f571697a 10285 
node-evp-bytestokey_1.0.3-5_amd64.buildinfo
Files:
 bfcee152c60ea6653f53c1491b503232 2457 javascript optional 
node-evp-bytestokey_1.0.3-5.dsc
 b944dcb1f15a7487a8a44302a858e9d5 3532 javascript optional 
node-evp-bytestokey_1.0.3-5.debian.tar.xz
 e99c3ee68a93a3120d2ff4ad0e6eca6f 4768 javascript optional 
node-evp-bytestokey_1.0.3-5_all.deb
 baff109b1c1609a6e46bd0a594a884e3 10285 javascript optional 
node-evp-bytestokey_1.0.3-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxMWqcACgkQ9tdMp8mZ
7ulqjw//Z4TBGSJc1j8HjLy/5kcY84gWtCrMiil7qflTEDiptfxJUDPy6jewdQ8X
3zV/e/Y3YnS1AO6Rgc6dN2Rr6vwlG9G1WthPK1iKZC0UnngId9GonYpTH/6Hb8G2
+9KKxcJMfd70eb0jByjAtZHPh9yZ71qjrldGLy39BYcfIrJap331DkOam4bV6jI5
04pI+aLEMdzQjTaQhKlfLJvt+8xS85C//w1MU9rLyBP4a6Pro24LkkQS/t7dfZyb
sWzSw8dWe6j4D8xAEWlRyJpuqJB2WL+i5i4i9v46STESldc+VmA8oyC3YToaJ64k
udThDhe95dcs1JnhINsxQe5f5jR65yAPRXPxAIJGUinVtgv/IBjc+TP3cApBPOfl
p3mjSJDyfuZwyUw97teox2lAcnmeJGqgycKyV+/qG/nNV5P3cDSUed9WThXOBEbM
GtK97uUNAt5UbCN6jZ/y1mxgetnSl+PEQiTKntg6VnUQNeSB9r41AKBcMDo9epS6
cIknriFCIEBc6BjNd/ENzA1PIicTFc4jSX/WX4E4YRqa/r450MbBMX/pKvpWlp++
gKi9Msc6b98axQ462uSR9ne8oG47BEDG9/IIaH8bxSHiv7B7Y1EOYEWC1PBQley9
m4dfIpgHWuHPCiixPogX3R1nh5kb/Tt/CBVm969H8pNKS3qP45c=
=RqDO
-END PGP SIGNATURE End Message ---

Bug#920366: marked as done (ftbfs causing regression in texlive-latex-recommended)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 12:39:24 +
with message-id 
and subject line Bug#920366: fixed in texlive-base 2018.20190126-1
has caused the Debian Bug report #920366,
regarding ftbfs causing regression in texlive-latex-recommended
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.)


-- 
920366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: developers-reference
Version: 3.4.21
Severity: serious

Hi,

so I was going to do a developers-reference upload today, thinking it's
good to update it 'long' before the freeze...

so I did some polishing and tried to build it, and failed, fixed some
broken tags (see git) and noticed it still fails to build in sid, but
builds fine in stable.

So I triggered a build of 3.4.21 on tests.reproducible-builds.org and
voila, it fails exactly as the git master branch for 3.4.22:

from 
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/developers-reference_3.4.21.rbuild.log.gz
(also attached)

xsltproc --nonet --novalid --xinclude 
/build/1st/developers-reference-3.4.21/xslt/txt.xsl 
/build/1st/developers-reference-3.4.21/index.dbk \
| LC_ALL=C.UTF-8 w3m -o display_charset=UTF-8 -cols 70 -dump -no-graph -T 
text/html > /build/1st/developers-reference-3.4.21/developers-reference.txt
dblatex --style=db2latex /build/1st/developers-reference-3.4.21/index.dbk \
--backend=xetex \
--xsl-user=xslt/user_param.xsl \
--xsl-user=xslt/xetex_param.xsl \
--param=lingua=/build/1st/developers-reference-3.4.21 \
&& mv /build/1st/developers-reference-3.4.21/index.dbk.pdf 
/build/1st/developers-reference-3.4.21/developers-reference.pdf
Build the book set list...
Build the listings...
XSLT stylesheets DocBook - LaTeX 2e (0.3.10)
===
Build index.dbk.pdf
xelatex failed
index.dbk.tex:279: Argument of \__fontspec_strip_leading_sign:Nw has an extra }.
index.dbk.tex:279: leading text: would be much less secure.\footnote{
index.dbk.tex:279: Paragraph ended before \__fontspec_strip_leading_sign:Nw was 
complete.
index.dbk.tex:279: leading text: would be much less secure.\footnote{
index.dbk.tex:308: Argument of \__fontspec_strip_leading_sign:Nw has an extra }.
index.dbk.tex:308: leading text: }
index.dbk.tex:308: Paragraph ended before \__fontspec_strip_leading_sign:Nw was 
complete.
index.dbk.tex:308: leading text: }
index.dbk.tex:558: Argument of \__fontspec_strip_leading_sign:Nw has an extra }.
index.dbk.tex:558: leading text: ... to the subject of your message\footnote{
index.dbk.tex:558: Paragraph ended before \__fontspec_strip_leading_sign:Nw was 
complete.
index.dbk.tex:558: leading text: ... to the subject of your message\footnote{
index.dbk.tex:562: Argument of \__fontspec_strip_leading_sign:Nw has an extra }.
index.dbk.tex:562: leading text: }
index.dbk.tex:562: Paragraph ended before \__fontspec_strip_leading_sign:Nw was 
complete.
index.dbk.tex:562: leading text: }
index.dbk.tex:2815: Argument of \__fontspec_strip_leading_sign:Nw has an extra 
}.
index.dbk.tex:2815: leading text: ... to \`{}main' or \`{}contrib'.\footnote{
index.dbk.tex:2815: Paragraph ended before \__fontspec_strip_leading_sign:Nw 
was complete.
index.dbk.tex:2815: leading text: ... to \`{}main' or \`{}contrib'.\footnote{
index.dbk.tex:2818: Argument of \__fontspec_strip_leading_sign:Nw has an extra 
}.
index.dbk.tex:2818: leading text: }
index.dbk.tex:2818: Paragraph ended before \__fontspec_strip_leading_sign:Nw 
was complete.
index.dbk.tex:2818: leading text: }
index.dbk.tex:3263: Argument of \__fontspec_strip_leading_sign:Nw has an extra 
}.
index.dbk.tex:3263: leading text: ...ion number of \texttt{3.4+b2}.\footnote{
index.dbk.tex:3263: Paragraph ended before \__fontspec_strip_leading_sign:Nw 
was complete.
index.dbk.tex:3263: leading text: ...ion number of \texttt{3.4+b2}.\footnote{
index.dbk.tex:3270: Argument of \__fontspec_strip_leading_sign:Nw has an extra 
}.
index.dbk.tex:3270: leading text: }
index.dbk.tex:3270: Paragraph ended before \__fontspec_strip_leading_sign:Nw 
was complete.
index.dbk.tex:3270: leading text: }
index.dbk.tex:3857: Argument of \__fontspec_strip_leading_sign:Nw has an extra 
}.
index.dbk.tex:3857: leading text:   package-{}name}\footnote{
index.dbk.tex:3857: Paragraph ended before \__fontspec_strip_leading_sign:Nw 
was complete.
index.dbk.tex:3857: leading text:   package-{}name}\footnote{
index.dbk.tex:3860: Argument of \__fontspec_strip_leading_sign:Nw has an extra 
}.
index.dbk.tex:3860: leading text: }

Bug#918508: marked as done (RM: golang-1.10 -- ROM; superseeded by golang-1.11)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 15:51:40 +
with message-id 
and subject line Bug#918508: Removed package(s) from unstable
has caused the Debian Bug report #918508,
regarding RM: golang-1.10 -- ROM; superseeded by golang-1.11
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.)


-- 
918508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918508
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-1.10
Severity: serious

With golang-1.11 as default now, should golang-1.10
be shipped in buster?
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

golang-1.10 |   1.10.7-2 | source, all
golang-1.10-doc |   1.10.7-2 | all
golang-1.10-go |   1.10.7-2 | amd64, arm64, armel, armhf, i386, mips, mips64el, 
mipsel, ppc64el, s390x
golang-1.10-src |   1.10.7-2 | amd64, arm64, armel, armhf, i386, mips, 
mips64el, mipsel, ppc64el, s390x

--- Reason ---
ROM; superseeded by golang-1.11
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 918...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/918508

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#920403: marked as done (libantlr3c: makefile error trapping and FTCBFS)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 15:50:25 +
with message-id 
and subject line Bug#920403: fixed in libantlr3c 3.4+dfsg-3
has caused the Debian Bug report #920403,
regarding libantlr3c: makefile error trapping and FTCBFS
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.)


-- 
920403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920403
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libantlr3c
Version: 3.4+dfsg-2
Severity: serious
Justification: policy 4.6
Tags: patch

libantlr3c fails to cross build from source, because it does not pass
--host to ./configure. The easiest way of doing so is using
dh_auto_configure. That is sufficient for making libantlr3c cross
buildable.

While preparing the patch, I noticed that debian/rules is chaining build
command (configure and ln) with ";". Doing so is prohibited by Debian
policy section 4.6, because it can result in silent misbuilds.
Therefore, I bumped the severity to serious. 

The attached patch fixes both issues as they really affect the same
lines. Merging these issues felt simpler that filing two bugs with
conflicting patches.

Helmut
diff --minimal -Nru libantlr3c-3.4+dfsg/debian/changelog 
libantlr3c-3.4+dfsg/debian/changelog
--- libantlr3c-3.4+dfsg/debian/changelog2018-06-21 12:38:06.0 
+0200
+++ libantlr3c-3.4+dfsg/debian/changelog2019-01-25 06:33:12.0 
+0100
@@ -1,3 +1,10 @@
+libantlr3c (3.4+dfsg-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Use dh_auto_configure. (Closes: #-1)
+
+ -- Helmut Grohne   Fri, 25 Jan 2019 06:33:12 +0100
+
 libantlr3c (3.4+dfsg-2) unstable; urgency=medium
 
   * QA upload.
diff --minimal -Nru libantlr3c-3.4+dfsg/debian/rules 
libantlr3c-3.4+dfsg/debian/rules
--- libantlr3c-3.4+dfsg/debian/rules2018-06-16 22:18:36.0 +0200
+++ libantlr3c-3.4+dfsg/debian/rules2019-01-25 06:33:10.0 +0100
@@ -16,22 +16,16 @@
 
 override_dh_auto_configure:
# Configure with ANTLR remote debugger enabled
-   mkdir build-dbg
-   ( cd build-dbg;   \
- ../configure $(CROSS) --prefix=/usr \
-   --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)\
+   dh_auto_configure --builddirectory=build-dbg --
--enable-debuginfo --disable-abiflags --enable-antlrdebug \
-   $(ENABLE_64BIT);  \
-   ln -s ../include )
+   $(ENABLE_64BIT)
+   ln -s ../include build-dbg/
 
# Configure with ANTLR remote debugger disabled
-   mkdir build-nodbg
-   ( cd build-nodbg;  \
- ../configure $(CROSS) --prefix=/usr  \
-   --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) \
+   dh_auto_configure --builddirectory=build-nodbg --
--enable-debuginfo --disable-abiflags --disable-antlrdebug \
-   $(ENABLE_64BIT);   \
- ln -s ../include )
+   $(ENABLE_64BIT)
+   ln -s ../include build-nodbg/
 
 override_dh_auto_build:
( cd build-dbg; $(MAKE) )
--- End Message ---
--- Begin Message ---
Source: libantlr3c
Source-Version: 3.4+dfsg-3

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated libantlr3c package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Jan 2019 16:22:40 +0100
Source: libantlr3c
Architecture: source
Version: 3.4+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 920403
Changes:
 libantlr3c (3.4+dfsg-3) unstable; urgency=medium
 .
   [ Andreas Beckmann ]
   * QA upload.
   * Switch to debhelper-compat (= 12).
   * Bump Standards-Version to 4.3.0 (no changes needed).
 .
   [ Helmut Grohne ]
   * Use dh_auto_configure. 

Bug#892340: marked as done (dvdauthor: Please use 'pkg-config' to find FreeType 2)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 15:50:14 +
with message-id 
and subject line Bug#892340: fixed in dvdauthor 0.7.2-1
has caused the Debian Bug report #892340,
regarding dvdauthor: Please use 'pkg-config' to find FreeType 2
to be marked as done.

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

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


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

Dear Maintainer,

The next release of libfreetype6-dev will *not* ship
`freetype-config', as the script has now been deprecated in favour of
`pkg-config'.

This is an upstream change:

"Use of the `freetype-config' script to get compilation and

linking options is deprecated since it doesn't support

cross-compiling, among other deficiencies. Instead, you should

use the `pkg-config' interface." [1]

Please use `pkg-config' to detect the FreeType 2 headers and
libraries in dvdauthor.

If this bug is not resolved prior to the release of FreeType 2.9.1,
your package may FTBFS.

Thank you

[1]
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=b0
a93839b52818abbfe9b4c8755b4aa0f5232063 
--- End Message ---
--- Begin Message ---
Source: dvdauthor
Source-Version: 0.7.2-1

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

Debian distribution maintenance software
pp.
Marc Leeman  (supplier of updated dvdauthor 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, 23 Jan 2019 13:48:34 +0100
Source: dvdauthor
Binary: dvdauthor dvdauthor-dbgsym
Architecture: source amd64
Version: 0.7.2-1
Distribution: unstable
Urgency: medium
Maintainer: Marc Leeman 
Changed-By: Marc Leeman 
Description:
 dvdauthor  - create DVD-Video file system
Closes: 637346 690300 892340 920207
Changes:
 dvdauthor (0.7.2-1) unstable; urgency=medium
 .
   * new upstream release 0.7.2 (Closes: #920207, Closes: #690300,
 Closes: #892340)
   * add video_format file (Closes: #637346)
Checksums-Sha1:
 c189536baefe1ba92b2ee68382e0c82efbc5a693 1974 dvdauthor_0.7.2-1.dsc
 1cb7fdee1ceba8adb3c8dae30cef707bd2eddc35 252344 dvdauthor_0.7.2.orig.tar.gz
 b535565b421b74b4519e5acebddf856e0ba8808a 13384 dvdauthor_0.7.2-1.debian.tar.xz
 3b928ede4ac648629c900ec2a73a42991e30ced1 476972 
dvdauthor-dbgsym_0.7.2-1_amd64.deb
 e0bdb7b1ce4a25d8bcca58803cf3a37c301289e7 13213 
dvdauthor_0.7.2-1_amd64.buildinfo
 7d93f3d95ae050e10460f211b377c8368a6d790d 191292 dvdauthor_0.7.2-1_amd64.deb
Checksums-Sha256:
 1120a7d8c89f6cb3b6d6c886ec5cee11484659ef526bba113a66ea8e5c7c928d 1974 
dvdauthor_0.7.2-1.dsc
 fd66b92f6c67bd406030ff0f1c3233175768b534df4d341c3f380ecd61de91b5 252344 
dvdauthor_0.7.2.orig.tar.gz
 092e3b4eb6420ca33cf4204c0dd18761c3f68ba590bb37bfec2f05db1f279fd9 13384 
dvdauthor_0.7.2-1.debian.tar.xz
 1ac9819755dbcc0de660dae879c6dd8b3aca9caf74bfc7a89b90963292a2e76c 476972 
dvdauthor-dbgsym_0.7.2-1_amd64.deb
 0dbb33a8d6a08c5a387930b41942093c97b884757f56772e7350cdd21ba27da1 13213 
dvdauthor_0.7.2-1_amd64.buildinfo
 99bc6f5db89cbd752ed539363b43fbf9d60110e0243778daf80609ee8286c2d3 191292 
dvdauthor_0.7.2-1_amd64.deb
Files:
 160b5e1688dd10acdb1da7f09e7e7821 1974 otherosfs optional dvdauthor_0.7.2-1.dsc
 164dad26edfbdaa7d76ed3debe7add74 252344 otherosfs optional 
dvdauthor_0.7.2.orig.tar.gz
 5b7d98b08ee92680b0db8d06da3e53da 13384 otherosfs optional 
dvdauthor_0.7.2-1.debian.tar.xz
 4544e7d68d4982616b0c3707cc43ac2b 476972 debug optional 
dvdauthor-dbgsym_0.7.2-1_amd64.deb
 474cfb422b61b0be5e6665b14fba9879 13213 otherosfs optional 
dvdauthor_0.7.2-1_amd64.buildinfo
 3e13fa5ddbc6cba4977ec8293e97d23a 191292 otherosfs optional 
dvdauthor_0.7.2-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEpAH/mTaPofmBUt51XICMK2VVgRcFAlxMfboACgkQXICMK2VV
gRdl9hAAnO3B3ym/c4zL44SNuFdYLvyXz/xr/gRrTvVb/JUWZUNsAjA/+Hb2AUle
uYyHZ8olA7X/cWpmjYJ+asTibjRoNKdwtcAv24Rz4b8ji9fjTykkvOBWQZvjUF9M
mrML6xxGREXjvuAFCYzlls0XXLqfjsFwiGaD8fuGzEgZf0jxbmy6mk2ud3gqbvnP
TXpHKNIzUK7aERtbv7YkmfJynZxl/fktGTmun9I7fkZmliqYQdepaBULGMnC5t1i

Bug#690300: marked as done (New upstream release: 0.7.1)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 15:50:14 +
with message-id 
and subject line Bug#690300: fixed in dvdauthor 0.7.2-1
has caused the Debian Bug report #690300,
regarding New upstream release: 0.7.1
to be marked as done.

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

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


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

Hello,

some months ago, the upstream author released a new version:

   http://sourceforge.net/projects/dvdauthor/files/dvdauthor/0.7.1/

A list of changes (as taken from the ChangeLog file) introduced by the
new release follows:

0.7.1: 2012 August 20
No longer silently fail to build dvdunauthor if libdvdread is not 
present;
must be explicitly disabled with --disable-dvdunauthor, 
otherwise configure
reports an error
Allow format specification at top level of dvdauthor control file
mpeg2desc now reports more details about video frames
More explanatory XML-parsing errors

Could you please update the packaging to such release?

If you need sponsoring, please consider to join the Debian Multimedia
Maintainers team:

  http://wiki.debian.org/DebianMultimedia#Get_involved

We'd be glad to support you in co-maintaining the packaging and, for sure,
sponsoring uploads for you.

Thanks in advance for any reply, cheers!

-- 
Alessio Treglia  | www.alessiotreglia.com
Debian Developer | ales...@debian.org
Ubuntu Core Developer| quadris...@ubuntu.com
0416 0004 A827 6E40 BB98 90FB E8A4 8AE5 311D 765A
--- End Message ---
--- Begin Message ---
Source: dvdauthor
Source-Version: 0.7.2-1

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

Debian distribution maintenance software
pp.
Marc Leeman  (supplier of updated dvdauthor 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, 23 Jan 2019 13:48:34 +0100
Source: dvdauthor
Binary: dvdauthor dvdauthor-dbgsym
Architecture: source amd64
Version: 0.7.2-1
Distribution: unstable
Urgency: medium
Maintainer: Marc Leeman 
Changed-By: Marc Leeman 
Description:
 dvdauthor  - create DVD-Video file system
Closes: 637346 690300 892340 920207
Changes:
 dvdauthor (0.7.2-1) unstable; urgency=medium
 .
   * new upstream release 0.7.2 (Closes: #920207, Closes: #690300,
 Closes: #892340)
   * add video_format file (Closes: #637346)
Checksums-Sha1:
 c189536baefe1ba92b2ee68382e0c82efbc5a693 1974 dvdauthor_0.7.2-1.dsc
 1cb7fdee1ceba8adb3c8dae30cef707bd2eddc35 252344 dvdauthor_0.7.2.orig.tar.gz
 b535565b421b74b4519e5acebddf856e0ba8808a 13384 dvdauthor_0.7.2-1.debian.tar.xz
 3b928ede4ac648629c900ec2a73a42991e30ced1 476972 
dvdauthor-dbgsym_0.7.2-1_amd64.deb
 e0bdb7b1ce4a25d8bcca58803cf3a37c301289e7 13213 
dvdauthor_0.7.2-1_amd64.buildinfo
 7d93f3d95ae050e10460f211b377c8368a6d790d 191292 dvdauthor_0.7.2-1_amd64.deb
Checksums-Sha256:
 1120a7d8c89f6cb3b6d6c886ec5cee11484659ef526bba113a66ea8e5c7c928d 1974 
dvdauthor_0.7.2-1.dsc
 fd66b92f6c67bd406030ff0f1c3233175768b534df4d341c3f380ecd61de91b5 252344 
dvdauthor_0.7.2.orig.tar.gz
 092e3b4eb6420ca33cf4204c0dd18761c3f68ba590bb37bfec2f05db1f279fd9 13384 
dvdauthor_0.7.2-1.debian.tar.xz
 1ac9819755dbcc0de660dae879c6dd8b3aca9caf74bfc7a89b90963292a2e76c 476972 
dvdauthor-dbgsym_0.7.2-1_amd64.deb
 0dbb33a8d6a08c5a387930b41942093c97b884757f56772e7350cdd21ba27da1 13213 
dvdauthor_0.7.2-1_amd64.buildinfo
 99bc6f5db89cbd752ed539363b43fbf9d60110e0243778daf80609ee8286c2d3 191292 
dvdauthor_0.7.2-1_amd64.deb
Files:
 160b5e1688dd10acdb1da7f09e7e7821 1974 otherosfs optional dvdauthor_0.7.2-1.dsc
 164dad26edfbdaa7d76ed3debe7add74 252344 otherosfs optional 
dvdauthor_0.7.2.orig.tar.gz
 5b7d98b08ee92680b0db8d06da3e53da 13384 otherosfs optional 
dvdauthor_0.7.2-1.debian.tar.xz
 4544e7d68d4982616b0c3707cc43ac2b 476972 debug optional 
dvdauthor-dbgsym_0.7.2-1_amd64.deb
 474cfb422b61b0be5e6665b14fba9879 13213 otherosfs optional 
dvdauthor_0.7.2-1_amd64.buildinfo
 

Bug#637346: marked as done (Please create /etc/video_format for default video format)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 15:50:14 +
with message-id 
and subject line Bug#637346: fixed in dvdauthor 0.7.2-1
has caused the Debian Bug report #637346,
regarding Please create /etc/video_format for default video format
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.)


-- 
637346: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=637346
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dvdauthor
Version: 0.7.0-1.1
Severity: important


Hi, after running:

movie-to-dvd -m pal -A 16:9 -M Wonders.m2t

from the videotrans package, then:

$ dvddirdel -o wonders2

$ dvdauthor -t -v pal+16:9 -o wonders2 Wonders.vob

DVDAuthor::dvdauthor, version 0.7.0.

Build options: gnugetopt imagemagick iconv freetype fribidi fontconfig

Send bug reports to

INFO: no default video format, must explicitly specify NTSC or PAL

INFO: dvdauthor creating VTS

STAT: Picking VTS 01

STAT: Processing Wonders.vob...

 [lots more output]

the final step:

$ dvdauthor -T  -o wonders2

gives me the error:

DVDAuthor::dvdauthor, version 0.7.0.
Build options: gnugetopt imagemagick iconv freetype fribidi fontconfig

Send bug reports to

INFO: no default video format, must explicitly specify NTSC or PAL
INFO: dvdauthor creating table of contents
INFO: Scanning wonders2/VIDEO_TS/VTS_01_0.IFO
ERR:  no video format specified for VMGM

so I try to specify the video format:

$ dvdauthor -T -v pal+16:9 -o wonders2

DVDAuthor::dvdauthor, version 0.7.0.
Build options: gnugetopt imagemagick iconv freetype fribidi fontconfig

Send bug reports to

INFO: no default video format, must explicitly specify NTSC or PAL
ERR:  TOC cannot have titles

What should I be doing?

Arthur. 

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

Kernel: Linux 3.0.0-git18 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages dvdauthor depends on:
ii  libbz2-1.0  1.0.5-6  high-quality block-sorting file co
ii  libc6   2.13-16  Embedded GNU C Library: Shared lib
ii  libdvdread4 4.1.3-10 library for reading DVDs
ii  libfontconfig1  2.8.0-3  generic font configuration library
ii  libfreetype62.4.6-1  FreeType 2 font engine, shared lib
ii  libfribidi0 0.19.2-1 Free Implementation of the Unicode
ii  libglib2.0-02.28.6-1 The GLib library of C routines
ii  libgomp14.6.1-6  GCC OpenMP (GOMP) support library
ii  libice6 2:1.0.7-2X11 Inter-Client Exchange library
ii  libjpeg62   6b1-2Independent JPEG Group's JPEG runt
ii  liblcms11.19.dfsg-1  Little CMS color management librar
ii  liblqr-1-0  0.4.1-1.1converts plain array images into m
ii  libltdl72.4-3A system independent dlopen wrappe
ii  libmagickcore4  8:6.6.9.7-5  low-level image manipulation libra
ii  libpng12-0  1.2.46-3 PNG library - runtime
ii  libsm6  2:1.2.0-2X11 Session Management library
ii  libtiff43.9.5-1  Tag Image File Format (TIFF) libra
ii  libx11-62:1.4.4-1X11 client-side library
ii  libxext62:1.3.0-3X11 miscellaneous extension librar
ii  libxml2 2.7.8.dfsg-4 GNOME XML library
ii  libxt6  1:1.1.1-2X11 toolkit intrinsics library
ii  zlib1g  1:1.2.3.4.dfsg-3 compression library - runtime

dvdauthor recommends no packages.

dvdauthor suggests no packages.

-- debconf-show failed


--- End Message ---
--- Begin Message ---
Source: dvdauthor
Source-Version: 0.7.2-1

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

Debian distribution maintenance software
pp.
Marc Leeman  (supplier of updated dvdauthor package)

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

Bug#920207: marked as done (Update dvdauthor to 0.7.2 - Update watch file)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 15:50:14 +
with message-id 
and subject line Bug#920207: fixed in dvdauthor 0.7.2-1
has caused the Debian Bug report #920207,
regarding Update dvdauthor to 0.7.2 - Update watch file
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.)


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

Please update to version 0.7.2. Upstream is on GitHub, so please update 
the watch file and homepage.

https://github.com/ldo/dvdauthor
http://dvdauthor.sourceforge.net/

0.7.2: 2016 December 31
     Various code-quality and build improvements
     Support “jump pgc n” and other interaction code-generation improvements
     Improve reliability of dvdunauthor
     Don’t force infinite pause on last cell of a PGC
     Allow specification of provider field in VMG IFO file
     Add video_format(7) man page
     Add padding to ensure .BUP and .IFO files end up in different ECC 
blocks
     Enabled hinting of rendered subtitle text
     Require cell start and end times (if specified) to be nonempty

0.7.1: 2012 August 20
     No longer silently fail to build dvdunauthor if libdvdread is not 
present;
         must be explicitly disabled with --disable-dvdunauthor, 
otherwise configure
         reports an error
     Allow format specification at top level of dvdauthor control file
     mpeg2desc now reports more details about video frames
More explanatory XML-parsing errors
--- End Message ---
--- Begin Message ---
Source: dvdauthor
Source-Version: 0.7.2-1

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

Debian distribution maintenance software
pp.
Marc Leeman  (supplier of updated dvdauthor 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, 23 Jan 2019 13:48:34 +0100
Source: dvdauthor
Binary: dvdauthor dvdauthor-dbgsym
Architecture: source amd64
Version: 0.7.2-1
Distribution: unstable
Urgency: medium
Maintainer: Marc Leeman 
Changed-By: Marc Leeman 
Description:
 dvdauthor  - create DVD-Video file system
Closes: 637346 690300 892340 920207
Changes:
 dvdauthor (0.7.2-1) unstable; urgency=medium
 .
   * new upstream release 0.7.2 (Closes: #920207, Closes: #690300,
 Closes: #892340)
   * add video_format file (Closes: #637346)
Checksums-Sha1:
 c189536baefe1ba92b2ee68382e0c82efbc5a693 1974 dvdauthor_0.7.2-1.dsc
 1cb7fdee1ceba8adb3c8dae30cef707bd2eddc35 252344 dvdauthor_0.7.2.orig.tar.gz
 b535565b421b74b4519e5acebddf856e0ba8808a 13384 dvdauthor_0.7.2-1.debian.tar.xz
 3b928ede4ac648629c900ec2a73a42991e30ced1 476972 
dvdauthor-dbgsym_0.7.2-1_amd64.deb
 e0bdb7b1ce4a25d8bcca58803cf3a37c301289e7 13213 
dvdauthor_0.7.2-1_amd64.buildinfo
 7d93f3d95ae050e10460f211b377c8368a6d790d 191292 dvdauthor_0.7.2-1_amd64.deb
Checksums-Sha256:
 1120a7d8c89f6cb3b6d6c886ec5cee11484659ef526bba113a66ea8e5c7c928d 1974 
dvdauthor_0.7.2-1.dsc
 fd66b92f6c67bd406030ff0f1c3233175768b534df4d341c3f380ecd61de91b5 252344 
dvdauthor_0.7.2.orig.tar.gz
 092e3b4eb6420ca33cf4204c0dd18761c3f68ba590bb37bfec2f05db1f279fd9 13384 
dvdauthor_0.7.2-1.debian.tar.xz
 1ac9819755dbcc0de660dae879c6dd8b3aca9caf74bfc7a89b90963292a2e76c 476972 
dvdauthor-dbgsym_0.7.2-1_amd64.deb
 0dbb33a8d6a08c5a387930b41942093c97b884757f56772e7350cdd21ba27da1 13213 
dvdauthor_0.7.2-1_amd64.buildinfo
 99bc6f5db89cbd752ed539363b43fbf9d60110e0243778daf80609ee8286c2d3 191292 
dvdauthor_0.7.2-1_amd64.deb
Files:
 160b5e1688dd10acdb1da7f09e7e7821 1974 otherosfs optional dvdauthor_0.7.2-1.dsc
 164dad26edfbdaa7d76ed3debe7add74 252344 otherosfs optional 
dvdauthor_0.7.2.orig.tar.gz
 5b7d98b08ee92680b0db8d06da3e53da 13384 otherosfs optional 
dvdauthor_0.7.2-1.debian.tar.xz
 4544e7d68d4982616b0c3707cc43ac2b 476972 debug optional 
dvdauthor-dbgsym_0.7.2-1_amd64.deb
 474cfb422b61b0be5e6665b14fba9879 13213 otherosfs optional 
dvdauthor_0.7.2-1_amd64.buildinfo
 3e13fa5ddbc6cba4977ec8293e97d23a 191292 otherosfs optional 
dvdauthor_0.7.2-1_amd64.deb

-BEGIN PGP SIGNATURE-

Bug#899298: marked as done (golang-1.10-go: vgo run fail)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 15:51:46 +
with message-id 
and subject line Bug#918508: Removed package(s) from unstable
has caused the Debian Bug report #899298,
regarding golang-1.10-go: vgo run fail
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.)


-- 
899298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-1.10-go
Version: 1.10.1-3
Severity: minor

Dear Maintainer,

I run:

$ go get -u golang.org/x/vgo
$ vgo -h
vgo requires Go 1.10 but VGOROOT=/usr/lib/go-1.10 is not a Go 1.10 source tree

Ugly hack:
# cd /usr/lib/go-1.10
# ln -s ../../share/go-1.10/api

Please add symlink to api in install script.

Add line:
usr/share/go-X.Y/api /usr/lib/go-X.Y/api
Into debian/golang-X.Y-go.links

Thanks

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

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

Versions of packages golang-1.10-go depends on:
ii  golang-1.10-src  1.10.1-3
ii  libc62.27-3

Versions of packages golang-1.10-go recommends:
ii  g++ 4:7.3.0-3
ii  gcc 4:7.3.0-3
ii  libc6-dev   2.27-3
ii  pkg-config  0.29-4+b1

Versions of packages golang-1.10-go suggests:
pn  bzr  
ii  ca-certificates  20180409
ii  git  1:2.17.0-1
pn  mercurial
pn  subversion   

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.10.7-2+rm

Dear submitter,

as the package golang-1.10 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/918508

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#897013: marked as done (golang-1.10-go: Package does not install binaries in normal locations)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 15:51:46 +
with message-id 
and subject line Bug#918508: Removed package(s) from unstable
has caused the Debian Bug report #897013,
regarding golang-1.10-go: Package does not install binaries in normal locations
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.)


-- 
897013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897013
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: golang-1.10-go
Version: 1.10.1-3
Severity: normal

Dear Maintainer,

The golang-1.10-go package does not install binaries in a normal location like
/usr/bin. It only installs them in /usr/lib/go-1.10/bin.

Of course I could add that path (/usr/lib/go-1.10/bin) to my PATH, but that
would break on version 1.11.




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

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

Versions of packages golang-1.10-go depends on:
ii  golang-1.10-src  1.10.1-3
ii  libc62.27-3

Versions of packages golang-1.10-go recommends:
ii  g++ 4:7.3.0-3
ii  gcc 4:7.3.0-3
ii  libc6-dev   2.27-3
ii  pkg-config  0.29-4+b1

Versions of packages golang-1.10-go suggests:
pn  bzr  
ii  ca-certificates  20180409
ii  git  1:2.17.0-1
pn  mercurial
pn  subversion   

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.10.7-2+rm

Dear submitter,

as the package golang-1.10 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/918508

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#920450: marked as done (RM: deal.ii [s390x] -- ROM; P4est/MPI toolchain on s390x broken)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 15:52:01 +
with message-id 
and subject line Bug#920450: Removed package(s) from unstable
has caused the Debian Bug report #920450,
regarding RM: deal.ii [s390x] -- ROM; P4est/MPI toolchain on s390x broken
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.)


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

Please remove the binary package for deal.ii for the s390x architecture.

A crucial test fails when currently building the package on s390x [1]
indicating that there is a problem with P4est and/or the MPI toolchain. As
deal.ii has probably no users on s390x removing the binary package for this
architecture temporarily for the release seems to be the best option.

Note: this was a request for a partial removal from testing, converted in one 
for unstable

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919370
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

libdeal.ii-9.0.1 |9.0.1-1 | s390x
libdeal.ii-dev |9.0.1-1 | s390x

--- Reason ---
ROM; P4est/MPI toolchain on s390x broken
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember that the changes have been done on the
master archive and will not propagate to any mirrors until the next
dinstall run at the earliest.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

Bugs which have been reported against this package are not automatically
removed from the Bug Tracking System.  Please check all open bugs and
close them or re-assign them to another package if the removed package
was superseded by another one.

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

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 920...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/920450

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#769296: marked as done (tint: fails to update scores)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 16:06:49 +
with message-id 
and subject line Bug#769296: fixed in tint 0.05
has caused the Debian Bug report #769296,
regarding tint: fails to update scores
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.)


-- 
769296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tint
Version: 0.04+nmu1
Severity: normal

Dear Maintainer,

After playing a game, tint fails to update the scores file because said file
is not writable by any user other than root.

ernest@doriath:~$ tint
Choose a level to start [1-9]: 5

   PLAYER STATISTICS

Score  8320
Efficiency0
Score ratio  30
Error writing to /var/games/tint.scores
ernest@doriath:~$ ll /var/games/
total 12
drwxrwsr-x 5 root games 4096 gen  1  2014 bsdgames
drwxrwsr-x 4 root games 4096 jul 14 00:19 nethack
-rw-r--r-- 1 root games  230 gen  1  2014 tint.scores

Regards.

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

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

Versions of packages tint depends on:
ii  libc62.19-12
ii  libncurses5  5.9+20140913-1

tint recommends no packages.

tint suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: tint
Source-Version: 0.05

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

Debian distribution maintenance software
pp.
Ricardo Mones  (supplier of updated tint package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Jan 2019 16:33:35 +0100
Source: tint
Binary: tint tint-dbgsym
Architecture: source amd64
Version: 0.05
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Ricardo Mones 
Description:
 tint   - Tetris clone for text based terminal
Closes: 738046 769296 823220 840874
Changes:
 tint (0.05) unstable; urgency=medium
 .
   * Put package under Games Team umbrella (Closes: #840874)
   * Switch copyright to machine-readable format (Closes: #823220)
   * Migrate menu to .desktop; add icon; install both (Closes: #738046)
   * Document global scores usage (Closes: #769296)
   * Bump debhelper compat level to 11
   * Update Standards-Version to 4.3.0
   * Remove package name from short description
   * Remove flags from shell line
   * Add Vcs-{Git|Browser} with current URLs
   * Remove whitespace and editor's config lines
Checksums-Sha1:
 02b76f00dd2d3e817be6ade31b99563b85368dde 1561 tint_0.05.dsc
 859008216930a4584e622d0df41fd75c44d2b47f 24180 tint_0.05.tar.xz
 db0db465ab54565ae4a0274e934ee8ee49573125 22992 tint-dbgsym_0.05_amd64.deb
 07934067c4d5864b30cb0c3cc36a7df6130f78ff 5632 tint_0.05_amd64.buildinfo
 c6d9d0462901a59d3ff64d5a9209f518447c9c56 25468 tint_0.05_amd64.deb
Checksums-Sha256:
 f4e035cabf71f7765ec39b6af6c639f23a847cd5ff18fcbcf179364144f47d9e 1561 
tint_0.05.dsc
 d9ac7ee1199b391d5b79a0a324d179fe5148ce4e64460cbbd49c44c6f11dd7dd 24180 
tint_0.05.tar.xz
 287f2b7d7663215da9be7a51a0b192de3bbab7252cf578a4672f3e1e46886463 22992 
tint-dbgsym_0.05_amd64.deb
 3a537059ba029a3c632ad8ab280391097e2e1109eba4f8f895569395c77f219e 5632 
tint_0.05_amd64.buildinfo
 956dd323b6b4954c6d1e6cec7d5791a8d7deaf62fb6b79973e0c6a56f20f393b 25468 
tint_0.05_amd64.deb
Files:
 56c9f36e49306a167a826d756a70215b 1561 games optional tint_0.05.dsc
 134c5fac011bf3148c86be11540ac98b 24180 games optional tint_0.05.tar.xz
 478b9b4fae11729a790c90c142649aea 22992 debug optional 
tint-dbgsym_0.05_amd64.deb
 5077d24c2f2a8a3117544ceceb417b7d 5632 games optional tint_0.05_amd64.buildinfo
 390501b10793850678d81e9f3395a7cd 25468 games optional tint_0.05_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEQ7w2SxbfDCBevXWSHw8KiN5bzKYFAlxMgfQACgkQHw8KiN5b
zKZpVRAAqYdqkT9EAczuLxLZHqw2yStZ6Gbxb764fkHqyw2hsotZqofqAukFucg/

Bug#823220: marked as done (tint: homepage in debian/copyright doesn't work anymore)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 16:06:49 +
with message-id 
and subject line Bug#823220: fixed in tint 0.05
has caused the Debian Bug report #823220,
regarding tint: homepage in debian/copyright doesn't work anymore
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.)


-- 
823220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tint
Version: 0.04+nmu1+b1
Severity: wishlist

The homepage listed in debian/copyright:

  http://oasis.frogfoot.net

... doesn't seem to work for me / anymore.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: tint
Source-Version: 0.05

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

Debian distribution maintenance software
pp.
Ricardo Mones  (supplier of updated tint package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Jan 2019 16:33:35 +0100
Source: tint
Binary: tint tint-dbgsym
Architecture: source amd64
Version: 0.05
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Ricardo Mones 
Description:
 tint   - Tetris clone for text based terminal
Closes: 738046 769296 823220 840874
Changes:
 tint (0.05) unstable; urgency=medium
 .
   * Put package under Games Team umbrella (Closes: #840874)
   * Switch copyright to machine-readable format (Closes: #823220)
   * Migrate menu to .desktop; add icon; install both (Closes: #738046)
   * Document global scores usage (Closes: #769296)
   * Bump debhelper compat level to 11
   * Update Standards-Version to 4.3.0
   * Remove package name from short description
   * Remove flags from shell line
   * Add Vcs-{Git|Browser} with current URLs
   * Remove whitespace and editor's config lines
Checksums-Sha1:
 02b76f00dd2d3e817be6ade31b99563b85368dde 1561 tint_0.05.dsc
 859008216930a4584e622d0df41fd75c44d2b47f 24180 tint_0.05.tar.xz
 db0db465ab54565ae4a0274e934ee8ee49573125 22992 tint-dbgsym_0.05_amd64.deb
 07934067c4d5864b30cb0c3cc36a7df6130f78ff 5632 tint_0.05_amd64.buildinfo
 c6d9d0462901a59d3ff64d5a9209f518447c9c56 25468 tint_0.05_amd64.deb
Checksums-Sha256:
 f4e035cabf71f7765ec39b6af6c639f23a847cd5ff18fcbcf179364144f47d9e 1561 
tint_0.05.dsc
 d9ac7ee1199b391d5b79a0a324d179fe5148ce4e64460cbbd49c44c6f11dd7dd 24180 
tint_0.05.tar.xz
 287f2b7d7663215da9be7a51a0b192de3bbab7252cf578a4672f3e1e46886463 22992 
tint-dbgsym_0.05_amd64.deb
 3a537059ba029a3c632ad8ab280391097e2e1109eba4f8f895569395c77f219e 5632 
tint_0.05_amd64.buildinfo
 956dd323b6b4954c6d1e6cec7d5791a8d7deaf62fb6b79973e0c6a56f20f393b 25468 
tint_0.05_amd64.deb
Files:
 56c9f36e49306a167a826d756a70215b 1561 games optional tint_0.05.dsc
 134c5fac011bf3148c86be11540ac98b 24180 games optional tint_0.05.tar.xz
 478b9b4fae11729a790c90c142649aea 22992 debug optional 
tint-dbgsym_0.05_amd64.deb
 5077d24c2f2a8a3117544ceceb417b7d 5632 games optional tint_0.05_amd64.buildinfo
 390501b10793850678d81e9f3395a7cd 25468 games optional tint_0.05_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEQ7w2SxbfDCBevXWSHw8KiN5bzKYFAlxMgfQACgkQHw8KiN5b
zKZpVRAAqYdqkT9EAczuLxLZHqw2yStZ6Gbxb764fkHqyw2hsotZqofqAukFucg/
KGhwjkO6i2jUUqbhRUoHxZ8rvqzTXFKnrTwMmcCSb3Ff0UGuwQSjuLNjPrARvdWY
QhsXLaJ5TKgX4AtNhpa50swc8gtIV5vjDFdtKMVe16UlPC4E7Vu5kcHZi+h10ZUW
zoQuZszOqN3e6yUBkAd0g0m+mV3vd1lGz1doxFoU1WJZlMbR6MLe4G+wR13CONR4
3eJOEfkrwJRZwYl6/hNc1GE0WDUAg6XLsZVkNbKx6jERbVUII0c95Wsq3wMqBxJP
B0+U2AVjV3XHuTRmEl+3+GgYBh+y9MYlQGtaqu4uPkJDNhsG6FaqvjrfQdfI5B9u
9B6qjkKNg8SUlqS2XxObgf3rVH+fmS1sxF/XWq0swGml7y2Q0Z8k9h/iUwKfu2Q5
rKLdb1ihY3/2VBD/8P4BWm8GFuQcUgu4zvifoHTpQrRLNJ6aQTB1vXiMx4G0IWJD
qvFhz0v3ZEObOfBhWIOUCxW+6lPUmZ/IFsLsgda3DPD/wmBADMTrl6k0Esqb78Vk
7alfEwLCK4ZWfZcMrzMA8JURwVn4csPCh477dkRF3XaUqf1/ryc+aA0GrmY2cEjh
1cjGQFWIBQU1JmJEYAztywsfonwQn+BgWxoA1tFcebnGlcQgUxA=
=mWe6
-END PGP SIGNATURE End Message ---

Bug#840874: marked as done (ITA: tint -- TINT Is Not Tetris(tm) ...at least the name isn't)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 16:06:49 +
with message-id 
and subject line Bug#840874: fixed in tint 0.05
has caused the Debian Bug report #840874,
regarding ITA: tint -- TINT Is Not Tetris(tm) ...at least the name isn't
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.)


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

The current maintainer of tint, Mario Lang ,
has retired.  Therefore, I orphan this package now.

Maintaining a package requires time and skills. Please only adopt this
package if you will have enough time and attention to work on it.

If you want to be the new maintainer, please see
https://www.debian.org/devel/wnpp/index.html#howto-o for detailed
instructions how to adopt a package properly.

Some information about this package:

Package: tint
Binary: tint
Version: 0.04+nmu1
Maintainer: Mario Lang 
Build-Depends: debhelper (>= 7), libncurses5-dev
Architecture: any
Standards-Version: 3.9.1
Format: 3.0 (native)
Files:
 32b0e1ca784c1b4a0fc8dc521a0302c8 836 tint_0.04+nmu1.dsc
 40e4674fcf2531c638cc32b6b09123aa 16037 tint_0.04+nmu1.tar.gz
Checksums-Sha256:
 af9d47bc58b7b2ebb0172a162122c1918738bfb1ca15ad92bffe0be914bc1603 836 
tint_0.04+nmu1.dsc
 c1ebbf652e6bec8fa8bfb5ebc94620dd8dc474b0bb647f61b93e2948837aeb9d 16037 
tint_0.04+nmu1.tar.gz
Directory: pool/main/t/tint
Priority: source
Section: games

Package: tint
Binary: tint
Version: 0.04+nmu1
Maintainer: Mario Lang 
Build-Depends: debhelper (>= 7), libncurses5-dev
Architecture: any
Standards-Version: 3.9.1
Format: 3.0 (native)
Files:
 32b0e1ca784c1b4a0fc8dc521a0302c8 836 tint_0.04+nmu1.dsc
 40e4674fcf2531c638cc32b6b09123aa 16037 tint_0.04+nmu1.tar.gz
Checksums-Sha1:
 76272a7ce53f85b604af85bc3f4fdc2c6a81c1d4 836 tint_0.04+nmu1.dsc
 7fcaa428c6d0de7096d1e4fbfd14848096ae5aad 16037 tint_0.04+nmu1.tar.gz
Checksums-Sha256:
 af9d47bc58b7b2ebb0172a162122c1918738bfb1ca15ad92bffe0be914bc1603 836 
tint_0.04+nmu1.dsc
 c1ebbf652e6bec8fa8bfb5ebc94620dd8dc474b0bb647f61b93e2948837aeb9d 16037 
tint_0.04+nmu1.tar.gz
Directory: pool/main/t/tint
Priority: source
Section: games

Package: tint
Source: tint (0.04+nmu1)
Version: 0.04+nmu1+b1
Installed-Size: 50
Maintainer: Mario Lang 
Architecture: amd64
Depends: libc6 (>= 2.14), libncurses5 (>= 6), libtinfo5 (>= 6)
Description-en: TINT Is Not Tetris(tm) ...at least the name isn't
 As the title suggests, this is a clone of the original tetris game
 written by Alexey Pajitnov, Dmitry Pavlovsky, and Vadim Gerasimov.
 .
 The game is as close to the original as possible, but there are a few
 differences.  Nevertheless, it's probably the closest to the original
 that you'll ever find in the UNIX world...
Description-md5: 7b971b35a8d49408337096b3ebaf7947
Tag: game::tetris, interface::text-mode, role::program, uitoolkit::ncurses,
 use::gameplaying
Section: games
Priority: optional
Filename: pool/main/t/tint/tint_0.04+nmu1+b1_amd64.deb
Size: 15150
MD5sum: 7eb0d6395e363c9883a4d64d61af3a65
SHA256: f2b6424c7aa7e67e0952e14eb57481eac58f270bfd44637a9c4ece83a8ce6cba

Package: tint
Source: tint (0.04+nmu1)
Version: 0.04+nmu1+b1
Installed-Size: 50
Maintainer: Mario Lang 
Architecture: amd64
Depends: libc6 (>= 2.14), libncurses5 (>= 6), libtinfo5 (>= 6)
Description-en: TINT Is Not Tetris(tm) ...at least the name isn't
 As the title suggests, this is a clone of the original tetris game
 written by Alexey Pajitnov, Dmitry Pavlovsky, and Vadim Gerasimov.
 .
 The game is as close to the original as possible, but there are a few
 differences.  Nevertheless, it's probably the closest to the original
 that you'll ever find in the UNIX world...
Description-md5: 7b971b35a8d49408337096b3ebaf7947
Tag: game::tetris, interface::text-mode, role::program, uitoolkit::ncurses,
 use::gameplaying
Section: games
Priority: optional
Filename: pool/main/t/tint/tint_0.04+nmu1+b1_amd64.deb
Size: 15150
MD5sum: 7eb0d6395e363c9883a4d64d61af3a65
SHA256: f2b6424c7aa7e67e0952e14eb57481eac58f270bfd44637a9c4ece83a8ce6cba



signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: tint
Source-Version: 0.05

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

Bug#912289: marked as done (devilspie2 FTCBFS: multiple reasons)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 19:19:10 +
with message-id 
and subject line Bug#912289: fixed in devilspie2 0.43-3
has caused the Debian Bug report #912289,
regarding devilspie2 FTCBFS: multiple reasons
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.)


-- 
912289: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912289
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: devilspie2
Version: 0.43-2
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

devilspie2 fails to cross build from source. debian/rules does not pass
cross tools to make. The easiest way of fixing that is using
dh_auto_build. Then the upstream Makefile hard codes the build
architecture pkg-config. The attached patch fixes both and makes
devilspie2 cross buildable. Please consider applying it.

Helmut
diff --minimal -Nru devilspie2-0.43/debian/changelog 
devilspie2-0.43/debian/changelog
--- devilspie2-0.43/debian/changelog2018-07-21 13:24:37.0 +0200
+++ devilspie2-0.43/debian/changelog2018-10-29 22:07:24.0 +0100
@@ -1,3 +1,12 @@
+devilspie2 (0.43-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Let dh_auto_build pass cross tools to make.
++ cross.patch: Make pkg-config substitutable.
+
+ -- Helmut Grohne   Mon, 29 Oct 2018 22:07:24 +0100
+
 devilspie2 (0.43-2) unstable; urgency=medium
 
   * QA upload.
diff --minimal -Nru devilspie2-0.43/debian/patches/cross.patch 
devilspie2-0.43/debian/patches/cross.patch
--- devilspie2-0.43/debian/patches/cross.patch  1970-01-01 01:00:00.0 
+0100
+++ devilspie2-0.43/debian/patches/cross.patch  2018-10-29 22:07:24.0 
+0100
@@ -0,0 +1,24 @@
+--- devilspie2-0.43.orig/Makefile
 devilspie2-0.43/Makefile
+@@ -20,6 +20,9 @@
+ ifndef CC
+   CC=gcc
+ endif
++ifndef PKG_CONFIG
++  PKG_CONFIG=pkg-config
++endif
+ SRC=src
+ OBJ=obj
+ BIN=bin
+@@ -59,9 +62,9 @@
+   PKG_WNCK=libwnck-3.0
+ endif
+ 
+-LIB_CFLAGS=$(shell pkg-config --cflags --silence-errors $(PKG_GTK) 
$(PKG_WNCK) lua5.1 || pkg-config --cflags $(PKG_GTK) $(PKG_WNCK) lua)
++LIB_CFLAGS=$(shell $(PKG_CONFIG) --cflags --silence-errors $(PKG_GTK) 
$(PKG_WNCK) lua5.1 || $(PKG_CONFIG) --cflags $(PKG_GTK) $(PKG_WNCK) lua)
+ STD_LDFLAGS=
+-LIBS=-lX11 $(shell pkg-config --libs --silence-errors $(PKG_GTK) $(PKG_WNCK) 
lua5.1 || pkg-config --libs $(PKG_GTK) $(PKG_WNCK) lua)
++LIBS=-lX11 $(shell $(PKG_CONFIG) --libs --silence-errors $(PKG_GTK) 
$(PKG_WNCK) lua5.1 || $(PKG_CONFIG) --libs $(PKG_GTK) $(PKG_WNCK) lua)
+ 
+ LOCAL_CFLAGS=$(STD_CFLAGS) $(DEPRECATED) $(CFLAGS) $(LIB_CFLAGS)
+ LOCAL_LDFLAGS=$(STD_CFLAGS) $(LDFLAGS) $(STD_LDFLAGS)
diff --minimal -Nru devilspie2-0.43/debian/patches/series 
devilspie2-0.43/debian/patches/series
--- devilspie2-0.43/debian/patches/series   2017-09-26 15:30:40.0 
+0200
+++ devilspie2-0.43/debian/patches/series   2018-10-29 22:07:24.0 
+0100
@@ -0,0 +1 @@
+cross.patch
diff --minimal -Nru devilspie2-0.43/debian/rules devilspie2-0.43/debian/rules
--- devilspie2-0.43/debian/rules2017-09-26 15:30:40.0 +0200
+++ devilspie2-0.43/debian/rules2018-10-29 22:07:22.0 +0100
@@ -11,7 +11,7 @@
dh $@
 
 override_dh_auto_build:
-   $(MAKE) PREFIX=/usr
+   dh_auto_build -- PREFIX=/usr
 
 override_dh_auto_install:
$(MAKE) DESTDIR=$$(pwd)/debian/devilspie2 PREFIX=/usr install
--- End Message ---
--- Begin Message ---
Source: devilspie2
Source-Version: 0.43-3

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

Debian distribution maintenance software
pp.
Andreas Rönnquist  (supplier of updated devilspie2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Jan 2019 18:33:06 +0100
Source: devilspie2
Architecture: source
Version: 0.43-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Rönnquist 
Closes: 912289
Changes:
 devilspie2 (0.43-3) unstable; urgency=medium
 .
   [ Andreas Rönnquist ]
   * QA upload
 

Bug#919801: marked as done (javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 22:12:41 +0100
with message-id <27efe383-a22a-1ff8-35a5-89238b413...@debian.org>
and subject line Re: libgoogle-gson-java: FTBFS (Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar)
has caused the Debian Bug report #919801,
regarding javadoc: The code being documented uses modules but the packages 
defined in … are in the unnamed module
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.)


-- 
919801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919801
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libgoogle-gson-java
Version: 2.8.5-2
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 javahelper --buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   dh_autoreconf -i -O--buildsystem=maven
   dh_auto_configure -i -O--buildsystem=maven
mh_patchpoms -plibgoogle-gson-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
[ERROR] Cannot find parent dependency 
com.google.code.gson:gson-parent:pom:2.8.5, use --no-parent option to resolve 
this issue or install the parent POM in the Maven repository
   jh_linkjars -i -O--buildsystem=maven
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
cp -Rvp gson/src/main/java-templates/* gson/src/main/java/
'gson/src/main/java-templates/com/google/gson/internal/GsonBuildConfig.java' -> 
'gson/src/main/java/com/google/gson/internal/GsonBuildConfig.java'
sed -i s/\$\{project.version\}/2.8.5/ 
gson/src/main/java/com/google/gson/internal/GsonBuildConfig.java
dh_auto_build

[... snipped ...]

[ERROR] 
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:87: 
warning - invalid usage of tag >
[ERROR] 
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:100: 
warning - invalid usage of tag >
[ERROR] 
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:102: 
warning - invalid usage of tag >
[ERROR] 
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:103: 
warning - invalid usage of tag >
[ERROR] 
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:104: 
warning - invalid usage of tag >
[ERROR] 
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:105: 
warning - invalid usage of tag >
[ERROR] 
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:123: 
warning - invalid usage of tag >
[ERROR] 
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:125: 
warning - invalid usage of tag >
[ERROR] 
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:126: 
warning - invalid usage of tag >
[ERROR] 
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:127: 
warning - invalid usage of tag >
[ERROR] 
/<>/gson/src/main/java/com/google/gson/FieldNamingPolicy.java:128: 
warning - invalid usage of tag >
[ERROR] 
/<>/gson/src/main/java/com/google/gson/annotations/Expose.java:37: 
warning - invalid usage of tag 
[ERROR] 
/<>/gson/src/main/java/com/google/gson/annotations/Expose.java:38: 
warning - invalid usage of tag 
[ERROR] 
/<>/gson/src/main/java/com/google/gson/annotations/Expose.java:39: 
warning - invalid usage of tag 
[ERROR] 
/<>/gson/src/main/java/com/google/gson/annotations/JsonAdapter.java:34:
 warning - invalid usage of tag 
[ERROR] 
/<>/gson/src/main/java/com/google/gson/annotations/JsonAdapter.java:43:
 warning - invalid usage of tag 
[ERROR] 
/<>/gson/src/main/java/com/google/gson/annotations/JsonAdapter.java:51:
 warning - invalid usage of tag 
[ERROR] 
/<>/gson/src/main/java/com/google/gson/annotations/JsonAdapter.java:62:
 warning - invalid usage of tag 
[ERROR] 
/<>/gson/src/main/java/com/google/gson/annotations/JsonAdapter.java:68:
 warning - invalid usage of tag 
[ERROR] 
/<>/gson/src/main/java/com/google/gson/annotations/SerializedName.java:38:
 warning - invalid usage of tag 
[ERROR] 
/<>/gson/src/main/java/com/google/gson/annotations/SerializedName.java:39:
 warning - invalid usage of tag 
[ERROR] 
/<>/gson/src/main/java/com/google/gson/annotations/Since.java:39: 
warning - invalid usage of tag 
[ERROR] 
/<>/gson/src/main/java/com/google/gson/annotations/Since.java:40: 
warning - invalid usage of tag 
[ERROR] 
/<>/gson/src/main/java/com/google/gson/annotations/Since.java:41: 
warning - invalid usage of tag 
[ERROR] 
/<>/gson/src/main/java/com/google/gson/annotations/Until.java:41: 
warning - invalid usage of tag 
[ERROR] 

Bug#920281: marked as done (ntopng: Unable to finish the post-inst.)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 16:00:10 +
with message-id 
and subject line Bug#920281: fixed in ntopng 3.8+dfsg1-2
has caused the Debian Bug report #920281,
regarding ntopng: Unable to finish the post-inst.
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.)


-- 
920281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ntopng
Version: 3.8+dfsg1-1
Severity: normal

Dear Maintainer,

ntopng’s installation can’t be finished because of a bug in the post-inst
script.

Paramétrage de ntopng (3.8+dfsg1-1) ...
Migrating data from /var/tmp/ntopng to /var/lib/ntopng...
tar: -C : open impossible: Aucun fichier ou dossier de ce type
tar: Error is not recoverable: exiting now
Relais brisé (pipe)
dpkg: erreur de traitement du paquet ntopng (--configure) :
 installed ntopng package post-installation script subprocess returned error
exit status 2

In English (my translation):
tar: -C : open impossible: No such file or directory
tar: Error is not recoverable: exiting now
Broken pipe
dpkg: error during package process ntopng (--configure) :



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

Kernel: Linux 4.17.0-3-686-pae (SMP w/3 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_FR:fr:en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ntopng depends on:
ii  adduser  3.118
ii  libc62.28-5
ii  libcap2  1:2.25-1.2
ii  libcurl3-gnutls  7.63.0-1
ii  libgcc1  1:8.2.0-14
ii  libhiredis0.14   0.14.0-3
ii  libjson-c3   0.12.1+ds-2
ii  liblua5.3-0  5.3.3-1.1
ii  libmariadb3  1:10.3.12-1
ii  libmaxminddb01.3.2-1
ii  libndpi2.6   2.6-3
ii  libpcap0.8   1.8.1-6
ii  librrd8  1.7.0-1+b3
ii  libsodium23  1.0.16-2
ii  libsqlite3-0 3.26.0+fossilbc891ac6b-1
ii  libssl1.11.1.1a-1
ii  libstdc++6   8.2.0-14
ii  libzmq5  4.3.1-2
ii  lsb-base 10.2018112800
ii  ntopng-data  3.8+dfsg1-1
ii  redis-server 5:5.0.3-4
ii  zlib1g   1:1.2.11.dfsg-1

ntopng recommends no packages.

Versions of packages ntopng suggests:
pn  geoip-database-contrib  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ntopng
Source-Version: 3.8+dfsg1-2

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

Debian distribution maintenance software
pp.
Ludovico Cavedon  (supplier of updated ntopng package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Jan 2019 00:36:22 -0800
Source: ntopng
Binary: ntopng ntopng-data ntopng-doc
Architecture: source all amd64
Version: 3.8+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Ludovico Cavedon 
Changed-By: Ludovico Cavedon 
Description:
 ntopng - High-Speed Web-based Traffic Analysis and Flow Collection Tool
 ntopng-data - High-Speed Web-based Traffic Analysis and Flow Collection Tool (d
 ntopng-doc - High-Speed Web-based Traffic Analysis and Flow Collection Tool (d
Closes: 920281
Changes:
 ntopng (3.8+dfsg1-2) unstable; urgency=medium
 .
   * Fix missing space in postinst migration script (Closes: #920281).
   * Delete ntopng user, group, /var/lib/ntopng, /var/log/ntopng during purge.
   * Set appropriate permissions for /var/log/ntopng.
Checksums-Sha1:
 047289714ff4fd2736c780db79e91230b2c84dea 2321 ntopng_3.8+dfsg1-2.dsc
 6a8b149392c2c6622fd6a5c8a8e2def08d3d4b9c 27880 ntopng_3.8+dfsg1-2.debian.tar.xz
 82cd39593e2b6ba52896a86e38d0bef56a7d074b 1867540 
ntopng-data_3.8+dfsg1-2_all.deb
 b6a0f85fb3b17dfb9f1d90ccb1d0245337fd377a 3818504 
ntopng-dbgsym_3.8+dfsg1-2_amd64.deb
 a4578610dec97efcc7f36721e9e05ee5f2efbd8a 25123536 
ntopng-doc_3.8+dfsg1-2_all.deb
 ac3236be8a98ffde387a161b1f6708cb9055e885 12435 
ntopng_3.8+dfsg1-2_amd64.buildinfo
 5e548ac342947ee0d5bbbd3a732005e7b057ff3f 352952 

Bug#920310: marked as done (quagga: unnecessary Build-Depends on pcre3)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 16:50:04 +
with message-id 
and subject line Bug#920310: fixed in quagga 1.2.4-3
has caused the Debian Bug report #920310,
regarding quagga: unnecessary Build-Depends on pcre3
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.)


-- 
920310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: quagga
Version: 1.2.4-2
Severity: minor

While investigating packages in Ubuntu main that use pcre3, I noticed
that quagga Build-Depends on libpcre3-dev. However, it is not actually
used during the build since quagga defaults to using the GNU regexp
library unless we used --enable-pcreposix which we don't.

pcre3 is the older library (despite its confusing name) and we're
trying to use pcre2 instead.

So I recommend just dropping libpcre3-dev from your Build-Depends.

Thanks,
Jeremy Bicha
--- End Message ---
--- Begin Message ---
Source: quagga
Source-Version: 1.2.4-3

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

Debian distribution maintenance software
pp.
Brett Parker  (supplier of updated quagga package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Jan 2019 10:32:12 +
Source: quagga
Binary: quagga quagga-bgpd quagga-bgpd-dbgsym quagga-core quagga-core-dbgsym 
quagga-doc quagga-isisd quagga-isisd-dbgsym quagga-ospf6d quagga-ospf6d-dbgsym 
quagga-ospfd quagga-ospfd-dbgsym quagga-pimd quagga-pimd-dbgsym quagga-ripd 
quagga-ripd-dbgsym quagga-ripngd quagga-ripngd-dbgsym
Architecture: source amd64 all
Version: 1.2.4-3
Distribution: unstable
Urgency: medium
Maintainer: Brett Parker 
Changed-By: Brett Parker 
Description:
 quagga - network routing daemons (metapackage)
 quagga-bgpd - BGP4/BGP4+ routing daemon
 quagga-core - network routing daemons (core abstraction layer)
 quagga-doc - network routing daemons (documentation)
 quagga-isisd - IS-IS routing daemon
 quagga-ospf6d - OSPF6 routing daemon
 quagga-ospfd - OSPF routing daemon
 quagga-pimd - PIM routing daemon
 quagga-ripd - RIPv1 routing daemon
 quagga-ripngd - RIPng routing daemon
Closes: 920310
Changes:
 quagga (1.2.4-3) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/copyright: Use https protocol in Format field
   * d/changelog: Remove trailing whitespaces
 .
   [ Brett Parker ]
   * d/control: remove build dep on libpcre3-dev (Closes: #920310)
Checksums-Sha1:
 bfc0764bccc03bceb7a00bf2c200adb818d1be39 2620 quagga_1.2.4-3.dsc
 e4e0d51429cff51372975deedf0a476716ed0776 30716 quagga_1.2.4-3.debian.tar.xz
 3b9406a345b2825d1ba2945787cef63c32d1d795 839024 
quagga-bgpd-dbgsym_1.2.4-3_amd64.deb
 f0a3ddf27c98ddbbe012e0500e11c07d7bd78338 255196 quagga-bgpd_1.2.4-3_amd64.deb
 a9406383315347fce27b07d4830a61c2898e3f61 1612296 
quagga-core-dbgsym_1.2.4-3_amd64.deb
 9be59ad958b5c9b4ee70e18f81b4a4ff3c0ccef7 553624 quagga-core_1.2.4-3_amd64.deb
 999db3536841b725e7fae1abce05fc85ecb0a1ec 882480 quagga-doc_1.2.4-3_all.deb
 d9227a82961d55ccc0c74b9d2c58b6014349504e 376216 
quagga-isisd-dbgsym_1.2.4-3_amd64.deb
 0437250e081d002550843d04bd7941fdc1320492 126648 quagga-isisd_1.2.4-3_amd64.deb
 678277fc494e2f13c43ff71c60c4a55c755aa402 347160 
quagga-ospf6d-dbgsym_1.2.4-3_amd64.deb
 1302f2950f07dca0d94edc044d1c74810b245218 124676 quagga-ospf6d_1.2.4-3_amd64.deb
 02cef6e5daca185e50f712653040f59977ccedeb 24468 
quagga-ospfd-dbgsym_1.2.4-3_amd64.deb
 8e0aff8ef1145a7182661ecf1a821cc988162289 32516 quagga-ospfd_1.2.4-3_amd64.deb
 6f277404ea2978b1f7d926edb72341a8fb855cbf 319988 
quagga-pimd-dbgsym_1.2.4-3_amd64.deb
 adc51019ac2445fc2bd7ff02cfdcfadf0202cbd1 113096 quagga-pimd_1.2.4-3_amd64.deb
 8ed99a76fc3e64bb1a07ba6ab06392bb1a676679 141824 
quagga-ripd-dbgsym_1.2.4-3_amd64.deb
 428313d4765fb5e06d1fb4beb0a1f528e39812bc 65344 quagga-ripd_1.2.4-3_amd64.deb
 03792474115c6fe6fdba7cc2721b1e8b13563a96 121908 
quagga-ripngd-dbgsym_1.2.4-3_amd64.deb
 68c188b59dc8d0f4bea76455e4560b503046b5f2 57720 quagga-ripngd_1.2.4-3_amd64.deb
 9f7414fbd22933fb8e4beb208e121b3902d8afad 13581 

Bug#738046: marked as done (tint: please provide a desktop file and icons)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 16:06:49 +
with message-id 
and subject line Bug#738046: fixed in tint 0.05
has caused the Debian Bug report #738046,
regarding tint: please provide a desktop file and icons
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.)


-- 
738046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738046
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tint
Version: 0.04+nmu1
Severity: wishlist
User: pkg-games-de...@lists.alioth.debian.org
Usertags: desktop-integration goals not-gamesteam

Dear maintainer,

currently tint does not supply a desktop file and
no desktop and menu icons. Hence the game is not well integrated into
the user's desktop environment. Please consider helping to improve the
desktop integration of games in Debian.

Please refer to the empire package for a ncurses-based game that already
provides desktop and menu files and to

https://wiki.debian.org/Games/JessieReleaseGoal

Regards,

Markus





signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: tint
Source-Version: 0.05

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

Debian distribution maintenance software
pp.
Ricardo Mones  (supplier of updated tint package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Jan 2019 16:33:35 +0100
Source: tint
Binary: tint tint-dbgsym
Architecture: source amd64
Version: 0.05
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team 
Changed-By: Ricardo Mones 
Description:
 tint   - Tetris clone for text based terminal
Closes: 738046 769296 823220 840874
Changes:
 tint (0.05) unstable; urgency=medium
 .
   * Put package under Games Team umbrella (Closes: #840874)
   * Switch copyright to machine-readable format (Closes: #823220)
   * Migrate menu to .desktop; add icon; install both (Closes: #738046)
   * Document global scores usage (Closes: #769296)
   * Bump debhelper compat level to 11
   * Update Standards-Version to 4.3.0
   * Remove package name from short description
   * Remove flags from shell line
   * Add Vcs-{Git|Browser} with current URLs
   * Remove whitespace and editor's config lines
Checksums-Sha1:
 02b76f00dd2d3e817be6ade31b99563b85368dde 1561 tint_0.05.dsc
 859008216930a4584e622d0df41fd75c44d2b47f 24180 tint_0.05.tar.xz
 db0db465ab54565ae4a0274e934ee8ee49573125 22992 tint-dbgsym_0.05_amd64.deb
 07934067c4d5864b30cb0c3cc36a7df6130f78ff 5632 tint_0.05_amd64.buildinfo
 c6d9d0462901a59d3ff64d5a9209f518447c9c56 25468 tint_0.05_amd64.deb
Checksums-Sha256:
 f4e035cabf71f7765ec39b6af6c639f23a847cd5ff18fcbcf179364144f47d9e 1561 
tint_0.05.dsc
 d9ac7ee1199b391d5b79a0a324d179fe5148ce4e64460cbbd49c44c6f11dd7dd 24180 
tint_0.05.tar.xz
 287f2b7d7663215da9be7a51a0b192de3bbab7252cf578a4672f3e1e46886463 22992 
tint-dbgsym_0.05_amd64.deb
 3a537059ba029a3c632ad8ab280391097e2e1109eba4f8f895569395c77f219e 5632 
tint_0.05_amd64.buildinfo
 956dd323b6b4954c6d1e6cec7d5791a8d7deaf62fb6b79973e0c6a56f20f393b 25468 
tint_0.05_amd64.deb
Files:
 56c9f36e49306a167a826d756a70215b 1561 games optional tint_0.05.dsc
 134c5fac011bf3148c86be11540ac98b 24180 games optional tint_0.05.tar.xz
 478b9b4fae11729a790c90c142649aea 22992 debug optional 
tint-dbgsym_0.05_amd64.deb
 5077d24c2f2a8a3117544ceceb417b7d 5632 games optional tint_0.05_amd64.buildinfo
 390501b10793850678d81e9f3395a7cd 25468 games optional tint_0.05_amd64.deb

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEQ7w2SxbfDCBevXWSHw8KiN5bzKYFAlxMgfQACgkQHw8KiN5b
zKZpVRAAqYdqkT9EAczuLxLZHqw2yStZ6Gbxb764fkHqyw2hsotZqofqAukFucg/
KGhwjkO6i2jUUqbhRUoHxZ8rvqzTXFKnrTwMmcCSb3Ff0UGuwQSjuLNjPrARvdWY
QhsXLaJ5TKgX4AtNhpa50swc8gtIV5vjDFdtKMVe16UlPC4E7Vu5kcHZi+h10ZUW
zoQuZszOqN3e6yUBkAd0g0m+mV3vd1lGz1doxFoU1WJZlMbR6MLe4G+wR13CONR4
3eJOEfkrwJRZwYl6/hNc1GE0WDUAg6XLsZVkNbKx6jERbVUII0c95Wsq3wMqBxJP
B0+U2AVjV3XHuTRmEl+3+GgYBh+y9MYlQGtaqu4uPkJDNhsG6FaqvjrfQdfI5B9u
9B6qjkKNg8SUlqS2XxObgf3rVH+fmS1sxF/XWq0swGml7y2Q0Z8k9h/iUwKfu2Q5
rKLdb1ihY3/2VBD/8P4BWm8GFuQcUgu4zvifoHTpQrRLNJ6aQTB1vXiMx4G0IWJD

Bug#750236: marked as done (einstein: corrections for russian translation)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 17:35:02 +
with message-id 
and subject line Bug#750236: fixed in einstein 2.0.dfsg.2-10
has caused the Debian Bug report #750236,
regarding einstein: corrections for russian translation
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.)


-- 
750236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=750236
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: einstein
Severity: wishlist
Tags: patch


- Forwarded message from Alexander Gulchenko  -

Date: Tue, 27 May 2014 12:47:24 +0300
From: Alexander Gulchenko 
To: ba...@debian.org
Subject: Patch for Debian einstein package

Good day!
I noticed some spelling errors in the Russian translation of the "Einstein"
game.
So I prepared a patch to fix them.
This is my first patch, so I could do something wrong. If you want me to
redo something or just send a modified file, please contact.

Enclosed please find a patch in a separate file.



- End forwarded message -
--- End Message ---
--- Begin Message ---
Source: einstein
Source-Version: 2.0.dfsg.2-10

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

Debian distribution maintenance software
pp.
Bart Martens  (supplier of updated einstein package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Jan 2019 17:40:31 +0100
Source: einstein
Binary: einstein
Architecture: source amd64
Version: 2.0.dfsg.2-10
Distribution: unstable
Urgency: medium
Maintainer: Bart Martens 
Changed-By: Bart Martens 
Description:
 einstein   - Puzzle game inspired on Einstein's puzzle
Closes: 750236 854590 901657
Changes:
 einstein (2.0.dfsg.2-10) unstable; urgency=medium
 .
   * Replaced ttf-dejavu by fonts-dejavu-core. Closes: #901657.
   * Set homepage to PTS page. Closes: #854590.
   * Added 16_russian.diff. Closes: #750236.
   * Added debian/clean.
Checksums-Sha1:
 2b6d88818a609f4a7e4f1f01f2cc333da21a797b 1881 einstein_2.0.dfsg.2-10.dsc
 f1a8a9231ae92f8ac04ae110c7ffb4630fa49917 15484 
einstein_2.0.dfsg.2-10.debian.tar.xz
 298cc8c458483b516d2958371e675eb97e31f0c0 10413 
einstein_2.0.dfsg.2-10_amd64.buildinfo
 80312dbfc4cd803292dac129eb9d5a615d08f8bb 1051956 
einstein_2.0.dfsg.2-10_amd64.deb
Checksums-Sha256:
 589b357d7912424964919340c8491feb0e6856d0e8468f8bcde91dc4fffb08d5 1881 
einstein_2.0.dfsg.2-10.dsc
 4918ea82844ac4d609e3ec41dc0b0feab177da593e0e14f2256be09d8bf53c8d 15484 
einstein_2.0.dfsg.2-10.debian.tar.xz
 5c6707c9aa37a261d484ab3abe68a44a476298ded38cf6ec10360d4c6bdffbe0 10413 
einstein_2.0.dfsg.2-10_amd64.buildinfo
 24ea360c96a1392cef15efb381bc3f6a90a9113b56f4259fac5357200c60cbce 1051956 
einstein_2.0.dfsg.2-10_amd64.deb
Files:
 3cfaf84552c632c457ffcbeafff3559d 1881 games optional einstein_2.0.dfsg.2-10.dsc
 0c5b1873be362f6036b3cff96905c853 15484 games optional 
einstein_2.0.dfsg.2-10.debian.tar.xz
 aba8cdf0afed45b69f67e85ff92731b5 10413 games optional 
einstein_2.0.dfsg.2-10_amd64.buildinfo
 b1379ae9f6f3effb0938b724227e53db 1051956 games optional 
einstein_2.0.dfsg.2-10_amd64.deb

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEZaEt9P4xrWusTXauM1X01jtYIcwFAlxMltURHGJhcnRtQGRl
Ymlhbi5vcmcACgkQM1X01jtYIcxFAg//UVC0VfxVru5cNU3ah1bB/Xy2SwzAHbwu
dGBFfwNHuM7X4YNWQsV+WgxjDfzNa88NSHg2ilb8eCO6lFhHqEDVzQCvpNtzoo9s
cCTinMjo3MzHjyvwqP5mCAih90jMvL3eWD4/Hmx6t3E0P0ybJPkhfbriBhI1wCdt
9v5stoNla2NvLXxyktUPxKTUYQFr3iNtwPu/XeqG9y+yC1pI+2UyqJHLSblV6s93
y8QgRxXX9EUolKj1iLkJsMyBYncePK9Xcq6gSMSOwMS3ZB3FFkMhGn5Vs/w5XFsy
aR6+PJrnvq+grWf7BB7WBUHqdyO/b1ti7xomhnc6FUCRQJEOHcKfcZ+czI8s23hq
HtbNnGHLG72H1stiYk6KZdWNhpA4x+9noCcqVD1tG/Cl81KZhBzltlfN6NJdQisI
flZrmORlcVkIo0PuAYC+aiXX5021j0qrZziKS3AL/0Kdcjl9AyVSFv2p0vkac2RU
aPkf/LV7Wcut3OFu5PeJ5/cMqOGkNQFfdapZVaUdn+wQe8244MAOflHKQs5bsst+
ORUltpG2+sdSWRoRlhMs19RUYFRLsq2rsGYTBVCm9FgWCVhtE11jUfmLk18YyyIq
ErRLzlid8ss9vYCaMpSiuvsd9xOt/R9U09hALewy4IzTnB09cDWBZs+QMAAf4HCd
LRe1jgZzGGw=
=krrt
-END PGP SIGNATURE End Message ---

Bug#901657: marked as done (einstein Build-Depends on transitional package ttf-dejavu)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 17:35:02 +
with message-id 
and subject line Bug#901657: fixed in einstein 2.0.dfsg.2-10
has caused the Debian Bug report #901657,
regarding einstein Build-Depends on transitional package ttf-dejavu
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.)


-- 
901657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: einstein
Version: 2.0.dfsg.2-9
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

einstein Build-Depends on ttf-dejavu, which is a transitional package.
The attached patch moves it to fonts-dejavu-core. Please consider
applying it.

As it happens, ttf-dejavu does not work for cross building.

Helmut
diff --minimal -Nru einstein-2.0.dfsg.2/debian/changelog 
einstein-2.0.dfsg.2/debian/changelog
--- einstein-2.0.dfsg.2/debian/changelog2012-04-29 15:22:15.0 
+0200
+++ einstein-2.0.dfsg.2/debian/changelog2018-06-16 12:48:42.0 
+0200
@@ -1,3 +1,10 @@
+einstein (2.0.dfsg.2-9.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update Build-Depends ttf-dejavu -> fonts-dejavu-core.  Closes: #-1.
+
+ -- Helmut Grohne   Sat, 16 Jun 2018 12:48:42 +0200
+
 einstein (2.0.dfsg.2-9) unstable; urgency=low
 
   * Added libfreetype6-dev to Build-Depends.  Closes: #669490.
diff --minimal -Nru einstein-2.0.dfsg.2/debian/control 
einstein-2.0.dfsg.2/debian/control
--- einstein-2.0.dfsg.2/debian/control  2012-04-29 15:46:09.0 +0200
+++ einstein-2.0.dfsg.2/debian/control  2018-06-16 12:48:42.0 +0200
@@ -2,7 +2,7 @@
 Section: games
 Priority: optional
 Maintainer: Bart Martens 
-Build-Depends: debhelper (>= 8.0.0), libsdl-ttf2.0-dev, libsdl-mixer1.2-dev, 
zlib1g-dev, ttf-dejavu, sharutils, libfreetype6-dev
+Build-Depends: debhelper (>= 8.0.0), libsdl-ttf2.0-dev, libsdl-mixer1.2-dev, 
zlib1g-dev, fonts-dejavu-core, sharutils, libfreetype6-dev
 Standards-Version: 3.9.3
 Homepage: http://games.flowix.com/
 
diff --minimal -Nru einstein-2.0.dfsg.2/debian/rules 
einstein-2.0.dfsg.2/debian/rules
--- einstein-2.0.dfsg.2/debian/rules2011-09-25 14:48:25.0 +0200
+++ einstein-2.0.dfsg.2/debian/rules2018-06-16 12:48:42.0 +0200
@@ -7,7 +7,7 @@
 
 override_dh_auto_configure:
dh_auto_configure
-   [ -f res/DejaVuSans.ttf ] || cp -p 
/usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf res/
+   [ -f res/DejaVuSans.ttf ] || cp -p 
/usr/share/fonts/truetype/dejavu/DejaVuSans.ttf res/
uudecode debian/einstein.png.uue
uudecode debian/icon.bmp.uue
 
--- End Message ---
--- Begin Message ---
Source: einstein
Source-Version: 2.0.dfsg.2-10

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

Debian distribution maintenance software
pp.
Bart Martens  (supplier of updated einstein package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Jan 2019 17:40:31 +0100
Source: einstein
Binary: einstein
Architecture: source amd64
Version: 2.0.dfsg.2-10
Distribution: unstable
Urgency: medium
Maintainer: Bart Martens 
Changed-By: Bart Martens 
Description:
 einstein   - Puzzle game inspired on Einstein's puzzle
Closes: 750236 854590 901657
Changes:
 einstein (2.0.dfsg.2-10) unstable; urgency=medium
 .
   * Replaced ttf-dejavu by fonts-dejavu-core. Closes: #901657.
   * Set homepage to PTS page. Closes: #854590.
   * Added 16_russian.diff. Closes: #750236.
   * Added debian/clean.
Checksums-Sha1:
 2b6d88818a609f4a7e4f1f01f2cc333da21a797b 1881 einstein_2.0.dfsg.2-10.dsc
 f1a8a9231ae92f8ac04ae110c7ffb4630fa49917 15484 
einstein_2.0.dfsg.2-10.debian.tar.xz
 298cc8c458483b516d2958371e675eb97e31f0c0 10413 
einstein_2.0.dfsg.2-10_amd64.buildinfo
 80312dbfc4cd803292dac129eb9d5a615d08f8bb 1051956 
einstein_2.0.dfsg.2-10_amd64.deb
Checksums-Sha256:
 589b357d7912424964919340c8491feb0e6856d0e8468f8bcde91dc4fffb08d5 1881 
einstein_2.0.dfsg.2-10.dsc
 4918ea82844ac4d609e3ec41dc0b0feab177da593e0e14f2256be09d8bf53c8d 15484 
einstein_2.0.dfsg.2-10.debian.tar.xz
 

Bug#854590: marked as done (einstein: Homepage is dead)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 17:35:02 +
with message-id 
and subject line Bug#854590: fixed in einstein 2.0.dfsg.2-10
has caused the Debian Bug report #854590,
regarding einstein: Homepage is dead
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.)


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

The only thing I found that could qualify as upstream is
https://github.com/lksj/einstein-puzzle.
--- End Message ---
--- Begin Message ---
Source: einstein
Source-Version: 2.0.dfsg.2-10

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

Debian distribution maintenance software
pp.
Bart Martens  (supplier of updated einstein package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Jan 2019 17:40:31 +0100
Source: einstein
Binary: einstein
Architecture: source amd64
Version: 2.0.dfsg.2-10
Distribution: unstable
Urgency: medium
Maintainer: Bart Martens 
Changed-By: Bart Martens 
Description:
 einstein   - Puzzle game inspired on Einstein's puzzle
Closes: 750236 854590 901657
Changes:
 einstein (2.0.dfsg.2-10) unstable; urgency=medium
 .
   * Replaced ttf-dejavu by fonts-dejavu-core. Closes: #901657.
   * Set homepage to PTS page. Closes: #854590.
   * Added 16_russian.diff. Closes: #750236.
   * Added debian/clean.
Checksums-Sha1:
 2b6d88818a609f4a7e4f1f01f2cc333da21a797b 1881 einstein_2.0.dfsg.2-10.dsc
 f1a8a9231ae92f8ac04ae110c7ffb4630fa49917 15484 
einstein_2.0.dfsg.2-10.debian.tar.xz
 298cc8c458483b516d2958371e675eb97e31f0c0 10413 
einstein_2.0.dfsg.2-10_amd64.buildinfo
 80312dbfc4cd803292dac129eb9d5a615d08f8bb 1051956 
einstein_2.0.dfsg.2-10_amd64.deb
Checksums-Sha256:
 589b357d7912424964919340c8491feb0e6856d0e8468f8bcde91dc4fffb08d5 1881 
einstein_2.0.dfsg.2-10.dsc
 4918ea82844ac4d609e3ec41dc0b0feab177da593e0e14f2256be09d8bf53c8d 15484 
einstein_2.0.dfsg.2-10.debian.tar.xz
 5c6707c9aa37a261d484ab3abe68a44a476298ded38cf6ec10360d4c6bdffbe0 10413 
einstein_2.0.dfsg.2-10_amd64.buildinfo
 24ea360c96a1392cef15efb381bc3f6a90a9113b56f4259fac5357200c60cbce 1051956 
einstein_2.0.dfsg.2-10_amd64.deb
Files:
 3cfaf84552c632c457ffcbeafff3559d 1881 games optional einstein_2.0.dfsg.2-10.dsc
 0c5b1873be362f6036b3cff96905c853 15484 games optional 
einstein_2.0.dfsg.2-10.debian.tar.xz
 aba8cdf0afed45b69f67e85ff92731b5 10413 games optional 
einstein_2.0.dfsg.2-10_amd64.buildinfo
 b1379ae9f6f3effb0938b724227e53db 1051956 games optional 
einstein_2.0.dfsg.2-10_amd64.deb

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEZaEt9P4xrWusTXauM1X01jtYIcwFAlxMltURHGJhcnRtQGRl
Ymlhbi5vcmcACgkQM1X01jtYIcxFAg//UVC0VfxVru5cNU3ah1bB/Xy2SwzAHbwu
dGBFfwNHuM7X4YNWQsV+WgxjDfzNa88NSHg2ilb8eCO6lFhHqEDVzQCvpNtzoo9s
cCTinMjo3MzHjyvwqP5mCAih90jMvL3eWD4/Hmx6t3E0P0ybJPkhfbriBhI1wCdt
9v5stoNla2NvLXxyktUPxKTUYQFr3iNtwPu/XeqG9y+yC1pI+2UyqJHLSblV6s93
y8QgRxXX9EUolKj1iLkJsMyBYncePK9Xcq6gSMSOwMS3ZB3FFkMhGn5Vs/w5XFsy
aR6+PJrnvq+grWf7BB7WBUHqdyO/b1ti7xomhnc6FUCRQJEOHcKfcZ+czI8s23hq
HtbNnGHLG72H1stiYk6KZdWNhpA4x+9noCcqVD1tG/Cl81KZhBzltlfN6NJdQisI
flZrmORlcVkIo0PuAYC+aiXX5021j0qrZziKS3AL/0Kdcjl9AyVSFv2p0vkac2RU
aPkf/LV7Wcut3OFu5PeJ5/cMqOGkNQFfdapZVaUdn+wQe8244MAOflHKQs5bsst+
ORUltpG2+sdSWRoRlhMs19RUYFRLsq2rsGYTBVCm9FgWCVhtE11jUfmLk18YyyIq
ErRLzlid8ss9vYCaMpSiuvsd9xOt/R9U09hALewy4IzTnB09cDWBZs+QMAAf4HCd
LRe1jgZzGGw=
=krrt
-END PGP SIGNATURE End Message ---

Bug#920515: marked as done (node-xmpp: switch build-depends from nodejs-dev to libnode-dev)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 14:50:36 +
with message-id 
and subject line Bug#920515: fixed in node-xmpp 0.3.2-4
has caused the Debian Bug report #920515,
regarding node-xmpp: switch build-depends from nodejs-dev to libnode-dev
to be marked as done.

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

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


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

Hi,

the old transitional package nodejs-dev is no longer built, please
update your build-depends to libnode-dev.


Andreas
--- End Message ---
--- Begin Message ---
Source: node-xmpp
Source-Version: 0.3.2-4

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

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated node-xmpp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Jan 2019 14:52:54 +0100
Source: node-xmpp
Architecture: source
Version: 0.3.2-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers 

Changed-By: Jérémy Lal 
Closes: 920515
Changes:
 node-xmpp (0.3.2-4) unstable; urgency=medium
 .
   * Team upload
   * Section: javascript
   * Update Vcs-* fields
   * Remove unneeded build-dep on nodejs-dev (Closes: #920515)
   * Standards-Version 4.3.0
   * Use https url for copyright format
   * Depends node-inherits
   * Move Recommends to Depends since they're available and
 actually needed to pass tests.
   * Add two autopkgtests
Checksums-Sha1:
 4d71e9094f628b8ae15613064626f334b7a19ff5 2094 node-xmpp_0.3.2-4.dsc
 15b499ba32f618f3b5b3fe006472e25d50476a97 5420 node-xmpp_0.3.2-4.debian.tar.xz
 73f6e0ad07cbee06ff3198e936841dcd5141e79d 8179 
node-xmpp_0.3.2-4_source.buildinfo
Checksums-Sha256:
 6179d934ed5bbf8de92b991080bca717cf613ce10d1aadabd454692e5d3a7e66 2094 
node-xmpp_0.3.2-4.dsc
 3b49b39032beab989ed654e00c96e75741757745b8275693344ae746007e5fc3 5420 
node-xmpp_0.3.2-4.debian.tar.xz
 e006c1394925ddfc778cc3b1fc54e5fae153b98029f44e975c5cf0e035b6fd0f 8179 
node-xmpp_0.3.2-4_source.buildinfo
Files:
 56994afea3062fa0220925bb56f643ad 2094 javascript optional node-xmpp_0.3.2-4.dsc
 1a09956aa4cc6cbc9637a3be20a57323 5420 javascript optional 
node-xmpp_0.3.2-4.debian.tar.xz
 a819b23a3ff09af281f2b5adb7fe787e 8179 javascript optional 
node-xmpp_0.3.2-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAlxMZnISHGthcG91ZXJA
bWVsaXgub3JnAAoJEGYRwF7dOfN0RhgP/izd+SViKBk/ftgDtsZ5vSjAPwtN806i
++ndztZNcCopJidt4FrK0+fz4gGVEWsAvOvEV2hStYBwGSRCwOCO8Wdz/BBJ5Kgr
0UqSFw4AcG15Gbpz9C2F+lGc8osxfL1AP8fcHNw2wxyDE0gRImQj9AmuOyKSqYHl
SxLqSQuQ2lLEUjwk9OzhsViP/DXkzWdcRe4ShMGb3ZbeZa3t0iVRroSejgpKD5b8
Hpa50fxVvKvbJ/KEKJxeNktfyWN8QfYkMSskgHo8ht88IvNCTGh+31rykzoMG903
xcf5iufpwaWMdjMG/h7bH6IATen8QyqMrEehAgetna8bUYOXZtJjqm2N9mv2P2Yp
YN2XVUjuqtWLHdXVuyMKrAmElGzJx+ixmfU/CWXwCLde5fhQqlYiLezzyBxo+UGv
B4irMLYaZ/02NsGwBvAN4NMaYsowQLup1o6blFeJCUr93Sa3zlKvj5RWOBdR3TOW
QnEpIkPcKr9zcNx60jGiyeKhOsiQ2BlLfqGx6aQQGQmSMPbQjZvVoLJ9PUMmEZ+V
oB+ABQbYYrWf9ta6JQ6ToeNwyi3RIlJaopxVwvM58gW+0FMzfYGibJM15ZfIprKs
91ioPc4Jq+uqUM4RJ6w9Qm7XgM1Yk2YZpYEc6Q9IhwZsqdeJszDKytERd/8Ol6el
ICbzhD+Dq4Ww
=32IG
-END PGP SIGNATURE End Message ---

Bug#919742: marked as done (orthanc-wsi FTBFS 'class GlobalDcmDataDictionary' has no member named 'unlock')

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 14:50:49 +
with message-id 
and subject line Bug#919742: fixed in orthanc-wsi 0.6-1
has caused the Debian Bug report #919742,
regarding orthanc-wsi FTBFS 'class GlobalDcmDataDictionary' has no member named 
'unlock'
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.)


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

Package: orthanc-wsi
Severity: serious
Version: 0.5-2

orthanc-wsi fails to build in unstable, I presume this was triggered by the 
dcmtk transition.

https://buildd.debian.org/status/fetch.php?pkg=orthanc-wsi=amd64=0.5-2%2Bb3=1547409452=0


/<>/BuildApplications/Orthanc-1.3.2/Core/DicomParsing/FromDcmtkBridge.cpp:188:21:
 error: 'class GlobalDcmDataDictionary' has no member named 'unlock'; did you mean 'rdlock'?
  dcmDataDict.unlock();
--- End Message ---
--- Begin Message ---
Source: orthanc-wsi
Source-Version: 0.6-1

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

Debian distribution maintenance software
pp.
Sebastien Jodogne  (supplier of updated orthanc-wsi 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Jan 2019 14:18:06 +0100
Source: orthanc-wsi
Binary: orthanc-wsi orthanc-wsi-dbgsym
Architecture: source amd64
Version: 0.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Sebastien Jodogne 
Description:
 orthanc-wsi - Whole-slide imaging support for Orthanc (digital pathology)
Closes: 919742
Changes:
 orthanc-wsi (0.6-1) unstable; urgency=medium
 .
   * New upstream version
   * Updated d/upstream/metadata with new reference paper about Orthanc
   * Fix FTBFS with dcmtk 3.6.4, Closes: #919742
Checksums-Sha1:
 6247d13c4b6681a6cce938695b843d2c558aac55 2228 orthanc-wsi_0.6-1.dsc
 0565f180fe7b75514bff8a60f3d1570ec5b8c357 114424 orthanc-wsi_0.6.orig.tar.xz
 7a4f89db0eea54f62c5e118cb74a92b6918195f7 1734884 
orthanc-wsi_0.6-1.debian.tar.xz
 dac05ac007b6e691df435773500d68678b3efacd 24098172 
orthanc-wsi-dbgsym_0.6-1_amd64.deb
 93fe28f8d3517b26a3371a04e3b468097c90da2f 14519 
orthanc-wsi_0.6-1_amd64.buildinfo
 bdbb9f1052459787fa90de656612362549ff52bf 820376 orthanc-wsi_0.6-1_amd64.deb
Checksums-Sha256:
 c0e5a5fd98cb708efcefa5a39620af0e04a2d64d2c6d364cc97efbab34298960 2228 
orthanc-wsi_0.6-1.dsc
 0cb4b8f5b5872939cedbef6da47eef249666711451f00f5b54f94c53117d0148 114424 
orthanc-wsi_0.6.orig.tar.xz
 f075b3ad3bbb503ed58115a0f3036950ded5f11760836ec7265443b7647c20ea 1734884 
orthanc-wsi_0.6-1.debian.tar.xz
 afa1ede11af33b13087acfc652b6e234441a3422da3665924cf89175fccd9b19 24098172 
orthanc-wsi-dbgsym_0.6-1_amd64.deb
 9b59b38e62b75fd1ac90587e83aec68571b687055a808601a9c871882ecb5da2 14519 
orthanc-wsi_0.6-1_amd64.buildinfo
 3d9b0e026a7212cc1d1b15b3974566bf45278981db5022fc24c21512f6478f88 820376 
orthanc-wsi_0.6-1_amd64.deb
Files:
 ba3717660ee2b841d5964aac1f4a8212 2228 science optional orthanc-wsi_0.6-1.dsc
 0a62408f527774bb07e05ca317345bd5 114424 science optional 
orthanc-wsi_0.6.orig.tar.xz
 df3add3edc93eb9be47dc6362a832f34 1734884 science optional 
orthanc-wsi_0.6-1.debian.tar.xz
 1af1f39bfc7a630078274ba3204f1115 24098172 debug optional 
orthanc-wsi-dbgsym_0.6-1_amd64.deb
 194e6a7df7825cf8d6a9c02fe5528fa4 14519 science optional 
orthanc-wsi_0.6-1_amd64.buildinfo
 def82f4933d3fe0cbbc07881d297af58 820376 science optional 
orthanc-wsi_0.6-1_amd64.deb

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEk76fGX7V0MMOWT2Lp3ZYKzEqw10FAlxMZpIUHHMuam9kb2du
ZUBnbWFpbC5jb20ACgkQp3ZYKzEqw12fiBAApUFQVWlEoerxzRKrhONPdfmEVQms
M8ipvYrEuu1/GZsoxKp+wgwVQJ+V7IVoYEco59xXq+oP7s3qDH+1MggSyUIZzHc9
NVH5D5ut2IXyM4x1ArrWVW5WAws3J7InJ0xaTXfLgQscvLQf2DHQdbBuET21XDBz
aplRy8mz85HPkXQ/ROIf4ewIAhIb6mnzzyUXZHa5WRnMPOjrPGM+eL9jff2jXh1k
dyXfJ/iq8RZtNdE9Mov/QGEPtHqCXi+LoQFl7kHZTKTyLBrgjZOtg94Rm6ToX0lx
yW/2BuYizD8aV/ZL3F7/Lpqu2W3gcVAttwk0xYtgPZG9wt1l7VeEXeYoGyAfvwIk
LHLi9n5DLKn+TTO9YLSf2yTuUeleok4a6YWbqAsfUIMlLF6uy6DkZvFY6+OcC9+V

Bug#798996: marked as done (Please refer to deb.debian.org over ftp.debian.org in commented-out examples)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 17:42:17 +0100
with message-id <20190126174217.f5e0a017bf392bb093213...@mailbox.org>
and subject line apt-setup: Please refer to deb.debian.org over ftp.debian.org 
in commented-out examples
has caused the Debian Bug report #798996,
regarding Please refer to deb.debian.org over ftp.debian.org in commented-out 
examples
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.)


-- 
798996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798996
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-setup
Version: 1:0.102
Severity: wishlist
Tags: patch

Hi,

Now that httpredir is under debian.org, it makes sense to refer to
httpredir.debian.org over ftp.debian.org in the (NB.) commented-out
example entries.

Patch attached.


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/generators/92updates b/generators/92updates
index d68ca89..982be73 100755
--- a/generators/92updates
+++ b/generators/92updates
@@ -47,7 +47,7 @@ else
echo "# are provided as examples, but you should amend them as 
appropriate" >> $file
echo "# for your mirror of choice." >> $file
echo "#" >> $file
-   echo "# deb http://ftp.debian.org/debian/ ${codename}-updates $dists" 
>> $file
+   echo "# deb http://httpredir.debian.org/debian/ ${codename}-updates 
$dists" >> $file
 fi
 if db_get netcfg/dhcp_options && \
[ "$RET" = "Do not configure the network at this time" ]; then
@@ -72,7 +72,7 @@ fi
 if [ -n "$protocol" ] && [ -n "$host" ]; then
echo "deb-src $protocol://${host}${directory} ${codename}-updates 
$dists" >> $file
 else
-   echo "# deb-src http://ftp.debian.org/debian/ ${codename}-updates 
$dists" >> $file
+   echo "# deb-src http://httpredir.debian.org/debian/ ${codename}-updates 
$dists" >> $file
 fi
 
 exit $CODE
diff --git a/generators/93backports b/generators/93backports
index 1021d5f..11b12ff 100755
--- a/generators/93backports
+++ b/generators/93backports
@@ -47,7 +47,7 @@ else
echo "# are provided as examples, but you should amend them as 
appropriate" >> $file
echo "# for your mirror of choice." >> $file
echo "#" >> $file
-   echo "# deb http://ftp.debian.org/debian/ ${codename}-backports $dists" 
>> $file
+   echo "# deb http://httpredir.debian.org/debian/ ${codename}-backports 
$dists" >> $file
 fi
 if db_get netcfg/dhcp_options && \
[ "$RET" = "Do not configure the network at this time" ]; then
@@ -72,7 +72,7 @@ fi
 if [ -n "$protocol" ] && [ -n "$host" ]; then
echo "deb-src $protocol://${host}${directory} ${codename}-backports 
$dists" >> $file
 else
-   echo "# deb-src http://ftp.debian.org/debian/ ${codename}-backports 
$dists" >> $file
+   echo "# deb-src http://httpredir.debian.org/debian/ 
${codename}-backports $dists" >> $file
 fi
 
 exit $CODE
--- End Message ---
--- Begin Message ---

> Chris Lamb wrote:
> 
> > apt-setup: Please refer to httpredir.debian.org over
> > ftp.debian.org in commented-out examples
> 
> I find httpredir too unreliable these days, so an updated patch
> is attached that uses http://deb.debian.org instead.

This has been fixed in 
https://tracker.debian.org/news/844054/accepted-apt-setup-10127-source-all-i386-into-unstable/

So closing this (forgotten) bug.


Holger


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#902663: marked as done (/etc/ca-certificates/update.d/mono-keystore error message on package remove)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 19:45:34 +
with message-id 
and subject line Bug#902663: fixed in mono 5.18.0.240+dfsg-2
has caused the Debian Bug report #902663,
regarding /etc/ca-certificates/update.d/mono-keystore error message on package 
remove
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.)


-- 
902663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ca-certificates-mono
Version: 4.6.2.7+dfsg-2
Severity: normal

Removing ca-certificates-mono (4.6.2.7+dfsg-2) ...
Processing triggers for ca-certificates (20180409) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...

done.
Updating Mono key store
/etc/ca-certificates/update.d/mono-keystore: 10: /etc/ca-
certificates/update.d/mono-keystore: /usr/bin/cert-sync: not found
Done
done.


This is because when the package is removed, /usr/bin/cert-sync doesn't exist
but the hook script wants to use it.



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

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

Versions of packages ca-certificates-mono depends on:
ii  ca-certificates  20180409
ii  libmono-corlib4.5-cil4.6.2.7+dfsg-2
ii  libmono-security4.0-cil  4.6.2.7+dfsg-2
ii  mono-runtime 4.6.2.7+dfsg-2

ca-certificates-mono recommends no packages.

ca-certificates-mono suggests no packages.

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: mono
Source-Version: 5.18.0.240+dfsg-2

We believe that the bug you reported is fixed in the latest version of
mono, 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.
Jo Shields  (supplier of updated mono package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Jan 2019 13:19:06 -0500
Source: mono
Binary: ca-certificates-mono libmono-2.0-1 libmono-2.0-dev 
libmono-accessibility4.0-cil libmono-btls-interface4.0-cil libmono-cairo4.0-cil 
libmono-cecil-private-cil libmono-cil-dev libmono-codecontracts4.0-cil 
libmono-compilerservices-symbolwriter4.0-cil libmono-corlib4.5-cil 
libmono-cscompmgd0.0-cil libmono-csharp4.0c-cil libmono-custommarshalers4.0-cil 
libmono-data-tds4.0-cil libmono-db2-1.0-cil libmono-debugger-soft4.0a-cil 
libmono-http4.0-cil libmono-i18n-cjk4.0-cil libmono-i18n-mideast4.0-cil 
libmono-i18n-other4.0-cil libmono-i18n-rare4.0-cil libmono-i18n-west4.0-cil 
libmono-i18n4.0-all libmono-i18n4.0-cil libmono-ldap4.0-cil 
libmono-management4.0-cil libmono-messaging-rabbitmq4.0-cil 
libmono-messaging4.0-cil libmono-microsoft-build-engine4.0-cil 
libmono-microsoft-build-framework4.0-cil 
libmono-microsoft-build-tasks-v4.0-4.0-cil 
libmono-microsoft-build-utilities-v4.0-4.0-cil libmono-microsoft-build4.0-cil 
libmono-microsoft-csharp4.0-cil
 libmono-microsoft-visualc10.0-cil libmono-microsoft-web-infrastructure1.0-cil 
libmono-oracle4.0-cil libmono-parallel4.0-cil libmono-peapi4.0a-cil 
libmono-posix4.0-cil libmono-profiler libmono-profiler-dbgsym 
libmono-rabbitmq4.0-cil libmono-relaxng4.0-cil libmono-security4.0-cil 
libmono-sharpzip4.84-cil libmono-simd4.0-cil libmono-smdiagnostics0.0-cil 
libmono-sqlite4.0-cil libmono-system-componentmodel-composition4.0-cil 
libmono-system-componentmodel-dataannotations4.0-cil 
libmono-system-configuration-install4.0-cil libmono-system-configuration4.0-cil 
libmono-system-core4.0-cil libmono-system-data-datasetextensions4.0-cil 
libmono-system-data-entity4.0-cil libmono-system-data-linq4.0-cil 
libmono-system-data-services-client4.0-cil libmono-system-data-services4.0-cil 
libmono-system-data4.0-cil libmono-system-deployment4.0-cil 

Bug#920476: marked as done (security issue: DoS due to changing # of allowed users in root channel)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 20:49:46 +
with message-id 
and subject line Bug#920476: fixed in mumble 1.3.0~git20190125.440b173+dfsg-1
has caused the Debian Bug report #920476,
regarding security issue: DoS due to changing # of allowed users in root channel
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.)


-- 
920476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920476
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mumble
Version: 1.3.0~git20190114.9fcc588+dfsg-1
Severity: serious
Tags: security fixed-upstream pending


A vulnerability has been discovered whereby a remote unauthenticated user
connected to the server can send a crafted packet to change the number of
allowed users in the root channel to 0, thereby disallowing users to connect to
the server and causing a Denial of Service.  All version of mumble-server prior
to the fix in Mumble issue #3586 on 2019-01-25 are affected.

   https://github.com/mumble-voip/mumble/issues/3585

A new upload of mumble is being prepared to fix this issue.

   -- Chris

-- 
Chris Knadle
chris.kna...@coredump.us



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: mumble
Source-Version: 1.3.0~git20190125.440b173+dfsg-1

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

Debian distribution maintenance software
pp.
Christopher Knadle  (supplier of updated mumble 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Jan 2019 03:33:10 +
Source: mumble
Binary: mumble mumble-server
Architecture: source
Version: 1.3.0~git20190125.440b173+dfsg-1
Distribution: unstable
Urgency: high
Maintainer: Christopher Knadle 
Changed-By: Christopher Knadle 
Description:
 mumble - Low latency encrypted VoIP client
 mumble-server - Low latency encrypted VoIP server
Closes: 919453 920237 920476
Changes:
 mumble (1.3.0~git20190125.440b173+dfsg-1) unstable; urgency=high
 .
   [ Helmut Grohne ]
   * debian/patches:
 - Add 60-crossbuild.diff to remove hard coded call to pkg-config
   to allow Mumble to be cross buildable
   Fixes "FTCBFS: builds for the wrong architecture"  (Closes: #919453)
   * debian/rules:
 - Merge qmake call into dh_auto_configure so qmake gets called only once
 .
   [ Christopher Knadle ]
   * New upstream git snapshot from 2019-01-25
 - Fixes "security issue: DoS due to changing # of allowed users in root
   channel"  (Closes: #920476)
   Thanks to "The Zom.bi Community" for finding the bug and fixing it
   upstream.
 - Fixes "lost list of server configurated"  (Closes: #920237)
   Thanks to petrohs  for reporting the bug, and to
   Antoine Beaupré  for discussing the bug upstream
   more in issue #1702 to verify that the prior fix was insufficient
   * debian/copyright:
 - Update directory location for codecs to be under 3rdparty/ rather than
   softlinks
Checksums-Sha1:
 d13653956b8fc31e32dc42145c6d7017ad03fbc7 2435 
mumble_1.3.0~git20190125.440b173+dfsg-1.dsc
 b6056729de1a1e14b80243b58fb41e4d9545ef10 7011554 
mumble_1.3.0~git20190125.440b173+dfsg.orig.tar.gz
 1f5e974c83b58e10f25479de035c13f59bec36ab 38676 
mumble_1.3.0~git20190125.440b173+dfsg-1.debian.tar.xz
 0f843a5307ad3bbb87e62ab167ac22f54ac2800e 5821 
mumble_1.3.0~git20190125.440b173+dfsg-1_source.buildinfo
Checksums-Sha256:
 bc60039d696392f458d35314c8f0bc0b7246e54891430e3272ea0058723745fd 2435 
mumble_1.3.0~git20190125.440b173+dfsg-1.dsc
 3340d7915f42b86c82a175d524d34b7b7f4523c2fe459f80913775f72480c944 7011554 
mumble_1.3.0~git20190125.440b173+dfsg.orig.tar.gz
 66eea06c78c4ae9151deeae27a58618877b94fbae4666f356cc2bcb60ca42f8c 38676 
mumble_1.3.0~git20190125.440b173+dfsg-1.debian.tar.xz
 31b97a8c1436a6627f1a94d097c47ad31e8568753df8081cc2f968bf435baad4 5821 
mumble_1.3.0~git20190125.440b173+dfsg-1_source.buildinfo
Files:
 d2143437b8b8d6cba2a5ab7fbc10bb40 2435 sound optional 
mumble_1.3.0~git20190125.440b173+dfsg-1.dsc
 086cef3df42034b2ff4951ed005cd8f5 7011554 sound optional 

Bug#920237: marked as done ([mumble] lost list of server configurated)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 20:49:46 +
with message-id 
and subject line Bug#920237: fixed in mumble 1.3.0~git20190125.440b173+dfsg-1
has caused the Debian Bug report #920237,
regarding [mumble] lost list of server configurated
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.)


-- 
920237: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920237
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mumble
Version: 1.3.0~git20190114.9fcc588+dfsg-1
Severity: normal

--- Please enter the report below this line. ---
[en] When updating the mumble client, the list of old servers
configurated does not exist, it was lost in the interface. (I found it
in ~/.local/share/data/Mumble/Mumble/.mumble.sqlite)

[es] Al actualizar el cliente mumble, la lista de servidores registrados
ya no existe, se perdió en la interfaz. (Si lo encontré en
~/.local/share/data/Mumble/Mumble/.mumble.sqlite)

--- System information. ---
Architecture:
Kernel: Linux 4.14.0-3-amd64

Debian Release: buster/sid
500 testing ftp.mx.debian.org
500 stable repo.skype.com

--- Package information. ---
Depends (Version) | Installed
-+-===
libasound2 (>= 1.0.16) |
libavahi-client3 (>= 0.6.16) |
libavahi-common3 (>= 0.6.16) |
libavahi-compat-libdnssd1 (>= 0.6.16) |
libc6 (>= 2.27) |
libgcc1 (>= 1:3.0) |
libgl1 |
libglib2.0-0 (>= 2.12.0) |
libopus0 (>= 1.1) |
libprotobuf17 |
libpulse0 (>= 0.99.1) |
libqt5core5a (>= 5.11.0~rc1) |
libqt5dbus5 (>= 5.0.2) |
libqt5gui5 (>= 5.3.0) |
libqt5network5 (>= 5.4.0) |
libqt5sql5 (>= 5.3.0) |
libqt5svg5 (>= 5.6.0~beta) |
libqt5widgets5 (>= 5.11.0~rc1) |
libqt5xml5 (>= 5.0.2) |
libsndfile1 (>= 1.0.20) |
libspeechd2 (>= 0.7.1) |
libspeex1 (>= 1.2~beta3-1) |
libspeexdsp1 (>= 1.2~beta3.2-1) |
libssl1.1 (>= 1.1.0) |
libstdc++6 (>= 5.2) |
libx11-6 (>= 2:1.2.99.901) |
libxi6 (>= 2:1.2.99.4) |
libqt5sql5-sqlite |
lsb-release |


Package's Recommends field is empty.

Suggests (Version) | Installed
-+-===
mumble-server |
speech-dispatcher | 0.8.8-9



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: mumble
Source-Version: 1.3.0~git20190125.440b173+dfsg-1

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

Debian distribution maintenance software
pp.
Christopher Knadle  (supplier of updated mumble 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Jan 2019 03:33:10 +
Source: mumble
Binary: mumble mumble-server
Architecture: source
Version: 1.3.0~git20190125.440b173+dfsg-1
Distribution: unstable
Urgency: high
Maintainer: Christopher Knadle 
Changed-By: Christopher Knadle 
Description:
 mumble - Low latency encrypted VoIP client
 mumble-server - Low latency encrypted VoIP server
Closes: 919453 920237 920476
Changes:
 mumble (1.3.0~git20190125.440b173+dfsg-1) unstable; urgency=high
 .
   [ Helmut Grohne ]
   * debian/patches:
 - Add 60-crossbuild.diff to remove hard coded call to pkg-config
   to allow Mumble to be cross buildable
   Fixes "FTCBFS: builds for the wrong architecture"  (Closes: #919453)
   * debian/rules:
 - Merge qmake call into dh_auto_configure so qmake gets called only once
 .
   [ Christopher Knadle ]
   * New upstream git snapshot from 2019-01-25
 - Fixes "security issue: DoS due to changing # of allowed users in root
   channel"  (Closes: #920476)
   Thanks to "The Zom.bi Community" for finding the bug and fixing it
   upstream.
 - Fixes "lost list of server configurated"  (Closes: #920237)
   Thanks to petrohs  for reporting the bug, and to
   Antoine Beaupré  for discussing the bug upstream
   more in issue #1702 to verify that the prior fix was insufficient
   * debian/copyright:
 - Update directory location for codecs to be under 3rdparty/ rather than
   softlinks
Checksums-Sha1:
 d13653956b8fc31e32dc42145c6d7017ad03fbc7 2435 
mumble_1.3.0~git20190125.440b173+dfsg-1.dsc
 

Bug#919305: marked as done (distcc: [INTL:nl] Dutch translation of debconf messages)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 15:34:19 +
with message-id 
and subject line Bug#919305: fixed in distcc 3.3.2-7
has caused the Debian Bug report #919305,
regarding distcc: [INTL:nl] Dutch translation of debconf messages
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.)


-- 
919305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
 
 
Package: distcc 
Severity: wishlist 
Tags: l10n patch 
 
 
 
Dear Maintainer, 
 
 
Please find attached the updated Dutch translation of distcc debconf
messages. 
It has been submitted for review to the debian-l10n-dutch mailing
list. 
Please add it to your next package revision. 
It should be put as debian/po/nl.po in your package build tree. 
 

-- 
Regards,
Frans Spiesschaert


nl.po.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: distcc
Source-Version: 3.3.2-7

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

Debian distribution maintenance software
pp.
Christian Marillat  (supplier of updated distcc package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Jan 2019 16:23:17 +0100
Source: distcc
Binary: distcc distcc-dbgsym distcc-pump distcc-pump-dbgsym distccmon-gnome 
distccmon-gnome-dbgsym
Architecture: source amd64
Version: 3.3.2-7
Distribution: unstable
Urgency: medium
Maintainer: Christian Marillat 
Changed-By: Christian Marillat 
Description:
 distcc - simple distributed compiler client and server
 distcc-pump - pump mode for distcc a distributed compiler client and server
 distccmon-gnome - GTK+ monitor for distcc a distributed client and server
Closes: 919305 920496
Changes:
 distcc (3.3.2-7) unstable; urgency=medium
 .
   * Update Dutch and french translations of debconf messages
 (CLoses: #919305, #920496)
Checksums-Sha1:
 174c2b7de97f36b9765ad58d4eaec4fde066860b 1954 distcc_3.3.2-7.dsc
 9ffd1fce6441d69d5de15ce8152186aad562d2d3 45488 distcc_3.3.2-7.debian.tar.xz
 59a46028840f0d7a85d5253497609ad1ed8d20af 399248 distcc-dbgsym_3.3.2-7_amd64.deb
 3f26f2a248a9fd4beb07471e976d82bfd46dfbcd 93052 
distcc-pump-dbgsym_3.3.2-7_amd64.deb
 f4a8a9d723795af7107d6a807550fd71d805c70e 151836 distcc-pump_3.3.2-7_amd64.deb
 f9f43ee74065201d2fd09a2fb6100a223326907e 12673 distcc_3.3.2-7_amd64.buildinfo
 dcf79777450dcdacbf707dec25a71011034ea3f7 208048 distcc_3.3.2-7_amd64.deb
 2e17e4093ee8fbef4c794eade0352c6d9ac25d80 77656 
distccmon-gnome-dbgsym_3.3.2-7_amd64.deb
 8a09ba4e93c57014d1a2d73472bc12aa8590ffb6 68764 
distccmon-gnome_3.3.2-7_amd64.deb
Checksums-Sha256:
 e915a3da5f7c7f978b8b7f42c538b0a632935b6d0ba9f754b393259ce4de4001 1954 
distcc_3.3.2-7.dsc
 3f8cea902a577f916725921e707de47a5581c559831cde0177e1b9942f57e95b 45488 
distcc_3.3.2-7.debian.tar.xz
 027224c99a947e145312f4f32c458e88e91ffb333be0f604b815b575e7de0382 399248 
distcc-dbgsym_3.3.2-7_amd64.deb
 73d93a503f9b0d404d9a09847e756298770280ef364877a75de6465e756e4f21 93052 
distcc-pump-dbgsym_3.3.2-7_amd64.deb
 cef3c1dbe68e31d56be223ce0f47fe1630c80f6585e50919b9bd501d45251a9f 151836 
distcc-pump_3.3.2-7_amd64.deb
 4ec87c458dc59e0cfe13aa7acf7cdb26fdbabec266258b6f1e12759e38b04329 12673 
distcc_3.3.2-7_amd64.buildinfo
 0717423a34412c7a655b425d3d969db7fe947a86eed2950bcf46af75084b95c2 208048 
distcc_3.3.2-7_amd64.deb
 6cb2e5b4f827dd207a1caf20371b3cd0a562a333f284e815f2d94fa5ed969823 77656 
distccmon-gnome-dbgsym_3.3.2-7_amd64.deb
 2cda00cd1be22f39a7f8b84c950ab9a44b776bf899af417dc10855433c28380b 68764 
distccmon-gnome_3.3.2-7_amd64.deb
Files:
 4801dd892aa8fa92a487c3bff6d95dac 1954 devel optional distcc_3.3.2-7.dsc
 94b9177aed1b41682a8e18b10c6c 45488 devel optional 
distcc_3.3.2-7.debian.tar.xz
 50144e5e4c771de549a8fe562673230d 399248 debug optional 
distcc-dbgsym_3.3.2-7_amd64.deb
 1843c955bd9a716aa7b21e48bfbe60e5 93052 debug optional 
distcc-pump-dbgsym_3.3.2-7_amd64.deb
 ff0fdf3e5bee7cde790429f0c0e62e4e 151836 devel optional 
distcc-pump_3.3.2-7_amd64.deb
 d1feccf351a5dd22477ecd8b33941f83 12673 devel optional 

Bug#920496: marked as done (distcc: [INTL:fr] French debconf translation update)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 15:34:19 +
with message-id 
and subject line Bug#920496: fixed in distcc 3.3.2-7
has caused the Debian Bug report #920496,
regarding distcc: [INTL:fr] French debconf translation update
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.)


-- 
920496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920496
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: distcc
Version: 3.3.2-5
Severity: wishlist
Tags: patch l10n

Dear Maintainer,

Please find attached the French debconf templates update, proofread by the
debian-l10n-french mailing list contributors.

Best regards,

Quentin Lejard


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

Kernel: Linux 4.9.93-mainline-rev1 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
# Translation of distcc debconf templates to French
# Copyright (C) 2007 Christian Perrier 
# Copyright (C) 2009-2019 Debian French l10n team 

# This file is distributed under the same license as the distcc package.
#
#
# Christian Perrier , 2007, 2008, 2009, 2010.
# Quentin Lejard , 2019.
msgid ""
msgstr ""
"Project-Id-Version: \n"
"Report-Msgid-Bugs-To: dis...@packages.debian.org\n"
"POT-Creation-Date: 2018-12-22 18:41+0100\n"
"PO-Revision-Date: 2019-01-18 12:53+0100\n"
"Last-Translator: Quentin LEJARD \n"
"Language-Team: French \n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Lokalize 2.0\n"
"Plural-Forms: nplurals=2; plural=(n > 1);\n"

#. Type: boolean
#. Description
#: ../distcc.templates:1001
msgid "Start the distcc daemon on startup?"
msgstr "Faut-il lancer le démon distcc au démarrage ?"

#. Type: boolean
#. Description
#: ../distcc.templates:1001
msgid ""
"distcc can be run as a daemon, listening on port 3632 for incoming "
"connections."
msgstr ""
"Distcc peut fonctionner avec un démon qui sera à l'écoute des connexions "
"entrantes sur le port 3632."

#. Type: boolean
#. Description
#: ../distcc.templates:1001
msgid ""
"You have the option of starting the distcc daemon automatically on the "
"computer startup. If in doubt, it's advised not to start it automatically on "
"startup. If you later change your mind, you can run: 'dpkg-reconfigure "
"distcc'."
msgstr ""
"Vous pouvez lancer le démon distcc automatiquement au démarrage du système. "
"Dans le doute, vous devriez vous en abstenir. Si vous souhaitez modifier ce "
"réglage plus tard, vous pourrez utiliser la commande « dpkg-reconfigure "
"distcc »."

#. Type: string
#. Description
#: ../distcc.templates:2001
msgid "Allowed client networks:"
msgstr "Réseaux clients autorisés :"

#. Type: string
#. Description
#: ../distcc.templates:2001
msgid ""
"The distcc daemon implements access control based on the IP address of the "
"client, that is trying to connect. Only the hosts or networks listed here "
"are allowed to connect."
msgstr ""
"Le démon distcc permet un contrôle d'accès basé sur l'adresse IP des clients "
"qui s'y connectent. Veuillez indiquer ici les hôtes ou réseaux qui seront "
"acceptés."

#. Type: string
#. Description
#: ../distcc.templates:2001
#| msgid ""
#| "You can list multiple hosts and/or networks, separated by spaces. Hosts "
#| "are represented by their IP address, networks have to be in CIDR "
#| "notation, f.e. \"192.168.1.0/24\"."
msgid ""
"You can list multiple hosts and/or networks, separated by spaces. Hosts are "
"represented by their IP address, networks have to be in CIDR notation, e.g. "
"\"192.168.1.0/24\"."
msgstr ""
"Vous pouvez indiquer plusieurs hôtes ou des réseaux entiers, séparés par des "
"espaces. Les hôtes sont représentés par leur adresse IP et les réseaux "
"doivent utiliser la notation CIDR, par exemple « 192.168.1.0/24 »."

#. Type: string
#. Description
#: ../distcc.templates:2001
msgid ""
"To change the list at a later point, you can run: 'dpkg-reconfigure distcc'."
msgstr ""
"Si vous souhaitez modifier la liste des réseaux autorisés plus tard, vous "
"pourrez utiliser la commande « dpkg-reconfigure distcc »."

#. Type: string
#. Description
#: ../distcc.templates:3001
msgid "Listen interfaces:"
msgstr "Interfaces d'écoute :"

#. Type: string
#. Description
#: ../distcc.templates:3001
msgid "The distcc daemon can 

Bug#859548: marked as done (pam-ssh-agent-auth: Please migrate to openssl1.1 in buster)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 16:22:26 +
with message-id 
and subject line Bug#859548: fixed in pam-ssh-agent-auth 0.10.3-2
has caused the Debian Bug report #859548,
regarding pam-ssh-agent-auth: 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.)


-- 
859548: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859548
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pam-ssh-agent-auth
Version: 0.10.2-1.1
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/pam-ssh-agent-auth_0.10.2-1.1_amd64-20160529-1504

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

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

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


Kurt
--- End Message ---
--- Begin Message ---
Source: pam-ssh-agent-auth
Source-Version: 0.10.3-2

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

Debian distribution maintenance software
pp.
Balint Reczey  (supplier of updated pam-ssh-agent-auth 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Jan 2019 22:30:04 +0700
Source: pam-ssh-agent-auth
Binary: libpam-ssh-agent-auth
Architecture: source
Version: 0.10.3-2
Distribution: unstable
Urgency: medium
Maintainer: Christian M. Amsüss 
Changed-By: Balint Reczey 
Description:
 libpam-ssh-agent-auth - PAM Authentication via forwarded ssh-agent
Closes: 859548
Changes:
 pam-ssh-agent-auth (0.10.3-2) unstable; urgency=medium
 .
   * Skip OpenSSL header check which was broken with OpenSSL 1.1
   * Build with default OpenSSL (1.1.x) (Closes: #859548)
   * Fix OpenSSL 1.1.1 compatibility with patch picked from FreeBSD via Gentoo
Checksums-Sha1:
 80ae01a59abcdac56b1d53b40f7eb16bcf057c71 1907 pam-ssh-agent-auth_0.10.3-2.dsc
 dd4c6b1d999c0e35cd39d216a07944e42350d7fb 13688 
pam-ssh-agent-auth_0.10.3-2.debian.tar.xz
 ba34dba0154c50438be64a1308fa008deb4dce0b 6345 
pam-ssh-agent-auth_0.10.3-2_source.buildinfo
Checksums-Sha256:
 860198d35988dd4e282bce946a9b1bbcb8cacda6d1a7c6879ee0576719f1037e 1907 
pam-ssh-agent-auth_0.10.3-2.dsc
 38301358644b9c21b0c7d6d99212dfa859167d9b2553d337cbc25f6e14cdbcec 13688 
pam-ssh-agent-auth_0.10.3-2.debian.tar.xz
 f8516ceefde7a44f5de8b2fa3daef39a7fb8ecf4b98917e55ee368fa57fa9c84 6345 
pam-ssh-agent-auth_0.10.3-2_source.buildinfo
Files:
 6f69ad00ac9293db31928fc5afe84198 1907 libs optional 
pam-ssh-agent-auth_0.10.3-2.dsc
 35d396c66c9f8f52c74fc2970fa8470f 13688 libs optional 
pam-ssh-agent-auth_0.10.3-2.debian.tar.xz
 bd9243570009c3dae5ae166a00b9cc0e 6345 libs optional 
pam-ssh-agent-auth_0.10.3-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEI/PvTgXX55rLQUfDg6KBkWslS0UFAlxMgGIACgkQg6KBkWsl
S0VcCQ//YHkN+0WjFeIO/GVXqaRz5BLtKyYE8JOh77p+T5dbXOpP8XhFrRvEbk/m
cRipyGCN2EjbkIpsGIr0xhhtt5tN7X/URAOKwqln4DCZHeF1rsHhDfh9CZLuTYg1
mmo7LSZUByVcO81UKtqBpCFk+8IUaXxHE1TqKgceediggpi7aTMTtw2s3M7S9qAr
HPTZtWRyfrEKCieu4AKsUOptBzjcGn3awkzSBi/KmHkefu9sb0RRpUyhF/Xi4f9g
c+nhBTAvpP+jgH+o88elmQ+hHlSlgRQtyR294U365mNCq/qsW372FaAhHqH4AZvA
3ojwoKo2mWv/Spkyp8yt+EInZABx/NDyuvTaLSEh5loWlXPHo21BwWFoiSdSklQ+
vXEpSMgEYoDDlJWeutyq8T4Cud0W3Y24Jl+MxRf0GwwxrpuO4Xqi6lr4ZlK3VDPX
qWbOHN7VYWIwFIF80DkP7nJAPLhzrjErHH1nkhHt4qqidP3peZ8u3bURxj9enHlD
G+WabD6SAcAI9U3yUU7MKEaHuqlBspPNpWMSgvkGePDXPLn5Vhel/4P6qpsMb0Ac
7PNMHmyGDHLxzC34Zkmf42opnO610BVlirmfzV/zH3PSZcBPoSnPvRkbu0dcQqPs
3A5UIv9uuJt7v369m1Q+Eeqi6v/sTfXH4cwfTuwo8MB/lrTWkOg=
=rhLX
-END PGP SIGNATURE End Message ---

Bug#744863: marked as done (punjabi installation broken (or at least rescue mode))

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 18:03:13 +0100
with message-id <20190126180313.f6719c01a11163a754f54...@mailbox.org>
and subject line Re: debian-installer: punjabi installation broken
has caused the Debian Bug report #727043,
regarding punjabi installation broken (or at least rescue mode)
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.)


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


[16:47] <  h01ger> | there seems to be a problem with punjabi which other 
languages dont show: 
  
https://jenkins.debian.net/view/g-i-installation/job/g-i-installation_debian_sid_daily_rescue_punjabi/
[17:37] < KiBi> it seems to loop on the keyboard options screen here
[17:37] < KiBi> maybe setxkbmap/console-setup failing, and making it loop
[17:37] < KiBi> (no traces in syslog afaict)


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---

Holger Levsen  wrote:
> 
> http://jenkins.debian.net/job/g-i-installation_debian_sid_daily_rescue_punjabi/8/
>  
> shows that there is a problem with the rescue mode in Punjabi and thus very 
> probably also with normal installations.

Since the last build was successful, I'm closing this (5 years old) bug.
(The build artefacts from those days are no longer available, so there is no
way to debug that build problems anyway.)

If new build problems on jenkins occur, feel free to file a new bug.


Holger

-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#727043: marked as done (punjabi installation broken)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 18:03:13 +0100
with message-id <20190126180313.f6719c01a11163a754f54...@mailbox.org>
and subject line Re: debian-installer: punjabi installation broken
has caused the Debian Bug report #727043,
regarding punjabi installation broken
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.)


-- 
727043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=727043
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: debian-installer
version: 20131014
severity: important

Hi,

http://jenkins.debian.net/job/g-i-installation_debian_sid_daily_rescue_punjabi/8/
 shows that there is a problem with the rescue mode in Punjabi and thus very 
probably also with normal installations.

 h01ger: not sure about that particular language, but I know there were 
regression for asian languages. not sure if that's a different or similar bug.  

 
 feel free to file a bug against src:debian-installer for now (along with 
the version I uploaded if you can reproduce it with it) 
  

Build 8 was triggered manually after #7 showed these symtons, and I've now 
triggered #9 as well.


cheers,
Holger


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---

Holger Levsen  wrote:
> 
> http://jenkins.debian.net/job/g-i-installation_debian_sid_daily_rescue_punjabi/8/
>  
> shows that there is a problem with the rescue mode in Punjabi and thus very 
> probably also with normal installations.

Since the last build was successful, I'm closing this (5 years old) bug.
(The build artefacts from those days are no longer available, so there is no
way to debug that build problems anyway.)

If new build problems on jenkins occur, feel free to file a new bug.


Holger

-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#920020: marked as done (javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 19:36:49 +0100
with message-id <8f5eee56-c32c-7295-25a2-c5a4aa7b6...@debian.org>
and subject line closing issues, the change is intentional
has caused the Debian Bug report #920020,
regarding javadoc: The code being documented uses modules but the packages 
defined in … are in the unnamed module
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.)


-- 
920020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920020
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openjdk-11-jdk
Version: 11.0.2+7-1
Severity: grave
Tags: patch
Justification: renders package unusable

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (attach-javadocs) on 
project octopus-rpctunnel: MavenReportException: Error while generating 
Javadoc: 
[ERROR] Exit code: 1 - javadoc: error - The code being documented uses modules 
but the packages defined in https://docs.oracle.com/javase/8/docs/api/ are in 
the unnamed module.

The cause for this is:

https://bugs.openjdk.java.net/browse/JDK-8212233

The fix is (not tested by myself):

http://hg.openjdk.java.net/jdk/jdk/rev/8ce4083fc831
via:
https://bugs.openjdk.java.net/browse/JDK-8217177

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

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages openjdk-11-jdk depends on:
ii  libc62.28-5
ii  openjdk-11-jdk-headless  11.0.2+7-1
ii  openjdk-11-jre   11.0.2+7-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages openjdk-11-jdk recommends:
pn  libxt-dev  

Versions of packages openjdk-11-jdk suggests:
pn  openjdk-11-demo
pn  openjdk-11-source  
pn  visualvm   

-- no debconf information
--- End Message ---
--- Begin Message ---
closing issues, the change is intentional.

see http://hg.openjdk.java.net/jdk-updates/jdk11u/rev/66a53d6047d1--- End Message ---

Bug#919895: marked as done (javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 19:36:49 +0100
with message-id <8f5eee56-c32c-7295-25a2-c5a4aa7b6...@debian.org>
and subject line closing issues, the change is intentional
has caused the Debian Bug report #919895,
regarding javadoc: The code being documented uses modules but the packages 
defined in … are in the unnamed module
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.)


-- 
919895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919895
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openjdk-11-jdk-headless
Version: 11.0.2+7-1
Severity: serious

Dear Java Maintainers:

There are a number of packages failing to build from source due to a
regression in javadoc. As I didn't find a bug for that in the openjdk
packages, I'm filing this report as the "main" bug and will reassign
and merge all the other bugs to this one.

Thanks.
--- End Message ---
--- Begin Message ---
closing issues, the change is intentional.

see http://hg.openjdk.java.net/jdk-updates/jdk11u/rev/66a53d6047d1--- End Message ---

Bug#914886: marked as done (chromium: SafeBrowsing is not working at all (sample included))

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 15:21:07 -0500
with message-id 

and subject line Re: Bug#914886: chromium: SafeBrowsing is not working at all 
(sample included)
has caused the Debian Bug report #914886,
regarding chromium: SafeBrowsing is not working at all (sample included)
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.)


-- 
914886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914886
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 70.0.3538.110-1
Severity: important

I am not completely sure how to handle this issue: it is obviously not present
in Google Chrome, only in Chromium so upstream isssue tracker doesn't seem to be
the best fit. Also I'm not sure how the SafeBrowsing component is maintained in
_Chromium_. If you believe this should be somehow reported upstream please do it
or request me to (with some details as of how and what).

Anyway, Chromium SafeBrowsing seems not to work at all, despite that both
"SafeBrowsing" and "Help improve SB" is on. 

Just go to this URL and see no warnings: https://www[.]xn--bbox-vw5a[.]com/login
(It is a phishing site for bibox.com with TLS domain padlock.)
The URL is detected by both FireFox and Google SafeBrowsing website.

I would say this is a pretty serious problem, considering the aforementioned
example of the phishing site WITH the padlock, where Average Joe have no real
chance to see the URL forgery.



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

Kernel: Linux 4.16.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages chromium depends on:
ii  chromium-common  70.0.3538.110-1
ii  libasound2   1.1.6-1
ii  libatk-bridge2.0-0   2.26.1-1
ii  libatk1.0-0  2.28.1-1
ii  libatomic1   8.2.0-7
ii  libavcodec58 10:4.0.2-dmo1
ii  libavformat5810:4.0.2-dmo1
ii  libavutil56  10:4.0.2-dmo1
ii  libc62.27-5
ii  libcairo-gobject21.16.0-1
ii  libcairo21.16.0-1
ii  libcups2 2.2.8-5
ii  libdbus-1-3  1.12.10-1
ii  libdrm2  2.4.89-1
ii  libevent-2.1-6   2.1.8-stable-4
ii  libexpat12.2.5-3
ii  libflac8 1.3.2-1
ii  libfontconfig1   2.13.1-2
ii  libfreetype6 2.8.1-0.1
ii  libgcc1  1:8.2.0-7
ii  libgdk-pixbuf2.0-0   2.38.0+dfsg-6
ii  libglib2.0-0 2.58.1-2
ii  libgtk-3-0   3.22.30-1
ii  libharfbuzz0b2.1.1-1+b1
ii  libicu63 63.1-4
ii  libjpeg62-turbo  1:1.5.2-2+b1
ii  liblcms2-2   2.9-1
ii  libminizip1  1.1-8+b1
ii  libnspr4 2:4.16-1+b1
ii  libnss3  2:3.34-1
ii  libopenjp2-7 2.3.0-1
ii  libopus0 1.3~beta+20180518-1
ii  libpango-1.0-0   1.42.4-3
ii  libpangocairo-1.0-0  1.42.4-3
ii  libpci3  1:3.5.2-1
ii  libpng16-16  1.6.34-1
ii  libpulse012.0-1
ii  libre2-4 20180301+dfsg-1
ii  libsnappy1v5 1.1.7-1
ii  libstdc++6   8.2.0-7
ii  libvpx5  1.7.0-3
ii  libwebp6 0.6.1-2
ii  libwebpdemux20.6.1-2
ii  libwebpmux3  0.6.1-2
ii  libx11-6 2:1.6.5-1
ii  libx11-xcb1  2:1.6.4-3
ii  libxcb1  1.13-2
ii  libxcomposite1   1:0.4.4-2
ii  libxcursor1  1:1.1.15-1
ii  libxdamage1  1:1.1.4-3
ii  libxext6 2:1.3.3-1+b2
ii  libxfixes3   1:5.0.3-1
ii  libxi6   2:1.7.9-1
ii  libxml2  2.9.4+dfsg1-6.1+b1
ii  libxrandr2   2:1.5.1-1
ii  libxrender1  1:0.9.10-1
ii  libxslt1.1   1.1.29-5
ii  libxss1  1:1.2.2-1+b2
ii  libxtst6 2:1.2.3-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages chromium recommends:
ii  chromium-sandbox  70.0.3538.102-1

Versions of packages chromium suggests:
pn  chromium-driver  
pn  chromium-l10n
pn  chromium-shell   

Versions of packages chromium-common depends on:
ii  x11-utils  7.7+4
ii  xdg-utils  1.1.2-1

Versions of packages chromium-common recommends:
ii  chromium-sandbox 70.0.3538.102-1
ii  dunst [notification-daemon]  1.2.0-2
ii  fonts-liberation 1:1.07.4-8
ii  libgl1-mesa-dri  17.3.1-1

Processed: closing 912204

[Debian Bug Tracking System]

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

> close 912204
Bug #912204 [vim-runtime] Issues on configs.
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#920531: marked as done (libmono-system-native.so missing)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 19:45:34 +
with message-id 
and subject line Bug#920531: fixed in mono 5.18.0.240+dfsg-2
has caused the Debian Bug report #920531,
regarding libmono-system-native.so missing
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.)


-- 
920531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mono-complete
Version: 5.18.0.240-0xamarin1+debian9b1
Severity: important

Dear Maintainer,

Since an update in unstable, I can't run the KSP CKAN software (was working 
correctly few weeks ago). It crashes with the following error:


Unhandled Exception:
System.InvalidOperationException: object_op ---> 
System.BadImageFormatException: Method has no body
  at System.IO.CoreFX.FileSystemWatcher.StartRaisingEvents () [0x00024] in 
:0 
  at System.IO.CoreFX.FileSystemWatcher.StartRaisingEventsIfNotDisposed () 
[0x0001c] in :0 
  at System.IO.CoreFX.FileSystemWatcher.set_EnableRaisingEvents (System.Boolean 
value) [0x0002a] in :0 
  at (wrapper remoting-invoke-with-check) 
System.IO.CoreFX.FileSystemWatcher.set_EnableRaisingEvents(bool)
  at System.IO.CoreFXFileSystemWatcherProxy.m__0 
(System.IO.CoreFX.FileSystemWatcher internal_fsw, System.IO.FileSystemWatcher 
fsw) [0x00048] in :0 
  at System.IO.CoreFXFileSystemWatcherProxy.Operation 
(System.Action`4[T1,T2,T3,T4] map_op, System.Action`2[T1,T2] object_op, 
System.Object handle, System.Action`2[T1,T2] cancel_op) [0x001d3] in 
:0 
   --- End of inner exception stack trace ---
  at System.IO.CoreFXFileSystemWatcherProxy.Operation 
(System.Action`4[T1,T2,T3,T4] map_op, System.Action`2[T1,T2] object_op, 
System.Object handle, System.Action`2[T1,T2] cancel_op) [0x001f8] in 
:0 
  at System.IO.CoreFXFileSystemWatcherProxy.StartDispatching (System.Object 
handle) [0x7] in :0 
  at System.IO.FileSystemWatcher.Start () [0x00024] in 
:0 
  at System.IO.FileSystemWatcher.set_EnableRaisingEvents (System.Boolean value) 
[0x00049] in :0 
  at (wrapper remoting-invoke-with-check) 
System.IO.FileSystemWatcher.set_EnableRaisingEvents(bool)
  at CKAN.NetFileCache..ctor (System.String path) [0x000b6] in 
<2c2371fb3f2949b2a6dfae930758e6ee>:0 
  at CKAN.NetFileCache..ctor (CKAN.KSPManager mgr, System.String path) 
[0x0] in <2c2371fb3f2949b2a6dfae930758e6ee>:0 
  at CKAN.NetModuleCache..ctor (CKAN.KSPManager mgr, System.String path) 
[0x6] in <2c2371fb3f2949b2a6dfae930758e6ee>:0 
  at CKAN.KSPManager.TrySetupCache (System.String path, System.String& 
failureReason) [0x0003d] in <2c2371fb3f2949b2a6dfae930758e6ee>:0 
  at CKAN.KSPManager.LoadInstancesFromRegistry () [0x000ad] in 
<2c2371fb3f2949b2a6dfae930758e6ee>:0 
  at CKAN.KSPManager..ctor (CKAN.IUser user, CKAN.IWin32Registry 
win32_registry) [0x00028] in <2c2371fb3f2949b2a6dfae930758e6ee>:0 
  at CKAN.CmdLine.MainClass.Execute (CKAN.KSPManager manager, 
CKAN.CmdLine.CommonOptions opts, System.String[] args) [0x0015b] in 
<2c2371fb3f2949b2a6dfae930758e6ee>:0 
  at CKAN.CmdLine.MainClass.Main (System.String[] args) [0x00091] in 
<2c2371fb3f2949b2a6dfae930758e6ee>:0 
[ERROR] FATAL UNHANDLED EXCEPTION: System.InvalidOperationException: object_op 
---> System.BadImageFormatException: Method has no body
  at System.IO.CoreFX.FileSystemWatcher.StartRaisingEvents () [0x00024] in 
:0 
  at System.IO.CoreFX.FileSystemWatcher.StartRaisingEventsIfNotDisposed () 
[0x0001c] in :0 
  at System.IO.CoreFX.FileSystemWatcher.set_EnableRaisingEvents (System.Boolean 
value) [0x0002a] in :0 
  at (wrapper remoting-invoke-with-check) 
System.IO.CoreFX.FileSystemWatcher.set_EnableRaisingEvents(bool)
  at System.IO.CoreFXFileSystemWatcherProxy.m__0 
(System.IO.CoreFX.FileSystemWatcher internal_fsw, System.IO.FileSystemWatcher 
fsw) [0x00048] in :0 
  at System.IO.CoreFXFileSystemWatcherProxy.Operation 
(System.Action`4[T1,T2,T3,T4] map_op, System.Action`2[T1,T2] object_op, 
System.Object handle, System.Action`2[T1,T2] cancel_op) [0x001d3] in 
:0 
   --- End of inner exception stack trace ---
  at System.IO.CoreFXFileSystemWatcherProxy.Operation 
(System.Action`4[T1,T2,T3,T4] map_op, System.Action`2[T1,T2] object_op, 
System.Object handle, System.Action`2[T1,T2] cancel_op) [0x001f8] in 
:0 
  at System.IO.CoreFXFileSystemWatcherProxy.StartDispatching (System.Object 
handle) [0x7] in :0 
  at System.IO.FileSystemWatcher.Start () [0x00024] in 
:0 
  at System.IO.FileSystemWatcher.set_EnableRaisingEvents (System.Boolean value) 
[0x00049] in :0 
  at (wrapper remoting-invoke-with-check) 

Bug#913343: marked as done (jclic: please switch to libmariadb-java)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 20:48:12 +
with message-id 
and subject line Bug#913343: fixed in jclic 0.3.2.10-1
has caused the Debian Bug report #913343,
regarding jclic: please switch to libmariadb-java
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.)


-- 
913343: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913343
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jclic
Version: 0.3.2.8-1
Severity: important
Tags: patch

Hello,

we would like to remove libmysql-java from Debian because it is
frequently affected by security vulnerabilities which are not fully
disclosed. This makes it hard to determine the impact of such a flaw.[1]
However we also have libmariadb-java which is a drop-in replacement
and upstream is more transparent about security issues.

Please find attached a patch that make the necessary changes to
the Debian packaging.

Regards,

Markus

[1] https://bugs.debian.org/912916
>From f1c646fd6280c187da8646c5ebe0183692e61fa1 Mon Sep 17 00:00:00 2001
From: Markus Koschany 
Date: Fri, 9 Nov 2018 18:32:31 +0100
Subject: [PATCH] Switch from libmysql-java to libmariadb-java.

---
 debian/changelog |  7 +++
 debian/control   |  2 +-
 debian/patches/mariadb.patch | 82 
 debian/patches/series|  1 +
 4 files changed, 91 insertions(+), 1 deletion(-)
 create mode 100644 debian/patches/mariadb.patch

diff --git a/debian/changelog b/debian/changelog
index ba5cbe7..1cf3a74 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+jclic (0.3.2.8-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Switch from libmysql-java to libmariadb-java.
+
+ -- Markus Koschany   Fri, 09 Nov 2018 18:32:47 +0100
+
 jclic (0.3.2.8-1) unstable; urgency=medium
 
   * New upstream version
diff --git a/debian/control b/debian/control
index 71e381f..ad05b4e 100644
--- a/debian/control
+++ b/debian/control
@@ -10,7 +10,7 @@ Standards-Version: 4.1.3.0
 Package: jclic
 Architecture: all
 Depends: ${misc:Depends}, default-jre | java7-runtime
-Recommends: libmysql-java, firefox
+Recommends: libmariadb-java, firefox
 Suggests: fonts-liberation | ttf-mscorefonts-installer
 Description: Tool for the development & use of multimedia educational 
activities
  JClic is formed by a set of computer applications that are used for
diff --git a/debian/patches/mariadb.patch b/debian/patches/mariadb.patch
new file mode 100644
index 000..982ab35
--- /dev/null
+++ b/debian/patches/mariadb.patch
@@ -0,0 +1,82 @@
+From: Markus Koschany 
+Date: Fri, 9 Nov 2018 18:31:17 +0100
+Subject: mariadb
+
+---
+ dist/linux/man/jclicreports.1| 2 +-
+ dist/reports/jclicReports.properties | 4 ++--
+ extensions/dbconn/config.properties  | 2 +-
+ src/report/jclicReports.properties   | 2 +-
+ src/report/reportServlets/edu/xtec/jclic/jclicReports.properties | 2 +-
+ 5 files changed, 6 insertions(+), 6 deletions(-)
+
+diff --git a/dist/linux/man/jclicreports.1 b/dist/linux/man/jclicreports.1
+index 5f11fcb..e1b876f 100644
+--- a/dist/linux/man/jclicreports.1
 b/dist/linux/man/jclicreports.1
+@@ -106,7 +106,7 @@ for first time.
+ .TP
+ .B dbServer jdbc\:mysql\://localhost/JClicReports
+ .TP
+-.B dbDriver com.mysql.jdbc.Driver
++.B dbDriver org.mariadb.jdbc.Driver
+ .TP
+ .B dbLogin root
+ .TP
+diff --git a/dist/reports/jclicReports.properties 
b/dist/reports/jclicReports.properties
+index 0d3bd84..e7bcd7c 100644
+--- a/dist/reports/jclicReports.properties
 b/dist/reports/jclicReports.properties
+@@ -6,11 +6,11 @@
+ # Name of the JDBC driver
+ #--
+ # Examples:  ODBC: sun.jdbc.odbc.JdbcOdbcDriver
+-#MySQL: com.mysql.jdbc.Driver
++#MySQL: org.mariadb.jdbc.Driver
+ #PointBase: com.pointbase.jdbc.jdbcUniversalDriver
+ #Oracle: oracle.jdbc.driver.OracleDriver
+ #--
+-dbDriver=com.mysql.jdbc.Driver
++dbDriver=org.mariadb.jdbc.Driver
+ 
+ #--
+ # URL of the the database
+diff --git a/extensions/dbconn/config.properties 
b/extensions/dbconn/config.properties
+index 7c30a6c..ed937c3 100644
+--- a/extensions/dbconn/config.properties
 b/extensions/dbconn/config.properties
+@@ -2,7 +2,7 @@
+ #ODBC: sun.jdbc.odbc.JdbcOdbcDriver
+ #PointBase: 

Bug#919453: marked as done (mumble FTCBFS: builds for the wrong architecture)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 20:49:46 +
with message-id 
and subject line Bug#919453: fixed in mumble 1.3.0~git20190125.440b173+dfsg-1
has caused the Debian Bug report #919453,
regarding mumble FTCBFS: builds for the wrong architecture
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.)


-- 
919453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mumble
Version: 1.3.0~git20190114.9fcc588+dfsg-1
Tags: patch
User: helm...@debian.org
Usertags: rebootstrap

mumble fails to cross build from source, because it calls the build
architecture qmake. It actually calls qmake twice: Once via
dh_auto_configure and once directly from debian/rules. The call via
dh_auto_configure uses the right qmake, but the wrong flags. Merging
those calls into one fixes this part. Then mumble hard codes the build
architecture pkg-config in a lot of places. Making those calls
substitutable should be upstreamable and makes mumble cross buildable.
Please consider applying the attached patch.

Helmut
diff --minimal -Nru mumble-1.3.0~git20190114.9fcc588+dfsg/debian/changelog 
mumble-1.3.0~git20190114.9fcc588+dfsg/debian/changelog
--- mumble-1.3.0~git20190114.9fcc588+dfsg/debian/changelog  2019-01-15 
06:53:33.0 +0100
+++ mumble-1.3.0~git20190114.9fcc588+dfsg/debian/changelog  2019-01-16 
06:24:27.0 +0100
@@ -1,3 +1,12 @@
+mumble (1.3.0~git20190114.9fcc588+dfsg-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
++ Call qmake once only. Via dh_auto_configure.
++ cross.patch: Do not hard code pkg-config.
+
+ -- Helmut Grohne   Wed, 16 Jan 2019 06:24:27 +0100
+
 mumble (1.3.0~git20190114.9fcc588+dfsg-1) unstable; urgency=medium
 
   * New upstream git snapshot from 2019-01-14
diff --minimal -Nru 
mumble-1.3.0~git20190114.9fcc588+dfsg/debian/patches/cross.path 
mumble-1.3.0~git20190114.9fcc588+dfsg/debian/patches/cross.path
--- mumble-1.3.0~git20190114.9fcc588+dfsg/debian/patches/cross.path 
1970-01-01 01:00:00.0 +0100
+++ mumble-1.3.0~git20190114.9fcc588+dfsg/debian/patches/cross.path 
2019-01-16 06:24:27.0 +0100
@@ -0,0 +1,148 @@
+--- mumble-1.3.0~git20190114.9fcc588+dfsg.orig/main.pro
 mumble-1.3.0~git20190114.9fcc588+dfsg/main.pro
+@@ -11,7 +11,7 @@
+ SUBDIRS *= src/mumble_proto
+ 
+ !CONFIG(no-client) {
+-  unix:!CONFIG(bundled-speex):system(pkg-config --atleast-version=1.2 
speexdsp):system(pkg-config --atleast-version=1.2 speex) {
++  unix:!CONFIG(bundled-speex):system($$PKG_CONFIG --atleast-version=1.2 
speexdsp):system($$PKG_CONFIG --atleast-version=1.2 speex) {
+ CONFIG *= no-bundled-speex
+   }
+   !CONFIG(no-bundled-speex) {
+@@ -21,7 +21,7 @@
+   CONFIG(sbcelt) {
+ SUBDIRS *= 3rdparty/celt-0.7.0-build 3rdparty/sbcelt-lib-build 
3rdparty/sbcelt-helper-build
+   } else {
+-unix:!CONFIG(bundled-celt):system(pkg-config --atleast-version=0.7.0 
celt) {
++unix:!CONFIG(bundled-celt):system($$PKG_CONFIG --atleast-version=0.7.0 
celt) {
+   CONFIG *= no-bundled-celt
+ }
+ !CONFIG(no-bundled-celt) {
+@@ -100,7 +100,7 @@
+ SUBDIRS *= src/murmur/murmur_ice
+   }
+   CONFIG(grpc) {
+-!system(pkg-config --atleast-version=3 protobuf) {
++!system($$PKG_CONFIG --atleast-version=3 protobuf) {
+   error(grpc requires protobuf>=3)
+ }
+ SUBDIRS *= src/murmur_grpcwrapper_protoc_plugin
+--- mumble-1.3.0~git20190114.9fcc588+dfsg.orig/qmake/compiler.pri
 mumble-1.3.0~git20190114.9fcc588+dfsg/qmake/compiler.pri
+@@ -8,6 +8,7 @@
+ include(buildenv.pri)
+ include(builddir.pri)
+ include(cplusplus.pri)
++include(pkgconfig.pri)
+ 
+ CONFIG *= warn_on
+ 
+--- mumble-1.3.0~git20190114.9fcc588+dfsg.orig/qmake/pkgconfig.pri
 mumble-1.3.0~git20190114.9fcc588+dfsg/qmake/pkgconfig.pri
+@@ -3,6 +3,8 @@
+ # that can be found in the LICENSE file at the root of the
+ # Mumble source tree or at .
+ 
++PKG_CONFIG = $$pkgConfigExecutable()
++
+ # must_pkgconfig(pkg)
+ #
+ # This function checks if the passed-in package
+@@ -17,7 +19,7 @@
+ #
+ defineTest(must_pkgconfig) {
+   pkg = $$1
+-  system(pkg-config --exists $$pkg) {
++  system($$PKG_CONFIG --exists $$pkg) {
+   PKGCONFIG *= $$pkg
+   export(PKGCONFIG)
+   } else {
+--- mumble-1.3.0~git20190114.9fcc588+dfsg.orig/src/mumble.pri
 mumble-1.3.0~git20190114.9fcc588+dfsg/src/mumble.pri
+@@ -123,7 +123,7 @@
+ 
+ unix {
+   CONFIG(static) {
+-  PKG_CONFIG = pkg-config --static
++  

Bug#920308: marked as done (compiz-core: compiz-decorator test is inverted, thus can't supply a config)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 20:45:10 +
with message-id 
and subject line Bug#920308: fixed in compiz 2:0.8.16.1-5
has caused the Debian Bug report #920308,
regarding compiz-core: compiz-decorator test is inverted, thus can't supply a 
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.)


-- 
920308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920308
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: compiz-core
Version: 2:0.8.16.1-4
Severity: normal
Tags: patch

Dear Maintainer,

The script /usr/bin/compiz-decorator has two clearly erroneous tests
near the beginning. XDG_CONFIG_DIRS and XDG_CONFIG_HOME are both checked
for emptiness, and if they are *not* empty, they are assigned values.
Included is a patch to fix this; please apply.


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

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

Versions of packages compiz-core depends on:
ii  libc6 2.28-5
ii  libgl11.1.0-1
ii  libice6   2:1.0.9-2
ii  libsm62:1.2.2-1+b3
ii  libstartup-notification0  0.12-6
ii  libx11-6  2:1.6.7-1
ii  libxcomposite11:0.4.4-2
ii  libxcursor1   1:1.1.15-2
ii  libxdamage1   1:1.1.4-3
ii  libxext6  2:1.3.3-1+b2
ii  libxfixes31:5.0.3-1
ii  libxi62:1.7.9-1
ii  libxinerama1  2:1.1.4-1
ii  libxml2   2.9.4+dfsg1-7+b3
ii  libxrandr22:1.5.1-1
ii  mesa-utils8.4.0-1+b1

Versions of packages compiz-core recommends:
ii  compiz-plugins   2:0.8.16.1-4
ii  compiz-plugins-main  2:0.8.16-2+b1

Versions of packages compiz-core suggests:
ii  nvidia-driver  410.93-1

-- no debconf information
diff -ur compiz-0.8.16.1.orig/plugins/compiz-decorator 
compiz-0.8.16.1/plugins/compiz-decorator
--- compiz-0.8.16.1.orig/plugins/compiz-decorator   2019-01-23 
17:45:23.311674363 -0500
+++ compiz-0.8.16.1/plugins/compiz-decorator2019-01-23 17:45:38.831472785 
-0500
@@ -27,10 +27,10 @@
 }
 
 # Create env variables if empty.
-if [ ! -z "$XDG_CONFIG_DIRS" ]; then
+if [ -z "$XDG_CONFIG_DIRS" ]; then
 XDG_CONFIG_DIRS="/etc/xdg"
 fi
-if [ ! -z "$XDG_CONFIG_HOME" ]; then
+if [ -z "$XDG_CONFIG_HOME" ]; then
 XDG_CONFIG_HOME="$HOME/.config"
 fi
 
--- End Message ---
--- Begin Message ---
Source: compiz
Source-Version: 2:0.8.16.1-5

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated compiz package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Jan 2019 21:01:22 +0100
Source: compiz
Binary: compiz compiz-core compiz-core-dbgsym compiz-dev compiz-gnome 
compiz-gnome-dbgsym compiz-mate compiz-mate-dbgsym compiz-plugins 
compiz-plugins-dbgsym compiz-plugins-default libdecoration0 
libdecoration0-dbgsym libdecoration0-dev
Architecture: source
Version: 2:0.8.16.1-5
Distribution: unstable
Urgency: medium
Maintainer: Hypra Team 
Changed-By: Samuel Thibault 
Description:
 compiz - OpenGL window and compositing manager
 compiz-core - OpenGL window and compositing manager
 compiz-dev - OpenGL window and compositing manager - development files
 compiz-gnome - OpenGL window and compositing manager - Gtk window decorator
 compiz-mate - OpenGL window and compositing manager - MATE window decorator
 compiz-plugins - OpenGL window and compositing manager - plugins
 compiz-plugins-default - transitional dummy package
 libdecoration0 - Compiz window decoration library
 libdecoration0-dev - Compiz window decoration library - development files
Closes: 920308
Changes:
 compiz (2:0.8.16.1-5) 

Bug#916148: marked as done (lpr FTBFS with glibc 2.28)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 21:20:40 +
with message-id 
and subject line Bug#916148: fixed in lpr 1:2008.05.17.3
has caused the Debian Bug report #916148,
regarding lpr FTBFS with glibc 2.28
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.)


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

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

...
lpr.c: In function 'main':
lpr.c:336:32: warning: implicit declaration of function 'makedev' 
[-Wimplicit-function-declaration]
(unsigned long long int)makedev( major(statb.st_dev), 
minor(statb.st_dev)), (int)statb.st_ino);
^~~
lpr.c:336:41: warning: implicit declaration of function 'major' 
[-Wimplicit-function-declaration]
(unsigned long long int)makedev( major(statb.st_dev), 
minor(statb.st_dev)), (int)statb.st_ino);
 ^
lpr.c:336:62: warning: implicit declaration of function 'minor'; did you mean 
'mknod'? [-Wimplicit-function-declaration]
(unsigned long long int)makedev( major(statb.st_dev), 
minor(statb.st_dev)), (int)statb.st_ino);
  ^
...
cc -o lpr lpr.o ../common_source/startdaemon.o ../common_source/common.o 
../common_source/common_vars.o ../common_source/getcap.o 
../common_source/strlcpy.o ../common_source/strlcat.o
/usr/bin/ld: lpr.o: in function `main':
/build/1st/lpr-2008.05.17.2/lpr/lpr.c:336: undefined reference to `minor'
/usr/bin/ld: /build/1st/lpr-2008.05.17.2/lpr/lpr.c:336: undefined reference to 
`major'
/usr/bin/ld: /build/1st/lpr-2008.05.17.2/lpr/lpr.c:336: undefined reference to 
`makedev'
collect2: error: ld returned 1 exit status
make[2]: *** [../Makefile.in:8: lpr] Error 1
--- End Message ---
--- Begin Message ---
Source: lpr
Source-Version: 1:2008.05.17.3

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 11 Jan 2019 22:06:54 +0200
Source: lpr
Binary: lpr
Architecture: source
Version: 1:2008.05.17.3
Distribution: unstable
Urgency: medium
Maintainer: Adam Majer 
Changed-By: Adrian Bunk 
Description:
 lpr- BSD lpr/lpd line printer spooling system
Closes: 601355 916148
Changes:
 lpr (1:2008.05.17.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS with glibc 2.28. (Closes: #916148)
   * Sugggest ghostscript instead of gs. (Closes: #601355)
   * Build with -g to get non-empty -dbgsym.
Checksums-Sha1:
 31e29a20123878b939da83522da8eb80d39e4d71 1506 lpr_2008.05.17.3.dsc
 aa67a60d2e6a2d411d0c9979d8dea0fb13393128 105064 lpr_2008.05.17.3.tar.gz
Checksums-Sha256:
 cf33eb7bb6cf7ec5088e980b45222d8c8ad7d06debbe7b39296198cd6bab34b5 1506 
lpr_2008.05.17.3.dsc
 ce9cf62e6783d528a71a0d61be8eb09b66b20d092139f96e38dec849887deba6 105064 
lpr_2008.05.17.3.tar.gz
Files:
 8c1aeb42123f457ab7db3f8761658e99 1506 net optional lpr_2008.05.17.3.dsc
 2c7428ee810859c5b0cfc556d1b59f00 105064 net optional lpr_2008.05.17.3.tar.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlw4+GAACgkQiNJCh6LY
mLGzgxAAnA24HEqSkwQS5EGwXYljkLUJkQWBaZZibynz9ccIwIVLklfTcZfn10kA
Oy3Rv/JO0//7dlJ8NYjgN5yuF1+UbNE4Sx34ITH9880lXPnb6YVJdC/2XaCOTeSg
MVMZw2RC3s6yWbQenduQSfgcYNQt4KWhaOunwUY42dvBf2PMAburgiYFeqBf63T1
ctfexN/vBRHfikXcSmc8lgLPoxKFmppqHyZgWTnkp43/qDTr/IVoU2otO19yQ5h3
ZqvSlTvdi44Z+B1LY4JOnSg+vxODASDh1RaYeOjI4YBdcbaTtTad5uWTkvNQjzKF
6dNN88GUYBeBWlpqbqJXb+Fe1tt09aqejTcJUQmOI+ieT05A94aQ+E9EXm7Xph0p
iFoISmFXYBLj5f1TQLBMfyHEt9JiwNQxygVl7bw8fK5N2S5V6PV2nBrHfWattSvV
gAG/945FIIM9tn1GIsn6b17pg0pe1LapYuG+awBJw9S6egZU8ua5MYeg7pZI8wdx
fo5qqX+hNdhR5FWVmW1pOlh42zyvpmaQDY16MCvR3fBYCSsVot1qjWEzIenOVQws
1k9NFrXwQKlXnF8X57abYtwile4O0sVNDluz3i0xCGVwiBKOLfrGXcJUeC58tblE

Bug#919331: marked as done (wine: /run/user exists, but not /run/user/$uuid)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 21:22:19 +
with message-id 
and subject line Bug#918666: fixed in wine 4.0-1
has caused the Debian Bug report #918666,
regarding wine: /run/user exists, but not /run/user/$uuid
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.)


-- 
918666: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918666
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wine
Version: 4.0~rc4-2
Severity: normal

I checked the patch (in bug 904041, not what was actually checked in to the 
source code)
and I see that it only checks for /run/user, which does exist on my system.

I do have pam-systemd, but not XDG_RUNTIME_DIR, as was requested in the other 
bug.

I manually created /run/user/1000 and everything works.

For me, this is a highly customized situation (PHP via a web page runs wine and 
uses stdout
from the windows executable to return results to PHP) so I don't mind a hacky 
solution at all.

Am I right in thinking I could set XDG_RUNTIME_DIR to a safe temporary 
directory somewhere
and that would be fine?

It seems the real fix would be to check for the actual $UUID directory, rather 
than just /run/user.


-- Package-specific info:
/usr/bin/wine points to /usr/bin/wine-stable.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

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

Versions of packages wine depends on:
ii  wine32  4.0~rc4-2

wine recommends no packages.

Versions of packages wine suggests:
pn  dosbox   
pn  playonlinux  
pn  q4wine   
pn  winbind  
pn  wine-binfmt  
pn  winetricks   

Versions of packages wine is related to:
pn  fonts-wine  
ii  wine4.0~rc4-2
ii  wine32  4.0~rc4-2
pn  wine64  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: wine
Source-Version: 4.0-1

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated wine package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Jan 2019 19:21:02 +
Source: wine
Binary: wine wine32 wine64 wine32-preloader wine64-preloader wine32-tools 
wine64-tools libwine libwine-dev wine-binfmt fonts-wine
Architecture: source
Version: 4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party 
Changed-By: Michael Gilbert 
Description:
 fonts-wine - Windows API implementation - fonts
 libwine- Windows API implementation - library
 libwine-dev - Windows API implementation - development files
 wine   - Windows API implementation - standard suite
 wine-binfmt - Register Wine as the interpreter for Windows executables
 wine32 - Windows API implementation - 32-bit binary loader
 wine32-preloader - Windows API implementation - prelinked 32-bit binary loader
 wine32-tools - Windows API implementation - 32-bit developer tools
 wine64 - Windows API implementation - 64-bit binary loader
 wine64-preloader - Windows API implementation - prelinked 64-bit binary loader
 wine64-tools - Windows API implementation - 64-bit developer tools
Closes: 918666
Changes:
 wine (4.0-1) unstable; urgency=medium
 .
   * New upstream release 4.0, released Jan 22, 2019.
   * Make sure /run/user/$uid exists before choosing to use it as the location
 for wine's temporary directory (closes: #918666).
Checksums-Sha1:
 66de32f0a7c414d162ca033af8d89ef28b77a4f5 4553 wine_4.0-1.dsc
 80196e577484cf9d6e5104d6a40290a596eed0c9 19888584 wine_4.0.orig.tar.xz
 79518e6c4ed0e538fd778f3256fedef16bc52e52 192476 wine_4.0-1.debian.tar.xz
 494cb426780b4c7a63aee718c628422c2a89107d 19156 wine_4.0-1_source.buildinfo
Checksums-Sha256:
 c85fc6de5f6dedf72e6a71befe28cea0c2a8a5b1b205c701452b569b44e048aa 4553 
wine_4.0-1.dsc
 

Bug#918666: marked as done (wine hardcodes /run/user/$UID directory)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 21:22:19 +
with message-id 
and subject line Bug#918666: fixed in wine 4.0-1
has caused the Debian Bug report #918666,
regarding wine hardcodes /run/user/$UID directory
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.)


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

wine hardcodes the use of /run/user/$UID/wine if it can determine
$UID (if getuid() exists) as the place to store server information.

It's not clear to me who is responsible for creating those directories,
but I'm not sure we can rely on them being available, so wine should
fallback to /tmp if /run/user/$UID does not exist, I guess.

In fact, it should be using $XDG_RUNTIME_DIR, not
hardcoding /run/user/$UID.

(this surfaced in Ubuntu autopkgtest for gpgv-win32).

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

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

-- 
debian developer - deb.li/jak | jak-linux.org - free software dev
ubuntu core developer  i speak de, en
--- End Message ---
--- Begin Message ---
Source: wine
Source-Version: 4.0-1

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated wine package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Jan 2019 19:21:02 +
Source: wine
Binary: wine wine32 wine64 wine32-preloader wine64-preloader wine32-tools 
wine64-tools libwine libwine-dev wine-binfmt fonts-wine
Architecture: source
Version: 4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Wine Party 
Changed-By: Michael Gilbert 
Description:
 fonts-wine - Windows API implementation - fonts
 libwine- Windows API implementation - library
 libwine-dev - Windows API implementation - development files
 wine   - Windows API implementation - standard suite
 wine-binfmt - Register Wine as the interpreter for Windows executables
 wine32 - Windows API implementation - 32-bit binary loader
 wine32-preloader - Windows API implementation - prelinked 32-bit binary loader
 wine32-tools - Windows API implementation - 32-bit developer tools
 wine64 - Windows API implementation - 64-bit binary loader
 wine64-preloader - Windows API implementation - prelinked 64-bit binary loader
 wine64-tools - Windows API implementation - 64-bit developer tools
Closes: 918666
Changes:
 wine (4.0-1) unstable; urgency=medium
 .
   * New upstream release 4.0, released Jan 22, 2019.
   * Make sure /run/user/$uid exists before choosing to use it as the location
 for wine's temporary directory (closes: #918666).
Checksums-Sha1:
 66de32f0a7c414d162ca033af8d89ef28b77a4f5 4553 wine_4.0-1.dsc
 80196e577484cf9d6e5104d6a40290a596eed0c9 19888584 wine_4.0.orig.tar.xz
 79518e6c4ed0e538fd778f3256fedef16bc52e52 192476 wine_4.0-1.debian.tar.xz
 494cb426780b4c7a63aee718c628422c2a89107d 19156 wine_4.0-1_source.buildinfo
Checksums-Sha256:
 c85fc6de5f6dedf72e6a71befe28cea0c2a8a5b1b205c701452b569b44e048aa 4553 
wine_4.0-1.dsc
 decaac4ecd5160b4bf79385a790dbb72e3650214f2e3023429423264ca1ca2c9 19888584 
wine_4.0.orig.tar.xz
 26df7de501ce54ee7641b1dac772b3d7e4a295e9967abb76dc2f4cc55bb13339 192476 
wine_4.0-1.debian.tar.xz
 3873d67c18d5278c6d74b9dea5f4de36345055e530931b4355da5fc744325933 19156 
wine_4.0-1_source.buildinfo
Files:
 782c118b00bf0f8457efed41aad20438 4553 otherosfs optional wine_4.0-1.dsc
 25ab35ae601b79ff15d09b67805677d4 19888584 otherosfs optional 
wine_4.0.orig.tar.xz
 2e6e758aa023321880247cc23d99bfe6 192476 otherosfs optional 
wine_4.0-1.debian.tar.xz
 

Bug#601355: marked as done (lpr: Suggests obsolete package gs)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 21:20:40 +
with message-id 
and subject line Bug#601355: fixed in lpr 1:2008.05.17.3
has caused the Debian Bug report #601355,
regarding lpr: Suggests obsolete package gs
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.)


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


Package gs is pure virtual, please update to ghostscript or ghostscript-x

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

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_DK.UTF-8, LC_CTYPE=en_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash


--- End Message ---
--- Begin Message ---
Source: lpr
Source-Version: 1:2008.05.17.3

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 11 Jan 2019 22:06:54 +0200
Source: lpr
Binary: lpr
Architecture: source
Version: 1:2008.05.17.3
Distribution: unstable
Urgency: medium
Maintainer: Adam Majer 
Changed-By: Adrian Bunk 
Description:
 lpr- BSD lpr/lpd line printer spooling system
Closes: 601355 916148
Changes:
 lpr (1:2008.05.17.3) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix FTBFS with glibc 2.28. (Closes: #916148)
   * Sugggest ghostscript instead of gs. (Closes: #601355)
   * Build with -g to get non-empty -dbgsym.
Checksums-Sha1:
 31e29a20123878b939da83522da8eb80d39e4d71 1506 lpr_2008.05.17.3.dsc
 aa67a60d2e6a2d411d0c9979d8dea0fb13393128 105064 lpr_2008.05.17.3.tar.gz
Checksums-Sha256:
 cf33eb7bb6cf7ec5088e980b45222d8c8ad7d06debbe7b39296198cd6bab34b5 1506 
lpr_2008.05.17.3.dsc
 ce9cf62e6783d528a71a0d61be8eb09b66b20d092139f96e38dec849887deba6 105064 
lpr_2008.05.17.3.tar.gz
Files:
 8c1aeb42123f457ab7db3f8761658e99 1506 net optional lpr_2008.05.17.3.dsc
 2c7428ee810859c5b0cfc556d1b59f00 105064 net optional lpr_2008.05.17.3.tar.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlw4+GAACgkQiNJCh6LY
mLGzgxAAnA24HEqSkwQS5EGwXYljkLUJkQWBaZZibynz9ccIwIVLklfTcZfn10kA
Oy3Rv/JO0//7dlJ8NYjgN5yuF1+UbNE4Sx34ITH9880lXPnb6YVJdC/2XaCOTeSg
MVMZw2RC3s6yWbQenduQSfgcYNQt4KWhaOunwUY42dvBf2PMAburgiYFeqBf63T1
ctfexN/vBRHfikXcSmc8lgLPoxKFmppqHyZgWTnkp43/qDTr/IVoU2otO19yQ5h3
ZqvSlTvdi44Z+B1LY4JOnSg+vxODASDh1RaYeOjI4YBdcbaTtTad5uWTkvNQjzKF
6dNN88GUYBeBWlpqbqJXb+Fe1tt09aqejTcJUQmOI+ieT05A94aQ+E9EXm7Xph0p
iFoISmFXYBLj5f1TQLBMfyHEt9JiwNQxygVl7bw8fK5N2S5V6PV2nBrHfWattSvV
gAG/945FIIM9tn1GIsn6b17pg0pe1LapYuG+awBJw9S6egZU8ua5MYeg7pZI8wdx
fo5qqX+hNdhR5FWVmW1pOlh42zyvpmaQDY16MCvR3fBYCSsVot1qjWEzIenOVQws
1k9NFrXwQKlXnF8X57abYtwile4O0sVNDluz3i0xCGVwiBKOLfrGXcJUeC58tblE
Mlt5rNHZ5YomgWhtl13/j8akU739xz6VERJUOOQR1EOQ9qyO73M=
=qVtT
-END PGP SIGNATURE End Message ---

Bug#872674: marked as done (puredata-import FTBFS with puredata 0.48.0-1)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 22:24:49 +
with message-id 
and subject line Bug#872674: fixed in puredata-import 1.3-5
has caused the Debian Bug report #872674,
regarding puredata-import FTBFS with puredata 0.48.0-1
to be marked as done.

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

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


-- 
872674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: puredata-import
Version: 1.3-3
Severity: serious
Tags: buster sid

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

...
make -j1
make[1]: Entering directory '/build/1st/puredata-import-1.3'
cc -I"/usr/include/pd" -Wall -W -g -DPD -DVERSION='"1.3"' -fPIC -O6 
-funroll-loops -fomit-frame-pointer -o "import.o" -c "import.c"
In file included from import.c:2:0:
s_stuff.h:48:12: error: conflicting types for 'sys_hostfontsize'
 EXTERN int sys_hostfontsize(int fontsize);
^~~~
In file included from import.c:1:0:
/usr/include/pd/m_pd.h:436:12: note: previous declaration of 'sys_hostfontsize' 
was here
 EXTERN int sys_hostfontsize(int fontsize, int zoom);
^~~~
import.c: In function 'import_new':
import.c:112:12: warning: unused variable 'currentdir' [-Wunused-variable]
  t_symbol *currentdir;
^~
import.c:109:35: warning: unused parameter 's' [-Wunused-parameter]
 static void *import_new(t_symbol *s, int argc, t_atom *argv)
   ^
import.c: In function 'import_free':
import.c:138:35: warning: unused parameter 'x' [-Wunused-parameter]
 static void import_free(t_import *x)
   ^
Makefile:191: recipe for target 'import.o' failed
make[1]: *** [import.o] Error 1
--- End Message ---
--- Begin Message ---
Source: puredata-import
Source-Version: 1.3-5

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

Debian distribution maintenance software
pp.
Hans-Christoph Steiner  (supplier of updated puredata-import 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Jan 2019 21:55:07 +
Source: puredata-import
Binary: puredata-import
Architecture: source amd64
Version: 1.3-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: Hans-Christoph Steiner 
Description:
 puredata-import - Pd object for loading libraries within a patch
Closes: 872674
Changes:
 puredata-import (1.3-5) unstable; urgency=medium
 .
   * bumped Standards-Version to 3.9.3
   * updated to copyright-format/1.0
   * removed deprecated DM-Upload-Allowed
   * added fallback to 'puredata' package for Deps to support easy backporting
   * use https URL for debian/copyright
   * purge obsolete patch that breaks the build (Closes: #872674)
Checksums-Sha1:
 77de12aed5d4300438a06673b92f88deb554274a 1703 puredata-import_1.3-5.dsc
 2d7be0c7b7e04bac1990fe4d332878d08a3d51e9 3928 
puredata-import_1.3-5.debian.tar.xz
 4397c5f788f7675442c43f4624ce8ed518d6f380 5546 
puredata-import_1.3-5_amd64.buildinfo
 380c1f046887948d4430d726f74dda6bf17f965f 6792 puredata-import_1.3-5_amd64.deb
Checksums-Sha256:
 efc71210bd1610235b9ddfd4ffaade73ed58b61b968b3726326607577e64a917 1703 
puredata-import_1.3-5.dsc
 7f194dde538b2abb656c1d6e4b6ed2698189ad17e8d69a83cd56d76c91785448 3928 
puredata-import_1.3-5.debian.tar.xz
 229994045cbb2915338cb223166f371b29ac0c53d190b060fbbee01dcc328234 5546 
puredata-import_1.3-5_amd64.buildinfo
 dd1fa9cc46d03617f3c521e343b6bfbec9efcc3d27e47bfb8cd819ebad227cb4 6792 
puredata-import_1.3-5_amd64.deb
Files:
 098b365208b8056721fdd219e8d33b24 1703 sound optional puredata-import_1.3-5.dsc
 e5981d7ef53eb3dd43d7b337f376c0ee 3928 sound optional 
puredata-import_1.3-5.debian.tar.xz
 7483884b45823878c8704b79d0bc1b13 5546 sound optional 
puredata-import_1.3-5_amd64.buildinfo
 ef2de0224408874e0a3a7b5457664054 6792 sound optional 
puredata-import_1.3-5_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPG for Android - https://guardianproject.info/code/gnupg/

Bug#872674: marked as done (puredata-import FTBFS with puredata 0.48.0-1)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 22:24:42 +
with message-id 
and subject line Bug#872674: fixed in puredata-import 1.3-4
has caused the Debian Bug report #872674,
regarding puredata-import FTBFS with puredata 0.48.0-1
to be marked as done.

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

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


-- 
872674: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872674
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: puredata-import
Version: 1.3-3
Severity: serious
Tags: buster sid

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

...
make -j1
make[1]: Entering directory '/build/1st/puredata-import-1.3'
cc -I"/usr/include/pd" -Wall -W -g -DPD -DVERSION='"1.3"' -fPIC -O6 
-funroll-loops -fomit-frame-pointer -o "import.o" -c "import.c"
In file included from import.c:2:0:
s_stuff.h:48:12: error: conflicting types for 'sys_hostfontsize'
 EXTERN int sys_hostfontsize(int fontsize);
^~~~
In file included from import.c:1:0:
/usr/include/pd/m_pd.h:436:12: note: previous declaration of 'sys_hostfontsize' 
was here
 EXTERN int sys_hostfontsize(int fontsize, int zoom);
^~~~
import.c: In function 'import_new':
import.c:112:12: warning: unused variable 'currentdir' [-Wunused-variable]
  t_symbol *currentdir;
^~
import.c:109:35: warning: unused parameter 's' [-Wunused-parameter]
 static void *import_new(t_symbol *s, int argc, t_atom *argv)
   ^
import.c: In function 'import_free':
import.c:138:35: warning: unused parameter 'x' [-Wunused-parameter]
 static void import_free(t_import *x)
   ^
Makefile:191: recipe for target 'import.o' failed
make[1]: *** [import.o] Error 1
--- End Message ---
--- Begin Message ---
Source: puredata-import
Source-Version: 1.3-4

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

Debian distribution maintenance software
pp.
Hans-Christoph Steiner  (supplier of updated puredata-import 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 26 Jan 2019 21:55:07 +
Source: puredata-import
Binary: puredata-import
Architecture: source amd64
Version: 1.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 

Changed-By: Hans-Christoph Steiner 
Description:
 puredata-import - Pd object for loading libraries within a patch
Closes: 872674
Changes:
 puredata-import (1.3-4) unstable; urgency=medium
 .
   * bumped Standards-Version to 3.9.3
   * updated to copyright-format/1.0
   * removed deprecated DM-Upload-Allowed
   * added fallback to 'puredata' package for Deps to support easy backporting
   * use https URL for debian/copyright
   * purge obsolete patch that breaks the build (Closes: #872674)
Checksums-Sha1:
 f8dce9914259b6e3990252af455de38459626bd8 1719 puredata-import_1.3-4.dsc
 c7b657326c294db22210ceb38492ba99f62b9ca7 3940 
puredata-import_1.3-4.debian.tar.xz
 ebf70f01ea8f5ae85bb65cac8605fc7a64668eb0 5546 
puredata-import_1.3-4_amd64.buildinfo
 a8695b9c93acd5290ff1ee8d54c8c26da3853dfc 6804 puredata-import_1.3-4_amd64.deb
Checksums-Sha256:
 f6398f87d6ac5e885f959e5461fcdbc3352e1bb3286107ed8d7f3ed9b4d2359a 1719 
puredata-import_1.3-4.dsc
 1c7708a73e218a0752304bb37c3e55695fbde78082353ac4726327d293690fba 3940 
puredata-import_1.3-4.debian.tar.xz
 e7229aaf6abd554485995adbd5585808b9deadfd9cf2ece8dea3364e56e12f95 5546 
puredata-import_1.3-4_amd64.buildinfo
 e64d7f3535ac2b05ba0176f731765cede5c55da3faf9f92be9113509fd36cdf8 6804 
puredata-import_1.3-4_amd64.deb
Files:
 7303147daf109fd2c5b4b891065445e4 1719 sound optional puredata-import_1.3-4.dsc
 01612a33253c82945338b78aca3ea002 3940 sound optional 
puredata-import_1.3-4.debian.tar.xz
 c486c04fa990c51ac0be135620f67029 5546 sound optional 
puredata-import_1.3-4_amd64.buildinfo
 14e17f0b769c1329023b7055ac75151e 6804 sound optional 
puredata-import_1.3-4_amd64.deb

-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: GPG for Android - 

Bug#919273: marked as done (libblis2: BLAS alternative is broken)

[Debian Bug Tracking System]

Your message dated Sun, 27 Jan 2019 06:34:13 +
with message-id 
and subject line Bug#919273: fixed in blis 0.5.1-7
has caused the Debian Bug report #919273,
regarding libblis2: BLAS alternative is broken
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.)


-- 
919273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919273
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libblis2
Version: 0.5.1-1
Severity: important

It doesn't work just to link libblis to libblas as a BLAS alternative
because the soname is wrong.  [The openblas package gets it right,
though in a heavyweight way as far as I remember.  The Fedora blis
packaging uses trivial shims
.]

-- System Information:
Debian Release: 9.6
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable'), 
(50, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8), LANGUAGE=en_GB:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages libblis2 depends on:
ii  libblis2-openmp  0.5.1-1

libblis2 recommends no packages.

libblis2 suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: blis
Source-Version: 0.5.1-7

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

Debian distribution maintenance software
pp.
Mo Zhou  (supplier of updated blis package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 27 Jan 2019 06:18:53 +
Source: blis
Architecture: source
Version: 0.5.1-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Mo Zhou 
Closes: 919273
Changes:
 blis (0.5.1-7) unstable; urgency=medium
 .
   * Modify upstream header to amend kFreeBSD detection.
   * Patch upstream Makefile to build separate libblas.so* .
   * Install separate libblas into blis{,64} subdirs, (Closes: #919273)
 where its SONAME is "libblas.so.3".
   * Change libblas.so* provider from libblis.so* to blis*/libblas.so*.
   * Override dh_dwz to append --no-dwz-multifile option.
   * Don't track symbols list for private shared objects.
Checksums-Sha1:
 8b4d51f2062fa20a0e93c058f5f7dde8d6d80a86 3554 blis_0.5.1-7.dsc
 aa54978ba8e6ccdb04fb74f68782e95255483f16 22132 blis_0.5.1-7.debian.tar.xz
 ea60ba3ff1c7532a10a409df4d9685b44c414015 6409 blis_0.5.1-7_source.buildinfo
Checksums-Sha256:
 7c0649777b3a500650f05d6ff354c38973818a5b78d7eb8102ea90fe32e6940a 3554 
blis_0.5.1-7.dsc
 91426bf16858409c891d56108f38f52abd6994122135d23227dbfd3da6d17028 22132 
blis_0.5.1-7.debian.tar.xz
 4d878379ed78e6461019e961ee109a5f193f71394f6551531aacb0fd0ffa9376 6409 
blis_0.5.1-7_source.buildinfo
Files:
 df98164b46f001b0772a37e73c86f439 3554 math optional blis_0.5.1-7.dsc
 eb178200fa6adb97aa0a9bc92ae0f216 22132 math optional blis_0.5.1-7.debian.tar.xz
 6850d9aafb1129b84cfe2a7e1ef3bc76 6409 math optional 
blis_0.5.1-7_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEY4vHXsHlxYkGfjXeYmRes19oaooFAlxNTYYACgkQYmRes19o
aork5w/9H78v+iz6GnnMNOx6DViWySFt4CLOcvr+M835K9H8c7ElZLAEkZpiSLZs
8R+WwdOXTuB5x8NhFMJmMFY0FTvJDGHPOYePC2kTec6BArXnEUWL2G+krf+ZDlP0
oHEORtWV3SPE5S1eP00nvB/pj4Pz31UMCx3VHCXgluifp4oOfihxNaFEuvffDH9h
NBFczmXpJF+dAgQ15hJ86UzLsbYI/DC5hE0v8BDDugL3zspGpzkPzmh+64FlOQzo
5TbHt7K0p5Bkol0wsS0LprCv0oiuFkqX9uSFNOUVco+iOWx819uJcYxeLa3SCpxT
aGA6jV8qTWA+4vbND5kPJ2ZSb7dsCI6LgML3WiG5B7oVzbTy1c2L9vUnijfKZrYK
cHh1YuOImkxC1SKu6lzWNROJN0M13K3L9rPpZs4e37FxMoXDyjssk8g0ntqTTw+x
MOAXEpDTYGJMtPy1GFQvq6Xzbv6BcvI6f5RcVAqYkcS6CHzoZErQOx3xNuSq16K6
fW+Smz3/D9SO+f0Q9bGyqPwzGYnk1+9VdugWjC8bcHN0mmEnKBQjlRrCRkXA1vLH
wWpCK/BgkExkLGlSiNPA0mXuFYcXEKhQ9k6evDdj0WKx7BzcL26pyYtAcfLKq1MN
YkrLD3w5jLVRg7HyIH12gbBNT/WANTqhaJJiXhuMNM6SRRlNvwo=
=ExtA
-END PGP SIGNATURE End Message ---

Bug#920189: marked as done (kopanocore: wrong installation directories)

[Debian Bug Tracking System]

Your message dated Sun, 27 Jan 2019 07:21:17 +
with message-id 
and subject line Bug#920189: fixed in kopanocore 8.7.0-1
has caused the Debian Bug report #920189,
regarding kopanocore: wrong installation directories
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.)


-- 
920189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920189
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kopanocore
Version 8.6.92-1
Severity: serious
Tags: patch

/usr/lib/@DEB_HOST_MULTIARCH@/kopano/kscriptrun
/usr/lib/@DEB_HOST_MULTIARCH@/kopano/mapitime

this is not a valid installation directory.

you might want to apply this patch to fix the issue.
http://launchpadlibrarian.net/407502595/kopanocore_8.6.92-1_8.6.92-1ubuntu1.diff.gz

(or convert the file in a install.in, but this requires more changes, while the 
change @@ to ${} seems to fix this issue properly.

Also, can you please force the systemd directory in rules file? this way we 
avoid issues when pkg-config is installed in the system as default, because of 
the configure.ac trying to figure out the directory
systemunitdir=$("$PKG_CONFIG" systemd --variable 
systemdsystemunitdir 2>/dev/null)
AS_IF([test -z "$systemunitdir"], 
[systemunitdir='${prefix}/lib/systemd/system'])


thanks

Gianfranco
--- End Message ---
--- Begin Message ---
Source: kopanocore
Source-Version: 8.7.0-1

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated kopanocore 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 27 Jan 2019 07:51:34 +0100
Source: kopanocore
Architecture: source
Version: 8.7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Giraffe Maintainers 

Changed-By: Carsten Schoenert 
Closes: 920189
Changes:
 kopanocore (8.7.0-1) unstable; urgency=medium
 .
   [ Carsten Schoenert ]
   * [80f58ba] New upstream version 8.7.0
   * [48214e0] kopano-libs.symbols: update symbols to 8.7.0
 .
   [ Gianfranco Costamagna ]
   * [b68a083] d/kopano-utils.install: change substitution variable
 (Closes: #920189)
   * [1e7d135] d/rules: adjust the systemd unit folder to use
Checksums-Sha1:
 cf78b92ec9d481d1ddee235f25cf3b6187aa9753 3823 kopanocore_8.7.0-1.dsc
 4da41e49b5ca5d5ca9ce99c16f8da99fe2d5dfdf 1819108 kopanocore_8.7.0.orig.tar.xz
 c2abe60e7b6f29ff0314e8064ed8e2a47a732c5f 44912 kopanocore_8.7.0-1.debian.tar.xz
 54731900a2019140d3969fcaed497010eeecc9df 18314 
kopanocore_8.7.0-1_amd64.buildinfo
Checksums-Sha256:
 fcc602964de6d089ba9756363cea4944dcbfdfc0c2d15d5f1b9d55aa22c4df8a 3823 
kopanocore_8.7.0-1.dsc
 3b5b0543efdf19a6bdee966af63ed8a981fa34a4b070664b1f328eb291b058fc 1819108 
kopanocore_8.7.0.orig.tar.xz
 3b14e13fbf3fbffcb684a6e1a34e25c5b3f39425ef1415fbd8dad003378e031a 44912 
kopanocore_8.7.0-1.debian.tar.xz
 ad4beba54d95631ad2280383ab82a302bcf146272986fd0219e849566359a662 18314 
kopanocore_8.7.0-1_amd64.buildinfo
Files:
 681dfa0f9fa01ae89f1346e797b72750 3823 mail optional kopanocore_8.7.0-1.dsc
 bf07cd642b5fbae436b82cbd97769ca9 1819108 mail optional 
kopanocore_8.7.0.orig.tar.xz
 d02edfb2b67149b0da8559875d7d4696 44912 mail optional 
kopanocore_8.7.0-1.debian.tar.xz
 d000bc1f7cc12be62525be03d5787b8a 18314 mail optional 
kopanocore_8.7.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtw38bxNP7PwBHmKqgwFgFCUdHbAFAlxNV1MACgkQgwFgFCUd
HbBj2A/+L3PvaUJPKJM319PB1/GEFJXG5wxSwvvXTH58MsfYdk+2aXJJKTgMJDcg
pzMk65KoXxBtaa0vjG7fmnzrfCtq4C8fK8UCccUGMBN8grbwMAtcIhuk9mEyxv9d
wCJkkmGlr1tcnlOSKD9C0/6o9WfPIVWxzH10EgKUbj//XoBZizUBufg06t3U7OfG
OQjLpVcaIW72wuMDwtUOXDkb6PCU9AQHCNYOQaRZNHa9M7kBS+KC3yeo5LsG0noO
hvWsVzBXO2NBNgbjx1x1b8qo0XmcBgNMhiVbpagbXf2eWndlAsOZ4eWiNR+P+HHx
3VpHF6OP/HdFqmntChsykCgdvcZNM/kAZ0PMP5fYhEQGK+g3xK1XipuWZf61kSHj
dlhnBPrJvA5b/8jKXAQC4RPYjBYQK7xZVNAUrOo5TjwG9xF2CAlvT3POafE+up+q
2YLR22Rze4qCRq+I3oc0cwo3DSsUcqW2ZVXMKoe8dFUsjWRhs2VJLdCi6Z2HCHx7
idvJ5MEwlVH06XDUi+B7hFVbPY0cdmo9qcH5A2cbWbGvRzwjKl7ZFfmz4+4XRBpO

Bug#918746: marked as done (Should this package be removed?)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 22:45:29 +0100
with message-id <20190126214529.2kof7lqa4su3g...@inutil.org>
and subject line Re: Bug#918746: pam-ssh-agent-auth alternative
has caused the Debian Bug report #918746,
regarding Should this package be removed?
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.)


-- 
918746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pam-ssh-agent-auth
Severity: serious

Should pam-ssh-agent-auth be removed from the archive?

It seems dead upstream, the last commits are from March 2014, it's broken
with OpenSSL 1.1 and was removed from testing more than a year ago. It's
also one of the few remaining packages blocking the removal of OpenSSL 1.0.

Cheers,
Moritz
  
--- End Message ---
--- Begin Message ---
On Sun, Jan 27, 2019 at 12:24:15AM +0700, Bálint Réczey wrote:
> Hi,
> 
> Benda Xu  ezt írta (időpont: 2019. jan. 26., Szo, 4:45):
> >
> > Hi Moritz,
> >
> > That needs to be seriously considered.  I am using this package
> > extensively.  Do you any alternatives to it?
> 
> I picked the patch used in Gentoo and FreeBSD to make the package
> build again, but it does not resurrect upstream.
> 
> I'd say with this change there is no immediate need for removal, but I
> removed myself from uploaders since I did not have enough time to take
> care of the package properly and let the final word on removal for the
> Security Team.

If it builds now with OpenSSL 1.1, I don't see a reason to remove it,
this was primarily motivated because we need to get rid of OpenSSL 1.0
for good.

I'm closing the bug for now.

Cheers,
Moritz--- End Message ---

Bug#920198: marked as done (dasher: Some training texts have trailing spaces)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 22:22:19 +
with message-id 
and subject line Bug#920198: fixed in dasher 5.0.0~beta~repack-7
has caused the Debian Bug report #920198,
regarding dasher: Some training texts have trailing spaces
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.)


-- 
920198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920198
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dasher
Version: 5.0.0~beta~repack-6
Severity: normal

The German, English and French training texts all have lines with trailing 
spaces
(i.e. period SPACE LF instead of PERIOD LF). This is broken; please fix.

The English training text contains HTML markup. Please remove.

I did not check others; the problem probably is more widespread.


-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable'), (590, 'stable'), (550, 
'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages dasher depends on:
ii  dasher-data  5.0.0~beta~repack-6
ii  libatk-adaptor   2.30.0-2
ii  libatspi2.0-02.30.0-5
ii  libc62.28-5
ii  libcairo21.16.0-2
ii  libexpat12.2.6-1
ii  libgcc1  1:8.2.0-14
ii  libglib2.0-0 2.58.2-3
ii  libgtk-3-0   3.24.3-1
ii  libpango-1.0-0   1.42.4-6
ii  libpangocairo-1.0-0  1.42.4-6
ii  libspeechd2  0.8.8-9
ii  libstdc++6   8.2.0-14

dasher recommends no packages.

dasher suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dasher
Source-Version: 5.0.0~beta~repack-7

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated dasher package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Jan 2019 22:58:36 +0100
Source: dasher
Binary: dasher dasher-data dasher-dbgsym
Architecture: source
Version: 5.0.0~beta~repack-7
Distribution: unstable
Urgency: medium
Maintainer: Debian Accessibility Team 
Changed-By: Samuel Thibault 
Description:
 dasher - graphical predictive text input system
 dasher-data - Data files for dasher
Closes: 920198
Changes:
 dasher (5.0.0~beta~repack-7) unstable; urgency=medium
 .
   * Bump Standards-Version to 4.2.0 (no changes).
   * patches/drop: Drop some spurious data (Closes: Bug#920198).
Checksums-Sha1:
 c30a1b58ba04e54edd3be2cb3699dbd1f9ad9e73 2194 dasher_5.0.0~beta~repack-7.dsc
 b8c0a485835d61130d14b97d067d0601d6a67038 2063828 
dasher_5.0.0~beta~repack-7.debian.tar.xz
Checksums-Sha256:
 70ddeba4413921aa85c4fedab2accd6eca546aa372b9573efe95badfaee30cb1 2194 
dasher_5.0.0~beta~repack-7.dsc
 84b91575e56f674deb017ea1c7803248ef6a279696e08ba5b9b2b72b846f21bd 2063828 
dasher_5.0.0~beta~repack-7.debian.tar.xz
Files:
 6a0abfd54693180cd9988e4a68303ad6 2194 x11 optional 
dasher_5.0.0~beta~repack-7.dsc
 b53df5a7d9167061d3315ea86c3303ef 2063828 x11 optional 
dasher_5.0.0~beta~repack-7.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEM/p7ZGGVAfjOnI+X4/ZanpVg20wFAlxM2PEACgkQ4/ZanpVg
20zs5Q/+MCLIejcOCoEMUOZmZ5lZAubWaRpahWF5Q2fYpgvjNfXXr8pDHvLlAyux
T4poJd6ZKT1HZjlxJ+lz0kItKKyn9qg6AXc0hZb2YQOTpyOs3EthlBE6rME48Uae
ot3O14bjFawS642ugdBdqWPeckxvftUEvUXJ+/dEqA5AsjvQPJhmQm8wuwHyZX3H
VCG1lk0EaovdV/5VzqLSt1rw7uNA3738k81FvLgVCTGwKSNYhxXHDJjw+gzfaljF
FxR4iBwbLXqnp1Q/U9dSPvcFpoe99EnGcbirGedDU8B86LvqMsxV8aS7LwnY0K4Z
ZWuDtGqQvmkXmA3j6jwQ8YjDDNiaoDHP7TywIw73LPHfkTBCSqg3ddrVAtIt5Xq+
NSoz0mzfMIy3p4ps+sTb5KhMvFLuoFndDQGCKBFgd0y5+C7EgmKBdUnnm6QPifre
8x01LiOHhXnQYuuRM7MDXT96QAeUXvud0A9cz2h8EF90Xdbi/FU3y8cOhayZNMkv
nYd43/NUFn6Q0XlU9dhzGV29KhP/bFAqTuARbIpO5Lh8k4O4ZHIW6sMOGktFCgC6
nHnoqcDDbZBFeymXr2FbO5inSim6OqbjGGHOCRMSlRTIBENOcaR3eE96SUQq88TM

Bug#920538: marked as done (node-date-now: flaky autopkgtest as it times out sometimes)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 22:52:35 +
with message-id 
and subject line Bug#920538: fixed in node-date-now 1.0.1-3
has caused the Debian Bug report #920538,
regarding node-date-now: flaky autopkgtest as it times out sometimes
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.)


-- 
920538: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920538
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-date-now
Version: 1.0.1-1
Severity: important
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainers,

In the last month, your package has failed 4 times on the ci.debian.net
with due to timeouts while a retry just after the failure passes. Could
you please investigate and make your autopkgtest more robust (e.g. check
if your timeout is reasonable in all circumstances)? Please contact me
if you need help and you think I can provide that (I am not subscribed
to this bug). If this flakiness can't really be fixed, consider setting
the "flaky" restriction (see
https://salsa.debian.org/ci-team/autopkgtest/raw/master/doc/README.package-tests.rst).

Recent discussion of gating migration by autopkgtests on debian-devel
[1] noted that if this is going to work, and in particular now we are
*blocking* migration when it causes autopkgtest regressions,
intermittent autopkgtest failures are likely to have to be considered RC
due to their impact on the tested package's dependencies; for now I've
filed it as important.

Paul

[1] https://lists.debian.org/debian-devel/2018/05/msg00061.html

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-date-now/1790722/log.gz

autopkgtest [14:34:44]: test command1: nodejs ./test
autopkgtest [14:34:44]: test command1: [---
TAP version 13
# date
ok 1 should be truthy
ok 2 should be truthy
# seeded
not ok 3 should be truthy
  ---
operator: ok
expected: true
actual:   false
at: Test.
(/tmp/autopkgtest-lxc.yfcqr67i/downtmp/build.wkk/src/test/index.js:25:12)
stack: |-
  Error: should be truthy
  at Test.assert [as _assert]
(/usr/lib/nodejs/tape/lib/test.js:235:54)
  at Test.bound [as _assert]
(/usr/lib/nodejs/tape/lib/test.js:87:32)
  at Test.assert (/usr/lib/nodejs/tape/lib/test.js:353:10)
  at Test.bound [as ok] (/usr/lib/nodejs/tape/lib/test.js:87:32)
  at Test.
(/tmp/autopkgtest-lxc.yfcqr67i/downtmp/build.wkk/src/test/index.js:25:12)
  at Test.bound [as _cb] (/usr/lib/nodejs/tape/lib/test.js:87:32)
  at Test.run (/usr/lib/nodejs/tape/lib/test.js:106:10)
  at Test.bound [as run] (/usr/lib/nodejs/tape/lib/test.js:87:32)
  at Immediate.next [as _onImmediate]
(/usr/lib/nodejs/tape/lib/results.js:71:15)
  at runCallback (timers.js:705:18)
  ...
ok 4 should be truthy
not ok 5 should be truthy
  ---
operator: ok
expected: true
actual:   false
at: Timeout._onTimeout
(/tmp/autopkgtest-lxc.yfcqr67i/downtmp/build.wkk/src/test/index.js:33:16)
stack: |-
  Error: should be truthy
  at Test.assert [as _assert]
(/usr/lib/nodejs/tape/lib/test.js:235:54)
  at Test.bound [as _assert]
(/usr/lib/nodejs/tape/lib/test.js:87:32)
  at Test.assert (/usr/lib/nodejs/tape/lib/test.js:353:10)
  at Test.bound [as ok] (/usr/lib/nodejs/tape/lib/test.js:87:32)
  at Timeout._onTimeout
(/tmp/autopkgtest-lxc.yfcqr67i/downtmp/build.wkk/src/test/index.js:33:16)
  at ontimeout (timers.js:436:11)
  at tryOnTimeout (timers.js:300:5)
  at listOnTimeout (timers.js:263:5)
  at Timer.processTimers (timers.js:223:10)
  ...
ok 6 should be truthy

1..6
# tests 6
# pass  4
# fail  2

autopkgtest [14:34:45]: test command1: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-date-now
Source-Version: 1.0.1-3

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

Debian distribution maintenance software
pp.
Jérémy Lal  (supplier of updated node-date-now package)

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

Bug#777716: marked as done ([jessie RC1] wireless LAN card not usable, problem with loading/using firmware)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 23:55:44 +0100
with message-id <20190126235544.fbd879828bd61c10f14f4...@mailbox.org>
and subject line [jessie RC1] wireless LAN card not usable, problem with 
loading/using firmware
has caused the Debian Bug report #16,
regarding [jessie RC1] wireless LAN card not usable, problem with loading/using 
firmware
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.)


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


I have a laptop here which needs firmware for the wireless LAN card
Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter (PCI-ID: 8086:1043).

It seems the process of requesting, loading and using firmware is not fully
functional:
When it comes to the d-i step "Detecting network hardware", there is lot of
output on the 4th console regarding 
"BUG: unable to handle kernel paging request at ce8ec00c"
and
"Oops: 0002 [#1]
and
"Call Trace:"
" ? ipw2100_down+0x9e/ox10 [ipw2100]
and the like.

I have attached a syslog of this installation try.

But I am able to proceed with the installation steps, d-i requests firmware
file, so I plug in my usbstick, the relevant firmware package is installed
(the firmware files end up in /lib/firmware), but the device is not able
to operate. It is not shown in the list of available network devices in the
d-i UI.


To investigate this, I started the installation again, but before the step
"Detect network hardware" is started, I mount my usbstick, copy the needed
firmware file into /lib/firmware by hand and then start the step
"Detect network hardware". And now the device is working, it is shown as
available nework device, it scans and shows available WLANs, so the hardware 
seems to work.
So it calms down to the firmware not being available, when the module is loaded.


(Please note, that the needed firmware is detected correctly, and the 
correct package is installed, so the newly created way of detecting missing
firmware seems to work fine!)



Regards
Holger



-- 

Created with Sylpheed 3.2.0 under
D E B I A N   L I N U X   7 . 0   W H E E Z Y !

Registered Linux User #311290 - https://linuxcounter.net/



firmware-problem.dmesg
Description: Binary data
--- End Message ---
--- Begin Message ---

Holger Wansing  wrote:
> I have a laptop here which needs firmware for the wireless LAN card
> Intel PRO/Wireless LAN 2100 3B Mini PCI Adapter (PCI-ID: 8086:1043).
> 
> It seems the process of requesting, loading and using firmware is not fully
> functional:
> When it comes to the d-i step "Detecting network hardware", there is lot of
> output on the 4th console regarding 
>   "BUG: unable to handle kernel paging request at ce8ec00c"
>   and
>   "Oops: 0002 [#1]
>   and
>   "Call Trace:"
>   " ? ipw2100_down+0x9e/ox10 [ipw2100]
>   and the like.
> 
> I have attached a syslog of this installation try.
> 
> But I am able to proceed with the installation steps, d-i requests firmware
> file, so I plug in my usbstick, the relevant firmware package is installed
> (the firmware files end up in /lib/firmware), but the device is not able
> to operate. It is not shown in the list of available network devices in the
> d-i UI.
> 
> 
> To investigate this, I started the installation again, but before the step
> "Detect network hardware" is started, I mount my usbstick, copy the needed
> firmware file into /lib/firmware by hand and then start the step
> "Detect network hardware". And now the device is working, it is shown as
> available nework device, it scans and shows available WLANs, so the hardware 
> seems to work.
> So it calms down to the firmware not being available, when the module is 
> loaded.

I no longer have access to this notebook, so I am unable to test if 
installation still fails on this device.
So closing this (jessie) bug.


Holger


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#920553: marked as done (pkg-config: Undefined subroutine ::warning called at /usr/share/pkg-config-dpkghook line 34.)

[Debian Bug Tracking System]

Your message dated Sun, 27 Jan 2019 05:19:06 +
with message-id 
and subject line Bug#920553: fixed in pkg-config 0.29-6
has caused the Debian Bug report #920553,
regarding pkg-config: Undefined subroutine ::warning called at 
/usr/share/pkg-config-dpkghook line 34.
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.)


-- 
920553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pkg-config
Version: 0.29-5
Severity: serious

pkg-config fails to upgrade on two machines (1x amd64 with i386 as
foreign architecture, 1x pure i386) as follows for me:

Setting up pkg-config (0.29-5) ...
Undefined subroutine ::warning called at /usr/share/pkg-config-dpkghook 
line 34.
dpkg: error processing package pkg-config (--configure):
 installed pkg-config package post-installation script subprocess returned 
error exit status 255
Errors were encountered while processing:
 pkg-config

In both cases the error message looks identical.

It does though not happen on all of my sid machines, including other
amd64 machines. Maybe a missing dependency on some Perl module or so?

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

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

Versions of packages pkg-config depends on:
ii  libc6 2.28-5
ii  libdpkg-perl  1.19.4
ii  libglib2.0-0  2.58.2-4

pkg-config recommends no packages.

Versions of packages pkg-config suggests:
ii  dpkg-dev  1.19.4

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pkg-config
Source-Version: 0.29-6

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

Debian distribution maintenance software
pp.
Tollef Fog Heen  (supplier of updated pkg-config package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 27 Jan 2019 05:56:33 +0100
Source: pkg-config
Binary: pkg-config
Architecture: source
Version: 0.29-6
Distribution: unstable
Urgency: medium
Maintainer: Tollef Fog Heen 
Changed-By: Tollef Fog Heen 
Description:
 pkg-config - manage compile and link flags for libraries
Closes: 920553
Changes:
 pkg-config (0.29-6) unstable; urgency=medium
 .
   * Add missing "warning" in use in dpkg hook, and corresponding test.
 Closes: #920553
   * Add missing set -e to tests.
Checksums-Sha1:
 0b16917b49979d5227aecab878e2d75d68789b89 1757 pkg-config_0.29-6.dsc
 a700a78832ea8f23a7b77a560cf59dcb4c78555c 8145 pkg-config_0.29-6.diff.gz
Checksums-Sha256:
 a5f1a8f976f3d8ad579341ba73514eb3af9dbc6bad8d2b5828699ac24196624f 1757 
pkg-config_0.29-6.dsc
 c06146d878fb7faa4ac3edb5e45188b184cc650a752384d5c1053f41edf590bc 8145 
pkg-config_0.29-6.diff.gz
Files:
 f40a3ea1c3cb1b7c514213395740634c 1757 devel optional pkg-config_0.29-6.dsc
 b70d14960a41816c1440c0921cc266e6 8145 devel optional pkg-config_0.29-6.diff.gz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEooQRpZYZMXEzGALAtlpIccoZ1xcFAlxNPSIACgkQtlpIccoZ
1xebdw//eTopGSLlH2s1MV2No+u82u5t5fUAFkIJhBSZYnDNhoTJZiWr28lzl7AK
xje6e0R5xuOBsbr3yC3LomDT2vPvVq0bNz3PtVaTxIqFW/+f4Ej5WZDo1D3Tr4tN
EzP83qQ629LZYJuWVUQ//Rzl3Q8azGOcsL2IoUJHQrapfGrRw1BsDGPLqwvsPOef
SQTuWQ7fspGxkeOBX8RFd9iQ5ao9wGu7grgXb6XrorMhFbmxY2up7pdoVeFMv56T
cxpeImzbXJdl80t5WEN4OiKnf+1lH9DiXMLbxbNWlGqxWGhGOChwNotJ7e86xWIQ
++JTnmoDPOVSv+9fi7pqBPH+qJD3M80nGxRg8tyULHlHeC5qr2cl+EjZOroUQ89v
5+icAgC3D0Qxh/LdCtU0951S0LSxdXllePk7/bFDiKkf20lN5lAbMfiLqrz4rJ2d
/md6c+oPvBObSLBRvS2A9KsGYxJbc5tiJ8brHz05oXT/zNP7MfZqtLfHa44Qyek3
zM/Xe+4LJHNcPbaD+XyPDH6ZwTOR2cZAWv7u0iIdPLNd7nLr45zIEC6PEtgowMDV
BpX1NmxRrxs0I4H41n9e7u5ZLpsaNLqxBCqxwcSFcmmtake1KW2bMFw3T60BygeN

Bug#918845: marked as done (kitchen: FTBFS with Sphinx 1.8: No module named 'sphinx.ext.pngmath')

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 23:06:55 +
with message-id 
and subject line Bug#918845: fixed in kitchen 1.2.5-4
has caused the Debian Bug report #918845,
regarding kitchen: FTBFS with Sphinx 1.8: No module named 'sphinx.ext.pngmath'
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.)


-- 
918845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kitchen
Version: 1.2.5-3
Severity: important
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx1.8

Dear Maintainer,

kitchen fails to build with Sphinx 1.8, currently available in experimental:

  PYTHONPATH=/<>/kitchen3/ http_proxy='127.0.0.1:9' \
  sphinx-build -N -bhtml kitchen3/docs/ kitchen3/docs/_build/html
  Running Sphinx v1.8.3
  loading translations [en]... done

  Extension error:
  Could not import extension sphinx.ext.pngmath (exception: No module named 
'sphinx.ext.pngmath')
  make[1]: *** [debian/rules:20: override_dh_auto_build] Error 2

The pngmath extension was deprecated in Sphinx 1.4 and has been removed [1]
in Sphinx 1.8. The recommended alternative is sphinx.ext.imgmath [2] which
also has SVG support in addition to PNG.

To me it looks like this extension is unused anyway: there are no “.. math::”
directives or “:math:” roles, and python-kitchen-doc does not have any
generated PNG images. So this extension can be simply removed from extensions
in conf.py.

[1]: https://github.com/sphinx-doc/sphinx/pull/4702
[2]: https://www.sphinx-doc.org/en/1.8/usage/extensions/math.html

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: kitchen
Source-Version: 1.2.5-4

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

Debian distribution maintenance software
pp.
Sergio Durigan Junior  (supplier of updated kitchen 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 26 Jan 2019 17:49:43 -0500
Source: kitchen
Architecture: source
Version: 1.2.5-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Sergio Durigan Junior 
Closes: 918845
Changes:
 kitchen (1.2.5-4) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * Use 'python3 -m sphinx' instead of sphinx-build for building docs
 .
   [ Sergio Durigan Junior ]
   * Remove dependency on 'sphinx.ext.pngmath' when building docs.
 Sphinx >= 1.8 has deprecated the support for 'sphinx.ext.pngmath'.
 Since kitchen doesn't even use this extension in its documentation,
 it's OK to just not depend on it at all.
 Thanks to Dmitry Shachnev  (Closes: #918845)
   * Bump Standards-Version to 4.3.0.
Checksums-Sha1:
 726b728654e8232d390a516cb27e8881c9afd165 2306 kitchen_1.2.5-4.dsc
 4856d837c971e42d2f78c9038e2815c00fb2f48f 24504 kitchen_1.2.5-4.debian.tar.xz
 5fb9b2847132a2132b1d043347f1aa4b3f7fc740 8391 kitchen_1.2.5-4_amd64.buildinfo
Checksums-Sha256:
 7fce3c4ef294f2c346cc5bd3b7b162a6f420e9e1e7db35bb0e5bef2850f53943 2306 
kitchen_1.2.5-4.dsc
 7174fc0ff9d1fceaae645da45a4607e18c4bc998638aa759bb094675ed92cee5 24504 
kitchen_1.2.5-4.debian.tar.xz
 2989494ece22dcc1ecf960d8deae34173a1e72ec6b3cbc695b6b72486fd5c15d 8391 
kitchen_1.2.5-4_amd64.buildinfo
Files:
 dbdf3d1b30d1beb0b8258a5f145750fb 2306 python optional kitchen_1.2.5-4.dsc
 fc5a8b8501091e2de1ff6c5e6193cbc7 24504 python optional 
kitchen_1.2.5-4.debian.tar.xz
 00c70650046e610ebb76bfa040210e30 8391 python optional 
kitchen_1.2.5-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEI3pUsQKHKL8A7zH00Ot2KGX8XjYFAlxM5UwUHHNlcmdpb2Rq
QGRlYmlhbi5vcmcACgkQ0Ot2KGX8XjbpjRAAlrAYgJtzCAFCq+5/9QPfge844fLL
KVIYpyWsP8WKU8lQ/okXZdYWNqzk2xQ1AwjRcs6/0nF6iCCJuQPbcEPHGPfjR/qo
9qvqV4cIhUIH3HEqO17j07L4f8klKzjdJeQWOyqH85f0SYAca6ZlkNAIBFsl++z3
SAKR37a8lvUeCVeCI8a7eSmiy5e+M0HsV0JwWtJedtgEbL7G89rTmuBfORryYFtj
6L4IjM4/MObN7LSspuPvGdq/FCiWyfV0dxNJgcZYOBEUqNcHvCFKX3bjOAMAY7MY
8zH4bPLaFAv8rj5hg7b2khjndDRg0iw9JStw5TnmWnijO+IEh4qqvaKbUAj1P5GD

Bug#920549: marked as done (git-annex: flaky autopkgtest)

[Debian Bug Tracking System]

Your message dated Sun, 27 Jan 2019 04:49:46 +
with message-id 
and subject line Bug#920549: fixed in git-annex 7.20190122-2
has caused the Debian Bug report #920549,
regarding git-annex: flaky autopkgtest
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.)


-- 
920549: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920549
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git-annex
Version: 7.20190122-1   
Severity: important
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainers,

You packages fails regularly on the ci.debian.net infrastructure without
apparent changes. Just now, it was blocking migration of sqlite3 due to
a failure, but when I retrigged the test, it passed. Could you please
investigate and make your autopkgtest more robust? Please contact me if
you need help and you think I can provide that (I am not subscribed to
this bug).

Recent discussion of gating migration by autopkgtests on debian-devel
[1] noted that if this is going to work, and in particular now we are
*blocking* migration when it causes autopkgtest regressions,
intermittent autopkgtest failures are likely to have to be considered RC
due to their impact on the tested package's dependencies; for now I've
filed it as important.

Paul

[1] https://lists.debian.org/debian-devel/2018/05/msg00061.html

https://ci.debian.net/data/autopkgtest/testing/amd64/g/git-annex/1791938/log.gz

get: 1 failed
FAIL (0.15s)
  Test.hs:1508:
  get failed
uninit (in git-annex branch): On branch master
nothing to commit, working tree clean
not supported in direct mode; skipping
OK (0.14s)
upgrade:  On branch master
nothing to commit, working tree clean
OK (0.23s)
whereis:  On branch master
nothing to commit, working tree clean
whereis: 1 failed
FAIL (0.15s)
  Test.hs:1526:
  whereis on non-present file failed
hook remote:  On branch master
nothing to commit, working tree clean
get: 1 failed
FAIL (0.16s)
  Test.hs:1546:
  get of file failed
directory remote: On branch master
nothing to commit, working tree clean
get: 1 failed
FAIL (0.16s)
  Test.hs:1570:
  get of file failed
rsync remote: On branch master
nothing to commit, working tree clean
get: 1 failed
FAIL (0.16s)
  Test.hs:1585:
  get of file failed
bup remote:   On branch master
nothing to commit, working tree clean
OK (0.12s)
crypto:   On branch master
nothing to commit, working tree clean
git-annex: There is already a special remote named "foo". (Use
enableremote to enable an existing special remote.)
initremote: 1 failed
get: 1 failed
FAIL (0.25s)
  Test.hs:1643:
  get of file failed
preferred content:On branch master
nothing to commit, working tree clean
get: 1 failed
FAIL (0.16s)
  Test.hs:550:
  get --auto of file failed with default preferred content
add subdirs:  On branch master
nothing to commit, working tree clean
Automatic merge went well; stopped before committing as requested
To /tmp/tmp.wo7OE4YXDe/.t/repo
   ae7c86c..522ac14  git-annex -> synced/git-annex
   da99c14..09870b7  annex/direct/master -> synced/master
OK (0.41s)
addurl:   On branch master
nothing to commit, working tree clean
Configuration does not allow accessing
file:///tmp/tmp.wo7OE4YXDe/.t/tmprepo291/myurl
download failed: Configuration does not allow accessing
file:///tmp/tmp.wo7OE4YXDe/.t/tmprepo291/myurl
OK (0.20s)

19 out of 227 tests failed (119.30s)
  (Failures above could be due to a bug in git-annex, or an incompatibility
   with utilities, such as git, installed on this system.)
autopkgtest [16:27:29]: test basics: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: git-annex
Source-Version: 7.20190122-2

We believe that the bug you reported is fixed in the latest version of
git-annex, 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 

Bug#915311: marked as done (dumb-init FTBFS on mips*: test failures)

[Debian Bug Tracking System]

Your message dated Sun, 27 Jan 2019 06:49:07 +
with message-id 
and subject line Bug#915311: fixed in dumb-init 1.2.2-1
has caused the Debian Bug report #915311,
regarding dumb-init FTBFS on mips*: test failures
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.)


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

https://buildd.debian.org/status/package.php?p=dumb-init

...
=== FAILURES ===
_ test_all_processes_receive_term_on_exit_if_setsid[1] _

@pytest.mark.usefixtures('both_debug_modes', 'setsid_enabled')
def test_all_processes_receive_term_on_exit_if_setsid():
"""If the child exits for some reason, dumb-init should send TERM to all
processes in its session if setsid mode is enabled."""
>   child_pid, child_stdout = spawn_process_which_dies_with_children()

tests/child_processes_test.py:109: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

def spawn_process_which_dies_with_children():
"""Spawn a process which spawns some children and then dies without
signaling them, wrapped in dumb-init.

Returns a tuple (child pid, child stdout pipe), where the child is
print_signals. This is useful because you can signal the PID and see if
anything gets printed onto the stdout pipe.
"""
proc = Popen(
(
'dumb-init',
'sh', '-c',

# we need to sleep before the shell exits, or dumb-init might 
send
# TERM to print_signals before it has had time to register 
custom
# signal handlers
'{python} -m testing.print_signals & sleep 0.1'.format(
python=sys.executable,
),
),
stdout=PIPE,
)
proc.wait()
assert proc.returncode == 0

# read a line from print_signals, figure out its pid
line = proc.stdout.readline()
match = re.match(b'ready \(pid: ([0-9]+)\)\n', line)
>   assert match, line
E   AssertionError: 
E   assert None

tests/child_processes_test.py:95: AssertionError
- Captured stderr call -
[dumb-init] Running in debug mode.
[dumb-init] Unable to detach from controlling tty (errno=25 Inappropriate ioctl 
for device).
[dumb-init] Child spawned with PID 7035.
[dumb-init] Unable to attach to controlling tty (errno=25 Inappropriate ioctl 
for device).
[dumb-init] setsid complete.
[dumb-init] Received signal 18.
[dumb-init] A child with PID 7035 exited with exit status 0.
[dumb-init] Forwarded signal 15 to children.
[dumb-init] Child exited with status 0. Goodbye.
_ test_all_processes_receive_term_on_exit_if_setsid[0] _

@pytest.mark.usefixtures('both_debug_modes', 'setsid_enabled')
def test_all_processes_receive_term_on_exit_if_setsid():
"""If the child exits for some reason, dumb-init should send TERM to all
processes in its session if setsid mode is enabled."""
>   child_pid, child_stdout = spawn_process_which_dies_with_children()

tests/child_processes_test.py:109: 
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 

def spawn_process_which_dies_with_children():
"""Spawn a process which spawns some children and then dies without
signaling them, wrapped in dumb-init.

Returns a tuple (child pid, child stdout pipe), where the child is
print_signals. This is useful because you can signal the PID and see if
anything gets printed onto the stdout pipe.
"""
proc = Popen(
(
'dumb-init',
'sh', '-c',

# we need to sleep before the shell exits, or dumb-init might 
send
# TERM to print_signals before it has had time to register 
custom
# signal handlers
'{python} -m testing.print_signals & sleep 0.1'.format(
python=sys.executable,
),
),
stdout=PIPE,
)
proc.wait()
assert proc.returncode == 0

# read a line from print_signals, figure out its pid
line = proc.stdout.readline()
match = re.match(b'ready \(pid: ([0-9]+)\)\n', line)
>  

Bug#920550: marked as done (ITP: icecream-sundae -- Commandline Monitor for Icecream (icecc))

[Debian Bug Tracking System]

Your message dated Sun, 27 Jan 2019 07:09:28 +
with message-id <20190127070928.74di7jjzrnjw3...@master.debian.org>
and subject line closing duplicate itp
has caused the Debian Bug report #920550,
regarding ITP: icecream-sundae -- Commandline Monitor for Icecream (icecc)
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.)


-- 
920550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920550
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Anton Gladky 

* Package name: icecream-sundae
  Version : 1.0.0
* URL : https://github.com/JPEWdev/icecream-sundae
* License : GPL-2+
  Programming Lang: C++
  Description : Commandline Monitor for Icecream (icecc)

This program is a commandline Monitor for Icecream (icecc) for an
overview of nodes connected to the icecream-scheduler, their loads
and other useful statistical information.
--- End Message ---
--- Begin Message ---
see 920298--- End Message ---

Bug#912633: marked as done (courier-imap-ssl: No supported cipher suite with the recent switch to TLS 1.3 in OpenSSL 1.1.1.)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 23:12:48 +0100
with message-id <75ef8e8b-57cb-967b-214b-63f3f0ccc...@bluegap.ch>
and subject line Re: Bug#912633: Solution
has caused the Debian Bug report #912633,
regarding courier-imap-ssl: No supported cipher suite with the recent switch to 
TLS 1.3 in OpenSSL 1.1.1.
to be marked as done.

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

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


-- 
912633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: courier-imap-ssl
Version: 4.18.1+0.78.0-2
Severity: grave
Justification: renders package unusable

After upgrading to the current version of OpenSSL in testing (1.1.1-2), when 
courier-imap-ssl is started
/var/log/mail.log fills with the following repeated many times:

mail imapd-ssl: No supported cipher suites have been found.

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

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

Versions of packages courier-imap-ssl depends on:
ii  courier-imap  4.18.1+0.78.0-2+b2

courier-imap-ssl recommends no packages.

courier-imap-ssl suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Soren,

thanks for your report, that has been very helpful.

On 1/19/19 6:30 AM, Soren Stoutner wrote:
> Tightening down the permission access is a good idea, so I applaud
> Courier for no longer using root access for reading certificates.  It
> would just have been helpful for the error message to point to a problem
> accessing the SSL certificate file instead of describing a problem with
> the cipher suites (which this isn't).

Testing this I figured that just above that line in the log
(/var/log/mail.log), courier reports pretty clear and helpful messages
regarding what's wrong with the pem file, e.g.: "No such file or
directory" or "Permission denied".

Kind Regards

Markus Wanner--- End Message ---

Bug#920545: marked as done (python-intervaltree breaks python-intervaltree-bio autopkgtest)

[Debian Bug Tracking System]

Your message dated Sat, 26 Jan 2019 23:35:24 +
with message-id 
and subject line Bug#920545: fixed in python-intervaltree-bio 1.0.1-3
has caused the Debian Bug report #920545,
regarding python-intervaltree breaks python-intervaltree-bio autopkgtest
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.)


-- 
920545: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920545
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-intervaltree, python-intervaltree-bio
Control: found -1 python-intervaltree/3.0.2-1
Control: found -1 python-intervaltree-bio/1.0.1-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: important
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of python-intervaltree the autopkgtest of
python-intervaltree-bio fails in testing when that autopkgtest is run
with the binary packages of python-intervaltree from unstable. It passes
when run with only packages from testing. In tabular form:
passfail
python-intervaltree from testing3.0.2-1
python-intervaltree-bio from testing1.0.1-2
all others  from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of
python-intervaltree to testing [1]. Due to the nature of this issue, I
filed this bug report against both packages. Can you please investigate
the situation and reassign the bug to the right package? If needed,
please change the bug's severity.

More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=python-intervaltree

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-intervaltree-bio/1785537/log.gz

=== FAILURES
===
 test_knownGene


def test_knownGene():
# To speed up testing, we'll download the file and reuse the
downloaded copy
knownGene_url =
'http://hgdownload.cse.ucsc.edu/goldenpath/hg19/database/knownGene.txt.gz'
# Mirror. Slightly faster and more stable, I believe:
knownGene_url =
'http://kt.era.ee/distribute/pyintervaltree/knownGene.txt.gz'

# To speed up testing, we'll download the file and reuse the
downloaded copy
knownGene_file, headers = urlretrieve(knownGene_url)

knownGene_localurl = 'file:///%s' % os.path.abspath(knownGene_file)
knownGene =
GenomeIntervalTree.from_table(url=knownGene_localurl, decompress=True) #
Py3 downloads .gz files to local files with names not ending with .gz
assert len(knownGene) == 82960
>   result = knownGene[b'chr1'].search(10, 138529)
E   AttributeError: 'IntervalTree' object has no attribute 'search'

.pc/offline-test-data.patch/tests/genomeintervaltree_test.py:28:
AttributeError
 
test_knownGene[file:///tmp/autopkgtest-lxc.z3ra1nek/downtmp/build.Szw/src/debian/data/]

base_url =
'file:///tmp/autopkgtest-lxc.z3ra1nek/downtmp/build.Szw/src/debian/data/'

def test_knownGene(base_url):
# To speed up testing, we'll download the file and reuse the
downloaded copy
knownGene_url = base_url + 'knownGene.txt.gz'

# To speed up testing, we'll download the file and reuse the
downloaded copy
knownGene_file, headers = urlretrieve(knownGene_url)

knownGene_localurl = 'file:///%s' % os.path.abspath(knownGene_file)
knownGene =
GenomeIntervalTree.from_table(url=knownGene_localurl, decompress=True) #
Py3 downloads .gz files to local files with names not ending with .gz
assert len(knownGene) == 82960
>   result = knownGene[b'chr1'].search(10, 138529)
E   AttributeError: 'IntervalTree' object has no attribute 'search'



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: python-intervaltree-bio
Source-Version: 1.0.1-3

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier 

Bug#764277: marked as done (Graphical DE task don't install any DE)

[Debian Bug Tracking System]

Your message dated Sun, 27 Jan 2019 00:35:38 +0100
with message-id <20190127003538.c22921770d206109eb54d...@mailbox.org>
and subject line [kfreebsd] Graphical DE task don't install any DE
has caused the Debian Bug report #764277,
regarding Graphical DE task don't install any DE
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.)


-- 
764277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: installation-reports
Version: 2.57
Severity: important

Dear Maintainer,

Testing debian-jessie-DI-b2-kfreebsd-amd64-netinst.iso under qemu-kvm,
if I only choose "Graphical desktop environment", d-i doesn't install any
DE, just something like desktop-base. It seems that I have to choose 
explicitly.
(Tested 2 times)

Attached is the output of dpkg --get-selections just after the first
reboot, and /var/log/installer/syslog.

-- Package-specific info:

Boot method: CD
Image version: debian-jessie-DI-b2-kfreebsd-amd64-netinst.iso
Date: 06 oct 2014

Machine: qemu-kvm on a DELL 780 host
Partitions: All in one partition


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:   [O]
Detect network card:[O]
Configure network:  [O]
Detect CD:  [O]
Load installer modules: [O]
Clock/timezone setup:   [O]
User/password setup:[O]
Detect hard drives: [O]
Partition hard drives:  [O]
No more 757986 nor 957987
Install base system:[O]
Install tasks:  [E]
Install boot loader:[O]
Overall install:[O]


==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION="Debian GNU/kFreeBSD installer"
DISTRIB_RELEASE="8 (jessie) - installer build 20141002"
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: GNU/kFreeBSD debian 10.0-1-amd64 #0 Tue, 20 May 2014 12:47:21 +0100 
x86_64 GNU/Linux
lspci -nn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC 
[Natoma] [8086:1237] (rev 02)
lspci -nn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA 
[Natoma/Triton II] [8086:7000]
lspci -nn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE 
[Natoma/Triton II] [8086:7010]
lspci -nn: 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI 
[8086:7113] (rev 03)
lspci -nn: 00:02.0 VGA compatible controller [0300]: Cirrus Logic GD 5446 
[1013:00b8]
lspci -nn: 00:03.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL-8100/8101L/8139 PCI Fast Ethernet Adapter [10ec:8139] (rev 20)
usb-list: Error: directory /sys/bus does not exist; is sysfs mounted?
kldstat: Id Refs AddressSize Name
kldstat:  1   16 0x8020 1142000  kfreebsd-10.gz
kldstat:  21 0x86012000 dc18 ext2fs.ko
kldstat:  31 0x8602 140df9   zfs.ko
kldstat:  41 0x86161000 2d61 opensolaris.ko
kldstat:  51 0x86164000 2374 nullfs.ko
kldstat:  61 0x86167000 88e3 fuse.ko
df: Filesystem   1K-blocks  Used Available Use% Mounted on
df: /dev/md0 72959 23515 49444  32% /
df: devfs1 1 0 100% /dev
df: devfs1 1 0 100% /dev
df: fdescfs  1 1 0 100% /dev/fd
df: linprocfs4 4 0 100% /proc
df: /sys 4 4 0 100% /sys
df: tmpfs   528600   140528460   0% /var/cache/anna
df: tmpfs   550504 22044528460   4% /var/lib/cdebconf
df: /dev/ada0s14813468   1424936   3003456  32% /target
df: devfs1 1 0 100% /target/dev
free: /usr/bin/report-hw: line 63: free: not found
/proc/cmdline: BOOT_IMAGE=/kernel ro root=302
/proc/cpuinfo: processor: 0
/proc/cpuinfo: vendor_id: GenuineIntel
/proc/cpuinfo: cpu family   : 6
/proc/cpuinfo: model: 2
/proc/cpuinfo: model name   : QEMU Virtual CPU version 1.1.2
/proc/cpuinfo: stepping : 3
/proc/cpuinfo: 
/proc/cpuinfo: processor: 1
/proc/cpuinfo: vendor_id: GenuineIntel
/proc/cpuinfo: cpu family   : 6
/proc/cpuinfo: model: 2
/proc/cpuinfo: model name   : QEMU Virtual CPU version 1.1.2
/proc/cpuinfo: stepping : 3
/proc/cpuinfo: 
/proc/cpuinfo: 

Bug#592770: marked as done (Daily build d-i + lenny + GRUB2: "Unable to install GRUB in /dev/sda")

[Debian Bug Tracking System]

Your message dated Sun, 27 Jan 2019 00:52:13 +0100
with message-id <20190127005213.1434b8cbb147d6325d4a1...@mailbox.org>
and subject line Re: Daily build d-i + lenny + GRUB2: "Unable to install GRUB 
in /dev/sda"
has caused the Debian Bug report #592770,
regarding Daily build d-i + lenny + GRUB2: "Unable to install GRUB in /dev/sda"
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.)


-- 
592770: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592770
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer
Version: 20100805-15:58
Severity: important

I am attempting to install lenny with GRUB2 using a daily build of d-i.
After being prompted whether or not to install to the MBR, I get a red-
screen error as follows:

[!!] Configuring grub-pc

Unable to install GRUB in /dev/sda
Executing 'grub-install /dev/sda' failed.

This is a fatal error.

Looking at the log on tty4, I see what appears to be the output of "grub-
install --help", and then

error: Running 'grub-install --no-floppy --force "/dev/sda"' failed.

The only instance of "grub-install" that I can find is under /target,
and if I invoke that as shown in the log, I get

Unrecognized option `--force'

If I drop the --force option, I get

/target/usr/sbin/grub-install: .: line 121: can't open 
'/usr/lib/grub/update-grub_lib'


--- End Message ---
--- Begin Message ---

"Daniel Richard G."  wrote:
> I am attempting to install lenny with GRUB2 using a daily build of d-i.
> After being prompted whether or not to install to the MBR, I get a red-
> screen error as follows:
> 
> [!!] Configuring grub-pc
> 
> Unable to install GRUB in /dev/sda
> Executing 'grub-install /dev/sda' failed.

Installing grub to a single /dev/sda used to be no problem these days, so this
is most probably an old report from times where grub2 had several problems.

Closing this bug (from 2010).


-- 
Holger Wansing 
PGP-Finterprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#837379: marked as done (mime-support: purge left files on system)

[Debian Bug Tracking System]

Your message dated Sun, 27 Jan 2019 10:12:45 +0900
with message-id <20190127011245.kqigwn52fkh6t...@bubu.plessy.net>
and subject line Re: Bug#837379: mime-support: purge left files on system
has caused the Debian Bug report #837379,
regarding mime-support: purge left files on 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.)


-- 
837379: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=837379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mime-support
Version: 3.60
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

by running piuparts for scons I get:

[quote]
0m52.2s DEBUG: Recording chroot state
0m54.7s DEBUG: Modified(user, group, mode, size, target): /var/lib/dpkg/info
/mime-support.list expected(root, root, - 100644, 40, None) != found(root,
root, - 100644, 855, None)
0m54.7s DEBUG: Modified(user, group, mode, size, target): /etc/mime.types
expected(root, root, - 100644, 24241, None) != found(root, root, - 100644,
24301, None)
0m54.8s ERROR: FAIL: Package purging left files on system:
  /etc/mailcap   not owned
  /usr/bin/compose -> run-mailcapowned by: mime-support
  /usr/bin/edit -> run-mailcap   owned by: mime-support
  /usr/bin/print -> run-mailcap  owned by: mime-support
  /usr/bin/run-mailcap   owned by: mime-support
  /usr/bin/see -> run-mailcapowned by: mime-support
  /usr/lib/mime/debian-view  owned by: mime-support
  /usr/lib/mime/mailcap  owned by: mime-support
  /usr/lib/mime/packages/mime-supportowned by: mime-support
  /usr/sbin/update-mime  owned by: mime-support
  /usr/share/bug/mime-support/   owned by: mime-support
  /usr/share/bug/mime-support/presubjowned by: mime-support
  /usr/share/doc/mime-support/   owned by: mime-support
  /usr/share/doc/mime-support/changelog.gz   owned by: mime-support
  /usr/share/doc/mime-support/copyright  owned by: mime-support
  /usr/share/man/man1/compose.1.gz -> run-mailcap.1.gz   owned by: mime-support
  /usr/share/man/man1/edit.1.gz -> run-mailcap.1.gz  owned by: mime-support
  /usr/share/man/man1/print.1.gz -> run-mailcap.1.gz owned by: mime-support
  /usr/share/man/man1/run-mailcap.1.gz   owned by: mime-support
  /usr/share/man/man1/see.1.gz -> run-mailcap.1.gz   owned by: mime-support
  /usr/share/man/man5/mailcap.5.gz   owned by: mime-support
  /usr/share/man/man5/mailcap.order.5.gz owned by: mime-support
  /usr/share/man/man8/update-mime.8.gz   owned by: mime-support
  /var/lib/dpkg/info/mime-support.conffiles  not owned
  /var/lib/dpkg/info/mime-support.md5sumsnot owned
  /var/lib/dpkg/info/mime-support.postinst   not owned
  /var/lib/dpkg/info/mime-support.prerm  not owned
  /var/lib/dpkg/info/mime-support.triggers   not owned

0m54.8s ERROR: FAIL: After purging files have been modified:
  /etc/mime.typesowned by: mime-support
  /var/lib/dpkg/info/mime-support.list   not owned

[/quote]



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

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

mime-support depends on no packages.

Versions of packages mime-support recommends:
ii  bzip2 1.0.6-8
ii  file  1:5.28-4
ii  xz-utils  5.1.1alpha+20120614-2.1

mime-support suggests no packages.

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJX1PouAAoJEAn4nzyModJd2FcQAMu4RJ7oyvGQ8m9PHmCgsusz
qx1uXXALQ23gHR5UR5HsPbvZnGcxQmZvQI3M7On3EyT4j+y88lR++wj7q6rr9du+
ec7WGAI+e89XwpJJyQCjY8eOispITFcTtVPjAGa6EmiQTrrcBjEa8YwYTUlOflVn
AXC/HOXCUhXXtIhsQRVhgolzHUqWgI3vZve1GDTrhGjyeTkMZX1gAkx9tUMfmBxm
m3r5I4ZludGes0I+fVi0UqFk/Pa2M2ISVI9/MNdE/OnLMO6JRer9pbpvuvqGqDCR
6DCtNFxU+H4LXVHh58JGSy11zHXu4qV75oDMvQX54Yl7sNACzqRTMMZmdhfe0jDn
uxzDe0AkeTk6VhQKyCFVKrzB4EUq0lB9cte4qh1Fhsj2QvFG0LLqFwbG63aKnP01
wuJi651empIDOfTxNCD8SH7zi2ymDVELf2+w38wZOtgqjiiLO25DFGXnklK4aS76
Aa+RS6QZ6Xr4zH78PD+FPWVIv1RSJvrozO2YlfAGpm4DRi9ckwC//seHSrEqdfJY
RzNR142HVYB9owKoh/8N8k899/OudreC9ym6PievNNJKJrxerXwjxYzEKaPIyNEy
siPIzocyZUiOxLuoGrwNRANNhcptQbfl29HdLw7Po2AU3w6gH7odwTeO5tkYy9Gi
YK2HBKhWzXHHNhpH4SEc
=1nuN
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
> Am Montag, den 12.12.2016, 21:40 +0900 schrieb Charles Plessy:
> > 
> > I am a bit puzzled: the main piuparts checks are running fine.
> > 
> >