Hello!
I'm writing to inform you that TPA's been moving on something that
should make it possible to eventually merge both of the prometheus /
grafana servers: we're moving towards per-user passwords that need to be
set through LDAP and deprecating the shared passwords.
I would invite every
16:30, Gabriel Filion wrote:
Hello ruby team!
I've worked today on bumping the upstream version for the package
metadata-json-lint (meant to validate files named metadata.json, linked
to puppet modules), which has no other dependencies.
However, I'm still not a debian maintainer and since
Hello!
I'm writing to inform you that TPA's been moving on something that
should make it possible to eventually merge both of the prometheus /
grafana servers: we're moving towards per-user passwords that need to be
set through LDAP and deprecating the shared passwords.
I would invite every
user debian-rele...@lists.debian.org
usertag 1100286 + bsp-2025-03-ca-montreal
tags 1100286 + confirmed upstream
thank you
Hello,
I'm able to reproduce this test failure. I also tried directly on the
upstream project and the same failure is happening there, too on the
latest commin on the `mai
user debian-rele...@lists.debian.org
usertag 1100286 + bsp-2025-03-ca-montreal
tags 1100286 + confirmed upstream
thank you
Hello,
I'm able to reproduce this test failure. I also tried directly on the
upstream project and the same failure is happening there, too on the
latest commin on the `mai
user debian-rele...@lists.debian.org
usertag 1099272 + bsp-2025-03-ca-montreal
tags 1099272 + fixed-upstream
thank you
Hello,
Upstream has apparently already fixed this issue:
https://github.com/bimmerconnected/bimmer_connected/pull/693
This fix was also released in a new upstream version.
So
user debian-rele...@lists.debian.org
usertag 1099272 + bsp-2025-03-ca-montreal
tags 1099272 + fixed-upstream
thank you
Hello,
Upstream has apparently already fixed this issue:
https://github.com/bimmerconnected/bimmer_connected/pull/693
This fix was also released in a new upstream version.
So
user debian-rele...@lists.debian.org
usertag 1091947 + bsp-2025-03-ca-montreal
tags 1091947 + patch
thank you
Hello,
The error that's happening in the build log has been handled by upstream
by disabling the failing test.
So we could fix this by bumping the library version to version 0.5.7
wh
user debian-rele...@lists.debian.org
usertag 1091947 + bsp-2025-03-ca-montreal
tags 1091947 + patch
thank you
Hello,
The error that's happening in the build log has been handled by upstream
by disabling the failing test.
So we could fix this by bumping the library version to version 0.5.7
wh
user debian-rele...@lists.debian.org
usertag 1100306 + bsp-2025-03-ca-montreal
usertag 1100307 + bsp-2025-03-ca-montreal
usertag 1100310 + bsp-2025-03-ca-montreal
usertag 1100313 + bsp-2025-03-ca-montreal
usertag 1100314 + bsp-2025-03-ca-montreal
usertag 1100315 + bsp-2025-03-ca-montreal
tags 1100
user debian-rele...@lists.debian.org
usertag 1100306 + bsp-2025-03-ca-montreal
usertag 1100307 + bsp-2025-03-ca-montreal
usertag 1100310 + bsp-2025-03-ca-montreal
usertag 1100313 + bsp-2025-03-ca-montreal
usertag 1100314 + bsp-2025-03-ca-montreal
usertag 1100315 + bsp-2025-03-ca-montreal
tags 1100
user debian-rele...@lists.debian.org
usertag 1100306 + bsp-2025-03-ca-montreal
usertag 1100307 + bsp-2025-03-ca-montreal
usertag 1100310 + bsp-2025-03-ca-montreal
usertag 1100313 + bsp-2025-03-ca-montreal
usertag 1100314 + bsp-2025-03-ca-montreal
usertag 1100315 + bsp-2025-03-ca-montreal
tags 1100
For what it's worth I found this which seems to point towards our bug
being 'thin' not yet supporting rack 3:
https://github.com/macournoyer/thin/issues/389
maybe we should reassign this to thin? (I'm not doing it now since I'm
not yet 100% confident on my analysis)
_
For what it's worth I found this which seems to point towards our bug
being 'thin' not yet supporting rack 3:
https://github.com/macournoyer/thin/issues/389
maybe we should reassign this to thin? (I'm not doing it now since I'm
not yet 100% confident on my analysis)
For what it's worth I found this which seems to point towards our bug
being 'thin' not yet supporting rack 3:
https://github.com/macournoyer/thin/issues/389
maybe we should reassign this to thin? (I'm not doing it now since I'm
not yet 100% confident on my analysis)
Hello,
I'm able to reproduce this bug on testing by just installing the
schleuder package.
Once that's done we can see that schleuder-api-daemon.service is
erroring out on startup
I'm not very confident about my skills for analysing ruby errors.. but
it looks like the problem might be stem
Hello,
I'm able to reproduce this bug on testing by just installing the
schleuder package.
Once that's done we can see that schleuder-api-daemon.service is
erroring out on startup
I'm not very confident about my skills for analysing ruby errors.. but
it looks like the problem might be stem
Hello,
I'm able to reproduce this bug on testing by just installing the
schleuder package.
Once that's done we can see that schleuder-api-daemon.service is
erroring out on startup
I'm not very confident about my skills for analysing ruby errors.. but
it looks like the problem might be stem
Package: unbound-anchor
Version: 1.17.1-2+deb12u2
Severity: important
Dear Maintainer,
We've been using unbound-anchor on our servers for a good while now and
we've been struggling with an issue that has an impact on the
reliability of the local DNS resolver.
When machines end up having th
Hello ruby team!
I've worked today on bumping the upstream version for the package
metadata-json-lint (meant to validate files named metadata.json, linked
to puppet modules), which has no other dependencies.
However, I'm still not a debian maintainer and since I get to touch
debian packaging o
Hello Jonathan,
Thanks for the bug report and the patch!
I've taken the time to test the issue in a new install of bookworm and I
wasn't able to reproduce it: smokeping correctly collects ping data from
localhost.
From what I can see in the VM, fping was already setup with cap_net_raw
direc
Hello all,
The TPA team had a meeting today where we prioritized our goals mostly
for Q1 of 2025 and had discussions about how to go around furthering the
merger with tails, especially on the Puppet side (e.g. so that both Tor
and Tails infrastructures can become managed by only one tool)
He
Hello again,
On 2024-11-21 12:13, Gabriel Filion wrote:
we're planning to
move/migrate the gitlab server from our Falkenstein-based cluster to the
one in Dallas.
This move will be happening on Thursday november 28th starting at 18:00
UTC.
The VM migration is now complete and the g
Hello all,
I'm sending a reminder about this since the last communication about it
was more than a month ago.
Hetzner is planning to perform maintenance on their networking equipment
next week, on December 3rd between 3:30 and 5:30 UTC. This is something
that the TPA team does not have contr
Hello,
Additionally to the mail server switch on Monday, we're planning to
move/migrate the gitlab server from our Falkenstein-based cluster to the
one in Dallas.
This move will be happening on Thursday november 28th starting at 18:00 UTC.
The disks for the gitlab server are fairly sizeable
On 2024-11-02 18:40, Cédric Boutillier wrote:
Hi Gabriel,
Can you push the upstream branch/tag and the pristine-tar branch? It
seems they haven't reached salsa.
argh sorry I always forget this part :\
I just used gbp push to send the upstream branch and tag for 0.7.0
Everything else looks f
Hello,
I've prepared the new upstream version for ruby-necromancer and I would
now need some help with verifying that I haven't missed something and
then also to send the new package to the archive since I don't have this
access.
Can I ask someone to please take a look at ruby-necromancer an
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
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_
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_
Package: ganeti
Version: 3.0.2-3
Severity: wishlist
Hello!
I've recently tried to read the ganeti man pages on manpages.debian.org but
found out that all of the man pages give out a 404 error there.
According to https://github.com/Debian/debiman/issues/177 this problem happens
in debiman specifi
On 2024-08-10 15:07, Antoine Beaupré wrote:
On 2024-08-05 10:35:55, Gabriel Filion wrote:
The manpage for undertime(1) mentions toward the end of the document
that there
should be an example configuration file in
/usr/share/doc/undertime/examples/undertime.yml
However, I don't see this fi
Hello Nis,
On 2024-08-10 16:03, Nis Martensen wrote:
Hi Gabriel,
On 05.08.2024 17.00, Gabriel Filion wrote:
When using the text UI, when it comes time to send via SMTP and I
need to connect to an MTA in order to send the email as an
authenticated user, if I happen to mistype the password I
Hello,
The upstream bug report was closed with a new release 1.10 Apparently
there was already a fix committed upstream and now it's part of a new
release.
Could we bump the version (again) to 1.10.0 in the hope that this error
gets fixed?
Thanks!
Hello,
The upstream bug report was closed with a new release 1.10 Apparently
there was already a fix committed upstream and now it's part of a new
release.
Could we bump the version (again) to 1.10.0 in the hope that this error
gets fixed?
Thanks!
Package: devscripts
Version: 2.23.7
Severity: normal
Hello,
I've been trying to send update a bug report with bts but right after I supply
my email password, bts crashes with the following error:
SMTP connection is already in SSL mode at /usr/share/perl/5.38/Net/SMTP.pm line
621, line 2.
note
close 1064686
thanks
The build issue was fixed with the tag 0.9.2-3 but the changelog did not
mark this issues as being closed by the correction.
Closing the issue now
The build issue was fixed with the tag 0.9.2-3 but the changelog did not
mark this issues as being closed by the correction.
Closing the issue now
The build issue was fixed with the tag 0.9.2-3 but the changelog did not
mark this issues as being closed by the correction.
Closing the issue now
___
Pkg-ruby-extras-maintainers mailing list
Pkg-ruby-extras-maintainers@alioth-lists.debian.net
https:/
mething that works
better. this
is just an example to better illustrate what I mean):
Y - (default) Yes, please retry.
p - Yes, please retry, but prompt again for the password.
n - No, save and exit.
q - Quit.
? - Display this help.
Cheers!
-- Package-specific info:
** Environment settings:
DE
Package: undertime
Version: 4.0.0
Severity: wishlist
Hello,
Thanks for maintaining undertime in debian (and maintaining it upstream
too :)
)
The manpage for undertime(1) mentions toward the end of the document
that there
should be an example configuration file in
/usr/share/doc/undertime/ex
Package: libsequoia-octopus-librnp
Version: 1.8.1-4
Severity: important
Hello,
I run sid and yesterday I did a run of upgrades.
Before the upgrades I was using thunderbird 115.12.0 and things were working
great.
However during the upgrade run, thunderbird was upgraded to 115.13.0 and now
thund
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 for
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 th
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,
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
Hello!
Just wanted to chime in to confirm that James' patch does make the
package compile.
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 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
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
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
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
Package: wnpp
Severity: wishlist
Owner: Gabriel Filion
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: libobject-result-perl
Version : 0.03
Upstream Author : Damian Conway
* URL : https://metacpan.org/release/Object-Result
* License
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: 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: 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: wnpp
Severity: wishlist
Owner: Gabriel Filion
X-Debbugs-Cc: debian-devel@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: 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
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
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
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
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
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
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
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, 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
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
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
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
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 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,
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.
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
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
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
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
Upstream hasn't yet made a release that includes the fix.
Since this is currently affecting the software on certain hosts and
making it impossible to connect to hosts using Let's Encrypt
certificates (we're seeing this problem with a production host), I'm
wondering if the patch could be includ
Package: smokeping
Severity: normal
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 would remove patches in the package.
I've received two emails directly requesting th
Package: undertime
Version: 2.6.0
Severity: grave
Justification: renders package unusable
Hello,
I'm currently getting stack traces consistently when using undertime. No matter
the timezone that I request, I get a stack trace with a TypeError exception:
$ undertime pt
Traceback (most recent call
Package: undertime
Version: 2.6.0
Severity: grave
Justification: renders package unusable
Hello,
I'm currently getting stack traces consistently when using undertime. No matter
the timezone that I request, I get a stack trace with a TypeError exception:
$ undertime pt
Traceback (most recent call
On 2021-09-07 6:10 p.m., Georg Faerber wrote:
On 21-08-21 19:41:24, Gabriel Filion wrote:
One of my packages was bumped out of testing during the freeze because
of a dependency problem in one of its requirements, ruby-puppet-forge
(e.g. #978228)
This bug is still open, and due to its
On 2021-09-07 6:05 p.m., Georg Faerber wrote:
Could someone please review my work and help me out with upload to
debian archive? I'm neither a DD nor a DM so I can't send there
myself.
* https://salsa.debian.org/ruby-team/facterdb
* https://salsa.debian.org/ruby-team/ruby-rspec-puppet-facts
Package: ganeti-3.0
Version: 3.0.1-2
Severity: normal
Hello,
I've just performed an upgrade of a ganeti cluster from buster+2.16 to
bullseye+3.0 and hit a problem during the upgrade.
The procedure that I used was to:
1. install ganeti 3.0 from buster-backports and upgrade the cluster
2. run O
Hello,
One of my packages was bumped out of testing during the freeze because
of a dependency problem in one of its requirements, ruby-puppet-forge
(e.g. #978228)
I've just looked at the state of things and if I understand correctly,
the dependency issues were fixed in #976270
So normally
Hello,
Today I've worked on fixing tests for autopkgtest for both facterdb and
ruby-rspec-puppet-facts.
Since both of them never made it to testing (because of the failing
autopkgtest), I've also decided to upgrade both of them to the current
latest upstream release.
Could someone please r
Hello,
Since the package I'm working on, puppet-development-kit, requires a
more recent version of ruby-hitimes I've worked on importing the latest
upstream release, 2.0.0.
Since I'm not a debian developer I would need someone to review my work
before sending it out the debian archive.
Thi
Package: wnpp
Severity: wishlist
* Package name: vim-vint
Version : 0.4a4
Upstream Author : Kuniwak
* URL : https://github.com/Vimjas/vint
* License : MIT
Programming Lang: Python
Description : Fast and highly extensible Vim script language lint
Vint i
Package: wnpp
Severity: wishlist
* Package name: vim-vint
Version : 0.4a4
Upstream Author : Kuniwak
* URL : https://github.com/Vimjas/vint
* License : MIT
Programming Lang: Python
Description : Fast and highly extensible Vim script language lint
Vint i
Hello,
On 2021-06-29 16 h 08, Jan Wagner wrote:
Hi Gabriel,
Am 29.06.21 um 19:34 schrieb Gabriel Filion:
I would like to suggest breaking up this package into smaller binary
packages
that are focused on one application/service per package. This way one
could
install only the checks that are
Package: monitoring-plugins-contrib
Severity: normal
Hello,
The monitoring-plugins-contrib package contains many useful things, so I tend
to always install it on hosts. However, many checks that are contained within
it are not really useful most of the time. This means that if I just install
this
Hi there Patrik,
Thanks for the change you've submitted! As you said, the init script is
still there in the package so we might as well keep it maintained.
I've committed your change to salsa and it should make it to the next
upload.
I'll see if I can gather the efforts necessary to get an
down below?
Thanks!
On 2021-03-24 11:11 p.m., Gabriel Filion wrote:
one of the requirements for the puppet-development-kit (pdk) application
is ruby-hitimes, and pdk's gemspec specifies that a version, 1.3.0, more
recent than the one currently in debian archives was needed. When I
checked upstr
Package: python3-sshtunnel
Version: 0.1.4-2
Severity: normal
Hello,
Thanks for maintaining this library package, I've used it to make things
easier for reaching services that are reachable only on localhost on
certain machines.
I've just encountered a bug with the currently available version whe
Package: python3-sshtunnel
Version: 0.1.4-2
Severity: normal
Hello,
Thanks for maintaining this library package, I've used it to make things
easier for reaching services that are reachable only on localhost on
certain machines.
I've just encountered a bug with the currently available version whe
On 2021-03-24 11:23 p.m., Gabriel Filion wrote:
On 2021-03-24 11:11 p.m., Gabriel Filion wrote:
one of the requirements for the puppet-development-kit (pdk)
application is ruby-hitimes, and pdk's gemspec specifies that a
version, 1.3.0, more recent than the one currently in debian arc
1 - 100 of 640 matches
Mail list logo
