Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Michael Watters]

Thanks.  I've updated our agents to use the new location.


On Wednesday, June 5, 2019 at 5:25:47 PM UTC-4, Molly Waggett wrote:
>
> Hi Michael,
>
> The puppetlabs-release-pc1 packages on yum.puppetlabs.com are the ones we 
> plan to re-archive. You will need to install new release packages from 
> http://release-archives.puppet.com/yum/ if you want to continue using the 
> PC1 repository. Neither of these repos will receive future updates.
>
> If you have additional questions, please let me know!
>
> On Wed, Jun 5, 2019 at 10:36 AM Michael Watters  > wrote:
>
>> Hello,
>>
>> I see the puppetlabs-release-pc1 package is available on 
>> yum.puppetlabs.com however it doesn't actually show as an available 
>> update when running "yum update".
>>
>> For example, here's the output on one of our servers.
>>
>> ```
>> [root@server1 yum.repos.d]# yum update puppetlabs-release-pc1
>> Loaded plugins: auto-update-debuginfo, fastestmirror, langpacks, 
>> versionlock
>> Loading mirror speeds from cached hostfile
>>  * elrepo: reflector.westga.edu
>>  * epel-debuginfo: mirror.uic.edu
>> No packages marked for update
>> ```
>>
>> I *was* able to update the package using the rpm command directly however 
>> I'd like to avoid doing this on hundreds of nodes.
>>
>>
>> On Tuesday, June 4, 2019 at 12:37:21 PM UTC-4, Molly Waggett wrote:
>>>
>>> Hi all,
>>>
>>> We have enabled repositories on release-archives.puppet.com.
>>>
>>> If you're using Puppet 3, install the puppet-archives-release-* packages.
>>> If you're using Puppet 4, install the puppetlabs-release-pc1-* packages.
>>>
>>> We do not yet have a timeline for when these packages will be 
>>> re-archived from the main {yum,apt}.puppet.com sites, but we'll let you 
>>> know when we do. 
>>> Nonetheless, we recommend switching to these archive repositories as 
>>> soon as possible.
>>>
>>> Thanks for bearing with us!
>>>
>> -- 
>> 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 puppet...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/71411a67-f71e-47df-8e6e-915cebcc6e2b%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> *Molly Waggett*
> she/her/hers
> Release Engineer @ Puppet, Inc.
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/7e8f2e8c-e611-45b9-94e3-004c42c42feb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Molly Waggett]

Hi Michael,

The puppetlabs-release-pc1 packages on yum.puppetlabs.com are the ones we
plan to re-archive. You will need to install new release packages from
http://release-archives.puppet.com/yum/ if you want to continue using the
PC1 repository. Neither of these repos will receive future updates.

If you have additional questions, please let me know!

On Wed, Jun 5, 2019 at 10:36 AM Michael Watters  wrote:

> Hello,
>
> I see the puppetlabs-release-pc1 package is available on
> yum.puppetlabs.com however it doesn't actually show as an available
> update when running "yum update".
>
> For example, here's the output on one of our servers.
>
> ```
> [root@server1 yum.repos.d]# yum update puppetlabs-release-pc1
> Loaded plugins: auto-update-debuginfo, fastestmirror, langpacks,
> versionlock
> Loading mirror speeds from cached hostfile
>  * elrepo: reflector.westga.edu
>  * epel-debuginfo: mirror.uic.edu
> No packages marked for update
> ```
>
> I *was* able to update the package using the rpm command directly however
> I'd like to avoid doing this on hundreds of nodes.
>
>
> On Tuesday, June 4, 2019 at 12:37:21 PM UTC-4, Molly Waggett wrote:
>>
>> Hi all,
>>
>> We have enabled repositories on release-archives.puppet.com.
>>
>> If you're using Puppet 3, install the puppet-archives-release-* packages.
>> If you're using Puppet 4, install the puppetlabs-release-pc1-* packages.
>>
>> We do not yet have a timeline for when these packages will be re-archived
>> from the main {yum,apt}.puppet.com sites, but we'll let you know when we
>> do.
>> Nonetheless, we recommend switching to these archive repositories as soon
>> as possible.
>>
>> Thanks for bearing with us!
>>
> --
> 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 puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/71411a67-f71e-47df-8e6e-915cebcc6e2b%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFOE68CGTA%2B0Rt%3DMN2Hzicq4-m%2BOc4SROUmHE8Pne7LFQRuTiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Michael Watters]

Hello,

I see the puppetlabs-release-pc1 package is available on yum.puppetlabs.com 
however it doesn't actually show as an available update when running "yum 
update".

For example, here's the output on one of our servers.

```
[root@server1 yum.repos.d]# yum update puppetlabs-release-pc1
Loaded plugins: auto-update-debuginfo, fastestmirror, langpacks, versionlock
Loading mirror speeds from cached hostfile
 * elrepo: reflector.westga.edu
 * epel-debuginfo: mirror.uic.edu
No packages marked for update
```

I *was* able to update the package using the rpm command directly however 
I'd like to avoid doing this on hundreds of nodes.


On Tuesday, June 4, 2019 at 12:37:21 PM UTC-4, Molly Waggett wrote:
>
> Hi all,
>
> We have enabled repositories on release-archives.puppet.com.
>
> If you're using Puppet 3, install the puppet-archives-release-* packages.
> If you're using Puppet 4, install the puppetlabs-release-pc1-* packages.
>
> We do not yet have a timeline for when these packages will be re-archived 
> from the main {yum,apt}.puppet.com sites, but we'll let you know when we 
> do. 
> Nonetheless, we recommend switching to these archive repositories as soon 
> as possible.
>
> Thanks for bearing with us!
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/71411a67-f71e-47df-8e6e-915cebcc6e2b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Molly Waggett]

Hi all,

We have enabled repositories on release-archives.puppet.com.

If you're using Puppet 3, install the puppet-archives-release-* packages.
If you're using Puppet 4, install the puppetlabs-release-pc1-* packages.

We do not yet have a timeline for when these packages will be re-archived
from the main {yum,apt}.puppet.com sites, but we'll let you know when we
do.
Nonetheless, we recommend switching to these archive repositories as soon
as possible.

Thanks for bearing with us!

On Thu, May 30, 2019 at 1:36 PM Molly Waggett 
wrote:

> Hi Michael,
>
> We don't plan to remove anything from our rsync servers at this time, so
> you should be able to continue using that as you currently are.
>
> On Thu, May 30, 2019 at 6:33 AM Michael Watters 
> wrote:
>
>> How does this change affect private mirrors?  Will rsync services be
>> available on the archive repos?
>>
>>
>> On Monday, April 22, 2019 at 5:31:09 PM UTC-4, Molly Waggett wrote:
>>>
>>> TLDR: On May 14, 1. yum release packages will move to the top-level of
>>> yum.puppet.com; 2. links to nightly release packages will be removed
>>> from {yum,apt}.puppet.com; and 3. PC1 (and older) packages will be
>>> moved to release-archives.puppet.com.
>>>
>>> All Puppet-maintained tooling and documentation referencing these paths
>>> will be updated by the time these changes are made. Please ensure that
>>> you are using current versions.
>>>
>>> Read on for details, especially if you've written custom tooling with
>>> hard-coded download paths (e.g. CI testing or provisioning workflows).
>>>
>>> ---*---*---
>>>
>>> Hey folks,
>>>
>>> In an effort to reduce clutter and confusion on some of our public
>>> download sites (yum.puppet.com, apt.puppet.com, downloads.puppet.com,
>>> and nightlies.puppet.com), we are planning to make some changes.
>>>
>>> 1. Release packages (for all active streams) will live at the top level
>>> only.
>>>
>>> This change only affects yum.puppet.com (and nightlies.puppet.com/yum),
>>> giving us consistency with the layout on apt.puppet.com. Currently, yum
>>> release packages live inside their corresponding repo directory, e.g.
>>> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm
>>> .
>>> THESE WILL BE REMOVED.
>>>
>>> Here are some examples of where you will be able to find release
>>> packages:
>>>
>>> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>>>
>>> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>>>
>>> Old: nightlies.puppet.com/yum/puppet-nightly/
>>> puppet-nightly-release-sles-12.noarch.rpm
>>>
>>> New: nightlies.puppet.com/yum/puppet-nightly-release-sles-12.noarch.rpm
>>>
>>> These new paths are currently available for use. We plan to remove the
>>> old ones on May 14. Please plan to make all updates during this period.
>>>
>>> 2. There will be no links to nightlies from main download sites.
>>>
>>> Links like yum.puppet.com/puppet-nightly
>>>  and
>>> apt.puppet.com/puppet-nightly
>>>  WILL BE REMOVED on May 14.
>>>
>>> If you're looking for nightlies, visit nightlies.puppet.com. The
>>> directory structure will match that of our main download sites.
>>>
>>> 3. All PC1 (and older) packages will be removed from {yum, apt,
>>> downloads}.puppet.com.
>>>
>>> PC1 (which includes puppet-agent 1.10.x and puppet 4.10.x) is reaching
>>> end-of-life, so all packages will be moved to
>>> release-archives.puppet.com on May 14 and no further updates will be
>>> made to these streams.
>>>
>>> ---*---*---
>>>
>>> We have set up a temporary s3 bucket that reflects the new layout if
>>> you’d like to test changes before the cutover:
>>> yum-test.puppet.com.s3-website-us-west-2.amazonaws.com
>>>
>>> PLEASE NOTE that s3 buckets are not naturally browsable on the web. If
>>> you visit the above url in your browser, the info you'll see is NOT
>>> ACCURATE. You CAN, however, download packages via wget/curl/etc. so this
>>> should only affect human eyes.
>>>
>>> If you have any questions or concerns about these changes, please
>>> reply-all to this email.
>>>
>>> Thanks!
>>>
>>> --
>>> *Molly Waggett*
>>> she/her/hers
>>> Release Engineer @ Puppet, Inc.
>>>
>> --
>> 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 puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/67d776c9-7490-4113-8220-580a838098f4%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> *Molly Waggett*
> she/her/hers
> Release Engineer @ Puppet, Inc.
>


