cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: rmccabe@sourceware.org <rmccabe@sourceware.org>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] conga conga.spec.in.in
Date: 16 May 2008 17:08:30 -0000	[thread overview]
Message-ID: <20080516170830.16284.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/cluster
Module name:	conga
Branch: 	RHEL5
Changes by:	rmccabe at sourceware.org	2008-05-16 17:08:29

Modified files:
	.              : conga.spec.in.in 

Log message:
	Fix bz446907

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/conga/conga.spec.in.in.diff?cvsroot=cluster&only_with_tag=RHEL5&r1=1.45.2.87&r2=1.45.2.88

--- conga/conga.spec.in.in	2008/05/12 17:37:38	1.45.2.87
+++ conga/conga.spec.in.in	2008/05/16 17:08:28	1.45.2.88
@@ -104,6 +104,7 @@
 
 %files -n luci
 %verify(not size md5 mtime) /var/lib/luci/var/Data.fs
+%verify(not size md5 mtime) /var/lib/luci/.default_password_has_been_reset
 %defattr(-,root,root)
 %config(noreplace)		%{_sysconfdir}/sysconfig/luci
 				%{_sysconfdir}/rc.d/init.d/luci
@@ -295,6 +296,7 @@
 - Fix bz444938 (conga fails to create proper cluster.conf entries for gfs2 filesystem type)
 - Fix bz444210 (Adding multiple fence devices at the same time causes duplicate entries)
 - Fix bz444381 (conga writes 'exportpath' instead of 'export' attribute for netfs)
+- Fix bz446907 (rpm -V luci fails)
 
 * Fri Apr 18 2008 Ryan McCabe <rmccabe@redhat.com> 0.12.0-8
 - Fix bz441580 (conga should install 'sg3_utils' and start service 'scsi_reserve' when scsi fencing is used)



             reply	other threads:[~2008-05-16 17:08 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-16 17:08 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-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-04-10 19:51 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=20080516170830.16284.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).