Bug 248432 - Bump default samba version
Summary: Bump default samba version
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-08-02 14:20 UTC by Dries Michiels
Modified: 2020-10-17 19:10 UTC (History)
4 users (show)

See Also:
driesm: maintainer-feedback? (timur)
driesm: exp-run?

Attachments
defaultsamba.diff (507 bytes, patch)
2020-08-02 14:20 UTC, Dries Michiels 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dries Michiels freebsd_committer freebsd_triage 2020-08-02 14:20:22 UTC 
Created attachment 216958 [details]
defaultsamba.diff

Please run an exp-run for bumping default samba version.
Comment 1 Vladimir Druzenko freebsd_committer freebsd_triage 2020-08-02 14:28:04 UTC 
Using it as default from 1st version in ports.

All work fine:
$ pkg info -r samba411
samba411-4.11.11:
        far2l-g20200622
        ffmpeg-4.3.1,1
        kio-extras-20.04.3_1
        vlc-3.0.11_3,4
        mpv-0.32.0_4,1
        mplayer-1.4.0.20200621_2
        mencoder-1.4.0.20200621_2
        libxine-1.2.9_13
Comment 2 Dries Michiels freebsd_committer freebsd_triage 2020-08-03 12:50:16 UTC 
PR should probably go to portmgr, but I can't change the assigne.
Comment 3 Daniel Engberg freebsd_committer freebsd_triage 2020-08-03 13:52:59 UTC 
Next time please be more verbose why you think this change needs to be done as it's a port that's popular (affects many) and we should avoid unnecessary breakage.

One valid reason is because its close to eol by upstream ("~2020-09") .
https://wiki.samba.org/index.php/Samba_Release_Planning#General_information

Regarding this version in particular if we for whatever reason need to downgrade it might be an issue for some users.

"Samba 4.11 has changed how the AD database is stored on disk. AD users should not really be affected by this change when upgrading to 4.11. However, AD users should be extremely careful if they need to downgrade from Samba 4.11 to an older release."
https://wiki.samba.org/index.php/Samba_4.11_Features_added/changed#UPGRADING

Best regards
Daniel
Comment 4 Daniel Engberg freebsd_committer freebsd_triage 2020-10-01 21:28:47 UTC 
I think we can close this as we have both 4.12 and 4.13 in tree.
Comment 5 Dries Michiels freebsd_committer freebsd_triage 2020-10-06 17:18:04 UTC 
I have renamed to bug to be more general. This way we can still track the fact that a bump of the default version should still occur (4.10 is EOL? or at least soonish). Given that 4.12 and 4.13 are in the tree now, I talked to Timur and we should let them mature a bit (4.12) before bumping the default version (probably to 4.12).
Comment 6 Dries Michiels freebsd_committer freebsd_triage 2020-10-06 17:22:00 UTC 
FYI: https://wiki.samba.org/index.php/Samba_Release_Planning
4.10 has been EOL-ed @ 2020-09-22
Comment 7 Vladimir Druzenko freebsd_committer freebsd_triage 2020-10-06 18:23:35 UTC 
(In reply to daniel.engberg.lists from comment #4)
Do it 4.13 - work for me fine.
Comment 8 Timur I. Bakeyev freebsd_committer freebsd_triage 2020-10-17 19:10:10 UTC 
4.12 is set as a new default.