Package: drupal6
Version: 6.18-1squeeze1
Severity: important
This is a regression in the drupal6 6.18-1squeeze1 package from
squeeze/updates.
The issue is not present in stock squeeze.
Line 656 in /usr/share/drupal6/includes/common.inc contains a call to
filter_xss:
$entry =
-off-by: Florian Haas florian.h...@linbit.com
---
debian/fop.sh |8 ++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/debian/fop.sh b/debian/fop.sh
index 6130d45..f5a6f06 100644
--- a/debian/fop.sh
+++ b/debian/fop.sh
@@ -15,7 +15,11 @@
# in your fop configuration file
On 2011-07-11 15:42, Gabriel Corona wrote:
Hello,
Shouldn't this be fixed in commons-logging ?
Removing the classpath entry from MANIFEST-MF
(06_classpath_manifest.patch in commons-logging)
should fix the problem in applications.
Individual applications might want to add log4j in their
Martin,
I am sure Lars would love a patch implementing this.
drbd-...@lists.linbit.com is the preferred mailing list for DRBD patches.
Florian
signature.asc
Description: OpenPGP digital signature
On 2011-02-16 13:53, Tim Stoop wrote:
Package: drbd8-utils
Version: 2:8.3.7-2.1
Severity: normal
Hi,
We're experiencing some trouble with the drbd init script. Specifically the
line
that starts $DRBDADM wait-con-int. If the peer is not available, this shows
the
dialog explaining
Package: pacemaker
Version: 1.0.10-5
Severity: normal
Pacemaker builds its man pages conditional on the availability of
help2man. The debian/control file is missing this package in the
Build-Depends list. Thus, the Debian package does not build nor install
any man pages.
-- System
This is not a bug, it's the intended behavior.
The advised 60 is the minimum timeout that the STONITH agent author
has suggested to use for this STONITH resource type. These suggested
minimum timeouts differ widely across agents.
The default timeout 20 is the default-action-timeout cluster
On 2011-01-04 05:06, Simon Horman wrote:
On Mon, Jan 03, 2011 at 12:50:18PM +0100, Florian Haas wrote:
The issue you are highlighting isn't specific to the ocf:heartbeat:mysql
RA. There are several resource agents where the upstream default does
not match the Debian default.
This means we
The issue you are highlighting isn't specific to the ocf:heartbeat:mysql
RA. There are several resource agents where the upstream default does
not match the Debian default.
This means we should either fix this for _all_ resource agents that ship
in the cluster-agents package, or leave it to users
Just to put this into perspective -- this issue certainly does not
break unrelated software; what it breaks is functionality
fundamentally intrinsic to Pacemaker.
I can also happily report that I've been using 1.0.9 with both clones
and resource groups in production for months, without running
Severity: critical
This results in an unbootable system for people putting /boot on a
separate partition. As such it fulfills the makes the whole system
break criterion for critical bugs.
signature.asc
Description: OpenPGP digital signature
Package: nfs-kernel-server
Version: 1:1.2.2-4
Severity: wishlist
The package has no facility to change the NFSv4 lease time (grace period)
from its upstream default of 90 seconds. Suggest to add an entry in the
defaults file to be able to change this.
-- System Information:
Debian Release:
Tags: patch
Florian Haas (1):
Make NFSv4 lease time configurable
debian/nfs-kernel-server.default |3 +++
debian/nfs-kernel-server.init|5 +
2 files changed, 8 insertions(+), 0 deletions(-)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
Add a new parameter, NFSV4LEASETIME to the defaults file. In the
init script, echo this value into /proc/fs/nfsd/nfsv4leasetime
immediately after nfsd is mounted.
Rationale:
When an NFSv4 client has no chance to give up a lease (for example,
when the IP address that it connects through simply
On 2010-10-25 13:09, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
Rather than discuss the severity of this bug, it would be easier if you
just noticed that it's
a) duplicate of 601084
b) fixed in -7 upload
It would be tremendously helpful if the relevant bugs were merged.
Florian
ConfigureMe is no longer used in the Debian build process, as per the
debian/rules in http://hg.debian.org/hg/debian-ha/heartbeat/. So how does this
apply to 3.0.3?
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
tags: fixed-upstream
I've just trivially merged upstream 1.0.9.1 into the sid branch in my
local checkout, run a test build, and deployed to a cluster. Merge,
build, and deploy works flawlessly.
Since squeeze is now on python 2.6, pacemaker will no longer support
being installed alongside
This bug has been fixed in the upstream 8.3.8 release.
signature.asc
Description: OpenPGP digital signature
Package: heartbeat
Version: 1:3.0.3-2
Severity: important
Heartbeat 3.0.3 requires Pacemaker, which provides cluster resource management
functionality
which was part of Heartbeat before the package split. Thus it is possible for a
user to do a direct
upgrade from Heartbeat 2.1.3 (lenny) to
Just a quick comment here: this issue is only relevant to setups using
the heartbeat drbddisk resource agent, which is deprecated. Such
setups should be converted to Pacemaker and the ocf:linbit:drbd
master/slave resource agent.
Which shouldn't keep us from fixing the insserv headers, of course.
This issue is being addressed upstream and will be fixed in the upcoming
DRBD 8.3.8 release. No need to carry any patch in Debian, just rebuild
when 8.3.8 is out.
Cheers,
Florian
signature.asc
Description: OpenPGP digital signature
Package: drizzle-server
Version: 2010.03.1347-1
Severity: important
The init script packaged with drizzle-server expects the directory
/var/log/drizzle to exist and be owned by drizzle:drizzle. That
directory isn't created on package install, making it impossible to
immediately start the drizzle
Package: drizzle-server
Version: 2010.03.1347-1
Severity: important
The init script packaged with drizzle-server expects the directory
/var/log/drizzle to exist and be owned by drizzle:drizzle. That
directory isn't created on package install, making it impossible to
immediately start the
Package: drizzle-server
Version: 2010.03.1347-1
Severity: important
The /etc/init.d/drizzle-server init script prematurely returns failure on stop,
when the drizzled process does not shut down quickly enough. See example
below:
r...@debian-sid:~# /etc/init.d/drizzle-server stop
Stopping
Package: fortunes-de
Version: 0.20-1
fortunes-de seems to install the fortunes into a directory where the
fortunes-programm cannot find them.
Way to reproduce:
On a system without any fortunes, install the package fortunes-de.
Satisfy the dependency fortune-mod
Now run fortune
Output is as
I can confirm this error.
My setup is courrier as imap-server. Having over 16000 Messages in the
Inbox (I'm importing emails from an older account by using fetchmail)
results in an emty site.
Greetings,
Florian Haas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe
26 matches
Mail list logo