-- 
*Molly Waggett*
she/her/hers

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Molly Waggett]

Hi Michael,

We don't plan to remove anything from our rsync servers at this time, so
you should be able to continue using that as you currently are.

On Thu, May 30, 2019 at 6:33 AM Michael Watters  wrote:

> How does this change affect private mirrors?  Will rsync services be
> available on the archive repos?
>
>
> On Monday, April 22, 2019 at 5:31:09 PM UTC-4, Molly Waggett wrote:
>>
>> TLDR: On May 14, 1. yum release packages will move to the top-level of
>> yum.puppet.com; 2. links to nightly release packages will be removed
>> from {yum,apt}.puppet.com; and 3. PC1 (and older) packages will be moved
>> to release-archives.puppet.com.
>>
>> All Puppet-maintained tooling and documentation referencing these paths
>> will be updated by the time these changes are made. Please ensure that
>> you are using current versions.
>>
>> Read on for details, especially if you've written custom tooling with
>> hard-coded download paths (e.g. CI testing or provisioning workflows).
>>
>> ---*---*---
>>
>> Hey folks,
>>
>> In an effort to reduce clutter and confusion on some of our public
>> download sites (yum.puppet.com, apt.puppet.com, downloads.puppet.com,
>> and nightlies.puppet.com), we are planning to make some changes.
>>
>> 1. Release packages (for all active streams) will live at the top level
>> only.
>>
>> This change only affects yum.puppet.com (and nightlies.puppet.com/yum),
>> giving us consistency with the layout on apt.puppet.com. Currently, yum
>> release packages live inside their corresponding repo directory, e.g.
>> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm
>> .
>> THESE WILL BE REMOVED.
>>
>> Here are some examples of where you will be able to find release packages:
>>
>> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>>
>> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>>
>> Old: nightlies.puppet.com/yum/puppet-nightly/
>> puppet-nightly-release-sles-12.noarch.rpm
>>
>> New: nightlies.puppet.com/yum/puppet-nightly-release-sles-12.noarch.rpm
>>
>> These new paths are currently available for use. We plan to remove the
>> old ones on May 14. Please plan to make all updates during this period.
>>
>> 2. There will be no links to nightlies from main download sites.
>>
>> Links like yum.puppet.com/puppet-nightly
>>  and
>> apt.puppet.com/puppet-nightly 
>> WILL BE REMOVED on May 14.
>>
>> If you're looking for nightlies, visit nightlies.puppet.com. The
>> directory structure will match that of our main download sites.
>>
>> 3. All PC1 (and older) packages will be removed from {yum, apt,
>> downloads}.puppet.com.
>>
>> PC1 (which includes puppet-agent 1.10.x and puppet 4.10.x) is reaching
>> end-of-life, so all packages will be moved to release-archives.puppet.com
>> on May 14 and no further updates will be made to these streams.
>>
>> ---*---*---
>>
>> We have set up a temporary s3 bucket that reflects the new layout if
>> you’d like to test changes before the cutover:
>> yum-test.puppet.com.s3-website-us-west-2.amazonaws.com
>>
>> PLEASE NOTE that s3 buckets are not naturally browsable on the web. If
>> you visit the above url in your browser, the info you'll see is NOT
>> ACCURATE. You CAN, however, download packages via wget/curl/etc. so this
>> should only affect human eyes.
>>
>> If you have any questions or concerns about these changes, please
>> reply-all to this email.
>>
>> Thanks!
>>
>> --
>> *Molly Waggett*
>> she/her/hers
>> Release Engineer @ Puppet, Inc.
>>
> --
> 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 puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/67d776c9-7490-4113-8220-580a838098f4%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFOE68DUmWr7sM5mFtev7HP1_737MnnWNqMGnoV-75zSdSu5EQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: [ACTION] Changes to release package links

[Michael Watters]

How does this change affect private mirrors?  Will rsync services be 
available on the archive repos?


On Monday, April 22, 2019 at 5:31:09 PM UTC-4, Molly Waggett wrote:
>
> TLDR: On May 14, 1. yum release packages will move to the top-level of 
> yum.puppet.com; 2. links to nightly release packages will be removed from 
> {yum,apt}.puppet.com; and 3. PC1 (and older) packages will be moved to 
> release-archives.puppet.com. 
>
> All Puppet-maintained tooling and documentation referencing these paths 
> will be updated by the time these changes are made. Please ensure that 
> you are using current versions.
>
> Read on for details, especially if you've written custom tooling with 
> hard-coded download paths (e.g. CI testing or provisioning workflows).
>
> ---*---*---
>
> Hey folks,
>
> In an effort to reduce clutter and confusion on some of our public 
> download sites (yum.puppet.com, apt.puppet.com, downloads.puppet.com, and 
> nightlies.puppet.com), we are planning to make some changes. 
>
> 1. Release packages (for all active streams) will live at the top level 
> only. 
>
> This change only affects yum.puppet.com (and nightlies.puppet.com/yum), 
> giving us consistency with the layout on apt.puppet.com. Currently, yum 
> release packages live inside their corresponding repo directory, e.g. 
> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm 
> . 
> THESE WILL BE REMOVED. 
>
> Here are some examples of where you will be able to find release packages:
>
> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>
> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>
> Old: nightlies.puppet.com/yum/puppet-nightly/
> puppet-nightly-release-sles-12.noarch.rpm
>
> New: nightlies.puppet.com/yum/puppet-nightly-release-sles-12.noarch.rpm
>
> These new paths are currently available for use. We plan to remove the 
> old ones on May 14. Please plan to make all updates during this period. 
>
> 2. There will be no links to nightlies from main download sites.
>
> Links like yum.puppet.com/puppet-nightly 
>  and 
> apt.puppet.com/puppet-nightly  
> WILL BE REMOVED on May 14.
>
> If you're looking for nightlies, visit nightlies.puppet.com. The 
> directory structure will match that of our main download sites.
>
> 3. All PC1 (and older) packages will be removed from {yum, apt, downloads}.
> puppet.com. 
>
> PC1 (which includes puppet-agent 1.10.x and puppet 4.10.x) is reaching 
> end-of-life, so all packages will be moved to release-archives.puppet.com 
> on May 14 and no further updates will be made to these streams.
>
> ---*---*---
>
> We have set up a temporary s3 bucket that reflects the new layout if you’d 
> like to test changes before the cutover:  
> yum-test.puppet.com.s3-website-us-west-2.amazonaws.com
>
> PLEASE NOTE that s3 buckets are not naturally browsable on the web. If 
> you visit the above url in your browser, the info you'll see is NOT 
> ACCURATE. You CAN, however, download packages via wget/curl/etc. so this 
> should only affect human eyes.
>
> If you have any questions or concerns about these changes, please 
> reply-all to this email.
>
> Thanks!
>
> -- 
> *Molly Waggett*
> she/her/hers
> Release Engineer @ Puppet, Inc.
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/67d776c9-7490-4113-8220-580a838098f4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Yosuke Adachi]

Hi Molly,

Alright, I will make a change to use the correct location as soon as I can.
I will keep eyes on this thread for a update schedule.

Thank you.

Yosuke

