[Bug 1952633] Re: %i token does not expand on 4.13.14+dfsg-0ubuntu0.20.04.2

2021-12-07 Thread Paride Legovini
I agree with Lucas: chasing the exact reason of the behavior you observed is a very time consuming task. This requires checking the build logs of .1 and .2: https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/+build/22389258 https://launchpad.net/ubuntu/+source/samba/2:4.13.14+df

[Bug 1952633] Re: %i token does not expand on 4.13.14+dfsg-0ubuntu0.20.04.2

2021-12-07 Thread Lucas Kanashiro
Hi Adam, Good to hear the issue was fixed for you. Tracking down the build dependencies changes between those two versions might not be easy, you could go through the publication history of each of them in Launchpad and check but I do not think this worth. I am setting the status of this bug to Fi

[Bug 1952633] Re: %i token does not expand on 4.13.14+dfsg-0ubuntu0.20.04.2

2021-12-06 Thread Adam Thorn
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

[Bug 1952633] Re: %i token does not expand on 4.13.14+dfsg-0ubuntu0.20.04.2

2021-12-02 Thread Adam Thorn
Hi Paride, Yeah, I checked the changelog for 4.13.14+dfsg-0ubuntu0.20.04.2 and the minor change reported there did not sound like it would have any relation to the behavior I've described. But none the less, I am confident I see a difference between the .1 and .2 set of packages. I've created a f

[Bug 1952633] Re: %i token does not expand on 4.13.14+dfsg-0ubuntu0.20.04.2

2021-12-02 Thread Paride Legovini
Hi Adam, the changes between 4.13.14+dfsg-0ubuntu0.20.04.1 and .2 do not really touch anything related to the IP address expansion; the change is only about (not) auto-populating the sambashare unix group at install time. This is the diff of the packages: https://launchpadlibrarian.net/570713970/

[Bug 1952633] Re: %i token does not expand on 4.13.14+dfsg-0ubuntu0.20.04.2

2021-12-02 Thread Adam Thorn
Hi Athos, Re-reading your comment #2, you mention seeing generated logfiles at /var/log/samba/log.$SERVER_IP . I think that means you're using a different smb.conf to the one I posted, which had log file = /var/log/samba/log.%m and so wouldn't generate log files including the server IP in the na

[Bug 1952633] Re: %i token does not expand on 4.13.14+dfsg-0ubuntu0.20.04.2

2021-12-01 Thread Adam Thorn
I've seen this problem on all the clients I've tried. Some examples include Windows 10 (when running "net use \\SERVER\SHARE") and Bionic clients (with smbclient 4.7.6+dfsg~ubuntu-0ubuntu2.24 when running e.g. smbclient -L //SERVER) I also see this with smbclient as distributed to the Focal test s

[Bug 1952633] Re: %i token does not expand on 4.13.14+dfsg-0ubuntu0.20.04.2

2021-12-01 Thread Athos Ribeiro
Hi Adam, Thank you for taking the time to file a bug report. Would you mind providing a reproducer for the bug you are experiencing? In special, what client tools are you using which are not being able to properly expand the token? While I do get the error message regarding a missing file at "/d

[Bug 1952633] Re: %i token does not expand on 4.13.14+dfsg-0ubuntu0.20.04.2

2021-11-30 Thread Adam Thorn
In case it helps to reproduce the problem, or if its useful to anyone else affected by this, we downgraded (and have also pinned) the following packages: apt-get install samba=2:4.13.14+dfsg-0ubuntu0.20.04.1 samba- common=2:4.13.14+dfsg-0ubuntu0.20.04.1 samba-common- bin=2:4.13.14+dfsg-0ubuntu0.20