Bug#893251: jabref 3.8 is started with OpenJDK 9 instead of 8

[tony mancill]

On Sun, Mar 18, 2018 at 04:28:26PM +0100, gregor herrmann wrote:
> > > You can run
> > > JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref
> > Something is wrong here. Did openjdk-8 changed a bit?
> 
> Hm ...
>  
> > $ JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref
> > Exception in thread "main" java.lang.NoSuchMethodError:
> > java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer; at
> > org.apache.logging.log4j.core.appender.OutputStreamManager.flushBuffer(OutputStreamManager.java:292)
> > at
> > org.apache.logging.log4j.core.appender.OutputStreamManager.flush(OutputStreamManager.java:303)
> > at
> > org.apache.logging.log4j.core.appender.OutputStreamManager.closeOutputStream(OutputStreamManager.java:308)
> > at
> > org.apache.logging.log4j.core.appender.OutputStreamManager.releaseSub(OutputStreamManager.java:137)
> > at
> > org.apache.logging.log4j.core.appender.AbstractManager.stop(AbstractManager.java:86)
> > at
> > org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.stop(AbstractOutputStreamAppender.java:142)
> > at
> > org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.stop(AbstractOutputStreamAppender.java:136)
> > at
> > org.apache.logging.log4j.core.config.AbstractConfiguration.stop(AbstractConfiguration.java:359)
> > at
> > org.apache.logging.log4j.core.AbstractLifeCycle.stop(AbstractLifeCycle.java:136)
> > at
> > org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:550)
> > at
> > org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:617)
> > at
> > org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:634)
> > at
> > org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:229)
> > at
> > org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:153)
> > at
> > org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
> > at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
> > at
> > org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:122)
> > at
> > org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39)
> > at
> > org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:46)
> > at
> > org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)
> > at
> > org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:55)
> > at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655) at
> > net.sf.jabref.JabRefMain.(JabRefMain.java:37)
> 
> Ouch, I have to confirm that I get the same errors.
> 
> Maybe that's caused by the recent update of liblog4j2-java 2.8.2-2 -> 2.10.0-1
> 
> Indeed, downgrading liblog4j2-java to 2.8.2-2 helps.
> 
> Not sure if this is a jabref problem or a liblog4j2-java issue; let's
> hope the java experts can shed some light on this bug.

Ouch indeed!  I'm pretty certain that this is an issue with how
liblog4j2-java is being built for Debian.  There is some discussion of
the issue here [1].  Basically, we need to take precautions when
building libraries with JDK 9 that are expected to run with JDK 8
runtimes.

That said, so far I'm not able to build a liblog4j2-java from the
2.10.0-1 source package that will play nicely with jabref, but I'll keep
looking at that and other options (aside from suggesting that we start
recommending a stretch chroot for jabref...)

Cheers,
tony

[1] https://github.com/plasma-umass/doppio/issues/497


signature.asc
Description: PGP signature

Bug#875346: checkstyle no longer FTBFS due to tools.jar

[tony mancill]

Since the update of checkstyle to 8.8 which includes this upstream fix
[1], tools.jar is no longer an issue.  However, it is affected by the
ant javadoc "--ignore-source-errors" issue (same as 893530 [2]).

I'm inclined to close this bug in favor of a new one to track the
javadoc problem.

Cheers,
tony

[1] https://github.com/checkstyle/checkstyle/issues/2905
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893530


signature.asc
Description: PGP signature

Bug#893547: ant: please do not emit --ignore-source-errors on Java 9

[tony mancill]

On Mon, Mar 19, 2018 at 09:16:24PM +0100, Ole Streicher wrote:
> Package: ant
> Version: 1.9.9-6
> Severity: serious
> 
> Dear maintainer,
> 
> to fix #884187, ant added the option "--ignore-source-errors" to
> javadoc. This option is however not available on Java 9, which leads to
> FTBFS on some packages: starjava-topcat, starjava-tools. I will merge
> the relevant bug reports.

Ah, this is also the cause for the current FTBFS state of checkstyle.

I'm in the midst of preparing an update for ant.  Is there any context
in which we want to add "--ignore-source-errors" to the ant javadoc
task, or should this patch [1] be removed entirely?

Thanks,
tony

[1] 
https://anonscm.debian.org/cgit/pkg-java/ant.git/commit/debian/patches/0013-auto-adjust-target.patch?id=2897cc4feed5a7d5bb431096602efecd143c0a78


signature.asc
Description: PGP signature

Bug#893577: sbuild-debian-developer-setup: Should not rely on files in /usr/share/doc

[Stuart Prescott]

Package: sbuild-debian-developer-setup
Version: 0.74.0-1
Severity: serious
Justification: Policy 12.3 Packages must not require the existence of any files 
in /usr/share/doc/ in order to function.

Dear Maintainer,

Thanks for adding sbuild-debian-developer-setup - it indeed looks like a good
way of a new user getting started with sbuild.

At the end of the script, it runs

symlink("/usr/share/doc/sbuild/examples/sbuild-update-all", 
"/etc/cron.daily/sbuild-debian-developer-setup-update-all");

which requires the file in /usr/share/doc to be present. Policy 12.3 says that
packages can't do that and says that such files should be in /usr/share/package
with a symlink into /usr/share/doc/package/ as appropriate.

regards
Stuart

Bug#893525: marked as done (CVE-2018-1000097)

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 00:34:50 +
with message-id 
and subject line Bug#893525: fixed in sharutils 1:4.15.2-3
has caused the Debian Bug report #893525,
regarding CVE-2018-197
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.)


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

This has been assigned CVE-2018-197:
http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg4.html

Proposed patch at:
http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg5.html

Cheers,
Moritz
--- End Message ---
--- Begin Message ---
Source: sharutils
Source-Version: 1:4.15.2-3

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

Debian distribution maintenance software
pp.
Santiago Vila  (supplier of updated sharutils 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: Tue, 20 Mar 2018 01:09:02 +0100
Source: sharutils
Binary: sharutils sharutils-doc
Architecture: source
Version: 1:4.15.2-3
Distribution: unstable
Urgency: medium
Maintainer: Santiago Vila 
Changed-By: Santiago Vila 
Description:
 sharutils  - shar, unshar, uuencode, uudecode
 sharutils-doc - Documentation for GNU sharutils
Closes: 893525
Changes:
 sharutils (1:4.15.2-3) unstable; urgency=medium
 .
   * Apply patch from Petr Pisar to fix heap buffer overflow in unshar.
 This is CVE-2018-197. Closes: #893525.
Checksums-Sha1:
 9aa6ff13e320b0f2afb1af87cf6ea97e60fc4363 1466 sharutils_4.15.2-3.dsc
 0ccde1b63f13c1da583deacaccd9e93a4097c399 7776 sharutils_4.15.2-3.debian.tar.xz
 103ae770f83a747b4008d80d99d77bd17f177348 5498 
sharutils_4.15.2-3_source.buildinfo
Checksums-Sha256:
 b40450f5e5ea6f55684e30a04316a4fa1bbf78d19a4d8ee51bd42c648d49ff2b 1466 
sharutils_4.15.2-3.dsc
 0dbdc08ebe2b274dabbbecc2df1bcb83ef9a2db94a954e43b85afcc6c4ef9efc 7776 
sharutils_4.15.2-3.debian.tar.xz
 cecaa271a3ba2084bc9166099df9347e4c24719f4503b9e75ffdbbb86927a934 5498 
sharutils_4.15.2-3_source.buildinfo
Files:
 28cf1c79b19d630f14988eb65c29fc76 1466 utils optional sharutils_4.15.2-3.dsc
 6da9ccfdda13389cfdeb044cd9e37238 7776 utils optional 
sharutils_4.15.2-3.debian.tar.xz
 beb55139090e48d19ec8aa405b1c62f8 5498 utils optional 
sharutils_4.15.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEE1Uw7+v+wQt44LaXXQc5/C58bizIFAlqwUa4ACgkQQc5/C58b
izLw/Qf/RtxYjGSWFxNe79Klg3iSa0He2ZPouL5J8iPXDjYDEWzpsJfKyUnCzjyM
Ms++ED97j/qZuNYeVfvCxJlELjCr3TyDZH3ZVakKCSTbQbpJGVOQwJfTtbi/ZVSQ
qldFZWK7Ju//WLaN8acyZgm3ca3MLjiserFXnlgY6KHljivly8tOvsRO0AbxkCvo
RJsSqGVGmpPqc9VegzfJy3GsMf3X7mfb9FDVKksXNIyJgOFIanWaSL4D0S8HftWb
Pn68o5RxYjQGSWnLV88xTtd9eE35qQb95/ijmFYZ8EIY9Zb7utVmlVnuYt5p4m0V
zbtBiV/3170gru952pIuWA20Zz+YGw==
=7PLB
-END PGP SIGNATURE End Message ---

Bug#891297: gnome-keyring: Incomplete debian/copyright?

[Chris Lamb]

Hey,

> To provide a bit more reasoning for my change today, this issue isn't
> new to version 3.27 and shouldn't prevent 3.27 or 3.28 from reaching
> Testing.

Nod. :)

> I think it is a huge waste of time to add the names of every person
> mentioned in the translations headers to debian/copyright 

Perhaps that is so; I was just missing some context to the
downgrade -- thank you for clarifying.


Best wishes,

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

Bug#891297: gnome-keyring: Incomplete debian/copyright?

[Jeremy Bicha]

To provide a bit more reasoning for my change today, this issue isn't
new to version 3.27 and shouldn't prevent 3.27 or 3.28 from reaching
Testing.

I think it is a huge waste of time to add the names of every person
mentioned in the translations headers to debian/copyright and at any
rate, it's not something I'm going to be working on right now.

Someone else is of course free to work on this bug.

Thanks,
Jeremy Bicha

Bug#890751: Bug #890751 in rake marked as pending

[georg]

Control: tag -1 pending

Hello,

Bug #890751 in rake 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/rake/commit/ea933f4e55577f043d38bce87ffb02d31ca8fab4


debian/ruby-tests.rb: Ensure tests are working with ruby 2.5

This commit removes the call to the dropped option '-rubygems' in ruby
2.5, makes the run of the testsuite verbose, and, drops the fixed seed,
again. This was introduced in 213d8513e32320b84584066069d0d78bc47f713f,
but now fixed upstream.

Closes: #890751



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/890751

Processed: Bug #890751 in rake marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #890751 [src:rake] rake FTBFS with Ruby 2.5: cannot load such file -- 
ubygems (LoadError)
Added tag(s) pending.

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

Bug#893424: marked as done (Cannot uninstall package)

[Debian Bug Tracking System]

Your message dated Tue, 20 Mar 2018 00:20:08 +
with message-id 
and subject line Bug#893424: fixed in sendmail 8.15.2-11
has caused the Debian Bug report #893424,
regarding Cannot uninstall package
to be marked as done.

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

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


-- 
893424: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893424
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sendmail-base
Version: 8.15.2-10
Severity: serious

Due to a bug in the maintainer script, sendmail-base cannot be uninstalled:

rak@zeta:~$ sudo apt-get remove sendmail-base
[sudo] password for rak:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
  lockfile-progs
Use 'sudo apt autoremove' to remove it.
The following packages will be REMOVED:
  sendmail-base
0 upgraded, 0 newly installed, 1 to remove and 52 not upgraded.
After this operation, 867 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 388617 files and directories currently installed.)
Removing sendmail-base (8.15.2-10) ...
rm: cannot remove '/etc/mail/m4': Is a directory
dpkg: error processing package sendmail-base (--remove):
 installed sendmail-base package pre-removal script subprocess returned error 
exit status 123
Errors were encountered while processing:
 sendmail-base
E: Sub-process /usr/bin/dpkg returned an error code (1)
rak@zeta:~$ sudo apt-get purge sendmail-base
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following package was automatically installed and is no longer required:
  lockfile-progs
Use 'sudo apt autoremove' to remove it.
The following packages will be REMOVED:
  sendmail-base*
0 upgraded, 0 newly installed, 1 to remove and 52 not upgraded.
After this operation, 867 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 388617 files and directories currently installed.)
Removing sendmail-base (8.15.2-10) ...
rm: cannot remove '/etc/mail/m4': Is a directory
dpkg: error processing package sendmail-base (--remove):
 installed sendmail-base package pre-removal script subprocess returned error 
exit status 123
Errors were encountered while processing:
 sendmail-base
E: Sub-process /usr/bin/dpkg returned an error code (1)

-- Package-specific info:
Output of /usr/share/bug/sendmail-base/script:

ls -alR /etc/mail:
/etc/mail:
total 24
drwxr-xr-x 1 root root   138 Mar 18 14:32 .
drwxr-xr-x 1 root root  5364 Mar 18 13:50 ..
-rw-r--r-- 1 root root   281 Jan 13 17:43 address.resolve
drwxr-xr-x 1 root root 0 Jan 13 17:43 m4
drwxr-xr-x 1 root root16 Mar 18 13:30 peers
-rw-r--r-- 1 root root 12235 Mar 18 13:33 sendmail.conf
-rw-r--r-- 1 root root   148 Jan 13 17:43 service.switch
-rw-r--r-- 1 root root   179 Jan 13 17:43 service.switch-nodns

/etc/mail/m4:
total 0
drwxr-xr-x 1 root root   0 Jan 13 17:43 .
drwxr-xr-x 1 root root 138 Mar 18 14:32 ..

/etc/mail/peers:
total 4
drwxr-xr-x 1 root root  16 Mar 18 13:30 .
drwxr-xr-x 1 root root 138 Mar 18 14:32 ..
-rw-r--r-- 1 root root 328 Jan 13 17:43 provider

sendmail.conf:
DAEMON_NETMODE="Static";
DAEMON_NETIF="eth0";
DAEMON_MODE="Daemon";
DAEMON_PARMS="";
DAEMON_HOSTSTATS="No";
DAEMON_MAILSTATS="No";
QUEUE_MODE="${DAEMON_MODE}";
QUEUE_INTERVAL="10m";
QUEUE_PARMS="";
MSP_MODE="Cron";
MSP_INTERVAL="20m";
MSP_PARMS="";
MSP_MAILSTATS="${DAEMON_MAILSTATS}";
MISC_PARMS="";
CRON_MAILTO="root";
CRON_PARMS="";
LOG_CMDS="No";
HANDS_OFF="No";
AGE_DATA="";
DAEMON_RUNASUSER="No";
DAEMON_STATS="${DAEMON_MAILSTATS}";
MSP_STATS="${MSP_MAILSTATS}";



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

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

Versions of packages sendmail-base depends on:
ii  adduser 3.117
ii  lockfile-progs  0.1.17+b1
ii  m4  1.4.18-1
ii  make4.2.1-1
ii  netbase 5.4
ii  perl5.26.1-5

sendmail-base recommends no packages.

Versions of packages sendmail-base suggests:
ii  ca-certificates  20170717
pn  logcheck 

Bug#893542: ntpsec-ntpviz: shares /var/log/ntpstats with ntp, which gets zapped when ntp is purged

[Richard Laager]

On 03/19/2018 02:42 PM, Julian Gilbey wrote:
> Package: ntpsec-ntpviz
> Version: 1.0.0+dfsg1-5
> Severity: serious
> 
> I installed the ntpsec suite, then purged the ntp packages.
> Unfortunately, this zapped the /var/log/ntpstats directory, which is
> needed by ntpsec-ntpviz.  There needs to either been some agreement
> between ntp and ntpsec about the use of this directory, or ntpsec
> needs to use a different log directory.

We have the same situation in reverse too, it seems.

Keeping the same log directory between ntp and ntpsec is desirable, for
several reasons:

- The log format is the same.
- Logs are not lost on conversions from ntp to ntpsec or ntpsec to ntp.
- ntpsec-ntpviz is co-installable with ntp and works. This might be
desirable, if someone wants to continue using ntp but use ntpviz to
create useful graphs.
- IIRC, the default /etc/ntp.conf from ntp references this path, so
keeping the logging path the same means we don't need to change
/etc/ntp.conf on conversions from ntp<->ntpsec.

Likewise for /var/lib/ntp, where the drift file is stored. There again,
it is very desirable to keep the same drift file upon conversions from
ntp<->ntpsec. Otherwise, accuracy is lost until the new ntpd has a
chance to recalculate the drift value.

Related, there's the issue of the ntp user (and ntp group). Those should
not be removed until /var/log/ntpstats is gone. The ntpsec-ntpviz
package also needs the ntp user and group, so coordination is required
there too.

An alternative would be to _copy_ the log files and drift file on
initial installation of ntpsec. This has some downsides:
- Only ntp -> ntpsec conversions benefit. If someone goes the other way,
or goes to ntpsec and then back, logs are still lost, unless ntp also
adopts a copying approach (but then why copy instead of share?).
- ntpsec needs to sed /etc/ntp.conf to change the paths. This breaks
logging if someone moves back to ntp, unless ntp also seds the config
file (again then why not just share?).
- This breaks anything else that someone might be doing with the log
files (and drift file, but that seems unlikely).
- We still need to coordinate on the ntp user (and group), unless ntpsec
uses a different user (and group) too. If so, then I'm deviating from
upstream naming (and years of user history with ntp).

Another alternative would be for both packages to simply _not_ delete
any of these things.

I have wrapped the `rm -rf` with a check for ntp. Here is what I have in
ntpsec.postrm now:

if ! LANG=C dpkg -s ntp > /dev/null 2>&1
then
rm -rf /var/lib/ntp/
rm -rf /var/log/ntpstats/
fi
if ! LANG=C dpkg -s ntpsec-ntpviz 2> /dev/null | \
 grep -qE "^Status: (hold|install)"; then
deluser --system --quiet ntp || true
fi


I suggest the same for ntp.postrm, but with "ntp" changed to "ntpsec":

if ! LANG=C dpkg -s ntpsec > /dev/null 2>&1
then
rm -rf /var/lib/ntp/
rm -rf /var/log/ntpstats/
fi
if ! LANG=C dpkg -s ntpsec-ntpviz 2> /dev/null | \
 grep -qE "^Status: (hold|install)"; then
deluser --system --quiet ntp || true
fi


Is this acceptable on the ntp side? If not, can you propose a different
solution?

-- 
Richard

Processed: Re: gcc-snapshot: AddressSanitizer uses glibc internal functions

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84761
Bug #892096 [gcc-snapshot] gcc-snapshot: AddressSanitizer uses glibc internal 
functions
Set Bug forwarded-to-address to 
'https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84761'.
> tags -1 fixed-upstream
Bug #892096 [gcc-snapshot] gcc-snapshot: AddressSanitizer uses glibc internal 
functions
Added tag(s) fixed-upstream.

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

Bug#892096: gcc-snapshot: AddressSanitizer uses glibc internal functions

