Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

apt.opscode.com is no longer available - remove the apt_install method #216

Open
thekorn opened this issue Nov 17, 2014 · 8 comments
Open
Labels

Comments

@thekorn
Copy link
Collaborator

thekorn commented Nov 17, 2014

chef is no longer installable via the apt repository as announced here: http://lists.opscode.com/sympa/arc/chef/2014-11/msg00015.html

@thekorn thekorn added the bug label Nov 17, 2014
@haad
Copy link

haad commented Nov 17, 2014

I think deploy_chef needs cleanup and only omnibus install should be kept.
That would simplify it a lot.
On Nov 17, 2014 2:56 PM, "Markus Korn" [email protected] wrote:

chef is no longer installable via the apt repository as announced here:
http://lists.opscode.com/sympa/arc/chef/2014-11/msg00015.html


Reply to this email directly or view it on GitHub
#216.

@tobami
Copy link
Owner

tobami commented Nov 18, 2014

@haad you are right. All "package" methods are now kind of obsolete, because omnibus supports most officially (with the exception of Gentoo?), and the gem install I am not sure it is useful anymore. Do you want to have a go at the cleanup?

@haad
Copy link

haad commented Nov 18, 2014

I was planning to. I will make a pull request for you.
On Nov 18, 2014 9:26 AM, "Miquel Torres" [email protected] wrote:

@haad https://github.com/haad you are right. All "package" methods are
now kind of obsolete, because omnibus supports most
https://www.getchef.com/download-chef-client/ officially (with the
exception of Gentoo?), and the gem install I am not sure it is useful
anymore. Do you want to have a go at the cleanup?


Reply to this email directly or view it on GitHub
#216 (comment).

@tobami
Copy link
Owner

tobami commented Nov 18, 2014

That is awesome!

Do you know whether the gem install is still useful?

@tobami
Copy link
Owner

tobami commented Nov 18, 2014

Looking at the changelog, there is enough new stuff and fixes that after this issue is solved we could release a version 1.8

@haad
Copy link

haad commented Nov 18, 2014

I was going to suggest that ! :)

I have one feature in my branch, I have added option to specify gateway,
proxy in node config file. I'm using it to configure nodes which are behind
different gateways with same littlechef.cfg.

Should I do pull request ?

On Tue, Nov 18, 2014 at 2:36 PM, Miquel Torres [email protected]
wrote:

Looking at the changelog, there is enough new stuff and fixes that after
this issue is solved we could release a version 1.8


Reply to this email directly or view it on GitHub
#216 (comment).

Regards.

Adam

@tobami
Copy link
Owner

tobami commented Nov 19, 2014

Sure, do that so we get it in the new version. And while you are at gateway and proxes you could look at #222 which seems to happen because some of the proxy settings are not set in the module

@haad
Copy link

haad commented Nov 22, 2014

I did my work at *chef-install-rework
https://github.com/haad/littlechef/tree/chef-install-rework *but I have
so many changes in my repository that it might be hard to pull them. I
have fixed tests on that branch too.

On Wed, Nov 19, 2014 at 10:34 AM, Miquel Torres [email protected]
wrote:

Sure, do that so we get it in the new version. And while you are at
gateway and proxes you could look at #222
#222 which seems to happen
because some of the proxy settings are not set in the module


Reply to this email directly or view it on GitHub
#216 (comment).

Regards.

Adam

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants