Same URI. My desktop has been dist-upgraded A few times and there’s
leftover bits of crud that apt and dpkg can’t figure out. I’m switching to
puppet after failing with chef so who knows what caused the install to
fail.
Thanks
On Tue, Jul 21, 2020 at 2:15 PM Morgan Rhodes wrote:
> Hi Steve,
>
>
Hi Steve,
What URL did you get the puppet-tools-release package from? I spun up an
ubuntu 18.04 VM this morning and I was able to install the package from
http://apt.puppetlabs.com/puppet-tools-release-bionic.deb without issue.
Thanks,
Morgan
On Mon, Jul 20, 2020 at 9:59 PM Steve Redlich wrote:
After waiting a long time and playing unsuccessfuly with apt, I was able to
extract puppet-tools.list from the .deb using dpkg-deb and install it.
to help the next person with this problem,
# Puppet Tools bionic Repository
deb http://apt.puppet.com bionic puppet-tools
On Monday, July 20, 2020 at
Simon Tideswell writes:
> Perhaps I can tackle this a different way. As mentioned in my original post
> I used the Ubuntu 14 Puppet DB package on Ubuntu 16 because Ubuntu no
> longer provided a PuppetDB package for Xenial. It's Java so as long as the
> schema is unchanged it should still work,
Hello
Perhaps I can tackle this a different way. As mentioned in my original post
I used the Ubuntu 14 Puppet DB package on Ubuntu 16 because Ubuntu no
longer provided a PuppetDB package for Xenial. It's Java so as long as the
schema is unchanged it should still work, right? So has the schema c
Thanks Chris
I'll take a look at PuppetBoard when the time comes, though I don't
remember it being particularly difficult to install. However I still need
to get PuppetDB installed first and that's where I'm stuck. I'm working on
something else right now, but will come back to this later. It'd
Louis,
Unfortunately, the way that Git for Windows is packaged, it doesn't update
the registry (HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall) or
touch the Windows Installer Database (and update the WMI Win32_Product).
As a result, no matter how you perform the installation (using e
> This might not be related to Puppet but it seems that the installation
> process hangs. I have tried this configuration on an empty w2008r2 VM.
Any particular reason you're using a file and a exec resource? I have a
samba share and the following:
package { 'VLC media player 2.0.5':
