Hello!

Our downloads sites were getting a bit cluttered with eol software.
Therefore, we turned off directory browsing for some of this eol software.
Hopefully this will aid users who manually browse the site to not get lost
in the clutter.

That being said, all of the files are still "there" (only browsing has been
turned off). So, if you know specifically what you are looking for, you can
still construct a link to it (example:
http://yum.puppetlabs.com/puppet5-release-el-6.noarch.rpm). Also, any
references to download links in scripts will still work.

However, it seems like a few people (including you :) ) need to still
browse to certain puppet5 artifacts.
Therefore, I've added them back here: http://yum.puppetlabs.com/eol-releases


Hopefully that helps!
Jackie

On Tue, May 4, 2021 at 2:21 PM Nick Bertrand <[email protected]> wrote:

> Hi all,
>
> It looks like the Puppet 5 RPMs were pulled from yum.puppetlabs.com, but
> they also don't seem to exist on release-archives.puppet.com. Can someone
> point me towards a repository I can use while I work on upgrading to a
> supported version?
>
> Thanks,
>
> Nick Bertrand
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/CAP15v%2B9yaCNvGQuO8AcexqehYNneAU5pK2MAzHs010dba2WUug%40mail.gmail.com
> <https://groups.google.com/d/msgid/puppet-users/CAP15v%2B9yaCNvGQuO8AcexqehYNneAU5pK2MAzHs010dba2WUug%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAMgPiFvFt-h%2BX2xCpHaXHbg%2B4%3DxPnkiOWcfYwCiraw3PgvTcFw%40mail.gmail.com.

Reply via email to