Bug#639358: Additional Information

The details of the bug as described on the mailing list are now available - please see http://www.shalla.de/mailman/private/squidguard/2011-August/002135.html The patch I submitted is available at http://www.shalla.de/mailman

Bug#639358: squidguard: Characters after a final % are ignored after rewriting

Package: squidguard Version: 1.4-2 Severity: important Tags: upstream As raised on the squidguard mailing list at http://www.shalla.de/mailman/private/squidguard/2011-August/002135.html (not all messages have appeared in the archive at time of writing). When using a rewrite rule in squidGuard, i

Bug#580484: munin-plugins-extra: With df plugin, Field name can be duplicated when working with long device names

Package: munin-plugins-extra Version: 1.2.6-10~lenny2 Severity: normal This is arguably a bug in the clean_fieldname function of Munin::Plugin.pm (part of munin-node) but would make things to bang in a rather big way (as explained below). On several of our systems, we create lvm partitions for ou

Bug#580483: munin-node: Perl module Munin::Plugin's clean_fieldname function can allow invalid fieldnames

Package: munin-node Version: 1.2.6-10~lenny2 Severity: normal clean_fieldname is a function in Munin::Plugin (provided by munin-node) which can be used to sanitize field names within data. The field name must: * Not start with an integer; and * Only contain characters in the range a-zA-Z0-9. Th

Bug#556459: php5-common: PHP Bug #50158 FILTER_VALIDATE_EMAIL fails with valid addresses containing = or ?

Package: php5-common Version: 5.2.6.dfsg.1-1+lenny3 Severity: normal Tags: patch As reported to bugs.php.net, the filter_var function, when used with the FILTER_VALIDATE_EMAIL filter, does not correctly parse e-mail addresses which contain either a ? or an =, both of which are valid according to t

Bug#526525: disk and network fail on Dell T610 under 64-bit kernel only

On Sat, May 30, 2009 at 10:36:21AM +0100, Andrew Robert Nicols wrote: > On Fri, May 29, 2009 at 12:01:56PM -0700, Tony Godshall wrote: > > retitle 526525 64-bit kernel failures on Nehelem CPUs such as Dell T610, > > R610 > > Possibly fixed by a BIOS upgrade. See report on t

Bug#526525: disk and network fail on Dell T610 under 64-bit kernel only

On Fri, May 29, 2009 at 12:01:56PM -0700, Tony Godshall wrote: > retitle 526525 64-bit kernel failures on Nehelem CPUs such as Dell T610, R610 Possibly fixed by a BIOS upgrade. See report on the PE mailing list at http://lists.us.dell.com/pipermail/linux-poweredge/2009-May/039328.html Will try on

Bug#526525: retitle 526525 disk and network fail on Dell T610 under 64-bit kernel only

On Tue, May 26, 2009 at 05:27:40PM -0700, Tony Godshall wrote: > retitle 526525 disk and network fail on Dell T610 under 64-bit kernel only Tony, This bug doesn't just affect disk and network and it doesn't just affect the T610. I'm seeing problems detecting the disk and network controllers and

Bug#526525: a problem with mptbase or bnx2 (was: Bug#526525: Kernel linux-image-2.6.26-2-amd64 does not see) root RAID device /dev/md0

On Fri, May 22, 2009 at 09:10:01AM -0700, Tony Godshall wrote: > On Fri, May 22, 2009 at 3:43 AM, Andrew Robert Nicols > wrote: > > For the record, I'm seeing exactly the same thing too here. I'm booting off > > a pendrive with the debian installer on it so the pe

Bug#526525: a problem with mptbase or bnx2 (was: Bug#526525: Kernel linux-image-2.6.26-2-amd64 does not see) root RAID device /dev/md0

On Wed, May 20, 2009 at 09:04:38AM -0700, Tony Godshall wrote: > Reboot with USB stick plugged in: now I get a long pause immediately > after "md: raid1 personality registered for level 1" > > I look in dmesg for a usb-storage device: nothing. I look for > /dev/sd[a-z]*: nothing > > So I can't m

Bug#529436: linux-image-2.6.26-2-vserver-686-bigmem: Only 3.2Gb of memory accessible out of 16gb in system

Package: linux-image-2.6.26-2-vserver-686-bigmem Version: 2.6.26-15lenny2 Severity: important System is a Dell R610 with 16GB of RAM but only the first 3.2GB is currently being detected. This is using a bigmem kernel so should expect to see all 16GB. Not quite sure where to start looking into th

Bug#528351: similar bug

I believe this may be the same bug experienced in bug #526525 which I'm also seeing on a Dell R610. If this helps, the R610 I'm seeing this on sees it's disk under Lenny running an i686 kernel, but I'm unable to either change to the amd64 kernel or complete the amd64 lenny installer as the disks a

Bug#526525: AMD64 kernel - mptbase

I'm having the same issue as being discussed in this thread with installation of a new Dell R610. i686 installation detects disks properly (output of lsmod attached). amd64 installation doesn't detect disks so I'm unable to install. Output seen in dmesg includes the line: mptbase: ioc0: Error - :

Bug#524968: apticron: Apticron mail subject ignores value of $SYSTEM instead using `/bin/hostname`

Package: apticron Version: 1.1.27 Severity: normal Although /etc/apticron/apticron.conf allows setting of the SYSTEM variable to override the hostname used in apticron mails, it does not make use of this variable in the mail subject. Further more, it doesn't even use the FQDN of the server which

Bug#512759: request-tracker3.8: Database schema - possible missing index for Postgres on Groups table

Package: request-tracker3.8 Version: 3.8.2-1~experimental1 Severity: normal Tags: patch This is a similar bug report to #512653. Tested on an instance with 50,000 tickets. Box has 4x3.2Ghz Xeon cores and a reasonable amount of memory. Although there are two existing indexes for the Groups table

Bug#512653: request-tracker3.8: Database schema missing indexes (Postgres)

Package: request-tracker3.8 Version: 3.8.2-1~experimental1 Severity: important Tags: patch It looks like the schema files for Postgres are missing at least one INDEXES. This is also missing in the upstream schema.Pg files on bestpractical's website. I've given a brief description and postgres ex

Bug#512646: request-tracker3.8: Missing dependency: libipc-run-safehandles-perl

Package: request-tracker3.8 Version: 3.8.2-1~experimental1 Severity: important For the ticket relationship graphs (From a Ticket, select Graph in the Links section), an error is experienced during compilation. Backtrace suggests that compliation failed at line 78 of /usr/share/request-tracker3.8/