http://bugzilla.lysator.liu.se/show_bug.cgi?id=169
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
Target Milestone|Future |2.1.3
------- Additional Comments From ceder(a)lysator.liu.se 2006-09-29 22:10 -------
Fixed in r5593.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=192
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From ceder(a)lysator.liu.se 2006-09-28 22:28 -------
Fixed in r5592, by introducing several new error codes and doing a complete
overhaul of the aux-related error codes. From the ChangeLog entry:
Renamed the error code illegal-aux-item to illegal-aux-item-tag.
Added error code 62=aux-exists, 63=aux-bad-object,
64=illegal-aux-data, 65=aux-create-only, 66=aux-modify-only,
67=aux-server-only, 68=aux-data-exists and 69=aux-no-such-text.
Return proper error codes. (Bug 192).
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=1615
------- Additional Comments From ceder(a)lysator.liu.se 2006-09-28 22:09 -------
This also happens even if you don't attempt to remove an aux-item. This is
also demonstrated by 21.exp.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=1615
Summary: modify-conf-info: wrong aux-item flagged as duplicate
Product: lyskomd
Version: 2.1.2
Platform: All
OS/Version: All
Status: NEW
Severity: trivial
Priority: P2
Component: server
AssignedTo: ceder(a)lysator.liu.se
ReportedBy: ceder(a)lysator.liu.se
QAContact: lyskomd-qa(a)lists.lysator.liu.se
When attempting to remove an faq-text, and adding back two instances of
the same faq-text aux-item, all in a single modify-conf-info call, the
wrong aux-item is reported as the duplicate. Aux-item 1 should be the
duplicate, but aux-item 0 is reported.
src/server/testsuite/lyskomd.0/21.exp triggers this bug.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=1614
Summary: modify-conf-info: removing and adding back the same faq-
text aux-item in a single operation fails
Product: lyskomd
Version: 2.1.2
Platform: All
OS/Version: All
Status: NEW
Severity: trivial
Priority: P2
Component: server
AssignedTo: ceder(a)lysator.liu.se
ReportedBy: ceder(a)lysator.liu.se
QAContact: lyskomd-qa(a)lists.lysator.liu.se
Removing and adding back the same faq-text aux-item in a single modify-conf-info
call fails with error code 68=aux-data-exists. It should succeed.
src/server/testsuite/lyskomd.0/21.exp triggers this bug.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=217
ceder(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
------- Additional Comments From ceder(a)lysator.liu.se 2006-09-13 21:38 -------
...and those test cases are enough to close this bug. I forgot to check
the proper checkbox when I wrote the previous message.
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://bugzilla.lysator.liu.se/show_bug.cgi?id=327
------- Additional Comments From ceder(a)lysator.liu.se 2006-09-03 17:11 -------
The "unique" attribute was renamed to "one-per-person" in r5590, in preparation
for adding a new "unique" attribute that really means "unique".
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.