Processed: tagging 905985

[Debian Bug Tracking System]

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

> tags 905985 + pending
Bug #905985 [pygame] pygame FTBFS with python 3.7
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 905985

[Debian Bug Tracking System]

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

> tags 905985 + ftbfs
Bug #905985 [pygame] pygame FTBFS with python 3.7
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: tagging 902035

[Debian Bug Tracking System]

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

> tags 902035 + fixed-upstream pending
Bug #902035 [pygame] pygame FTBFS on ppc64el, testsuite failure.
Added tag(s) pending and fixed-upstream.
> thanks
Stopping processing here.

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

Processed: tagging 902036

[Debian Bug Tracking System]

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

> tags 902036 + fixed-upstream pending
Bug #902036 [pygame] pygame FTBFS on s390x, testsuite failure.
Added tag(s) fixed-upstream and pending.
> thanks
Stopping processing here.

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

Bug#902035: Future of pygame in Debian.

[Dominik George]

Hi,

> […] tagged accordingly in the BTS […]

Oops, you are right. There are still two FTBFS bugs I failed to tag (but not
to fix).

Cheers,
Nik


signature.asc
Description: PGP signature

Bug#902036: Future of pygame in Debian.

[Dominik George]

Hi,

> pygame in Debian testing is currently python2 only, I am sure I am not
> alone in thinking this is not a good state of affairs given that pygame is
> frequently used for introducing people to programming.
> 
> pygame in sid has python3 support but is held back from migrating to
> testing by three rc bugs.  None of which have had any response from the
> maintainer.
> 
> One of those is a FTBFS with python 3.7 which is apparently fixed
> upstream.  So presumably the best thing to do about this one would be to
> update the package to the new upstream.  I may have a go at this myself
> but I'm not an expert in python packaging so I don't know how well I will
> do.
> 
> The other two are testsuite failures on architectures where frankly I
> doubt pygame has many users*.  I may also take a look at these after the
> new upstream version is dealt with but I don't think it's worth putting
> huge amounts of effort into pygame on architectures where I doubt it has
> any users and I equally don't think it should be allowed to block the
> availability of python3-pygame in testing on architectures people do
> actually care about, so if the root cause cannot be found quickly I would
> propose either disabling the tests on these architectures or requesting
> the ftpmasters remove the binaries.
> 
> Anyone have any comments or suggestions?

Yes. I am the maintainer whom you accuse of not maintaining the package.

Sorry to say that, but all your assumptions are wrong - all of the bugs you
mention are handled, tagged accordingly in the BTS, new uploads are prepared
in the packaging repository, and fixing last issues for the upload are being
coordinated with upstream, keeping the buster release schedule in mind:

  https://github.com/pygame/pygame/issues/543

Anything more I can do for you?

Cheers,
Nik


signature.asc
Description: PGP signature

Processed: your mail

[Debian Bug Tracking System]

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

> affects 902255 - src:chromium-browser
Bug #902255 [src:llvm-toolchain-6.0] llvm-toolchain-6.0: unicode non free 
license
Removed indication that 902255 affects src:chromium-browser
> thanks
Stopping processing here.

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

Processed: severity of 872039 is important

[Debian Bug Tracking System]

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

> severity 872039 important
Bug #872039 [initscripts] initscripts: umountfs leaves /var mounted (rw)
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#900596: marked as done ([chromium-browser] unicode non free license)

[Debian Bug Tracking System]

Your message dated Sat, 13 Oct 2018 04:36:47 +
with message-id 
and subject line Bug#900596: fixed in chromium-browser 69.0.3497.100-1
has caused the Debian Bug report #900596,
regarding [chromium-browser]  unicode non free license
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.)


-- 
900596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900596
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium-browser
Severity: serious
version: 67.0.3396.62-1 

The following file are non free:
third_party/breakpad/breakpad/src/common/convert_UTF.c
third_party/swiftshader/third_party/llvm-subzero/lib/Support/
ConvertUTF.cpp

Found by lintian, checked manually


The following file source files include material under a non-free license 
from Unicode Inc. Therefore, it is not possible to ship this in main or 
contrib.

This license does not grant any permission to modify the files (thus 
failing DFSG#3). Moreover, the license grant seems to attempt to restrict use 
to "products supporting the Unicode Standard" (thus failing DFSG#6).

In this case a solution is to use libicu and to remove this code by 
repacking.

If this is a false-positive, please report a bug against Lintian.

Refer to https://bugs.debian.org/823100 for details.

Severity: serious, Certainty: possible

Check: cruft, Type: source


signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
Source: chromium-browser
Source-Version: 69.0.3497.100-1

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

Debian distribution maintenance software
pp.
Michael Gilbert  (supplier of updated chromium-browser 
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, 13 Oct 2018 02:35:46 +
Source: chromium-browser
Binary: chromium chromium-l10n chromium-shell chromium-driver chromium-common
Architecture: source
Version: 69.0.3497.100-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Chromium Team 
Changed-By: Michael Gilbert 
Description:
 chromium   - web browser
 chromium-common - web browser - common resources used by the chromium packages
 chromium-driver - web browser - WebDriver support
 chromium-l10n - web browser - language packs
 chromium-shell - web browser - minimal shell
Closes: 884887 890392 900596 910842
Changes:
 chromium-browser (69.0.3497.100-1) unstable; urgency=medium
 .
   * New upstream stable release.
   * Update standards version to 4.2.1.
   * Clarify debugging section in README.debian (closes: #910842).
   * Remove ConvertUTF from the upstream tarball (closes: #900596).
   * Load all extensions installed to /usr/share/chromium/extensions.
 - Thanks to Michael Meskes (closes: #890392).
   * Remove audio_capture_enable setting from the default preferences
 (closes: #884887).
Checksums-Sha1:
 604e39afe72737fe00362dd838ba9b9f7224e52a 4209 
chromium-browser_69.0.3497.100-1.dsc
 3e5e5314634a3f60e705010134f6999e402d1c80 201109576 
chromium-browser_69.0.3497.100.orig.tar.xz
 54fa04f2f51c73b1a4dcae35028f171a6c6c9643 149500 
chromium-browser_69.0.3497.100-1.debian.tar.xz
 a6777fd1ce5f45926202f5319f58216593d31479 19556 
chromium-browser_69.0.3497.100-1_source.buildinfo
Checksums-Sha256:
 47f5ac6b3b64e4cbbd3dcd4738b1ca310ab5a833323e49e4d9b9c371db4c1d4d 4209 
chromium-browser_69.0.3497.100-1.dsc
 3bf7b016bd746383af6dff98a97825c85cc5e3cb71ded75cb0c1f34add53ae02 201109576 
chromium-browser_69.0.3497.100.orig.tar.xz
 de1a136dbaceed07526dc4dc947d35f79c07017ec6dafce05a45eff92373d900 149500 
chromium-browser_69.0.3497.100-1.debian.tar.xz
 a94fc495b8007d43d253d69de4df6eafa4a071daed187017f65004fb34d5bcad 19556 
chromium-browser_69.0.3497.100-1_source.buildinfo
Files:
 b24d14514f704a88e12586da9265bef1 4209 web optional 
chromium-browser_69.0.3497.100-1.dsc
 467ab252f908ac0dace042c8fe5fe86f 201109576 web optional 
chromium-browser_69.0.3497.100.orig.tar.xz
 ccc65f672d2016336472894a9b123135 149500 web optional 
chromium-browser_69.0.3497.100-1.d

Bug#899697: marked as done (swfmill: Invalid maintainer address pkg-flash-de...@lists.alioth.debian.org)

[Debian Bug Tracking System]

Your message dated Sat, 13 Oct 2018 03:37:50 +
with message-id 
and subject line Bug#899697: fixed in swfmill 0.3.6-1
has caused the Debian Bug report #899697,
regarding swfmill: Invalid maintainer address 
pkg-flash-de...@lists.alioth.debian.org
to be marked as done.

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

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


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

Dear uploader of swfmill,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: swfmill
Source-Version: 0.3.6-1

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

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

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

Debian distribution maintenance software
pp.
Miriam Ruiz  (supplier of updated swfmill 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, 13 Oct 2018 04:54:02 +0200
Source: swfmill
Binary: swfmill
Architecture: source amd64
Version: 0.3.6-1
Distribution: unstable
Urgency: medium
Maintainer: Miriam Ruiz 
Changed-By: Miriam Ruiz 
Description:
 swfmill- xml2swf and swf2xml processor
Closes: 899697
Changes:
 swfmill (0.3.6-1) unstable; urgency=medium
 .
   * New upstream release
   * Set myself as the maintainer again. Closes: #899697
   * Upgraded Standards-Version from 3.9.8 to 4.2.1.2
   * Removed suggestion for mtasc (obsolete)
Checksums-Sha1:
 6ba7b3ce670a31cc6bc1f0d79dec929da1d7d090 1816 swfmill_0.3.6-1.dsc
 33a078987a9e202d11f1bbce1adb6073ff5c 1448824 swfmill_0.3.6.orig.tar.gz
 0d1799f7eed439eb954f80deba7d588077e454cd 24332 swfmill_0.3.6-1.debian.tar.xz
 3528ac2de7f85de452483eebcf0b762e57aa4662 2681668 
swfmill-dbgsym_0.3.6-1_amd64.deb
 4e31d2335b1bd3036c7c2180c87997f3a40d92e5 6937 swfmill_0.3.6-1_amd64.buildinfo
 891a7bb81bb41fbe5318af79c416460e50a91a62 352536 swfmill_0.3.6-1_amd64.deb
Checksums-Sha256:
 729150d05fa188cd6f4835280645bdabfadf988424c8ad151f321d0d5b8f2299 1816 
swfmill_0.3.6-1.dsc
 db24f63963957faec02bb14b8b61cdaf7096774f8cfdeb9d3573e2e19231548e 1448824 
swfmill_0.3.6.orig.tar.gz
 974ed37c060798da103f2ba8a488a5ee3cd4198d560b97ab1386bf65c6a46768 24332 
swfmill_0.3.6-1.

Bug#896759: [gui-ufw] FTBFS and no maintainer activity since 2016

[Miriam Ruiz]

I'm not particularly interested in maintaining the package and, as I'm
not using it anymore myself. I would be terribly glad if you wanted to
take care of it.

Greetings,
Miry

El mié., 3 oct. 2018 a las 23:57, Samuel Henrique
() escribió:
>
> Hello Everyone, I'm not sure if I should have CC'ed everyone, sorry if
> I shouldn't.
>
> Today a Brazilian user was asking help installing gufw on Testing, he
> said it was only on unstable and stable, I decided to have a look and
> discovered:
>
> * The last upload was a NMU on 2017-05-13
> * The last maintainer upload was on 2016-11-06
> * Package currently has an very easy fix FTBFS bug opened since April this 
> year
> * One of the maintainers (Devid) is still maintaining the package on
> Ubuntu and doing uploads
> * Deivid had to get sponsor for their uploads on Debian
>
> I would really like to see the status of the package be the same as of
> on Ubuntu, being up to date and without bugs.
>
> Deivid and Miriam, are you still willing to maintain the package? I
> can see that Deivid already have DM permission on some packages, you
> could get one for gui-fw, or at least I could sponsor your uploads (if
> Miriam stopped doing so).
>
> In the last case, I could have a look and put the package up to date
> with Ubuntu's.
>
> Thanks for your consideration.
> --
> Samuel Henrique 

Bug#902035: Future of pygame in Debian.

[peter green]

pygame in Debian testing is currently python2 only, I am sure I am not alone in 
thinking this is not a good state of affairs given that pygame is frequently 
used for introducing people to programming.

pygame in sid has python3 support but is held back from migrating to testing by 
three rc bugs. None of which have had any response from the maintainer.

One of those is a FTBFS with python 3.7 which is apparently fixed upstream. So 
presumably the best thing to do about this one would be to update the package 
to the new upstream. I may have a go at this myself but I'm not an expert in 
python packaging so I don't know how well I will do.

The other two are testsuite failures on architectures where frankly I doubt 
pygame has many users*. I may also take a look at these after the new upstream 
version is dealt with but I don't think it's worth putting huge amounts of 
effort into pygame on architectures where I doubt it has any users and I 
equally don't think it should be allowed to block the availability of 
python3-pygame in testing on architectures people do actually care about, so if 
the root cause cannot be found quickly I would propose either disabling the 
tests on these architectures or requesting the ftpmasters remove the binaries.

Anyone have any comments or suggestions?

*Both are very expensive architectures driven by IBM.

Bug#828481: ori: FTBFS with openssl 1.1.0

[Afif Elghraoui]

على ٣‏/٢‏/١٤٤٠ هـ ‫٤:٣٣ م، كتب Moritz Mühlenhoff:

On Fri, Oct 13, 2017 at 12:52:55AM -0400, Afif Elghraoui wrote:





What's the status? ori hasn't been uploaded since 21 months, is there
any progress?



There's been no development activity upstream since then either. I think 
it's time I filed for this package's removal.


regards
Afif

--
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name

Bug#897806: lmms: ftbfs with GCC-8

[Javier Serrano Polo]

Someone should give me access to the repository, user jasp-guest.

smime.p7s
Description: S/MIME cryptographic signature

Processed: reassign 909218 to nvidia-graphics-drivers

[Debian Bug Tracking System]

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

> reassign 909218 nvidia-graphics-drivers
Bug #909218 [nvidia-xconfig] nvidia-xconfig: Files section missing ModulePath 
entries break GLX upon installing libgl1-nvidia-glx (required by Steam)
Bug reassigned from package 'nvidia-xconfig' to 'nvidia-graphics-drivers'.
No longer marked as found in versions nvidia-xconfig/390.25-1.
Ignoring request to alter fixed versions of bug #909218 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#872885: netty-tcnative-1.1: Please migrate to openssl1.1 in Buster

[Emmanuel Bourg]

Le 12/10/2018 à 22:33, Moritz Mühlenhoff a écrit :

> src:tcnetty has been fixed wrt OpenSSL 1.1 and netty-tcnative-1.1 has no
> reverse dependencies in the archive. Shall we remove it from the archive?

Actually netty-tcnative-1.1 is still needed by netty-3.9.

There are 3 rdeps left for netty-3.9:
- maven-indexer (through aether), but it isn't used and could be removed
- tycho (through aether again), I'm working on an upgrade no longer
depending on it
- libgpars-groovy-java which is used by groovy. I don't have a solution
for this one yet.

Emmanuel Bourg

Processed: clone elpy FTBFS randomly bug

[Debian Bug Tracking System]

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

> clone 910311 -1
Bug #910311 [src:elpy] elpy FTBFS randomly: test 
elpy-promise-wait-should-return-early-for-resolved-promise fails
Warning: Unknown package 'src:elpy'
Bug 910311 cloned as bug 910897
Warning: Unknown package 'src:elpy'
> retitle -1 elpy: reenable 
> elpy-promise-wait-should-return-early-for-resolved-promise
Bug #910897 [src:elpy] elpy FTBFS randomly: test 
elpy-promise-wait-should-return-early-for-resolved-promise fails
Warning: Unknown package 'src:elpy'
Changed Bug title to 'elpy: reenable 
elpy-promise-wait-should-return-early-for-resolved-promise' from 'elpy FTBFS 
randomly: test elpy-promise-wait-should-return-early-for-resolved-promise 
fails'.
Warning: Unknown package 'src:elpy'
> severity -1 important
Bug #910897 [src:elpy] elpy: reenable 
elpy-promise-wait-should-return-early-for-resolved-promise
Warning: Unknown package 'src:elpy'
Severity set to 'important' from 'serious'
Warning: Unknown package 'src:elpy'
> thanks
Stopping processing here.

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

Bug#910896: syslog-ng FTBFS, testsuite failure.

[peter green]

Package: syslog-ng
Version: 3.13.2-4.1
Severity: serious

syslog-ng failed to build on all release architectures during binnmus for the 
hiredis transition. The failure seems to be in a python related test but the 
build log doesn't seem to indicate why exactly it failed.

https://buildd.debian.org/status/package.php?p=syslog-ng&suite=unstable
https://buildd.debian.org/status/fetch.php?pkg=syslog-ng&arch=amd64&ver=3.13.2-4.1%2Bb1&stamp=1539246825&raw=0


FAIL: modules/python/pylib/test_pylib
=

make[7]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
nosetests ../../modules/python/pylib/syslogng

--
Ran 108 tests in 0.243s

OK
pep8 --ignore=E501 ../../modules/python/pylib/syslogng
../../modules/python/pylib/syslogng/debuggercli/macrocompleter.py:138:17: W504 
line break after binary operator
../../modules/python/pylib/syslogng/debuggercli/macrocompleter.py:139:17: W504 
line break after binary operator
../../modules/python/pylib/syslogng/debuggercli/macrocompleter.py:191:28: W504 
line break after binary operator
../../modules/python/pylib/syslogng/debuggercli/tablexer.py:76:17: W504 line 
break after binary operator
../../modules/python/pylib/syslogng/debuggercli/tablexer.py:77:18: W504 line 
break after binary operator
make[7]: *** [Makefile:20215: python-pep8] Error 1
FAIL modules/python/pylib/test_pylib.sh (exit status: 2)

Bug#899060: FTBFS: even if tests pass, dh_auto_test fails

[Sunil Mohan Adapa]

tags 899060 +patch
thanks

Hello,

The attached patch seems to fix the problem.

It appears that if a socket that socat wants to listen on exists, socat
fails (socat(1)). When socat finishes by itself, ssh-socket will be
unlinked but if it is killed for some reason than socket file is not
unlinked. The attached patch tells socat to remove the socket before
starting its normal activity.

I got the hint towards this when I stopped cleaning the temp home
directory and read the sshd.log after a failure. I was to reproduce the
problem with high success rate before the patch and after the applying
the patch, I can't reproduce it building 10 times. All of the logs on
this bug report (that are not related to OpenSSL pem2openpgp, fixed in
#909700) are similar and should get fixed with this patch. I didn't
investigate why this behavior was not seen earlier (socat changes?
something else?).

I believe this is the last of the unfixed serious issues. I think this
package is set to cause removal issues for other packages in testing.
Please consider uploading this fix, along with other unreleased fixes, soon.

Thank you,

-- 
Sunil
From fcd96673225bc488494cf6c2979b21e6e1778299 Mon Sep 17 00:00:00 2001
From: Sunil Mohan Adapa 
Date: Fri, 12 Oct 2018 13:01:24 -0700
Subject: [PATCH] tests: Ensure that stale sockets don't fail socat (Closes:
 #899060)

---
 tests/basic | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tests/basic b/tests/basic
index 9102bb9..3afe008 100755
--- a/tests/basic
+++ b/tests/basic
@@ -63,7 +63,7 @@ ssh_test() {
 
 # start the ssh daemon on the socket
 echo "# starting ssh server..."
-socat EXEC:"/usr/sbin/sshd -f ${SSHD_CONFIG} -i -D -e" "UNIX-LISTEN:${SOCKET}" 2> "$TEMPDIR"/sshd.log &
+socat EXEC:"/usr/sbin/sshd -f ${SSHD_CONFIG} -i -D -e" "UNIX-LISTEN:${SOCKET},unlink-early" 2> "$TEMPDIR"/sshd.log &
 SSHD_PID="$!"
 
 # wait until the socket is created before continuing
-- 
2.19.1



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#899060: FTBFS: even if tests pass, dh_auto_test fails

[Debian Bug Tracking System]

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

> tags 899060 +patch
Bug #899060 [src:monkeysphere] FTBFS: even if tests pass, dh_auto_test fails
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#879917: marked as done (libgambit4-dev: fails to upgrade from 'sid' - trying to overwrite /usr/include/gambit.h)

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 20:44:22 +
with message-id 
and subject line Bug#879917: fixed in gambc 4.8.8-3.1
has caused the Debian Bug report #879917,
regarding libgambit4-dev: fails to upgrade from 'sid' - trying to overwrite 
/usr/include/gambit.h
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.)


-- 
879917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgambit4-dev
Version: 4.8.8-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#s-replaces

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

  Selecting previously unselected package libgambit4-dev.
  Preparing to unpack .../libgambit4-dev_4.8.8-1_amd64.deb ...
  Unpacking libgambit4-dev (4.8.8-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libgambit4-dev_4.8.8-1_amd64.deb (--unpack):
   trying to overwrite '/usr/include/gambit.h', which is also in package 
libgambc4-dev 4.2.8-2+b1
  Errors were encountered while processing:
   /var/cache/apt/archives/libgambit4-dev_4.8.8-1_amd64.deb


cheers,

Andreas


libgambc4-dev=4.2.8-2+b1_libgambit4-dev=4.8.8-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: gambc
Source-Version: 4.8.8-3.1

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 27 Sep 2018 22:26:49 +0300
Source: gambc
Binary: gambc libgambit4 libgambit4-dev gambc-doc
Architecture: source
Version: 4.8.8-3.1
Distribution: unstable
Urgency: medium
Maintainer: Abdelhakim Qbaich 
Changed-By: Adrian Bunk 
Description:
 gambc  - Gambit Scheme interpreter and compiler
 gambc-doc  - documentation for the Gambit interpreter and compiler
 libgambit4 - Shared libraries for the Gambit interpreter and compiler
 libgambit4-dev - Header file and link for the Gambit shared library
Closes: 879917
Changes:
 gambc (4.8.8-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add the missing Breaks. (Closes: #879917)
Checksums-Sha1:
 2d3aebea11b25e1735ca7f1e310280cd24c62d0d 1984 gambc_4.8.8-3.1.dsc
 a5a4495c9f8287950f94ecd22adb75e3a9388aca 48568 gambc_4.8.8-3.1.debian.tar.xz
Checksums-Sha256:
 9a9c2305174aeaea0c4f1e75a899f0bf4fb90db82141acb7b8c31cc4a277c82a 1984 
gambc_4.8.8-3.1.dsc
 41af51c4d773071d406f39a1871b77fce1277c74b6e289330937a2a7d91fb9b2 48568 
gambc_4.8.8-3.1.debian.tar.xz
Files:
 c321b997af1284bc24f706841bff3cfd 1984 devel optional gambc_4.8.8-3.1.dsc
 6191bec7ceb0cc8eab523f08f4064c7f 48568 devel optional 
gambc_4.8.8-3.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlutMVgACgkQiNJCh6LY
mLGB4w//fq7sbuGEuipv4c6As+XsBXA+kRqqhX+ULFU7JIyRw0fqZwxbfKhRzwTE
e+YBQLdIkXesqW7RwWD0/3WfwSIjotBKApeVzDnpvFL8n0TJVXPsvpQuqrtmEn/X
ZljVQhy6VX5EdKEUVha8XgWd92eJxoMF4qkd2VwgC2xAe/Li+YaQe48ngNWGmXg8
A1kRqp2fofkuU7nCckzQ5S/P0ICGz68RLW7YF6EnESCCsW4D6D6O1wzFWLrpSnrQ
HPXy/gMvrghlOm6Ea7O186eGQ480ikD3Su5B2Nth5rIrSc7OqCvI4cFw4HTVb+LF
WJt32r8lZ2ouwn8AjR1Y9zwwsnY8VadkCUbzDtJo6pFyWKwpOn+hR6wR9loCmNC4
ghYHjtAtaazXRqQqVq11AU3+TnCMMHfktgKI6c6UytNzykP3dG4yBqGa3HQLV5E6
vgmdz8MysjUQ9BZ4Hdt8TaWVEPa6nvUmkuUYcNig3gmscayFxxhjaUJixK5yqPa3
ddudTBoIT3wFPY/vYk2xp+8shWPlSk1/tvEbvqnbPV7ZqXXTMkekcU7G2/2tRPsb
hGd2u1bLTCS6N2xQ0J3jwXMPhIpuUfShBK7HKxhpESsgnNw9tApeqJm6HyI6TUG8
5j1IgCenR7yJ67Yqn4V7iw8f08XMvIgaqWz9/wAdoTeHQMNc328=
=toZO
-END PGP SIGNATURE End Message ---

Bug#828481: ori: FTBFS with openssl 1.1.0

[Moritz Mühlenhoff]

On Fri, Oct 13, 2017 at 12:52:55AM -0400, Afif Elghraoui wrote:
> 
> 
> على الخميس 12 تشرين الأول 2017 ‫17:44، كتب Sebastian Andrzej Siewior:
> > Hi,
> > 
> > this is a remainder about the openssl transition [0]. We really want to
> > remove libssl1.0-dev from unstable for Buster. I will raise the severity
> > of this bug to serious in a month. Please react before that happens.
> > 
> > [0] https://bugs.debian.org/871056#55
> > 
> 
> I've just followed up with upstream, who would actually like to remove
> the dependency on openssl altogether.

What's the status? ori hasn't been uploaded since 21 months, is there
any progress?

Cheers,
Moritz

Bug#872885: netty-tcnative-1.1: Please migrate to openssl1.1 in Buster

[Moritz Mühlenhoff]

n Thu, Oct 12, 2017 at 11:44:47PM +0200, Sebastian Andrzej Siewior wrote:
> 
> this is a remainder about the openssl transition [0]. We really want to
> remove libssl1.0-dev from unstable for Buster. I will raise the severity
> of this bug to serious in a month. Please react before that happens.

Emmanuel,
src:tcnetty has been fixed wrt OpenSSL 1.1 and netty-tcnative-1.1 has no
reverse dependencies in the archive. Shall we remove it from the archive?

Cheers,
Moritz

Bug#910891: nis build against libgdbm.6 doesn't work as server on a sysvinit system

[Elimar Riesebieter]

Package: nis
Version: 3.17.1-3+b1
Severity: serious
Justification: 5 (f)


Dear maintainer,

since 3.17.1-3+b1 nis dosn't work as server on a sysvinit system.

3.17.1-3+b1:
$ ldd /usr/sbin/ypbind

linux-vdso.so.1 (0x7ffd9699)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7ff8ce6ff000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7ff8ce6de000)
libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x7ff8ce6c5000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7ff8ce508000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7ff8ce4fe000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7ff8ce2d8000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7ff8ce0b9000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7ff8cdd9d000)
/lib64/ld-linux-x86-64.so.2 (0x7ff8ce7a5000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7ff8cdd98000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7ff8cdd76000)



3.17.1-2:
$ ldd /usr/sbin/ypbind

linux-vdso.so.1 (0x7ffd11af2000)
libdbus-glib-1.so.2 => /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2 
(0x7fd5fb4c4000)
libdbus-1.so.3 => /lib/x86_64-linux-gnu/libdbus-1.so.3 
(0x7fd5fb471000)
libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fd5fb41d000)
libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7fd5fb30)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7fd5fb274000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fd5fb253000)
libnsl.so.1 => /lib/x86_64-linux-gnu/libnsl.so.1 (0x7fd5fb238000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fd5fb07b000)
libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fd5faed7000)
libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 
(0x7fd5facce000)
libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x7fd5fac5a000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x7fd5fac5)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7fd5faa28000)
liblz4.so.1 => /usr/lib/x86_64-linux-gnu/liblz4.so.1 
(0x7fd5fa80b000)
libgcrypt.so.20 => /lib/x86_64-linux-gnu/libgcrypt.so.20 
(0x7fd5fa4ef000)
/lib64/ld-linux-x86-64.so.2 (0x7fd5fb509000)
libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 
(0x7fd5fa4e9000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7fd5fa2cb000)
libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 
(0x7fd5fa0a3000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7fd5fa088000)
libmount.so.1 => /lib/x86_64-linux-gnu/libmount.so.1 
(0x7fd5fa02c000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fd5fa027000)
libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 
(0x7fd5fa005000)
libblkid.so.1 => /lib/x86_64-linux-gnu/libblkid.so.1 
(0x7fd5f9fb3000)
libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x7fd5f9fa8000)

Elimar

-- Package-specific info:

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

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

Versions of packages nis depends on:
ii  debconf [debconf-2.0]  1.5.69
ii  hostname   3.21
ii  libc6  2.27-6
ii  libgdbm6   1.18-2
ii  libsystemd0239-10
ii  lsb-base   9.20170808
ii  make   4.2.1-1.2
ii  netbase5.4
ii  rpcbind [portmap]  0.2.3-0.6

nis recommends no packages.

Versions of packages nis suggests:
ii  nscd  2.27-6

-- Configuration Files:
/etc/ypserv.securenets changed [not included]
/var/yp/Makefile changed [not included]

Bug#908947: youtube-dl: backport youtube-dl to recent version for stretch

[Holger Levsen]

Dear Rogério, dear release team, dear backports-admins,

On Sun, Sep 16, 2018 at 02:57:30PM +0200, Thierry wrote:
> Package: youtube-dl
> Version: 2017.05.18.1-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
> the version of youtube-dl that is shipped with stretch does not work
> anymore for the youtube website, making the package unusable for some
> videos. It should be updated to a more recent version. If this is not
> possible by Debian policy, stretch-backport should provide a recent
> version.

(it's not only youtube that's broken but also others..)

For the 2nd time in 2 months today I have installed a local backport of
youtube-dl on my machine (and soon will do the same at friends...) so by
now I'm also pretty close to upload youtube 2018.09.10-1~bpo9+1 to
stretch-backports to solve this (better) for "me" (and others) but then
I really do believe this should be fixed by uploading
2018.09.10-1~deb9u1 to stable(-updates).

what's your stance on this? 

I'm happy to prepare uploads to either if that helps. (and a proper bug
if the stable updates route is chosen.)


-- 
cheers,
Holger

---
   holger@(debian|reproducible-builds|layer-acht).org
   PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C


signature.asc
Description: PGP signature

Bug#910808: sagemath: Sage crashes on startup, seems to be compiled against wrong libsingular version

[Adrian Bunk]

Control: reopen -1
Control: reassign -1 libsingular4 1:4.1.1-p2+ds-2
Control: retitle -1 libsingular4 must change packagename when sonames change
Control: affects -1 sagemath

On Thu, Oct 11, 2018 at 05:55:06PM +0200, Tobias Hansen wrote:
> It's not a bug in sagemath. The problem is that the singular library package 
> was not renamed even though the library name changed.
> However this is only a problem for people who somehow do partial updates.

People who use testing are also victims of this kind of bugs.

If the soname of included libraries changes with every minor release, 
then the package name of the package also has to change.

Reopening and reassigning to libsingular4.

> Best,
> Tobias

cu
Adrian

-- 

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

Processed: Re: Bug#910808: sagemath: Sage crashes on startup, seems to be compiled against wrong libsingular version

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #910808 {Done: Tobias Hansen } [sagemath] sagemath: 
Sage crashes on startup, seems to be compiled against wrong libsingular version
Bug reopened
Ignoring request to alter fixed versions of bug #910808 to the same values 
previously set
> reassign -1 libsingular4 1:4.1.1-p2+ds-2
Bug #910808 [sagemath] sagemath: Sage crashes on startup, seems to be compiled 
against wrong libsingular version
Bug reassigned from package 'sagemath' to 'libsingular4'.
No longer marked as found in versions sagemath/8.3-3.
Ignoring request to alter fixed versions of bug #910808 to the same values 
previously set
Bug #910808 [libsingular4] sagemath: Sage crashes on startup, seems to be 
compiled against wrong libsingular version
Marked as found in versions singular/1:4.1.1-p2+ds-2.
> retitle -1 libsingular4 must change packagename when sonames change
Bug #910808 [libsingular4] sagemath: Sage crashes on startup, seems to be 
compiled against wrong libsingular version
Changed Bug title to 'libsingular4 must change packagename when sonames change' 
from 'sagemath: Sage crashes on startup, seems to be compiled against wrong 
libsingular version'.
> affects -1 sagemath
Bug #910808 [libsingular4] libsingular4 must change packagename when sonames 
change
Added indication that 910808 affects sagemath

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

Processed: Re: Bug#910517: monero: FTBFS on i386: compiler runs our of memory

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #910517 [src:monero] monero: FTBFS on i386: compiler runs our of memory
Warning: Unknown package 'src:monero'
Added tag(s) patch.
Warning: Unknown package 'src:monero'

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

Bug#910517: monero: FTBFS on i386: compiler runs our of memory

[Adrian Bunk]

Control: tags -1 patch

On Sun, Oct 07, 2018 at 05:19:53PM +0200, Emilio Pozuelo Monfort wrote:
> Source: monero
> Version: 0.12.3.0~dfsg-2
> Severity: serious
> 
> Your package failed to build on i386:
> 
> cd "/<>/obj-i686-linux-gnu/contrib/epee/src" && /usr/bin/c++  
> -DAUTO_INITIALIZE_EASYLOGGINGPP -DBLOCKCHAIN_DB=DB_LMDB 
> -DDEFAULT_DB_TYPE=\"lmdb\" -DHAVE_EXPLICIT_BZERO -DHAVE_PCSC -DHAVE_READLINE 
> -DHAVE_STRPTIME -DPER_BLOCK_CHECKPOINT 
> -I"/<>/external/rapidjson/include" 
> -I"/<>/external/easylogging++" -I"/<>/src" 
> -I"/<>/contrib/epee/include" -I"/<>/external" 
> -I"/<>/obj-i686-linux-gnu/translations" 
> -I"/<>/external/db_drivers/liblmdb" -I/usr/include/PCSC  -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fno-strict-aliasing 
> -DNO_AES -std=c++11 -D_GNU_SOURCE   -Wall -Wextra -Wpointer-arith -Wundef 
> -Wvla -Wwrite-strings -Wno-error=extra -Wno-error=deprecated-declarations 
> -Wno-unused-parameter -Wno-unused-variable -Wno-error=unused-variable 
> -Wno-error=undef -Wno-error=uninitialized -Wlogical-op 
> -Wno-error=maybe-uninitialized -Wno-error=cpp -Wno-reorder 
> -Wno-missing-field-initializers   -fPIC  -Wformat -Wformat-security 
> -fstack-protector -fstack-protector-strong -fno-strict-aliasing   -Werror -o 
> CMakeFiles/epee.dir/network_throttle.cpp.o -c 
> "/<>/contrib/epee/src/network_throttle.cpp"
> 
> cc1plus: out of memory allocating 27008520 bytes after a total of 83218432 
> bytes
> make[3]: *** [src/mnemonics/CMakeFiles/obj_mnemonics.dir/build.make:66: 
> src/mnemonics/CMakeFiles/obj_mnemonics.dir/electrum-words.cpp.o] Error 1
> make[3]: Leaving directory '/<>/obj-i686-linux-gnu'
> 
> Full logs at https://buildd.debian.org/status/package.php?p=monero

The usual -g1 workaround for this gcc regression also helps here,
additionally work around the libatomic gcc bug on some architectures:

--- debian/rules.old2018-10-08 22:51:57.676638667 +
+++ debian/rules2018-10-09 00:20:51.142297976 +
@@ -1,5 +1,12 @@
 #!/usr/bin/make -f
 
+ifeq ($(DEB_HOST_ARCH_BITS),32)
+export DEB_CXXFLAGS_MAINT_APPEND = -g1
+endif
+ifneq (,$(filter $(DEB_HOST_ARCH), armel m68k mips mipsel powerpc powerpcspe 
sh4))
+export DEB_LDFLAGS_MAINT_APPEND=-latomic
+endif
+
 #testsuite needs writable $HOME
 FAKEHOME = $(CURDIR)/debian/fakehome
 

> Emilio

cu
Adrian

-- 

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

Bug#904459: Uploading soon?

[Tollef Fog Heen]

]] Daniel Baumann 

