Dependency proken: ltsp-update-kernels needs restorecon from policycoreutils

Bug #993179 reported by Johan Schiff
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LTSP5
Fix Released
Low
Alkis Georgopoulos

Bug Description

The ltsp-update-kernels returns status 1 if /sbin/restorecon (package policycoreutils) doesn't exist. This causes ltsp-build-client to fail.

Either ltsp-server should require policycoreutils, or ltsp-update-kernels should be fixed.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ltsp-server 5.3.7-0ubuntu2 [modified: usr/sbin/ltsp-update-kernels]
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic-pae 3.2.14
Uname: Linux 3.2.0-24-generic-pae i686
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
Date: Wed May 2 12:36:05 2012
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=sv_SE.UTF-8
 TERM=xterm
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
SourcePackage: ltsp
UpgradeStatus: Upgraded to precise on 2012-04-30 (1 days ago)

Revision history for this message
Johan Schiff (johan-idealist) wrote :
Revision history for this message
Alkis Georgopoulos (alkisg) wrote :

That line was added in 2008-02-26 by a Fedora developer:
http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/573
(selinux isn't used by default in Ubuntu)

I've no idea about selinux, would it be OK to just check for restorecon existence before running it?

if [ -f /selinux/enforce ] && [ -x /sbin/restorecon ]; then
    restorecon -R "$tftpdir" > /dev/null
fi

no longer affects: ltsp (Ubuntu)
Revision history for this message
Johan Schiff (johan-idealist) wrote :

Yes, that fixes it on my setup.

Revision history for this message
Johan Schiff (johan-idealist) wrote :

Here's the diff from my (now properly working) ltsp-update-kernels (precise).

Revision history for this message
Alkis Georgopoulos (alkisg) wrote :
Changed in ltsp:
assignee: nobody → Alkis Georgopoulos (alkisg)
importance: Undecided → Low
status: New → Fix Committed
Revision history for this message
Alkis Georgopoulos (alkisg) wrote :

Fix released in LTSP 5.4.0.

Changed in ltsp:
status: Fix Committed → Fix Released
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.