1. Forum
  2. Usenet
  3. LINUX.DEBIAN.DEVEL.MENTOR

  • Re: Can't build mplayer (sbuild)

    From =?UTF-8?B?SsOpcsOpbXkgTGFs?=@21:1/5 to All on Sat Mar 22 22:10:01 2025
    Le sam. 22 mars 2025 à 21:56, Lorenzo <plorenzo@disroot.org> a écrit :

    Hello Mentors,

    I'm trying to build mplayer in sbuild to upload another version, https://salsa.debian.org/multimedia-team/mplayer/-/tree/next?ref_type=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 <plorenzo@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

    then I tested

    (this is schroot)
    sbuild-shell unstable-amd64-sbuild

    (inside the chroot)
    #apt-get install nasm #works fine
    #apt-get -s build-dep mplayer # installs 460 new packages, but still no issues

    then I tested with a fresh chroot tar and unshare, same error..

    I have no clues why sbuild fails, any idea?


    It works perfectly here (unshare backend).
    Could it be your copy of the repository that isn't clean ?
    Or apt-cacher-ng ?

    <div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">Le sam. 22 mars 2025 à 21:56, Lorenzo &lt;<a href="mailto:plorenzo@disroot.org">plorenzo@disroot.org</a>&gt; a écrit :<br></
    <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello Mentors,<br>

    I&#39;m trying to build mplayer in sbuild to upload another version,<br>
    <a href="https://salsa.debian.org/multimedia-team/mplayer/-/tree/next?ref_type=heads" rel="noreferrer" target="_blank">https://salsa.debian.org/multimedia-team/mplayer/-/tree/next?ref_type=heads</a><br>
    (note that it can be build in salsa CI)<br>

    $sbuild --source<br>

    this usually works, but now it fails with<br>

    dpkg-source: info: using patch list from debian/patches/series<br>
    dpkg-source: info: applying 0002_mplayer_debug_printf.patch<br>
    dpkg-source: info: applying 0201_PATH_MAX_HURD.patch<br>
    dpkg-source: info: applying 0202_glibc-2.27.patch<br>
    dpkg-source: info: applying 0203_generic-arch-fallback.patch<br>
    dpkg-source: info: applying 0204_fix-ftbfs-jack-ffmpeg7.patch<br> dpkg-buildpackage: info: source package mplayer<br>
    dpkg-buildpackage: info: source version 2:1.5+svn38674-2<br>
    dpkg-buildpackage: info: source distribution unstable<br>
    dpkg-buildpackage: info: source changed by Lorenzo Puliti<br>
    &lt;<a href="mailto:plorenzo@disroot.org" target="_blank">plorenzo@disroot.org</a>&gt; dpkg-checkbuilddeps: error: unmet build<br>
    dependencies: nasm dpkg-buildpackage: error: build<br>
    dependencies/conflicts unsatisfied; aborting dpkg-buildpackage: hint:<br> satisfy build dependencies with your package manager frontend<br>

    then I tested<br>

    (this is schroot)<br>
    sbuild-shell unstable-amd64-sbuild<br>

    (inside the chroot)<br>
    #apt-get install nasm  #works fine<br>
    #apt-get -s build-dep mplayer  # installs 460 new packages, but still no<br> issues<br>

    then I tested with a fresh chroot tar and unshare, same error..<br>

    I have no clues why sbuild fails, any idea?<br></blockquote><div><br></div><div>It works perfectly here (unshare backend).</div><div>Could it be your copy of the repository that isn&#39;t clean ?</div><div>Or apt-cacher-ng ?</div><div><br></div></div></


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lorenzo@21:1/5 to All on Sat Mar 22 22:00:02 2025
    Hello Mentors,

    I'm trying to build mplayer in sbuild to upload another version, https://salsa.debian.org/multimedia-team/mplayer/-/tree/next?ref_type=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 <plorenzo@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

    then I tested

    (this is schroot)
    sbuild-shell unstable-amd64-sbuild

    (inside the chroot)
    #apt-get install nasm #works fine
    #apt-get -s build-dep mplayer # installs 460 new packages, but still no
    issues

    then I tested with a fresh chroot tar and unshare, same error..

    I have no clues why sbuild fails, any idea?

    Best,
    Lorenzo

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Soren Stoutner@21:1/5 to All on Sat Mar 22 14:11:09 2025
    Copy: plorenzo@disroot.org (Lorenzo)

    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 <plorenzo@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
    soren@debian.org
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmffJ20ACgkQwufLJ66w tgNLDg/+MS7ssJQo7bhfZzC6rUP89Nwh03x6F14fhUoDEXqphJao9TrnqeZvy+sw X8C1DEngb5SUGK2yr0KFqaOJgY3430VlvS1P3OhLbXG1C0I1nCOl7UEx4EjNxPni kFKdCcjSSfdUwnxpgKJmjgZT4gEoo0nUvDiyU4aeBTokQnfxzbQbn2R0aypyBvm1 LlVnczVidbjRCyU0iLE1Cqs8Z94Bv8zFlixX1nfwRv7B5a00bds65S2QpSdJNf6S TpQuxiJDy6cWuro3adPSNoeSr64sljaSgSItovOL4v5h00mTSAlGKljeS8b8DkQV tDCQk24bRzvCVw2C1B3K6wqYo9Ya6S82wiWELY0qngr9U2dnX8CoaEOKcQmrn7Ux yoP/DJG9JG84qG6UlrhFvevh06iLY9R4DqKvMiBo+V1DRMXVmK8FDPwxlLZYHPcX j5OPxpzGgA9gs/t6fQjLu51s2I4PzziJjKeOjM7yhjsu87BtPtdKQb1FmKGjB7zB BURAYtBZwuXQMriTzjN5EsWt28HWtucjvrmPSNBVfvKscA2F4rUR6+ISJq+TplyM PCg8NTNqsSkhhqNWU68Wke4OSmD5GwnRCHk3/WUQyFkhQJ4Xn5P5t+JelI/n7dFF zOo7l5vd9kRzLsIRkBvhDtU2h0kAW9YFwjLfBspx95Z5TrGAdLA=
    =5QnL
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lorenzo@21:1/5 to Soren Stoutner on Sat Mar 22 23:00:02 2025
    Soren, Jérémy,

    thanks for your help.

    On Sat, 22 Mar 2025 14:11:09 -0700
    Soren Stoutner <soren@debian.org> wrote:


    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.


    yes that's the issue.
    I'm now having a look at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088269

    Best,
    Lorenzo

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)