Bug#912030: vim-youcompleteme depends on ycmd (< 0+20161219+git486b809.1) but 0+20180708+git600f54d-1 is to be installed

[Sebastian Ramacher]

Hi Sylvestre

thanks for the much needed ycmd update.

On 2018-10-27 16:02:20, Adrian Bunk wrote:
> Package: vim-youcompleteme
> Version: 0+20161219+git194ff33-1
> Severity: serious
> Tags: buster sid
> 
> The following packages have unmet dependencies:
>  vim-youcompleteme : Depends: ycmd (< 0+20161219+git486b809.1) but 
> 0+20180708+git600f54d-1 is to be installed

Will you also take care of vim-youcompleteme? Both packges are tightly coupled.

Cheers
-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Processed: fixed 909000 in 2:2.0.8-5

[Debian Bug Tracking System]

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

> fixed 909000 2:2.0.8-5
Bug #909000 [enigmail] Enigmail 2.0 needed in Stretch after Thunderbird 60 
upload
Bug #909001 [enigmail] enigmail: Enigmail get uninstalled while upgrading 
thunderbird (60.0-3~deb9u1)
Bug #909081 [enigmail] [enigmail] impossible install enigmail
Bug #909225 [enigmail] enigmail cannot be installed on stretch
Bug #909816 [enigmail] dependency issues - enigmail : Depends: thunderbird (>= 
1:52.0) but it is not going to be installed or
Marked as fixed in versions enigmail/2:2.0.8-5.
Marked as fixed in versions enigmail/2:2.0.8-5.
Marked as fixed in versions enigmail/2:2.0.8-5.
Marked as fixed in versions enigmail/2:2.0.8-5.
Marked as fixed in versions enigmail/2:2.0.8-5.
> thanks
Stopping processing here.

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

Bug#912030: vim-youcompleteme depends on ycmd (< 0+20161219+git486b809.1) but 0+20180708+git600f54d-1 is to be installed

[Sylvestre Ledru]

Le 31/10/2018 à 08:39, Sebastian Ramacher a écrit :
> Hi Sylvestre
>
> thanks for the much needed ycmd update.
>
> On 2018-10-27 16:02:20, Adrian Bunk wrote:
>> Package: vim-youcompleteme
>> Version: 0+20161219+git194ff33-1
>> Severity: serious
>> Tags: buster sid
>>
>> The following packages have unmet dependencies:
>>  vim-youcompleteme : Depends: ycmd (< 0+20161219+git486b809.1) but 
>> 0+20180708+git600f54d-1 is to be installed
> Will you also take care of vim-youcompleteme? Both packges are tightly 
> coupled.

I started working on it https://salsa.debian.org/debian//vim-youcompleteme

but as I don't use vim I am not sure how to test that.

S





signature.asc
Description: OpenPGP digital signature

Bug#909442: outguess: patch for #909442

[Frédéric Bonnard]

Hi Eriberto,

the errors you see in the builds of 2018-10-29 are the same issues : I
initially tried to reproduce the bug but failed, so I asked a give back.
The new errors you see just occurred during that rebuild but are not
different issues.
So the merge request I sent should fix all the errors on amd64 and power
arches.

F.

On Tue, 30 Oct 2018 22:41:11 -0300, Eriberto  wrote:
> Em ter, 30 de out de 2018 às 13:03, Frédéric Bonnard
>  escreveu:
> >
> > Tags: patch pending
> >
> > --
> >
> > Hi,
> >
> > it seems there's a race condition that happens when trying to build
> > libjpeg.a in directory jpeg-6b-steg (seen with make -j8).
> >
> > libjpeg.a: ansi2knr $(LIBOBJECTS)
> > launches both compilation of ansi2knr and $(LIBOBJECTS) but the latter
> > needs ansi2knr before it's compiled. So I make $(LIBOBJECTS) depend on 
> > ansi2knr.
> >
> > Here is a merge request with a patch to fix this.
> > https://salsa.debian.org/pkg-security-team/outguess/merge_requests/2
> >
> > I could reproduce the bug on plummer (ppc64el porterbox) and check the
> > fix.
> >
> > F.
> 
> Hi Frédéric,
> 
> Thanks a lot for your patch. We have new issues over some
> architectures. Please, see here[1].
> 
> [1] https://buildd.debian.org/status/package.php?p=outguess&suite=experimental
> 
> Regards,
> 
> Eriberto
> 


pgpxDFnTvtvJD.pgp
Description: PGP signature

Bug#912397: xserver-xorg-video-amdgpu: Running web browser performance test crashes whole system on AMD RX 460

[Michel Dänzer]

On 2018-10-31 6:32 a.m., Will Brokenbourgh wrote:
> Package: xserver-xorg-video-amdgpu
> Version: 1.2.0-1+b1
> Severity: serious
> 
> Dear Maintainer,
> 
> When a web browser performance test was performed using the latest git 
> version of the surf browser
> it appears the 'xserver-xorg-vide-amdgpu' driver crashes the whole system, 
> [...]

This is more likely an issue in Mesa or the kernel. The Xorg driver
doesn't have any GPU specific code which could cause something like this
anymore.


-- 
Earthling Michel Dänzer   |   http://www.amd.com
Libre software enthusiast | Mesa and X developer

Bug#912147: marked as done (clevis FTBFS: dh_missing: usr/bin/clevis-decrypt-tpm2 exists in debian/tmp but is not installed to anywhere)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 09:07:53 +
with message-id 
and subject line Bug#912147: fixed in clevis 11-1
has caused the Debian Bug report #912147,
regarding clevis FTBFS: dh_missing: usr/bin/clevis-decrypt-tpm2 exists in 
debian/tmp but is not installed to anywhere
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.)


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

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

...
   debian/rules override_dh_missing
make[1]: Entering directory '/build/1st/clevis-10'
dh_missing --fail-missing
dh_missing: usr/bin/clevis-decrypt-tpm2 exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/bin/clevis-encrypt-tpm2 exists in debian/tmp but is not 
installed to anywhere
dh_missing: usr/share/man/man1/clevis-encrypt-tpm2.1 exists in debian/tmp but 
is not installed to anywhere
dh_missing: missing files, aborting
The following debhelper tools have reported what they installed (with 
files per package)
 * dh_install: clevis (8), clevis-dracut (2), clevis-luks (4), 
clevis-systemd (3), clevis-tpm2 (2), clevis-udisks2 (2)
 * dh_installdocs: clevis (0), clevis-dracut (0), clevis-luks (0), 
clevis-systemd (0), clevis-tpm2 (0), clevis-udisks2 (0)
 * dh_installman: clevis (5), clevis-dracut (0), clevis-luks (4), 
clevis-systemd (0), clevis-tpm2 (1), clevis-udisks2 (0)
If the missing files are installed by another tool, please file a bug 
against it.
When filing the report, if the tool is not part of debhelper itself, 
please reference the
"Logging helpers and dh_missing" section from the "PROGRAMMING" guide 
for debhelper (10.6.3+).
  (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz)
Be sure to test with dpkg-buildpackage -A/-B as the results may vary 
when only a subset is built
For a short-term work-around: Add the files to debian/not-installed
make[1]: *** [debian/rules:11: override_dh_missing] Error 255
--- End Message ---
--- Begin Message ---
Source: clevis
Source-Version: 11-1

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

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

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

