Dear maintainer:

During a rebuild of all packages in unstable, this package failed to build.

Below you will find the last part of the build log (probably the most
relevant part, but not necessarily). If required, the full build log
is available here:

https://people.debian.org/~sanvila/build-logs/202510/

About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.

If you cannot reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:bgw-replstatus, so that this is still
visible in the BTS web page for this package.

Thanks.
--------------------------------------------------------------------------------
[...]
 debian/rules clean
dh clean --with pgxs
   dh_auto_clean --buildsystem=pgxs
	pg_buildext clean build-%v postgresql-%v-bgw-replstatus
rm -rf build-*/
rm -rf debian/postgresql-*-bgw-replstatus/ debian/postgresql-*-bgw-replstatus.substvars
make[1]: Entering directory '/<<PKGBUILDDIR>>'
rm -f bgw_replstatus.so bgw_replstatus.o  \
    bgw_replstatus.bc
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
   dh_clean
   pg_buildext checkcontrol
--- debian/control	2025-04-20 15:57:21.000000000 +0000
+++ debian/control.uhgZU8	2025-10-04 10:06:32.319364992 +0000
@@ -17,7 +17,7 @@
 Vcs-Git: https://github.com/mhagander/bgw_replstatus.git
 Vcs-Browser: https://github.com/mhagander/bgw_replstatus

Re: Santiago Vila

Hi Santiago,

I am aware that I started a transition. This was planned for last week
but there was a business trip on short notice.

This mass bug filing isn't really helpful because now I'll have to
hand-pick a bug number for each upload instead of just doing them
mechanically.

Christoph

This postprocessing will give you a list in the simple form

package bugnumber

cat subjects-for-the-last-mbf.txt | tr -d ":" | awk '{ gsub("Bug#", "", $2); print $3 " " $2 }'

Thanks.

Sorry for the lack of context. I forgot to Cc the bug address in two previous emails.

I initially gave Christoph the subject lines for 88 bugs with the bug number in them,
since I always use X-debbugs-Cc. Those probably account for 90% of the related bugs.

The postprocessing above extracts the package and the bug number, I'm
attaching the output here for reference.

Thanks.

Re: Santiago Vila

Thanks for the list, automating that part of the changelog entry is a
great idea, had not thought of that.

Cheers,
Christoph