Public bug reported:
Recently, a bunch of packages build-depending on libautomaton-java
started to FTBFS (see #1093346 for example). The reason seems to be an
inconsistent placement of JAR and POM files:
$ tree /usr/share/maven-repo/dk/brics/
/usr/share/maven-repo/dk/brics/
└── automaton
├── 1.12-4
│ └── automaton-1.12-4.jar ->
../../../../../java/automaton-1.12-4+dfsg.jar
├── automaton
│ ├── 1.11-8
│ │ └── automaton-1.11-8.pom
│ └── debian
│ └── automaton-debian.pom
└── debian
└── automaton-debian.jar ->
../../../../../java/automaton-1.12-4+dfsg.jar
This most likely has been broken due to automaton changing its
groupId:artifactId. I see automaton carries an upstream- and Debian
mantainer-provided POMs. Maybe the Debian-provided POM could be dropped
in favor of the upstream-provided one?
** Affects: automaton (Ubuntu)
Importance: Undecided
Status: New
** Affects: automaton (Debian)
Importance: Unknown
Status: Unknown
** Bug watch added: Debian Bug tracker #1093582
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093582
** Also affects: automaton (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1093582
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2095448
Title:
libautomaton-java: inconsistent JAR and POM placement
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/automaton/+bug/2095448/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
