Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.java > #11851 > unrolled thread

incomplete manifest in jar files

Back to article view | Back to linux.debian.maint.java

Contents

  incomplete manifest in jar files Sudip Mukherjee <sudipm.mukherjee@gmail.com> - 2020-09-18 13:50 +0200
    Re: incomplete manifest in jar files tony mancill <tmancill@debian.org> - 2020-09-20 00:40 +0200
      Re: incomplete manifest in jar files Sudip Mukherjee <sudipm.mukherjee@gmail.com> - 2020-09-20 02:10 +0200
        Re: incomplete manifest in jar files tony mancill <tmancill@debian.org> - 2020-09-21 06:40 +0200
          Re: incomplete manifest in jar files Sudip Mukherjee <sudipm.mukherjee@gmail.com> - 2020-09-21 22:20 +0200

#11851 — incomplete manifest in jar files

Hi All,

While working on #943552 I faced few problems with manifest files and
as a result I am unable to list them in the bundles.info file.

1) libxml-commons-resolver1.1-java -
  MANIFEST.MF is not complete and not having any Bundle-* informations
in xml-resolver-1.2.jar

2) guava-libraries -
 The manifest file of guava.jar says "Import-Package:
com.google.common.util.concurrent.internal" but for Debian build its
internal as the d/rules files copies it to
guava/src/com/google/common/util/concurrent/ and then builds it, so
there is no external package to import.

Solution: Remove "com.google.common.util.concurrent.internal" from the
list of packages in Import-Package of the manifest file.

3) libcommons-cli-java:
  MANIFEST.MF is not complete and not having any Bundle-* informations
in commons-cli.jar

4) batik:
  a)  MANIFEST.MF is not complete and not having any Bundle-*
informations in batik-i18n.jar
  b) I am getting -
java.lang.NoClassDefFoundError: org/apache/batik/i18n/Localizable
Caused by:
java.lang.ClassNotFoundException: org.apache.batik.i18n.Localizable
cannot be found by org.apache.batik.css_1.12.0

Solution - Add "Require-Bundle: org.apache.batik.i18n" to the manifest
of batik-css.jar

If no-one has any problem with my suggested changes then I can go
ahead and team-upload them. All the changes are only in the
MANIFEST.MF and nothing in the code.


--
Regards
Sudip

[toc] | [next] | [standalone]

#11854

[Multipart message — attachments visible in raw view] — view raw

On Fri, Sep 18, 2020 at 12:40:44PM +0100, Sudip Mukherjee wrote:
> Hi All,
> 
> While working on #943552 I faced few problems with manifest files and
> as a result I am unable to list them in the bundles.info file.
> 
> <--snip-->
> 
> If no-one has any problem with my suggested changes then I can go
> ahead and team-upload them. All the changes are only in the
> MANIFEST.MF and nothing in the code.

Hi Sudip,

Sounds reasonable to me.

Cheers,
tony

[toc] | [prev] | [next] | [standalone]

#11855

On Sat, Sep 19, 2020 at 11:34 PM tony mancill <tmancill@debian.org> wrote:
>
> On Fri, Sep 18, 2020 at 12:40:44PM +0100, Sudip Mukherjee wrote:
> > Hi All,
> >
> > While working on #943552 I faced few problems with manifest files and
> > as a result I am unable to list them in the bundles.info file.
> >
> > <--snip-->
> >
> > If no-one has any problem with my suggested changes then I can go
> > ahead and team-upload them. All the changes are only in the
> > MANIFEST.MF and nothing in the code.
>
> Hi Sudip,
>
> Sounds reasonable to me.

Thanks Tony. And, I have a doubt about another package, maybe you can
tell me about it. I noticed that there was a "lucene" which was
removed when "lucene2" was introduced,  then that was removed and
"lucene4.10" package was added. Now, I am looking at upstream v8.6.2,
so I need to package it as "lucene8" ? And I am mostly puzzled about
why instead of updating the original "lucene" source package, separate
source was packaged for each version? for transition?


-- 
Regards
Sudip

[toc] | [prev] | [next] | [standalone]

#11857

[Multipart message — attachments visible in raw view] — view raw

On Sun, Sep 20, 2020 at 01:01:43AM +0100, Sudip Mukherjee wrote:
> On Sat, Sep 19, 2020 at 11:34 PM tony mancill <tmancill@debian.org> wrote:
> >
> > On Fri, Sep 18, 2020 at 12:40:44PM +0100, Sudip Mukherjee wrote:
> > > Hi All,
> > >
> > > While working on #943552 I faced few problems with manifest files and
> > > as a result I am unable to list them in the bundles.info file.
> > >
> > > <--snip-->
> > >
> > > If no-one has any problem with my suggested changes then I can go
> > > ahead and team-upload them. All the changes are only in the
> > > MANIFEST.MF and nothing in the code.
> >
> > Hi Sudip,
> >
> > Sounds reasonable to me.
> 
> Thanks Tony. And, I have a doubt about another package, maybe you can
> tell me about it. I noticed that there was a "lucene" which was
> removed when "lucene2" was introduced,  then that was removed and
> "lucene4.10" package was added. Now, I am looking at upstream v8.6.2,
> so I need to package it as "lucene8" ? And I am mostly puzzled about
> why instead of updating the original "lucene" source package, separate
> source was packaged for each version? for transition?

Hi Sudip,

Good question.  I don't think it is for transition but probably because
lucene3 and lucene4 aren't API-compatible and we weren't able to port
the packages that depend on them.  (Although I don't recall specifically
and haven't checked.)

You can use japi-compliance-checker or clirr to assess compatibility
between lucene4.10 and version 8.  Maybe we can port forward this time
around.  But I am not familiar with lucene, so maybe it's easier to
introduce a new lucene8 source package.

$ reverse-depends -b liblucene4.10-java
Reverse-Build-Depends
* derby
* h2database
* openjfx
* scilab

$ reverse-depends -b liblucene3-java   
Reverse-Build-Depends
* netbeans
* omegat

Cheers,
tony

[toc] | [prev] | [next] | [standalone]

#11858

Hi Tony,

On Mon, Sep 21, 2020 at 5:35 AM tony mancill <tmancill@debian.org> wrote:
>
> On Sun, Sep 20, 2020 at 01:01:43AM +0100, Sudip Mukherjee wrote:
> > On Sat, Sep 19, 2020 at 11:34 PM tony mancill <tmancill@debian.org> wrote:
> > >
> > > On Fri, Sep 18, 2020 at 12:40:44PM +0100, Sudip Mukherjee wrote:
> > > > Hi All,
> > > >
> > > > While working on #943552 I faced few problems with manifest files and
> > > > as a result I am unable to list them in the bundles.info file.
> > > >
<snip>
>
> You can use japi-compliance-checker or clirr to assess compatibility
> between lucene4.10 and version 8.  Maybe we can port forward this time
> around.  But I am not familiar with lucene, so maybe it's easier to
> introduce a new lucene8 source package.

I was trying lucene8 today, and it seems it will need an update to
carrotsearch-randomizedtesting. That update has changed a class name,
so its breaking the build of all the 4 of its reverse-dependencies. I
have done one of them locally now, but I will check the build of the
reverse-dependencies of this one.  I think I will need to go via the
transition process here and will upload to experimental after checking
all of them. "carrotsearch-randomizedtesting" is not having any
"Uploaders:", any objection in adding my name to it?

lucene8 build fails even after updating
"carrotsearch-randomizedtesting" and next it needs an update to
morfologik-stemming. Not sure if 'andrewsh' is planning it (I think I
will check with him).


-- 
Regards
Sudip

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.java

csiph-web