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

Puppet 3.1.0 final #11

Closed
wants to merge 5 commits into from
Closed

Puppet 3.1.0 final #11

wants to merge 5 commits into from

Conversation

aboe76
Copy link
Contributor

@aboe76 aboe76 commented Feb 5, 2013

updated to 3.1.0 final, build from gem

@GregSutcliffe
Copy link
Owner

Can we make it depend on facter || ruby-facter? I'm concerned about how people upgrade - there's no conflict on facter, and ruby-facter installs the same stuff, so what's the point? Does ruby-facter provide facter also?

Awesome work as ever, by the way ;)

@aboe76
Copy link
Contributor Author

aboe76 commented Feb 5, 2013

I think you're right, about facter || ruby-facter... only difference between the two is the place where stuff gets installed,
ruby-facter installs in /usr/lib/ruby/gems/
facter installs in /usr/lib/ruby/site_ruby/

both provide facter but ruby-facter is easier to maintain.

@GregSutcliffe
Copy link
Owner

i'm happy to drop the facter package and let joschi maintain ruby-facter. Should we ask him if he wants to add facter to the provides?

@aboe76
Copy link
Contributor Author

aboe76 commented Feb 5, 2013

sure than he can drop ruby-puppet. because this provides it.
so it's like a trade

2013/2/5 Greg Sutcliffe notifications@github.com

i'm happy to drop the facter package and let joschi maintain ruby-facter.
Should we ask him if he wants to add facter to the provides?


Reply to this email directly or view it on GitHubhttps://github.com//pull/11#issuecomment-13130849.

@GregSutcliffe
Copy link
Owner

Getting some conflicts when I try to build this. Looks like we're depending on a package that provies /usr/bin/hiera and also installing ourselves. Looking into it now, but if you know the answer....

@GregSutcliffe
Copy link
Owner

I think installing the hiera gem inside the $pkgdir is leaving files behind - it cleans up some of them by calling "gem uninstall hiera" after you copy the files out, but that causes the PKGBUILD to ask for input. What are we taking from the hiera gem?

@GregSutcliffe
Copy link
Owner

Ok, so removing the hiera gem entirely seems to work - do we need it for anything @aboe76?

@GregSutcliffe
Copy link
Owner

Also the systemd files aren't copied into place. trying to fix that now

@GregSutcliffe
Copy link
Owner

Scratch that, they are, but fsr aren't starting right. Will get back to you on why...

@GregSutcliffe
Copy link
Owner

Ok, it's working now, must have done something stupid to my previous VM. Going to push a fixed version of this, check it out when you have a chance.

@aboe76
Copy link
Contributor Author

aboe76 commented Feb 9, 2013

It looks good, what was the reason hiera 1.0.0 not needed?
I was trying on a fresh archlinux vm and I could only get it working with
hiera 1.0.0 and hiera 1.1.2 installed???

2013/2/8 Greg Sutcliffe notifications@github.com

Ok, it's working now, must have done something stupid to my previous VM.
Going to push a fixed version of this, check it out when you have a chance.


Reply to this email directly or view it on GitHubhttps://github.com//pull/11#issuecomment-13317891..

@GregSutcliffe
Copy link
Owner

With the hiera gem in the PKGBUILD, the file "/usr/bin/hiera" conflicts with the ruby-hiera package. Do you still have the test case for the hiera problem? I can test it against my PKGBUILD... Maybe we should add a tests folder to the repo ;)

@GregSutcliffe
Copy link
Owner

3.1 published, closing this.

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

Successfully merging this pull request may close these issues.

None yet

2 participants