Bug#713273: osgi-core: FTBFS: debian/.mh/pom.properties: line 3: 4.3.0n: command not found

[Lucas Nussbaum]

Source: osgi-core
Version: 4.3.0-3
Severity: serious
Tags: jessie sid
User: debian-qa at lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part:
> make[1]: Entering directory `/«PKGBUILDDIR»'
> jar umf src/META-INF/MANIFEST.MF debian/libosgi-core-java/usr/share/java/osgi.core.jar
> Jun 21, 2013 6:25:25 AM java.util.jar.Attributes read
> WARNING: Duplicate name in Manifest: Manifest-Version.
> Ensure that the manifest does not have duplicate entries, and
> that blank lines separate individual sections in both your
> manifest and in the META-INF/MANIFEST.MF entry in the jar file.
> Jun 21, 2013 6:25:25 AM java.util.jar.Attributes read
> WARNING: Duplicate name in Manifest: Created-By.
> Ensure that the manifest does not have duplicate entries, and
> that blank lines separate individual sections in both your
> manifest and in the META-INF/MANIFEST.MF entry in the jar file.
> make[1]: Leaving directory `/«PKGBUILDDIR»'
>    jh_exec
>    jh_depends
>    mh_installpoms
> debian/.mh/pom.properties: line 3: 4.3.0n: command not found
> make: *** [binary] Error 1

The full build log is available from:
   http://aws-logs.debian.net/ftbfs-logs/2013/06/20/osgi-core_4.3.0-3_unstable.log

A list of current common problems and possible solutions is available at 
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.