Hi,
Am 17.02.26 um 18:58 schrieb Adrian Bunk:
> ( overwrite error )
Yeah, noticed that too but didn't file it since it will be blocked by
autopkgtest catching that anyway. :)
I would suggest reviewing all removals in debian/rules, e.g. whatever the
problem behind
rm -rf $(CURDIR)/debian/tmp/usr/lib/python3/python3.14
is, it might do the wrong thing when the package gets rebuilt for the upcoming
Python 3.14
defaults transition.
Actually it probably is, since
/usr/lib/python3/python3.14
is a wrong path even then.
This is probably a side-effect of
# Eliminating python3.13 directory
for i in $$(find debian/ -name "python3.*"); do echo "I: Found='$$i'"; a=$$(dirname $$i); if [ ! -d "$$(dirname
"$$a")/python3" ]; then echo "I: renaming to '$$a/python3'"; mv "$$i" "$$a/python3"; fi ; done
which means the second one (3.13, then 3.14) coming ends up in
/usr/lib/python3/python3.14 where it shouldn't.
Tried to clean that up and send a MR (and build only with the default python to
avoid this mess,but I still get a dh_shlibdeps error, so no MR yet...
Regards,
Rene
