[Pkg-samba-maint] Upgrade question

[Mathieu Parent]

Hi,

2009/4/9 Christian Perrier <bubulle at debian.org>:
> Quoting Terry McKenn (smckenna_debian at clanlineage.com):
>> 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?
>
>
> I'm not sure there is a good answer to that question.
>
> Obviously, you were hit by an upstream behaviour change that we didn't
> anticipate. The package changelog doesn't show any particular item
> about this because we generally don't list upstream changes in our
> changelog (that would make them too huge).
>
> Would this have been detected during the development of lenny, we
> would certainly have considered introducing a warning (probably not,
> actually....imagine what would happen if all packages print warning
> about potential behaviour change when doing a major upstream upgrade)
> or an item in NEWS.Debian

Agree.

>
> I haven't upgraded my own major file servers yet but, when preparing
> for it, I'll probably use a server mimicing the real server setup to
> try identifying potential problems introduced by the upgrade.
>
> I'm not even sure that I would be able to detect such problem with
> this.
>
> I think that I will make upstream the suggesiton of keeping a full
> changelog history instead of "just" providing WHATSNEW.txt which just
> lists the *latest* changes. *This* is something that always annoys me
> when I try tracking down what version introduced a given change.
>

The relevant info is at
http://wiki.samba.org/index.php/Samba_Features_added/changed_(by_release)
Unfortunately, it seems unmaintained.

But this particular change is in 3.0.25 :
<quote>
Changes to MS-DFS Root Share Behavior
+ Please be aware that the initial value for the "msdfs root" share
parameter was changed in the 3.0.25 release series and that this
option is now disabled by default. Windows clients frequently require
a reboot in order to clear any cached information about MS-DFS root
shares on a server and you may experience failures accessing file
services on Samba 3.0.25 servers until the client reboot is performed.
Alternately, you may explicitly re-enable the parameter in smb.conf.
Please refer to the smb.conf(5) man page for more details.
</quote>

Mathieu Parent