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

  • Bug#1106803: liblxc-common: statically linked against glibc without a B

    From Aurelien Jarno@21:1/5 to All on Thu May 29 23:00:02 2025
    UGFja2FnZTogbGlibHhjLWNvbW1vbgpWZXJzaW9uOiAxOjUuMC4yLTEKU2V2ZXJpdHk6IHNlcmlv dXMKSnVzdGlmaWNhdGlvbjogUG9saWN5IDcuOAoKRGVhciBtYWludGFpbmVyLAoKVGhlIGxpYmx4 Yy1jb21tb24gcGFja2FnZSBwcm92aWRlcyAvdXNyL3NiaW4vaW5pdC5seGMuc3RhdGljIHdoaWNo IGlzCnN0YXRpY2FsbHkgbGlua2VkIGFnYWluc3QgZ2xpYmMuCgpnbGliYyBpcyBtb3N0bHkgaXMg bW9zdGx5IGxpY2Vuc2VkIHVuZGVyIHRoZSBMR1BMLCB3aGljaCByZXF1aXJlcyB0aGF0CnRoZSBm dWxsIHNvdXJjZSBjb2RlIG9mIHRoZSBpbmNvcnBvcmF0aW5nIGJpbmFyeSBwYWNrYWdlIGJlIG1h ZGUKYXZhaWxhYmxlLiBBY2NvcmRpbmcgdG8gRGViaWFuIFBvbGljeSDCpzcuOCBbMV0gc3VjaCBh IGJpbmFyeSBwYWNrYWdlCk1VU1QgbGlzdCB0aGUgZ2xpYmMgc291cmNlIHBhY2thZ2UgKGFuZCBw b3NzaWJseSBvdGhlcnMpIGluIHRoZQpCdWlsdC1Vc2luZzogZmllbGQuCgpSZWdhcmRzCkF1cmVs aWVuCgpbMV0gaHR0cHM6Ly93d3cuZGViaWFuLm9yZy9kb2MvZGViaWFuLXBvbGljeS9jaC1yZWxh dGlvbnNoaXBzLmh0bWwjYWRkaXRpb25hbC1zb3VyY2UtcGFja2FnZXMtdXNlZC10by1idWlsZC10 aGUtYmluYXJ5LWJ1aWx0LXVzaW5nCg==

    --- 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:10:01 2025
    Processing control commands:

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

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

    --- 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 15:30:01 2025
    This is a multi-part message in MIME format...

    Your message dated Fri, 30 May 2025 13:19:31 +0000
    with message-id <[email protected]>
    and subject line Bug#1106803: fixed in lxc 1:6.0.4-4
    has caused the Debian Bug report #1106803,
    regarding liblxc-common: 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.)


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

    Received: (at submit) by bugs.debian.org; 29 May 2025 20:53:39 +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, 15; hammy, 150; neutral, 34; 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