These odd » characters are shown at some part of the patch. I wonder
what causes this display issue... And non-ascii characters are not
printed correctly although they are in the "View Raw" mode. Please see
the utf8str.txt file.
277 @@ -1499,30 +1506,36 @@ entry2str_internal_size_attrlist( const
Slapi_Attr *attrlist, int entry2str_ctrl
280 » » /* Count the space required for the present and deleted values */
281 -» » elen+= entry2str_internal_size_valueset(a->a_type,
282 -» » » » » » » » » » » » entry2str_ctrl, attribute_state,
283 -» » » » » » » » » » » » VALUE_PRESENT); 305 +» » elen += entry2str_internal_size_valueset(a, a->a_type,
306 +» » entry2str_ctrl, attribute_state, VALUE_PRESENT);
Note: The test build was blessed by the bug reporter.
I am final year software engineering student at srilanka institute of
information technology and i would like to contribute to project *developing
administrative tools for 389 directory server* for GSoC and i would like to
know more about the project and would be grateful if someone can guide me
We are planning on doing the Trac to Pagure migration this Friday.
Using Pagure is very similar to Trac, except you create "Issues" instead
One change to keep in mind is that we now have separate projects for our
components like: admin server, 389-ds-console, idm-console-framework,
389-dsgw, 389-ds-base, etc. These can all be found under the
If you have an Admin Server issue to report create a new issue under the
389-admin project, etc.
Please use the "389-ds-base" project for new Directory Server issues.
Note, your previous tickets you filed, or are following, will still have
the same ticket number:
Once the migration is complete there will be a final announcement, and
Trac will be put into read-only mode until it is decommissioned.
What do you think of this?
If you want, I can write up a full design doc. I think this is the best
way, rather than each plugin trying to intercept and block the
operation, if we provide a generic way to register and block these.
Red Hat, Brisbane