Missing line-end comma in debian/control

[Andrew Sayers]

Binary package hint: java-gcj-compat

This bug was sent manually, but the text was written to a template, as I have several similar bugs to report today. Please see my recent bug reports for a list, or bug #391165 for the root cause.

Versions 1.0.78-2 and 1.0.80-1 of java-gcj-compat have a missing line-end comma in the "Build-Dependencies" section of debian/control. There should be a comma in the area marked by ***asterisks***:

Build-Depends: debhelper (>= 5.0.37.2),
 gcj-4.3 (>= 4.3)***
 ***ecj (>= 3.3.0), fastjar, gjdoc (>= 0.7.8), python-dev (>= 2.3.5-11), python-central (>= 0.5), lsb-release, openssl, ca-certificates

I haven't tested the exact effects of this issue in java-gcj-compat. It might be that these dependencies are unnecessary and can be removed, or it might be that some features are silently disabled (see bug #365770 for an example). If the dependencies should stay, the bug can be fixed by inserting a comma in the marked area.

[David Stansby (dstansby-deactivatedaccount)]

Here's the fix.

[Daniel Holbach (dholbach)]

The package was removed from Karmic:
https://launchpad.net/ubuntu/karmic/+source/java-gcj-compat/1.0.80-1

[David Stansby (dstansby-deactivatedaccount)]

So would I be right in thinking that this package will remain in Jaunty and Intrepid, but won't need this problem fixing because no new builds of it will be done?

[Daniel Holbach (dholbach)]

Good question. Do we have misbuilt packages in Jaunty and Intrepid? Bug 391165 indicates this is just necessary for Karmic.

[Andrew Sayers (andrew-bugs-launchpad-net)]

A quick test suggests that the dependency on "gjdoc" pulls in gcj with it, so I would not expect this bug to have any practical effect on this package in Jaunty.