1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.DIST

  • Bug#1103054: devscripts: debbisect gives ERROR:root:./debbisect.2025041

    From Santiago Vila@21:1/5 to All on Mon Apr 14 12:40:01 2025
    This is a multi-part message in MIME format.
    Package: devscripts
    Version: 2.25.8~bpo12+1

    Hi.

    While playing with my not-yet-finished --reverse option
    for debbisect I found an issue which also happens with
    regular debbisect in the current package (at least the one
    in bookworm-backports).

    I'm running the following script:

    #!/bin/sh
    PACKAGE=resampy
    GOOD="20250413T085924Z"
    BAD="20250413T204319Z"
    DEBIAN_BISECT_SRCPKG=${PACKAGE} debbisect --cache=./cache \
    "${GOOD}" "${BAD}" $HOME/bin/debbisect_buildsrc_inverted.sh


    where "debbisect_buildsrc_inverted.sh" is attached.
    (It's just debbisect_buildsrc.sh but with exit status swapped).

    This is the outcome:

    bisection finished successfully
    last good timestamp: 20250413T150122Z
    first bad timestamp: 20250413T204319Z ERROR:root:./debbisect.20250413T150122Z.pkglist doesn't exist


    I hope this is not a bug in snapshot.debian.org (in one of those
    timestamps), because it would mean it will not have an easy fix.

    (Note: resampy has a very small build time, so don't be afraid of
    trying the script yourself)

    Thanks. IyEvYmluL3NoCiMKIyB1c2UgdGhpcyBzY3JpcHQgdG8gYnVpbGQgYSBzb3VyY2UgcGFja2Fn ZSB3aXRoIGRlYmJpc2VjdCBsaWtlIHRoaXM6CiMKIyAgICAkIERFQklBTl9CSVNFQ1RfU1JD UEtHPW15c3JjIC4vZGViYmlzZWN0IC0tY2FjaGU9Li9jYWNoZSAidHdvIHllYXJzIGFnbyIg eWVzdGVyZGF5IC91c3Ivc2hhcmUvZG9jL2RldnNjcmlwdHMvZXhhbXBsZXMvZGViYmlzZWN0 X2J1aWxkc3JjLnNoCiMKIyBjb3B5IHRoaXMgc2NyaXB0IGFuZCBlZGl0IGl0IGlmIHlvdSB3 YW50IHRvIGN1c3RvbWl6ZSBpdAoKc2V0IC1ldQoKaWYgbW1kZWJzdHJhcCAtLXZhcmlhbnQ9 YXB0IHVuc3RhYmxlIFwKLS1hcHRvcHQ9J0FwdDo6S2V5OjpncGd2Y29tbWFuZCAiL3Vzci9z aGFyZS9kZWJ1ZXJyZW90eXBlL3NjcmlwdHMvLmdwZ3YtaWdub3JlLWV4cGlyYXRpb24uc2gi JyBcCi0tYXB0b3B0PSdBY3F1aXJlOjpDaGVjay1WYWxpZC1VbnRpbCAiZmFsc2UiJyBcCi0t Y3VzdG9taXplLWhvb2s9J2Nocm9vdCAiJDEiIGFwdC1nZXQgLS15ZXMgYnVpbGQtZGVwICci JERFQklBTl9CSVNFQ1RfU1JDUEtHIiBcCi0tY3VzdG9taXplLWhvb2s9J2Nocm9vdCAiJDEi IHNoIC1jICJkcGtnLXF1ZXJ5IC1XID4gL3BrZ2xpc3QiJyBcCi0tY3VzdG9taXplLWhvb2s9 J2Rvd25sb2FkIC9wa2dsaXN0IC4vZGViYmlzZWN0LiciJERFQklBTl9CSVNFQ1RfVElNRVNU QU1QIicucGtnbGlzdCcgXAotLWN1c3RvbWl6ZS1ob29rPSdybSAiJDEiL3BrZ2xpc3QnIFwK LS1jdXN0b21pemUtaG9vaz0iY2hyb290IFwiXCQxXCIgZHBrZy1xdWVyeSAtLXNob3dmb3Jt YXQgJ1wke2JpbmFyeTpQYWNrYWdlfT1cJHtWZXJzaW9ufVxuJyAtLXNob3ciIFwKLS1jdXN0 b21pemUtaG9vaz0nY2hyb290ICIkMSIgYXB0LWdldCBzb3VyY2UgLS1idWlsZCAnIiRERUJJ QU5fQklTRUNUX1NSQ1BLRyIgXAovZGV2L251bGwgJERFQklBTl9CSVNFQ1RfTUlSUk9SICJk ZWItc3JjICRERUJJQU5fQklTRUNUX01JUlJPUiB1bnN0YWJsZSBtYWluIjsgdGhlbgogIGV4 aXQgMQplbHNlCiAgZXhpdCAwCmZpCg==

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Santiago Vila@21:1/5 to All on Mon Apr 14 12:50:02 2025
    Ok, here is the explanation.

    By looking at old build logs I had, this is what happens:

    The following packages have unmet dependencies:
    python3-numba : Depends: python3 (< 3.13) but 3.13.2-2 is to be installed
    Depends: python3-numpy-abi9 but it is not installable
    E: Unable to correct problems, you have held broken packages.
    E: The following information from --solver 3.0 may provide additional context:
    Unable to satisfy dependencies. Reached two conflicting decisions:
    1. python3-numba:amd64 is selected for install because:
    1. sbuild-build-depends-main-dummy:amd64=0.invalid.0 is selected for install
    2. sbuild-build-depends-main-dummy:amd64 Depends python3-numba (>= 0.53)
    2. python3-numba:amd64 Depends python3 (< 3.13)
    but none of the choices are installable:
    [no choices]
    apt-get failed.
    E: Package installation failed
    Not removing build depends: cloned chroot in use


    So I would agree this does not have an easy fix, as the only
    information provided by the test script is a simple yes/no.

    Thanks.

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