Issue #17777 has been updated by Michael Steger.



    $ grep '^#!' /usr/sbin/puppetd
    #!/usr/bin/ruby1.9.1  




----------------------------------------
Bug #17777: broken debian package on apt.puppetlabs.com / shebang change
https://projects.puppetlabs.com/issues/17777#change-81206

Author: Marc Fournier
Status: Investigating
Priority: Normal
Assignee: Matthaus Owens
Category: Debian
Target version: 
Affected Puppet version: 2.7.20
Keywords: debian packaging apt.puppetlabs.com
Branch: 


http://apt.puppetlabs.com/pool/wheezy/main/p/puppet/puppet-common_2.7.20-1puppetlabs1_all.deb
 has the following properties:

    $ dpkg -I puppet-common_2.7.20-1puppetlabs1_all.deb | grep Dep
    Depends: ruby1.8, libxmlrpc-ruby, libopenssl-ruby, libshadow-ruby1.8, 
libaugeas-ruby1.8, adduser, facter (>= 1.5), facter (<< 2.0), lsb-base, sysv-rc 
(>= 2.86) | file-rc

    $ dpkg -c puppet-common_2.7.20-1puppetlabs1_all.deb  | grep puppet.rb
    -rw-r--r-- root/root      2831 2012-11-20 00:48 ./usr/lib/ruby/1.8/puppet.rb

But once installed I noticed that:

    $ grep '^#!' /usr/bin/puppet
    #!/usr/bin/ruby1.9.1

Which yields the following error if you happen to not have ruby1.9.1 installed:

    # /etc/init.d/puppetmaster start
    Starting puppet masterstart-stop-daemon: unable to start /usr/bin/puppet 
(No such file or directory)
     failed!

And this one once it's installed:

    # /etc/init.d/puppetmaster start
    Starting puppet master<internal:lib/rubygems/custom_require>:29:in 
`require': no such file to load -- puppet/util/command_line (LoadError)
            from <internal:lib/rubygems/custom_require>:29:in `require'
            from /usr/bin/puppet:4:in `<main>'

2.7.19 and previous don't have this problem.

It's not the first time I found broken packages on apt.puppetlabs.com. Maybe 
would it be an idea to add some automated tests which would bootstrap every 
distro listed on http://apt.puppetlabs.com/pool/ and simply try to install the 
packages before releasing them ? This would at least catch broken dependencies 
and obvious errors such as this one.




-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to