bug-cvs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Is CVS development still active ?


From: Brian Murphy
Subject: Re: Is CVS development still active ?
Date: Fri, 12 May 2006 21:37:26 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.12) Gecko/20051007 Debian/1.7.12-1

Mark D. Baushke wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yves Dorfsman <address@hidden> writes:

Is CVS development still active ?

Yes.

Will we ever see 1.12 make it to stable ?

Yes. See URL:
 https://savannah.nongnu.org/task/?func=detailitem&item_id=4686
for the list of dependencies.

What does it take to get a patch included in the three.

s/three./tree?/

Test cases and general agreement that the patch is needed.

I hit a problem with PAM/ldap on Solaris, and ended using this patch
to solve it:

http://savannah.nongnu.org/patch/?func=detailitem&item_id=4488

Yup. I believe Brian Murphy took care of that on 2005-10-16 in the
FEATURE branch which was almost two weeks after 1.12.13 was released.

Brian? If you applied #4488 to the FEATURE branch, could you please
close the bug?

But I was wondering the chances of it to make it to the trunk, and the
likely timeline.

I believe it is already present... (at least the part that made sense).
I am not sure if the 'pam_set_item (pamh, PAM_RUSER, pam_username);' code
was used or not.

You may checkout your own copy of the cvs 1.12.13.1 top-of-tree sources
Check out the 'CVS' link on the https://savannah.nongnu.org/cvs/?group=cvs
page.

It was reported as a bug here:

http://savannah.nongnu.org/bugs/index.php?func=detailitem&item_id=14721

and as a patch. Not knowing how the patch section should work I just let it alone
in case it was useful to someone. How *should* it be used?

As you can see a patch has been committed to the feature branch and should
work without further changes.

/Brian





reply via email to

[Prev in Thread] Current Thread [Next in Thread]