Processed: Bug #919625 in neutron-fwaas marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #919625 [neutron-fwaas-common] neutron-fwaas-common: fails to remove: 
neutron-plugin-manage disable: error: argument --service-plugin: invalid 
choice: 'firewall_v2'
Added tag(s) pending.

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

Bug#919625: Bug #919625 in neutron-fwaas marked as pending

[Thomas Goirand]

Control: tag -1 pending

Hello,

Bug #919625 in neutron-fwaas 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/openstack-team/services/neutron-fwaas/commit/55a25f69492645950945480592b33d5e8a05552f


* Get rid of neutron-fwaas-common, and move all to python3-neutron-fwaas.
  * Fix the neutron config in the prerm so that neutron-plugin-manage can read
the entry point before removal (Closes: #919625).


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/919625

Bug#880393: testing cyrus-sasl2 2.1.27+dfsg-1~exp1 (was: Re: nmuing cyrus-sasl2)

[Ryan Tandy]

Hello Ondřej,

On Mon, Jan 21, 2019 at 05:54:39PM +0100, OndÅ?ej Surý wrote:
I spent a half-day hacking cyrus-sasl2 and I uploaded 2.1.27 to 
experimental. I would appreciate if more people can test the package (I 
won’t have time until tomorrow or next week). I didn’t even had a 
chance to test it myself, so even the basic it installs and nothing 
breaks horribly would help.


Thank you for spending some time working on the package! I have spent 
some time looking at it this evening.


I noticed in debian/control that the Build-Depends lines for 
libpod-pom-view-restructured-perl and python3-sphinx are indented with 
mixed spaces and tabs.


I confirm that these bugs are fixed:
#880393 (MIT modules installed in heimdal pkg)
#919639 (man pages were empty -- please close this one in changelog)

These bugs still exist:
#917140 (changes from old NMUs silently dropped)
#917129 (unnecessary GSSAPI linking breaks slapd-smbk5pwd)

I already opened merge requests on salsa for these last two and am 
rebasing them now; would you mind taking a look? #917129 in particular 
would be great to have in buster as slapd-smbk5pwd is currently unusable 
with heimdal.


I tested the following use cases:

* testsaslauthd with saslauthd using sasldb backend
* testsaslauthd with saslauthd using pam backend
* testsaslauthd with saslauthd using ldap backend
* testsaslauthd with saslauthd using kerberos5 backend
* EXTERNAL authentication to slapd
* GSSAPI authentication to slapd (heimdal module)
* GSSAPI authentication to slapd (MIT module)
* DIGEST-MD5 authentication to slapd (password stored in slapd)
* PLAIN authentication to slapd (password stored in slapd)
* PLAIN authentication to slapd with pass-through to saslauthd
* LOGIN authentication to slapd with pass-through to saslauthd

and all of those are working fine. I have not looked at the sql or otp 
modules.


I also checked some man pages and the html docs (-doc package) briefly 
and everything looked ok.


Thank you for working on cyrus-sasl2, and please consider adding the 
patch for #917129 if you can. :)


cheers,
Ryan

Bug#920146: janest-core-kernel: build-depends on libbin-prot-camlp4-dev

[Ralf Treinen]

Package: src:janest-core-kernel
Version: 113.00.00-3
Severity: serious
Tags: ftbfs
User: trei...@debian.org
Usertags: edos-uninstallable

janest-core-kernel build-depends on libbin-prot-camlp4-dev which lives
in sid only on hurd-i386. This makes it FTBFS on all other archs where
it used to compile before.

-Ralf.

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 920045 src:ntopng
Bug #920045 [ntomng] ntopng FTBFS with new ndpi
Warning: Unknown package 'ntomng'
Bug reassigned from package 'ntomng' to 'src:ntopng'.
No longer marked as found in versions 2.4+dfsg1-4.
Ignoring request to alter fixed versions of bug #920045 to the same values 
previously set
> forcemerge 919907 920045
Bug #919907 [src:ntopng] ntopng FTBFS with ndpi 2.6
Bug #920045 [src:ntopng] ntopng FTBFS with new ndpi
Marked as found in versions ntopng/2.4+dfsg1-4.
Added tag(s) ftbfs.
Merged 919907 920045
> thanks
Stopping processing here.

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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 920020 openjdk-11-jdk-headless
Bug #920020 [openjdk-11-jdk] javadoc: The code being documented uses modules 
but the packages defined in … are in the unnamed module
Bug reassigned from package 'openjdk-11-jdk' to 'openjdk-11-jdk-headless'.
No longer marked as found in versions openjdk-11/11.0.2+7-1.
Ignoring request to alter fixed versions of bug #920020 to the same values 
previously set
> forcemerge 919798 920020
Bug #919798 [openjdk-11-jdk-headless] antlr4: FTBFS (Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar)
Bug #919800 [openjdk-11-jdk-headless] jackson-databind: FTBFS (Failed to 
execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar)
Bug #919801 [openjdk-11-jdk-headless] libgoogle-gson-java: FTBFS (Failed to 
execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar)
Bug #919874 [openjdk-11-jdk-headless] bsaf: FTBFS (Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar)
Bug #919875 [openjdk-11-jdk-headless] commons-csv: FTBFS (Failed to execute 
goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar=
Bug #919876 [openjdk-11-jdk-headless] java-string-similarity: FTBFS (Failed to 
execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar)
Bug #919878 [openjdk-11-jdk-headless] servlet-api: FTBFS (Failed to execute 
goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar)
Bug #919883 [openjdk-11-jdk-headless] libreoffice arch all FTBFS, javadoc: 
error - The code being documented uses modules but the packages defined in 
http://java.sun.com/j2se/1.5/docs/api/ are in the unnamed module.
Bug #919895 [openjdk-11-jdk-headless] openjdk-11-jdk-headless: Regression: 
Breaks a bunch of packages using javadoc
Bug #919968 [openjdk-11-jdk-headless] libreoffice: binary-all FTBFS
Bug #919798 [openjdk-11-jdk-headless] antlr4: FTBFS (Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar)
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Added tag(s) patch.
Bug #920020 [openjdk-11-jdk-headless] javadoc: The code being documented uses 
modules but the packages defined in … are in the unnamed module
Severity set to 'serious' from 'grave'
Added indication that 920020 affects 
src:libparanamer-java,src:libreoffice,src:java-string-similarity,src:libgoogle-gson-java,src:libxml-security-java,src:antlr4,src:jnr-posix,src:localizer,src:jackson-databind,src:dirgra,src:bsaf,src:servlet-api,src:weupnp,src:commons-csv
Marked as found in versions openjdk-11/11.0.2+7-1.
Added tag(s) ftbfs.
Bug #919800 [openjdk-11-jdk-headless] jackson-databind: FTBFS (Failed to 
execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar)
Bug #919801 [openjdk-11-jdk-headless] libgoogle-gson-java: FTBFS (Failed to 
execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar)
Bug #919874 [openjdk-11-jdk-headless] bsaf: FTBFS (Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar)
Bug #919875 [openjdk-11-jdk-headless] commons-csv: FTBFS (Failed to execute 
goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar=
Bug #919876 [openjdk-11-jdk-headless] java-string-similarity: FTBFS (Failed to 
execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar)
Bug #919878 [openjdk-11-jdk-headless] servlet-api: FTBFS (Failed to execute 
goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar)
Bug #919883 [openjdk-11-jdk-headless] libreoffice arch all FTBFS, javadoc: 
error - The code being documented uses modules but the packages defined in 
http://java.sun.com/j2se/1.5/docs/api/ are in the unnamed module.
Bug #919895 [openjdk-11-jdk-headless] openjdk-11-jdk-headless: Regression: 
Breaks a bunch of packages using javadoc
Bug #919968 [openjdk-11-jdk-headless] libreoffice: binary-all FTBFS
Merged 919798 919800 919801 919874 919875 919876 919878 919883 919895 919968 
920020
> affects 919798 openjdk-11-jdk
Bug #919798 [openjdk-11-jdk-headless] antlr4: FTBFS (Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar)
Bug #919800 [openjdk-11-jdk-headless] jackson-databind: FTBFS (Failed to 
execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar)
Bug #919801 [openjdk-11-jdk-headless] libgoogle-gson-java: FTBFS (Failed to 
execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar)
Bug #919874 [openjdk-11-jdk-headless] bsaf: FTBFS (Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar)
Bug #919875 [openjdk-11-jdk-headless] commons-csv: FTBFS (Failed to execute 
goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar=
Bug #919876 [openjdk-11-jdk-headless] java-string-similarity: FTBFS (Failed to 
execute goal org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar)
Bug #919878 [openjdk-11-jdk-headless] servlet-api: 

Bug#919822: marked as done (gitlab: CVE-2019-6240: Arbitrary repo read in Gitlab project import)

[Debian Bug Tracking System]

Your message dated Tue, 22 Jan 2019 06:05:01 +
with message-id 
and subject line Bug#919822: fixed in gitlab 11.5.7+dfsg-1
has caused the Debian Bug report #919822,
regarding gitlab: CVE-2019-6240: Arbitrary repo read in Gitlab project import
to be marked as done.

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

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


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

Hi,

The following vulnerability was published for gitlab, and fixed in
11.6.4, 11.5.7, and 11.4.14.

CVE-2019-6240[0]:
RESERVED

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-2019-6240
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6240
[1] 
https://about.gitlab.com/2019/01/16/critical-security-release-gitlab-11-dot-6-dot-4-released/

Please adjust the affected versions in the BTS as needed.

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

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

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

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

Debian distribution maintenance software
pp.
Abhijith PA  (supplier of updated gitlab package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 20 Jan 2019 21:37:01 +0530
Source: gitlab
Binary: gitlab gitlab-common
Architecture: source all
Version: 11.5.7+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Abhijith PA 
Description:
 gitlab - git powered software platform to collaborate on code (non-omnibus
 gitlab-common - git powered software platform to collaborate on code (common)
Closes: 919822
Changes:
 gitlab (11.5.7+dfsg-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream version 11.5.7+dfsg
   * Fix CVE-2019-6240: Arbitrary repo read in Gitlab project import
 (Closes: #919822)
Checksums-Sha1:
 946de46090868d8e2622a1cd035fa8cb9d13c28a 2326 gitlab_11.5.7+dfsg-1.dsc
 4d46b46ef4c70d791ed1bbdec91d982e07089865 51005289 
gitlab_11.5.7+dfsg.orig.tar.gz
 ff154f96786cbf4d0efcb95f94e2336133b7cc44 66956 
gitlab_11.5.7+dfsg-1.debian.tar.xz
 f5d66741df516c5e2d439a496df010dc0a04dda1 145524 
gitlab-common_11.5.7+dfsg-1_all.deb
 d993b7d7dbd2d0842725b0023dc9bd92df2d28b6 46627576 gitlab_11.5.7+dfsg-1_all.deb
 547d382f5482268e54859687be65b88212533f4a 8995 
gitlab_11.5.7+dfsg-1_amd64.buildinfo
Checksums-Sha256:
 bf0f94ad51752740c40734e82d55ce242dea7f106d7696970dd7557bf374d8c3 2326 
gitlab_11.5.7+dfsg-1.dsc
 d6989d4d07ac4b3d1dc4afbc3f019fbae793b2791fb37b9c918e6b529a69641e 51005289 
gitlab_11.5.7+dfsg.orig.tar.gz
 5b1f5409b3079d82f9bb8a0b5d5c4b0c9b374485c56abd29063a8cc9e36ee3e6 66956 
gitlab_11.5.7+dfsg-1.debian.tar.xz
 e3864d4e56589aea0f14e874fb46001321b74ce519e2d5fa71759f06b066db6c 145524 
gitlab-common_11.5.7+dfsg-1_all.deb
 a71dbebb2563ec3ecd7b3de043b6a825a9d23f75b2fe86a0049792001c6c6dfb 46627576 
gitlab_11.5.7+dfsg-1_all.deb
 17ddda591c226d32c840d76e386cd6cc4f3c5c6049ab599481ae301459d885d3 8995 
gitlab_11.5.7+dfsg-1_amd64.buildinfo
Files:
 1a34cfb1ffb3a1a6477a8bae5f1fd923 2326 net optional gitlab_11.5.7+dfsg-1.dsc
 c09eb5b441ef6df079e5794bfcdf4c06 51005289 net optional 
gitlab_11.5.7+dfsg.orig.tar.gz
 047592a4f701f4fc5758bcb4e7353378 66956 net optional 
gitlab_11.5.7+dfsg-1.debian.tar.xz
 8ebf3ee11ef683a482d3a16ede40f215 145524 net optional 
gitlab-common_11.5.7+dfsg-1_all.deb
 d6127bfa71d3afa4ecb9ea63fa1ed837 46627576 contrib/net optional 
gitlab_11.5.7+dfsg-1_all.deb
 3a8809009a2626abc288348caf7dcdcc 8995 net optional 
gitlab_11.5.7+dfsg-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE7xPqJqaY/zX9fJAuhj1N8u2cKO8FAlxGrmEUHGFiaGlqaXRo
QGRlYmlhbi5vcmcACgkQhj1N8u2cKO9qWA/+LHLTN7NKenNLaEiY806UIcTF/za9
GSA8rwN4eH0pIjS0ROSbzvCn/dXYugXzDh3DG7nR3L+5nnb2qBbnSurUz+cL7M9o

Processed: tagging 920018, severity of 920018 is serious

[Debian Bug Tracking System]

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

> tags 920018 + upstream
Bug #920018 [systemd] Memory Leak in journald?  Failed to write entry (23 
items, 500 bytes), ignoring: Cannot allocate memory
Added tag(s) upstream.
> # regression
> severity 920018 serious
Bug #920018 [systemd] Memory Leak in journald?  Failed to write entry (23 
items, 500 bytes), ignoring: Cannot allocate memory
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#919727: cmtk /dcmtk

[Torsten Rohlfing]

Thanks Yarik, but too late ;)

Anyway, I have a patch (see below) that appears to work. I'll be rolling a
small bugfix release of CMTK in the next few days if/when I get a chance.

Index: core/apps/dcm2image.cxx
===
--- core/apps/dcm2image.cxx (revision 5439)
+++ core/apps/dcm2image.cxx (working copy)
@@ -82,7 +82,11 @@
 const std::string tagName( pattern, static_cast(
equals-pattern ) );

 const DcmDictEntry* dictEntry = dcmDataDict.rdlock().findEntry(
tagName.c_str() );
+#if PACKAGE_VERSION_NUMBER < 364
 dcmDataDict.unlock();
+#else
+dcmDataDict.rdunlock();
+#endif

 if ( dictEntry )
   {
@@ -482,7 +486,11 @@
 #ifdef CMTK_DCMDICTPATH
 if ( dcmDataDict.wrlock().loadDictionary( CMTK_DCMDICTPATH ) )
   {
+#if PACKAGE_VERSION_NUMBER < 364
   dcmDataDict.unlock();
+#else
+  dcmDataDict.wrunlock();
+#endif
   }
 else
 #endif
@@ -489,7 +497,11 @@
 #ifdef CMTK_DCMDICTPATH_INSTALL
 if ( dcmDataDict.wrlock().loadDictionary( CMTK_DCMDICTPATH_INSTALL ) )
   {
+#if PACKAGE_VERSION_NUMBER < 364
   dcmDataDict.unlock();
+#else
+  dcmDataDict.wrunlock();
+#endif
   }
 else
 #endif
@@ -566,9 +578,17 @@

   if ( !dcmDataDict.rdlock().findEntry( "RawDataType_ImageType" ) )
 {
+#if PACKAGE_VERSION_NUMBER < 364
 dcmDataDict.unlock();
+#else
+dcmDataDict.rdunlock();
+#endif
 dcmDataDict.wrlock().addEntry( new DcmDictEntry( 0x0043, 0x102f,
EVR_SS, "RawDataType_ImageType", 1, 1, NULL, OFFalse, "GE" ) );
+#if PACKAGE_VERSION_NUMBER < 364
 dcmDataDict.unlock();
+#else
+dcmDataDict.wrunlock();
+#endif
 }

   VolumeList volumeList( Tolerance );
===



On Mon, Jan 21, 2019 at 8:08 PM Yaroslav Halchenko 
wrote:

>
> On Mon, 21 Jan 2019, Torsten Rohlfing wrote:
>
> >Hi there -
> >Upstream owner of CMTK here. It looks like DCMTK in release 3.6.4
> changed
> >their API for locking/unlocking the global data dictionary.
> >I am going to look into fixing this, but it'll take a while since I'll
> >have to set up a suitable Debian VM for testing first.
>
> docker run -it --rm debian:sid
>
> adjust /etc/apt/sources.list to include deb-src entries
>
> apt-get update
> apt-get build-dep cmtk
>
> and you should be all set ;)
>
> --
> Yaroslav O. Halchenko
> Center for Open Neuroscience http://centerforopenneuroscience.org
> Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
> Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
> WWW:   http://www.linkedin.com/in/yarik
>

Bug#914147: marked as done (libkolabxml FTBFS: symbol differences)

[Debian Bug Tracking System]

Your message dated Tue, 22 Jan 2019 05:04:15 +
with message-id 
and subject line Bug#914147: fixed in libkolabxml 1.1.6-3.1
has caused the Debian Bug report #914147,
regarding libkolabxml FTBFS: symbol differences
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.)


-- 
914147: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914147
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libkolabxml
Version: 1.1.6-3
Severity: serious
Tags: ftbfs

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

...
   dh_makeshlibs -a -O--buildsystem=pybuild
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libkolabxml1v5/DEBIAN/symbols doesn't match 
completely debian/libkolabxml1v5.symbols
--- debian/libkolabxml1v5.symbols (libkolabxml1v5_1.1.6-3+b2_amd64)
+++ dpkg-gensymbolsIUxgTb   2018-11-16 17:42:07.534213410 +
@@ -3937,6 +3937,8 @@
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_014TznamePropTypeEEC2EPKcS7_S7_S7_@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_014TznamePropTypeEED1Ev@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_014TznamePropTypeEED2Ev@Base
 1.1.0
+ 
_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015AltrepParamTypeEEC1EPKcS7_S7_S7_@Base
 1.1.6-3+b2
+ 
_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015AltrepParamTypeEEC2EPKcS7_S7_S7_@Base
 1.1.6-3+b2
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015AltrepParamTypeEED1Ev@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015AltrepParamTypeEED2Ev@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015CommentPropTypeEEC1EPKcS7_S7_S7_@Base
 1.1.0
@@ -3951,8 +3953,8 @@
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015CreatedPropTypeEEC2EPKcS7_S7_S7_@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015CreatedPropTypeEED1Ev@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015CreatedPropTypeEED2Ev@Base
 1.1.0
- (optional=templinst|arch=amd64 
kfreebsd-amd64)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015CutypeParamTypeEEC1EPKcS7_S7_S7_@Base
 1.1.6