> On 10/12/2018 09:56 AM, Tollef Fog Heen wrote:
> > any chance you could find time to get this uploaded soon? It'd be great
> > to have netdata back in testing (and in buster when it gets released).
> 
> yep, working on it.. will take a couple of days though. having netdata
> in buster is important to me too.

Thank you! :-)

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> unarchive 896893
Bug #896893 {Done: James Cowgill } [release.debian.org] 
transition: ffmpeg
Unarchived Bug 896893
> forcemerge 888357 910795
Bug #888357 [src:opal] opal: FTBFS with FFmpeg 4.0
Bug #910795 [src:opal] libopal3.10.10: package uninstallable
896893 was blocked by: 888385 888345 888353 888360 888343 888344 888384 888356 
896823 888335 888357 888386 888326 888352 888338 888328 888332 888381 888325 
904104 904267 888330 888376 888375 888370 888380 888374 888329 888336 888383 
888378 888372 888371 888346 888367 888349 888350 888364 888389 888377 896824 
896825 888373 888331 888347 888382 888333 888359 888362 888337 888388 888365 
888363 888358 888340 888366
896893 was not blocking any bugs.
Added blocking bug(s) of 896893: 910795
Added indication that 910795 affects libopal3.10.10
Marked as found in versions opal/3.10.10~dfsg2-2.1.
Added tag(s) patch, buster, ftbfs, and sid.
Merged 888357 910795
> affects 888357 libopal3.10.10
Bug #888357 [src:opal] opal: FTBFS with FFmpeg 4.0
Bug #910795 [src:opal] libopal3.10.10: package uninstallable
Ignoring request to set affects of bug 888357 to the same value previously set
Ignoring request to set affects of bug 910795 to the same value previously set
> thanks
Stopping processing here.

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

Processed (with 1 error): Merge duplicates

[Debian Bug Tracking System]

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

> reassign 910795 src:opal
Bug #910795 [libopal3.10.10] libopal3.10.10: package uninstallable
Bug reassigned from package 'libopal3.10.10' to 'src:opal'.
Ignoring request to alter found versions of bug #910795 to the same values 
previously set
Ignoring request to alter fixed versions of bug #910795 to the same values 
previously set
> forcemerge 888357 910795
Bug #888357 [src:opal] opal: FTBFS with FFmpeg 4.0
Bug #910795 [src:opal] libopal3.10.10: package uninstallable
Severity set to 'serious' from 'grave'
Failed to forcibly merge 888357: Failure while trying to adjust bugs, please 
report this as a bug: Not altering archived bugs; see unarchive..
 at /usr/local/lib/site_perl/Debbugs/Control.pm line 2133.

> affects 888357 libopal3.10.10
Bug #888357 [src:opal] opal: FTBFS with FFmpeg 4.0
Added indication that 888357 affects libopal3.10.10
> thanks
Stopping processing here.

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

Processed: fixed 910182 in 18.3-1

[Debian Bug Tracking System]

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

> fixed 910182 18.3-1
Bug #910182 {Done: Thomas Goirand } [src:cloud-init] 
cloud-init FTBFS: tests fail
Marked as fixed in versions cloud-init/18.3-1.
> thanks
Stopping processing here.

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

Bug#910887: imagemagick: CVE-2018-16412

[Salvatore Bonaccorso]

Given VE-2018-16413 is fixed with the same commit, rettitled this bug
to just use it for both CVEs.

Regards,
Salvatore

Processed: imagemagick: CVE-2018-16645

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 8:6.9.7.4+dfsg-11+deb9u6
Bug #910889 [src:imagemagick] imagemagick: CVE-2018-16645
The source 'imagemagick' and version '8:6.9.7.4+dfsg-11+deb9u6' do not appear 
to match any binary packages
Marked as fixed in versions imagemagick/8:6.9.7.4+dfsg-11+deb9u6.

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

Bug#910889: imagemagick: CVE-2018-16645

[Salvatore Bonaccorso]

Source: imagemagick
Version: 8:6.9.7.4+dfsg-1
Severity: grave
Tags: patch security upstream
Forwarded: https://github.com/ImageMagick/ImageMagick/issues/1268
Control: fixed -1 8:6.9.7.4+dfsg-11+deb9u6

[adding already the fixed version for the pending stretch-security DSA
version]

Hi,

The following vulnerability was published for imagemagick.

CVE-2018-16645[0]:
| There is an excessive memory allocation issue in the functions
| ReadBMPImage of coders/bmp.c and ReadDIBImage of coders/dib.c in
| ImageMagick 7.0.8-11, which allows remote attackers to cause a denial
| of service via a crafted image file.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16645
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16645
[1] https://github.com/ImageMagick/ImageMagick/issues/1268

Regards,
Salvatore

Bug#910888: imagemagick: CVE-2018-16644

[Salvatore Bonaccorso]

Source: imagemagick
Version: 8:6.9.7.4+dfsg-1
Severity: grave
Tags: patch security upstream
Forwarded: https://github.com/ImageMagick/ImageMagick/issues/1269
Control: fixed -1 8:6.9.7.4+dfsg-11+deb9u6

[adding already the fixed version for the already pending
stretch-security DSA version]

Hi,

The following vulnerability was published for imagemagick.

CVE-2018-16644[0]:
| There is a missing check for length in the functions ReadDCMImage of
| coders/dcm.c and ReadPICTImage of coders/pict.c in ImageMagick
| 7.0.8-11, which allows remote attackers to cause a denial of service
| via a crafted image.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16644
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16644
[1] https://github.com/ImageMagick/ImageMagick/issues/1269

Regards,
Salvatore

Processed: imagemagick: CVE-2018-16644

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 8:6.9.7.4+dfsg-11+deb9u6
Bug #910888 [src:imagemagick] imagemagick: CVE-2018-16644
The source 'imagemagick' and version '8:6.9.7.4+dfsg-11+deb9u6' do not appear 
to match any binary packages
Marked as fixed in versions imagemagick/8:6.9.7.4+dfsg-11+deb9u6.

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

