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
You'd be better declaring netplan as a requires:
if $operatingsystem == "Ubuntu" {
if versioncmp($facts['os']['release']['full'], '18') >= 0 {
package { 'netplan':
ensure => present,
}
file { "/etc/netplan/windows-dhcp.yaml":
mode=> '0644',
owner => "${roo
Hi Molly,
That's great news, thank you! (Sadly, I have a lot of inherited, crusty
puppet code that means I'm stuck running a v3 setup until I can take
delivery of a sufficient quantity of the round 'tuits' to re-base it all.
Unfortunately, hexagonal ones are insufficient!)
I shall check in aga
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 st
Hi Chris,
We originally did not plan to support repositories on release-archives, but
due to the high demand, yes we are working to enable them as soon as
possible.
On Wed, May 15, 2019 at 3:23 PM Chris Taylor wrote:
> Guessing this is related to the archiving of the puppet 4 & older packages?
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 reposito
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
Guessing this is related to the archiving of the puppet 4 & older packages?
I note that the yum archive still functions as a repo, but the apt one
doesn't have any release files (or a dists folder), in spite of otherwise
being structured appropriately.. Is this going to be fixed?
(release-archi
The bionic repo should be working again. Let us know if you have any more
issues.
On Wed, May 15, 2019 at 1:45 PM Morgan Rhodes wrote:
> Hi Peter,
>
> Apologies, we've been having some repo issues today. I'm getting the
> bionic repository updated now and it should be done within the hour. I wil
Hi Peter,
Apologies, we've been having some repo issues today. I'm getting the bionic
repository updated now and it should be done within the hour. I will send
another update here when it completes.
On Wed, May 15, 2019 at 1:43 PM Peter Berghold
wrote:
> Just this afternoon around 4PM I started
Just this afternoon around 4PM I started noticing this happen in my Docker
builds that incorporate loading the Puppet agent:
W: Skipping acquire of configured file 'puppet/binary-all/Packages' as
repository 'http://apt.puppetlabs.com bionic InRelease' doesn't have the
component 'puppet' (component
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
>
Ben Ford wrote:
> To be sure, this pattern doesn't always work and you don't always have
> control over the full system. What's your use case that you're trying
> to solve?
if $operatingsystem == "Ubuntu" {
if versioncmp($facts['os']['release']['full'], '18') >= 0 {
file { "/etc/netplan/win
13 matches
Mail list logo