On Friday, May 24, 2019 at 6:19:14 PM UTC+1, Molly Waggett wrote:
>
> Hi Yosuke,
>
> We will likely remove the release packages from the subdirectories 
> *before* the archives are ready. I'll send an update next week when we 
> have a better sense of the timeline.
>
> Let us know if you have any concerns.
>
> Thanks!
>
> On Thu, May 23, 2019 at 1:13 PM Yosuke Adachi wrote:
>
>> Hi Molly,
>>
>> When are you planning to remove release packages from 
>> yum.puppet.com/puppet6/ or puppet5/ sub directory (e.g. yum.puppet.com/
>> puppet6/puppet6-release-el-7.noarch.rpm) ?
>> Is it same timing as when the release-archive repository is ready?
>>
>>
>> Kind regards
>> Yosuke
>>
>> On Monday, May 6, 2019 at 11:16:25 PM UTC+1, Molly Waggett wrote:
>>>
>>> Hey folks,
>>>
>>> REMINDER that the repository path changes* will take effect next week, 
>>> on Tuesday, May 14.
>>>
>>> Please make sure any custom tooling using these paths has been updated.
>>>
>>> If you have any questions or concerns, please reply-all to this email.
>>>
>>> Thanks!
>>>
>>> * in case you forgot, changes include:
>>>
>>> 1. yum release packages will be removed from nested directories on 
>>> yum.puppet.com (e.g. yum.puppet.com/puppet6/
>>> puppet6-release-el-7.noarch.rpm
>>>
>>> --> yum.puppet.com/puppet6-release-el-7.noarch.rpm).
>>>
>>> PLEASE NOTE that these are actually symlinks to release packages that 
>>> live inside their respective repositories, so package updates can be 
>>> applied via your package manager, like any other package.
>>>
>>> 2. links to nightly release packages will be removed from {yum,apt}.
>>> puppet.com.
>>> 3. PC1 (and older) packages will be moved to release-archives.puppet.com. 
>>> This includes puppet-agent 1.10.x and puppet 4.x.
>>>
>>> On Tue, Apr 23, 2019 at 9:13 AM Molly Waggett  
>>> wrote:
>>>
 Hi John,

 The top-level release packages are actually symlinks to release 
 packages that *are* inside their respective repositories. When we 
 publish new release packages, we update those links so that users don't 
 have to bump version numbers in any tooling that installs these 
 repositories.

 Thanks!

 On Tue, Apr 23, 2019 at 6:21 AM jcbollinger  
 wrote:

>
>
> On Monday, April 22, 2019 at 4:31:09 PM UTC-5, Molly Waggett wrote:
>>
>> 1. Release packages (for all active streams) will live at the top 
>> level only. 
>>
>> This change only affects yum.puppet.com (and nightlies.puppet.com/yum
>> ), giving us consistency with the layout on apt.puppet.com. 
>> Currently, yum release packages live inside their corresponding repo 
>> directory, e.g. yum.puppet.com/puppet6/
>> puppet6-release-fedora-28.noarch.rpm 
>> .
>>  
>> THESE WILL BE REMOVED. 
>>
>> Here are some examples of where you will be able to find release 
>> packages:
>>
>> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>>
>> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>>
>>
> It is conventional for repository release packages to be inside their 
> repositories so that repository configuration updates can be published 
> and 
> applied via the same mechanism that is used for ordinary packages.  Even 
> if 
> this is a capability that Puppet rarely uses, it seems ill-considered to 
> give it up.  The desire for consistency could be as well served by moving 
> the other release packages into their repos, or by making the release 
> packages consistently  available in both places.
>
>
> John
>
> -- 
> 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 puppet...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/c711eeca-239c-4022-8f4b-55f9ea577c8d%40googlegroups.com
>  
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


 -- 
 *Molly Waggett*
 she/her/hers
 Release Engineer @ Puppet, Inc.

>>>
>>>
>>> -- 
>>> *Molly Waggett*
>>> she/her/hers
>>> Release Engineer @ Puppet, Inc.
>>>
>> -- 
>> 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 puppet...@googlegroups.com .
>> To view this discussion on the web visit 
>> 

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Molly Waggett]

Hi Yosuke,

We will likely remove the release packages from the subdirectories *before* the
archives are ready. I'll send an update next week when we have a better
sense of the timeline.

Let us know if you have any concerns.

Thanks!

On Thu, May 23, 2019 at 1:13 PM Yosuke Adachi  wrote:

> Hi Molly,
>
> When are you planning to remove release packages from
> yum.puppet.com/puppet6/ or puppet5/ sub directory (e.g. yum.puppet.com/
> puppet6/puppet6-release-el-7.noarch.rpm) ?
> Is it same timing as when the release-archive repository is ready?
>
>
> Kind regards
> Yosuke
>
> On Monday, May 6, 2019 at 11:16:25 PM UTC+1, Molly Waggett wrote:
>>
>> Hey folks,
>>
>> REMINDER that the repository path changes* will take effect next week,
>> on Tuesday, May 14.
>>
>> Please make sure any custom tooling using these paths has been updated.
>>
>> If you have any questions or concerns, please reply-all to this email.
>>
>> Thanks!
>>
>> * in case you forgot, changes include:
>>
>> 1. yum release packages will be removed from nested directories on
>> yum.puppet.com (e.g. yum.puppet.com/puppet6/
>> puppet6-release-el-7.noarch.rpm
>>
>> --> yum.puppet.com/puppet6-release-el-7.noarch.rpm).
>>
>> PLEASE NOTE that these are actually symlinks to release packages that
>> live inside their respective repositories, so package updates can be
>> applied via your package manager, like any other package.
>>
>> 2. links to nightly release packages will be removed from {yum,apt}.
>> puppet.com.
>> 3. PC1 (and older) packages will be moved to release-archives.puppet.com.
>> This includes puppet-agent 1.10.x and puppet 4.x.
>>
>> On Tue, Apr 23, 2019 at 9:13 AM Molly Waggett 
>> wrote:
>>
>>> Hi John,
>>>
>>> The top-level release packages are actually symlinks to release packages
>>> that *are* inside their respective repositories. When we publish new
>>> release packages, we update those links so that users don't have to bump
>>> version numbers in any tooling that installs these repositories.
>>>
>>> Thanks!
>>>
>>> On Tue, Apr 23, 2019 at 6:21 AM jcbollinger 
>>> wrote:
>>>


 On Monday, April 22, 2019 at 4:31:09 PM UTC-5, Molly Waggett wrote:
>
> 1. Release packages (for all active streams) will live at the top
> level only.
>
> This change only affects yum.puppet.com (and nightlies.puppet.com/yum),
> giving us consistency with the layout on apt.puppet.com. Currently,
> yum release packages live inside their corresponding repo directory, e.g.
> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm
> .
> THESE WILL BE REMOVED.
>
> Here are some examples of where you will be able to find release
> packages:
>
> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>
> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>
>
 It is conventional for repository release packages to be inside their
 repositories so that repository configuration updates can be published and
 applied via the same mechanism that is used for ordinary packages.  Even if
 this is a capability that Puppet rarely uses, it seems ill-considered to
 give it up.  The desire for consistency could be as well served by moving
 the other release packages into their repos, or by making the release
 packages consistently  available in both places.


 John

 --
 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 puppet...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/puppet-users/c711eeca-239c-4022-8f4b-55f9ea577c8d%40googlegroups.com
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>> --
>>> *Molly Waggett*
>>> she/her/hers
>>> Release Engineer @ Puppet, Inc.
>>>
>>
>>
>> --
>> *Molly Waggett*
>> she/her/hers
>> Release Engineer @ Puppet, Inc.
>>
> --
> 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 puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/6770a73d-bfbb-4445-92af-239f798ee0af%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet 

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Yosuke Adachi]

Hi Molly,

When are you planning to remove release packages from 
yum.puppet.com/puppet6/ or puppet5/ sub directory (e.g. yum.puppet.com/
puppet6/puppet6-release-el-7.noarch.rpm) ?
Is it same timing as when the release-archive repository is ready?


Kind regards
Yosuke

