Hello,
Am Wed, 4 Sep 2024 19:48:27 -0300
schrieb Antonio Terceiro :
> Can you please clarify how exactly are you hitting this issue? Can you
> provide an example of how I can reproduce this?
yes, sorry for omitting these details in my initial bug report.
I just created a fresh image for testin
Package: gosa
Version: 2.8~git20230203.10abe45+dfsg-1+deb12u2
Severity: normal
Dear Maintainer,
I recently noticed, that I cannot edit properties of a user account
in the GOsa web interface anymore.
This applies to my own account as well as other people's accounts in an
admin context.
I am runni
Package: gosa
Version: 2.8~git20230203.10abe45+dfsg-1+deb12u2
Severity: normal
Dear Maintainer,
thank you for maintaining gosa!
I just run the web-based setup procedure of gosa in Debian Bookworm.
Quite early I received the following error:
PHP Fatal error: Uncaught TypeError: ldap_get_entries
Package: auto-apt-proxy
Version: 14.1
Severity: normal
Dear Maintainer,
according to d#756656 [1] https-URLs cannot be given to `approx`.
Thus, the `approx` check should be skipped when an https URL is
requested.
Cheers,
Lars
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756656
Package: auto-apt-proxy
Version: 14.1
Severity: normal
Dear Maintainer,
Hello,
in my environment the name `apt-proxy` resolves to both an IPv4 and an
IPv6 address.
In `/usr/bin/auto-apt-proxy` the hostname `apt-proxy` is resolved via
the following command:
getent hosts apt-proxy
But the abov
Source: django-macaddress
Version: 1.5.0-3
Severity: wishlist
Dear Maintainer,
a few minor releases were published for django-macaddress during the
last years.
Mostly they deal with issues regarding compatibility with more recent
Django versions.
See [1] for details.
I would really appreciate, i
Package: gitlab
Version: 15.2.3+ds1-2~fto11+1
Severity: normal
Dear Maintainer,
recently I noticed, that the following gitlab-related services remained
in the "failed" state after booting the VM:
* gitlab-puma
* gitlab-sidekiq
* gitlab-workhorse
The problem was caused by the absence of the datab
Package: gitlab
Version: 15.2.3+ds1-2~fto11+1
Severity: normal
Tags: patch
Dear Maintainer,
during gitlab's package installation, the following line in
`rake-tasks.sh` causes a failure of the postinst processing:
> -runuser -u ${gitlab_user} -- sh -c 'test -d "/var/lib/gitlab/.cache/yarn/v6"
>
Package: kexec-tools
Version: 1:2.0.24-1+b1
Followup-For: Bug #1010406
Control: tags -1 patch
Dear Maintainer,
here on my system I replaced the content of the "restart" branch with
a simple stop/start sequence:
restart|reload|force-reload)
"$0" stop
"$0" start
;;
Thi
Source: pyserial-asyncio
Version: 0.5-2
Severity: normal
Dear Maintainer,
I just noticed, that the python3-serial-asyncio package announces the
following packages as hard dependencies ("Depends"):
python3-serial, python3:any, libjs-sphinxdoc, sphinx-rtd-theme-common
I guess, that the two sphi
Package: slt
Version: 0.0.git20140301-6+b3
Severity: normal
Tags: patch
Dear Maintainer,
currently the stl package lacks a systemd service.
Attached you find one.
The service contains my specific execution restrictions.
Thus should help working around slt's lack of priviledge dropping.
The syst
Package: sogo
Version: 5.0.1-4+deb11u1
Severity: minor
Dear Maintainer,
the sogo backup script (/usr/sbin/sogo-backup) contains the following
line:
BACKUP_DIR=${BACKUP_DIR:-/var/backups/backups}
Instead it should probably be:
BACKUP_DIR=${BACKUP_DIR:-/var/backups/sogo}
In addition, I *t
Source: bumpversion
Version: 1.0.1-1
Severity: wishlist
Dear Maintainer,
thank you for moving to the new upstream (bump2version, #916498)!
Could you please add the following minor corrections in order to
properly inform users of the new state of the package:
* change `Homepage` in `d/control` t
Package: iproute2
Version: 5.10.0-4
Severity: normal
Dear Maintainer,
I just upgraded a host from Buster to testing.
After reboot my locally configured policy routing failed to work.
How to reproduce:
root@example:~# echo 120 foo >>/etc/iproute2/rt_tables
root@example:~# ip route show table f
Package: gitlab
Version: 13.7.7-1~fto10+1
Severity: normal
Dear Maintainer,
while upgrading from 13.6.7 to 13.7.7, the installation stops (see error
log below).
The cause of the error was guessed within minutes via IRC (thanks!):
> 18:49 sumpfralle1: that looks like an obsolete initializer tha
Package: libpam-modules
Version: 1.4.0-4
Severity: normal
Dear Maintainer,
= Description of the use-case =
I am using pam_mkhomedir on a file server (samba).
Users are managed via LDAP (configured in smbd).
The home directories of users are supposed to be created, as soon as the
user accesses
Package: gitlab
Version: 13.5.6-1~fto10+1
Severity: normal
Dear Maintainer,
after upgrading from 13.4.7-2~fto10+1 to 13.5.6-1~fto10+1, every issue
view shows the following error message at the top:
Failed to load sidebar lock status
No negative impact is visible besides this error message.
T
Package: dh-sysuser
Version: 1.3.5
Severity: wishlist
Dear Maintainer,
I would like to use "dh-sysuser" in order to clean up my prerm/postinst
scripts.
But I am struggling to apply dh-sysuser in the context of the following
postinst script:
https://git.hack-hro.de/grouprise/grouprise/-/blob/ma
Package: kodi-pvr-hts
Version: 4.4.20-1
Severity: normal
Dear Maintainer,
since the update of the Kodi package (2:19.0~beta2+dfsg1-2, many thanks
for that!), the kodi-pvr-hts package is not compatible with the kodi
package anymore (requiring a different version of "kodi-api-pvr").
Instead of goi
Package: gitlab
Version: 13.4.7-1~fto10+1
Followup-For: Bug #901379
Dear Maintainer,
attached you find a patch, that checks whether the configured database
host is "localhost".
The initialization procedure (which works only locally, at the moment)
is only executed if this check succeeds.
The pro
Package: gitlab
Version: 13.4.6-1~fto10+1
Severity: normal
Dear Maintainer,
there are two occurrences of "file" being called in the postinst script.
One example is the following:
> if [ "$(file /etc/gitlab/ssl/gitlab.crt|awk '{ print $NF }')" =
> "/etc/letsencrypt/live/${GITLAB_HOST}/fullchain
Package: oomd
Version: 0.4.0-1
Severity: normal
Tags: patch
Dear Maintainer,
I am happy, that you are providing an init script for the oomd package.
At the moment the script has two small problems:
1) the oomd process cannot detach into background on its own, thus
`/etc/init.d/oomd start` ha
Package: mopidy
Version: 3.0.1-2
Severity: normal
Dear Maintainer,
if mopidy is installed along with python3-pykka 1.2.1-4 (Buster), then
the following error message is emitted:
ModuleNotFoundError: No module named 'pykka.messages'
The "messages" module was introduced into pykka in v2.0.0:
Package: autopkgtest
Version: 5.11
Severity: normal
Tags: patch
Dear Maintainer,
while running autopkgtest for the munin packages, I encountered problems
in combination with sysvinit in the lxc-based container.
The tests were started before all sysvinit scripts were finished.
In a systemd environ
Package: libldap-2.4-2
Version: 2.4.48+dfsg-1+b2
Severity: normal
Dear Maintainer,
I am using claws-mail from Debian testing on i386.
>From time to time claws-mail crashes. Thus I started collecting stack
traces.
Attached you find a stack trace involving "libldap_r".
The most relevant lines sh
Package: libgpgme11
Version: 1.13.1-1
Severity: normal
Dear Maintainer,
I am using the claws-mail package for handling emails (Debian testing
on i386).
Due to repeated crashes, I started to collect stack traces.
This specific issue (related to libgpgme) happened only once during the
last months
Hello Steve,
Am Fri, 12 Apr 2019 21:41:34 -0700
schrieb Steve Langasek :
> After merging munin 2.0.47-1 into Ubuntu, the node-systemd autopkgtest was
> failing on armhf because of a mismatch in the list of plugins being exposed:
> [..]
> The attached patch fixes the test failure by adding a test
Package: linux-image-armmp-lpae
Version: 4.19+104
Severity: normal
Dear Maintainer,
after upgrading from 4.9.144-3 to 4.19+104 I am not able to mount
cryptsetup devices anymore.
# cryptsetup luksOpen /dev/lvm-foo/crypto foo
Enter passphrase for /dev/lvm-foo/crypto:
device-mapper: reload i
Package: cifs-utils
Version: 2:6.8-2
Severity: normal
Dear Maintainer,
recently I changed my LDAP password to a new one, that contains a "$" character.
Afterwards I failed to mount shares with this new password.
I tried the following approaches:
* interactive mount (e.g. "mount -t cifs -o user=f
Control: tags -1 fixed-upstream
Hello Thorsten,
Am Wed, 13 Mar 2019 22:25:04 +
schrieb "Thorsten Ortlepp" :
> >Could you please verify, whether this change fixes your issue?
>
> Yes, this fix made postgres_connections_example work again.
great - thank you!
Lars
Hello Thorsten,
thank you for your report!
Am Tue, 12 Mar 2019 21:48:29 +0100
schrieb Thorsten Ortlepp :
> after I updated munin-plugins-core to 2.0.47-1, the plugin
> postgres_connections_ does not show any values in the graphics for specific
> databases. It does show values for postgres_conne
Control: tags -1 + fixed-upstream
Hello Craig,
thank you for your report!
Am Tue, 12 Mar 2019 13:01:44 +1100
schrieb Craig Sanders :
> I fixed this on my system by replacing the /etc/munin/plugins/cpuspeed symlink
> (to /usr/share/munin/plugins/cpuspeed) with a copy of the plugin and making
>
Package: rainloop
Severity: normal
Dear Maintainer,
I am a user of rainloop and I am glad, that you packaged it.
But recently I took a look at the development activity:
https://github.com/RainLoop/rainloop-webmail/graphs/contributors
This looks a bit bleak :(
(there are only a few maintenance
Package: freeciv-client-sdl
Version: 2.6.0-1
Severity: important
Dear Maintainer,
I tried to run freeciv-sdl2, but sadly it failed with the following
output:
$ LANG= freeciv-sdl2
2: Didn't find the option file. Creating a new one.
2: Migrating options from sdl to sdl2 client
2: Using Video
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
>
> L
Hello,
Am Wed, 20 Feb 2019 16:05:11 +0100
schrieb Steve Schnepp :
> I might be naive, but I'm wondering if some debconf dialog to choose at
> install time might be an option.
Sounds like a good idea to me.
So we have the following options:
A) mention in README.Debian
B) mention in NEWS
C) ask
Hello,
Am Sat, 16 Feb 2019 16:33:53 +0100
schrieb Marc Donges :
> I think to make this less awkward two things would be nice:
>
> - a option to allow monitoring of /home without editing a non-conffile in
> /lib (How is this even done properly? I just edited the service file to
> find the cause
Control: merge -1 918851
Hello Marc,
Am Sun, 10 Feb 2019 22:55:45 +0100
schrieb Marc Donges :
> # Plugins like "df" require access to /home if that is a separate filesystem
> ProtectHome=false
Indeed, this setting prevents your use case.
See the other bug report for this issue:
https://bugs.
Hello Andreas,
Am Thu, 7 Feb 2019 22:36:49 +0100
schrieb Andreas Tille :
> I admit I have no idea what file "tests is seeked in
>
>ERROR: file not found: tests
>
> Any idea how to fix this?
the two failed commands in the autopkgtest suite are "command1" and "command2".
These are the "unna
Hello Mattia,
thank you for your report!
Could it be, that your plugin configuration files contain a section "df"?
In this case the more specific section ("df") would take precedence over the
wildcard section ("df*").
Or maybe another theory: the wildcards are currently applied a bit loosely:
Package: changetrack
Version: 4.7-5
Severity: normal
Tags: patch upstream
Dear Maintainer,
changetrack allows the specification of patterns for "find" to be used
in /etc/changetrack. A use case is the exclusion of specific files
below /etc/ from the change tracking.
Example (excluding daily upd
Hello Vincas,
thank you for reporting this issue!
Am Thu, 03 Jan 2019 14:44:55 +0200
schrieb Vincas Dargis :
> I have noticed that postgres_connections_* graphs started rendering zero
> height graphs after upgrading munin from Streth Backports. This is
> output example:
>
> ```
> # munin-run p
Package: bumpversion
Version: 0.5.3-3
Severity: wishlist
Dear Maintainer,
sadly the bumpversion project [1] seems to have stalled since 2015.
Its maintainer indicated that he should better mark it as unmaintained
[2], but failed to do so up to now.
Two attempts of asking the maintainer for transi
Hello,
Am Fri, 14 Dec 2018 13:39:28 +
schrieb Holger Levsen :
> > gawk and procps are used by many plugins. I am not sure, whether it is worth
> > the trouble to track the plugins (and their corresponding) packages using
> > these
> > common tools.
>
> I agree, those should be depends (o
Hello Benoît-Pierre,
thank you for your bug report!
Am Sun, 22 Apr 2018 12:38:46 +0200
schrieb Benoît-Pierre DEMAINE :
> when the apt-all plugin is loaded (what is automatic on Debian because of
> the package install script), then two cron lines in /etc/cron.d/munin-node
>
> */5 * * * *roo
Hello,
Am Thu, 18 Sep 2014 13:19:24 +0200
schrieb Holger Levsen :
> control: retitle -1 most of munin-nodes suggests should move to
> munin-plugins-core
>
> [..]
>
> The only suggests which should stay are munin and munin-plugins-java, IMO,
> [..]
I prepared a proposal that moves most sugge
Control: tags -1 +fixed-upstream
Hello,
Am Fri, 21 Apr 2017 16:27:26 +0200
schrieb Frederik Himpe :
> >https://github.com/munin-monitoring/munin/issues/794#issuecomment-295878938
> >
> >to be clear, you're only seeing the "2." from that github issue, but
> >not "1.", correct?!
>
> That's corr
Hello Marcel,
Am Wed, 31 Jan 2018 21:28:35 +0100
schrieb Marcel Partap :
> That should teach me a lessen to follow systemd updates!
:)
> I don't even understand the problem, the pid file is no symlink and is owned
> by root.
> chase_symlinks() appears a massive fluke to me. 😄
I would like
Control: forwarded -1 https://github.com/munin-monitoring/munin/issues/1119
Control: tags -1 -patch
Hello Nye,
thank you for taking the time to report and analyze the issue.
Please let us continue the discussion in the upstream issue [1], that you
kindly opened.
I would be happy, if we could rea
Package: mariadb-common
Version: 10.3.0-0+exp2
Severity: normal
Dear Maintainer,
currently the piuparts tests for the munin package in experimental fail.
See
https://piuparts.debian.org/experimental/fail/munin-plugins-mysql_2.999.9-3.log
for an example.
The relevant part of the log:
The foll
Control: tags -1 +pending
Hello Andreas,
thank you for your report.
I prepared a fix for the issue.
@Holger: please take a look at the commit (6d4791c9) in my repository on salsa
[1] and merge it, if it looks good for you.
Cheers,
Lars
[1] g...@salsa.debian.org:sumpfralle-guest/munin.git
Control: tags -1 + pending fixed-upstream
Hello Gerald,
thank you!
Indeed this change was not well understood at that point in time and needed to
be reversed. I just did this:
https://github.com/munin-monitoring/munin/commit/087478ed7df023733e8b3efb37703eadd3305791
The change will be released
Control: tags -1 + pending fixed-upstream
Hello Gerald,
thank you for reporting, analyzing and fixing the issue!
I applied your suggestion upstream. It will be available with the next release
of munin (2.0.44).
Cheers,
Lars
Hello Vincas,
Am Thu, 15 Nov 2018 08:27:40 +0200
schrieb Vincas Dargis :
> After upgrading to 2.0.42-5 from backports, logcheck on multiple Stretch
> machines started to capture this new message:
>
> ```
> Nov 14 22:25:04 dl380 systemd-tmpfiles[13769]:
> [/usr/lib/tmpfiles.d/munin-node.conf:2]
Hello Andreas,
Am Thu, 15 Nov 2018 17:39:10 +0100
schrieb Andreas Pommer :
> I just had a look at the patch, unfortunately, it does not work: [..]
thank you for checking my commit!
Indeed I stopped reading perlfunc's entry for "system" right after the
following:
Does exactly the same thing as
Hello Andreas,
Am Tue, 13 Nov 2018 19:56:12 +0100
schrieb Andreas Pommer :
> The exec() call transfers the execution to the apt-get command, but exec()
> never returns, so the call to the function update_state() afterwards never
> happens, leading to a stale state-file.
thank you for your quick
Hello Christian,
thank you for reporting this issue!
Am Thu, 1 Nov 2018 00:18:26 +0100
schrieb Christian Schrötter :
> I've upgraded my Debian Buster system to OpenSSL 1.1.1-1 (and
> libnet-ssleay-perl 1.85-2).
Just in case it is easy for you to test: does the paranoid mode still works, if
you
Hello Vincas,
thank you for your bug report!
Could you please check whether reverting the changes introduced with
https://github.com/munin-monitoring/munin/commit/d7e138176e9a09b883031544e523e33e5ef9238b
would fix this issue for you?
Cheers,
Lars
Hello,
Am Fri, 19 Oct 2018 18:40:04 +
schrieb Holger Levsen :
> > # failed 1 among 1 test(s)
> > 1..1
> > Dubious, test returned 1 (wstat 256, 0x100)
> > Failed 1/1 subtests
>
> I don't understand this output and thus I dont find it helpful at all.
Indeed: the sharness testing tool does
Package: munin-plugins-core
Followup-For: Bug #863231
Control: retitle -1 Plugins "apt" and "apt_all" use state file with same name
in different locations
Control: forwarded -1 https://github.com/munin-monitoring/munin/issues/1072
Hello,
ok - I took another look at the issue. Sadly it is a bit m
Package: linux-base
Version: 4.5
Severity: normal
Dear Maintainer,
I recently encountered the following situation while trying to remove the
package of a currently running kernel:
root@router-foo:~# apt purge linux-image-4.9.0-6-amd64
Reading package lists... Done
Building dependency tree
Readin
Package: munin-plugins-core
Followup-For: Bug #717287
Hello,
I just fixed this issue upstream:
https://github.com/munin-monitoring/munin/commit/ace9a23aa14a314828b4b8a34b8db3bbea3168ee
It does the following:
* try to use the good statistics provided by "acpi-cpufreq" (as before)
* fall back t
Package: mod-gearman
Version: 1.5.5-1
Severity: minor
Dear Maintainer,
recently the new package "sharness" entered unstable.
Thus you may want to remove its embedded code copy and add a test
dependency instead.
The following actions should be sufficient:
* rm debian/tests/sharness.sh
* find debi
Package: hiera-eyaml
Version: 2.1.0-1
Severity: minor
Dear Maintainer,
recently the new package "sharness" entered unstable.
Thus you may want to remove its embedded code copy and add a test
dependency instead.
The following actions should be sufficient:
* rm debian/tests/sharness.sh
* find debi
Package: puppet-lint
Version: 2.3.3-1
Severity: minor
Dear Maintainer,
recently the new package "sharness" entered unstable.
Thus you may want to remove its embedded code copy and add a test
dependency instead.
The following actions should be sufficient:
* rm debian/tests/sharness.sh
* find debi
Package: puppet-module-puppetlabs-stdlib
Version: 4.25.1-1
Severity: minor
Dear Maintainer,
recently the new package "sharness" entered unstable.
Thus you may want to remove its embedded code copy and add a test
dependency instead.
The following actions should be sufficient:
* rm debian/tests/sh
Source: jemalloc
Version: 3.6.0-11
Severity: minor
Dear Maintainer,
recently the new package "sharness" entered unstable.
Thus you may want to remove its embedded code copy and add a test
dependency instead.
The following actions should be sufficient:
* rm debian/tests/sharness.sh
* find debian/
Package: puppet-module-puppetlabs-concat
Version: 4.2.1-1
Severity: minor
Dear Maintainer,
recently the new package "sharness" entered unstable.
Thus you may want to remove its embedded code copy and add a test
dependency instead.
The following actions should be sufficient:
* rm debian/tests/sha
Package: gearmand
Version: 1.1.18+ds-1
Severity: minor
Dear Maintainer,
recently the new package "sharness" entered unstable.
Thus you may want to remove its embedded code copy and add a test
dependency instead.
The following actions should be sufficient:
* rm debian/tests/sharness.sh
* find deb
Package: puppet-module-puppetlabs-ntp
Version: 7.1.1-1
Severity: minor
Dear Maintainer,
recently the new package "sharness" entered unstable.
Thus you may want to remove its embedded code copy and add a test
dependency instead.
The following actions should be sufficient:
* rm debian/tests/sharne
Hello Bertrand,
Am Sun, 5 Aug 2018 10:01:58 +0200
schrieb BERTRAND Joël :
> Yesterday, after my bug report, I have done a apt dist-upgrade and this
> message disappears. Very strange, perl and munin were not upgraded.
What a pity - this issue looked mysteriously interesting :)
I fail to have a
Package: munin
Followup-For: Bug #905457
Hello Bertrand,
On Sat, 04 Aug 2018 22:35:54 +0200, BERTRAND Joël wrote,
> I don't understand why perl tries to run /usr/sbin/munin, there is no
> such script nor executable.
indeed there is no such file shipped in any munin package.
I just tried to rep
Package: debian-edu-install
Severity: normal
Dear Maintainer,
I recently downloaded the offline version of the Stretch release
(http://ftp.skolelinux.org/skolelinux-cd/debian-edu-9+edu0-USB.iso) and started
the installation in a qemu-based VM.
But sadly the installation failed due to requirement
Package: piuparts.debian.org
Severity: minor
Dear Maintainer,
the piuparts website [1] currently contains two links to /doc/README.html,
but the target file does not exist. The location /doc/ contains only
README.txt (among other files).
Cheers,
Lars
[1] https://piuparts.debian.org/
Hello Sergio,
Am Fri, 13 Jul 2018 12:28:10 -0400
schrieb Sergio Durigan Junior :
> Created:
>
> https://salsa.debian.org/debian/sharness
>
> And added you as a Developer there.
Thank you!
I pushed my repository to its new location. I will remove the old project
after the next packaging uplo
Hello Sergio,
> After I sent you the reply I saw that you're actually packaging on top
> of upstream's git repo. I personally don't like this option, but that's
> a matter of taste. If you haven't yet, I recommend you read:
>
>
> https://honk.sigxcpu.org/projects/git-buildpackage/manual-htm
Hello Sergio,
Am Thu, 12 Jul 2018 21:11:50 -0400
schrieb Sergio Durigan Junior :
> [..]
> Hm, it seems you removed an important line, [..]
stumbling upon my own feet :(
> 1) Since this is the first release of the package, a d/changelog with an
> entry like:
> [..]
> would have been enough.
Hello Sergio,
thank you for reviewing my packaging attempt!
Am Wed, 11 Jul 2018 23:21:05 -0400
schrieb Sergio Durigan Junior :
> [..]
> 1) On d/copyright, you don't list the files under the "debian/"
> directory. These should be listed, and you should be the author. I
> recommend choosing the
Hi Andreas,
Am Sun, 8 Jul 2018 18:09:10 +0200
schrieb Andreas Tille :
> there was a race condition between your patch and my upload. [..]
what a nice indication for an overwhelmingly responsive package maintainer :)
Thank you!
Cheers,
Lars
Package: blends-dev
Version: 0.7.0
Followup-For: Bug #903292
Dear Maintainer,
instead of adding the dependency on "bc", its usage could also be
replaced with a portable shell substitution:
https://salsa.debian.org/blends-team/blends/merge_requests/1
Cheers,
Lars
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "sharness"
Package name: sharness
Version : 1.0.0-1
Upstream Author : Christian Couder
URL : https://github.com/chriscool/sharness
License : GPL-2 or later
Package: wnpp
Severity: wishlist
Owner: Lars Kruse
* Package name: sharness
Version : 1.0.0
Upstream Author : Christian Couder
* URL : https://github.com/chriscool/sharness
* License : GPL2+
Programming Lang: Shell
Description : Sharness is a portable
Hello Calum,
Am Sun, 24 Jun 2018 22:51:09 +0100
schrieb Calum Mackay :
> > The following workaround should clean up the situation for most
> > installations:
> >find /etc/fonts/conf.avail/ -type d -empty -delete
>
> interestingly, that finds one remaining entry for me, although I am no lon
Hi Calum,
thank you for reporting your state of the things so quickly!
Am Sat, 23 Jun 2018 23:45:40 +0100
schrieb Calum Mackay :
> > This is probably
> > https://bugs.debian.org/853848https://bugs.debian.org/853848, fixed by
> > upgrading/removing:
> > fonts-beng-extra
> > fonts-deva-extr
Hello Martin,
Am Wed, 25 Nov 2015 14:33:04 +1300
schrieb martin f krafft :
> Package: munin-plugins-extra
> Version: 2.0.25-2
> Severity: minor
> File: /usr/share/munin/plugins/apt
>
> I am seeing this on all hosts running the apt plugin:
>
> Use of uninitialized value $ENV{"MUNIN_PLUGSTATE"
Hi Uwe,
I assume, that this issue was caused by "munin_stats" ignoring that cgi-based
graph generation was configured?
In this case it was fixed in v2.0.27-1.
Or what do you think?
Cheers,
Lars
Hello,
Am Fri, 30 Sep 2016 14:55:26 +0200
schrieb Holger Levsen :
> from IRC:
>
> |
> https://tests.reproducible-builds.org/debian/rb-pkg/experimental/armhf/diffoscope-results/munin.html
> - fascinating. also how this cannot be seen on i386?!?
> < ntyni> | race between ./plugins/node.d.linux
Package: munin-plugins-core
Version: 2.0.37-2
Followup-For: Bug #675318
Hi,
the issue is fixed upstream and will be part of the upcoming releases
2.0.38 and 2.999.9.
Cheers,
Lars
Hi,
Am Sat, 14 Dec 2013 20:12:03 +0100
schrieb "Marc A. Donges" :
> munin’s XHTML output is malformed XML in several places.
All relevant occurrences should be fixed now in upstream (to be relased as
2.0.38).
Cheers,
Lars
Hi,
Am Tue, 28 Oct 2014 21:28:51 +0800
schrieb Paul Wise :
> [..]
> The fix appears to involve figuring out why munin does not use the
> freebsd plugins on kFreeBSD,
currently the "munin-plugins-core" package has "Architecture: all".
We could change this to "hurd-any linux-any kfreebsd-any".
Hi,
Am Sat, 23 Jun 2018 01:03:44 +0200
schrieb Lars Kruse :
> I just checked here, whether it would be sufficient to simply run the cron-job
> as "nobody" (instead of root). This works for me.
> This would be preferable (compared to the change above), or?
> Or maybe
Hi,
Am Wed, 24 May 2017 09:40:49 +
schrieb Holger Levsen :
> > Adding the following to /etc/munin/plugin-config.d/munin-node fixed it
> > for me:
> >
> > [apt_all]
> > user root
> > env.MUNIN_PLUGSTATE /var/lib/munin-node/plugin-state/nobody/
> >
> > I'm not sure if that's the correct fix, t
Package: munin-plugins-extra
Followup-For: Bug #767018
Hello,
munin support vd* device names since v2.0.25.
The wrong LVM major block device number is fixed upstream (to be released with
v2.0.38).
Cheers,
Lars
Package: munin-async
Followup-For: Bug #772277
Hi,
checkbashism seems to be wrong here:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843913
See the source of "sleep":
~# type sleep
sleep is hashed (/bin/sleep)
Let us wait, until the check in checkbashism is fixed.
Cheers,
Lars
Package: munin-plugins-core
Version: 2.0.37-2
Followup-For: Bug #901729
Hello Christian,
thank you for preparing the patch!
I just pushed a commit [1] fixing this issue (based on your patch) to
upstream. Thus it will be part of the release (2.0.38) of munin.
Cheers,
Lars
[1]
https://github.co
Source: munin
Followup-For: Bug #895868
Hello,
I took a look at the bugs reported for fontconfig [1]. I did not find a
description of this problem. Maybe someone could report it there?
Since munin is likely only affected indirectly by this problem, we
should probably solve it in fontconfig, in
Package: licensecheck
Followup-For: Bug #472199
Dear Maintainer,
currently the following methods for creating a DEP-5 compliant copyright
file:
debmake -c
cme check dpkg-copyright
licensecheck -r --merge-licenses --deb-machine .
Thus this wishlist bug can probably be closed.
Cheers,
Lars
Package: tracker.debian.org
Severity: normal
Dear Maintainer,
recently I sent a mail to , as this is
currently (by mistake) advertised as the contact address of the munin
package maintainers.
(this issue of the missing team "munin") is about to be fixed now)
My mail was silently discarded (see [
Package: unattended-upgrades
Followup-For: Bug #886415
Dear Maintainer,
I encounter the same issue.
Running "unattended-upgrades --debug --apt-debug" I see the following
reasoning for the non-upgrade:
Checking: linux-image-amd64 ([,
])
Installing linux-image-4.9.0-6-amd64 as Depends of l
Package: ripit
Version: 4.0.0~beta20140508-1
Severity: normal
Tags: patch
Dear Maintainer,
while trying to rip an album with a name containing curly braces ("{}"),
ripit stopped with an error:
Unescaped left brace in regex is illegal here in regex; marked by <--
HERE in m//foo { <-- HERE bar}.
1 - 100 of 184 matches
Mail list logo
