Source: transmission
Version: 4.0.5-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=transmission&arch=armel&ver=4.0.5-1%2Bb1&stamp=1711181507&raw=0

/usr/bin/ld: ../../libtransmission/libtransmission.a(web.cc.o): undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0'
/usr/bin/ld: /lib/arm-linux-gnueabi/libatomic.so.1: error adding symbols: DSO missing from command line


-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

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

Hi,

/usr/bin/ld: ../../libtransmission/libtransmission.a(web.cc.o): undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0'
/usr/bin/ld: /lib/arm-linux-gnueabi/libatomic.so.1: error adding symbols: DSO missing from command line

As transmission does not link directly to libatomic, it is likely that
this bug should be reassigned to the dependency that brings in libatomic,
maybe gcc.

Thanks,

Alex

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

This is a multi-part message in MIME format...

Your message dated Sun, 07 Apr 2024 19:51:52 +0000
with message-id <E1rtYYS-008qz0-CH@fasolo.debian.org>
and subject line Bug#1067625: fixed in transmission 4.0.5-2
has caused the Debian Bug report #1067625,
regarding FTBFS on armel: undefined reference to symbol '__atomic_load_8@@LIBATOMIC_1.0'
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.)


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

Received: (at submit) by bugs.debian.org; 24 Mar 2024 19:30:27 +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=-8.0 required=4.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,FORGED_SPF_HELO,FOURLA,FROMDEVELOPER,SPF_HELO_PASS,SPF_NONE,
XMAILER_REPORTBUG autolearn=ham autolearn_force=no
version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 19; hammy, 150; neutral, 73; spammy,
0. spammytokens: hammytokens:0.000-+--sk:buildd.,
0.000-+--UD:buildd.debian.org, 0.000-+--buildddebianorg,
0.000-+--buildd.debian.org, 0.000-+--trixie
Return-path: <wrar@debian.org>
Received: from wrar.name ([116.203.248.210]:55682 helo=durkon.wrar.name)
by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256