Bug#893458: libundead depends on cruft packages.

[peter green]

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.

Please update your package.

Bug#893424: Cannot uninstall package

[Ryan Kavanagh]

On Mon, Mar 19, 2018 at 01:42:09AM +0100, Andreas Beckmann wrote:
> Interesting. The empty directory shows up with size 0.
> What filesystem do you use for / ?

Similarly here:

rak@zeta:~$ ls -lashR /etc/mail
/etc/mail:
total 24K
   0 drwxr-xr-x 1 root root  138 Mar 18 14:32 .
   0 drwxr-xr-x 1 root root 5.3K Mar 18 17:51 ..
4.0K -rw-r--r-- 1 root root  281 Jan 13 17:43 address.resolve
   0 drwxr-xr-x 1 root root0 Jan 13 17:43 m4
   0 drwxr-xr-x 1 root root   16 Mar 18 13:30 peers
 12K -rw-r--r-- 1 root root  12K Mar 18 13:33 sendmail.conf
4.0K -rw-r--r-- 1 root root  148 Jan 13 17:43 service.switch
4.0K -rw-r--r-- 1 root root  179 Jan 13 17:43 service.switch-nodns

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

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

> What filesystem do you use for / ?

/dev/sda1 on / type btrfs (rw,relatime,ssd,space_cache,subvolid=5,subvol=/)

> The error should be triggered by this line in the prerm:
> # Remove empty files (probably touched databases)
> find /etc/mail -maxdepth 1 -size 0 | xargs -r rm;

Yeah, I think the problem is that it's calling 'rm' on directories. Tacking on a
'-type f' like you suggested (and perhaps even a '-delete' to skip the xargs
bit) would likely do the trick.

> $ find /etc/mail -maxdepth 1 -size 0
> $ find /etc/mail -maxdepth 1 -type f -size 0

rak@zeta:~$ find /etc/mail -maxdepth 1 -size 0
/etc/mail/m4
rak@zeta:~$ find /etc/mail -maxdepth 1 -type f -size 0
rak@zeta:~$

> The first should output /etc/mail/m4, the second should output nothing.

Your hunch on the error was right. I tried adding "set -x" to the top of the
prerm file, and got the following output:

rak@zeta:~$ sudo vim /var/lib/dpkg/info/sendmail-base.prerm
No protocol specified
rak@zeta:~$ sudo apt-get remove sendmail-base
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libxfont1 lockfile-progs
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  sendmail-base
0 upgraded, 0 newly installed, 1 to remove and 57 not upgraded.
After this operation, 867 kB disk space will be freed.
Do you want to continue? [Y/n]
(Reading database ... 389313 files and directories currently installed.)
Removing sendmail-base (8.15.2-10) ...
+ PACKAGE=sendmail-base
+ [ remove = remove ]
+ [ -x /usr/sbin/update-inetd ]
+ update-inetd --group MAIL --disable smtp,smtps,submission
+ [ -L /etc/mail/aliases ]
+ [ -f /etc/mail/aliases ]
+ rm -f /etc/cron.d/sendmail
+ rm -f /usr/lib/sasl/Sendmail.conf
+ rm -rf /var/lib/sendmail
+ rm -rf /var/run/sendmail
+ [ -x /etc/init.d/sendmail ]
+ [ -L /var/spool/mqueue ]
+ [ -d /var/spool/mqueue ]
+ [ -L /var/spool/mqueue-client ]
+ [ -d /var/spool/mqueue-client ]
+ rm -f /etc/mail/*.db /etc/mail/*.dir /etc/mail/*.pag
+ rm -f /etc/mail/sendmail.cf /etc/mail/sendmail.cf.old 
/etc/mail/sendmail.cf.errors /etc/mail/sendmail.mc.old /etc/mail/submit.cf 
/etc/mail/submit.cf.errors /etc/mail/submit.mc.old /etc/mail/databases 
/etc/mail/Makefile
+ rm -rf /etc/mail/smrsh /etc/mail/sasl /etc/mail/tls
+ find /etc/mail -maxdepth 1 -size 0
+ xargs -r rm
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)

Hope this helps,
Ryan

-- 
|)|/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac |  BD95 8F7B F8FC 4A11 C97A


signature.asc
Description: PGP signature

Bug#890751: rake FTBFS with Ruby 2.5: cannot load such file -- ubygems (LoadError)

[Georg Faerber]

I'll work on this today.

Cheers,
Georg


signature.asc
Description: Digital signature

Bug#893456: jawn: FTBFS with java 9

[Andreas Beckmann]

Source: jawn
Version: 0.10.4-1
Severity: serious
Justification: fails to build from source

Hi,

jawn FTBFS with openjdk-9 as the default jdk:

...
# Executing command line:
java
-Xms1024m
-Xmx1024m
-XX:ReservedCodeCacheSize=128m
-XX:MaxMetaspaceSize=256m
-Dsbt.ivy.home=/build/jawn-0.10.4/debian/sbt_home/.ivy2
-Dsbt.override.build.repos=true
-Dsbt.global.base=/build/jawn-0.10.4/debian/sbt_home/.sbt
-jar
/build/jawn-0.10.4/bootstrapsbt/bin/sbt-launch.jar
"set offline := true"
packageBin
make-pom

Getting org.scala-sbt sbt 0.13.12 ...
:: retrieving :: org.scala-sbt#boot-app
confs: [default]
49 artifacts copied, 0 already retrieved (17462kB/94ms)
Getting Scala 2.10.6 (for sbt)...
:: retrieving :: org.scala-sbt#boot-scala
confs: [default]
5 artifacts copied, 0 already retrieved (24494kB/39ms)
error: error while loading package, Missing dependency 'object java.lang.Object 
in compiler mirror', required by 
/build/jawn-0.10.4/debian/sbt_home/.sbt/boot/scala-2.10.6/lib/scala-library.jar(scala/package.class)
error: error while loading package, Missing dependency 'object java.lang.Object 
in compiler mirror', required by 
/build/jawn-0.10.4/debian/sbt_home/.sbt/boot/scala-2.10.6/lib/scala-library.jar(scala/runtime/packag
e.class)
scala.reflect.internal.MissingRequirementError: object java.lang.Object in 
compiler mirror not found.
at 
scala.reflect.internal.MissingRequirementError$.signal(MissingRequirementError.scala:16)
at 
scala.reflect.internal.MissingRequirementError$.notFound(MissingRequirementError.scala:17)
...


Andreas


jawn_0.10.4-1.log.gz
Description: application/gzip

Bug#893454: libjloda-java: FTBFS with java 9

[Andreas Beckmann]

Source: libjloda-java
Version: 0.0+20170502-1
Severity: serious
Justification: fails to build from source

Hi,

libjloda-java FTBFS with openjdk-9 as default jdk:

compile:
[javac] Compiling 265 source files to 
/build/libjloda-java-0.0+20170502/antbuild/class
[javac] 
/build/libjloda-java-0.0+20170502/antbuild/src/jloda/phylo/PhyloTree.java:30: 
error: package com.sun.istack.internal is not visible
[javac] import com.sun.istack.internal.Nullable;
[javac]  ^
[javac]   (package com.sun.istack.internal is declared in module 
java.xml.bind, which is not in the module graph)
[javac] 
/build/libjloda-java-0.0+20170502/antbuild/src/jloda/graphview/NodeView.java:258:
 warning: [dep-ann] deprecated item is not annotated with @Deprecated
[javac] public void setShape(byte a) {
[javac] ^
[javac] 
/build/libjloda-java-0.0+20170502/antbuild/src/jloda/graphview/NodeView.java:268:
 warning: [dep-ann] deprecated item is not annotated with @Deprecated
[javac] public byte getShape() {
[javac] ^
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 1 error
[javac] 2 warnings


Andreas


libjloda-java_0.0+20170502-1_indep.log.gz
Description: application/gzip

Bug#893453: json4s: FTBFS with java 9

[Andreas Beckmann]

Source: json4s
Version: 3.5.0-1
Severity: serious
Justification: fails to build from source

Hi,

json4s started to FTBFS since the default jdk ws changed to openjdk 9.

...
# Executing command line:
java
-Xms1024m
-Xmx1024m
-XX:ReservedCodeCacheSize=128m
-XX:MaxMetaspaceSize=256m
-Dsbt.ivy.home=/build/json4s-3.5.0/debian/sbt_home/.ivy2
-Dsbt.override.build.repos=true
-Dsbt.global.base=/build/json4s-3.5.0/debian/sbt_home/.sbt
-jar
/build/json4s-3.5.0/bootstrapsbt/bin/sbt-launch.jar
"set offline := true"
packageBin
make-pom

Getting org.scala-sbt sbt 0.13.12 ...
:: retrieving :: org.scala-sbt#boot-app
confs: [default]
49 artifacts copied, 0 already retrieved (17462kB/172ms)
Getting Scala 2.10.6 (for sbt)...
:: retrieving :: org.scala-sbt#boot-scala
confs: [default]
5 artifacts copied, 0 already retrieved (24494kB/38ms)
error: error while loading package, Missing dependency 'object java.lang.Object 
in compiler mirror', required by 
/build/json4s-3.5.0/debian/sbt_home/.sbt/boot/scala-2.10.6/lib/scala-library.jar(scala/package.class)
error: error while loading package, Missing dependency 'object java.lang.Object 
in compiler mirror', required by 
/build/json4s-3.5.0/debian/sbt_home/.sbt/boot/scala-2.10.6/lib/scala-library.jar(scala/runtime/package.class)
scala.reflect.internal.MissingRequirementError: object java.lang.Object in 
compiler mirror not found.
at 
scala.reflect.internal.MissingRequirementError$.signal(MissingRequirementError.scala:16)
...


Andreas


json4s_3.5.0-1_indep.log.gz
Description: application/gzip

Bug#893424: Cannot uninstall package

[Andreas Beckmann]

On 2018-03-18 19:43, Ryan Kavanagh wrote:
> 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

> 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

Interesting. The empty directory shows up with size 0.
What filesystem do you use for / ?

The error should be triggered by this line in the prerm:
# Remove empty files (probably touched databases)
find /etc/mail -maxdepth 1 -size 0 | xargs -r rm;

Please run these two commands:

$ find /etc/mail -maxdepth 1 -size 0
$ find /etc/mail -maxdepth 1 -type f -size 0

The first should output /etc/mail/m4, the second should output nothing.


Andreas

Bug#892458: marked as done (cfitsio: vulnerabilities)

[Debian Bug Tracking System]

Your message dated Mon, 19 Mar 2018 00:34:12 +
with message-id 
and subject line Bug#892458: fixed in cfitsio 3.430-1
has caused the Debian Bug report #892458,
regarding cfitsio: vulnerabilities
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.)


-- 
892458: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892458
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cfitsio
Version: 3.420-3
Severity: grave
Tags: security

Hi,

a new version of cfitsio just came out, accompanied with the following
notice from upstream:

The NASA security team requires the following warning to all users of
CFITSIO:

   =
   The CFITSIO open source software project contains vulnerabilities
   that could allow a remote, unauthenticated attacker to take control
   of a server running the CFITSIO software.  These vulnerabilities
   affect all servers and products running the CFITSIO software.

   The CFITSIO team has released software updates to address these
   vulnerabilities.  There are no workarounds to address these
   vulnerabilities.  In all cases, the CFITSIO team is recommending an
   immediate update to resolve the issues.
   =


I didn't check the specific problem, but it may be important to upgrade.

Best regards

Ole
--- End Message ---
--- Begin Message ---
Source: cfitsio
Source-Version: 3.430-1

We believe that the bug you reported is fixed in the latest version of
cfitsio, 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.
Aurelien Jarno  (supplier of updated cfitsio 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 01:02:44 +0100
Source: cfitsio
Binary: libcfitsio5 libcfitsio-dev libcfitsio-bin libcfitsio-doc
Architecture: source
Version: 3.430-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Astronomy Maintainers 

Changed-By: Aurelien Jarno 
Description:
 libcfitsio-bin - CFITSIO based utilities
 libcfitsio-dev - library for I/O with FITS format data files (development 
files)
 libcfitsio-doc - documentation for CFITSIO
 libcfitsio5 - shared library for I/O with FITS format data files
Closes: 892458
Changes:
 cfitsio (3.430-1) unstable; urgency=medium
 .
   * New upstream version:
 - Fixes unknown vulnerabilities (Closes: #892458).
 - Rebase 07-pkgconfig-no-curl.patch.
   * Update VCS URLs to salsa.debian.org.
   * Rebuild all PDF documentation and ship it instead of the PS version.
Checksums-Sha1:
 8eddffe5984f7045f0ae1706d653bad402d9792b 2264 cfitsio_3.430-1.dsc
 78b6c36d5146e278b1904d4b6aa81bf1f5d186e5 4696718 cfitsio_3.430.orig.tar.gz
 1149ce021c1f70b281a6f417c5fe88a8596e2373 1 cfitsio_3.430-1.debian.tar.xz
 135c1a8f757d76f2f937d9a6ad4631750dbf2417 5437 cfitsio_3.430-1_source.buildinfo
Checksums-Sha256:
 637cf0eed2043ea4fda0374e44e87e64e313033534d2d6e1f8923bb46135421b 2264 
cfitsio_3.430-1.dsc
 c8deae752aba1e736336b01f0471d4004a497dc50bc1e01aad2eebb2574084e7 4696718 
cfitsio_3.430.orig.tar.gz
 cf3667130c9dcd2a9ac64750e19985160002e14ccfb29ba7467c18fc17348217 1 
cfitsio_3.430-1.debian.tar.xz
 3c1f7e60c36a4788c3a725a9de89cacda0a5288022ead3217e2628be02fbc786 5437 
cfitsio_3.430-1_source.buildinfo
Files:
 498bae2d2b3d2e4dfc71d730bbf6ca06 2264 devel optional cfitsio_3.430-1.dsc
 d23ab7cad8853bcb8b192681cb4cb7b8 4696718 devel optional 
cfitsio_3.430.orig.tar.gz
 c2d2d744ed5148701a5dcd6a38b936bd 1 devel optional 
cfitsio_3.430-1.debian.tar.xz
 75772d8a194a763daa1d1a6f069ec838 5437 devel optional 
cfitsio_3.430-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEUryGlb40+QrX1Ay4E4jA+JnoM2sFAlqu/kwACgkQE4jA+Jno
M2thgw/+LtnHu/4ErAxqonHGEuc9vzO9DjpScbgaymc4D7OoeolFX46P0daR/sL2
oCnPhEHR77DNjEHkw5ACdSTQ2J+cat7sE75Ok7UaTI+DvkAdOS4QFMtWkZTWZcll
u670sQ7a+2s8KgueAswrgi6fU8bECwOP+ZP21I9mAe6fGkDqk7P0slixnBLFu422
ILvGlxVm1maceXk6r+nVMTXzKPg4214oEVWbGZKC62wUAc0UeEAOMuDQea0iUCLd
Sh2djJSLyt/7B+NWZ4PHWcZvnD4wrJhXws+o7sflL/APNzsT06f+wjOb2Bo5ufKK

Bug#844939: Yup, fixed.

[Gilles Filippini]

On Sat, 17 Mar 2018 17:00:08 +0100 Gilles Filippini  wrote:
> Hi,
> 
> I've just tried to build your package and it fails the tests:
> # still have 3 known breakage(s)
> # failed 18 among remaining 36 test(s)
> 1..39

Actually, after upgrading against [1] it builds fine.

[1] https://github.com/mnauw/git-remote-hg/issues/11

Thanks,

_g.



signature.asc
Description: OpenPGP digital signature

Processed (with 1 error): Fwd: python-lesscpy

[Debian Bug Tracking System]

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

> retitle 893233 python-lesscpy: python3-lesscpy not working with python
Bug #893233 [src:python-lesscpy] python-lesscpy: python3-lesscpy not working 
with python
Ignoring request to change the title of bug#893233 to the same title
>   3.5 or newer
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Bug#893357: marked as done (jboss-logmanager FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Sun, 18 Mar 2018 23:20:40 +
with message-id 
and subject line Bug#893357: fixed in jboss-logmanager 2.1.0-1
has caused the Debian Bug report #893357,
regarding jboss-logmanager 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.)


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

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

...
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running org.jboss.logmanager.FileHandlerPerformanceTests
459
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.61 s - 
in org.jboss.logmanager.FileHandlerPerformanceTests
[INFO] Running org.jboss.logmanager.LogManagerTests
[ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.001 s 
<<< FAILURE! - in org.jboss.logmanager.LogManagerTests
[ERROR] testLevelReplacement(org.jboss.logmanager.LogManagerTests)  Time 
elapsed: 0.001 s  <<< FAILURE!
java.lang.AssertionError: expected: but was:
at 
org.jboss.logmanager.LogManagerTests.testLevelReplacement(LogManagerTests.java:74)

[INFO] Running org.jboss.logmanager.formatters.PatternFormatterTests
[INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.026 s 
- in org.jboss.logmanager.formatters.PatternFormatterTests
[INFO] Running org.jboss.logmanager.formatters.FormattersTests
[INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 s 
- in org.jboss.logmanager.formatters.FormattersTests
[INFO] Running org.jboss.logmanager.formatters.StackTraceFormatterTests
[INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.058 s 
- in org.jboss.logmanager.formatters.StackTraceFormatterTests
[INFO] Running org.jboss.logmanager.PropertyConfiguratorTests
Handler c2 is not defined and will not be written to the configuration for 
logger test.logger
Error manager INVALID is not defined
Handler INVALID is not defined
Formatter INVALID is not defined
[INFO] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.181 s 
- in org.jboss.logmanager.PropertyConfiguratorTests
[INFO] Running org.jboss.logmanager.LoggerTests
[INFO] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.022 s 
- in org.jboss.logmanager.LoggerTests
[INFO] Running org.jboss.logmanager.ProtectTests
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 s 
- in org.jboss.logmanager.ProtectTests
[INFO] Running org.jboss.logmanager.FilterTests
[INFO] Tests run: 28, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.025 s 
- in org.jboss.logmanager.FilterTests
[INFO] Running org.jboss.logmanager.handlers.AsyncHandlerTests
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 s 
- in org.jboss.logmanager.handlers.AsyncHandlerTests
[INFO] Running org.jboss.logmanager.handlers.PeriodicRotatingFileHandlerTests
[13:42:35,333 INFO  [null] (main) Date: 2019-05-09]
[13:42:35,350 INFO  [null] (main) Date: 2019-05-09]
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.073 s 
- in org.jboss.logmanager.handlers.PeriodicRotatingFileHandlerTests
[INFO] Running org.jboss.logmanager.handlers.SizeRotatingFileHandlerTests
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.054 s 
- in org.jboss.logmanager.handlers.SizeRotatingFileHandlerTests
[INFO] Running 
org.jboss.logmanager.handlers.PeriodicSizeRotatingFileHandlerTests
[WARNING] Tests run: 3, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 0.038 
s - in org.jboss.logmanager.handlers.PeriodicSizeRotatingFileHandlerTests
[INFO] Running org.jboss.logmanager.handlers.SyslogHandlerTests
[INFO] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.093 s 
- in org.jboss.logmanager.handlers.SyslogHandlerTests
[INFO] Running org.jboss.logmanager.handlers.QueueHandlerTests
[INFO] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 s 
- in org.jboss.logmanager.handlers.QueueHandlerTests
[INFO] Running org.jboss.logmanager.HandlerTests
[INFO] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 s 
- in org.jboss.logmanager.HandlerTests
[INFO] 
[INFO] Results:
[INFO] 
[ERROR] Failures: 
[ERROR]   LogManagerTests.testLevelReplacement:74 expected: but 
was:
[INFO] 
[ERROR] Tests run: 93, Failures: 

Bug#893143: marked as done (easyconf FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Sun, 18 Mar 2018 23:19:37 +
with message-id 
and subject line Bug#893143: fixed in easyconf 0.9.5-6
has caused the Debian Bug report #893143,
regarding easyconf 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.)


-- 
893143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: easyconf
Version: 0.9.5-5
Severity: serious
Tags: buster sid

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

...
compile:
[mkdir] Created dir: /build/1st/easyconf-0.9.5/target/classes
[javac] /build/1st/easyconf-0.9.5/build.xml:36: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Compiling 27 source files to 
/build/1st/easyconf-0.9.5/target/classes
[javac] Using ant.build.javac.target 1.5 is no longer supported, switching 
to 1.6
[javac] Using ant.build.javac.target 1.5 is no longer supported, switching 
to 1.6
[javac] Using ant.build.javac.source 1.5 is no longer supported, switching 
to 1.6
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/easyconf-0.9.5/src/java/com/germinus/easyconf/ClassParameter.java:25:
 error: unmappable character (0xE9) for encoding US-ASCII
[javac]  * M?todos de utilidad para trabajar con par?metros de 
configuraci?n que representan
[javac] ^
[javac] 
/build/1st/easyconf-0.9.5/src/java/com/germinus/easyconf/ClassParameter.java:25:
 error: unmappable character (0xE1) for encoding US-ASCII
[javac]  * M?todos de utilidad para trabajar con par?metros de 
configuraci?n que representan
[javac] ^
[javac] 
/build/1st/easyconf-0.9.5/src/java/com/germinus/easyconf/ClassParameter.java:25:
 error: unmappable character (0xF3) for encoding US-ASCII
[javac]  * M?todos de utilidad para trabajar con par?metros de 
configuraci?n que representan
[javac]   ^
[javac] 
/build/1st/easyconf-0.9.5/src/java/com/germinus/easyconf/ClassParameter.java:28:
 error: unmappable character (0xFA) for encoding US-ASCII
[javac]  * @author Jes?s J?imez Rodr?guez 
[javac]   ^
[javac] 
/build/1st/easyconf-0.9.5/src/java/com/germinus/easyconf/ClassParameter.java:28:
 error: unmappable character (0xE1) for encoding US-ASCII
[javac]  * @author Jes?s J?imez Rodr?guez 
[javac]   ^
[javac] 
/build/1st/easyconf-0.9.5/src/java/com/germinus/easyconf/ClassParameter.java:28:
 error: unmappable character (0xED) for encoding US-ASCII
[javac]  * @author Jes?s J?imez Rodr?guez 
[javac] ^
[javac] 
/build/1st/easyconf-0.9.5/src/java/com/germinus/easyconf/jmx/ComponentConfigurationDynamicMBean.java:49:
 error: unmappable character (0xEF) for encoding US-ASCII
[javac]  * @author Alvaro Gonz???lez
[javac]   ^
[javac] 
/build/1st/easyconf-0.9.5/src/java/com/germinus/easyconf/jmx/ComponentConfigurationDynamicMBean.java:49:
 error: unmappable character (0xBF) for encoding US-ASCII
[javac]  * @author Alvaro Gonz???lez
[javac]^
[javac] 
/build/1st/easyconf-0.9.5/src/java/com/germinus/easyconf/jmx/ComponentConfigurationDynamicMBean.java:49:
 error: unmappable character (0xBD) for encoding US-ASCII
[javac]  * @author Alvaro Gonz???lez
[javac] ^
[javac] 9 errors
[javac] 4 warnings

BUILD FAILED
/build/1st/easyconf-0.9.5/build.xml:36: Compile failed; see the compiler error 
output for details.

Total time: 9 seconds
make: *** [/usr/share/cdbs/1/class/ant.mk:39: debian/stamp-ant-build] Error 1
--- End Message ---
--- Begin Message ---
Source: easyconf
Source-Version: 0.9.5-6

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

Processed (with 1 error): Fwd: python-lesscpy

[Debian Bug Tracking System]

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

> retitle 893233 python-lesscpy: python3-lesscpy not working with python
Bug #893233 [src:python-lesscpy] python-lesscpy: python3-lesscpy not working 
with python
Ignoring request to change the title of bug#893233 to the same title
> 3.5 or newer
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Processed: Bug #893426 in systemd marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #893426 [systemd] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN
Added tag(s) pending.

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

Bug#893426: Bug #893426 in systemd marked as pending

[biebl]

Control: tag -1 pending

Hello,

Bug #893426 in systemd 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/systemd-team/systemd/commit/975f69262e207d1f8a4bbaef1e98c60f839eaf3d


basic/macros: Rename noreturn into _noreturn_

"noreturn" is reserved and can be used in other header files we include.

Closes: #893426



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/893426

Processed: Pending fixes for bugs in the easyconf package

[Debian Bug Tracking System]

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

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

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

Bug#893143: Pending fixes for bugs in the easyconf package

[pkg-java-maintainers]

tag 893143 + pending
thanks

Some bugs in the easyconf package are closed in revision
4010904deb4748d81df544a9a4a8950ee5899861 in branch 'master' by
Emmanuel Bourg

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

Commit message:

Fixed the build failure with Java 9 (Closes: #893143)

Processed: reassign 893393 to src:linux, severity of 893393 is important

[Debian Bug Tracking System]

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

> reassign 893393 src:linux 4.14.17-1
Bug #893393 [src:linux] linux-image-amd64: Kernel panic on active outgoing 
traffic through Huawei E173 modem in NDIS (CDC) mode
Ignoring request to reassign bug #893393 to the same package
Bug #893393 [src:linux] linux-image-amd64: Kernel panic on active outgoing 
traffic through Huawei E173 modem in NDIS (CDC) mode
Ignoring request to alter found versions of bug #893393 to the same values 
previously set
> severity 893393 important
Bug #893393 [src:linux] linux-image-amd64: Kernel panic on active outgoing 
traffic through Huawei E173 modem in NDIS (CDC) mode
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Bug#885117: marked as done (drupal7-mod-civicrm: Please stop building the drupal7-mod-civicrm binary package (dependency drupal7 to be removed))

[Debian Bug Tracking System]

Your message dated Sun, 18 Mar 2018 22:35:12 +
with message-id 
and subject line Bug#885117: fixed in civicrm 4.7.30+dfsg-1
has caused the Debian Bug report #885117,
regarding drupal7-mod-civicrm: Please stop building the drupal7-mod-civicrm 
binary package (dependency drupal7 to be removed)
to be marked as done.

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

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


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

Hi,

I have requested ftp-masters to remove drupaly (#884929) as it should
not be part of the next stable Debian release. I have been pointed out
drupal7-mod-civicrm depends on it.

Please build a new release of civicrm that does not generate this
binary package!

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

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

Versions of packages drupal7-mod-civicrm depends on:
pn  civicrm-common  
pn  drupal7 

drupal7-mod-civicrm recommends no packages.

Versions of packages drupal7-mod-civicrm suggests:
pn  civicrm-l10n  
--- End Message ---
--- Begin Message ---
Source: civicrm
Source-Version: 4.7.30+dfsg-1

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated civicrm 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 08:27:36 +1100
Source: civicrm
Binary: civicrm-common civicrm-l10n wordpress-civicrm
Architecture: source all
Version: 4.7.30+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 civicrm-common - CiviCRM common files
 civicrm-l10n - CiviCRM country and language data
 wordpress-civicrm - CiviCRM plugin for WordPress
Closes: 883640 885117 887330
Changes:
 civicrm (4.7.30+dfsg-1) unstable; urgency=medium
 .
   * New upstream release [February 2018].
 + fixed multiple XSS vulnerabilities (Closes: #887330).
 + fixed compatibility with php-symfony 3.4 (Closes: #883640).
   * No longer build "drupal7-mod-civicrm" package (Closes: #885117).
 Thanks, Gunnar Wolf.
   * Standards-Version: 4.1.3.
   * debhelper & compat to version 11.
Checksums-Sha1:
 8f3a083db6b434b3f6247afdb77732fc6414457b 3210 civicrm_4.7.30+dfsg-1.dsc
 e3e52d655c0f912a68b06b23cdf7b068c695a549 7588660 
civicrm_4.7.30+dfsg.orig-l10n.tar.xz
 98e70e07eafb50e6968cf7469a17e5ecd0e4aa6d 45496 
civicrm_4.7.30+dfsg.orig-wordpress.tar.xz
 b0cfa2ecbbb9d3a257ba8518d007fdcba31c88df 8713388 
civicrm_4.7.30+dfsg.orig.tar.xz
 f0eb1d7a26cd6434d03fdff73a97ac782651f6e9 40860 
civicrm_4.7.30+dfsg-1.debian.tar.xz
 f62d3934cb480480ff2c8ac1c34f866330c3e370 7402092 
civicrm-common_4.7.30+dfsg-1_all.deb
 d3800b9d00680aa48d978e76eb7ff979535fe3b4 8144908 
civicrm-l10n_4.7.30+dfsg-1_all.deb
 85a612301965dc68a9c08232fa6bda17a0a294f4 8806 
civicrm_4.7.30+dfsg-1_amd64.buildinfo
 7b97a1ece2cca45c2060bea3bac9bd2c30699124 729260 
wordpress-civicrm_4.7.30+dfsg-1_all.deb
Checksums-Sha256:
 3a267f087e7a55b626c04fa94b8813bf2af538bf45d68a9763e51cc4ad205285 3210 
civicrm_4.7.30+dfsg-1.dsc
 445494031608555c6c471cfea775517955764b69d4bc7da3b8ea048c069ebaf6 7588660 
civicrm_4.7.30+dfsg.orig-l10n.tar.xz
 3a96620ba57664c680101ae809288c51d08b5cf44702f8109c745cb709694527 45496 
civicrm_4.7.30+dfsg.orig-wordpress.tar.xz
 4d86ebc8b9f65362ce00bccdca94de52a2c012b63f50b01bce9f557b1a8c64e2 8713388 
civicrm_4.7.30+dfsg.orig.tar.xz
 93898ba5b7f64111df3113465598d608a628e8d91076863d4c47346565320f6f 40860 
civicrm_4.7.30+dfsg-1.debian.tar.xz
 06e78c174cd991aed9c32e191860637d40a1fbd4969e08a9a9103b7d3fd31b13 7402092 

Bug#887330: marked as done (civicrm: Multiple XSS vulnerabilities were found in CiviCRM <4.7.26)

[Debian Bug Tracking System]

Your message dated Sun, 18 Mar 2018 22:35:12 +
with message-id 
and subject line Bug#887330: fixed in civicrm 4.7.30+dfsg-1
has caused the Debian Bug report #887330,
regarding civicrm: Multiple XSS vulnerabilities were found in CiviCRM <4.7.26
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.)


-- 
887330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: civicrm
Version: 4.7.24+dfsg-1
Severity: serious
Tags: security
Justification: security issues

(Since CiviCRM isn't in Jessie nor in Stretch I guess the Security Team
can ignore this.)

4.7.26, released on Nov. 1, fixes multiple security issues, with risks
upstream classified up to “critical” for CIVI-SA-2017-1[1-5]:

CIVI-SA-2017-08 XSS in HTML link attributes
CIVI-SA-2017-09 Shell injection vulnerability in smarty
CIVI-SA-2017-10 XSS scripting in premium product name 
CIVI-SA-2017-11 XSS in dedupe rules 
CIVI-SA-2017-12 XSS in tag descrption
CIVI-SA-2017-13 Selectedchild URL parameter not properly validated for 
CiviCRM message templates 
CIVI-SA-2017-14 XSS in search criteria description 
CIVI-SA-2017-15 Extension key not properly validated when adding or 
disabling or uninstalling extension 
CIVI-SA-2017-16 SQL injection risk in CiviReports listing
— 
https://civicrm.org/blog/dev-team/security-release-civicrm-4726-and-4633-monthly-release-4727

-- 
Guilhem.


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: civicrm
Source-Version: 4.7.30+dfsg-1

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated civicrm 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 08:27:36 +1100
Source: civicrm
Binary: civicrm-common civicrm-l10n wordpress-civicrm
Architecture: source all
Version: 4.7.30+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 civicrm-common - CiviCRM common files
 civicrm-l10n - CiviCRM country and language data
 wordpress-civicrm - CiviCRM plugin for WordPress
Closes: 883640 885117 887330
Changes:
 civicrm (4.7.30+dfsg-1) unstable; urgency=medium
 .
   * New upstream release [February 2018].
 + fixed multiple XSS vulnerabilities (Closes: #887330).
 + fixed compatibility with php-symfony 3.4 (Closes: #883640).
   * No longer build "drupal7-mod-civicrm" package (Closes: #885117).
 Thanks, Gunnar Wolf.
   * Standards-Version: 4.1.3.
   * debhelper & compat to version 11.
Checksums-Sha1:
 8f3a083db6b434b3f6247afdb77732fc6414457b 3210 civicrm_4.7.30+dfsg-1.dsc
 e3e52d655c0f912a68b06b23cdf7b068c695a549 7588660 
civicrm_4.7.30+dfsg.orig-l10n.tar.xz
 98e70e07eafb50e6968cf7469a17e5ecd0e4aa6d 45496 
civicrm_4.7.30+dfsg.orig-wordpress.tar.xz
 b0cfa2ecbbb9d3a257ba8518d007fdcba31c88df 8713388 
civicrm_4.7.30+dfsg.orig.tar.xz
 f0eb1d7a26cd6434d03fdff73a97ac782651f6e9 40860 
civicrm_4.7.30+dfsg-1.debian.tar.xz
 f62d3934cb480480ff2c8ac1c34f866330c3e370 7402092 
civicrm-common_4.7.30+dfsg-1_all.deb
 d3800b9d00680aa48d978e76eb7ff979535fe3b4 8144908 
civicrm-l10n_4.7.30+dfsg-1_all.deb
 85a612301965dc68a9c08232fa6bda17a0a294f4 8806 
civicrm_4.7.30+dfsg-1_amd64.buildinfo
 7b97a1ece2cca45c2060bea3bac9bd2c30699124 729260 
wordpress-civicrm_4.7.30+dfsg-1_all.deb
Checksums-Sha256:
 3a267f087e7a55b626c04fa94b8813bf2af538bf45d68a9763e51cc4ad205285 3210 
civicrm_4.7.30+dfsg-1.dsc
 445494031608555c6c471cfea775517955764b69d4bc7da3b8ea048c069ebaf6 7588660 
civicrm_4.7.30+dfsg.orig-l10n.tar.xz
 3a96620ba57664c680101ae809288c51d08b5cf44702f8109c745cb709694527 45496 
civicrm_4.7.30+dfsg.orig-wordpress.tar.xz
 4d86ebc8b9f65362ce00bccdca94de52a2c012b63f50b01bce9f557b1a8c64e2 8713388 
civicrm_4.7.30+dfsg.orig.tar.xz
 93898ba5b7f64111df3113465598d608a628e8d91076863d4c47346565320f6f 

Bug#883640: marked as done (civicrm-common: uninstallable in sid: Depends: php-symfony-* (< 3~~) but 3.4.0+dfsg-1 is to be installed)

[Debian Bug Tracking System]

Your message dated Sun, 18 Mar 2018 22:35:12 +
with message-id 
and subject line Bug#883640: fixed in civicrm 4.7.30+dfsg-1
has caused the Debian Bug report #883640,
regarding civicrm-common: uninstallable in sid: Depends: php-symfony-* (< 3~~) 
but 3.4.0+dfsg-1 is to be installed
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.)


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

Hi,

during a test with piuparts I noticed your package is no longer
installable in sid:

The following packages have unmet dependencies:
 civicrm-common : Depends: php-symfony-config (< 3~~) but 3.4.0+dfsg-1 is to be 
installed
  Depends: php-symfony-dependency-injection (< 3~~) but 
3.4.0+dfsg-1 is to be installed
  Depends: php-symfony-event-dispatcher (< 3~~) but 
3.4.0+dfsg-1 is to be installed
  Depends: php-symfony-filesystem (< 3~~) but 3.4.0+dfsg-1 is 
to be installed
  Depends: php-symfony-process (< 3~~) but 3.4.0+dfsg-1 is to 
be installed
  Depends: php-symfony-finder (< 3~~) but 3.4.0+dfsg-1 is to be 
installed
E: Unable to correct problems, you have held broken packages.


Cheers,

Andreas
--- End Message ---
--- Begin Message ---
Source: civicrm
Source-Version: 4.7.30+dfsg-1

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

Debian distribution maintenance software
pp.
Dmitry Smirnov  (supplier of updated civicrm 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 08:27:36 +1100
Source: civicrm
Binary: civicrm-common civicrm-l10n wordpress-civicrm
Architecture: source all
Version: 4.7.30+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Dmitry Smirnov 
Changed-By: Dmitry Smirnov 
Description:
 civicrm-common - CiviCRM common files
 civicrm-l10n - CiviCRM country and language data
 wordpress-civicrm - CiviCRM plugin for WordPress
Closes: 883640 885117 887330
Changes:
 civicrm (4.7.30+dfsg-1) unstable; urgency=medium
 .
   * New upstream release [February 2018].
 + fixed multiple XSS vulnerabilities (Closes: #887330).
 + fixed compatibility with php-symfony 3.4 (Closes: #883640).
   * No longer build "drupal7-mod-civicrm" package (Closes: #885117).
 Thanks, Gunnar Wolf.
   * Standards-Version: 4.1.3.
   * debhelper & compat to version 11.
Checksums-Sha1:
 8f3a083db6b434b3f6247afdb77732fc6414457b 3210 civicrm_4.7.30+dfsg-1.dsc
 e3e52d655c0f912a68b06b23cdf7b068c695a549 7588660 
civicrm_4.7.30+dfsg.orig-l10n.tar.xz
 98e70e07eafb50e6968cf7469a17e5ecd0e4aa6d 45496 
civicrm_4.7.30+dfsg.orig-wordpress.tar.xz
 b0cfa2ecbbb9d3a257ba8518d007fdcba31c88df 8713388 
civicrm_4.7.30+dfsg.orig.tar.xz
 f0eb1d7a26cd6434d03fdff73a97ac782651f6e9 40860 
civicrm_4.7.30+dfsg-1.debian.tar.xz
 f62d3934cb480480ff2c8ac1c34f866330c3e370 7402092 
civicrm-common_4.7.30+dfsg-1_all.deb
 d3800b9d00680aa48d978e76eb7ff979535fe3b4 8144908 
civicrm-l10n_4.7.30+dfsg-1_all.deb
 85a612301965dc68a9c08232fa6bda17a0a294f4 8806 
civicrm_4.7.30+dfsg-1_amd64.buildinfo
 7b97a1ece2cca45c2060bea3bac9bd2c30699124 729260 
wordpress-civicrm_4.7.30+dfsg-1_all.deb
Checksums-Sha256:
 3a267f087e7a55b626c04fa94b8813bf2af538bf45d68a9763e51cc4ad205285 3210 
civicrm_4.7.30+dfsg-1.dsc
 445494031608555c6c471cfea775517955764b69d4bc7da3b8ea048c069ebaf6 7588660 
civicrm_4.7.30+dfsg.orig-l10n.tar.xz
 3a96620ba57664c680101ae809288c51d08b5cf44702f8109c745cb709694527 45496 
civicrm_4.7.30+dfsg.orig-wordpress.tar.xz
 4d86ebc8b9f65362ce00bccdca94de52a2c012b63f50b01bce9f557b1a8c64e2 8713388 
civicrm_4.7.30+dfsg.orig.tar.xz
 93898ba5b7f64111df3113465598d608a628e8d91076863d4c47346565320f6f 40860 
civicrm_4.7.30+dfsg-1.debian.tar.xz
 06e78c174cd991aed9c32e191860637d40a1fbd4969e08a9a9103b7d3fd31b13 7402092 

Bug#893358: marked as done (jboss-threads FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Sun, 18 Mar 2018 22:22:54 +
with message-id 
and subject line Bug#893358: fixed in jboss-threads 2.3.1-2
has caused the Debian Bug report #893358,
regarding jboss-threads 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.)


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

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

...
[INFO] -
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/1st/jboss-threads-2.3.1/src/main/java/org/jboss/threads/EnhancedQueueExecutor.java:[56,16]
 cannot find symbol
  symbol:   class Contended
  location: package sun.misc
[ERROR] 
/build/1st/jboss-threads-2.3.1/src/main/java/org/jboss/threads/EnhancedQueueExecutor.java:[70,2]
 cannot find symbol
  symbol: class Contended
[ERROR] 
/build/1st/jboss-threads-2.3.1/src/main/java/org/jboss/threads/EnhancedQueueExecutor.java:[2040,6]
 cannot find symbol
  symbol:   class Contended
  location: class org.jboss.threads.EnhancedQueueExecutor
[ERROR] 
/build/1st/jboss-threads-2.3.1/src/main/java/org/jboss/threads/EnhancedQueueExecutor.java:[2121,6]
 cannot find symbol
  symbol:   class Contended
  location: class org.jboss.threads.EnhancedQueueExecutor
[ERROR] 
/build/1st/jboss-threads-2.3.1/src/main/java/org/jboss/threads/EnhancedQueueExecutor.java:[2065,6]
 cannot find symbol
  symbol:   class Contended
  location: class org.jboss.threads.EnhancedQueueExecutor
[ERROR] 
/build/1st/jboss-threads-2.3.1/src/main/java/org/jboss/threads/EnhancedQueueExecutor.java:[2097,6]
 cannot find symbol
  symbol:   class Contended
  location: class org.jboss.threads.EnhancedQueueExecutor
[INFO] 6 errors 
[INFO] -
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 53.231 s
[INFO] Finished at: 2018-03-17T08:36:14-12:00
[INFO] Final Memory: 15M/52M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile (default-compile) 
on project jboss-threads: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/jboss-threads-2.3.1/src/main/java/org/jboss/threads/EnhancedQueueExecutor.java:[56,16]
 cannot find symbol
[ERROR]   symbol:   class Contended
[ERROR]   location: package sun.misc
[ERROR] 
/build/1st/jboss-threads-2.3.1/src/main/java/org/jboss/threads/EnhancedQueueExecutor.java:[70,2]
 cannot find symbol
[ERROR]   symbol: class Contended
[ERROR] 
/build/1st/jboss-threads-2.3.1/src/main/java/org/jboss/threads/EnhancedQueueExecutor.java:[2040,6]
 cannot find symbol
[ERROR]   symbol:   class Contended
[ERROR]   location: class org.jboss.threads.EnhancedQueueExecutor
[ERROR] 
/build/1st/jboss-threads-2.3.1/src/main/java/org/jboss/threads/EnhancedQueueExecutor.java:[2121,6]
 cannot find symbol
[ERROR]   symbol:   class Contended
[ERROR]   location: class org.jboss.threads.EnhancedQueueExecutor
[ERROR] 
/build/1st/jboss-threads-2.3.1/src/main/java/org/jboss/threads/EnhancedQueueExecutor.java:[2065,6]
 cannot find symbol
[ERROR]   symbol:   class Contended
[ERROR]   location: class org.jboss.threads.EnhancedQueueExecutor
[ERROR] 
/build/1st/jboss-threads-2.3.1/src/main/java/org/jboss/threads/EnhancedQueueExecutor.java:[2097,6]
 cannot find symbol
[ERROR]   symbol:   class Contended
[ERROR]   location: class org.jboss.threads.EnhancedQueueExecutor
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/jboss-threads-2.3.1 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/jboss-threads-2.3.1/debian/maven.properties 

Bug#893426: Processed: Re: Processed: Re: Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

[Michael Biebl]

Control: tags -1 fixed-upstream patch
Control: forwarded -1 https://github.com/systemd/systemd/pull/8456

Fixed upstream by
https://github.com/systemd/systemd/commit/848e863acc51ecfb0f3955c498874588201d9130



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: severity of 893369 is important

[Debian Bug Tracking System]

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

> severity 893369 important
Bug #893369 [systemd] systemd-udevd is killed at startup
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.

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

Processed: Re: Processed: Re: Processed: Re: Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

[Debian Bug Tracking System]

Processing control commands:

> tags -1 fixed-upstream patch
Bug #893426 [systemd] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN
Added tag(s) fixed-upstream and patch.
> forwarded -1 https://github.com/systemd/systemd/pull/8456
Bug #893426 [systemd] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN
Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/pull/8456'.

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

Bug#893105: marked as done (clirr FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Sun, 18 Mar 2018 22:21:04 +
with message-id 
and subject line Bug#893105: fixed in clirr 0.6-6
has caused the Debian Bug report #893105,
regarding clirr 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.)


-- 
893105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893105
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: clirr
Version: 0.6-5
Severity: serious
Tags: buster sid

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

...
compile:
[mkdir] Created dir: /build/1st/clirr-0.6/build/generated-sources
[javac] /usr/share/maven-ant-helper/maven-build.xml:356: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.5 is no longer supported, switching to 1.6
[javac] Using javac -target 1.5 is no longer supported, switching to 1.6
[javac] Compiling 46 source files to /build/1st/clirr-0.6/build/classes
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/ant/AntLogger.java:3: error: 
unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] /build/1st/clirr-0.6/core/src/java/net/sf/clirr/ant/AntTask.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/ant/ChangeCounter.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/ant/PatternSetFilter.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] /build/1st/clirr-0.6/core/src/java/net/sf/clirr/cli/Clirr.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/ApiDifference.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/Checker.java:3: error: 
unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/CheckerException.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/ClassFilter.java:3: error: 
unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/ClassSelector.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/DiffListener.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/DiffListenerAdapter.java:3:
 error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/EventMessages.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 
/build/1st/clirr-0.6/core/src/java/net/sf/clirr/core/FileDiffListener.java:3: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] // Copyright (C) 2003 - 2005  Lars K?hne
[javac] ^
[javac] 

Bug#893369: systemd-udevd is killed at startup

[Michael Biebl]

Am 18.03.2018 um 22:41 schrieb LEDUQUE Mickaël:
> No I don't think I have one
> dpkg -l udev only shows udev and64

what about systemd? i386 or amd64


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Pending fixes for bugs in the clirr package

[Debian Bug Tracking System]

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

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

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

Bug#893105: Pending fixes for bugs in the clirr package

[pkg-java-maintainers]

tag 893105 + pending
thanks

Some bugs in the clirr package are closed in revision
0cf56abff475d627ca5da729a8c0c32e87afbf5d in branch 'master' by
Emmanuel Bourg

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

Commit message:

Build with maven-debian-helper instead of maven-ant-helper (Closes: #893105)

Processed: block testing migration while we think about this

[Debian Bug Tracking System]

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

> # feel free to revert if you disagree
> severity 893360 serious
Bug #893360 [python3-tornado] python3-tornado 5.0.0 breaks python3-zmq
Severity set to 'serious' from 'normal'
> affects 893360 python3-ipykernel jupyter-notebook jupyter-nbconvert
Bug #893360 [python3-tornado] python3-tornado 5.0.0 breaks python3-zmq
Added indication that 893360 affects python3-ipykernel, jupyter-notebook, and 
jupyter-nbconvert
>
End of message, stopping processing here.

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

Bug#893433: marked as done (libegl1-mesa-dev: File conflicts with libwayland-dev:amd64 1.14.91-1)

[Debian Bug Tracking System]

Your message dated Sun, 18 Mar 2018 22:43:11 +0100
with message-id <20180318214311.euphco43iyml2...@betterave.cristau.org>
and subject line Re: Bug#893433: libegl1-mesa-dev: File conflicts with 
libwayland-dev:amd64 1.14.91-1
has caused the Debian Bug report #893433,
regarding libegl1-mesa-dev: File conflicts with libwayland-dev:amd64 1.14.91-1
to be marked as done.

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

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


-- 
893433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893433
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libegl1-mesa-dev
Version: 18.0.0~rc4-1
Severity: serious
Justification: File conflicts

Hi! While trying to build qtwayland I ran across:

dpkg: error processing archive 
/tmp/apt-dpkg-install-VBKAMl/062-libegl1-mesa-dev_18.0.0~rc4-1_amd64.deb 
(--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which 
is also in package libwayland-dev:amd64 1.14.91-1

Admitedly I'm using a build against experimental using aspcud as dep resolver, 
as I need to build Qt in experimental, so maybe this is related.

Thanks, Lisandro.

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

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

Versions of packages libegl1-mesa-dev depends on:
ii  libdrm-dev2.4.91-1
ii  libglvnd-dev  1.0.0-2
pn  libwayland-dev
ii  libwayland-egl1-mesa  17.3.6-1
ii  libx11-dev2:1.6.4-3
ii  libx11-xcb-dev2:1.6.4-3
ii  libxcb-dri2-0-dev 1.13-1
ii  libxcb-dri3-dev   1.13-1
ii  libxcb-glx0-dev   1.13-1
ii  libxcb-present-dev1.13-1
ii  libxcb-sync-dev   1.13-1
ii  libxdamage-dev1:1.1.4-3
ii  libxext-dev   2:1.3.3-1+b2
ii  libxfixes-dev 1:5.0.3-1
ii  libxshmfence-dev  1.2-1+b2
ii  libxxf86vm-dev1:1.1.4-1+b2
ii  x11proto-dri2-dev 2.8-2
ii  x11proto-gl-dev   1.4.17-1

libegl1-mesa-dev recommends no packages.

libegl1-mesa-dev suggests no packages.
--- End Message ---
--- Begin Message ---
On Sun, Mar 18, 2018 at 16:51:48 -0300, Lisandro Damián Nicanor Pérez Meyer 
wrote:

> Package: libegl1-mesa-dev
> Version: 18.0.0~rc4-1
> Severity: serious
> Justification: File conflicts
> 
> Hi! While trying to build qtwayland I ran across:
> 
> dpkg: error processing archive 
> /tmp/apt-dpkg-install-VBKAMl/062-libegl1-mesa-dev_18.0.0~rc4-1_amd64.deb 
> (--unpack):
> trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', 
> which is also in package libwayland-dev:amd64 1.14.91-1
> 
> Admitedly I'm using a build against experimental using aspcud as dep 
> resolver, as I need to build Qt in experimental, so maybe this is related.
> 
This is a dupe of #893366.

Cheers,
Julien--- End Message ---

Bug#893369: systemd-udevd is killed at startup

[LEDUQUE Mickaël]

No I don't think I have one
dpkg -l udev only shows udev and64

2018-03-18 22:39 GMT+01:00 Michael Biebl :

> Am 18.03.2018 um 22:33 schrieb LEDUQUE Mickaël:
> > Looks like commenting out
> >
> > SystemCallArchitectures=native
> >
> > fixes  the issue.
>
> Does that mean you have a udev:i386 installed on a amd64 system?
>
>
>
> If so, that would basically be a duplicate of #869719
>
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
>

Processed: closing 893044

[Debian Bug Tracking System]

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

> close 893044 17.11.5-1
Bug #893044 [src:slurm-llnl] slurm-llnl: CVE-2018-7033: Issue in 
accounting_storage/mysql plugin by always escaping strings within the slurmdbd
Marked as fixed in versions slurm-llnl/17.11.5-1.
Bug #893044 [src:slurm-llnl] slurm-llnl: CVE-2018-7033: Issue in 
accounting_storage/mysql plugin by always escaping strings within the slurmdbd
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#893044: closing 893044

[Salvatore Bonaccorso]

close 893044 17.11.5-1
thanks

Bug#893369: systemd-udevd is killed at startup

[Michael Biebl]

Am 18.03.2018 um 22:33 schrieb LEDUQUE Mickaël:
> Looks like commenting out
> 
> SystemCallArchitectures=native
> 
> fixes  the issue.

Does that mean you have a udev:i386 installed on a amd64 system?



If so, that would basically be a duplicate of #869719


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#893426: Processed: Re: Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

[Michael Biebl]

Control: reassign -1 systemd
Control: found -1 238-1

It was correctly pointed out by Andreas Henriksson, that redefining
noreturn is probably not such a good idea, so let's reassign this back. 

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed: Re: Processed: Re: Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 systemd
Bug #893426 [libgpg-error-dev] systemd FTBFS: syntax error close to 
GPGRT_ATTR_NORETURN
Bug reassigned from package 'libgpg-error-dev' to 'systemd'.
No longer marked as found in versions libgpg-error/1.28-1.
Ignoring request to alter fixed versions of bug #893426 to the same values 
previously set
> found -1 238-1
Bug #893426 [systemd] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN
Marked as found in versions systemd/238-1.

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

Bug#893220: marked as done (jackson-dataformat-yaml FTBFS with libyaml-snake-java 1.20-1)

[Debian Bug Tracking System]

Your message dated Sun, 18 Mar 2018 21:34:24 +
with message-id 
and subject line Bug#893220: fixed in jackson-dataformat-yaml 2.8.10-3
has caused the Debian Bug report #893220,
regarding jackson-dataformat-yaml FTBFS with libyaml-snake-java 1.20-1
to be marked as done.

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

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


-- 
893220: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893220
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jackson-dataformat-yaml
Version: 2.8.10-2
Severity: serious

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/jackson-dataformat-yaml.html

...
[ERROR] COMPILATION ERROR : 
[INFO] -
[ERROR] 
/build/1st/jackson-dataformat-yaml-2.8.10/src/main/java/com/fasterxml/jackson/dataformat/yaml/YAMLGenerator.java:[423,40]
 incompatible types: java.lang.Boolean cannot be converted to 
org.yaml.snakeyaml.DumperOptions.FlowStyle
[ERROR] 
/build/1st/jackson-dataformat-yaml-2.8.10/src/main/java/com/fasterxml/jackson/dataformat/yaml/YAMLGenerator.java:[451,39]
 incompatible types: java.lang.Boolean cannot be converted to 
org.yaml.snakeyaml.DumperOptions.FlowStyle
[ERROR] 
/build/1st/jackson-dataformat-yaml-2.8.10/src/main/java/com/fasterxml/jackson/dataformat/yaml/YAMLGenerator.java:[768,29]
 incompatible types: java.lang.Character cannot be converted to 
org.yaml.snakeyaml.DumperOptions.ScalarStyle
[ERROR] 
/build/1st/jackson-dataformat-yaml-2.8.10/src/main/java/com/fasterxml/jackson/dataformat/yaml/snakeyaml/error/Mark.java:[44,23]
 cannot find symbol
  symbol:   method getIndex()
  location: variable _source of type org.yaml.snakeyaml.error.Mark
[INFO] 4 errors 
[INFO] -
[INFO] 
[INFO] 
[INFO] Skipping Jackson-dataformat-YAML
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 01:32 min
[INFO] Finished at: 2018-03-16T17:28:39-12:00
[INFO] Final Memory: 17M/60M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-compiler-plugin:3.6.2:compile (default-compile) 
on project jackson-dataformat-yaml: Compilation failure: Compilation failure: 
[ERROR] 
/build/1st/jackson-dataformat-yaml-2.8.10/src/main/java/com/fasterxml/jackson/dataformat/yaml/YAMLGenerator.java:[423,40]
 incompatible types: java.lang.Boolean cannot be converted to 
org.yaml.snakeyaml.DumperOptions.FlowStyle
[ERROR] 
/build/1st/jackson-dataformat-yaml-2.8.10/src/main/java/com/fasterxml/jackson/dataformat/yaml/YAMLGenerator.java:[451,39]
 incompatible types: java.lang.Boolean cannot be converted to 
org.yaml.snakeyaml.DumperOptions.FlowStyle
[ERROR] 
/build/1st/jackson-dataformat-yaml-2.8.10/src/main/java/com/fasterxml/jackson/dataformat/yaml/YAMLGenerator.java:[768,29]
 incompatible types: java.lang.Character cannot be converted to 
org.yaml.snakeyaml.DumperOptions.ScalarStyle
[ERROR] 
/build/1st/jackson-dataformat-yaml-2.8.10/src/main/java/com/fasterxml/jackson/dataformat/yaml/snakeyaml/error/Mark.java:[44,23]
 cannot find symbol
[ERROR]   symbol:   method getIndex()
[ERROR]   location: variable _source of type org.yaml.snakeyaml.error.Mark
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/build/1st/jackson-dataformat-yaml-2.8.10 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/build/1st/jackson-dataformat-yaml-2.8.10/debian/maven.properties
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/build/1st/jackson-dataformat-yaml-2.8.10/debian 

Bug#885117: tagged as pending

[Dmitry Smirnov]

tag 885117 pending
--

We believe that the bug #885117 you reported has been fixed in the Git
repository. You can see the commit message below and/or inspect the
commit contents at:

http://anonscm.debian.org/cgit/collab-maint/civicrm.git/diff/?id=1342d56

(This message was generated automatically by
 'git-post-receive-tag-pending-commitmsg' hook).
---
commit 1342d56
Author: Dmitry Smirnov 
Date:   Sun Mar 18 21:01:27 2018

No longer build "drupal7-mod-civicrm" package (Closes: #885117).

Bug#893369: systemd-udevd is killed at startup

[LEDUQUE Mickaël]

Looks like commenting out

SystemCallArchitectures=native

fixes  the issue.

2018-03-18 22:27 GMT+01:00 LEDUQUE Mickaël :

> I disabled them all and got a normal startup.
> Now I'll try to find the one (or more) that causes the problem.
> Thanks.
>
> 2018-03-18 21:48 GMT+01:00 Michael Biebl :
>
>> Am 18.03.2018 um 20:38 schrieb Mickaël Leduque:
>> > Package: systemd
>> > Version: 238-2
>> > Followup-For: Bug #893369
>> >
>> > It didn't work so I just added the options in /etc/default/grub.
>> > Here are the journal and the systemctl list-jobs output (which is just
>> "no jobs").
>> >
>>
>> Ok, thanks.
>> Once you are dropped into the rescue shell, can you try running
>> systemd-udevd manually, via
>> /lib/systemd/systemd-udevd
>>
>> If that works, you can try disabling the security features in
>> /lib/systemd/system/systemd-udevd.service
>> by commenting out the lines
>>
>> MemoryDenyWriteExecute=yes
>> RestrictRealtime=yes
>> RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
>> SystemCallArchitectures=native
>> LockPersonality=yes
>>
>> one by one and test if that makes a difference.
>>
>>
>> --
>> Why is it that all of the instruments seeking intelligent life in the
>> universe are pointed away from Earth?
>>
>>
>

Processed: Bug#885117 tagged as pending

[Debian Bug Tracking System]

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

> tag 885117 pending
Bug #885117 [drupal7-mod-civicrm] drupal7-mod-civicrm: Please stop building the 
drupal7-mod-civicrm binary package (dependency drupal7 to be removed)
Ignoring request to alter tags of bug #885117 to the same tags previously set
> --
Stopping processing here.

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

Bug#893369: systemd-udevd is killed at startup

[LEDUQUE Mickaël]

I disabled them all and got a normal startup.
Now I'll try to find the one (or more) that causes the problem.
Thanks.

2018-03-18 21:48 GMT+01:00 Michael Biebl :

> Am 18.03.2018 um 20:38 schrieb Mickaël Leduque:
> > Package: systemd
> > Version: 238-2
> > Followup-For: Bug #893369
> >
> > It didn't work so I just added the options in /etc/default/grub.
> > Here are the journal and the systemctl list-jobs output (which is just
> "no jobs").
> >
>
> Ok, thanks.
> Once you are dropped into the rescue shell, can you try running
> systemd-udevd manually, via
> /lib/systemd/systemd-udevd
>
> If that works, you can try disabling the security features in
> /lib/systemd/system/systemd-udevd.service
> by commenting out the lines
>
> MemoryDenyWriteExecute=yes
> RestrictRealtime=yes
> RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
> SystemCallArchitectures=native
> LockPersonality=yes
>
> one by one and test if that makes a difference.
>
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
>

Bug#893122: marked as done (cronometer FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Sun, 18 Mar 2018 21:19:43 +
with message-id 
and subject line Bug#893122: fixed in cronometer 0.9.9+dfsg-2
has caused the Debian Bug report #893122,
regarding cronometer 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.)


-- 
893122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cronometer
Version: 0.9.9+dfsg-1
Severity: serious
Tags: buster sid

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

...
compile:
[javac] /build/1st/cronometer-0.9.9+dfsg/build.xml:26: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.5 is no longer supported, switching to 1.6
[javac] Compiling 174 source files to /build/1st/cronometer-0.9.9+dfsg/bin
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] /build/1st/cronometer-0.9.9+dfsg/src/ca/spaz/util/XMLNode.java:157: 
error: unmappable character (0x93) for encoding US-ASCII
[javac]  else if (c == '?') sb.append("");
[javac] ^
[javac] /build/1st/cronometer-0.9.9+dfsg/src/ca/spaz/util/XMLNode.java:158: 
error: unmappable character (0x94) for encoding US-ASCII
[javac]  else if (c == '?') sb.append("");
[javac] ^
[javac] /build/1st/cronometer-0.9.9+dfsg/src/ca/spaz/util/XMLNode.java:159: 
error: unmappable character (0x91) for encoding US-ASCII
[javac]  else if (c == '?') sb.append("'");
[javac] ^
[javac] /build/1st/cronometer-0.9.9+dfsg/src/ca/spaz/util/XMLNode.java:160: 
error: unmappable character (0x92) for encoding US-ASCII
[javac]  else if (c == '?') sb.append("'"); 
[javac] ^
[javac] 4 errors
[javac] 3 warnings

BUILD FAILED
/build/1st/cronometer-0.9.9+dfsg/build.xml:26: Compile failed; see the compiler 
error output for details.

Total time: 34 seconds
dh_auto_build: ant -Duser.name debian returned exit code 1
make[1]: *** [debian/rules:16: override_dh_auto_build] Error 2
--- End Message ---
--- Begin Message ---
Source: cronometer
Source-Version: 0.9.9+dfsg-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Mar 2018 21:55:04 +0100
Source: cronometer
Binary: cronometer
Architecture: source
Version: 0.9.9+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Emmanuel Bourg 
Description:
 cronometer - CRON-o-Meter - Exercise and nutrient intake tracker
Closes: 893122
Changes:
 cronometer (0.9.9+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
   * Fixed the build failure with Java 9 (Closes: #893122)
   * Standards-Version updated to 4.1.3
   * Switch to debhelper level 11
   * Use secure Vcs-* URLs
Checksums-Sha1:
 93db64b30ddcd2d3ea275211a402f9fc5561b9cf 2110 cronometer_0.9.9+dfsg-2.dsc
 7881b6192d194d8247731ca85ed307e7b7752a53 9476 
cronometer_0.9.9+dfsg-2.debian.tar.xz
 e380c679fa75c2193bef04f4e0f482c8c74c81f8 6281 
cronometer_0.9.9+dfsg-2_source.buildinfo
Checksums-Sha256:
 df6ff65e7912703f7c36efbafa0e7fb71278de6a90c108d7a6e73cb6639b9b8a 2110 
cronometer_0.9.9+dfsg-2.dsc
 158de0a4cdfe184df67a71c3bdf2c1fd4e034e0e8b40b51c1be86c67b1bc62be 9476 
cronometer_0.9.9+dfsg-2.debian.tar.xz
 06be456bd2393aa68407ff9d8e9d346d9cd28acb9816f01fe390c1a26d178061 6281 
cronometer_0.9.9+dfsg-2_source.buildinfo

Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

[Michael Biebl]

Control: reassign -1 libgpg-error-dev
Control: found -1 1.28-1
Control: affects -1 + systemd

Am 18.03.2018 um 19:54 schrieb Helmut Grohne:
> Package: systemd
> Version: 238-2
> Severity: serious
> User: helm...@debian.org
> Usertags: rebootstrap
> 
> systemd fails to build from source on amd64. Here is a tail of the build
> log.
> 
> | FAILED: journal-core@sta/src_journal_journald-context.c.o 
> | cc  -Ijournal-core@sta -I. -I.. -I../ -Isrc/libsystemd-network 
> -I../src/libsystemd-network -I../src/libsystemd/sd-network 
> -I../src/libsystemd/sd-netlink -I../src/libsystemd/sd-id128 
> -I../src/libsystemd/sd-hwdb -I../src/libsystemd/sd-device 
> -I../src/libsystemd/sd-bus -Isrc/core -I../src/core -Isrc/libudev 
> -I../src/libudev -Isrc/udev -I../src/udev -Isrc/login -I../src/login 
> -Isrc/timesync -I../src/timesync -Isrc/resolve -I../src/resolve -Isrc/journal 
> -I../src/journal -Isrc/systemd -I../src/systemd -Isrc/shared -I../src/shared 
> -Isrc/basic -I../src/basic -flto -fdiagnostics-color=always -pipe 
> -D_FILE_OFFSET_BITS=64 -std=gnu99 -Wextra -Werror=undef -Wlogical-op 
> -Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self 
> -Wdeclaration-after-statement -Wfloat-equal -Wsuggest-attribute=noreturn 
> -Werror=missing-prototypes -Werror=implicit-function-declaration 
> -Werror=missing-declarations -Werror=return-type 
> -Werror=incompatible-pointer-types -Werror=format=2 -Wstrict-prototypes 
> -Wredundant-decls -Wmissing-noreturn -Wimplicit-fallthrough=5 -Wshadow 
> -Wendif-labels -Wstrict-aliasing=2 -Wwrite-strings -Werror=overflow 
> -Wdate-time -Wnested-externs -ffast-math -fno-common 
> -fdiagnostics-show-option -fno-strict-aliasing -fvisibility=hidden 
> -fstack-protector -fstack-protector-strong --param=ssp-buffer-size=4 -fPIE 
> -Wno-unused-parameter -Wno-missing-field-initializers -Wno-unused-result 
> -Wno-format-signedness -Wno-error=nonnull -Werror=shadow -ffunction-sections 
> -fdata-sections -include config.h -g -O2 
> -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ 
> 'journal-core@sta/src_journal_journald-context.c.o' -MF 
> 'journal-core@sta/src_journal_journald-context.c.o.d' -o 
> 'journal-core@sta/src_journal_journald-context.c.o' -c 
> ../src/journal/journald-context.c
> | In file included from ../src/basic/alloc-util.h:28:0,
> |  from ../src/journal/journald-context.c:25:
> | ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’
> |  #define noreturn __attribute__((noreturn))
> |   ^
> | In file included from /usr/include/gcrypt.h:30:0,
> |  from ../src/journal/journal-file.h:26,
> |  from ../src/journal/journald-server.h:31,
> |  from ../src/journal/journald-context.h:30,
> |  from ../src/journal/journald-context.c:33:
> | /usr/include/x86_64-linux-gnu/gpg-error.h:1545:46: error: expected ‘,’ or 
> ‘;’ before ‘)’ token
> |  void gpgrt_log_bug (const char *fmt, ...)GPGRT_ATTR_NR_PRINTF(1,2);
> |   ^
> | In file included from ../src/basic/alloc-util.h:28:0,
> |  from ../src/journal/journald-context.c:25:
> | ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’
> |  #define noreturn __attribute__((noreturn))
> |   ^
> | In file included from /usr/include/gcrypt.h:30:0,
> |  from ../src/journal/journal-file.h:26,
> |  from ../src/journal/journald-server.h:31,
> |  from ../src/journal/journald-context.h:30,
> |  from ../src/journal/journald-context.c:33:
> | /usr/include/x86_64-linux-gnu/gpg-error.h:1546:46: error: expected ‘,’ or 
> ‘;’ before ‘)’ token
> |  void gpgrt_log_fatal (const char *fmt, ...)  GPGRT_ATTR_NR_PRINTF(1,2);
> |   ^
> | In file included from ../src/basic/alloc-util.h:28:0,
> |  from ../src/journal/journald-context.c:25:
> | ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’
> |  #define noreturn __attribute__((noreturn))
> |   ^
> | In file included from /usr/include/gcrypt.h:30:0,
> |  from ../src/journal/journal-file.h:26,
> |  from ../src/journal/journald-server.h:31,
> |  from ../src/journal/journald-context.h:30,
> |  from ../src/journal/journald-context.c:33:
> | /usr/include/x86_64-linux-gnu/gpg-error.h:1558:43: error: expected ‘,’ or 
> ‘;’ before ‘)’ token
> |  const char *func) GPGRT_ATTR_NORETURN;
> |^
> | [231/1523] /usr/bin/python3 /usr/bin/meson --internal exe 
> /<>/build-deb/meson-private/meson_exe_awk_ec289b1578d245bbf1d8589a5ea437fc6525ccd3.dat
> | ninja: build stopped: subcommand failed.
> | dh_auto_build: cd build-deb && LC_ALL=C.UTF-8 ninja 

Processed: Re: Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 libgpg-error-dev
Bug #893426 [systemd] systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN
Bug reassigned from package 'systemd' to 'libgpg-error-dev'.
No longer marked as found in versions systemd/238-2.
Ignoring request to alter fixed versions of bug #893426 to the same values 
previously set
> found -1 1.28-1
Bug #893426 [libgpg-error-dev] systemd FTBFS: syntax error close to 
GPGRT_ATTR_NORETURN
Marked as found in versions libgpg-error/1.28-1.
> affects -1 + systemd
Bug #893426 [libgpg-error-dev] systemd FTBFS: syntax error close to 
GPGRT_ATTR_NORETURN
Added indication that 893426 affects systemd

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

Processed: Pending fixes for bugs in the cronometer package

[Debian Bug Tracking System]

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

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

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

Bug#893298: marked as done (libsbml FTBFS with openjdk-9)

[Debian Bug Tracking System]

Your message dated Sun, 18 Mar 2018 20:55:34 +
with message-id 
and subject line Bug#893298: fixed in libsbml 5.16.0+dfsg-2
has caused the Debian Bug report #893298,
regarding libsbml 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.)


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

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

...
CMake Error at docs/CMakeLists.txt:212 (message):
  Cannot generate java documentation, please specify the Java_JAVADOC_JAR.


-- Configuring incomplete, errors occurred!
See also "/build/1st/libsbml-5.16.0+dfsg/build/CMakeFiles/CMakeOutput.log".
See also "/build/1st/libsbml-5.16.0+dfsg/build/CMakeFiles/CMakeError.log".
make[1]: *** [debian/rules:62: override_dh_auto_configure] Error 1
--- End Message ---
--- Begin Message ---
Source: libsbml
Source-Version: 5.16.0+dfsg-2

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

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

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated libsbml package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 18 Mar 2018 19:49:01 +0100
Source: libsbml
Binary: libsbml5-dev libsbml5 libsbml5-python libsbml5-java libsbml5-perl 
libsbml5-octave libsbml5-cil libsbml5-examples libsbml5-doc libsbml5-cil-doc 
libsbml5-java-doc libsbml5-perl-doc libsbml5-python-doc
Architecture: source
Version: 5.16.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Andreas Tille 
Description:
 libsbml5   - System Biology Markup Language library
 libsbml5-cil - System Biology Markup Language library - CLI bindings
 libsbml5-cil-doc - System Biology Markup Language library -- CLI documentation
 libsbml5-dev - System Biology Markup Language library - development files
 libsbml5-doc - System Biology Markup Language library -- documentation
 libsbml5-examples - System Biology Markup Language library -- example files
 libsbml5-java - System Biology Markup Language library - Java bindings
 libsbml5-java-doc - System Biology Markup Language library -- Java 
documentation
 libsbml5-octave - System Biology Markup Language library - Octave bindings
 libsbml5-perl - System Biology Markup Language library - Perl bindings
 libsbml5-perl-doc - System Biology Markup Language library -- Perl 
documentation
 libsbml5-python - System Biology Markup Language library - Python bindings
 libsbml5-python-doc - System Biology Markup Language library -- Python 
documentation
Closes: 893298
Changes:
 libsbml (5.16.0+dfsg-2) unstable; urgency=medium
 .
   * Work around javadoc issue with Java 9
 Closes: #893298
Checksums-Sha1:
 c751dbb6e1a17f96583276b4d675c7e733e2c845 2982 libsbml_5.16.0+dfsg-2.dsc
 20a312688fd38e9684c510753930a83f11c68318 19656 
libsbml_5.16.0+dfsg-2.debian.tar.xz
 fedc23ee251fb2d63be2c75780dc659ac6a70d38 26916 
libsbml_5.16.0+dfsg-2_source.buildinfo
Checksums-Sha256:
 d17e02e62920a204c069ce55b50fb0019a9e3f4a512e85a5504b56abd1ff0613 2982 
libsbml_5.16.0+dfsg-2.dsc
 ca884695de473056263ca02178dc97b364c976b93742dba5803ef2a3d503f264 19656 
libsbml_5.16.0+dfsg-2.debian.tar.xz
 c3a98b61a8c74e3f8ec095963a181e29c299b57a24878152bfdcd90fcc43e7b7 26916 
libsbml_5.16.0+dfsg-2_source.buildinfo
Files:
 615167c1d42cc31e1e9d182969bbaff6 2982 science optional 
libsbml_5.16.0+dfsg-2.dsc
 e4b26f6eb88767c6d897a298cea24663 19656 science optional 
libsbml_5.16.0+dfsg-2.debian.tar.xz
 707478227c0d80aea32d2bc688bb0c1d 26916 science optional 
libsbml_5.16.0+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJCBAEBCAAsFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAlquy2AOHHRpbGxlYUBy
a2kuZGUACgkQV4oElNHGRtHlEQ/6A/0bqInRW7hNxta2ECpfqlTvWTKwn21XnGA5
1vej0l7ekWqJBVDZzxwFrkDH37wlzbj2LA32oOxKz2Aq9JHjnTfcYe/uN/3ncmJN

Bug#893122: Pending fixes for bugs in the cronometer package

[pkg-java-maintainers]

tag 893122 + pending
thanks

Some bugs in the cronometer package are closed in revision
db2620d0ca8afa07f8d1c68f5ef01f28f4ad57c2 in branch 'master' by
Emmanuel Bourg

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

Commit message:

Fixed the build failure with Java 9 (Closes: #893122)

Bug#893369: systemd-udevd is killed at startup

[Michael Biebl]

Am 18.03.2018 um 20:38 schrieb Mickaël Leduque:
> Package: systemd
> Version: 238-2
> Followup-For: Bug #893369
> 
> It didn't work so I just added the options in /etc/default/grub.
> Here are the journal and the systemctl list-jobs output (which is just "no 
> jobs").
> 

Ok, thanks.
Once you are dropped into the rescue shell, can you try running
systemd-udevd manually, via
/lib/systemd/systemd-udevd

If that works, you can try disabling the security features in
/lib/systemd/system/systemd-udevd.service
by commenting out the lines

MemoryDenyWriteExecute=yes
RestrictRealtime=yes
RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
SystemCallArchitectures=native
LockPersonality=yes

one by one and test if that makes a difference.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Processed (with 1 error): python-lesscpy

[Debian Bug Tracking System]

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

> retitle 893233 python-lesscpy: python3-lesscpy not working with python
Bug #893233 [src:python-lesscpy] ITA:python3-lesscpy not working with python 
3.5 or newer
Changed Bug title to 'python-lesscpy: python3-lesscpy not working with python' 
from 'ITA:python3-lesscpy not working with python 3.5 or newer'.
> 3.5 or newer
Unknown command or malformed arguments to command.
>
End of message, stopping processing here.

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

Bug#893442: lynkeos.app: FTBFS on ppc64el: AltiVec argument passed to unprototyped function

[Yavor Doganov]

Source: lynkeos.app
Version: 2.10+dfsg1-2
Severity: serious
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el

I would appreciate if someone knowledgeable from -powerpc confirms
that the attached patch is correct.  The build failure is:

gcc /<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m 
-c \
  -MMD -MP -Wdate-time -D_FORTIFY_SOURCE=2 -I. -I.. 
-I/<>/lynkeos.app-2.10+dfsg1/GNUstep.. 
-I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources 
-I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../ThreadConnectionSources 
-I/<>/lynkeos.app-2.10+dfsg1/GNUstep/../ThirdPartySources/SMDoubleSlider
 -DNO_FRAMEWORK_CHECK=1 -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 -DGNU_GUI_LIBRARY=1 
-DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 -fno-strict-aliasing -fexceptions 
-fobjc-exceptions -D_NATIVE_OBJC_EXCEPTIONS -pthread -fPIC -Wall -DGSWARN 
-DGSDIAGNOSE -Wno-import -g -O2 -g -O2 
-fdebug-prefix-map=/<>/lynkeos.app-2.10+dfsg1=. 
-fstack-protector-strong -Wformat -Werror=format-security -fgnu-runtime 
-Wno-unknown-pragmas -Wno-cpp -fconstant-string-class=NSConstantString -I. 
-I/usr/local/include/GNUstep -I/usr/include/GNUstep \
   -o obj/Lynkeos.obj/MyDeconvolution.m.o
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m: In 
function 'vector_Process_One_line':
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:72:44:
 warning: excess elements in vector initializer
0x04050607, 0x04050607 };
^~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:72:44:
 note: (near initialization for 'Vperma')
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:72:56:
 warning: excess elements in vector initializer
0x04050607, 0x04050607 };
^~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:72:56:
 note: (near initialization for 'Vperma')
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:74:44:
 warning: excess elements in vector initializer
0x0C0D0E0F, 0x0C0D0E0F };
^~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:74:44:
 note: (near initialization for 'Vpermb')
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:74:56:
 warning: excess elements in vector initializer
0x0C0D0E0F, 0x0C0D0E0F };
^~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:74:56:
 note: (near initialization for 'Vpermb')
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:88:13:
 warning: implicit declaration of function 'vec_madd' 
[-Wimplicit-function-declaration]
   Vdx = vec_madd( vec_ld(0,expXptr), Vdy, Vzero );
 ^~~~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:88:23:
 warning: implicit declaration of function 'vec_ld'; did you mean 'vector'? 
[-Wimplicit-function-declaration]
   Vdx = vec_madd( vec_ld(0,expXptr), Vdy, Vzero );
   ^~
   vector
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:88:7: 
error: AltiVec argument passed to unprototyped function
   Vdx = vec_madd( vec_ld(0,expXptr), Vdy, Vzero );
   ^~~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:89:41:
 warning: implicit declaration of function 'vec_cmplt' 
[-Wimplicit-function-declaration]
   const __vector __bool int Vmask = vec_cmplt(Vdx,Vthr);
 ^
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:89:7: 
error: AltiVec argument passed to unprototyped function
   const __vector __bool int Vmask = vec_cmplt(Vdx,Vthr);
   ^
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:90:27:
 warning: implicit declaration of function 'vec_and'; did you mean 'vscanf'? 
[-Wimplicit-function-declaration]
   __vector REAL Vge = vec_and(Vdx,Vmask);
   ^~~
   vscanf
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:90:7: 
error: AltiVec argument passed to unprototyped function
   __vector REAL Vge = vec_and(Vdx,Vmask);
   ^~~~
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:91:27:
 warning: implicit declaration of function 'vec_andc'; did you mean 'vscanf'? 
[-Wimplicit-function-declaration]
   __vector REAL Vlt = vec_andc(Vthr,Vmask);
   ^~~~
   vscanf
/<>/lynkeos.app-2.10+dfsg1/GNUstep/../Sources/MyDeconvolution.m:91:7: 
error: AltiVec argument passed to unprototyped function
   __vector REAL Vlt = vec_andc(Vthr,Vmask);
   ^~~~

Bug#891407: httping: diff for NMU version 2.5-1.1

[Adrian Bunk]

Control: tags 891407 + patch
Control: tags 891407 + pending

Dear maintainer,

I've prepared an NMU for httping (versioned as 2.5-1.1) and uploaded
it to DELAYED/14. Please feel free to tell me if I should cancel it.

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

diff -Nru httping-2.5/debian/changelog httping-2.5/debian/changelog
--- httping-2.5/debian/changelog	2016-09-12 18:34:13.0 +0300
+++ httping-2.5/debian/changelog	2018-03-18 22:14:33.0 +0200
@@ -1,3 +1,10 @@
+httping (2.5-1.1) unstable; urgency=low
+
+  * Non-maintainer upload.
+  * Build-depend on clang-tools. (Closes: #891407)
+
+ -- Adrian Bunk   Sun, 18 Mar 2018 22:14:33 +0200
+
 httping (2.5-1) unstable; urgency=low
 
   * New upstream release
diff -Nru httping-2.5/debian/control httping-2.5/debian/control
--- httping-2.5/debian/control	2016-09-12 18:34:13.0 +0300
+++ httping-2.5/debian/control	2018-03-18 22:14:33.0 +0200
@@ -5,6 +5,7 @@
 Build-Depends: debhelper (>= 9), 
libssl-dev, 
clang, 
+   clang-tools,
libncursesw5-dev, 
libncurses5-dev, 
libfftw3-dev,

Processed: httping: diff for NMU version 2.5-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 891407 + patch
Bug #891407 [src:httping] httping: needs B-D: clang-tools
Added tag(s) patch.
> tags 891407 + pending
Bug #891407 [src:httping] httping: needs B-D: clang-tools
Added tag(s) pending.

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

Bug#893436: jupyter-notebook: CVE-2018-8768

[Salvatore Bonaccorso]

Source: jupyter-notebook
Version: 4.2.3-4
Severity: grave
Tags: patch security upstream

Hi,

the following vulnerability was published for jupyter-notebook.

CVE-2018-8768[0]:
| In Jupyter Notebook before 5.4.1, a maliciously forged notebook file
| can bypass sanitization to execute JavaScript in the notebook context.
| Specifically, invalid HTML is 'fixed' by jQuery after sanitization,
| making it dangerous.

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2018-8768
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-8768
[1] http://www.openwall.com/lists/oss-security/2018/03/15/2
[2] 
https://github.com/jupyter/notebook/commit/4e79ebb49acac722b37b03f1fe811e67590d3831

Regards,
Salvatore

Bug#893433: libegl1-mesa-dev: File conflicts with libwayland-dev:amd64 1.14.91-1

[Lisandro Damián Nicanor Pérez Meyer]

Package: libegl1-mesa-dev
Version: 18.0.0~rc4-1
Severity: serious
Justification: File conflicts

Hi! While trying to build qtwayland I ran across:

dpkg: error processing archive 
/tmp/apt-dpkg-install-VBKAMl/062-libegl1-mesa-dev_18.0.0~rc4-1_amd64.deb 
(--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/pkgconfig/wayland-egl.pc', which 
is also in package libwayland-dev:amd64 1.14.91-1

Admitedly I'm using a build against experimental using aspcud as dep resolver, 
as I need to build Qt in experimental, so maybe this is related.

Thanks, Lisandro.

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

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

Versions of packages libegl1-mesa-dev depends on:
ii  libdrm-dev2.4.91-1
ii  libglvnd-dev  1.0.0-2
pn  libwayland-dev
ii  libwayland-egl1-mesa  17.3.6-1
ii  libx11-dev2:1.6.4-3
ii  libx11-xcb-dev2:1.6.4-3
ii  libxcb-dri2-0-dev 1.13-1
ii  libxcb-dri3-dev   1.13-1
ii  libxcb-glx0-dev   1.13-1
ii  libxcb-present-dev1.13-1
ii  libxcb-sync-dev   1.13-1
ii  libxdamage-dev1:1.1.4-3
ii  libxext-dev   2:1.3.3-1+b2
ii  libxfixes-dev 1:5.0.3-1
ii  libxshmfence-dev  1.2-1+b2
ii  libxxf86vm-dev1:1.1.4-1+b2
ii  x11proto-dri2-dev 2.8-2
ii  x11proto-gl-dev   1.4.17-1

libegl1-mesa-dev recommends no packages.

libegl1-mesa-dev suggests no packages.

Bug#893369: systemd-udevd is killed at startup

[Mickaël Leduque]

Package: systemd
Version: 238-2
Followup-For: Bug #893369

It didn't work so I just added the options in /etc/default/grub.
Here are the journal and the systemctl list-jobs output (which is just "no 
jobs").

-- Package-specific info:

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

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

Versions of packages systemd depends on:
ii  adduser  3.117
ii  libacl1  2.2.52-3+b1
ii  libapparmor1 2.12-3
ii  libaudit11:2.8.2-1
ii  libblkid12.31.1-0.5
ii  libc62.27-2
ii  libcap2  1:2.25-1.2
ii  libcryptsetup12  2:2.0.2-1
ii  libgcrypt20  1.8.1-4
ii  libgpg-error01.28-1
ii  libidn11 1.33-2.1
ii  libip4tc01.6.2-1
ii  libkmod2 25-1
ii  liblz4-1 0.0~r131-2+b1
ii  liblzma5 5.2.2-1.3
ii  libmount12.31.1-0.5
ii  libpam0g 1.1.8-3.7
ii  libseccomp2  2.3.1-2.1
ii  libselinux1  2.7-2+b1
ii  libsystemd0  238-2
ii  mount2.31.1-0.5
ii  procps   2:3.3.12-4
ii  util-linux   2.31.1-0.5

Versions of packages systemd recommends:
ii  dbus1.12.6-2
ii  libpam-systemd  238-2

Versions of packages systemd suggests:
ii  policykit-10.113-2
pn  systemd-container  

Versions of packages systemd is related to:
pn  dracut   
ii  initramfs-tools  0.130
ii  udev 238-2

-- no debconf information
-- Logs begin at Fri 2017-10-06 17:03:19 CEST, end at Sun 2018-03-18 20:32:15 
CET. --
mars 18 20:30:14 falkynkip kernel: microcode: microcode updated early to 
revision 0x1f, date = 2018-02-07
mars 18 20:30:14 falkynkip kernel: Linux version 4.15.0-1-amd64 
(debian-ker...@lists.debian.org) (gcc version 7.3.0 (Debian 7.3.0-3)) #1 SMP 
Debian 4.15.4-1 (2018-02-18)
mars 18 20:30:14 falkynkip kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-4.15.0-1-amd64 
root=UUID=5fe70463-3aae-4be3-ac38-9a92ac404edb ro quiet 
init=/lib/systemd/systemd
mars 18 20:30:14 falkynkip kernel: x86/fpu: Supporting XSAVE feature 0x001: 
'x87 floating point registers'
mars 18 20:30:14 falkynkip kernel: x86/fpu: Supporting XSAVE feature 0x002: 
'SSE registers'
mars 18 20:30:14 falkynkip kernel: x86/fpu: Supporting XSAVE feature 0x004: 
'AVX registers'
mars 18 20:30:14 falkynkip kernel: x86/fpu: xstate_offset[2]:  576, 
xstate_sizes[2]:  256
mars 18 20:30:14 falkynkip kernel: x86/fpu: Enabled xstate features 0x7, 
context size is 832 bytes, using 'standard' format.
mars 18 20:30:14 falkynkip kernel: e820: BIOS-provided physical RAM map:
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0x-0x0009d7ff] usable
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0x0009d800-0x0009] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0x000e-0x000f] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0x0010-0x1fff] usable
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0x2000-0x201f] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0x2020-0x40003fff] usable
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0x40004000-0x40004fff] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0x40005000-0xcced8fff] usable
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xcced9000-0xcd7fafff] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xcd7fb000-0xcd884fff] usable
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xcd885000-0xcd923fff] ACPI NVS
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xcd924000-0xce163fff] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xce164000-0xce164fff] usable
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xce165000-0xce1a7fff] ACPI NVS
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xce1a8000-0xcebfbfff] usable
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xcebfc000-0xceff1fff] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xceff2000-0xceff] usable
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xcf80-0xdf9f] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xf800-0xfbff] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xfec0-0xfec00fff] reserved
mars 18 20:30:14 falkynkip kernel: BIOS-e820: [mem 
0xfed0-0xfed03fff] reserved
mars 18 20:30:14 falkynkip kernel: 

Bug#893409: pixelmed FTBFS with openjdk-9

[Andreas Tille]

Control: tags -1 help

On Sun, Mar 18, 2018 at 07:54:32PM +0200, Adrian Bunk wrote:
> Source: pixelmed
> Version: 20150917-2
> Severity: serious
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/pixelmed.html
> 
> ...
> ../../../../com/pixelmed/display/SourceImage.java:1626: error: cannot find 
> symbol
>   sun.misc.Cleaner cleaner = 
> (sun.misc.Cleaner)getCleanerMethod.invoke(object,new Object[0]);
>   ^
>   symbol:   class Cleaner
>   location: package sun.misc
> ../../../../com/pixelmed/display/SourceImage.java:1626: error: cannot find 
> symbol
>   sun.misc.Cleaner cleaner = 
> (sun.misc.Cleaner)getCleanerMethod.invoke(object,new Object[0]);
>   
> ^
>   symbol:   class Cleaner
>   location: package sun.misc

Unfortunately I have no idea how to fix this.  Any hint?

Kind regards

   Andreas. 

-- 
http://fam-tille.de

Processed: Re: Bug#893409: pixelmed FTBFS with openjdk-9

[Debian Bug Tracking System]

Processing control commands:

> tags -1 help
Bug #893409 [src:pixelmed] pixelmed FTBFS with openjdk-9
Added tag(s) help.

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

Bug#893367: marked as done ("smtpctl stop" not supported by upstream anymore)

[Debian Bug Tracking System]

Your message dated Sun, 18 Mar 2018 19:05:23 +
with message-id 
and subject line Bug#893367: fixed in opensmtpd 6.0.3p1-2
has caused the Debian Bug report #893367,
regarding "smtpctl stop" not supported by upstream anymore
to be marked as done.

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

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


-- 
893367: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893367
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: opensmtpd
Version: 6.0.3p1-1
Severity: serious

"smtpctl stop" is not supported by upstream anymore. This affects
debian/opensmtpd.service. opensmtpd doesn't go away, and the
restart fails (e.g. at a package upgrade). Serious problem.

The proper way to stop a daemon on Unix is to send it a SIGTERM.


Regards
Harri



signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: opensmtpd
Source-Version: 6.0.3p1-2

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Mar 2018 13:53:00 -0400
Source: opensmtpd
Binary: opensmtpd
Architecture: source amd64
Version: 6.0.3p1-2
Distribution: unstable
Urgency: medium
Maintainer: Ryan Kavanagh 
Changed-By: Ryan Kavanagh 
Description:
 opensmtpd  - secure, reliable, lean, and easy-to configure SMTP server
Closes: 859544 888290 893367
Changes:
 opensmtpd (6.0.3p1-2) unstable; urgency=medium
 .
   * Fix the stop target in the systemd service (Closes: #893367)
   * Update Vcs-* fields to point to salsa
   * Enable OpenSSL 1.1 support, 11_ssl_1.1.diff (Closes: #859544)
 Thanks to Sebastian Andrzej Siewior for the patch.
   * Conflict with sendmail-base: provides various commands such as
 "newaliases" that could cause confusion with our own commands
 (Closes: #888290)
Checksums-Sha1:
 e8c03524f02fad995200bcf8cfa96fc7252f3c82 3050 opensmtpd_6.0.3p1-2.dsc
 e633e1ea3723f57b26d1d1184c59d93368171cd6 29344 
opensmtpd_6.0.3p1-2.debian.tar.xz
 979cc34281e1c947b3e3aa7552bbaa6c2874ba7b 1047984 
opensmtpd-dbgsym_6.0.3p1-2_amd64.deb
 e9281a438a6b4d7567f2168c28c1d687f0184761 7406 
opensmtpd_6.0.3p1-2_amd64.buildinfo
 28af29d3f2a2dafdd32675e3f2cae3e29e959ca4 260120 opensmtpd_6.0.3p1-2_amd64.deb
Checksums-Sha256:
 5085a7b19202cf936198545d74caeccc326d6aff7daea4e2151aa8adbd0b05e2 3050 
opensmtpd_6.0.3p1-2.dsc
 14d0e84a121d1fee6b757d7c56267a74f694c62af7cef29c8cee112c6e8d643b 29344 
opensmtpd_6.0.3p1-2.debian.tar.xz
 68863b215b269a874169e426f24968d3f3c6a2e82ab9fa0afedfab526455890b 1047984 
opensmtpd-dbgsym_6.0.3p1-2_amd64.deb
 827a4a73405c7259fb7f38055ddbd1a2397933a48b991d26ac61da68c7c8b7fc 7406 
opensmtpd_6.0.3p1-2_amd64.buildinfo
 5a813605178d3e99fe8ad43a1d416447dc8ed955a8b95a2588eb97dba950f05f 260120 
opensmtpd_6.0.3p1-2_amd64.deb
Files:
 d19f28d84ba4f790b0a488030053400f 3050 mail optional opensmtpd_6.0.3p1-2.dsc
 4bc973bf8ebc6ea6e617cb05be32571b 29344 mail optional 
opensmtpd_6.0.3p1-2.debian.tar.xz
 26b2295cfdc561e3d3b8b8d7730e87c4 1047984 debug optional 
opensmtpd-dbgsym_6.0.3p1-2_amd64.deb
 9c4cef84c7a29406b2a10070338a001e 7406 mail optional 
opensmtpd_6.0.3p1-2_amd64.buildinfo
 f3667bff4c7715fed7e65f0728c2417d 260120 mail optional 
opensmtpd_6.0.3p1-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQVDBAEBCgAtFiEETkaVGe1ndzQmj72Vj3v4/EoRyXoFAlqusqUPHHJha0BkZWJp
YW4ub3JnAAoJEI97+PxKEcl6bGQoAKj2DP9ibbGn/ydPCRQy+mR+GSRIZWyGy2/6
WWOCxE91CVaCFrt4YoDOWL/AYzIKvo+j5BlbSkZ/e8iRBvdxJvYuRQrZ8yxUWATw
Wsstdxk0JvOD2j17kfm3qG4Tlaf5m8JcCddKAx9m0mw/c44ocLHJGeoleoOs67ic
dVvgS5K1lwBFu2IEtDBI9g0X1j4SjQYn7DXRNcQzffxQkwgQA+pDAKU+eCZk+8Tf
G5CUaE39jRtdewBoivXTuHB3QWqaILTukC25vY/zKCsN3KJkBQQTO/S+HM5jfbsp
78yhgdePmCJdz3womLdEuWscpaUkNRh5fB989ZYxGlFspP+aNBRSyoWdQJCzXaOR
p5c3CtJ05QOuwNm7urLA1PE3YX+Wmj6ROmxjs1r/YzoMWPx4lhItstFUOqaoDQmw
oqrqn23LooFw5CucBAdonSLRgOnYa28PIChWC+5hRfUuhSieIrA2/sU7jMUXt1MA

Bug#859544: marked as done (opensmtpd: Please migrate to openssl1.1 in buster)

[Debian Bug Tracking System]

Your message dated Sun, 18 Mar 2018 19:05:23 +
with message-id 
and subject line Bug#859544: fixed in opensmtpd 6.0.3p1-2
has caused the Debian Bug report #859544,
regarding opensmtpd: Please migrate to openssl1.1 in buster
to be marked as done.

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

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


-- 
859544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859544
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opensmtpd
Version: 5.7.3p2-1
Severity: important
Control: block 827061 by -1

Hi,

OpenSSL 1.1.0 is about to released.  During a rebuild of all packages using
OpenSSL this package fail to build.  A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/opensmtpd_5.7.3p2-1_amd64-20160529-1501

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

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

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


Kurt
--- End Message ---
--- Begin Message ---
Source: opensmtpd
Source-Version: 6.0.3p1-2

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

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

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

Debian distribution maintenance software
pp.
Ryan Kavanagh  (supplier of updated opensmtpd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Mar 2018 13:53:00 -0400
Source: opensmtpd
Binary: opensmtpd
Architecture: source amd64
Version: 6.0.3p1-2
Distribution: unstable
Urgency: medium
Maintainer: Ryan Kavanagh 
Changed-By: Ryan Kavanagh 
Description:
 opensmtpd  - secure, reliable, lean, and easy-to configure SMTP server
Closes: 859544 888290 893367
Changes:
 opensmtpd (6.0.3p1-2) unstable; urgency=medium
 .
   * Fix the stop target in the systemd service (Closes: #893367)
   * Update Vcs-* fields to point to salsa
   * Enable OpenSSL 1.1 support, 11_ssl_1.1.diff (Closes: #859544)
 Thanks to Sebastian Andrzej Siewior for the patch.
   * Conflict with sendmail-base: provides various commands such as
 "newaliases" that could cause confusion with our own commands
 (Closes: #888290)
Checksums-Sha1:
 e8c03524f02fad995200bcf8cfa96fc7252f3c82 3050 opensmtpd_6.0.3p1-2.dsc
 e633e1ea3723f57b26d1d1184c59d93368171cd6 29344 
opensmtpd_6.0.3p1-2.debian.tar.xz
 979cc34281e1c947b3e3aa7552bbaa6c2874ba7b 1047984 
opensmtpd-dbgsym_6.0.3p1-2_amd64.deb
 e9281a438a6b4d7567f2168c28c1d687f0184761 7406 
opensmtpd_6.0.3p1-2_amd64.buildinfo
 28af29d3f2a2dafdd32675e3f2cae3e29e959ca4 260120 opensmtpd_6.0.3p1-2_amd64.deb
Checksums-Sha256:
 5085a7b19202cf936198545d74caeccc326d6aff7daea4e2151aa8adbd0b05e2 3050 
opensmtpd_6.0.3p1-2.dsc
 14d0e84a121d1fee6b757d7c56267a74f694c62af7cef29c8cee112c6e8d643b 29344 
opensmtpd_6.0.3p1-2.debian.tar.xz
 68863b215b269a874169e426f24968d3f3c6a2e82ab9fa0afedfab526455890b 1047984 
opensmtpd-dbgsym_6.0.3p1-2_amd64.deb
 827a4a73405c7259fb7f38055ddbd1a2397933a48b991d26ac61da68c7c8b7fc 7406 
opensmtpd_6.0.3p1-2_amd64.buildinfo
 5a813605178d3e99fe8ad43a1d416447dc8ed955a8b95a2588eb97dba950f05f 260120 
opensmtpd_6.0.3p1-2_amd64.deb
Files:
 d19f28d84ba4f790b0a488030053400f 3050 mail optional opensmtpd_6.0.3p1-2.dsc
 4bc973bf8ebc6ea6e617cb05be32571b 29344 mail optional 
opensmtpd_6.0.3p1-2.debian.tar.xz
 26b2295cfdc561e3d3b8b8d7730e87c4 1047984 debug optional 
opensmtpd-dbgsym_6.0.3p1-2_amd64.deb
 9c4cef84c7a29406b2a10070338a001e 7406 mail optional 
opensmtpd_6.0.3p1-2_amd64.buildinfo
 f3667bff4c7715fed7e65f0728c2417d 260120 mail optional 
opensmtpd_6.0.3p1-2_amd64.deb

-BEGIN PGP SIGNATURE-

iQVDBAEBCgAtFiEETkaVGe1ndzQmj72Vj3v4/EoRyXoFAlqusqUPHHJha0BkZWJp
YW4ub3JnAAoJEI97+PxKEcl6bGQoAKj2DP9ibbGn/ydPCRQy+mR+GSRIZWyGy2/6
WWOCxE91CVaCFrt4YoDOWL/AYzIKvo+j5BlbSkZ/e8iRBvdxJvYuRQrZ8yxUWATw

Bug#893426: systemd FTBFS: syntax error close to GPGRT_ATTR_NORETURN

[Helmut Grohne]

Package: systemd
Version: 238-2
Severity: serious
User: helm...@debian.org
Usertags: rebootstrap

systemd fails to build from source on amd64. Here is a tail of the build
log.

| FAILED: journal-core@sta/src_journal_journald-context.c.o 
| cc  -Ijournal-core@sta -I. -I.. -I../ -Isrc/libsystemd-network 
-I../src/libsystemd-network -I../src/libsystemd/sd-network 
-I../src/libsystemd/sd-netlink -I../src/libsystemd/sd-id128 
-I../src/libsystemd/sd-hwdb -I../src/libsystemd/sd-device 
-I../src/libsystemd/sd-bus -Isrc/core -I../src/core -Isrc/libudev 
-I../src/libudev -Isrc/udev -I../src/udev -Isrc/login -I../src/login 
-Isrc/timesync -I../src/timesync -Isrc/resolve -I../src/resolve -Isrc/journal 
-I../src/journal -Isrc/systemd -I../src/systemd -Isrc/shared -I../src/shared 
-Isrc/basic -I../src/basic -flto -fdiagnostics-color=always -pipe 
-D_FILE_OFFSET_BITS=64 -std=gnu99 -Wextra -Werror=undef -Wlogical-op 
-Wmissing-include-dirs -Wold-style-definition -Wpointer-arith -Winit-self 
-Wdeclaration-after-statement -Wfloat-equal -Wsuggest-attribute=noreturn 
-Werror=missing-prototypes -Werror=implicit-function-declaration 
-Werror=missing-declarations -Werror=return-type 
-Werror=incompatible-pointer-types -Werror=format=2 -Wstrict-prototypes 
-Wredundant-decls -Wmissing-noreturn -Wimplicit-fallthrough=5 -Wshadow 
-Wendif-labels -Wstrict-aliasing=2 -Wwrite-strings -Werror=overflow -Wdate-time 
-Wnested-externs -ffast-math -fno-common -fdiagnostics-show-option 
-fno-strict-aliasing -fvisibility=hidden -fstack-protector 
-fstack-protector-strong --param=ssp-buffer-size=4 -fPIE -Wno-unused-parameter 
-Wno-missing-field-initializers -Wno-unused-result -Wno-format-signedness 
-Wno-error=nonnull -Werror=shadow -ffunction-sections -fdata-sections -include 
config.h -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong 
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ 
'journal-core@sta/src_journal_journald-context.c.o' -MF 
'journal-core@sta/src_journal_journald-context.c.o.d' -o 
'journal-core@sta/src_journal_journald-context.c.o' -c 
../src/journal/journald-context.c
| In file included from ../src/basic/alloc-util.h:28:0,
|  from ../src/journal/journald-context.c:25:
| ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’
|  #define noreturn __attribute__((noreturn))
|   ^
| In file included from /usr/include/gcrypt.h:30:0,
|  from ../src/journal/journal-file.h:26,
|  from ../src/journal/journald-server.h:31,
|  from ../src/journal/journald-context.h:30,
|  from ../src/journal/journald-context.c:33:
| /usr/include/x86_64-linux-gnu/gpg-error.h:1545:46: error: expected ‘,’ or ‘;’ 
before ‘)’ token
|  void gpgrt_log_bug (const char *fmt, ...)GPGRT_ATTR_NR_PRINTF(1,2);
|   ^
| In file included from ../src/basic/alloc-util.h:28:0,
|  from ../src/journal/journald-context.c:25:
| ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’
|  #define noreturn __attribute__((noreturn))
|   ^
| In file included from /usr/include/gcrypt.h:30:0,
|  from ../src/journal/journal-file.h:26,
|  from ../src/journal/journald-server.h:31,
|  from ../src/journal/journald-context.h:30,
|  from ../src/journal/journald-context.c:33:
| /usr/include/x86_64-linux-gnu/gpg-error.h:1546:46: error: expected ‘,’ or ‘;’ 
before ‘)’ token
|  void gpgrt_log_fatal (const char *fmt, ...)  GPGRT_ATTR_NR_PRINTF(1,2);
|   ^
| In file included from ../src/basic/alloc-util.h:28:0,
|  from ../src/journal/journald-context.c:25:
| ../src/basic/macro.h:423:18: error: expected ‘)’ before ‘__attribute__’
|  #define noreturn __attribute__((noreturn))
|   ^
| In file included from /usr/include/gcrypt.h:30:0,
|  from ../src/journal/journal-file.h:26,
|  from ../src/journal/journald-server.h:31,
|  from ../src/journal/journald-context.h:30,
|  from ../src/journal/journald-context.c:33:
| /usr/include/x86_64-linux-gnu/gpg-error.h:1558:43: error: expected ‘,’ or ‘;’ 
before ‘)’ token
|  const char *func) GPGRT_ATTR_NORETURN;
|^
| [231/1523] /usr/bin/python3 /usr/bin/meson --internal exe 
/<>/build-deb/meson-private/meson_exe_awk_ec289b1578d245bbf1d8589a5ea437fc6525ccd3.dat
| ninja: build stopped: subcommand failed.
| dh_auto_build: cd build-deb && LC_ALL=C.UTF-8 ninja -j8 -v returned exit code 
1
| make[1]: *** [debian/rules:161: override_dh_auto_build] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:294: binary-arch] Error 2
| dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

This issue might be related to the 

Bug#893427: tunnelx FTBFS with openjdk-9

[Adrian Bunk]

Source: tunnelx
Version: 20170928-1
Severity: serious

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

...
jh_build
find src -name *.java -and -type f -print0 | xargs -s 512000 -0 
/usr/lib/jvm/default-java/bin/javac -g -cp :debian/_jh_build.tunnelx -d 
debian/_jh_build.tunnelx -source 1.7 -target 1.7 -encoding ISO8859-1
warning: [options] bootstrap class path not set in conjunction with -source 1.7
src/SelectedSubsetsStructure.java:260: error: incompatible types: 
Enumeration cannot be converted to Enumeration
Enumeration 
tnenum = tn.depthFirstEnumeration(); 

 ^
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
1 warning
make[1]: *** [debian/rules:21: override_jh_build] Error 123

Bug#893425: nordugrid-arc FTBFS with openjdk-9

[Adrian Bunk]

Source: nordugrid-arc
Version: 5.4.2-1
Severity: serious

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

...
/usr/lib/jvm/java-1.9.0-openjdk-amd64/bin/javac -J-Xms50M -J-Xmx50M -source 1.5 
-target 1.5 -cp . nordugrid/arc/arc.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[4]: *** [Makefile:1110: nordugrid/arc/arc.class] Error 2

Bug#893423: thepeg FTBFS with openjdk-9

[Adrian Bunk]

Source: thepeg
Version: 1.8.0-3
Severity: serious

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

...
checking for javac... /usr/bin/javac
checking for java... /usr/bin/java
checking for jar... /usr/bin/jar
checking if java works... no
configure: Java GUI disabled
...
   debian/rules override_dh_install-indep
make[1]: Entering directory '/build/1st/thepeg-1.8.0'
dh_install
dh_install: Cannot find (any matches for) "usr/bin/thepeg" (tried in ., 
debian/tmp)

dh_install: thepeg-gui missing files: usr/bin/thepeg
dh_install: Cannot find (any matches for) "usr/lib/*/ThePEG/ThePEG.jar" (tried 
in ., debian/tmp)