On Monday, May 6, 2019 at 11:16:25 PM UTC+1, Molly Waggett wrote:
>
> Hey folks,
>
> REMINDER that the repository path changes* will take effect next week, on 
> Tuesday, 
> May 14.
>
> Please make sure any custom tooling using these paths has been updated.
>
> If you have any questions or concerns, please reply-all to this email.
>
> Thanks!
>
> * in case you forgot, changes include:
>
> 1. yum release packages will be removed from nested directories on 
> yum.puppet.com (e.g. yum.puppet.com/puppet6/
> puppet6-release-el-7.noarch.rpm
>
> --> yum.puppet.com/puppet6-release-el-7.noarch.rpm).
>
> PLEASE NOTE that these are actually symlinks to release packages that live 
> inside their respective repositories, so package updates can be applied via 
> your package manager, like any other package.
>
> 2. links to nightly release packages will be removed from {yum,apt}.
> puppet.com.
> 3. PC1 (and older) packages will be moved to release-archives.puppet.com. 
> This includes puppet-agent 1.10.x and puppet 4.x.
>
> On Tue, Apr 23, 2019 at 9:13 AM Molly Waggett  > wrote:
>
>> Hi John,
>>
>> The top-level release packages are actually symlinks to release packages 
>> that *are* inside their respective repositories. When we publish new 
>> release packages, we update those links so that users don't have to bump 
>> version numbers in any tooling that installs these repositories.
>>
>> Thanks!
>>
>> On Tue, Apr 23, 2019 at 6:21 AM jcbollinger > > wrote:
>>
>>>
>>>
>>> On Monday, April 22, 2019 at 4:31:09 PM UTC-5, Molly Waggett wrote:

 1. Release packages (for all active streams) will live at the top level 
 only. 

 This change only affects yum.puppet.com (and nightlies.puppet.com/yum), 
 giving us consistency with the layout on apt.puppet.com. Currently, 
 yum release packages live inside their corresponding repo directory, e.g. 
 yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm 
 . 
 THESE WILL BE REMOVED. 

 Here are some examples of where you will be able to find release 
 packages:

 Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm

 New: yum.puppet.com/puppet6-release-el-7.noarch.rpm


>>> It is conventional for repository release packages to be inside their 
>>> repositories so that repository configuration updates can be published and 
>>> applied via the same mechanism that is used for ordinary packages.  Even if 
>>> this is a capability that Puppet rarely uses, it seems ill-considered to 
>>> give it up.  The desire for consistency could be as well served by moving 
>>> the other release packages into their repos, or by making the release 
>>> packages consistently  available in both places.
>>>
>>>
>>> John
>>>
>>> -- 
>>> 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 puppet...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/puppet-users/c711eeca-239c-4022-8f4b-55f9ea577c8d%40googlegroups.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> -- 
>> *Molly Waggett*
>> she/her/hers
>> Release Engineer @ Puppet, Inc.
>>
>
>
> -- 
> *Molly Waggett*
> she/her/hers
> Release Engineer @ Puppet, Inc.
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/6770a73d-bfbb-4445-92af-239f798ee0af%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Morgan Rhodes]

We're still working on getting repositories set up on
release-archives.puppet.com. You can follow along with progress at
tickets.puppetlabs.com/browse/CPR-685

On Mon, May 20, 2019 at 12:21 PM choffee  wrote:

> So what at the new URL's for PC1 using apt? Just changing the hostname
> does not work, neither does adding the /apt prefix. It looks like the pool
> directory has been copied across but no the dist dir.
>
> The puppetlabs-release-pc1 package is also broken now so there is no
> simple way to install that I can see.
>
> Thanks
>
> john
>
> On Wednesday, 15 May 2019 16:14:00 UTC+1, Bob Vincent wrote:
>>
>> First sign of breakage: https://tickets.puppetlabs.com/browse/BKR-1590
>>
>> Fixed here: https://github.com/puppetlabs/beaker-puppet/pull/113
>>
>> On Monday, May 6, 2019 at 6:16:25 PM UTC-4, Molly Waggett wrote:
>>>
>>> Hey folks,
>>>
>>> REMINDER that the repository path changes* will take effect next week,
>>> on Tuesday, May 14.
>>>
>>> Please make sure any custom tooling using these paths has been updated.
>>>
>>> If you have any questions or concerns, please reply-all to this email.
>>>
>>> Thanks!
>>>
>>> * in case you forgot, changes include:
>>>
>>> 1. yum release packages will be removed from nested directories on
>>> yum.puppet.com (e.g. yum.puppet.com/puppet6/
>>> puppet6-release-el-7.noarch.rpm
>>>
>>> --> yum.puppet.com/puppet6-release-el-7.noarch.rpm).
>>>
>>> PLEASE NOTE that these are actually symlinks to release packages that
>>> live inside their respective repositories, so package updates can be
>>> applied via your package manager, like any other package.
>>>
>>> 2. links to nightly release packages will be removed from {yum,apt}.
>>> puppet.com.
>>> 3. PC1 (and older) packages will be moved to release-archives.puppet.com.
>>> This includes puppet-agent 1.10.x and puppet 4.x.
>>>
>>> On Tue, Apr 23, 2019 at 9:13 AM Molly Waggett 
>>> wrote:
>>>
 Hi John,

 The top-level release packages are actually symlinks to release
 packages that *are* inside their respective repositories. When we
 publish new release packages, we update those links so that users don't
 have to bump version numbers in any tooling that installs these
 repositories.

 Thanks!

 On Tue, Apr 23, 2019 at 6:21 AM jcbollinger 
 wrote:

>
>
> On Monday, April 22, 2019 at 4:31:09 PM UTC-5, Molly Waggett wrote:
>>
>> 1. Release packages (for all active streams) will live at the top
>> level only.
>>
>> This change only affects yum.puppet.com (and nightlies.puppet.com/yum
>> ), giving us consistency with the layout on apt.puppet.com.
>> Currently, yum release packages live inside their corresponding repo
>> directory, e.g. yum.puppet.com/puppet6/
>> puppet6-release-fedora-28.noarch.rpm
>> .
>> THESE WILL BE REMOVED.
>>
>> Here are some examples of where you will be able to find release
>> packages:
>>
>> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>>
>> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>>
>>
> It is conventional for repository release packages to be inside their
> repositories so that repository configuration updates can be published and
> applied via the same mechanism that is used for ordinary packages.  Even 
> if
> this is a capability that Puppet rarely uses, it seems ill-considered to
> give it up.  The desire for consistency could be as well served by moving
> the other release packages into their repos, or by making the release
> packages consistently  available in both places.
>
>
> John
>
> --
> 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 puppet...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/c711eeca-239c-4022-8f4b-55f9ea577c8d%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


 --
 *Molly Waggett*
 she/her/hers
 Release Engineer @ Puppet, Inc.

>>>
>>>
>>> --
>>> *Molly Waggett*
>>> she/her/hers
>>> Release Engineer @ Puppet, Inc.
>>>
>> --
> 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 puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/003ef1cb-1038-4a82-a9ab-8b2921dc999e%40googlegroups.com
> 

[Puppet Users] Re: [ACTION] Changes to release package links

[Greg Delisle]

As of this morning I notice that the old directories have been restored 
under yum.puppetlabs.com -- the el/fedora repos, the puppet-nightly 
directories, the pc1 stuff, everything. 


On Wednesday, May 15, 2019 at 7:04:53 PM UTC-4, Chris Taylor wrote:
>
> Try 
> http://release-archives.puppet.com/yum/el/7/PC1/x86_64/puppetlabs-release-pc1-1.1.0-5.el7.noarch.rpm
>
> Just be aware it will probably install a repo with yum.puppetlabs.com 
> into /etc/yum.repos.d/, so you will need to update the path to the 
> appropriate place.
>
>
> On Wednesday, May 15, 2019 at 11:25:19 PM UTC+1, michael mack wrote:
>>
>> How do you get the following old repo to work?
>>
>> rpm -Uvh 
>> https://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm
>>
>>
>> On Monday, April 22, 2019 at 2:31:09 PM UTC-7, Molly Waggett wrote:
>>>
>>> TLDR: On May 14, 1. yum release packages will move to the top-level of 
>>> yum.puppet.com; 2. links to nightly release packages will be removed 
>>> from {yum,apt}.puppet.com; and 3. PC1 (and older) packages will be 
>>> moved to release-archives.puppet.com. 
>>>
>>> All Puppet-maintained tooling and documentation referencing these paths 
>>> will be updated by the time these changes are made. Please ensure that 
>>> you are using current versions.
>>>
>>> Read on for details, especially if you've written custom tooling with 
>>> hard-coded download paths (e.g. CI testing or provisioning workflows).
>>>
>>> ---*---*---
>>>
>>> Hey folks,
>>>
>>> In an effort to reduce clutter and confusion on some of our public 
>>> download sites (yum.puppet.com, apt.puppet.com, downloads.puppet.com, 
>>> and nightlies.puppet.com), we are planning to make some changes. 
>>>
>>> 1. Release packages (for all active streams) will live at the top level 
>>> only. 
>>>
>>> This change only affects yum.puppet.com (and nightlies.puppet.com/yum), 
>>> giving us consistency with the layout on apt.puppet.com. Currently, yum 
>>> release packages live inside their corresponding repo directory, e.g. 
>>> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm 
>>> . 
>>> THESE WILL BE REMOVED. 
>>>
>>> Here are some examples of where you will be able to find release 
>>> packages:
>>>
>>> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>>>
>>> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>>>
>>> Old: nightlies.puppet.com/yum/puppet-nightly/
>>> puppet-nightly-release-sles-12.noarch.rpm
>>>
>>> New: nightlies.puppet.com/yum/puppet-nightly-release-sles-12.noarch.rpm
>>>
>>> These new paths are currently available for use. We plan to remove the 
>>> old ones on May 14. Please plan to make all updates during this period. 
>>>
>>> 2. There will be no links to nightlies from main download sites.
>>>
>>> Links like yum.puppet.com/puppet-nightly 
>>>  and 
>>> apt.puppet.com/puppet-nightly 
>>>  WILL BE REMOVED on May 14.
>>>
>>> If you're looking for nightlies, visit nightlies.puppet.com. The 
>>> directory structure will match that of our main download sites.
>>>
>>> 3. All PC1 (and older) packages will be removed from {yum, apt, 
>>> downloads}.puppet.com. 
>>>
>>> PC1 (which includes puppet-agent 1.10.x and puppet 4.10.x) is reaching 
>>> end-of-life, so all packages will be moved to 
>>> release-archives.puppet.com on May 14 and no further updates will be 
>>> made to these streams.
>>>
>>> ---*---*---
>>>
>>> We have set up a temporary s3 bucket that reflects the new layout if 
>>> you’d like to test changes before the cutover:  
>>> yum-test.puppet.com.s3-website-us-west-2.amazonaws.com
>>>
>>> PLEASE NOTE that s3 buckets are not naturally browsable on the web. If 
>>> you visit the above url in your browser, the info you'll see is NOT 
>>> ACCURATE. You CAN, however, download packages via wget/curl/etc. so this 
>>> should only affect human eyes.
>>>
>>> If you have any questions or concerns about these changes, please 
>>> reply-all to this email.
>>>
>>> Thanks!
>>>
>>> -- 
>>> *Molly Waggett*
>>> she/her/hers
>>> Release Engineer @ Puppet, Inc.
>>>
>>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/23bf2a97-48bf-4110-a2f9-063f19a14567%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[choffee]