[Vincent Lefevre]

Control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84761
Control: tags -1 fixed-upstream

in the sense that this will be OK at least up to glibc 2.27.

See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84761#c9

Author: jakub
Date: Mon Mar 19 20:47:29 2018
New Revision: 258663

URL: https://gcc.gnu.org/viewcvs?rev=258663=gcc=rev
Log:
PR sanitizer/84761
* sanitizer_common/sanitizer_linux_libcdep.cc (__GLIBC_PREREQ):
Define if not defined.
(DL_INTERNAL_FUNCTION): Don't define.
(InitTlsSize): For __i386__ if not compiled against glibc 2.27+
determine at runtime whether to use regparm(3), stdcall calling
convention for older glibcs or normal calling convention for
newer glibcs for call to _dl_get_tls_static_info.

Modified:
trunk/libsanitizer/ChangeLog
trunk/libsanitizer/sanitizer_common/sanitizer_linux_libcdep.cc

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#893371: marked as done (dh-dlang binary-any FTBFS: debian/dh-dlang/usr/share/dh-dlang/gcc-to-ldc-flags.py': No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 19 Mar 2018 23:49:25 +
with message-id 
and subject line Bug#893371: fixed in dh-dlang 0.5
has caused the Debian Bug report #893371,
regarding dh-dlang binary-any FTBFS: 
debian/dh-dlang/usr/share/dh-dlang/gcc-to-ldc-flags.py': 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.)


-- 
893371: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893371
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dh-dlang
Version: 0.4
Severity: serious

https://buildd.debian.org/status/package.php?p=dh-dlang=sid

...
dh binary-arch
   dh_testroot -a
   dh_prep -a
   debian/rules override_dh_install
make[1]: Entering directory '/<>'
dh_install
chmod +x /<>/debian/dh-dlang/usr/share/dh-dlang/gcc-to-ldc-flags.py
chmod: cannot access 
'/<>/debian/dh-dlang/usr/share/dh-dlang/gcc-to-ldc-flags.py': No 
such file or directory
debian/rules:12: recipe for target 'override_dh_install' failed
make[1]: *** [override_dh_install] Error 1
--- End Message ---
--- Begin Message ---
Source: dh-dlang
Source-Version: 0.5

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

Debian distribution maintenance software
pp.
Matthias Klumpp  (supplier of updated dh-dlang package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 20 Mar 2018 10:26:33 +0100
Source: dh-dlang
Binary: dh-dlang default-d-compiler
Architecture: source amd64 all
Version: 0.5
Distribution: unstable
Urgency: medium
Maintainer: Debian D Language Group 
Changed-By: Matthias Klumpp 
Description:
 default-d-compiler - Default D compiler (metapackage)
 dh-dlang   - Packaging helpers for building D code
Closes: 893371
Changes:
 dh-dlang (0.5) unstable; urgency=medium
 .
   * Fix FTBFS when building arch-dependent packages only (Closes: #893371)
   * Ensure minimum DC versions (at least GDC >= 8, LDC >= 1.8)
Checksums-Sha1:
 cfaef3094a8dda61ff3833403d23b65b2ac07abf 1750 dh-dlang_0.5.dsc
 1f525141ab6ada5b02a544003f9fa51be3c8bb83 3668 dh-dlang_0.5.tar.xz
 899e89089b4976077033fce20e6508ce8c8b0f06 2320 default-d-compiler_0.5_amd64.deb
 929cfc409e48550b657691957c8ad6b4f3398003 4204 dh-dlang_0.5_all.deb
 507ab3475d33a824a5d0e3b706edeac9db44d21f 6414 dh-dlang_0.5_amd64.buildinfo
Checksums-Sha256:
 8fd6b20062b57be483e8ef95bfb10f25970d0e43ff2e24fe8d9cef99b2a9d66e 1750 
dh-dlang_0.5.dsc
 ecbc75663b80ec56e00e6c68b58e6eb16d3e467dcd5bbdf19ba7aaa251757cb3 3668 
dh-dlang_0.5.tar.xz
 f1d7be85dcbbb1656c4a927d3bb2e8714f145551a92f7f9b3aa2d6efa8cd75d9 2320 
default-d-compiler_0.5_amd64.deb
 387517bc9ae9b69ce1b95b6b203bab8535a4acab3fe313ffd52c7e612529f0d2 4204 
dh-dlang_0.5_all.deb
 b4e697193154512e01da831856361ba32b81e3ff18db282b0aae143c35d86ad2 6414 
dh-dlang_0.5_amd64.buildinfo
Files:
 08c131c9eb9ccbe529cbea84979e8d22 1750 devel optional dh-dlang_0.5.dsc
 23a7787ce672061ca6a7218356c5cc5a 3668 devel optional dh-dlang_0.5.tar.xz
 20bb2901b8bf6543926ca1a1cc7edf16 2320 devel optional 
default-d-compiler_0.5_amd64.deb
 7098ba91ed6e92928a30e52e43e0e586 4204 devel optional dh-dlang_0.5_all.deb
 db1f246361fe25a2caaac8d90ce587d6 6414 devel optional 
dh-dlang_0.5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEE0zo/DKFrCsxRpgc4SUyKX79N7OsFAlqwSAYPHG1ha0BkZWJp
YW4ub3JnAAoJEElMil+/TezrJg8P+gNsHweMuQf31vb4VPtq075wzrVSlC0Squmw
BFgBDr4AQKM/ro2DEZjqAUWUJnF238f9v99Oqh6QabJZ/f/raHGq0tGrZMbv62ip
seZSP6NA/y80tPFMo1Pqegs32KQk78Jc9JCIszQWaNfd9o6pDb3+Y3x7lP8ut77N
C/sa3b7BOgG0QFR6bSRbG0Wkz3Gobdo00m3FrizGMmKkVvSf+9VrlOBnDH+jzJz1
6dm8mC4lyigb4OLlA2ncRzcKjAo+TrcFNDWAIwMIXxfe/rDS/fQ8aAE3Y2duYuXt
CxannQN8MwXrqETDk9X1aC8Xw+u0ZJIsKkpRtZlEqmzIpSNizoWEZizvGuIb2oWo
qhlmWPslaNKvdHmNlXTCxhyYLlUR/cLfJPp0DuiIDVq9Nm/GKlmeoXaWNasw3dNC
rwagWCfl3hxzeUEIqSfC03OEyVhY+j6WRNOBpMCmkgwlV2FnCLuLKueGe6hAH41b
oWWTOvIpn8mjgZjzICiwCR/AuiHOIKh5Kdz5tmAP9WlqQEwaWzHu/h88cAlboZyL
rDVe/3fFNtrpzR8zPswyoEc00SMTCxGHtp81kLSJ+XpVEs5wMVd0pmevyiU3uGyy

Processed: Re: Bug#892980: gnome-themes-extra: Incomplete debian/copyright?

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #892980 [src:gnome-themes-extra] gnome-themes-extra: Incomplete 
debian/copyright?
Severity set to 'important' from 'serious'

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

Bug#892980: gnome-themes-extra: Incomplete debian/copyright?

[Jeremy Bicha]

Control: severity -1 important

I'm lowering the severity here, but the important part is that this
will be fixed with our next upload which should be soon…

Thanks,
Jeremy Bicha

Bug#892980: Bug #892980 in gnome-themes-standard marked as pending

[jbicha]

Control: tag -1 pending

Hello,

Bug #892980 in gnome-themes-standard 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/gnome-team/gnome-themes-extra/commit/b92933ca2b63d12116f5d2e86fca0f28db784387


debian/copyright: Add more copyright holders (Closes: #892980)



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/892980

Processed: Bug #892980 in gnome-themes-standard marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #892980 [src:gnome-themes-extra] gnome-themes-extra: Incomplete 
debian/copyright?
Added tag(s) pending.

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

Bug#892980: gnome-themes-extra: Incomplete debian/copyright?

[Jeremy Bicha]

Control: notfound -1 3.20.1-2

On Mon, Mar 19, 2018 at 6:44 PM, Chris Lamb  wrote:
> Oh, did I file with the wrong version, or..?

Oops. I meant to adjust https://bugs.debian.org/891297 (where the
copyright issue isn't new and shouldn't prevent a package from
migrating to testing).

Thanks,
Jeremy Bicha

Bug#891297: gnome-keyring: Incomplete debian/copyright?

[Jeremy Bicha]

Control: found -1 3.20.1-2

Processed: Re: Bug#891297: gnome-keyring: Incomplete debian/copyright?

[Debian Bug Tracking System]

Processing control commands:

> found -1 3.20.1-2
Bug #891297 [src:gnome-keyring] gnome-keyring: Incomplete debian/copyright?
Marked as found in versions gnome-keyring/3.20.1-2.

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

Processed: Re: Bug#892980: gnome-themes-extra: Incomplete debian/copyright?

[Debian Bug Tracking System]

Processing control commands:

> notfound -1 3.20.1-2
Bug #892980 [src:gnome-themes-extra] gnome-themes-extra: Incomplete 
debian/copyright?
The source 'gnome-themes-extra' and version '3.20.1-2' do not appear to match 
any binary packages
No longer marked as found in versions gnome-themes-extra/3.20.1-2.

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

Processed: tagging 893557, severity of 893557 is minor ...

[Debian Bug Tracking System]

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

> tags 893557 + patch
Bug #893557 [thin-provisioning-tools] thin-provisioning-tools: FTBFS with glibc 
2.17
Added tag(s) patch.
> severity 893557 minor
Bug #893557 [thin-provisioning-tools] thin-provisioning-tools: FTBFS with glibc 
2.17
Severity set to 'minor' from 'serious'
> retitle 893557 thin-provisioning-tools: FTBFS with -O3
Bug #893557 [thin-provisioning-tools] thin-provisioning-tools: FTBFS with glibc 
2.17
Changed Bug title to 'thin-provisioning-tools: FTBFS with -O3' from 
'thin-provisioning-tools: FTBFS with glibc 2.17'.
> thanks
Stopping processing here.

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

Processed: block 893236 with 893558

[Debian Bug Tracking System]

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

> block 893236 with 893558
Bug #893236 [src:activemq] activemq FTBFS with openjdk-9
893236 was not blocked by any bugs.
893236 was not blocking any bugs.
Added blocking bug(s) of 893236: 893558
> thanks
Stopping processing here.

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

Bug#892980: gnome-themes-extra: Incomplete debian/copyright?

[Chris Lamb]

Hi Jeremy,

> Control: found -1 3.20.1-2

Oh, did I file with the wrong version, or..?


Regards,

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

Bug#893561: libtablelayout-java: license does not seem to meet the DFSG

[Adrian Bunk]

On Mon, Mar 19, 2018 at 10:28:13PM +0100, Francesco Poli (wintermute) wrote:
>...
> The debian/copyright file states, in part:
> 
> | The source code has been modified to make the package suitable for main (see
> | license III. 4.). The package namespace has been changed from
> | info.clearthought.layout to org.debian.tablelayout.
> 
> Personally, I don't think that applying a patch that changes the namespace
> is enough to make the package suitable for Debian main.
> I mean: it's true that it is now possible to create drop-in replacements
> for the Debian package (without further changing the namespace), but it is
> still forbidden to create a modified version that changes the namespace
> back to "info.clearthought".
> 
> I think that this restriction goes beyond what is allowed by DFSG#4.
>...

In https://lists.debian.org/debian-legal/2005/01/msg00142.html you 
agreed entirely that it is OK when software is made DFSG-free through
renaming to avoid trademark violations.

What difference would it make whether our users are forbidden to change
the namespace back to "info.clearthought" due to
1. trademark
2. licence
3. both

The precedent of Firefox and Thunderbird in Debian followed your advice 
that it is OK for 1., and I don't see anything in the DFSG that would 
imply that it would matter whether it is 1. or 2. or 3. that prevents 
our users from changing the namespace back to "info.clearthought".

cu
Adrian

-- 

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

Bug#893536: marked as done (wildfly-common FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Mon, 19 Mar 2018 22:36:22 +
with message-id 
and subject line Bug#893536: fixed in wildfly-common 1.3.1-1
has caused the Debian Bug report #893536,
regarding wildfly-common FTBFS with openjdk-9
to be marked as done.

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

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


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

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

...
[ERROR] Tests run: 9, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 0.609 s 
<<< FAILURE! - in org.wildfly.common.rpc.TestRemoteExceptionCause
[ERROR] serial0(org.wildfly.common.rpc.TestRemoteExceptionCause)  Time elapsed: 
0.197 s  <<< FAILURE!
arrays first differed at element [0]; expected: 
java.lang.StackTraceElement
 but was: 
java.lang.StackTraceElement
at 
org.junit.internal.ComparisonCriteria.arrayEquals(ComparisonCriteria.java:55)
at org.junit.Assert.internalArrayEquals(Assert.java:532)
at org.junit.Assert.assertArrayEquals(Assert.java:283)
at org.junit.Assert.assertArrayEquals(Assert.java:298)
at 
org.wildfly.common.rpc.TestRemoteExceptionCause.lambda$serial0$1(TestRemoteExceptionCause.java:119)
at 
org.wildfly.common.rpc.TestRemoteExceptionCause.doSerialTest(TestRemoteExceptionCause.java:112)
at 
org.wildfly.common.rpc.TestRemoteExceptionCause.serial0(TestRemoteExceptionCause.java:117)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:52)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:369)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:275)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:239)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:160)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:373)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:334)
at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:119)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:407)
Caused by: java.lang.AssertionError: expected: 
java.lang.StackTraceElement
 but was: 
java.lang.StackTraceElement
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at 

Processed: Re: Bug#892980: gnome-themes-extra: Incomplete debian/copyright?

[Debian Bug Tracking System]

Processing control commands:

> found -1 3.20.1-2
Bug #892980 [src:gnome-themes-extra] gnome-themes-extra: Incomplete 
debian/copyright?
The source 'gnome-themes-extra' and version '3.20.1-2' do not appear to match 
any binary packages
Marked as found in versions gnome-themes-extra/3.20.1-2.

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

Bug#893557: thin-provisioning-tools: FTBFS with glibc 2.17

[Steve Langasek]

Package: thin-provisioning-tools
Version: 0.7.4-2
Followup-For: Bug #893557
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu bionic ubuntu-patch

Control: retitle -1 thin-provisioning-tools: FTBFS with -O3
Control: severity -1 minor
Control: tags -1 + patch

Ok, after some trial and error, I've determined that the reason my earlier
test succeeded was because I had built the test preload.so without the
benefit of dpkg-buildflags, which means -O3, which is used by default for
ppc64el on Ubuntu, was missing from the commandline.

The attached patch supersedes the previous one, and fixes the build failure
on Ubuntu ppc64el.  Please consider including it in Debian as well for
benefit of anyone who happens to be using -O3 in dpkg-buildflags (not
actually relevant in the distro case in Debian).

-- 
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 Developerhttp://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru thin-provisioning-tools-0.7.4/debian/control 
thin-provisioning-tools-0.7.4/debian/control
--- thin-provisioning-tools-0.7.4/debian/control2017-11-01 
14:50:39.0 -0700
+++ thin-provisioning-tools-0.7.4/debian/control2018-03-19 
15:31:50.0 -0700
@@ -1,8 +1,7 @@
 Source: thin-provisioning-tools
 Section: admin
 Priority: optional
-Maintainer: Ubuntu Developers 
-XSBC-Original-Maintainer: Debian LVM Team 

+Maintainer: Debian LVM Team 
 Uploaders: Bastian Blank 
 Build-Depends:
  debhelper (>= 9),
diff -Nru thin-provisioning-tools-0.7.4/debian/rules 
thin-provisioning-tools-0.7.4/debian/rules
--- thin-provisioning-tools-0.7.4/debian/rules  2017-11-01 14:50:39.0 
-0700
+++ thin-provisioning-tools-0.7.4/debian/rules  2018-03-19 15:30:07.0 
-0700
@@ -15,7 +15,9 @@
--with-optimisation=-O2
 
 override_dh_auto_test:
-   $(MAKE) -C debian/unit-tests all
+   $(MAKE) -C debian/unit-tests all \
+   CFLAGS="$$(env DEB_CFLAGS_MAINT_STRIP=-O3 \
+   dpkg-buildflags --get CFLAGS)"
+LD_PRELOAD=$(CURDIR)/debian/unit-tests/preload.so $(MAKE) unit-test 
GMOCK_DIR=/usr/src/googletest
 
 override_dh_auto_clean:

Bug#892980: gnome-themes-extra: Incomplete debian/copyright?

[Jeremy Bicha]

Control: found -1 3.20.1-2

Bug#893533: marked as done (qdox2 FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Mon, 19 Mar 2018 22:05:41 +
with message-id 
and subject line Bug#893533: fixed in qdox2 2.0~M8-2
has caused the Debian Bug report #893533,
regarding qdox2 FTBFS with openjdk-9
to be marked as done.

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

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


-- 
893533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893533
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qdox2
Version: 2.0~M7-1
Severity: serious

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

...
[ERROR] Tests run: 8, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.868 s 
<<< FAILURE! - in com.thoughtworks.qdox.EnumsModelTest
[ERROR] 
testAddEnumWithFieldAndConstructorsToModelBinary(com.thoughtworks.qdox.EnumsModelTest)
  Time elapsed: 0.913 s  <<< FAILURE!
junit.framework.AssertionFailedError
at 
com.thoughtworks.qdox.EnumsModelTest.testAddEnumWithFieldAndConstructorsToModelBinary(EnumsModelTest.java:181)
--- End Message ---
--- Begin Message ---
Source: qdox2
Source-Version: 2.0~M8-2

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

