Re: Next alpha of 3.0 planned for Friday

2003-03-28 Thread Gerald (Jerry) Carter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

 This is just a heads up for everyone.  I'm planning 
 the 3.0alpha23 release for this Friday.  If you have code 
 that needs to be merged of commited to the SAMBA_3_0 cvs tree, 
 please get in checked in by 8am EST on Friday of the week.

I've hit a few small bugs (one in RH packaging and one 
in smbpasswd).  As soon as I get those cleaned up, 3.0alpha23 
will be on its way.  Hopefully tomorrow.




cheers, jerry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.0 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQE+hNGSIR7qMdg1EfYRAlv+AKDWJbF5ZBK5IPE104O/ZPmD6nFwIgCfckUG
6oCiLf1R6SKsDsu4FkgS+PI=
=A0L2
-END PGP SIGNATURE-



Re: Next alpha of 3.0 planned for Friday

2003-03-28 Thread Gerald (Jerry) Carter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thu, 27 Mar 2003, Tomoki AONO wrote:

 In [EMAIL PROTECTED],
 [EMAIL PROTECTED] wrote:
 
  This is just a heads up for everyone.  I'm planning 
  the 3.0alpha23 release for this Friday.  If you have code 
  that needs to be merged of commited to the SAMBA_3_0 cvs tree, 
  please get in checked in by 8am EST on Friday of the week.
 
 Would someone take a look at CIDR-like notation problem by
 Mr. Takeda (and following mail by me) ? If this is right,
 example config described in securing-samba.sgml will not
 work as expected.
 (http://lists.samba.org/pipermail/samba-technical/2003-March/042993.html)

Fixed. 




cheers, jerry
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.0 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQE+hG2DIR7qMdg1EfYRAv+ZAJ446QsKK2fNTJQMUaEanz0rbJoCCACeNcuH
Mxs352anoxclJKqT4TwrrLI=
=JAQm
-END PGP SIGNATURE-



Re: Next alpha of 3.0 planned for Friday

2003-03-27 Thread Tomoki AONO
In [EMAIL PROTECTED],
[EMAIL PROTECTED] wrote:

 This is just a heads up for everyone.  I'm planning 
 the 3.0alpha23 release for this Friday.  If you have code 
 that needs to be merged of commited to the SAMBA_3_0 cvs tree, 
 please get in checked in by 8am EST on Friday of the week.

Would someone take a look at CIDR-like notation problem by
Mr. Takeda (and following mail by me) ? If this is right,
example config described in securing-samba.sgml will not
work as expected.
(http://lists.samba.org/pipermail/samba-technical/2003-March/042993.html)


Tomoki AONO ([EMAIL PROTECTED])


Next alpha of 3.0 planned for Friday

2003-03-26 Thread Gerald (Jerry) Carter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

FYI...

This is just a heads up for everyone.  I'm planning 
the 3.0alpha23 release for this Friday.  If you have code 
that needs to be merged of commited to the SAMBA_3_0 cvs tree, 
please get in checked in by 8am EST on Friday of the week.

I'm also planning on spending some time reviewing how soon we 
can turn the alpha releases into beta.  I'll post a plan to the
samba-technical list early next week.




cheers, jerry
 --
 Hewlett-Packard- http://www.hp.com
 SAMBA Team -- http://www.samba.org
 GnuPG Key   http://www.plainjoe.org/gpg_public.asc
 You can never go home again, Oatman, but I guess you can shop there.  
--John Cusack - Grosse Point Blank (1997)

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.0 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/

iD8DBQE+gmSFIR7qMdg1EfYRAj50AJ9CQSMyN6oxr9OaPp0DgLT2RqGW1QCgo2I7
jUBQ3/OVT+7un5NTh3foLlA=
=9NPP
-END PGP SIGNATURE-



Re: Next alpha of 3.0 planned for Friday

2003-03-26 Thread Stefan (metze) Metzmacher
At 20:40 26.03.2003 -0600, Gerald (Jerry) Carter wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
FYI...

This is just a heads up for everyone.  I'm planning
the 3.0alpha23 release for this Friday.  If you have code
that needs to be merged of commited to the SAMBA_3_0 cvs tree,
please get in checked in by 8am EST on Friday of the week.
I'm not sure if the new LDAP modify stuff works without problems.
I have problems with that I can't change user entries via usrmgr.exe
the LDAP server returns 'can't add attribute'
(here the attribute should be modified)
and before this changes all works well (I hvae not touched the ldap server)

It would be nice if this could be fixed till alpha23

metze
-
Stefan metze Metzmacher [EMAIL PROTECTED]