So what at the new URL's for PC1 using apt? Just changing the hostname does 
not work, neither does adding the /apt prefix. It looks like the pool 
directory has been copied across but no the dist dir.

The puppetlabs-release-pc1 package is also broken now so there is no simple 
way to install that I can see.

Thanks

john

On Wednesday, 15 May 2019 16:14:00 UTC+1, Bob Vincent wrote:
>
> First sign of breakage: https://tickets.puppetlabs.com/browse/BKR-1590
>
> Fixed here: https://github.com/puppetlabs/beaker-puppet/pull/113
>
> On Monday, May 6, 2019 at 6:16:25 PM UTC-4, Molly Waggett wrote:
>>
>> Hey folks,
>>
>> REMINDER that the repository path changes* will take effect next week, 
>> on Tuesday, May 14.
>>
>> Please make sure any custom tooling using these paths has been updated.
>>
>> If you have any questions or concerns, please reply-all to this email.
>>
>> Thanks!
>>
>> * in case you forgot, changes include:
>>
>> 1. yum release packages will be removed from nested directories on 
>> yum.puppet.com (e.g. yum.puppet.com/puppet6/
>> puppet6-release-el-7.noarch.rpm
>>
>> --> yum.puppet.com/puppet6-release-el-7.noarch.rpm).
>>
>> PLEASE NOTE that these are actually symlinks to release packages that 
>> live inside their respective repositories, so package updates can be 
>> applied via your package manager, like any other package.
>>
>> 2. links to nightly release packages will be removed from {yum,apt}.
>> puppet.com.
>> 3. PC1 (and older) packages will be moved to release-archives.puppet.com. 
>> This includes puppet-agent 1.10.x and puppet 4.x.
>>
>> On Tue, Apr 23, 2019 at 9:13 AM Molly Waggett  
>> wrote:
>>
>>> Hi John,
>>>
>>> The top-level release packages are actually symlinks to release packages 
>>> that *are* inside their respective repositories. When we publish new 
>>> release packages, we update those links so that users don't have to bump 
>>> version numbers in any tooling that installs these repositories.
>>>
>>> Thanks!
>>>
>>> On Tue, Apr 23, 2019 at 6:21 AM jcbollinger  
>>> wrote:
>>>


 On Monday, April 22, 2019 at 4:31:09 PM UTC-5, Molly Waggett wrote:
>
> 1. Release packages (for all active streams) will live at the top 
> level only. 
>
> This change only affects yum.puppet.com (and nightlies.puppet.com/yum), 
> giving us consistency with the layout on apt.puppet.com. Currently, 
> yum release packages live inside their corresponding repo directory, e.g. 
> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm 
> . 
> THESE WILL BE REMOVED. 
>
> Here are some examples of where you will be able to find release 
> packages:
>
> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>
> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>
>
 It is conventional for repository release packages to be inside their 
 repositories so that repository configuration updates can be published and 
 applied via the same mechanism that is used for ordinary packages.  Even 
 if 
 this is a capability that Puppet rarely uses, it seems ill-considered to 
 give it up.  The desire for consistency could be as well served by moving 
 the other release packages into their repos, or by making the release 
 packages consistently  available in both places.


 John

 -- 
 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 puppet...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/puppet-users/c711eeca-239c-4022-8f4b-55f9ea577c8d%40googlegroups.com
  
 
 .
 For more options, visit https://groups.google.com/d/optout.

>>>
>>>
>>> -- 
>>> *Molly Waggett*
>>> she/her/hers
>>> Release Engineer @ Puppet, Inc.
>>>
>>
>>
>> -- 
>> *Molly Waggett*
>> she/her/hers
>> Release Engineer @ Puppet, Inc.
>>
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/003ef1cb-1038-4a82-a9ab-8b2921dc999e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Molly Waggett]

Hi all,

As you may have seen, the packages we removed from {yum,apt}.puppetlabs.com
this week have been put back. This was due to an outage and the need to
restore from backups.

While we originally did not intend to enable repositories on
release-archives.puppet.com, the overwhelming demand has made this a
priority for us. We will keep the EOL packages on {yum,apt}.puppetlabs.com
until that work is done, but then they will be re-archived. You can follow
along here: https://tickets.puppetlabs.com/browse/CPR-685

To provide some clarity:

   - The puppetlabs-release-* repos contain puppet 3 packages. THESE WILL
   BE ARCHIVED. You will soon be able to find them at
   http://release-archives.puppet.com/yum/puppet-archives-release-*.
   - The puppetlabs-release-pc1-* repos contain puppet 4 packages. THESE
   WILL BE ARCHIVED. You will soon be able to find them at
   http://release-archives.puppet.com/yum/puppetlabs-release-pc1-*.
   - puppet-release-* is our rolling repository, which always points to our
   latest software stream. This is currently puppet 6.

If you have any questions, please feel free to reach out.

Thanks!



On Wed, May 15, 2019 at 4:04 PM Chris Taylor  wrote:

> Try
> http://release-archives.puppet.com/yum/el/7/PC1/x86_64/puppetlabs-release-pc1-1.1.0-5.el7.noarch.rpm
>
> Just be aware it will probably install a repo with yum.puppetlabs.com
> into /etc/yum.repos.d/, so you will need to update the path to the
> appropriate place.
>
>
> On Wednesday, May 15, 2019 at 11:25:19 PM UTC+1, michael mack wrote:
>>
>> How do you get the following old repo to work?
>>
>> rpm -Uvh
>> https://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm
>>
>>
>> On Monday, April 22, 2019 at 2:31:09 PM UTC-7, Molly Waggett wrote:
>>>
>>> TLDR: On May 14, 1. yum release packages will move to the top-level of
>>> yum.puppet.com; 2. links to nightly release packages will be removed
>>> from {yum,apt}.puppet.com; and 3. PC1 (and older) packages will be
>>> moved to release-archives.puppet.com.
>>>
>>> All Puppet-maintained tooling and documentation referencing these paths
>>> will be updated by the time these changes are made. Please ensure that
>>> you are using current versions.
>>>
>>> Read on for details, especially if you've written custom tooling with
>>> hard-coded download paths (e.g. CI testing or provisioning workflows).
>>>
>>> ---*---*---
>>>
>>> Hey folks,
>>>
>>> In an effort to reduce clutter and confusion on some of our public
>>> download sites (yum.puppet.com, apt.puppet.com, downloads.puppet.com,
>>> and nightlies.puppet.com), we are planning to make some changes.
>>>
>>> 1. Release packages (for all active streams) will live at the top level
>>> only.
>>>
>>> This change only affects yum.puppet.com (and nightlies.puppet.com/yum),
>>> giving us consistency with the layout on apt.puppet.com. Currently, yum
>>> release packages live inside their corresponding repo directory, e.g.
>>> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm
>>> .
>>> THESE WILL BE REMOVED.
>>>
>>> Here are some examples of where you will be able to find release
>>> packages:
>>>
>>> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>>>
>>> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>>>
>>> Old: nightlies.puppet.com/yum/puppet-nightly/
>>> puppet-nightly-release-sles-12.noarch.rpm
>>>
>>> New: nightlies.puppet.com/yum/puppet-nightly-release-sles-12.noarch.rpm
>>>
>>> These new paths are currently available for use. We plan to remove the
>>> old ones on May 14. Please plan to make all updates during this period.
>>>
>>> 2. There will be no links to nightlies from main download sites.
>>>
>>> Links like yum.puppet.com/puppet-nightly
>>>  and
>>> apt.puppet.com/puppet-nightly
>>>  WILL BE REMOVED on May 14.
>>>
>>> If you're looking for nightlies, visit nightlies.puppet.com. The
>>> directory structure will match that of our main download sites.
>>>
>>> 3. All PC1 (and older) packages will be removed from {yum, apt,
>>> downloads}.puppet.com.
>>>
>>> PC1 (which includes puppet-agent 1.10.x and puppet 4.10.x) is reaching
>>> end-of-life, so all packages will be moved to
>>> release-archives.puppet.com on May 14 and no further updates will be
>>> made to these streams.
>>>
>>> ---*---*---
>>>
>>> We have set up a temporary s3 bucket that reflects the new layout if
>>> you’d like to test changes before the cutover:
>>> yum-test.puppet.com.s3-website-us-west-2.amazonaws.com
>>>
>>> PLEASE NOTE that s3 buckets are not naturally browsable on the web. If
>>> you visit the above url in your browser, the info you'll see is NOT
>>> ACCURATE. You CAN, however, download packages via wget/curl/etc. so this
>>> should only affect human eyes.
>>>
>>> If you have any questions or concerns about these changes, please
>>> reply-all to this email.
>>>
>>> 

[Puppet Users] Re: [ACTION] Changes to release package links

[Chris Taylor]

Try 
http://release-archives.puppet.com/yum/el/7/PC1/x86_64/puppetlabs-release-pc1-1.1.0-5.el7.noarch.rpm

Just be aware it will probably install a repo with yum.puppetlabs.com into 
/etc/yum.repos.d/, so you will need to update the path to the appropriate 
place.


On Wednesday, May 15, 2019 at 11:25:19 PM UTC+1, michael mack wrote:
>
> How do you get the following old repo to work?
>
> rpm -Uvh https://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm
>
>
> On Monday, April 22, 2019 at 2:31:09 PM UTC-7, Molly Waggett wrote:
>>
>> TLDR: On May 14, 1. yum release packages will move to the top-level of 
>> yum.puppet.com; 2. links to nightly release packages will be removed 
>> from {yum,apt}.puppet.com; and 3. PC1 (and older) packages will be moved 
>> to release-archives.puppet.com. 
>>
>> All Puppet-maintained tooling and documentation referencing these paths 
>> will be updated by the time these changes are made. Please ensure that 
>> you are using current versions.
>>
>> Read on for details, especially if you've written custom tooling with 
>> hard-coded download paths (e.g. CI testing or provisioning workflows).
>>
>> ---*---*---
>>
>> Hey folks,
>>
>> In an effort to reduce clutter and confusion on some of our public 
>> download sites (yum.puppet.com, apt.puppet.com, downloads.puppet.com, 
>> and nightlies.puppet.com), we are planning to make some changes. 
>>
>> 1. Release packages (for all active streams) will live at the top level 
>> only. 
>>
>> This change only affects yum.puppet.com (and nightlies.puppet.com/yum), 
>> giving us consistency with the layout on apt.puppet.com. Currently, yum 
>> release packages live inside their corresponding repo directory, e.g. 
>> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm 
>> . 
>> THESE WILL BE REMOVED. 
>>
>> Here are some examples of where you will be able to find release packages:
>>
>> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>>
>> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>>
>> Old: nightlies.puppet.com/yum/puppet-nightly/
>> puppet-nightly-release-sles-12.noarch.rpm
>>
>> New: nightlies.puppet.com/yum/puppet-nightly-release-sles-12.noarch.rpm
>>
>> These new paths are currently available for use. We plan to remove the 
>> old ones on May 14. Please plan to make all updates during this period. 
>>
>> 2. There will be no links to nightlies from main download sites.
>>
>> Links like yum.puppet.com/puppet-nightly 
>>  and 
>> apt.puppet.com/puppet-nightly  
>> WILL BE REMOVED on May 14.
>>
>> If you're looking for nightlies, visit nightlies.puppet.com. The 
>> directory structure will match that of our main download sites.
>>
>> 3. All PC1 (and older) packages will be removed from {yum, apt, 
>> downloads}.puppet.com. 
>>
>> PC1 (which includes puppet-agent 1.10.x and puppet 4.10.x) is reaching 
>> end-of-life, so all packages will be moved to release-archives.puppet.com 
>> on May 14 and no further updates will be made to these streams.
>>
>> ---*---*---
>>
>> We have set up a temporary s3 bucket that reflects the new layout if 
>> you’d like to test changes before the cutover:  
>> yum-test.puppet.com.s3-website-us-west-2.amazonaws.com
>>
>> PLEASE NOTE that s3 buckets are not naturally browsable on the web. If 
>> you visit the above url in your browser, the info you'll see is NOT 
>> ACCURATE. You CAN, however, download packages via wget/curl/etc. so this 
>> should only affect human eyes.
>>
>> If you have any questions or concerns about these changes, please 
>> reply-all to this email.
>>
>> Thanks!
>>
>> -- 
>> *Molly Waggett*
>> she/her/hers
>> Release Engineer @ Puppet, Inc.
>>
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/a28bd1dd-f956-468c-b0ab-a367620c8a73%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[michael mack]

Gotcha, thanks Molly.

On Wednesday, May 15, 2019 at 3:32:40 PM UTC-7, Molly Waggett wrote:
>
> Hi Michael,
>
> That path has been removed, as PC1 has gone EOL. All associated packages 
> have been moved to release-archives.puppet.com. We currently don't have 
> repositories enabled, since these streams will not receive any future 
> updates. Due to high demand, however, we are working to enable repositories 
> on release-archives. We will let you know when those are available.
>
> On Wed, May 15, 2019 at 3:25 PM michael mack  > wrote:
>
>> How do you get the following old repo to work?
>>
>> rpm -Uvh 
>> https://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm
>>
>>
>> On Monday, April 22, 2019 at 2:31:09 PM UTC-7, Molly Waggett wrote:
>>>
>>> TLDR: On May 14, 1. yum release packages will move to the top-level of 
>>> yum.puppet.com; 2. links to nightly release packages will be removed 
>>> from {yum,apt}.puppet.com; and 3. PC1 (and older) packages will be 
>>> moved to release-archives.puppet.com. 
>>>
>>> All Puppet-maintained tooling and documentation referencing these paths 
>>> will be updated by the time these changes are made. Please ensure that 
>>> you are using current versions.
>>>
>>> Read on for details, especially if you've written custom tooling with 
>>> hard-coded download paths (e.g. CI testing or provisioning workflows).
>>>
>>> ---*---*---
>>>
>>> Hey folks,
>>>
>>> In an effort to reduce clutter and confusion on some of our public 
>>> download sites (yum.puppet.com, apt.puppet.com, downloads.puppet.com, 
>>> and nightlies.puppet.com), we are planning to make some changes. 
>>>
>>> 1. Release packages (for all active streams) will live at the top level 
>>> only. 
>>>
>>> This change only affects yum.puppet.com (and nightlies.puppet.com/yum), 
>>> giving us consistency with the layout on apt.puppet.com. Currently, yum 
>>> release packages live inside their corresponding repo directory, e.g. 
>>> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm 
>>> . 
>>> THESE WILL BE REMOVED. 
>>>
>>> Here are some examples of where you will be able to find release 
>>> packages:
>>>
>>> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>>>
>>> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>>>
>>> Old: nightlies.puppet.com/yum/puppet-nightly/
>>> puppet-nightly-release-sles-12.noarch.rpm
>>>
>>> New: nightlies.puppet.com/yum/puppet-nightly-release-sles-12.noarch.rpm
>>>
>>> These new paths are currently available for use. We plan to remove the 
>>> old ones on May 14. Please plan to make all updates during this period. 
>>>
>>> 2. There will be no links to nightlies from main download sites.
>>>
>>> Links like yum.puppet.com/puppet-nightly 
>>>  and 
>>> apt.puppet.com/puppet-nightly 
>>>  WILL BE REMOVED on May 14.
>>>
>>> If you're looking for nightlies, visit nightlies.puppet.com. The 
>>> directory structure will match that of our main download sites.
>>>
>>> 3. All PC1 (and older) packages will be removed from {yum, apt, 
>>> downloads}.puppet.com. 
>>>
>>> PC1 (which includes puppet-agent 1.10.x and puppet 4.10.x) is reaching 
>>> end-of-life, so all packages will be moved to 
>>> release-archives.puppet.com on May 14 and no further updates will be 
>>> made to these streams.
>>>
>>> ---*---*---
>>>
>>> We have set up a temporary s3 bucket that reflects the new layout if 
>>> you’d like to test changes before the cutover:  
>>> yum-test.puppet.com.s3-website-us-west-2.amazonaws.com
>>>
>>> PLEASE NOTE that s3 buckets are not naturally browsable on the web. If 
>>> you visit the above url in your browser, the info you'll see is NOT 
>>> ACCURATE. You CAN, however, download packages via wget/curl/etc. so this 
>>> should only affect human eyes.
>>>
>>> If you have any questions or concerns about these changes, please 
>>> reply-all to this email.
>>>
>>> Thanks!
>>>
>>> -- 
>>> *Molly Waggett*
>>> she/her/hers
>>> Release Engineer @ Puppet, Inc.
>>>
>> -- 
>> 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 puppet...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/puppet-users/37de6ec5-f1a5-4d83-ba2f-5cb0f89f3e53%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> -- 
> *Molly Waggett*
> she/her/hers
> Release Engineer @ Puppet, Inc.
>