- (optional=templinst|arch=amd64 
kfreebsd-amd64)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015CutypeParamTypeEEC2EPKcS7_S7_S7_@Base
 1.1.6
+#MISSING: 1.1.6-3+b2# (optional=templinst|arch=amd64 
kfreebsd-amd64)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015CutypeParamTypeEEC1EPKcS7_S7_S7_@Base
 1.1.6
+#MISSING: 1.1.6-3+b2# (optional=templinst|arch=amd64 
kfreebsd-amd64)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015CutypeParamTypeEEC2EPKcS7_S7_S7_@Base
 1.1.6
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015CutypeParamTypeEED1Ev@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015CutypeParamTypeEED2Ev@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree27element_factory_initializerILm0EcN13icalendar_2_015DtstampPropTypeEEC1EPKcS7_S7_S7_@Base
 1.1.0
@@ -4395,8 +4397,8 @@
  (optional=templinst|arch=!amd64 !hppa 
!kfreebsd-amd64)_ZN3xsd3cxx4tree30element_serializer_initializerILm0EcN13icalendar_2_011UidPropTypeEEC2EPKcS7_S7_S7_@Base
 1.1.6
  
(optional=templinst)_ZN3xsd3cxx4tree30element_serializer_initializerILm0EcN13icalendar_2_011UidPropTypeEED1Ev@Base
 1.1.0
  
(optional=templinst)_ZN3xsd3cxx4tree30element_serializer_initializerILm0EcN13icalendar_2_011UidPropTypeEED2Ev@Base
 1.1.0
- (optional=templinst|arch=!alpha !armel !armhf !hppa !mips64el !ppc64el 
!sparc64)_ZN3xsd3cxx4tree30element_serializer_initializerILm0EcN13icalendar_2_011UrlPropTypeEEC1EPKcS7_S7_S7_@Base
 1.1.0
- (optional=templinst|arch=!alpha !armel !armhf !hppa !mips64el !ppc64el 
!sparc64)_ZN3xsd3cxx4tree30element_serializer_initializerILm0EcN13icalendar_2_011UrlPropTypeEEC2EPKcS7_S7_S7_@Base
 1.1.0
+#MISSING: 1.1.6-3+b2# (optional=templinst|arch=!alpha !armel !armhf !hppa 
!mips64el !ppc64el 

Bug#919917: yui-compressor: insufficient java dependency in jessie

[tony mancill]

On Sun, Jan 20, 2019 at 06:14:31PM +0100, Andreas Beckmann wrote:
> Package: yui-compressor
> Version: 2.4.7-2
> Severity: serious
> Tags: jessie
> User: debian...@lists.debian.org
> Usertags: piuparts
> Control: affects -1 + libjs-protoaculous
> Control: found -1 libjs-protoaculous/5

Hi Andreas,

The version of the package in the bug is found in jessie (oldstable)
and doesn't exist in stretch (stable) or buster (testing).  Also, I
believe the problem is with the version of default-jre-headless in
jessie, given that the Depends hasn't changed since 2012.

Are you requesting that the bug be addressed for jessie?  (Do we need to
open a RC-severity bug for oldstable right before the buster freeze?)

Thanks,
tony


signature.asc
Description: PGP signature

Bug#919727: cmtk /dcmtk

[Yaroslav Halchenko]

On Mon, 21 Jan 2019, Torsten Rohlfing wrote:

>Hi there -
>Upstream owner of CMTK here. It looks like DCMTK in release 3.6.4 changed
>their API for locking/unlocking the global data dictionary.
>I am going to look into fixing this, but it'll take a while since I'll
>have to set up a suitable Debian VM for testing first.

docker run -it --rm debian:sid

adjust /etc/apt/sources.list to include deb-src entries

apt-get update
apt-get build-dep cmtk

and you should be all set ;)

-- 
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834   Fax: +1 (603) 646-1419
WWW:   http://www.linkedin.com/in/yarik

Processed: Re: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

[Debian Bug Tracking System]

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

> tags 919296 - patch pending
Bug #919296 [git-daemon-run] git-daemon-run: fails with 'warning: git-daemon: 
unable to open supervise/ok: file does not exist'
Removed tag(s) patch and pending.
> quit
Stopping processing here.

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

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

[Jonathan Nieder]

tags 919296 - patch pending
quit

Jonathan Nieder wrote:

