El 30/1/23 a las 12:36, Boian Bonev escribió:
Before uploading I did purge tzdata from my sbuild chroot and the build succeeded.
Probably you did a full build, with both arch-dependent packages and arch-independent packages. In such case sbuild installs all build-dependencies, the ones in Build-Depends and the ones in Build-Depends-Indep. That's probably why it worked. If you already have a clean chroot in which tzdata is not present, the following two things should both work: sbuild --arch-all --no-arch-any -d sid gammu sbuild --arch-any --no-arch-all -d sid gammu Currently, only the first command works, because tzdata is also required in the second command but it's only in Build-Depends-Indep. When adding or removing build-dependencies (this is not really related to tzdata), it is always a good idea to try those commands before upload, because we have different autobuilders for arch-independent packages and for arch-dependent packages and those two commands are what autobuilders really do.
Please provide some log showing the error.
I believe that with those additional explanations it should not be necessary. The way sbuild --arch-any --no-arch-all fails on a really clean chroot is exactly what I included in the very first email in this bug report. About the other things you mention: My summary would be that this is a bug according to current policy in bookworm (which I believe we likely will not change just before the release), and the fact that the bug is not RC just means that the bug is not so grave that we would want to remove the package if it's not fixed.
While I am always willing to fix low priority stuff, I'd prefer to wait and see some final resolution before proceeding.
So: It is up to you. I don't plan to NMU or anything like that, but I won't deny that I will be very happy if we could release bookworm without FTBFS bugs of any kind (which includes this one), or as few as possible. Thanks.
