On Tue, 15 Feb 2022 14:56:22 +0100 Petter Reinholdtsen
wrote:
I came across this in
https://piuparts.debian.org/sid/pass/smokeping_2.7.3-3.log >
Purging configuration files for smokeping (2.7.3-3) ...
/var/lib/dpkg/info/smokeping.postrm: 32: ucf: not found
Look like something should be
On Thu, 3 Jun 2021 13:58:36 -0400 Gabriel Filion
wrote:
I've committed your change to salsa and it should make it to the next
upload.
woops! I apparently forgot to add a changelog entry about this fix with
the Closes mention.
The fix was sent to unstable last week with 2.7.3-4. I'll wait
Hi,
On Mon, 21 Mar 2022 18:25:33 -0700 Adam Williamson
wrote:
Just reporting I found the same problem on Fedora 36. Filed here:
https://bugzilla.redhat.com/show_bug.cgi?id=2066527 .
Thanks for this added information!
Following information from the redhat bug report, I've tried this on my
Hi there,
For what it's worth, upstream puppet does not yet suppport ruby 3.0.
see: https://puppet.com/docs/puppet/7/release_notes_puppet.html
puppet 7 added support for ruby 2.7 but 2.9 and 3.0 were never there
upstream. I'm guessing they'll bump to 3.x for the puppet 8 cycle only.
Package: vagrant-libvirt
Version: 0.8.0-1
Severity: important
Hello,
Ever since I've upgraded vagrant-libvirt to 0.8.0, I've been having issues with
VMs that have a "private_ip" setup: their secondary IP is not brought up before
the puppet provisioning step, which means the puppet server can't
Package: traceroute
Version: 1:2.1.0-3
Severity: wishlist
Tags: upstream ipv6
Hi,
The traceroute binary can currently be used with both address families, IPv4
and IPv6, which is great!
However, contrary to how i.e ping behaves traceroute does not chose to use ipv6
when a dns record exists
Package: wnpp
Severity: wishlist
Owner: Gabriel Filion
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: libobject-result-perl
Version : 0.03
Upstream Author : Damian Conway
* URL : https://metacpan.org/release/Object-Result
* License
Hi Alexey,
On 2022-09-17 15 h 44, Alexey Vazhnov wrote:
I've tested Smokeping 2.8.2 in `Devuan GNU/Linux 5 (daedalus/ceres)` (based on
Debian testing 12 bookworm), it works
without errors.
How to:
I created a .deb package in `Debian GNU/Linux 11 (bullseye)` by commands like
these:
```
sudo
Hi Micheal,
On 2022-09-13 01 h 50, Michael Prokop wrote:
* Gabriel Filion [Mon Jan 24, 2022 at 10:53:27AM -0500]:
Upstream has released a new version of smokeping, 2.8.2 and it would be helpful
to upgrade the debian package to this version since it contains a number of
fixes, some of which
Hello!
Just wanted to chime in to confirm that James' patch does make the
package compile.
Hi there,
This could be happening for many reasons. Just to investigate one
possiblity: in your syslog do you see messages from apparmor when you
try to load a file?
Hi,
I've just taken a look at this issue together with someone else during
the Montreal BSP and we think that the init script is possibly the
source of the problem:
the stop action fails if it is called when the service is not running,
which is the case when you install the package on a new
Hello,
Upstream has produced more releases and is now at 0.4.8 on pypi
In addition to The changes mentioned by Michael, the newer versions also
have some additional CLI options that enable features that some users
may need. For exemple "ruff format --diff" is currently used by
coc-pyright
Hello xavier,
I'm working on doing a bit of cleanup in the bug reports for smokeping
and yours has not been addressed for the last 10 years, which is sad.
Do you still use smokeping on debian? and if so, are you still
experiencing the same issue?
If you're still having the issue, could you
Hello Marcin,
I've tried to reproduce this behavior in the current testing version of
smokeping and I wasn't able to do it.
with the following contents for config.d/Probes, and all other files
with defaults from the package (so just one target for localhost that
uses the fping probe) plus
Hello,
I believe that this issue concerns a nowadays old release of debian, and
also from what I found there was an item in the NEWS file for version
2.3.5-1 that explained the changes required in the config with regards
to the new config split, specifically it was mentioning to make sure to
201 - 216 of 216 matches
Mail list logo