> For "buster", I prefer a minimal fix within the framework of the
> current packages, along the lines you suggested upthread:
>
> diff --git i/debian/changelog w/debian/changelog
> index ef513b2e1d..fb996c91f4 100644
> --- i/debian/changelog
> +++ w/debian/changelog
> @@ -3,6 +3,9 @@ git (1:2.20.1-1.1) unstable; urgency=low
>* package git-gui: actually Suggests: meld for mergetool support;
>  describe what meld is used for in package description (thx Jens
>  Reyer; closes: #707790).
> +  * git-daemon-run: pre-create supervise directory so that postinst
> +can start the service (thx Celejar and Dmitry Bogatov; closes:
> +#919296).
>  
>   -- Jonathan Nieder   Mon, 21 Jan 2019 19:36:25 -0800
>  
> diff --git i/debian/git-daemon-run.dirs w/debian/git-daemon-run.dirs
> index 7847e85525..0e62ab6ac0 100644
> --- i/debian/git-daemon-run.dirs
> +++ w/debian/git-daemon-run.dirs
> @@ -1 +1,2 @@
>  etc/sv/git-daemon/log
> +var/lib/supervise/git-daemon

Unfortunately, this doesn't work.  /var/lib/supervise/git-daemon ought
to contain a definition of a supervise service, whereas this produces
an empty directory so it still fails.

Do you have more details?  Why was this approach expected to work, and
where can I read more about what changed in runit and how to
appropriately adjust this package to handle the changes?

Thanks,
Jonathan

Bug#919296: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

[Jonathan Nieder]

found 919296 git/1:2.20.1-1
tags 919296 + patch pending
quit

Hi Dmitry,

Dmitry Bogatov wrote:
> [2019-01-16 14:49] Dmitry Bogatov 

>> So, should I propose you patch (in 7 days), that merges
>> bin:git-daemon-run into bin:git-daemon, would you be able to review
>> and apply/upload it before hard freeze?
>
> Probably, even better would be to merge `git-daemon-run' and
> `git-daemon-sysvinit'. What do you think?

For "buster", I prefer a minimal fix within the framework of the
current packages, along the lines you suggested upthread:

diff --git i/debian/changelog w/debian/changelog
index ef513b2e1d..fb996c91f4 100644
--- i/debian/changelog
+++ w/debian/changelog
@@ -3,6 +3,9 @@ git (1:2.20.1-1.1) unstable; urgency=low
   * package git-gui: actually Suggests: meld for mergetool support;
 describe what meld is used for in package description (thx Jens
 Reyer; closes: #707790).
+  * git-daemon-run: pre-create supervise directory so that postinst
+can start the service (thx Celejar and Dmitry Bogatov; closes:
+#919296).
 
  -- Jonathan Nieder   Mon, 21 Jan 2019 19:36:25 -0800
 
diff --git i/debian/git-daemon-run.dirs w/debian/git-daemon-run.dirs
index 7847e85525..0e62ab6ac0 100644
--- i/debian/git-daemon-run.dirs
+++ w/debian/git-daemon-run.dirs
@@ -1 +1,2 @@
 etc/sv/git-daemon/log
+var/lib/supervise/git-daemon

By the way, was there a change in runit precipitating this regression?
I'm wondering so that we can set up the right dependencies (e.g. a
versioned Breaks from runit) to ensure upgrades proceed smoothly.

This way, the same behavior as the previous release will persist for
users expecting it (in particular, allowing users to easily decide
which configuration will control their running daemon --- see [1] for
more context).  That said, I'm happy to pursue a merge of the packages
into a git-daemon package in experimental in preparation for buster+1,
especially if there's a standard for runit service packaging that we
can follow there.

Thanks again for your help.

[1] http://bugs.debian.org/422139#121

Processed: Re: git-daemon-run: fails with 'warning: git-daemon: unable to open supervise/ok: file does not exist'

[Debian Bug Tracking System]

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

> found 919296 git/1:2.20.1-1
Bug #919296 [git-daemon-run] git-daemon-run: fails with 'warning: git-daemon: 
unable to open supervise/ok: file does not exist'
Marked as found in versions git/1:2.20.1-1.
> tags 919296 + patch pending
Bug #919296 [git-daemon-run] git-daemon-run: fails with 'warning: git-daemon: 
unable to open supervise/ok: file does not exist'
Added tag(s) pending and patch.
> quit
Stopping processing here.

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

Bug#920136: libgnutls30: symbol lookup error...undefined symbol: __gmpz_limbs_write

[James Van Zandt]

Package: libgnutls30
Version: 3.6.5-2
Severity: critical
Justification: breaks unrelated software

Dear Maintainer,


Sun 20 Jan 2019 10:25:49 PM EST

I upgraded several packages on Jan 16.  Since then, many programs
(including cupsd, apt-get, and apt) fail like this:

  /usr/lib/apt/methods/http: symbol lookup error:
/usr/lib/x86_64-linux-gnu/libgnutls.so.30: undefined symbol:
__gmpz_limbs_write

The file comes in this package:
  libgnutls30: /usr/lib/x86_64-linux-gnu/libgnutls.so.30

I have two copies of this package installed:
  jrv@home:/usr/local/src/octave/octave-4.4.1$ dpkg -l libgnutls30
  Desired=Unknown/Install/Remove/Purge/Hold
  |
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name  Version  Architecture Description

+++-=---==
  ii  libgnutls30:amd64 3.6.5-2  amd64GNU TLS library - main
runtime library
  ii  libgnutls30:i386  3.6.5-2  i386 GNU TLS library - main
runtime library

...corresponding to the two architectures installed here:

  jrv@home:~/Downloads$ dpkg --print-architecture
  amd64
  jrv@home:~/Downloads$ dpkg --print-foreign-architectures
  i386


I found a partial workaround, as follows:

I found libgnutls30 packages of version 3.5.19 in my backups.
Installing just the amd64 package (with dpkg) failed:
  package libgnutls30:amd64 3.5.19-1 cannot be configured because
libgnutls30:i386 is at a different version (3.6.5-2)

However, installing both architectures together succeeded:
  $ dpkg -l libgnutls30
  Desired=Unknown/Install/Remove/Purge/Hold
  |
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name  Version  Architecture Description

+++-=---==
  ii  libgnutls30:amd64 3.5.19-1 amd64GNU TLS library - main
runtime library
  ii  libgnutls30:i386  3.5.19-1 i386 GNU TLS library - main
runtime library

cupsd will now run (so I can print again).

apt-get also runs, but complains about versions being out of sync:

  $ sudo apt-get check
  [sudo] password for jrv:
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   apt : Depends: libgnutls30 (>= 3.6.5) but 3.5.19-1 is installed
   exim4-daemon-light : Depends: libgnutls30 (>= 3.6.5) but 3.5.19-1 is
installed
   glib-networking : Depends: libgnutls30 (>= 3.6.5) but 3.5.19-1 is
installed
   libavformat58 : Depends: libgnutls30 (>= 3.6.5) but 3.5.19-1 is installed
   libgnutls-dane0 : Depends: libgnutls30 (= 3.6.5-2) but 3.5.19-1 is
installed
   libgnutls-openssl27 : Depends: libgnutls30 (= 3.6.5-2) but 3.5.19-1 is
installed
   libgnutls28-dev : Depends: libgnutls30 (= 3.6.5-2) but 3.5.19-1 is
installed
   libgnutlsxx28 : Depends: libgnutls30 (= 3.6.5-2) but 3.5.19-1 is
installed
   libimobiledevice-utils : Depends: libgnutls30 (>= 3.6.5) but 3.5.19-1 is
installed
   libimobiledevice6 : Depends: libgnutls30 (>= 3.6.5) but 3.5.19-1 is
installed
   libldap-2.4-2 : Depends: libgnutls30 (>= 3.6.5) but 3.5.19-1 is installed
   libvirt-clients : Depends: libgnutls30 (>= 3.6.5) but 3.5.19-1 is
installed
   libvirt-daemon : Depends: libgnutls30 (>= 3.6.5) but 3.5.19-1 is
installed
   libvirt-daemon-system : Depends: libgnutls30 (>= 3.6.5) but 3.5.19-1 is
installed
   libvirt0 : Depends: libgnutls30 (>= 3.6.5) but 3.5.19-1 is installed
   libvte-2.91-0 : Depends: libgnutls30 (>= 3.6.5) but 3.5.19-1 is installed
   python-pycurl : Depends: libgnutls30 (>= 3.6.5) but 3.5.19-1 is installed
   python3-pycurl : Depends: libgnutls30 (>= 3.6.5) but 3.5.19-1 is
installed
   qemu-utils : Depends: libgnutls30 (>= 3.6.5) but 3.5.19-1 is installed
   samba-libs : Depends: libgnutls30 (>= 3.6.5) but 3.5.19-1 is installed
   systemd : Depends: libgnutls30 (>= 3.6.5) but 3.5.19-1 is installed
   wget : Depends: libgnutls30 (>= 3.6.5) but 3.5.19-1 is installed
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages
(or specify a solution).


I suspect a missing dependency, but I've not been able to identify it.
Evidently some libraries are out of sync, but I can't be sure which package
should be held responsible.  Since apt-get is affected, I think the problem
qualifies as "critical".


My attempts to track down the problem follow...

>From /var/log/history.log, those packages were upgraded on Jan 16:

  Start-Date: 2019-01-14  20:53:51
  Commandline: apt-get upgrade
  Requested-By: jrv (1000)
  Upgrade: ... libgnutls30:amd64 (3.5.19-1+b1, 3.6.5-2), libgnutls30:i386
(3.5.19-1+b1, 3.6.5-2) ...

The last three backups are more recent than that upgrade:

  drwxr-xr-x 14 

Bug#919196: Debian bug when running unit tests

[Pierre-Elliott Bécue]

Le lundi 21 janvier 2019 à 14:37:36+0100, Thomas Goirand a écrit :
> Hi,
> 
> Would you have any idea how to resolve this Debian bug?
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919196
> 
> I'm not sure, but to me, it looks like the unit tests are running in
> loop in the ::handshake() method.

The handshake fails, because gnutls doesn't accept the security level
offered by the handshake.

It seems to me the issue is in the next test: t->send is called, and
send is defined as a looping function until the decrypted content is
received. As the handshake previously failed, t->send waits forever.

I guess the tests should have a timeout method.

Anyway, increasing the security of the handshake would make it work and
hence the current issue should be gone.

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Bug#919196: Debian bug when running unit tests

[Pierre-Elliott Bécue]

Le mardi 22 janvier 2019 à 01:57:22+0100, Pierre-Elliott Bécue a écrit :
> Le lundi 21 janvier 2019 à 14:37:36+0100, Thomas Goirand a écrit :
> > Hi,
> > 
> > Would you have any idea how to resolve this Debian bug?
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919196
> > 
> > I'm not sure, but to me, it looks like the unit tests are running in
> > loop in the ::handshake() method.
> 
> The handshake fails, because gnutls doesn't accept the security level
> offered by the handshake.
> 
> It seems to me the issue is in the next test: t->send is called, and
> send is defined as a looping function until the decrypted content is
> received. As the handshake previously failed, t->send waits forever.
> 
> I guess the tests should have a timeout method.
> 
> Anyway, increasing the security of the handshake would make it work and
> hence the current issue should be gone.

I found out that a new upstream release includes fixes the security
issue I mentioned before. Attempting to build this release works fine
and the tests are passing without hanging.

I'm not certain whether the fix is due to the addition of
'gnutls_certificate_set_x509_system_trust( m_credentials );' to
tlsgnutlsclient.cpp or to the changes made to
'gnutls_priority_set_direct' in tlsgnutls{server,client}anon.cpp.

This looks good to me.

Vincent, I made a NMU branch which is just a fast-forward of master on
the salsa repo[0]. The branch name is 1.0.22-0.1

If you agree, I shall do an upload. Otherwise I'll let you taking care
of it.

Best regards,

[0] https://salsa.debian.org/debian/gloox/commits/1.0.22-0.1

-- 
Pierre-Elliott Bécue
GPG: 9AE0 4D98 6400 E3B6 7528  F493 0D44 2664 1949 74E2
It's far easier to fight for one's principles than to live up to them.


signature.asc
Description: PGP signature

Processed: bug 841494 is forwarded to https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24659 ...

[Debian Bug Tracking System]

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

> # bts-link: follow the redirect
> forwarded 841494 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24659
Bug #841494 [guile-1.8] guile-1.8: CVE-2016-8605: Thread-unsafe umask 
modification
Changed Bug forwarded-to-address to 
'https://debbugs.gnu.org/cgi/bugreport.cgi?bug=24659' from 
'http://bugs.gnu.org/24659'.
> forwarded 875449 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=28350
Bug #875449 [src:emacs23] emacs23: CVE-2017-14482: enriched text remote code 
execution
Changed Bug forwarded-to-address to 
'https://debbugs.gnu.org/cgi/bugreport.cgi?bug=28350' from 
'https://bugs.gnu.org/28350'.
> forwarded 875448 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=28350
Bug #875448 [src:emacs24] emacs24: CVE-2017-14482: enriched text remote code 
execution
Changed Bug forwarded-to-address to 
'https://debbugs.gnu.org/cgi/bugreport.cgi?bug=28350' from 
'https://bugs.gnu.org/28350'.
> thanks
Stopping processing here.

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

Bug#919727: cmtk /dcmtk

[Torsten Rohlfing]

Hi there -

Upstream owner of CMTK here. It looks like DCMTK in release 3.6.4 changed
their API for locking/unlocking the global data dictionary.

I am going to look into fixing this, but it'll take a while since I'll have
to set up a suitable Debian VM for testing first.

Best,
  Torsten

Bug#919158: Bug #919158 in mailman-suite marked as pending

[Pierre-Elliott Bécue]

Control: tag -1 pending

Hello,

Bug #919158 in mailman-suite 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/mailman-team/mailman-suite/commit/b3e8167f08db7a87293271e8732250fb47b98cd7


d/mailman3-web.cron.d refactored

Use /u/s/mailman3-web/manage.py instead of a call to django-admin and use flock 
to avoid piling up cron processes.

Closes: #919158


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/919158

Processed: Bug #919158 in mailman-suite marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #919158 [mailman3-web] mailman3-web: cronjobs should be run with flock to 
avoid them running amok
Added tag(s) pending.

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

Bug#919174: marked as done (ruby-sinatra FTBFS with ruby-haml 5.0.4-1)

[Debian Bug Tracking System]

Your message dated Mon, 21 Jan 2019 23:21:56 +
with message-id 
and subject line Bug#919174: fixed in ruby-sinatra 2.0.5-4
has caused the Debian Bug report #919174,
regarding ruby-sinatra FTBFS with ruby-haml 5.0.4-1
to be marked as done.

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

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


-- 
919174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919174
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-sinatra
Version: 2.0.5-3
Severity: serious
Tags: ftbfs

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

...
  1) Failure:
HAMLTest#test_renders_with_file_layouts_0 
[/build/1st/ruby-sinatra-2.0.5/test/haml_test.rb:40]:
--- expected
+++ actual
@@ -1,3 +1,4 @@
 "HAML Layout!
-Hello World
+Hello World
+
 "


  2) Failure:
HAMLTest#test_renders_with_inline_layouts_0 
[/build/1st/ruby-sinatra-2.0.5/test/haml_test.rb:34]:
--- expected
+++ actual
@@ -1,2 +1,3 @@
-"THIS. IS. SPARTA
+"THIS. IS. SPARTA
+
 "


1062 runs, 2424 assertions, 2 failures, 0 errors, 0 skips
--- End Message ---
--- Begin Message ---
Source: ruby-sinatra
Source-Version: 2.0.5-4

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

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

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

Debian distribution maintenance software
pp.
Antonio Terceiro  (supplier of updated ruby-sinatra 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 21 Jan 2019 19:02:20 -0200
Source: ruby-sinatra
Binary: ruby-sinatra ruby-sinatra-contrib ruby-rack-protection
Architecture: source
Version: 2.0.5-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Extras Maintainers 

Changed-By: Antonio Terceiro 
Description:
 ruby-rack-protection - Protects against typical web attacks for Rack apps
 ruby-sinatra - Ruby web-development dressed in a DSL
 ruby-sinatra-contrib - collection of useful extensions to the Sinatra web 
framework
Closes: 919174
Changes:
 ruby-sinatra (2.0.5-4) unstable; urgency=medium
 .
   * Team upload.
   * Add 0003-test_haml-update-for-haml-5.patch to make tests pass against
 ruby-haml >= 5 (Closes: #919174)
Checksums-Sha1:
 0bd9258e3ea20fe4970f148b05207dae695895af 2942 ruby-sinatra_2.0.5-4.dsc
 160b22dbf8d1548e8e14bfe58d2fb7d45ff81312 6612 
ruby-sinatra_2.0.5-4.debian.tar.xz
 8a775cced89877c7900811ec1bc499957d1fa351 14782 
ruby-sinatra_2.0.5-4_source.buildinfo
Checksums-Sha256:
 d9986f04184db6e029ca9e4fc30e60b842eb6280c2d27ee11dce7e34106ee09a 2942 
ruby-sinatra_2.0.5-4.dsc
 22450d7de775f9dd6c1d78a2a1421b090e1c13641ee6f5737ff5153b58a287d6 6612 
ruby-sinatra_2.0.5-4.debian.tar.xz
 7dc58e84b2a72accb782ae404fe9db1f9c16e418435405acdd6c1fd8936c5527 14782 
ruby-sinatra_2.0.5-4_source.buildinfo
Files:
 f837cf0b15761e2ad3286a540c116997 2942 ruby optional ruby-sinatra_2.0.5-4.dsc
 ad816046f388e7af5fd8f5bbaccbd6c0 6612 ruby optional 
ruby-sinatra_2.0.5-4.debian.tar.xz
 0eba3ff9ef06bafe7f4edc3cd6da94e8 14782 ruby optional 
ruby-sinatra_2.0.5-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlxGUYYACgkQ/A2xu81G
C94Bgg//UUJWQiXiR5qFb7T63H1FKQTd2tYHN+BYVWXWFQeVOWWUL/U4Wg6CuqSJ
OlKFx9WTfn0NzYWb7r/zbnVhOLui3Auljc9Z4hNBgNL0haGPhbEKq1QGBboAOww7
u2km+OfGN2w4BWxZPkz6bxlLLX1a5agXMNeb6c23XTzKOZLmofWPE2alW1oUwh+G
yoCvEzv000XIZ9x5HUNjvYYrhvW2+5Zb40BitLEsEYz/KEf4tAI9KKJkEo1J4/AJ
mKUgQX1tf35nMfCuyXwTQ6zONnJDUWWx6R1ydqI5gf9G8l/0RIWfpqhGfE3QUf5z
72o01BRKwa2+pLpRXc7FYMsb83ZJIKjCfz9T/cyfnpcbWdMNb0bvcCMrCwvE6ChN
bEtcl9eyV6R0SoJhCAcW+h+PG6nW1j6gI8zlM4dCVW9cmTwVpfPn8edPm5eyi6TC
ogtmlSuQ1lzyW5kdUSQuHDkZojzSLbrInDKw8PotdvxJyk1nuQUK/S7eV2x53BNp
i6SKgDdRcW5oHIRjvRIDMZbHld4pajv0afLgqWEQ02ypCrf1h1qmL9TCDrLGZ3zv
nf6/8JJsvx9CUrDAoI4Jwe7AL32Kb2yq0ODpSdqrepcBMD/1Zy8dTSEEHnYYfiMc
31a2EXUfd5FSvzqwh+qBMtUFnzCqsSajjC+SYdPijtPZeqlo6yM=
=phSd
-END PGP SIGNATURE End Message ---

Bug#910295: Bug#920019: duplicate of bug#910295 (dput: FTBFS: tests fail to mock HTTP request)

[Ben Finney]

Control: found -1 dput/1.0.2
Control: block -1 by 919599
Control: summary 920019 The HTTPretty library is failing to mock requests from 
Python's HTTPConnection.
Control: outlook 920019 Either correct the HTTPretty library; or re-work the 
DPut test cases to avoid HTTPretty.
Control: forcemerge -1 920019

On 21-Jan-2019, Debian Bug Tracking System wrote:
> > merge 910295 -1
> Bug #910295 [dput] dput: FTBFS: tests fail to mock HTTP request
> Unable to merge bugs because:
> blockedby of #920019 is '' not '919599'
> summary of #920019 is '' not 'The HTTPretty library is failing to mock 
> requests from Python's HTTPConnection.'
> outlook of #920019 is '' not 'Either correct the HTTPretty library; or 
> re-work the DPut test cases to avoid HTTPretty.'
> Failed to merge 910295: Did not alter merged bugs.

-- 
 \  “Anyone who believes exponential growth can go on forever in a |
  `\finite world is either a madman or an economist.” —Kenneth |
_o__)   Boulding, 1973 |
Ben Finney 

Processed: Bug #919174 in ruby-sinatra marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #919174 [src:ruby-sinatra] ruby-sinatra FTBFS with ruby-haml 5.0.4-1
Added tag(s) pending.

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

Bug#919174: Bug #919174 in ruby-sinatra marked as pending

[Antonio Terceiro]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ruby-team/ruby-sinatra/commit/ceb6c62605883541986d4a117e5fccf0dcd3de6f


make tests pass against ruby-haml >= 5

Closes: #919174


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/919174

Processed: Bug#920019: duplicate of bug#910295 (dput: FTBFS: tests fail to mock HTTP request)

[Debian Bug Tracking System]

Processing control commands:

> found -1 dput/1.0.2
Bug #910295 [dput] dput: FTBFS: tests fail to mock HTTP request
Marked as found in versions dput/1.0.2.
> block -1 by 919599
Bug #910295 [dput] dput: FTBFS: tests fail to mock HTTP request
910295 was blocked by: 919599
910295 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #910295 to the same blocks 
previously set
> summary 920019 The HTTPretty library is failing to mock requests from 
> Python's HTTPConnection.
Summary recorded from message bug 920019 message 
> outlook 920019 Either correct the HTTPretty library; or re-work the DPut test 
> cases to avoid HTTPretty.
Outlook recorded from message bug 920019 message 
> forcemerge -1 920019
Bug #910295 [dput] dput: FTBFS: tests fail to mock HTTP request
Bug #920019 [dput] dput fails to build on test errors
920019 was not blocked by any bugs.
920019 was not blocking any bugs.
Added blocking bug(s) of 920019: 919599
Added tag(s) ftbfs, sid, confirmed, and buster.
Bug #910295 [dput] dput: FTBFS: tests fail to mock HTTP request
Added tag(s) moreinfo.
Merged 910295 920019

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

Bug#917500: marked as done (liggghts: FTBFS (style_atom.h: No such file or directory))

[Debian Bug Tracking System]

Your message dated Mon, 21 Jan 2019 23:06:01 +
with message-id 
and subject line Bug#917500: fixed in liggghts 3.8.0+repack1-3
has caused the Debian Bug report #917500,
regarding liggghts: FTBFS (style_atom.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.)


-- 
917500: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917500
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:liggghts
Version: 3.8.0+repack1-1
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --buildsystem=cmake 
--builddirectory=/<>/liggghts-3.8.0+repack1/debian/build
   dh_update_autotools_config -i -O--buildsystem=cmake 
-O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build
   dh_autoreconf -i -O--buildsystem=cmake 
-O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build
   dh_auto_configure -i -O--buildsystem=cmake 
-O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build
cd debian/build && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ../..
-- The C compiler identification is GNU 8.2.0
-- The CXX compiler identification is GNU 8.2.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done

[... snipped ...]

CMAKE_EXPORT_NO_PACKAGE_REGISTRY


-- Build files have been written to: 
/<>/liggghts-3.8.0+repack1/debian/build
   dh_auto_build -i -O--buildsystem=cmake 
-O--builddirectory=/<>/liggghts-3.8.0\+repack1/debian/build
cd debian/build && make -j1 "INSTALL=install --strip-program=true"
make[1]: Entering directory '/<>/liggghts-3.8.0+repack1/debian/build'
/usr/bin/cmake -S/<>/liggghts-3.8.0+repack1 
-B/<>/liggghts-3.8.0+repack1/debian/build --check-build-system 
CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start 
/<>/liggghts-3.8.0+repack1/debian/build/CMakeFiles 
/<>/liggghts-3.8.0+repack1/debian/build/CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<>/liggghts-3.8.0+repack1/debian/build'
make -f src/CMakeFiles/libliggghts.dir/build.make 
src/CMakeFiles/libliggghts.dir/depend
make[3]: Entering directory '/<>/liggghts-3.8.0+repack1/debian/build'
cd /<>/liggghts-3.8.0+repack1/debian/build && /usr/bin/cmake -E 
cmake_depends "Unix Makefiles" /<>/liggghts-3.8.0+repack1 
/<>/liggghts-3.8.0+repack1/src 
/<>/liggghts-3.8.0+repack1/debian/build 
/<>/liggghts-3.8.0+repack1/debian/build/src 
/<>/liggghts-3.8.0+repack1/debian/build/src/CMakeFiles/libliggghts.dir/DependInfo.cmake
 --color=
Scanning dependencies of target libliggghts
make[3]: Leaving directory '/<>/liggghts-3.8.0+repack1/debian/build'
make -f src/CMakeFiles/libliggghts.dir/build.make 
src/CMakeFiles/libliggghts.dir/build
make[3]: Entering directory '/<>/liggghts-3.8.0+repack1/debian/build'
[  0%] Building CXX object src/CMakeFiles/libliggghts.dir/angle.cpp.o
cd /<>/liggghts-3.8.0+repack1/debian/build/src && /usr/bin/mpicxx  
-Dlibliggghts_EXPORTS -DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkIOParallel_AUTOINIT="1(vtkIOMPIParallel)" 
-DvtkRenderingCore_AUTOINIT="3(vtkInteractionStyle,vtkRenderingFreeType,vtkRenderingOpenGL)"
 -I/usr/include/vtk-6.3 -I/usr/include/freetype2 
-I/usr/include/x86_64-linux-gnu -I/usr/include/hdf5/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi 
-I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/include/jsoncpp 
-I/usr/include/eigen3 -I/<>/liggghts-3.8.0+repack1 
-I/<>/liggghts-3.8.0+repack1/src  -g -O2 
-fdebug-prefix-map=/<>/liggghts-3.8.0+repack1=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -DLAMMPS_VTK6 -DLAMMPS_VTK -std=c++0x -DLAMMPS_JPEG -fPIC  
 -o CMakeFiles/libliggghts.dir/angle.cpp.o -c 
/<>/liggghts-3.8.0+repack1/src/angle.cpp
[  0%] Building CXX object src/CMakeFiles/libliggghts.dir/angle_hybrid.cpp.o
cd /<>/liggghts-3.8.0+repack1/debian/build/src && /usr/bin/mpicxx  
-Dlibliggghts_EXPORTS -DvtkIOGeometry_AUTOINIT="1(vtkIOMPIParallel)" 

Bug#912476: marked as done (libapache-poi-java: FTBFS with Java 11 due to JAXB removal)

[Debian Bug Tracking System]

Your message dated Mon, 21 Jan 2019 23:05:33 +
with message-id 
and subject line Bug#912476: fixed in libapache-poi-java 4.0.1-1
has caused the Debian Bug report #912476,
regarding libapache-poi-java: FTBFS with Java 11 due to JAXB removal
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.)


-- 
912476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912476
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: libapache-poi-java
Source-Version: 4.0.1-1

We believe that the bug 

Processed (with 1 error): Bug#920019: duplicate of bug#910295 (dput: FTBFS: tests fail to mock HTTP request)

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #920019 [dput] dput fails to build on test errors
Severity set to 'serious' from 'normal'
> reassign 910295 dput
Bug #910295 [python3-httpretty] dput: FTBFS: tests fail to mock HTTP request
Bug reassigned from package 'python3-httpretty' to 'dput'.
No longer marked as found in versions dput/1.0.2.
Ignoring request to alter fixed versions of bug #910295 to the same values 
previously set
> block 910295 by 919599
Bug #910295 [dput] dput: FTBFS: tests fail to mock HTTP request
910295 was blocked by: 919599
910295 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #910295 to the same blocks 
previously set
> merge 910295 -1
Bug #910295 [dput] dput: FTBFS: tests fail to mock HTTP request
Unable to merge bugs because:
blockedby of #920019 is '' not '919599'
summary of #920019 is '' not 'The HTTPretty library is failing to mock requests 
from Python's HTTPConnection.'
outlook of #920019 is '' not 'Either correct the HTTPretty library; or re-work 
the DPut test cases to avoid HTTPretty.'
Failed to merge 910295: Did not alter merged bugs.


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

Bug#920020: [Openjdk] Bug#920020: javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module

[Thorsten Glaser]

On Mon, 21 Jan 2019, Matthias Klose wrote:

> no, why are you exaggerating? Both the jre and the jdk are usable.

The javadoc tool isn’t, and this breaks all builds.

I’ve enacted the workaround in the meantime, even if this
goes against the documented javadoc options…

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

Bug#920028: marked as done (python3-bsddb3: ships header in /usr/include/python3.7/)

[Debian Bug Tracking System]

Your message dated Mon, 21 Jan 2019 22:52:28 +
with message-id 
and subject line Bug#920028: fixed in python-bsddb3 6.2.6-3
has caused the Debian Bug report #920028,
regarding python3-bsddb3: ships header in /usr/include/python3.7/
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.)


-- 
920028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-bsddb3
Version: 6.2.6-2
Severity: serious

Hi,

your package ships the header file(s):

  /usr/include/python3.7/bsddb3/bsddb.h

but /usr/include/python3.7 is a symlink to python3.7m in
libpython3.7-dev. This may result in silent file overwrites or depending
on the unpacking order /usr/include/python3.7 being a directory in some
cases, separating the headers into two independent trees.

These header files must be shipped in /usr/include/python3.7m/ instead.
Please talk to the python maintainers to find a proper solution for
handling the packaging of python header files in a future-proof way.


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: python-bsddb3
Source-Version: 6.2.6-3

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

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

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python-bsddb3 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Mon, 21 Jan 2019 23:17:17 +0100
Source: python-bsddb3
Binary: python-bsddb3 python-bsddb3-dbg python3-bsddb3 python3-bsddb3-dbg 
python-bsddb3-doc
Architecture: source
Version: 6.2.6-3
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Description:
 python-bsddb3 - Python interface for Berkeley DB
 python-bsddb3-dbg - Python interface for Berkeley DB (debug extension)
 python-bsddb3-doc - Documentation for the python Berkeley DB interface module
 python3-bsddb3 - Python interface for Berkeley DB (Python 3.x)
 python3-bsddb3-dbg - Python interface for Berkeley DB (debug extension, Python 
3.x)
Closes: 920028
Changes:
 python-bsddb3 (6.2.6-3) unstable; urgency=medium
 .
   * Bump standards version.
   * python3-bsddb3: Fix location of include directory. Closes: #920028.
Checksums-Sha1:
 63cc4f02708b0d6274a02002ce8a0abf89e4baf9 2224 python-bsddb3_6.2.6-3.dsc
 854731e00c51aad2858cae8c4a8d515c3c42da36 8268 
python-bsddb3_6.2.6-3.debian.tar.xz
 2850f3482c71cb1d067e0f085ae434156142dc72 7602 
python-bsddb3_6.2.6-3_source.buildinfo
Checksums-Sha256:
 c929576780d9d3861336f744c5e0b9005128c27563e3b0df598bec5bdd7d4d3f 2224 
python-bsddb3_6.2.6-3.dsc
 59b12c49250d11af6c965f52b1488a659284c0504d4a97416e0892fb36a4f0a3 8268 
python-bsddb3_6.2.6-3.debian.tar.xz
 7b280f8f78e230aa4d9e1238afdb3c3aa4c216641202442986bddc9b0fbece19 7602 
python-bsddb3_6.2.6-3_source.buildinfo
Files:
 4e303c1339756776d1e44649297385bc 2224 python optional python-bsddb3_6.2.6-3.dsc
 fb41e0a461d84b6e074cd5e597d2dce9 8268 python optional 
python-bsddb3_6.2.6-3.debian.tar.xz
 95634415544ff1022a642cb507a8ec4e 7602 python optional 
python-bsddb3_6.2.6-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAlxGSFsQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9R/PD/4qNzvcyFWfpY+01J7B5b6lXKyDDqiy4BrX
Q3BS/9YMb1x2R9LiLkbvu9ltIoR32FNTIwVRArC6GqK6vbMg/w+TwoXuKRFmCdcW
ArU/k3GrSzkFKo0N4bpAUWsgO+H21/89177zNmoCVxy7aXCd1gPqzloWwiBvm3F3
/t59eXOh0dE9wH6n5zevWjcyHqstD4xIoNG0+pFFvXlpNw1gcF6yw8XptVtr2Fy/
VSQO4Gu7MxlbEBVhWgN8tpNOyQco7c+V1Fj/4Wvz+HUgxh4u4n92ZE9Su/w9M0Z4
4Cccu3AJ3ZBSGNt1m0WkUIvKsceXwiU7oC0KiaMGUroYfMdPhxJ60+waA/Yx2WLL
jqSTghRBmtGa7A4ZH1bRTsvAXTnuqOuETm26FRUVpT7rKonmyV8AWhNReKpeotiL
jGy5Gb0WhkSl7ALlG9UnRmS4I1TiIR0wxMTqm3ZdXgtlsn/3Vk5FDs95R/EUkDFL
Rvf3+BUlvJybztXwpcMxwpgJzj8NpCPl1u1WTeRexCkJ1EPMuyT749GJ3YduNvhl
dNSiFDeVyee4lL5eRwhmipdZf0eTqDa1ZKZXvLvZEL+9FXYjj+Z/7BWF856qchrE
cY15joJlFvjgahjYS86lNTMF2zDhCSHjvYjgITZIadUmPROzwpPax2Tw+78yCxK8
kwD00d+Pvg==
=nC8s
-END PGP SIGNATURE End Message ---

Bug#912476: Bug #912476 in libapache-poi-java marked as pending

[Emmanuel Bourg]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/java-team/libapache-poi-java/commit/f73c09cc8ef3e9868434c4eb2be1ee28f233528e


Build with Java 11 (Closes: #912476)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/912476

Processed: Bug #912476 in libapache-poi-java marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #912476 [src:libapache-poi-java] libapache-poi-java: FTBFS with Java 11 due 
to JAXB removal
Added tag(s) pending.

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

Bug#915514: marked as done (pysph: Missing build-dependency on python-pytest-runner, Debian builds pulling source from network?)

[Debian Bug Tracking System]

Your message dated Mon, 21 Jan 2019 22:34:50 +
with message-id 
and subject line Bug#915514: fixed in pysph 0~20180411.git1ae58e1-2.1
has caused the Debian Bug report #915514,
regarding pysph: Missing build-dependency on python-pytest-runner, Debian 
builds pulling source from network?
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.)


-- 
915514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915514
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pysph
Version: 0~20180411.git1ae58e1-2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch

Dear maintainers,

The pysph package was failing to build in Ubuntu because it is trying to hit
pypi.org at build time, and this is (intentionally) denied by the firewall
in Launchpad:

[...]
[16/16] Cythonizing pyzoltan/core/carray.pyx
Download error on https://pypi.org/simple/pytest-runner/: [Errno -2] Name or 
service not known -- Some packages may not be found!
Couldn't find index page for 'pytest-runner' (maybe misspelled?)
Download error on https://pypi.org/simple/: [Errno -2] Name or service not 
known -- Some packages may not be found!
No local packages or working download links found for pytest-runner
Traceback (most recent call last):
  File "setup.py", line 751, in 
setup_package()
  File "setup.py", line 746, in setup_package
""".splitlines() if len(c.split()) > 0],
  File "/usr/lib/python2.7/dist-packages/setuptools/__init__.py", line 139, in 
setup
_install_setup_requires(attrs)
  File "/usr/lib/python2.7/dist-packages/setuptools/__init__.py", line 134, in 
_install_setup_requires
dist.fetch_build_eggs(dist.setup_requires)
  File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 514, in 
fetch_build_eggs
replace_conflicting=True,
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 777, 
in resolve
replace_conflicting=replace_conflicting
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 1060, 
in best_match
return self.obtain(req, installer)
  File "/usr/lib/python2.7/dist-packages/pkg_resources/__init__.py", line 1072, 
in obtain
return installer(requirement)
  File "/usr/lib/python2.7/dist-packages/setuptools/dist.py", line 581, in 
fetch_build_egg
return cmd.easy_install(req)
  File "/usr/lib/python2.7/dist-packages/setuptools/command/easy_install.py", 
line 695, in easy_install
raise DistutilsError(msg)
distutils.errors.DistutilsError: Could not find suitable distribution for 
Requirement.parse('pytest-runner')
make[1]: *** [Makefile:22: build] Error 1
[...]

   (https://launchpad.net/ubuntu/+source/pysph/0~20180411.git1ae58e1-2)

Since this is listed as a requirement in setup.py, and is not pulled in as a
build dependency in Debian, I suspect the Debian builds have succeeded only
because the network is *not* filtered on the Debian builders.  In that case,
pysph's source package is not self-hosting, which is not a good thing.

I've uploaded the attached patch to Ubuntu, which fixes the build failure. 
Please consider applying it in Debian as well.

If you're able to confirm that the build failure applies to Debian also, you
might want to raise the severity of the bug report.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru pysph-0~20180411.git1ae58e1/debian/control 
pysph-0~20180411.git1ae58e1/debian/control
--- pysph-0~20180411.git1ae58e1/debian/control  2018-05-20 08:43:05.0 
-0700
+++ pysph-0~20180411.git1ae58e1/debian/control  2018-12-04 02:28:20.0 
-0800
@@ -11,6 +11,8 @@
python-mock,
python-nose,
python-numpy,
+   python-pytest,
+   python-pytest-runner,
python-sphinx,
python-sphinx-rtd-theme,
python-traits,
--- End Message ---
--- Begin Message ---
Source: pysph
Source-Version: 0~20180411.git1ae58e1-2.1

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

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

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

Bug#917500: liggghts: FTBFS (style_atom.h: No such file or directory)

[Santiago Vila]

Small update: I've given Anton Gladky access to a machine where this
seems to happen all the time. (While we are at it: Anybody reading
this willing to debug the problem in the test machine, please contact
me privately and I will gladly give you access as well).

It is interesting to see that this also fails in reproducible-builds:

https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/liggghts_3.8.0+repack1-2.rbuild.log.gz

but the way it fails is slightly different, and that's why I think it
is a Makefile bug of some kind.

I'm no CMAKE expert at all, but in our test machine, the error message
is like this:

style_atom.h: No such file or directory

So: Where is that style_atom.h file supposed to be generated and how
does the different Makefiles ensure that it's generated *before* it's
actually being used?

Thanks.

Processed: Re: BleachBit causing error since updating Firefox to Firefox Quantum 60.0 ESR

[Debian Bug Tracking System]

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

> severity 912324 important
Bug #912324 [bleachbit] BleachBit causing error since updating Firefox to 
Firefox Quantum 60.0 ESR
Severity set to 'important' from 'serious'
> fixed 912324 2.0-1
Bug #912324 [bleachbit] BleachBit causing error since updating Firefox to 
Firefox Quantum 60.0 ESR
Marked as fixed in versions bleachbit/2.0-1.
> thanks
Stopping processing here.

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

Bug#919649: axiom: /usr/lib/axiom-20170401/bin missing when package is rebuilt

[Camm Maguire]

Greetings, and thanks so much for your report!  Just a quick note now to
let you know I will be looking into this shortly!

Take care,

Juhani Numminen  writes:

> Juhani Numminen kirjoitti 18.1.2019 klo 13.15:
>> Hi again,
>> 
>> My test build just finished and I have attached the build log
>> from my pbuilder as well as the result of
>>   dpkg --contents axiom_20170501-3_amd64.deb
>> on the freshly built package.
>
> I noticed that the files I attached actually described a successful
> build with all the required files.
>
> I have now tried pbuilder with
>  1) amd64, all binary packages
>  2) amd64, arch-dependent binary packages
>  3) i386, all binary packages
> but unfortunately all those builds have produced working packages :)
>
>
> Juhani
>
>
>

-- 
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah

Bug#919321: marked as done (CVE-2019-6246)

[Debian Bug Tracking System]

Your message dated Mon, 21 Jan 2019 21:50:38 +
with message-id 
and subject line Bug#919321: fixed in svgpp 1.2.3+dfsg1-4
has caused the Debian Bug report #919321,
regarding CVE-2019-6246
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.)


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

Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6246

It will also be affected by CVE-2019-6247 and CVE-2019-6245, as agg
doesn't provide a shared library...

So make sure to add a versioned build-deps on the fixed agg when
that's done.

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: svgpp
Source-Version: 1.2.3+dfsg1-4

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Jan 2019 22:41:04 +0100
Source: svgpp
Binary: libsvgpp-dev libsvgpp-doc
Architecture: source
Version: 1.2.3+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: Anton Gladky 
Changed-By: Anton Gladky 
Description:
 libsvgpp-dev - SVG-framework with parsers for various syntaxes and adapters. 
Dev
 libsvgpp-doc - SVG-framework with parsers for various syntaxes and adapters. 
Doc
Closes: 884700 919321
Changes:
 svgpp (1.2.3+dfsg1-4) unstable; urgency=medium
 .
   [ Ondřej Nový ]
   * d/control: Deprecating priority extra as per policy 4.0.1
   * Use 'python3 -m sphinx' instead of sphinx-build for building docs
   * d/control: Remove Testsuite field, not needed anymore
   * d/control: Set Vcs-* to salsa.debian.org
 .
   [ Anton Gladky ]
   * [5d0f0bc] Fix CVE-2019-6246. (Closes: #919321)
   * [f3060a6] Set compat level 11
   * [a3e759c] Fix some privacy-breaches
 .
   [ Matthias Klose ]
   * [60dacd9] autopkg tests: Build with -g1, same as done for the build.
   (Closes: #884700)
Checksums-Sha1:
 0faa6216a5e19e3badeec9580bfdd80ad8cb1fd1 2093 svgpp_1.2.3+dfsg1-4.dsc
 d120a59a81ce3177e4076c5593bd1b7dc9e1ec44 4896 svgpp_1.2.3+dfsg1-4.debian.tar.xz
 87a5c0bf480a97548c744467b6dfac906947d21f 6307 
svgpp_1.2.3+dfsg1-4_source.buildinfo
Checksums-Sha256:
 d5a8610ad2bcb61348cdd5881eb8ab31abca6b4caf87c093bb2752a04f05fd41 2093 
svgpp_1.2.3+dfsg1-4.dsc
 249d1a7c60cc85ab3bb3a49e82ecc6648e9d0f0dc08b21c7f8d21d52a460bc41 4896 
svgpp_1.2.3+dfsg1-4.debian.tar.xz
 e127714e82fa2dd594d1dce825947faa57bf372bf6e86806fa87ac538bc2cf1f 6307 
svgpp_1.2.3+dfsg1-4_source.buildinfo
Files:
 8429a529c64f7de159576b316ec982b5 2093 libs optional svgpp_1.2.3+dfsg1-4.dsc
 02de3af9a52b1a7433139afe79e80154 4896 libs optional 
svgpp_1.2.3+dfsg1-4.debian.tar.xz
 e6c5bc349de1f0f3a49b381081608c14 6307 libs optional 
svgpp_1.2.3+dfsg1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAlxGPKgACgkQ0+Fzg8+n
/wYjhQ/+Kjdzylh0NB/OrJIbgILMwBRL1lFcEvvUGEMcVDTgxgKokQqw7cYHW3XH
oDN/sKlhuaOmOWOojzfuQlbdXus0CQt10nrBNdce967h3LuhsdeGrnvAVqCCoMu/
4GaIpy5motPkT3Yitn+sPCuOuLtBTXNoNL3hhke6AJVeDA0HNd/ZK/9PnFvv7IHJ
lIPsm3tb1Wzw2gD3KW2FvjS9YeBhYcqS6UIBK3ituRs4l+FVY4ghKdg7GPxn32l9
M22kP9w3BmyuxfD5CZM6qkSQ64RtOfVeg3hQa6teajr8OIYAcF4QUrZ7OuJBKOs1
HtCkt4Tmcd85s2pIKBoVaGlIRS1JIcebf6UwGFdJWumjdUI7ynjXn/UOxldjUpdM
H/LcKEQHQ9hx19puD71MW/2WW5GmEA35VwfW6lsdHnOIJq9jUv+bbALa+zlUIuyg
oOZE7ROSHMM6gnkpzZ/pYjpFFVjhSCiLnq+ivorabkC8ahh+yw0FyQM7+T3ULe6z
3TjXY0y3yQpIRaA0elJtAbfQFRIbHfWRqLJH7bwTrtKEjXn1ffNNLRasEGJD71ks
eoVp5q1z5XwHP2Tkch9Pr0TP2CWPdopBYRaErAMD3iSRCsQejV7KzYPShmzIS0fc
kL8Y7DLDV/rbNrkqx844tumOTzZIWKRdUhCmkkM7RGChe+EBv8o=
=03E+
-END PGP SIGNATURE End Message ---

Bug#919232: wireguard-dkms: Wireguard dkms module does not buuld against linux kernel 5.0-rc1 commit 7b55851367136b1efd84d98fea81ba57a98304cf

[Antoine Beaupre]

Control: severity -1 important

Hi!

Thank you for your bug report.

It seems to me this problem affects only builds against the 5.0-rc1
Linux kernel version. Is that correct?

Since that kernel version is not currently shipped in Debian, as far as
I know, I do not believe the severity of that bug report ("grave:
renders package unusable") is warranted.

It is still an important bug and it should be fixed when the latest
version of wireguard is packaged in Debian, according to your findings
at least, but I don't think it should be a blocker for now.

Have a nice day!

A.

On Mon, Jan 14, 2019 at 03:42:22AM +0530, Aryan Duggal wrote:
> I was able to solve the problem by temporarily compiling it from
> https://git.zx2c4.com/WireGuard and installing it
> 
> On Mon, 14 Jan 2019, 03:37 Aryan Duggal  
> > DKMS make.log for wireguard-0.0.20181218 for kernel 5.0.0-rc1+ (x86_64)
> > Sun Jan 13 21:52:56 GMT 2019
> > make: Entering directory '/usr/src/linux-headers-5.0.0-rc1+'
> >   CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/main.o
> >   CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/noise.o
> >   CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/device.o
> >   CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/peer.o
> > /var/lib/dkms/wireguard/0.0.20181218/build/noise.c: In function
> > ‘tai64n_now’:
> > /var/lib/dkms/wireguard/0.0.20181218/build/noise.c:453:2: error: implicit
> > declaration of function ‘getnstimeofday64’; did you mean ‘getnstimeofday’?
> > [-Werror=implicit-function-declaration]
> >   getnstimeofday64();
> >   ^~~~
> >   getnstimeofday
> >   CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/timers.o
> >   CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/queueing.o
> >   CC [M]  /var/lib/dkms/wireguard/0.0.20181218/build/send.o
> > cc1: some warnings being treated as errors
> > make[1]: *** [scripts/Makefile.build:277:
> > /var/lib/dkms/wireguard/0.0.20181218/build/noise.o] Error 1
> > make[1]: *** Waiting for unfinished jobs
> > make: *** [Makefile:1554:
> > _module_/var/lib/dkms/wireguard/0.0.20181218/build] Error 2
> > make: Leaving directory '/usr/src/linux-headers-5.0.0-rc1+'
> >
> > On Mon, 14 Jan 2019, 03:36 anupritaisno1  >
> >> Package: wireguard-dkms
> >> Version: 0.0.20181218-1
> >> Severity: grave
> >> Justification: renders package unusable
> >>
> >>
> >>
> >> -- System Information:
> >> Debian Release: buster/sid
> >>   APT prefers unstable
> >>   APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
> >> Architecture: amd64 (x86_64)
> >> Foreign Architectures: i386, i686
> >>
> >> Kernel: Linux 5.0.0-rc1+ (SMP w/4 CPU cores)
> >> Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8
> >> (charmap=UTF-8)
> >> Shell: /bin/sh linked to /bin/dash
> >> Init: systemd (via /run/systemd/system)
> >> LSM: AppArmor: enabled
> >>
> >> Versions of packages wireguard-dkms depends on:
> >> ii  dkms  2.6.1-3
> >>
> >> Versions of packages wireguard-dkms recommends:
> >> ii  wireguard-tools  0.0.20181218-1
> >>
> >> wireguard-dkms suggests no packages.
> >>
> >> -- no debconf information
> >>
> >

-- 
Either you're with us or you're with the terrorist state.


signature.asc
Description: PGP signature

Processed: Re: Bug#919232: wireguard-dkms: Wireguard dkms module does not buuld against linux kernel 5.0-rc1 commit 7b55851367136b1efd84d98fea81ba57a98304cf

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #919232 [wireguard-dkms] wireguard-dkms: Wireguard dkms module does not 
buuld against linux kernel 5.0-rc1 commit 
7b55851367136b1efd84d98fea81ba57a98304cf
Severity set to 'important' from 'grave'

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

Bug#910627: xul-ext-nostalgy: Please update to upstream 0.2.36 to be compatible with TB 60+

[Moritz Mühlenhoff]

On Sat, Jan 19, 2019 at 04:18:06PM -0500, Louis-Philippe Véronneau wrote:
> Hello from the Montreal BSP!
> 
> I tested the latest release of the upstream version (0.2.36) and it
> worked fine for me on the latest Thunderbird in testing.
> 
> I migrated the nostalgy VCS from the Alioth archive to Salsa and updated
> it to the latest release: https://salsa.debian.org/webext-team/nostalgy
> 
> After testing it, everything seems to work for me. I asked
> anar...@debian.org to upload it to the archive.

Note that the original bug report is for Stretch. Are you also planning
to update stable as well?

Cheers,
Moritz

Bug#920027: ships headers in /usr/include/python3.7/

[Chris Lamb]

Hi,

> your package ships the header file(s):

FYI this will be explicitly detected and reported on in lintian
2.5.123 in the package-contains-python-header-in-incorrect-
directory tag.


Regards,

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

Bug#919971: node-rollup-pluginutils: autopkgtestsuite failure

[Julien Puydt]

Hi,

I had not updated this package precisely because I couldn't get the 
autopkgtestsuite to run properly :


https://github.com/rollup/rollup-pluginutils/issues/38

If you have a fix, that's a good news.

I might have the time to have a look in two days ; if you're in a hurry, 
it's team maintained and help is welcome!


Cheers,

JP

Bug#900299: leiningen-clojure: depends on openjdk-8

[Elana Hashman]

On 2019-01-21 14:49, Moritz Mühlenhoff wrote:


We can only support one OpenJDK relase in a stable release and that 
version

will be openjdk-11. I'm bumping the severity back to serious.

Cheers,
Moritz


So here's the issue with Leiningen and Java 11. We previously tracked 
down some sort of bytecode incompatibilty problem. When Leiningen is 
built with Java 11, it seems to recompile every time it's run, leading 
to unacceptable performance, and it results in *different* help output, 
which is baffling.


Phil, have we attempted building Leiningen with Java 11 upstream?


Built with Java 8
-

elana@debian:/debian$ time lein help
Leiningen is a tool for working with Clojure projects.

...
real0m2.961s
user0m3.511s
sys 0m0.381s
elana@debian:/debian/leiningen-clojure$ sadt
..

OK (tests=2)


Built with Java 11
--

elana@debian:/debian$ time lein help
Leiningen is a tool for working with Clojure projects.
...
real0m10.659s
user0m12.258s
sys 0m0.787s
elana@debian:/debian/leiningen-clojure$ sadt
.F
==
FAIL: test-lein (exit code: 1)

FAILED (tests=2, failures=1)
elana@debian:/debian/leiningen-clojure$ bash debian/tests/test-lein
lein check 1 failed
diff:
4c4,5
< change  Rewrite project.clj by applying a function.
---
WARNING: cat already refers to: #'clojure.core/cat in namespace: 
net.cgrand.regex, being replaced by: #'net.cgrand.regex/cat
change  Rewrite project.clj with f applied to the value at 
key-or-path.

6,7c7,8
< classpath   Print the classpath of the current project.
< clean   Remove all files from project's target-path.
---
classpath   Write the classpath of the current project to 
output-file.
clean   Removes all files from paths in clean-targets for a 
project

9,10c10,11
< deploy  Build and deploy jar to remote repository.
< depsDownload all dependencies.
---

deploy  Deploy jar and pom to remote repository.
depsShow details about dependencies.

12,13c13,14
< helpDisplay a list of tasks or help for a given task.
< install Install the current project to the local 
repository.

---
helpDisplay a list of tasks or help for a given task or 
subtask.
install Install jar and pom to the local repository; 
typically ~/.m2.

16c17
< new Generate project scaffolding based on a template.
---
new Generate scaffolding for a new project based on a 
template.

19c20
< release Perform :release-tasks.
---

release Perform release tasks.

22c23
< run Run a -main function with optional command-line 
arguments.

---

run Run the project's -main function.

27c28
< uberjar Package up the project files and dependencies into 
a jar file.

---
uberjar Package up the project files and all dependencies 
into a jar file.

Bug#917884: It might be a missing dependency

[Rock Storm]

On Sat, Jan 19, 2019 at 10:19:34AM -0500, John Scott wrote:
> Hello.
> 
> I'm not the maintainer, but I replied to your bug report [1] and noticed that 
> I forgot to CC you by mistake. I'm including what I'd sent.

Hi John, thank you for sending me the e-mail directly, not only I forgot
to subscribe but I also forgot about this report. I'm so sorry.

I found a workaround to the problem by chance and I've been happily
using the mate dock since then. It turns out installing
'system-config-printer' solves the issue. So I guess one of the
following dependencies of system-config-printer is also a missing
dependency for 'mate-dock-applet':

ii  gir1.2-gdkpixbuf-2.0  2.38.0+dfsg-7
ii  gir1.2-glib-2.0   1.58.3-2
ii  gir1.2-gtk-3.03.24.3-1
ii  gir1.2-notify-0.7 0.7.7-4
ii  gir1.2-packagekitglib-1.0 1.1.12-1
ii  gir1.2-pango-1.0  1.42.4-6
ii  gir1.2-polkit-1.0 0.105-25
ii  python3   3.7.2-1
ii  python3-cups  1.9.73-2+b1
ii  python3-cupshelpers   1.5.11-4
ii  python3-dbus  1.2.8-2+b3
ii  python3-gi3.30.4-1
ii  system-config-printer-common  1.5.11-4


I suspect it is 'gir1.2-packagekitglib-1.0' but I'll leave this to the
maintainers.

> > Could you be using Wayland by any chance, like with GNOME 3? For me,
> > mate-panel crashes there regardless of applets used. Since the applet works
> > fine for me, I hope you don't mind that I reduce the bug severity.

I know it is high, but I believe the severity was correctly set as per
[1]. Whatever the problem is, it "makes the package in question
unusable".

 [1]: https://www.debian.org/Bugs/Developer#severities

> > I suggest that you try invoking mate-panel from the command-line, attempt to
> > add the applet again, and see if it gives any output that might be
> > meaningful  to be posted here.

I'd be happy to provide any feedback to debug this. Running 'mate-panel'
on the command line however does nothing (which was expected I guess).

$ mate-panel
Cannot register the panel shell: there is already one running.

How can I create a new panel from the command line?

Thanks a lot,

-- 
Rock Storm
GPG KeyID: 4096R/C96832FD
GPG Fingerprint:
 C304 34B3 632C 464C 2FAF  C741 0439 CF52 C968 32FD


signature.asc
Description: PGP signature

Bug#912324: BleachBit causing error since updating Firefox to Firefox Quantum 60.0 ESR

[Hugo Lefeuvre]

severity 912324 important
thanks

Hi,

Personal issues took me away from Debian these last weeks, I could not
take care of this issue sooner.

This is bad.

I have lowered the severity to important, but unless the release team
agrees to make an exception bleachbit will not be available in Buster
(we did not get it back in time for the soft freeze).

There is definitely no reason why bleachbit wouldn't be included in
Buster: this issue appears to affect the stretch version, not the one
from unstable.

regards,
 Hugo

-- 
Hugo Lefeuvre (hle)|www.owl.eu.com
RSA4096_ 360B 03B3 BF27 4F4D 7A3F D5E8 14AA 1EB8 A247 3DFD
ed25519_ 37B2 6D38 0B25 B8A2 6B9F 3A65 A36F 5357 5F2D DC4C


signature.asc
Description: PGP signature

Bug#920046: ruby-diaspora-federation: build-depends on ruby-faraday (< 0.10~)

[Ralf Treinen]

Package: src:ruby-diaspora-federation
Version: 0.1.4-2
Severity: serious
Tags: ftbfs
Usertags: edos-uninstallable

ruby-diaspora-federation build-depends on ruby-faraday (<< 0.10~). The
version of ruby-faraday in sid is, however, 0.13.1-2. 

-Ralf.

Bug#916468: whitedune: diff for NMU version 0.30.10-2.2

[Paul Gevers]

Control: tags -1 pending

Hi,

Pending the discussion in bug 919951 [1] I canceled my NMU. Depending on
the outcome and if nothing has happened in this bug by the whitedune
maintainers, I'll re-upload with the fix for the man-page included.

Paul

[1] https://bugs.debian.org/919951



signature.asc
Description: OpenPGP digital signature

Processed: Re: whitedune: diff for NMU version 0.30.10-2.2

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #916468 [whitedune] dune: /usr/bin/dune is already provided by the 
whitedune package
Ignoring request to alter tags of bug #916468 to the same tags previously set

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

Bug#920045: ntopng FTBFS with new ndpi

[peter green]

package: ntomng
version: 2.4+dfsg1-4
severity: serious

ntopng fails to build from source with the new ndpi, which recently migrated to testing. 
This affects both the version in buster (as evidenced by the raspbian binnmu 
http://buildd.raspbian.org/status/fetch.php?pkg=ntopng=armhf=2.4%2Bdfsg1-4%2Bb3=1548089724
 ) and the version in sid (as evidenced by reproducible builds 
https://tests.reproducible-builds.org/debian/rbuild/unstable/amd64/ntopng_3.2+dfsg1-1.rbuild.log.gz
 )

Bug#919006: FTBFS: test failure with new DBD::SQLite

[gregor herrmann]

On Mon, 21 Jan 2019 21:28:43 +0200, Niko Tyni wrote:

> Looks like type_info() now returns more than it used to: with the older
> libdbd-sqlite3-perl it gave just 'undef', but now it gives (somewhat
> unhelpful)
> 
> $VAR1 = {
>   'CASE_SENSITIVE' => undef,
>   'MAXIMUM_SCALE' => undef,
>   'NUM_PREC_RADIX' => undef,
>   'MINIMUM_SCALE' => undef,
>   'SQL_DATETIME_SUB' => undef,
>   'NULLABLE' => undef,
>   'LOCAL_TYPE_NAME' => undef,
>   'LITERAL_PREFIX' => undef,
>   'INTERVAL_PRECISION' => undef,
>   'TYPE_NAME' => undef,
>   'DATA_TYPE' => 0,
>   'FIXED_PREC_SCALE' => undef,
>   'AUTO_UNIQUE_VALUE' => undef,
>   'SEARCHABLE' => undef,
>   'UNSIGNED_ATTRIBUTE' => undef,
>   'CREATE_PARAMS' => undef,
>   'COLUMN_SIZE' => undef,
>   'LITERAL_SUFFIX' => undef,
>   'SQL_DATA_TYPE' => undef
> };
> 
> I'm not sure how intentional this is, but it seems to have changed
> in DBD-SQLite 1.61_02 as noted in the upstream bug.
> 
>   
> https://metacpan.org/diff/file?target=ISHIGAKI/DBD-SQLite-1.61_02/=ISHIGAKI/DBD-SQLite-1.61_01/

I think it's intentional:
https://github.com/DBD-SQLite/DBD-SQLite/commit/61e1616c613f2da35e464bdbcfee7b8b2483ca35
(and also https://github.com/DBD-SQLite/DBD-SQLite/issues/36 )
and the returned values of type_info_all() don't look crazy, compared
to the commented out example from DBD::Oracle which was in the code
before.

Why $sth->{TYPE} still doesn't return SQL_ is another question
…
 
> Checking that the value is defined seems to fix / work around this,
> as seen in the attached patch. I'm not totally sure that this
> won't break things on other DBD implementations though.

I don't think so, if they $info->have {TYPE_NAME} the behaviour
shouldn't change …


Cheers,
gregor

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


signature.asc
Description: Digital Signature

Bug#919591: marked as done (libwin32-exe-perl: Incomplete debian/copyright?)

[Debian Bug Tracking System]

Your message dated Mon, 21 Jan 2019 19:49:05 +
with message-id 
and subject line Bug#919591: fixed in libwin32-exe-perl 0.17-2
has caused the Debian Bug report #919591,
regarding libwin32-exe-perl: 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.)


-- 
919591: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919591
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libwin32-exe-perl
Version: 0.17-1
Severity: serious
Justication: Policy 12.5
X-Debbugs-CC: Cyrille Bollu , ftpmas...@debian.org

Hi,

I just ACCEPTed libwin32-exe-perl from NEW but noticed it was missing 
attribution in debian/copyright for at least Mark Dootson.

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: libwin32-exe-perl
Source-Version: 0.17-2

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

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

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

Debian distribution maintenance software
pp.
Cyrille Bollu  (supplier of updated libwin32-exe-perl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Jan 2019 20:26:27 +0100
Source: libwin32-exe-perl
Binary: libwin32-exe-perl
Architecture: source
Version: 0.17-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: Cyrille Bollu 
Closes: 919591
Description: 
 libwin32-exe-perl - Manipulate Win32 executable files
Changes:
 libwin32-exe-perl (0.17-2) unstable; urgency=medium
 .
   * Fix debian/copyright (Closes: #919591)
Checksums-Sha1: 
 db2237e09ad5add5d623c7eb1522385568fa 2149 libwin32-exe-perl_0.17-2.dsc
 f7fa5ad1198303cc19eaa8d6623527668df1d8f7 2656 
libwin32-exe-perl_0.17-2.debian.tar.xz
Checksums-Sha256: 
 9f649c1be0beccf44a82ca37f809a4c16736838910e113ff14f80f96ea2419c4 2149 
libwin32-exe-perl_0.17-2.dsc
 03e66b452d9855701386b005ba67a2c0416c982bb7c88f3b9beccfcd19e1f4f8 2656 
libwin32-exe-perl_0.17-2.debian.tar.xz
Files: 
 3eb0516fdfda3588f40956457c36f8bc 2149 perl optional 
libwin32-exe-perl_0.17-2.dsc
 e1b55a05107f0809b91fb1e00dac64a5 2656 perl optional 
libwin32-exe-perl_0.17-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxGHaMQHHlhZGRAZGVi
aWFuLm9yZwAKCRD210ynyZnu6Yq2D/0X7bI1iKonPGVOFDz3EN89pz8cBBbR0Vgp
eEmcIwYmv+lxBqYDo8Cdq/VSGmUPJxxv3hmnydoFhkAd0EUr145Zfb6TcljCCBlV
D9ctZmIJQ8Gd8pVXoAGdfxP/Rw83Htb0jUwrTcHp/OmqWOa9sppIJ1HNYxXL2FFc
j4Wy9etxWHMotbvLvcSQD8sZiyH9VyZEReUtV3jZPy83spkGgDUagXmSD3wIJTac
XEXN7LGab84gbmR8RFub/Q+TW1tUpkUQkJXIV2WYxlL5L7pcvZbGJAc0Z42hv7Sh
0nUSIsuL34l/LOui5+5842NZOYoJ/obXvLJJvFlYzWr8Qf0iGnG+a/MlfDsFD9hy
ZlI+zQ1M+XJ0yzowHBcc2hFznlzYDs0rMKVAmGYlrKF3LlYP0Z48d7HGDrBcItcG
yoMN+ACjLXQ4dHv3TvTxP3eSuNxaHxhMPFHrD6Z3rImVH49Bzts9w2QQrYNiHC7D
r3QLPLPaiIF3N1wsij//CFkCqe1Qs3dDpqj6H+dEo/b5cRloBLN02hmjeOvaQW8s
iHVpfA+iE3uofT/gNbpAI27feQmeDYsYjGI7iLuP+HzCXKFzPMlF+YnW8Xsqj6zU
S+TdxzZ//BUv4H+lf209EdLony/YYxxQkj0IAq2GKaCJL75RoBsp2JQJoh50Fefu
2pJ3CCUx0w==
=/R8A
-END PGP SIGNATURE End Message ---

Processed: Re: Bug#900299: leiningen-clojure: depends on openjdk-8

[Debian Bug Tracking System]

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

> severity 900299 serious
Bug #900299 [src:leiningen-clojure] leiningen-clojure: depends on openjdk-8
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#919805: redmine: FTBFS (Could not find gem mail)

[Jonathan Boilesen]

Dear maintainer, I have solved this issue by running the command: gem
install mail -v 2.6.4 I think this is the only thing missing in order to
install redmine successfully on Buster. Best regards, Jonathan Boilesen

-- 

 

© 2018 Boilesen Associates. Todos os direitos 
reservados.

--
Este e-mail pode conter informações sigilosas e ou 
confidenciais e, sendo assim, confirme com o remetente antes de 
compartilhá-lo ou reproduzí-lo.

Bug#920037: Don't include in buster

[Moritz Muehlenhoff]

Source: openjdk-8
Severity: serious

The default Java version in buster is openjdk-11 and there's only a handful
of packages still depending on -8, don't include it in buster (which would
double the effort for security updates in stable).

Cheers,
Moritz

Bug#919006: FTBFS: test failure with new DBD::SQLite

[Niko Tyni]

Control: tag -1 patch

On Fri, Jan 11, 2019 at 05:37:52PM +0100, gregor herrmann wrote:
> Source: libclass-dbi-plugin-type-perl
> Version: 0.02-8
> Severity: serious
> Tags: upstream buster sid ftbfs
> Justification: fails to build from source
> Forwarded: https://rt.cpan.org/Public/Bug/Display.html?id=128135

> ok 1 - use Class::DBI::Plugin::Type;
> not ok 2 - notes is text
> #   Failed test 'notes is text'
> #   at t/1.t line 28.
> #   undef
> # doesn't match '(?^:text|blob)'

>From Class::DBI::Plugin::Type::import() :

   @hash{@{$sth->{NAME}}} =
map {
my $info = scalar $self->db_Main->type_info($_);
if ($info) { $info->{TYPE_NAME} }
else { $_ } # Typeless databases (SQLite)
}
@{$sth->{TYPE}};

Looks like type_info() now returns more than it used to: with the older
libdbd-sqlite3-perl it gave just 'undef', but now it gives (somewhat
unhelpful)

$VAR1 = {
  'CASE_SENSITIVE' => undef,
  'MAXIMUM_SCALE' => undef,
  'NUM_PREC_RADIX' => undef,
  'MINIMUM_SCALE' => undef,
  'SQL_DATETIME_SUB' => undef,
  'NULLABLE' => undef,
  'LOCAL_TYPE_NAME' => undef,
  'LITERAL_PREFIX' => undef,
  'INTERVAL_PRECISION' => undef,
  'TYPE_NAME' => undef,
  'DATA_TYPE' => 0,
  'FIXED_PREC_SCALE' => undef,
  'AUTO_UNIQUE_VALUE' => undef,
  'SEARCHABLE' => undef,
  'UNSIGNED_ATTRIBUTE' => undef,
  'CREATE_PARAMS' => undef,
  'COLUMN_SIZE' => undef,
  'LITERAL_SUFFIX' => undef,
  'SQL_DATA_TYPE' => undef
};

I'm not sure how intentional this is, but it seems to have changed
in DBD-SQLite 1.61_02 as noted in the upstream bug.

  
https://metacpan.org/diff/file?target=ISHIGAKI/DBD-SQLite-1.61_02/=ISHIGAKI/DBD-SQLite-1.61_01/

Checking that the value is defined seems to fix / work around this,
as seen in the attached patch. I'm not totally sure that this
won't break things on other DBD implementations though.
-- 
Niko Tyni   nt...@debian.org
>From b8cd9d0d853fdca08488f261d5856801e2ce2771 Mon Sep 17 00:00:00 2001
From: Niko Tyni 
Date: Mon, 21 Jan 2019 21:07:59 +0200
Subject: [PATCH] Fix compatibility with DBD-SQLite >=  1.61_02

type_info() now returns an array of mostly undefined values, breaking
the t/1.t tests. Add a guard for definedness so we still take the other
branch in this case.

Bug: https://rt.cpan.org/Public/Bug/Display.html?id=128135
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919006
---
 Type.pm | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Type.pm b/Type.pm
index 688ca35..986fecd 100644
--- a/Type.pm
+++ b/Type.pm
@@ -29,7 +29,7 @@ sub import {
 @hash{@{$sth->{NAME}}} = 
 map { 
 my $info = scalar $self->db_Main->type_info($_);
-if ($info) { $info->{TYPE_NAME} } 
+if ($info and defined $info->{TYPE_NAME}) { $info->{TYPE_NAME} }
 else { $_ } # Typeless databases (SQLite)
 }
 @{$sth->{TYPE}};
-- 
2.20.1

Processed: Re: Bug#919006: FTBFS: test failure with new DBD::SQLite

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #919006 [src:libclass-dbi-plugin-type-perl] FTBFS: test failure with new 
DBD::SQLite
Added tag(s) patch.

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

Bug#884243: djmount status, two patches and about conversion to libupnp 1.8

[Uwe Kleine-König]

Hello,

On 12/16/18 10:06 PM, Uwe Kleine-König wrote:
> On Wed, May 23, 2018 at 05:31:08PM +0200, Dario Minnucci wrote:
>> Sorry for the delay and thanks to invest time on this issue.
>>
>> On 18/05/18 23:30, Uwe Kleine-König wrote:
>>> On Tue, Jan 09, 2018 at 09:17:35PM +0100, Rémi wrote:
 you are right, I have not been active on djmount for quite some time now.
 I tried to find a volonteer to maintain it at the time, but it didn't
 happen.

 I am sorry I don't have the right setup to validate these patches :-/
 So removing should be considered, unless a maintainer can be found.
>>>
>>> What is your POV on this? Is djmount worth fixing, or should we remove
>>> it? If the former, can you give test feedback on the patches I already
>>> sent?
>>>
>>
>>
>> I need to setup an environment to include libupnp10 (upnp 1.8) and
>> implement provided patches.
>>
>> I lack of free time right now, but will engage on this as soon as I
>> can.
>>
>> Again sorry for the delay.
> 
> The current situation is that djmount is the last package that is using
> libupnp6. (Well, there is still linux-igd, but this is about to be
> removed -> #916643)

linux-igd is gone.

> djmount was already removed from testing. I wonder if we should also
> remove it from unstable given that there happened nothing to make
> djmount build with libupnp-1.8 for a year.

I will report a request to remove djmount from unstable in February
unless someone opposes (and does to work to convert it to libupnp-1.8).

Best regards
Uwe




signature.asc
Description: OpenPGP digital signature

Bug#917085: marked as done (pyzo: missing dependancy to python3-pkg-resources)

[Debian Bug Tracking System]

Your message dated Mon, 21 Jan 2019 18:49:50 +
with message-id 
and subject line Bug#917085: fixed in pyzo 4.4.3-1.2
has caused the Debian Bug report #917085,
regarding pyzo: missing dependancy to python3-pkg-resources
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.)


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

Source: pyzo
Severity: important

Dear Maintainer,

Installing pyzo does not install pkg_resources which prevents from
launching pyzo.

Regards,

J.

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

Kernel: Linux 4.14.67-07156-gc116f2c8c400 (SMP w/2 CPU cores; PREEMPT)
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)
--- End Message ---
--- Begin Message ---
Source: pyzo
Source-Version: 4.4.3-1.2

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 11 Jan 2019 20:09:52 +0200
Source: pyzo
Binary: pyzo pyzo-doc iep
Architecture: source
Version: 4.4.3-1.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Adrian Bunk 
Description:
 iep- transitional dummy package for IEP
 pyzo   - interactive editor for scientific Python
 pyzo-doc   - documentation for Pyzo
Closes: 917085
Changes:
 pyzo (4.4.3-1.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add the missing dependency on python3-pkg-resources,
 thanks to Julien Cervelle. (Closes: #917085)
Checksums-Sha1:
 5c622bfe8af07d8ebcdddc4c36e0d7df363cb97d 2113 pyzo_4.4.3-1.2.dsc
 39be41abb98b5c3ad76205919c5519fe94b0fe36 14432 pyzo_4.4.3-1.2.debian.tar.xz
Checksums-Sha256:
 df98a02800f26a7f30b089b48c8d69c03c42c15e4eac3d45a815db2bc9037109 2113 
pyzo_4.4.3-1.2.dsc
 974e1aa36fa61ce9cc3a98a8e8f8708ebb224a85a37336fc8ef023ecf4fee995 14432 
pyzo_4.4.3-1.2.debian.tar.xz
Files:
 57c985ef77ae65e52d6c826cc8e1d0aa 2113 science optional pyzo_4.4.3-1.2.dsc
 03de599b84331e488718204a6d93b905 14432 science optional 
pyzo_4.4.3-1.2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEOvp1f6xuoR0v9F3wiNJCh6LYmLEFAlw43h4ACgkQiNJCh6LY
mLHgAQ/8DFnmFuwxo+2UY0L+wvTIl+mvjTBZNJhYDdZPDUwy/bSebaho9DWvR+ts
++b8CcpsqZrZVy0VjJ5NypLsuqgOjJ7T7akHTVqBhGGnZ2U0uToK4JUJDL39uz6o
FcmuZ+2UYaOd3bzFgsYmTAGDKYlYSPctcMDbCZKfNglWZlnKmevDA+K1MCvtVzEI
OiJhR4ydMUHfsVVaCVV/Mk92moQzKipDcluHJDYZxhgLLX/i4a8OYTQASJNgSi53
3gX1rvDTODzv7+LsRry7JnHoKQICXFx4xLC8E9CV9UvURGxyPKsnPk/ax5Hnmuoz
w01KaGzI8rNgRqPf1A+CPm4E5jU0Us05Tp9/Z4hqyWZk/s8aGbCtxlu0qKM+4Ttg
palYqtGNgJoG8WkLNSwToP84X+lhO9YwWEgSjvG63xWneav72YVZtSIcx+XfSp4C
O3k6fNfobpvLrVP2a5YhY/hCBMzT3EFcsAXVMa7nqAYKlAd8DmTSYAm9zWyFOx96
ri+pR5wns0dA+mF0m/290vYlGPDuNXE+9M/sgup0x5GZt12Ts+NRE+nX10JAjlnz
DYX/mkqOBYPcudZVDFg7hmV96zLidcsCbcZETcZ22geJirBXav2iVpx/vRD0e06N
F8yBe+IV7TS/z1mPK1oi3czikg29M9rCYolFPSFAa7uZVeYEICQ=
=RbQU
-END PGP SIGNATURE End Message ---

Bug#919829: libatteanx-store-sparql-perl: FTBFS (failing tests)

[Niko Tyni]

On Sun, Jan 20, 2019 at 12:19:21AM +, Santiago Vila wrote:
> Package: src:libatteanx-store-sparql-perl
> Version: 0.010-1
> Severity: serious
> Tags: ftbfs

> Test Summary Report
> ---
> t/plan.t   (Wstat: 65280 Tests: 0 Failed: 0)
>   Non-zero exit status: 255
>   Parse errors: No plan found in TAP output
> Files=2, Tests=1,  7 wallclock secs ( 0.05 usr  0.01 sys +  5.78 cusr  0.51 
> csys =  6.35 CPU)
> Result: FAIL

  $ perl -Iblib/lib  t/plan.t 
  Can't apply Attean::API::Model to AtteanX::Model::SPARQL - missing 
count_quads_estimate at /usr/share/perl5/Moo/Role.pm line 280.
  Compilation failed in require at t/plan.t line 5.
  BEGIN failed--compilation aborted at t/plan.t line 5.

This seems to have broken with libattean-perl 0.020-1. The upstream changelog
states:

  (Update) Expose count_quads_estimate method at the model level.

-- 
Niko Tyni   nt...@debian.org

Processed: tagging 919773

[Debian Bug Tracking System]

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

> tags 919773 - pending
Bug #919773 [src:libdbd-sqlite3-perl] libdbd-sqlite3-perl FTBFS on mips: test 
failure
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 919773

[Debian Bug Tracking System]

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

> tags 919773 + upstream
Bug #919773 [src:libdbd-sqlite3-perl] libdbd-sqlite3-perl FTBFS on mips: test 
failure
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#916702: Merge request

[Dave Steele]

Upstream upgrade available as a merge request.

https://salsa.debian.org/debian/python-freezegun/merge_requests

Bug#909996: marked as done (vdirsyncer: FTBFS (TypeError: 'NoneType' object is not iterable))

[Debian Bug Tracking System]

Your message dated Mon, 21 Jan 2019 18:21:52 +
with message-id 
and subject line Bug#909996: fixed in vdirsyncer 0.16.7-1
has caused the Debian Bug report #909996,
regarding vdirsyncer: FTBFS (TypeError: 'NoneType' object is not iterable)
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.)


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

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --with python3,sphinxdoc --buildsystem=pybuild
   dh_update_autotools_config -i -O--buildsystem=pybuild
   dh_autoreconf -i -O--buildsystem=pybuild
   dh_auto_configure -i -O--buildsystem=pybuild
I: pybuild base:217: python3.7 setup.py config 
running config
/usr/lib/python3/dist-packages/setuptools_scm/version.py:191: UserWarning: meta 
invoked without explicit configuration, will use defaults where required.
  "meta invoked without explicit configuration,"
I: pybuild base:217: python3.6 setup.py config 
running config
/usr/lib/python3/dist-packages/setuptools_scm/version.py:191: UserWarning: meta 
invoked without explicit configuration, will use defaults where required.
  "meta invoked without explicit configuration,"
   debian/rules override_dh_auto_build

[... snipped ...]

tests/storage/test_singlefile.py ... [ 49%]
.ss.ss   [ 53%]
tests/storage/dav/test_caldav.py sss [ 62%]
sss  [ 65%]
tests/storage/dav/test_carddav.py ss [ 71%]
tests/storage/dav/test_main.py . [ 71%]
tests/system/cli/test_config.py .[ 73%]
tests/system/cli/test_discover.py .  [ 74%]
tests/system/cli/test_fetchparams.py ..  [ 76%]
tests/system/cli/test_repair.py .[ 77%]
tests/system/cli/test_sync.py .  [ 81%]
tests/system/cli/test_utils.py ..[ 82%]
tests/system/utils/test_main.py .sssF[ 83%]
tests/unit/test_exceptions.py .  [ 83%]
tests/unit/test_metasync.py .[ 85%]
tests/unit/test_repair.py .. [ 87%]
tests/unit/test_sync.py ...  [ 94%]
tests/unit/cli/test_config.py .  [ 94%]
tests/unit/cli/test_discover.py ..   [ 96%]
tests/unit/utils/test_vobject.py ..  [100%]

=== FAILURES ===
__ TestFilesystemStorage.test_metadata_normalization ___
tests/storage/__init__.py:301: in test_metadata_normalization
st.none(),
E   hypothesis.errors.FailedHealthCheck: It looks like your strategy is 
filtering out a lot of data. Health check found 50 filtered examples but only 3 
good ones. This will make your tests much slower, and also will probably 
distort the data generation quite a lot. You should adapt your strategy to 
filter less. This can also be caused by a low max_leaves parameter in 
recursive() calls
E   See https://hypothesis.readthedocs.io/en/latest/healthchecks.html for more 
information about this. If you want to disable just this health check, add 
HealthCheck.filter_too_much to the suppress_health_check settings for this test.
-- Hypothesis --
You can add @seed(296577508032444947572819497154329054860) to this test or run 
pytest with --hypothesis-seed=296577508032444947572819497154329054860 to 
reproduce this failure.
 TestMemoryStorage.test_metadata_normalization _
tests/storage/__init__.py:301: in test_metadata_normalization
st.none(),
E   hypothesis.errors.FailedHealthCheck: It looks like your strategy is 
filtering out a lot of data. Health check found 50 filtered examples but only 5 
good ones. This will make your tests much slower, and also 

Bug#920030: python3-pygame: ships headers in /usr/include/python3.7/

[Andreas Beckmann]

Package: python3-pygame
Version: 1.9.4.post1+dfsg-2
Severity: serious

Hi,

your package ships the header file(s):

 /usr/include/python3.7/pygame/_camera.h
 /usr/include/python3.7/pygame/_pygame.h
 /usr/include/python3.7/pygame/_surface.h
 /usr/include/python3.7/pygame/bitmask.h
 /usr/include/python3.7/pygame/camera.h
 /usr/include/python3.7/pygame/fastevents.h
 /usr/include/python3.7/pygame/font.h
 /usr/include/python3.7/pygame/freetype.h
 /usr/include/python3.7/pygame/mask.h
 /usr/include/python3.7/pygame/mixer.h
 /usr/include/python3.7/pygame/pgarrinter.h
 /usr/include/python3.7/pygame/pgbufferproxy.h
 /usr/include/python3.7/pygame/pgcompat.h
 /usr/include/python3.7/pygame/pgopengl.h
 /usr/include/python3.7/pygame/pygame.h
 /usr/include/python3.7/pygame/scrap.h
 /usr/include/python3.7/pygame/surface.h

but /usr/include/python3.7 is a symlink to python3.7m in
libpython3.7-dev. This may result in silent file overwrites or depending
on the unpacking order /usr/include/python3.7 being a directory in some
cases, separating the headers into two independent trees.

These header files must be shipped in /usr/include/python3.7m/ instead.
Please talk to the python maintainers to find a proper solution for
handling the packaging of python header files in a future-proof way.


Cheers,

Andreas

Bug#920029: python3-zope.proxy: ships header in /usr/include/python3.7/

[Andreas Beckmann]

Package: python3-zope.proxy
Version: 4.2.0-1
Severity: serious

Hi,

your package ships the header file(s):

  /usr/include/python3.7/zope.proxy/proxy.h

but /usr/include/python3.7 is a symlink to python3.7m in
libpython3.7-dev. This may result in silent file overwrites or depending
on the unpacking order /usr/include/python3.7 being a directory in some
cases, separating the headers into two independent trees.

These header files must be shipped in /usr/include/python3.7m/ instead.
Please talk to the python maintainers to find a proper solution for
handling the packaging of python header files in a future-proof way.


Cheers,

Andreas

Bug#920028: python3-bsddb3: ships header in /usr/include/python3.7/

[Andreas Beckmann]

Package: python3-bsddb3
Version: 6.2.6-2
Severity: serious

Hi,

your package ships the header file(s):

  /usr/include/python3.7/bsddb3/bsddb.h

but /usr/include/python3.7 is a symlink to python3.7m in
libpython3.7-dev. This may result in silent file overwrites or depending
on the unpacking order /usr/include/python3.7 being a directory in some
cases, separating the headers into two independent trees.

These header files must be shipped in /usr/include/python3.7m/ instead.
Please talk to the python maintainers to find a proper solution for
handling the packaging of python header files in a future-proof way.


Cheers,

Andreas

Bug#920027: python3-persistent: ships headers in /usr/include/python3.7/

[Andreas Beckmann]

Package: python3-persistent
Version: 4.2.2-1
Severity: serious

Hi,

your package ships the header file(s):

 /usr/include/python3.7/persistent/cPersistence.h
 /usr/include/python3.7/persistent/ring.h

but /usr/include/python3.7 is a symlink to python3.7m in
libpython3.7-dev. This may result in silent file overwrites or depending
on the unpacking order /usr/include/python3.7 being a directory in some
cases, separating the headers into two independent trees.

These header files must be shipped in /usr/include/python3.7m/ instead.
Please talk to the python maintainers to find a proper solution for
handling the packaging of python header files in a future-proof way.


Cheers,

Andreas

Processed: reassign 832491 to src:aboot

[Debian Bug Tracking System]

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

> reassign 832491 src:aboot
Bug #832491 [aboot] aboot: please remove build dependency on obsolete package sp
Bug reassigned from package 'aboot' to 'src:aboot'.
No longer marked as found in versions 1.0~pre20040408-4.
Ignoring request to alter fixed versions of bug #832491 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#920026: python-greenlet-dev: ships header in /usr/include/python3.7/

[Andreas Beckmann]

Package: python-greenlet-dev
Version: 0.4.15-1
Severity: serious

Hi,

your package ships the header file(s):

  /usr/include/python3.7/greenlet/greenlet.h

but /usr/include/python3.7 is a symlink to python3.7m in
libpython3.7-dev. This may result in silent file overwrites or depending
on the unpacking order /usr/include/python3.7 being a directory in some
cases, separating the headers into two independent trees.

These header files must be shipped in /usr/include/python3.7m/ instead.
Please talk to the python maintainers to find a proper solution for
handling the packaging of python header files in a future-proof way.


Andreas

Bug#919558: marked as done (node-get-value: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Mon, 21 Jan 2019 17:50:39 +
with message-id 
and subject line Bug#920004: fixed in node-get-value 3.0.1+~3.0.1-1
has caused the Debian Bug report #920004,
regarding node-get-value: autopkgtest regression
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.)


-- 
920004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-get-value
Version: 3.0.1-1
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of node-get-value the autopkgtest of node-get-value
fails in testing when that autopkgtest is run with the binary packages
of node-get-value from unstable. It passes when run with only packages
from testing. In tabular form:
   passfail
node-get-value from testing3.0.1-1
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it? If needed, please
change the bug's severity.

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

Paul

[1] https://qa.debian.org/excuses.php?package=node-get-value

https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-get-value/1717375/log.gz

autopkgtest [04:39:41]: test require: [---
module.js:549
throw err;
^

Error: Cannot find module 'isobject'
at Function.Module._resolveFilename (module.js:547:15)
at Function.Module._load (module.js:474:25)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object. (/usr/lib/nodejs/get-value/index.js:8:18)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
autopkgtest [04:39:42]: test require: ---]



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: node-get-value
Source-Version: 3.0.1+~3.0.1-1

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Jan 2019 18:24:53 +0100
Source: node-get-value
Binary: node-get-value
Architecture: source
Version: 3.0.1+~3.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Xavier Guimard 
Changed-By: Xavier Guimard 
Closes: 920004
Description: 
 node-get-value - Use property paths to get a nested value from an object
Changes:
 node-get-value (3.0.1+~3.0.1-1) unstable; urgency=medium
 .
   * Team upload
   * Add isobject component (Closes: #920004)
   * New upstream version 3.0.1+~3.0.1
   * Add mocha test in autopkgtest files
   * Update debian/copyright
Checksums-Sha1: 
 17c1814e478ac73283f8d14703f2ae63385c3162 2446 node-get-value_3.0.1+~3.0.1-1.dsc
 4e431e92b11a9731636aa1f9c8d1ccbcfdab78df 2839 
node-get-value_3.0.1+~3.0.1.orig-isobject.tar.gz
 0c93273af0f5210c334d06f20405ef55c8872375 30330 
node-get-value_3.0.1+~3.0.1.orig.tar.gz
 7fe04a645f764de078c44ad300e9bee8526b4e59 2756 
node-get-value_3.0.1+~3.0.1-1.debian.tar.xz
Checksums-Sha256: 
 46d56dad27860c6add5332c47a900b0674dc7dd804875bff4ff77873a7056a6c 2446 
node-get-value_3.0.1+~3.0.1-1.dsc
 3cc6c92b005a644c93fbc9e3eb450b6a642bbca3443cc9dcc169152961367d37 2839 
node-get-value_3.0.1+~3.0.1.orig-isobject.tar.gz
 ac5abdee9c235e878f179ee3fb4520f217f31794b5232d34edaab7c05dbb5dd8 30330 
node-get-value_3.0.1+~3.0.1.orig.tar.gz
 af99a4f45330771ac6960562a740795afa3543c26451347f33632891ef3ea313 2756 
node-get-value_3.0.1+~3.0.1-1.debian.tar.xz
Files: 
 29dd842f0cd3e97771a4e192da9dd3fd 2446 javascript optional 

Bug#920004: marked as done (node-get-value: missing dependency on node-isobject)

[Debian Bug Tracking System]

Your message dated Mon, 21 Jan 2019 17:50:39 +
with message-id 
and subject line Bug#920004: fixed in node-get-value 3.0.1+~3.0.1-1
has caused the Debian Bug report #920004,
regarding node-get-value: missing dependency on node-isobject
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.)


-- 
920004: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: node-get-value
Version: 3.0.1-1
Severity: serious

> require('get-value')
{ Error: Cannot find module 'isobject'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
at Function.Module._load (internal/modules/cjs/loader.js:507:25)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (internal/modules/cjs/helpers.js:22:18) code: 'MODULE_NOT_FOUND' 
}
>
--- End Message ---
--- Begin Message ---
Source: node-get-value
Source-Version: 3.0.1+~3.0.1-1

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 21 Jan 2019 18:24:53 +0100
Source: node-get-value
Binary: node-get-value
Architecture: source
Version: 3.0.1+~3.0.1-1
Distribution: unstable
Urgency: medium
Maintainer: Xavier Guimard 
Changed-By: Xavier Guimard 
Closes: 920004
Description: 
 node-get-value - Use property paths to get a nested value from an object
Changes:
 node-get-value (3.0.1+~3.0.1-1) unstable; urgency=medium
 .
   * Team upload
   * Add isobject component (Closes: #920004)
   * New upstream version 3.0.1+~3.0.1
   * Add mocha test in autopkgtest files
   * Update debian/copyright
Checksums-Sha1: 
 17c1814e478ac73283f8d14703f2ae63385c3162 2446 node-get-value_3.0.1+~3.0.1-1.dsc
 4e431e92b11a9731636aa1f9c8d1ccbcfdab78df 2839 
node-get-value_3.0.1+~3.0.1.orig-isobject.tar.gz
 0c93273af0f5210c334d06f20405ef55c8872375 30330 
node-get-value_3.0.1+~3.0.1.orig.tar.gz
 7fe04a645f764de078c44ad300e9bee8526b4e59 2756 
node-get-value_3.0.1+~3.0.1-1.debian.tar.xz
Checksums-Sha256: 
 46d56dad27860c6add5332c47a900b0674dc7dd804875bff4ff77873a7056a6c 2446 
node-get-value_3.0.1+~3.0.1-1.dsc
 3cc6c92b005a644c93fbc9e3eb450b6a642bbca3443cc9dcc169152961367d37 2839 
node-get-value_3.0.1+~3.0.1.orig-isobject.tar.gz
 ac5abdee9c235e878f179ee3fb4520f217f31794b5232d34edaab7c05dbb5dd8 30330 
node-get-value_3.0.1+~3.0.1.orig.tar.gz
 af99a4f45330771ac6960562a740795afa3543c26451347f33632891ef3ea313 2756 
node-get-value_3.0.1+~3.0.1-1.debian.tar.xz
Files: 
 29dd842f0cd3e97771a4e192da9dd3fd 2446 javascript optional 
node-get-value_3.0.1+~3.0.1-1.dsc
 9e7647515c0885e809f9aeb22de293f3 2839 javascript optional 
node-get-value_3.0.1+~3.0.1.orig-isobject.tar.gz
 a14ccb4c3fa4d00b4ff7f489d9e3433d 30330 javascript optional 
node-get-value_3.0.1+~3.0.1.orig.tar.gz
 79448fa190d15d31ff1dac35734a8d10 2756 javascript optional 
node-get-value_3.0.1+~3.0.1-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAlxGAZEQHHlhZGRAZGVi
aWFuLm9yZwAKCRD210ynyZnu6UKyD/4meui30HebT5S5OBSsmZEJa4fILt5ZtvkK
LXtdo6t/j9iaHL4yMRiMe6Kn5kcMMYBRAgSHinqxFZ/Fa6+okwhzhzeYBTT1UEiK
jzp8obiXWVT7FgqTkv4OeLXruy3a6ZVM2yM1dVl6PEZYtgJ15k1yPC9W7hJlS8+Y
NYpDCht+oJBPADp/POQZuwHavGK0t0TDEFfcbx5EShokZCP+dt+R97WxEjUi/jb1
j/+WvRzK4gVH3/qN2gcmZ2pKpClPF60yfWt9ewS3tBe+k9oLse3yaaasgTlkbGJx
AaGEYMG8rr8+x6LnMmn1v3ksEjJKCk99GL6kUcPyNzJF10KBXB3zE4otVVPR1o8K
wcEug8gX2eaUQgE4b43TwbkFTzAzB+84Rb2HYYuuhJiTK6sQ8QJzeOnVebaOWJDI
1YOJ6RSdIveGe9KMQ/LJ0G6I+Nkj+r5piWAcyZiINpVPA5oKI2yxsaYn9kXi8Oz9
qReoxzAa9bMwBcDHxuBxBE25Cw372dd/1F/2mSpmAvaS/fyZ2f5mtmRtTzWv1Azo
EjcFMnwcRteBNTuA8UX3EyCAWgt3D++hacAzkVlRHjDFNafRCQLT1XhFYXVjyDBr
hUQWOylVnKaWbtRR5T3RBnmWD+tvNWmaSB1cEHcMVO29qFaOmSSvljbWwvNU671E
K/4cyFmGyg==
=1ASe
-END PGP SIGNATURE End Message ---

Processed: reassign 919558 to node-get-value, forcibly merging 920004 919558

[Debian Bug Tracking System]

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

> reassign 919558 node-get-value
Bug #919558 [src:node-get-value] node-get-value: autopkgtest regression
Bug reassigned from package 'src:node-get-value' to 'node-get-value'.
No longer marked as found in versions node-get-value/3.0.1-1.
Ignoring request to alter fixed versions of bug #919558 to the same values 
previously set
> forcemerge 920004 919558
Bug #920004 [node-get-value] node-get-value: missing dependency on node-isobject
Bug #919558 [node-get-value] node-get-value: autopkgtest regression
Severity set to 'serious' from 'normal'
Marked as found in versions node-get-value/3.0.1-1.
Added tag(s) pending.
Merged 919558 920004
> thanks
Stopping processing here.

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

Processed: tagging 920004

[Debian Bug Tracking System]

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

> tags 920004 + pending
Bug #920004 [node-get-value] node-get-value: missing dependency on node-isobject
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:svgpp

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:svgpp
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #919321 (http://bugs.debian.org/919321)
> # Bug title: CVE-2019-6246
> #  * https://github.com/svgpp/svgpp/issues/70
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 919321 + fixed-upstream
Bug #919321 [src:svgpp] CVE-2019-6246
Added tag(s) fixed-upstream.
> usertags 919321 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:libmail-chimp3-perl

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:libmail-chimp3-perl
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #918380 (http://bugs.debian.org/918380)
> # Bug title: FTBFS: test failures with new Web::API
> #  * https://github.com/jdigory/p5-Mail-Chimp3/issues/4
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 918380 + fixed-upstream
Bug #918380 [src:libmail-chimp3-perl] FTBFS: test failures with new Web::API
Added tag(s) fixed-upstream.
> usertags 918380 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 918380 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:python-mne

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:python-mne
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #896025 (http://bugs.debian.org/896025)
> # Bug title: python-mne FTBFS with python-matplotlib 2.2.2-1
> #  * https://github.com/mne-tools/mne-python/issues/5806
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 896025 + fixed-upstream
Bug #896025 [src:python-mne] python-mne FTBFS with python-matplotlib 2.2.2-1
Added tag(s) fixed-upstream.
> usertags 896025 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 896025 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package systemd

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package systemd
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #788499 (http://bugs.debian.org/788499)
> # Bug title: udev: incorrect documentation in 
> /lib/udev/hwdb.d/60-keyboard.hwdb
> #  * https://github.com/systemd/systemd/issues/1813
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 788499 + fixed-upstream
Bug #788499 [udev] udev: incorrect documentation in 
/lib/udev/hwdb.d/60-keyboard.hwdb
Bug #788586 [udev] udev: "udevadm trigger /dev/input/event*" doesn't work
Added tag(s) fixed-upstream.
Added tag(s) fixed-upstream.
> usertags 788499 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 788499 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #788586 (http://bugs.debian.org/788586)
> # Bug title: udev: "udevadm trigger /dev/input/event*" doesn't work
> #  * https://github.com/systemd/systemd/issues/1813
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 788586 + fixed-upstream
Bug #788586 [udev] udev: "udevadm trigger /dev/input/event*" doesn't work
Bug #788499 [udev] udev: incorrect documentation in 
/lib/udev/hwdb.d/60-keyboard.hwdb
Ignoring request to alter tags of bug #788586 to the same tags previously set
Ignoring request to alter tags of bug #788499 to the same tags previously set
> usertags 788586 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 788586 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> # remote status report for #919390 (http://bugs.debian.org/919390)
> # Bug title: udev: network interface gets ID_NET_NAME even when NAME has been 
> set by /etc/udev/rules.d/70-persistent-net.rules
> #  * https://github.com/systemd/systemd/issues/11436
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 919390 + fixed-upstream
Bug #919390 [udev] udev: network interface gets ID_NET_NAME even when NAME has 
been set by /etc/udev/rules.d/70-persistent-net.rules
Added tag(s) fixed-upstream.
> usertags 919390 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package src:libbiod

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:libbiod
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting user to debian-bts-l...@lists.debian.org (was 
debian-bts-l...@lists.debian.org).
> # remote status report for #912077 (http://bugs.debian.org/912077)
> # Bug title: libbiod FTBFS on i386: Error: cannot implicitly convert 
> expression
> #  * https://github.com/biod/BioD/issues/43
> #  * remote status changed: closed -> open
> #  * reopen upstream
> tags 912077 - fixed-upstream
Bug #912077 [src:libbiod] libbiod FTBFS on i386: Error: cannot implicitly 
convert expression
Removed tag(s) fixed-upstream.
> usertags 912077 - status-closed
Usertags were: status-closed.
Usertags are now: .
> usertags 912077 + status-open
There were no usertags set.
Usertags are now: status-open.
> thanks
Stopping processing here.

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

Bug#915689: Fwd: Re: Bug#919893: package shouldn't exist

[Diederik de Haas]

On maandag 21 januari 2019 17:13:42 CET Michael Stone wrote:
> >Entropy generation for the creation of SSH keys as the netinstaller is
> >mostly used in headless situations.
> >https://github.com/debian-pi/raspbian-ua-netinst/issues/42
> 
> That functionality doesn't require the old package; will work fine with
> rng-tools5.

Great, thanks :)

FTR: That *I* don't need it in my particular use case does not mean that no 
one has a need for the functionality now provided by rng-tools-debian

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

Processed (with 1 error): Re: [Openjdk] Bug#920020: javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + important
Unknown tag/s: important.
Recognized are: patch wontfix moreinfo unreproducible help security upstream 
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed 
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore.

Bug #920020 [openjdk-11-jdk] javadoc: The code being documented uses modules 
but the packages defined in … are in the unnamed module
Requested to add no tags; doing nothing.

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

Bug#920020: [Openjdk] Bug#920020: javadoc: The code being documented uses modules but the packages defined in … are in the unnamed module

[Matthias Klose]

Control: tags -1 + important

On 21.01.19 17:42, Thorsten Glaser wrote:
> Package: openjdk-11-jdk
> Version: 11.0.2+7-1

> Severity: grave
> Justification: renders package unusable

no, why are you exaggerating? Both the jre and the jdk are usable.

> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-javadoc-plugin:3.0.1:jar (attach-javadocs) on 
> project octopus-rpctunnel: MavenReportException: Error while generating 
> Javadoc: 
> [ERROR] Exit code: 1 - javadoc: error - The code being documented uses 
> modules but the packages defined in 
> https://docs.oracle.com/javase/8/docs/api/ are in the unnamed module.
> 
> The cause for this is:
> 
> https://bugs.openjdk.java.net/browse/JDK-8212233
> 
> The fix is (not tested by myself):
> 
> http://hg.openjdk.java.net/jdk/jdk/rev/8ce4083fc831
> via:
> https://bugs.openjdk.java.net/browse/JDK-8217177

Bug#880393: nmuing cyrus-sasl2

[Ondřej Surý]

Hi all,

I spent a half-day hacking cyrus-sasl2 and I uploaded 2.1.27 to experimental. I 
would appreciate if more people can test the package (I won’t have time until 
tomorrow or next week). I didn’t even had a chance to test it myself, so even 
the basic it installs and nothing breaks horribly would help.

Ondrej
--
Ondřej Surý 

> On 21 Jan 2019, at 03:17, Ryan Tandy  wrote:
> 
> Hello,
> 
> I extracted Helmut's changes for this issue from the debdiff he posted in an 
> earlier message, and proposed a merge request on salsa.
> 
> https://salsa.debian.org/debian/cyrus-sasl2/merge_requests/3
> 
> as a git-format-patch(1) patch:
> 
> https://salsa.debian.org/debian/cyrus-sasl2/merge_requests/3.patch
> 
> I have built it and verified that the Depends line and library dependencies 
> are corrected, and that it is installable. I have not actually tested the 
> module's functionality.
> 
> I agree with Helmut that this looks suitable for a stretch update. I would be 
> willing to drive that process if the maintainers agree but lack time.

Processed: Fwd: Bug#919966: akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: _ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStringRK8QVariant

[Debian Bug Tracking System]

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

> reassign 919966 libkf5newstuff5 5.54.0-1
Bug #919966 [libkf5newstuff5] akregator: symbol lookup error: 
/usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: 
_ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStringRK8QVariant
Ignoring request to reassign bug #919966 to the same package
Bug #919966 [libkf5newstuff5] akregator: symbol lookup error: 
/usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: 
_ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStringRK8QVariant
Marked as found in versions knewstuff/5.54.0-1.
> forcemerge 919765 919966
Bug #919765 {Done: steve } [libkf5newstuff5] Multiple 
applications: symbol lookup error: libKF5NewStuff.so.5: undefined symbol
Bug #919966 [libkf5newstuff5] akregator: symbol lookup error: 
/usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: 
_ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStringRK8QVariant
Severity set to 'important' from 'grave'
Marked Bug as done
Added indication that 919966 affects dolphin,kpat,akregator,kmail
Merged 919765 919966
>
End of message, stopping processing here.

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

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

[Thorsten Glaser]

Package: openjdk-11-jdk
Version: 11.0.2+7-1
Severity: grave
Tags: patch
Justification: renders package unusable

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

The cause for this is:

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

The fix is (not tested by myself):

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

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

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

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

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

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

-- no debconf information

Processed: reassign 919966 to libkf5newstuff5

[Debian Bug Tracking System]

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

> reassign 919966 libkf5newstuff5
Bug #919966 [akregator] akregator: symbol lookup error: 
/usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: 
_ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStringRK8QVariant
Bug reassigned from package 'akregator' to 'libkf5newstuff5'.
No longer marked as found in versions akregator/4:18.08.1-1.
Ignoring request to alter fixed versions of bug #919966 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed (with 1 error): merging 919966 919765

[Debian Bug Tracking System]

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

> merge 919966 919765
Bug #919966 [akregator] akregator: symbol lookup error: 
/usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: 
_ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStringRK8QVariant
Unable to merge bugs because:
severity of #919765 is 'important' not 'grave'
done of #919765 is 'steve ' not ''
affects of #919765 is 'dolphin,kpat,akregator,kmail' not ''
package of #919765 is 'libkf5newstuff5' not 'akregator'
Failed to merge 919966: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#880393: marked as done (libsasl2-modules-gssapi-heimdal seems built against MIT)

[Debian Bug Tracking System]

Your message dated Mon, 21 Jan 2019 16:34:43 +
with message-id 
and subject line Bug#880393: fixed in cyrus-sasl2 2.1.27+dfsg-1~exp1
has caused the Debian Bug report #880393,
regarding libsasl2-modules-gssapi-heimdal seems built against MIT
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.)


-- 
880393: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880393
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libsasl2-modules-gssapi-heimdal
Version: 2.1.27~101-g0780600+dfsg-3
Severity: important

Dear Maintainer,

I think something is fishy with the package "libsasl2-modules-gssapi-heimdal".
I suspect that the package is built against MIT instead of Heimdal.

Trying to migrate a Xenial machine to Stretch I noticed a difference in
behavior when using `saslauthd` in a Postfix chroot - configs that
haven't been required before was now required and `saslauthd` is
complaing about settings that I have never seen with our previous setup. We
have always used the Heimdal Kerberos libraries and therefore always
used "libsasl2-modules-gssapi-heimdal" for `saslauthd`.

Couldn't find any upstream changes in either Heimdal or Cyrus SASL which
would explain my issuses so I went digging in the Debian package
instead.
Found that Heimdal was ripped out from the package(s) in October 24
2016:
* 004977091b89363daa04301e89a045e7e2ffbad8
* b9158ab7d2bc71a026d417982fee61bc854935f4
* b334c34bce70f20d85ef0e86e79c6310b69f7345
And added again on Dec 31:
* f382638d18a1e1e75560076d0cb1482e0b4dc613

Unfortunately the package(s) has moved a lot between removal and reinstatement
so I can't get a clean diff over the changes. But I suspect that the
reinstatement didn't go as planned.

>From Jessie:
```
# dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libgssapiv2.so.2.0.25
libsasl2-modules-gssapi-heimdal:amd64: 
/usr/lib/x86_64-linux-gnu/sasl2/libgssapiv2.so.2.0.25

# ldd /usr/lib/x86_64-linux-gnu/sasl2/libgssapiv2.so.2.0.25
linux-vdso.so.1 (0x7fffc877e000)
libgssapi.so.3 => /usr/lib/x86_64-linux-gnu/libgssapi.so.3 
(0x7fd5b206a000)
libkrb5.so.26 => /usr/lib/x86_64-linux-gnu/libkrb5.so.26 
(0x7fd5b1ddb000)
libasn1.so.8 => /usr/lib/x86_64-linux-gnu/libasn1.so.8 
(0x7fd5b1b2b000)
libroken.so.18 => /usr/lib/x86_64-linux-gnu/libroken.so.18 
(0x7fd5b1915000)
libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 
(0x7fd5b16de000)
libcrypto.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 
(0x7fd5b12e1000)
libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 
(0x7fd5b10dd000)
libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 
(0x7fd5b0ec6000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fd5b0b1a000)
libheimntlm.so.0 => /usr/lib/x86_64-linux-gnu/libheimntlm.so.0 
(0x7fd5b0911000)
libhcrypto.so.4 => /usr/lib/x86_64-linux-gnu/libhcrypto.so.4 
(0x7fd5b06dc000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fd5b04be000)
libwind.so.0 => /usr/lib/x86_64-linux-gnu/libwind.so.0 
(0x7fd5b0295000)
libheimbase.so.1 => /usr/lib/x86_64-linux-gnu/libheimbase.so.1 
(0x7fd5b0086000)
libhx509.so.5 => /usr/lib/x86_64-linux-gnu/libhx509.so.5 
(0x7fd5afe39000)
libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7fd5afb7)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7fd5af96c000)
/lib64/ld-linux-x86-64.so.2 (0x7fd5b24ba000)

# strings /usr/lib/x86_64-linux-gnu/sasl2/libgssapiv2.so.2.0.25 | egrep 
"MIT|HEIM"
HEIMDAL_GSS_2.0
```

>From Ubuntu Xenial:
```
# dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libgssapiv2.so.2.0.25
libsasl2-modules-gssapi-heimdal:amd64: 
/usr/lib/x86_64-linux-gnu/sasl2/libgssapiv2.so.2.0.25

# ldd /usr/lib/x86_64-linux-gnu/sasl2/libgssapiv2.so.2.0.25
linux-vdso.so.1 =>  (0x7ffd967d4000)
libgssapi.so.3 => /usr/lib/x86_64-linux-gnu/libgssapi.so.3 
(0x7f818c61c000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f818c252000)
libheimntlm.so.0 => /usr/lib/x86_64-linux-gnu/libheimntlm.so.0 
(0x7f818c048000)
libkrb5.so.26 => /usr/lib/x86_64-linux-gnu/libkrb5.so.26 
(0x7f818bdbe000)
libasn1.so.8 => /usr/lib/x86_64-linux-gnu/libasn1.so.8 
(0x7f818bb1c000)
libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 
(0x7f818b917000)
libhcrypto.so.4 => /usr/lib/x86_64-linux-gnu/libhcrypto.so.4 
(0x7f818b6e4000)
libroken.so.18 => 

Bug#919794: marked as done (python3-sbml5-doc: missing Breaks+Replaces: libsbml5-python-doc)

[Debian Bug Tracking System]

Your message dated Mon, 21 Jan 2019 16:35:18 +
with message-id 
and subject line Bug#919794: fixed in libsbml 5.17.2+dfsg-2
has caused the Debian Bug report #919794,
regarding python3-sbml5-doc: missing Breaks+Replaces: libsbml5-python-doc
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.)


