Great thanks! I will try it :-)
That's correct Daniel!
you can try it yourself with:
puppet-lint manifest.pp
The package is now installed on the machines.
2015-02-11 10:46 GMT+01:00 Daniel Mustieles García <daniel mustieles gmail com>:
> Just to clarify things, puppet-lint is used to check and fix manifests'
> files syntax right?
>
> 2015-02-11 10:03 GMT+01:00 Andrea Veri <av gnome org>:
>>
>> CCing gnome-infrastructure so that all the apprentices might benefit
>> from the same answers.
>>
>> 2015-02-11 0:37 GMT+01:00 Joey STANFORD <joey canonical com>:
>> > Hi Andrea,
>>
>> Hey!
>>
>> > I've hit a few problems.
>> >
>> > 1) According to
>> >
>> > https://wiki.gnome.org/Sysadmin/Apprentices
>> >
>> > I'm not allowed to clone the puppet branch (otherwise I would have
>> > just done it from my workstation and life would be great!).
>> > How do I clone the sucker so I can make changes and then file
>> > a bug with a merge proposal? I'd rather do a merge proposal over a patch
>> > file because it uses git that way.
>>
>> The current repository is a "shallow clone" and that actually means:
>>
>> 1. it contains the same files and directories as the original
>> repository but with a truncated history (the history can only be
>> accessed if you have the relevant rights to the original repository.
>> That is restricted to sysadmins)
>> 2. you can't clone nor fetch from it
>> 3. you should create a workdir on the machine itself and play with
>> diff(1). With that you will be safely able to create patches and
>> attach them to BZ
>>
>> > 2) I've locked myself out
>> >
>> > I tried to see if I could sshfs mount it locally
>> > but that didn't work out so well. I must have tripped a failsafe
>> > because I can't ssh in (but can get to freeipa):
>> >
>> > ssh_exchange_identification: read: Connection reset by peer
>>
>> Why would you need to mount it through sshfs? just ssh to the machine,
>> copy the files and start creating patches. You can't push anything to
>> the repository as you need an ack from two existing sysadmins before
>> doing so. The workflow you can use should look like this:
>>
>> cp -r /srv/git/puppet.git . && cd puppet.git
>> vim modules/puppet/manifest/init.pp
>> git commit -a -m 'Added the puppet-lint package'
>> git format-patch -1 --stdout > 01-add-puppet-lint-to-puppet-class.patch
>>
>> Then submit to Bugzilla as per [1].
>>
>> > 3) One of the first things I'd like to do is lint the puppet files.
>> > My preferred method is using puppet-lint, unfortunately that's
>> > not installed on bastion. Since I can't seem to sshfs in and
>> > I can't locally clone the git repo, is it possible to have you sudo gem
>> > install puppet-lint for me?
>>
>> Merging [2] in a few minutes.
>>
>> Have an awesome day!
>>
>> [1] https://wiki.gnome.org/Sysadmin/Apprentices
>> [2] https://bugzilla.gnome.org/show_bug.cgi?id=744196
>>
>>
>> --
>> Cheers,
>>
>> Andrea
>>
>> Debian Developer,
>> Fedora / EPEL packager,
>> GNOME Infrastructure Team Coordinator,
>> GNOME Foundation Board of Directors Secretary,
>> GNOME Foundation Membership & Elections Committee Chairman
>>
>> Homepage: http://www.gnome.org/~av
>> _______________________________________________
>> gnome-infrastructure mailing list
>> gnome-infrastructure gnome org
>> https://mail.gnome.org/mailman/listinfo/gnome-infrastructure
>
>
--
Cheers,
Andrea
Debian Developer,
Fedora / EPEL packager,
GNOME Infrastructure Team Coordinator,
GNOME Foundation Board of Directors Secretary,
GNOME Foundation Membership & Elections Committee Chairman
Homepage: http://www.gnome.org/~av