http://bugzilla.lysator.liu.se/show_bug.cgi?id=333
byers(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
BugsThisDependsOn| |199
------- Additional Comments From byers(a)lysator.liu.se 2004-05-27 17:49 -------
Making this dependent on bug 199 (perhaps it should be a duplicate).
------- 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=313
------- Additional Comments From byers(a)lysator.liu.se 2004-05-27 17:32 -------
My working copy of lyskomd.texi now reads:
@item author-only
Boolean, default false. When true, restricts creation of items with
this tag to specific users. Items with this tag may be attached to
texts only by the author and supervisors of the author. Items with
this tag may be attached to conferences only by supervisors of the
conference (for conferences with the letterbox flag set, the person
with the same number as the conference may also attach items with this
tag). This flag has no effect on items being attached to the server.
@item supervisor-only
Boolean, default false. When true, restricts creation of items with
this tag to specific users. Items with this tag may be attached to
texts only by supervisors of the author (which may include the
author). Items with this tag may be attached to conferences (with or
without the letterbox flag) only by supervisors of the conference.
This flag has no effect on items being attached to the server.
Good enough?
I have looked over the implementation, and it appears to be correct, contraty to
a comment in lyskomd.texi (which, btw, I think I wrote).
------- 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=328
byers(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
OtherBugsDependingO| |580
nThis| |
------- 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=580
byers(a)lysator.liu.se changed:
What |Removed |Added
----------------------------------------------------------------------------
BugsThisDependsOn| |328
------- Additional Comments From byers(a)lysator.liu.se 2004-05-27 17:05 -------
In my working copy, the description of the aux-item-permission error code for
all three calls now reads:
No permission to delete one or more of the items in @rarg{delete}, or
@rarg{delete} indicates a non-existent aux-item, or not enough permissions to
add one or more of the items in @rarg{add}.
Good enough?
Marking this dependent on 328 since fixing that bug may change the error codes.
------- 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=328
------- Additional Comments From byers(a)lysator.liu.se 2004-05-27 17:01 -------
The text in comment #1 is gone.
I don't think it's horrible to return aux-item-permission here, but yes, (a new)
undefined-aux-item would probably be prettier. It's not a big deal to fix --
I'll do it if you think it should be done.
Shouldn't this be retargeted to "server"? There's another bug that covers the
documentation issue.
------- 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=196
------- Additional Comments From byers(a)lysator.liu.se 2004-05-27 15:48 -------
Yep, I've done them all. I think I'll go over them again -- the full text is
repeated in two places and referred to from two others. If possible I want to
avoid repeating the text. There's also a sublety I noticed that isn't covered
(Who-Info.username is not where the person logged in from most recently, but
where the session logged in from).
------- 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=196
------- Additional Comments From ceder(a)lysator.liu.se 2004-05-27 15:44 -------
Looks good.
There are three occurances of "FIXME (bug 196)" in Protocol-A.texi. Have you
dealt with all of them?
------- 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=201
------- Additional Comments From byers(a)lysator.liu.se 2004-05-26 22:29 -------
Well, okay then.
My working copy now reads:
The importer needs to be careful not to deliver messages to
conferences that do not allow messages, even though the server might
not complain. Limitations on what messages a conference accepts are
defined by aux-items. See @ref{The Aux-Item List} and @ref{Aux-Item
Types}, in particular @aux{redirect}, @aux{allowed-content-type} and
@aux{mx-refuse-import} for more information.
Good enough?
------- 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=200
------- Additional Comments From byers(a)lysator.liu.se 2004-05-26 22:18 -------
No, the username can't change.
My working copy reads:
This message is sent when a session's working conference,
@code{what-i-am-doing} string (@pxref{change-what-i-am-doing})
changes. The new information is sent in @aarg{info}.
Good enough?
------- 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=199
------- Additional Comments From byers(a)lysator.liu.se 2004-05-26 22:13 -------
I can verify that access-denied is only used to signal not enough access to the
conference to add members, at least in lyskomd.
My working copy now reads:
Not enough permissions or privileges to add members to @rarg{conf-no}.
Good enough?
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.