setools version 3.3.6.ds-7.2ubuntu4 FTBFS on i386 in precise

Bug #935440 reported by Andreas Moog
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
setools (Debian)
Fix Released
Unknown
setools (Ubuntu)
Fix Released
High
Unassigned
Precise
Won't Fix
High
Unassigned

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:

checking for Tk 8.4 or greater... yes
checking for Tk public headers... /usr/include/tcl8.4
checking for X... libraries , headers
checking for X11 header files... checking for wish... /usr/bin/wish8.4
checking for BWidget 1.7 or greater... skipped, assuming 1.8+ is installed
checking for running SELinux system... configure: WARNING: could not read /selinux/policyvers - disabling runtime SELinux support
checking for sepol/sepol.h... checking sepol/sepol.h usability... yes
checking sepol/sepol.h presence... yes
checking for sepol/sepol.h... yes
checking for sepol_policydb_read in -lsepol... yes
checking selinux/selinux.h usability... yes
checking selinux/selinux.h presence... yes
checking for selinux/selinux.h... yes
checking selinux/context.h usability... yes
checking selinux/context.h presence... yes
checking for selinux/context.h... yes
checking for selinux_policy_root in -lselinux... yes
checking for /usr/lib/libsepol.a... no
configure: error: make sure libsepol-static is installed
make[1]: *** [debian/stamp/conf/setools] Error 1
make[1]: Leaving directory `/build/buildd/setools-3.3.6.ds'
make: *** [debian/stamp/do-pre-config-common] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
******************************************************************************
Build finished at 20120211-0403
FAILED [dpkg-buildpackage died]

The full buidlog can be found at https://launchpad.net/ubuntu/+archive/test-rebuild-20120201/+build/3170882/+files/buildlog_ubuntu-precise-i386.setools_3.3.6.ds-7.2ubuntu4_FAILEDTOBUILD.txt.gz.

[1] http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20120201-precise.html

Andreas Moog (ampelbein)
Changed in setools (Ubuntu):
importance: Undecided → High
Revision history for this message
Marcin Juszkiewicz (hrw) wrote :

This patch makes setools build go a bit further. Then it fails like in Debian.

tags: added: patch
Changed in setools (Debian):
status: Unknown → New
Revision history for this message
Laurent Bigonville (bigon) wrote :

I've just made an upload in debian that should fix the FTBFS

I guess that the package can be synced

Changed in setools (Debian):
status: New → Fix Released
Vibhav Pant (vibhavp)
Changed in setools (Ubuntu):
assignee: nobody → Vibhav Pant (vibhavp)
Changed in setools (Ubuntu Precise):
assignee: nobody → Vibhav Pant (vibhavp)
Vibhav Pant (vibhavp)
Changed in setools (Ubuntu Precise):
assignee: Vibhav Pant (vibhavp) → nobody
Changed in setools (Ubuntu):
assignee: Vibhav Pant (vibhavp) → nobody
Changed in setools (Ubuntu):
status: New → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in setools (Ubuntu Precise):
status: New → Confirmed
Revision history for this message
Rolf Leggewie (r0lf) wrote :

I'm surprised (and a bit appaled) at the number of FTBFS bugs still open in precise. I was able to verify this particular one and will see if I can come up with a debdiff.

Changed in setools (Ubuntu Precise):
assignee: nobody → Rolf Leggewie (r0lf)
Revision history for this message
Rolf Leggewie (r0lf) wrote :

I backported fix_configure.patch from 3.3.7-1 which according to the changelog should fix this issue but it still fails all the same.

Rolf Leggewie (r0lf)
Changed in setools (Ubuntu Precise):
assignee: Rolf Leggewie (r0lf) → nobody
milestone: none → ubuntu-12.04.3
Revision history for this message
Andreas Moog (ampelbein) wrote :

Precise is EoL, setting task to Won't Fix.

Changed in setools (Ubuntu Precise):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.