1. Forum
  2. Usenet
  3. LINUX.DEBIAN.MAINT.EMACSE

  • Bug#1044760: embark: Fails to build source after successful build

    From Lucas Nussbaum@21:1/5 to All on Sun Aug 13 19:50:12 2023
    XPost: linux.debian.bugs.dist

    Source: embark
    Version: 0.21-1
    Severity: minor
    Tags: trixie sid ftbfs
    User: lucas@debian.org
    Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
    User: debian-qa@lists.debian.org
    Usertags: qa-doublebuild

    Hi,

    This package fails to build a source package after a successful build (dpkg-buildpackage ; dpkg-buildpackage -S).

    This is probably a clear violation of Debian Policy section 4.9 (clean target), but this is filed as severity:minor for now, because a discussion on debian-devel showed that we might want to revisit the requirement of a working 'clean' target.

    More information about this class of issues, included common problems and solutions, is available at https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild

    Relevant part of the build log:
    cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -S
    ------------------------------------------------------------------------------------------------------------------

    dpkg-buildpackage: info: source package embark
    dpkg-buildpackage: info: source version 0.21-1
    dpkg-buildpackage: info: source distribution unstable
    dpkg-buildpackage: info: source changed by Aymeric Agon-Rambosson <aymeric.agon@yandex.com>
    dpkg-source --before-build .
    debian/rules clean
    dh clean --with elpa
    debian/rules override_dh_auto_clean
    make[1]: Entering directory '/<<PKGBUILDDIR>>'
    rm -f embark.info embark.html.gz
    test -f embark.texi.orig && mv embark.texi.orig embark.texi || true
    make[1]: Leaving directory '/<<PKGBUILDDIR>>'
    dh_clean
    dpkg-source -b .
    dpkg-source: info: using source format '3.0 (quilt)'
    dpkg-source: info: building embark using existing ./embark_0.21.orig.tar.gz dpkg-source: info: using patch list from debian/patches/series
    dpkg-source: warning: file embark-0.21/embark.html has no final newline (either original or modified version)
    dpkg-source: info: local changes detected, the modified files are:
    embark-0.21/embark.html
    dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/embark_0.21-1.diff.XRm9JE
    dpkg-source: info: Hint: make sure the version in debian/changelog matches the unpacked source tree
    dpkg-source: info: you can integrate the local changes with dpkg-source --commit
    dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2

    E: Command 'cd /<<PKGBUILDDIR>> && runuser -u user42 -- dpkg-buildpackage --sanitize-env -us -uc -rfakeroot -S' failed to run.


    The full build log is available from: http://qa-logs.debian.net/2023/08/13/embark_0.21-1_unstable.log

    If you reassign this bug to another package, please mark it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects

    If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Fri Oct 20 05:30:01 2023
    This is a multi-part message in MIME format...

    Your message dated Fri, 20 Oct 2023 03:20:38 +0000
    with message-id <E1qtg3y-00A9PN-9H@fasolo.debian.org>
    and subject line Bug#1044760: fixed in embark 0.23-1
    has caused the Debian Bug report #1044760,
    regarding embark: Fails to build source after successful build
    to be marked as done.

    This means that you claim that the problem has been dealt with.
    If this is not the case it is now your responsibility to reopen the
    Bug report if necessary, and/or fix the problem forthwith.

    (NB: If you are a system administrator and have no idea what this
    message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org
    immediately.)


    --
    1044760: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044760
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems

    Received: (at submit) by bugs.debian.org; 13 Aug 2023 17:37:44 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
    (2021-04-09) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-103.2 required=4.0 tests=ATTENDEES_DBSPAM_BODY3,
    ATTENDEES_DBSPAM_BODY7,BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
    DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,MURPHY_DRUGS_REL8,
    SPF_HELO_NONE,SPF_NONE,UNPARSEABLE_RELAY,USER_IN_DKIM_WELCOMELIST,
    USER_IN_DKIM_WHITELIST autolearn=ham autolearn_force=no
    version=3.4.6-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 35; hammy, 150; neutral, 151; spammy,
    0. spammytokens: hammytokens:0.000-+--pkgbuilddir,
    0.000-+--PKGBUILDDIR, 0.000-+--Hx-spam-relays-external:sk:stravin,
    0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311 Return-path: <lucas@debian.org>