Dear Maintainer,

The META-INF/MANIFEST.MF file of libbcpg-java contains only the following:

Manifest-Version: 1.0
Ant-Version: Apache Ant 1.10.12
Application-Library-Allowable-Codebase: *
Application-Name: Bouncy Castle OpenPGP API
Automatic-Module-Name: org.bouncycastle.pg
Caller-Allowable-Codebase: *
Class-Path: bcprov.jar
Codebase: *
Created-By: 11.0.15+10-post-Debian-1 (Debian)
Extension-Name: org.bouncycastle.bcpg
Implementation-Vendor: BouncyCastle.org
Implementation-Vendor-Id: org.bouncycastle
Implementation-Version: 1.71.00.0
Permissions: all-permissions
Specification-Vendor: BouncyCastle.org
Specification-Version: 1.1
Trusted-Library: true

Which is incomplete and does not contain all the other required information
like Bundle-Version, Bundle-Name, Export-Package etc. And this lack of information
makes the package unusable when using a SimpleConfigurator based bundles.info file.

But if I see the jar file in the maven repository I can see the manifest file in that
contains all the required information. The jar can be found at:
https://repo1.maven.org/maven2/org/bouncycastle/bcpg-jdk18on/1.71/bcpg-jdk18on-1.71.jar

Control: tags -1 patch
--

<snip>
But Emmanuel Bourg did not agree so I am not doing an upload but keeping
the patch here for record.
Ref: https://lists.debian.org/debian-java/2022/09/msg00002.html

Le 30/10/2022 à 01:31, Sudip Mukherjee a écrit :

My objection was about patching the Eclipse manifests, not Bouncy Castle.

Regarding BC, the question is why the build system doesn't generate the
same OSGi metadata than the ones in Maven Central. Is there a missing
build step on our side?

Emmanuel Bourg

This problem still exists in 1.77 (to be released soon). That sounds like a bnd
problem. I can find a reference to a bnd.sh script but it is not included in
the source distribution. There is also a add_module.sh script. If we can't find
a way to automate this build step, we could use jh_manifest which I would
prefer over the patch.