facter fails to run from rebuilt source package
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
facter (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Precise |
Invalid
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned | ||
Raring |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
SRUs and security updates are impossible without breaking the package.
[Development Fix]
My merge of facter 1.7 drops most of the Ubuntu delta that is now no longer necessary. This eliminates the problem.
[Stable Fix]
Build-Depend on ruby1.8 specifically, instead of the ruby virtual package. The Quantal and Raring binaries in the archive were originally built against ruby1.8 anyway, as this is what the ruby virtual package brought in at the time of the build. With this minimal fix, the build doesn't change to pulling in 1.9.1 instead and thus causing breakage.
[Test Case]
A dep8 smoke test has been added. If the problem is fixed, the dep8 test should pass.
Failing this, just run "facter". If you get a bunch of facts printed out, then the problem is fixed. Note that to test this properly, you should start by not having ruby1.9.1 installed.
The two failure possibilities are:
# facter
/usr/lib/
from /usr/lib/
from /usr/bin/
# facter
bash: /usr/bin/facter: /usr/bin/ruby1.9.1: bad interpreter: No such file or directory
[Regression Potential]
The build could have accidentally changed other things apart from the original Ruby 1.8 dependency since the original build. But since "facter" on its own prints all known facts, it is easy to confidently verify that factor's fact-detection behaviour has not changed unexpectedly after an update.
[Original Description]
If I rebuild 1.6.9-2ubuntu1 in a raring chroot, then when I attempt to run facter I get an error:
$ sudo dpkg -i facter_
(Reading database ... 77464 files and directories currently installed.)
Preparing to replace facter 1.6.9-2ubuntu1 (using facter_
Unpacking replacement facter ...
Setting up facter (1.6.9-2ubuntu1) ...
Processing triggers for man-db ...
ubuntu@
-bash: /usr/bin/facter: /usr/bin/ruby1.9.1: bad interpreter: No such file or directory
The problem is that /usr/bin/facter gets a shebang of #!/usr/
It also looks like Debian's facter 1.6.10-1 rejigged some of the ruby versioning, so I suspect that the problem can be fixed in Saucy with a simple merge.
But I suspect that an attempted SRU to Quantal or Raring will cause a regression unless this bug is fixed there.
description: | updated |
Changed in facter (Ubuntu Quantal): | |
status: | New → Triaged |
Changed in facter (Ubuntu Raring): | |
status: | New → Triaged |
Debdiff against Debian facter 1.6.10-1 (current sid) for a merge attached.