Hi,

This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).

This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.

More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild

Relevant part of the build log:
The full build log is available from:
http://qa-logs.debian.net/2023/08/13/hyperkitty_1.3.7-1_unstable.log

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.

Hey Lucas,

Lucas Nussbaum <lucas@debian.org> wrote on 13/08/2023 at 21:20:47+0200:

I think it's no longer a problem with recent versions of HyperKitty, is
it?

Closing, if needed, please either reopen or resubmit a FTBFS against
latest version. :)

Le dimanche 20 octobre 2024 à 22:38:16+0200, Pierre-Elliott Bécue a écrit :

tags 1046092 patch
severity 1046092 normal
reopen 1046092
thanks

We are almost there. This is how the current version fails using
a recent dpkg-dev:


dpkg-source: info: local changes detected, the modified files are:
 example.html
dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/hyperkitty_1.3.12-4.diff.A6LYnE


Fortunately this is in the "easy" category, because the file does not
exist in the source code and it's just generated at build time, which
means it's completely safe to remove it in the clean target.

(The "not so easy" category is the case where the file exists, it's
modified during build, but removing it in debian/clean makes the build
to fail).


The attached patch works for me. I have tested not only that
it makes possible to build source after binary, but also that
the generated .debs are identical.

Thanks.

Hello,

Bug #1046092 in hyperkitty reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/mailman-team/hyperkitty/-/commit/abdb1c4c03b2f598ed8f23bcfe11b807df667926

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1046092

We believe that the bug you reported is fixed in the latest version of
hyperkitty, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1046092@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexandre Detiste <tchet@debian.org> (supplier of updated hyperkitty package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sat, 20 Jun 2026 22:51:50 +0200
Source: hyperkitty
Architecture: source
Version: 1.3.12-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Mailman Team <pkg-mailman-hackers@lists.alioth.debian.org>
Changed-By: Alexandre Detiste <tchet@debian.org>
Closes: 1046092
Changes:
 hyperkitty (1.3.12-5) unstable; urgency=medium
 .
   * Team Upload
   * Remove python3-mock from autopkgtest dependencies
   * Drop "Rules-Requires-Root: no": it is the default now
   * Bump Standards-Version to 4.7.4, drop Priority: tag
   * Rename files under debian/ for future debhelper 14 compatibility
   * Use canonical URL in Vcs-Git.
   * Add debian/upstream/metadata
   * use dh-sequence-python3
   * Use dh-sequence-sphinxdoc
   * Rewrite d/rules with newer & shorter syntax
 .
   [ Santiago Vila ]
   * Fix clean target. Closes: #1046092.
Checksums-Sha1:
 3f80c8dcf26829cec7e5fa3b2023e679f5e8895b 2703 hyperkitty_1.3.12-5.dsc
 f8e99c26b1d853cc5eddbee095c1e22cf6171446 69912 hyperkitty_1.3.12-5.debian.tar.xz
 2402da280d661bc18d77bfbe4bbef55ea2685cb9 12510 hyperkitty_1.3.12-5_source.buildinfo
Checksums-Sha256:
 53c66ad55cbe393ebe5aae0ee349b0cc924c80aa2c2ab54060fd746b10b75960 2703 hyperkitty_1.3.12-5.dsc
 c6d9f66e3b37d9c322af0a66937deee2d920bc749d268ab12266d7a013737511 69912 hyperkitty_1.3.12-5.debian.tar.xz
 18da36e24f06a705d0bc16f0f9c8f042c10dd8c2b134f5195159122ee9bd5415 12510 hyperkitty_1.3.12-5_source.buildinfo
Files:
 02c3360fa7defc649f5dd9f0db898716 2703 python optional hyperkitty_1.3.12-5.dsc
 e3d4bb9ff4fa5a9ca46d5a3d784244de 69912 python optional hyperkitty_1.3.12-5.debian.tar.xz
 7e39aee67492b92e71441aebfc0edaa6 12510 python optional hyperkitty_1.3.12-5_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmo2/d4RHHRjaGV0QGRl
Ymlhbi5vcmcACgkQMfMURUShdBqFWA/7BpxFYqZiIeN1OXEFLI4AfYSiIVnM/CmC
mI+d7rWytA7o8vY2SyDxnbqdt9HaNJn71ooGnYagzQaoUDUbdTIrEC6BtQOI6XDX
qCjGSXjDzXpX+yajQe9P9NjMl7de+Py1MrUyMXHQrMgW33cv32ycfgEjrIfbnlTb
GfMlTtEu9r7al4nLtGVWBHxjf1MorHxvxOTzrxO/L62uqrPrIwjnWK2rCIkFvmoZ
ysl8B/28yLghXAHTLXGgg4//HTZbNtWKmlU7Xjc68VuTwfs537/t4auPgWODa+N9
yhVv1cMzcY4/l5G0gVCnGYgrKOGddHLjkNgSreS14mNbot1aIYu22z+Sa//+Dq68
wjDMgyFjn7yk+peT5Wb9R9TIxuVEiP27Yg8urhVNpAZMKANye2WHE1UTh2X2VDNA
/OXAOcBP458Ky4yCuhf5WZj7Ztkn6/cxGup1RrxDYpbhTLBFCBGRq6pzUCkzhqxY
k1haKfhJKdsiFqr47GFRm/EXg2JU3k/s3h+iG9UmwnDxZRH0rFZ7Rbj/6k0Pr+M1
s00Jf9/Kr6iu0XFVnRTL03ZmmxyejB2SlEWjrWY+r9OmcGDnznDs69QNjMemqoBU
AKtS9cfVco/5cfR0ZGghCgdI2SCQMWNJ8Juh6DUZh3XHDRQ0/OyWrbekwGbm++CI
NYGCxV13GhY=
=amkI
-----END PGP SIGNATURE-----