[Bug 1173265] Re: facter fails to run from rebuilt source package

[Andres Rodriguez]

** Also affects: facter (Ubuntu Precise)
   Importance: Undecided
       Status: New

** Also affects: facter (Ubuntu Quantal)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1173265

Title:
  facter fails to run from rebuilt source package

Status in “facter” package in Ubuntu:
  Triaged
Status in “facter” source package in Precise:
  New
Status in “facter” source package in Quantal:
  New

Bug 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_1.6.9-2ubuntu1_all.deb 
  (Reading database ... 77464 files and directories currently installed.)
  Preparing to replace facter 1.6.9-2ubuntu1 (using facter_1.6.9-2ubuntu1_all.deb) ...
  Unpacking replacement facter ...
  Setting up facter (1.6.9-2ubuntu1) ...
  Processing triggers for man-db ...
  ubuntu at raring-test:~$ facter
  -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/bin/ruby1.9.1 after the rebuild, rather than the
  #!/usr/bin/ruby1.8 shebang in the binary in the archive. It looks like
  this might have happened after the ruby metapackage was updated to 4.9
  which changed the default ruby to 1.9 from 1.8, causing the facter
  package build to turn out differently.

  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/facter/+bug/1173265/+subscriptions