-- 
919794: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919794
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-sbml5-doc
Version: 5.17.2+dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

This test intentionally skipped 'testing' to find file overwrite
problems before packages migrate from 'unstable' to 'testing'.

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

  Preparing to unpack .../python3-sbml5-doc_5.17.2+dfsg-1_all.deb ...
  Unpacking python3-sbml5-doc (5.17.2+dfsg-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/python3-sbml5-doc_5.17.2+dfsg-1_all.deb (--unpack):
   trying to overwrite '/usr/share/doc/libsbml5/python-api', which is also in 
package libsbml5-python-doc 5.13.0+dfsg-1
  Errors were encountered while processing:
   /var/cache/apt/archives/python3-sbml5-doc_5.17.2+dfsg-1_all.deb


cheers,

Andreas


libsbml5-python-doc=5.13.0+dfsg-1_python3-sbml5-doc=5.17.2+dfsg-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libsbml
Source-Version: 5.17.2+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Michael R. Crusoe  (supplier of updated libsbml 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 19 Jan 2019 23:39:33 -0800
Source: libsbml
Binary: libsbml5-dev libsbml5 python3-sbml5 libsbml5-java libsbml5-perl 
libsbml5-octave libsbml5-cil libsbml5-examples libsbml5-doc libsbml5-cil-doc 
libsbml5-perl-doc python3-sbml5-doc
Architecture: source
Version: 5.17.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Michael R. Crusoe 
Description:
 libsbml5   - System Biology Markup Language library
 libsbml5-cil - System Biology Markup Language library - CLI bindings
 libsbml5-cil-doc - System Biology Markup Language library -- CLI documentation
 libsbml5-dev - System Biology Markup Language library - development files
 libsbml5-doc - System Biology Markup Language library -- documentation
 libsbml5-examples - System Biology Markup Language library -- example files
 libsbml5-java - System Biology Markup Language library - Java bindings
 libsbml5-octave - System Biology Markup Language library - Octave bindings
 libsbml5-perl - System Biology Markup Language library - Perl bindings
 libsbml5-perl-doc - System Biology Markup Language library -- Perl 
documentation
 python3-sbml5 - System Biology Markup Language library - Python3 bindings
 python3-sbml5-doc - System Biology Markup Language library - Python3 
documentation
Closes: 919794
Changes:
 libsbml (5.17.2+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Andreas Tille ]
   * Add missing Breaks+Replaces: libsbml5-python-doc
 Closes: #919794
 .
   [ Michael R. Crusoe ]
   * Fix build for multiarch cross building (specifically i386 on amd64)
   * Link to jquery and other assets from the default-jdk-doc
   * Slim build-deps (637 → 595) use jdk-headless
Checksums-Sha1:
 0eb84aef6e61a5fbfe09a153a85e25b11dd3b57c 2914 libsbml_5.17.2+dfsg-2.dsc
 175d76f94eaae0e7867bf15bd272c1db681c78e1 27848 
libsbml_5.17.2+dfsg-2.debian.tar.xz
 d22d9c1244cf9dfc50db4faf45e4bffc885ea78b 27775 
libsbml_5.17.2+dfsg-2_source.buildinfo
Checksums-Sha256:
 

Bug#919356: Fw: Bug#919356: dwarves-dfsg: Copyright/licensing is unclear

[MJ Ray]

Missed the bug off the CC for this. Sorry.

Begin forwarded message:

Date: Mon, 21 Jan 2019 13:34:13 +
From: MJ Ray 
To: debian-le...@lists.debian.org
Subject: Re: Bug#919356: dwarves-dfsg: Copyright/licensing is unclear


Domenico Andreoli  skribis:

>   the situation of dwarves-dfsg improved a lot over the weekend, the
> only knot left is now the license of hash.h
> 
> This file is also present in the kernel [0] with an updated copyright
> but still without license.
> 
> I received a private email from somebody in the kernel community who
> already tried to contact Nadia in the past but did not get any reply.
> [...]
> [0]
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/hash.h
>   

One of the commits to that file is from Nadia. Sorry if I'm being
dense, but where does the doubt that it is under the kernel's licence
arise?

Thanks,
-- 

MJR http://mjr.towers.org.uk/
Member of http://www.software.coop/ (but this email is my personal view
only)



-- 

MJR http://mjr.towers.org.uk/
Member of http://www.software.coop/ (but this email is my personal view
only)



