[Pkg-samba-maint] samba 4.6.3 on mentors

Jelmer Vernoo?? jelmer at jelmer.uk
Mon Jun 5 17:56:21 UTC 2017

Hi Louis,

Sorry for the delay, I'd meant to send this out sooner. Thanks again
for working on 4.6.0 packages.

On Fri, May 19, 2017 at 11:23:40AM +0200, L.P.H. van Belle wrote:
> Sorry for the late responce. 
> I had to do some other things first because of a sick dad (cancer), 
> which was taking a lot of time get him correct medicine.
> Thats going the correct way now, so im getting more time again for samba again.
> Now, in responce to below. 
> Im preparing for a new build which i'll make for experimental. 
> For example, i'll go build tdb 1.3.13. 
> I'll make a changelog from there git.
> https://git.samba.org/?p=samba.git;a=history;f=lib/tdb; 
> I'll leave out the "builded for jessie", i did set that because i builded samba for jessie only.
Please build and test on unstable.

> And these packages are use by people on the samba list. 
They use the jessie builds AFAIK, which are not the same as what we're after
here - packages for unstable. In particular, we'd like to find out
about incompatibilities with the other packages in unstable.

> Now im always having problems with the version tagging and what exact to put in the changelogs. 
> I've preparied tdb 1.3.13 now, and i've added this in the debian/changelog 
> This what you/debian wants/expects? 
> tdb (1.3.13-1+nmu1) experimental; urgency=medium
>   * Non-maintainer upload
>   * New upstream release.
>     - tdb: Improve debugging in _tdb_transaction_starttree
>     - tdb: Improve debugging when the allrecord lock fails.
>     - tdb: runtime check for robust mutexes may hang in threath
>     - tdbtool: Add "storehex" commandtree
>     - tdb: Test for readonly lock upgrade bugtree
>     - tdb: Do lock upgrades properlytree
>     - tdb: Fix some signed/unsigned hickupstree
>     - tdbtools: add documentation for the tdbbackup -n optiontree
>     - waf: disable-python - align tdb's wscripttree

Please follow the same format as the other entries in the changelog:

 * Don't repeat the upstream changelog
 * Add entries for bugs reported in Debian that are fixed by this release,
   making sure to add "Closes: #XXXXXX" for bugs you close. For tdb, this is
   probably not the case, but for the Samba 4.6 upload there should be a
   fair number of bugs on https://bugs.debian.org/src:samba that you can

   See also https://www.debian.org/doc/debian-policy/ch-source.html#s-dpkgchangelog

> Now, about that part. 
> What is expected 1.3.13-1+nmu1 or plain 1.3.13-1
1.3.13-1, but either is fine, it's easy to fix up when uploading.

> When thats clear, i can make the needed package for samba 4.6.x ( and/or comming 4.7 ) 
> Without the "builded for jessie" in the logs. 
As mentioned above, the package will be uploaded to experimental so it
needs to actually build and be tested on unstable (possibly with other
packages from experimental pulled in) - not jessie.

> I have a git build of 4.7 with MIT kerberos builded also for jessie, but thats why ahead, 
> ( have a peek here : http://downloads.van-belle.nl/samba4/samba-470-BUILD_SET/README.txt ) 
> Now, last question. 
> Samba 4.6.x needs cmocka 1.0.x but 1.1.1 is release. 
> Not shown here : 
> https://git.samba.org/?p=samba.git;a=summary 
> But needed for 4.7. 
> Question is, build the 4.6 with 1.0.x cmocka or 1.1.1? 
You should be able to find out by trying to build it against the newer version
of cmocka. If it doesn't, then we need to figure out if we can get it to work
with a newer version of cmocka, or if we can somehow have two versions of
cmocka in the Debian archive.

(see Andrew's reply as well)

> And can i upload the pam_wrapper 1.0.4 to experimental.
> Which contains a build fix and fix a resource leak. 
pam_wrapper is not maintained by the Samba packaging team, but by Timo
Aaltonen. Please contact him about updating it.
> And last, i went through the debian/samba buglist. 
> Lots of problems there are due to misconfigured smb.conf. 
> This is one of the main things why i want 4.6 in debian. 
> This wil help the users but also the debian samba developers since it wil reduce the bug list of bugs.
> What do others think about this? 
Please mention the bugs that are closed by the 4.6 release in the changelog
as explained above.



More information about the Pkg-samba-maint mailing list