#1046849 subversion: Fails to build source after successful build

#1046849#5
Date:
2023-08-13 19:21:29 UTC
From:
To:
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/subversion_1.14.2-4_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.

#1046849#8
Date:
2023-10-07 13:54:54 UTC
From:
To:
Hello,

Bug #1046849 in subversion 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/jamessan/subversion/-/commit/9cdf8614ecf927888389faad025e4051d42fa269
------------------------------------------------------------------------
Remove BUILD directory and other detritus during clean

Closes: #1046849
Signed-off-by: James McCoy <jamessan@debian.org>
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1046849

#1046849#15
Date:
2023-11-04 00:13:03 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
subversion, 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 1046849@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James McCoy <jamessan@debian.org> (supplier of updated subversion 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: Fri, 03 Nov 2023 19:34:37 -0400
Source: subversion
Architecture: source
Version: 1.14.2-5
Distribution: unstable
Urgency: medium
Maintainer: James McCoy <jamessan@debian.org>
Changed-By: James McCoy <jamessan@debian.org>
Closes: 1031229 1046849 1055242
Changes:
 subversion (1.14.2-5) unstable; urgency=medium
 .
   * Add future=+lfs build options to ensure use of 64-bit filesystem APIs
   * Add commented example for SVNListParentPath in dav_svn.conf
     (Closes: #1031229)
   * Remove BUILD directory and other detritus during clean (Closes: #1046849)
   * Backport upstream patch to fix missing version in pkg-config files
     (Closes: #1055242)
     + autogen.sh: export environment variable "PYTHON", for autoheader and autoconf
   * Skip dh_autoreconf, since we already call autogen.sh
Checksums-Sha1:
 ee1cbcd72237c25c26f3c9a92f94b4011c676a48 4046 subversion_1.14.2-5.dsc
 1b878b6f20f8a86078d2c7f9b54e45f6ed382cd0 337732 subversion_1.14.2-5.debian.tar.xz
Checksums-Sha256:
 440238a21f27f8c77d47a7349930e78efbdbad944211aed3ab5a8b3a238d9283 4046 subversion_1.14.2-5.dsc
 a898a4f010a730860bd592eda28822c55751c1b83303d4cf050f9684cf8692e5 337732 subversion_1.14.2-5.debian.tar.xz
Files:
 bfd2f3374bac555accf8d583ff730521 4046 vcs optional subversion_1.14.2-5.dsc
 774f2939a55dca307c8d81b298d41bef 337732 vcs optional subversion_1.14.2-5.debian.tar.xz
-----BEGIN PGP SIGNATURE-----

iQKoBAEBCgCSFiEEkb+/TWlWvV33ty0j3+aRrjMbo9sFAmVFhUVfFIAAAAAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDkx
QkZCRjRENjk1NkJENURGN0I3MkQyM0RGRTY5MUFFMzMxQkEzREIUHGphbWVzc2Fu
QGRlYmlhbi5vcmcACgkQ3+aRrjMbo9uDMxAAvvLznewscGPq6tzzHLq8D8Xpx3BJ
GFdKBNIfu4xpWiY7p3dZM8Jr0aLtRE4RS9cT5cJkTgIi3xaxHMjOPda3Aevh09ZV
gIHIaiKUoFCXnctT7xcpejf9pVtHnbE6zc0F1PZbWb8sGFZ96Mv7zlGIP/pcg2Y5
0wg90DcUgsH2N6NmksqpN5uvf+b+ykSLF2f+DTL1qu206JgtUw0v9pzNHZ+YjiY1
itezHGGyY9VNJ7s5E6WmkmRw4UXpYaW8qLCEy4wzBt3kd1NmzJ+YNHnVEGou7HQt
dWGg7vlRaWwoCdazZqDwK6sk8Fr9rnuz1ImF+rLWo+8fZMaLadAvTsII+ZVmrKuq
EAwJ08KOFhQLOrnKUPpPFe01NUEyaEBP3L1nvE/uf9gNJwU6P6OLuZcDO8L6FZ2t
y1dKIdaVdN0SUl4Hux9Wl9Ap7J8kDG+ZdiyhMIsiZ1sjnOJFbdPxwsr7m4YXzGAl
AObvST98TC3/lXzV8NyMkDpdGIPC42mfqcBYPT4Oc9UOAWcSRjTBW3ldLMkbIuFD
UN7Cbh8gCPSHhD5nWPfUVR3MFpluYD4imfLF73bsHo0BKDz3sn08qSMy9sJq+8DZ
LPV6JbyGayHRhSzEbuLeQeH1qf6U0ykE2GI32kCmxTYKePJ61fuXv8ufLjBb+jZW
RmrgJXbI5s14ESM=
=IJxD
-----END PGP SIGNATURE-----

#1046849#26
Date:
2026-02-08 22:29:02 UTC
From:
To:
Control: notfound -1 1.14.5-3

Just because something shows the same symptom, does not mean it is the
same root cause. Rather than unarchiving and marking old bugs as
"fixed", it would have been better, IMO, to file new bugs.

That also wouldn't have left your link to the build logs as part of a
comment in a control@ email, where it's harder to find. I only saw it
when digging up this email to reply to it.

At least as far as this subversion bug is considered, it is indeed a
different issue from before, so I'm removing the "found" annotation.

Cheers,

#1046849#33
Date:
2026-02-08 22:41:50 UTC
From:
To:
We don't really know if if it's a different issue or not.

I wrote this to Michael Tokarev in Bug #1048754 who complained
in a similar way, and I believe my reply does apply here as well:
---------------------------------------------------------------- Hi. The underlying problem here is that dpkg-source does not report all the errors: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1126665 So, yes, it may be the case that some packages now fail for a "different" reason. But it can also be the case that the fix was incomplete because the original report was incomplete as well (because of the above bug). I've seen this to happen quite often when people fix the thing that they see in the build log but do not bother to try again. Since I don't have an easy way to determine if the fix that was implemented at the time was correct or not, I decided to reopen the bug when I was able to determine that it currently fails. I agree that this may not be perfect, but I believe it was better than the all the other alternatives. Thanks.
#1046849#38
Date:
2026-02-08 23:06:36 UTC
From:
To:
that the package does not build source after a binary build.

I'm having difficulty to understand why some people seem to be upset
about this.

If a package written in C FTBFS with gcc-15, and it has foo.c and
bar.c, both of which requiring a fix, and the maintainer fixes foo.c
only (as only foo.c appears in the build log) would you say that it's
wrong to reopen because now it fails for a "different" reason? (bar.c)

BTW: I'm building subversion by adding this single file to debian/clean

subversion/tests/cmdline/.davautocheck.sh.stop

and will let you know how it goes when it finish, but according to the
dpkg-dev bug which I quoted before, this may or may not be enough to
fix the bug ("the bug" = fails to build source after binary build).

Thanks.

#1046849#43
Date:
2026-02-08 23:30:23 UTC
From:
To:
I didn't say you're reporting the root cause, but re-opening the same
bug implies that it is the same root cause.

Separate issues should be handled by separate bugs. I'm not expecting
you to determine if the root cause is the same. That's for me to do and
and, if so, merge the new bug into the existing one.

Yes.

I'm seeing a failure completely unrelated to that, so I doubt it will
be enough.

Cheers,

#1046849#48
Date:
2026-02-08 23:59:22 UTC
From:
To:
Well, I think nobody would do that.

If a package FTBFS with gcc-15, everybody would understand that the
bug is only fixed when the package builds again with gcc-15, not when
only the first foo.c is fixed.

Well, my build succeeded after adding the above line. What's the
failure you see on your end?

Thanks.

#1046849#53
Date:
2026-02-09 00:27:22 UTC
From:
To:
Hi. The attached patch works for me.

(the file is not in the original source and it's created as new,
therefore I guess it belongs to the first section of debian/clean,
before the comment).

Would you please check if it fixes the current issue?

(I would prefer not to report new bugs for now).

Thanks.

#1046849#60
Date:
2026-02-11 15:54:47 UTC
From:
To:
We believe that the bug you reported is fixed in the latest version of
subversion, 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 1046849@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James McCoy <jamessan@debian.org> (supplier of updated subversion 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: Wed, 11 Feb 2026 10:20:31 -0500
Source: subversion
Architecture: source
Version: 1.14.5-6
Distribution: unstable
Urgency: medium
Maintainer: James McCoy <jamessan@debian.org>
Changed-By: James McCoy <jamessan@debian.org>
Closes: 1046849
Changes:
 subversion (1.14.5-6) unstable; urgency=medium
 .
   * Fix "build source after successful build" (Closes: #1046849)
     + Remove subversion/tests/cmdline/.davautocheck.sh.stop during clean
     + Do not run upstream's extraclean target in parallel
   * Remove Priority field, since optional is the default value
   * Remove kfreebsd architecture restrictions
   * Declare compliance with Policy 4.7.3
Checksums-Sha1:
 0246f09f59c3369a72ea6d45ac4bf36d17c82666 3976 subversion_1.14.5-6.dsc
 c9b883ec88cce01ed4966bb79bf90855f9fdb8d8 300584 subversion_1.14.5-6.debian.tar.xz
 3728b927a9d862aae30ddf8ae059e662b394a5b9 26942508 subversion_1.14.5-6.git.tar.xz
 118cefe942d9e919dfeffccdf7fb9944751a2d76 17310 subversion_1.14.5-6_source.buildinfo
Checksums-Sha256:
 b7c7eb4009f4251e23043adc68b486eb3b7539d57cbd03f496d66b1a767960e5 3976 subversion_1.14.5-6.dsc
 242c7c9cd09a4d08c578500b4d78857047319601b8deb0cbca51e2bd47db4c94 300584 subversion_1.14.5-6.debian.tar.xz
 9343cca05f9152d3291e4d5dba5e0614543a8edbd8d43a015d7405c68beccdec 26942508 subversion_1.14.5-6.git.tar.xz
 5be8c5f8b4293d7e0abbd789b2e26a81b2a2ecc04cab95454c42593a4a41a1a7 17310 subversion_1.14.5-6_source.buildinfo
Files:
 80d2ca68e482c51112cc5a4b2d94a01f 3976 vcs optional subversion_1.14.5-6.dsc
 751390d206c130d97a1dc32ca9e988d8 300584 vcs optional subversion_1.14.5-6.debian.tar.xz
 0f485b0fe88f7d4bc4d27ff813f1878d 26942508 vcs None subversion_1.14.5-6.git.tar.xz
 3887ba8385520598d4306dad254d82cc 17310 vcs optional subversion_1.14.5-6_source.buildinfo
Git-Tag-Info: tag=7be28f7063b3741d194b3733904f3da4427b4648 fp=91bfbf4d6956bd5df7b72d23dfe691ae331ba3db
Git-Tag-Tagger: James McCoy <jamessan@debian.org>
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEN02M5NuW6cvUwJcqYG0ITkaDwHkFAmmMn+wACgkQYG0ITkaD
wHm1gQ//XYz5LIOPoPGyiNWTVWGU2+y8lxvwnLy//YmULnZD6WeVBXlHjbY7+ooZ
mNqERWSSdWDDwuwdaqObysKChSgivi7S8AkYjWUj+X1cmulq8P80vfmQb6ovGzdM
nKrFeWaAIXEPK8NqtNXpwc+lWdS2/EjUT+6z37JLdyJdEpmgW0FoMzBbSWsMdFRo
xkafo71ENsyACsWJzYSyOpzGFXLo9UQS9QIYcUWnpk1isOP8y99isub55yPjcxro
lGKGOz6OEax1gVOde1XeeVo6DMxJYQDnNI71iER6NL1wC0Pzw44M+9c3U2JRn8ll
JIbFvGAjh4PF/c8QW3KibOdHr1y5RiVAYaXfwwnoKLfpDG5xUVbLHvMgrbCOMGjy
R0CvAzBEUWf8TDwJAhl24NRBtOzMiY/qYG09QxiSneFeMYBtIqoA7DFhG31UYh94
l0Le2umuDie6gJ4mWzsX6S9iHfBSZrgV1wW0K+Tzqal+XuII68F8F6Z8n96xao0s
jHD4OeCK1NL+opykmi2KVqGCsryfvNYzqyEJga4EfWlwaaJDyaJpQHWNHzakw61s
b7NkoiEBdPSNwuDGnwdiz02jfLzOJ8RANW9wtJdJiyr9VPmHC3bdWGQAa+dZNArR
yeKbadtc7mLn41QazqE0+7Fik2CD2vuT+UtvUgj5iYdZ6aI8KJs=
=bFYT
-----END PGP SIGNATURE-----