[Pkg-samba-maint] Bug#1048754: Processed: Fails to build source after successful build

[Michael Tokarev]

Control: notfound 1048754 2:4.22.6+dfsg-0+deb13u1

On 2/4/26 02:14, Debian Bug Tracking System wrote:
>> # These bugs were opened as part of the MBF described on
>> # https://wiki.debian.org/qa.debian.org/FTBFS/DoubleBuild
>> #
>> # At some point they were closed, but a recent test shows
>> # that "ftbfs source after binary build" still applies,
>> # hence the reopening.

>> found 1048754 2:4.22.6+dfsg-0+deb13u1
> Bug #1048754 {Done: Michael Tokarev <mjt at tls.msk.ru>} [src:samba] samba: Fails to build source after successful build
> Marked as found in versions samba/2:4.22.6+dfsg-0+deb13u1 and reopened.
This particular bug has been fixed for good, - there was a certain
problem with the build, namely, not cleaned up python .pyc cache files:

 > dpkg-source: error: cannot represent change to 
source4/scripting/bin/__pycache__/gen_error_common.cpython-311.pyc: 
binary file contents changed
 > dpkg-source: error: add 
source4/scripting/bin/__pycache__/gen_error_common.cpython-311.pyc in 
debian/source/include-binaries if you want to store the modified binary 
in the debian tarball
...

This time, while the result is the same, the issue is entirely different,
and it is an entirely different bug:

 > dpkg-source: info: local changes detected, the modified files are:
 >  python/samba/provision/kerberos_implementation.py
 > dpkg-source: error: aborting due to unexpected upstream changes

this issue has nothing to do with the issue being reopened - even
despite the fact it is also something with python.

I'll open another bug for this particular issue.

But I guess there are many bug other bugs like this, - when you opened
an unrelated old bug which is unrelated to the current ftbfs issue.

BTW, this issue might actually be more than fails to build the second
time in a row - I missed this file in the samba-ad-provision package.
I'll check this one too.

Thanks,

/mjt