Puppet 2.6.x fate

[Michael Stahnke]

It was decided earlier this week that the 2.6 series will have it's
last release at 2.6.10 (we're currently at 2.6.9). However, we are
not doing a 2.6.10 RC/release this month. That will wait until
August.

If you have patches waiting on some final tweaks or any other work
that you feel like just *has* to be in the 2.6 series, please get it
filed with us ASAP. Right now the bug-fix list is not huge, and we're
pretty happy about that.

As always, if a security issue is discovered in 2.6.x, we will issue
updates to fix those.

Mike

(You're coming to PuppetConf <http://www.bit.ly/puppetconfsig> right?)

[PBWebGuy]

Hi Mike,

I wanted to comment on bug http://projects.puppetlabs.com/issues/7680
which is a regression introduced in 2.6.8. I recently ran into this
issue and had to downgrade to 2.6.7 from 2.6.8. When I discovered the
issue I tried upgrading to 2.6.9 and it was still an issue.

The problem is simply that if the source points to a symlinked file,
the md5 calculation fails. This bug has prevented me from moving
forward and would love to see it get fixed.

I wanted to vote on the bug but I have not figured out how to get some
level of access to the bug tracking system. I also have a few other
bugs that I would like to report but the process is not clearly
documented.

Thanks,

John

[Jacob Helwig]

On Thu, 14 Jul 2011 09:53:36 -0700, PBWebGuy wrote:
>
> Hi Mike,
>
> I wanted to comment on bug http://projects.puppetlabs.com/issues/7680
> which is a regression introduced in 2.6.8. I recently ran into this
> issue and had to downgrade to 2.6.7 from 2.6.8. When I discovered the
> issue I tried upgrading to 2.6.9 and it was still an issue.
>
> The problem is simply that if the source points to a symlinked file,
> the md5 calculation fails. This bug has prevented me from moving
> forward and would love to see it get fixed.
>
> I wanted to vote on the bug but I have not figured out how to get some
> level of access to the bug tracking system. I also have a few other
> bugs that I would like to report but the process is not clearly
> documented.
>
> Thanks,
>
> John
>

You should be able to vote on the issue once you've logged in. It
shouldn't require any special permissions.

I'm guessing you've already created an account on the Redmine
instance[1]?

As far as reporting other bugs: Once you've logged in, you should be
able to click the New Issue link[2] when you're viewing the appropriate
project. There isn't really much "process" around it. We appreciate if
you check for a pre-existing ticket before filing a new one, but it's
not like we'll get angry if you don't spot that it's duplicate.

[1] https://projects.puppetlabs.com/account/register
[2] https://projects.puppetlabs.com/projects/puppet/issues/new

--
Jacob Helwig
,----
| Join us for PuppetConf, September 22nd and 23rd in Portland, OR
| http://bit.ly/puppetconfsig
`----