Related debian bug is http://bugs.debian.org/650527, and this is fixed
in 2.7.12-2.
** Bug watch added: Debian Bug tracker #650527
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650527
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
On Thu, May 23, 2013 at 01:33:28PM -, Matthias Klose wrote:
> falling back to ruby1.8 is not a solution. Are there any extensions not
> yet built for 1.9? If not, please do so.
>
At a glance, it looks like facter is not available in the load path of
ruby1.9. I'd start looking at the "facter"
Related Debian bug is at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713070
When this is resolved, it should work both apache2.2 and apache2.4.
--
Stig
** Bug watch added: Debian Bug tracker #713070
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713070
--
You received this bug noti
Correct. This packaging bug was fixed in the debian repository just
before the 3.3.0-1 release, with commit id
11a376f8348dfa2c254b19f7b29aec13940aeb92.
The "ruby-hiera" dependency was moved from the "puppetmaster-common"
package to the "puppet-common" package. Previously, this was only
needed b
Puppet will need hiera when you apply a manifest containing any
parameterized class, like the one in your example.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1242363
Title:
Puppe
(and this is new functionality in puppet 3.x, it does not apply to
puppet 2.7)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1242363
Title:
Puppet package needs ruby-hiera (unmapped
This is fixed in 2.6.5-1 and later, in commit
c29ee05efdfbfaf0fe96573571047bd74a27bc11 in the debian packaging
repository.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/793632
Title:
Thanks for the bug report.
This issue is fixed in the 0.25.5 release, which will be available (or
superseded by 2.6.0) in maverick.
--
Stig Sandbeck Mathisen
ooo, shiny!
--
emacs puppet-mode not auto loaded in lucid
https://bugs.launchpad.net/bugs/605977
You received
Not exactly true anymore. The client and the puppetmaster is in the
puppet-common package, all the puppet and the puppetmaster packages
contain are the compatibility links used to retain the old script names,
their man pages, and the init scripts.
The "puppet" binary is now in the "puppet-common"
an
older version is kept when upgrading? An "md5sum /etc/init.d/puppet" may
also help, if they differ.
--
Stig Sandbeck Mathisen
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/
even if the source of the bug
was not found. :)
--
Stig Sandbeck Mathisen
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1060184
Title:
puppet client init script pid file error
T
ct if
you run "puppet agent --test" on the command line.
--
Stig Sandbeck Mathisen
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1076286
Title:
Puppet agent not correc
The source of this problem is in the debian packaging repository for
2.7.11-1.
The
/usr/lib/ruby/1.8/puppet/util/instrumentation/listeners/process_name.rb
file is included in the debian/2.7.11-1 packaging when it shouldn't.
The difference in the puppet source between the upstream and the
packagin
On Mon, Mar 04, 2013 at 07:59:33AM -, Benjamin Kerensa wrote:
> @Micah: Hi, This we actually just a test I was doing at our jam today
> but we did discuss plans to land a newer version of puppet and I do
> agree it would be most appropriate to have a released version and get
> that through debi
On Thu, Mar 07, 2013 at 06:59:44PM -, Adam Gandelman wrote:
> - The *.postinst changes still look valid, but you haven't specified
> why they can be dropped. (aside: It looks like these changes
> would be suitable candidates for submitting to debian in the
> future to reduce the delta?)
Correct behaviour (default to systemd, determine if it is running,
fallback to upstart / sysvinit) seems to have been added to puppet
upstream at 4.1.0-87-g7fe6164, just a few days ago. This looks like it
will be part of the puppet 4.1.1 release.
The packages currently in debian stable was changed
ces on ubuntu is:
defaultfor :operatingsystem => :ubuntu
commands :start => "/sbin/start",
:stop=> "/sbin/stop",
:restart => "/sbin/restart",
:status_exec => "/sbin/status",
:initctl
ion is correct, I wonder what would be the "generic" way of
enumerating services the correct way would be to find this variable for
all instanciated services.
--
Stig Sandbeck Mathisen
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is sub
On Wed, Apr 30, 2014 at 05:02:44PM -, Matthew Wedgwood wrote:
> Fixed in upstream:
> https://tickets.puppetlabs.com/browse/PUP-1332
Not sure about the "fixed". They are adding to a list of services which are
known to need parameters to start. They are not fixing the upstart service
provider.
The package description for "vim-puppet" says:
# As per the Debian vim policy, installed addons are not activated
# automatically, but the "vim-addon-manager" tool can be used for this
# purpose.
Not sure if this is also the Ubuntu policy for vim addons, but since
this package is unmodified from
ind any bug
filed for it, open or closed.
--
Stig Sandbeck Mathisen
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1397910
Title:
Puppet daemon dies from SIGUSR1 if no certificate
o you need to keep track of the PID there, as well (something for
post-start, then)?
--
Stig Sandbeck Mathisen
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1397898
Title:
incorre
22 matches
Mail list logo