pgpT5hY4tmkxU.pgp
Description: OpenPGP digital signature

Processed: severity of 919966 is grave

[Debian Bug Tracking System]

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

> severity 919966 grave
Bug #919966 [akregator] akregator: symbol lookup error: 
/usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: 
_ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStringRK8QVariant
Ignoring request to change severity of Bug 919966 to the same value.
> thanks
Stopping processing here.

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

Bug#919529: CVE-2019-6256

[Salvatore Bonaccorso]

Hi,

On Sun, Jan 20, 2019 at 03:22:31PM +0100, Sebastian Ramacher wrote:
> On 2019-01-19 22:36:05, Salvatore Bonaccorso wrote:
> > Hey!
> > 
> > On Thu, Jan 17, 2019 at 12:00:13AM +0100, Sebastian Ramacher wrote:
> > > Control: found -1 2016.11.28-1
> > > 
> > > On 2019-01-16 23:19:45, Moritz Muehlenhoff wrote:
> > > > Source: liblivemedia
> > > > Severity: grave
> > > > Tags: security
> > > > 
> > > > Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6256
> > > > 
> > > > Cheers,
> > > > Moritz
> > > 
> > > Not sure if I'm missing something, but the PoC does not seem to work on
> > > buster/sid. On stretch I get segfaults, but only if I abort the PoC. So 
> > > marking
> > > as found in stable and closing for sid.
> > 
> > Not having a poc triggering does not necessarly mean the issue needs
> > to be fixed. Do we know something on the actual fix? Skimming (but
> > only superficial) in the git repository I have not found something
> > obvious, but possible I only missed it.
> 
> http://lists.live555.com/pipermail/live-devel/2018-November/021099.html
> explicitely mentions that the issue was fixed in 2018.11.26.

