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
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
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
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
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
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
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
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
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
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,
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:
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
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
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
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
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
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
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
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
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
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
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
Package: wnpp
Severity: wishlist
* Package name: shellspec
Version : 0.28.0
Upstream Author : Koichi Nakashima <>
* URL : https://github.com/shellspec/shellspec
* License : Expat
Programming Lang: Shell
Description : Unit testing framework using the BDD
Package: facter
Version: 3.14.12-1+b2
Severity: normal
Hello,
The "facter" package currently does not ship the .gemspec file that gets
generated during build. This means that facter is not visible as an installed
system-wide gem.
The impact of this is that other packages that depend on the
Package: python3-pypuppetdb
Version: 0.3.3-2
Severity: normal
Hello, the version of this library that's currently in debian is now 3 years
old and new versions were released since.
The latest release is 2.2.0 from june 2020. It brings in a couple desirable
changes among which are:
* support
Package: trocla
Severity: normal
Hello,
according to github tag timestamps[0], version 0.3.0 of trocla was released in
august 2017.
[0]:https://github.com/duritong/trocla/tags
it would be nice to get the newer version in debian , especially since
puppet-related tools have the tendency to move
Package: python3-plac
Version: 0.9.6-1
Severity: normal
Hello,
The plac library has see some releases since the current version that's in the
debian archive was released.
Version 1.2.0 is currently available:
https://pypi.org/project/plac/#files
Version 0.9.6 was released in 2016:
On 2020-10-05 9:58 a.m., Tobias Frost wrote:
On Sun, Oct 04, 2020 at 01:59:33PM -0400, Gabriel Filion wrote:
Package: gnome-shell-extension-autohidetopbar
Version: 20200921-1
Severity: normal
Hello,
I've run upgrades today on debian sid, and gnome-shell was upgraded from
3.36.6-1 to 3.38.0-2
Package: gnome-shell-extension-autohidetopbar
Version: 20200921-1
Severity: normal
Hello,
I've run upgrades today on debian sid, and gnome-shell was upgraded from
3.36.6-1 to 3.38.0-2. The autohidetopbar is not working, and in gnome-tweaks I
see a message on the add-on that says "Error loading
Package: opendkim
Version: 2.11.0~alpha-12
Severity: normal
Hello,
When installing opendkim on debian buster, I get the following warning:
Setting up opendkim (2.11.0~alpha-12) ...
Created symlink /etc/systemd/system/multi-user.target.wants/opendkim.service ->
Hi there,
This bug is still present and it's annoying that we can't use the plugin
with tls connections because of it. There hasn't been any movement
upstream for 8 years now unfortunately.
But, thanks to Jan's input, I've tried a simple workaround of just
commenting out all of the calls to the
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).
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.
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
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
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
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 :
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 :
Hi Cameron,
Sorry it took me so much time to reply. I've just now fixed my local
discardable VM setup for testing so I'm able to dive in again.
On Tue, 11 Feb 2020 11:23:19 +1000 Cameron Davidson
wrote:
> This has just started hapenning to my also.
>
> The cause, I think, that evenutally a
Hi Guido,
thanks for your quick feedback! much appreciated.
On 2020-04-17 3:10 a.m., Guido Günther wrote:
> On Thu, Apr 16, 2020 at 06:42:32PM -0400, Gabriel Filion wrote:
>> my user is part of the libvirt and kvm groups so I should have access to the
>> local unix sockets. how
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
FYI I saw that there was an RFP open for puppet-development-kit, which I
had missed earlier: #879271
I've closed this other bug report since this one aims to fulfill it.
signature.asc
Description: OpenPGP digital signature
Package: wnpp
Severity: wishlist
Owner: Gabriel Filion
* Package name: jgrep
Version : 1.5.2
Upstream Author : Pieter Loubser , Dominic Cleal
, R.I. Pienaar
* URL : https://github.com/ploubser/JSON-Grep
* License : Apache-2.0
Programming Lang: Ruby
Package: wnpp
Severity: wishlist
Owner: Gabriel Filion
* Package name: facterdb
Version : 1.2.0
Upstream Author : Mickaël Canévet
* URL : https://github.com/camptocamp/facterdb
* License : Apache-2.0
Programming Lang: Ruby
Description : Database
Package: wnpp
Severity: wishlist
Owner: Gabriel Filion
* Package name: metadata-json-lint
Version : 2.2.0
Upstream Author : Vox Pupuli
* URL : https://github.com/voxpupuli/metadata-json-lint
* License : Apache-2.0
Programming Lang: Ruby
Description
Package: wnpp
Severity: wishlist
Owner: Gabriel Filion
* Package name: ruby-rspec-puppet-facts
Version : 1.10.0
Upstream Author : Mickaël Canévet
* URL : https://github.com/mcanevet/rspec-puppet-facts
* License : Apache-2.0
Programming Lang: Ruby
Package: wnpp
Severity: wishlist
Owner: Gabriel Filion
* Package name: ruby-spdx-licenses
Version : 1.2.0
Upstream Author : Dominic Cleal
* URL : https://github.com/domcleal/spdx-licenses
* License : Expat
Programming Lang: Ruby
Description : Library
Package: wnpp
Severity: wishlist
Owner: Gabriel Filion
* Package name: ruby-tty-spinner
Version : 0.9.3
Upstream Author : Piotr Murach
* URL : https://ttytoolkit.org/
* License : expat
Programming Lang: Ruby
Description : Library for showing a spinner
Hi Kate,
Thanks for this report. rsa1, wow, blast from the past.
On 2019-12-16 10:00 a.m., Dawson, Kate wrote:
> The SSH plugin in smokeping calls ssh-keyscan and expects to look for rsa1
> type keys on initialisation. However ssh-keyscan no longer supports rsa1.
> This causes smokeping to
Package: ganeti-instance-debootstrap
Version: 0.16-6
Severity: wishlist
Tags: upstream
Hi,
I couldn't find an upstream bug reporting page so I'll send it here. If you
have a better idea where the bug tracking happens upstream fo this project,
could you please forward this?
Currently the option
Package: wnpp
Severity: wishlist
Owner: Gabriel Filion
* Package name: ruby-tty-screen
Version : 0.7.0
Upstream Author : Piotr Murach
* URL : https://ttytoolkit.org/
* License : expat
Programming Lang: Ruby
Description : Ruby library that detects
Package: wnpp
Severity: wishlist
Owner: Gabriel Filion
* Package name: ruby-tty-cursor
Version : 0.7.0
Upstream Author : Piotr Murach
* URL : https://ttytoolkit.org/
* License : expat
Programming Lang: Ruby
Description : Ruby library to help move
Package: wnpp
Severity: wishlist
Owner: Gabriel Filion
* Package name: ruby-tty-reader
Version : 0.6.0
Upstream Author : Piotr Murach
* URL : https://ttytoolkit.org/
* License : expat
Programming Lang: Ruby
Description : A set of methods
Package: wnpp
Severity: wishlist
Owner: Gabriel Filion
* Package name: ruby-tty-color
Version : 0.5.0
Upstream Author : Piotr Murach
* URL : http://piotrmurach.github.io/tty
* License : expat
Programming Lang: Ruby
Description : Ruby library
Package: wnpp
Severity: wishlist
Owner: Gabriel Filion
* Package name: ruby-equatable
Version : 0.6.1
Upstream Author : Piotr Murach
* URL : https://github.com/piotrmurach/equatable
* License : expat
Programming Lang: Ruby
Description : Ruby module
Package: wnpp
Severity: wishlist
Owner: Gabriel Filion
* Package name: ruby-pastel
Version : 0.7.3
Upstream Author : Piotr Murach
* URL : https://piotrmurach.github.io/tty/
* License : expat
Programming Lang: Ruby
Description : Terminal strings
Package: rubocop
Version: 0.52.1+dfsg-1
Severity: normal
Hello,
There's been multiple upstream releases since the currently packaged version.
The current latest release is 0.74.0.
version 0.52 was released on december 12th 2017
-- System Information:
Debian Release: bullseye/sid
APT prefers
Package: ruby-rspec-puppet
Version: 2.6.1-1
Severity: normal
Hi,
The version of rspec-puppet that's currently in sid is quite old: it dates
back to 2017. Upstream has seen a good number of releases since then and it
would be nice to have a fresher version of this code in unstable.
Cheers!
--
Hi,
On 2019-09-18 1:36 a.m., Geert Stappers wrote:
> On Tue, Sep 17, 2019 at 10:52:54AM -0400, Gabriel Filion wrote:
>> I was wondering if folks maintaining the vagrant boxes would be willing to
>> publish additional images that would have puppet/ansible pre-installed with
>>
Package: cloud.debian.org
Severity: wishlist
Hi there,
I've been holding back on using the debian/* boxes with vagrant mostly since
there's no puppet pre-installed in the boxes.
I know that, as documented in the wiki, I can install puppet with a shell
provisioner, but doing that on every boot
Package: nagios-plugins-contrib
Version: 24.20190301
Severity: normal
Hi,
Ever since the package version in buster, debsecan gets installed
automatically when you let "recommends" install.
It also means that it gets installed automatically during a dist-upgrade to
buster.
This means that root
Package: wnpp
Severity: wishlist
Owner: Gabriel Filion
* Package name: ruby-necromancer
Version : 0.5.0
Upstream Author : Piotr Murach
* URL : https://github.com/piotrmurach/necromancer
* License : Expat
Programming Lang: Ruby
Description : Conversion
Package: wnpp
Severity: wishlist
Owner: Gabriel Filion
* Package name: ruby-tty-prompt
Version : 0.19.0
Upstream Author : Piotr Murach
* URL : https://ttytoolkit.org/
* License : Expat
Programming Lang: Ruby
Description : Beautiful and powerful
Package: wnpp
Severity: wishlist
Owner: Gabriel Filion
* Package name: ruby-pathspec
Version : 0.2.1
Upstream Author : Brandon High
* URL : https://github.com/highb/pathspec-ruby
* License : Apache License 2.0
Programming Lang: Ruby
Description : Ruby
On Mon, 02 Sep 2019 17:11:44 -0400 Gabriel Filion
wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Gabriel Filion
>
> * Package name: ruby-pdk
I've discussed the name a bit on different channels today and the folks
in the ruby team told me that calling it "ruby-pdk
Package: wnpp
Severity: wishlist
Owner: Gabriel Filion
* Package name: ruby-pdk
Version : 1.13.0
Upstream Author : Puppet, Inc.
* URL : https://github.com/puppetlabs/pdk
* License : Apache License 2.0
Programming Lang: Ruby
Description : A CLI
has started to look like something more concrete and I'll
continue working out the remaining details in the coming weeks to remove
lintian errors:
https://salsa.debian.org/ruby-team/vagrant-librarian-puppet
On Sun, 10 Mar 2019 20:41:21 -0400 Gabriel Filion
wrote:
> Package: wnpp
> Se
On Sat, 6 Jul 2019 13:01:12 -0400 Gabriel Filion
wrote:
> On Tue, 2 Apr 2019 10:46:38 -0400 Gabriel Filion
> wrote:
> > On 2019-03-26 3:26 p.m., BERTRAND Joël wrote:
> > >> Did you recently upgrade smokeping? if so what version were you
> > >> using before? (
On Thu, 11 Jul 2019 10:21:08 +0200 =?UTF-8?B?SmnFmcOtIEp1xZlpY2E=?=
wrote:
> I think I solvedthe Keith's problem. I had same issue when I yesterday
> installed smokeping and after I read that smokeping has apache config I
> tried another url then before. Firstly I tried url
>
On 2019-08-23 11:07 p.m., tony mancill wrote:
> On Fri, Aug 23, 2019 at 04:44:07PM -0400, Gabriel Filion wrote:
> From the PTS page [1], I see the excuse as:
> [1] https://tracker.debian.org/pkg/trapperkeeper-webserver-jetty9-clojure
> testing migrations
> excuses:
> - 38
Hello!
Thanks a bunch for the fix to the
libtrapperkeeper-webserver-jetty9-clojure package.
I'm wondering though why the package hasn't migrated to testing (and
stable) yet. This info is completely uninformative about the situation:
Hello,
On Wed, 21 Aug 2019 10:16:26 -0400 Antoine Beaupre
wrote:
> Vagrant, using the libvirt backend, started failing me recently, with
> something like this:
>
> anarcat@curie:stretch64(master)$ vagrant up --provider libvirt
> Bringing machine 'default' up with 'libvirt' provider...
> ==>
On 2019-08-12 10:43 a.m., Gabriel Filion wrote:
> It seems to me that some folks reported in this issue being able to stop
> the influx of emails by chaning the "format" option where edgetrigger is
> set. Did you try applying this solution?
woops! sorry for the impreci
Hi there Gerald,
On 2019-08-07 2:09 p.m., Gerald Turner wrote:
> Control: tags -1 + patch
>
> I've created a patch which restores "prevmatch" to being a boolean,
> fixing the edgetrigger alerts. I built and tested the package with this
> patch.
>
> The only side-effect is the aformentioned
Package: munin-plugins-extra
Version: 2.0.49-1
Severity: normal
Hello,
I've been using the multigraph plugin for asterisk that's present in
the munin-contrib repository for a number of years and find it nice.
I was wondering if this package would be well suited for including it.
For what it's
Package: puppetdb
Version: 6.2.0-3
Severity: grave
Justification: renders package unusable
Hi there!
I've hit a bug with a new installation of puppetdb on buster (e.g. I've
re-created my puppetmaster vagrant box) where puppetdb would fail to start,
erroring out on an SQL upgrade of the database
Hello Simon,
On Wed, 18 Jan 2012 19:21:26 + Simon Wilcox
wrote:
> Smokeping has the ability to run in a master/slave configuration.
>
> In the slave configuration data is sent to a master server and a local
> apache installation is not required.
>
> We want to install smokeping on devices
Hi Keith,
I'm terribly sorry for the time it took to respond to your bug report.
On Sat, 25 May 2019 10:09:27 +0100 Keith Edmunds
wrote:
> Package: smokeping
> Version: 2.7.3-2
> Severity: important
>
> System was upgraded from Stretch to Buster, with smokeping working on Stretch.
>
> After
Hi again Bertrand,
On Tue, 2 Apr 2019 10:46:38 -0400 Gabriel Filion
wrote:
> On 2019-03-26 3:26 p.m., BERTRAND Joël wrote:
> >> Did you recently upgrade smokeping? if so what version were you
> >> using before? (maybe check your dpkg logs for signs of upgrade of
>
Hi,
Since the bug report was indicating that the issue was fixed in
3.4.2-1+deb8u4, I've tried to apply upgrades and it seems to have
upgraded successfully. So the fix seems to work for me!
signature.asc
Description: OpenPGP digital signature
Hi again!
On Tue, 7 May 2019 02:24:59 -0400 Gabriel Filion wrote:
> On Mon, 29 Apr 2019 15:44:39 +0200 Santiago Vila wrote:
> > On Mon, Apr 29, 2019 at 01:22:18PM +, Holger Levsen wrote:
> > > if we now could please focus on #928172 and ignore #927450 for now,
> &g
On Mon, 29 Apr 2019 15:44:39 +0200 Santiago Vila wrote:
> On Mon, Apr 29, 2019 at 01:22:18PM +, Holger Levsen wrote:
> > if we now could please focus on #928172 and ignore #927450 for now,
> > that would be great. (and "ignoring #927450" also means not mixing them
> > up.)
>
> Let's focus
Package: cryptsetup
Version: 2:2.1.0-2
Severity: grave
Justification: renders package unusable
Hello,
I've rebooted my computer this morning and the password prompt to unlock the
crypto device would not appear before grub would search for the lvm device
inside.
This means that the system was not
Hello,
On 2019-03-26 3:26 p.m., BERTRAND Joël 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)
> Yes, I have.
>
> -> 2019-03-17 03:26:38 upgrade smokeping:all 2.7.2-3
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
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.
>
>
Hello,
Additionally to what wavexx reported, the systemd unit file is also
pointing PIDFile= inside the deprecated /var/run instead of /run. The
init script is also pointing to that directory.
I'm reporting this here since it's related to why that tmpfiles line
exists. However, this would imply
Package: wnpp
Severity: wishlist
Owner: Gabriel Filion
* Package name: vagrant-librarian-puppet
Version : 0.9.2
Upstream Author : Vox Pupuli
* URL : https://github.com/voxpupuli/vagrant-librarian-puppet
* License : MIT
Programming Lang: Ruby
Description
Package: puppet
Version: 5.5.10-1
Severity: normal
Hello,
I recently saw that the "puppet" package deploys the ruby code for
puppet, but does not install that code as a gem.
This means that other packages that should depend on puppet cannot
satisfy their dependencies, and debian packages need
tag 923087 pending
thanks
Date: Sat Feb 23 20:03:41 2019 -0500
Author: Gabriel Filion
Commit ID: 34b9da1de902be0f4e43fd99d0fcb7e278bedbd9
Commit URL:
https://git.sigxcpu.org/cgit/git-buildpackage//commit/?id=34b9da1de902be0f4e43fd99d0fcb7e278bedbd9
Patch URL:
https://git.sigxcpu.org/cgit/git
I've formatted a patch for upstream that fixes this behaviour. See file
attached
From 42582015feef85b760932c05e802e2f65418a19c Mon Sep 17 00:00:00 2001
From: Gabriel Filion
Date: Sat, 23 Feb 2019 20:03:41 -0500
Subject: [PATCH] Disable PGP signatures when retrieving list of commits
gbp dch
Package: git-buildpackage
Version: 0.9.13
Severity: normal
Hi,
I'm having difficulty running gbp dch. I get the following output (with
--verbose set):
pkg-smokeping$ gbp dch --verbose
gbp:debug: ['git', 'rev-parse', '--show-cdup']
gbp:debug: ['git', 'rev-parse', '--is-bare-repository']
Hello,
I've taken a look at this issue and I believe that in theory the file
"smokeping_secrets" should not be managed by the package as a config
file at all.
...however while trying to patch the package for this, I relized the
following:
* smokeing absolutely *wants* to have "secrets="
1 - 100 of 212 matches
Mail list logo
