proxies only taking one member

[guy@…]

created a proxies.xml file when multiple entries for some calendars... ie delegated out to several people..eg:

	<record>
		<!-- testaccount -->
		<guid>ed2a576f-e439-4342-8c3c-6e48dbde6752</guid>
		<proxies>
			<member>9dfed9e0-fb0a-4ba3-a80f-be033cf59c2d</member>
			<member>db103f15-ecd6-4f65-8c3a-973c2c79d8fa</member>
			<member>2036a3a5-3b32-4710-9eeb-27caddf29c2f</member>
			<member>92f61292-e3f2-477b-bcd2-7a80f16f9a8d</member>
		</proxies>
	</record>

However only one of these users can see the calendar.

Looking in the proxies.sqlite database I see that only one entry has been made.

# sqlite3 proxies.sqlite 
SQLite version 3.3.6
Enter ".help" for instructions
sqlite> .dump
BEGIN TRANSACTION;
CREATE TABLE CALDAV (KEY text unique, VALUE text unique);
INSERT INTO "CALDAV" VALUES('SCHEMA_VERSION', '4');
INSERT INTO "CALDAV" VALUES('TYPE', 'ProxyDB');
CREATE TABLE GROUPS (GROUPNAME text, MEMBER text);
INSERT INTO "GROUPS" VALUES('ed2a576f-e439-4342-8c3c-6e48dbde6752#calendar-proxy-write', 'db103f15-ecd6-4f65-8c3a-973c2c79d8fa');
CREATE INDEX GROUPNAMES on GROUPS (GROUPNAME);
CREATE INDEX MEMBERS on GROUPS (MEMBER);
COMMIT;
sqlite> 

It also seems a little random as to which entry is taken... End users are still able to delegate out their calendars manually in ical.app without issue.

[sagen@…]

Should be fixed in trunk rev 5312

[guy@…]

confirmed it's fixed in 5312.

Thanks