Oh, jeesh, this is getting to be a real time sink. First, you should see what the last buster-backports build had to do, since you'll no doubt have to repeat it:
Code: Select all
libreoffice (1:7.0.4~rc2-1~bpo10+2) buster-backports; urgency=medium
* actually include the tarballs...
-- Rene Engelhard <rene@debian.org> Fri, 18 Dec 2020 16:16:02 +0100
libreoffice (1:7.0.4~rc2-1~bpo10+1) buster-backports; urgency=medium
* Rebuild for buster-backports.
* debian/source/include-binaries:
- include tarballs/libmwaw-0.3.16.tar.xz
- include tarballs/mdds-1.6.0.tar.bz2
- include tarballs/liborcus-0.16.1.tar.bz2
- include tarballs/xmlsec1-1.2.30.tar.gz
- include tarballs/libnumbertext-1.0.6.tar.xz
* debian/rules:
- revert clang (>= 1:11) build-dep for buster-backports; doesn't exist in
buster and we resort back to gcc
I'm pretty sure those tarballs go in the /tarballs folder in the extracted source. Take a look in yours to see if you have those, and add those if missing as I suspect they are. Get the buster-backports debianized sources, extract them, get the missing tarballs, put them in /tarballs, and list them in debian/source/include-binaries so the build system accepts them.
As for what regenerates the control file, it's in the rules file, and it acts upon debian/control.in.
Code: Select all
#############
# Distro-specific overrides
# Debian Buster
ifeq "$(DEB_DISTRIBUTION)" "buster-backports"
BUGS=mailto:debian-backports@lists.debian.org
SYSTEM_STUFF := $(filter-out libmwaw xmlsec mdds orcus libnumbertext,$(SYSTEM_STUFF))
USE_DWZ := n
BUSTER_BACKPORT=y
endif
I actually backported all the SYSTEM_STUFF for MX Linux before I figured out how the system worked, so now I have a choice whether to use those or the tarballs, if I had the time to try another backport for MX. I also have dwz backports, so I could change that to "y" if desired...but you don't, so don't change it. What you can do is add your new stanza to the top of debian/changelog, use "buster-backports" for the distribution, then instead of the build command, regenerate the source files with (you have devscripts installed, right?)
Code: Select all
debuild -S -uc -us -d && cd .. &&rm -f *.buildinfo *.changes *.build && exit
Then take a look to see how the build-depends came out.