maven-javadoc-plugin 3.0.0-2 MIGRATED to testing

[Debian testing watch]

FYI: The status of the maven-javadoc-plugin source package
in Debian's testing distribution has changed.

  Previous version: 3.0.0-1
  Current version:  3.0.0-2

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

jetty9 9.2.23-1 MIGRATED to testing

[Debian testing watch]

FYI: The status of the jetty9 source package
in Debian's testing distribution has changed.

  Previous version: 9.2.22-3
  Current version:  9.2.23-1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Re: Proposed (lib)curl switch to openssl 1.1

[Alessandro Ghedini]

On Sat, Dec 02, 2017 at 06:09:39PM +0100, Julien Cristau wrote:
> On Thu, Nov 23, 2017 at 15:49:26 +, Ian Jackson wrote:
> > Reasons I am aware that it *might* be a bad idea are:
> > 
> > 1. libcurl exposes parts of the openssl ABI, via
> >CURLOPT_SSL_CTX_FUNCTION, and this would be an implicit ABI break
> >without libcurl soname change.  This is not good, but it seems like
> >the alternative would be to diverge our soname from everyone else's
> >for the same libcurl.
> > 
> > 2. For the reason just mentioned, it might be a good idea to put in a
> >Breaks against old versions of packages using
> >CURLOPT_SSL_CTX_FUNCTION.  However, (a) I am not sure if this is
> >actually necessary (b) in any case I don't have a good list of all
> >the appropriate versions (c) maybe this would need coordination.
> > 
> > 3. This might be an implicit a "transition" (in the Debian release
> >management sense) which I would be mishandling, or starting without
> >permission, or something.
> > 
> Because of 1 I think we should change the package name (and SONAME) for
> libcurl3.  I don't think 2 is appropriate.

Following discussion on the ticket (#858398) it was suggested to follow the
strategy used for the GCC 5 C++ ABI transition, that is, rename the libcurl
package and add Conflicts+Replaces for teh old package.

Due to the fact that the previous transition (libcurl3 -> libcurl4) was
partially reverted (in 2007 according to the changelog), I'd also like to
taeke this opportunity to finally complete that as well, so I made a patch
to not only rename libcurl3 -> libcurl4, but also (libcurl3-gnutls,
libcurl3-nss) -> (libcurl4-gnutls, libcurl4-nss), and remove the hacks needed
to keep compatibility with the previous ABI.

Thoughts?

The patch is at https://salsa.debian.org/debian/curl/merge_requests/2

CHeers


signature.asc
Description: PGP signature
__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#878971: [libjaxb-java] libjaxb-java cause guacamole start fail

[Takuya Ono]

I am testing libjaxb-java 2.3.0-3. Recently, jaxb-impl.jar was divided
into jaxb-runtime.jar and jaxb-core.jar. And, jaxb-impl.jar just
symbolic link to jaxb-runtime.jar. But, it does not include jaxb-core.jar.
The other hand, guacamole 0.9.9 reference only jaxb-impl.jar.

Workaround:
Make symbolic link to jaxb-core.jar on
/usr/share/guacamole/guacamole/WEB-INF/lib/.

Example:
root:/usr/share/guacamole/guacamole/WEB-INF/lib# ln -s
../../../../java/jaxb-core.jar

> How shoud we resolve this problem? change libjaxb-java or guacmole?

I believe that the root cause is libjaxb-java's specification change.

Ref: We discussed on my blog. http://on-o.com/page/diary/20171009.html
(Japanese)
--
Takuya Ono  

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#886875: maven-archiver FTBFS: test failure

[Adrian Bunk]

Source: maven-archiver
Version: 3.2.0-1
Severity: serious

https://buildd.debian.org/status/fetch.php?pkg=maven-archiver=all=3.2.0-1=1515540053=0

...
[INFO] ---
[INFO]  T E S T S
[INFO] ---
[INFO] Running org.apache.maven.archiver.MavenArchiverTest
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy-defaults.jar
[INFO] Building jar: /<>/target/test/dummy-explicit-simple.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: 
/<>/target/test/dummy-custom-layout-repo-non-unique.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummyWithDashes.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy-custom-layout-simple.jar
[INFO] Building jar: /<>/target/test/dummy-custom-layout-repo.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: 
/<>/target/test/dummy-custom-layout-simple-non-unique.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[INFO] Building jar: /<>/target/test/dummy.jar
[ERROR] Tests run: 27, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.464 
s <<< FAILURE! - in org.apache.maven.archiver.MavenArchiverTest
[ERROR] testRecreation(org.apache.maven.archiver.MavenArchiverTest)  Time 
elapsed: 0.382 s  <<< FAILURE!
java.lang.AssertionError: expected:<1515540046000> but was:<1515539986000>
at 
org.apache.maven.archiver.MavenArchiverTest.testRecreation(MavenArchiverTest.java:248)

[INFO] Running org.apache.maven.archiver.MavenArchiveConfigurationTest
[INFO] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 s - in 
org.apache.maven.archiver.MavenArchiveConfigurationTest
[INFO] Running org.apache.maven.archiver.ManifestConfigurationTest
[INFO] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 s 
- in org.apache.maven.archiver.ManifestConfigurationTest
[INFO] 
[INFO] Results:
[INFO] 
[ERROR] Failures: 
[ERROR]   MavenArchiverTest.testRecreation:248 expected:<1515540046000> but 
was:<1515539986000>
[INFO] 
[ERROR] Tests run: 34, Failures: 1, Errors: 0, Skipped: 0
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 4.620 s
[INFO] Finished at: 2018-01-09T23:20:48Z
[INFO] Final Memory: 9M/217M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test (default-test) on 
project maven-archiver: There are test failures.
[ERROR] 
[ERROR] Please refer to /<>/target/surefire-reports for the 
individual test results.
[ERROR] Please refer to dump files (if any exist) [date]-jvmRun[N].dump, 
[date].dumpstream and [date]-jvmRun[N].dumpstream.
[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_test: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo --batch-mode test 
returned exit code 1
debian/rules:4: recipe for target 'build-indep' faile

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.