Puppet loads Facter, which has a "partitions" fact and a "disks" fact,
both of which may be worth investigating. I'm moving this to the
"facter" package.
** Package changed: puppet (Ubuntu) => facter (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I strongly recommend you to use a way to configure your service in a way
as to keep the entire commandline in one place, instead of keeping it in
several files.
Environmentfiles are good for giving a running service environment
variables for it to use after startup. I do not recommend using it
In varnish 5.2.0-1, the "reload-vcl" script was replaced with a
"varnishreload" script from upstream. This should take care of this
issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676242
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
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
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
To manage notifications about this bug go to:
https
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:
incorrect PID
Sandbeck Mathisen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397910
Title:
Puppet daemon dies from SIGUSR1 if no certificate
To manage notifications about this bug go to:
https
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397898
Title:
incorrect PID in initscript
To manage
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 its
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 its
There is no mysql_grant resource in the puppet-module-puppetlabs-
apache package.
I guess this should have been filed on the puppet-module-puppetlabs-
mysql package instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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.
--
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.
--
:operatingsystem = :ubuntu
commands :start = /sbin/start,
:stop= /sbin/stop,
:restart = /sbin/restart,
:status_exec = /sbin/status,
:initctl = /sbin/initctl
Is this wrong for Ubuntu?
--
Stig Sandbeck Mathisen
--
You received this bug notification
instanciated services.
--
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/1276766
Title:
'status startpar-bridge' fails with 'status: Unknown parameter: JOB'
To manage
:operatingsystem = :ubuntu
commands :start = /sbin/start,
:stop= /sbin/stop,
:restart = /sbin/restart,
:status_exec = /sbin/status,
:initctl = /sbin/initctl
Is this wrong for Ubuntu?
--
Stig Sandbeck Mathisen
--
You received this bug notification
instanciated services.
--
Stig Sandbeck Mathisen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1276766
Title:
'status startpar-bridge' fails with 'status: Unknown parameter: JOB'
To manage notifications
instead of -C. It does check the
config, but I guess that only works if you have a running varnish.
--
Stig Sandbeck Mathisen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1284095
Title:
add
On Mon, Feb 24, 2014 at 01:02:41PM -, Samuele Giovanni Tonon wrote:
Public bug reported:
hello, it would be awesome to have a configtest action in the init.d
script , in this way you can safely test a vcl configuration by just
doing
/etc/init.d/varnish configtest
Thank you.
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:
(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
(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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242363
Title:
Puppet package needs ruby-hiera (unmapped dep)
To manage
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1242363
Title:
Puppet package needs
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 by the
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 by the
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
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
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
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
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?)
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?)
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 debian.
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 debian.
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
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
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 correcly configuring facts synch'd from master
To manage
on the command line.
--
Stig Sandbeck Mathisen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1076286
Title:
Puppet agent not correcly configuring facts synch'd from master
To manage notifications about
. For the ubuntu packaging, it may be
different.
Your bug report mentions a newer version, could you check if you have
the init script that came with the package, or if it is changed, or an
older version is kept when upgrading? An md5sum /etc/init.d/puppet may
also help, if they differ.
--
Stig Sandbeck
. :)
--
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
To manage notifications about this bug go to:
https
. For the ubuntu packaging, it may be
different.
Your bug report mentions a newer version, could you check if you have
the init script that came with the package, or if it is changed, or an
older version is kept when upgrading? An md5sum /etc/init.d/puppet may
also help, if they differ.
--
Stig Sandbeck
. :)
--
Stig Sandbeck Mathisen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1060184
Title:
puppet client init script pid file error
To manage notifications about this bug go to:
https://bugs.launchpad.net
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
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
Bugs, which is subscribed to
In varnish 3.0.1-2 and on it is possible to set DAEMON_OPTS in
/etc/default/varnishncsa without it being overwritten in
/etc/init.d/varnishncsa.
The first ubuntu release which includes this change is precise.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Forwarded upstream to https://github.com/comotion/cpm/issues/25
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/914989
Title:
cpm crashes when trying to use gpg key with UTF-8 extended characters
To
gearmand 0.27-1 has been uploaded to debian. When that version is pulled
into Ubuntu, this bug should auto-close.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/682680
Title:
New upstream release,
** Summary changed:
- New upstream release, gearmand 0.23
+ New upstream release, gearmand 0.24
** Description changed:
- There is a new upstream release, gearmand 0.17, available from upstream
+ There is a new upstream release, gearmand 0.24, available from upstream
at
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:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/793632
Title:
puppetmaster
:-, in combination with set -u in shell scripts, used to allow some
variables to be empty. That it looks like a smiley is just an added
bonus.
Example:
$ set -u
$ echo ${START}
bash: START: unbound variable
$ echo ${START:-}
$
--
You received this bug notification because you
Public bug reported:
Binary package hint: module-init-tools
In the file /etc/modprobe.d/intel-3945-iwlagn-disable11n.conf, the line
options iwl3945 11n_disable=1 prevents loading of the iwl3945 module in natty.
This fails, on kernel 2.6.38-7-generic, with the following error message in
the
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/747214
Title:
Wireless interface disabled after upgrade to natty and reboot
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Summary changed:
- New upstream release, gearmand 0.14
+ New upstream release, gearmand 0.17
** Description changed:
- There is a new upstream release, gearmand 0.14, available from upstream
+ There is a new upstream release, gearmand 0.17, available from upstream
at
Public bug reported:
Binary package hint: lvm2
When running lvresize or lvextend with the --help option, it
mentions a --resizefs option which is not covered in the man page.
ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: lvm2 2.02.54-1ubuntu6
ProcVersionSignature: Ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/723172
Title:
lvresize/lvextend manpages missing --resizefs option
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
I've made mod-gearman packages from 0.14, available at
http://people.debian.org/~ssm/debs/unstable/source/
I added one IPv6 fix to debian/patches, from
https://bugs.launchpad.net/gearmand/+bug/635476 (A struct sockaddr isn't
big enough to hold an ipv6 address)
--
You received this bug
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
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
** Branch linked: lp:debian/sid/varnish
--
libvarnish-dev does not install /usr/lib/libvarnishapi.so
https://bugs.launchpad.net/bugs/488258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Varnish 2.1.3-2 has been uploaded to Debian, and contains a fix for this issue.
http://packages.qa.debian.org/v/varnish/news/20100729T222002Z.html
Chances are, it'll be available for Ubuntu quite soon.
--
varnish daemon should not start by default
https://bugs.launchpad.net/bugs/569060
You
Varnish 2.1.3-2 has been uploaded to Debian, and contains a fix for this issue.
http://packages.qa.debian.org/v/varnish/news/20100729T222002Z.html
Chances are, it'll be available for Ubuntu quite soon.
--
libvarnish-dev does not install /usr/lib/libvarnishapi.so
Varnish 2.1.3-2 has been uploaded to Debian, and contains a fix for this issue.
http://packages.qa.debian.org/v/varnish/news/20100729T222002Z.html
Chances are, it'll be available for Ubuntu quite soon.
--
varnishlog should not run as root
https://bugs.launchpad.net/bugs/461593
You received this
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
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
Thanks, I'll take a look at this issue.
--
Stig Sandbeck Mathisen
ooo, shiny!
--
libvarnish-dev does not install /usr/lib/libvarnishapi.so
https://bugs.launchpad.net/bugs/488258
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Thanks,
I agree it should not run as root. I'll add an unprivileged user for
varnishlog.
--
varnishlog should not run as root
https://bugs.launchpad.net/bugs/461593
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
On 19. feb.. 2009, at 19.17, Jamie Strandboge wrote:
Is 2.0.3 bug fix only, or does it add any new features over 2.0.2?
Almost entirely a bug fix release, but there has been one enhancement
to an existing function in VCL, and some defaults have been changed.
Changelog:
68 matches
Mail list logo
