Bug#769526: xlshlt: xslhlt should use configuration file provided by package by default
Hi and thank you for your bug report! I examined the patch and have a
question about it.
What is the purpose of } else if (new
File(xslthl-config.xml).isFile()) {? As far as I understand it will
always be true. What did I miss?
I would only change
configFilename = xslthl-config.xml;
to
configFilename = /usr/share/xslthl/highlighters/xslthl-config.xml;
__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers.
Please use
debian-j...@lists.debian.org for discussions and questions.
Bug#769526: xlshlt: xslhlt should use configuration file provided by package by default
On 2014-11-16 10:54, Eugene Zhukov wrote:
Hi and thank you for your bug report! I examined the patch and have a
question about it.
What is the purpose of } else if (new
File(xslthl-config.xml).isFile()) {? As far as I understand it will
always be true. What did I miss?
I would only change
configFilename = xslthl-config.xml;
to
configFilename = /usr/share/xslthl/highlighters/xslthl-config.xml;
__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers.
Please use
debian-j...@lists.debian.org for discussions and questions.
Hi,
I suppose the purpose of the } else if(new File(...) is to keep the
current behaviour of using ./xslthl-config.xml if it exists (in
preference to the global one).
On a related note, if xslthl-config.xml is a file that the end user
might want to change (i.e. it contains configuration), then the Debian
package should look for it in /etc (possibly falling back to the
/usr/share one if the /etc variant does not exist).
~Niels
Ref: https://www.debian.org/doc/debian-policy/ch-files.html#s-config-files
__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers.
Please use
debian-j...@lists.debian.org for discussions and questions.
Bug#767541: jenkins: CVE-2014-3665
Hi from the Paris Bugs Squashing Party :) In order to help people who participate, can you (jenkins' maintainer) describe what you intend to do, and if help is possible? From what I understand: - The security ~fix is a new slave-master access control system - Jenkins releases a LTS version every 3 months - Debian currently doesn't ship the current LTS from last month, but the one before, which doesn't seem supported anymore. - Options that I see are either pushing the current LTS in Debian, backporting the new access control system, or drop the package. Let us know what is your suggested course of action. Cheers! Sylvain __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#767541: jenkins: CVE-2014-3665
Hi Sylvain, Le 16/11/2014 11:26, b...@debian.org a écrit : Hi from the Paris Bugs Squashing Party :) Thank you for helping! In order to help people who participate, can you (jenkins' maintainer) describe what you intend to do, and if help is possible? - The security ~fix is a new slave-master access control system - Jenkins releases a LTS version every 3 months - Debian currently doesn't ship the current LTS from last month, but the one before, which doesn't seem supported anymore. - Options that I see are either pushing the current LTS in Debian, backporting the new access control system, or drop the package. Let us know what is your suggested course of action. The new LTS is probably too big to be pushed to testing now. As an alternative I'm considering either disabling the master/slave mechanism, or adding a big red warning in the UI to inform the user about the risks. Emmanuel Bourg __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Processed: tagging 764630
Processing commands for cont...@bugs.debian.org: tags 764630 - moreinfo Bug #764630 [jarwrapper] missing JNI multi-arch PATHs in jarwrapper Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 764630: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764630 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Processed: block 768671 with 769358
Processing commands for cont...@bugs.debian.org: block 768671 with 769358 Bug #768671 [src:jenkins] jenkins: FTBFS in jessie: build-dependency not installable: libjson-java 768671 was blocked by: 721072 768671 was not blocking any bugs. Added blocking bug(s) of 768671: 769358 thanks Stopping processing here. Please contact me if you need assistance. -- 768671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#769804: jarjar-maven-plugin: FTBFS against rebuilt packages: Failed to resolve artifact ant
Source: jarjar-maven-plugin Version: 1.9-2 Severity: important In my locally rebuilt repository, ant is no longer automatically pulled in by the Build-Depends of jarjar-maven-plugin (with the official package builds, it's pulled in by velocity). As a result, I'm getting this error in the build: ... cd . /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven2/boot/classworlds.jar:/usr/lib/jvm/default-java/lib/tools.jar -Dproperties.file.manual=/tmp/buildd/jarjar-maven-plugin-1.9/debian/maven.properties -Dclassworlds.conf=/etc/maven2/m2-debian.conf org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml -Dmaven.repo.local=/tmp/buildd/jarjar-maven-plugin-1.9/debian/maven-repo package [INFO] NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] Scanning for projects... [INFO] [INFO] Building JarJar Maven Plugin [INFO]task-segment: [package] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.ant:ant:jar:debian Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.ant -DartifactId=ant -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.ant -DartifactId=ant -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.sonatype.plugins:jarjar-maven-plugin:maven-plugin:1.9 2) org.apache.ant:ant:jar:debian -- 1 required artifact is missing. for artifact: org.sonatype.plugins:jarjar-maven-plugin:maven-plugin:1.9 from the specified remote repositories: central (http://repo1.maven.org/maven2) NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Tue Nov 11 18:19:57 UTC 2014 [INFO] Final Memory: 7M/149M [INFO] /usr/share/cdbs/1/class/maven.mk:87: recipe for target 'mvn-build' failed make: *** [mvn-build] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 (I've verified that pbuilder build velocity using all official packages results in a package with Depends: libcommons-collections3-java, libcommons-lang-java (= 2.6). If that's incorrect, feel free to correct the issue in maven-debian-helper and then close this bug.) -- Daniel Schepler __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#769804: jarjar-maven-plugin: FTBFS against rebuilt packages: Failed to resolve artifact ant
Hi Daniel, As I understand ant is pulled through maven-debian-helper-velocity-ant. How did you manage to install the build dependencies without ant installed? Ant is a direct dependency so it would be a good idea to add it to the build deps, but this error should not happen with the current dependency graph. Emmanuel Bourg __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#769804: jarjar-maven-plugin: FTBFS against rebuilt packages: Failed to resolve artifact ant
On 11/16/2014 09:53 AM, Emmanuel Bourg wrote: Hi Daniel, As I understand ant is pulled through maven-debian-helper-velocity-ant. How did you manage to install the build dependencies without ant installed? Ant is a direct dependency so it would be a good idea to add it to the build deps, but this error should not happen with the current dependency graph. Hi Emmanuel, I believe what Daniel is saying is that if you rebuild the entire dependency chain, ant isn't being pulled in (by velocity). Or put another way, there is a difference between the dependency graph that exists for the binary build-deps in the archive, and the dependency graph created by rebuilding all of the build-deps in the archive from source. Daniel, first, do I have that right, and secondly, is your rebuild on jessie or sid? In any event, no harm in adding ant directly, although it would be good to determine if this is a class of FTBFS bugs instead of an isolated instance. E.g., there may be other packages that were expecting velocity to pull in ant. (Theoretically, because I haven't looked into it, but velocity appears to be long overdue for some freshening...) Cheers, tony signature.asc Description: OpenPGP digital signature __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#769831: [testng] Some sources are not included in your package
Package: testng Version: 6.8.8-2 user: lintian-ma...@debian.org usertags: source-is-missing severity: serious X-Debbugs-CC: ftpmas...@debian.org Hi, Your package seems to include some files that lack sources in prefered forms of modification: src/main/resources/jquery-1.7.1.min.js According to Debian Free Software Guidelines [1] (DFSG) #2: The program must include source code, and must allow distribution in source code as well as compiled form.. This could also constitute a license violation for some copyleft licenses such as the GNU GPL. In order to solve this problem, you could: 1. repack the origin tarball adding the missing source to it. 2 add the source files to debian/missing-sources directory Both way satisfies the requirement that we ship the source. Second option might be preferable due to the following reasons [2]: - Upstream can do it too and you could even supply a patch to them, thus full filling our social contract [3], see particularly §2. - If source and non-source are in different locations, ftpmasters may miss the source and (needlessly) reject the package. - The source isn't duplicated in every .diff.gz/.debian.tar.* (though this only really matters for larger sources). You could also ask debian...@lists.debian.org or #debian-qa for more guidance. Waiting for next upstream release is not sufficient. [1] https://www.debian.org/social_contract.en.html#guidelines [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=736873#8 [3] https://www.debian.org/social_contract __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#769804: jarjar-maven-plugin: FTBFS against rebuilt packages: Failed to resolve artifact ant
Daniel confirmed privately he rebuilt velocity locally. The pom.xml file in velocity has a dependency on ant with the scope 'provided'. The recent versions of maven-debian-helper no longer inject this kind of dependencies in the package dependencies (because the provided dependencies are usually satisfied at runtime by a container. This is typical with the dependencies on the Servlet and the OSGi APIs). So here the rebuilt velocity package lacks the dependency on ant and breaks jarjar-maven-plugin. Thank you for spotting this issue Daniel. I'm going to add the missing build dependency on Ant. __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Processing of jarjar-maven-plugin_1.9-3_amd64.changes
jarjar-maven-plugin_1.9-3_amd64.changes uploaded successfully to localhost along with the files: jarjar-maven-plugin_1.9-3.dsc jarjar-maven-plugin_1.9-3.debian.tar.xz libjarjar-maven-plugin-java_1.9-3_all.deb libjarjar-maven-plugin-java-doc_1.9-3_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
jarjar-maven-plugin_1.9-3_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 17 Nov 2014 00:09:39 +0100 Source: jarjar-maven-plugin Binary: libjarjar-maven-plugin-java libjarjar-maven-plugin-java-doc Architecture: source all Version: 1.9-3 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers pkg-java-maintainers@lists.alioth.debian.org Changed-By: Emmanuel Bourg ebo...@apache.org Description: libjarjar-maven-plugin-java - Maven plugin to repackage third-party jars libjarjar-maven-plugin-java-doc - Maven plugin to repackage third-party jars - documentation Closes: 769804 Changes: jarjar-maven-plugin (1.9-3) unstable; urgency=medium . * debian/control: - Added an explicit build dependency on ant (Closes: #769804) - Standards-Version updated to 3.9.6 (no changes) Checksums-Sha1: 660a9ea645ee006f3c8c242ba4daf61190eb4b1d 2500 jarjar-maven-plugin_1.9-3.dsc 50c2cfee35882994c4f6c35a251f6c16857ed1aa 3832 jarjar-maven-plugin_1.9-3.debian.tar.xz 9ee0216aa40b553224beecb6b6e0b086799de130 65566 libjarjar-maven-plugin-java_1.9-3_all.deb 4b1bc4ec2f18f7f5bb710178f0158a86f9e169bd 189126 libjarjar-maven-plugin-java-doc_1.9-3_all.deb Checksums-Sha256: 6bcec01dadfc573ca9c53220fbada93caccfd64561be92167ccdc54c8b2a516e 2500 jarjar-maven-plugin_1.9-3.dsc 9a067498d371e55a7569b104c5e9cdf607af1eb82559c5bdb231d4e920996d3d 3832 jarjar-maven-plugin_1.9-3.debian.tar.xz 2c7481aa2599cdc79a5a976d3aed31647bf8de1cf77506d93d7eaae1860c87a5 65566 libjarjar-maven-plugin-java_1.9-3_all.deb b0034c84388048c1c794c3f80d3df14ffa401d739f3df90f14ea49d4cf3e6b68 189126 libjarjar-maven-plugin-java-doc_1.9-3_all.deb Files: 1b7649197d836ddc02b3f07c650d 2500 java optional jarjar-maven-plugin_1.9-3.dsc b4d9593357795d7a30735d5b35f7eb21 3832 java optional jarjar-maven-plugin_1.9-3.debian.tar.xz 860c582da004c45bc93cb8ab0b89697a 65566 java optional libjarjar-maven-plugin-java_1.9-3_all.deb 570ad3c87fc2c8ccd5157aee458b0d1d 189126 doc optional libjarjar-maven-plugin-java-doc_1.9-3_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJUaTDtAAoJEPUTxBnkudCs19YQAJlpDY6hLDGypbFIVK6Od6xA gERAp5B3qfayj1GOVHBPgKdq48bxpOrB9Emwa9IEfsebnobj+L83xcV63tjFycVu 7jS8ghNmBAT+PuvM8qutp9USYZMxUaDgKZPLpb16rEbRPwE5hBwEbAtpPkMyuO29 FneU3SEYfccxA3yUG+fAmcEU04S85PBOTWmuoGPqDhRY445JzshGW4RHXDYh2Mxx DFw+d+iK9Xs+M+FZixrqJ5Bjr0cBqYsosTprRdT5zgKlk9IuHGJo6SWt3dZra5Bc nw6TV+UgfQchCh/R7tJ0XgKiB+i4YagY2LlUjnTFw305qSxEXtEXqsbSTsYA2fL0 i8QleTQclysGUHOcmbgKzfNjZP1YfP1ul9pOu1CDMoqPnvARmdU/TJEOzULHhke5 fIGK433KIlvhc4+lLNqvNmfIKUH84Whs3dgdfFZvdUlcbWqMqnIALmfvnUVPK5zw FM8E7P6QzrHMZDBPC0lErCV5zKLvDwt+nHy/Ph0ilw0XqZtFZF2eaXyco8UF3VoM 3nA0xXYiuU+DpG5ld4p3NORqbPidtZYWcfzMYInf2KjLQ7wIHhqhNfGbMQh44xOI Dqx1JJK/d88dmiaeh8N+cwaafzULmq2pXLaHUbbTf1Xwg30k/bgHsCS3vudWlezA oZ7P9XylcRohssADsSU/ =OX6F -END PGP SIGNATURE- Thank you for your contribution to Debian. __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Bug#769804: marked as done (jarjar-maven-plugin: FTBFS against rebuilt packages: Failed to resolve artifact ant)
Your message dated Sun, 16 Nov 2014 23:33:41 + with message-id e1xq9k9-0005bf...@franck.debian.org and subject line Bug#769804: fixed in jarjar-maven-plugin 1.9-3 has caused the Debian Bug report #769804, regarding jarjar-maven-plugin: FTBFS against rebuilt packages: Failed to resolve artifact ant 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.) -- 769804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769804 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: jarjar-maven-plugin Version: 1.9-2 Severity: important In my locally rebuilt repository, ant is no longer automatically pulled in by the Build-Depends of jarjar-maven-plugin (with the official package builds, it's pulled in by velocity). As a result, I'm getting this error in the build: ... cd . /usr/lib/jvm/default-java/bin/java -noverify -cp /usr/share/maven2/boot/classworlds.jar:/usr/lib/jvm/default-java/lib/tools.jar -Dproperties.file.manual=/tmp/buildd/jarjar-maven-plugin-1.9/debian/maven.properties -Dclassworlds.conf=/etc/maven2/m2-debian.conf org.codehaus.classworlds.Launcher -s/etc/maven2/settings-debian.xml -Dmaven.repo.local=/tmp/buildd/jarjar-maven-plugin-1.9/debian/maven-repo package [INFO] NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] Scanning for projects... [INFO] [INFO] Building JarJar Maven Plugin [INFO]task-segment: [package] [INFO] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.ant:ant:jar:debian Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.ant -DartifactId=ant -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.ant -DartifactId=ant -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.sonatype.plugins:jarjar-maven-plugin:maven-plugin:1.9 2) org.apache.ant:ant:jar:debian -- 1 required artifact is missing. for artifact: org.sonatype.plugins:jarjar-maven-plugin:maven-plugin:1.9 from the specified remote repositories: central (http://repo1.maven.org/maven2) NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Tue Nov 11 18:19:57 UTC 2014 [INFO] Final Memory: 7M/149M [INFO] /usr/share/cdbs/1/class/maven.mk:87: recipe for target 'mvn-build' failed make: *** [mvn-build] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 (I've verified that pbuilder build velocity using all official packages results in a package with Depends: libcommons-collections3-java, libcommons-lang-java (= 2.6). If that's incorrect, feel free to correct the issue in maven-debian-helper and then close this bug.) -- Daniel Schepler ---End Message--- ---BeginMessage--- Source: jarjar-maven-plugin Source-Version: 1.9-3 We believe that the bug you reported is fixed in the latest version of jarjar-maven-plugin, 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 769...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Emmanuel Bourg ebo...@apache.org (supplier of updated jarjar-maven-plugin 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: SHA1 Format: 1.8 Date: Mon, 17 Nov 2014
Bug#769804: jarjar-maven-plugin: FTBFS against rebuilt packages: Failed to resolve artifact ant
On Sun, Nov 16, 2014 at 11:26 AM, tony mancill tmanc...@debian.org wrote: I believe what Daniel is saying is that if you rebuild the entire dependency chain, ant isn't being pulled in (by velocity). That's correct. Or put another way, there is a difference between the dependency graph that exists for the binary build-deps in the archive, and the dependency graph created by rebuilding all of the build-deps in the archive from source. Daniel, first, do I have that right, and secondly, is your rebuild on jessie or sid? The rebuild is based on sid. By the way, after I built maven-jarjar-plugin with ant added, I got a similar failure building sisu-guice: [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.ant:ant:jar:debian Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.ant -DartifactId=ant -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.ant -DartifactId=ant -Dversion=debian -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.sonatype.plugins:jarjar-maven-plugin:maven-plugin:1.9 2) org.apache.ant:ant:jar:debian -- 1 required artifact is missing. for artifact: org.sonatype.plugins:jarjar-maven-plugin:maven-plugin:1.9 from the specified remote repositories: central (http://repo1.maven.org/maven2) NOTE: Maven is executing in offline mode. Any artifacts not already in your local repository will be inaccessible. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 4 seconds [INFO] Finished at: Sun Nov 16 22:29:05 UTC 2014 [INFO] Final Memory: 17M/344M [INFO] /usr/share/cdbs/1/class/maven.mk:87: recipe for target 'mvn-build' failed make: *** [mvn-build] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2 I'm not sure why that's happening, given that as far as I can tell, the dependency on ant is marked as optional in jarjar-maven-plugin's pom.xml file. -- Daniel Schepler __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
Processing of jackson-datatype-guava_2.4.2+dfsg-1_amd64.changes
jackson-datatype-guava_2.4.2+dfsg-1_amd64.changes uploaded successfully to localhost along with the files: jackson-datatype-guava_2.4.2+dfsg-1.dsc jackson-datatype-guava_2.4.2+dfsg.orig.tar.gz jackson-datatype-guava_2.4.2+dfsg-1.debian.tar.xz libjackson2-datatype-guava-java_2.4.2+dfsg-1_all.deb libjackson2-datatype-guava-java-doc_2.4.2+dfsg-1_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
jackson-datatype-guava_2.4.2+dfsg-1_amd64.changes is NEW
binary:libjackson2-datatype-guava-java is NEW. binary:libjackson2-datatype-guava-java-doc is NEW. source:jackson-datatype-guava is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will recieve an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html __ This is the maintainer address of Debian's Java team http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. Please use debian-j...@lists.debian.org for discussions and questions.
