Hello,
I'm sorry for the time it took for me to respond to your report. The
start of the pandemic transformed me into a useless puddle of stress :S
On Wed, 12 Feb 2020 14:08:46 -0800 Matt Taggart wrote:
> Maybe these things could be made into a README.apache that could be
> included. It could
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&#x
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 m
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 be
On Tue, 01 Mar 2022 06:58:36 +0100 =?utf-8?q?Stefan_R=C3=BCcker?=
wrote:
root@mars:/lib/firmware/i915# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-5.16.0-1-amd64
W: Possible missing firmware /lib/firmware/i915/adlp_dmc_ver2_12.bin for module
i915
I'm also seeing this warn
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.
Hi there,
I'm just chiming in to add yet another object on the scale:
in current debian testing, ruby has been transitioned to 3.0 and judging
from the release history, puppet has not added support for ruby 3.0
until 7.8.0:
https://puppet.com/docs/puppet/7/release_notes_puppet.html#enhanceme
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
c
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
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 f
Hi again,
On 2022-06-19 03:28, Shengjing Zhu wrote:
I used to be able to run rootless container on debian sid maybe 3 months ago
(I'm sorry, I don't have much more precise information about versions when
things used to work), but now that I try and start containers again I am
consistently hittin
Package: wnpp
Severity: wishlist
Owner: Gabriel Filion
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: libinfluxdb-http-perl
Version : 0.04
Upstream Author : Raphael Seebacher
* URL :
https://metacpan.org/pod/InfluxDB::HTTP#LICENSE-AND-COPYRIGHT
Package: podman
Version: 3.4.4+ds1-1
Severity: normal
Hello,
I used to be able to run rootless container on debian sid maybe 3 months ago
(I'm sorry, I don't have much more precise information about versions when
things used to work), but now that I try and start containers again I am
consistentl
Hrm...
I think I might have sent the bug report too quickly. I tried
downgrading to vagrant-libvirt 0.8.0 after sending the report and the
problem did not go away (0.8.0 used to work for me).
I first tried creating the networks manually in virt-manager, but that
didn't help.
Then I tried c
Oohh .. I think I just found my issue, and it doesn't seem to be related
to a bug in the software, but rather in my Vagrantfile.
from what I can see the variable that's used as the IP address for the
private network is not getting me the value that it should.
so now I plunge into ruby debuggi
Hi,
>> A quick workaround to get facter to run is to create the three
>> directories:
>
>> /etc/facter/facts.d
>> /etc/puppetlabs/facter/facts.d
>> /opt/puppetlabs/facter/facts.d
>
> Yup, confirmed that works. Thank you!
thanks for the workaround.
while it seems to work when running facter as
Hello Thorsten,
On 2020-07-17 4:39 p.m., Thorsten Alteholz wrote:
> do you make progress with uploading puppet-development-kit? Do you need
> a hand?
thanks for suggesting your help!
the current situation is that I've packaged "most of the dependencies"
with help from folks in the ruby team.
I'
Hi Chris,
On 2020-07-25 7:40 p.m., Chris Hofstaedtler wrote:
> Source: mcollective
>
> Dear mcollective Maintainers,
>
> thanks for maintaining mcollective in Debian in the past.
>
> As you are probably aware, upstream seems to have lost interest in
> this codebase (and "replaced" it by bolt).
Package: charybdis
Version: 4.1.1-1+b1
Severity: normal
Hello,
I've found out that the init script, as it is currently shipped by this
package does not properly perform its "reload" action.
This means that when one changes the configuration, or rotates the TLS
certificates, the service does not
Source: asterisk
Severity: wishlist
Hello dear maintainers!
First, thanks for your work for keeping this package alive in debian. I use it
for work and it's greatly useful.
I've just had a quick look at upstream and it would seem as though the version
that's presently in bullseye is quite late w
Package: libvirt-daemon
Version: 6.0.0-6
Severity: important
Hello,
I've been unable to use libvirt for a while and I haven't yet found a
workaround or a fix..
This started happening the last time I ran package upgrades. However, since I
don't run them very often I'm not sure with which versions
Hello,
On Sun, 07 Jan 2018 23:39:36 +1300 Andrew Ruthven wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Andrew Ruthven
>
> * Package name: rt4-extension-mergeusers
> Version : 1.03
> Upstream Author : Best Practical Solutions, LLC
> * URL : https://metacpan.or
Hello,
On Fri, 06 Apr 2018 14:57:30 +1200 Andrew Ruthven wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Andrew Ruthven
>
> * Package name: rt4-extension-rest2
> Version : 1.03
> Upstream Author : Best Practical Solutions
> * URL : https://metacpan.org/release/
Hi Bertrand,
On 2019-03-25 2:57 a.m., BERTRAND Joël wrote:
> I have restarted a server last sunday and I have seen that smokeping doesn't
> start anymore.
>
> In systemd config file, smokeping is launched with --pid-dir=/run/smokeping
> and
> systemd complains about non existent pid file.
>
> I
On 2019-03-26 2:43 p.m., Gabriel Filion wrote:
> Did you recently upgrade smokeping? if so what version were you using
> before? (maybe check your dpkg logs for signs of upgrade of the
> smokeping package)
I just thought of something else: if you were using the 2.7.3-1 package
previou
far into the future, but who knows when :\
On 2024-10-22 14:37, Gabriel Filion wrote:
Package: librarian-puppet
Version: 5.0.0-1
Severity: important
Hello,
I've just installed librarian-puppet in sid and tried using `librarian-puppet
install` to get new dependencies from something I adde
Package: librarian-puppet
Version: 5.0.0-1
Severity: important
Hello,
I've just installed librarian-puppet in sid and tried using `librarian-puppet
install` to get new dependencies from something I added to a Puppetfile and the
binary crashed with the following stack trace:
/usr/lib/ruby/vendor_
201 - 227 of 227 matches
Mail list logo