dh_install: thepeg-gui missing files: usr/lib/*/ThePEG/ThePEG.jar
dh_install: missing files, aborting
make[1]: *** [debian/rules:38: override_dh_install-indep] Error 25

Bug#893424: Cannot uninstall package

[Ryan Kavanagh]

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 
ii  logrotate3.11.0-0.1
pn  resolvconf   
pn  sendmail-doc 

-- no debconf information

-- 
|)|/  Ryan Kavanagh  | GPG: 4E46 9519 ED67 7734 268F
|\|\  https://rak.ac |  BD95 8F7B F8FC 4A11 C97A

Bug#893402: marked as done (Uses deprecated llvm3.9)

[Debian Bug Tracking System]

Your message dated Sun, 18 Mar 2018 18:36:14 +
with message-id 
and subject line Bug#893402: fixed in qtcreator 4.5.2-3
has caused the Debian Bug report #893402,
regarding Uses deprecated llvm3.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.)


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

llvm 3.9 is deprecated and in the process of being removed for stretch,
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873408

Please update your package to use the latest, recommended version which
is llvm6.0.

Thanks,
Michael

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

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

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: qtcreator
Source-Version: 4.5.2-3

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Mar 2018 19:10:54 +0100
Source: qtcreator
Binary: qtcreator qtcreator-data qtcreator-doc
Architecture: source
Version: 4.5.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Qt/KDE Maintainers 
Changed-By: Adam Majer 
Description:
 qtcreator  - integrated development environment (IDE) for Qt
 qtcreator-data - application data for Qt Creator IDE
 qtcreator-doc - documentation for Qt Creator IDE
Closes: 893402
Changes:
 qtcreator (4.5.2-3) unstable; urgency=medium
 .
   * Update libclang dependency to 6.0 (closes: #893402)
Checksums-Sha1:
 88fd76b829bd0cf33af8003ca0e3608ef5233747 2815 qtcreator_4.5.2-3.dsc
 4058bdf666d9064cdcb07843a4447ca921fa76ca 23608 qtcreator_4.5.2-3.debian.tar.xz
 210f7230b790e21e3b08e98dc9dc5f348cbc86c0 12372 
qtcreator_4.5.2-3_source.buildinfo
Checksums-Sha256:
 e785e7787cef3f3e144c7b3219841d15c5d766f2a66940791c0661302a39ad06 2815 
qtcreator_4.5.2-3.dsc
 16ff63ce9a66f0d4e96af6af41a3f3c3c798973ea58f2b7884c0203e74c363cc 23608 
qtcreator_4.5.2-3.debian.tar.xz
 a4c703091712a6cac2168563d4466966552bdb91125ef8eaceb39110e78fc929 12372 
qtcreator_4.5.2-3_source.buildinfo
Files:
 9488a02f60009a77dd20867e6f41b211 2815 devel optional qtcreator_4.5.2-3.dsc
 900031998121dded172c2476093ebbc5 23608 devel optional 
qtcreator_4.5.2-3.debian.tar.xz
 ef2ae2e0255e1c104f6b6851c19bf216 12372 devel optional 
qtcreator_4.5.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIuBAEBCgAwFiEES+fB08xlgTrzSdQvhkUIsBsmec8FAlqurFgSHGFkYW1tQHpv
bWJpbm8uY29tAAoJEIZFCLAbJnnPF/APOwRUaDnjQU2WyALydXKMuUAAePacT0QF
5fAECUMSzKhD+0yCpStGPfTUuUnYh4IWbd6SczjXOefIL+HHg8+zOwryHReFXKP3
gYrBAMWwjI/vqVKz3C1acrU1sJDnYylQMMQQbINbIWlYFU/GR1xzTd5JFuK2LTdT
B1uIyPfsRlXPFygs1Nv8Xq4jPLcvT5oy2Xx2qCC+zKx0RyqaOqu/SkveYxP7NQyT
vWzH9DRHrvSVvakD4tcjPQ9OrZcNaGCzpZgBB8fqhdgdmy0jOkH6nf6CyVpPUaKq
lT58XVe+buHopPcnCky6pq31MQE1fwbZtFFLj+NTMlUhmwFhK5qJjc4N6sopHW1U
4C73WbtGWZiHOZUimnZEKqFlrjCU30H8Ch8wwbDOgFVt2FTffwuQsoedbJXt4z6k
47b7wxPF/Gz2D9AWzVK/NyfniA3LMIFbtrYyXLd6hDPX+/p9xtOrpNCZZ8hc9It1
TwGd46DFh5Y4eE26DlDhXOeMyhEn5IpSB98Jvi+fAWraQ1Uc0rLd1bmK6/LWnikB
1brKUCrdIG4qmBmLqIMSWSTeLd9ZLIlWzjVZ6tcvnJVjozCvdgboyVcFVdnkvvY6
MPtNFkJF5KCYhBhBSRwTB7nCePEDnJ4VYDi3krIxKopF
=r8uS
-END PGP SIGNATURE End Message ---

Bug#893065: marked as done (ironic-inspector: fails to install: ironic-inspector-dbsync: not found)

[Debian Bug Tracking System]

Your message dated Sun, 18 Mar 2018 18:35:06 +
with message-id 
and subject line Bug#893065: fixed in ironic-inspector 7.2.0-3
has caused the Debian Bug report #893065,
regarding ironic-inspector: fails to install: ironic-inspector-dbsync: not found
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.)


-- 
893065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893065
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ironic-inspector
Version: 7.2.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

  Selecting previously unselected package ironic-inspector.
  (Reading database ... 
(Reading database ... 16191 files and directories currently installed.)
  Preparing to unpack .../ironic-inspector_7.2.0-2_all.deb ...
  Unpacking ironic-inspector (7.2.0-2) ...
  Setting up ironic-inspector (7.2.0-2) ...
  sh: 1: ironic-inspector-dbsync: not found
  dpkg: error processing package ironic-inspector (--configure):
   installed ironic-inspector package post-installation script subprocess 
returned error exit status 127
  Errors were encountered while processing:


cheers,

Andreas


ironic-inspector_7.2.0-2.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: ironic-inspector
Source-Version: 7.2.0-3

We believe that the bug you reported is fixed in the latest version of
ironic-inspector, 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.
Thomas Goirand  (supplier of updated ironic-inspector 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, 06 Mar 2018 22:08:30 +
Source: ironic-inspector
Binary: ironic-inspector python3-ironic-inspector
Architecture: source all
Version: 7.2.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Description:
 ironic-inspector - discovering hardware properties for OpenStack Ironic - 
Daemon
 python3-ironic-inspector - discovering hardware properties for OpenStack 
Ironic - Python 2.7
Closes: 893065
Changes:
 ironic-inspector (7.2.0-3) unstable; urgency=medium
 .
   * Fixed generation of python.json with --format json.
   * Add missing dh_install call (Closes: #893065).
   * Add dh_python3 --shebang=/usr/bin/python3.
Checksums-Sha1:
 324c75742405422ca4c51646fd11efefadd11da6 3363 ironic-inspector_7.2.0-3.dsc
 3628076d60050d1bcacddba118d0943c675c1470 5520 
ironic-inspector_7.2.0-3.debian.tar.xz
 2babf184c5a6b57da6245e022f4f4d0abe1ac9bb 25252 ironic-inspector_7.2.0-3_all.deb
 6a802aa73d693688f212f2fb924266affe970543 14964 
ironic-inspector_7.2.0-3_amd64.buildinfo
 69087bdf469db4402f809df5f18e0cf108f5129b 106352 
python3-ironic-inspector_7.2.0-3_all.deb
Checksums-Sha256:
 462758a08161d89e943f3294cc965fc9161695d4693d15c146dad64477f70bd2 3363 
ironic-inspector_7.2.0-3.dsc
 7f71e536a74e7b87a3dd5a7cabca5fdb09d03d2e1db8879bd7ff3dbaaa04834c 5520 
ironic-inspector_7.2.0-3.debian.tar.xz
 b86158052c604c58e88efdf2b6aab7d48006a0f42acf959e7930e31e5f5c4b71 25252 
ironic-inspector_7.2.0-3_all.deb
 49db005f1b258d2fb9ed8700a6f0bd257a9888366d6d71963fbd971c0a5f4137 14964 
ironic-inspector_7.2.0-3_amd64.buildinfo
 f8db5fc80f36a5cf263c013b1d688d684e00ed4e2830571ab091a911722fd568 106352 
python3-ironic-inspector_7.2.0-3_all.deb
Files:
 744057e953a1cf9d823ebc59330e5c75 3363 python optional 
ironic-inspector_7.2.0-3.dsc
 a8081bd7a2e54f88cdb7bee6700bc3e3 5520 python optional 
ironic-inspector_7.2.0-3.debian.tar.xz
 66a0cddc9bf644572a0f0ed91c913aa7 25252 python optional 
ironic-inspector_7.2.0-3_all.deb
 f55cef0145686f519376004a33f3fdbc 14964 python optional 
ironic-inspector_7.2.0-3_amd64.buildinfo
 74ee6d46d5c9b71dd91a1d5f35b99b08 106352 python optional 
python3-ironic-inspector_7.2.0-3_all.deb

Bug#893402: Uses deprecated llvm3.9

[Lisandro Damián Nicanor Pérez Meyer]

On 18 March 2018 at 15:22, Michael Biebl  wrote:
> Am 18.03.2018 um 19:13 schrieb Lisandro Damián Nicanor Pérez Meyer:
>> El 18 mar. 2018 2:39 p.m., "Michael Biebl" > > escribió:
>>
>> Am 18.03.2018 um 18:33 schrieb Michael Biebl:
>> > Source: qtcreator
>> > Version: 4.5.2-2
>> > Severity: serious
>> >
>> > llvm 3.9 is deprecated and in the process of being removed for
>> stretch,
>> > see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873408
>
>> Sorry, wrong C, I meant this bug report
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884541
>
> And I meant buster, of course...

Adam just tried and it seems that somehow it works with llvm 6, which
is highly unexpected. He will try to upload it soon.


-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Processed: affects 873227

[Debian Bug Tracking System]

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

> affects 873227 src:simplyhtml
Bug #873227 [src:gradle] Please upgrade to 4.1: Java 9 support
Added indication that 873227 affects src:simplyhtml
> 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#893369: systemd-udevd is killed at startup

[LEDUQUE Mickaël]

Ok, I was more searching for a way to do it from inside grub itself, but
this will have to do.

2018-03-18 18:55 GMT+01:00 Michael Biebl :

> Am 18.03.2018 um 18:50 schrieb LEDUQUE Mickaël:
> > I'll do all that, thanks. Do you know how I can set a correct keymap in
> > the grub "e" text editor ?
>
> I don't. But this is literally the first google hit regarding that question
> https://askubuntu.com/questions/751259/how-to-
> change-grub-command-line-grub-shell-keyboard-layout
>
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
>

Bug#893421: swi-prolog FTBFS with openjdk-9

[Adrian Bunk]

Source: swi-prolog
Version: 7.6.2+dfsg-1
Severity: serious

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

...
/usr/bin/make -C packages/jpl 
DESTDIR=/build/1st/swi-prolog-7.6.4+dfsg/debian/swi-prolog-java 
PL=/build/1st/swi-prolog-7.6.4+dfsg/src/swipl.sh 
PLEXE=/build/1st/swi-prolog-7.6.4+dfsg/src/swipl.sh PLBASE=/usr/lib/swi-prolog/ 
install < /dev/null
make[2]: Entering directory '/build/1st/swi-prolog-7.6.4+dfsg'
make[2]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
rule.
gcc -shared -rdynamic -Wl,-z,relro -g -O2 -fstack-protector-strong -Wformat 
-Werror=format-security -pthread  
-L/build/1st/swi-prolog-7.6.4+dfsg/src/../lib/amd64  -o libjpl.so src/c/jpl.o  
-ljava -lverify -ljvm -lswipl
/usr/bin/ld: cannot find -ljava
/usr/bin/ld: cannot find -lverify
/usr/bin/ld: cannot find -ljvm
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:44: libjpl.so] Error 1

Bug#893402: Uses deprecated llvm3.9

[Michael Biebl]

Am 18.03.2018 um 19:13 schrieb Lisandro Damián Nicanor Pérez Meyer:
> El 18 mar. 2018 2:39 p.m., "Michael Biebl"  > escribió:
> 
> Am 18.03.2018 um 18:33 schrieb Michael Biebl:
> > Source: qtcreator
> > Version: 4.5.2-2
> > Severity: serious
> >
> > llvm 3.9 is deprecated and in the process of being removed for
> stretch,
> > see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873408

> Sorry, wrong C, I meant this bug report
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884541

And I meant buster, of course...


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#893420: swt-gtk FTBFS with openjdk-9

[Adrian Bunk]

Source: swt-gtk
Version: 3.8.2-4
Severity: serious

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

...
/usr/bin/make -f debian/Makefile -C . CFLAGS="-g -O2 -fstack-protector-strong 
-Wformat -Werror=format-security -fPIC -Wdate-time -D_FORTIFY_SOURCE=2" 
CXXFLAGS="-g -O2 -fstack-protector-strong -Wformat -Werror=format-security" 
CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro" 
make[1]: Entering directory '/build/1st/swt-gtk-3.8.2'
find org -name *.java -o -name *.properties | sort > swt-gtk-3.8.2.files
mkdir -p swt-gtk-3.8.2
grep \.java swt-gtk-3.8.2.files | xargs -r javac -classpath . -source 1.5 
-target 1.5 -d swt-gtk-3.8.2
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[1]: *** [debian/Makefile:25: swt-gtk-3.8.2-stamp] Error 123

Processed: Bug #893065 in ironic-inspector marked as pending

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #893065 [ironic-inspector] ironic-inspector: fails to install: 
ironic-inspector-dbsync: not found
Added tag(s) pending.

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

Bug#893065: Bug #893065 in ironic-inspector marked as pending

[thomas]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/openstack-team/services/ironic-inspector/commit/7b47246a153d2aedf6426569a0c44b2d7e0d77ed


Add missing dh_install call (Closes: #893065).



(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/893065

Bug#893419: stylebook FTBFS with openjdk-9

[Adrian Bunk]

Source: stylebook
Version: 1.0~b3~svn20061109-6
Severity: serious
Tags: buster sid

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

...
compile2:
[javac] /build/1st/stylebook-1.0~b3~svn20061109/build.xml:86: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] This version of java does not support the classic compiler; 
upgrading to modern
[javac] Compiling 40 source files to 
/build/1st/stylebook-1.0~b3~svn20061109/build/classes
[javac] This version of java does not support the classic compiler; 
upgrading to modern
[javac] Using ant.build.javac.target 1.5 is no longer supported, switching 
to 1.6
[javac] Using ant.build.javac.target 1.5 is no longer supported, switching 
to 1.6
[javac] Using ant.build.javac.source 1.5 is no longer supported, switching 
to 1.6
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/stylebook-1.0~b3~svn20061109/src/org/apache/stylebook/AbstractComponent.java:16:
 error: unmappable character (0xC3) for encoding US-ASCII
[javac]  * @version CVS $Revision: 313195 $ $Date: 1999-11-15 23:08:18 
+0100 (m??n, 15 nov 1999) $
[javac] 
   ^
[javac] 
/build/1st/stylebook-1.0~b3~svn20061109/src/org/apache/stylebook/AbstractComponent.java:16:
 error: unmappable character (0xA5) for encoding US-ASCII
[javac]  * @version CVS $Revision: 313195 $ $Date: 1999-11-15 23:08:18 
+0100 (m??n, 15 nov 1999) $
[javac] 
^
[javac] 
/build/1st/stylebook-1.0~b3~svn20061109/src/org/apache/stylebook/BasicParameters.java:19:
 error: unmappable character (0xC3) for encoding US-ASCII
[javac]  * @version CVS $Revision: 313195 $ $Date: 1999-11-15 23:08:18 
+0100 (m??n, 15 nov 1999) $
[javac] 
   ^
[javac] 
/build/1st/stylebook-1.0~b3~svn20061109/src/org/apache/stylebook/BasicParameters.java:19:
 error: unmappable character (0xA5) for encoding US-ASCII
[javac]  * @version CVS $Revision: 313195 $ $Date: 1999-11-15 23:08:18 
+0100 (m??n, 15 nov 1999) $
[javac] 
^
[javac] 
/build/1st/stylebook-1.0~b3~svn20061109/src/org/apache/stylebook/Component.java:16:
 error: unmappable character (0xC3) for encoding US-ASCII
[javac]  * @version CVS $Revision: 313195 $ $Date: 1999-11-15 23:08:18 
+0100 (m??n, 15 nov 1999) $
[javac] 
   ^
[javac] 
/build/1st/stylebook-1.0~b3~svn20061109/src/org/apache/stylebook/Component.java:16:
 error: unmappable character (0xA5) for encoding US-ASCII
[javac]  * @version CVS $Revision: 313195 $ $Date: 1999-11-15 23:08:18 
+0100 (m??n, 15 nov 1999) $
[javac] 
^
[javac] 
/build/1st/stylebook-1.0~b3~svn20061109/src/org/apache/stylebook/ComponentFactory.java:16:
 error: unmappable character (0xC3) for encoding US-ASCII
[javac]  * @version CVS $Revision: 313195 $ $Date: 1999-11-15 23:08:18 
+0100 (m??n, 15 nov 1999) $
[javac] 
   ^
[javac] 
/build/1st/stylebook-1.0~b3~svn20061109/src/org/apache/stylebook/ComponentFactory.java:16:
 error: unmappable character (0xA5) for encoding US-ASCII
[javac]  * @version CVS $Revision: 313195 $ $Date: 1999-11-15 23:08:18 
+0100 (m??n, 15 nov 1999) $
[javac] 
^
[javac] 
/build/1st/stylebook-1.0~b3~svn20061109/src/org/apache/stylebook/CreationException.java:19:
 error: unmappable character (0xC3) for encoding US-ASCII
[javac]  * @version CVS $Revision: 313195 $ $Date: 1999-11-15 23:08:18 
+0100 (m??n, 15 nov 1999) $
[javac] 
   ^
[javac] 
/build/1st/stylebook-1.0~b3~svn20061109/src/org/apache/stylebook/CreationException.java:19:
 error: unmappable character (0xA5) for encoding US-ASCII
[javac]  * @version CVS $Revision: 313195 $ $Date: 1999-11-15 23:08:18 
+0100 (m??n, 15 nov 1999) $
[javac] 
^
[javac] 
/build/1st/stylebook-1.0~b3~svn20061109/src/org/apache/stylebook/Engine.java:19:
 error: unmappable character (0xC3) for encoding US-ASCII
[javac]  * @version CVS 

Bug#893417: spock FTBFS with openjdk-9

[Adrian Bunk]

Source: spock
Version: 0.7-groovy-2.0-3
Severity: serious
Tags: buster sid

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

...
build.core:
[mkdir] Created dir: /build/1st/spock-0.7-groovy-2.0/spock-core/build
  [groovyc] Compiling 350 source files to 
/build/1st/spock-0.7-groovy-2.0/spock-core/build
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
org.codehaus.groovy.reflection.CachedClass 
(file:/usr/share/java/groovy-all.jar) to method java.lang.Object.finalize()
WARNING: Please consider reporting this to the maintainers of 
org.codehaus.groovy.reflection.CachedClass
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
  [groovyc] org.codehaus.groovy.control.MultipleCompilationErrorsException: 
startup failed:
  [groovyc] Invalid commandline usage for javac.
  [groovyc] warning: [options] bootstrap class path not set in conjunction with 
-source 1.5
  [groovyc] error: Source option 1.5 is no longer supported. Use 1.6 or later.
  [groovyc] error: Target option 1.5 is no longer supported. Use 1.6 or later.
  [groovyc] 
  [groovyc] 
  [groovyc] 1 error

BUILD FAILED
/build/1st/spock-0.7-groovy-2.0/debian/build.xml:82: The following error 
occurred while executing this line:
/build/1st/spock-0.7-groovy-2.0/debian/build.xml:122: Compilation Failed

Total time: 2 seconds
dh_auto_build: ant -Duser.name debian returned exit code 1
make: *** [debian/rules:8: build] Error 2

Bug#893402: Uses deprecated llvm3.9

[Lisandro Damián Nicanor Pérez Meyer]

El 18 mar. 2018 2:39 p.m., "Michael Biebl"  escribió:

Am 18.03.2018 um 18:33 schrieb Michael Biebl:
> Source: qtcreator
> Version: 4.5.2-2
> Severity: serious
>
> llvm 3.9 is deprecated and in the process of being removed for stretch,
> see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873408

Sorry, wrong C, I meant this bug report
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884541


Ok, this is unfortunate, qtcreator won't probably support a newer llvm
until the next release. Actually the problem here lies on llvm not having a
stable API, but nothing you and I can do about it.

I'll see what can be done...

Bug#893416: sezpoz FTBFS with openjdk-9

[Adrian Bunk]

Source: sezpoz
Version: 1.10-2
Severity: serious
Tags: buster sid

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

...
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running net.java.sezpoz.IndexTest
warning: Supported source version 'RELEASE_6' from annotation processor 
'net.java.sezpoz.impl.Indexer6' less than -source '1.9'
/tmp/net.java.sezpoz.IndexTest/test1/src/x/A.java:5: warning: should be marked 
@Retention(RetentionPolicy.SOURCE)
public @interface A {}
^
error: java.nio.file.NoSuchFileException: 
/tmp/net.java.sezpoz.IndexTest/test1/clz/META-INF/annotations/x.A
1 error
2 warnings
warning: Supported source version 'RELEASE_6' from annotation processor 
'net.java.sezpoz.impl.Indexer6' less than -source '1.9'
/tmp/net.java.sezpoz.IndexTest/test2/src/x/A.java:6: warning: should be marked 
@Retention(RetentionPolicy.SOURCE)
public @interface A {
^
error: java.nio.file.NoSuchFileException: 
/tmp/net.java.sezpoz.IndexTest/test2/clz/META-INF/annotations/x.A
1 error
2 warnings
warning: Supported source version 'RELEASE_6' from annotation processor 
'net.java.sezpoz.impl.Indexer6' less than -source '1.9'
/tmp/net.java.sezpoz.IndexTest/test3/src/api/MenuItem.java:6: warning: should 
be marked @Retention(RetentionPolicy.SOURCE)
public @interface MenuItem {
^
error: java.nio.file.NoSuchFileException: 
/tmp/net.java.sezpoz.IndexTest/test3/clz/META-INF/annotations/api.MenuItem
1 error
2 warnings
warning: Supported source version 'RELEASE_6' from annotation processor 
'net.java.sezpoz.impl.Indexer6' less than -source '1.9'
/tmp/net.java.sezpoz.IndexTest/test4/src/x/A.java:5: warning: should be marked 
@Retention(RetentionPolicy.SOURCE)
public @interface A {
^
error: java.nio.file.NoSuchFileException: 
/tmp/net.java.sezpoz.IndexTest/test4/clz/META-INF/annotations/x.A
1 error
2 warnings
warning: Supported source version 'RELEASE_6' from annotation processor 
'net.java.sezpoz.impl.Indexer6' less than -source '1.9'
/tmp/net.java.sezpoz.IndexTest/test5/src/x/A.java:6: warning: should be marked 
@Retention(RetentionPolicy.SOURCE)
public @interface A {
^
error: java.nio.file.NoSuchFileException: 
/tmp/net.java.sezpoz.IndexTest/test5/clz/META-INF/annotations/x.A
1 error
2 warnings
warning: Supported source version 'RELEASE_6' from annotation processor 
'net.java.sezpoz.impl.Indexer6' less than -source '1.9'
error: java.nio.file.NoSuchFileException: 
/tmp/net.java.sezpoz.IndexTest/test6/clz/META-INF/annotations/net.java.sezpoz.IndexTest$Marker
1 error
1 warning
warning: Supported source version 'RELEASE_6' from annotation processor 
'net.java.sezpoz.impl.Indexer6' less than -source '1.9'
/tmp/net.java.sezpoz.IndexTest/test7/src/x/A.java:5: warning: should be marked 
@Retention(RetentionPolicy.SOURCE)
public @interface A {
^
error: java.nio.file.NoSuchFileException: 
/tmp/net.java.sezpoz.IndexTest/test7/clz/META-INF/annotations/x.A
1 error
2 warnings
warning: Supported source version 'RELEASE_6' from annotation processor 
'net.java.sezpoz.impl.Indexer6' less than -source '1.9'
/tmp/net.java.sezpoz.IndexTest/test8/src/x/A.java:5: warning: should be marked 
@Retention(RetentionPolicy.SOURCE)
public @interface A {}
^
error: java.nio.file.NoSuchFileException: 
/tmp/net.java.sezpoz.IndexTest/test8/clz/META-INF/annotations/x.A
1 error
2 warnings
[ERROR] Tests run: 8, Failures: 0, 
Errors: 8, Skipped: 0, Time elapsed: 3.751 s <<< 
FAILURE! - in net.java.sezpoz.IndexTest
[ERROR] multipleCodeSources(net.java.sezpoz.IndexTest)  Time elapsed: 
1.474 s  <<< ERROR!
net.java.sezpoz.impl.AptFailedException: processing failed with error code 1
at net.java.sezpoz.IndexTest.multipleCodeSources(IndexTest.java:209)

[ERROR] complexStructure(net.java.sezpoz.IndexTest)  Time elapsed: 
0.425 s  <<< ERROR!
net.java.sezpoz.impl.AptFailedException: processing failed with error code 1
at net.java.sezpoz.IndexTest.complexStructure(IndexTest.java:398)

[ERROR] basicUsage(net.java.sezpoz.IndexTest)  Time elapsed: 0.478 s  
<<< ERROR!
net.java.sezpoz.impl.AptFailedException: processing failed with error code 1
at net.java.sezpoz.IndexTest.basicUsage(IndexTest.java:94)

[ERROR] heavyOverlap(net.java.sezpoz.IndexTest)  Time elapsed: 0.352 
s  <<< ERROR!
net.java.sezpoz.impl.AptFailedException: processing failed with error code 1
at net.java.sezpoz.IndexTest.heavyOverlap(IndexTest.java:277)

[ERROR] defaultValues(net.java.sezpoz.IndexTest)  Time elapsed: 0.24 
s  <<< ERROR!
net.java.sezpoz.impl.AptFailedException: processing failed with error code 1
at net.java.sezpoz.IndexTest.defaultValues(IndexTest.java:320)

[ERROR] 

Bug#831158: marked as done (scim-unikey: FTBFS with GCC 6: data.cpp:242:1: error: narrowing conversion of ''\37777777670'' from 'char' to 'unsigned char' inside { } [-Wnarrowing])

[Debian Bug Tracking System]

Your message dated Sun, 18 Mar 2018 18:07:48 +
with message-id 
and subject line Bug#811766: fixed in scim-unikey 0.3.1+debian-3.2
has caused the Debian Bug report #811766,
regarding scim-unikey: FTBFS with GCC 6: data.cpp:242:1: error: narrowing 
conversion of ''\3777670'' from 'char' to 'unsigned char' inside { } 
[-Wnarrowing]
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.)


-- 
811766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: scim-unikey
Version: 0.3.1+debian-3.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64

Hi,

During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html

Relevant part (hopefully):
> /bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. 
> -g -O2 -c -o data.lo data.cpp
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -g -O2 -c data.cpp  -fPIC 
> -DPIC -o .libs/data.o
> data.cpp:242:1: error: narrowing conversion of ''\3777670'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
>  };
>  ^
> data.cpp:242:1: error: narrowing conversion of ''\3777670'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777665'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777665'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777666'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777666'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777667'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777667'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777671'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777671'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777642'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777651'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\312'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\312'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\307'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\307'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\310'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\310'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\311'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\311'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\313'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\313'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777641'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777650'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777676'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777676'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> 

Bug#811766: marked as done (scim-unikey: FTBFS with GCC 6: narrowing conversion)

[Debian Bug Tracking System]

Your message dated Sun, 18 Mar 2018 18:07:48 +
with message-id 
and subject line Bug#811766: fixed in scim-unikey 0.3.1+debian-3.2
has caused the Debian Bug report #811766,
regarding scim-unikey: FTBFS with GCC 6: narrowing conversion
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.)


-- 
811766: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=811766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: scim-unikey
Version: 0.3.1+debian-3.1
Severity: important
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-6 gcc-6-narrowing

This package fails to build with GCC 6.  GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.

Note that only the first error is reported; there might be more.  You
can find a snapshot of GCC 6 in experimental.  To build with GCC 6,
you can set CC=gcc-6 CXX=g++-6 explicitly.

You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html

> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> /bin/bash ../libtool  --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. 
> -g -O2 -c -o data.lo data.cpp
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -g -O2 -c data.cpp  -fPIC 
> -DPIC -o .libs/data.o
> data.cpp:242:1: error: narrowing conversion of ''\3777670'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
>  };
>  ^
> 
> data.cpp:242:1: error: narrowing conversion of ''\3777670'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777665'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777665'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777666'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777666'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777667'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777667'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777671'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777671'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777642'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\3777651'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\312'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\312'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\307'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\307'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\310'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\310'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\311'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
> data.cpp:242:1: error: narrowing conversion of ''\311'' from 'char' 
> to 'unsigned char' inside { } [-Wnarrowing]
...

-- 
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
Source: scim-unikey
Source-Version: 0.3.1+debian-3.2

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

Debian distribution maintenance software
pp.
James Cowgill  (supplier of updated scim-unikey package)

(This message was generated automatically at 

Bug#893415: robocode FTBFS with openjdk-9

[Adrian Bunk]

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

Bug#893412: saxonb FTBFS with openjdk-9

[Adrian Bunk]

Source: saxonb
Version: 9.1.0.8+dfsg-1
Severity: serious
Tags: buster sid

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

...
compile:
[mkdir] Created dir: /build/1st/saxonb-9.1.0.8+dfsg/build
[javac] /build/1st/saxonb-9.1.0.8+dfsg/debian/build.xml:10: warning: 
'includeantruntime' was not set, defaulting to build.sysclasspath=last; set to 
false for repeatable builds
[javac] Using javac -source 1.5 is no longer supported, switching to 1.6
[javac] Using javac -target 1.5 is no longer supported, switching to 1.6
[javac] Compiling 946 source files to /build/1st/saxonb-9.1.0.8+dfsg/build
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/codenorm/NormalizerData.java:11: 
error: unmappable character (0xA9) for encoding US-ASCII
[javac]  * Copyright ? 1998-1999 Unicode, Inc. All Rights Reserved.
[javac] ^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/codenorm/NormalizerData.java:19: 
error: unmappable character (0xA9) for encoding US-ASCII
[javac] static final String copyright = "Copyright ? 1998-1999 Unicode, 
Inc.";
[javac]^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/codenorm/NormalizerData.java:41: 
error: unmappable character (0xB8) for encoding US-ASCII
[javac] * @param   second   second character (e.g. '?' cedilla)
[javac] ^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/codenorm/NormalizerData.java:42: 
error: unmappable character (0xE7) for encoding US-ASCII
[javac] * @return  composite (e.g. '?')
[javac] ^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/codenorm/UnicodeDataGenerator.java:30:
 error: unmappable character (0xA9) for encoding US-ASCII
[javac] static final String copyright = "Copyright ? 1998-1999 Unicode, 
Inc.";
[javac]^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/number/Numberer_da.java:16: 
error: unmappable character (0xF8) for encoding US-ASCII
[javac] "", "f?rste", "anden", "tredje", "fjerde", "femte", 
"sjette", "syvende", "ottende", "niende",
[javac]   ^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/number/Numberer_da.java:17: 
error: unmappable character (0xE9) for encoding US-ASCII
[javac] "tiende", "?lfte", "tolvte", "trettende" , "fjortende", 
"femtende", "sekstende",
[javac]^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/number/Numberer_da.java:185: 
error: unmappable character (0xF8) for encoding US-ASCII
[javac] "mandag", "tirsdag", "onsdag", "torsdag", "fredag", 
"l?rdag", "s?ndag"
[javac]   ^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/number/Numberer_da.java:185: 
error: unmappable character (0xF8) for encoding US-ASCII
[javac] "mandag", "tirsdag", "onsdag", "torsdag", "fredag", 
"l?rdag", "s?ndag"
[javac] 
^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/number/Numberer_da.java:189: 
error: unmappable character (0xF8) for encoding US-ASCII
[javac] "ma", "ti", "on", "to", "fr", "l?", "s?"
[javac] ^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/number/Numberer_da.java:189: 
error: unmappable character (0xF8) for encoding US-ASCII
[javac] "ma", "ti", "on", "to", "fr", "l?", "s?"
[javac]   ^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/number/Numberer_de.java:64: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] "", "Eins", "Zwei", "Drei", "Vier", "F?nf", "Sechs", 
"Sieben", "Acht", "Neun",
[javac]   ^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/number/Numberer_de.java:65: 
error: unmappable character (0xF6) for encoding US-ASCII
[javac] "Zehn", "Elf", "Zw?lf", "Dreizehn", "Vierzehn", "F?nfzehn", 
"Sechszehn",
[javac]   ^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/number/Numberer_de.java:65: 
error: unmappable character (0xFC) for encoding US-ASCII
[javac] "Zehn", "Elf", "Zw?lf", "Dreizehn", "Vierzehn", "F?nfzehn", 
"Sechszehn",
[javac]   ^
[javac] 
/build/1st/saxonb-9.1.0.8+dfsg/bj/net/sf/saxon/number/Numberer_de.java:69: 
error: unmappable character (0xDF) for encoding US-ASCII
[javac] "", "Zehn", "Zwanzig", "Drei?ig", "Vierzig", "F?nfzig",
[javac] ^
[javac] 

Bug#893411: sat4j FTBFS with openjdk-9

[Adrian Bunk]

Source: sat4j
Version: 2.3.5-0.2
Severity: serious
Tags: buster sid

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

...
build:
 [echo] Compiling source code org.sat4j.core/src/main/java using target 1.5
[javac] Using javac -source 1.5 is no longer supported, switching to 1.6
[javac] Using javac -target 1.5 is no longer supported, switching to 1.6
[javac] Compiling 215 source files to /build/1st/sat4j-2.3.5/bin
[javac] warning: [options] bootstrap class path not set in conjunction with 
-source 1.6
[javac] warning: [options] source value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.6 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 
/build/1st/sat4j-2.3.5/org.sat4j.core/src/main/java/org/sat4j/tools/Backbone.java:54:
 error: unmappable character (0xC3) for encoding US-ASCII
[javac]  * Jo??o Marques-Silva, Mikol??s Janota, In??s Lynce: On 
Computing Backbones of
[javac]  ^
[javac] 
/build/1st/sat4j-2.3.5/org.sat4j.core/src/main/java/org/sat4j/tools/Backbone.java:54:
 error: unmappable character (0xA3) for encoding US-ASCII
[javac]  * Jo??o Marques-Silva, Mikol??s Janota, In??s Lynce: On 
Computing Backbones of
[javac]   ^
[javac] 
/build/1st/sat4j-2.3.5/org.sat4j.core/src/main/java/org/sat4j/tools/Backbone.java:54:
 error: unmappable character (0xC3) for encoding US-ASCII
[javac]  * Jo??o Marques-Silva, Mikol??s Janota, In??s Lynce: On 
Computing Backbones of
[javac]  ^
[javac] 
/build/1st/sat4j-2.3.5/org.sat4j.core/src/main/java/org/sat4j/tools/Backbone.java:54:
 error: unmappable character (0xA1) for encoding US-ASCII
[javac]  * Jo??o Marques-Silva, Mikol??s Janota, In??s Lynce: On 
Computing Backbones of
[javac]   ^
[javac] 
/build/1st/sat4j-2.3.5/org.sat4j.core/src/main/java/org/sat4j/tools/Backbone.java:54:
 error: unmappable character (0xC3) for encoding US-ASCII
[javac]  * Jo??o Marques-Silva, Mikol??s Janota, In??s Lynce: On 
Computing Backbones of
[javac]^
[javac] 
/build/1st/sat4j-2.3.5/org.sat4j.core/src/main/java/org/sat4j/tools/Backbone.java:54:
 error: unmappable character (0xAA) for encoding US-ASCII
[javac]  * Jo??o Marques-Silva, Mikol??s Janota, In??s Lynce: On 
Computing Backbones of
[javac] ^
[javac] 
/build/1st/sat4j-2.3.5/org.sat4j.core/src/main/java/org/sat4j/tools/Backbone.java:70:
 error: unmappable character (0xC3) for encoding US-ASCII
[javac]  * Jo??o Marques-Silva, Mikol??s Janota, In??s Lynce: On 
Computing Backbones of
[javac]  ^
[javac] 
/build/1st/sat4j-2.3.5/org.sat4j.core/src/main/java/org/sat4j/tools/Backbone.java:70:
 error: unmappable character (0xA3) for encoding US-ASCII
[javac]  * Jo??o Marques-Silva, Mikol??s Janota, In??s Lynce: On 
Computing Backbones of
[javac]   ^
[javac] 
/build/1st/sat4j-2.3.5/org.sat4j.core/src/main/java/org/sat4j/tools/Backbone.java:70:
 error: unmappable character (0xC3) for encoding US-ASCII
[javac]  * Jo??o Marques-Silva, Mikol??s Janota, In??s Lynce: On 
Computing Backbones of
[javac]  ^
[javac] 
/build/1st/sat4j-2.3.5/org.sat4j.core/src/main/java/org/sat4j/tools/Backbone.java:70:
 error: unmappable character (0xA1) for encoding US-ASCII
[javac]  * Jo??o Marques-Silva, Mikol??s Janota, In??s Lynce: On 
Computing Backbones of
[javac]   ^
[javac] 
/build/1st/sat4j-2.3.5/org.sat4j.core/src/main/java/org/sat4j/tools/Backbone.java:70:
 error: unmappable character (0xC3) for encoding US-ASCII
[javac]  * Jo??o Marques-Silva, Mikol??s Janota, In??s Lynce: On 
Computing Backbones of
[javac]^
[javac] 
/build/1st/sat4j-2.3.5/org.sat4j.core/src/main/java/org/sat4j/tools/Backbone.java:70:
 error: unmappable character (0xAA) for encoding US-ASCII
[javac]  * Jo??o Marques-Silva, Mikol??s Janota, In??s Lynce: On 
Computing Backbones of
[javac] ^
[javac] 12 errors
[javac] 4 warnings

BUILD FAILED
/build/1st/sat4j-2.3.5/build.xml:210: The following error occurred while 
executing this line:
/build/1st/sat4j-2.3.5/build.xml:330: Compile failed; see the compiler error 
output for details.

Total time: 2 seconds
make[1]: *** [debian/rules:44: override_dh_auto_build] Error 1

Bug#893409: pixelmed FTBFS with openjdk-9

[Adrian Bunk]

Source: pixelmed
Version: 20150917-2
Severity: serious

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

...
../../../../com/pixelmed/display/SourceImage.java:1626: error: cannot find 
symbol
sun.misc.Cleaner cleaner = 
(sun.misc.Cleaner)getCleanerMethod.invoke(object,new Object[0]);
^
  symbol:   class Cleaner
  location: package sun.misc
../../../../com/pixelmed/display/SourceImage.java:1626: error: cannot find 
symbol
sun.misc.Cleaner cleaner = 
(sun.misc.Cleaner)getCleanerMethod.invoke(object,new Object[0]);

^
  symbol:   class Cleaner
  location: package sun.misc

Bug#893369: systemd-udevd is killed at startup

[Michael Biebl]

Am 18.03.2018 um 18:50 schrieb LEDUQUE Mickaël:
> I'll do all that, thanks. Do you know how I can set a correct keymap in
> the grub "e" text editor ?

I don't. But this is literally the first google hit regarding that question
https://askubuntu.com/questions/751259/how-to-change-grub-command-line-grub-shell-keyboard-layout


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#893410: polyglot-maven FTBFS with openjdk-9

[Adrian Bunk]

Source: polyglot-maven
Version: 0.8~tobrien+git20120905-8
Severity: serious

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

...
build.groovy:
  [groovyc] Compiling 31 source files to 
/build/1st/polyglot-maven-0.8~tobrien+git20120905/build/groovy
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
org.codehaus.groovy.reflection.CachedClass 
(file:/usr/share/java/groovy-all.jar) to method java.lang.Object.finalize()
WARNING: Please consider reporting this to the maintainers of 
org.codehaus.groovy.reflection.CachedClass
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations
WARNING: All illegal access operations will be denied in a future release
  [groovyc] org.codehaus.groovy.control.MultipleCompilationErrorsException: 
startup failed:
  [groovyc] Invalid commandline usage for javac.
  [groovyc] warning: [options] bootstrap class path not set in conjunction with 
-source 1.5
  [groovyc] error: Source option 1.5 is no longer supported. Use 1.6 or later.
  [groovyc] error: Target option 1.5 is no longer supported. Use 1.6 or later.
  [groovyc] 
  [groovyc] 
  [groovyc] 1 error

BUILD FAILED
/build/1st/polyglot-maven-0.8~tobrien+git20120905/debian/build.xml:118: The 
following error occurred while executing this line:
/build/1st/polyglot-maven-0.8~tobrien+git20120905/debian/build.xml:273: 
Compilation Failed

Total time: 5 seconds
dh_auto_build: ant -Duser.name debian returned exit code 1
make[1]: *** [debian/rules:15: override_dh_auto_build] Error 2

Bug#893369: systemd-udevd is killed at startup

[LEDUQUE Mickaël]

I'll do all that, thanks. Do you know how I can set a correct keymap in the
grub "e" text editor ?

2018-03-18 16:57 GMT+01:00 Michael Biebl :

> On Sun, 18 Mar 2018 12:14:41 +0100 =?utf-8?q?Micka=C3=ABl_Leduque?=
>  wrote:
> > Package: systemd
> > Version: 238-2
> > Severity: critical
> > Justification: breaks the whole system
> >
> > Dear Maintainer,
> >
> > After an update and a restart of the system, boot fails. It enters a
> loop, where (apparently) systemd-udevd fails to start and is retries for a
> certain time.
> > After thaat, I am dropped into recovery mode (or failsafe, I don't
> remember the word).
> > I tried investigating the logs, but I couldn't go very far, I just saw
> something that may (or may nt) be related, seccomp logs about systemd-udevd
> using a syscall
> > but that's an "audit" log so I'm not sure it does anyhting at all.
>
> See https://freedesktop.org/wiki/Software/systemd/Debugging/
> "If You Can Get a Shell", and attach the journalctl output of such a boot.
> Since this affects udev, please also consider adding
> udev.log_priority=debug to the kernel command line (see man
> kernel-command-line)
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
>

Bug#893402: Uses deprecated llvm3.9

[Michael Biebl]

Am 18.03.2018 um 18:33 schrieb Michael Biebl:
> Source: qtcreator
> Version: 4.5.2-2
> Severity: serious
> 
> llvm 3.9 is deprecated and in the process of being removed for stretch,
> see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873408

Sorry, wrong C, I meant this bug report
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884541


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#893402: Uses deprecated llvm3.9

[Michael Biebl]

Source: qtcreator
Version: 4.5.2-2
Severity: serious

llvm 3.9 is deprecated and in the process of being removed for stretch,
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873408

Please update your package to use the latest, recommended version which
is llvm6.0.

Thanks,
Michael

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

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

-- no debconf information

Processed: your mail

[Debian Bug Tracking System]

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

> retitle 850915 ghc: Please switch to llvm 6.0
Bug #850915 [src:ghc] ghc: Please switch to llvm 5.0
Changed Bug title to 'ghc: Please switch to llvm 6.0' from 'ghc: Please switch 
to llvm 5.0'.
> retitle 836602 RM: llvm-toolchain-3.7 -- ROM
Bug #836602 [ftp.debian.org] RM: llvm-toolchain-3.7 -- ROM; We should ship only 
3.8, 3.9 and maybe 4.0 in the next stable
Changed Bug title to 'RM: llvm-toolchain-3.7 -- ROM' from 'RM: 
llvm-toolchain-3.7 -- ROM; We should ship only 3.8, 3.9 and maybe 4.0 in the 
next stable'.
> retitle 873408 julia: Please update to llvm-toolchain 6.0
Bug #873408 [src:julia] julia: Please update to llvm-toolchain 4.0 or, better, 
5.0
Changed Bug title to 'julia: Please update to llvm-toolchain 6.0' from 'julia: 
Please update to llvm-toolchain 4.0 or, better, 5.0'.
> retitle 873412 ycmd: Please update to llvm-toolchain 6.0
Bug #873412 [src:ycmd] ycmd: Please update to llvm-toolchain 4.0 or, better, 5.0
Changed Bug title to 'ycmd: Please update to llvm-toolchain 6.0' from 'ycmd: 
Please update to llvm-toolchain 4.0 or, better, 5.0'.
> thanks
Stopping processing here.

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

Processed: limit source to opensmtpd, tagging 859544, tagging 893367

[Debian Bug Tracking System]

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

> limit source opensmtpd
Limiting to bugs with field 'source' containing at least one of 'opensmtpd'
Limit currently set to 'source':'opensmtpd'

> tags 859544 + pending
Bug #859544 [src:opensmtpd] opensmtpd: Please migrate to openssl1.1 in buster
Added tag(s) pending.
> tags 893367 + pending
Bug #893367 [opensmtpd] "smtpctl stop" not supported by upstream anymore
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#893298: libsbml FTBFS with openjdk-9

[Markus Koschany]

Hello Andreas,

Am 18.03.2018 um 09:30 schrieb Andreas Tille:
> Control: tags -1 help
> 
> On Sat, Mar 17, 2018 at 10:07:50PM +0200, Adrian Bunk wrote:
>> ...
>> CMake Error at docs/CMakeLists.txt:212 (message):
>>   Cannot generate java documentation, please specify the Java_JAVADOC_JAR.
> 
> I need to admit I have no idea how to fix this.  Any help from the
> debian-java team?
> 
> Kind regards
> 
>   Andreas.


This issue is caused by the removal of tools.jar in OpenJDK 9. In
debian/rules you can remove this line:

CMAKE_OPTS += -DJava_JAVADOC_JAR=$(JDK_PATH)/lib/tools.jar
-DJAVA_INCLUDE_PATH=$(JAVA_INCLUDE_PATH)

and then you should patch docs/CMakeLists.txt and remove this line:

if (NOT EXISTS "${Java_JAVADOC_JAR}")
  message(FATAL_ERROR "Cannot generate java documentation, please
specify the Java_JAVADOC_JAR.")
endif()

This will work around the FTBFS because tools.jar is "only" needed on
the classpath when building the documentation. The build succeeds
afterwards but there might be some documentation for classes missing
which were provided by tools.jar. I would report this as an upstream bug.

Regards,

Markus



signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#893242: python-pygit2 FTBFS with dh-python 3.20180313

[Debian Bug Tracking System]

Processing control commands:

> severity 893242 normal
Bug #893242 [dh-python] python-pygit2 FTBFS with dh-python 3.20180313
Severity set to 'normal' from 'serious'
> tags 893242 + wontfix
Bug #893242 [dh-python] python-pygit2 FTBFS with dh-python 3.20180313
Added tag(s) wontfix.

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

Bug#893242: python-pygit2 FTBFS with dh-python 3.20180313

[Piotr Ożarowski]

Control: severity 893242 normal
Control: tags 893242 + wontfix

>   File "/usr/lib/python3.6/unittest/loader.py", line 451, in _find_test_path
> msg % (mod_name, module_dir, expected_dir))
> ImportError: 'test_archive' module incorrectly imported from 
> '/build/1st/python-pygit2-0.26.3/.pybuild/cpython3_3.6_pygit2/build/test'. 
> Expected '/build/1st/python-pygit2-0.26.3/test'. Is this module globally 
> installed?

I change the current directory to the build directory on purpose. I want
to test files that will be installed in the package, not the source
files and that's what happens if you start tests from source dir (due to
Python's "." in sys.path).

I'm amazed that even stdlib enforces such insane setting...

PS note that previous version of dh-python/pybuild also used build dir
as current directory

Processed: bug 893251 is not forwarded

[Debian Bug Tracking System]

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

> notforwarded 893251
Bug #893251 [jabref] jabref: doesn't start with liblog4j2-java 2.10.0-1
Unset Bug forwarded-to-address
> thanks
Stopping processing here.

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

Processed: Re: Bug#893353: libinline-java-perl FTBFS with openjdk-9

[Debian Bug Tracking System]

Processing control commands:

> tag -1 + fixed-upstream
Bug #893353 [src:libinline-java-perl] libinline-java-perl FTBFS with openjdk-9
Added tag(s) fixed-upstream.

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

Bug#893353: libinline-java-perl FTBFS with openjdk-9

[gregor herrmann]

Control: tag -1 + fixed-upstream

On Sun, 18 Mar 2018 10:14:10 +0200, Adrian Bunk wrote:

> Source: libinline-java-perl
> Version: 0.58~dfsg-3
> Severity: serious
> 
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libinline-java-perl.html
> 
> ...
> Test Summary Report
> ---
> t/04_members.t   (Wstat: 6400 Tests: 18 Failed: 0)
>   Non-zero exit status: 25
>   Parse errors: Bad plan.  You planned 28 tests but ran 18.
> t/05_arrays.t(Wstat: 6400 Tests: 24 Failed: 1)
>   Failed test:  24
>   Non-zero exit status: 25
>   Parse errors: Bad plan.  You planned 55 tests but ran 24.
> t/12_1_callbacks.t   (Wstat: 6400 Tests: 17 Failed: 0)
>   Non-zero exit status: 25
>   Parse errors: Bad plan.  You planned 37 tests but ran 17.
> Files=20, Tests=287, 314 wallclock secs ( 1.92 usr  1.31 sys + 374.44 cusr 
> 121.68 csys = 499.35 CPU)
> Result: FAIL
> Failed 3/20 test programs. 1/287 subtests failed.
> make[1]: *** [Makefile:918: test_dynamic] Error 255

According to the upstream Changes, this is supposed to be fixed in
0.61.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Red Hot Chili Peppers: Road Trippin'


signature.asc
Description: Digital Signature

Bug#893369: systemd-udevd is killed at startup

[Michael Biebl]

On Sun, 18 Mar 2018 12:14:41 +0100 =?utf-8?q?Micka=C3=ABl_Leduque?=
 wrote:
> Package: systemd
> Version: 238-2
> Severity: critical
> Justification: breaks the whole system
> 
> Dear Maintainer,
> 
> After an update and a restart of the system, boot fails. It enters a loop, 
> where (apparently) systemd-udevd fails to start and is retries for a certain 
> time.
> After thaat, I am dropped into recovery mode (or failsafe, I don't remember 
> the word).
> I tried investigating the logs, but I couldn't go very far, I just saw 
> something that may (or may nt) be related, seccomp logs about systemd-udevd 
> using a syscall
> but that's an "audit" log so I'm not sure it does anyhting at all.

See https://freedesktop.org/wiki/Software/systemd/Debugging/
"If You Can Get a Shell", and attach the journalctl output of such a boot.
Since this affects udev, please also consider adding
udev.log_priority=debug to the kernel command line (see man
kernel-command-line)

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Bug#890563: marked as done (quagga: CVE-2018-5378 CVE-2018-5379 CVE-2018-5380 CVE-2018-5381)

[Debian Bug Tracking System]

Your message dated Sun, 18 Mar 2018 15:49:59 +
with message-id 
and subject line Bug#890563: fixed in quagga 1.2.4-1
has caused the Debian Bug report #890563,
regarding quagga: CVE-2018-5378 CVE-2018-5379 CVE-2018-5380 CVE-2018-5381
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.)


-- 
890563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: quagga
Version: 1.1.1-1
Severity: serious
Tags: security upstream fixed-upstream
Justification: security update done via DSA-4115-1; regression from stable

Hi,

the following vulnerabilities were published for quagga.

CVE-2018-5378[0]:
invalid attr length sends NOTIFY with data overrun

CVE-2018-5379[1]:
Fix double free of unknown attribute

CVE-2018-5380[2]:
debug print of received NOTIFY data can over-read msg array

CVE-2018-5381[3]:
fix infinite loop on certain invalid OPEN messages

See [4] for the announcement.

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-5378
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5378
[1] https://security-tracker.debian.org/tracker/CVE-2018-5379
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5379
[2] https://security-tracker.debian.org/tracker/CVE-2018-5380
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5380
[3] https://security-tracker.debian.org/tracker/CVE-2018-5381
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5381
[4] https://savannah.nongnu.org/forum/forum.php?forum_id=9095

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: quagga
Source-Version: 1.2.4-1

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

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

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 17 Mar 2018 15:33:00 +
Source: quagga
Binary: quagga quagga-core quagga-doc quagga-bgpd quagga-isisd quagga-ospf6d 
quagga-ospfd quagga-pimd quagga-ripd quagga-ripngd
Architecture: source
Version: 1.2.4-1
Distribution: unstable
Urgency: medium
Maintainer: Brett Parker 
Changed-By: Brett Parker 
Description:
 quagga - network routing daemons (metapackage)
 quagga-bgpd - BGP4/BGP4+ routing daemon
 quagga-core - network routing daemons (core abstraction layer)
 quagga-doc - network routing daemons (documentation)
 quagga-isisd - IS-IS routing daemon
 quagga-ospf6d - OSPF6 routing daemon
 quagga-ospfd - OSPF routing daemon
 quagga-pimd - PIM routing daemon
 quagga-ripd - RIPv1 routing daemon
 quagga-ripngd - RIPng routing daemon
Closes: 884919 890563
Changes:
 quagga (1.2.4-1) unstable; urgency=medium
 .
   * New maintainer (Closes: #884919)
   * New upstream release (Closes: #890563)
 - Fixes CVE-2018-5278
 - Fixes CVE-2018-5279
 - Fixes CVE-2018-5280
 - Fixes CVE-2018-5281
Checksums-Sha1:
 ab5e6e27ad132f022a4e1375b59bf75dfe9be878 2581 quagga_1.2.4-1.dsc
 bc891de7c979fb04d14fc74a5f5da9c42192660c 2937122 quagga_1.2.4.orig.tar.gz
 551cb16e6a73c84b7174e127809c19511cf2cb6e 28364 quagga_1.2.4-1.debian.tar.xz
 0d16588066a7d003d91d0b145a0793cf918cdcac 10125 quagga_1.2.4-1_source.buildinfo
Checksums-Sha256:
 d68931487c8a92710eacfbc50b635a092e766533db3021e5c42d447f709ebdf6 2581 
quagga_1.2.4-1.dsc
 4d1b28f215c661deab421c744b0502aadeac90b3497db3bf2bf454fcf339281f 2937122 
quagga_1.2.4.orig.tar.gz
 e2c518efc6a30158056d81c9e3ff37941642a974c2b1f3523473909eac9c722e 28364 
quagga_1.2.4-1.debian.tar.xz
 f79cf3511494dd95ae7c2b9287de6b4b876c650e87137627ac7f9fa08d60fd5c 10125 
quagga_1.2.4-1_source.buildinfo
Files:
 e7e806d1a1c8ab93364ee18bca814962 2581 net optional quagga_1.2.4-1.dsc