libpam4j version 1.4-1 FTBFS on i386 in precise
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libpam4j (Ubuntu) |
Fix Released
|
High
|
James Page | ||
Precise |
Fix Released
|
High
|
James Page |
Bug Description
This is a semi-automatic report based on the latest archive rebuild results [1].
Apologies if it reaches you in error.
Excerpt from the buildlog:
dh_installdebconf -plibpam4j-java
dh_installemacsen -plibpam4j-java
dh_installcatalogs -plibpam4j-java
dh_installpam -plibpam4j-java
dh_installlogrotate -plibpam4j-java
dh_installlogcheck -plibpam4j-java
dh_installchang
dh_installudev -plibpam4j-java
dh_lintian -plibpam4j-java
dh_bugfiles -plibpam4j-java
dh_install -plibpam4j-java
dh_link -plibpam4j-java
dh_installmime -plibpam4j-java
dh_installgsettings -plibpam4j-java
jh_installlibs -plibpam4j-java
jh_classpath -plibpam4j-java
IO error: opening debian/
at /usr/share/
Archive:
main::
jh_manifest: Could not read debian/
make: *** [binary-
dpkg-buildpackage: error: /usr/bin/fakeroot debian/rules binary gave error exit status 2
*******
Build finished at 20120207-2048
FAILED [dpkg-buildpackage died]
The full buidlog can be found at https:/
[1] http://
Related branches
Changed in libpam4j (Ubuntu): | |
importance: | Undecided → High |
This is caused due to a change in default behaviour in maven-debian- helper; packages must specify --java-lib in the libXX-java.poms file otherwise jar files are not installed to /usr/share/java.