| This is what I did,
although I did run into some funky errors that required two chef runs
with updating the package. Next time I might choose to remove and
replace the package. Not sure. I'll probably experiment a bit more next
time before pushing out an update. Joshua Timberman wrote: " type="cite">I recommend downloading the omnibus package and hosting it on an internal repository, and updating to the latest when ready to do so. Cheers, Joshua On Jun 9, 2013, at 2:02 PM, Dan Razzell ">< > wrote:A disadvantage of manually downloading and installing Debian packages is that dpkg doesn't manage dependencies. If your system never uses apt-get, but instead you do your own dependency management somehow, that's arguably a possible strategy. It was how Solaris packages were managed. But if you do use apt-get, then manually installing some packages with dpkg throws the model into an inconsistent state. On Sun, Jun 9, 2013 at 1:49 AM, Steffen Gebert ">< > wrote: Hi, I'm wondering how one should upgrade the chef-client omnibus package. I'm moving away from the old apt repo for version 10 and am currently downloading the .deb files and then installing them. Is this the (only) right way? Thanks for your response Steffen |
Archive powered by MHonArc 2.6.16.