[chef] Re: RE: CHEF-Client installation

[Kimball Johnson < >]

That is strange as I couldn't install chef on a freshly installed
lenny at all without creating a backport of libjson-ruby1.8, whihc is
the dependency error you see in the final stage.

You are right, you should not change the dependencies file, it
wouldn't help anyway, each package holds it's own dependencies, the
file is to help apt resolve them automatically

On 31 March 2011 16:36, WEINHAPL Andreas
<
 >
 wrote:
> Mhm that seems to be a other problem which look like mine. The weird thing 
> is that I'm able to install chef if the sever doesn't work with puppet 
> before. So I think "puppet" will write something to a file which will be 
> checked by apt-get.
>
> I made a test and I can reproduce it with no problems, just set up a debian 
> server (debian-507-amd64-netinst.iso)
>        * Install chef (apt-get install chef) -> TO be sure that it will work
>        * Uninstall it with (apt-get --purge remove chef)
>        * Autoremove all automatic installed packages "apt-get --purge 
> autoremove"
>        * Install "puppet" -> apt-get install puppet
>        * Remove puppet after installed -> apt-get --purge remove puppet
>        * apt-get --purge autoremove
>        * clean up everything -> apt-get clean
>        * and install chef again -> apt-get install chef
>
> The result is that you will run into dependency errors:
>         * Depends: libjson-ruby1.8 (>= 1.4.6) but it is not going to be 
> installed
>       * Depends: ohai (>= 0.5.8) but it is not going to be installed
>       * Depends: libchef-ruby1.8 (= 0.9.14+dfsg-1) but it is not going to 
> be installed
>
> I found out that the dependencies are stored at /var/lib/apt/lists/ 
> ftp.at.debian.org_debian_dists_lenny_main_binary-i386_Packages
>
> But I don't think that it will be good to edit this file :)