-- 
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 

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Molly Waggett]

Hi Michael,

That path has been removed, as PC1 has gone EOL. All associated packages
have been moved to release-archives.puppet.com. We currently don't have
repositories enabled, since these streams will not receive any future
updates. Due to high demand, however, we are working to enable repositories
on release-archives. We will let you know when those are available.

On Wed, May 15, 2019 at 3:25 PM michael mack  wrote:

> How do you get the following old repo to work?
>
> rpm -Uvh https://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm
>
>
> On Monday, April 22, 2019 at 2:31:09 PM UTC-7, Molly Waggett wrote:
>>
>> TLDR: On May 14, 1. yum release packages will move to the top-level of
>> yum.puppet.com; 2. links to nightly release packages will be removed
>> from {yum,apt}.puppet.com; and 3. PC1 (and older) packages will be moved
>> to release-archives.puppet.com.
>>
>> All Puppet-maintained tooling and documentation referencing these paths
>> will be updated by the time these changes are made. Please ensure that
>> you are using current versions.
>>
>> Read on for details, especially if you've written custom tooling with
>> hard-coded download paths (e.g. CI testing or provisioning workflows).
>>
>> ---*---*---
>>
>> Hey folks,
>>
>> In an effort to reduce clutter and confusion on some of our public
>> download sites (yum.puppet.com, apt.puppet.com, downloads.puppet.com,
>> and nightlies.puppet.com), we are planning to make some changes.
>>
>> 1. Release packages (for all active streams) will live at the top level
>> only.
>>
>> This change only affects yum.puppet.com (and nightlies.puppet.com/yum),
>> giving us consistency with the layout on apt.puppet.com. Currently, yum
>> release packages live inside their corresponding repo directory, e.g.
>> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm
>> .
>> THESE WILL BE REMOVED.
>>
>> Here are some examples of where you will be able to find release packages:
>>
>> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>>
>> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>>
>> Old: nightlies.puppet.com/yum/puppet-nightly/
>> puppet-nightly-release-sles-12.noarch.rpm
>>
>> New: nightlies.puppet.com/yum/puppet-nightly-release-sles-12.noarch.rpm
>>
>> These new paths are currently available for use. We plan to remove the
>> old ones on May 14. Please plan to make all updates during this period.
>>
>> 2. There will be no links to nightlies from main download sites.
>>
>> Links like yum.puppet.com/puppet-nightly
>>  and
>> apt.puppet.com/puppet-nightly 
>> WILL BE REMOVED on May 14.
>>
>> If you're looking for nightlies, visit nightlies.puppet.com. The
>> directory structure will match that of our main download sites.
>>
>> 3. All PC1 (and older) packages will be removed from {yum, apt,
>> downloads}.puppet.com.
>>
>> PC1 (which includes puppet-agent 1.10.x and puppet 4.10.x) is reaching
>> end-of-life, so all packages will be moved to release-archives.puppet.com
>> on May 14 and no further updates will be made to these streams.
>>
>> ---*---*---
>>
>> We have set up a temporary s3 bucket that reflects the new layout if
>> you’d like to test changes before the cutover:
>> yum-test.puppet.com.s3-website-us-west-2.amazonaws.com
>>
>> PLEASE NOTE that s3 buckets are not naturally browsable on the web. If
>> you visit the above url in your browser, the info you'll see is NOT
>> ACCURATE. You CAN, however, download packages via wget/curl/etc. so this
>> should only affect human eyes.
>>
>> If you have any questions or concerns about these changes, please
>> reply-all to this email.
>>
>> Thanks!
>>
>> --
>> *Molly Waggett*
>> she/her/hers
>> Release Engineer @ Puppet, Inc.
>>
> --
> 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 puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/37de6ec5-f1a5-4d83-ba2f-5cb0f89f3e53%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFOE68AOTn94Mz_JLcOMn_EzMO99NOghzCD09UVC_dS7o9qeSQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: [ACTION] Changes to release package links

[michael mack]

How do you get the following old repo to work?

rpm -Uvh https://yum.puppetlabs.com/puppetlabs-release-pc1-el-7.noarch.rpm


On Monday, April 22, 2019 at 2:31:09 PM UTC-7, Molly Waggett wrote:
>
> TLDR: On May 14, 1. yum release packages will move to the top-level of 
> yum.puppet.com; 2. links to nightly release packages will be removed from 
> {yum,apt}.puppet.com; and 3. PC1 (and older) packages will be moved to 
> release-archives.puppet.com. 
>
> All Puppet-maintained tooling and documentation referencing these paths 
> will be updated by the time these changes are made. Please ensure that 
> you are using current versions.
>
> Read on for details, especially if you've written custom tooling with 
> hard-coded download paths (e.g. CI testing or provisioning workflows).
>
> ---*---*---
>
> Hey folks,
>
> In an effort to reduce clutter and confusion on some of our public 
> download sites (yum.puppet.com, apt.puppet.com, downloads.puppet.com, and 
> nightlies.puppet.com), we are planning to make some changes. 
>
> 1. Release packages (for all active streams) will live at the top level 
> only. 
>
> This change only affects yum.puppet.com (and nightlies.puppet.com/yum), 
> giving us consistency with the layout on apt.puppet.com. Currently, yum 
> release packages live inside their corresponding repo directory, e.g. 
> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm 
> . 
> THESE WILL BE REMOVED. 
>
> Here are some examples of where you will be able to find release packages:
>
> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>
> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>
> Old: nightlies.puppet.com/yum/puppet-nightly/
> puppet-nightly-release-sles-12.noarch.rpm
>
> New: nightlies.puppet.com/yum/puppet-nightly-release-sles-12.noarch.rpm
>
> These new paths are currently available for use. We plan to remove the 
> old ones on May 14. Please plan to make all updates during this period. 
>
> 2. There will be no links to nightlies from main download sites.
>
> Links like yum.puppet.com/puppet-nightly 
>  and 
> apt.puppet.com/puppet-nightly  
> WILL BE REMOVED on May 14.
>
> If you're looking for nightlies, visit nightlies.puppet.com. The 
> directory structure will match that of our main download sites.
>
> 3. All PC1 (and older) packages will be removed from {yum, apt, downloads}.
> puppet.com. 
>
> PC1 (which includes puppet-agent 1.10.x and puppet 4.10.x) is reaching 
> end-of-life, so all packages will be moved to release-archives.puppet.com 
> on May 14 and no further updates will be made to these streams.
>
> ---*---*---
>
> We have set up a temporary s3 bucket that reflects the new layout if you’d 
> like to test changes before the cutover:  
> yum-test.puppet.com.s3-website-us-west-2.amazonaws.com
>
> PLEASE NOTE that s3 buckets are not naturally browsable on the web. If 
> you visit the above url in your browser, the info you'll see is NOT 
> ACCURATE. You CAN, however, download packages via wget/curl/etc. so this 
> should only affect human eyes.
>
> If you have any questions or concerns about these changes, please 
> reply-all to this email.
>
> Thanks!
>
> -- 
> *Molly Waggett*
> she/her/hers
> Release Engineer @ Puppet, Inc.
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/37de6ec5-f1a5-4d83-ba2f-5cb0f89f3e53%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Bob Vincent]