perfect, thank you!

Salvatore

Processed (with 1 error): Re: Bug#919966: akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: _ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStrin

[Debian Bug Tracking System]

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

> forcemerge 919765 919966
Bug #919765 {Done: steve } [libkf5newstuff5] Multiple 
applications: symbol lookup error: libKF5NewStuff.so.5: undefined symbol
Unable to merge bugs because:
package of #919966 is 'akregator' not 'libkf5newstuff5'
Failed to forcibly merge 919765: Did not alter merged bugs.

>
End of message, stopping processing here.

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

Bug#919966: akregator: symbol lookup error: /usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: _ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStringRK8QVariant

[Francois Marier]

On 2019-01-21 at 15:48:29, Bernhard Übelacker wrote:
> this looks like a duplicate of bug:
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=919765

Indeed. Thanks for that.

-- 
https://fmarier.org/

Processed (with 1 error): merging 919966 919765

[Debian Bug Tracking System]

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

> merge 919966 919765
Bug #919966 [akregator] akregator: symbol lookup error: 
/usr/lib/x86_64-linux-gnu/libKF5NewStuff.so.5: undefined symbol: 
_ZN7KNSCore6Engine15signalErrorCodeERKNS_9ErrorCodeERK7QStringRK8QVariant
Unable to merge bugs because:
severity of #919765 is 'important' not 'grave'
done of #919765 is 'steve ' not ''
affects of #919765 is 'dolphin,kpat,akregator,kmail' not ''
package of #919765 is 'libkf5newstuff5' not 'akregator'
Failed to merge 919966: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#915689: Fwd: Re: Bug#919893: package shouldn't exist

