Groups > linux.debian.maint.java > #13083

Heads up: broken OSGi Bundle-version in debian package jar file MANIFEST.MF

Path	csiph.com!weretis.net!feeder8.news.weretis.net!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod
From	Steinar Bang <sb@dod.no>
Newsgroups	linux.debian.maint.java
Subject	Heads up: broken OSGi Bundle-version in debian package jar file MANIFEST.MF
Date	Sun, 19 Oct 2025 10:10:01 +0200
Message-ID	<LHwEh-6jUF-1@gated-at.bofh.it> (permalink)
X-Original-To	debian-java@lists.debian.org
X-Mailbox-Line	From debian-java-request@lists.debian.org Sun Oct 19 08:00:44 2025
Old-Return-Path	<glddj-debian-java-2@m.gmane-mx.org>
X-Amavis-Spam-Status	No, score=-6.997 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001] autolearn=ham autolearn_force=no
X-Policyd-Weight	using cached result; rate: -4.6
X-Injected-Via-Gmane	http://gmane.org/
Mail-Followup-To	debian-java@lists.debian.org
Organization	Probably a good idea
MIME-Version	1.0
Content-Type	text/plain
User-Agent	Gnus/5.13 (Gnus v5.13)
Cancel-Lock	sha1:8Xs8OAL9Fg3xX5RfErh9A5w5O/c=
Mail-Copies-To	never
X-Mailing-List	<debian-java@lists.debian.org> archive/latest/23824
List-ID	<debian-java.lists.debian.org>
List-URL	<https://lists.debian.org/debian-java/>
List-Archive	https://lists.debian.org/msgid-search/87o6q3gw32.fsf@dod.no
Approved	robomod@news.nic.it
Lines	26
Sender	robomod@news.nic.it
X-Original-Date	Sun, 19 Oct 2025 10:00:17 +0200
X-Original-Message-ID	<87o6q3gw32.fsf@dod.no>
Xref	csiph.com linux.debian.maint.java:13083

Show key headers only | View raw

Today I reported the following bug on libasm-java 9.8-1
 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1118387

The problem is that the MANIFEST.MF header Bundle-version looks like
this:
 Bundle-version: 9.8-SNAPSHOT
and this causes the asm jar file to fail when being loaded as an OSGi
bundle.

This indicates two things:
 1. The debian package may not actually be built from the git tag
    matching the release
 2. Whatever creates the OSGi headers of MANIFEST.MF doesn't handle
    SNAPSHOT releases correctly (eg. the apache felix maven-bundle-plugin
    would have created the header "Bundle-version: 9.8.SNAPSHOT" which
    would have loaded correctly in OSGi)

And the reason I'm writing here as well as reporting the bug is that
this could affect other debian java library packages with OSGi headers
in their MANIFEST.MF files.

(It may be that not many others care about OSGi these days... but I
do... :-) )

If someone run into problems trying to fix OSGi headers in debian java
library packages I am willing to assist.

Back to linux.debian.maint.java | Previous | Next — Next in thread | Find similar

Thread

Heads up: broken OSGi Bundle-version in debian package jar file MANIFEST.MF Steinar Bang <sb@dod.no> - 2025-10-19 10:10 +0200
  Re: Heads up: broken OSGi Bundle-version in debian package jar file  MANIFEST.MF Emmanuel Bourg <ebourg@apache.org> - 2025-10-19 12:00 +0200
    Re: Heads up: broken OSGi Bundle-version in debian package jar file MANIFEST.MF Steinar Bang <sb@dod.no> - 2025-10-19 16:50 +0200

csiph-web