Bug#769804: jarjar-maven-plugin: FTBFS against rebuilt packages: Failed to resolve artifact ant

tony mancill tmancill at debian.org
Sun Nov 16 19:26:21 UTC 2014


On 11/16/2014 09:53 AM, Emmanuel Bourg wrote:
> Hi Daniel,
> 
> As I understand ant is pulled through
> maven-debian-helper->velocity->ant. How did you manage to install the
> build dependencies without ant installed?
> 
> Ant is a direct dependency so it would be a good idea to add it to the
> build deps, but this error should not happen with the current dependency
> graph.

Hi Emmanuel,

I believe what Daniel is saying is that if you rebuild the entire
dependency chain, ant isn't being pulled in (by velocity).

Or put another way, there is a difference between the dependency graph
that exists for the binary build-deps in the archive, and the dependency
graph created by rebuilding all of the build-deps in the archive from
source.

Daniel, first, do I have that right, and secondly, is your rebuild on
jessie or sid?

In any event, no harm in adding ant directly, although it would be good
to determine if this is a class of FTBFS bugs instead of an isolated
instance.  E.g., there may be other packages that were expecting
velocity to pull in ant.  (Theoretically, because I haven't looked into
it, but velocity appears to be long overdue for some freshening...)

Cheers,
tony

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20141116/52309d4a/attachment.sig>


More information about the pkg-java-maintainers mailing list