[Michael Stone]

On Mon, Jan 21, 2019 at 04:47:51PM +0100, Diederik de Haas wrote:

On maandag 21 januari 2019 13:34:19 CET Michael Stone wrote:

On Mon, Jan 21, 2019 at 01:15:13PM +0100, Diederik de Haas wrote:
>On zondag 20 januari 2019 16:59:11 CET Thorsten Glaser wrote:
>> I’m very much against just saying this package
>> “should not exist”
>
>I'm inclined to agree with this as the source (+ features/parameters) for
>this package is substantially different from rng-tools/rng-tools5.

Yes, but most of those features are obsolescent at best. I'm not clear
on what functionality is actually being used. (I'm hesitant to remove
it exactly because I'm not clear on that, but I tend to think that it's
functionally obsolete.)


I'm not knowledgeable enough to weigh in on that and/or what is best towards
the future, so I'll leave that up to you.


>coordination/progress. I'm thinking of updating
>https://github.com/debian-pi/ raspbian-ua-netinst/ to buster level and we
>use(d) the old rng-tools to get much better/more entropy on the Raspberry
>Pi.

In what way?


Entropy generation for the creation of SSH keys as the netinstaller is mostly
used in headless situations.
https://github.com/debian-pi/raspbian-ua-netinst/issues/42


