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
On 2019-05-20 18:57, Peter Berghold wrote:
So here I am I have a base profile for my Ubuntu (Debian family)
machines that invokes the class
class{'apt':
... some paramters
}
I then invoke the class
class{'postgresql': }
and now Puppet is screaming that the class 'apt' cannot be invoked
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
>
Hi Bram,
We are in the process of retiring puppet-client-tools entirely. Shipping
puppet-client-tools was significant overhead for a package that only
contained the PuppetDB CLI. Also, in an effort to limit the number of
languages we develop in, we have rewritten the PuppetDB CLI in Ruby and
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
So here I am I have a base profile for my Ubuntu (Debian family) machines
that invokes the class
class{'apt':
... some paramters
}
I then invoke the class
class{'postgresql': }
and now Puppet is screaming that the class 'apt' cannot be invoked twice.
This seems to be a flaw in Puppet
jcbollinger wrote:
> On Thursday, May 16, 2019 at 10:50:45 AM UTC-5, Helmut Schneider
> wrote:
>
> > I don't want to install netplan but if it exists do the needful:
>
> I reiterate Ben Ford's comments: This is generally considered an
> anti-pattern.
>
> It is better from an administrative
