Unfortunately, with issues of security, software QA, and a machine that will go away in the not-too-distant future, it is not worth the effort to upgrade entirely. I need current versions of samba due to the large number of Windows machines in our organization that interface with this server; the features/security of the newer version are preferred.
On Fri, 2004-09-17 at 08:25, Cernese, Dan wrote: > I added testing to my sources list and did an update of everything dselect > selected. > That means not just things necessary to get samba working. > However, it is very stable so far. > > > -----Original Message----- > > From: James D. Freels [mailto:[EMAIL PROTECTED] > > Sent: Thursday, September 16, 2004 5:45 PM > > To: Cernese, Dan > > Cc: [email protected] > > Subject: RE: samba broken for Debian/Woody backport for the alpha > > > > When you say "updated to sarge", did you update the entire system, or > > just the packages needed to get samba working ? I am trying > > to keep as much of this machine running Woody as possible for QA reasons > (server) > > > > On Thu, 2004-09-16 at 17:08, Cernese, Dan wrote: > > > fyi, I've been running samba 3.0.6-3 (3.0.6-Debian) on Alpha for more > > > than 3 months without much problem. I'm running a system installed > > > with woody(stable) and updated to sarge(testing). > > > > > > fwiw, > > > Dan > > > > > > > > > > -----Original Message----- > > > > From: James D. Freels [mailto:[EMAIL PROTECTED] > > > > Sent: Wednesday, September 15, 2004 11:51 AM > > > > To: [EMAIL PROTECTED] > > > > Cc: [email protected] > > > > Subject: samba broken for Debian/Woody backport for the alpha > > > > > > > > Package: samba and related sub-packages > > > > Version: >= 3.0.6* > > > > > > > > Starting at 3.0.6, samba packages backported to Woody (as > > all previous > > > > packages had been before) for the Alpha architecture produced > > > > this bug. I have tried both the 3.0.6* and 3.0.7 series > > and they both > > > have this > > > > bug. > > > > > > > > The bug is that the files on a Windows client that show up in the > > > > directory cannot be displayed, edited, or accessed in any > > > > way. They are locked out. This basically makes the > > package totally > > > unusable. > > > > > > > > The package compiles and builds .deb files without any > > > > alteration of the source as backported from > > > > > > > > deb-src http://www.backports.org/debian stable samba > > > > > > > > or alternatively. > > > > > > > > deb-src > > http://de.samba.org/samba/ftp/bin-pkgs/Debian/samba3/ stable > > > > main > > > > > > > > These apt-get sources produce reliable packages for > > versions <=3.0.5 > > > > > > > > This bug does not appear on the i386 architecture for Debian/Sid > > > > (unstable) or backported to Debian/Woody (stable). I do > > not have a > > > > machine to test Debian/Sid for the alpha for this bug, > > but I highly > > > > suspect it does exist. > > > > > > > > As a work around, I reinstalled the backported 3.0.5 > > packages for the > > > > alpha. I could also revert back to the Woody packages that > > > > also contain some of the security updates contained up > > through 3.0.7 > > > > series of samba. > > > > > > > > -- > > > > James D. Freels, Ph.D. > > > > Oak Ridge National Laboratory > > > > [EMAIL PROTECTED] -- James D. Freels, Ph.D. Oak Ridge National Laboratory [EMAIL PROTECTED]