That functionality doesn't require the old package; will work fine with 
rng-tools5. 

Bug#919802: Fwd: Re: Bug#919802: libjstun-java: FTBFS (The code being documented uses packages in the unnamed module)

[Gilles Filippini]

Hi Emmanuel, Niels,

Any input on this topic?

Thanks in advance,

_g.

 Message transféré 
Sujet : Re: Bug#919802: libjstun-java: FTBFS (The code being documented
uses packages in the unnamed module)
Date : Mon, 21 Jan 2019 16:58:08 +0100
De : Gilles Filippini 
Pour : 919...@bugs.debian.org, Ying-Chun Liu (PaulLiu)
, Santiago Vila 

Hi,

On Sun, 20 Jan 2019 13:28:57 +0800 "Ying-Chun Liu (PaulLiu)"
 wrote:
> Santiago Vila 於 2019/1/20 上午1:35 寫道:
> > Package: src:libjstun-java
> > Version: 0.7.3+dfsg-1
> > Severity: serious
> > Tags: ftbfs
> > 
> > Dear maintainer:
> > 
> > I tried to build this package in buster but it failed:
> > 
> > 
> > [...]
> >  debian/rules build-indep
> > dh build-indep --with javahelper
> >dh_update_autotools_config -i
> >jh_linkjars -i
> >jh_build -i
> > find src/de -name *.java -and -type f -print0 | xargs -s 512000 -0 
> > /usr/lib/jvm/default-java/bin/javac -g -cp 
> > /usr/share/java/slf4j-jdk14.jar:/usr/share/java/slf4j-api.jar:/usr/share/java/junit.jar:debian/_jh_build.libjstun-java
> >  -d debian/_jh_build.libjstun-java -source 1.7 -target 1.7 -encoding 
> > ISO8859-1
> > warning: [options] bootstrap class path not set in conjunction with -source 
> > 7
> > Note: src/de/javawi/jstun/test/demo/ice/ICENegociator.java uses unchecked 
> > or unsafe operations.
> > Note: Recompile with -Xlint:unchecked for details.
> > 1 warning
> > find src/de -name *.java -and -type f -print0 | xargs -s 512000 -0 
> > /usr/lib/jvm/default-java/bin/javadoc -locale en_US -link 
> > /usr/share/doc/default-jdk-doc/api -link 
> > /usr/share/doc/default-jre-headless/api -classpath 
> > /usr/share/java/slf4j-jdk14.jar:/usr/share/java/slf4j-api.jar:/usr/share/java/junit.jar:debian/_jh_build.libjstun-java
> >  -d debian/_jh_build.javadoc/api -quiet -encoding ISO8859-1 -notimestamp 
> > -source 1.7
> > Creating destination directory: "debian/_jh_build.javadoc/api/"
> > javadoc: error - The code being documented uses packages in the unnamed 
> > module, but the packages defined in /usr/share/doc/default-jdk-doc/api/ are 
> > in named modules.
> > javadoc: error - The code being documented uses packages in the unnamed 
> > module, but the packages defined in 
> > /usr/share/doc/default-jre-headless/api/ are in named modules.
> > 2 errors
> > make: *** [debian/rules:11: build-indep] Error 123
> > dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
> > status 2
> > 
> > 
> > (The above is just how the builds ends and not necessarily the most 
> > relevant part)
> > 
> > The build was made in my autobuilder with "dpkg-buildpackage -A"
> > and it also fails here:
> > 
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libjstun-java.html
> > 
> > where you can get a full build log if you need it.
> > 
> > If this is really a bug in one of the build-depends, please use reassign 
> > and affects,
> > so that this is still visible in the BTS web page for this package.
> > 
> > Thanks.
> > 
> 
> Hi Santiago,
> 
> It seems to me that this line causes the problem.
> find src/de -name *.java -and -type f -print0 | xargs -s 512000 -0
> /usr/lib/jvm/default-java/bin/javadoc -locale en_US -link
> /usr/share/doc/default-jdk-doc/api -link
> /usr/share/doc/default-jre-headless/api -classpath
> /usr/share/java/slf4j-jdk14.jar:/usr/share/java/slf4j-api.jar:/usr/share/java/junit.jar:debian/_jh_build.libjstun-java
> -d debian/_jh_build.javadoc/api -quiet -encoding ISO8859-1 -notimestamp
> -source 1.7
> 
> But if remove "-link /usr/share/doc/default-jdk-doc/api -link
> /usr/share/doc/default-jre-headless/api", then it will pass.
> 
> I'm wondering if javahelper needs to call javadoc in different way.

I've got the very same result for #919803 affecting src:mac-widgets.

Thanks,

_g.





signature.asc
Description: OpenPGP digital signature

Bug#919802: libjstun-java: FTBFS (The code being documented uses packages in the unnamed module)

[Gilles Filippini]

Hi,

On Sun, 20 Jan 2019 13:28:57 +0800 "Ying-Chun Liu (PaulLiu)"
 wrote:
> Santiago Vila 於 2019/1/20 上午1:35 寫道:
> > Package: src:libjstun-java
> > Version: 0.7.3+dfsg-1
> > Severity: serious
> > Tags: ftbfs
> > 
> > Dear maintainer:
> > 
> > I tried to build this package in buster but it failed:
> > 
> > 
> > [...]
> >  debian/rules build-indep
> > dh build-indep --with javahelper
> >dh_update_autotools_config -i
> >jh_linkjars -i
> >jh_build -i
> > find src/de -name *.java -and -type f -print0 | xargs -s 512000 -0 
> > /usr/lib/jvm/default-java/bin/javac -g -cp 
> > /usr/share/java/slf4j-jdk14.jar:/usr/share/java/slf4j-api.jar:/usr/share/java/junit.jar:debian/_jh_build.libjstun-java
> >  -d debian/_jh_build.libjstun-java -source 1.7 -target 1.7 -encoding 
> > ISO8859-1
> > warning: [options] bootstrap class path not set in conjunction with -source 
> > 7
> > Note: src/de/javawi/jstun/test/demo/ice/ICENegociator.java uses unchecked 
> > or unsafe operations.
> > Note: Recompile with -Xlint:unchecked for details.
> > 1 warning
> > find src/de -name *.java -and -type f -print0 | xargs -s 512000 -0 
> > /usr/lib/jvm/default-java/bin/javadoc -locale en_US -link 
> > /usr/share/doc/default-jdk-doc/api -link 
> > /usr/share/doc/default-jre-headless/api -classpath 
> > /usr/share/java/slf4j-jdk14.jar:/usr/share/java/slf4j-api.jar:/usr/share/java/junit.jar:debian/_jh_build.libjstun-java
> >  -d debian/_jh_build.javadoc/api -quiet -encoding ISO8859-1 -notimestamp 
> > -source 1.7
> > Creating destination directory: "debian/_jh_build.javadoc/api/"
> > javadoc: error - The code being documented uses packages in the unnamed 
> > module, but the packages defined in /usr/share/doc/default-jdk-doc/api/ are 
> > in named modules.
> > javadoc: error - The code being documented uses packages in the unnamed 
> > module, but the packages defined in 
> > /usr/share/doc/default-jre-headless/api/ are in named modules.
> > 2 errors
> > make: *** [debian/rules:11: build-indep] Error 123
> > dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit 
> > status 2
> > 
> > 
> > (The above is just how the builds ends and not necessarily the most 
> > relevant part)
> > 
> > The build was made in my autobuilder with "dpkg-buildpackage -A"
> > and it also fails here:
> > 
> > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libjstun-java.html
> > 
> > where you can get a full build log if you need it.
> > 
> > If this is really a bug in one of the build-depends, please use reassign 
> > and affects,
> > so that this is still visible in the BTS web page for this package.
> > 
> > Thanks.
> > 
> 
> Hi Santiago,
> 
> It seems to me that this line causes the problem.
> find src/de -name *.java -and -type f -print0 | xargs -s 512000 -0
> /usr/lib/jvm/default-java/bin/javadoc -locale en_US -link
> /usr/share/doc/default-jdk-doc/api -link
> /usr/share/doc/default-jre-headless/api -classpath
> /usr/share/java/slf4j-jdk14.jar:/usr/share/java/slf4j-api.jar:/usr/share/java/junit.jar:debian/_jh_build.libjstun-java
> -d debian/_jh_build.javadoc/api -quiet -encoding ISO8859-1 -notimestamp
> -source 1.7
> 
> But if remove "-link /usr/share/doc/default-jdk-doc/api -link
> /usr/share/doc/default-jre-headless/api", then it will pass.
> 
> I'm wondering if javahelper needs to call javadoc in different way.

I've got the very same result for #919803 affecting src:mac-widgets.

Thanks,

_g.



signature.asc
Description: OpenPGP digital signature