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

  • Bug#1106793: balboa: statically linked against glibc without a Built-Us

    From Aurelien Jarno@21:1/5 to All on Thu May 29 22:50:01 2025
    UGFja2FnZTogYmFsYm9hLWJhY2tlbmQtY29tbW9uClZlcnNpb246IDIuMC4wK2RzLTUKU2V2ZXJp dHk6IHNlcmlvdXMKSnVzdGlmaWNhdGlvbjogUG9saWN5IDcuOAoKRGVhciBtYWludGFpbmVyLAoK VGhlIGJhbGJvYSBwYWNrYWdlIHByb3ZpZGVzIC91c3IvYmluL2JhbGJvYS1iYWNrZW5kLWNvbnNv bGUgd2hpY2ggaXMKc3RhdGljYWxseSBsaW5rZWQgYWdhaW5zdCBnbGliYy4KCmdsaWJjIGlzIG1v c3RseSB1c2luZyBhIExHUEwgbGljZW5zZSB3aGljaCByZXF1aXJlcyB0aGF0IHRoZSBmdWxsIHNv dXJjZQpjb2RlIG9mIHRoZSBpbmNvcnBvcmF0aW5nIGJpbmFyeSBwYWNrYWdlIGJlIG1hZGUgYXZh aWxhYmxlLiBBY2NvcmRpbmcgdG8KRGViaWFuIFBvbGljeSDCpzcuOCBbMV0gc3VjaCBhIGJpbmFy eSBwYWNrYWdlIE1VU1QgbGlzdCB0aGUgZ2xpYmMgc291cmNlCnBhY2thZ2UgKGFuZCBwb3NzaWJs eSBvdGhlcnMpIGluIHRoZSBCdWlsdC1Vc2luZzogZmllbGQuCgpSZWdhcmRzCkF1cmVsaWVuCgpb MV0gaHR0cHM6Ly93d3cuZGViaWFuLm9yZy9kb2MvZGViaWFuLXBvbGljeS9jaC1yZWxhdGlvbnNo aXBzLmh0bWwjYWRkaXRpb25hbC1zb3VyY2UtcGFja2FnZXMtdXNlZC10by1idWlsZC10aGUtYmlu YXJ5LWJ1aWx0LXVzaW5nCg==

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Fri May 30 12:30:01 2025
    Processing control commands:

    tag -1 + patch
    Bug #1106793 [balboa-backend-common] balboa: statically linked against glibc without a Built-Using: field
    Added tag(s) patch.

    --
    1106793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106793
    Debian Bug Tracking System
    Contact [email protected] with problems

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Aurelien Jarno@21:1/5 to Aurelien Jarno on Sat May 31 14:20:01 2025
    Hi,

    On 2025-05-30 12:22, Aurelien Jarno wrote:
    control: tag -1 + patch

    Hi,

    On 2025-05-29 22:43, Aurelien Jarno wrote:
    Package: balboa-backend-common
    Version: 2.0.0+ds-5
    Severity: serious
    Justification: Policy 7.8

    Dear maintainer,

    The balboa package provides /usr/bin/balboa-backend-console which is statically linked against glibc.

    glibc is mostly using a LGPL license which requires that the full source code of the incorporating binary package be made available. According to Debian Policy ยง7.8 [1] such a binary package MUST list the glibc source package (and possibly others) in the Built-Using: field.

    Please find attached a patch to fix that issue.

    In the meantime I have been pointed out at dh-builtusing. Please find
    attached a patch with that alternative.

    Regards
    Aurelien

    --
    Aurelien Jarno GPG: 4096R/1DDD8C9B [email protected] http://aurel32.net

    --- balboa-2.0.0+ds/debian/control
    +++ balboa-2.0.0+ds/debian/control
    @@ -4,6 +4,7 @@
    Maintainer: Sascha Steinbiss <[email protected]>
    Build-Depends: debhelper-compat (= 13),
    dh-golang,
    + dh-sequence-builtusing,
    golang-go (>= 2:1.9),
    golang-github-machinebox-graphql-dev,
    golang-github-graph-gophers-graphql-go-dev,
    @@ -42,6 +43,7 @@
    Package: balboa-backend-common
    Architecture: any
    Depends: ${shlibs:Depends}, ${misc:Depends}
    +Built-Using: ${dh-builtusing:libc-dev-bin}
    Recommends: balboa
    Description: Common files for balboa backends
    balboa is the BAsic Little Book Of Answers. It consumes and indexes

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Debian Bug Tracking System@21:1/5 to All on Sun Jun 1 15:00:01 2025
    This is a multi-part message in MIME format...

    Your message dated Sun, 01 Jun 2025 12:48:59 +0000
    with message-id <[email protected]>
    and subject line Bug#1106793: fixed in balboa 2.0.0+ds-7
    has caused the Debian Bug report #1106793,
    regarding balboa: statically linked against glibc without a Built-Using: field 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 [email protected]
    immediately.)


    --
    1106793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1106793
    Debian Bug Tracking System
    Contact [email protected] with problems

    Received: (at submit) by bugs.debian.org; 29 May 2025 20:43:42 +0000 X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
    (2024-03-25) on buxtehude.debian.org
    X-Spam-Level:
    X-Spam-Status: No, score=-123.0 required=4.0 tests=BAYES_00,
    BODY_INCLUDES_PACKAGE,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,
    DKIM_VALID_AU,DKIM_VALID_EF,FOURLA,FROMDEVELOPER,HAS_PACKAGE,
    SPF_HELO_NONE,SPF_NONE,UNPARSEABLE_RELAY,USER_IN_DKIM_WELCOMELIST,
    XMAILER_REPORTBUG autolearn=ham autolearn_force=no
    version=4.0.1-bugs.debian.org_2005_01_02
    X-Spam-Bayes: score:0.0000 Tokens: new, 17; hammy, 150; neutral, 30; spammy,
    0. spammytokens:
    hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
    0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
    0.000-+--H*RT:311, 0.000-+--H*RT:108
    Return-path: <[email protected]>
    Received: from stravinsky.debia