Jim Bala wrote:
> At least to me, the optimal placement would be under the "New Issue"
> tab, which is always there regardless of login status. If you aren't
> logged in, it says, "Please login or register for an account to
> create a new issue." Just seems counterintuitive to hide the
> tab/link
At least to me, the optimal placement would be under the "New Issue" tab, which
is always there regardless of login status. If you aren't logged in, it says,
"Please login or register for an account to create a new issue." Just seems
counterintuitive to hide the tab/link.
-Jim
On Jul 17, 20
Jim Bala wrote:
> Also: for those that've never gone through this process before (such
> as me), could use a hint somewhere on the bugtracker (at least on the
> "Issues" page) that you need to register to create a new issue.
> Since the "New Issue" link doesn't show up at all until you've
> registe
Done.
http://projects.puppetlabs.com/issues/4266
http://projects.puppetlabs.com/issues/4267
Also: for those that've never gone through this process before (such as me),
could use a hint somewhere on the bugtracker (at least on the "Issues" page)
that you need to register to create a new issue.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Am I perhaps doing something wrong or do one or both of these appear
> to be a genuine bug(s)?
I would say these are 2 bugs, can you file the reports? Thanks.
cheers pete
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Usi
Hi all,
Full path:
/usr/lib/ruby/site_ruby/1.8/puppet/provider/ssh_authorized_key/parsed.rb
Two problems:
1) Even if filebucketing is disabled, this (still) tries to backup
authorized_keys to /var/lib/puppet/clientbucket/[...]; no other
modules are doing filebucketing when it's disabled but they