Debian distribution maintenance software
pp.
Christoph Biedl  (supplier of updated clevis 
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, 30 Oct 2018 22:55:28 +0100
Source: clevis
Binary: clevis clevis-tpm2 clevis-dracut clevis-luks clevis-systemd 
clevis-udisks2
Architecture: source
Version: 11-1
Distribution: unstable
Urgency: medium
Maintainer: Christoph Biedl 
Changed-By: Christoph Biedl 
Description:
 clevis - automated encryption framework
 clevis-dracut - Dracut integration for clevis
 clevis-luks - LUKSv1 integration for clevis
 clevis-systemd - systemd integration for clevis
 clevis-tpm2 - automated encryption framework, TPM2 support
 clevis-udisks2 - UDisks2/Storaged integration for clevis
Closes: 912147
Changes:
 clevis (11-1) unstable; urgency=medium
 .
   * New upstream version. Closes: #912147
Checksums-Sha1:
 409de918debfa61f6ca0bab8f9a02f2d9b777e5a 2321 clevis_11-1.dsc
 086374814a4d71db8625d27a1719e03244a7cff0 37216 clevis_11.orig.tar.xz
 7da1f6f9a5a29e133dc207a5a0caf74c942175be 4128 clevis_11-1.debian.tar.xz
 dc9f5b513587dceb872d3511c581e876a6e4f5df 10341 clevis_11-1_armel.buildinfo
Checksums-Sha256:
 72ab062b14a5a74bf9e1af9f521864c8a47ec1dd952803ce18febceea73323f8 2321 
clevis_11-1.dsc
 26f03c825549830a5840979cf07abaf055be524ac5a2bc5c315ab4786196320a 37216 
clevis_11.orig.tar.xz
 6a9b338f3909eb4d813cc0c9937f61a503021e842faeec6e6ce917ea82586b83 4128 
clevis_11-1.debian.tar.xz
 2c848b6859b6a20cf4e7f06582ad3059eb97cb004f88aea06368fcb39ba74e30 10341 
clevis_11-1_armel.buildinfo
Files:
 6b7e8b0bea2048a81af12fc394232fa1 2321 net optional clevis_11-1.dsc
 d9c2254c7fada860bcfffa49e5632313 37216 net optional clevis_11.orig.tar.xz
 7ec37001f0911dd177b3da049d6258d1 4128

Bug#912410: python-igraph's tests fail with Python 3.7

[Matthias Klose]

Package: src:python-igraph
Version: 0.7.1.post6-5
Severity: serious
Tags: sid buster

python-igraph's tests fail with Python 3.7, RC severity for the upcoming Python
3.7 transition.

testMSTofGRG (igraph.test.homepage.HomepageExampleTests) ... ok

==
ERROR: testFormula (igraph.test.generators.GeneratorTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/generators.py", line 72, in testFormula
g = Graph.Formula(formula)
  File "/<>/igraph/formula.py", line 209, in
construct_graph_from_formula
for start_names, end_names, arrowheads in generate_edges(part):
  File "/<>/igraph/formula.py", line 90, in generate_edges
raise SyntaxError(msg)
SyntaxError: invalid token found in edge specification: A

==
ERROR: testEigenvectorCentrality (igraph.test.structural.CentralityTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/structural.py", line 301, in
testEigenvectorCentrality
cent = g.evcent()
InternalError: Error at arpack.c:944: ARPACK error, Could not build an Arnoldi
factorization

==
ERROR: testCohesiveBlocks2 (igraph.test.decomposition.CohesiveBlocksTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/decomposition.py", line 339, in
testCohesiveBlocks2
g = Graph.Formula("1-2:3:4:5:6, 2-3:4:5:7, 3-4:6:7, 4-5:6:7, "
  File "/<>/igraph/formula.py", line 209, in
construct_graph_from_formula
for start_names, end_names, arrowheads in generate_edges(part):
  File "/<>/igraph/formula.py", line 90, in generate_edges
raise SyntaxError(msg)
SyntaxError: invalid token found in edge specification: 1-2:3:4:5:6

==
ERROR: testAuthorityScore (igraph.test.atlas.GraphAtlasTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/atlas.py", line 83, in testAuthorityScore
sc = g.authority_score()
InternalError: Error at arpack.c:944: ARPACK error, Could not build an Arnoldi
factorization

==
ERROR: testHubScore (igraph.test.atlas.GraphAtlasTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/atlas.py", line 71, in testHubScore
sc = g.hub_score()
InternalError: Error at arpack.c:944: ARPACK error, Could not build an Arnoldi
factorization

==
ERROR: testAuthorityScore (igraph.test.atlas.IsoclassTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/atlas.py", line 83, in testAuthorityScore
sc = g.authority_score()
InternalError: Error at arpack.c:944: ARPACK error, Could not build an Arnoldi
factorization

==
ERROR: testHubScore (igraph.test.atlas.IsoclassTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/atlas.py", line 71, in testHubScore
sc = g.hub_score()
InternalError: Error at arpack.c:944: ARPACK error, Could not build an Arnoldi
factorization

==
FAIL: testEigenvectorCentrality (igraph.test.atlas.GraphAtlasTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/atlas.py", line 35, in
testEigenvectorCentrality
self.assertTrue(False, msg="Eigenvector centrality threw exception for graph
#%d: %s" % (idx, ex))
AssertionError: Eigenvector centrality threw exception for graph #5: Error at
arpack.c:944: ARPACK error, Could not build an Arnoldi factorization

==
FAIL: testEigenvectorCentrality (igraph.test.atlas.IsoclassTests)
--
Traceback (most recent call last):
  File "/<>/igraph/test/atlas.py", line 35, in
testEigenvectorCentrality
self.assertTrue(False, msg="Eigenvector centrality threw exception for graph
#%d: %s" % (idx, ex))
AssertionError: Eigenvector centrality threw exception for graph #3: Error at
arpack.c:1174: ARPACK error, Could not build an Arnoldi factorization

--
Ran 307 tests in 20.550s

FAILED (failures=2, errors=7, skipped=3)
Test failed: 

Processed: your mail

[Debian Bug Tracking System]

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

> found 897405 0.3-7
Bug #897405 {Done: Debian FTP Masters } 
[viewflif] viewflif doesn't work [white rectangle shown]
Marked as found in versions flif/0.3-7 and reopened.
> found 898406 0.3-7
Bug #898406 {Done: Debian FTP Masters } 
[src:flif] flif: CVE-2018-10971
Warning: Unknown package 'src:flif'
Marked as found in versions flif/0.3-7 and reopened.
Warning: Unknown package 'src:flif'
> found 898407 0.3-7
Bug #898407 {Done: Debian FTP Masters } 
[src:flif] flif: CVE-2018-10972
Warning: Unknown package 'src:flif'
Marked as found in versions flif/0.3-7 and reopened.
Warning: Unknown package 'src:flif'
> found 902188 0.3-7
Bug #902188 {Done: Debian FTP Masters } 
[src:flif] CVE-2018-11507
Warning: Unknown package 'src:flif'
Marked as found in versions flif/0.3-7 and reopened.
Warning: Unknown package 'src:flif'
> found 902196 0.3-7
Bug #902196 {Done: Debian FTP Masters } 
[src:flif] flif: CVE-2018-12109
Warning: Unknown package 'src:flif'
Marked as found in versions flif/0.3-7 and reopened.
Warning: Unknown package 'src:flif'
>
End of message, stopping processing here.

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

Bug#912363: marked as done (orthanc-imagej FTBFS with OpenJDK 11)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 09:18:10 +
with message-id 
and subject line Bug#912363: fixed in orthanc-imagej 1.2+dfsg-1
has caused the Debian Bug report #912363,
regarding orthanc-imagej FTBFS with OpenJDK 11
to be marked as done.

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

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


-- 
912363: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912363
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: orthanc-imagej
Version: 1.1+dfsg-3
Severity: serious
Tags: ftbfs

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

...
cd /build/1st/orthanc-imagej-1.1+dfsg && /usr/bin/javac -source 1.6 -target 1.6 
-classpath 
:/usr/share/java/ij.jar:/usr/share/java/json-simple.jar:/build/1st/orthanc-imagej-1.1+dfsg:/build/1st/orthanc-imagej-1.1+dfsg/Build
 -d /build/1st/orthanc-imagej-1.1+dfsg/Build/CMakeFiles/Orthanc_Import.dir 
@/build/1st/orthanc-imagej-1.1+dfsg/Build/CMakeFiles/Orthanc_Import.dir/java_sources
warning: [options] bootstrap class path not set in conjunction with -source 6
warning: [options] source value 6 is obsolete and will be removed in a future 
release
warning: [options] target value 1.6 is obsolete and will be removed in a future 
release
warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
/build/1st/orthanc-imagej-1.1+dfsg/com/orthancserver/OrthancConnection.java:32: 
error: package javax.xml.bind does not exist
import javax.xml.bind.DatatypeConverter;
 ^
/build/1st/orthanc-imagej-1.1+dfsg/com/orthancserver/SelectImageDialog.java:52: 
error: package javax.xml.bind does not exist
import javax.xml.bind.DatatypeConverter;
 ^
/build/1st/orthanc-imagej-1.1+dfsg/com/orthancserver/OrthancConnection.java:100:
 error: cannot find symbol
return DatatypeConverter.printBase64Binary(auth.getBytes());
   ^
  symbol:   variable DatatypeConverter
  location: class OrthancConnection
/build/1st/orthanc-imagej-1.1+dfsg/com/orthancserver/SelectImageDialog.java:555:
 error: cannot find symbol
  String decoded = new String(DatatypeConverter.parseBase64Binary(s));
  ^
  symbol:   variable DatatypeConverter
  location: class SelectImageDialog
/build/1st/orthanc-imagej-1.1+dfsg/com/orthancserver/SelectImageDialog.java:578:
 error: cannot find symbol
return DatatypeConverter.printBase64Binary(config.getBytes());
   ^
  symbol:   variable DatatypeConverter
  location: class SelectImageDialog
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
5 errors
4 warnings
make[3]: *** [CMakeFiles/Orthanc_Import.dir/build.make:79: 
CMakeFiles/Orthanc_Import.dir/java_compiled_Orthanc_Import] Error 1
--- End Message ---
--- Begin Message ---
Source: orthanc-imagej
Source-Version: 1.2+dfsg-1

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 31 Oct 2018 08:28:01 +0100
Source: orthanc-imagej
Binary: orthanc-imagej
Architecture: source all
Version: 1.2+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Sebastien Jodogne 
Description:
 orthanc-imagej - ImageJ plugin to import images from Orthanc
Closes: 912363
Changes:
 orthanc-imagej (1.2+dfsg-1) unstable; urgency=medium
 .
   * New upstream version. (Closes: #912363)
Checksums-Sha1:
 8f931d4718d0edadc7a85ae579512ab850d5cc6a 2129 orthanc-imagej_1.2+dfsg-1.dsc
 22ea39fabfc3db027d85ef70a1b636d12c0585b4 22468 
orthanc-imagej_1.2+dfsg.orig.tar.xz
 329c783a10d8763296654c38e23c332c42e8bd69 3324 
orthanc-imagej_1.2+dfsg-1.debian.tar.xz
 1096887d212613a6d067b27278ecde23d54344ba 35108 
orthanc-imagej_1.2+dfsg-1_all.deb
 d2af78b945c987d8dd07bdcd8fbd3048

Bug#887712: fixed in ftgl 2.3.0-1

[IOhannes m zmölnig]

On Sat, 20 Oct 2018 14:49:43 + m...@debian.org (Manuel A. Fernandez
Montecelo) wrote:
> Source: ftgl
> Source-Version: 2.3.0-1

thanks for doing an upload of ftgl-2.3 to "experimental".
do you have any plans, to also upload to "unstable" (so all those
reverse-dependencies that are marked AUTORM won't get kicked out of
Debian)? is a transition required?

(btw, where is ftgl-2.3.0 upstream? is it the
https://github.com/ulrichard/ftgl fork?)

fgamsdr
IOhannes



signature.asc
Description: OpenPGP digital signature

Processed: Forward

[Debian Bug Tracking System]

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

> forwarded 911697 https://github.com/mesonbuild/meson/issues/4452
Bug #911697 [meson] meson: varying levels of quote interpretation make it 
impossible to define G_LOG_DOMAIN
Set Bug forwarded-to-address to 
'https://github.com/mesonbuild/meson/issues/4452'.
>
End of message, stopping processing here.

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

Processed: downgrade severity of gtksourceview2 bugs instead of using ignore tag

[Debian Bug Tracking System]

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

> severity 911167 important
Bug #911167 [src:gwyddion] gwyddion: Depend on gtksourceview2
Severity set to 'important' from 'serious'
> severity 911164 important
Bug #911164 [gnome-genius] gnome-genius: Depends on unmaintained gtksourceview2
Severity set to 'important' from 'serious'
> severity 885681 important
Bug #885681 [src:gummi] gummi: Depends on unmaintained gtksourceview2
Severity set to 'important' from 'serious'
> severity 911166 important
Bug #911166 [src:gtksourceview2] gtksourceview2: Do not release with Buster
Severity set to 'important' from 'serious'
> tags 911167 -buster-ignore
Bug #911167 [src:gwyddion] gwyddion: Depend on gtksourceview2
Removed tag(s) buster-ignore.
> tags 911164 -buster-ignore
Bug #911164 [gnome-genius] gnome-genius: Depends on unmaintained gtksourceview2
Removed tag(s) buster-ignore.
> tags 885681 -buster-ignore
Bug #885681 [src:gummi] gummi: Depends on unmaintained gtksourceview2
Removed tag(s) buster-ignore.
> tags 911166 -buster-ignore
Bug #911166 [src:gtksourceview2] gtksourceview2: Do not release with Buster
Removed tag(s) buster-ignore.
>
End of message, stopping processing here.

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

Bug#911713: marked as done (sdcc FTBFS: tex failure during documentation build)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 10:58:36 +
with message-id 
and subject line Bug#911713: fixed in sdcc 3.8.0+dfsg-1
has caused the Debian Bug report #911713,
regarding sdcc FTBFS: tex failure during documentation build
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.)


-- 
911713: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911713
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sdcc
Version: 3.7.0+dfsg2-0.1
Severity: serious
Tags: ftbfs

sdcc fails to build from source in unstable.

| LaTeX Warning: Reference `subsec:Search-Paths' on page 32 undefined on input 
li
| ne 2261.
| 
| [32]
| 
| ! LaTeX Error: File `MCS51_named' not found.
| 
| See the LaTeX manual or LaTeX Companion for explanation.
| Type  H   for immediate help.
|  ...  
|   
| l.2283 \includegraphics{MCS51_named}
| 
| ? 
| ! Emergency stop.
|  ...  
|   
| l.2283 \includegraphics{MCS51_named}
| 
| Output written on sdccman.dvi (33 pages, 170988 bytes).
| Transcript written on sdccman.log.
| make[1]: *** [Makefile:67: sdccman.dvi] Error 1
| make[1]: Leaving directory '/<>/doc'
| make: *** [debian/rules:71: build-indep-stamp] Error 2
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Supposedly, this was fixed in #909995, but the issue persists.

This time around the traceback looks a little different:

| +Read the file doc/LaTeXConfig.lyx for more information.
| LyX: Done!
| Traceback (most recent call last):
|   File "/usr/share/lyx/scripts/convertDefault.py", line 38, in 
| output = output.decode()
| AttributeError: 'str' object has no attribute 'decode'
| support/Systemcall.cpp (294): Systemcall: 'python3 -tt 
"/usr/share/lyx/scripts/convertDefault.py" svg 
"/tmp/lyx_tmpdir.hxwECXKtFDVu/lyx_tmpbuf0/1_build_sdcc-KkmAiE_sdcc-3_7_0+dfsg2_doc_MCS51_named.svg"
 eps 
"/tmp/lyx_tmpdir.hxwECXKtFDVu/lyx_tmpbuf0/1_build_sdcc-KkmAiE_sdcc-3_7_0+dfsg2_doc_MCS51_named.eps"'
 finished with exit code 1
| Error: Cannot convert file
| 
| No information for converting svg format files to eps.
| Define a converter in the preferences.
| latex sdccman.tex

Helmut
--- End Message ---
--- Begin Message ---
Source: sdcc
Source-Version: 3.8.0+dfsg-1

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

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

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

Debian distribution maintenance software
pp.
Gudjon I. Gudjonsson  (supplier of updated sdcc 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, 30 Oct 2018 09:51:18 +0100
Source: sdcc
Binary: sdcc sdcc-libraries sdcc-ucsim sdcc-doc
Architecture: source amd64 all
Version: 3.8.0+dfsg-1
Distribution: sid
Urgency: medium
Maintainer: Debian Electronics Packaging Team 

Changed-By: Gudjon I. Gudjonsson 
Description:
 sdcc   - Small Device C Compiler
 sdcc-doc   - Small Device C Compiler (documentation)
 sdcc-libraries - Small Device C Compiler (libraries)
 sdcc-ucsim - Micro-controller simulator for SDCC
Closes: 911713
Changes:
 sdcc (3.8.0+dfsg-1) unstable; urgency=medium
 .
   [ Jonathan McDowell ]
   * Add myself to Uploaders and move under the Electronics Packaging Team.
   * Move to debhelper compat level 10.
   * Rename git-buildpackage section header to just buildpackage.
 .
   [ Gudjon I. Gudjonsson ]
   * New upstream release
   * Remove a few autogenerated files from git and add to debian/rules
 clean target.
   * Don't install device/examples, removed from upstream
   * Bump standards to 4.2.1
   * Change watch from http to https
   * Add patch to fix spelling 01_fix_spelling.patch
   * Fix spelling error in ucsim and sdcc manpages
   * Change version check to DEB_VERSION_UPSTREAM in rules file
   * Add override file to remove false lintian gfdl positives
   * Add dependency on zlib1g-dev
   * Add dependency on inkscap

Bug#912386: [Debian-med-packaging] Bug#912386: rdp-readseq FTBFS with OpenJDK 11

[Olivier Sallou]

- Mail original -
> De: "andreas" 
> À: 912...@bugs.debian.org
> Envoyé: Mercredi 31 Octobre 2018 07:10:01
> Objet: [Debian-med-packaging] Bug#912386: rdp-readseq FTBFS with OpenJDK 11

> Control: tags -1 help
> 
> Hi,
>   
> I'm afraid I need help for this bug from the Debian Java team.
> 
> Kind regards
>   
>   Andreas.
> 
> On Wed, Oct 31, 2018 at 04:58:09AM +0200, Adrian Bunk wrote:
>> Source: rdp-readseq
>> Version: 2.0.2-4
>> Severity: serious
>> Tags: ftbfs
>> 
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rdp-readseq.html
>> 
>> ...
>>debian/rules override_dh_auto_build
>> make[1]: Entering directory '/build/1st/rdp-readseq-2.0.2'
>> jh_build --javacopts="-encoding UTF8" rdp-readseq.jar src
>> find src -name *.java -and -type f -print0 | xargs -s 512000 -0
>> /usr/lib/jvm/default-java/bin/javac -g -cp
>> /usr/share/java/commons-cli.jar:/usr/share/java/commons-lang.jar:/usr/share/java/commons-io.jar:debian/_jh_build.rdp-readseq
>> -d debian/_jh_build.rdp-readseq -source 1.7 -target 1.7 -encoding UTF8
>> warning: [options] bootstrap class path not set in conjunction with -source 7
>> src/edu/msu/cme/rdp/readseq/readers/Sequence.java:11: error: package
>> javax.xml.bind.annotation does not exist
>> import javax.xml.bind.annotation.XmlAttribute;


java xml has been removed from "core" jdk with Java 9 ou 10.

Commands (javac, java , ...) needs to add javax.xml module with --add-module 
option (not sure of syntax). We have other packages where we added such option 
with java upgrades.



I am on travel, cannot fix this now but I can have a look later on. But adding 
option should do the job (if there is a shell that calls java cmd line, it 
should also be added)

Olivier


>> ^
>> src/edu/msu/cme/rdp/readseq/readers/Sequence.java:12: error: package
>> javax.xml.bind.annotation does not exist
>> import javax.xml.bind.annotation.XmlElement;
>> ^
>> src/edu/msu/cme/rdp/readseq/readers/Sequence.java:19: error: cannot find 
>> symbol
>> @XmlAttribute
>>  ^
>>   symbol:   class XmlAttribute
>>   location: class Sequence
>> src/edu/msu/cme/rdp/readseq/readers/Sequence.java:21: error: cannot find 
>> symbol
>> @XmlAttribute
>>  ^
>>   symbol:   class XmlAttribute
>>   location: class Sequence
>> src/edu/msu/cme/rdp/readseq/readers/Sequence.java:23: error: cannot find 
>> symbol
>> @XmlElement
>>  ^
>>   symbol:   class XmlElement
>>   location: class Sequence
>> Note: Some input files use or override a deprecated API.
>> Note: Recompile with -Xlint:deprecation for details.
>> Note: Some input files use unchecked or unsafe operations.
>> Note: Recompile with -Xlint:unchecked for details.
>> 5 errors
>> 1 warning
>> make[1]: *** [debian/rules:27: override_dh_auto_build] Error 123
>> 
>> ___
>> Debian-med-packaging mailing list
>> debian-med-packag...@alioth-lists.debian.net
>> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging
> 
> --
> http://fam-tille.de
> 
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging

Bug#912385: rdp-classifier FTBFS with OpenJDK 11

[Olivier Sallou]

- Mail original -
> De: "andreas" 
> À: 912...@bugs.debian.org, "Debian Java List" 
> Envoyé: Mercredi 31 Octobre 2018 07:07:36
> Objet: Re: Bug#912385: rdp-classifier FTBFS with OpenJDK 11

> Control: tags -1 help
> 
> Hi,
> 
> I'm afraid I need help for this bug from the Debian Java team.
> 
> Kind regards
> 
>   Andreas.
> 
> On Wed, Oct 31, 2018 at 04:56:52AM +0200, Adrian Bunk wrote:
>> Source: rdp-classifier
>> Version: 2.10.2-3
>> Severity: serious
>> Tags: ftbfs
>> 
>> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/rdp-classifier.html
>> 
>> ...
>> junit:
>> [javac] /build/1st/rdp-classifier-2.10.2/tmp-junit.xml:13: warning:
>> 'includeantruntime' was not set, defaulting to build.sysclasspath=last; 
>> set to
>> false for repeatable builds
>> [javac] Compiling 18 source files
>> [javac] warning: [options] bootstrap class path not set in conjunction 
>> with
>> -source 8
>> [javac] Note: Some input files use unchecked or unsafe operations.
>> [javac] Note: Recompile with -Xlint:unchecked for details.
>> [javac] 1 warning
>>  [echo] Using java version 11.0.1
>> [junit] Error occurred during initialization of boot layer
>> [junit] java.lang.module.FindException: Module java.se.ee not found


think this needs to be forwarded to upstream (if any...)

According to javadoc [0]

@Deprecated(since="9", forRemoval=true)

Module java.se.ee
Deprecated, for removal: This API element is subject to removal in a future 
version.



In the meanwhile, adding --add-module java.se.ee should do the job

Some module that were removed from jdk and need the --add-module option:

java.xml.ws (JAX-WS, plus the related technologies SAAJ and Web Services 
Metadata)
java.xml.bind (JAXB)
java.activation (JAF)
java.xml.ws.annotation (Common Annotations)
java.corba (CORBA)
java.transaction (JTA)

Related modules in Java SE 9 are also deprecated for removal:

java.se.ee (Aggregator module for the six modules above)
jdk.xml.ws (Tools for JAX-WS)
jdk.xml.bind (Tools for JAXB)



[0] https://docs.oracle.com/javase/9/docs/api/java.se.ee-summary.html



>> [junit] Running edu.msu.cme.rdp.classifier.rrnaclassifier.ClassifierTest
>> [junit] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 
>> 0 sec
>> 
>> BUILD FAILED
>> /build/1st/rdp-classifier-2.10.2/tmp-junit.xml:31: Test
>> edu.msu.cme.rdp.classifier.rrnaclassifier.ClassifierTest failed (crashed)
>> 
>> Total time: 3 seconds
>> make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1
>> 
>> ___
>> Debian-med-packaging mailing list
>> debian-med-packag...@alioth-lists.debian.net
>> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging
> 
> --
> http://fam-tille.de

Bug#912380: endless looping, breaks dpkg

[Colin Watson]

On Tue, Oct 30, 2018 at 10:27:22PM +0100, Eduard Bloch wrote:
> I am no longer able to install many packages. The man-db hook keeps
> running and running for ages.
> 
> I have monitored it with strace and it seems to run over the same files
> in man1 folder all over again, never ending. See the logs (also
> filtered for open* syscalls):
> 
> https://www.unix-ag.uni-kl.de/~bloch/misc/wtf_mandb_dead_loop.txt.gz
> https://www.unix-ag.uni-kl.de/~bloch/misc/wtf_mandb_dead_loop.strace.log

Are you sure it's looping endlessly?  Your logs don't support that
theory.  Some file names are repeated, but that's because they're the
basenames of manual pages that exist in a number of different languages.
I haven't so far seen any page being processed more than once in your
log.  (Note that each file is opened twice in relatively quick
succession for different phases of processing, which is a little bit
suboptimal but not evidence of an endless loop.)

I think what's happening is simply that man-db was rebuilt against a new
version of gdbm and therefore has to rebuild its database from scratch,
and that this is unfortunately rather slow.  I'd need more evidence to
determine that there's an endless-loop-type bug here.

-- 
Colin Watson   [cjwat...@debian.org]

Bug#910764: Forward 910764 OpenJFX 11 segmentation fault

[Markus Koschany]

Control: severity -1 important

On Tue, 30 Oct 2018 14:39:11 +0100 Markus Koschany  wrote:
> Control: forwarded -1 
> https://bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8213149
> thanks
> 
> Look like upstream can't reproduce this issue with their custom JDK image.
> 

Ok, apparently this bug is a duplicate of

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

See also https://github.com/javafxports/openjdk-jfx/issues/175

Although not ideal we can work around it by passing -Djdk.gtk.version=2
to all JavaFX applications at the moment. Thus I'm lowering the severity
to important.

Markus



signature.asc
Description: OpenPGP digital signature

Processed: Re: Forward 910764 OpenJFX 11 segmentation fault

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #910764 [openjfx] openjfx: segmentation fault in GtkNativeMainLoopThread
Severity set to 'important' from 'serious'

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

Bug#905215: marked as done (CVE-2018-2941)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 12:59:40 +0100
with message-id <83f08898-2e0d-dc48-96b0-ce652e2cf...@debian.org>
and subject line Re: CVE-2018-2941
has caused the Debian Bug report #905215,
regarding CVE-2018-2941
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.)


-- 
905215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=905215
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjfx
Severity: grave
Tags: security

http://www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html
fixed CVE-2018-2941 in JavaFX, which should affect our openjfx package.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Version: 11+26-1

As previously stated I believe this issue was fixed in OpenJFX 11.
However there is no way to prove it because Oracle didn't release any
publicly available information about the details. I am going to close
this bug report now but feel free to reopen it, if you can share more
information about CVE-2018-2941.

Markus



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#912167: marked as done (dpuser FTBFS on arm64: Segmentation fault)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 12:04:07 +
with message-id 
and subject line Bug#912167: fixed in giza 1.0.0-2
has caused the Debian Bug report #912167,
regarding dpuser FTBFS on arm64: Segmentation fault
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.)


-- 
912167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dpuser
Version: 3.3+p1+dfsg-2
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/arm64/dpuser.html

...
Executing selfmade procedure # 6
>>> "addquad" exists already as stored function!
>>> "factorial" exists already as stored function!
>>> "cropdata" exists already as stored function!
***
CONGRATULATIONS: All tests were successful!
***
DPUSER> fgrep -q CONGRATULATIONS test.log
make[1]: Leaving directory '/build/1st/dpuser-3.3+p1+dfsg'
 fakeroot debian/rules binary
dh  binary
   dh_testroot
   dh_prep
   dh_install
   debian/rules override_dh_installdocs
make[1]: Entering directory '/build/1st/dpuser-3.3+p1+dfsg'
cd dpuser/doc && echo @makehelp.dpuser | ../../dpuser/dpuser
     _   _   _   
|  _ \|  _ \| | | / ___|| |  _ \ 
| | | | |_) | | | \___ \|  _| | |_) |
| |_| |  __/| |_| |___) | |___|  _ < 
|/|_|\___/|/|_|_| \_\ - The Next Generation 3.3
Rev. 
Written since 1999 by Thomas Ott
Inspired by the original MPE dp_user speckle data reduction software
 
For basic information, type "help" at the DPUSER> prompt.
Online documentation available at: http://www.mpe.mpg.de/~ott/dpuser
230 functions registered.
99 procedures registered.
126 pgplot procedures registered.
DPUSER> @makehelp.dpuser
Segmentation fault
make[1]: *** [debian/rules:20: override_dh_installdocs] Error 139
--- End Message ---
--- Begin Message ---
Source: giza
Source-Version: 1.0.0-2

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

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

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated giza package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 31 Oct 2018 12:31:58 +0100
Source: giza
Binary: giza-dev libgiza0 libpgplot0 libcpgplot0
Architecture: source
Version: 1.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Description:
 giza-dev   - Lightweight scientific plotting library (development files)
 libcpgplot0 - CPGPLOT replacement shared lib based on giza
 libgiza0   - Lightweight scientific plotting library (shared library)
 libpgplot0 - PGPLOT replacement shared lib based on giza
Closes: 912167
Changes:
 giza (1.0.0-2) unstable; urgency=medium
 .
   * Fix off-by-one declaration bug in giza_scanner.l (Closes: #912167)
Checksums-Sha1:
 4c575eb433a3dd6319595ad6d3a5a0992731d296 2084 giza_1.0.0-2.dsc
 b11f28880ba1f2602b36ce15e3cf35635f9fed6d 4040 giza_1.0.0-2.debian.tar.xz
Checksums-Sha256:
 e894525979eea7eed37521f7c04cab7e521c313e9dbf590abaddd4cff90775f2 2084 
giza_1.0.0-2.dsc
 5034a8f82fd9f8df0a47f8d3c6e2b9d6650555ae561906f804ced681fd7a53ce 4040 
giza_1.0.0-2.debian.tar.xz
Files:
 b138e0d579d9fed7cc3cf10e6625222e 2084 science optional giza_1.0.0-2.dsc
 8f9c87668e0c30045300aef388f46928 4040 science optional 
giza_1.0.0-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEuvxshffLFD/utvsVcRWv0HcQ3PcFAlvZk18ACgkQcRWv0HcQ
3PeD0A/+L6crasJjfeuLl/3ooy/m5mvFE3NGLuu3yoJgbkA2eQQ/p1XmBRWzwaeQ
l2Q9iHwediG0od73Ve7w4aVpLzUmMAJhs0NFWWjvwqD/gAOw1xHOUW/tfigMu3Rz
y2KKNrmCPQdXtq70oy06TNPUe/Gq5hBiXeDbX0BXDjq+eWiNkH05qD3+Xx43vjuH
fMvg7X32iKVvP70olUaKulKKiS+rhDl+bIKREDVA/+n65l+5s13dphPLZie3ezb3
A9SWQzt/G9LX6cLAwavPcikO5A9l/jv2B3x1iKSK0MwNotzm4UIOdqic/ymrUkh4
6zQ7cY9QGyf75YR+J50WuGEz+DVNRbBLnEcfj9hy3m8p9ahFMib7CRUrQVUfG6oI
v5sXOUtv/ifgbsWnxjoYjBnjOusB8R3uVxiz9XuPTzxaCqbsgtOUDSEepKXeVyiQ
Vt8Mp5CcCzlDVOSPPQ9rQoQjOFDN1AyQW9dl24rihJ+T30RuI0eVvAi3n2TBqFXO
xZqhEwDS25ezxyxfBcEx+Bwa31JSy0FcQ/gclDnY6iY7kLRvdUrmjid9i01ZlXaE
SujlYDciQBKUc+XYVUZd34aDakhO0xzvl

Bug#912380: endless looping, breaks dpkg

[Eduard Bloch]

Hallo,
* Colin Watson [Wed, Oct 31 2018, 11:38:31AM]:
> On Tue, Oct 30, 2018 at 10:27:22PM +0100, Eduard Bloch wrote:
> > I am no longer able to install many packages. The man-db hook keeps
> > running and running for ages.
> > 
> > I have monitored it with strace and it seems to run over the same files
> > in man1 folder all over again, never ending. See the logs (also
> > filtered for open* syscalls):
> > 
> > https://www.unix-ag.uni-kl.de/~bloch/misc/wtf_mandb_dead_loop.txt.gz
> > https://www.unix-ag.uni-kl.de/~bloch/misc/wtf_mandb_dead_loop.strace.log
> 
> Are you sure it's looping endlessly?  Your logs don't support that
> theory.  Some file names are repeated, but that's because they're the
> basenames of manual pages that exist in a number of different languages.
> I haven't so far seen any page being processed more than once in your
> log.  (Note that each file is opened twice in relatively quick
> succession for different phases of processing, which is a little bit
> suboptimal but not evidence of an endless loop.)
> 
> I think what's happening is simply that man-db was rebuilt against a new
> version of gdbm and therefore has to rebuild its database from scratch,
> and that this is unfortunately rather slow.  I'd need more evidence to
> determine that there's an endless-loop-type bug here.

No, not sure. But it was running for minutes and didn't seem to finish.
The system was not under load, FS is running on SSD, plenty of RAM
available too.

Today, after reboot, it works again like nothing happened. So, assuming
you are right, it looks like a sudden performance degradation but
without any obvious reason and not reproducible anymore.

Maybe I should have waited a few minutes more. So I guess we should
close the BR then?

Best regards,
Eduard.

Bug#912047: marked as done (nullmailer: FTBFS: Test failure)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 12:51:02 +
with message-id 
and subject line Bug#912047: fixed in nullmailer 1:2.1-8
has caused the Debian Bug report #912047,
regarding nullmailer: FTBFS: Test failure
to be marked as done.

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

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


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

>From my pbuilder build log:

...
Making check in test
make[2]: Entering directory '/build/nullmailer-2.1/test'
./address-test
42 tests run, 0 failed.
./argparse-test
14 tests run, 0 failed.
sh ./clitest.sh
All tests passed.
./runtests `find /build/nullmailer-2.1/test/tests -type f -not -name '.*'`
Running test /build/nullmailer-2.1/test/tests/inject/from_...
Checking that inject ignores a leading "From " line
Checking that inject ignores a leading ">From " line
Done.
Running test /build/nullmailer-2.1/test/tests/inject/recips...
Checking that inject uses command line with -a.
Checking that inject ignores header lines with -a.
Checking that inject uses command line with -b.
Checking that inject uses header lines with -b.
Checking that inject ignores command line with -h.
Checking that inject uses header lines with -h.
Checking that inject uses command line with -e and no header.
Checking that inject uses command line with -e and header.
Checking that inject uses header with -e and no command line.
Checking that inject ignores header with -e and command line.
Checking that inject uses command line with no header by default.
Checking that inject uses command line with header by default.
Checking that inject uses header with no command line by default.
Checking that inject ignores header with command line by default.
Done.
Running test /build/nullmailer-2.1/test/tests/inject/from...
Checking that inject inserts a from line.
Checking that inject preserves an existing from line.
Checking that inject does not add more from lines.
Checking that inject will strip from lines.
Checking that inject obeys me
Checking that inject obeys config/defaulthost
Checking that inject obeys config/defaultdomain
Checking that inject ignores config/defaultdomain for localhost
Checking that inject obeys HOSTNAME.
Checking that inject obeys MAILHOST.
Checking that inject obeys NULLMAILER_HOST.
Checking that inject uses getpwnam
Checking that inject obeys LOGNAME.
Checking that inject obeys USER.
Checking that inject obeys MAILUSER.
Checking that inject obeys NULLMAILER_USER.
Checking that inject uses a blank name.
Checking that inject obeys NAME.
Checking that inject obeys MAILNAME.
Checking that inject obeys NULLMAILER_NAME.
Checking that inject will use address-comment form.
Done.
Running test /build/nullmailer-2.1/test/tests/inject/return-path...
Checking that inject does not inserts a return-path.
Checking that inject strips return-paths.
Done.
Running test /build/nullmailer-2.1/test/tests/inject/message-id...
Checking that inject inserts a message-id.
Checking that inject preserves an existing message-id.
Checking that inject does not add more message-ids.
Checking that inject will ignore an existing message-id.
Checking that inject obeys me
Checking that inject obeys config/idhost
Done.
Running test /build/nullmailer-2.1/test/tests/inject/date...
Checking that inject inserts a date line.
Checking that inject preserves an existing date line.
Checking that inject does not add more date lines.
Done.
Running test /build/nullmailer-2.1/test/tests/inject/sender...
Checking that inject obeys me
Checking that inject obeys config/defaulthost
Checking that inject obeys config/defaultdomain
Checking that inject ignores config/defaultdomain for localhost
Checking that inject obeys HOSTNAME.
Checking that inject canonicalizes HOSTNAME.
Checking that inject obeys MAILHOST.
Checking that inject canonicalizes MAILHOST.
Checking that inject obeys NULLMAILER_HOST.
Checking that inject canonicalizes NULLMAILER_HOST.
Checking that inject uses getpwnam
Checking that inject obeys LOGNAME.
Checking that inject obeys USER.
Checking that inject obeys MAILUSER.
Checking that inject obeys NULLMAILER_USER.
Checking that inject ignores Errors-To:
Checking that inject ignores From:
Checking that inject ignores Reply-To:
Checking that inject ignores Resent-From:
Checking that inject ignores Resent-Reply-To:
Checking that inject ignores Resent-Sender:
Checking that inject ignores Return-Receipt-To:
Checking that inject ignores Sender:
Checking that inject uses Return-Path:
Checking that inject ignores Return-

Bug#909442: Bug #909442 in outguess marked as pending

[Joao Eriberto Mota Filho]

Control: tag -1 pending

Hello,

Bug #909442 in outguess 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/pkg-security-team/outguess/commit/e04f85db0042edd2285210fda63e11166576cfae


Merge branch 'fix-909442' into 'debian/master'

Fix parallel builds (Closes: #909442)

See merge request pkg-security-team/outguess!2


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/909442

Processed: Bug #909442 in outguess marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #909442 [outguess] outguess: FTBFS in some architectures
Added tag(s) pending.

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

Processed: Bug #909442 in outguess marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #909442 [outguess] outguess: FTBFS in some architectures
Ignoring request to alter tags of bug #909442 to the same tags previously set

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

Bug#909442: Bug #909442 in outguess marked as pending

[Joao Eriberto Mota Filho]

Control: tag -1 pending

Hello,

Bug #909442 in outguess 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/pkg-security-team/outguess/commit/6967302ec0993c8b8df37d6a5a317e8f6b74cb23


Fix parallel builds (Closes: #909442)

On build machines with many cpus, race conditions can happen in
jpeg-6b-steg directory where :
libjpeg.a: ansi2knr $(LIBOBJECTS)
launches both compilation of ansi2knr and $(LIBOBJECTS) but the latter
needs ansi2knr.
So make $(LIBOBJECTS) depend on ansi2knr.



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/909442

Processed: Bug#912423: codelite: fails to start: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #912423 [codelite] Gtk-Error: GTK+ 2.x symbols detected. Using GTK+ 2.x and 
GTK+ 3 in the same process is not supported
Severity set to 'grave' from 'important'
> tags -1 confirmed
Bug #912423 [codelite] Gtk-Error: GTK+ 2.x symbols detected. Using GTK+ 2.x and 
GTK+ 3 in the same process is not supported
Added tag(s) confirmed.
> retitle -1 codelite: fails to start: GTK+ 2.x symbols detected. Using GTK+ 
> 2.x and GTK+ 3 in the same process is not supported
Bug #912423 [codelite] Gtk-Error: GTK+ 2.x symbols detected. Using GTK+ 2.x and 
GTK+ 3 in the same process is not supported
Changed Bug title to 'codelite: fails to start: GTK+ 2.x symbols detected. 
Using GTK+ 2.x and GTK+ 3 in the same process is not supported' from 
'Gtk-Error: GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same 
process is not supported'.

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

Bug#908112: possible fix

[Mauro Gaioni]

See #895599
Apply fix in 
https://github.com/ganeti/ganeti/commit/5f90a0f64bf5fee7fe353a95d02c79736a5943c5

For me works.
Regards, Mauro

Bug#908112: possible fix

[Apollon Oikonomopoulos]

Control: tags -1 pending

Hi,

On 14:48 Wed 31 Oct , Mauro Gaioni wrote:
> See #895599
> Apply fix in 
> https://github.com/ganeti/ganeti/commit/5f90a0f64bf5fee7fe353a95d02c79736a5943c5
> 
> For me works.
> Regards, Mauro

Yes, this is already queued up for a stable update. Thanks!

Bug#912433: libgoogle-gson-java FTBFS with OpenJDK 11

[Adrian Bunk]

Source: libgoogle-gson-java
Version: 2.8.2-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libgoogle-gson-java.html

...
[INFO] Running com.google.gson.DefaultDateTypeAdapterTest
[ERROR] Tests run: 11, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.242 
s <<< FAILURE! - in com.google.gson.DefaultDateTypeAdapterTest
[ERROR] 
testParsingDatesFormattedWithSystemLocale(com.google.gson.DefaultDateTypeAdapterTest)
  Time elapsed: 0.118 s  <<< ERROR!
com.google.gson.JsonSyntaxException: jeudi 1 janvier 1970 ? 00:00:00 
Coordinated Universal Time
at 
com.google.gson.DefaultDateTypeAdapterTest.assertParsed(DefaultDateTypeAdapterTest.java:195)
at 
com.google.gson.DefaultDateTypeAdapterTest.testParsingDatesFormattedWithSystemLocale(DefaultDateTypeAdapterTest.java:90)
Caused by: java.text.ParseException: Failed to parse date ["jeudi 1 janvier 
1970 ? 00:00:00 Coordinated Universal Time']: Invalid number: jeud
at 
com.google.gson.DefaultDateTypeAdapterTest.assertParsed(DefaultDateTypeAdapterTest.java:195)
at 
com.google.gson.DefaultDateTypeAdapterTest.testParsingDatesFormattedWithSystemLocale(DefaultDateTypeAdapterTest.java:90)
Caused by: java.lang.NumberFormatException: Invalid number: jeud
at 
com.google.gson.DefaultDateTypeAdapterTest.assertParsed(DefaultDateTypeAdapterTest.java:195)
at 
com.google.gson.DefaultDateTypeAdapterTest.testParsingDatesFormattedWithSystemLocale(DefaultDateTypeAdapterTest.java:90)

Processed: Re: Bug#908112: possible fix

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #908112 [ganeti] ganeti: Unable to move an instance to an other node
Added tag(s) pending.

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

Bug#912434: devscripts-el Depends: elpa-devscripts-el but it is not installable

[Adrian Bunk]

Package: devscripts-el
Version: 40.2
Severity: serious

The following packages have unmet dependencies:
 devscripts-el : Depends: elpa-devscripts-el but it is not installable

Bug#912436: xandikos FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xce in position 447: ordinal not in range(128)

[Adrian Bunk]

Source: xandikos
Version: 0.0.10-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=xandikos&arch=all&ver=0.0.10-1&stamp=1540956480&raw=0

...
dh clean --with python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py clean 
running clean
removing '/<>/.pybuild/cpython3_3.7/build' (and everything under 
it)
'build/bdist.linux-amd64' does not exist -- can't clean it
'build/scripts-3.7' does not exist -- can't clean it
I: pybuild base:217: python3.6 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 35, in 
long_description = f.read()
  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 0xce in position 447: 
ordinal not in range(128)
E: pybuild pybuild:338: clean: plugin distutils failed with: exit code=1: 
python3.6 setup.py clean 
dh_auto_clean: pybuild --clean -i python{version} -p "3.7 3.6" returned exit 
code 13
make: *** [debian/rules:4: clean] Error 25

Bug#912435: getmail FTBFS: cannot stat 'debian/getmail/usr/share/doc/getmail-*': No such file or directory

[Adrian Bunk]

Source: getmail
Version: 5.7-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=getmail&arch=all&ver=5.7-1&stamp=1540940824&raw=0

...
dh_install
# Move documentation files created by setup.py
# to Debian style versionless directory
mv debian/getmail/usr/share/doc/getmail-* \
debian/getmail/usr/share/doc/getmail
mv: cannot stat 'debian/getmail/usr/share/doc/getmail-*': No such file or 
directory
make[1]: *** [debian/rules:15: override_dh_install] Error 1

Bug#912437: openmpi-bin: Fails to upgrade: update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link /usr/bin/mpicc

[Axel Beckert]

Package: openmpi-bin
Version: 3.1.3-1
Severity: serious

openmpi-bin fails to upgrade from 3.1.2-6 to 3.1.3-1 as follows for me:

Setting up openmpi-bin (3.1.3-1) ...
update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave link 
same as main link /usr/bin/mpicc
dpkg: error processing package openmpi-bin (--configure):
 installed openmpi-bin package post-installation script subprocess returned 
error exit status 2
Errors were encountered while processing:
 openmpi-bin

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

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

Versions of packages openmpi-bin depends on:
ii  libc62.27-8
ii  libevent-2.1-6   2.1.8-stable-4
ii  libevent-pthreads-2.1-6  2.1.8-stable-4
ii  libhwloc51.11.11-2
ii  libopenmpi3  3.1.3-1
ii  openmpi-common   3.1.3-1
ii  openssh-client [ssh-client]  1:7.9p1-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages openmpi-bin recommends:
pn  libopenmpi-dev  

Versions of packages openmpi-bin suggests:
ii  gfortran  4:8.2.0-2

-- no debconf information

Bug#912437: openmpi-bin: Fails to upgrade: update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link /usr/bin/mpicc

[Alastair McKinstry]

Thanks for this report.

I'm unable to reproduce this, and have no failures testing 3.1.2-6 -> 
3.1.3-1 upgrade.


The change made in the openmpi-bin.postinst script was to enable "set 
-e" properly (avoiding a conditional  in the script that relied on 
testing non-zero return code). I suspect that 
/var/lib/dpkg/alternatives/mpi was corrupt from a previous upgrade 
(quite likely; major changes happened in the 2->3 transition due to 
multiarch handling).


So, I think:

(1) the current package is actually technically ok.

(2) Some more handling needs to be added to cope with 'inheriting' a 
corrupt mpi alternatives.


regards

Alastair


On 31/10/2018 14:28, Axel Beckert wrote:

Package: openmpi-bin
Version: 3.1.3-1
Severity: serious

openmpi-bin fails to upgrade from 3.1.2-6 to 3.1.3-1 as follows for me:

Setting up openmpi-bin (3.1.3-1) ...
update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave link 
same as main link /usr/bin/mpicc
dpkg: error processing package openmpi-bin (--configure):
  installed openmpi-bin package post-installation script subprocess returned 
error exit status 2
Errors were encountered while processing:
  openmpi-bin

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

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

Versions of packages openmpi-bin depends on:
ii  libc62.27-8
ii  libevent-2.1-6   2.1.8-stable-4
ii  libevent-pthreads-2.1-6  2.1.8-stable-4
ii  libhwloc51.11.11-2
ii  libopenmpi3  3.1.3-1
ii  openmpi-common   3.1.3-1
ii  openssh-client [ssh-client]  1:7.9p1-1
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages openmpi-bin recommends:
pn  libopenmpi-dev  

Versions of packages openmpi-bin suggests:
ii  gfortran  4:8.2.0-2

-- no debconf information


--
Alastair McKinstry, , , 
https://diaspora.sceal.ie/u/amckinstry
Commander Vimes didn’t like the phrase “The innocent have nothing to fear,”
 believing the innocent had everything to fear, mostly from the guilty but in 
the longer term
 even more from those who say things like “The innocent have nothing to fear.”
 - T. Pratchett, Snuff

Bug#912437: openmpi-bin: Fails to upgrade: update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link /usr/bin/mpicc

[Axel Beckert]

Hi Alastair,

Alastair McKinstry wrote:
> The change made in the openmpi-bin.postinst script was to enable
> "set -e" properly (avoiding a conditional  in the script that relied
> on testing non-zero return code). I suspect that
> /var/lib/dpkg/alternatives/mpi was corrupt from a previous upgrade
> (quite likely; major changes happened in the 2->3 transition due to
> multiarch handling).

Indeed, this system has about 2.5 years of Debian Unstable history,
yes. :-)

Attached the contents of /var/lib/dpkg/alternatives/mpi. Since I can
still reproduce the issue by calling e.g. "dpkg --configure -a", this
doesn't seem to be a one-time issue. I hope the attached file enables
you to find the root cause.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
auto
/usr/bin/mpicc
libmpi++.so
/usr/lib/libmpi++.so
libmpi.so
/usr/lib/libmpi.so
libmpicxx.so
/usr/lib/libmpicxx.so
libmpif77.so
/usr/lib/libmpif77.so
libmpif90.so
/usr/lib/libmpif90.so
libmpifort.so
/usr/lib/libmpifort.so
mpi.pc
/usr/lib/x86_64-linux-gnu/pkgconfig/mpi.pc
mpiCC
/usr/bin/mpiCC
mpiCC.1.gz
/usr/share/man/man1/mpiCC.1.gz
mpic++
/usr/bin/mpic++
mpic++.1.gz
/usr/share/man/man1/mpic++.1.gz
mpicc
/usr/bin/mpicc
mpicc.1.gz
/usr/share/man/man1/mpicc.1.gz
mpicxx
/usr/bin/mpicxx
mpicxx.1.gz
/usr/share/man/man1/mpicxx.1.gz
mpif77
/usr/bin/mpif77
mpif77.1.gz
/usr/share/man/man1/mpif77.1.gz
mpif90
/usr/bin/mpif90
mpif90.1.gz
/usr/share/man/man1/mpif90.1.gz
mpifort
/usr/bin/mpifort
mpifort.1.gz
/usr/share/man/man1/mpifort.1.gz

/usr/bin/mpicc.openmpi
50







/usr/bin/mpic++.openmpi
/usr/share/man/man1/mpiCC.openmpi.1.gz
/usr/bin/mpic++.openmpi
/usr/share/man/man1/mpic++.openmpi.1.gz

/usr/share/man/man1/mpicc.openmpi.1.gz
/usr/bin/mpic++.openmpi
/usr/share/man/man1/mpicxx.openmpi.1.gz
/usr/bin/mpif77.openmpi
/usr/share/man/man1/mpif77.openmpi.1.gz
/usr/bin/mpif90.openmpi
/usr/share/man/man1/mpif90.openmpi.1.gz
/usr/bin/mpifort.openmpi
/usr/share/man/man1/mpifort.openmpi.1.gz
/usr/include/mpich
40
/usr/lib/x86_64-linux-gnu/libmpichcxx.so
/usr/lib/x86_64-linux-gnu/libmpich.so
/usr/lib/x86_64-linux-gnu/libmpichcxx.so
/usr/lib/x86_64-linux-gnu/libmpichfort.so
/usr/lib/x86_64-linux-gnu/libmpichfort.so
/usr/lib/x86_64-linux-gnu/libmpichfort.so
/usr/lib/x86_64-linux-gnu/pkgconfig/mpich.pc
/usr/bin/mpicxx.mpich
/usr/share/man/man1/mpicxx.mpich.1.gz
/usr/bin/mpicxx.mpich
/usr/share/man/man1/mpicxx.mpich.1.gz
/usr/bin/mpicc.mpich
/usr/share/man/man1/mpicc.mpich.1.gz
/usr/bin/mpicxx.mpich
/usr/share/man/man1/mpicxx.mpich.1.gz
/usr/bin/mpifort.mpich
/usr/share/man/man1/mpif77.mpich.1.gz
/usr/bin/mpifort.mpich
/usr/share/man/man1/mpif90.mpich.1.gz
/usr/bin/mpifort.mpich
/usr/share/man/man1/mpifort.mpich.1.gz

Bug#911464: free42-nologo: Numbers entered incorrectly on arm architectures

[Stephen Kitt]

On Sat, Oct 20, 2018 at 04:00:17PM +0200, AKrempler wrote:
> entering numbers in free42-nologo does not work on armhf and arm64 
> architectures (but does work as expected on i386 and amd64).
> 
> I would expect that typing [1][0][enter] would have the (decimal) number 10 
> in the x register and on the display.

This is fixed in current upstream versions (at least, 2.0.21 doesn’t
suffer from this issue on my ARM systems, whereas 1.4.77 does).

Christian, do you need a hand upgrading the package?

Regards,

Stephen


signature.asc
Description: PGP signature

Bug#863520: Will bug #863520 be fixed in stable

[Frédéric Brin]

Hello,

We are an other party hit by this bug.

Could you please enlighten us what the best option to fix this bug
could be ?
-> My preference would be to have the 2.5.11 backported to stable

Regards,
Frédéric

Processed: Re: Bug#909750: applications tries to write to /usr/* directories via libfontconfig1

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #909750 [libfontconfig1] applications tries to write to /usr/* directories 
via libfontconfig1
Severity set to 'serious' from 'normal'

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

Processed: severity of 885685 is important

[Debian Bug Tracking System]

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

> severity 885685 important
Bug #885685 [src:ufoai] ufoai: Depends on unmaintained gtksourceview2
Severity set to 'important' from 'serious'
> thanks
Stopping processing here.

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

Processed: openhft-chronicle-threads FTBFS with OpenJDK 11

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 1.16.3-1
Bug #912445 [src:openhft-chronicle-threads] openhft-chronicle-threads  FTBFS 
with OpenJDK 11
Marked as fixed in versions openhft-chronicle-threads/1.16.3-1.
> close -1
Bug #912445 [src:openhft-chronicle-threads] openhft-chronicle-threads  FTBFS 
with OpenJDK 11
Marked Bug as done

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

Bug#912445: openhft-chronicle-threads FTBFS with OpenJDK 11

[Adrian Bunk]

Source: openhft-chronicle-threads
Version: 1.1.6-1
Severity: serious
Tags: ftbfs buster sid
Control: fixed -1 1.16.3-1
Control: close -1

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/openhft-chronicle-threads.html

...
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 2.711 s
[INFO] Finished at: 2019-12-02T18:25:38-12:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) 
on project chronicle-threads: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/openhft-chronicle-threads-1.1.6/src/main/java/net/openhft/chronicle/threads/MonitorEventLoop.java:[28,20]
 package javax.xml.ws does not exist
[ERROR] 
/build/1st/openhft-chronicle-threads-1.1.6/src/main/java/net/openhft/chronicle/threads/MonitorEventLoop.java:[123,32]
 cannot find symbol
[ERROR]   symbol:   class WebServiceException
[ERROR]   location: class net.openhft.chronicle.threads.MonitorEventLoop
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/openhft-chronicle-threads-1.1.6 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/openhft-chronicle-threads-1.1.6/debian/maven.properties
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/openhft-chronicle-threads-1.1.6/debian 
-Dmaven.repo.local=/build/1st/openhft-chronicle-threads-1.1.6/debian/maven-repo 
--batch-mode package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned 
exit code 1
make: *** [debian/rules:4: build] Error 1


This bug is already fixed in experimental.

Bug#911670: php-igbinary only comes with a module for PHP 7.3, making it unusable with the buster default PHP 7.2

[Veilleux, Anthony]

There are use cases for which PHP 7.3 is not acceptable, such as applications 
that we don't have control over failing to support PHP 7.3 (in my personal 
case, NextCloud Stable). Is there a compelling reason not to compile 
php7.X-igbinary packages to support these use cases, like many other modules do?


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.

Bug#912450: python-nanomsg FTBFS with nanomsg 1.1.5

[Adrian Bunk]

Source: python-nanomsg
Version: 1.0-2
Severity: serious
Tags: ftbfs

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

...
   dh_auto_test -a -O--buildsystem=pybuild
I: pybuild base:217: python2.7 setup.py test 
running test
running egg_info
creating nanomsg.egg-info
writing nanomsg.egg-info/PKG-INFO
writing top-level names to nanomsg.egg-info/top_level.txt
writing dependency_links to nanomsg.egg-info/dependency_links.txt
writing manifest file 'nanomsg.egg-info/SOURCES.txt'
reading manifest file 'nanomsg.egg-info/SOURCES.txt'
writing manifest file 'nanomsg.egg-info/SOURCES.txt'
running build_ext
building '_nanomsg_cpy' extension
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-fno-strict-aliasing -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python2.7 -c _nanomsg_cpy/wrapper.c -o 
build/temp.linux-amd64-2.7/_nanomsg_cpy/wrapper.o
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-A8UpPM/python2.7-2.7.15=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 
build/temp.linux-amd64-2.7/_nanomsg_cpy/wrapper.o -lnanomsg -o 
/<>/_nanomsg_cpy.so -Wl,-z,now
test_subscribe_works (tests.test_pubsub.TestPubSubSockets) ... ok
test_send_recv (tests.test_pair.TestPairSockets) ... ok
test_send_recv_large_message (tests.test_pair.TestPairSockets) ... ok
test_send_recv_with_embeded_nulls (tests.test_pair.TestPairSockets) ... ok
test_bind (tests.test_general_socket_methods.TestGeneralSocketMethods) ... ok
test_connect (tests.test_general_socket_methods.TestGeneralSocketMethods) ... ok
test_get_int_option 
(tests.test_general_socket_methods.TestGeneralSocketMethods) ... FAIL
test_is_open_is_false_when_closed 
(tests.test_general_socket_methods.TestGeneralSocketMethods) ... ok
test_is_open_is_true_when_open 
(tests.test_general_socket_methods.TestGeneralSocketMethods) ... ok
test_set_int_option 
(tests.test_general_socket_methods.TestGeneralSocketMethods) ... FAIL

==
FAIL: test_get_int_option 
(tests.test_general_socket_methods.TestGeneralSocketMethods)
--
Traceback (most recent call last):
  File "/<>/tests/test_general_socket_methods.py", line 56, in 
test_get_int_option
self.assertEqual(LINGER_DEFAULT_VALUE, actual)
AssertionError: 1000 != 0

==
FAIL: test_set_int_option 
(tests.test_general_socket_methods.TestGeneralSocketMethods)
--
Traceback (most recent call last):
  File "/<>/tests/test_general_socket_methods.py", line 51, in 
test_set_int_option
self.assertEqual(expected, actual)
AssertionError: 500 != 0

--
Ran 10 tests in 0.024s

FAILED (failures=2)
Test failed: 
error: Test failed: 
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=1: 
python2.7 setup.py test 
dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
make: *** [debian/rules:7: build-arch] Error 25

Bug#912451: staden-io-lib FTBFS on !x86: test failures

[Adrian Bunk]

Source: staden-io-lib
Version: 1.14.11-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=staden-io-lib&suite=sid

...
FAIL: scram
===

Loading ce.fa
Generating ce#sorted.sam
Generating ce#unsorted.sam
=== testing ./data/c1#bounds.sam ===
./scram.test: 27: [: ./data/c1#bounds.sam: unexpected operator
 ../progs/scramble  ./data/c1#bounds.sam test.out/c1#bounds.sam
 ../progs/scramble  -r ./data/c1.fa ./data/c1#bounds.sam 
test.out/c1#bounds.full.cram
 ../progs/scramble  ./data/c1#bounds.sam > test.out/tmp.sam
 ../progs/scramble  test.out/c1#bounds.full.cram > test.out/c1#bounds.full.sam
 ../progs/scramble  -O bam test.out/c1#bounds.full.cram > 
test.out/c1#bounds.full.bam
 ../progs/scramble  test.out/c1#bounds.full.bam test.out/tmp.sam
corrupted size vs. prev_size
Aborted
FAIL scram.test (exit status: 1)

FAIL: scram_mt
==

=== testing ./data/c1#bounds.sam ===
./scram.test: 27: [: ./data/c1#bounds.sam: unexpected operator
 ../progs/scramble -t4 ./data/c1#bounds.sam test.out/c1#bounds.sam
 ../progs/scramble -t4 -r ./data/c1.fa ./data/c1#bounds.sam 
test.out/c1#bounds.full.cram
 ../progs/scramble -t4 ./data/c1#bounds.sam > test.out/tmp.sam
 ../progs/scramble -t4 test.out/c1#bounds.full.cram > 
test.out/c1#bounds.full.sam
 ../progs/scramble -t4 -O bam test.out/c1#bounds.full.cram > 
test.out/c1#bounds.full.bam
 ../progs/scramble -t4 test.out/c1#bounds.full.bam test.out/tmp.sam
corrupted size vs. prev_size
Aborted
FAIL scram_mt.test (exit status: 1)


Testsuite summary for io_lib 1.14.11

# TOTAL: 9
# PASS:  7
# SKIP:  0
# XFAIL: 0
# FAIL:  2
# XPASS: 0
# ERROR: 0

See tests/test-suite.log

make[4]: *** [Makefile:716: test-suite.log] Error 1

Processed: severity of 867719 is grave

[Debian Bug Tracking System]

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

> severity 867719 grave
Bug #867719 [src:phpldapadmin] phpldapadmin: CVE-2017-11107
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#867719: phpldapadmin: CVE-2017-11107

[Antoine Beaupre]

Control: tags 867719 +patch

The attached patch fixes the issue and was applied to the wheezy and
jessie versions of the package.

It comes from the Ubuntu version of this same bug:

https://bugs.launchpad.net/ubuntu/+source/phpldapadmin/+bug/1701731
--- phpldapadmin-1.2.2.orig/htdocs/entry_chooser.php
+++ phpldapadmin-1.2.2/htdocs/entry_chooser.php
@@ -15,9 +15,9 @@ $www['page'] = new page();
 
 $request = array();
 $request['container'] = get_request('container','GET');
-$request['form'] = get_request('form','GET');
-$request['element'] = get_request('element','GET');
-$request['rdn'] = get_request('rdn','GET');
+$request['form'] = htmlspecialchars(addslashes(get_request('form','GET')));
+$request['element'] = htmlspecialchars(addslashes(get_request('element','GET')));
+$request['rdn'] = htmlspecialchars(addslashes(get_request('rdn','GET')));
 
 echo '';
 printf('%s',_('Entry Chooser'));
@@ -33,7 +33,7 @@ echo '';
 echo '';
 if ($request['container']) {
 	printf('%s:%s',_('Server'),$app['server']->getName());
-	printf('%s:%s',_('Looking in'),$request['container']);
+	printf('%s:%s',_('Looking in'),htmlspecialchars($request['container']));
 	echo ' ';
 }
 


signature.asc
Description: PGP signature

Bug#911971: marked as done (t50 builds with -march=native)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 17:55:55 +
with message-id 
and subject line Bug#911971: fixed in t50 5.8.2-2
has caused the Debian Bug report #911971,
regarding t50 builds with -march=native
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.)


-- 
911971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911971
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: t50
Version: 5.8.2-1
Severity: serious

t50 builds with -march=native, which makes the resulting binaries
only run on machines that are compatible with whatever buildd
built the package.

Please remove -march=native.
--- End Message ---
--- Begin Message ---
Source: t50
Source-Version: 5.8.2-2

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

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

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

Debian distribution maintenance software
pp.
Samuel Henrique  (supplier of updated t50 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, 26 Oct 2018 16:38:49 -0300
Source: t50
Binary: t50
Architecture: source
Version: 5.8.2-2
Distribution: unstable
Urgency: high
Maintainer: Debian Security Tools 
Changed-By: Samuel Henrique 
Description:
 t50- Multi-protocol packet injector tool
Closes: 911971
Changes:
 t50 (5.8.2-2) unstable; urgency=high
 .
   * d/u/metadata: update urls to gitlab
   * d/p/01_Fix-Makefile.patch: Update to remove march-native flag
 (closes: #911971)
Checksums-Sha1:
 615b3568fcb7dfd49230b4f43d9e6bb8d4d991cd 1916 t50_5.8.2-2.dsc
 3b91b0fae86ac854dcb67987a0648d7f17097b61 6880 t50_5.8.2-2.debian.tar.xz
 54dbef8a2f189c1fa40382700610cc60df1b4298 5469 t50_5.8.2-2_amd64.buildinfo
Checksums-Sha256:
 b8349c6424f5ef993626dcb70cc950921c83948e82b2ffe04d6250be007e339d 1916 
t50_5.8.2-2.dsc
 9799b29be605b2a97c66ac5017a36142eb9283a5dbbd9fc00cecb8af8168cd15 6880 
t50_5.8.2-2.debian.tar.xz
 6bdb53865b4a87c2ee9eb4af74801e2dce095a3dc76103aabe14163e9fa02e8c 5469 
t50_5.8.2-2_amd64.buildinfo
Files:
 7380a25788ad96e58dbb7f6dd1904323 1916 utils optional t50_5.8.2-2.dsc
 82cd771a5233c1cb84a06702c07bbb28 6880 utils optional t50_5.8.2-2.debian.tar.xz
 10fec1de2caf5fef035938591b2b6546 5469 utils optional 
t50_5.8.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEBdtqg34QX0sdAsVfu6n6rcz7RwcFAlvZ52gACgkQu6n6rcz7
Rwf81xAAqWAy6w0jE6dILERdZFik4pjKn1a4JZpUro0xSaJtq1oZyIT662t0npoj
eQIgz9cD2+34dNxnMobH3QheWq2DU5PYmege42tRzjqhftvXqZbrif+Sx2MaF4dT
he9DEZIZuMBq0a0u8Mgn8BVPByQihUdKkqvcBP/dUMLYcUSe0B26y3E0tlAcdrgP
Vze99N6SO6SyeGh34qbIyYUEsef+w7ZoGn+zthHPHZgfXhDz41l8GGqAw28+5QBu
mjvYYc0el9NErbpROO9caM/iPtKUrXCBrVNescpwox00pHye77BPZeCu/k0Q/nJm
nS+jcwfnCY/KSDCxTxnjzSwjBbBvF3pT7Q/gzlJixSvPPZ+qDVW16OWJtDyU1pIW
mZPPIdMEYmTo4oY8JHhhHzNNTpz7a3ZiZQG7pUqN4ZRtA7bEPUlcsFULp72SrRe3
SyoSJQUGXYbMbEcQYrkZiRCcuSTlJwxlOkdm7/PzW3SCwNs+mWQoQiYSOrsggrLq
cD7lP1fjFXYSLzQdbmPNoRoRbPCyQxEahYqI2SgTn7j684tvWxMTlt5RafGhN4Os
be4mmCFymqFRmqcYyxG+8nhlSJxyvLSg4jXjwqHFiBGi3GGuGXPqOD205xkYqy40
3ldYUBDZQEPWngXZPUDiRnERboeT+b7a0OKrSQBAOXCby6NAwho=
=yQDU
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#867719: phpldapadmin: CVE-2017-11107

[Debian Bug Tracking System]

Processing control commands:

> tags 867719 +patch
Bug #867719 [src:phpldapadmin] phpldapadmin: CVE-2017-11107
Added tag(s) patch.

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

Bug#911670: php-igbinary only comes with a module for PHP 7.3, making it unusable with the buster default PHP 7.2

[Ondřej Surý]

PHP 7.2 had been removed from Debian unstable and it will go from testing as 
soon as the transition is complete.

NextCloud is not available from Debian, but generally speaking, if you want a 
stable distribution then you need to use Debian stable.

Ondrej
--
Ondřej Surý 

> On 31 Oct 2018, at 17:58, Veilleux, Anthony  wrote:
> 
> There are use cases for which PHP 7.3 is not acceptable, such as applications 
> that we don't have control over failing to support PHP 7.3 (in my personal 
> case, NextCloud Stable). Is there a compelling reason not to compile 
> php7.X-igbinary packages to support these use cases, like many other modules 
> do?
> 
> 
> The information in this e-mail is intended only for the person to whom it is
> addressed. If you believe this e-mail was sent to you in error and the e-mail
> contains patient information, please contact the Partners Compliance HelpLine 
> at
> http://www.partners.org/complianceline . If the e-mail was sent to you in 
> error
> but does not contain patient information, please contact the sender and 
> properly
> dispose of the e-mail.
> 

Bug#912455: istack-commons FTBFS with OpenJDK 11

[Adrian Bunk]

Source: istack-commons
Version: 3.0.6-2
Severity: serious
Tags: ftbfs

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

...
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/1st/istack-commons-3.0.6/istack-commons/runtime/src/main/java/module-info.java:[44,29]
 module not found: java.activation
[INFO] 1 error

Bug#912456: imbalanced-learn FTBFS with scikit-learn 0.20.0

[Adrian Bunk]

Source: imbalanced-learn
Version: 0.3.3-1
Severity: serious
Tags: ftbfs

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

...
   dh_auto_test -O--buildsystem=pybuild
I: pybuild base:217: cd 
/build/1st/imbalanced-learn-0.3.3/.pybuild/cpython3_3.6_imbalanced-learn/build; 
python3.6 -m pytest 
= test session starts ==
platform linux -- Python 3.6.7, pytest-3.6.4, py-1.6.0, pluggy-0.6.0
rootdir: /build/1st/imbalanced-learn-0.3.3, inifile: setup.cfg
plugins: doctestplus-0.1.3
collected 228 items / 2 errors

 ERRORS 
 ERROR collecting 
.pybuild/cpython3_3.6_imbalanced-learn/build/imblearn/tests/test_common.py 
imblearn/tests/test_common.py:6: in 
from sklearn.utils.testing import _named_check
E   ImportError: cannot import name '_named_check'
 ERROR collecting 
.pybuild/cpython3_3.6_imbalanced-learn/build/imblearn/tests/test_common.py 
ImportError while importing test module 
'/build/1st/imbalanced-learn-0.3.3/.pybuild/cpython3_3.6_imbalanced-learn/build/imblearn/tests/test_common.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
imblearn/tests/test_common.py:6: in 
from sklearn.utils.testing import _named_check
E   ImportError: cannot import name '_named_check'
!!! Interrupted: 2 errors during collection 
=== 2 error in 1.42 seconds 
E: pybuild pybuild:338: test: plugin distutils failed with: exit code=2: cd 
/build/1st/imbalanced-learn-0.3.3/.pybuild/cpython3_3.6_imbalanced-learn/build; 
python3.6 -m pytest 
dh_auto_test: pybuild --test --test-pytest -i python{version} -p 3.6 returned 
exit code 13
make: *** [debian/rules:5: build] Error 25

Bug#906860: xul-ext-mozvoikko no longer works with firefox-esr 60

[Moritz Mühlenhoff]

On Mon, Oct 08, 2018 at 10:44:15PM +0200, Moritz Mühlenhoff wrote:
> On Tue, Aug 28, 2018 at 10:08:51AM +0300, Timo Jyrinki wrote:
> > Unfortunately upstream has removed the API that makes it possible to add
> > external spellcheckers, and the upstream selected library for
> > spellchecking is unable to properly support a language with a structure
> > of Finnish.
> > 
> > Currently there is no other option than to live without spell-checking
> > support in Mozilla products, and eg copy-paste to and back from a text
> > editor for spell checking. Or use a full Voikko library compiled into
> > Javascript with dependencies like at
> > https://www.puimula.org/htp/testing/js-libvoikko/js-libvoikko-demo.html
> 
> Let's remove mozvoikko from the archive, then?

Filed a removal bug as #912457.

Cheers,
Moritz

Bug#912458: jftp FTBFS with OpenJDK 11

[Adrian Bunk]

Source: jftp
Version: 1.60+dfsg-2
Severity: serious
Tags: ftbfs buster sid

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

...
compile:
[javac] /build/1st/jftp-1.60+dfsg/build.xml:68: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Compiling 125 source files to 
/build/1st/jftp-1.60+dfsg/build/classes
[javac] 
/build/1st/jftp-1.60+dfsg/src/java/net/sf/jftp/util/JReciever.java:95: error: 
cannot find symbol
[javac] reciever.destroy();
[javac] ^
[javac]   symbol:   method destroy()
[javac]   location: variable reciever of type Thread
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 1 error

BUILD FAILED
/build/1st/jftp-1.60+dfsg/build.xml:68: Compile failed; see the compiler error 
output for details.

Total time: 5 seconds
dh_auto_build: ant -Duser.name debian -Dant.build.javac.source=1.6 
-Dant.build.javac.target=1.6 jars returned exit code 1
make[1]: *** [debian/rules:11: override_dh_auto_build] Error 2

Bug#865967: marked as done (trac 1.2 no longer provides get_db_cnx)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 19:04:33 +
with message-id 
and subject line Bug#865967: fixed in trac-tags 0.9-1
has caused the Debian Bug report #865967,
regarding trac 1.2 no longer provides get_db_cnx
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.)


-- 
865967: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865967
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: trac-tags
Version: 0.7+svn12392-1
Severity: important

Dear Maintainer,

the trac-tags plugin is not usable after installing trac and trac-tags on a 
fresh container environment
of current debian stable.
Trac is configured to use sqlite as database backend and no user management is 
used for this test case.

After installing the packages and configuring Apache to serve trac, the 
trac-tags plugin is enabled
via the web admin guis plugin section. Then the required database upgrade is 
run via a terminal session.
Additionally the suggested wiki upgrade is also executed.

Afterwards the trac project is broken as the Wiki start page now shows an 
Oops...:
# Oops…
#
# Trac detected an internal error:
#
#   AttributeError: 'Environment' object has no attribute 'get_db_cnx'
# ...
# Python Traceback
# Most recent call last:
#
#File "/usr/lib/python2.7/dist-packages/trac/web/main.py", line 613, in 
_dispatch_request
#File "/usr/lib/python2.7/dist-packages/trac/web/main.py", line 273, in 
dispatch
#File "/usr/lib/python2.7/dist-packages/trac/web/chrome.py", line 1123, in 
render_template
#File "/usr/lib/python2.7/dist-packages/genshi/core.py", line 133, in __or__
#File "/usr/lib/python2.7/dist-packages/trac/web/chrome.py", line 1436, in 
inner
#File "/usr/lib/python2.7/dist-packages/tractags/wiki.py", line 101, in 
filter_stream
#File "/usr/lib/python2.7/dist-packages/tractags/wiki.py", line 167, in 
_wiki_view
#File "/usr/lib/python2.7/dist-packages/tractags/wiki.py", line 162, in 
_page_tags
#File "/usr/lib/python2.7/dist-packages/tractags/api.py", line 238, in 
get_tags
#File "/usr/lib/python2.7/dist-packages/tractags/model.py", line 98, in 
resource_tags
#File "/usr/lib/python2.7/dist-packages/tractags/model.py", line 113, in 
_get_db 

However, the project can be reset into a usable state by restoring the 
/db/trac.db from the backup version
from pre-upgrade as well as removing all bitten config entries from 
conf/trac.ini within the trac project
folder.

The trac-tags functionality remains unusable.


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

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

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


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

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

Versions of packages trac-tags depends on:
ii  python2.7.13-2
ii  python-genshi 0.7-5
ii  python-pkg-resources  33.1.1-1
ii  trac  1.2+dfsg-1

trac-tags recommends no packages.

trac-tags suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: trac-tags
Source-Version: 0.9-1

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated trac-tags 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 31 Oct 2018 14:31:08 -0400
Source: trac-tags
Binary: trac-tags
Architecture: source
Version: 0.9-1
Distribution: unstable
Urgency: medium
Maintainer: Daniel Kahn Gillmor 
Changed-By: Daniel Kahn Gillmor 
Description:
 trac-tags  - T

Bug#912459: jaxe FTBFS with OpenJDK 11

[Adrian Bunk]

Source: jaxe
Version: 3.5-9
Severity: serious
Tags: ftbfs

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

...
[javac] /build/1st/jaxe-3.5/source/jaxe/JaxeTransferHandler.java:284: 
error: cannot find symbol
[javac] sm.checkSystemClipboardAccess();
[javac]   ^
[javac]   symbol:   method checkSystemClipboardAccess()
[javac]   location: variable sm of type SecurityManager

Bug#912461: jaxb FTBFS with OpenJDK 11

[Adrian Bunk]

Source: jaxb
Version: 2.3.0.1-5
Severity: serious
Tags: ftbfs

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

...
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 18.186 s
[INFO] Finished at: 2018-10-31T07:37:00-12:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) 
on project jaxb-core: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/jaxb-2.3.0.1/jaxb-ri/core/src/main/java/com/sun/xml/bind/v2/model/core/PropertyInfo.java:[45,23]
 error: package javax.activation does not exist
[ERROR] 
/build/1st/jaxb-2.3.0.1/jaxb-ri/core/src/main/java/com/sun/xml/bind/v2/model/core/PropertyInfo.java:[143,4]
 error: cannot find symbol
[ERROR]   symbol:   class MimeType
[ERROR]   location: interface PropertyInfo
[ERROR]   where T,C are type-variables:
[ERROR] T extends Object declared in interface PropertyInfo
[ERROR] C extends Object declared in interface PropertyInfo
[ERROR] 
/build/1st/jaxb-2.3.0.1/jaxb-ri/core/src/main/java/com/sun/xml/bind/v2/runtime/SwaRefAdapterMarker.java:[44,23]
 error: package javax.activation does not exist
[ERROR] 
/build/1st/jaxb-2.3.0.1/jaxb-ri/core/src/main/java/com/sun/xml/bind/v2/runtime/SwaRefAdapterMarker.java:[51,60]
 error: cannot find symbol
[ERROR]   symbol: class DataHandler
[ERROR] 
/build/1st/jaxb-2.3.0.1/jaxb-ri/core/src/main/java/com/sun/xml/bind/v2/runtime/SwaRefAdapterMarker.java:[53,11]
 error: cannot find symbol
[ERROR]   symbol:   class DataHandler
[ERROR]   location: class SwaRefAdapterMarker
[ERROR] 
/build/1st/jaxb-2.3.0.1/jaxb-ri/core/src/main/java/com/sun/xml/bind/v2/runtime/SwaRefAdapterMarker.java:[57,26]
 error: cannot find symbol
[ERROR]   symbol:   class DataHandler
[ERROR]   location: class SwaRefAdapterMarker
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :jaxb-core
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/jaxb-2.3.0.1 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/jaxb-2.3.0.1/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/jaxb-2.3.0.1/debian 
-Dmaven.repo.local=/build/1st/jaxb-2.3.0.1/debian/maven-repo --batch-mode -f 
jaxb-ri/pom.xml package javadoc:aggregate -DskipTests -DskipTests 
-Dnotimestamp=true -Dlocale=en_US returned exit code 1
make[1]: *** [debian/rules:9: override_dh_auto_build] Error 1

Bug#911904: Processed: block 911904 with 911915

[073plan]

Hi all,

在 2018-10-26五的 13:49 +0200，Michal Čihař写道：
> Hi
> 
> On Fri, 2018-10-26 at 10:51 +0200, Ondřej Surý wrote:
> > LIBTIDY_LIBRARY=$(shell readlink -f
> > /usr/lib/$(DEB_HOST_MULTIARCH)/libtidy.so)
> 
> Well it all started from this file being absent from the package :-)
> 
> > LIBTIDY_PACKAGE=$(shell dpkg-query --search $(LIBTIDY_LIBRARY) | cut
> > -f 1 -d :)
> > LIBTIDY_LIBRARY_FILE$(shell basename $(LIBTIDY_LIBRARY))
> > 
> > then
> > 
> > sed -e “s/libtidy.so/$(LIBTIDY_LIBRARY_FILE)” lib.py
> > 
> > echo libtidy:Depends=$(LIBTIDY_PACKAGE) > python-utidylib.substvars
> > 
> > and replace
> > 
> > libtidy5deb1 | libtidy5,
> 
> I don't get what this would solve - there is nothing wrong with
> alternate dependecies as long as they both provide libtidy.so. Anyway
> same is in Build-Depends as well, where substvars are not really
> helpful.

So what will be the final solution? I'm wondering if we could solve the
problem soon to complete the transition.

BTW I see the advantage of automatically generating lib dependency; however, I
also believe that listing alternate dependencies should be okay as well since
it extends the compatibility range of binary package. Manual adjustment will
be necessary in each transition but as long as the package maintainer is
comfortable with that, it should be acceptable.


--
Regards,
Boyuan Yang

Bug#903826: marked as done (python3-pycuda: fails to install with python 3.7 as a supported python version)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 19:44:56 +
with message-id 
and subject line Bug#903826: fixed in pycuda 2018.1.1-1
has caused the Debian Bug report #903826,
regarding python3-pycuda: fails to install with python 3.7 as a supported 
python 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.)


-- 
903826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-pycuda
Version: 2017.1.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: block 902788 with -1 

Hi,

during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.

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

  Selecting previously unselected package python3-pycuda.
  (Reading database ... 
(Reading database ... 13293 files and directories currently installed.)
  Preparing to unpack .../python3-pycuda_2017.1.1-2_amd64.deb ...
  Unpacking python3-pycuda (2017.1.1-2) ...
  Setting up python3-pycuda (2017.1.1-2) ...
File "/usr/lib/python3/dist-packages/pycuda/gpuarray.py", line 230
  def set(self, ary, async=False, stream=None):
 ^
  SyntaxError: invalid syntax
  
  dpkg: error processing package python3-pycuda (--configure):
   installed python3-pycuda package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   python3-pycuda


async has become a reserved keyword in 3.7


cheers,

Andreas


python3-pycuda_2017.1.1-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: pycuda
Source-Version: 2018.1.1-1

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

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

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

Debian distribution maintenance software
pp.
Tomasz Rybak  (supplier of updated pycuda package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 31 Oct 2018 18:59:56 +0100
Source: pycuda
Binary: python3-pycuda python3-pycuda-dbg python-pycuda python-pycuda-dbg 
python-pycuda-doc
Architecture: source amd64 all
Version: 2018.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Tomasz Rybak 
Description:
 python-pycuda - Python module to access Nvidia‘s CUDA parallel computation API
 python-pycuda-dbg - Python module to access Nvidia‘s CUDA API (debug 
extensions)
 python-pycuda-doc - module to access Nvidia‘s CUDA computation API 
(documentation)
 python3-pycuda - Python 3 module to access Nvidia‘s CUDA parallel computation 
API
 python3-pycuda-dbg - Python 3 module to access Nvidia‘s CUDA API (debug 
extensions)
Closes: 903826
Changes:
 pycuda (2018.1.1-1) unstable; urgency=medium
 .
   [ Andreas Beckmann ]
   * Put package under maintenance by the Debian NVIDIA Maintainers team, move
 Tomasz to Uploaders.
   * Switch Vcs-* URLs to salsa.debian.org.
 .
   [ Tomasz Rybak ]
   * New upstream release (Closes: #903826).
   * Add Rules-Requires-Root to d/control.
   * Update d/copyright links to use https protocol.
   * Add disclaimer to d/copyright describing why PyCUDA is in contrib.
   * Reorder d/control putting Python 3 packages first.
   * Remove unnecessary X-Python{,3}-Version fields.
   * Update Standards-Version to 4.2.1; no changes necessary.
   * Set compatibility level to 11
 * Point python-pycuda-doc.doc-base to main package's doc directory.
Checksums-Sha1:
 0c8c9639464e65e71ff828448d31b17d3ddc2dce 2715 pycuda_2018.1.1-1.dsc
 60478425f2d636d58c38ca88a392a1bab72c48f8 184764 pycuda_2018.1.1.orig.tar.xz
 af83a45cc3606dcf013f9a27dbe88ffb6eb18734 10568 pycuda_2018.1.1-1.debian.tar.xz
 8d5bab2854f2cb1e9a7e6419e1ba425dabf68548 13772 
pycuda_2018.1.1-1_amd64.buildinfo
 d54ef22e204b0f76da4eb4d05899cd92d39b2ed0 6246452 
python-pycuda-dbg_2018.1.1-1_amd64.deb
 809586db8023fc761bdb38c2ace482072992d827 121888 
python-pycuda-doc_2018.1.1-1_all.deb
 9c0bca2a1c10ed63872d1c4c7bc515d817430108 311780 
python-pycuda_2018.1.1-

Bug#912464: icedtea-netx should depend on default-jre | java*-runtime

[Adrian Bunk]

Package: icedtea-netx
Version: 1.7.1-1
Severity: serious

It sounds wrong that icedtea-netx no longer has any JRE dependency.

Bug#912466: jaxb-api FTBFS with OpenJDK 11

[Adrian Bunk]

Source: jaxb-api
Version: 2.3.0-2
Severity: serious
Tags: ftbfs

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

...
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/1st/jaxb-api-2.3.0/jaxb-api/src/main/java/javax/xml/bind/attachment/AttachmentMarshaller.java:[43,24]
 package javax.activation does not exist
[ERROR] 
/build/1st/jaxb-api-2.3.0/jaxb-api/src/main/java/javax/xml/bind/attachment/AttachmentMarshaller.java:[125,46]
 cannot find symbol
  symbol:   class DataHandler
  location: class javax.xml.bind.attachment.AttachmentMarshaller
[ERROR] 
/build/1st/jaxb-api-2.3.0/jaxb-api/src/main/java/javax/xml/bind/attachment/AttachmentMarshaller.java:[214,48]
 cannot find symbol
  symbol:   class DataHandler
  location: class javax.xml.bind.attachment.AttachmentMarshaller
[ERROR] 
/build/1st/jaxb-api-2.3.0/jaxb-api/src/main/java/javax/xml/bind/attachment/AttachmentUnmarshaller.java:[43,24]
 package javax.activation does not exist
[ERROR] 
/build/1st/jaxb-api-2.3.0/jaxb-api/src/main/java/javax/xml/bind/attachment/AttachmentUnmarshaller.java:[131,20]
 cannot find symbol
  symbol:   class DataHandler
  location: class javax.xml.bind.attachment.AttachmentUnmarshaller
[ERROR] 
/build/1st/jaxb-api-2.3.0/jaxb-api/src/main/java/javax/xml/bind/annotation/XmlInlineBinaryData.java:[52,24]
 package javax.activation does not exist
[ERROR] 
/build/1st/jaxb-api-2.3.0/jaxb-api/src/main/java/javax/xml/bind/annotation/XmlAttachmentRef.java:[43,24]
 package javax.activation does not exist
[INFO] 7 errors 
[INFO] -
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Java Architecture for XML Binding 2.3.0  SUCCESS [  0.002 s]
[INFO] jaxb-api 2.3.0 . FAILURE [  4.549 s]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 5.616 s
[INFO] Finished at: 2019-12-03T14:55:31-12:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (base-compile) on 
project jaxb-api: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/jaxb-api-2.3.0/jaxb-api/src/main/java/javax/xml/bind/attachment/AttachmentMarshaller.java:[43,24]
 package javax.activation does not exist
[ERROR] 
/build/1st/jaxb-api-2.3.0/jaxb-api/src/main/java/javax/xml/bind/attachment/AttachmentMarshaller.java:[125,46]
 cannot find symbol
[ERROR]   symbol:   class DataHandler
[ERROR]   location: class javax.xml.bind.attachment.AttachmentMarshaller
[ERROR] 
/build/1st/jaxb-api-2.3.0/jaxb-api/src/main/java/javax/xml/bind/attachment/AttachmentMarshaller.java:[214,48]
 cannot find symbol
[ERROR]   symbol:   class DataHandler
[ERROR]   location: class javax.xml.bind.attachment.AttachmentMarshaller
[ERROR] 
/build/1st/jaxb-api-2.3.0/jaxb-api/src/main/java/javax/xml/bind/attachment/AttachmentUnmarshaller.java:[43,24]
 package javax.activation does not exist
[ERROR] 
/build/1st/jaxb-api-2.3.0/jaxb-api/src/main/java/javax/xml/bind/attachment/AttachmentUnmarshaller.java:[131,20]
 cannot find symbol
[ERROR]   symbol:   class DataHandler
[ERROR]   location: class javax.xml.bind.attachment.AttachmentUnmarshaller
[ERROR] 
/build/1st/jaxb-api-2.3.0/jaxb-api/src/main/java/javax/xml/bind/annotation/XmlInlineBinaryData.java:[52,24]
 package javax.activation does not exist
[ERROR] 
/build/1st/jaxb-api-2.3.0/jaxb-api/src/main/java/javax/xml/bind/annotation/XmlAttachmentRef.java:[43,24]
 package javax.activation does not exist
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :jaxb-api
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/jaxb-api-2.3.0 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/jaxb-api-2.3.0/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/jaxb-api-2.3.0/debian 
-Dmaven.repo.local=/build/1st/jaxb-api-2.3.0/debian/maven-repo --batch-mode 
package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
make: *** [debian/rules:4: build] Erro

Bug#912467: jasperreports FTBFS with OpenJDK 11

[Adrian Bunk]

Source: jasperreports
Version: 6.3.1-2
Severity: serious
Tags: ftbfs

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

...
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 27.382 s
[INFO] Finished at: 2019-12-03T14:59:05-12:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:compile (default-compile) 
on project jasperreports: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[35,22]
 package javax.xml.soap does not exist
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[36,22]
 package javax.xml.soap does not exist
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[37,22]
 package javax.xml.soap does not exist
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[38,22]
 package javax.xml.soap does not exist
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[39,22]
 package javax.xml.soap does not exist
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[40,22]
 package javax.xml.soap does not exist
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[41,22]
 package javax.xml.soap does not exist
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[42,22]
 package javax.xml.soap does not exist
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[43,22]
 package javax.xml.soap does not exist
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[44,22]
 package javax.xml.soap does not exist
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[45,22]
 package javax.xml.soap does not exist
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[46,22]
 package javax.xml.soap does not exist
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[47,22]
 package javax.xml.soap does not exist
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[97,17]
 cannot find symbol
[ERROR]   symbol:   class SOAPFactory
[ERROR]   location: class net.sf.jasperreports.olap.xmla.JRXmlaQueryExecuter
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[98,17]
 cannot find symbol
[ERROR]   symbol:   class SOAPConnection
[ERROR]   location: class net.sf.jasperreports.olap.xmla.JRXmlaQueryExecuter
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[215,19]
 cannot find symbol
[ERROR]   symbol:   class SOAPConnection
[ERROR]   location: class net.sf.jasperreports.olap.xmla.JRXmlaQueryExecuter
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[232,19]
 cannot find symbol
[ERROR]   symbol:   class SOAPMessage
[ERROR]   location: class net.sf.jasperreports.olap.xmla.JRXmlaQueryExecuter
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[299,41]
 cannot find symbol
[ERROR]   symbol:   class SOAPEnvelope
[ERROR]   location: class net.sf.jasperreports.olap.xmla.JRXmlaQueryExecuter
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[299,64]
 cannot find symbol
[ERROR]   symbol:   class SOAPElement
[ERROR]   location: class net.sf.jasperreports.olap.xmla.JRXmlaQueryExecuter
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[299,154]
 cannot find symbol
[ERROR]   symbol:   class SOAPException
[ERROR]   location: class net.sf.jasperreports.olap.xmla.JRXmlaQueryExecuter
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[326,44]
 cannot find symbol
[ERROR]   symbol:   class SOAPMessage
[ERROR]   location: class net.sf.jasperreports.olap.xmla.JRXmlaQueryExecuter
[ERROR] 
/build/1st/jasperreports-6.3.1/jasperreports/src/net/sf/jasperreports/olap/xmla/JRXmlaQueryExecuter.java:[326,19]
 cannot find symbol
[ERROR]   symb

Bug#906871: xul-ext-flashblock no longer works with firefox-esr 60

[Moritz Mühlenhoff]

On Tue, Aug 21, 2018 at 09:37:01PM +0300, Adrian Bunk wrote:
> Package: xul-ext-flashblock
> Version: 1.5.20-2
> Severity: serious
> 
> XUL addons are no longer supported.

Seems dead upstream, let's remove?

Cheers,
Moritz

Bug#912468: java3d FTBFS with OpenJDK 11

[Adrian Bunk]

Source: java3d
Version: 1.5.2+dfsg-15
Severity: serious
Tags: ftbfs

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

...
[javac] 
/build/1st/java3d-1.5.2+dfsg/j3d-core-utils/src/classes/share/com/sun/j3d/utils/applet/JMainFrame.java:292:
 error: cannot find symbol
[javac] return new sun.applet.AppletAudioClip( url );
[javac]  ^
[javac]   symbol:   class AppletAudioClip
[javac]   location: package sun.applet
[javac] 
/build/1st/java3d-1.5.2+dfsg/j3d-core-utils/src/classes/share/com/sun/j3d/utils/applet/MainFrame.java:341:
 error: cannot find symbol
[javac] return new sun.applet.AppletAudioClip( url );
[javac]  ^
[javac]   symbol:   class AppletAudioClip
[javac]   location: package sun.applet

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

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 20:52:30 +
with message-id 
and subject line Bug#899501: fixed in fcitx-chewing 0.2.3-1
has caused the Debian Bug report #899501,
regarding fcitx-chewing: Invalid maintainer address 
pkg-ime-de...@lists.alioth.debian.org
to be marked as done.

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

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


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

Dear uploader of fcitx-chewing,

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

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

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

Your options:

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

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

  More information about the new service can be found here:
  

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


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

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

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

Regards,

Christoph and some alioth-lists maintainers


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: fcitx-chewing
Source-Version: 0.2.3-1

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated fcitx-chewing package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 31 Oct 2018 16:06:23 -0400
Source: fcitx-chewing
Binary: fcitx-chewing
Architecture: source
Version: 0.2.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team 
Changed-By: Boyuan Yang 
Description:
 fcitx-chewing - Fcitx wrapper for Chewing library
Closes: 899501
Changes:
 fcitx-chewing (0.2.3-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release.
   * Refresh packaging instructions.
 + d/control: Update maintainer email address (Closes: #899501).
 + Use debhelper compat v11.
 + d/rules: bump standards-version to 4.2.1.
 + d/rules: enable full hardening.
 + d/copyright: refresh information.
 + d/control: use GitLab as homepage.
 + d/control: use canonical Vcs URL.
 + d/control: bump fcitx version requirement.
   * d/watch: point to download.fcitx-im.org.
   * d/control: Mark fcitx-chewing as Multi-Arch: same.
Checksums-Sha1:
 abfdc146ada3c39ec3ce072f4d853880eaef667d 2089 fcitx-chewing_0.2.3-1.dsc
 5488ff86405aae4d2cf76739fd5ede1e14a861d1 19804 fcitx-chewing_0.2.3.orig.tar.xz
 c45071eb4370662a8c1f1f12261324b7db28efae 2868 
fcitx-chewing_0.2.3-1.debian.tar.xz
 6e1b8dac0105b885e1f91bf573c74565cb73064d 8069 
fcitx-chewing_0.2.3-1_amd64.build

Bug#911686: marked as done (wtf-peewee FTBFS: AttributeError: 'ModelSelect' object has no attribute 'model_class')

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 21:56:48 +0100
with message-id <20181031205648.ga1...@msg.df7cb.de>
and subject line wtf-peewee_3.0.0+dfsg-1_source.changes ACCEPTED into unstable 
(fwd)
has caused the Debian Bug report #911686,
regarding wtf-peewee FTBFS: AttributeError: 'ModelSelect' object has no 
attribute 'model_class'
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.)


-- 
911686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: wtf-peewee
Version: 0.2.6+dfsg-2
Severity: serious
Tags: ftbfs

wtf-peewee fails to build from source in unstable for multiple
architectures, e.g. i386:

https://tests.reproducible-builds.org/debian/rbuild/unstable/i386/wtf-peewee_0.2.6+dfsg-2.rbuild.log.gz

| ERROR: test_hidden_field_none (wtfpeewee.tests.WTFPeeweeTestCase)
| --
| Traceback (most recent call last):
|   File "/build/1st/wtf-peewee-0.2.6+dfsg/wtfpeewee/tests.py", line 479, in 
test_hidden_field_none
| 'blog': '',
|   File "/usr/lib/python2.7/dist-packages/wtforms/form.py", line 212, in 
__call__
| return type.__call__(cls, *args, **kwargs)
|   File "/usr/lib/python2.7/dist-packages/wtforms/form.py", line 272, in 
__init__
| super(Form, self).__init__(self._unbound_fields, meta=meta_obj, 
prefix=prefix)
|   File "/usr/lib/python2.7/dist-packages/wtforms/form.py", line 52, in 
__init__
| field = meta.bind_field(self, unbound_field, options)
|   File "/usr/lib/python2.7/dist-packages/wtforms/meta.py", line 27, in 
bind_field
| return unbound_field.bind(form=form, **options)
|   File "/usr/lib/python2.7/dist-packages/wtforms/fields/core.py", line 353, 
in bind
| return self.field_class(*self.args, **kw)
|   File "/build/1st/wtf-peewee-0.2.6+dfsg/wtfpeewee/fields.py", line 319, in 
__init__
| self.model = query.model_class
| AttributeError: 'ModelSelect' object has no attribute 'model_class'
| 
| --
| Ran 15 tests in 0.055s
| 
| FAILED (errors=7)
| E: pybuild pybuild:338: test: plugin distutils failed with: exit code=2: 
python2.7 setup.py test
| dh_auto_test: pybuild --test -i python{version} -p 2.7 returned exit code 13
| make: *** [debian/rules:5: build] Error 25
| dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

Helmut
--- End Message ---
--- Begin Message ---
Version: 3.0.0+dfsg-1

Format: 1.8
Date: Tue, 30 Oct 2018 22:12:17 +0100
Source: wtf-peewee
Binary: python-wtf-peewee python3-wtf-peewee
Architecture: source
Version: 3.0.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Christoph Berg 
Description:
 python-wtf-peewee - WTForms integration for peewee models (Python 2)
 python3-wtf-peewee - WTForms integration for peewee models (Python 3)
Changes:
 wtf-peewee (3.0.0+dfsg-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/watch: Use https protocol
 .
   [ Christoph Berg ]
   * New upstream version.--- End Message ---

Bug#912470: jmdns FTBFS with OpenJDK 11

[Adrian Bunk]

Source: jmdns
Version: 3.5.4-1
Severity: serious
Tags: ftbfs

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

...
[INFO] Compiling 57 source files to /build/1st/jmdns-3.5.4/target/classes
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/1st/jmdns-3.5.4/src/main/java/javax/jmdns/impl/DNSOutgoing.java:[56,14] 
writeBytes(byte[]) in javax.jmdns.impl.DNSOutgoing.MessageOutputStream cannot 
override writeBytes(byte[]) in java.io.ByteArrayOutputStream
  attempting to assign weaker access privileges; was public
[INFO] 1 error

Bug#912069: flask-wtf FTBFS: FAIL: test_i18n_enabled (tests.test_i18n.TestI18NCase)

[Christoph Berg]

Re: Adrian Bunk 2018-10-27 
<154067546369.20678.16027981767936779592.reportbug@localhost>
> Some recent change in unstable makes flask-wtf FTBFS:
> Traceback (most recent call last):
>   File 
> "/build/1st/flask-wtf-0.14.2/.pybuild/cpython2_2.7_flaskext.wtf/build/tests/test_i18n.py",
>  line 32, in test_i18n_enabled
> assert '\u8be5\u5b57\u6bb5\u662f' in to_unicode(response.data)

I recently updated wtforms which is probably the culprit here. The
unicode string it is looking for is "该字段是" which is the
translation of "This field is required." (see tests/test_i18n.py).
The string is still in wtforms' wtforms/locale/zh/LC_MESSAGES/wtforms.po
file, though.

It looks like translations are busted:

foo = response.data
print (foo)
assert '\u8be5\u5b57\u6bb5\u662f' in to_unicode(foo)

AssertionError:
 >> begin captured stdout << -







{'name': [u'This field is required.']}



Name









- >> end captured stdout << --

Christoph

Bug#912473: jython FTBFS with OpenJDK 11

[Adrian Bunk]

Source: jython
Version: 2.7.1+repack-4
Severity: serious
Tags: ftbfs

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

...
compile:
[javac] /build/1st/jython-2.7.1+repack/build.xml:486: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Compiling 882 source files to 
/build/1st/jython-2.7.1+repack/build/classes
[javac] 
/build/1st/jython-2.7.1+repack/src/org/python/compiler/Module.java:21: error: 
package javax.xml.bind does not exist
[javac] import javax.xml.bind.DatatypeConverter;
[javac]  ^
[javac] 
/build/1st/jython-2.7.1+repack/src/org/python/core/BytecodeLoader.java:11: 
error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.DatatypeConverter;
[javac]  ^
 ...
[javac] 
/build/1st/jython-2.7.1+repack/src/org/python/compiler/Module.java:867: error: 
cannot find symbol
[javac] String code_str = 
DatatypeConverter.printBase64Binary(bo.toByteArray());
[javac]   ^
[javac]   symbol:   variable DatatypeConverter
[javac]   location: class Module
...
[javac] 
/build/1st/jython-2.7.1+repack/src/org/python/core/BytecodeLoader.java:82: 
error: cannot find symbol
[javac] byte[] b = DatatypeConverter.parseBase64Binary(code_str);
[javac]^
[javac]   symbol:   variable DatatypeConverter
[javac]   location: class BytecodeLoader

Bug#912474: junit4 FTBFS with OpenJDK 11

[Adrian Bunk]

Source: junit4
Version: 4.12-7
Severity: serious
Tags: ftbfs

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

...
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 14.974 s
[INFO] Finished at: 2018-10-31T09:30:32-12:00
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.8.0:testCompile 
(default-testCompile) on project junit: Compilation failure: Compilation 
failure: 
[ERROR] 
/build/1st/junit4-4.12/src/test/java/org/junit/tests/running/core/MainRunner.java:[194,8]
 error: method does not override or implement a method from a supertype
[ERROR] 
/build/1st/junit4-4.12/src/test/java/org/junit/tests/running/core/MainRunner.java:[196,60]
 error: cannot find symbol
[ERROR]   symbol: method checkTopLevelWindow(Object)
[ERROR] 
/build/1st/junit4-4.12/src/test/java/org/junit/tests/running/core/MainRunner.java:[196,114]
 error: cannot find symbol
[ERROR]   symbol:   method checkTopLevelWindow(Object)
[ERROR]   location: variable originalSecurityManager of type SecurityManager
[ERROR] 
/build/1st/junit4-4.12/src/test/java/org/junit/tests/running/core/MainRunner.java:[206,8]
 error: method does not override or implement a method from a supertype
[ERROR] 
/build/1st/junit4-4.12/src/test/java/org/junit/tests/running/core/MainRunner.java:[209,39]
 error: cannot find symbol
[ERROR]   symbol:   method checkSystemClipboardAccess()
[ERROR]   location: variable originalSecurityManager of type SecurityManager
[ERROR] 
/build/1st/junit4-4.12/src/test/java/org/junit/tests/running/core/MainRunner.java:[213,8]
 error: method does not override or implement a method from a supertype
[ERROR] 
/build/1st/junit4-4.12/src/test/java/org/junit/tests/running/core/MainRunner.java:[216,39]
 error: cannot find symbol
[ERROR]   symbol:   method checkAwtEventQueueAccess()
[ERROR]   location: variable originalSecurityManager of type SecurityManager
[ERROR] 
/build/1st/junit4-4.12/src/test/java/org/junit/tests/running/core/MainRunner.java:[241,8]
 error: method does not override or implement a method from a supertype
[ERROR] 
/build/1st/junit4-4.12/src/test/java/org/junit/tests/running/core/MainRunner.java:[244,39]
 error: cannot find symbol
[ERROR]   symbol:   method checkMemberAccess(Class,int)
[ERROR]   location: variable originalSecurityManager of type SecurityManager
[ERROR]   where CAP#1 is a fresh type-variable:
[ERROR] CAP#1 extends Object from capture of ?
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/junit4-4.12 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/junit4-4.12/debian 
-Dmaven.repo.local=/build/1st/junit4-4.12/debian/maven-repo --batch-mode 
package javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true 
-Dlocale=en_US returned exit code 1
make: *** [debian/rules:4: build] Error 2

Bug#912434: marked as done (devscripts-el Depends: elpa-devscripts-el but it is not installable)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 21:50:10 +
with message-id 
and subject line Bug#912434: fixed in devscripts-el 40.3
has caused the Debian Bug report #912434,
regarding devscripts-el Depends: elpa-devscripts-el but it is not installable
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.)


-- 
912434: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912434
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: devscripts-el
Version: 40.2
Severity: serious

The following packages have unmet dependencies:
 devscripts-el : Depends: elpa-devscripts-el but it is not installable
--- End Message ---
--- Begin Message ---
Source: devscripts-el
Source-Version: 40.3

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

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

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

Debian distribution maintenance software
pp.
David Bremner  (supplier of updated devscripts-el 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, 31 Oct 2018 18:09:11 -0300
Source: devscripts-el
Binary: elpa-devscripts devscripts-el
Architecture: source
Version: 40.3
Distribution: unstable
Urgency: medium
Maintainer: Debian Emacsen team 
Changed-By: David Bremner 
Description:
 devscripts-el - Transition package, devscripts-el to elpa-devscripts
 elpa-devscripts - Emacs wrappers for the commands in devscripts
Closes: 912434
Changes:
 devscripts-el (40.3) unstable; urgency=medium
 .
   * Bug fix: "devscripts-el Depends: elpa-devscripts-el but it is not
 installable", thanks to Adrian Bunk (Closes: #912434).
Checksums-Sha1:
 48e6a92ebf2ecc2c7c0a9fd611273e553480f9c3 1625 devscripts-el_40.3.dsc
 ba9a7ab4f2ccf3404b8d5a9e270d0879ec81d2b6 9344 devscripts-el_40.3.tar.xz
Checksums-Sha256:
 bc9b89055576239ca9f0c17fbfeef102cfa1659dfe4a509d14dd51cae24ff123 1625 
devscripts-el_40.3.dsc
 8f0056d82a1fcafe52deb7cba513db54bc2a707a7f9bea3a9994e016baf1eb8b 9344 
devscripts-el_40.3.tar.xz
Files:
 070717d30920ef64dbdfb9e4c9f64e67 1625 lisp optional devscripts-el_40.3.dsc
 e49bf2dc2cef6f5fa1f3650838f8 9344 lisp optional devscripts-el_40.3.tar.xz

-BEGIN PGP SIGNATURE-

iQGzBAEBCAAdFiEE3VS2dnyDRXKVCQCp8gKXHaSnniwFAlvaHO0ACgkQ8gKXHaSn
niyqawwAiQ28CQ/zShqqzZ9cZom2yo3r/u1hwjCuamyG21+C8nG/k4sBYkCyQMAG
w5oeCr07JqeVEandpye8911zssZvX49cX7gcupTx7Vks6eA23IzEcnPHcImOELvk
lfXsfWba0uip15mQVLxXWimKGyAklDQze2FFMN8FvK4XqL0XtsxnuDqDwOapMgxN
neFzDejgd+uw03cyEpCiUuy7a0ybY+xW2zLn9Fv+nVrd9kceuDso3Ida6RTkLeg5
1cXvGBQPjllKL8h8qlYH+TuKr/LaBxHLzqkthgJ8FbnqalCvMGdjKyzN8wM51IpA
KtLZO7+WH40LhRBFId5cLTMcGfU1+6zPJd+a3q7ZCRxVxRDYS1YwbhPPzIYG4ExH
zJoH/lMD+Szrm8jCcYzIgtlZBcvg0Akallb/Nwim7zh2y/CPTIKlG/tRXUuOynni
ZB2+xYQRvOOFQhUxfUC66nJOhohpGsiPjCMPYmlWwUy1I8dhAEBwNaksJ563tzyu
z4wp2W3q
=ImOO
-END PGP SIGNATURE End Message ---

Bug#912435: marked as done (getmail FTBFS: cannot stat 'debian/getmail/usr/share/doc/getmail-*': No such file or directory)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 21:54:23 +
with message-id 
and subject line Bug#912435: fixed in getmail 5.7-3
has caused the Debian Bug report #912435,
regarding getmail FTBFS: cannot stat 'debian/getmail/usr/share/doc/getmail-*': 
No such file or 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.)


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

https://buildd.debian.org/status/fetch.php?pkg=getmail&arch=all&ver=5.7-1&stamp=1540940824&raw=0

...
dh_install
# Move documentation files created by setup.py
# to Debian style versionless directory
mv debian/getmail/usr/share/doc/getmail-* \
debian/getmail/usr/share/doc/getmail
mv: cannot stat 'debian/getmail/usr/share/doc/getmail-*': No such file or 
directory
make[1]: *** [debian/rules:15: override_dh_install] Error 1
--- End Message ---
--- Begin Message ---
Source: getmail
Source-Version: 5.7-3

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

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

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

Debian distribution maintenance software
pp.
Daniel Kahn Gillmor  (supplier of updated getmail 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 31 Oct 2018 17:38:18 -0400
Source: getmail
Binary: getmail getmail4
Architecture: source
Version: 5.7-3
Distribution: unstable
Urgency: medium
Maintainer: Osamu Aoki 
Changed-By: Daniel Kahn Gillmor 
Description:
 getmail- mail retriever with support for POP3, IMAP4 and SDPS
 getmail4   - transitional dummy package
Closes: 912435
Changes:
 getmail (5.7-3) unstable; urgency=medium
 .
   * use pybuild and python-all instead of python2 (Closes: #912435)
   * revert earlier buildd debugging
Checksums-Sha1:
 6eaa6546077ad3aaa0fcc2b21d33506378a99188 1334 getmail_5.7-3.dsc
 a1ce2b68f653cd17577c95da911eccefc4e0e7c1 8472 getmail_5.7-3.debian.tar.xz
 a0b72e262b3679e649c394d7695aaefa07b14889 6601 getmail_5.7-3_amd64.buildinfo
Checksums-Sha256:
 b509b1da6d343853390c980519edfb60880fe50e153dd85e2fdbc170b1fea9ce 1334 
getmail_5.7-3.dsc
 70ebc63de776ed90a9e4087edf9230aab1a697a23007437b26610542f59ad83b 8472 
getmail_5.7-3.debian.tar.xz
 358ef6b8e98aac5d384c040887727e88dc8861d934ab3cf8fca2aa20032389b0 6601 
getmail_5.7-3_amd64.buildinfo
Files:
 2317535beb3be61c07a6b311e4410629 1334 mail optional getmail_5.7-3.dsc
 aa1fcb66be25e60140c66d12b6171c8c 8472 mail optional getmail_5.7-3.debian.tar.xz
 8c432089e5f4d3d066868bb2a9d98314 6601 mail optional 
getmail_5.7-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQTTaP514aqS9uSbmdJsHx7ezFD6UwUCW9og9AAKCRBsHx7ezFD6
U60kAP9umuT/ZosNszVsQDHAnuUiHJis9gVvyyNfiRa/zlT0UAD8DnsP6a+c7clk
tUV+dep3XVuTFfbVGQNtxAJvSaGZWA4=
=d/NR
-END PGP SIGNATURE End Message ---

Bug#910031: marked as done (fuse3: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 23:07:36 +0100
with message-id 

and subject line Re: fuse3: Incomplete debian/copyright?
has caused the Debian Bug report #910031,
regarding fuse3: 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.)


-- 
910031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910031
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fuse3
Version: 3.2.4-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Laszlo Boszormenyi (GCS) , 
ftpmas...@debian.org

Hi,

I just ACCEPTed fuse3 from NEW but noticed it was missing attribution 
in debian/copyright for at least Sebastian Pipping, SUSE Linux, Tejun
Heo, etc.

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: fuse3
Source-Version: 3.2.6-1

It looks fixed in 3.2.6-1, as said in my previous comment.--- End Message ---

Bug#912476: libapache-poi-java FTBFS with OpenJDK 11

[Adrian Bunk]

Source: libapache-poi-java
Version: 3.12-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libapache-poi-java.html

...
compile-ooxml:
[javac] Compiling 384 source files to 
/build/1st/libapache-poi-java-3.12/build/ooxml-classes
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 6
[javac] warning: [options] source value 6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/libapache-poi-java-3.12/src/ooxml/java/org/apache/poi/poifs/crypt/dsig/services/TSPTimeStampService.java:45:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.DatatypeConverter;
[javac]  ^
[javac] 
/build/1st/libapache-poi-java-3.12/src/ooxml/java/org/apache/poi/xssf/usermodel/helpers/XSSFPaswordHelper.java:25:
 error: package javax.xml.bind does not exist
[javac] import javax.xml.bind.DatatypeConverter;
[javac]  ^
[javac] 
/build/1st/libapache-poi-java-3.12/src/ooxml/java/org/apache/poi/poifs/crypt/dsig/services/TSPTimeStampService.java:130:
 error: cannot find symbol
[javac] String encoding = 
DatatypeConverter.printBase64Binary(userPassword.getBytes(Charset.forName("iso-8859-1")));
[javac]   ^
[javac]   symbol:   variable DatatypeConverter
[javac]   location: class TSPTimeStampService
[javac] 
/build/1st/libapache-poi-java-3.12/src/ooxml/java/org/apache/poi/xssf/usermodel/helpers/XSSFPaswordHelper.java:72:
 error: cannot find symbol
[javac] cur.insertAttributeWithValue(getAttrName(prefix, 
"hashValue"), DatatypeConverter.printBase64Binary(hash));
[javac] 
   ^
[javac]   symbol:   variable DatatypeConverter
[javac]   location: class XSSFPaswordHelper
[javac] 
/build/1st/libapache-poi-java-3.12/src/ooxml/java/org/apache/poi/xssf/usermodel/helpers/XSSFPaswordHelper.java:73:
 error: cannot find symbol
[javac] cur.insertAttributeWithValue(getAttrName(prefix, 
"saltValue"), DatatypeConverter.printBase64Binary(salt));
[javac] 
   ^
[javac]   symbol:   variable DatatypeConverter
[javac]   location: class XSSFPaswordHelper
[javac] 
/build/1st/libapache-poi-java-3.12/src/ooxml/java/org/apache/poi/xssf/usermodel/helpers/XSSFPaswordHelper.java:111:
 error: cannot find symbol
[javac] byte hash1[] = 
DatatypeConverter.parseBase64Binary(hashVal);
[javac]^
[javac]   symbol:   variable DatatypeConverter
[javac]   location: class XSSFPaswordHelper
[javac] 
/build/1st/libapache-poi-java-3.12/src/ooxml/java/org/apache/poi/xssf/usermodel/helpers/XSSFPaswordHelper.java:113:
 error: cannot find symbol
[javac] byte salt[] = 
DatatypeConverter.parseBase64Binary(saltVal);
[javac]   ^
[javac]   symbol:   variable DatatypeConverter
[javac]   location: class XSSFPaswordHelper
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 7 errors
[javac] 4 warnings

BUILD FAILED
/build/1st/libapache-poi-java-3.12/build.xml:756: Compile failed; see the 
compiler error output for details.

Total time: 2 minutes 18 seconds
dh_auto_build: ant -propertyfile ./debian/ant.properties -Duser.name debian 
-Dversion.id=3.12 -DDSTAMP=20180725 jar maven-poms javadocs returned exit code 1
make[1]: *** [debian/rules:13: override_dh_auto_build] Error 2

Bug#912477: libcommons-collections4-java FTBFS with OpenJDK 11

[Adrian Bunk]

Source: libcommons-collections4-java
Version: 4.1-1
Severity: serious
Tags: ftbfs buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libcommons-collections4-java.html

...
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/1st/libcommons-collections4-java-4.1/src/test/java/org/apache/commons/collections4/collection/AbstractCollectionTest.java:[1088,36]
 reference to toArray is ambiguous
  both method toArray(T[]) in java.util.Collection and method 
toArray(java.util.function.IntFunction) in java.util.Collection match
[INFO] 1 error

Bug#912515: libcommons-collections3-java FTBFS with OpenJDK 11

[Adrian Bunk]

Source: libcommons-collections3-java
Version: 3.2.2-1
Severity: serious
Tags: ftbfs buster sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libcommons-collections3-java.html

...
compile.tests:
[mkdir] Created dir: 
/build/1st/libcommons-collections3-java-3.2.2/build/tests
[javac] /build/1st/libcommons-collections3-java-3.2.2/build.xml:273: 
warning: 'includeantruntime' was not set, defaulting to 
build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 203 source files to 
/build/1st/libcommons-collections3-java-3.2.2/build/tests
[javac] Using ant.build.javac.source 1.4 is no longer supported, switching 
to 6
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 6
[javac] warning: [options] source value 6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/libcommons-collections3-java-3.2.2/src/test/org/apache/commons/collections/collection/AbstractTestCollection.java:1119:
 error: reference to toArray is ambiguous
[javac] array = collection.toArray(null);
[javac]   ^
[javac]   both method toArray(T#1[]) in Collection and method 
toArray(IntFunction) in Collection match
[javac]   where T#1,T#2 are type-variables:
[javac] T#1 extends Object declared in method toArray(T#1[])
[javac] T#2 extends Object declared in method 
toArray(IntFunction)
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 1 error
[javac] 3 warnings

Bug#912516: libcommons-lang3-java FTBFS with OpenJDK 11

[Adrian Bunk]

Source: libcommons-lang3-java
Version: 3.8-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libcommons-lang3-java.html

...
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/1st/libcommons-lang3-java-3.8/src/test/java/org/apache/commons/lang3/concurrent/BasicThreadFactoryTest.java:[120,55]
 incompatible types: java.lang.Object cannot be converted to 
java.util.concurrent.ThreadFactory
[ERROR] 
/build/1st/libcommons-lang3-java-3.8/src/test/java/org/apache/commons/lang3/event/EventListenerSupportTest.java:[144,60]
 incompatible types: java.lang.Object cannot be converted to 
java.beans.VetoableChangeListener
[INFO] 2 errors 

Bug#848073: marked as done (python3-django-macaddress: Compatibility of django-macaddress with django 1.10 in stretch)

[Debian Bug Tracking System]

Your message dated Wed, 31 Oct 2018 17:58:10 -0500
with message-id <20181031225810.ucee6jmrxdtml...@powdarrmonkey.net>
and subject line Re: Bug#848073: python3-django-macaddress: Compatibility of 
django-macaddress with django 1.10 in stretch
has caused the Debian Bug report #848073,
regarding python3-django-macaddress: Compatibility of django-macaddress with 
django 1.10 in stretch
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.)


-- 
848073: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848073
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-django-macaddress
Version: 1.3.2-1
Severity: important
Tags: upstream

Dear Maintainer,

I recently installed python3-django environment in debian stretch/testing, 
which version is 1.10. 
When I tried to use python3-django-macaddress (an optionnal module : 
https://github.com/django-macaddress/django-macaddress/ ), the import of this 
module crashed on AttributeError: module 'django.db.models' has no attribute 
'SubfieldBase'.

After a rapid search, i can report that this bug has been fixed by this commit 
https://github.com/django-macaddress/django-macaddress/commit/7c4764e0e04588dbc1f3740603644b154450254d
 on the upstream version, which version number is 1.4.0.

But in debian stretch , the version is 1.3.2. I think that packaging the 1.4.0 
version would easily fix this problem.


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

Kernel: Linux 4.8.0-1-amd64 (SMP w/1 CPU core)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to fr_FR.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
Version: 1.5.0-1

Hi,

On Tue, Dec 13, 2016 at 07:56:00PM +0100, Gabriel Detraz wrote:
> I recently installed python3-django environment in debian stretch/testing, 
> which version is 1.10. 
> When I tried to use python3-django-macaddress (an optionnal module : 
> https://github.com/django-macaddress/django-macaddress/ ), the import of this 
> module crashed on AttributeError: module 'django.db.models' has no attribute 
> 'SubfieldBase'.
> 
> After a rapid search, i can report that this bug has been fixed by this 
> commit 
> https://github.com/django-macaddress/django-macaddress/commit/7c4764e0e04588dbc1f3740603644b154450254d
>  on the upstream version, which version number is 1.4.0.
> 
> But in debian stretch , the version is 1.3.2. I think that packaging the 
> 1.4.0 version would easily fix this problem.

This was fixed some while ago, but the bug wasn't properly closed. Closing
now.

Thanks,

-- 
Jonathan Wiltshire  j...@debian.org
Debian Developer http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51--- End Message ---

Bug#912437: openmpi-bin: Fails to upgrade: update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link /usr/bin/mpicc

[Axel Beckert]

Control: clone -1 -2
Control: reassign -2 mpich 3.3~b3-3
Control: retitle -2 mpich: Fails to upgrade: update-alternatives: error: 
/var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link 
/usr/bin/mpicc

Hi Alastair,

Alastair McKinstry wrote:
> I'm unable to reproduce this, and have no failures testing 3.1.2-6
> -> 3.1.3-1 upgrade.

Same for the mpich 3.3~b3-2 to 3.3~b3-3 upgrade (on the same machine).
Cloning the bug, as I assume that this needs to be applied to both
packages:

> (2) Some more handling needs to be added to cope with 'inheriting' a
> corrupt mpi alternatives.

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-|  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE

Processed: Re: Bug#912437: openmpi-bin: Fails to upgrade: update-alternatives: error: /var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link /usr/bin/mpicc

[Debian Bug Tracking System]

Processing control commands:

> clone -1 -2
Bug #912437 [openmpi-bin] openmpi-bin: Fails to upgrade: update-alternatives: 
error: /var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link 
/usr/bin/mpicc
Bug 912437 cloned as bug 912523
> reassign -2 mpich 3.3~b3-3
Bug #912523 [openmpi-bin] openmpi-bin: Fails to upgrade: update-alternatives: 
error: /var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link 
/usr/bin/mpicc
Bug reassigned from package 'openmpi-bin' to 'mpich'.
No longer marked as found in versions openmpi/3.1.3-1.
Ignoring request to alter fixed versions of bug #912523 to the same values 
previously set
Bug #912523 [mpich] openmpi-bin: Fails to upgrade: update-alternatives: error: 
/var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link 
/usr/bin/mpicc
Marked as found in versions mpich/3.3~b3-3.
> retitle -2 mpich: Fails to upgrade: update-alternatives: error: 
> /var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link 
> /usr/bin/mpicc
Bug #912523 [mpich] openmpi-bin: Fails to upgrade: update-alternatives: error: 
/var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link 
/usr/bin/mpicc
Changed Bug title to 'mpich: Fails to upgrade: update-alternatives: error: 
/var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link 
/usr/bin/mpicc' from 'openmpi-bin: Fails to upgrade: update-alternatives: 
error: /var/lib/dpkg/alternatives/mpi corrupt: slave link same as main link 
/usr/bin/mpicc'.

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

Bug#912459: marked as done (jaxe FTBFS with OpenJDK 11)

[Debian Bug Tracking System]

Your message dated Thu, 01 Nov 2018 00:34:45 +
with message-id 
and subject line Bug#912459: fixed in jaxe 3.5-10
has caused the Debian Bug report #912459,
regarding jaxe FTBFS with OpenJDK 11
to be marked as done.

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

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


-- 
912459: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912459
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jaxe
Version: 3.5-9
Severity: serious
Tags: ftbfs

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

...
[javac] /build/1st/jaxe-3.5/source/jaxe/JaxeTransferHandler.java:284: 
error: cannot find symbol
[javac] sm.checkSystemClipboardAccess();
[javac]   ^
[javac]   symbol:   method checkSystemClipboardAccess()
[javac]   location: variable sm of type SecurityManager
--- End Message ---
--- Begin Message ---
Source: jaxe
Source-Version: 3.5-10

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

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

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

Debian distribution maintenance software
pp.
Samuel Thibault  (supplier of updated jaxe 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, 01 Nov 2018 01:15:54 +0100
Source: jaxe
Binary: jaxe libjaxe-java libjaxe-java-doc
Architecture: source
Version: 3.5-10
Distribution: unstable
Urgency: medium
Maintainer: Samuel Thibault 
Changed-By: Samuel Thibault 
Description:
 jaxe   - JAva Xml Editor
 libjaxe-java - JAva Xml Editor - library
 libjaxe-java-doc - JAva Xml Editor - Library documentation
Closes: 912459
Changes:
 jaxe (3.5-10) unstable; urgency=medium
 .
   * control: Bump Standards-Version to 4.2.0 (no changes).
   * patches/openjdk11: Drop unused function which FTBFS (Closes: Bug#912459).
Checksums-Sha1:
 881ee3092c3292400bb8c138ba661a21d23621a8 2279 jaxe_3.5-10.dsc
 da8be8f6ac0a4944f198fccc6a03e449edcf9555 11540 jaxe_3.5-10.debian.tar.xz
Checksums-Sha256:
 ad9cd803a031e61127c17ffe7a521df230257363b176594f7e74e361af0cd32e 2279 
jaxe_3.5-10.dsc
 b581eb6b216c8e8eff93e6d60a7424cda7d60c07e5510042e9538bae02d3e7c6 11540 
jaxe_3.5-10.debian.tar.xz
Files:
 90bc3a0b95c65f0dd3e8d477476e323a 2279 java optional jaxe_3.5-10.dsc
 e1b3e292164720783b521e79b614679b 11540 java optional jaxe_3.5-10.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOjpdRkZg6GdhDKQnmWhJwc9WBHgFAlvaRi4ACgkQmWhJwc9W
BHgrxA/9Gr5j7gXdwZ1HddM43sbH/sMfkgcsggowHfXpLNJRnwruiETNl4MRP+CH
SIuYju26kzqrTx1HHQIuBkbhnXjyXC4lSUjbCrdrjehZsrZnE9TfSoIznYaoadgi
LnKJoXDC8RAiMMroisFMIdgGdtdD9gHKd9PU7aQxbXALoDHJV6zmMsedbJLoUPjb
2+MMhinrYA7dB8tOZ3tX20XqlRqbFFEStIdt4kN3MiOJRT/UhMq1a/i/Zl/yQ2fr
96zZ2tUyUwvH6ISnlt38ZXQF6Oh7iw/BkNpg+VEQslCmOLbzIF06E0rCW1+PKoYG
W7RjDrB6mgJP/sUF0OnYee100w71Nr1WZXVSHuLiXcLWmLuszVSKiq+nEdxl/RiK
GcvV8F+kIX6MfmyJvxht6mZ8bdBNQE/XdgOkxHurJ7DWlAh80mLbvKFtEK3y+vtr
ur5VuJ3PLPqL782o/xavonwgIUViqJ6sr1QFk4k9IuvZ2fXVE/Pe5K7oX6JYtXzL
Bt8V+HkpYiHQYqsa4oxSUjOKpwMx9U5JyKkaIOPsHjof+kE0gZffzHpmioVUvB4N
J/1g8I8uR3gEirKtpDQFMcgpJyPxT53YxB/ygpAKaCAXRZfaonFbh8xEw7S4JG7B
Az6Da1f7UJaD/tyIg8NEZnIZ5Nvvhw+1Tm0eWMRk3sZvaSzXt50=
=u2eR
-END PGP SIGNATURE End Message ---

Bug#908327: marked as done (curl: CVE-2018-14618: NTLM password overflow via integer overflow)

[Debian Bug Tracking System]

Your message dated Thu, 01 Nov 2018 00:34:23 +
with message-id 
and subject line Bug#908327: fixed in curl 7.62.0-1
has caused the Debian Bug report #908327,
regarding curl: CVE-2018-14618: NTLM password overflow via integer overflow
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.)


-- 
908327: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908327
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: curl
Version: 7.61.0-1
Severity: serious
Tags: security upstream
Justification: otherwise regression from stable for security fix
Forwarded: https://github.com/curl/curl/issues/2756
Control: found -1 7.52.1-1
Control: fixed -1 7.52.1-5+deb9u7

Hi,

The following vulnerability was published for curl. Justification for
the severity, is that it would otherwise imply a regression from
stable for a security fix.

CVE-2018-14618[0]:
| curl before version 7.61.1 is vulnerable to a buffer overrun in the
| NTLM authentication code. The internal function
| Curl_ntlm_core_mk_nt_hash multiplies the length of the password by two
| (SUM) to figure out how large temporary storage area to allocate from
| the heap. The length value is then subsequently used to iterate over
| the password and generate output into the allocated storage buffer. On
| systems with a 32 bit size_t, the math to calculate SUM triggers an
| integer overflow when the password length exceeds 2GB (2^31 bytes).
| This integer overflow usually causes a very small buffer to actually
| get allocated instead of the intended very huge one, making the use of
| that buffer end up in a heap buffer overflow. (This bug is almost
| identical to CVE-2017-8816.)

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-14618
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14618
[1] https://curl.haxx.se/docs/CVE-2018-14618.html
[2] https://github.com/curl/curl/issues/2756
[3] https://github.com/curl/curl/commit/57d299a499155d4b327e341c6024e293b0418243

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: curl
Source-Version: 7.62.0-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 31 Oct 2018 22:42:44 +
Source: curl
Binary: curl libcurl4 libcurl3-gnutls libcurl3-nss libcurl4-openssl-dev 
libcurl4-gnutls-dev libcurl4-nss-dev libcurl4-doc
Architecture: source
Version: 7.62.0-1
Distribution: unstable
Urgency: medium
Maintainer: Alessandro Ghedini 
Changed-By: Alessandro Ghedini 
Description:
 curl   - command line tool for transferring data with URL syntax
 libcurl3-gnutls - easy-to-use client-side URL transfer library (GnuTLS flavour)
 libcurl3-nss - easy-to-use client-side URL transfer library (NSS flavour)
 libcurl4   - easy-to-use client-side URL transfer library (OpenSSL flavour)
 libcurl4-doc - documentation for libcurl
 libcurl4-gnutls-dev - development files and documentation for libcurl (GnuTLS 
flavour)
 libcurl4-nss-dev - development files and documentation for libcurl (NSS 
flavour)
 libcurl4-openssl-dev - development files and documentation for libcurl 
(OpenSSL flavour)
Closes: 908327 911333
Changes:
 curl (7.62.0-1) unstable; urgency=medium
 .
   * New upstream release
 + Fix NTLM password overflow via integer overflow as per CVE-2018-14618
   (Closes: #908327) https://curl.haxx.se/docs/CVE-2018-14618.html
 + Fix SASL password overflow via integer overflow as per CVE-2018-16839
   https://curl.haxx.se/docs/CVE-2018-16839.html
 + Fix use-after-free in handle close as per CVE-2018-16840
   https://curl.haxx.se/docs/CVE-2018-16840.html
 + Fix warning message out-of-buffer read as per CVE-2018-16842
   https://curl.haxx.se/docs/CV

Bug#912436: marked as done (xandikos FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 0xce in position 447: ordinal not in range(128))

[Debian Bug Tracking System]

Your message dated Thu, 01 Nov 2018 00:38:09 +
with message-id 
and subject line Bug#912436: fixed in xandikos 0.0.10-2
has caused the Debian Bug report #912436,
regarding xandikos FTBFS: UnicodeDecodeError: 'ascii' codec can't decode byte 
0xce in position 447: ordinal not in range(128)
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=xandikos&arch=all&ver=0.0.10-1&stamp=1540956480&raw=0

...
dh clean --with python3 --buildsystem=pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py clean 
running clean
removing '/<>/.pybuild/cpython3_3.7/build' (and everything under 
it)
'build/bdist.linux-amd64' does not exist -- can't clean it
'build/scripts-3.7' does not exist -- can't clean it
I: pybuild base:217: python3.6 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 35, in 
long_description = f.read()
  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 0xce in position 447: 
ordinal not in range(128)
E: pybuild pybuild:338: clean: plugin distutils failed with: exit code=1: 
python3.6 setup.py clean 
dh_auto_clean: pybuild --clean -i python{version} -p "3.7 3.6" returned exit 
code 13
make: *** [debian/rules:4: clean] Error 25
--- End Message ---
--- Begin Message ---
Source: xandikos
Source-Version: 0.0.10-2

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

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

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

Debian distribution maintenance software
pp.
Jelmer Vernooij  (supplier of updated xandikos 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, 01 Nov 2018 00:06:12 +
Source: xandikos
Binary: xandikos
Architecture: source
Version: 0.0.10-2
Distribution: unstable
Urgency: medium
Maintainer: Jelmer Vernooij 
Changed-By: Jelmer Vernooij 
Description:
 xandikos   - Git-backed CalDAV/CardDAV server
Closes: 912436
Changes:
 xandikos (0.0.10-2) unstable; urgency=medium
 .
   * Read README.rst with encoding utf-8. Closes: #912436
Checksums-Sha1:
 000977874397ad02b4525b6aa92cfe45c50d82aa 2045 xandikos_0.0.10-2.dsc
 3f6650833aed6a2bcd9ab70cb79116c5391688e7 32616 xandikos_0.0.10-2.debian.tar.xz
 77ee6d1a7ca4e3affbd72b821777a44bf3703379 6487 
xandikos_0.0.10-2_source.buildinfo
Checksums-Sha256:
 5ba112fafda1644299d004822bf3a7d04413b45e9e4c40d246c79255258c4025 2045 
xandikos_0.0.10-2.dsc
 dc4269501b5e9535dd9a1754f9459e2ad631452598399c0d6dda9f67340b66f1 32616 
xandikos_0.0.10-2.debian.tar.xz
 fc77752ceca11e4260185b51a6eccbce917ac2b19846a50019597afe48d25cbc 6487 
xandikos_0.0.10-2_source.buildinfo
Files:
 ddf7e57990a171671dcc0a8e2dfbe7a2 2045 python optional xandikos_0.0.10-2.dsc
 c90e7c1f95cbf1db25122bb9d9a3cc8a 32616 python optional 
xandikos_0.0.10-2.debian.tar.xz
 e53e37bd2176d4a41790e72ffe5b2e18 6487 python optional 
xandikos_0.0.10-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAlvaQ7ISHGplbG1lckBk
ZWJpYW4ub3JnAAoJEFecFg1MniPoz3wP/2jQKRkcoI6zzCBQEejL2j5NNdGJxk2w
HfhBS8JsFMVbqH86p4GFxk9FuYmBhWvGLf+qfi8M6uBkgikDt+rgBJbfI2nqtrx1
L4J9CTM78Z8f/Nz/VW5/SLrtqyMtkzU9IJUdpbeiP1ac4r8vJZyM4ZmEDCXGqCQd
r6xMeJy/kkLe/LCEf4Bw8BRdcLM2Mu6Of+5bEfOEASjW27aY7qujm3iQ7S3keRbW
QKo1SFJKiCHg+lDK4GELGPw+vyRhSg2JfcpQkEvSS2NHVFBcJz5T5Qt4wFIAU569
w9raqQWN0rmGtNL7qxUxbnxrrbR4hgdaV4EPpwbUbJjXUiZ7/NYiZwoRKHAUxlnU
ptfbj0nF/3l+YWeN0kaUqpOs8sghnt7/Qr1XeiLf2Z9PL3kAL8UaMLqNx/vxVw/u
XN/AYnygnkC1n8crRms7JC5Vv97MZue8TvIIWhi9TfZZbCGG1vM1SMwQ3ElRGJOA
nYtzyPYZIyzNu5ieaYoePDQcBbuXOBwtFH7MXTrSZwqPUjS/NuqfN9v7eGRAUPbb
OHcSTTFocFj/i2Rs+s41yO2dymSxpJlpEWVlC5QHBImEcJ9R8ttOdPSyCYU4S43M
9Gy59G9mKTe1xV4Hv35BCtpJ6P28MZLzt4zlsPn4UeVtFHe9WxOoakL9FiNCxZbR
Nff5WxKYhTB5
=OGpP
-END PGP SIGNATURE End Message ---

Bug#912221: jabref: incompatible with openjdk 11

[tony mancill]

On Tue, Oct 30, 2018 at 12:31:29PM +0100, Markus Koschany wrote:
> Am 30.10.18 um 01:15 schrieb Emmanuel Bourg:
> > Le 30/10/2018 à 00:41, gregor herrmann a écrit :
> > 
> >> I guess we need to make sure that we build with openjdk-8.
> >> (You know this better than me but I seem to remember that the plan
> >> was to keep openjdk-8 in buster for building packages?)
> > 
> > No please don't built with openjdk-8 if there is a workaround with
> > openjdk-11. Building with openjdk-8 is really a last resort solution,
> > and very few cases justify its use (see lombok for a good example).
> 
> If it is too complicated, too intrusive or takes too much of your time
> away I find it OK to build-depend on openjdk-8. Just ensure that
> upstream knows about this issue because in the next cycle OpenJDK 8 will
> be definitely removed. It is more important that jabref works with
> OpenJDK 11 at runtime.

Hi Markus, hi Emmanuel - 

Thank you both for contributing to this thread.  For the time-being, the
package will build-depend on openjdk-8 to leverage xjc until we have a
suitable recipe for gradle-based builds.  So far, the only plugins I've
found are either wrappers for the xjc command-line tools or the ant
task. I'm hoping there is something out there that we can use in
conjunction with the maven-jaxb2-plugin, but haven't found anything yet.

Note that Debian's gradle in unstable won't run against openjdk-8, so
right now jabref depends on both default-jdk AND openjdk-8.  The build 
is with default-jdk and openjdk-8 is only for the xjc binary.

I am definitely open to (and appreciative of) your suggestions.

Cheers,
tony


signature.asc
Description: PGP signature

Bug#912104: marked as done (hobbit-plugins: missing build dependency on libtimedate-perl)

[Debian Bug Tracking System]

Your message dated Thu, 01 Nov 2018 01:04:13 +
with message-id 
and subject line Bug#912104: fixed in hobbit-plugins 20181101
has caused the Debian Bug report #912104,
regarding hobbit-plugins: missing build dependency on libtimedate-perl
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.)


-- 
912104: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912104
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hobbit-plugins
Version: FTBFS
Severity: serious
Tags: ftbfs

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

...
   dh_auto_test
make -j1 test
make[1]: Entering directory '/build/1st/hobbit-plugins-20180711'
prove -v -l
./src/usr/lib/xymon/server/ext/tftp syntax OK
./src/usr/lib/xymon/server/ext/pgbouncer syntax OK
./src/usr/lib/xymon/server/ext/ircbot syntax OK
./src/usr/lib/xymon/server/ext/conn6 syntax OK
./src/usr/lib/xymon/server/ext/aptdiff syntax OK
./src/usr/lib/xymon/client/ext/temp syntax OK
./src/usr/lib/xymon/client/ext/sftbnc syntax OK
./src/usr/lib/xymon/client/ext/postgres syntax OK
./src/usr/lib/xymon/client/ext/ntpq syntax OK
./src/usr/lib/xymon/client/ext/netstats syntax OK
./src/usr/lib/xymon/client/ext/net syntax OK
Sun Nov 17 03:22:10 2019 ./src/usr/lib/xymon/client/ext/mq 
hobbit.pm.uninitialized: Can't locate Date/Parse.pm in @INC (you may need to 
install the Date::Parse module) (@INC contains: t/fake-lib 
/build/1st/hobbit-plugins-20180711/lib /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.26.2 /usr/local/share/perl/5.26.2 
/usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 
/usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at 
./src/usr/lib/xymon/client/ext/mq line 32.

Sun Nov 17 03:22:10 2019 ./src/usr/lib/xymon/client/ext/mq 
hobbit.pm.uninitialized: Hobbit::max_color(): No colors given as argument at 
/build/1st/hobbit-plugins-20180711/lib/Hobbit.pm line 126.
BEGIN failed--compilation aborted at ./src/usr/lib/xymon/client/ext/mq line 32.

Hobbit::max_color(): No colors given as argument at 
/build/1st/hobbit-plugins-20180711/lib/Hobbit.pm line 126.

#   Failed test 'Perl file passes our syntax check: 
./src/usr/lib/xymon/client/ext/mq'
#   at t/perl-syntax.t line 89.
#  got: '512'
# expected: '0'
./src/usr/lib/xymon/client/ext/misc syntax OK
./src/usr/lib/xymon/client/ext/mdstat syntax OK
./src/usr/lib/xymon/client/ext/mailman syntax OK
./src/usr/lib/xymon/client/ext/libs syntax OK
./src/usr/lib/xymon/client/ext/ipmi syntax OK
./src/usr/lib/xymon/client/ext/entropy syntax OK
./src/usr/lib/xymon/client/ext/dnsq syntax OK
./src/usr/lib/xymon/client/ext/dirtyvcs syntax OK
./src/usr/lib/xymon/client/ext/dirtyetc syntax OK
./src/usr/lib/xymon/client/ext/cntrk syntax OK
./src/usr/lib/xymon/client/ext/cciss syntax OK
./src/usr/lib/xymon/client/ext/backuppc syntax OK
./src/usr/lib/xymon/client/ext/apt syntax OK
./src/usr/bin/xynagios syntax OK
./examples/verify/zombie.pl syntax OK
# Looks like you failed 1 test of 27.
...
--- End Message ---
--- Begin Message ---
Source: hobbit-plugins
Source-Version: 20181101

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

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

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

Debian distribution maintenance software
pp.
Axel Beckert  (supplier of updated hobbit-plugins 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, 01 Nov 2018 00:42:55 +0100
Source: hobbit-plugins
Binary: hobbit-plugins
Architecture: source all
Version: 20181101
Distribution: unstable
Urgency: medium
Maintainer: Christoph Berg 
Changed-By: Axel Beckert 
Description:
 hobbit-plugins - plugins for the Xymon network monitor
Closes: 912104
Changes:
 hobbit-plugins (20181101) unstable; urgency=medium
 .
   * libs.yaml:
 - Whitelist "/memfd:" pseudo files (used by at least pulseaudio and
   Xorg) causing false positive. Thanks Alex Myczko for the report!
 - Whitelist "/var/lib/nfs/etab". Thanks Alex Myczko for the report!
   * Declare compliance with Debian Policy 4.2.1.

Bug#910485: libpsm2-2: times out on /dev/hfi1_0 device and causes test errors

[Drew Parsons]

Package: libpsm2-2
Version: 11.2.68-1
Followup-For: Bug #910485

I agree with Mehdi, your workaround patch would help manage the petsc
and hypre tests while we're waiting for the proper upstream patch.

Drew

Bug#896759: marked as done (gui-ufw: missing build dependency on python3-distutils)

[Debian Bug Tracking System]

Your message dated Thu, 01 Nov 2018 02:38:57 +
with message-id 
and subject line Bug#896759: fixed in gui-ufw 18.10.0-1
has caused the Debian Bug report #896759,
regarding gui-ufw: missing build dependency on python3-distutils
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.)


-- 
896759: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896759
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gui-ufw
Version: 17.04.1-1.1
Severity: serious
Tags: buster sid

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

...
dh_auto_clean --
I: pybuild base:217: python3.6 setup.py clean 
Traceback (most recent call last):
  File "setup.py", line 20, in 
from DistUtilsExtra.auto import setup
  File "/usr/lib/python3/dist-packages/DistUtilsExtra/auto.py", line 43, in 

import distutils.core
ModuleNotFoundError: No module named 'distutils.core'
E: pybuild pybuild:336: clean: plugin distutils failed with: exit code=1: 
python3.6 setup.py clean 
dh_auto_clean: pybuild --clean -i python{version} -p 3.6 returned exit code 13
make[1]: *** [debian/rules:10: override_dh_auto_clean] Error 25


Due to

python3.6 (3.6.5~rc1-2) unstable; urgency=medium

  * python3.6: Drop dependency on python3-distutils.
...
 -- Matthias Klose   Tue, 20 Mar 2018 14:29:58 +0800
--- End Message ---
--- Begin Message ---
Source: gui-ufw
Source-Version: 18.10.0-1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 31 Oct 2018 23:05:56 -0300
Source: gui-ufw
Binary: gufw
Architecture: source
Version: 18.10.0-1
Distribution: unstable
Urgency: high
Maintainer: Python Applications Packaging Team 

Changed-By: Samuel Henrique 
Description:
 gufw   - graphical user interface for ufw
Closes: 896759
Changes:
 gui-ufw (18.10.0-1) unstable; urgency=high
 .
   [ Samuel Henrique ]
   * Team Upload
   * New upstream version 18.10.0
   * Move packaging to salsa
   * Bump DH level to 11
   * Bump Standards-Version to 4.2.1
   * Bump watch to v4
   * d/control:
 - Add Build-Dep on python3-distutils (closes: #896759)
 - Use https for upstream homepage
 - Remove dependency on net-tools, not needed since 17.10
   * wrap-and-sort -a
 .
   [ Ondřej Nový ]
   * d/changelog: Remove trailing whitespaces
Checksums-Sha1:
 0ae0ad1242a5b5590793c0a3b7ad84421b604ad1 2030 gui-ufw_18.10.0-1.dsc
 86f00f1263174288783f10f037cbaa3d55365195 2279218 gui-ufw_18.10.0.orig.tar.gz
 a4f57a22eec758a09f21a43b0201dfb1d7f98fed 4316 gui-ufw_18.10.0-1.debian.tar.xz
 4e9d940114aca16bdbd87fce42d8b72c91e12adf 6834 gui-ufw_18.10.0-1_amd64.buildinfo
Checksums-Sha256:
 a3823ebcd88577632ac47cddf2c6e4afc9f01f764b703b46dfe09e2fd063d174 2030 
gui-ufw_18.10.0-1.dsc
 c44468550cbcb35ebee0dd8339341447118811ccd0714e79350136117421b93b 2279218 
gui-ufw_18.10.0.orig.tar.gz
 0212ec18590dcf6dbc0b1ee6ff98876978b7dec13ffd6b2d0e1c2fcc6b11c2cd 4316 
gui-ufw_18.10.0-1.debian.tar.xz
 eba96035c309569dedfdb24b1677860024a1947c49a724f1b16796ee5f64922c 6834 
gui-ufw_18.10.0-1_amd64.buildinfo
Files:
 00d8dac3d8df621892e750700b419d1c 2030 admin optional gui-ufw_18.10.0-1.dsc
 ceab2bc447ac374917c1224b5aec9cd9 2279218 admin optional 
gui-ufw_18.10.0.orig.tar.gz
 73876b4ecdbcf1b082a04996ba5b8b5d 4316 admin optional 
gui-ufw_18.10.0-1.debian.tar.xz
 2ad0ba59dcfb350a43f1b22327dd8d7c 6834 admin optional 
gui-ufw_18.10.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEBdtqg34QX0sdAsVfu6n6rcz7RwcFAlvaYSgACgkQu6n6rcz7
RwcOVhAAuWk+gJO5RNeycaO02tILj2eao0QUl/dXskqp0mPaJe0U6sriY7ipYxJk
f6lRyqumSHZ+2ZGQC+nV+RLn77Fgu5qzTiXVzOIQc4nHO0Jy6KlGPxNBpCqQtVYw
fO7+QrCuA5+4cirJSvN3483+Di/DiYMvCEAOpk59FHycTZZUuVkkVou2QeWAXOa1
S3tbv6B4kghyg1T8s/afdoiiIPOddVgzeMOdFYNqgsPoXgSDjrfI/5JqkZfSeiYx
GyvHCdZ7uzgGbwM2W26AndQMTaDgZzt3oqOXEi7srjpXVFckMJX3jtoPGk3JESAn
gxStxF7iRCK8GEOeV9dyv7gymB7WBAFyHWm7U5UhQbuKeozRoOwk4ViTcn9cLnIJ
JSRfcxPBUlBHMGZcj4ViZnDRfThHC

Bug#912221: marked as done (jabref: incompatible with openjdk 11)

[Debian Bug Tracking System]

Your message dated Thu, 01 Nov 2018 02:39:07 +
with message-id 
and subject line Bug#912221: fixed in jabref 3.8.2+ds-8
has caused the Debian Bug report #912221,
regarding jabref: incompatible with openjdk 11
to be marked as done.

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

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


-- 
912221: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912221
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: jabref
Version: 3.8.2+ds-7
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Now that openjdk 11 is the default, jabref won't start without some
help:

% jabref
Error occurred during initialization of boot layer
java.lang.module.FindException: Module java.se.ee not found

(java.se.ee is required by the /usr/bin/jabref wrapper).

With JAVA_HOME set, all is fine: Both
JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref
and
JAVA_HOME=/usr/lib/jvm/java-10-openjdk-amd64/ jabref
still work.


Seems like we need some fiddling with /usr/bin/jabref and/or the
runtime dependencies to make sure we use openjdk {8,9,10} but not 11.
Or better a way to make it work with 11, if that's the default for
buster …


This is also
https://bugs.launchpad.net/bugs/1799106
which brought me to check the situation in Debian.


Cheers,
gregor


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

Kernel: Linux 4.18.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=de_AT.utf8 (charmap=UTF-8), LANGUAGE=C (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)
LSM: AppArmor: enabled

Versions of packages jabref depends on:
ii  java-wrappers   0.3
ii  libandroid-json-java8.1.0+r23-2
ii  libantlr3-runtime-java  3.5.2-9
ii  libantlr4-runtime-java  4.6-2
ii  libbcprov-java  1.60-1
ii  libcommons-cli-java 1.4-1
ii  libcommons-lang3-java   3.8-1
ii  libcommons-logging-java 1.2-2
ii  libglazedlists-java 1.9.1-2
ii  libguava-java   19.0-1
ii  libhttpasyncclient-java 4.1.4-1
ii  libhttpclient-java  4.5.6-1
ii  libhttpmime-java4.5.6-1
ii  libjava-string-similarity-java  0.24-1
ii  libjempbox-java 1:1.8.16-1
ii  libjgoodies-common-java 1.8.1-2
ii  libjgoodies-forms-java  1.9.0-3
ii  libjgoodies-looks-java  2.7.0-3
ii  libjhlabs-filters-java  2.0.235-3
ii  libjsoup-java   1.10.2-2
ii  liblog4j2-java  2.11.1-1
ii  libmicroba-java 1:0.4.4.3-5
ii  libpdfbox-java  1:1.8.16-1
ii  libreoffice-java-common 1:6.1.3~rc1-2
ii  libspin-java1.5+dfsg-8
ii  libswing-layout-java1.0.4-4
ii  libswingx-java  1:1.6.2-3
ii  libunirest-java-java1.4.8-2

Versions of packages jabref recommends:
ii  libmysql-java5.1.45-1
ii  libpostgresql-jdbc-java  42.2.5-1
ii  libreoffice-writer   1:6.1.3~rc1-2
ii  xdg-utils1.1.3-1

Versions of packages jabref suggests:
ii  acroread [pdf-viewer] 9.5.5-dmo5
ii  epdfview [pdf-viewer] 0.1.8-3
ii  evince [postscript-viewer]3.30.1-1
ii  ghostscript [postscript-viewer]   9.25~dfsg-4
ii  gv [postscript-viewer]1:3.7.4-1+b1
ii  mupdf [pdf-viewer]1.14.0+ds1-1
ii  xpdf [pdf-viewer] 3.04-9
ii  zathura-pdf-poppler [pdf-viewer]  0.2.9-1

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAlvXAwJfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgbPUg//UmAPUuWvMDng/dD5NHbMPJ1ARz0ZDMdSk2cjdnER4E9VtHUE42FdoNda
O7zXgSAMaEazyKQFVyahymdr9boqcRojVwqlSS1K+zfqs7iPFqBeZV9fhwGkhWrF
jzMeA4efO2zs5gLY7Uievu+xpzSQ8UHMmYZ+lXYhgRD7enU9t+2hcFUoF785YFCy
rxJtAN/Ah1kucC4Gzf3NagfPUL+pJbiWDa96dSdUzbKyrrusJf2GoUVAXr22Wm1M
xTy+cam60nc5acvcDjIxh7gp9SyRzytu/3NHXzITurw+tN4e6eDHcWlCqwpvoulK
srLgA33K86Ts8J9HIlJuK+Aje4f5OQ4kIXjyNNBT0uTN4ApAcrw3a7HjdSED1c2v
Q7r3P5rXSKklvwT3p+iyrJPrNr42+CUL8MjJ8mA7dM19t1WD/3voY7bN0C7NrDQ2
zuiR40jH1T5klP6XXhM/0JkBhyiu9+f5vE0u2PuvXJSyf2oVFiTuQ5FocdFmVUVA
bFU/YLmzC0yAbKMlZLCJ+vbRtoPP5bGV1+oUcQ+1Ng+Ra39PCFimoLy5bHTh2dY/
+aZEfnASvAaS6Asn2+vYAUWhNvIIf9AGcJIa5qVAimLl0p3xoQwcKBnh1ra2cIUg
GKeHS

Bug#912238: marked as done (android-platform-libnativehelper FTBFS: ScopedPthreadMutexLock.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Thu, 1 Nov 2018 11:13:26 +0800
with message-id <4ce0c64d-57a3-c811-538f-a53120b68...@gmail.com>
and subject line Re: android-platform-libnativehelper FTBFS: 
ScopedPthreadMutexLock.h: No such file or directory
has caused the Debian Bug report #912238,
regarding android-platform-libnativehelper FTBFS: ScopedPthreadMutexLock.h: No 
such file or 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.)


-- 
912238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: android-platform-libnativehelper
Version: 7.0.0+r33-1
Severity: serious
Tags: ftbfs buster sid

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

...
g++ JNIHelp.cpp JniConstants.cpp toStringArray.cpp JniInvocation.cpp 
AsynchronousCloseMonitor.cpp -o libnativehelper.so.0 -g -O2 
-ffile-prefix-map=/build/1st/android-platform-libnativehelper-7.0.0+r33=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-fvisibility=protected -Wdate-time -D_FORTIFY_SOURCE=2 -DNDEBUG 
-I/usr/include/android -Iinclude/nativehelper -I/usr/include/android/libcore 
-Wl,-z,relro -fPIC -shared -Wl,-soname,libnativehelper.so.0 -ldl -lpthread 
-Wl,-rpath=/usr/lib/x86_64-linux-gnu/android 
-L/usr/lib/x86_64-linux-gnu/android -llog
In file included from AsynchronousCloseMonitor.cpp:19:
include/nativehelper/AsynchronousCloseMonitor.h:20:10: fatal error: 
ScopedPthreadMutexLock.h: No such file or directory
 #include "ScopedPthreadMutexLock.h"
  ^~
compilation terminated.
make[2]: *** [debian/Makefile:14: build] Error 1
--- End Message ---
--- Begin Message ---
Source-Version: 8.1.0+r23-1

Forgot to mention this bug in the release.



signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#911226: marked as done (lttoolbox: FTBFS on several architectures: test failures)

[Debian Bug Tracking System]

Your message dated Thu, 01 Nov 2018 04:34:09 +
with message-id 
and subject line Bug#911226: fixed in lttoolbox 3.5.0-3
has caused the Debian Bug report #911226,
regarding lttoolbox: FTBFS on several architectures: test failures
to be marked as done.

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

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


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

There are several test failures on various architectures, e.g.:

FAIL: runTest (lt_proc.PrintWeightsNegative)
--
Traceback (most recent call last):
  File "/<>/tests/proctest.py", line 71, in runTest
exp+"[][\n]")
AssertionError: u'^cat/cat+n/cat+v$[][\n]' != 
u'^cat/cat+n/cat+v$[][\n]'
- ^cat/cat+n/cat+v$[][
+ ^cat/cat+n/cat+v$[][
  ]


FAIL: runTest (lt_print.NegativeWeightedFst)
--
Traceback (most recent call last):
  File "/<>/tests/printtest.py", line 62, in runTest
self.assertEqual(self.communicateFlush(), self.expectedOutput)
AssertionError: 
u'0\t1\tc\tc\t4.567895\t\n1\t2\ta\ta\t0.989532\t\n2\t3\tt\tt\t2.796193\t\n3\t4\t
 [truncated]... != 
u'0\t1\tc\tc\t4.567895\t\n1\t2\ta\ta\t0.989532\t\n2\t3\tt\tt\t2.796193\t\n3\t4\t
 [truncated]...
  0 1   c   c   4.567895
  1 2   a   a   0.989532
  2 3   t   t   2.796193
- 3 4   \u03b5  +   0.00
+ 3 4   \u03b5  +   -0.824564   
  4 5   \u03b5  n   1.824564
  4 5   \u03b5  v   2.856296
- 5 0.00
+ 5 -0.525487


Full logs: https://buildd.debian.org/status/package.php?p=lttoolbox

Emilio
--- End Message ---
--- Begin Message ---
Source: lttoolbox
Source-Version: 3.5.0-3

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

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

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

Debian distribution maintenance software
pp.
Kartik Mistry  (supplier of updated lttoolbox 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, 01 Nov 2018 08:53:13 +0530
Source: lttoolbox
Binary: lttoolbox liblttoolbox3-3.5-1 lttoolbox-dev
Architecture: source amd64
Version: 3.5.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Team 

Changed-By: Kartik Mistry 
Description:
 liblttoolbox3-3.5-1 - Shared library for lttoolbox
 lttoolbox  - Apertium lexical processing modules and tools
 lttoolbox-dev - Development tools and library for lttoolbox
Closes: 911226
Changes:
 lttoolbox (3.5.0-3) unstable; urgency=medium
 .
   * debian/patches:
 + Added a patch fix FTBFS on several architectures (Closes: #911226)
Checksums-Sha1:
 077c47dee603edbe8fc0128df26897f43f5bc7f4 2272 lttoolbox_3.5.0-3.dsc
 9bb1dbd6ed3136718d0e457298b051d16e6efeb8 145008 lttoolbox_3.5.0.orig.tar.bz2
 6ab4cd515ef289c6d7b26e915faeb546b7e608ba 5136 lttoolbox_3.5.0-3.debian.tar.xz
 06ebb4aa0ff8a7bd9b16f54cd9f3b15e917e639e 3059160 
liblttoolbox3-3.5-1-dbgsym_3.5.0-3_amd64.deb
 f35eee6e1828d4d77d7539d68a1d43746d47896d 162860 
liblttoolbox3-3.5-1_3.5.0-3_amd64.deb
 8708cb18af679b8a9101b05682435bae09cf9ba0 377848 
lttoolbox-dbgsym_3.5.0-3_amd64.deb
 54db7afb48f3bf96dabc0cce87c9279683eaae24 505900 
lttoolbox-dev-dbgsym_3.5.0-3_amd64.deb
 fa84b17b905264d0eb1f846ad2f14659ff2bfe7c 52724 lttoolbox-dev_3.5.0-3_amd64.deb
 a6b1554db672400c33b928743994b9640b88b926 11345 
lttoolbox_3.5.0-3_amd64.buildinfo
 a25bc4256b653b15702e2652e87c37aed600967e 23156 lttoolbox_3.5.0-3_amd64.deb
Checksums-Sha256:
 eaf013e621549ef75c00a9836cb9bfdba8f530f1ee9de8aab347b77eb4176ad2 2272 
lttoolbox_3.5.0-3.dsc
 6b495779bcf469c441512689fda0754f9c84171e8dc88afcf3545a5f23fcb865 145008 
lttoolbox_3.5.0.orig.tar.bz2
 4fac4892aacc30024104caf92bd77d85af977c2ed64cf02e16b3576fd1b850c9 5136 
lttoolbox_3.5.0-3.debian.tar.xz
 3f81e6d281381e10b1feda5c2807900812e13959fa4da9929939cb84182b4dbc 3059160 
liblttoolbox3-3.5-1-dbgsym_3.5.0-3_amd64.deb
 c403337555

Bug#911951: Bug #911951 in partd marked as pending

[Diane Trout]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/modules/partd/commit/4064b8701aa307c76527a115cde2634b4c75c48d


add autopkgtest depends on python3-all. (Closes: #911951)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/911951

Processed: Bug #911951 in partd marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #911951 [src:partd] partd autopkg tests need to depend on python3-all
Added tag(s) pending.

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

Bug#911951: marked as done (partd autopkg tests need to depend on python3-all)

[Debian Bug Tracking System]

Your message dated Thu, 01 Nov 2018 05:04:43 +
with message-id 
and subject line Bug#911951: fixed in partd 0.3.9-1
has caused the Debian Bug report #911951,
regarding partd autopkg tests need to depend on python3-all
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.)


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

the partd autopkg tests need to depend on python3-all, same as in the build
dependencies. This will block at least python3-defaults once failing autopkg
tests are made blocking.
--- End Message ---
--- Begin Message ---
Source: partd
Source-Version: 0.3.9-1

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

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

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

Debian distribution maintenance software
pp.
Diane Trout  (supplier of updated partd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 31 Oct 2018 21:38:51 -0700
Source: partd
Binary: python3-partd
Architecture: source
Version: 0.3.9-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Diane Trout 
Description:
 python3-partd - Appendable key-value storage for Python 3
Closes: 911951
Changes:
 partd (0.3.9-1) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Set Vcs-* to salsa.debian.org
   * d/watch: Use https protocol
   * d/control: Remove ancient X-Python-Version field
   * d/control: Remove ancient X-Python3-Version field
 .
   [ Diane Trout ]
   * New upstream release.
   * Update debhelper compat to 11
   * Wrap Test-Command for easier reading
   * add autopkgtest depends on python3-all. (Closes: #911951)
   * Update to standards version 4.2.1. No changes needed
   * Remove unnecessary-testsuite-autopkgtest-field
   * Remove needs-recommends restriction and list optional test dependencies
   * Remove .pytest_cache in debian/rules in case we ran tests
   * Be more verbose in tests so I can find where it was hanging
Checksums-Sha1:
 1a35e47f38f1fb2577201dac29cbcc8a5d4ae24b 2173 partd_0.3.9-1.dsc
 8292e96ad3f2a48e58a0799b7a72a9c63b42492d 19312 partd_0.3.9.orig.tar.gz
 9188ae94b6a9515e3cccff2fd74ca7eb1ea42293 3364 partd_0.3.9-1.debian.tar.xz
 052c466ae34bf5967f1496360f35030babcf5a8e 7624 partd_0.3.9-1_source.buildinfo
Checksums-Sha256:
 90f7d341f4901b2e613f43bf2c0ecf03933ac07b9ab393b5b307344556c8c762 2173 
partd_0.3.9-1.dsc
 1fd6d9c12f14ea180e659a9e4a686ff2816dd930e8fb0b84c0d8116a29cfe66b 19312 
partd_0.3.9.orig.tar.gz
 51236d81e51ff73667edabb2d42f21a9a58a959eba4b4d1c73725a4a4d3bffc3 3364 
partd_0.3.9-1.debian.tar.xz
 02530466848d3a3e68edc74c6f27a72566d86aed5d90bff7152be236768cc818 7624 
partd_0.3.9-1_source.buildinfo
Files:
 b96b1076f9416517711f6ec248f5f3e4 2173 python optional partd_0.3.9-1.dsc
 d795ec221af698048709a8051746d907 19312 python optional partd_0.3.9.orig.tar.gz
 dc5164d4be45283d6c50ae19149f315a 3364 python optional 
partd_0.3.9-1.debian.tar.xz
 383657d5454ea76c0d7e8f002db5fd18 7624 python optional 
partd_0.3.9-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQVcMeSBIEX5AQ11mQ04NnM013AFAlvahfoACgkQmQ04NnM0
13BQow//R70LVo0SAIklUnXvupDJIbjXGgIIxyBqb0TP5UqANacfp42N1s4BEiZP
d9unLvyr8qrwu1kpUCys6hW6BGZZ7Yf6VkLnD1YgauxqU/e6b0+Z2S4EXa2d530m
YZ9HnkJeswOxSEI9MWkSdDoFQ1fJ6cL0GLkQ3GjC6Jp5QURDBj2t192wFKwD4Coj
7+evX7n+J+KWll9mkhhuTUXW+1j/TVWsHCo2erX7dSP1OjYIJ4Wj2+TWyVcRxJow
wvMLJHrcUqEhsMhtgZN6rUNYceHx37Nay4et8b89abl8MB9IoAkAwHU4QHERcMTh
NXrcrVgg2RDpL2IwxXH5nmrhRXZnSYJkeCAmG4Vy7oCk7Ztt8ffe1U9FRMtD4e1H
Wfarl0Y+y/SZzzs4zU19a2E/JtFERAYchJnNTuYjMRnkTOdQ95gBiVjk3w3AD0aw
jgvWBZKfbeDdvOejpwBY4MI20n6IS03JE73B2bV9+AUipzFn3iD7J1zaDN/Jm7NU
XexvpcJZEuJCDTAEctSxJGGGLp1CmU2+rtTZ3bu0+IQoBbhhIvnOeoQRTLCdkMwt
8da780ck1aUismzQ9GZwTzfQGFlWqn8mLkuZH2PBqlTcoL8djc4lW4S73I4uSgRU
ofQIhqGPu36nwevxw0nAZKbmauGOFsKpiDISoUbTmuoXRUFC+xk=
=YTrg
-END PGP SIGNATURE End Message ---