#1125614 mydumper: FTBFS with CMake 4.2

Package:
src:mydumper
Source:
src:mydumper
Submitter:
Santiago Vila
Date:
2026-05-13 02:45:37 UTC
Severity:
normal
Tags:
#1125614#5
Date:
2026-01-15 14:39:58 UTC
From:
To:
Dear maintainer:

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

(Note: I'm assuming that the failure happens because of CMake 4.2,
but I may be wrong).

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/202601/

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:mydumper, so that this is still
visible in the BTS web page for this package.

Thanks.
--------------------------------------------------------------------------------
[...]
 debian/rules clean
dh clean --with=sphinxdoc
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
   dh_clean
	rm -f debian/debhelper-build-stamp
	rm -rf debian/.debhelper/
dh_clean: warning: Compatibility levels before 10 are deprecated (level 9 in use)
	rm -f -- debian/mydumper.substvars debian/mydumper-doc.substvars debian/files
	rm -fr -- debian/mydumper/ debian/tmp/ debian/mydumper-doc/
	find .  \( \( \
		\( -path .\*/.git -o -path .\*/.svn -o -path .\*/.bzr -o -path .\*/.hg -o -path .\*/CVS -o -path .\*/.pc -o -path .\*/_darcs \) -prune -o -type f -a \
	        \( -name '#*#' -o -name '.*~' -o -name '*~' -o -name DEADJOE \
		 -o -name '*.orig' -o -name '*.rej' -o -name '*.bak' \
		 -o -name '.*.orig' -o -name .*.rej -o -name '.SUMS' \
		 -o -name TAGS -o \( -path '*/.deps/*' -a -name '*.P' \) \
		\) -exec rm -f {} + \) -o \
		\( -type d -a \( -name autom4te.cache -o -name __pycache__ \) -prune -exec rm -rf {} + \) \)
 debian/rules binary
dh binary --with=sphinxdoc
dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
   dh_update_autotools_config
   dh_auto_configure
dh_auto_configure: warning: Compatibility levels before 10 are deprecated (level 9 in use)
	cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb PKG_CONFIG=/usr/bin/pkg-config cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON -DCMAKE_FIND_USE_PACKAGE_REGISTRY=OFF -DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DFETCHCONTENT_FULLY_DISCONNECTED=ON "-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON -DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ..
CMake Error at CMakeLists.txt:1 (cmake_minimum_required):
  Compatibility with CMake < 3.5 has been removed from CMake.

  Update the VERSION argument <min> value.  Or, use the <min>...<max> syntax
  to tell CMake that the project requires at least <min> but has been updated
  to work with policies introduced by <max> or earlier.

  Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway.

#1125614#10
Date:
2026-01-16 05:12:17 UTC
From:
To:
Ack that I saw this but I don't plan to fix anything in current
version, but waiting for new upstream release 1.0 and will import it
and fix everything at once with it.

#1125614#15
Date:
2026-01-24 05:56:17 UTC
From:
To:
I will fix the CMake 4.2 compatibility when I import the next version
of mydumper.

#1125614#20
Date:
2026-02-13 04:45:44 UTC
From:
To:
Ack that I saw this but I don't plan to fix anything in current
version, but waiting for new upstream release 1.0 and will import it
and fix everything at once with it.

Upstream should release very soon. Hopefully mydumper does not get
completely removed from Debian in the meanwhile.

#1125614#25
Date:
2026-03-01 05:00:00 UTC
From:
To:
According to https://github.com/mydumper/mydumper/milestone/62
upstream planned to release v1.0.1 on March 1st. Once that happens I
will import it into Debian and fix all issues. It does not make sense
for me to invest time in fixing the current v0.10 in Debian when
upstream most likely has all issues fixed in the new upstream version.