I see that 2:4.13.14+dfsg-0ubuntu0.20.04.3 was released today. I've
built and uploaded a container using that version, and the %i token
expansion now seems to work again:
====
$ docker run --rm
registry.gitlab.developers.cam.ac.uk/alt36/lp1952633:20.04.3-dynamic
* Starting SMB/CIFS daemon smbd
...done.
. D 0 Mon Dec 6 16:08:08 2021
.. D 0 Mon Dec 6 16:08:10 2021
examplefile N 0 Mon Dec 6 16:08:08 2021
61794184 blocks of size 1024. 14908796 blocks available
Output of "prexec.sh %i:"
127.0.0.1
====
However, the changelog for .3 references the upstream samba bugs 14901
(changes around 'map username script') and 14918 (failure to delete a
directory containing dangling symlinks), neither of which seem to be
related to my bug report here. My guess is thus that something
unintended happened with the binaries shipped with .2
Because this broke all of our production fileservers I'm keen to get to
the bottom of what happened and to make sure there isn't a repeat with
future releases.
In #5 Paride raised a possible suspicion with "the newer build
dependencies .2 has been built against." I'm not sure where to find
those, or to see if they've been changed again for the .3 build. If
there's anything more I can do here I'm happy to repeatedly try building
with different options and test the results.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952633
Title:
%i token does not expand on 4.13.14+dfsg-0ubuntu0.20.04.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1952633/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
