Hi Lars,
Am 20.02.19 um 21:13 schrieb Lars Kruse:
> Am Wed, 20 Feb 2019 13:33:34 +
> schrieb Holger Levsen :
>> strangely this commit is in Buster:
>> ~/Projects/munin/munin$ git tag --contains 44604624b1c27f6
>> 2.0.44
>> 2.0.45
>> debian/2.0.44-1
>> debian/2.0.44-1_bpo9+1
>> debian/2.0.44-2
Hello,
Am Wed, 20 Feb 2019 13:33:34 +
schrieb Holger Levsen :
> strangely this commit is in Buster:
>
> ~/Projects/munin/munin$ git tag --contains 44604624b1c27f6
> 2.0.44
> 2.0.45
> debian/2.0.44-1
> debian/2.0.44-1_bpo9+1
> debian/2.0.44-2
> debian/2.0.45-1
> debian/2.0.45-1_bpo9+1
>
>
Hi Jan,
thanks for coming back to this!
On Wed, Feb 20, 2019 at 02:21:10PM +0100, Jan Wagner wrote:
> Am 06.07.13 um 09:23 schrieb David Schmitt:
> > root@testagent:~# /usr/share/munin/plugins/apt_all update 7200 1
> > E: The value 'testing' is invalid for APT::Default-Release as such a
> >
Am 06.07.13 um 09:23 schrieb David Schmitt:
> root@testagent:~# /usr/share/munin/plugins/apt_all update 7200 1
> E: The value 'testing' is invalid for APT::Default-Release as such a
> release is not available in the sources
> E: The value 'unstable' is invalid for APT::Default-Release as such a
>
Package: munin-plugins-core
Version: 2.0.25-1+deb8u2
Followup-For: Bug #715141
Hi,
This issue just appeared on my Jessie stable in one of the recent update
of the package through unattended-upgrades.
For now I've worked around by manually editing the apt_all script to
change
> my @releases =
Hi,
I too am interested in getting this fixed.
(see also: #761190)
Regards
Ingmar
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hi Steve,
On Tue 03.09.2013 08:17:36, Steve Schnepp wrote:
Looking closely, that was done specifically like that. But it sounds wrong
to me, and qualifies as a bug. Will be fixed in the next upstream stable
release.
The extra $ARGV will be transparently given to the plugin, as the config
or
Le 3 sept. 2013 03:15, DUVERGIER Claude claude@duvergier.fr a
écrit :
But sadly munin-run don't push the extra 7200 and 12 parameters to
the apt_all
Looking closely, that was done specifically like that. But it sounds wrong
to me, and qualifies as a bug. Will be fixed in the next upstream
Hi,
I've applied the proposed solution (using $ENV{MUNIN_APT_RELEASES}) but
ran into an unsuspected issue:
munin-node package creates a cron jobs file (/etc/cron.d/munin-node)
where it directly runs the apt_all plugin, as an executable script, not
through Munin's system (like `munin-run`
Package: munin-plugins-core
Version: 2.0.6-4+deb7u1
Severity: minor
Hi,
when using the apt_all plugin the cronjob creates the following error
messages, when only stable is configured:
root@testagent:~# /usr/share/munin/plugins/apt_all update 7200 1
E: The value 'testing' is invalid for
10 matches
Mail list logo
