Bug#773805: liblucene4-java: Incomplete poms installed in /usr/share/maven-repo

2015-01-07 Thread tony mancill
On 12/23/2014 08:55 PM, Hilko Bengen wrote:
 * Emmanuel Bourg:
 
 Package: liblucene4-java
 Version: 1:4.6.1+dfsg-2
 Severity: serious

 The liblucene4-java package installs dummy pom.xml files in 
 /usr/share/maven-repo
 which are missing important information to be usable by other packages.
 
 Emmanuel,
 
 thank you for finding and reporting the problem. I cannot fix and upload
 this at the moment.
 
 So, I'd be grateful if you (or anyone else) could make an upload to fix
 this,


Hello Hilko, Emmanuel,

I'm taking a look at this, but in the interest of the jessie release, I
wanted to ask Emmanuel whether it would be okay to decrease the severity.

We have a number of other packages with missing or incomplete poms, and
propose that we discuss maven metadata for all Java library packages as
a release goal for jessie + 1.

Otherwise, the package will be removed soonish (February 5th).

https://tracker.debian.org/pkg/lucene4

Thanks,
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#773805: liblucene4-java: Incomplete poms installed in /usr/share/maven-repo

2015-01-07 Thread Emmanuel Bourg
Le 08/01/2015 07:41, Niels Thykier a écrit :

 If the bug only prevents new packages from being build (i.e. packages
 not already in Jessie/sid), it /sounds/ like it might not be RC after
 all (maybe important).  However, please keep in mind that my answer is
 solely based on the above mail.

You are right, let's decrease the severity.

Emmanuel

__
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#773805: liblucene4-java: Incomplete poms installed in /usr/share/maven-repo

2015-01-07 Thread Niels Thykier
On 2015-01-08 05:17, tony mancill wrote:
 [...]
 
 
 Hello Hilko, Emmanuel,
 
 I'm taking a look at this, but in the interest of the jessie release, I
 wanted to ask Emmanuel whether it would be okay to decrease the severity.
 
 We have a number of other packages with missing or incomplete poms, and
 propose that we discuss maven metadata for all Java library packages as
 a release goal for jessie + 1.
 
 Otherwise, the package will be removed soonish (February 5th).
 
 https://tracker.debian.org/pkg/lucene4
 
 Thanks,
 tony
 
 [...]

Hi,

If the bug is RC on its own, but you believe it is irrelevant for the
Jessie release, the correct option would be to have it ignored (please
file a bug against release.debian.org for that).
  Mind you, the assumption is that the bug is in fact RC.  If not, the
release team will probably recommend downgrading it instead.

If the bug only prevents new packages from being build (i.e. packages
not already in Jessie/sid), it /sounds/ like it might not be RC after
all (maybe important).  However, please keep in mind that my answer is
solely based on the above mail.

Thanks,
~Niels

__
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#746017: /usr/share/maven/man is good when 2 packages have same man.

2015-01-07 Thread Oleksandr Gavenko
During movement from maven2 to maven3 it is not possible to store 2 man
page at same location.

For this purpose used Debian alternatives:

  desktop+bash# ls -l /usr/share/man/man1/mvn*
  lrwxrwxrwx 1 root root 26 2013-10-05 18:33 /usr/share/man/man1/mvn.1.gz - 
/etc/alternatives/mvn.1.gz
  lrwxrwxrwx 1 root root 31 2013-10-05 18:33 /usr/share/man/man1/mvnDebug.1.gz 
- /etc/alternatives/mvnDebug.1.gz

This bug may be closed.

-- 
Best regards!

__
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#677989: Where is mainstream for bash-completion?

2015-01-07 Thread Oleksandr Gavenko
 When I type mvn dependency:resolve -D and
 press tab, I get an error message bash: -D: command not found.

I already provide fix for that:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?archive=yesbug=688696

But I debug only one case.

Just grep:

  $ grep -C 1 '^[[:blank:]]*-D' /etc/bash_completion.d/maven

  551-__mvncomp archetypeArtifactId= archetypeCatalog= archetypeGroupId= 
archetypeRepository= archetypeVersion= basedir= goals= interactiveMode= \
  552:-D ${cur}
  553-}
  --
  581-overWriteReleases=true overWriteSnapshots=true 
silent=true type= 
  582:-D ${cur}
  583-;;
  --
  598-$(__mvnlist_prefix 'resolutionFuzziness=' 
${fuzziness}) 
  599:-D ${cur}
  600-;;
  --
  629-$(__mvnlist_prefix 'tokens=' ${tokens}) 
  630:-D ${cur}
  631-;;

All those lines incorrect except first (which is my fix - continuation of
command by escaping \ new-line).

Header say that script author is:

  # Copyright (C) 2009, Ludovic Claude ludovic.cla...@laposte.net

Where is origin/mainstream of this bash-completion script?

I already do some local improvements based on Debian variant like adding new
options and handling completion based on pom.xml content.

Do package maintainer have interest in improvements and fixed?

Fill free to contact me - gaven...@gmail.com

-- 
Best regards!

__
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.