excalibur-logkit 2.0-12 MIGRATED to testing

2018-04-02 Thread Debian testing watch
FYI: The status of the excalibur-logkit source package in Debian's testing distribution has changed. Previous version: 2.0-11 Current version: 2.0-12 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

Bug#894522: marked as done (libserializer build depends on java-gcj-compat-dev)

2018-04-02 Thread Debian Bug Tracking System
Your message dated Tue, 03 Apr 2018 03:19:29 + with message-id and subject line Bug#894522: fixed in libserializer 1.1.6-5 has caused the Debian Bug report #894522, regarding libserializer build depends on java-gcj-compat-dev to be marked as done. This

Accepted libserializer 1.1.6-5 (source all) into unstable

2018-04-02 Thread tony mancill
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 02 Apr 2018 18:42:51 -0700 Source: libserializer Binary: libserializer-java Architecture: source all Version: 1.1.6-5 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers

libserializer_1.1.6-5_amd64.changes ACCEPTED into unstable

2018-04-02 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Mon, 02 Apr 2018 18:42:51 -0700 Source: libserializer Binary: libserializer-java Architecture: source all Version: 1.1.6-5 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers

Processing of libserializer_1.1.6-5_amd64.changes

2018-04-02 Thread Debian FTP Masters
libserializer_1.1.6-5_amd64.changes uploaded successfully to localhost along with the files: libserializer_1.1.6-5.dsc libserializer_1.1.6-5.debian.tar.xz libserializer-java_1.1.6-5_all.deb libserializer_1.1.6-5_amd64.buildinfo Greetings, Your Debian queue daemon (running on host

Processed: owner 894522, tagging 894522

2018-04-02 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > owner 894522 tmanc...@debian.org Bug #894522 [src:libserializer] libserializer build depends on java-gcj-compat-dev Owner recorded as tmanc...@debian.org. > tags 894522 + pending Bug #894522 [src:libserializer] libserializer build depends on

Bug#894641: gradle FTBFS: error: BaseDirSelector is not abstract and does not override abstract method isSelected(Resource) in ResourceSelector

2018-04-02 Thread Adrian Bunk
Source: gradle Version: 3.4.1-4 Severity: serious https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gradle.html ... :docs:samples/build/1st/gradle-3.4.1/subprojects/core/src/main/java/org/gradle/api/internal/file/ant/BaseDirSelector.java:22: error: BaseDirSelector is not

[bts-link] source package src:jabref

2018-04-02 Thread bts-link-upstream
# # bts-link upstream status pull for source package src:jabref # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #894293 (http://bugs.debian.org/894293) # Bug title: jabref FTBFS with openjdk-9 #

[Branch ~openjdk/openjdk/openjdk7] Rev 622: openjdk-7 (7u171-2.6.13-1) experimental; urgency=high

2018-04-02 Thread noreply
revno: 622 committer: Matthias Klose branch nick: openjdk7 timestamp: Mon 2018-04-02 11:29:14 +0200 message: openjdk-7 (7u171-2.6.13-1) experimental; urgency=high [ Tiago Stürmer Daitx ] * IcedTea release

[pkg-java] r19331 - trunk/saxonb/debian

2018-04-02 Thread Rene Engelhard
Author: rene Date: 2018-04-02 09:07:24 + (Mon, 02 Apr 2018) New Revision: 19331 Modified: trunk/saxonb/debian/changelog trunk/saxonb/debian/control Log: remove myself from Uploaders: Modified: trunk/saxonb/debian/changelog

[Branch ~openjdk/openjdk/openjdk7] Rev 621: 7u161-2.6.12-1 upload

2018-04-02 Thread noreply
revno: 621 committer: Matthias Klose branch nick: openjdk7 timestamp: Mon 2018-04-02 10:31:46 +0200 message: 7u161-2.6.12-1 upload removed: patches/sec-webrev-8u151-backport-S8006591-backport-for-S8181692.jdk.patch

Bug#893635: does not show up in GNOME's application menus

2018-04-02 Thread Felix Natter
hello Antoine, I have got a reply from xdg from a user who has the same problem: https://lists.freedesktop.org/archives/xdg/2018-April/014010.html So it looks like this might be a GNOME(3) problem (or can you reproduce this with KDE or another desktop?) I think it would make sense to report