Hi @all, I cannot use this patch in 2.2.5. I patched the source before with parse_sec.patch ldap_start_tls.patch Makefile.in.patch srv_spoolss_nt.patch addform.diff Containes the samba-2.2.5-printing.patch only parts of the above patches? tom
On Wed, Aug 28, 2002 at 12:28:22PM +0200, Thomas Bork wrote:> Hi @all, > > I cannot use this patch in 2.2.5. > I patched the source before with >Hi! I've just patched the samba 2.2.5, and it works perfectly. It even works the HP1220C printer (that didn't work with some of the patches applied). :) (Thanks Jerry!!!!!) Thomas, you must patch from directory: "samba-2.2.5/.." I mean, the directory just before the samba one. Not from "source" ! Hope it helps! :)
On Wed, 28 Aug 2002, Thomas Bork wrote:> Hi @all, > > I cannot use this patch in 2.2.5. > I patched the source before with > > parse_sec.patch > ldap_start_tls.patch > Makefile.in.patch > srv_spoolss_nt.patch > addform.diff > > Containes the samba-2.2.5-printing.patch only parts of the above > patches?Start with a fresh 2.2.5 tree. Then apply the * samba-2.2.5-printing.patch * ldap_start_tls.patch * Makefile.in.patch The addform, srv_spoolss, & parse_sec patches have been rolled into the cumulative patch. Sorry for the confusion :-) cheers, jerry --------------------------------------------------------------------- Hewlett-Packard http://www.hp.com SAMBA Team http://www.samba.org -- http://www.plainjoe.org "Sam's Teach Yourself Samba in 24 Hours" 2ed. ISBN 0-672-32269-2 --"I never saved anything for the swim back." Ethan Hawk in Gattaca--
Hallo Gerald Carter, you wrote:> > I cannot use this patch in 2.2.5. > > I patched the source before with > > > > parse_sec.patch > > ldap_start_tls.patch > > Makefile.in.patch > > srv_spoolss_nt.patch > > addform.diff > > > > Containes the samba-2.2.5-printing.patch only parts of the above > > patches? > > Start with a fresh 2.2.5 tree. Then apply the > > * samba-2.2.5-printing.patch > * ldap_start_tls.patch > * Makefile.in.patch > > The addform, srv_spoolss, & parse_sec patches have been rolled into > the cumulative patch. Sorry for the confusion :-)Patching the fresh 2.2.5-tree solved the problems. Thanks for your help. tom