Bug#908953: marked as done (pinball FTBFS with automake 1.16)

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 19:21:26 +
with message-id 
and subject line Bug#908953: fixed in pinball 0.3.1-14.1
has caused the Debian Bug report #908953,
regarding pinball FTBFS with automake 1.16
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.)


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

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

...
Making all in src
make[3]: Entering directory '/build/1st/pinball-0.3.1/src'
g++ -DHAVE_CONFIG_H -I. -I.. -I../base -I../addon   -Wdate-time 
-D_FORTIFY_SOURCE=2 -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT  -g -O2 
-ffile-prefix-map=/build/1st/pinball-0.3.1=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o Pinball.o Pinball.cpp
In file included from /usr/include/c++/8/backward/strstream:50,
 from Pinball.cpp:13:
/usr/include/c++/8/backward/backward_warning.h:32:2: warning: #warning This 
file includes at least one deprecated or antiquated header which may be removed 
without further notice at a future date. Please use a non-deprecated interface 
with equivalent functionality instead. For a listing of replacement headers and 
interfaces, consult the file backward_warning.h. To disable this warning use 
-Wno-deprecated. [-Wcpp]
 #warning \
  ^~~
Pinball.cpp: In function 'MenuItem* createMenus(Engine*)':
Pinball.cpp:566:10: warning: ignoring return value of 'int chdir(const char*)', 
declared with attribute warn_unused_result [-Wunused-result]
 chdir(Config::getInstance()->getDataDir());
 ~^
Pinball.cpp:579:10: warning: ignoring return value of 'int chdir(const char*)', 
declared with attribute warn_unused_result [-Wunused-result]
 chdir(cwd);
 ~^
make[3]: *** No rule to make target '../src/libemilia_pin.a', needed by 
'pinball'.  Stop.
make[3]: Leaving directory '/build/1st/pinball-0.3.1/src'
make[2]: *** [Makefile:535: all-recursive] Error 1


This is likely an old latent bug that would always have caused
problems with parallel building.

Fix is attached.
Description: Fix the src/Makefile.am dependencies
Author: Adrian Bunk 

--- pinball-0.3.1.orig/src/Makefile.am
+++ pinball-0.3.1/src/Makefile.am
@@ -9,7 +9,7 @@ pinlib_LIBRARIES = libemilia_pin.a
 
 INCLUDES = -I../base -I../addon @INCLTDL@
 
-pinball_LDADD = ../src/libemilia_pin.a ../addon/libemilia_addon.a 
../base/libemilia_base.a @LIBLTDL@
+pinball_LDADD = libemilia_pin.a ../addon/libemilia_addon.a 
../base/libemilia_base.a @LIBLTDL@
 pinball_LDFLAGS = -export-dynamic
 
 pinball_SOURCES = Pinball.cpp
--- End Message ---
--- Begin Message ---
Source: pinball
Source-Version: 0.3.1-14.1

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 27 Sep 2018 21:17:18 +0300
Source: pinball
Binary: pinball pinball-dev pinball-data
Architecture: source
Version: 0.3.1-14.1
Distribution: unstable
Urgency: medium
Maintainer: Innocent De Marchi 
Changed-By: Adrian Bunk 
Description:
 pinball- Emilia Pinball Emulator
 pinball-data - Data files for the Emilia Pinball Emulator
 pinball-dev - Development files for the Emilia Pinball Emulator
