rvjcallanan wrote: > Just have a look at the Samba bug fixes between 3.022 and 3.025c and you will see what I mean.
And then have a look at regression bugs (still unsolved): https://bugzilla.samba.org/show_bug.cgi?id=4047 https://bugzilla.samba.org/show_bug.cgi?id=4886 and undefined (regression or new) bugs: https://bugzilla.samba.org/show_bug.cgi?id=4917 https://bugzilla.samba.org/show_bug.cgi?id=4955 ... Some of this bugs are marked as 'major'. This is what Soren is talking about. Backporting new version really does fix some bugs, but also (in some cases) introduces new bugs. In this case, introducing 3.0.25c could make ubuntu clients unusable in AD networks (4047), unusable for older Samba installs (count in almost all Linux distributions and OSX) (4886), probably hog some servers with too high RAM consumption (4917) and make ACLs in Windows unusable (4955). The list goes on, of course. I don't say that things like this will happen, but there is possibility and there are bugs open. So, there is a chance that some/all users of Samba in Dapper will have new problems. This is not how LTS works. Just take a look at RHEL 4 (or any other enterprise distribution)- they still have kernel 2.6.9. -- Samba Backport Urgently Needed https://bugs.launchpad.net/bugs/137656 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