Debian distribution maintenance software
pp.
Markus Koschany  (supplier of updated qdox2 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, 19 Mar 2018 22:41:15 +0100
Source: qdox2
Binary: libqdox2-java libqdox2-java-doc
Architecture: source
Version: 2.0~M8-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Markus Koschany 
Description:
 libqdox2-java - quickly parses declarations and Javadoc from Java source
 libqdox2-java-doc - Documentation for QDox
Closes: 893533
Changes:
 qdox2 (2.0~M8-2) unstable; urgency=medium
 .
   * Ignore the test failure for now but forward the issue upstream.
 (Closes: #893533)
Checksums-Sha1:
 75956b09a83edbf526c1dccfc6fcc323139f132a 2285 qdox2_2.0~M8-2.dsc
 06f93cc0a172b13facea9ea73038cef3e9d2 3804 qdox2_2.0~M8-2.debian.tar.xz
 334eef2bffb3c7b7694a6409ee23fe87f852709f 15660 qdox2_2.0~M8-2_amd64.buildinfo
Checksums-Sha256:
 1fa949bf94422ff71b775fa75a8935b2c9c5940659c62950de8eb94c6c977637 2285 
qdox2_2.0~M8-2.dsc
 55360a9165763e6ad1767748e86be0d7b084b4741a12a6c78633292cc5252a32 3804 
qdox2_2.0~M8-2.debian.tar.xz
 1c61365346d20518f1b983464c1ef76d6bd7b0e836420083e00205421d99f6a4 15660 
qdox2_2.0~M8-2_amd64.buildinfo
Files:
 8d643d831c4a1cc15f3c092b5220631b 2285 java optional qdox2_2.0~M8-2.dsc
 ada085eb31642435ff4580bf03987b25 3804 java optional 
qdox2_2.0~M8-2.debian.tar.xz
 27c7512359e4fd54a1547635b82f2fba 15660 java optional 
qdox2_2.0~M8-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAlqwL19fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD
RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp
YW4ub3JnAAoJENmtFLlRO1HkU18P/1qihz55prI+dtH3p/Tm9li63PrAyF9SKufg
kFcMl26fbq3P2QxqGhCeBqTTxuOJ9mtFEiu9q+TZmrJqqZc9ief9S1R3dCcXTweC
/UY1w6c7CYj7/a84zanpozjkKi7C1SiP15ONUQKGU+koDo1WU8QnuGte3kuv+b1H
UIqD2Wd64lbNksXp/JGtLnaOT3CDBtfoI54gOu5ADQvZtipD50aAsQ3LEXmVO/yG
lP5hiaIDFvk4A+hvMWsybJV0Tke8tm/jkmpe3C2chv3cCsfEi/hYbj1aF6ZBnRA6
zqMrWZ7PsLEnLihU4HTi3i3mjQOE4uP6rLNAwhNDg3V0FJgCF8ulv9FWUmPkK4aF
4dFlxtRlO6TwXVIJpoGpIT6aYalTg0g+gCToXA181FUQniyKy36h4TdmSEqYnn/3
XIuY2xD1pGIQM7DmISAxltfCryREfLKO24B87ogqgxm58qan5M1J1ljWrgjNJYtm
r19iqIBnX+QR+OHnKHavQUsDD6z23u+/0nMdFjozsxL93p36xnd1a/lR1TwqRaVG
IegK8ZRsley0ZLhp3r9ViwoCfI+hDBltT6mMigaVWQFinmO+KvmAocChC5EZNu/j
X75PiIuLBCCZehwWtX7eZ6Vv6T68t/SArTHBNu6rLUOWoETC8KIAHGjeztGQXR5w
yp2+C/8X
=SZQ1
-END PGP SIGNATURE End Message ---

Processed: Merge intel-microcode tracking into one bug (part 2)

[Debian Bug Tracking System]

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

> unarchive 886998
Bug #886998 {Done: Henrique de Moraes Holschuh } 
[intel-microcode] intel-microcode: regressions on Haswell, Broadwell 
(crashes/reboots) and Kaby Lake (sleep-to-ram)
Unarchived Bug 886998
> forcemerge 886367 887856
Bug #886367 [intel-microcode] intel-microcode: spectre microcode updates
Bug #886367 [intel-microcode] intel-microcode: spectre microcode updates
Marked as fixed in versions intel-microcode/3.20180312.1~bpo9+1.
Marked as found in versions intel-microcode/3.20171117.1~bpo9+1 and 
intel-microcode/3.20170707.1~deb9u1.
Bug #887856 [intel-microcode] intel-microcode: spectre microcode updates for 
stable
887856 was blocked by: 886998
887856 was not blocking any bugs.
Removed blocking bug(s) of 887856: 886998
Marked as fixed in versions intel-microcode/3.20180312.1.
Marked as found in versions intel-microcode/3.20180108.1+really20171117.1, 
intel-microcode/3.20170707.1, and intel-microcode/3.20171117.1.
Merged 886367 887856
> retitle 886367 intel-microcode: spectre microcode updates
Bug #886367 [intel-microcode] intel-microcode: spectre microcode updates
Bug #887856 [intel-microcode] intel-microcode: spectre microcode updates for 
stable
Ignoring request to change the title of bug#886367 to the same title
Changed Bug title to 'intel-microcode: spectre microcode updates' from 
'intel-microcode: spectre microcode updates for stable'.
> thanks
Stopping processing here.

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

Processed: Re: thin-provisioning-tools: FTBFS with glibc 2.17

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - patch
Bug #893557 [thin-provisioning-tools] thin-provisioning-tools: FTBFS with glibc 
2.17
Removed tag(s) patch.
> severity -1 serious
Bug #893557 [thin-provisioning-tools] thin-provisioning-tools: FTBFS with glibc 
2.17
Severity set to 'serious' from 'important'

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

Processed: Pending fixes for bugs in the qdox2 package

[Debian Bug Tracking System]

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

> tag 893533 + pending
Bug #893533 [src:qdox2] qdox2 FTBFS with openjdk-9
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#893533: Pending fixes for bugs in the qdox2 package

[pkg-java-maintainers]

tag 893533 + pending
thanks

Some bugs in the qdox2 package are closed in revision
2969244f835e1af4519d4129cd8d98526b22419a in branch 'master' by Markus
Koschany

The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-java/qdox2.git/commit/?id=2969244

Commit message:

Ignore the test failure for now but forward the issue upstream.

Closes: #893533

Processed (with 1 error): Merge intel-microcode tracking into one bug

[Debian Bug Tracking System]

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

> found 886367 3.20170707.1
Bug #886367 [intel-microcode] intel-microcode: spectre microcode updates for 
unstable/testing
Marked as found in versions intel-microcode/3.20170707.1.
> forcemerge 886367 887856
Bug #886367 [intel-microcode] intel-microcode: spectre microcode updates for 
unstable/testing
Bug #887856 [intel-microcode] intel-microcode: spectre microcode updates for 
stable
No valid blocking bug(s) given; not doing anything
Failed to forcibly merge 886367: Failure while trying to adjust bugs, please 
report this as a bug: Unknown/archived blocking bug(s):886998.
 at /usr/local/lib/site_perl/Debbugs/Control.pm line 2133.

> retitle 886367 intel-microcode: spectre microcode updates
Bug #886367 [intel-microcode] intel-microcode: spectre microcode updates for 
unstable/testing
Changed Bug title to 'intel-microcode: spectre microcode updates' from 
'intel-microcode: spectre microcode updates for unstable/testing'.
> thanks
Stopping processing here.

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

Bug#869986: closing 869986

[Ferenc Wágner]

close 869986 
thanks

Bug#893458: libundead depends on cruft packages.

[Matthias Klumpp]

2018-03-19 9:29 GMT+01:00 Andreas Tille :
> Hi,
>
> On Mon, Mar 19, 2018 at 02:51:38AM +, peter green wrote:
>> Package: libundead
>> Version: 1.0.9-1
>> Severity: serious
>>
>> libundead-dev depends on libphobos2-ldc-dev
>> libundead0 depends on libphobos2-ldc76
>>
>> Neither of these packages is built by ldc anymore. They seem to have been 
>> replaced by  libphobos2-ldc-shared-dev and libphobos2-ldc-shared78
>>
>> It seems there has not been an attempt to been an attempt to binnmu 
>> libundead for this transition in Debian. When we binnmu'd it in raspbian the 
>> dependency on libphobos2-ldc76 was replaced by libphobos2-ldc-shared78 but 
>> the dependency on libphobos2-ldc-dev remained.
>
> The depencency on libphobos2-ldc-dev was explicitly added by Matthias
> Klumpp.  I guess it needs to be replaced by libphobos2-ldc-shared-dev
> but want to let Matthias confirm this assumption before uploading.

Adding that explicit dependency was a mistake on my side - since it is
the compiler's standard library, and since we don't actually ship any
D code that doesn't depend on it, having that explicit dependency
doesn't make sense. And even if you compile without Phobos, any D
compiler will pull it in on Debian anyway, so if you have a D
compiler, you have Phobos too.

I dropped the dependency in Git, and also made the package use
dh-dlang to pick the right compiler and compiler flags.
Feel free to upload the changes if you want to, and thanks for asking
about the dependency!

Cheers,
Matthias


-- 
I welcome VSRE emails. See http://vsre.info/

Processed: closing 869986

[Debian Bug Tracking System]

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

> close 869986
Bug #869986 {Done: Ferenc Wágner } [src:pacemaker] pacemaker 
FTBFS: missing symbols
Bug 869986 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Processed: closing 869986

[Debian Bug Tracking System]

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

> close 869986
Bug #869986 [src:pacemaker] pacemaker FTBFS: missing symbols
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#893561: libtablelayout-java: license does not seem to meet the DFSG

[Francesco Poli (wintermute)]

Package: libtablelayout-java
Version: 20090826-3
Severity: serious
Justification: Policy 2.2.1

Hello!
Thanks for maintaining this package in Debian.

I noticed that the license was
[discussed](https://lists.debian.org/debian-legal/2009/06/msg00050.html)
on debian-legal a long time ago.
My
[opinion](https://lists.debian.org/debian-legal/2009/06/msg00053.html)
was that at least two clauses fail to meet the DFSG.

The debian/copyright file states, in part:

| The source code has been modified to make the package suitable for main (see
| license III. 4.). The package namespace has been changed from
| info.clearthought.layout to org.debian.tablelayout.

Personally, I don't think that applying a patch that changes the namespace
is enough to make the package suitable for Debian main.
I mean: it's true that it is now possible to create drop-in replacements
for the Debian package (without further changing the namespace), but it is
still forbidden to create a modified version that changes the namespace
back to "info.clearthought".

I think that this restriction goes beyond what is allowed by DFSG#4.

Additionally, the license is clearly GPL-incompatible, which may
be an issue for other packages that link with this library.


Is it possible to persuade the upstream copyright holder to
drop clauses III.3 and III.4?
Or, even better, to re-license the library under well-vetted and
clearly DFSG-free terms, such as the
[Expat/MIT license](http://www.jclark.com/xml/copying.txt)
or the
[zlib license](http://www.zlib.net/zlib_license.html)
?

I hope this can be done.
Thanks for your time and helpfulness!

Bug#869986: pacemaker FTBFS: missing symbols

[Ferenc Wágner]

Control: fixed 869986 1.1.18~rc3-1
Control: done 869986

Pacemaker builds again for some time, looks like the new upload was
enough to fix this breakage after all.
-- 
Feri

Processed (with 1 error): Re: Bug#869986: pacemaker FTBFS: missing symbols

[Debian Bug Tracking System]

Processing control commands:

> fixed 869986 1.1.18~rc3-1
Bug #869986 [src:pacemaker] pacemaker FTBFS: missing symbols
Marked as fixed in versions pacemaker/1.1.18~rc3-1.
> done 869986
Unknown command or malformed arguments to command.


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

Processed: Re: activemq FTBFS with openjdk-9

[Debian Bug Tracking System]

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

> clone 893236 -1
Bug #893236 [src:activemq] activemq FTBFS with openjdk-9
Bug 893236 cloned as bug 893558
> reassign -1 src:openjdk-9
Bug #893558 [src:activemq] activemq FTBFS with openjdk-9
Bug reassigned from package 'src:activemq' to 'src:openjdk-9'.
No longer marked as found in versions activemq/5.15.3-1.
Ignoring request to alter fixed versions of bug #893558 to the same values 
previously set
> retitle -1 openjdk9: NullPointerException when building MethodSubHeader
Bug #893558 [src:openjdk-9] activemq FTBFS with openjdk-9
Changed Bug title to 'openjdk9: NullPointerException when building 
MethodSubHeader' from 'activemq FTBFS with openjdk-9'.
> forwarded -1 https://bugs.openjdk.java.net/browse/JDK-8199307
Bug #893558 [src:openjdk-9] openjdk9: NullPointerException when building 
MethodSubHeader
Set Bug forwarded-to-address to 
'https://bugs.openjdk.java.net/browse/JDK-8199307'.
> thanks
Stopping processing here.

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

Bug#892708: marked as done (kicad-demos: missing Breaks+Replaces: kicad-common (<< 5))

[Debian Bug Tracking System]

Your message dated Mon, 19 Mar 2018 21:20:26 +
with message-id 
and subject line Bug#892708: fixed in kicad 5.0.0~rc1+dfsg1+20180318-1
has caused the Debian Bug report #892708,
regarding kicad-demos: missing Breaks+Replaces: kicad-common (<< 5)
to be marked as done.

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

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


-- 
892708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892708
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kicad-demos
Version: 5.0.0~rc1+dfsg1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package kicad-demos.
  Preparing to unpack .../kicad-demos_5.0.0~rc1+dfsg1-1_all.deb ...
  Unpacking kicad-demos (5.0.0~rc1+dfsg1-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/kicad-demos_5.0.0~rc1+dfsg1-1_all.deb (--unpack):
   trying to overwrite '/usr/share/kicad/demos/complex_hierarchy/ampli_ht.sch', 
which is also in package kicad-common 4.0.7+dfsg1-1
  Errors were encountered while processing:
   /var/cache/apt/archives/kicad-demos_5.0.0~rc1+dfsg1-1_all.deb


cheers,

Andreas


kicad-common=4.0.7+dfsg1-1_kicad-demos=5.0.0~rc1+dfsg1-1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: kicad
Source-Version: 5.0.0~rc1+dfsg1+20180318-1

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

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

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

Debian distribution maintenance software
pp.
Carsten Schoenert  (supplier of updated kicad 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, 19 Mar 2018 19:11:39 +0100
Source: kicad
Binary: kicad kicad-common kicad-demos kicad-doc-ca kicad-doc-de kicad-doc-en 
kicad-doc-es kicad-doc-fr kicad-doc-it kicad-doc-ja kicad-doc-nl kicad-doc-pl 
kicad-doc-ru kicad-libraries
Architecture: source
Version: 5.0.0~rc1+dfsg1+20180318-1
Distribution: experimental
Urgency: medium
Maintainer: Debian Electronics Team 

Changed-By: Carsten Schoenert 
Description:
 kicad  - Electronic schematic and PCB design software
 kicad-common - Old common files used by kicad - Transitional Package
 kicad-demos - Demo projects for kicad
 kicad-doc-ca - Kicad help files (Catalan)
 kicad-doc-de - Kicad help files (German)
 kicad-doc-en - Kicad help files (English)
 kicad-doc-es - Kicad help files (Spanish)
 kicad-doc-fr - Kicad help files (French)
 kicad-doc-it - Kicad help files (Italian)
 kicad-doc-ja - Kicad help files (Japanese)
 kicad-doc-nl - Kicad help files (Dutch)
 kicad-doc-pl - Kicad help files (Polish)
 kicad-doc-ru - Kicad help files (Russian)
 kicad-libraries - Virtual package providing common used libraries by kicad
Closes: 892708
Changes:
 kicad (5.0.0~rc1+dfsg1+20180318-1) experimental; urgency=medium
 .
   * [fcfaee0] kicad-demos: adjusting B+R against previous kicad{-common} pkg
 + Like for done for the virtual package kicad-libraries the package
   kicad-demos also need a valid Breaks and Replace against the now
   transitional package kicad-common so dpkg isn't complaining about files
which appears to be within two different packages.
 (Closes: #892708)
   * [12fa90d] kicad-libraries: remove Recommends on kicad-common
 + Of course we won't recommending a now transitional package.
   * [08bc66e] New upstream version 5.0.0~rc1+dfsg1+20180318
   * [0a2d284] rebuild patch queue from patch-queue branch
 + removed patches (applied upstream)
   fixes/fix-misspelled-Appearence-Appearance.patch
   

Bug#893236: activemq FTBFS with openjdk-9

[Markus Koschany]

clone 893236 -1
reassign -1 src:openjdk-9
retitle -1 openjdk9: NullPointerException when building MethodSubHeader
forwarded -1 https://bugs.openjdk.java.net/browse/JDK-8199307
thanks

The NullPointerException looks like an OpenJDK bug to me. This was
already reported upstream. The doclint feature is already set to "none"
in activemq, so I would expect that any javadoc warning is not treated
as an error. Currently the only way to work around this for activemq is
to disable the documentation completely.

Markus



signature.asc
Description: OpenPGP digital signature

Processed: affects 893547

[Debian Bug Tracking System]

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

> affects 893547 src:starjava-ttools src:starjava-topcat
Bug #893547 [ant] ant: please do not emit --ignore-source-errors on Java 9
Bug #893530 [ant] starjava-ttools FTBFS with openjdk-9
Bug #893531 [ant] starjava-topcat FTBFS with openjdk-9
Added indication that 893547 affects src:starjava-ttools and src:starjava-topcat
Added indication that 893530 affects src:starjava-ttools and src:starjava-topcat
Added indication that 893531 affects src:starjava-ttools and src:starjava-topcat
> thanks
Stopping processing here.

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

Bug#893554: range-v3 FTBFS

[Adrian Bunk]

Source: range-v3
Version: 0.3.5-1
Severity: serious

Some recent change in unstable makes range-v3 FTBFS:

https://tests.reproducible-builds.org/debian/history/range-v3.html
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/range-v3.html

...
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:70:26: error: no 
matching function for call to 'initializer_list(const volatile 
std::initializer_list&)'
 begin(r)
 ~^~~
/build/1st/range-v3-0.3.5/include/range/v3/detail/config.hpp:99:32: note: in 
definition of macro 'RANGES_AUTO_RETURN_NOEXCEPT'
 noexcept(noexcept(decltype(__VA_ARGS__)(__VA_ARGS__)))  \
^~~
In file included from /usr/include/c++/7/bits/range_access.h:36:0,
 from /usr/include/c++/7/list:62,
 from /build/1st/range-v3-0.3.5/test/action/push_front.cpp:10:
/usr/include/c++/7/initializer_list:47:11: note: candidate: constexpr 
std::initializer_list::initializer_list(const std::initializer_list&) 

 class initializer_list
   ^~~~
/usr/include/c++/7/initializer_list:47:11: note:   conversion of argument 1 
would be ill-formed:
In file included from 
/build/1st/range-v3-0.3.5/include/range/v3/range_fwd.hpp:21:0,
 from 
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:22,
 from /build/1st/range-v3-0.3.5/include/range/v3/core.hpp:17,
 from /build/1st/range-v3-0.3.5/test/action/push_front.cpp:12:
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:70:26: error: binding 
reference of type 'const std::initializer_list&' to 'const volatile 
std::initializer_list' discards qualifiers
 begin(r)
 ~^~~
/build/1st/range-v3-0.3.5/include/range/v3/detail/config.hpp:99:32: note: in 
definition of macro 'RANGES_AUTO_RETURN_NOEXCEPT'
 noexcept(noexcept(decltype(__VA_ARGS__)(__VA_ARGS__)))  \
^~~
In file included from /usr/include/c++/7/bits/range_access.h:36:0,
 from /usr/include/c++/7/list:62,
 from /build/1st/range-v3-0.3.5/test/action/push_front.cpp:10:
/usr/include/c++/7/initializer_list:47:11: note: candidate: constexpr 
std::initializer_list::initializer_list(std::initializer_list&&) 

 class initializer_list
   ^~~~
/usr/include/c++/7/initializer_list:47:11: note:   conversion of argument 1 
would be ill-formed:
In file included from 
/build/1st/range-v3-0.3.5/include/range/v3/range_fwd.hpp:21:0,
 from 
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:22,
 from /build/1st/range-v3-0.3.5/include/range/v3/core.hpp:17,
 from /build/1st/range-v3-0.3.5/test/action/push_front.cpp:12:
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:70:26: error: cannot 
bind rvalue reference of type 'std::initializer_list&&' to lvalue of type 
'const volatile std::initializer_list'
 begin(r)
 ~^~~
/build/1st/range-v3-0.3.5/include/range/v3/detail/config.hpp:99:32: note: in 
definition of macro 'RANGES_AUTO_RETURN_NOEXCEPT'
 noexcept(noexcept(decltype(__VA_ARGS__)(__VA_ARGS__)))  \
^~~
In file included from /usr/include/c++/7/bits/range_access.h:36:0,
 from /usr/include/c++/7/list:62,
 from /build/1st/range-v3-0.3.5/test/action/push_front.cpp:10:
/usr/include/c++/7/initializer_list:89:5: note:   initializing argument 1 of 
'constexpr const _Tp* std::begin(std::initializer_list<_Tp>) [with _Tp = int]'
 begin(initializer_list<_Tp> __ils) noexcept
 ^
In file included from 
/build/1st/range-v3-0.3.5/include/range/v3/range_fwd.hpp:21:0,
 from 
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:22,
 from /build/1st/range-v3-0.3.5/include/range/v3/core.hpp:17,
 from /build/1st/range-v3-0.3.5/test/action/push_front.cpp:12:
/build/1st/range-v3-0.3.5/include/range/v3/begin_end.hpp:70:26: error: no 
matching function for call to 'initializer_list(const volatile 
std::initializer_list&)'
 begin(r)
 ~^~~
/build/1st/range-v3-0.3.5/include/range/v3/detail/config.hpp:99:45: note: in 
definition of macro 'RANGES_AUTO_RETURN_NOEXCEPT'
 noexcept(noexcept(decltype(__VA_ARGS__)(__VA_ARGS__)))  \
 ^~~
In file included from /usr/include/c++/7/bits/range_access.h:36:0,
 from /usr/include/c++/7/list:62,
 from /build/1st/range-v3-0.3.5/test/action/push_front.cpp:10:
/usr/include/c++/7/initializer_list:47:11: note: candidate: constexpr 
std::initializer_list::initializer_list(const std::initializer_list&) 

 class initializer_list
   ^~~~
/usr/include/c++/7/initializer_list:47:11: 

Bug#893553: visualvm FTBFS with openjdk-9

[Adrian Bunk]

Source: visualvm
Version: 1.3.9-1
Severity: serious
Tags: buster sid

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

...
compile:
 [nb-javac] Compiling 15 source files to 
/build/1st/visualvm-1.3.9/netbeans/profiler.oql/build/classes
[parseprojectxml] warning: [options] bootstrap class path not set in 
conjunction with -source 1.6
[parseprojectxml] warning: [options] source value 1.6 is obsolete and will be 
removed in a future release
[parseprojectxml] warning: [options] target value 1.6 is obsolete and will be 
removed in a future release
[parseprojectxml] warning: [options] To suppress warnings about obsolete 
options, use -Xlint:-options.
[parseprojectxml] 
/build/1st/visualvm-1.3.9/netbeans/nbbuild/build/public-package-jars/org-netbeans-api-annotations-common.jar(/org/netbeans/api/annotations/common/NonNull.class):
 warning: Cannot find annotation method 'when()' in type 'Nonnull': class file 
for javax.annotation.Nonnull not found
[parseprojectxml] error: java.nio.file.NoSuchFileException: 
/build/1st/visualvm-1.3.9/netbeans/profiler.oql/build/classes/META-INF/services/org.netbeans.modules.profiler.spi.IconsProvider
[parseprojectxml] warning: No processor claimed any of these annotations: 
org.netbeans.api.annotations.common.NonNull
[parseprojectxml] 
/build/1st/visualvm-1.3.9/netbeans/nbbuild/build/public-package-jars/org-netbeans-api-annotations-common.jar(/org/netbeans/api/annotations/common/NonNull.class):
 warning: Cannot find annotation method 'when()' in type 'Nonnull': class file 
for javax.annotation.Nonnull not found
[parseprojectxml] 1 error
[parseprojectxml] 7 warnings

BUILD FAILED
/build/1st/visualvm-1.3.9/netbeans/nbbuild/templates/projectized.xml:123: The 
following error occurred while executing this line:
/build/1st/visualvm-1.3.9/netbeans/nbbuild/templates/common.xml:220: Compile 
failed; see the compiler error output for details.

Total time: 28 seconds
make[1]: *** [debian/rules:32: override_dh_auto_build] Error 1

Bug#893552: lcm FTBFS with openjdk-9

[Adrian Bunk]

Source: lcm
Version: 1.3.1+repack1-1
Severity: serious
Tags: buster sid

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

...
Making all in lcm-java
make[3]: Entering directory '/build/1st/lcm-1.3.1+repack1/lcm-java'
chmod 755 lcm-logplayer-gui
chmod 755 lcm-spy
mkdir -p /build/1st/lcm-1.3.1+repack1/lcm-java/build
CLASSPATH=/build/1st/lcm-1.3.1+repack1/lcm-java/build:.//build/1st/lcm-1.3.1+repack1/lcm-java/build${CLASSPATH:+":$CLASSPATH"}
 /usr/bin/javac -d /build/1st/lcm-1.3.1+repack1/lcm-java/build  -source 1.5 
-target 1.5 -classpath /usr/share/java/jchart2d.jar  lcm/lcm/Provider.java 
lcm/lcm/LogFileProvider.java lcm/lcm/LCMDataOutputStream.java 
lcm/lcm/TCPService.java lcm/lcm/URLParser.java lcm/lcm/LCM.java 
lcm/lcm/MessageAggregator.java lcm/lcm/MemqProvider.java 
lcm/lcm/TCPProvider.java lcm/lcm/LCMSubscriber.java lcm/lcm/LCMEncodable.java 
lcm/lcm/UDPMulticastProvider.java lcm/lcm/LCMDataInputStream.java 
lcm/spy/ObjectPanel.java lcm/spy/SpyPlugin.java lcm/spy/LCMTypeDatabase.java 
lcm/spy/Spy.java lcm/spy/ChannelData.java lcm/spy/ChartData.java 
lcm/spy/ZoomableChartScrollWheel.java lcm/util/ColorMapper.java 
lcm/util/ClassDiscoverer.java lcm/util/ParameterListener.java 
lcm/util/JImage.java lcm/util/BufferedRandomAccessFile.java 
lcm/util/ParameterGUI.java lcm/util/TableSorter.java 
lcm/logging/LogDiagnostic.java lcm/logging/JScrubberListener.java 
lcm/logging/Log.java lcm/logging/LogPlayer.java lcm/logging/JScrubber.java
warning: [options] bootstrap class path not set in conjunction with -source 1.5
error: Source option 1.5 is no longer supported. Use 1.6 or later.
error: Target option 1.5 is no longer supported. Use 1.6 or later.
make[3]: *** [Makefile:415: classnoinst.stamp] Error 2

Processed: Merging bugs

[Debian Bug Tracking System]

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

> forcemerge 893547 893530 893531
Bug #893547 [ant] ant: please do not emit --ignore-source-errors on Java 9
Bug #893530 [ant] starjava-ttools FTBFS with openjdk-9
Removed indication that 893530 affects src:starjava-topcat
Bug #893531 [ant] starjava-topcat FTBFS with openjdk-9
Removed indication that 893531 affects src:starjava-ttools
Merged 893530 893531 893547
> thanks
Stopping processing here.

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

Bug#893251: jabref 3.8 is started with OpenJDK 9 instead of 8

[c.buhtz]

Dear Gregor,

thank you very much for your fast reply.

> True, this is already reported as #890905/#893138.
> I ('m trying to) merge those two bugs.

Sorry, for reporting again. I noticed that bugs. But as a
Java-foreigner it wasn't clear for me if they address the same issue.

> You can run
> JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref

Something is wrong here. Did openjdk-8 changed a bit?

$ JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref
Exception in thread "main" java.lang.NoSuchMethodError:
java.nio.ByteBuffer.flip()Ljava/nio/ByteBuffer; at
org.apache.logging.log4j.core.appender.OutputStreamManager.flushBuffer(OutputStreamManager.java:292)
at
org.apache.logging.log4j.core.appender.OutputStreamManager.flush(OutputStreamManager.java:303)
at
org.apache.logging.log4j.core.appender.OutputStreamManager.closeOutputStream(OutputStreamManager.java:308)
at
org.apache.logging.log4j.core.appender.OutputStreamManager.releaseSub(OutputStreamManager.java:137)
at
org.apache.logging.log4j.core.appender.AbstractManager.stop(AbstractManager.java:86)
at
org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.stop(AbstractOutputStreamAppender.java:142)
at
org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.stop(AbstractOutputStreamAppender.java:136)
at
org.apache.logging.log4j.core.config.AbstractConfiguration.stop(AbstractConfiguration.java:359)
at
org.apache.logging.log4j.core.AbstractLifeCycle.stop(AbstractLifeCycle.java:136)
at
org.apache.logging.log4j.core.LoggerContext.setConfiguration(LoggerContext.java:550)
at
org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:617)
at
org.apache.logging.log4j.core.LoggerContext.reconfigure(LoggerContext.java:634)
at
org.apache.logging.log4j.core.LoggerContext.start(LoggerContext.java:229)
at
org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:153)
at
org.apache.logging.log4j.core.impl.Log4jContextFactory.getContext(Log4jContextFactory.java:45)
at org.apache.logging.log4j.LogManager.getContext(LogManager.java:194)
at
org.apache.logging.log4j.spi.AbstractLoggerAdapter.getContext(AbstractLoggerAdapter.java:122)
at
org.apache.logging.log4j.jcl.LogAdapter.getContext(LogAdapter.java:39)
at
org.apache.logging.log4j.spi.AbstractLoggerAdapter.getLogger(AbstractLoggerAdapter.java:46)
at
org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:40)
at
org.apache.logging.log4j.jcl.LogFactoryImpl.getInstance(LogFactoryImpl.java:55)
at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:655) at
net.sf.jabref.JabRefMain.(JabRefMain.java:37)



signature.asc
Description: Digital Signature

Processed (with 1 error): Merging bugs

[Debian Bug Tracking System]

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

> merge 893547 893530 893531
Bug #893547 [ant] ant: please do not emit --ignore-source-errors on Java 9
Unable to merge bugs because:
affects of #893530 is 'src:starjava-topcat' not ''
affects of #893531 is 'src:starjava-ttools' not ''
Failed to merge 893547: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed (with 2 errors): Merging bugs

[Debian Bug Tracking System]

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

> reassign 893530 ant 1.9.9-6
Bug #893530 [src:starjava-ttools] starjava-ttools FTBFS with openjdk-9
Bug reassigned from package 'src:starjava-ttools' to 'ant'.
No longer marked as found in versions starjava-ttools/3.1.2-1.
Ignoring request to alter fixed versions of bug #893530 to the same values 
previously set
Bug #893530 [ant] starjava-ttools FTBFS with openjdk-9
Marked as found in versions ant/1.9.9-6.
> affects 893530 src:starjava-topcat
Bug #893530 [ant] starjava-ttools FTBFS with openjdk-9
Ignoring request to set affects of bug 893530 to the same value previously set
> merge 893547 893530
Bug #893547 [ant] ant: please do not emit --ignore-source-errors on Java 9
Unable to merge bugs because:
affects of #893530 is 'src:starjava-topcat' not ''
Failed to merge 893547: Did not alter merged bugs.

> reassign 893531 ant 1.9.9-6
Bug #893531 [src:starjava-topcat] starjava-topcat FTBFS with openjdk-9
Bug reassigned from package 'src:starjava-topcat' to 'ant'.
No longer marked as found in versions starjava-topcat/4.5.1-1.
Ignoring request to alter fixed versions of bug #893531 to the same values 
previously set
Bug #893531 [ant] starjava-topcat FTBFS with openjdk-9
Marked as found in versions ant/1.9.9-6.
> affects 893531 src:starjava-ttools
Bug #893531 [ant] starjava-topcat FTBFS with openjdk-9
Ignoring request to set affects of bug 893531 to the same value previously set
> merge 893547 893531
Failed to merge 893547: failed to get lock on 
/org/bugs.debian.org/spool/lock/893547 -- Unable to lock 
/org/bugs.debian.org/spool/lock/893547 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/893547 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/893547 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/893547 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/893547 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/893547 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/893547 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/893547 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/893547 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/893547 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
$locks = {
   'locks' => {}
 };
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 622.

> thanks
Stopping processing here.

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

Processed (with 4 errors): Merging bugs

[Debian Bug Tracking System]

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

> assign 893530 ant 1.9.9-6
Unknown command or malformed arguments to command.
> affects 893530 src:starjava-topcat
Bug #893530 [src:starjava-ttools] starjava-ttools FTBFS with openjdk-9
Added indication that 893530 affects src:starjava-topcat
> merge 893547 893530
Bug #893547 [ant] ant: please do not emit --ignore-source-errors on Java 9
Unable to merge bugs because:
affects of #893530 is 'src:starjava-topcat' not ''
package of #893530 is 'src:starjava-ttools' not 'ant'
Failed to merge 893547: Did not alter merged bugs.

> assign 893531 ant 1.9.9-6
Unknown command or malformed arguments to command.
> affects 893531 src:starjava-ttools
Bug #893531 [src:starjava-topcat] starjava-topcat FTBFS with openjdk-9
Added indication that 893531 affects src:starjava-ttools
> merge 893547 893531
Failed to merge 893547: failed to get lock on 
/org/bugs.debian.org/spool/lock/893547 -- Unable to lock 
/org/bugs.debian.org/spool/lock/893547 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/893547 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/893547 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/893547 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/893547 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/893547 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/893547 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/893547 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/893547 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
Unable to lock /org/bugs.debian.org/spool/lock/893547 Resource temporarily 
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 664.
$locks = {
   'locks' => {}
 };
 at /usr/local/lib/site_perl/Debbugs/Common.pm line 622.

> thanks
Stopping processing here.

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

Bug#893547: ant: please do not emit --ignore-source-errors on Java 9

[Ole Streicher]

Package: ant
Version: 1.9.9-6
Severity: serious

Dear maintainer,

to fix #884187, ant added the option "--ignore-source-errors" to
javadoc. This option is however not available on Java 9, which leads to
FTBFS on some packages: starjava-topcat, starjava-tools. I will merge
the relevant bug reports.

Best regards

Ole

Processed: curl: CVE-2018-1000120 CVE-2018-1000121 CVE-2018-1000122

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 7.38.0-4+deb8u10
Bug #893546 [src:curl] curl: CVE-2018-1000120 CVE-2018-1000121 CVE-2018-1000122
Marked as fixed in versions curl/7.38.0-4+deb8u10.
> fixed -1 7.52.1-5+deb9u5
Bug #893546 [src:curl] curl: CVE-2018-1000120 CVE-2018-1000121 CVE-2018-1000122
Marked as fixed in versions curl/7.52.1-5+deb9u5.

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

Bug#893546: curl: CVE-2018-1000120 CVE-2018-1000121 CVE-2018-1000122

[Salvatore Bonaccorso]

Source: curl
Version: 7.38.0-4
Severity: serious
Tags: patch security upstream fixed-upstream
Justification: regression with respect to stable with security fixes
Control: fixed -1 7.38.0-4+deb8u10
Control: fixed -1 7.52.1-5+deb9u5

Hi,

the following vulnerabilities were published for curl.

CVE-2018-1000120[0]:
| A buffer overflow exists in curl 7.12.3 to and including curl 7.58.0
| in the FTP URL handling that allows an attacker to cause a denial of
| service or worse.

CVE-2018-1000121[1]:
| A NULL pointer dereference exists in curl 7.21.0 to and including curl
| 7.58.0 in the LDAP code that allows an attacker to cause a denial of
| service

CVE-2018-1000122[2]:
| A buffer over-read exists in curl 7.20.0 to and including curl 7.58.0
| in the RTSP+RTP handling code that allows an attacker to cause a
| denial of service or information leakage

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-1000120
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000120
[1] https://security-tracker.debian.org/tracker/CVE-2018-1000121
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000121
[2] https://security-tracker.debian.org/tracker/CVE-2018-1000122
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000122

Regards,
Salvatore

Processed: merge duplicates - yes, jupyter is mostly broken

[Debian Bug Tracking System]

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

> # maybe should be on pyzmq, since that's probably where
> # it will really get fixed
> reassign 893474 python3-tornado
Bug #893474 [src:jupyter-core] jupyter-core: AttributeError on launch since 
last update of python 3.6 in Sid
Bug reassigned from package 'src:jupyter-core' to 'python3-tornado'.
No longer marked as found in versions jupyter-core/4.4.0-2.
Ignoring request to alter fixed versions of bug #893474 to the same values 
previously set
> reassign 893385 python3-tornado
Bug #893385 [src:ipykernel] ipykernel FTBFS: test failures
Bug reassigned from package 'src:ipykernel' to 'python3-tornado'.
No longer marked as found in versions ipykernel/4.8.2-2.
Ignoring request to alter fixed versions of bug #893385 to the same values 
previously set
> forcemerge 893360 893474 893385
Bug #893360 [python3-tornado] python3-tornado 5.0.0 breaks python3-zmq
Bug #893474 [python3-tornado] jupyter-core: AttributeError on launch since last 
update of python 3.6 in Sid
Severity set to 'serious' from 'grave'
Added indication that 893474 affects 
python3-ipykernel,jupyter-notebook,jupyter-nbconvert
Marked as found in versions python-tornado/5.0.0-1.
Added tag(s) pending.
Bug #893385 [python3-tornado] ipykernel FTBFS: test failures
Removed indication that 893385 affects src:jupyter-notebook
Added indication that 893385 affects 
python3-ipykernel,jupyter-notebook,jupyter-nbconvert
Marked as found in versions python-tornado/5.0.0-1.
Added tag(s) pending.
Merged 893360 893385 893474
> affects 893360 src:jupyter-notebook src:jupyter-client src:ipykernel
Bug #893360 [python3-tornado] python3-tornado 5.0.0 breaks python3-zmq
Bug #893385 [python3-tornado] ipykernel FTBFS: test failures
Bug #893474 [python3-tornado] jupyter-core: AttributeError on launch since last 
update of python 3.6 in Sid
Added indication that 893360 affects src:jupyter-notebook, src:jupyter-client, 
and src:ipykernel
Added indication that 893385 affects src:jupyter-notebook, src:jupyter-client, 
and src:ipykernel
Added indication that 893474 affects src:jupyter-notebook, src:jupyter-client, 
and src:ipykernel
>
End of message, stopping processing here.

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

Bug#893542: ntpsec-ntpviz: shares /var/log/ntpstats with ntp, which gets zapped when ntp is purged

[Julian Gilbey]

Package: ntpsec-ntpviz
Version: 1.0.0+dfsg1-5
Severity: serious

I installed the ntpsec suite, then purged the ntp packages.
Unfortunately, this zapped the /var/log/ntpstats directory, which is
needed by ntpsec-ntpviz.  There needs to either been some agreement
between ntp and ntpsec about the use of this directory, or ntpsec
needs to use a different log directory.

Best wishes,

   ulian

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

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

Versions of packages ntpsec-ntpviz depends on:
ii  adduser   3.117
ii  cron [cron-daemon]3.0pl1-130
ii  fonts-liberation  1:1.07.4-5
ii  gnuplot   5.2.2+dfsg1-2
ii  gnuplot-qt [gnuplot]  5.2.2+dfsg1-2
ii  python3   3.6.4-1
ii  python3-ntp   1.0.0+dfsg1-5
ii  systemd   238-2

Versions of packages ntpsec-ntpviz recommends:
ii  apache2 [httpd]  2.4.29-2
ii  ntpsec   1.0.0+dfsg1-5
ii  python3-psutil   5.4.2-1
ii  systemd  238-2

Versions of packages ntpsec-ntpviz suggests:
ii  python  2.7.14-4
pn  python-gps  

-- no debconf information

Bug#893415: marked as done (robocode FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Mon, 19 Mar 2018 19:39:41 +
with message-id 
and subject line Bug#893415: fixed in robocode 1.9.3.1-1
has caused the Debian Bug report #893415,
regarding robocode FTBFS with openjdk-9
to be marked as done.

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

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


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

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

...
[INFO] Reactor Summary:
[INFO] 
[INFO] Robocode ... SUCCESS [  0.035 s]
[INFO] Robocode API ... SUCCESS [01:27 min]
[INFO] Robocode Core .. SUCCESS [ 18.426 s]
[INFO] Robocode Host .. SUCCESS [  7.635 s]
[INFO] Robocode Repository  SUCCESS [  4.169 s]
[INFO] Robocode Battle  SUCCESS [  6.276 s]
[INFO] Robocode Sound . SUCCESS [  2.009 s]
[INFO] Robocode UI  SUCCESS [ 15.828 s]
[INFO] Robocode UI Robot editor ... SUCCESS [  6.744 s]
[INFO] Robocode Samples ... SUCCESS [  2.980 s]
[INFO] Roborumble Client .. SUCCESS [  2.028 s]
[INFO] Robocode Tested Robots . SUCCESS [  7.296 s]
[INFO] Robocode Tests . SUCCESS [  3.717 s]
[INFO] Robocode Installer . SUCCESS [  1.443 s]
[INFO] Robocode Content ... SUCCESS [  1.463 s]
[INFO] Robocode Distribution .. FAILURE [ 11.916 s]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 03:03 min
[INFO] Finished at: 2018-03-18T03:53:08-12:00
[INFO] Final Memory: 31M/104M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-assembly-plugin:3.1.0:single (make-assembly) on 
project robocode.distribution: Failed to create assembly: Error creating 
assembly archive setup: Cannot transform line endings on this kind of file: 
javadoc/member-search-index.zip
[ERROR] Doing so is more or less guaranteed to destroy the file, and it 
indicates a problem with your assembly descriptor.
[ERROR] This error message is new as of 2.5.3. 
[ERROR] Earlier versions of assembly-plugin will silently destroy your file. 
Fix your descriptor
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :robocode.distribution
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/robocode-1.9.2.6 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/robocode-1.9.2.6/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/robocode-1.9.2.6/debian 
-Dmaven.repo.local=/build/1st/robocode-1.9.2.6/debian/maven-repo --batch-mode 
package -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit code 1
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 2
--- End Message ---
--- Begin Message ---
Source: robocode
Source-Version: 1.9.3.1-1

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

Debian distribution maintenance software
pp.
Markus Koschany 

Bug#893472: libfurl-perl: broken on s390x?

[Niko Tyni]

On Mon, Mar 19, 2018 at 01:03:12AM -0700, Steve Langasek wrote:
> Source: libfurl-perl
> Version: 3.13-1
> Severity: grave
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu bionic autopkgtest

> t/100_low/13_deflate.t .. 
> # normal 1 gzip
> Uncompress error: data error at /usr/share/perl5/Furl/HTTP.pm line 845.

> From what I'm able to tell, this test failure points to the library actually
> being broken on s390x, as it fails to decompress data sent back by the
> test server which is implemented using libplack-middleware-deflater-perl.
> But it's also possible that it's libplack-middleware-deflater-perl which is
> broken on s390x, in which case this bug should be certainly reassigned.

Thanks for the report. Testing on zelenka.d.o, I see the same behaviour.

I suspect the real culprit is libplack-middleware-deflater-perl; it uses
pack() in suspicious ways that might break on big vs. little endian.
Its own t/furl.t is failing similarly, but gets skipped on Debian
build+autopkgtest because libfurl-perl is not a build dependency of
libplack-middleware-deflater-perl (possibly due to build cycle reasons.)

I got as far as seeing that removing line 144 in Deflater.pm

 
https://sources.debian.org/src/libplack-middleware-deflater-perl/0.12-1/lib/Plack/Middleware/Deflater.pm/#L144

-   $buf .= pack("LL", $self->{crc},$self->{length}) if $self->{encoding} 
eq 'gzip';

makes both test suites pass, but that doesn't seem like a fully
satisfactory patch. (And no, s/LL/NN/ doesn't fix it.)

There's some probably related upstream discussion in

 https://github.com/miyagawa/Plack-Middleware-Deflater/issues/11

 
https://github.com/miyagawa/Plack-Middleware-Deflater/commit/02db7d339af94c9013a81f17189fccf082cfe3a9

No tuits to actually dig into gzip streams at least tonight...
-- 
Niko Tyni   nt...@debian.org

Bug#893110: marked as done (gupnp-igd: FTBFS (randomly?) testsuite failures - gupnp-simple-igd SIGTRAP)

[Debian Bug Tracking System]

Your message dated Mon, 19 Mar 2018 19:19:25 +
with message-id 
and subject line Bug#893110: fixed in gupnp-igd 0.2.5-2
has caused the Debian Bug report #893110,
regarding gupnp-igd: FTBFS (randomly?) testsuite failures - gupnp-simple-igd 
SIGTRAP
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.)


-- 
893110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gupnp-igd
Version: 0.2.5-1
Severity: serious
Tags: sid buster

Hi,

gupnp-igd FTBFS on some of the buildds with this error:
> make[6]: Entering directory '/<>/tests/gtest'
> ../../test-driver: line 107: 11204 Trace/breakpoint trap   "$@" > $log_file 
> 2>&1
> FAIL: gupnp-simple-igd
> make[6]: Leaving directory '/<>/tests/gtest'
> make[6]: Entering directory '/<>/tests/gtest'
> =
>gupnp-igd 0.2.5: tests/gtest/test-suite.log
> =
> 
> # TOTAL: 1
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: gupnp-simple-igd
> ==
> 
> /simpleigd/new: 
> (/<>/tests/gtest/.libs/gupnp-simple-igd:11204): 
> GUPnP-ContextManager-Linux-WARNING **: Got new address for device 1 but 
> device is not active
> FAIL gupnp-simple-igd (exit status: 133)
> 
> 
> Testsuite summary for gupnp-igd 0.2.5
> 
> # TOTAL: 1
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  1
> # XPASS: 0
> # ERROR: 0
> 
> See tests/gtest/test-suite.log
> Please report to http://www.gupnp.org/
> 

While it built on amd64 on the buildds, the package fails with the same
error when I locally rebuild it. I notice it build fine on all the
Ubuntu builders. I'm afraid I have no idea what is going on here.

James



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: gupnp-igd
Source-Version: 0.2.5-2

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated gupnp-igd 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, 19 Mar 2018 15:00:39 -0400
Source: gupnp-igd
Binary: libgupnp-igd-1.0-4 libgupnp-igd-1.0-dev libgupnp-igd-1.0-doc 
gir1.2-gupnpigd-1.0
Architecture: source
Version: 0.2.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bicha 
Description:
 gir1.2-gupnpigd-1.0 - GObject introspection data for the GUPnP IGD library
 libgupnp-igd-1.0-4 - library to handle UPnP IGD port mapping
 libgupnp-igd-1.0-dev - library to handle UPnP IGD port mapping - development 
files
 libgupnp-igd-1.0-doc - library to handle UPnP IGD port mapping - documentation
Closes: 893110
Changes:
 gupnp-igd (0.2.5-2) unstable; urgency=medium
 .
   * Ignore build test failures again (Closes: #893110)
Checksums-Sha1:
 663460e5364e0221cddf84f8906569e01ca1b740 2420 gupnp-igd_0.2.5-2.dsc
 30da91f6019b000a2f755028f004d50b863a587c 4728 gupnp-igd_0.2.5-2.debian.tar.xz
 eb9375fa7c529c2ab54fe99b211799cfbd1e348c 10866 
gupnp-igd_0.2.5-2_source.buildinfo
Checksums-Sha256:
 e0e160b63f81621dadc24049b21c4bb8600a0e86cae5fc97fff54f7e156a6bd3 2420 
gupnp-igd_0.2.5-2.dsc
 e1ccf8109680b523761be2aa23d861a66afe9d5cb66e258816ee1885b0ce26ce 4728 
gupnp-igd_0.2.5-2.debian.tar.xz
 6ff89e8c02202bcc84d160c50f50e0a8d0cff87593f1485954a53fe2abb715f6 10866 
gupnp-igd_0.2.5-2_source.buildinfo
Files:
 091cfc7db19da160e0b3b4bbbd3a37f0 2420 libs optional gupnp-igd_0.2.5-2.dsc
 2d633cc6f8a07b107c1fdbfb3d265eed 4728 libs optional 

Bug#893538: kbibtex FTBFS: delegate-failed rsvg-convert

[Helmut Grohne]

Source: kbibtex
Version: 0.8~20170819git31a77b27e8e83836e-3
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

I was trying to cross build kbibtex and wondered why it failed, but to
my amazement, the failure simply is a native FTBFS. Hope this helps in
diagnosing:

| # rebuild icons
| rm -rf debian/tmp/usr/share/icons
| # build icons cache (build for each arch in order to get more testing)
| set -e; for SIZE in 8x8 16x16 22x22 24x24 32x32 36x36 42x42 48x48 64x64 72x72 
96x96 128x128 192x192 256x256; do \
| mkdir -p debian/tmp/usr/share/icons/hicolor/$SIZE/apps/ ;\
| echo "Make icons for size $SIZE..."; \
| convert icons/kbibtex.svg \
|-background none -define filter:blur=0.75 -filter Gaussian 
-resize $SIZE \
|-gravity center -extent $SIZE  \
|+set date:create +set date:modify -define 
png:exclude-chunk=time  \
|debian/tmp/usr/share/icons/hicolor/$SIZE/apps/kbibtex.png; 
\
| echo "Done"; \
| done
| Make icons for size 8x8...
| convert-im6.q16: delegate failed `'rsvg-convert' -o '%o' '%i'' @ 
error/delegate.c/InvokeDelegate/1919.
| convert-im6.q16: unable to open file `/tmp/magick-29767lUAn6InfQnK3': No such 
file or directory @ error/constitute.c/ReadImage/544.
| convert-im6.q16: no images defined 
`debian/tmp/usr/share/icons/hicolor/8x8/apps/kbibtex.png' @ 
error/convert.c/ConvertImageCommand/3258.
| make[1]: *** [debian/rules:42: override_dh_auto_install] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:26: binary-arch] Error 2
| dpkg-buildpackage: error: fakeroot debian/rules binary-arch subprocess 
returned exit status 2

Helmut

Processed: your mail

[Debian Bug Tracking System]

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

> owner 893244 !
Bug #893244 [src:jruby] jruby FTBFS with openjdk-9
Owner recorded as Miguel Landaeta .
> tags 893244 + confirmed
Bug #893244 [src:jruby] jruby FTBFS with openjdk-9
Added tag(s) confirmed.
> thanks
Stopping processing here.

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

> severity 850921 serious
Bug #850921 [openjfx] openjfx version for openjdk 9.0
Severity set to 'serious' from 'wishlist'
> tags 850921 buster sid
Bug #850921 [openjfx] openjfx version for openjdk 9.0
Added tag(s) sid and buster.
> affects 850921 src:afterburner.fx src:controlsfx src:easybind 
> src:fontawesomefx src:javafxsvg src:josm src:mediathekview src:pdfsam 
> src:triplea
Bug #850921 [openjfx] openjfx version for openjdk 9.0
Added indication that 850921 affects src:afterburner.fx, src:controlsfx, 
src:easybind, src:fontawesomefx, src:javafxsvg, src:josm, src:mediathekview, 
src:pdfsam, and src:triplea
> reassign 893348 openjfx
Bug #893348 [src:openjfx] openjfx not available for openjdk-9
Bug reassigned from package 'src:openjfx' to 'openjfx'.
Ignoring request to alter found versions of bug #893348 to the same values 
previously set
Ignoring request to alter fixed versions of bug #893348 to the same values 
previously set
> reassign 893190 openjfx
Bug #893190 [src:afterburner.fx] afterburner.fx FTBFS with openjdk-9
Bug reassigned from package 'src:afterburner.fx' to 'openjfx'.
No longer marked as found in versions afterburner.fx/1.7.0-1.
Ignoring request to alter fixed versions of bug #893190 to the same values 
previously set
> reassign 893194 openjfx
Bug #893194 [src:fontawesomefx] fontawesomefx FTBFS with openjdk-9
Bug reassigned from package 'src:fontawesomefx' to 'openjfx'.
No longer marked as found in versions fontawesomefx/8.9-1.
Ignoring request to alter fixed versions of bug #893194 to the same values 
previously set
> reassign 893345 openjfx
Bug #893345 [src:javafxsvg] javafxsvg FTBFS with openjdk-9
Bug reassigned from package 'src:javafxsvg' to 'openjfx'.
No longer marked as found in versions javafxsvg/1.2.1-1.
Ignoring request to alter fixed versions of bug #893345 to the same values 
previously set
> reassign 893348 openjfx
Bug #893348 [openjfx] openjfx not available for openjdk-9
Ignoring request to reassign bug #893348 to the same package
> forcemerge 850921 893348 893190 893194 893345 893348
Bug #850921 [openjfx] openjfx version for openjdk 9.0
Bug #893194 [openjfx] fontawesomefx FTBFS with openjdk-9
Added indication that 893194 affects 
src:javafxsvg,src:fontawesomefx,src:pdfsam,src:easybind,src:afterburner.fx,src:josm,src:mediathekview,src:controlsfx,src:triplea
Marked as found in versions openjfx/8u111-b14-1.
Added tag(s) confirmed, sid, and buster.
Bug #893190 [openjfx] afterburner.fx FTBFS with openjdk-9
Added indication that 893190 affects 
src:javafxsvg,src:fontawesomefx,src:pdfsam,src:easybind,src:afterburner.fx,src:josm,src:mediathekview,src:controlsfx,src:triplea
Marked as found in versions openjfx/8u111-b14-1.
Added tag(s) sid and buster.
Bug #893348 [openjfx] openjfx not available for openjdk-9
Removed indication that 893348 affects src:josm
Added indication that 893348 affects 
src:javafxsvg,src:fontawesomefx,src:pdfsam,src:easybind,src:afterburner.fx,src:josm,src:mediathekview,src:controlsfx,src:triplea
Marked as found in versions openjfx/8u111-b14-1.
Added tag(s) sid, buster, and confirmed.
Bug #850921 [openjfx] openjfx version for openjdk 9.0
Added tag(s) confirmed.
Bug #893345 [openjfx] javafxsvg FTBFS with openjdk-9
Added indication that 893345 affects 
src:javafxsvg,src:fontawesomefx,src:pdfsam,src:easybind,src:afterburner.fx,src:josm,src:mediathekview,src:controlsfx,src:triplea
Marked as found in versions openjfx/8u111-b14-1.
Added tag(s) confirmed, buster, and sid.
Merged 850921 893190 893194 893345 893348
> thanks
Stopping processing here.

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

Processed: affects 873227

[Debian Bug Tracking System]

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

> affects 873227 src:triplea
Bug #873227 [src:gradle] Please upgrade to 4.1: Java 9 support
Ignoring request to set affects of bug 873227 to the same value previously set
> thanks
Stopping processing here.

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

Bug#893520: Processed: Re: ImportError: No module named backports.ssl_match_hostname

[Matthias Klose]

reassign 893520 python-backports.ssl-match-hostname
thanks

I don't think this module is needed anymore.

On 20.03.2018 00:57, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> 
>> reassign 893520 python-minimal 2.7.14-4
> Bug #893520 [python-docker] ImportError: No module named 
> backports.ssl_match_hostname
> Bug reassigned from package 'python-docker' to 'python-minimal'.
> No longer marked as found in versions python-docker/2.5.1-1.
> Ignoring request to alter fixed versions of bug #893520 to the same values 
> previously set
> Bug #893520 [python-minimal] ImportError: No module named 
> backports.ssl_match_hostname
> Marked as found in versions python-defaults/2.7.14-4.
>> thanks
> Stopping processing here.
> 
> Please contact me if you need assistance.
> 

Processed: affects 892733

[Debian Bug Tracking System]

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

> affects 892733 src:stockpile-clojure 
> src:trapperkeeper-webserver-jetty9-clojure
Bug #892733 [gettext] gettext: msgfmt doesn't work with Java 9
Added indication that 892733 affects src:stockpile-clojure and 
src:trapperkeeper-webserver-jetty9-clojure
> thanks
Stopping processing here.

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

Bug#893525: CVE-2018-1000097

[Moritz Muehlenhoff]

On Mon, Mar 19, 2018 at 06:20:44PM +0100, Santiago Vila wrote:
> On Mon, Mar 19, 2018 at 05:58:04PM +0100, Moritz Muehlenhoff wrote:
> > Source: sharutils
> > Severity: grave
> > Tags: security
> > 
> > This has been assigned CVE-2018-197:
> > http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg4.html
> > 
> > Proposed patch at:
> > http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg5.html
> 
> Thanks for the report. Simple question: Is this the same problem as this one?
> 
> http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg3.html
> 
> or there will be another different CVE for that?
> 
> (I will apply the proposed patch anyway, since it's a one-liner).

I'm not sure yet, 
http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg3.html
might be a different issue, the CVE assignment is apparently only for
"msg4.html".

Cheers,
Moritz

Bug#893536: wildfly-common FTBFS with openjdk-9

[Adrian Bunk]

Source: wildfly-common
Version: 1.3.0-1
Severity: serious

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

...
[ERROR] Tests run: 9, Failures: 4, Errors: 0, Skipped: 0, Time elapsed: 0.609 s 
<<< FAILURE! - in org.wildfly.common.rpc.TestRemoteExceptionCause
[ERROR] serial0(org.wildfly.common.rpc.TestRemoteExceptionCause)  Time elapsed: 
0.197 s  <<< FAILURE!
arrays first differed at element [0]; expected: 
java.lang.StackTraceElement
 but was: 
java.lang.StackTraceElement
at 
org.junit.internal.ComparisonCriteria.arrayEquals(ComparisonCriteria.java:55)
at org.junit.Assert.internalArrayEquals(Assert.java:532)
at org.junit.Assert.assertArrayEquals(Assert.java:283)
at org.junit.Assert.assertArrayEquals(Assert.java:298)
at 
org.wildfly.common.rpc.TestRemoteExceptionCause.lambda$serial0$1(TestRemoteExceptionCause.java:119)
at 
org.wildfly.common.rpc.TestRemoteExceptionCause.doSerialTest(TestRemoteExceptionCause.java:112)
at 
org.wildfly.common.rpc.TestRemoteExceptionCause.serial0(TestRemoteExceptionCause.java:117)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:564)
at 
org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
at 
org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at 
org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:52)
at 
org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
at 
org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:369)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:275)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:239)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:160)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:373)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:334)
at 
org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:119)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:407)
Caused by: java.lang.AssertionError: expected: 
java.lang.StackTraceElement
 but was: 
java.lang.StackTraceElement
at org.junit.Assert.fail(Assert.java:88)
at org.junit.Assert.failNotEquals(Assert.java:834)
at org.junit.Assert.assertEquals(Assert.java:118)
at org.junit.Assert.assertEquals(Assert.java:144)
at 
org.junit.internal.ExactComparisonCriteria.assertElementsEqual(ExactComparisonCriteria.java:8)
at 
org.junit.internal.ComparisonCriteria.arrayEquals(ComparisonCriteria.java:53)
... 31 more

[ERROR] serial1(org.wildfly.common.rpc.TestRemoteExceptionCause)  Time elapsed: 
0.105 s  <<< FAILURE!
arrays first differed at element [0]; expected: 
java.lang.StackTraceElement
 but was: 
java.lang.StackTraceElement
at 
org.junit.internal.ComparisonCriteria.arrayEquals(ComparisonCriteria.java:55)
at org.junit.Assert.internalArrayEquals(Assert.java:532)
at org.junit.Assert.assertArrayEquals(Assert.java:283)
at 

Processed: found 887856 in 3.20170707.1~deb9u1

[Debian Bug Tracking System]

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

> # Declare as found in the current version in stretch as the BTS currently 
> does not seem to consider stretch as affected
> found 887856 3.20170707.1~deb9u1
Bug #887856 [intel-microcode] intel-microcode: spectre microcode updates for 
stable
Marked as found in versions intel-microcode/3.20170707.1~deb9u1.
> thanks
Stopping processing here.

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

Bug#893533: qdox2 FTBFS with openjdk-9

[Adrian Bunk]

Source: qdox2
Version: 2.0~M7-1
Severity: serious

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

...
[ERROR] Tests run: 8, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.868 s 
<<< FAILURE! - in com.thoughtworks.qdox.EnumsModelTest
[ERROR] 
testAddEnumWithFieldAndConstructorsToModelBinary(com.thoughtworks.qdox.EnumsModelTest)
  Time elapsed: 0.913 s  <<< FAILURE!
junit.framework.AssertionFailedError
at 
com.thoughtworks.qdox.EnumsModelTest.testAddEnumWithFieldAndConstructorsToModelBinary(EnumsModelTest.java:181)

Bug#893532: undertow FTBFS with openjdk-9

[Adrian Bunk]

Source: undertow
Version: 1.4.23-1
Severity: serious

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

...
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-javadoc-plugin:3.0.0:jar (default-cli) on 
project undertow-core: MavenReportException: Error while generating Javadoc: 
[ERROR] Exit code: 1 - 
/build/1st/undertow-1.4.23/core/target/generated-sources/annotations/io/undertow/websockets/core/WebSocketMessages_$bundle.java:6:
 error: package javax.annotation is not visible
[ERROR] import javax.annotation.Generated;
[ERROR] ^
[ERROR]   (package javax.annotation is declared in module 
java.xml.ws.annotation, which is not in the module graph)
[ERROR] 
/build/1st/undertow-1.4.23/core/target/generated-sources/annotations/io/undertow/websockets/core/WebSocketLogger_$logger.java:5:
 error: package javax.annotation is not visible
[ERROR] import javax.annotation.Generated;
[ERROR] ^
[ERROR]   (package javax.annotation is declared in module 
java.xml.ws.annotation, which is not in the module graph)
[ERROR] 
/build/1st/undertow-1.4.23/core/target/generated-sources/annotations/io/undertow/client/UndertowClientMessages_$bundle.java:6:
 error: package javax.annotation is not visible
[ERROR] import javax.annotation.Generated;
[ERROR] ^
[ERROR]   (package javax.annotation is declared in module 
java.xml.ws.annotation, which is not in the module graph)
[ERROR] 
/build/1st/undertow-1.4.23/core/target/generated-sources/annotations/io/undertow/UndertowMessages_$bundle.java:7:
 error: package javax.annotation is not visible
[ERROR] import javax.annotation.Generated;
[ERROR] ^
[ERROR]   (package javax.annotation is declared in module 
java.xml.ws.annotation, which is not in the module graph)
[ERROR] 
/build/1st/undertow-1.4.23/core/target/generated-sources/annotations/io/undertow/UndertowLogger_$logger.java:21:
 error: package javax.annotation is not visible
[ERROR] import javax.annotation.Generated;
[ERROR] ^
[ERROR]   (package javax.annotation is declared in module 
java.xml.ws.annotation, which is not in the module graph)
[ERROR] 
[ERROR] Command line was: /usr/lib/jvm/java-9-openjdk-amd64/bin/javadoc 
@options @packages
[ERROR] 
[ERROR] Refer to the generated Javadoc files in 
'/build/1st/undertow-1.4.23/core/target/apidocs' dir.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :undertow-core
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/undertow-1.4.23 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/undertow-1.4.23/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/build/1st/undertow-1.4.23/debian 
-Dmaven.repo.local=/build/1st/undertow-1.4.23/debian/maven-repo --batch-mode 
package javadoc:jar javadoc:aggregate -DskipTests -Dnotimestamp=true 
-Dlocale=en_US returned exit code 1
make: *** [debian/rules:4: build] Error 1

Processed: fixed 887856 in 3.20180312.1~bpo9+1

[Debian Bug Tracking System]

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

> # Don't let apt-listbugs report 3.20180312.1~bpo9+1 as having the RC bug 
> »spectre microcode updates for stable«.
> fixed 887856 3.20180312.1~bpo9+1
Bug #887856 [intel-microcode] intel-microcode: spectre microcode updates for 
stable
Marked as fixed in versions intel-microcode/3.20180312.1~bpo9+1.
> thanks
Stopping processing here.

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

Bug#893370: marked as done (libgpg-error FTBFS on arm*: error: incompatible type for argument 4 of '_gpgrt_logv_printhex')

[Debian Bug Tracking System]

Your message dated Mon, 19 Mar 2018 17:51:16 +
with message-id 
and subject line Bug#893370: fixed in libgpg-error 1.28-2
has caused the Debian Bug report #893370,
regarding libgpg-error FTBFS on arm*: error: incompatible type for argument 4 
of '_gpgrt_logv_printhex'
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.)


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

https://buildd.debian.org/status/package.php?p=libgpg-error=sid

...
../../src/logging.c: In function '_gpgrt_log_printhex':
../../src/logging.c:1153:49: error: incompatible type for argument 4 of 
'_gpgrt_logv_printhex'
 _gpgrt_logv_printhex (buffer, length, NULL, NULL);
 ^~~~
../../src/logging.c:1097:1: note: expected 'va_list {aka __va_list}' but 
argument is of type 'void *'
 _gpgrt_logv_printhex (const void *buffer, size_t length,
 ^~~~
Makefile:1041: recipe for target 'libgpg_error_la-logging.lo' failed
make[5]: *** [libgpg_error_la-logging.lo] Error 1
--- End Message ---
--- Begin Message ---
Source: libgpg-error
Source-Version: 1.28-2

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 19 Mar 2018 17:20:31 +
Source: libgpg-error
Binary: libgpg-error-dev libgpg-error0 libgpg-error0-udeb 
libgpg-error-mingw-w64-dev
Architecture: source
Version: 1.28-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GnuPG Maintainers 
Changed-By: Daniel Kahn Gillmor 
Description:
 libgpg-error-dev - library for common error values and messages in GnuPG 
components
 libgpg-error-mingw-w64-dev - library of error values and messages in GnuPG 
(Windows developmen
 libgpg-error0 - library for common error values and messages in GnuPG 
components
 libgpg-error0-udeb - library for common error values and messages in GnuPG 
components (udeb)
Closes: 893370
Changes:
 libgpg-error (1.28-2) unstable; urgency=medium
 .
   * avoid FTBFS on arm* (Closes: #893370)
Checksums-Sha1:
 763db276b44ca6bce53cfd5378d9ce135339b43f 1997 libgpg-error_1.28-2.dsc
 2717dbfcd05717514f7a5ca2ae094480ee283629 17028 
libgpg-error_1.28-2.debian.tar.xz
 e3d0f65e8ad13eba609add998dcfa919c2778754 7290 
libgpg-error_1.28-2_amd64.buildinfo
Checksums-Sha256:
 85d54f70fb3d590f4c9a1e4e5ccfaa6f8469d2fa676f87600d1ea22a7366b920 1997 
libgpg-error_1.28-2.dsc
 a943dc5ac05a32ab29cb3e1fe9ebe2780caae98acd9e201222f4a3a56c381e23 17028 
libgpg-error_1.28-2.debian.tar.xz
 38965db09edbe9ebcf162d66b080752a96aab465ffb7422237a5f011b72f4126 7290 
libgpg-error_1.28-2_amd64.buildinfo
Files:
 05ade1cdc91cc62d372f555be340280a 1997 libs optional libgpg-error_1.28-2.dsc
 4c259e4b9fba27f65ed5e407da5525bd 17028 libs optional 
libgpg-error_1.28-2.debian.tar.xz
 bac35b5212445f704533146178f44274 7290 libs optional 
libgpg-error_1.28-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQTTaP514aqS9uSbmdJsHx7ezFD6UwUCWq/1mgAKCRBsHx7ezFD6
U/MbAP9cMGxZnBNPI+xSHVpeKotdYygeX1sxTV46Ug5t0uvjjQEA9VCjSwywC3Tr
tAiNobGPhcY8IDOkXnOWgF86xj/TrwU=
=z+Tt
-END PGP SIGNATURE End Message ---

Bug#893531: starjava-topcat FTBFS with openjdk-9

[Adrian Bunk]

Source: starjava-topcat
Version: 4.5.1-1
Severity: serious

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

...
build-extras:
  [javadoc] Generating Javadoc
  [javadoc] Debian build on Java >=9: Adding --ignore-source-errors.
  [javadoc] Javadoc execution
  [javadoc] javadoc: warning - The old Doclet and Taglet APIs in the packages
  [javadoc] com.sun.javadoc, com.sun.tools.doclets and their implementations
  [javadoc] are planned to be removed in a future JDK release. These
  [javadoc] components have been superseded by the new APIs in 
jdk.javadoc.doclet.
  [javadoc] Users are strongly recommended to migrate to the new APIs.
  [javadoc] Usage: javadoc [options] [packagenames] [sourcefiles] [@files]
  [javadoc]   -overview  Read overview documentation from 
HTML file
  [javadoc]   -public  Show only public classes and 
members
  [javadoc]   -protected   Show protected/public classes 
and members (default)
  [javadoc]   -package Show package/protected/public 
classes and members
  [javadoc]   -private Show all classes and members
  [javadoc]   -helpDisplay command line options and 
exit
  [javadoc]   -doclet   Generate output via alternate 
doclet
  [javadoc]   -docletpathSpecify where to find doclet 
class files
  [javadoc]   --module-source-path   Specify where to find input 
source files for multiple modules
  [javadoc]   --upgrade-module-path  Override location of upgradeable 
modules
  [javadoc]   --module-path , -p   Specify where to find 
application modules
  [javadoc]   --add-modules (,)*
  [javadoc]Root modules to resolve in 
addition to the initial modules,
  [javadoc]or all modules on the module 
path if  is ALL-MODULE-PATH.
  [javadoc]   --limit-modules (,)*
  [javadoc]Limit the universe of observable 
modules
  [javadoc]   --source-path  Specify where to find source 
files
  [javadoc]   -sourcepathSpecify where to find source 
files
  [javadoc]   --class-path   Specify where to find user class 
files
  [javadoc]   -classpath Specify where to find user class 
files
  [javadoc]   -cpSpecify where to find user class 
files
  [javadoc]   -excludeSpecify a list of packages to 
exclude
  [javadoc]   -subpackages Specify subpackages to 
recursively load
  [javadoc]   -breakiterator   Compute first sentence with 
BreakIterator
  [javadoc]   -bootclasspath Override location of platform 
class files
  [javadoc]used for non-modular releases
  [javadoc]   --systemOverride location of system 
modules used
  [javadoc]for modular releases.
  [javadoc]   -source Provide source compatibility 
with specified release
  [javadoc]   --release   Provide source compatibility 
with specified release
  [javadoc]   -extdirsOverride location of installed 
extensions
  [javadoc]   -verbose Output messages about what 
Javadoc is doing
  [javadoc]   -localeLocale to be used, e.g. en_US or 
en_US_WIN
  [javadoc]   -encoding  Source file encoding name
  [javadoc]   -quiet   Do not display status messages
  [javadoc]   -J Pass  directly to the 
runtime system
  [javadoc]   -X   Print a synopsis of nonstandard 
options and exit
  [javadoc] 
  [javadoc] 
  [javadoc] GNU-style options may use = instead whitespace to separate the name 
of an option
  [javadoc] from its value.
  [javadoc] 
  [javadoc] 1 error
  [javadoc] javadoc: error - invalid flag: --ignore-source-errors

BUILD FAILED
/build/1st/starjava-topcat-4.5.1/build.xml:503: The following error occurred 
while executing this line:
/build/1st/starjava-topcat-4.5.1/build.xml:520: Javadoc returned 1

Total time: 30 seconds
make[1]: *** [debian/rules:7: override_dh_auto_build] Error 1

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

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:kubernetes
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #892801 (http://bugs.debian.org/892801)
> # Bug title: kubernetes: CVE-2017-1002101: Volume security can be sidestepped 
> with innocent emptyDir and subpath
> #  * https://github.com/kubernetes/kubernetes/issues/60813
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 892801 + fixed-upstream
Bug #892801 [src:kubernetes] kubernetes: CVE-2017-1002101: Volume security can 
be sidestepped with innocent emptyDir and subpath
Added tag(s) fixed-upstream.
> usertags 892801 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:paramiko
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #892859 (http://bugs.debian.org/892859)
> # Bug title: paramiko: CVE-2018-7750: Server implementation does not check 
> for auth before serving later requests
> #  * https://github.com/paramiko/paramiko/issues/1175
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 892859 + fixed-upstream
Bug #892859 [src:paramiko] paramiko: CVE-2018-7750: Server implementation does 
not check for auth before serving later requests
Added tag(s) fixed-upstream.
> usertags 892859 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#893530: starjava-ttools FTBFS with openjdk-9

[Adrian Bunk]

Source: starjava-ttools
Version: 3.1.2-1
Severity: serious

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

...

build-extras:
[mkdir] Created dir: /build/1st/starjava-ttools-3.1.2/build/javadocs
  [javadoc] Generating Javadoc
  [javadoc] Debian build on Java >=9: Adding --ignore-source-errors.
  [javadoc] Javadoc execution
  [javadoc] javadoc: warning - The old Doclet and Taglet APIs in the packages
  [javadoc] com.sun.javadoc, com.sun.tools.doclets and their implementations
  [javadoc] are planned to be removed in a future JDK release. These
  [javadoc] components have been superseded by the new APIs in 
jdk.javadoc.doclet.
  [javadoc] Users are strongly recommended to migrate to the new APIs.
  [javadoc] javadoc: error - invalid flag: --ignore-source-errors
  [javadoc] Usage: javadoc [options] [packagenames] [sourcefiles] [@files]
  [javadoc]   -overview  Read overview documentation from 
HTML file
  [javadoc]   -public  Show only public classes and 
members
  [javadoc]   -protected   Show protected/public classes 
and members (default)
  [javadoc]   -package Show package/protected/public 
classes and members
  [javadoc]   -private Show all classes and members
  [javadoc]   -helpDisplay command line options and 
exit
  [javadoc]   -doclet   Generate output via alternate 
doclet
  [javadoc]   -docletpathSpecify where to find doclet 
class files
  [javadoc]   --module-source-path   Specify where to find input 
source files for multiple modules
  [javadoc]   --upgrade-module-path  Override location of upgradeable 
modules
  [javadoc]   --module-path , -p   Specify where to find 
application modules
  [javadoc]   --add-modules (,)*
  [javadoc]Root modules to resolve in 
addition to the initial modules,
  [javadoc]or all modules on the module 
path if  is ALL-MODULE-PATH.
  [javadoc]   --limit-modules (,)*
  [javadoc]Limit the universe of observable 
modules
  [javadoc]   --source-path  Specify where to find source 
files
  [javadoc]   -sourcepathSpecify where to find source 
files
  [javadoc]   --class-path   Specify where to find user class 
files
  [javadoc]   -classpath Specify where to find user class 
files
  [javadoc]   -cpSpecify where to find user class 
files
  [javadoc]   -excludeSpecify a list of packages to 
exclude
  [javadoc]   -subpackages Specify subpackages to 
recursively load
  [javadoc]   -breakiterator   Compute first sentence with 
BreakIterator
  [javadoc]   -bootclasspath Override location of platform 
class files
  [javadoc]used for non-modular releases
  [javadoc]   --systemOverride location of system 
modules used
  [javadoc]for modular releases.
  [javadoc]   -source Provide source compatibility 
with specified release
  [javadoc]   --release   Provide source compatibility 
with specified release
  [javadoc]   -extdirsOverride location of installed 
extensions
  [javadoc]   -verbose Output messages about what 
Javadoc is doing
  [javadoc]   -localeLocale to be used, e.g. en_US or 
en_US_WIN
  [javadoc]   -encoding  Source file encoding name
  [javadoc]   -quiet   Do not display status messages
  [javadoc]   -J Pass  directly to the 
runtime system
  [javadoc]   -X   Print a synopsis of nonstandard 
options and exit
  [javadoc] 
  [javadoc] 
  [javadoc] GNU-style options may use = instead whitespace to separate the name 
of an option
  [javadoc] from its value.
  [javadoc] 
  [javadoc] 1 error

BUILD FAILED
/build/1st/starjava-ttools-3.1.2/build.xml:511: The following error occurred 
while executing this line:
/build/1st/starjava-ttools-3.1.2/build.xml:530: Javadoc returned 1

Total time: 41 seconds
make[1]: *** [debian/rules:7: override_dh_auto_build] Error 1

Bug#893529: starjava-util FTBFS with openjdk-9

[Adrian Bunk]

Source: starjava-util
Version: 1.0+2017.09.28-1
Severity: serious

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

...
run-tests:
[junit] Testsuite: uk.ac.starlink.util.CgiQueryTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.082 sec
[junit] 
[junit] Testcase: testPartial took 0.015 sec
[junit] Testcase: testFormat took 0.012 sec
[junit] Testcase: testBroken took 0.038 sec
[junit] Testcase: testQuery took 0.012 sec
[junit] Testsuite: uk.ac.starlink.util.CountMapTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.009 sec
[junit] 
[junit] Testcase: testCountMap took 0.005 sec
[junit] Testsuite: uk.ac.starlink.util.DOMUtilsTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.163 sec
[junit] 
[junit] Testcase: testGetChildElementByName took 0.042 sec
[junit] Testcase: testGetTextContent took 0.004 sec
[junit] Testcase: testNewDocument took 0.01 sec
[junit] Testcase: testRelativizeDOM took 0.102 sec
[junit] Testsuite: uk.ac.starlink.util.DataSourceTest
[junit] Tests run: 6, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 
0.735 sec
[junit] 
[junit] Testcase: testData took 0.099 sec
[junit] Testcase: testIntro took 0.083 sec
[junit] Testcase: testStream took 0.158 sec
[junit] Testcase: testHybridStream took 0.202 sec
[junit] Testcase: testCombo1 took 0.126 sec
[junit] Testcase: testResourceStream took 0.056 sec
[junit] FAILED
[junit] null
[junit] junit.framework.AssertionFailedError
[junit] at junit.framework.Assert.fail(Assert.java:47)
[junit] at junit.framework.Assert.assertTrue(Assert.java:20)
[junit] at junit.framework.Assert.assertTrue(Assert.java:27)
[junit] at 
uk.ac.starlink.util.DataSourceTest.testResourceStream(DataSourceTest.java:118)
[junit] at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[junit] at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
[junit] at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[junit] at java.base/java.lang.reflect.Method.invoke(Method.java:564)
[junit] at junit.framework.TestCase.runTest(TestCase.java:164)
[junit] at junit.framework.TestCase.runBare(TestCase.java:130)
[junit] at junit.framework.TestResult$1.protect(TestResult.java:106)
[junit] at junit.framework.TestResult.runProtected(TestResult.java:124)
[junit] at junit.framework.TestResult.run(TestResult.java:109)
[junit] at junit.framework.TestCase.run(TestCase.java:120)
[junit] at junit.framework.TestSuite.runTest(TestSuite.java:230)
[junit] at junit.framework.TestSuite.run(TestSuite.java:225)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:538)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1187)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:1039)
[junit] 

BUILD FAILED
/build/1st/starjava-util-1.0+2017.09.28/build.xml:925: Test 
uk.ac.starlink.util.DataSourceTest failed

Total time: 6 seconds
make[1]: *** [debian/rules:11: override_dh_auto_test] Error 1

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

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package src:cinnamon
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #856699 (http://bugs.debian.org/856699)
> # Bug title: cinnamon: recommends gksu which is deprecated
> #  * https://github.com/linuxmint/Cinnamon/issues/6674
> #  * remote status changed: open -> closed
> #  * closed upstream
> tags 856699 + fixed-upstream
Bug #856699 [src:cinnamon] cinnamon: recommends gksu which is deprecated
Added tag(s) fixed-upstream.
> usertags 856699 - status-open
Usertags were: status-open.
Usertags are now: .
> usertags 856699 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Processed: [bts-link] source package ruby-omniauth-saml

[Debian Bug Tracking System]

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

> #
> # bts-link upstream status pull for source package ruby-omniauth-saml
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #892864 (http://bugs.debian.org/892864)
> # Bug title: CVE-2017-11430
> #  * https://github.com/omniauth/omniauth-saml/pull/157
> #  * remote status changed: (?) -> closed
> #  * closed upstream
> tags 892864 + fixed-upstream
Bug #892864 [ruby-omniauth-saml] CVE-2017-11430
Added tag(s) fixed-upstream.
> usertags 892864 + status-closed
There were no usertags set.
Usertags are now: status-closed.
> thanks
Stopping processing here.

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

Bug#893525: CVE-2018-1000097

[Santiago Vila]

On Mon, Mar 19, 2018 at 05:58:04PM +0100, Moritz Muehlenhoff wrote:
> Source: sharutils
> Severity: grave
> Tags: security
> 
> This has been assigned CVE-2018-197:
> http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg4.html
> 
> Proposed patch at:
> http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg5.html

Thanks for the report. Simple question: Is this the same problem as this one?

http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg3.html

or there will be another different CVE for that?

(I will apply the proposed patch anyway, since it's a one-liner).

Thanks.

Processed: tagging 893525

[Debian Bug Tracking System]

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

> tags 893525 + upstream
Bug #893525 [src:sharutils] CVE-2018-197
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: found 893525 in 1:4.14-2

[Debian Bug Tracking System]

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

> found 893525 1:4.14-2
Bug #893525 [src:sharutils] CVE-2018-197
Marked as found in versions sharutils/1:4.14-2.
> thanks
Stopping processing here.

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

Processed: found 893525 in 1:4.15.2-2

[Debian Bug Tracking System]

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

> found 893525 1:4.15.2-2
Bug #893525 [src:sharutils] CVE-2018-197
Marked as found in versions sharutils/1:4.15.2-2.
> thanks
Stopping processing here.

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

Bug#893526: mrs: FTBFS on 32-bit arches - error: format not a string literal and no format arguments

[James Cowgill]

Source: mrs
Version: 6.0.5+dfsg-4
Severity: serious
Tags: sid buster

mrs FTBFS with this error on 32-bit architectures:
>>> src/M6Parser.cpp
> src/M6Parser.cpp: In static member function 'static M6ParserImpl* 
> M6ParserImpl::GetObject(SV*)':
> src/M6Parser.cpp:417:73: warning: null argument where non-null required 
> (argument 2) [-Wnonnull]
>if (tmp != 0 and strcmp(kM6ScriptType, HvNAME(SvSTASH(SvRV(inScalar == 
> 0)
>  ^
> src/M6Parser.cpp: In function 'void 
> _M6_Script_set_attribute(PerlInterpreter*, CV*)':
> src/M6Parser.cpp:694:17: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>croak(e.what());
>  ^
> src/M6Parser.cpp: In function 'void _M6_Script_set_document(PerlInterpreter*, 
> CV*)':
> src/M6Parser.cpp:724:17: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>croak(e.what());
>  ^
> src/M6Parser.cpp: In function 'void _M6_Script_index_text(PerlInterpreter*, 
> CV*)':
> src/M6Parser.cpp:762:18: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> croak(e.what());
>   ^
> src/M6Parser.cpp: In function 'void _M6_Script_index_string(PerlInterpreter*, 
> CV*)':
> src/M6Parser.cpp:802:18: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> croak(e.what());
>   ^
> src/M6Parser.cpp: In function 'void 
> _M6_Script_index_unique_string(PerlInterpreter*, CV*)':
> src/M6Parser.cpp:840:18: error: format not a string literal and no format 
> arguments [-Werror=format-security]
> croak(e.what());
>   ^
> src/M6Parser.cpp: In function 'void _M6_Script_index_number(PerlInterpreter*, 
> CV*)':
> src/M6Parser.cpp:880:17: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>croak(e.what());
>  ^
> src/M6Parser.cpp: In function 'void _M6_Script_index_date(PerlInterpreter*, 
> CV*)':
> src/M6Parser.cpp:918:17: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>croak(e.what());
>  ^
> src/M6Parser.cpp: In function 'void _M6_Script_add_link(PerlInterpreter*, 
> CV*)':
> src/M6Parser.cpp:958:17: error: format not a string literal and no format 
> arguments [-Werror=format-security]
>croak(e.what());
>  ^
> cc1plus: some warnings being treated as errors
> GNUmakefile:104: recipe for target 'obj/M6Parser.o' failed

I think the reason this only fails on 32-bit architectures is a quirk in
the perl Configure script which I'm looking at. I don't think it's
related to mrs (ie it _should_ have failed everywhere).

James



signature.asc
Description: OpenPGP digital signature

Bug#893525: CVE-2018-1000097

[Moritz Muehlenhoff]

Source: sharutils
Severity: grave
Tags: security

This has been assigned CVE-2018-197:
http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg4.html

Proposed patch at:
http://lists.gnu.org/archive/html/bug-gnu-utils/2018-02/msg5.html

Cheers,
Moritz

Processed: Re: ImportError: No module named backports.ssl_match_hostname

[Debian Bug Tracking System]

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

> reassign 893520 python-minimal 2.7.14-4
Bug #893520 [python-docker] ImportError: No module named 
backports.ssl_match_hostname
Bug reassigned from package 'python-docker' to 'python-minimal'.
No longer marked as found in versions python-docker/2.5.1-1.
Ignoring request to alter fixed versions of bug #893520 to the same values 
previously set
Bug #893520 [python-minimal] ImportError: No module named 
backports.ssl_match_hostname
Marked as found in versions python-defaults/2.7.14-4.
> thanks
Stopping processing here.

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

Bug#893520: ImportError: No module named backports.ssl_match_hostname

[Laurent Bigonville]

reassign 893520 python-minimal 2.7.14-4
thanks

On Mon, 19 Mar 2018 17:35:28 +0100 Laurent Bigonville  
wrote:


> Hi,
>
> Seems that python-docker completely fails:
>
> >>> import docker
> Traceback (most recent call last):
> File "", line 1, in 
> File "/usr/lib/python2.7/dist-packages/docker/__init__.py", line 2, 
in 

> from .api import APIClient
> File "/usr/lib/python2.7/dist-packages/docker/api/__init__.py", line 
2, in 

> from .client import APIClient
> File "/usr/lib/python2.7/dist-packages/docker/api/client.py", line 
11, in 

> from .build import BuildApiMixin
> File "/usr/lib/python2.7/dist-packages/docker/api/build.py", line 9, 
in 

> from .. import utils
> File "/usr/lib/python2.7/dist-packages/docker/utils/__init__.py", 
line 2, in 

> from .build import tar, exclude_paths
> File "/usr/lib/python2.7/dist-packages/docker/utils/build.py", line 
5, in 

> from .utils import create_archive
> File "/usr/lib/python2.7/dist-packages/docker/utils/utils.py", line 
18, in 

> from .. import tls
> File "/usr/lib/python2.7/dist-packages/docker/tls.py", line 5, in 


> from .transport import SSLAdapter
> File "/usr/lib/python2.7/dist-packages/docker/transport/__init__.py", 
line 3, in 

> from .ssladapter import SSLAdapter
> File 
"/usr/lib/python2.7/dist-packages/docker/transport/ssladapter.py", line 
21, in 

> from backports.ssl_match_hostname import match_hostname
> ImportError: No module named backports.ssl_match_hostname
>
> As you can see below, python-backports.ssl-match-hostname is installed
>
So (force) purging python-backports.ssl-match-hostname and reinstalling 
it fixed the isssue...


When purging dpkg showed the following lines:

Suppression de python-backports.ssl-match-hostname (3.5.0.1-1) ...
E: namespace:121: cannot remove 
/usr/lib/python2.7/dist-packages/backports/__init__.py


Somehow, /usr/lib/python2.7/dist-packages/backports/__init__.py was not 
existing on the system

Bug#892539: pdftk: Depends on GCJ which is going away

[Adrian Bunk]

On Sat, Mar 10, 2018 at 09:58:42AM +0100, po...@debian.org wrote:
> Source: pdftk
> Severity: serious
> Tags: sid buster
> User: debian-...@lists.debian.org
> Usertags: gcj-rm
> 
> Hi,
> 
> pdftk depends or build-depends on GCJ. GCJ has been dropped upstream
> since GCC 7, so we are dropping it from Debian. Thus please either
> drop support for GCJ if you are just building an alternative package
> with GCJ support (e.g. ant-gcj, ecj-gcj) or switch to default-jdk /
> default-jre as appropriate.

There seems to be a fork that makes that possible:
https://gitlab.com/marcvinyals/pdftk

Builds and works for me without gcj.

> Cheers, Emilio 

cu
Adrian

-- 

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

Bug#893520: ImportError: No module named backports.ssl_match_hostname

[Laurent Bigonville]

Package: python-docker
Version: 2.5.1-1
Severity: grave

Hi,

Seems that python-docker completely fails:

>>> import docker
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/docker/__init__.py", line 2, in 

from .api import APIClient
  File "/usr/lib/python2.7/dist-packages/docker/api/__init__.py", line 2, in 

from .client import APIClient
  File "/usr/lib/python2.7/dist-packages/docker/api/client.py", line 11, in 

from .build import BuildApiMixin
  File "/usr/lib/python2.7/dist-packages/docker/api/build.py", line 9, in 

from .. import utils
  File "/usr/lib/python2.7/dist-packages/docker/utils/__init__.py", line 2, in 

from .build import tar, exclude_paths
  File "/usr/lib/python2.7/dist-packages/docker/utils/build.py", line 5, in 

from .utils import create_archive
  File "/usr/lib/python2.7/dist-packages/docker/utils/utils.py", line 18, in 

from .. import tls
  File "/usr/lib/python2.7/dist-packages/docker/tls.py", line 5, in 
from .transport import SSLAdapter
  File "/usr/lib/python2.7/dist-packages/docker/transport/__init__.py", line 3, 
in 
from .ssladapter import SSLAdapter
  File "/usr/lib/python2.7/dist-packages/docker/transport/ssladapter.py", line 
21, in 
from backports.ssl_match_hostname import match_hostname
ImportError: No module named backports.ssl_match_hostname

As you can see below, python-backports.ssl-match-hostname is installed

Kind regards,

Laurent Bigonville

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

Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_BE.UTF-8, LC_CTYPE=fr_BE.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr_BE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: SELinux: enabled - Mode: Permissive - Policy name: refpolicy

Versions of packages python-docker depends on:
ii  python   2.7.14-4
ii  python-backports.ssl-match-hostname  3.5.0.1-1
ii  python-dockerpycreds 0.2.1-1
ii  python-ipaddress 1.0.17-1
ii  python-requests  2.18.4-2
ii  python-six   1.11.0-2
ii  python-websocket 0.37.0-2

python-docker recommends no packages.

python-docker suggests no packages.

-- no debconf information

Bug#893517: Installation of gcc-8 made clang-6 unusable.

[Roman Lebedev]

Package: clang-6.0
Version: 1:6.0-1
Severity: serious

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

$ cat test.cpp 
#include 
$ clang++-6.0 -c test.cpp 
In file included from test.cpp:1:
In file included from 
/usr/bin/../lib64/gcc/x86_64-linux-gnu/8.0.1/../../../../include/c++/8.0.1/ostream:38:
In file included from 
/usr/bin/../lib64/gcc/x86_64-linux-gnu/8.0.1/../../../../include/c++/8.0.1/ios:42:
In file included from 
/usr/bin/../lib64/gcc/x86_64-linux-gnu/8.0.1/../../../../include/c++/8.0.1/bits/ios_base.h:41:
In file included from 
/usr/bin/../lib64/gcc/x86_64-linux-gnu/8.0.1/../../../../include/c++/8.0.1/bits/locale_classes.h:40:
In file included from 
/usr/bin/../lib64/gcc/x86_64-linux-gnu/8.0.1/../../../../include/c++/8.0.1/string:48:
/usr/bin/../lib64/gcc/x86_64-linux-gnu/8.0.1/../../../../include/c++/8.0.1/bits/stl_function.h:545:9:
 error: redefinition of '__not_overloaded<_Tp, _Up>'
struct __not_overloaded<_Tp, _Up> : __not_overloaded2<_Tp, _Up> { };
   ^~
/usr/bin/../lib64/gcc/x86_64-linux-gnu/8.0.1/../../../../include/c++/8.0.1/bits/stl_function.h:531:9:
 note: previous definition is here
struct __not_overloaded<_Tp, _Up, __void_t<
   ^
/usr/bin/../lib64/gcc/x86_64-linux-gnu/8.0.1/../../../../include/c++/8.0.1/bits/stl_function.h:608:9:
 error: redefinition of '__not_overloaded<_Tp, _Up>'
struct __not_overloaded<_Tp, _Up> : __not_overloaded2<_Tp, _Up> { };
   ^~
/usr/bin/../lib64/gcc/x86_64-linux-gnu/8.0.1/../../../../include/c++/8.0.1/bits/stl_function.h:594:9:
 note: previous definition is here
struct __not_overloaded<_Tp, _Up, __void_t<
   ^
/usr/bin/../lib64/gcc/x86_64-linux-gnu/8.0.1/../../../../include/c++/8.0.1/bits/stl_function.h:671:9:
 error: redefinition of '__not_overloaded<_Tp, _Up>'
struct __not_overloaded<_Tp, _Up> : __not_overloaded2<_Tp, _Up> { };
   ^~
/usr/bin/../lib64/gcc/x86_64-linux-gnu/8.0.1/../../../../include/c++/8.0.1/bits/stl_function.h:657:9:
 note: previous definition is here
struct __not_overloaded<_Tp, _Up, __void_t<
   ^
/usr/bin/../lib64/gcc/x86_64-linux-gnu/8.0.1/../../../../include/c++/8.0.1/bits/stl_function.h:734:9:
 error: redefinition of '__not_overloaded<_Tp, _Up>'
struct __not_overloaded<_Tp, _Up> : __not_overloaded2<_Tp, _Up> { };
   ^~
/usr/bin/../lib64/gcc/x86_64-linux-gnu/8.0.1/../../../../include/c++/8.0.1/bits/stl_function.h:720:9:
 note: previous definition is here
struct __not_overloaded<_Tp, _Up, __void_t<
   ^
4 errors generated.


Strangely, clang-5 still works.
But clang-7 fails too.

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

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

Versions of packages clang-6.0 depends on:
ii  binutils 2.30-8
ii  libc62.27-2
ii  libc6-dev2.27-2
ii  libclang-common-6.0-dev  1:6.0-1
ii  libclang1-6.0    1:6.0-1
ii  libgcc-7-dev 7.3.0-12
ii  libgcc1  1:8-20180319-1
ii  libjsoncpp1  1.7.4-3
ii  libllvm6.0   1:6.0-1
ii  libobjc-7-dev    7.3.0-12
ii  libstdc++-7-dev  7.3.0-12
ii  libstdc++6   8-20180319-1

Versions of packages clang-6.0 recommends:
ii  libomp-dev6.0-1
ii  llvm-6.0-dev  1:6.0-1
ii  python2.7.14-4

Versions of packages clang-6.0 suggests:
pn  clang-6.0-doc  
pn  gnustep
pn  gnustep-devel  

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEjkF6151RK40WXe2HCDw+u0oWieAFAlqv5aYACgkQCDw+u0oW
ieABKxAAhombUUuICiB93PXBM8fZpsDyFrpMbFpd8JHCuNkRSXs9oNgRoLogWEMF
j+f+VDk8QYQt35C4rxCdVDqdm/4JYeV9wKlW0dIlmmPzQgPn819QwA5Y44qh492n
576n5GSFf/6UpoDLGbKaEqa3ayPCmMKRh2cMrW2939BV823enc/AMA3x7UU4Nzcp
zivn/oJfbvs5pQYOzg/IikUEiB4cxpajFtQ88V3W56mVe66Go+/GZkJwLpl8ZbYk
JOYyICIKXES1dNfCvHZv5v2ZADDDsQ/l+iR8paDZ4NVbaL7QANGttHtHv8uXa2NU
YkG2WZ5I2zw0sgmNxINJk5OuNb4I2m7MiYoZqfU4nSZ9FTnv8MFD6KhGLF4PmBYf
cc6LJY7GBkhMb8xU9UrUHHl8y2Q3H6vcbJPMYK3JcntLzfGVPmjlXrk2w8WWodR1
O8L1hQ+B1oF/ylcnzv3eOnM7ZqIs1XND6z53WuVhUaat3bKi9/B18esc0EXhIpMD
Sg6XCV1NfQU/6c3imWFb5h8UHt0KfL6PmAfn5dTYzoOhr0mkmWCwjtMdrtvD3GfV
+4MTGQvhC9U/+KWM8TqcYxjROjUEhy5Q5McqmzYJ55Z7RQ8X6Ag8+tuyKYiVYwUK
6thXK0devHBL9G5OQIRBTClRJT9t9+VLgWaVz2UEKsQHoNqRIA4=
=NUpD
-END PGP SIGNATURE-

Bug#854688: marked as done (bitlbee: The versions in stable/testing are vulnerable to CVE-2016-10189 and CVE-2016-10188)

[Debian Bug Tracking System]

Your message dated Mon, 19 Mar 2018 12:50:52 -0300
with message-id 

and subject line Re: Bug#854688
has caused the Debian Bug report #854688,
regarding bitlbee: The versions in stable/testing are vulnerable to 
CVE-2016-10189 and CVE-2016-10188
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.)


-- 
854688: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854688
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bitlbee
Version: 3.4.2-1.1
Severity: grave
Tags: upstream security patch fixed-upstream

Hi,

I'm opening this bug since #853282, which was just fixed by the
3.5.1-1 upload, seems to apply to sid only.

CVE-2016-10188 is "bitlbee-libpurple: Use after free when expiring
file transfer requests"

https://security-tracker.debian.org/tracker/CVE-2016-10188

CVE-2016-10189 is "Null pointer dereference with file transfer request
from unknown contacts"

https://security-tracker.debian.org/tracker/CVE-2016-10189

The current version in sid would fix both of these issues for stretch,
but it's blocked due to the freeze. I would like to request an unblock
for that particular case, if possible.

Thanks.
--- End Message ---
--- Begin Message ---
Version: 3.2.2-2+deb8u1

3.2.2-2+deb8u1 was uploaded to oldstable on 2017-06-07 and
stable/testing have the latest upstream release, this is done.--- End Message ---

Bug#892959: marked as done (slic3r-prusa FTBFS on 32bit: error: format not a string literal and no format arguments)

[Debian Bug Tracking System]

Your message dated Mon, 19 Mar 2018 15:43:29 +
with message-id 
and subject line Bug#892959: fixed in slic3r-prusa 1.39.1+dfsg-2
has caused the Debian Bug report #892959,
regarding slic3r-prusa FTBFS on 32bit: error: format not a string literal and 
no format arguments
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.)


-- 
892959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slic3r-prusa
Version: 1.39.1+dfsg-1
Severity: serious

https://buildd.debian.org/status/package.php?p=slic3r-prusa=sid

...
/usr/bin/perl -MExtUtils::XSpp::Cmd -e xspp -- -t 
"/<>/slic3r-prusa-1.39.1+dfsg/xs/xsp/typemap.xspt" 
"/<>/slic3r-prusa-1.39.1+dfsg/xs/xsp/Print.xsp": In function 'void 
XS_Slic3r__Print_output_filepath(PerlInterpreter*, CV*)':
/usr/bin/perl -MExtUtils::XSpp::Cmd -e xspp -- -t 
"/<>/slic3r-prusa-1.39.1+dfsg/xs/xsp/typemap.xspt" 
"/<>/slic3r-prusa-1.39.1+dfsg/xs/xsp/Print.xsp":847:31: error: format 
not a string literal and no format arguments [-Werror=format-security]
--- End Message ---
--- Begin Message ---
Source: slic3r-prusa
Source-Version: 1.39.1+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Chow Loong Jin  (supplier of updated slic3r-prusa 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, 19 Mar 2018 12:17:00 +0800
Source: slic3r-prusa
Binary: slic3r-prusa
Architecture: source amd64
Version: 1.39.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian 3-D Printing Packages 
<3dprinter-gene...@lists.alioth.debian.org>
Changed-By: Chow Loong Jin 
Description:
 slic3r-prusa - G-code generator for 3D printers
Closes: 892959
Changes:
 slic3r-prusa (1.39.1+dfsg-2) unstable; urgency=medium
 .
   * [3fb5ec7] Fix format-security FTBFS (Closes: #892959)
Checksums-Sha1:
 c6bbf2723c1ceba228283360c8c9fd5f3fcd523e 2580 slic3r-prusa_1.39.1+dfsg-2.dsc
 0a50961bed78b57beb74a7aa52b09401979c729d 28048 
slic3r-prusa_1.39.1+dfsg-2.debian.tar.xz
 00bf3ae9a5c78e42eeba10ac5a9231d61b8a5c4c 32850296 
slic3r-prusa-dbgsym_1.39.1+dfsg-2_amd64.deb
 32c762df3a56718e622ae779d18423b43268b964 20932 
slic3r-prusa_1.39.1+dfsg-2_amd64.buildinfo
 68860dd430bdb90c349d803eca99774a9f34697c 1750276 
slic3r-prusa_1.39.1+dfsg-2_amd64.deb
Checksums-Sha256:
 cdb7dbd5241196f66ddeb76536272441b600b4acbcf7d1ff0925c9a910a05f8c 2580 
slic3r-prusa_1.39.1+dfsg-2.dsc
 8a55598fa1e2d02cebc0be2d80bfc3f1f197cd81eb5ba42e0711c6ca8ccec6d4 28048 
slic3r-prusa_1.39.1+dfsg-2.debian.tar.xz
 06d4a7ddb5e14dc32b85f68f47ae0e9e6b8e45e14bff2c2395abc0be96b9e5c8 32850296 
slic3r-prusa-dbgsym_1.39.1+dfsg-2_amd64.deb
 540377392f2b94f1374268e475ace51a4490bee2d609d791aab6ddb1940dcfb9 20932 
slic3r-prusa_1.39.1+dfsg-2_amd64.buildinfo
 ff001057a2543537dfb988dfe30820de1b25b9f939edce92984ff5389b7502d3 1750276 
slic3r-prusa_1.39.1+dfsg-2_amd64.deb
Files:
 0655d5e7303466b70077d559e79a1be5 2580 perl optional 
slic3r-prusa_1.39.1+dfsg-2.dsc
 5a23dc216f227cc342f5100df20d50e7 28048 perl optional 
slic3r-prusa_1.39.1+dfsg-2.debian.tar.xz
 addf1c690b5d0eb247fdc7da1e2458ea 32850296 debug optional 
slic3r-prusa-dbgsym_1.39.1+dfsg-2_amd64.deb
 7201216684ea51bb628f3c373ea33823 20932 perl optional 
slic3r-prusa_1.39.1+dfsg-2_amd64.buildinfo
 0d046450cbc6a271164ae517603f1db9 1750276 perl optional 
slic3r-prusa_1.39.1+dfsg-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQIcBAEBCAAGBQJar1kDAAoJEPvVIltYh1KhBuIQAK6u5h2ohl5kdoBQOXnQorzx
p+eXer7tm94qTQw1JBHoahT3TtTdHkgAQgZairSxvAn3KVNbjGwNjXIeZX1mzxBn
l5i+ZA+x3TgGv7F0fdEliJQiz5iHqQcAIziwaKiKYBGV0N8EaH6UcyiV+d5G2FTi
uuIFMm+gJ+j0P/l1q8pJCEKd83ifSwb2LY6lAxxsZxEE1TKS8D1WfORr/sOd/zQx
UkS/bmjrb7CaFvtH28xdDHzfdTWdEtxZ7IDTh0s1cCSmrS4cEkYlbkGWGO6iqsF+
1pTztFxJUlMpB46EYUIBEQTBHXPvwgUrlB9mA789+j0zBcMU8uxJcl+SjyL9a4yh
Y4sY4zdbsazazvAuzetkKK8OOW0Bm62bftcBulCExhAvvYQU4LUAFSwTEdYUXVLx
EGMO2e10ZxV+7uefPQy9HvyLTqzpYeCHOAysKZMTy/0aUkeQw6twMWNYlFN4XC6u

Bug#893272: marked as done (aoflagger FTBFS with glibc 2.27)

[Debian Bug Tracking System]

Your message dated Mon, 19 Mar 2018 15:22:30 +
with message-id 
and subject line Bug#893272: fixed in aoflagger 2.10.0-2
has caused the Debian Bug report #893272,
regarding aoflagger FTBFS with glibc 2.27
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.)


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

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

...
In file included from 
/build/1st/aoflagger-2.10.0/src/interface/../quality/histogramcollection.h:4:0,
 from 
/build/1st/aoflagger-2.10.0/src/interface/aoflagger.cpp:19:
/build/1st/aoflagger-2.10.0/src/interface/../quality/loghistogram.h: In member 
function 'double LogHistogram::const_iterator::binStart() const':
/build/1st/aoflagger-2.10.0/src/interface/../quality/loghistogram.h:420:7: 
error: 'pow10' was not declared in this scope
   pow10(log10(_iterator->first)-0.005) :
   ^
/build/1st/aoflagger-2.10.0/src/interface/../quality/loghistogram.h:420:7: 
note: suggested alternative: 'powl'
   pow10(log10(_iterator->first)-0.005) :
   ^
   powl
/build/1st/aoflagger-2.10.0/src/interface/../quality/loghistogram.h: In member 
function 'double LogHistogram::const_iterator::binEnd() const':
/build/1st/aoflagger-2.10.0/src/interface/../quality/loghistogram.h:426:7: 
error: 'pow10' was not declared in this scope
   pow10(log10(_iterator->first)+0.005) :
   ^
/build/1st/aoflagger-2.10.0/src/interface/../quality/loghistogram.h:426:7: 
note: suggested alternative: 'powl'
   pow10(log10(_iterator->first)+0.005) :
   ^
   powl
/build/1st/aoflagger-2.10.0/src/interface/../quality/loghistogram.h: In member 
function 'double LogHistogram::binStart(double) const':
/build/1st/aoflagger-2.10.0/src/interface/../quality/loghistogram.h:493:5: 
error: 'pow10' was not declared in this scope
 pow10(log10(x)-0.005) :
 ^
/build/1st/aoflagger-2.10.0/src/interface/../quality/loghistogram.h:493:5: 
note: suggested alternative: 'powl'
 pow10(log10(x)-0.005) :
 ^
 powl
/build/1st/aoflagger-2.10.0/src/interface/../quality/loghistogram.h: In member 
function 'double LogHistogram::binEnd(double) const':
/build/1st/aoflagger-2.10.0/src/interface/../quality/loghistogram.h:499:5: 
error: 'pow10' was not declared in this scope
 pow10(log10(x)+0.005) :
 ^
/build/1st/aoflagger-2.10.0/src/interface/../quality/loghistogram.h:499:5: 
note: suggested alternative: 'powl'
 pow10(log10(x)+0.005) :
 ^
 powl
/build/1st/aoflagger-2.10.0/src/interface/../quality/loghistogram.h: In static 
member function 'static double LogHistogram::getCentralAmplitude(double)':
/build/1st/aoflagger-2.10.0/src/interface/../quality/loghistogram.h:506:12: 
error: 'pow10' was not declared in this scope
 return pow10(round(100.0*log10(amplitude))/100.0);
^
/build/1st/aoflagger-2.10.0/src/interface/../quality/loghistogram.h:506:12: 
note: suggested alternative: 'powl'
 return pow10(round(100.0*log10(amplitude))/100.0);
^
powl
/build/1st/aoflagger-2.10.0/src/interface/../quality/loghistogram.h:508:13: 
error: 'pow10' was not declared in this scope
 return -pow10(round(100.0*log10(-amplitude))/100.0);
 ^
--- End Message ---
--- Begin Message ---
Source: aoflagger
Source-Version: 2.10.0-2

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated aoflagger 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, 19 Mar 2018 15:08:04 +0100
Source: aoflagger
Binary: aoflagger libaoflagger0 aoflagger-dev
Architecture: source
Version: 2.10.0-2
Distribution: unstable
Urgency: low
Maintainer: Debian Astro Team 

Bug#893366: libwayland-dev: Uninstallable due to conflicting wayland-egl.pc

[Hector Oron]

Hello,

On Sun, Mar 18, 2018 at 11:35:52AM +0100, Guillem Jover wrote:
> Package: libwayland-dev
> Version: 1.14.91-1
> Severity: serious
> 
> Hi!
> 
> This package ships the file /usr/lib//pkgconfig/wayland-egl.pc
> which conflicts with the one installed by libegl1-mesa-dev, w/o any
> Replaces field or similar.
> 
> The problem also is that the file providing the shared library is also
> not pulled in by libwayland-dev, so packages that would find the
> pkg-config file would then fail to build, and they should really not
> be depending on the shared library directly.

Thanks for the report, I have pushed
  [debian-experimental 33a3903] libwayland-dev: fix installability issues
to address this issue. I would appreciate if you could review it.

Regards,
-- 


signature.asc
Description: PGP signature

Processed: tagging 893366

[Debian Bug Tracking System]

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

> tags 893366 + pending
Bug #893366 [libwayland-dev] libwayland-dev: Uninstallable due to conflicting 
wayland-egl.pc
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#893513: libayatana-indicator FTBFS: error: assignment from incompatible pointer type

[Helmut Grohne]

Source: libayatana-indicator
Version: 0.6.1-1
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

After failing to cross build libayatana-indicator, I tried to build it
natively, but it fails the same way:

| /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. 
-I../../../libayatana-indicator -I..   -Wdate-time -D_FORTIFY_SOURCE=2 -pthread 
-I/usr/include/libayatana-ido3-0.4 -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include  
-DG_LOG_DOMAIN=\"libayatana-indicator\" -Wall -Werror 
-Wno-error=deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -o 
libayatana_indicator3_la-indicator-ng.lo `test -f 'indicator-ng.c' || echo 
'../../../libayatana-indicator/'`indicator-ng.c
| libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I../../../libayatana-indicator 
-I.. -Wdate-time -D_FORTIFY_SOURCE=2 -pthread 
-I/usr/include/libayatana-ido3-0.4 -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 
-I/usr/include/libpng16 -I/usr/include/glib-2.0 
-I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-DG_LOG_DOMAIN=\"libayatana-indicator\" -Wall -Werror 
-Wno-error=deprecated-declarations -g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c 
../../../libayatana-indicator/indicator-ng.c  -fPIC -DPIC -o 
.libs/libayatana_indicator3_la-indicator-ng.o
| ../../../libayatana-indicator/indicator-ng.c: In function 'indicator_ng_init':
| ../../../libayatana-indicator/indicator-ng.c:690:21: error: assignment from 
incompatible pointer type [-Werror=incompatible-pointer-types]
|self->entry.label = g_object_ref_sink (gtk_label_new (NULL));
|  ^
| ../../../libayatana-indicator/indicator-ng.c:691:21: error: assignment from 
incompatible pointer type [-Werror=incompatible-pointer-types]
|self->entry.image = g_object_ref_sink (gtk_image_new ());
|  ^
| ../../../libayatana-indicator/indicator-ng.c:693:20: error: assignment from 
incompatible pointer type [-Werror=incompatible-pointer-types]
|self->entry.menu = g_object_ref_sink (gtk_menu_new ());
| ^
| cc1: all warnings being treated as errors
| make[5]: *** [Makefile:770: libayatana_indicator3_la-indicator-ng.lo] Error 1
| make[5]: Leaving directory 
'/<>/builddir/gtk3/libayatana-indicator'
| make[4]: *** [Makefile:520: all] Error 2
| make[4]: Leaving directory 
'/<>/builddir/gtk3/libayatana-indicator'
| make[3]: *** [Makefile:439: all-recursive] Error 1
| make[3]: Leaving directory '/<>/builddir/gtk3'
| make[2]: *** [Makefile:370: all] Error 2
| make[2]: Leaving directory '/<>/builddir/gtk3'
| dh_auto_build: cd builddir/gtk3 && make -j1 returned exit code 2
| make[1]: *** [debian/rules:33: dobuild-gtk3] Error 2
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:20: build-arch] Error 2
| dpkg-buildpackage: error: debian/rules build-arch subprocess returned exit 
status 2

Helmut