[IntelMQ-dev] Small unpatching issue during build of intelmq v3.3.0

mika.silander at csc.fi mika.silander at csc.fi
Thu Apr 4 10:33:50 CEST 2024


--
Hi,

 Gave a try on intelmq v3.3.0 (cloned from github and on the develop branch) today and
got this when running "dpkg-buildpackage -us -uc -b -d" on a Ubuntu 22.04 LTS:

dpkg-buildpackage: warning:     debian/changelog(l5): ignoring invalid week day 'Fr'
LINE:  -- Aaron Kaplan <aaron at lo-res.org>  Fr, 01 Mar 2024 14:19:00 +0100
dpkg-buildpackage: info: source package intelmq
dpkg-buildpackage: info: source version 3.3.0-1
dpkg-buildpackage: info: source distribution stable
dpkg-buildpackage: info: source changed by Aaron Kaplan <aaron at lo-res.org>
dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build .
dpkg-source: warning: intelmq_v2/debian/changelog(l5): ignoring invalid week day 'Fr'
LINE:  -- Aaron Kaplan <aaron at lo-res.org>  Fr, 01 Mar 2024 14:19:00 +0100
 fakeroot debian/rules clean
dh clean --with python3,sphinxdoc --without python2 --buildsystem=pybuild --with quilt --with systemd
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
   dh_auto_clean -O--buildsystem=pybuild
dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 9 in use)
I: pybuild base:239: python3.10 setup.py clean
running clean
removing '/home/mika/intelmqwork/intelmq_v2/.pybuild/cpython3_3.10_intelmq/build' (and everything under it)
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-3.10' does not exist -- can't clean it
   dh_quilt_unpatch -O--buildsystem=pybuild
Patch fix-intelmq-paths.patch does not remove cleanly (refresh it or enforce with -f)
dh_quilt_unpatch: error: quilt --quiltrc /dev/null pop -a || test $? = 2 returned exit code 1
make: *** [debian/rules:20: clean] Error 1
dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2

 What buttons, levers, cranks and the like should be turned to get passed the patching
issue? I'd prefer not to have to enforce the thing as suggested.

Br, Mika



More information about the IntelMQ-dev mailing list