Your message dated Fri, 27 Mar 2020 15:35:02 +0000
with message-id <e1jhr0g-000cny...@fasolo.debian.org>
and subject line Bug#951384: fixed in ck 0.6.0-1.3
has caused the Debian Bug report #951384,
regarding ck: FTBFS against glibc 2.30
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 ow...@bugs.debian.org
immediately.)
--
951384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951384
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ck
Version: 0.6.0-1.2
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch
Dear Maintainer,
ck fails to build from source against glibc 2.30, which is currently in
experimental. In Ubuntu, glibc 2.30 has been used since the last stable
release.
In Ubuntu, the attached patch was applied to achieve the following:
* d/p/glibc-2.30.patch: Apply patch from upstream to fix FTBFS against glibc
2.30.
Thanks for considering the patch.
Logan Rosen
-- System Information:
Debian Release: buster/sid
APT prefers eoan-updates
APT policy: (500, 'eoan-updates'), (500, 'eoan-security'), (500, 'eoan'),
(100, 'eoan-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.3.0-29-generic (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru ck-0.6.0/debian/patches/glibc-2.30.patch
ck-0.6.0/debian/patches/glibc-2.30.patch
--- ck-0.6.0/debian/patches/glibc-2.30.patch 1969-12-31 19:00:00.000000000
-0500
+++ ck-0.6.0/debian/patches/glibc-2.30.patch 2020-02-15 12:39:01.000000000
-0500
@@ -0,0 +1,52 @@
+From b520d58d00b7ed6c5cc9bc97c62f07e09f4f49ad Mon Sep 17 00:00:00 2001
+From: Samy Al Bahra <sba...@backtrace.io>
+Date: Tue, 29 Oct 2019 17:30:09 -0400
+Subject: [PATCH] regressions/common: rename gettid wrapper to common_gettid.
+
+glibc-2.30 added a wrapper to gettid (https://lwn.net/Articles/795127/).
+gettid will clash with the glibc-provided symbol. Remove the
+macro and instead move to a dedicated namespace.
+
+We go this route to avoid introducing unnecessary complexity to
+build.
+
+Fixes #147
+---
+ regressions/common.h | 8 +++-----
+ 1 file changed, 3 insertions(+), 5 deletions(-)
+
+--- a/regressions/common.h
++++ b/regressions/common.h
+@@ -267,13 +267,11 @@
+ #define AFFINITY_INITIALIZER {0, 0}
+
+ #ifdef __linux__
+-#ifndef gettid
+ static pid_t
+-gettid(void)
++common_gettid(void)
+ {
+ return syscall(__NR_gettid);
+ }
+-#endif /* gettid */
+
+ CK_CC_UNUSED static int
+ aff_iterate(struct affinity *acb)
+@@ -285,7 +283,7 @@
+ CPU_ZERO(&s);
+ CPU_SET(c % CORES, &s);
+
+- return sched_setaffinity(gettid(), sizeof(s), &s);
++ return sched_setaffinity(common_gettid(), sizeof(s), &s);
+ }
+
+ CK_CC_UNUSED static int
+@@ -297,7 +295,7 @@
+ CPU_ZERO(&s);
+ CPU_SET((*core) % CORES, &s);
+
+- return sched_setaffinity(gettid(), sizeof(s), &s);
++ return sched_setaffinity(common_gettid(), sizeof(s), &s);
+ }
+ #elif defined(__MACH__)
+ CK_CC_UNUSED static int
diff -Nru ck-0.6.0/debian/patches/series ck-0.6.0/debian/patches/series
--- ck-0.6.0/debian/patches/series 2019-11-21 03:36:35.000000000 -0500
+++ ck-0.6.0/debian/patches/series 2020-02-15 12:41:20.000000000 -0500
@@ -1 +1,2 @@
allow-disable-sse.patch
+glibc-2.30.patch
--- End Message ---
--- Begin Message ---
Source: ck
Source-Version: 0.6.0-1.3
Done: JCF Ploemen (jcfp) <li...@jcf.pm>
We believe that the bug you reported is fixed in the latest version of
ck, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 951...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
JCF Ploemen (jcfp) <li...@jcf.pm> (supplier of updated ck package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 27 Mar 2020 10:14:22 +0000
Source: ck
Architecture: source
Version: 0.6.0-1.3
Distribution: unstable
Urgency: medium
Maintainer: Robert Edmonds <edmo...@debian.org>
Changed-By: JCF Ploemen (jcfp) <li...@jcf.pm>
Closes: 951384
Changes:
ck (0.6.0-1.3) unstable; urgency=medium
.
* Non-maintainer upload.
* Backport upstream commit b520d58 to fix build failure against
glibc 2.30; patch provided by Logan Rosen. (Closes: #951384)
Checksums-Sha1:
301eeb3cda97551ab04ef2dd622c0ea7a7ad7b45 1922 ck_0.6.0-1.3.dsc
19a6226c68f5e1a09e65ab227008c79fff1fd2f8 5344 ck_0.6.0-1.3.debian.tar.gz
7a73292282247eca22ddef730de80ed325fefc51 5260 ck_0.6.0-1.3_source.buildinfo
Checksums-Sha256:
a4293d444169419971f717c156869cd524b32fc3a7d0c86b5a94acba62cf9332 1922
ck_0.6.0-1.3.dsc
ba2fd16ca7d9ae4a5040b75ce53a0abfcf5772c2628b8b7ddc8c7d83cd843f03 5344
ck_0.6.0-1.3.debian.tar.gz
1cdd8d01a0257ebdca5bb1c720fc2ef9d5908d43b22fa1d7dffb89c5254876cd 5260
ck_0.6.0-1.3_source.buildinfo
Files:
798fff647d2298bc587f6200776b9bf1 1922 libs optional ck_0.6.0-1.3.dsc
02c6394be213173159508c2b1badd20f 5344 libs optional ck_0.6.0-1.3.debian.tar.gz
f60b1470aab9591a76b3d255af824a86 5260 libs optional
ck_0.6.0-1.3_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl5+EKEACgkQweDZLphv
fH5agBAA9IQlLSRByYrpVv4u45VvUijCVKecUuwcFUJTTbNzQNSZhRgQ3h1lf6zX
o9iVA9avDCj9hAnMvvJ7mjjHctrwp9oHjIqgEobaf4ui2jkZyx4jusavOnlTn12Q
VME513kN+XECX3JacBytdC4oymk1SwG7fw3m8T3bsSkbmu7m3QiLFRHp6jmZkkvt
T96GqJJQKMQNjboaUA834oH4C1DqomR78Aa6ZeNerieWb9ujzmYaqt6qxFhh/iYc
hBeLZPwgqAIl7Ygr96Z35xytxvcwMOPcpGay188BOPhLMqjn2jeTqWGaYRLsRcl/
Il/zPzs3SCneWE/6x6FoVtgcDmQv9Coln9kkEEVr13XL7XnICwlO937v047cLBB1
xXOzHVMYN2XwaV6Y/5nLrXhGuRZMf5L98Yqm1Q900q0Svuh8M7ocSiNaXPcdW2VS
+jRdgMfsr+etvqgBIqpjCZmQJNc1F5OmEYfHbx4BFzpqJHZ1huMr8mnyWzEqZnxR
3dF4Q2GfQfj9wM+JBZlIG5b8k0oTzgVuMJZ8R3EFdCh6AbezYSJuvPJgj79pn8zf
zRGyKOkf05pMIJ0W7wckEQ3XWyZFcpaclrToJpkS1fbWZQq9AKYusnZ0zUU4ya+n
dPgQno3MtUG04treASTNm2mkF9QDTE9OrXfGmqKwMFCwPJG1y0g=
=o812
-----END PGP SIGNATURE-----
--- End Message ---
