[mythtv-users] errors on build of mythtv v34 Debain 12 packages after recent updates

David Hampton mythtv at love2code.net
Fri Feb 9 00:53:47 UTC 2024


On Thu, 2024-02-08 at 16:11 -0500, David Hampton wrote:
> On Thu, 2024-02-08 at 20:33 +0100, Roland Ernst wrote:
> > 
> > On Thu, Feb 8, 2024 at 8:11 PM Roland Ernst <rcrernst at gmail.com>
> > wrote:
> > > 
> > > 
> > > On Thu, Feb 8, 2024 at 7:56 PM Roland Ernst <rcrernst at gmail.com>
> > > wrote:
> > > > 
> > > > On Thu, Feb 8, 2024 at 12:36 PM James Abernathy
> > > > <jfabernathy at gmail.com> wrote:
> > > > > I've been rebuilding the packages of Mythtv master for Debian
> > > > > 12 after I saw Ubuntu  22.04 mythtv packages change.
> > > > > 
> > > > > That worked yesterday morning, but today after some cmake
> > > > > updates I get errors pretty close to the beginning  of the
> > > > > build.  I'm using the wiki method for building the Debian
> > > > > packages.
> > > > > 
> > > > > here's the console log
> > > > > 
> > > > > #build the tarball
> > > > > ....
> > > > >  dpkg-source -i -I.git -b .
> > > > > dpkg-source: info: using options from
> > > > > mythtv/debian/source/options: --extend-diff-
> > > > > ignore=.github|.dockerig
> > > > > nore|.clang-tidy|.clazy
> > > > > dpkg-source: info: using source format '3.0 (quilt)'
> > > > > dpkg-source: info: building mythtv using existing
> > > > > ./mythtv_34.0~master.20240208.93e52a62.orig.tar.gz
> > > > > dpkg-source: info: using patch list from
> > > > > debian/patches/series
> > > > > dpkg-source: info: local changes detected, the modified files
> > > > > are:
> > > > >  mythtv/.cmake-format.py
> > > > >  mythtv/.cppcheck-includes
> > > > >  mythtv/.cppcheck-suppress
> > > > > dpkg-source: error: aborting due to unexpected upstream
> > > > > changes, see /tmp/mythtv_34.0~master.20240208.93e5
> > > > > 2a62-0ubuntu0.diff.ISOrKD
> > > > > 
> > > > 
> > > > 
> > > > 
> > > > The log already shows a hint how to solve this error: 
> > > > Add these 3 modified files to the file 
> > > > packaging/deb/debian/source/options
> > > > by using the same syntax as given by the file itself:
> > > > extend-diff-ignore=.github|.dockerignore|.clang-
> > > > tidy|.clazy|.cmake-format.py|.cppcheck-includes|.cppcheck-
> > > > suppress
> > > > 
> > > > It is the same issue as previouslywith the '.clazy' file:
> > > >  
> > > > https://github.com/MythTV/packaging/commit/2f9f4b97cdcbebf479d1534
> > > > 3dd5fd140f8daddc9
> > > > It does not affect the lauchpad build at 
> > > > https://launchpad.net/~mythbuntu/+archive/ubuntu/34
> > > > 
> > > > 2:34.0~master.202402081705.1f5dfbce31~ubuntuxx.yy.z
> > > > was build successfully a couple of minutes ago.
> > > > 
> > > > @Jim A: could you please verify above change on debian?
> > > > Roland
> > > > 
> > > > 
> > > 
> > > 
> > > 
> > > Sorry, 
> > > build at launchpad failed but with a different error:
> > > fatal: not a git repository (or any of the parent directories):
> > > .git
> > > 
> > > Roland
> > > 
> > 
> > 
> > And being more explicitly:
> > dh_autoconfigure wants to execute 'cmake'
> >    dh_auto_configure
> > 	cd obj-x86_64-linux-gnu && DEB_PYTHON_INSTALL_LAYOUT=deb
> > 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 ..
> > Can't exec "cmake": No such file or directory at
> > /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 518.
> > Not amused,  
> > Roland
> 
> Why has build-debs.sh suddenly decided it needs to run cmake instead
> of
> configure/make?
> 
> Not amused.
> 
> I see that the debhelper command has an option to tell it which build
> system to use, but I don't see where debhelper is called.
> 
> I'm working on it.

Ok.  I had to do the following:

1) Ignore the extra files like you mentioned, Roland.

2) Override the automatic configuration step so that the scripts
wouldn't try and run cmake.

After doing these two things, my test debian build ran to completion. 
Sorry it took so long; its was a complete compile for the first time on
a slow VM.

Once you update your packaging repo you should be able to build again.

David




More information about the mythtv-users mailing list