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 <[email protected]> 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 <[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]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/puppet-users/003ef1cb-1038-4a82-a9ab-8b2921dc999e%40googlegroups.com > <https://groups.google.com/d/msgid/puppet-users/003ef1cb-1038-4a82-a9ab-8b2921dc999e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Morgan Rhodes Release Engineering [email protected] -- 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/CA%2BFnDv0n1n_tUR2aG56CRGS1CzTtuD9ZXXm4%2BVU8jCDYE0njUg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
