From: rmccabe@sourceware.org <rmccabe@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] conga conga.spec.in.in
Date: 10 Apr 2007 19:51:26 -0000 [thread overview]
Message-ID: <20070410195126.16691.qmail@sourceware.org> (raw)
CVSROOT: /cvs/cluster
Module name: conga
Branch: RHEL5
Changes by: rmccabe at sourceware.org 2007-04-10 20:51:26
Modified files:
. : conga.spec.in.in
Log message:
changelog update
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/conga.spec.in.in.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.45.2.30&r2=1.45.2.31
--- conga/conga.spec.in.in 2007/03/30 15:12:52 1.45.2.30
+++ conga/conga.spec.in.in 2007/04/10 19:51:25 1.45.2.31
@@ -294,8 +294,12 @@
- Fixed bz230457 (kmod-gfs-xen not installed with Conga install)
- Fixed bz230461 ('enable shared storage' option cleared whenever there is a configuration error)
- Fixed bz230469 (Must manually edit cluster.conf on the dom0 cluster to add "<fence_xvmd/>")
-- Resolves: bz229027, bz230447, bz230452, bz230454, bz230457, bz230461
-- Resolves: bz230469, bz228637, bz233326, bz225747
+- Fixed bz225206 (Cluster cannot be deleted (from 'Manage Systems') - but no error results)
+- Fixed bz225164 (Conga allows creation/rename of clusters with name greater than 15 characters)
+- Fixed bz227758 (Entering bad password when creating a new cluster = UnboundLocalError: local variable 'e' referenced before assignment)
+- Resolves: bz229027, bz230447, bz230452, bz230454, bz230457,
+- Resolves: bz230469, bz228637, bz233326, bz225747, bz225206,
+- Resolves: bz230461, bz225164, bz227758
* Tue Jan 23 2007 Stanko Kupcevic <kupcevic@redhat.com> 0.8-30
- Fixed bz212445 (release blocker: prevent management page access)
next reply other threads:[~2007-04-10 19:51 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 19:51 rmccabe [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-09-23 17:34 [Cluster-devel] conga conga.spec.in.in rmccabe
2008-06-13 18:39 rmccabe
2008-06-13 18:38 rmccabe
2008-05-16 17:11 rmccabe
2008-05-16 17:10 rmccabe
2008-05-16 17:08 rmccabe
2008-04-18 3:28 rmccabe
2008-03-19 14:59 rmccabe
2008-01-23 5:20 rmccabe
2008-01-23 4:57 rmccabe
2008-01-22 15:20 rmccabe
2007-10-09 20:57 rmccabe
2007-08-29 1:02 rmccabe
2007-08-27 18:42 rmccabe
2007-08-11 4:23 rmccabe
2007-08-11 4:22 rmccabe
2007-08-09 22:37 rmccabe
2007-07-16 22:18 rmccabe
2007-06-29 15:58 rmccabe
2007-06-26 21:41 rmccabe
2007-06-18 19:06 rmccabe
2007-04-30 18:34 rmccabe
2007-03-30 14:48 kupcevic
2007-03-27 2:20 rmccabe
2007-03-27 2:17 rmccabe
2007-03-20 17:39 rmccabe
2007-03-20 17:38 rmccabe
2007-03-20 17:26 rmccabe
2007-03-20 17:01 kupcevic
2007-03-20 16:38 kupcevic
2007-03-01 1:02 rmccabe
2007-02-16 15:55 rmccabe
2007-02-16 15:54 rmccabe
2007-01-17 16:38 kupcevic
2007-01-10 23:52 rmccabe
2007-01-10 23:51 rmccabe
2006-12-22 18:06 rmccabe
2006-12-22 18:04 rmccabe
2006-12-22 18:01 rmccabe
2006-12-22 18:00 rmccabe
2006-12-14 18:28 rmccabe
2006-12-13 23:58 rmccabe
2006-12-12 13:58 kupcevic
2006-12-12 5:21 rmccabe
2006-12-11 23:52 rmccabe
2006-12-06 23:03 rmccabe
2006-11-16 18:23 rmccabe
2006-11-15 18:07 rmccabe
2006-08-21 23:22 kupcevic
2006-08-18 20:10 kupcevic
2006-08-18 13:59 kupcevic
2006-07-25 21:00 kupcevic
2006-07-17 22:57 kupcevic
2006-07-05 22:08 kupcevic
2006-06-30 22:12 kupcevic
2006-06-28 21:42 kupcevic
2006-06-27 21:46 kupcevic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070410195126.16691.qmail@sourceware.org \
--to=rmccabe@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.