On Saturday, March 22, 2025 1:55:27 PM Mountain Standard Time Lorenzo wrote: > Hello Mentors, > > I'm trying to build mplayer in sbuild to upload another version, > https://salsa.debian.org/multimedia-team/mplayer/-/tree/next?ref_typ > e=heads (note that it can be build in salsa CI) > > $sbuild --source > > this usually works, but now it fails with > > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: applying 0002_mplayer_debug_printf.patch > dpkg-source: info: applying 0201_PATH_MAX_HURD.patch > dpkg-source: info: applying 0202_glibc-2.27.patch > dpkg-source: info: applying 0203_generic-arch-fallback.patch > dpkg-source: info: applying 0204_fix-ftbfs-jack-ffmpeg7.patch > dpkg-buildpackage: info: source package mplayer > dpkg-buildpackage: info: source version 2:1.5+svn38674-2 > dpkg-buildpackage: info: source distribution unstable > dpkg-buildpackage: info: source changed by Lorenzo Puliti > <plore...@disroot.org> dpkg-checkbuilddeps: error: unmet build > dependencies: nasm dpkg-buildpackage: error: build > dependencies/conflicts unsatisfied; aborting dpkg-buildpackage: > hint: satisfy build dependencies with your package manager frontend
I have been bit by this before, and it wasn’t apparent to me what the problem was until someone kindly explained it to me. The answer is that you need to install nasm on your main system, because all the packages listed in the build-depends have to be installed to run the clean target, which happens on your main system before sbuild starts the chroot. Probably you had it installed on your main system at some point in the past and it was recently removed. -- Soren Stoutner so...@debian.org
signature.asc
Description: This is a digitally signed message part.
