[Pkg-samba-maint] Upgrade question

[Terry McKenn]

I am sincerely thankful to all maintainers at debian, so don't take this 
as a gripe.  I am merely curious...What should I have done?

A fully patched etch machine uses
# dpkg -l |grep -i 'samba'
ii  samba                      3.0.24-6etch10   a LanManager-like file 
and printer server fo
ii  samba-common               3.0.24-6etch10   Samba common files used 
by both the server a

Upgrading to lenny uses
# dpkg -l | grep -i 'samba'
ii  samba                      2:3.2.5-4       a LanManager-like file 
and printer server fo
ii  samba-common               2:3.2.5-4       Samba common files used 
by both the server a

[unknown yet] In 3.0.25 the default for "msdfs root" was changed to "no" 
which requires rebooting the clients to update their cache.

The winxp clients could not connect.
Googling the error codes in the /var/log/samba/log.* files did not help.
Googling terms like "samba upgrade lenny" did not help.

I found and used "testparm -vs" to show all of the settings and compared 
an etch pc to the new lenny pc.
    I used the raw output of etch on lenny to see if they worked, 
removed 7 obsolete items, and they worked.

So I started narrowing down the list of suspects.
    The culprit ... "msdfs root"

*** Now armed with something specific, the hunt became easier. ***

Searching the man pages revealed nothing relevant.

Looking here...nothing
    
http://packages.debian.org/changelogs/pool/main/s/samba/samba_3.2.5-4/changelog

Googling with something more specific, I found this
    http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=424610
which lead to this
     https://bugzilla.samba.org/show_bug.cgi?id=4619

 From the two bug reports, I looked here
    http://packages.debian.org/lenny/i386/samba/filelist
And found this as a likely file
    /usr/share/doc/samba/WHATSNEW.txt
    But such an old change is no longer there.

The big question is what should I have done?
    Asking first is not in my nature...hunting I learn more.

Thanks...