First sign of breakage: https://tickets.puppetlabs.com/browse/BKR-1590

Fixed here: https://github.com/puppetlabs/beaker-puppet/pull/113

On Monday, May 6, 2019 at 6:16:25 PM UTC-4, Molly Waggett wrote:
>
> Hey folks,
>
> REMINDER that the repository path changes* will take effect next week, on 
> Tuesday, 
> May 14.
>
> Please make sure any custom tooling using these paths has been updated.
>
> If you have any questions or concerns, please reply-all to this email.
>
> Thanks!
>
> * in case you forgot, changes include:
>
> 1. yum release packages will be removed from nested directories on 
> yum.puppet.com (e.g. yum.puppet.com/puppet6/
> puppet6-release-el-7.noarch.rpm
>
> --> yum.puppet.com/puppet6-release-el-7.noarch.rpm).
>
> PLEASE NOTE that these are actually symlinks to release packages that live 
> inside their respective repositories, so package updates can be applied via 
> your package manager, like any other package.
>
> 2. links to nightly release packages will be removed from {yum,apt}.
> puppet.com.
> 3. PC1 (and older) packages will be moved to release-archives.puppet.com. 
> This includes puppet-agent 1.10.x and puppet 4.x.
>
> On Tue, Apr 23, 2019 at 9:13 AM Molly Waggett  > wrote:
>
>> Hi John,
>>
>> The top-level release packages are actually symlinks to release packages 
>> that *are* inside their respective repositories. When we publish new 
>> release packages, we update those links so that users don't have to bump 
>> version numbers in any tooling that installs these repositories.
>>
>> Thanks!
>>
>> On Tue, Apr 23, 2019 at 6:21 AM jcbollinger > > wrote:
>>
>>>
>>>
>>> On Monday, April 22, 2019 at 4:31:09 PM UTC-5, Molly Waggett wrote:

 1. Release packages (for all active streams) will live at the top level 
 only. 

 This change only affects yum.puppet.com (and nightlies.puppet.com/yum), 
 giving us consistency with the layout on apt.puppet.com. Currently, 
 yum release packages live inside their corresponding repo directory, e.g. 
 yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm 
 . 
 THESE WILL BE REMOVED. 

 Here are some examples of where you will be able to find release 
 packages:

 Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm

 New: yum.puppet.com/puppet6-release-el-7.noarch.rpm


>>> It is conventional for repository release packages to be inside their 
>>> repositories so that repository configuration updates can be published and 
>>> applied via the same mechanism that is used for ordinary packages.  Even if 
>>> this is a capability that Puppet rarely uses, it seems ill-considered to 
>>> give it up.  The desire for consistency could be as well served by moving 
>>> the other release packages into their repos, or by making the release 
>>> packages consistently  available in both places.
>>>
>>>
>>> John
>>>
>>> -- 
>>> 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 puppet...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/puppet-users/c711eeca-239c-4022-8f4b-55f9ea577c8d%40googlegroups.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> -- 
>> *Molly Waggett*
>> she/her/hers
>> Release Engineer @ Puppet, Inc.
>>
>
>
> -- 
> *Molly Waggett*
> she/her/hers
> Release Engineer @ Puppet, Inc.
>

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/8607ae27-d495-4aaf-b113-e263dad063dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Molly Waggett]

Hey folks,

REMINDER that the repository path changes* will take effect next week,
on Tuesday,
May 14.

Please make sure any custom tooling using these paths has been updated.

If you have any questions or concerns, please reply-all to this email.

Thanks!

* in case you forgot, changes include:

1. yum release packages will be removed from nested directories on
yum.puppet.com (e.g. yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm

--> yum.puppet.com/puppet6-release-el-7.noarch.rpm).

PLEASE NOTE that these are actually symlinks to release packages that live
inside their respective repositories, so package updates can be applied via
your package manager, like any other package.

2. links to nightly release packages will be removed from {yum,apt}.
puppet.com.
3. PC1 (and older) packages will be moved to release-archives.puppet.com.
This includes puppet-agent 1.10.x and puppet 4.x.

On Tue, Apr 23, 2019 at 9:13 AM Molly Waggett 
wrote:

> Hi John,
>
> The top-level release packages are actually symlinks to release packages
> that *are* inside their respective repositories. When we publish new
> release packages, we update those links so that users don't have to bump
> version numbers in any tooling that installs these repositories.
>
> Thanks!
>
> On Tue, Apr 23, 2019 at 6:21 AM jcbollinger 
> wrote:
>
>>
>>
>> On Monday, April 22, 2019 at 4:31:09 PM UTC-5, Molly Waggett wrote:
>>>
>>> 1. Release packages (for all active streams) will live at the top level
>>> only.
>>>
>>> This change only affects yum.puppet.com (and nightlies.puppet.com/yum),
>>> giving us consistency with the layout on apt.puppet.com. Currently, yum
>>> release packages live inside their corresponding repo directory, e.g.
>>> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm
>>> .
>>> THESE WILL BE REMOVED.
>>>
>>> Here are some examples of where you will be able to find release
>>> packages:
>>>
>>> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>>>
>>> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>>>
>>>
>> It is conventional for repository release packages to be inside their
>> repositories so that repository configuration updates can be published and
>> applied via the same mechanism that is used for ordinary packages.  Even if
>> this is a capability that Puppet rarely uses, it seems ill-considered to
>> give it up.  The desire for consistency could be as well served by moving
>> the other release packages into their repos, or by making the release
>> packages consistently  available in both places.
>>
>>
>> John
>>
>> --
>> 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 puppet-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/c711eeca-239c-4022-8f4b-55f9ea577c8d%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> *Molly Waggett*
> she/her/hers
> Release Engineer @ Puppet, Inc.
>


-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFOE68DrRGy%2BiO5yCykhCd0MwpLJSjY8FifFAB4HscNvuoQS%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Re: [ACTION] Changes to release package links

[Molly Waggett]

Hi John,

The top-level release packages are actually symlinks to release packages
that *are* inside their respective repositories. When we publish new
release packages, we update those links so that users don't have to bump
version numbers in any tooling that installs these repositories.

Thanks!

On Tue, Apr 23, 2019 at 6:21 AM jcbollinger 
wrote:

>
>
> On Monday, April 22, 2019 at 4:31:09 PM UTC-5, Molly Waggett wrote:
>>
>> 1. Release packages (for all active streams) will live at the top level
>> only.
>>
>> This change only affects yum.puppet.com (and nightlies.puppet.com/yum),
>> giving us consistency with the layout on apt.puppet.com. Currently, yum
>> release packages live inside their corresponding repo directory, e.g.
>> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm
>> .
>> THESE WILL BE REMOVED.
>>
>> Here are some examples of where you will be able to find release packages:
>>
>> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>>
>> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>>
>>
> It is conventional for repository release packages to be inside their
> repositories so that repository configuration updates can be published and
> applied via the same mechanism that is used for ordinary packages.  Even if
> this is a capability that Puppet rarely uses, it seems ill-considered to
> give it up.  The desire for consistency could be as well served by moving
> the other release packages into their repos, or by making the release
> packages consistently  available in both places.
>
>
> John
>
> --
> 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 puppet-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/c711eeca-239c-4022-8f4b-55f9ea577c8d%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Molly Waggett*
she/her/hers
Release Engineer @ Puppet, Inc.

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAFOE68B72vTBnDab8dwFORFZusf9Cr1d4BqHGm9SxEi9oiW-Bg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Re: [ACTION] Changes to release package links

[jcbollinger]

On Monday, April 22, 2019 at 4:31:09 PM UTC-5, Molly Waggett wrote:
>
> 1. Release packages (for all active streams) will live at the top level 
> only. 
>
> This change only affects yum.puppet.com (and nightlies.puppet.com/yum), 
> giving us consistency with the layout on apt.puppet.com. Currently, yum 
> release packages live inside their corresponding repo directory, e.g. 
> yum.puppet.com/puppet6/puppet6-release-fedora-28.noarch.rpm 
> . 
> THESE WILL BE REMOVED. 
>
> Here are some examples of where you will be able to find release packages:
>
> Old: yum.puppet.com/puppet6/puppet6-release-el-7.noarch.rpm
>
> New: yum.puppet.com/puppet6-release-el-7.noarch.rpm
>
>
It is conventional for repository release packages to be inside their 
repositories so that repository configuration updates can be published and 
applied via the same mechanism that is used for ordinary packages.  Even if 
this is a capability that Puppet rarely uses, it seems ill-considered to 
give it up.  The desire for consistency could be as well served by moving 
the other release packages into their repos, or by making the release 
packages consistently  available in both places.


John

-- 
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 puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/c711eeca-239c-4022-8f4b-55f9ea577c8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.