Closes: 908953
Changes:
 pinball (0.3.1-14.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix the Makefile dependencies. (Closes: #908953)
Checksums-Sha1:
 1079dad39e0a91200e3ec2b1657a0f21ddbbf182 2124 pinball_0.3.1-14.1.dsc
 635a288aff98682174b3bd1d4b071a50ff51ecd7 12732 pinball_0.3.1-14.1.debian.tar.xz
Checksums-Sha256:
 e4085c598752bdfe52d9ebbb9ecaab4e6ebd2a73ee0e1ee2c5009552efa79881 2124 
pinball_0.3.1-14.1.dsc
 835c4d783b488187f095956d5d453692f2f03d0eba1587f312733d8c2337b8c6 12732 
pinball_0.3.1-14.1.debian.tar.xz
Files:
 03d03f54ee22143e99066461e7e0e2f8 2

Processed: retitle 910887 to imagemagick: CVE-2018-16412 CVE-2018-16413

[Debian Bug Tracking System]

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

> retitle 910887 imagemagick: CVE-2018-16412 CVE-2018-16413
Bug #910887 [src:imagemagick] imagemagick: CVE-2018-16412
Changed Bug title to 'imagemagick: CVE-2018-16412 CVE-2018-16413' from 
'imagemagick: CVE-2018-16412'.
> thanks
Stopping processing here.

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

Processed: imagemagick: CVE-2018-16412

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 8:6.9.7.4+dfsg-11+deb9u6
Bug #910887 [src:imagemagick] imagemagick: CVE-2018-16412
The source 'imagemagick' and version '8:6.9.7.4+dfsg-11+deb9u6' do not appear 
to match any binary packages
Marked as fixed in versions imagemagick/8:6.9.7.4+dfsg-11+deb9u6.

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

Bug#910887: imagemagick: CVE-2018-16412

[Salvatore Bonaccorso]

Source: imagemagick
Version: 8:6.9.7.4+dfsg-11
Severity: grave
Tags: patch security upstream
Forwarded: https://github.com/ImageMagick/ImageMagick/issues/1250
Control: fixed -1 8:6.9.7.4+dfsg-11+deb9u6

[adding already the fixed version for strech-security as DSA pending]

Hi,

The following vulnerability was published for imagemagick.

CVE-2018-16412[0]:
| ImageMagick 7.0.8-11 Q16 has a heap-based buffer over-read in the
| coders/psd.c ParseImageResourceBlocks function.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-16412
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-16412
[1] https://github.com/ImageMagick/ImageMagick/issues/1250

Regards,
Salvatore

Bug#910638: marked as done (net-snmp: CVE-2018-18065)

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 19:02:09 +
with message-id 
and subject line Bug#910638: fixed in net-snmp 5.7.3+dfsg-1.7+deb9u1
has caused the Debian Bug report #910638,
regarding net-snmp: CVE-2018-18065
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.)


-- 
910638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910638
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: net-snmp
Version: 5.7.3+dfsg-1
Severity: grave
Tags: patch security upstream

Hi,

The following vulnerability was published for net-snmp.

CVE-2018-18065[0]:
| _set_key in agent/helpers/table_container.c in Net-SNMP before 5.8 has
| a NULL Pointer Exception bug that can be used by an authenticated
| attacker to remotely cause the instance to crash via a crafted UDP
| packet, resulting in Denial of Service.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-18065
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-18065
[1] 
https://sourceforge.net/p/net-snmp/code/ci/7ffb8e25a0db851953155de91f0170e9bf8c457d/

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: net-snmp
Source-Version: 5.7.3+dfsg-1.7+deb9u1

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

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

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated net-snmp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 09 Oct 2018 10:45:49 +0200
Source: net-snmp
Binary: snmpd snmptrapd snmp libsnmp-base libsnmp30 libsnmp30-dbg libsnmp-dev 
libsnmp-perl python-netsnmp tkmib
Architecture: source
Version: 5.7.3+dfsg-1.7+deb9u1
Distribution: stretch-security
Urgency: high
Maintainer: Net-SNMP Packaging Team 
Changed-By: Salvatore Bonaccorso 
Closes: 910638
Description: 
 libsnmp-base - SNMP configuration script, MIBs and documentation
 libsnmp-dev - SNMP (Simple Network Management Protocol) development files
 libsnmp-perl - SNMP (Simple Network Management Protocol) Perl5 support
 libsnmp30  - SNMP (Simple Network Management Protocol) library
 libsnmp30-dbg - SNMP (Simple Network Management Protocol) library debug
 python-netsnmp - SNMP (Simple Network Management Protocol) Python support
 snmp   - SNMP (Simple Network Management Protocol) applications
 snmpd  - SNMP (Simple Network Management Protocol) agents
 snmptrapd  - Net-SNMP notification receiver
 tkmib  - SNMP (Simple Network Management Protocol) MIB browser
Changes:
 net-snmp (5.7.3+dfsg-1.7+deb9u1) stretch-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * snmpd crashes when receiving a GetNext PDU with multiple Varbinds
 (CVE-2018-18065) (Closes: #910638)
Checksums-Sha1: 
 9892e4bb6b3612d5cfd4f6e4ce1c10e678640edf 3316 
net-snmp_5.7.3+dfsg-1.7+deb9u1.dsc
 ebbbc5e9fc5006edd3e62d595366497592d964a2 3371224 
net-snmp_5.7.3+dfsg.orig.tar.xz
 c4b93e29ac47a4129bea38a52bdecf82d673cd29 74236 
net-snmp_5.7.3+dfsg-1.7+deb9u1.debian.tar.xz
Checksums-Sha256: 
 61687e824bca1d7cbfa0506c854f4cbcbbefaa0d0e1c012a7c88520e5139815d 3316 
net-snmp_5.7.3+dfsg-1.7+deb9u1.dsc
 073eb05b926a9d23a2eba3270c4e52dd94c0aa27e8b7cf7f1a4e59a4d3da3fb5 3371224 
net-snmp_5.7.3+dfsg.orig.tar.xz
 17d7cd84de728889aabec767eb8b616bb750a42a194eddbd66953dd6311eb88b 74236 
net-snmp_5.7.3+dfsg-1.7+deb9u1.debian.tar.xz
Files: 
 f7f9d620ab58372044e7d6110b2b1c90 3316 net optional 
net-snmp_5.7.3+dfsg-1.7+deb9u1.dsc
 6391ae27eb1ae34ff5530712bb1c4209 3371224 net optional 
net-snmp_5.7.3+dfsg.orig.tar.xz
 424d11ee489f1f8f7e0efae9df590be6 74236 net optional 
net-snmp_5.7.3+dfsg-1.7+deb9u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAlu9GMFfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EgIsP/2emxTpp0+jWMagBt72U9nG/wHkWijFW
WVdoRq4qH8/iJY0/

Processed: fixed version is in unstable now

[Debian Bug Tracking System]

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

> fixed 907488 10.7.5+dfsg-2
Bug #907488 {Done: Pirate Praveen } [gitlab] gitlab: 
post-inst fails: Could not find gem 'rugged (~> 0.26.0)'
Marked as fixed in versions gitlab/10.7.5+dfsg-2.
>
End of message, stopping processing here.

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

Bug#910874: Bug#g : u a nnmmnattended-upgrades removes packages even ifkkkjukiukknknnnkknkyknjynkknikyikknkk

[Karlos GNU CON KERNEL LINUX]

Inhkikyikkhtkhikiioij y kín un jknkokonko nkbt

Unotkki uno kknnntknnkkukukií
Ukinkk nn n

Bug#907488: marked as done (gitlab: post-inst fails: Could not find gem 'rugged (~> 0.26.0)')

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 18:49:21 +
with message-id 
and subject line Bug#907488: fixed in gitlab 10.7.7+dfsg-2
has caused the Debian Bug report #907488,
regarding gitlab: post-inst fails: Could not find gem 'rugged (~> 0.26.0)'
to be marked as done.

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

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


-- 
907488: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=907488
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gitlab
Version: 10.6.5+dfsg-2
Severity: serious

Dear Maintainer,

The post-inst script consistently fails for me with unstable's current
gitlab package. I tested this with two systems (one buster/sid and one
sid).

Installation log follows.

8<--

Setting up gitlab (10.6.5+dfsg-2) ...
Creating/updating git user account...
Making git owner of /var/lib/gitlab...
Could not find gem 'rugged (~> 0.26.0)' in any of the gem sources listed
in your Gemfile.
dpkg: error processing package gitlab (--configure):
 installed gitlab package post-installation script subprocess returned
 error exit status 1
 Errors were encountered while processing:
  gitlab

>8--

I think the problem comes from the dependency on ruby-rugged, which is
pinned to ">= 0.26~".
The package in buster and sid is at version 0.27.4+ds-1.
The Gemfile, however, pins it to "~> 0.26.0", meaning that versions 0.27
and superior aren't acceptable.


Kind regards,
Pikrass.


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

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

Versions of packages gitlab depends on:
ii  adduser3.117
ii  asciidoctor1.5.7.1-1
ii  bc 1.07.1-2+b1
ii  bundler1.16.1-3
ii  dbconfig-pgsql 2.0.9
ii  debconf [debconf-2.0]  1.5.69
ii  exim4-daemon-heavy [mail-transport-agent]  4.91-6
ii  git1:2.18.0-1
ii  gitlab-shell   7.1.2+dfsg-2
ii  gitlab-workhorse   4.3.1+debian-1
ii  lsb-base   9.20170808
ii  nginx  1.13.12-1
ii  nginx-full [nginx] 1.13.12-1
ii  nodejs 8.11.2~dfsg-1
ii  npm5.8.0+ds-2
ii  openssh-client 1:7.7p1-4
ii  postgresql-client  10+193
ii  postgresql-client-10 [postgresql-client]   10.5-1
ii  postgresql-contrib 10+193
ii  rake   12.3.1-3
ii  redis-server   5:4.0.11-2
ii  ruby   1:2.5.1
ii  ruby-ace-rails-ap  4.1.1-1
ii  ruby-acts-as-taggable-on   5.0.0-2
ii  ruby-addressable   2.5.2-1
ii  ruby-akismet   2.0.0-1
ii  ruby-allocations   1.0.3-1+b4
ii  ruby-arel  6.0.4-1
ii  ruby-asana 0.6.0-1
ii  ruby-asciidoctor-plantuml  0.0.8-1
ii  ruby-asset-sync2.4.0-1
ii  ruby-attr-encrypted3.1.0-1
ii  ruby-babosa1.0.2-2
ii  ruby-base320.3.2-3
ii  ruby-batch-loader  1.2.1-1
ii  ruby-bcrypt-pbkdf  1.0.0-1+b2
ii  ruby-bootstrap-form2.7.0-1
ii  ruby-bootstrap-sass3.3.5.1-5.1
ii  ruby-browser   2.2.0-2
ii  ruby-carrierwave   1.2.2-1
ii  ruby-charlock-holmes   0.7.5-1+b2
ii  ruby-chronic   0.10.2-3
ii  ruby-chronic-duration  0.10.6-1
ii  ruby-commonmarker  0.17.9-1
ii  ruby-connection-pool   2.2.0-1
ii  ruby-creole0.5.0-2
ii  ruby-d3-rails 

Bug#896231: marked as done (python-pytest-runner: ptr fails to import)

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 18:35:07 +
with message-id 
and subject line Bug#896231: fixed in pytest-runner 2.11.1-1.1
has caused the Debian Bug report #896231,
regarding python-pytest-runner: ptr fails to import
to be marked as done.

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

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


-- 
896231: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896231
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-pytest-runner
Version: 2.11.1-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python-pytest-runner importing the module ptr
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/ptr.py", line 18, in 
import pkg_resources
ImportError: No module named pkg_resources

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

Helmut
--- End Message ---
--- Begin Message ---
Source: pytest-runner
Source-Version: 2.11.1-1.1

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated pytest-runner package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 27 Sep 2018 20:35:32 +0300
Source: pytest-runner
Binary: python-pytest-runner python3-pytest-runner
Architecture: source
Version: 2.11.1-1.1
Distribution: unstable
Urgency: high
Maintainer: Debian Python Modules Team 

Changed-By: Adrian Bunk 
Description:
 python-pytest-runner - Invoke py.test as distutils command with dependency 
resolution -
 python3-pytest-runner - Invoke py.test as distutils command with dependency 
resolution -
Closes: 896231 896428
Changes:
 pytest-runner (2.11.1-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * python-pytest-runner: Add the missing dependencies on
 python-pkg-resources and python-setuptools. (Closes: #896231)
   * python3-pytest-runner: Add the missing dependencies on
 python3-pkg-resources and python3-setuptools. (Closes: #896428)
Checksums-Sha1:
 766a8ec0502d638978a4c64d098edd0669ffcd54 2277 pytest-runner_2.11.1-1.1.dsc
 a21be629fd9f92bd7efd220c44db345823112bd3 2424 
pytest-runner_2.11.1-1.1.debian.tar.xz
Checksums-Sha256:
 ccc680424d6d36e547c917fb2b934021c5a92161790d2d22dfc6b5c0aae325e1 2277 
pytest-runner_2.11.1-1.1.dsc
 6ed50eac693a0f5a9d156583231403575360c97fbf130884d3329a7f8e19287c 2424 
pytest-runner_2.11.1-1.1.debian.tar.xz
Files:
 ef318e985374f877f840e2f052a8403b 2277 python optional 
pytest-runner_2.11.1-1.1.dsc
 edad2fd8e930fa3122611ce5493dd3a9 2424 python optional 
pytest-runner_2.11.1-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlutFigACgkQiNJCh6LY
mLEWPg//f8vWL71GKuZ8AxiyUC4R1NCeQD0G7Ox9YTioQaKB8jDfwUPxjUlg/A/8
4mU1SUw55k0PZ457j/juQ52r/lPoKsyR3r+CLBiwcPD+LQQ1wrDmi1Q1sUar3xd5
7F0yDW5hdqYK13RIszu94HR1Sedy2Kq4LOF+JlO6VpPh/mWV5IEYg08VIcpOG2WX
1siw1+95jku4G3Bct5AU47oaQd1d7wI0B8DofdE40rjjdy0Pf9jKxCyWXmQJrFrL
uf2eBmMN4sAkBndSDId+d6K2t8v4vie7s7cmTgrfbhgwdG3+SUrFmOV4tnM2VNLO
bJPmDKWUBkySCQhnFSppeorwp3rwmqCEWWGlGnwTchsP9xUnmz5fe6I2aqUGB+AO
a0oBrJP94N4DVYZVLqkuDk+qP+WLdAsjLF7TAEHeB/71ajxHosKpx3e1nT5KzDZ9
SKCev+Hy3PfNfMeqt6lSeKOi6hXr2RwQAPLrU9J25mmfJtbgwzlIgVconDs1vTBF
CftNF3DVu5TMNT1BTJDAyy+EDU79mbg3eYsUbKyXRa0Qs3Q5o1ZHE+TLQQ32Y5X6
qqLqHMQTfaC/TkHvg0vw50yByf7g8eyD0zw+VLs3ZE8QhE9BQK8TysoN9LsGP5Fw
yEiM603RP+k1ZoJVkA761taKj3jlSBvLPKqvzZyL3HRorIQqqyE=
=PaBF
-END PGP SIGNATURE End Message ---

Bug#896428: marked as done (python3-pytest-runner: ptr fails to import)

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 18:35:07 +
with message-id 
and subject line Bug#896428: fixed in pytest-runner 2.11.1-1.1
has caused the Debian Bug report #896428,
regarding python3-pytest-runner: ptr fails to import
to be marked as done.

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

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


-- 
896428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pytest-runner
Version: 2.11.1-1
Severity: serious
User: helm...@debian.org
Usertags: python-import

After installing python3-pytest-runner importing the module ptr
into a python interpreter fails with the following error:

Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/ptr.py", line 18, in 
import pkg_resources
ModuleNotFoundError: No module named 'pkg_resources'

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

Helmut
--- End Message ---
--- Begin Message ---
Source: pytest-runner
Source-Version: 2.11.1-1.1

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

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

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

Debian distribution maintenance software
pp.
Adrian Bunk  (supplier of updated pytest-runner package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 27 Sep 2018 20:35:32 +0300
Source: pytest-runner
Binary: python-pytest-runner python3-pytest-runner
Architecture: source
Version: 2.11.1-1.1
Distribution: unstable
Urgency: high
Maintainer: Debian Python Modules Team 

Changed-By: Adrian Bunk 
Description:
 python-pytest-runner - Invoke py.test as distutils command with dependency 
resolution -
 python3-pytest-runner - Invoke py.test as distutils command with dependency 
resolution -
Closes: 896231 896428
Changes:
 pytest-runner (2.11.1-1.1) unstable; urgency=high
 .
   * Non-maintainer upload.
   * python-pytest-runner: Add the missing dependencies on
 python-pkg-resources and python-setuptools. (Closes: #896231)
   * python3-pytest-runner: Add the missing dependencies on
 python3-pkg-resources and python3-setuptools. (Closes: #896428)
Checksums-Sha1:
 766a8ec0502d638978a4c64d098edd0669ffcd54 2277 pytest-runner_2.11.1-1.1.dsc
 a21be629fd9f92bd7efd220c44db345823112bd3 2424 
pytest-runner_2.11.1-1.1.debian.tar.xz
Checksums-Sha256:
 ccc680424d6d36e547c917fb2b934021c5a92161790d2d22dfc6b5c0aae325e1 2277 
pytest-runner_2.11.1-1.1.dsc
 6ed50eac693a0f5a9d156583231403575360c97fbf130884d3329a7f8e19287c 2424 
pytest-runner_2.11.1-1.1.debian.tar.xz
Files:
 ef318e985374f877f840e2f052a8403b 2277 python optional 
pytest-runner_2.11.1-1.1.dsc
 edad2fd8e930fa3122611ce5493dd3a9 2424 python optional 
pytest-runner_2.11.1-1.1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlutFigACgkQiNJCh6LY
mLEWPg//f8vWL71GKuZ8AxiyUC4R1NCeQD0G7Ox9YTioQaKB8jDfwUPxjUlg/A/8
4mU1SUw55k0PZ457j/juQ52r/lPoKsyR3r+CLBiwcPD+LQQ1wrDmi1Q1sUar3xd5
7F0yDW5hdqYK13RIszu94HR1Sedy2Kq4LOF+JlO6VpPh/mWV5IEYg08VIcpOG2WX
1siw1+95jku4G3Bct5AU47oaQd1d7wI0B8DofdE40rjjdy0Pf9jKxCyWXmQJrFrL
uf2eBmMN4sAkBndSDId+d6K2t8v4vie7s7cmTgrfbhgwdG3+SUrFmOV4tnM2VNLO
bJPmDKWUBkySCQhnFSppeorwp3rwmqCEWWGlGnwTchsP9xUnmz5fe6I2aqUGB+AO
a0oBrJP94N4DVYZVLqkuDk+qP+WLdAsjLF7TAEHeB/71ajxHosKpx3e1nT5KzDZ9
SKCev+Hy3PfNfMeqt6lSeKOi6hXr2RwQAPLrU9J25mmfJtbgwzlIgVconDs1vTBF
CftNF3DVu5TMNT1BTJDAyy+EDU79mbg3eYsUbKyXRa0Qs3Q5o1ZHE+TLQQ32Y5X6
qqLqHMQTfaC/TkHvg0vw50yByf7g8eyD0zw+VLs3ZE8QhE9BQK8TysoN9LsGP5Fw
yEiM603RP+k1ZoJVkA761taKj3jlSBvLPKqvzZyL3HRorIQqqyE=
=PaBF
-END PGP SIGNATURE End Message ---

Bug#897725: marked as done (courier-authlib: ftbfs with GCC-8)

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 18:34:22 +
with message-id 
and subject line Bug#897725: fixed in courier-authlib 0.68.0-4.1
has caused the Debian Bug report #897725,
regarding courier-authlib: ftbfs with GCC-8
to be marked as done.

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

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


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

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
make[3]: Leaving directory '/<>'
make[2]: Leaving directory '/<>'
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
pod2man --center='Debian GNU/Linux Documentation' --release='Debian GNU/Linux 
'`cat /etc/debian_version` --section=8 debian/authenumerate.pod > 
debian/tmp/usr/share/man/man8/authenumerate.8
perl -pe 's/^authmodulelist=".*?"/authmodulelist="authpam"/' 
debian/tmp/etc/courier/authdaemonrc.dist > debian/tmp/etc/courier/authdaemonrc
rm debian/tmp/etc/courier/authdaemonrc.dist
perl -pe 's/^(LDAP_SERVER\s+)ldap.example.com/$1localhost/' 
debian/tmp/etc/courier/authldaprc.dist > debian/tmp/etc/courier/authldaprc
rm debian/tmp/etc/courier/authldaprc.dist
perl -pe 
's/^(MYSQL_SERVER\s+)mysql.example.com/$1localhost/;s%^(#?\s*MYSQL_SOCKET\s+)/.*%$1/var/run/mysqld/mysqld.sock%'
 debian/tmp/etc/courier/authmysqlrc.dist > debian/tmp/etc/courier/authmysqlrc
rm debian/tmp/etc/courier/authmysqlrc.dist
perl -pe 's%^(SQLITE_DATABASE\s+)/var/users.db%$1/var/lib/courier/users.db%' 
debian/tmp/etc/courier/authsqliterc.dist > debian/tmp/etc/courier/authsqliterc
rm debian/tmp/etc/courier/authsqliterc.dist
mv debian/tmp/etc/courier/authpgsqlrc.dist debian/tmp/etc/courier/authpgsqlrc
dh_install --fail-missing -X.la
dh_install: Please use dh_missing --list-missing/--fail-missing instead
dh_install: This feature will be removed in compat 12.
make[1]: Leaving directory '/<>'
   dh_installdocs -a
   dh_installchangelogs -a
   dh_installman -a
   dh_installinit -a
   dh_perl -a
   dh_link -a
   dh_strip_nondeterminism -a
   dh_compress -a
   dh_fixperms -a
   dh_missing -a
   dh_strip -a
   dh_makeshlibs -a
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: warning: debian/courier-authlib/DEBIAN/symbols doesn't match 
completely debian/courier-authlib.symbols
--- debian/courier-authlib.symbols (courier-authlib_0.68.0-4_amd64)
+++ dpkg-gensymbolsCbNatr   2018-05-02 12:58:47.976257477 +
@@ -101,6 +101,11 @@
  strdupdefdomain@Base 0.63.0
 libcourierauthcommon.so.0 courier-authlib #MINVER#
 * Build-Depends-Package: courier-authlib-dev
+ 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIN9__gnu_cxx17__normal_iteratorIPKcS4_vT_SB_St20forward_iterator_tag@Base
 0.68.0-4
+ 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPKcEEvT_S8_St20forward_iterator_tag@Base
 0.68.0-4
+ 
_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE12_M_constructIPcEEvT_S7_St20forward_iterator_tag@Base
 0.68.0-4
+ 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE16_M_insert_uniqueIS6_IS5_S5_EEES6_ISt17_Rb_tree_iteratorIS8_EbEOT_@Base
 0.68.0-4
+ 
_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_c

Bug#853256: marked as done (ruby-sidekiq: Switch form twitter-bootstrap to libjs-bootstrap (v2 to v3))

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 18:21:59 +
with message-id 
and subject line Bug#853256: fixed in ruby-sidekiq 5.2.2+dfsg-1
has caused the Debian Bug report #853256,
regarding ruby-sidekiq: Switch form twitter-bootstrap to libjs-bootstrap (v2 to 
v3)
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.)


-- 
853256: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=853256
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ruby-sidekiq
Version: 4.2.3+dfsg-1
Severity: wishlist

I'd like to recommend switching from twitter-bootstrap package to
libjs-bootstrap which would upgrade it from v2 to v3.

it would just require relinking bootstrap.css to
../../../../javascript/bootstrap/bootstrap.min.css instead.

I have done this locally to fix a few visual bugs that you can see will in 
gitlab under /admin/background_jobs and I'm sure there are others.

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

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

Versions of packages ruby-sidekiq depends on:
ii  libjs-twitter-bootstrap  2.0.2+dfsg-10
ii  ruby 1:2.3.3
ii  ruby-celluloid   0.16.0-4
ii  ruby-concurrent  1.0.0-3
ii  ruby-connection-pool 2.2.0-1
ii  ruby-json2.0.1+dfsg-3
ii  ruby-redis   3.2.2-1
ii  ruby-redis-namespace 1.5.2-3

ruby-sidekiq recommends no packages.

ruby-sidekiq suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ruby-sidekiq
Source-Version: 5.2.2+dfsg-1

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated ruby-sidekiq 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: Thu, 11 Oct 2018 22:32:15 +0530
Source: ruby-sidekiq
Binary: ruby-sidekiq
Architecture: source
Version: 5.2.2+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 ruby-sidekiq - Simple, efficient background processing for Ruby
Closes: 853256
Changes:
 ruby-sidekiq (5.2.2+dfsg-1) unstable; urgency=medium
 .
   [ Manas kashyap ]
   * Celluloid version updated
   * Patch created long time back when gem2deb did not have an option handle
 non ruby files correctly dropped in favor of --gem-install option
 .
   [ Pirate Praveen ]
   * Use https in watch file
   * New upstream version 5.2.2+dfsg
   * Bump Standards-Version to 4.2.1 (no changes needed)
   * Switch to libjs-bootstrap from libjs-twitter-bootstrap (Closes: #853256)
Checksums-Sha1:
 16181292ce5627b0836efcf016793c6f6e45d9c8 2480 ruby-sidekiq_5.2.2+dfsg-1.dsc
 ed29c55d2be32c12af8e19908c3556f49308f919 129272 
ruby-sidekiq_5.2.2+dfsg.orig.tar.xz
 9b70a6c093990579f329e47b464a50542176e115 4100 
ruby-sidekiq_5.2.2+dfsg-1.debian.tar.xz
 18e777ba95a64cffbe6848f9808d8af64e701332 8919 
ruby-sidekiq_5.2.2+dfsg-1_source.buildinfo
Checksums-Sha256:
 0d26cba72edd167686b11e29c79db2adde9b85dc74979d804a8d4597812728f9 2480 
ruby-sidekiq_5.2.2+dfsg-1.dsc
 0ca2c0861e458c09e23ef950b6329ad1c7e85a4376b925bee0d37a4de2bc0502 129272 
ruby-sidekiq_5.2.2+dfsg.orig.tar.xz
 da9dc08ba30b6c745dca8a4385a979b92b5d9433c75b57c33002d7c1a6fbbbaa 4100 
ruby-sidekiq_5.2.2+dfsg-1.debian.tar.xz
 e2ee0dc58d4af6d30bac37c70930eac559366b50ddf136d4c8a80d422591aff2 8919 
ruby-sidekiq_5.2.2+dfsg-1_source.buildinfo
Files:
 7024f4d3da1574a40b5e12c6ae575d71 2480 ruby optional 
ruby-sidekiq_5.2.2+dfsg-1.dsc
 1833dee303e2f324e26bce251b2b7a7a 129272 ruby optional 
ruby-sidekiq_5.2.2+dfsg.orig.tar.xz
 b86bf182ac53035cc41adf873aa85718 4100 ruby optional 
ruby-sidekiq_5.2.2+dfsg-1.debian.tar.xz
 1cdfaef45716df94c8653bbe5a36145b 8919 ruby optional 
ruby-sidekiq_5.2.2+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEB

Bug#910885: rust-pcap: Unsatisfiable dependencies

[Jeremy Bicha]

It looks like there are a lot of these unsatisfiable dependencies for
rust packages. Could you look through

https://qa.debian.org/developer.php?email=pkg-rust-maintainers%40alioth-lists.debian.net&version=testing

Thanks,
Jeremy Bicha

Bug#910885: rust-pcap: Unsatisfiable dependencies

[Jeremy Bicha]

Source: rust-pcap
Version: 0.7.0-1
Severity: serious

rust-pcap is not migrating to testing because of these unsatisfiable
dependencies:

librust-pcap+clippy-dev Depends: librust-clippy-0.0+default-dev
librust-pcap+mio-dev Depends: librust-mio-0.6+default-dev
librust-pcap+tokio-core-dev Depends: librust-tokio-core-0.1+default-dev
librust-pcap+tokio-dev Depends: librust-mio-0.6+default-dev
librust-pcap+tokio-dev Depends: librust-tokio-core-0.1+default-dev

https://tracker.debian.org/pkg/rust-pcap

Thanks,
Jeremy Bicha

Bug#904026: marked as done (gitlab: CVE-2018-14364)

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 18:07:12 +
with message-id 
and subject line Bug#904026: fixed in gitlab 10.7.7+dfsg-1
has caused the Debian Bug report #904026,
regarding gitlab: CVE-2018-14364
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.)


-- 
904026: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904026
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gitlab
Version: 8.9.0+dfsg-1
Severity: grave
Tags: security upstream

Hi,

The following vulnerability was published for gitlab.

CVE-2018-14364[0]:
Remote Code Execution Vulnerability in GitLab Projects Import

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-14364
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14364
[1] 
https://about.gitlab.com/2018/07/17/critical-security-release-gitlab-11-dot-0-dot-4-released/

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: gitlab
Source-Version: 10.7.7+dfsg-1

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

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

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

Debian distribution maintenance software
pp.
Pirate Praveen  (supplier of updated gitlab 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: Mon, 20 Aug 2018 21:38:35 +0530
Source: gitlab
Binary: gitlab gitlab-common
Architecture: source all
Version: 10.7.7+dfsg-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Pirate Praveen 
Description:
 gitlab - git powered software platform to collaborate on code (non-omnibus
 gitlab-common - git powered software platform to collaborate on code (common)
Closes: 904026
Changes:
 gitlab (10.7.7+dfsg-1) experimental; urgency=medium
 .
   * New upstream version 10.7.7+dfsg (Fixes: CVE-2018-14364) (Closes: #904026)
   * Bump Standards-Version to 4.2.0 (no changes needed)
Checksums-Sha1:
 48c7fc0a62554cc73cead299f7bf38b80d9e6570 2545 gitlab_10.7.7+dfsg-1.dsc
 dc16b898933578951728e672135705cc534c0e27 44558392 
gitlab_10.7.7+dfsg.orig.tar.xz
 4e2c6a444333270cb2fb159b322b02457a1538c8 64244 
gitlab_10.7.7+dfsg-1.debian.tar.xz
 8fb619e060a5b1d49e5c0369acc005051c4b50f4 106448 
gitlab-common_10.7.7+dfsg-1_all.deb
 0969d7b8ae03030733eac69316b988b00259beb9 44949232 gitlab_10.7.7+dfsg-1_all.deb
 cb94baba861c5292e0677afa46872cbcebd31a63 6964 
gitlab_10.7.7+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 05f6e09645c4fd50981ac8c56fc3862375352e4cae3eea27e5fb3f03f9ca7b1c 2545 
gitlab_10.7.7+dfsg-1.dsc
 6c96e974e09816c15d9c9713b8eb647483f52dd980c7d79554533cd9ed23af94 44558392 
gitlab_10.7.7+dfsg.orig.tar.xz
 cf84b23acd0a061d6bc0ba1c0e10cff5d4e37691734a230707b81ee0c3d7baf8 64244 
gitlab_10.7.7+dfsg-1.debian.tar.xz
 afccc8503eed02a7b2109a149ddeac2bd07f90595bbd239892cf300240af3d77 106448 
gitlab-common_10.7.7+dfsg-1_all.deb
 85b610e2d410adddae5cfe8f52ec037f33c046441d18f7930b5cbbfe28191a03 44949232 
gitlab_10.7.7+dfsg-1_all.deb
 dc7fe04aeede45fb96fa104987c59ef510138b0807ff6f57a067bc7398e58003 6964 
gitlab_10.7.7+dfsg-1_amd64.buildinfo
Files:
 1668c81fe3741967fb3bd42a85fd75b1 2545 contrib/net optional 
gitlab_10.7.7+dfsg-1.dsc
 6b71d9502a2c947281986726c6ad3eea 44558392 contrib/net optional 
gitlab_10.7.7+dfsg.orig.tar.xz
 59f8161d6a6fbb51ede72f1ad8d15cc1 64244 contrib/net optional 
gitlab_10.7.7+dfsg-1.debian.tar.xz
 e91bdf7ceb6d8f45a941aeb0de9c334c 106448 contrib/net optional 
gitlab-common_10.7.7+dfsg-1_all.deb
 6bfd2ee3e2ff3e4f4e80c6f03ee25b7a 44949232 contrib/net optional 
gitlab_10.7.7+dfsg-1_all.deb
 30ee3409ebb9a6fa33816f2c9a008818 6964 contrib/net optional 
gitlab_10.7.7+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEKnl0ri/BUtd4Z9pKzh+cZ0USwioFAlt668AACgkQzh+cZ0US
wiqY2BAAjCjAVsZjgtXN2fEsmR6tEWAxrSLZhty18480nJitOgL+iNQlMLot+72m
yys0t6SAM/SIqPFrqlRG/aA1tdAD9jxb7b/9wzqKRVaYuhtbfRy2mTS65yq5xnRw
CcelEumsnF7MoiqV+OhNVzfr67jHPnHGrTj4ONQaeNLQxf7iVd9Lwt1hZuwN2UfQ
uPWpZoMfovXYOKhGj3liOgqTbSu4fNfN1okkgCkuOKuh7mFHPd

Bug#872806: marked as done (libgpg-error0 packs runtime support files in shared library)

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 18:07:13 +
with message-id 
and subject line Bug#872806: fixed in libgpg-error 1.32-2
has caused the Debian Bug report #872806,
regarding libgpg-error0 packs runtime support files in shared library
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.)


-- 
872806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=872806
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgpg-error0
Version: 1.27-3
Severity: serious
Justification: policy 8.2
User: helm...@debian.org
Usertags: rebootstrap

libgpg-error0 packs runtime support files (i.e. .mo files) into the
shared library package. It happens that these files are not versioned
(e.g. libgpg-error.mo rather than libgpg-error0.mo). Doing so violates
Debian policy section 8.2:

|If your package contains files whose names do not change with each change
|in the library shared object version, you must not put them in the shared
|library package. Otherwise, several versions of the shared library cannot
|be installed at the same time without filename clashes, making upgrades
|and transitions unnecessarily difficult.

This happens to also break multiarch. Rebuilds of libgpg-error are not
currently coinstallable with other instances from the archive:

| Unpacking libgpg-error-dev:ppc64 (1.27-3) ...
| dpkg: error processing archive 
/tmp/repo/pool/main/libg/libgpg-error/libgpg-error0_1.27-3_ppc64.deb (--unpack):
|  trying to overwrite shared 
'/usr/share/locale/cs/LC_MESSAGES/libgpg-error.mo', which is different from 
other instances of package libgpg-error0:ppc64
| Errors were encountered while processing:
|  /tmp/repo/pool/main/libg/libgpg-error/libgpg-error0_1.27-3_ppc64.deb
| E: Sub-process /usr/bin/dpkg returned an error code (1)
| E: Failed to process build dependencies

I suggest moving them to an Arch:all package.

Helmut
--- End Message ---
--- Begin Message ---
Source: libgpg-error
Source-Version: 1.32-2

We believe that the bug you reported is fixed in the latest version of
libgpg-error, 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.
Daniel Kahn Gillmor  (supplier of updated libgpg-error 
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, 12 Oct 2018 10:04:28 -0400
Source: libgpg-error
Binary: libgpg-error-dev libgpg-error0 gpgrt-tools libgpg-error0-udeb 
libgpg-error-mingw-w64-dev libgpg-error-l10n
Architecture: source amd64 all
Version: 1.32-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG Maintainers 
Changed-By: Daniel Kahn Gillmor 
Description:
 gpgrt-tools - GnuPG development runtime library (executable tools)
 libgpg-error-dev - GnuPG development runtime library (developer tools)
 libgpg-error-l10n - library of error values and messages in GnuPG 
(localization files
 libgpg-error-mingw-w64-dev - library of error values and messages in GnuPG 
(Windows developmen
 libgpg-error0 - GnuPG development runtime library
 libgpg-error0-udeb - library for common error values and messages in GnuPG 
components (udeb)
Closes: 869605 872806
Changes:
 libgpg-error (1.32-2) unstable; urgency=medium
 .
   [ Sven Joachim ]
   * Move the translation files to a new libgpg-error-l10n package
 (Closes: #872806)
 .
   [ Wookey ]
   * Add support for arm64ilp32 (Closes: #869605)
 .
   [ Daniel Kahn Gillmor ]
   * Standards-Version: bumped to 4.2.1 (no changes needed)
Checksums-Sha1:
 89145907fb7f0bfc24e5242a9fec71d6ed9a6baa 2133 libgpg-error_1.32-2.dsc
 187915577bca37ffa62dcaf888967f9ca58e070b 16076 
libgpg-error_1.32-2.debian.tar.xz
 c2bb85c3ee5da8108d4373fde6d53f9ce9c9ed14 41996 
gpgrt-tools-dbgsym_1.32-2_amd64.deb
 c1011298db62e54aca9b53bc666da6d82b3864de 38756 gpgrt-tools_1.32-2_amd64.deb
 4eea554ce061e15361a91497e12b5cf73e7ade1c 117996 
libgpg-error-dev_1.32-2_amd64.deb
 33f69931ec50a248a72f6e8aeeeb959dcb1ecca2 97820 libgpg-error-l10n_1.32-2_all.deb
 e83100e24f738cf9e27fdb97c45da86311058f76 587360 
libgpg-error-mingw-w64-dev_1.32-2_all.deb
 1f29f4bff448594e33b1faacd9f924865d05c52a 173524 
libgpg-error0-dbgsym_1.32-2_amd64.deb

Bug#910879: print-manager: Prevent to start a kde session for all users

[Eric Valette]

Package: print-manager
Version: 4:18.04.1-1
Severity: critical
Justification: breaks unrelated software

Yesterday my daughther came with her laptop and said it was no more possible to 
log in.
After entering the password, plasmashell was starting, then a strange message 
from okular
and then a black screen with only the mouse pointer. Plasmashell did carsh.

At fisrt I suspecter the .config or .kde config file to be corrupted, moved 
them with
no result and then tried my own account with same behavior.

So I installed another windown manager and started plasmashell manually to 
discover
that print-manager was crashing with SIGSEGV in
/usr/lib/x86_64-linux-gnu/libkcupslib.so that in turn makde plasmashell stop.

Removed print-manager and was able to log again on plasma. Didi some savalge
of leftover /var/spool/cups/* old directory and also a file there, reinstalled
print-manager, printer and it continued to work.

Anyway a SIGSEGV in /usr/lib/x86_64-linux-gnu/libkcupslib.so is abnormal,
the fact that it can prvent to start a session also.



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

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

Versions of packages print-manager depends on:
ii  kio   5.49.0-1
ii  libc6 2.27-6
ii  libcups2  2.3~b5-2
ii  libkf5configcore5 5.49.0-1
ii  libkf5configgui5  5.49.0-1
ii  libkf5configwidgets5  5.49.0-1
ii  libkf5coreaddons5 5.49.0-1
ii  libkf5dbusaddons5 5.49.0-1
ii  libkf5i18n5   5.49.0-1
ii  libkf5iconthemes5 5.49.0-1
ii  libkf5kiocore55.49.0-1
ii  libkf5kiowidgets5 5.49.0-1
ii  libkf5notifications5  5.49.0-1
ii  libkf5service-bin 5.49.0-1
ii  libkf5service55.49.0-1
ii  libkf5widgetsaddons5  5.49.0-1
ii  libkf5windowsystem5   5.49.0-1
ii  libqt5core5a  5.11.1+dfsg-9
ii  libqt5dbus5   5.11.1+dfsg-9
ii  libqt5gui55.11.1+dfsg-9
ii  libqt5network55.11.1+dfsg-9
ii  libqt5qml55.11.1-6
ii  libqt5widgets55.11.1+dfsg-9
ii  libstdc++68.2.0-7
ii  plasma-framework  5.49.0-1

Versions of packages print-manager recommends:
ii  cups  2.3~b5-2
ii  system-config-printer-common  1.5.11-3
ii  system-config-printer-udev1.5.11-3

print-manager suggests no packages.

-- no debconf information

Bug#910874: unattended-upgrades removes packages even if

[Jan Kowalsky]

Package: unattended-upgrades
Version: 0.93.1+nmu1
Severity: serious

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


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

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

APT::AutoRemove::RecommendsImportant "false";

In my understanding this shouldn't be the case.

Here is the output of unattended-upgrade:

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


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

Bug#867273: marked as done (purify FTBFS on arm64 due to long-running test)

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 15:50:01 +
with message-id 
and subject line Bug#867273: fixed in purify 2.0.0-4
has caused the Debian Bug report #867273,
regarding purify FTBFS on arm64 due to long-running test
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=purify&arch=arm64&ver=2.0.0-1&stamp=1499198222&raw=0

...
   dh_auto_test -a -O--parallel -O--buildsystem=cmake
make -j8 test ARGS\+=-j8
make[1]: Entering directory '/<>/obj-aarch64-linux-gnu'
Running tests...
/usr/bin/ctest --force-new-ctest-process -j8
Test project /<>/obj-aarch64-linux-gnu
Start 1: test_measurement_operator
Start 2: test_FFT_operator
Start 3: test_purify_fitsio
Start 4: test_utils
Start 5: test_sparse
1/5 Test #5: test_sparse ..   Passed0.20 sec
2/5 Test #3: test_purify_fitsio ...   Passed0.91 sec
3/5 Test #2: test_FFT_operator    Passed2.39 sec
4/5 Test #4: test_utils ...   Passed   13.53 sec
E: Build killed with signal TERM after 150 minutes of inactivity


Building purify on asachi I get:
5/5 Test #1: test_measurement_operator    Passed  12011.56 sec

That's 200 minutes.
--- End Message ---
--- Begin Message ---
Source: purify
Source-Version: 2.0.0-4

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated purify 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, 12 Oct 2018 17:22:28 +0200
Source: purify
Binary: purify libpurify2.0 libpurify-dev
Architecture: source
Version: 2.0.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Description:
 libpurify-dev - Routines for radio interferometric imaging (development files)
 libpurify2.0 - Routines for radio interferometric imaging (shared lib)
 purify - Collection of routines for radio interferometric imaging
Closes: 867273
Changes:
 purify (2.0.0-4) unstable; urgency=medium
 .
   * Disable measurement_operator test on aarch64 (Closes: #867273)
Checksums-Sha1:
 b0d09e00ab43f61c3eeb49c4a81b4d47b8f19e0a 2201 purify_2.0.0-4.dsc
 027d5a014a45ac6fa641cce87abe92c01be1640a 18832 purify_2.0.0-4.debian.tar.xz
Checksums-Sha256:
 f1dd93758b0e15f063ecb054999f5224b3979ab12c81003f5a486175ff5f8aaa 2201 
purify_2.0.0-4.dsc
 5fca72e69a8968fa03d5c8fe48fd4ad038c8406fe74b089421efe49b5d930ebc 18832 
purify_2.0.0-4.debian.tar.xz
Files:
 d164d73f07f79cba33182f1e0d423c45 2201 science optional purify_2.0.0-4.dsc
 7cef3c96a6672510ab4f246548a88ed0 18832 science optional 
purify_2.0.0-4.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE7/BpV0Ra2/h0L3qtmk9WvbkOGL0FAlvAvSIACgkQmk9WvbkO
GL1rJBAAl64hJQegI4FyezTnCpJ9aFI93BTLk7MqJ0DfgcUlnOsVIQHbbz+UYiaN
otI7otXixUHH2HnM1JLgs5pUjBOp7RkeKPRhBARM2ZwbcHBGK4Wlnq1dISpOQrKc
niKANxDHhjtQ+UqfdarFhieyn0hPOxo9HubRQbbmaVKC4grGZTtnB1bfcYRaSFVX
lRlsSCu4GrfjZ1dUPG5nv1vDyNNkK7ZyjWaC5OmiVhr/302uIJegh5rpSiBfKhSr
TQ0Qa2sDUE90u8xzkS28fS0dKHat1go8DbwA5qKNE/mzIW3LKYIUvBXI7Dz9Q5hL
/tnwVpF/GgJpTToEXp1JwF0b61aXq7JwohfJ/BBaOJ/PFOvP+akdfaOrsVxflynh
ohUQlTT06QymFb8YYnMbNKDkzB/8EUqMDhW4vkcyugBgmPZcbopLsA/0ytpctHBQ
aY/kaV+jAd1Kyyg+edeuVvoFBmjty0Xr+3n3cDHyiPgs9u/qm4ght+luYMFK0W4I
KuIXqaWD58kGZkro0/B1SRNDcwOLxL3g03UT0rmmwZEIS0y6F+1Ygk3K8uBMwT+m
x7wrxs3Gqo0jr6ND+5zqvF2YS/8AUV/vtGQXGBfu9ft+YzfsYrLaMstJTjSuPzeS
zGW8EwsbUgfpRNAVSxzLu/vzJ9KaMTCAeKmbO9jT9lAdQn8S8cA=
=7QiW
-END PGP SIGNATURE End Message ---

Bug#910657: marked as done (syndie: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 14:55:44 +
with message-id 
and subject line Bug#910657: fixed in syndie 1.107b-2
has caused the Debian Bug report #910657,
regarding syndie: Incomplete debian/copyright?
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.)


-- 
910657: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910657
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: syndie
Version: 1.107b-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Masayuki Hatta , ftpmas...@debian.org

Hi,

I just ACCEPTed syndie from NEW but noticed it was missing 
attribution in debian/copyright for at least Adam Buckley, Gregory
Rubin...

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


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: syndie
Source-Version: 1.107b-2

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

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

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

Debian distribution maintenance software
pp.
Masayuki Hatta  (supplier of updated syndie 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, 12 Oct 2018 22:31:52 +0900
Source: syndie
Binary: syndie
Architecture: source all
Version: 1.107b-2
Distribution: unstable
Urgency: medium
Maintainer: Masayuki Hatta 
Changed-By: Masayuki Hatta 
Description:
 syndie - system for operating distributed forums
Closes: 910657 910752
Changes:
 syndie (1.107b-2) unstable; urgency=medium
 .
   * d/install: Install png and svg icons for desktop.
   * d/copyright: Clarify licensing - closes: #910657
   * Made the build reproducible, thanks Chirs Lamb - closes: #910752
Checksums-Sha1:
 6968486a92071397c84d58226a3a31da212d5c68 1905 syndie_1.107b-2.dsc
 08f03061b9b012341b0624cb255adc280f694106 9908 syndie_1.107b-2.debian.tar.xz
 8ae16501d2923916618bcfb5ae88383a7682 4190464 syndie_1.107b-2_all.deb
 a1041604570ae79867c9aac6dfcc9e16d55a7124 11123 syndie_1.107b-2_amd64.buildinfo
Checksums-Sha256:
 c002fdbb5735018f6bb2c8b1a9cc022ca68bef459fa639ce146e7ad1df0c5e5a 1905 
syndie_1.107b-2.dsc
 8114938970f3b9b9ebf10663e01175ff70e3a8fabef31b236e0d7dc7764528b0 9908 
syndie_1.107b-2.debian.tar.xz
 20c50df3da494643aafc33ac5259f4c30a5b18cc3fd96c71fdd7edaa07d14c3c 4190464 
syndie_1.107b-2_all.deb
 1d672b9f0eda59aacd299ceeb027d46f49e6de7333788fc71c5576d303149f32 11123 
syndie_1.107b-2_amd64.buildinfo
Files:
 4ce141aa24b22f532f58f52818494a5c 1905 net optional syndie_1.107b-2.dsc
 d0baaa8f5854927ba4ea8c6a1bb77095 9908 net optional 
syndie_1.107b-2.debian.tar.xz
 704eaaa993590b68f5148624558edc11 4190464 net optional syndie_1.107b-2_all.deb
 6fc43cac201670d138680fcb05953ca4 11123 net optional 
syndie_1.107b-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEZDzS6N3LAPjxWBIb3a4SYm4UEDUFAlvArNASHG1oYXR0YUBk
ZWJpYW4ub3JnAAoJEN2uEmJuFBA1FyMP/0nbefou7tnZpSxE9LiJ5hVi4xgmhZ5Q
yHiqX54oDVLbbjVm64SnPNBjGKnSmfRbQ9t3IDRBQklFZbNU2GSrr6laZQ5Z1Ilh
ovFUQ3AOcg81/LtHjYrVhjxgkY8eHQCVDXn8E2QBTd82decBmu1Mtaov8ZPWgMqe
m5ounAwtbzeOIBpOa/Z/g/2b5Lho6C7uMTKWBLv8yjdiiX0RMEL77qzJwXZxWZQa
eOn0fSHSF13Pz7L1GxdWqzy7LZ73/ULaapWZ6Ft71aFQYUiFFnnQb+iWAWse0mu/
DdCbwiUUNAlPbYSYd3cMPzkro2iK7SAj2q45OfciQbB2IVYZ5NOfYlJVkZA4Fmgy
0Yfpwe/T7BlEcYKg6ItG1igp9uHaR5GHbpFQ1ZOOBAY7j8jsOEg+v4IpspCmjNUu
/hdTKjC2JMzn57PlayO1QLCy6LtZ1nhIQKQYtXc1cU0P1nJ481Sani8/hn/O2aJ4
fkFQImnM43REFe/bGCHpX4hkQVhRdfSO8VP2/9pjRZcIV7wWvq6dQPIsRCELAsoy
SgOnWcpvSNAN7b94nKQs4ONfpJ4AHET5hxwYJZ0KBxx2cCHU5z29Vf8d8AeqVuoc
tHeIFHfFSs5i1Sppp5MuR53pqV15EjItc9C9LmLitqX83w6InzmZgw7j+BKW6VOS
cU8LlwrPqNtP
=9vxH
-END PGP SIGNATURE End Message ---

Bug#910808: marked as done (sagemath: Sage crashes on startup, seems to be compiled against wrong libsingular version)

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 16:49:12 +0200
with message-id <18341834-181c-e033-e515-bb4ff5e23...@debian.org>
and subject line Re: Bug#910808: sagemath: Sage crashes on startup, seems to be 
compiled against wrong libsingular version
has caused the Debian Bug report #910808,
regarding sagemath: Sage crashes on startup, seems to be compiled against wrong 
libsingular version
to be marked as done.

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

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


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

Dear Maintainer,

The relevant output from the crash report:

ImportError: libsingular-factory-4.1.0.so: cannot open shared object file: No 
such file or directory

I believe, given the dependencies of sagemath 8.3, that it should be compiled 
against libsingular 4.1.1, not 4.1.0

Thanks!

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

Kernel: Linux 4.18.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)
LSM: AppArmor: enabled

Versions of packages sagemath depends on:
ii  cysignals-tools  1.6.7+ds-4
ii  cython   0.28.4-1
ii  ecl  16.1.2-4+b1
ii  eclib-tools  20171002-1+b3
ii  f2c  20160102-1
ii  fflas-ffpack 2.3.2-3
ii  flintqs  1:1.0-3
ii  gap-core 4r8p8-3
ii  gfan 0.6.2-2
ii  gmp-ecm  7.0.4+ds-3
ii  ipython  5.5.0-1
ii  iso-codes4.1-1
ii  jmol 14.6.4+2016.11.05+dfsg1-3.1
ii  lcalc1.23+dfsg-7
ii  less 487-0.1+b1
ii  libatlas3-base [liblapack.so.3]  3.10.3-7+b1
ii  libblas3 [libblas.so.3]  3.8.0-1+b1
ii  libbrial-groebner3   1.2.0-2
ii  libbrial31.2.0-2
ii  libc62.27-6
ii  libcdd-tools 094h-1+b1
ii  libcliquer1  1.21-2
ii  libec3   20171002-1+b3
ii  libecm1  7.0.4+ds-3
ii  libflint-2.5.2   2.5.2-18
ii  libflint-arb21:2.14.0-4
ii  libgap-sage-44.8.8+3+20160327g69a66f0+dsx-1
ii  libgcc1  1:8.2.0-7
ii  libgd3   2.2.5-4
ii  libgivaro9   4.0.4-2
ii  libglpk404.65-2
ii  libgmp10 2:6.1.2+dfsg-3
ii  libgmpxx4ldbl2:6.1.2+dfsg-3
ii  libgsl23 2.5+dfsg-5
ii  libgslcblas0 2.5+dfsg-5
ii  libiml0  1.0.4-1+b2
ii  libjs-mathjax2.7.4+dfsg-1
ii  libjs-three  80+dfsg2-2
ii  liblapack3 [liblapack.so.3]  3.8.0-1+b1
ii  liblfunction01.23+dfsg-7
ii  liblinbox-1.5.2-01.5.2-2
ii  liblinboxsage-1.5.2-01.5.2-2
ii  liblrcalc1   1.2-2+b1
ii  libm4ri-0.0.20140914 20140914-2+b1
ii  libm4rie-0.0.2015090820150908-2
ii  libmpc3  1.1.0-1
ii  libmpfi0 1.5.3+ds-2
ii  libmpfr6 4.0.1-1
ii  libntl35

Bug#910861: Tool for managing users and groups will not start any more

[Bruninksbeek]

Package: mate-system-tools
Version: 1.8.1+dfsg1-2
Severity: grave
Tags:


Dear maintainer

I use Debian Jessie with the MATE desktop environment.

The application for adding and removing users and groups (command: 
mate-users-admin) will not start any more when clicking:


System > Management > Users and groups

System log:
Oct 11 13:51:30 desktop-computer kernel: [ 1141.192153] traps: 
mate-users-admi[2865] trap int3 ip:7f982286b261 sp:7ffda2bb4830 error:0
Oct 11 13:51:30 desktop-computer kernel: [ 1141.192157] in 
libglib-2.0.so.0.5000.3[7f982281b000+112000]


When using a terminal window:
root@desktop-computer:/home/maarten# mate-users-admin

(mate-users-admin:5553): Gtk-ERROR **: GTK+ 2.x symbols detected. Using 
GTK+ 2.x and GTK+ 3 in the same process is not supported

Traceer/breekpunt-instructie
root@desktop-computer:/home/maarten#

I did not have this problem earlier. I do not have any broken packages 
and debsums -as indicated that all my packages are intact.


Synaptic (package manager) tells that mate-system-tools also contains 
the tool for adjusting the date and time, and the tool for setting the 
network options. These two tools were found easily in the Configuration 
Centre. However, those tools also do not start any more.


Debian Jessie is being advised for production machines. I hope that this 
programming error gets corrected soon.


With kind regards

Maarten

Bug#872806: [pkg-gnupg-maint] Bug#872806: libgpg-error0 packs runtime support files in shared library

[Daniel Kahn Gillmor]

On Fri 2018-10-12 12:36:12 +0200, Sven Joachim wrote:
> Control: tags -1 + patch

thank you, Sven and Helmut for your attention to this kind of detail.
I'm preparing an upload with these changes.

Y'all rock!

  --dkg

Bug#894284: android-platform-tools-base FTBFS with openjdk-9

[Emmanuel Bourg]

The javax.xml.bind errors can be simply fixed by adding a dependency
on jaxb-api:

--- a/repository/build.gradle
+++ b/repository/build.gradle
@@ -9,6 +9,7 @@
 compile project(':base:common')
 compile 'org.apache.commons:commons-compress:1.8.1'
 compile 'com.google.jimfs:jimfs:1.1'
+compile 'javax.xml.bind:jaxb-api:debian'

 testCompile 'junit:junit:4.12'
 }


There is another error with Java 10 caused by a change in the return
type of javax.xml.namespace.NamespaceContext.getPrefixes().
It's easily fixed with:

--- a/common/src/main/java/com/android/xml/AndroidXPathFactory.java
+++ b/common/src/main/java/com/android/xml/AndroidXPathFactory.java
@@ -81,7 +81,7 @@
 }

 @Override
-public Iterator getPrefixes(String namespaceURI) {
+public Iterator getPrefixes(String namespaceURI) {
 if (SdkConstants.NS_RESOURCES.equals(namespaceURI)) {
 return mAndroidPrefixes.iterator();
 }


Unfortunately there is another issue with SignedJarBuilder:

  
/build/android-platform-tools-base-2.2.2/sdklib/src/main/java/com/android/sdklib/internal/build/SignedJarBuilder.java:23:
 error: package sun.security.pkcs is not visible
  import sun.security.pkcs.ContentInfo;
 ^
(package sun.security.pkcs is declared in module java.base, which does not 
export it to the unnamed module)
  
/build/android-platform-tools-base-2.2.2/sdklib/src/main/java/com/android/sdklib/internal/build/SignedJarBuilder.java:24:
 error: package sun.security.pkcs is not visible
  import sun.security.pkcs.PKCS7;
 ^
(package sun.security.pkcs is declared in module java.base, which does not 
export it to the unnamed module)
  
/build/android-platform-tools-base-2.2.2/sdklib/src/main/java/com/android/sdklib/internal/build/SignedJarBuilder.java:25:
 error: package sun.security.pkcs is not visible
  import sun.security.pkcs.SignerInfo;
 ^
(package sun.security.pkcs is declared in module java.base, which does not 
export it to the unnamed module)
  
/build/android-platform-tools-base-2.2.2/sdklib/src/main/java/com/android/sdklib/internal/build/SignedJarBuilder.java:26:
 error: package sun.security.x509 is not visible
  import sun.security.x509.AlgorithmId;
 ^
(package sun.security.x509 is declared in module java.base, which does not 
export it to the unnamed module)
  
/build/android-platform-tools-base-2.2.2/sdklib/src/main/java/com/android/sdklib/internal/build/SignedJarBuilder.java:27:
 error: package sun.security.x509 is not visible
  import sun.security.x509.X500Name;
 ^
(package sun.security.x509 is declared in module java.base, which does not 
export it to the unnamed module)

Bug#906336: marked as done (bintray-client-java: FTBFS in buster/sid)

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 12:48:56 +
with message-id 
and subject line Bug#906336: fixed in bintray-client-java 0.8.1-4
has caused the Debian Bug report #906336,
regarding bintray-client-java: FTBFS in buster/sid
to be marked as done.

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

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


-- 
906336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906336
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bintray-client-java
Version: 0.8.1-3
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=gradle --with javahelper
   dh_update_autotools_config -i -O--buildsystem=gradle
   dh_auto_configure -i -O--buildsystem=gradle
   jh_linkjars -i -O--buildsystem=gradle
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- assemble javadoc
mkdir -p .gradle/init.d
cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
gradle --info --console plain --offline --stacktrace --no-daemon 
--refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
-Duser.name=debian -Ddebian.package=bintray-client-java -Dfile.encoding=UTF-8 
assemble javadoc
Initialized native services in: /<>/.gradle/native
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.gradle.internal.reflect.JavaMethod 
(file:/usr/share/gradle/lib/gradle-base-services-3.4.1.jar) to method 
java.lang.ClassLoader.getPackages()

[... snipped ...]

at 
org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
at 
org.gradle.launcher.daemon.server.exec.LogAndCheckHealth.execute(LogAndCheckHealth.java:50)
at 
org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
at 
org.gradle.launcher.daemon.server.exec.LogToClient.doBuild(LogToClient.java:60)
at 
org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
at 
org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
at 
org.gradle.launcher.daemon.server.exec.EstablishBuildEnvironment.doBuild(EstablishBuildEnvironment.java:72)
at 
org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
at 
org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:120)
at 
org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy$1.run(StartBuildOrRespondWithBusy.java:50)
at 
org.gradle.launcher.daemon.server.DaemonStateCoordinator$1.run(DaemonStateCoordinator.java:297)
at 
org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at 
org.gradle.internal.concurrent.StoppableExecutorImpl$1.run(StoppableExecutorImpl.java:46)
Caused by: org.gradle.api.GradleException: Javadoc generation failed. Generated 
Javadoc options file (useful for troubleshooting): 
'/<>/api/build/tmp/javadoc/javadoc.options'
at 
org.gradle.api.tasks.javadoc.internal.JavadocGenerator.execute(JavadocGenerator.java:58)
at 
org.gradle.api.tasks.javadoc.internal.JavadocGenerator.execute(JavadocGenerator.java:31)
at 
org.gradle.api.tasks.javadoc.Javadoc.executeExternalJavadoc(Javadoc.java:157)
at org.gradle.api.tasks.javadoc.Javadoc.generate(Javadoc.java:145)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73)
at 
org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.doExecute(DefaultTaskClassInfoStore.java:141)
at 
org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.execute(DefaultTaskClassInfoStore.java:134)
at 
org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.execute(DefaultTaskClassInfoStore.java:123)
at 
org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:632)
at 
org.gradle.api.internal.AbstractTask$TaskActio

Bug#910858: tpm2-tss: FTBFS on big endian architectures: test failures

[Emilio Pozuelo Monfort]

Source: tpm2-tss
Version: 2.1.0-1
Severity: serious
Tags: ftbfs

Hi,

Your package failed to build on big endian architectures:

[ RUN  ] tpm2b_unmarshal_success
[  ERROR   ] --- 0xefbeadde != 0xdeadbeef
[   LINE   ] --- test/unit/TPM2B-marshal.c:213: error: Failure!
[  FAILED  ] tpm2b_unmarshal_success
[ RUN  ] tpm2b_unmarshal_success_offset
[  ERROR   ] --- 0xefbeadde != 0xdeadbeef
[   LINE   ] --- test/unit/TPM2B-marshal.c:254: error: Failure!
[  FAILED  ] tpm2b_unmarshal_success_offset

Full logs at

https://buildd.debian.org/status/package.php?p=tpm2-tss

Emilio

Processed: Re: Bug#890606: Patch for kopete 18.04.2-1 in experimental

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #890606 [src:kopete] src:kopete: FTBFS against libmediastreamer 2.16
Severity set to 'serious' from 'important'
> tags -1 - help
Bug #890606 [src:kopete] src:kopete: FTBFS against libmediastreamer 2.16
Removed tag(s) help.

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

Processed: Bug #906336 in bintray-client-java marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #906336 [src:bintray-client-java] bintray-client-java: FTBFS in buster/sid
Added tag(s) pending.

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

Bug#906336: Bug #906336 in bintray-client-java marked as pending

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/bintray-client-java/commit/2ac50605bef398ef98920d04a6b12199c8699cf1


Added the missing build dependency on default-jdk-doc (Closes: #906336)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/906336

Processed: Re: openjfx FTBFS on big endian: ../lib/icupkg: No such file or directory

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #880359 [src:openjfx] openjfx FTBFS on big endian: ../lib/icupkg: No such 
file or directory
Severity set to 'important' from 'serious'
> tags -1 + help
Bug #880359 [src:openjfx] openjfx FTBFS on big endian: ../lib/icupkg: No such 
file or directory
Added tag(s) help.

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

Bug#880359: openjfx FTBFS on big endian: ../lib/icupkg: No such file or directory

[Emmanuel Bourg]

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

Downgrading the severity, upstream doesn't support non x86 architectures
and the packages are only provided as a best effort.

Processed: Re: icedtea-web: FTBFS: configure: error: Package requirements (mozilla-plugin) were not met

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #855686 [src:icedtea-web] icedtea-web: FTBFS: configure: error: Package 
requirements (mozilla-plugin) were not met
Added tag(s) pending.

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

Bug#855686: icedtea-web: FTBFS: configure: error: Package requirements (mozilla-plugin) were not met

[Emmanuel Bourg]

Control: tags -1 + pending

The plugin is being removed

Bug#897106: marked as done (jpylyzer FTBFS with pandoc 2.1.2)

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 11:36:52 +
with message-id 
and subject line Bug#897106: fixed in jpylyzer 1.18.0-3
has caused the Debian Bug report #897106,
regarding jpylyzer FTBFS with pandoc 2.1.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.)


-- 
897106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=897106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jpylyzer
Version: 1.18.0-2
Severity: serious

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

...
dh_auto_build
python setup.py build --force
running build
running build_py
creating build
creating build/lib.linux-x86_64-2.7
creating build/lib.linux-x86_64-2.7/jpylyzer
copying jpylyzer/shared.py -> build/lib.linux-x86_64-2.7/jpylyzer
copying jpylyzer/jpylyzer.py -> build/lib.linux-x86_64-2.7/jpylyzer
copying jpylyzer/etpatch.py -> build/lib.linux-x86_64-2.7/jpylyzer
copying jpylyzer/config.py -> build/lib.linux-x86_64-2.7/jpylyzer
copying jpylyzer/byteconv.py -> build/lib.linux-x86_64-2.7/jpylyzer
copying jpylyzer/boxvalidator.py -> build/lib.linux-x86_64-2.7/jpylyzer
copying jpylyzer/__main__.py -> build/lib.linux-x86_64-2.7/jpylyzer
copying jpylyzer/__init__.py -> build/lib.linux-x86_64-2.7/jpylyzer
copying jpylyzer/shared.py -> build/lib.linux-x86_64-2.7/jpylyzer
copying jpylyzer/jpylyzer.py -> build/lib.linux-x86_64-2.7/jpylyzer
copying jpylyzer/etpatch.py -> build/lib.linux-x86_64-2.7/jpylyzer
copying jpylyzer/config.py -> build/lib.linux-x86_64-2.7/jpylyzer
copying jpylyzer/byteconv.py -> build/lib.linux-x86_64-2.7/jpylyzer
copying jpylyzer/boxvalidator.py -> build/lib.linux-x86_64-2.7/jpylyzer
copying jpylyzer/__main__.py -> build/lib.linux-x86_64-2.7/jpylyzer
copying jpylyzer/__init__.py -> build/lib.linux-x86_64-2.7/jpylyzer
(cd doc && pandoc -s --toc --toc-depth=2 -N --chapters --latex-engine=xelatex 
-o jpylyzerUserManual.pdf jpylyzerUserManual.md)
--chapters has been removed. Use --top-level-division=chapter instead.
--latex-engine has been removed.  Use --pdf-engine instead.
Try pandoc --help for more information.
make[1]: *** [debian/rules:22: override_dh_auto_build] Error 2
--- End Message ---
--- Begin Message ---
Source: jpylyzer
Source-Version: 1.18.0-3

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

Debian distribution maintenance software
pp.
Mathieu Malaterre  (supplier of updated jpylyzer 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: Thu, 11 Oct 2018 21:24:05 +0200
Source: jpylyzer
Binary: python-jpylyzer python-jpylyzer-doc
Architecture: source
Version: 1.18.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Mathieu Malaterre 
Description:
 python-jpylyzer - JP2 (JPEG 2000 Part 1) validator and properties extractor
 python-jpylyzer-doc - JP2 (JPEG 2000 Part 1) validator and properties 
extractor - doc
Closes: 897106
Changes:
 jpylyzer (1.18.0-3) unstable; urgency=medium
 .
   * Bump Std-Vers. No changes needed
   * Fix doc building. Closes: #897106
Checksums-Sha1:
 206ce0fb6573d2c1107bb16514a226793d4ac0f6 2029 jpylyzer_1.18.0-3.dsc
 49092d17a68c993bcfbe51a45d78d2c4c8dafdb6 3836 jpylyzer_1.18.0-3.debian.tar.xz
 0f6ff196facf3fbec8389bb35d32cee17aee5da1 9136 
jpylyzer_1.18.0-3_source.buildinfo
Checksums-Sha256:
 e5e2f21235cb8e768a384f4b30575be9f84bd0747cd801777a5c38f255505c90 2029 
jpylyzer_1.18.0-3.dsc
 6f479e70d652bc181e718eaa5a0ebe2b2a916a2d574e45683f8904fa0f1e0b0a 3836 
jpylyzer_1.18.0-3.debian.tar.xz
 0b1aba600cce96711dd3e8b89a4af1753ee3b332f83d15e7b0d2b3a97f5a3e9b 9136 
jpylyzer_1.18.0-3_source.buildinfo
Files:
 78464c56fabe87fcaeb964c0c3971a55 2029 python optional jpylyzer_1.18.0-3.dsc
 f2d66d06ab08d6978c697a0e13f992e9 3836 python optional 
jpylyzer_1.18.0-3.debian.tar.xz
 245ff989283f6936098c50ecd3f5e11c 9136 python optional 
jpylyzer_1.18.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEaTNn/67NjqrNHwY7AXHhgorgk0UFAlvAgxERHG1hbGF0QGRl
Ymlhbi5vcmcACgkQAXHhgorgk0VtDhAAktL60JrZAv8jgq/GRWU0kiiSxBHrws+

Bug#894287: marked as done (android-platform-frameworks-data-binding FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 11:34:10 +
with message-id 
and subject line Bug#894287: fixed in android-platform-frameworks-data-binding 
2.2.2-3
has caused the Debian Bug report #894287,
regarding android-platform-frameworks-data-binding FTBFS with openjdk-9
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.)


-- 
894287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=894287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: android-platform-frameworks-data-binding
Version: 2.2.2-2
Severity: serious
Tags: buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/android-platform-frameworks-data-binding.html

...
/build/1st/android-platform-frameworks-data-binding-2.2.2/compilerCommon/src/main/java/android/databinding/tool/store/ResourceBundle.java:37:
 error: package javax.xml.bind is not visible
import javax.xml.bind.JAXBContext;
^
  (package javax.xml.bind is declared in module java.xml.bind, which is not in 
the module graph)
/build/1st/android-platform-frameworks-data-binding-2.2.2/compilerCommon/src/main/java/android/databinding/tool/store/ResourceBundle.java:38:
 error: package javax.xml.bind is not visible
import javax.xml.bind.JAXBException;
^
  (package javax.xml.bind is declared in module java.xml.bind, which is not in 
the module graph)
/build/1st/android-platform-frameworks-data-binding-2.2.2/compilerCommon/src/main/java/android/databinding/tool/store/ResourceBundle.java:39:
 error: package javax.xml.bind is not visible
import javax.xml.bind.Marshaller;
^
  (package javax.xml.bind is declared in module java.xml.bind, which is not in 
the module graph)
/build/1st/android-platform-frameworks-data-binding-2.2.2/compilerCommon/src/main/java/android/databinding/tool/store/ResourceBundle.java:40:
 error: package javax.xml.bind is not visible
import javax.xml.bind.Unmarshaller;
^
  (package javax.xml.bind is declared in module java.xml.bind, which is not in 
the module graph)
/build/1st/android-platform-frameworks-data-binding-2.2.2/compilerCommon/src/main/java/android/databinding/tool/store/ResourceBundle.java:41:
 error: package javax.xml.bind.annotation is not visible
import javax.xml.bind.annotation.XmlAccessType;
 ^
  (package javax.xml.bind.annotation is declared in module java.xml.bind, which 
is not in the module graph)
...
--- End Message ---
--- Begin Message ---
Source: android-platform-frameworks-data-binding
Source-Version: 2.2.2-3

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

Debian distribution maintenance software
pp.
Emmanuel Bourg  (supplier of updated 
android-platform-frameworks-data-binding 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, 12 Oct 2018 13:02:22 +0200
Source: android-platform-frameworks-data-binding
Binary: libandroid-databinding-java
Architecture: source
Version: 2.2.2-3
Distribution: unstable
Urgency: medium
Maintainer: Android Tools Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 libandroid-databinding-java - Android Data Binding Library
Closes: 894287
Changes:
 android-platform-frameworks-data-binding (2.2.2-3) unstable; urgency=medium
 .
   * Team upload.
   * Added a dependency on JAXB to fix the build failure with Java 9
 (Closes: #894287)
   * Standards-Version updated to 4.2.1
   * Switch to debhelper level 11
Checksums-Sha1:
 d4331110cdc23fea84522f230456caa9d081b6d5 2520 
android-platform-frameworks-data-binding_2.2.2-3.dsc
 bbd9a3f7f6a3d2a80e9e552491d1272f0933fe9f 6784 
android-platform-frameworks-data-binding_2.2.2-3.debian.tar.xz
 c4fe10bf599a5ca4b5ef14fab9430ef81a3b92ec 15476 
android-platform-frameworks-data-binding_2.2.2-3_source.buildinfo
Checksums-Sha256:
 f872547afe4139f7a64cfe6f3615c5d097ab5030e8a7c56298df0efa2944da44 2520 
android-platform-frameworks-data-binding_2.2.2-3.dsc
 7fd1963469e563559257bb9235a27034683f57f0f5c2cd7711cbe44c6065c39f 6784 
android-platform-frameworks-data-b

Processed: New version uploaded - does that problem persist?

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #909990 [src:nibabel] nibabel: FTBFS (Failed example)
Severity set to 'important' from 'serious'
> tags -1 moreinfo
Bug #909990 [src:nibabel] nibabel: FTBFS (Failed example)
Added tag(s) moreinfo.

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

Bug#909990: New version uploaded - does that problem persist?

[Andreas Tille]

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

Hi Santiago,

thanks for your QA check.  I have uploaded a new version.  Could you
please redo your batch job with this version and confirm whether the
problem persists or if it is possibly solved by the new version?

Kind regards

  Andreas.

-- 
http://fam-tille.de

Bug#904459: Uploading soon?

[Daniel Baumann]

On 10/12/2018 09:56 AM, Tollef Fog Heen wrote:
> any chance you could find time to get this uploaded soon? It'd be great
> to have netdata back in testing (and in buster when it gets released).

yep, working on it.. will take a couple of days though. having netdata
in buster is important to me too.

Regards,
Daniel

Bug#910854: marked as done (distro-info: FTBFS: test failure: UnicodeDecodeError)

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 13:14:44 +0200
with message-id <20181012111443.oluh5bot4rom6...@debian.org>
and subject line Re: distro-info: FTBFS: test failure: UnicodeDecodeError
has caused the Debian Bug report #910854,
regarding distro-info: FTBFS: test failure: UnicodeDecodeError
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.)


-- 
910854: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910854
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: src:distro-info
version: 0.19
severity: serious
tags: ftbfs

Hi,

The latest version of distro-info in unstable fails on all architectures:

https://buildd.debian.org/status/package.php?p=distro-info

cd python && python3.6 setup.py test
Traceback (most recent call last):
  File "setup.py", line 32, in 
version=get_debian_version(),
  File "setup.py", line 22, in get_debian_version
head = open(changelog).readline()
  File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc5 in position 111: 
ordinal not in range(128)
make[1]: *** [Makefile:40: test-python] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: make -j4 test returned exit code 2
make: *** [debian/rules:6: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


Cheers,

Ivo
--- End Message ---
--- Begin Message ---
Version: 0.20

On Fri, Oct 12, 2018 at 10:16:23AM +, Ivo De Decker wrote:
> The latest version of distro-info in unstable fails on all architectures:

This is fixed in 0.20, which was uploaded around the same time I filed the
bug. Sorry for the noise.

Ivo--- End Message ---

Bug#910457: marked as done (syncany: FTBFS: dh_installman: Cannot find (any matches for) "/build/syncany-0.4.9~alpha/build/debian/syncany/debian/man/sy-cleanup.1" (tried in .))

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 11:11:55 +
with message-id 
and subject line Bug#910457: fixed in syncany 0.4.9~alpha-2
has caused the Debian Bug report #910457,
regarding syncany: FTBFS: dh_installman: Cannot find (any matches for) 
"/build/syncany-0.4.9~alpha/build/debian/syncany/debian/man/sy-cleanup.1" 
(tried in .)
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.)


-- 
910457: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910457
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: syncany
Version: 0.4.9~alpha-1
Severity: serious
Justification: fails to build from source

Hi,

syncany cannot be built in a current sid+experimental environment any
more:

[...]
 fakeroot debian/rules binary
dh binary --with bash-completion
   dh_testroot
   dh_prep
   dh_auto_install
   debian/rules override_dh_install
make[1]: Entering directory '/build/syncany-0.4.9~alpha'
rm -f build/install/syncany/bin/*.bat
dh_install
make[1]: Leaving directory '/build/syncany-0.4.9~alpha'
   dh_installdocs
   debian/rules override_dh_installchangelogs
make[1]: Entering directory '/build/syncany-0.4.9~alpha'
dh_installchangelogs build/install/syncany/CHANGELOG.md
make[1]: Leaving directory '/build/syncany-0.4.9~alpha'
   dh_installman
dh_installman: Cannot find (any matches for) 
"/build/syncany-0.4.9~alpha/build/debian/syncany/debian/man/sy-cleanup.1" 
(tried in .)

dh_installman: Aborting due to earlier error
make: *** [debian/rules:4: binary] Error 25
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit 
status 2


Andreas


syncany_0.4.9~alpha-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: syncany
Source-Version: 0.4.9~alpha-2

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

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

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated syncany 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, 12 Oct 2018 12:24:03 +0200
Source: syncany
Binary: syncany
Architecture: source
Version: 0.4.9~alpha-2
Distribution: experimental
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 syncany- secure cloud storage and filesharing application
Closes: 910457
Changes:
 syncany (0.4.9~alpha-2) experimental; urgency=medium
 .
   * Switch to compat level 11.
   * Use https for Format field.
   * Declare compliance with Debian Policy 4.2.1.
   * Create a manpages file and avoid using a automatic method in
 debian/rules which apparently fixes the current build failure.
 Thanks to Andreas Beckmann for the report. (Closes: #910457)
Checksums-Sha1:
 5d4c1d024d3550aca0deffe082344a799a8f618d 2429 syncany_0.4.9~alpha-2.dsc
 5e5179d97bcc879e1b583110f4b9797c11c4ed26 4668 
syncany_0.4.9~alpha-2.debian.tar.xz
 795d25c408e712656a86d86149ee3950a264ddbb 15125 
syncany_0.4.9~alpha-2_amd64.buildinfo
Checksums-Sha256:
 6061557f2e4b47bbdd4d20b75753ed55db6ade30529d7b281a07cf8168072464 2429 
syncany_0.4.9~alpha-2.dsc
 9e315cc6c617ff74dd212c7a5c2f71626d3829d05a85befc7f35764ae0e1bb6f 4668 
syncany_0.4.9~alpha-2.debian.tar.xz
 b68ae7c601e5d40f6ee6e79c10ba2ca28d1a36ff69266d4b5931de900859737b 15125 
syncany_0.4.9~alpha-2_amd64.buildinfo
Files:
 33744e24c078998d76e61358b1973b4d 2429 utils optional syncany_0.4.9~alpha-2.dsc
 f8d72e2eab33594f80fc4abb5188221d 4668 utils optional 
syncany_0.4.9~alpha-2.debian.tar.xz
 0f8f2820bf51d9d2a2f5aca6d2389808 15125 utils optional 
syncany_0.4.9~alpha-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlvAd3lfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HksgkQAJ0D7ycFppyc3jSI5CLIdJkgIu19C3FfqG2e
uF+c6M6LsiqBaLlR0lKJ3hqygxpSJKiY5RfsJ5wXVpOwsrosU6A29vC+pKZZ6/CT
AIaEd0GxhySvGiloKGyRwpks6JthYJ6G+M0aEasisSBTN4MWQliN7xHjC9Aw9M42
nG5js5y5fBRHbh22ECwfH3dLN5xBLFRqPWeOIhSgji+fvs3uY3u/LmhJ/2fId7aN
rk1VkCONivli14V9/YbYSHjsAnjZNoaJqITOu

Processed: Re: Bug#906366: Seems to be fixed in 1.28-1

[Debian Bug Tracking System]

Processing control commands:

> notfound 906366 1.28-1
Bug #906366 {Done: Emmanuel Bourg } [src:ivyplusplus] 
ivyplusplus: FTBFS in buster/sid
No longer marked as found in versions ivyplusplus/1.28-1.

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

Bug#906366: Seems to be fixed in 1.28-1

[Ivo De Decker]

Control: notfound 906366 1.28-1

On Tue, Oct 09, 2018 at 02:36:37PM +0200, Emmanuel Bourg wrote:
> The error on the builders is the following:

[...]

> If I'm not mistaken this was fixed in liblombok-java/1.16.22-3

1.28-1 builds fine in buster now and built fine in unstable (on 2018-10-09
12:32, after the liblombok-java upload and before the 1.28-2 upload), so
removing the found version to make sure this bug is no longer marked as
affecting testing and unstable.

https://tests.reproducible-builds.org/debian/history/ivyplusplus.html

Cheers,

Ivo

Processed: Re: Bug#872806: libgpg-error0 packs runtime support files in shared library

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #872806 [libgpg-error0] libgpg-error0 packs runtime support files in shared 
library
Added tag(s) patch.

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

Bug#872806: libgpg-error0 packs runtime support files in shared library

[Sven Joachim]

Control: tags -1 + patch

Am 21.08.2017 um 14:53 schrieb Helmut Grohne:

> Package: libgpg-error0
> Version: 1.27-3
> Severity: serious
> Justification: policy 8.2
> User: helm...@debian.org
> Usertags: rebootstrap
>
> libgpg-error0 packs runtime support files (i.e. .mo files) into the
> shared library package. It happens that these files are not versioned
> (e.g. libgpg-error.mo rather than libgpg-error0.mo). Doing so violates
> Debian policy section 8.2:
>
> |If your package contains files whose names do not change with each change
> |in the library shared object version, you must not put them in the shared
> |library package. Otherwise, several versions of the shared library cannot
> |be installed at the same time without filename clashes, making upgrades
> |and transitions unnecessarily difficult.

There are a few other library package which include .mo files, but most
include the soname in their filename, so they don't have that problem.

> This happens to also break multiarch. Rebuilds of libgpg-error are not
> currently coinstallable with other instances from the archive:
>
> | Unpacking libgpg-error-dev:ppc64 (1.27-3) ...
> | dpkg: error processing archive 
> /tmp/repo/pool/main/libg/libgpg-error/libgpg-error0_1.27-3_ppc64.deb 
> (--unpack):
> |  trying to overwrite shared
> | '/usr/share/locale/cs/LC_MESSAGES/libgpg-error.mo', which is
> | different from other instances of package libgpg-error0:ppc64
> | Errors were encountered while processing:
> |  /tmp/repo/pool/main/libg/libgpg-error/libgpg-error0_1.27-3_ppc64.deb
> | E: Sub-process /usr/bin/dpkg returned an error code (1)
> | E: Failed to process build dependencies

This was apparently due to some changes in msgfmt's output format at the
time.  It does not seem to be a problem currently, but future changes in
msgfmt might bring it up again.

> I suggest moving them to an Arch:all package.

Attached is a patch which does that, introducing a libgpg-error-l10n
package with the translation files.  The exact Provides/Replaces
versions might have to be adjusted, and the exact relationship between
libgpg-error0 and libgpg-error-l10n is also debatable.  I have chosen an
unversioned Recommends, but others are also possible.  What would not
work is an exact "Depends: libgpg-error-l10n (= ${source:Version}),
since that breaks when libgpg-error1 comes along.

Cheers,
   Sven

>From da01ec471e451de75415589bb5ba942599ee5d26 Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Fri, 12 Oct 2018 11:25:02 +0200
Subject: [PATCH] Move the translation files to a new libgpg-error-l10n package

Closes: #872806
---
 debian/control   | 22 ++
 debian/libgpg-error-l10n.install |  1 +
 debian/libgpg-error0.install.in  |  1 -
 3 files changed, 23 insertions(+), 1 deletion(-)
 create mode 100644 debian/libgpg-error-l10n.install

diff --git a/debian/control b/debian/control
index 1ff8e2e..ec14e5c 100644
--- a/debian/control
+++ b/debian/control
@@ -43,6 +43,8 @@ Depends:
  ${shlibs:Depends},
 Pre-Depends:
  ${misc:Pre-Depends},
+Recommends:
+ libgpg-error-l10n,
 Description: GnuPG development runtime library
  Library that defines common error values, messages, and common
  runtime functionality for all GnuPG components.  Among these are GPG,
@@ -102,3 +104,23 @@ Description: library of error values and messages in GnuPG (Windows development)
  This is a Windows version of libgpg-error.  It's meant to be used
  when cross-building software that targets the Windows platform,
  e.g. the win32-loader component of Debian-Installer.
+
+Package: libgpg-error-l10n
+Architecture: all
+Section: localization
+Multi-Arch: foreign
+Depends:
+ ${misc:Depends},
+Replaces:
+ libgpg-error0 (<< 1.32-1.1~),
+Breaks:
+ libgpg-error0 (<< 1.32-1.1~),
+Description: library of error values and messages in GnuPG (localization files)
+ Library that defines common error values, messages, and common
+ runtime functionality for all GnuPG components.  Among these are GPG,
+ GPGSM, GPGME, GPG-Agent, libgcrypt, pinentry, SmartCard Daemon and
+ possibly more in the future.
+ .
+ It will likely be renamed "gpgrt" in the future.
+ .
+ This package contains the translation files for the use in non-English locales.
diff --git a/debian/libgpg-error-l10n.install b/debian/libgpg-error-l10n.install
new file mode 100644
index 000..3635480
--- /dev/null
+++ b/debian/libgpg-error-l10n.install
@@ -0,0 +1 @@
+usr/share/locale
diff --git a/debian/libgpg-error0.install.in b/debian/libgpg-error0.install.in
index ebdeae6..eea2676 100644
--- a/debian/libgpg-error0.install.in
+++ b/debian/libgpg-error0.install.in
@@ -1,2 +1 @@
 usr/lib/@DEB_HOST_MULTIARCH@/libgpg-error.so.* lib/@DEB_HOST_MULTIARCH@/
-usr/share/locale
-- 
2.19.1

Bug#897482: brailleutils: FTBFS: [javac] /<>/src/org/daisy/braille/pef/PEFNamespaceContext.java:37: error: PEFNamespaceContext is not abstract and does not override abstract method getPre

[Emmanuel Bourg]

Control: tags -1 + patch

The fix is ready to be merged on Salsa:
https://salsa.debian.org/a11y-team/brailleutils/merge_requests/1

Bug#910852: libqt5webengine5: Akregator crashes very often, WebEngine related - another backtrace

[Martin Steigerwald]

Hello.

I produced another backtrace. Backtraces appear to be random to me.
If its helpful I can produce some more backtrace at a later time.

I think that "A parser-blocking, cross site" message on console is unrelated.
The message comes very often. Also way before it crashes. I think I may
better switch Akregator to use an external web browser that I hardened
before in the future.

WebEnginePage::javaScriptConsoleMessage lineNumber:  1  message:  "Uncaught 
TypeError: Cannot read property 'mobile_detect_force_mobile' of null"
WebEnginePage::javaScriptConsoleMessage lineNumber:  1  message:  "Uncaught 
TypeError: Cannot read property 'getItem' of null"
WebEnginePage::javaScriptConsoleMessage lineNumber:  1  message:  "Uncaught (in 
promise) TypeError: Cannot read property 'getItem' of null"
WebEnginePage::javaScriptConsoleMessage lineNumber:  1  message:  "Uncaught (in 
promise) TypeError: Super expression must either be null or a function, not 
undefined"
WebEnginePage::javaScriptConsoleMessage lineNumber:  1  message:  "TypeError: 
b.toUpperCase is not a function"
[New Thread 0x7fff32a5d700 (LWP 24326)]
WebEnginePage::javaScriptConsoleMessage lineNumber:  2  message:  "JQMIGRATE: 
Migrate is installed, version 1.4.1"
[New Thread 0x7fff3225c700 (LWP 24568)]
[Thread 0x7fff3b7ff700 (LWP 22492) exited]
[New Thread 0x7fff3b7ff700 (LWP 24692)]

Thread 21 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff7700 (LWP 19839)]
0x0020 in ?? ()
(gdb) bt full
#0  0x0020 in ?? ()
No symbol table info available.
#1  0x7fffed18811f in 
QtWebEngineCore::NetworkDelegateQt::OnBeforeURLRequest(net::URLRequest*, 
base::RepeatingCallback const&, GURL*) () from 
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info available.
#2  0x7fffeec1db86 in 
net::NetworkDelegate::NotifyBeforeURLRequest(net::URLRequest*, 
base::RepeatingCallback const&, GURL*) () from 
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info available.
#3  0x7fffeed6c1ab in net::URLRequest::Start() [clone .part.109] () from 
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info available.
#4  0x7fffeda8b01e in content::ResourceLoader::StartRequestInternal() () 
from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info available.
#5  0x7fffeda8bcfd in content::ResourceLoader::Resume(bool) () from 
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info available.
#6  0x7fffeda8beea in content::ResourceLoader::StartRequest() () from 
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info available.
#7  0x7fffeda8562e in 
content::ResourceDispatcherHostImpl::BeginRequestInternal(std::unique_ptr >, 
std::unique_ptr >) () from 
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info available.
#8  0x7fffeda86f4f in 
content::ResourceDispatcherHostImpl::BeginNavigationRequest(content::ResourceContext*,
 net::URLRequestContext*, storage::FileSystemContext*, 
content::NavigationRequestInfo const&, 
std::unique_ptr >, 
content::NavigationURLLoaderImplCore*, 
mojo::InterfacePtr, 
mojo::InterfaceRequest, 
content::ServiceWorkerNavigationHandleCore*, 
content::AppCacheNavigationHandleCore*, unsigned int, 
content::GlobalRequestID*) () from 
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info available.
#9  0x7fffeda74ca5 in 
content::NavigationURLLoaderImplCore::Start(content::ResourceContext*, 
net::URLRequestContextGetter*, storage::FileSystemContext*, 
content::ServiceWorkerNavigationHandleCore*, 
content::AppCacheNavigationHandleCore*, 
std::unique_ptr >, 
std::unique_ptr >) () from 
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info available.
#10 0x7fffeda745b0 in 
base::internal::Invoker >, 
std::unique_ptr >), 
scoped_refptr, content::ResourceContext*, 
base::internal::UnretainedWrapper, 
base::internal::UnretainedWrapper, 
content::ServiceWorkerNavigationHandleCore*, 
content::AppCacheNavigationHandleCore*, 
base::internal::PassedWrapper > >, 
base::internal::PassedWrapper > > >, void 
()>::RunOnce(base::internal::BindStateBase*) () from 
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info available.
#11 0x7fffee71a218 in base::debug::TaskAnnotator::RunTask(char const*, 
base::PendingTask*) () from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info available.
#12 0x7fffee73a91a in base::MessageLoop::RunTask(base::PendingTask*) () 
from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info available.
#13 0x7fffee73b3bf in 
base::MessageLoop::DeferOrRunPendingTask(base::PendingTask) () from 
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info available.
#14 0x7fffee73b558 in base::MessageLoop::DoWork() [clone .part.202] () from 
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info avai

Processed: Re: brailleutils: FTBFS: [javac] /<>/src/org/daisy/braille/pef/PEFNamespaceContext.java:37: error: PEFNamespaceContext is not abstract and does not override abstract method get

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #897482 [src:brailleutils] brailleutils: FTBFS with Java 10 due to return 
type change of javax.xml.namespace.NamespaceContext.getPrefixes​()
Added tag(s) patch.

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

Bug#909818: firefox: Web Content is eating nearly 100% CPU, several of them

[Florian Apolloner]

Sadly no since I tried half a day... I think in the end removing most packages 
starting with fonts- (just enough to not completely remove the system) helped. 
Also /etc/fonts/conf.d now consists only out of dejavue - maybe you can get to 
that state and it works then (probably also log the removed packages)

On October 12, 2018 12:05:38 PM GMT+02:00, "Pétùr"  wrote:
>On Wed, 10 Oct 2018 12:26:42 +0200 Florian Apolloner
> wrote:
>> I got rid of the problem by removing most of my fonts-* packages,
>> resetting fontconfig to it's default config from dpkg and recreating
>the
>> font-cache. I have no idea which of those did actually fix it; but it
>> might help someone else…
>
>Could you describe exactly what commands did you launch?
>
>I tried to reset fontconfig with `dpkg-reconfigure fontconfig`. No
>improvement.
>
>-- 
>To unsubscribe, send mail to 909818-unsubscr...@bugs.debian.org.

Bug#910854: distro-info: FTBFS: test failure: UnicodeDecodeError

[Ivo De Decker]

package: src:distro-info
version: 0.19
severity: serious
tags: ftbfs

Hi,

The latest version of distro-info in unstable fails on all architectures:

https://buildd.debian.org/status/package.php?p=distro-info

cd python && python3.6 setup.py test
Traceback (most recent call last):
  File "setup.py", line 32, in 
version=get_debian_version(),
  File "setup.py", line 22, in get_debian_version
head = open(changelog).readline()
  File "/usr/lib/python3.6/encodings/ascii.py", line 26, in decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc5 in position 111: 
ordinal not in range(128)
make[1]: *** [Makefile:40: test-python] Error 1
make[1]: Leaving directory '/<>'
dh_auto_test: make -j4 test returned exit code 2
make: *** [debian/rules:6: binary-indep] Error 2
dpkg-buildpackage: error: debian/rules binary-indep subprocess returned exit 
status 2


Cheers,

Ivo

Bug#910852: libqt5webengine5: Akregator crashes very often, WebEngine related

[Martin Steigerwald]

Package: libqt5webengine5
Version: 5.11.1+dfsg-5
Severity: serious
Justification: crashes make Akregator almost unusable

Dear Dmitry,

I found Akregator crashing very often when accessing articles as webpages
which are rendered by Qt WebEngine. These may also be related to KDEPIM
18.08 update. Please reassign if needed.

I downgraded libqt5quick5 to 5.11.1-5 due to the hint in

#910317: libqt5quick5: Sefault in applications using QWebEngineView
https://bugs.debian.org/910500

However this did not help. Thus I installed debug packages to retrieve a
useful backtrace.

Steps to reproduce:
- Start Akregator
- Open articles in a few feeds (I used feeds from pro-linux.de, heise.de/open
  and various Debian related and other feeds, I bet it does not matter all
  that much which ones)
- Click around in those articles, follow links, close QtWebEngine rendered
  articles

Basically I just "use" Akregator as usual and it usually crashes within 5
minutes. I have also seen crashes in KMail after having rendered HTML mail.
I did not yet generate a backtrace from those.

Often I see this "A parser-blocking, cross site" message on console. I do
not know whether this is related. I'd love to use uBlock Origin with my
hardened settings within Qt WebEngine to get rid of that advertising
and tracking crap.

WebEnginePage::javaScriptConsoleMessage lineNumber:  0  message:  "Mixed 
Content: The page at 
'https://www.pro-linux.de/news/1/26392/pydio-cells-12-verzichtet-auf-php.html' 
was loaded over HTTPS, but requested an insecure script 
'http://pagead2.googlesyndication.com/pagead/show_ads.js'. This request has 
been blocked; the content must be served over HTTPS."
WebEnginePage::javaScriptConsoleMessage lineNumber:  16  message:  "A 
parser-blocking, cross site (i.e. different eTLD+1) script, 
https://adserver.idg.de/gptjs/tn/tn_dogpt_sync.js, is invoked via 
document.write. The network request for this script MAY be blocked by the 
browser in this or a future page load due to poor network connectivity. If 
blocked in this page load, it will be confirmed in a subsequent console 
message. See https://www.chromestatus.com/feature/5718547946799104 for more 
details."
WebEnginePage::javaScriptConsoleMessage lineNumber:  16  message:  "A 
parser-blocking, cross site (i.e. different eTLD+1) script, 
https://adserver.idg.de/gptjs/tn/tn_dogpt_sync.js, is invoked via 
document.write. The network request for this script MAY be blocked by the 
browser in this or a future page load due to poor network connectivity. If 
blocked in this page load, it will be confirmed in a subsequent console 
message. See https://www.chromestatus.com/feature/5718547946799104 for more 
details."
WebEnginePage::javaScriptConsoleMessage lineNumber:  620  message:  "Uncaught 
TypeError: googletag.defineSlot is not a function"
WebEnginePage::javaScriptConsoleMessage lineNumber:  2  message:  "Uncaught 
Error: Error: No input element in the page matches .algolia-search"

Thread 21 "Chrome_IOThread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff7700 (LWP 28635)]
0x00750062006d in ?? ()
(gdb) bt full
#0  0x00750062006d in ?? ()
No symbol table info available.
#1  0x7fffed18811f in 
QtWebEngineCore::NetworkDelegateQt::OnBeforeURLRequest(net::URLRequest*, 
base::RepeatingCallback const&, GURL*) () from 
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info available.
#2  0x7fffeec1db86 in 
net::NetworkDelegate::NotifyBeforeURLRequest(net::URLRequest*, 
base::RepeatingCallback const&, GURL*) () from 
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info available.
#3  0x7fffeed6c1ab in net::URLRequest::Start() [clone .part.109] () from 
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info available.
#4  0x7fffeda8b01e in content::ResourceLoader::StartRequestInternal() () 
from /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info available.
#5  0x7fffeda8bcfd in content::ResourceLoader::Resume(bool) () from 
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info available.
#6  0x7fffeda8beea in content::ResourceLoader::StartRequest() () from 
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info available.
#7  0x7fffeda8562e in 
content::ResourceDispatcherHostImpl::BeginRequestInternal(std::unique_ptr >, 
std::unique_ptr >) () from 
/usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5
No symbol table info available.
#8  0x7fffeda86f4f in 
content::ResourceDispatcherHostImpl::BeginNavigationRequest(content::ResourceContext*,
 net::URLRequestContext*, storage::FileSystemContext*, 
content::NavigationRequestInfo const&, 
std::unique_ptr >, 
content::NavigationURLLoaderImplCore*, 
mojo::InterfacePtr, 
mojo::InterfaceRequest, 
content::ServiceWorkerNavigationHandleCore*, 
content::AppCacheNavigationHandleCore*, unsigned int, 
content::GlobalRequestID*) () from 
/usr/lib/x86_64-linux-gnu/libQt5WebEng

Bug#904459: Uploading soon?

[Tollef Fog Heen]

Hi,

any chance you could find time to get this uploaded soon? It'd be great
to have netdata back in testing (and in buster when it gets released).

Cheers,
-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are

Bug#909818: firefox: Web Content is eating nearly 100% CPU, several of them

[Pétùr]

On Wed, 10 Oct 2018 12:26:42 +0200 Florian Apolloner
 wrote:
> I got rid of the problem by removing most of my fonts-* packages,
> resetting fontconfig to it's default config from dpkg and recreating the
> font-cache. I have no idea which of those did actually fix it; but it
> might help someone else…

Could you describe exactly what commands did you launch?

I tried to reset fontconfig with `dpkg-reconfigure fontconfig`. No
improvement.

Bug#909818: firefox: Web Content is eating nearly 100% CPU, several of them

[Pétùr]

On Mon, 01 Oct 2018 14:08:51 +0200 Simon Budig  wrote:

> I can confirm the CPU-eating problem with firefox.
> 
> It might be related to the desktop environment. In my case I use XFCE and
> the CPU eating problem goes away if I kill xfsettingsd.

I can confirm this behavior (killing xfsettingsd fixes the bug).

If I launch again xfsettings with the debug option and use firefox, I
have the following messages related to fontconfig.

$ XFSETTINGSD_DEBUG=1 xfsettingsd --replace --no-daemon
xfce4-settings(fontconfig): monitoring 131 paths
xfce4-settings(workspaces): 4 desktop names set from xfconf
xfce4-settings(fontconfig): timestamp updated (time=1539336916)
xfce4-settings(xsettings): 33 settings changed (serial=1, len=1252)
xfce4-settings(fontconfig): monitoring 131 paths
xfce4-settings(fontconfig): timestamp updated (time=1539336919)
xfce4-settings(xsettings): 33 settings changed (serial=2, len=1252)
xfce4-settings(fontconfig): monitoring 131 paths
Fontconfig warning: Directory/file mtime in the future. New fonts may
not be detected.
xfce4-settings(fontconfig): timestamp updated (time=1539336922)
xfce4-settings(xsettings): 33 settings changed (serial=3, len=1252)
xfce4-settings(fontconfig): monitoring 131 paths
Fontconfig warning: Directory/file mtime in the future. New fonts may
not be detected.
xfce4-settings(fontconfig): timestamp updated (time=1539336925)
xfce4-settings(xsettings): 33 settings changed (serial=4, len=1252)
xfce4-settings(fontconfig): monitoring 131 paths
xfce4-settings(fontconfig): timestamp updated (time=1539336928)
xfce4-settings(xsettings): 33 settings changed (serial=5, len=1252)
xfce4-settings(fontconfig): monitoring 131 paths
xfce4-settings(fontconfig): timestamp updated (time=1539336931)
xfce4-settings(xsettings): 33 settings changed (serial=6, len=1252)
xfce4-settings(fontconfig): monitoring 131 paths
xfce4-settings(fontconfig): timestamp updated (time=1539336934)
xfce4-settings(xsettings): 33 settings changed (serial=7, len=1252)
xfce4-settings(fontconfig): monitoring 131 paths
xfce4-settings(fontconfig): timestamp updated (time=1539336937)
xfce4-settings(xsettings): 33 settings changed (serial=8, len=1252)
xfce4-settings(fontconfig): monitoring 131 paths

Bug#910342: marked as done (playerctl: FTBFS with GLib 2.58.1: redundant use of AC_PATH_PROG)

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 09:49:10 +
with message-id 
and subject line Bug#910342: fixed in playerctl 0.6.1-1.1
has caused the Debian Bug report #910342,
regarding playerctl: FTBFS with GLib 2.58.1: redundant use of AC_PATH_PROG
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.)


-- 
910342: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910342
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: playerctl
Version: 0.6.1-1
Severity: serious
Tags: patch upstream
Justification: fails to build from source
Control: block 909846 by -1

playerctl has this pattern in configure.ac:

AC_PATH_PROG([GDBUS_CODEGEN], [`$PKG_CONFIG --variable=gdbus_codegen 
gio-2.0`])

This doesn't work with recent versions of GLib, in which the pkg-config
call produces an absolute path. AC_PATH_PROG only accepts a basename for
its second argument.

There is some debate over whether the recommended way to check for tools
like these is to search the PATH:

AC_PATH_PROG([GDBUS_CODEGEN], [gdbus-codegen])

or to ask pkg-config:

PKG_CHECK_VAR([GDBUS_CODEGEN], [gio-2.0], [gdbus_codegen])

but combining AC_PATH_PROG with pkg-config certainly doesn't seem to be
what's intended. Either of those macro invocations would allow the location
to be overridden with "./configure GDBUS_CODEGEN=..." if required.

I have confirmed that the attached patch makes playerctl build
successfully in sbuild.

smcv
From: Simon McVittie 
Date: Thu, 4 Oct 2018 21:08:27 +0100
Subject: build: Use PKG_CHECK_VAR to check for gdbus-codegen

Recent versions of GLib define $gdbus_codegen to the absolute path to
gdbus-codegen, but AC_PATH_PROG doesn't work for an absolute path as
its second argument, causing configure to fail.

There's actually no need to use AC_PATH_PROG here, because
we don't need an absolute path to gdbus-codegen: if it's just a
basename that AC_PATH_PROG could find in the PATH, then the Makefile
can also find it in the PATH.

Using PKG_CHECK_VAR (from pkg-config 0.28+) preserves the ability for
a user to specify the path to a gdbus-codegen tool as a configure
argument, defaulting to the value of $gdbus_codegen from gio-2.0.pc.
---
 configure.ac | 6 ++
 1 file changed, 2 insertions(+), 4 deletions(-)

diff --git a/configure.ac b/configure.ac
index 21679fa..9a137c9 100644
--- a/configure.ac
+++ b/configure.ac
@@ -21,10 +21,8 @@ AC_PROG_INSTALL
 PKG_CHECK_MODULES([GOBJECT], [gobject-2.0 >= 2.38])
 PKG_CHECK_MODULES([GIO], [gio-unix-2.0])
 
-AC_PATH_PROG([GDBUS_CODEGEN], [`$PKG_CONFIG --variable=gdbus_codegen gio-2.0`])
-if test -z "$GDBUS_CODEGEN"; then
-AC_MSG_ERROR([*** gdbus-codegen is required to build playerctl])
-fi
+PKG_CHECK_VAR([GDBUS_CODEGEN], [gio-2.0], [gdbus_codegen], [],
+  [AC_MSG_ERROR([*** gdbus-codegen is required to build playerctl])])
 
 # Checks for typedefs, structures, and compiler characteristics
 AC_PROG_CC_STDC
--- End Message ---
--- Begin Message ---
Source: playerctl
Source-Version: 0.6.1-1.1

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

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated playerctl 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, 10 Oct 2018 09:09:00 +0100
Source: playerctl
Binary: playerctl libplayerctl-1.0-0 libplayerctl-dev libplayerctl-doc 
gir1.2-playerctl-1.0
Architecture: source
Version: 0.6.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: Nick Morrott 
Changed-By: Simon McVittie 
Description:
 gir1.2-playerctl-1.0 - utility to control media players via MPRIS (gir 
bindings)
 libplayerctl-1.0-0 - utility to control media players via MPRIS (library)
 libplayerctl-dev - utility to control media players via MPRIS (development 
files)
 libplayerctl-doc - utility to control media players via MPRIS (documentation)
 playerctl  - utility to control media players via MPRIS
Closes: 910342
Changes:
 playerctl (0.6.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * d/p/build-Use-PKG_CHECK_VAR-to-check-for

Bug#910340: marked as done (tpm2-abrmd: FTBFS with GLib 2.58.1: redundant use of AC_PATH_PROG)

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 09:49:27 +
with message-id 
and subject line Bug#910340: fixed in tpm2-abrmd 1.3.1-1.1
has caused the Debian Bug report #910340,
regarding tpm2-abrmd: FTBFS with GLib 2.58.1: redundant use of AC_PATH_PROG
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.)


-- 
910340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tpm2-abrmd
Version: 1.3.1-1
Severity: serious
Tags: patch upstream
Justification: fails to build from source
Control: block 909846 by -1

tmp2-abrmd has this pattern in configure.ac:

AC_PATH_PROG([GDBUS_CODEGEN], [`$PKG_CONFIG --variable=gdbus_codegen 
gio-2.0`])

This doesn't work with recent versions of GLib, in which the pkg-config
call produces an absolute path. AC_PATH_PROG only accepts a basename for
its second argument.

There is some debate over whether the recommended way to check for tools
like these is to search the PATH:

AC_PATH_PROG([GDBUS_CODEGEN], [gdbus-codegen])

or to ask pkg-config:

PKG_CHECK_VAR([GDBUS_CODEGEN], [gio-2.0], [gdbus_codegen])

but combining AC_PATH_PROG with pkg-config certainly doesn't seem to be
what's intended. Either of those macro invocations would allow the location
to be overridden with "./configure GDBUS_CODEGEN=..." if required.

The upstream developer of tpm2-abrmd already applied a
patch to use AC_PATH_PROG([GDBUS_CODEGEN], [gdbus-codegen]):
https://github.com/tpm2-software/tpm2-abrmd/commit/b4036908dd067f8eadc9d53b1a2a39032aed109d
so I would suggest applying that (attached). I can confirm that applying
that patch fixes the build in sbuild.

smcv
From: Jonas Witschel 
Date: Tue, 11 Sep 2018 13:14:36 +0200
Subject: Fix gdbus-codegen lookup for recent versions of GLib

If GLib is built using Meson, the gdbus_codegen variable contains the
whole path to the binary instead of just the binary name. This cannot be
parsed by AC_PATH_PROG and leads to an error in the configure script.
According to https://gitlab.gnome.org/GNOME/glib/issues/1521#note_313402,
the recommended way to solve this is to look up gdbus-codegen directly
without using the pkg-config variable.

Origin: upstream, 2.0.3, commit:b4036908dd067f8eadc9d53b1a2a39032aed109d
---
 configure.ac | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/configure.ac b/configure.ac
index fe278e3..d1ea91b 100644
--- a/configure.ac
+++ b/configure.ac
@@ -32,7 +32,7 @@ PKG_CHECK_MODULES([GLIB], [glib-2.0])
 PKG_CHECK_MODULES([GOBJECT], [gobject-2.0])
 PKG_CHECK_MODULES([SAPI],[sapi < 2.0.0])
 AC_ARG_VAR([GDBUS_CODEGEN],[The gdbus-codegen executable.])
-AC_PATH_PROG([GDBUS_CODEGEN], [`$PKG_CONFIG --variable=gdbus_codegen gio-2.0`])
+AC_PATH_PROG([GDBUS_CODEGEN], [gdbus-codegen])
 if test -z "$GDBUS_CODEGEN"; then
 AC_MSG_ERROR([*** gdbus-codegen is required to build tpm2-abrmd])
 fi
--- End Message ---
--- Begin Message ---
Source: tpm2-abrmd
Source-Version: 1.3.1-1.1

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

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

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

Debian distribution maintenance software
pp.
Simon McVittie  (supplier of updated tpm2-abrmd 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, 10 Oct 2018 08:46:43 +0100
Source: tpm2-abrmd
Binary: libtcti-tabrmd0 libtcti-tabrmd-dev tpm2-abrmd
Architecture: source
Version: 1.3.1-1.1
Distribution: unstable
Urgency: medium
Maintainer: SZ Lin (林上智) 
Changed-By: Simon McVittie 
Description:
 libtcti-tabrmd-dev - TPM2 Access Broker & Resource Management - static 
libraries and h
 libtcti-tabrmd0 - TPM2 Access Broker & Resource Management - shared libraries
 tpm2-abrmd - TPM2 Access Broker & Resource Management Daemon
Closes: 910340 910341
Changes:
 tpm2-abrmd (1.3.1-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * d/p/0002-Fix-gdbus-codegen-lookup-for-recent-versions-of-GLib.patch:
 Apply patch from upstream to make the build system compatible with
 recent GLib versions. In older GLib versions,
 `$PKG_CONFIG --variable=gdbus_codegen gio

Processed: Re: brailleutils: FTBFS: [javac] /<>/src/org/daisy/braille/pef/PEFNamespaceContext.java:37: error: PEFNamespaceContext is not abstract and does not override abstract method get

[Debian Bug Tracking System]

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

> user debian-j...@lists.debian.org
Setting user to debian-j...@lists.debian.org (was ebo...@apache.org).
> usertag 897482 + default-java10
There were no usertags set.
Usertags are now: default-java10.
> retitle 897482 brailleutils: FTBFS with Java 10 due to return type change of 
> javax.xml.namespace.NamespaceContext.getPrefixes​()
Bug #897482 [src:brailleutils] brailleutils: FTBFS: [javac] 
/<>/src/org/daisy/braille/pef/PEFNamespaceContext.java:37: error: 
PEFNamespaceContext is not abstract and does not override abstract method 
getPrefixes(String) in NamespaceContext
Changed Bug title to 'brailleutils: FTBFS with Java 10 due to return type 
change of javax.xml.namespace.NamespaceContext.getPrefixes​()' from 
'brailleutils: FTBFS: [javac] 
/<>/src/org/daisy/braille/pef/PEFNamespaceContext.java:37: error: 
PEFNamespaceContext is not abstract and does not override abstract method 
getPrefixes(String) in NamespaceContext'.
>
End of message, stopping processing here.

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

Bug#897482: brailleutils: FTBFS: [javac] /<>/src/org/daisy/braille/pef/PEFNamespaceContext.java:37: error: PEFNamespaceContext is not abstract and does not override abstract method getPre

[Emmanuel Bourg]

user debian-j...@lists.debian.org
usertag 897482 + default-java10
retitle 897482 brailleutils: FTBFS with Java 10 due to return type change of 
javax.xml.namespace.NamespaceContext.getPrefixes​()

Bug#909551: marked as done (qdirstat: Segfault immediately after choosing scan directory)

[Debian Bug Tracking System]

Your message dated Fri, 12 Oct 2018 09:21:59 +
with message-id 
and subject line Bug#909551: fixed in qdirstat 1.4-3
has caused the Debian Bug report #909551,
regarding qdirstat: Segfault immediately after choosing scan 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.)


-- 
909551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909551
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qdirstat
Version: 1.4-2
Severity: grave
Tags: a11y
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

   I installed qdirstat and launched it. It gave me a GTK(3?) prompt for
   choosing the directory I wish to scan. After choosing the directory
   and clicking "Open", it crashes. The message given when run from the
   terminal is "Segmentation fault". This happens when running
   with/without root privileges. Here is the log:

2018-09-24 22:36:10.956 [5046] Logger.cpp:143 openLogFile():  -- Log 
Start --
2018-09-24 22:36:10.956 [5046] main.cpp:44 logVersion():  
QDirStat-1.4 built with Qt 5.7.1
2018-09-24 22:36:11.070 [5046]DirTreeModel.cpp:549 sort():  Sorting 
by NameCol ascending
2018-09-24 22:36:11.070 [5046]TreemapView.cpp:124 
setSelectionModel():  
2018-09-24 22:36:11.071 [5046] Cleanup.cpp:415 desktopSpecificApps(): 
 Detected desktop "XFCE"
2018-09-24 22:36:11.071 [5046] Cleanup.cpp:468 desktopSpecificApps(): 
 %filemanager => "thunar"
2018-09-24 22:36:11.071 [5046] Cleanup.cpp:468 desktopSpecificApps(): 
 %terminal => "xfce4-terminal &"
2018-09-24 22:36:11.071 [5046]DebugHelpers.cpp:133 
dumpExcludeRules():  
2018-09-24 22:36:11.071 [5046] MainWindow.cpp:818 
toggleVerboseSelection():  Verbose selection is now off. Change this with 
Shift-F7.
2018-09-24 22:36:12.818 [5046] DirTree.cpp:95 startReading(): 
url: "/home/yankee"
2018-09-24 22:36:12.818 [5046] DirTree.cpp:98 startReading():  
device: /dev/sda5
2018-09-24 22:36:12.818 [5046]DirReadJob.cpp:349 stat():  url: 
"/home/yankee"
2018-09-24 22:36:12.818 [5046]MainWindow.cpp:589 
expandTreeToLevel():  Expanding tree to level 1
2018-09-24 22:36:12.835 [5046]DirReadJob.cpp:248 startReading():  
Found cache file .qdirstat.cache.gz
2018-09-24 22:36:12.836 [5046]DirReadJob.cpp:260 startReading():  
Using cache file /home/yankee/.qdirstat.cache.gz for /home/yankee
2018-09-24 22:36:12.836 [5046]DirReadJob.cpp:544 killAll():  NOT 
killing read job 
2018-09-24 22:36:12.836 [5046]DirReadJob.cpp:278 startReading():  
Deleting subtree /home/yankee
2018-09-24 22:36:12.836 [5046]DirTree.cpp:237 deletingChildNotify(): 
 Deleting child /home/yankee
2018-09-24 22:36:12.836 [5046]DirTreeModel.cpp:918 deletingChild():  
Deleting child /home/yankee
2018-09-24 22:36:12.836 [5046]DirTreeModel.cpp:926 deletingChild():  
beginRemoveRows for /home/yankee row 0
2018-09-24 22:36:12.836 [5046]DirTreeModel.cpp:984 
invalidatePersistent():  Invalidating 

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

I attempted to start and use qdirstat, but it crashed when selecting
a directory to scan.

   * What was the outcome of this action?

   It crashed.

   * What outcome did you expect instead?

   It should not crash.

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

Kernel: Linux 4.18.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)
LSM: AppArmor: enabled

Versions of packages qdirstat depends on:
ii  libc62.27-6
ii  libgcc1  1:8.2.0-7
ii  libgl1   1.1.0-1
ii  libgl1-mesa-glx  18.1.7-1
ii  libqt5core5a 5.11.1+dfsg-8
ii  libqt5gui5   5.11.1+dfsg-8
ii  libqt5widgets5   5.11.1+dfsg-8
ii  libstdc++6   8.2.0-7
ii  liburi-perl  1.74-1
ii  perl 5.26.2-7
ii  zlib1g   1:1.2.11.dfsg-1

qdirstat recommends no packages.

qdirstat suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: qdirstat
Source-Version: 1.4-3

We believe that the bug you reported is fixed in the latest version of
qdirstat, 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

Processed: Re: Bug#910217: apparmor: removed shipped file: /var/cache/apparmor/CACHEDIR.TAG

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #910217 [apparmor] apparmor: removed shipped file: 
/var/cache/apparmor/CACHEDIR.TAG
Added tag(s) patch.

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

Bug#910217: apparmor: removed shipped file: /var/cache/apparmor/CACHEDIR.TAG

[Sven Joachim]

Control: tags -1 + patch

On 2018-10-03 17:33 +0200, Andreas Beckmann wrote:

> Package: apparmor
> Version: 2.13-8
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed your package removes files that
> it has shipped.
>
> From the attached log (scroll to the bottom...):
>
> 0m35.9s ERROR: FAIL: debsums reports modifications inside the chroot:
>   debsums: missing file /var/cache/apparmor/CACHEDIR.TAG (from apparmor 
> package)
>
>
> This was observed after a stretch->buster upgrade.

Attached is a patch (untested).

Cheers,
   Sven

>From 6c6d71192d2b1dc0ec47757f8c6acaf0c85a079e Mon Sep 17 00:00:00 2001
From: Sven Joachim 
Date: Fri, 12 Oct 2018 10:54:04 +0200
Subject: [PATCH] Do not remove /var/cache/apparmor/CACHEDIR.TAG on upgrades

Closes: #910217
---
 debian/apparmor.postinst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/apparmor.postinst b/debian/apparmor.postinst
index 7fefe18c..28cb4c78 100644
--- a/debian/apparmor.postinst
+++ b/debian/apparmor.postinst
@@ -32,7 +32,7 @@ case "$1" in
 	# since 2.13-1 apparmor_parser won't create cache files at the root
 	# of the cache-loc, but instead in sub-directories.
 	if dpkg --compare-versions "$2" lt-nl "2.13-7"; then
-		find /var/cache/apparmor -maxdepth 1 -type f -delete
+		find /var/cache/apparmor -maxdepth 1 -type f '!' -name CACHEDIR.TAG -delete
 	fi
 
 	# Try to determine values for apparmor/homedirs if the administrator
-- 
2.19.1

Processed: reopen

[Debian Bug Tracking System]

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

> reopen #909551
Bug #909551 {Done: Patrick Matthäi } [qdirstat] qdirstat: 
Segfault immediately after choosing scan directory
Bug reopened
Ignoring request to alter fixed versions of bug #909551 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#909822: mkchromecast: Should probably depend on pulseaudio-utils

[Andreas Henriksson]

Hi,

Chiming in here because I'd like to just suggest an alternative
that might be more in line with how other packages are layed out
and thus how users might expect things to work.

On Thu, Oct 11, 2018 at 04:24:16PM -0400, Muammar El Khatib wrote:
> On Sat, Sep 29, 2018 at 3:33 AM Ruben Undheim
>  wrote:
[...]
> > I get an error saying 'pactl' cannot be found when
> > starting. Solved it by installing pulseaudio-utils.
> >
> 
> The package suggests mkchromecast-pulseaudio:
[...]

I think I understand how you layed out the package.
You expect the user to pick a particular special version that suits
their needs from mkchromecast-* and install that. Then that pulls in the
common (mkchromecast) package.

If a package has the bulk of the program, but users are not expected to
directly install it but rather have it pulled in via a dependency then
usually the package name gets a -common postfix, ie. in your current
layout you could have named mkchromecast mkchromecast-common instead.

Going back a bit and looking at the bigger picture again I find your
current layout not how packages in debian normally are layed out.
Normally I find that the main package (mkchromecast here) instead has
alternative dependency on the different backends, eg. mkchromecast would:
Depends: mkchromecast-pulseaudio | mkchromecast-alsa | mkchromecast-gstreamer

(Or in which ever order you prefer, listing the recommended and best
supported backend as the first alternative.)

(And to avoid circular dependencies, the mkchromecast-* package would
have to drop or demote the Dependency on mkchromecast to a Recommends.)

This way the users can just pull the package named after the program and
end up having the recommeded backend pulled in for them.

With this package layout you avoid ever having an uninformed user
ending up with installing a package and having it 'not working'.
If they install mkchromecast they get the recommended backend with it.
If they install a particular mkchromecast-* the recommends will pull
in the mkchromecast package. (And if they disable installing recommends
then they are expected to pay attention or they get to keep all their
broken pieces. eg. apt install mkchromecast mkchromecast-gstreamer would
given them the non-default backend without pulling in the
recommended/first alternative dependency.)

While I find your package layout okish (albeit not in line with other
stuff in debian), I think someone could technically still argue that
the 'mkchromecast' binary package is RC-buggy since installing it
in a clean environment leaves it missing needed functionality to
operate. Thus I didn't take the liberty of downgrading the severity
on this bug, but please note that the autoremoval tracker has your
package targeted for removal on Oct 28 so some action on this bug
report before then would be nice.

Hope this helps.

Regards,
Andreas Henriksson