Package: python-audit
Version: 1:2.8.4-2
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
The following operations fail due to a SWIG-related type error:
```
% sudo python
Python 2.7.16 (default, Apr 6 2019, 01:42:57)
[GCC 8.3.0] on linux2
Type "help",
Package: bareos
Version: 14.2.1+20141017gitc6c5b56-4
Severity: critical
Justification: causes serious data loss
In March 2015 bareos fixed a bug which caused silent corruption of
backups when the following conditions are met:
* backups are written to disk (tape backups are not affected)
*
amounts of
traffic moving through that queue.
This has been verified with the current head
(e4fc7e2625a29c99a77f03584da82e75f2930534) from iproute2
(http://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/)
all the best,
Michael Renner
-- Package-specific info:
** Version:
Linux
Package: wget
Version: 1.13.4-3+deb7u1
Severity: important
Hi!
Doing a wget from raw.githubusercontent.com will cause a TLS warning:
robe@tokamak ~/tmp % openssl x509 -in (openssl s_client -connect
raw.githubusercontent.com:443 -prexit 2/dev/null) -text | grep -B 1
githubusercontent
On Nov 21, 2012, at 11:40 , intrigeri intrig...@debian.org wrote:
Kenyon Ralph wrote (23 Jun 2012 20:17:28 GMT) :
When you specify a target via hostname which has both a v6 and v4
address munin tries to connect to the v6 address first and if this
fails bails out completely. This skips data
On Jul 10, 2012, at 17:25 , Christoph Lechleitner wrote:
Am 2012-07-10 16:58, schrieb Benjamin Henrion:
I am affected by that bug, as updatedb crashes inside a VZ:
Can someone fix that?
Just to be sure, you did notice we from ITEG are providing binary
packages for now?
Thanks - they
On Jun 28, 2012, at 7:18 , Ola Lundqvist wrote:
I do not know if there is much point in that. We can do that of course
but as we soon have a new release without those kernels I do not
really see the benefit of doing so.
As long as the Debian Squeeze kernels are actively maintained serious
Package: munin
Version: 2.0.0-1
Severity: important
Tags: ipv6 upstream
When you specify a target via hostname which has both a v6 and v4
address munin tries to connect to the v6 address first and if this fails
bails out completely. This skips data collection for this host,
resulting in lost data
Package: munin
Version: 2.0.0-1
Severity: normal
Tags: upstream
There's a problem with the df plugin on Wheezy OpenVZ guests though it's
probably not limited to those.
OpenVZ on Squeeze exposes some virtual filesystems, including the
quota-enhanced root filesystem and tmpfs, as /dev/simfs to
Package: munin-node
Version: 2.0.0-1
Followup-For: Bug #675593
severity 675593 important
thanks
The current situation means that no plugin with a permission override in
the plugin configuration can use a statefile which at least makes
diskstats unusable and breaks old installations.
all the
Package: munin-node
Version: 2.0.0-1
Severity: normal
Tags: upstream ipv6
Hey Holger,
the default munin-node configuration doesn't allow localhost IPv6
connections.
Adding a
allow ^::1$
fixes this.
This would also be a good opportunity to get rid of the travesty that is
the regex netblock
Package: unattended-upgrades
Version: 0.76.3
Severity: normal
Hi!
when running wheezy in a container on a squeeze OpenVZ host I'm getting these
errors on each unattended-upgrade run:
ionice: ioprio_set failed: Operation not permitted
Here with verbose output:
---
/etc/cron.daily/apt:
On Feb 24, 2012, at 21:42 , Bernd Zeimetz wrote:
I just stumbled upon
https://trac.id.ethz.ch/projects/nagios_plugins/wiki/check_ssl_cert, which
does exactly what you are searching. Maybe it's a candidate for
nagios-plugins-contrib?
Sounds like a good cancdidate.
Please send patches or
On Feb 23, 2012, at 13:55 , Jan Wagner wrote:
that was not my point. I asked, _where_ do you expect such an information.
And
while we are at it, maybe you can tell me, _what_ do you expect at this
place.
Feel free to provide patches and/or just the text.
Sorry, misinterpreted you there
On Feb 19, 2012, at 12:06 , Jan Wagner wrote:
Notes:
This plugin will attempt to open an HTTP connection with the host.
[...]
This plugin can also check whether an SSL enabled web server is able to
serve content (optionally within a specified time) or whether the X509
certificate is still
On Feb 19, 2012, at 13:05 , Jan Wagner wrote:
Explicitly pointing out that this plugin will _ONLY_ verify the
expiry date of the certificate should prevent surprises for other
people in the future.
/usr/lib/nagios/plugins/check_http --help doesn't count as
documentation? Where do you
Package: nagios-plugins-basic
Version: 1.4.15-3squeeze1
Severity: normal
Tags: upstream
Nagios' check_http plugin does no verification whatsoever on the SSL
certificate presented by the server next to checking the expiry time.
This is highly counter-intuitive and makes the plugin pretty much
Package: linux-image-2.6.32-5-openvz-amd64
Version: 2.6.32-35
Severity: normal
When using OpenVZ the iptables raw table gets leaked to containers. This is
problematic when using OpenVZs checkpointing feature since every restore of a
container invokes iptables-restore in the container with the
Package: libsysfs2
Version: 2.1.0+repack-1
Severity: minor
Tags: patch upstream
LSI bundled a modified libsysfs library with their recent versions of
their CLI raid controller utility where they apparently patched a bug
in cdev_name_equal.
Upstream for sysfsutils _SEEMS_ very dead, reporting
Package: vzctl
Severity: important
Tags: upstream
ndsend is the ipv6 equivalent to arpsend to update the neighbour discovery
table in a router. This is necessary when MAC-addresses change (e.g. a
guest being migrated from one OpenVZ hardware node to a different
one).
ndsend in it's current
Package: shorewall6
Severity: normal
The shorewall6-rules manpage lists DNAT as a valid action and even
has DNAT examples with IPv6 addresses albeit ip6tables doesn't offer
any DNAT support.
-- System Information:
Debian Release: 6.0.1
APT prefers stable-updates
APT policy: (500,
Package: unattended-upgrades
Version: 0.42debian1
Severity: important
unattended-upgrades produces warnings on every run, resulting in an superfluous
email every day. This makes the package unfit for it's usecase.
Some of the content:
/usr/bin/unattended-upgrade:385: DeprecationWarning:
Package: red5-server
Severity: wishlist
Please update the red5 package to 0.9.1, it's stable since late february and
it'd be nice if this version was in squeeze compared to the current svn
snapshot.
Thanks,
Michael
-- System Information:
Debian Release: 5.0.4
APT prefers stable
APT
Package: e2fsprogs
Version: 1.41.3-1
Severity: normal
Doing an online resize of an ext3 filesystem causes an unexpected filesystem
check at the next reboot.
Please either
*) fix this in e2fsck
*) reassign this bug to the kernel
*) or at least document/warn the user about the behavior when
Package: munin-plugins-extra
Severity: wishlist
Per previous discussion with Holger.
Current version can always be found at
https://workbench.amd.co.at/trac/munin-plugins .
-- System Information:
Debian Release: 5.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64
Package: php-apc
Followup-For: Bug #494273
As there is no other way to actually see if APC is doing anything, the presence
of a sample apc.php is vital. Pulling the file from upstream is just extra
hassle for the user.
best regards,
Michael
--
To UNSUBSCRIBE, email to
On Tuesday 09 December 2008 22:56, Michael Renner wrote:
Ahhh, sorry. I meant that the munin package (cronjob-powered data
collection and graphing) stopped working after removing munin-node. If
this is unexpected I'll follow up with more information.
Thats unexpected, please follow up
Holger Levsen wrote:
Hi,
On Monday 08 December 2008 02:37, Michael Renner wrote:
Installing munin pulls munin-node per recommend, purging munin-node after
installation leaves a non-functioning munin package. This was verified with
1.2.6-8.
and where is the bug?
I always thought
Package: munin
Severity: normal
Installing munin pulls munin-node per recommend, purging munin-node after
installation leaves a non-functioning munin package. This was verified with
1.2.6-8.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Robert Lemmen wrote:
hi michael,
could you explain how to create such a partition? i have created a small
loopback with a GPT partition, but i don't see that behaviour...
Not using a loopback device but a plain file:
# create a sparse file, ~200GB in this case
dd if=/dev/zero of=fakedisk
Package: linux-image-2.6.26-1-openvz-amd64
Version: 2.6.26-10
Followup-For: Bug #500645
Apparently this has been fixed in upstream already [1], could you please
integrate the patch?
best regards,
Michael
[1] http://bugzilla.openvz.org/show_bug.cgi?id=1034#c6
-- System Information:
Package: mercurial
Version: 1.0.1-5.1
Severity: normal
I tried viewing a moved/renamed with hgwebdir.cgi which results in an endless
loop of the serving python process (100% CPU utilization). Trying the same with
debian etch + mercurial from BPO (1.0.1-5.1~bpo40+1) works fine.
The repository
After experimenting a bit the highlighter turned out to be the problem.
This problem is already fixed in 1.0.2, applying the patch found at
http://nopaste.narf.at/f2685f85d fixed the problem for me.
best regards,
Michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
Package: gnu-fdisk
Version: 1.0-3+b1
Severity: grave
Justification: causes non-serious data loss
gnu-fdisk wipes out the Code Area in the MBR of a given device when modifying a
GPT partition. If this happens to be the boot device, this can cause serious
trouble.
The behaviour can be easily
Package: grub2
Version: 1.96+20080724-11
Severity: important
grub2 fails to detect free space for embedding it's core.img when necessary
(e.g. lvm-root) when being confronted with a GPT disklabel.
With this layout (output from parted -l)
Model: Areca raid10-PV (scsi)
Disk /dev/sdc: 200GB
Package: gnu-fdisk
Version: 1.0-3+b1
Severity: normal
gnu fdisk should emit a warning when an written partition table couldn't be
refreshed by the kernel due to active partitions on the given device.
The warning of it's predecessor looks like this:
---
Command (m for help): w
The partition
Otavio Salvador wrote:
Michael, can you confirm if GRUB2 works for you?
Sorry for my late reply. GRUB2 didn't work for me; I've filed a bug
against the GRUB2 package with the specifics [1].
best regards,
Michael
[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=409073
--
To
Package: grub2
Version: 1.95-2
Severity: important
Tags: upstream
GRUB 2 (1.95) refused to get installed on a GPT-partitioned server.
The layout is as follows:
parted:
Disk /dev/sda: 3000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End SizeFile
easily feel free to close this bug and I'll reopen
a new one in GRUB2 if this should be a persisting problem.
best regards,
Michael Renner
Robert Millan wrote:
On Sat, Jan 27, 2007 at 03:55:34PM +0100, Michael Renner wrote:
How hard is it to do a GPT install with the standard installer? I haven't
tried, but I guess you could use the CD (with 'rescue' command) for your
first boot, and then install GRUB 2 from there. Did you
with a GPT-Partition instead of
silently not doing The Right Thing (tm).
Both fdisk and cfdisk seem to overflow a variable, with the result that on a
~3 TB blockdevice only a ~780 GiB partition gets created when trying to
allocate all space.
best regards,
Michael Renner
[1] http://support.microsoft.com
Package: nagios-plugins-standard
Version: 1.4.5-1
Severity: normal
The command definition for check_ldaps is missing from ldap.cfg, please add it.
Copying the definition for check_ldap worked fine for me...
-- System Information:
Debian Release: 4.0
APT prefers testing
APT policy: (500,
be an option in the future but unfortunately it's not usable [2] in
it's current state.
[1] http://lists.gnu.org/archive/html/bug-grub/2006-07/msg00037.html
[2] http://lists.gnu.org/archive/html/grub-devel/2007-01/msg00030.html
best regards,
Michael Renner
-- System Information:
Debian Release: 4.0
APT
Hi Julien,
I discussed the timestamp idea with Andi Kleen, and, basically, it's
of no use because the precision of the timestamp would suck.
The kernel collects MCE data every 5 minutes by default, then mcelog
runs every 5 minutes, collecting the data collected by the kernel.
[..]
Andi
Julien BLACHE wrote:
Michael Renner [EMAIL PROTECTED] wrote:
Uhm, if I've got a logfile full of MCE entries after (e.g.) returning
from a weeks vacation a timestamp with a granularity of 5 minutes is
That'd be 10 minutes, not 5, and it can be even more than that under
some circumstances
Package: mcelog
Version: 0.7-1
Severity: wishlist
It would be nice if mcelog could log timestamps in its logfile. A quick
hack for doing that would be:
foo=`/usr/sbin/mcelog --ignorenodev --filter`; if [[ $foo ]]; then echo
-e `date`\n$foo /var/log/mcelog; fi
best regards,
Michael
--
Package: lighttpd
Version: 1.4.11-7
Severity: minor
Please use sane default values for the logrotate config; rotating daily
with keeping 7 logfiles certainly isn't for a webserver.
I'd opt for something along the lines of weekly rotating and keeping at
least 3 months worth of accesslogs.
--
Package: libstring-random-perl
Version: 0.198-4
Severity: wishlist
Please upgrade String::Random to the latest version.
See http://search.cpan.org/src/STEVE/String-Random-0.21/Changes for
changes.
best regards,
Michael Renner
-- System Information:
Debian Release: testing/unstable
APT
Package: libdata-validate-domain-perl
Version: 0.01-2
Severity: wishlist
Please upgrade this package to the latest version. See
http://search.cpan.org/src/NEELY/Data-Validate-Domain-0.03/Changes for
changes.
best regards,
Michael Renner
-- System Information:
Debian Release: testing/unstable
Package: pdns-recursor
Version: 3.1.2-1
Severity: important
Tags: patch
powerdns-recursor 3.1.2 crashes in it's current form at least on amd64
(other 64bit platforms might be affected as well) on certain queries. An
example host which should trigger this problem (as mentioned by Bert Hubert) is
Package: rsync
Version: 2.6.6-1
Severity: wishlist
rsync 2.6.7 was released on the 11th of march with quite a few interesting
bugfixes and improvements, could you upload the latest version when you've got
time?
best regards,
Michael
-- System Information:
Debian Release: testing/unstable
Package: ipac-ng
Version: 1.31-1
Followup-For: Bug #315351
iptables versions = 1.3.1 will cause current ipac-ng builds to fail, see
http://sourceforge.net/tracker/index.php?func=detailaid=1193721group_id=40604atid=428516
for patches regarding this problem.
-- System Information:
Debian
Daniel Baumann wrote:
Michael Renner wrote:
iptables versions = 1.3.1 will cause current ipac-ng builds to fail, see
http://sourceforge.net/tracker/index.php?func=detailaid=1193721group_id=40604atid=428516
for patches regarding this problem.
I know, problem is if I apply the patch
Package: lighttpd
Version: 1.4.8-2
Severity: minor
The current output of the init script misleads the user into thinking
that lighttpd actually parsed the (changed) configuration whereas it
actually only cycled the logfiles. The output of the init script should
be changed to reflect the truth
Package: pdns
Version: 2.9.19-1
Severity: important
Tags: patch
2.9.19 doesn't allow records with a slash in the name, which are used in
classless ptr delegation. See problem description and patch at
http://wiki.powerdns.com/projects/trac/ticket/48 . I suggest you apply
the patch and roll a new
and bugfixes - if there are
no new perl versions or bugs, why release a new version?
Please don't let libcdb-file-perl become yet another perl-module that
has to be installed via cpan because it's not packaged (anymore!).
--
thanks and best regards,
Michael Renner - Network services
Package: libcdb-file-perl
Severity: important
I wasn't able to reproduce this error in a standalone perl script, but
running a script which uses CDB_File in mod_perl gave me Protocol
errors all the time (this was on amd64 though). Installing the most recent
version (as suggested
in #192050) via
Ivan Kohler wrote:
Hi Michael,
Upgrading libdbd-pg-perl does not break 7.x compatibility in all cases.
This is a bug in libdbd-perl-perl.
Sorry, I was a bit quick-tempered when I sent that. I'm seeing random
infinite loops accompanied with (null) messages in errorlog when using
Package: nagios-plugins
Version: 1.4-6
Severity: normal
Tags: upstream
check_ntp fails when the offset is 0. This might have worked fine back
then, but nowadays with fast servers you can actually get an offset of
0 when doing ntp checks on localhost.
morework:/#
Package: libdbd-pg-perl
Version: 1.32-2
Followup-For: Bug #315708
When upgrading libdbd-pg-perl silently breaks 7.x compatibility, this is
plain wrong. There is more than one setup where the server is remote and
you don't have the slightest chance to know or even depend on its version. If
7.x
60 matches
Mail list logo
