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 <[email protected]>
>>> 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 <[email protected]>
>>>> 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
>>>>>> <http://yum.puppetlabs.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 [email protected].
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/puppet-users/c711eeca-239c-4022-8f4b-55f9ea577c8d%40googlegroups.com
>>>>>
>>>>> <https://groups.google.com/d/msgid/puppet-users/c711eeca-239c-4022-8f4b-55f9ea577c8d%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>> 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 [email protected] <javascript:>.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-users/6770a73d-bfbb-4445-92af-239f798ee0af%40googlegroups.com
>>
>> <https://groups.google.com/d/msgid/puppet-users/6770a73d-bfbb-4445-92af-239f798ee0af%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> 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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/dbc5f468-949b-4f52-a442-5ef7df037adc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
