From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 0F6746DE0EED for ; Fri, 10 Jan 2020 15:16:46 -0800 (PST) Authentication-Results: arlo.cworth.org; dkim=permerror (0-bit key) header.d=fifthhorseman.net header.i=@fifthhorseman.net header.b="JI9vsusC"; dkim=pass (2048-bit key; unprotected) header.d=fifthhorseman.net header.i=@fifthhorseman.net header.b="VD7zLDnO"; dkim-atps=neutral X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -1.563 X-Spam-Level: X-Spam-Status: No, score=-1.563 tagged_above=-999 required=5 tests=[AWL=0.938, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T_JlRyyaacX2 for ; Fri, 10 Jan 2020 15:16:44 -0800 (PST) Received: from che.mayfirst.org (che.mayfirst.org [162.247.75.118]) by arlo.cworth.org (Postfix) with ESMTPS id 0CE096DE0C45 for ; Fri, 10 Jan 2020 15:16:43 -0800 (PST) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019; t=1578698202; h=from : to : cc : subject : in-reply-to : references : date : message-id : mime-version : content-type : from; bh=cPI3SC9+KR6JtY3DWooQFhL/4Z+CXNxjmAJjdytm6tM=; b=JI9vsusC90FqG+425dVzfn4mcY1u7mGaS/tU54Slcj/VknF7sIUecMZx tWzTJwVcyu0V+edY2xJwVTJ1e0pCDg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019rsa; t=1578698202; h=from : to : cc : subject : in-reply-to : references : date : message-id : mime-version : content-type : from; bh=cPI3SC9+KR6JtY3DWooQFhL/4Z+CXNxjmAJjdytm6tM=; b=VD7zLDnOTMKr/La7tXOW5mCxn5QOWWmy0cdzlQJ4XPVyN01/BUPxAq8i 3S62Vpnwfb4jE073WF+bgthKo3cBrzpr5yjY1skGSlnRJIe4PEftPry6H/ ldGNF/2gwVuGEVqi84L+Hhl9ufew6hF9K2xHyka0iIgj2RS0CWWuWLcXMu jMjG937+7mtNScSjNWtNJoQeNBIJNsMFWCVkcbGdlFOHOaKf7e6MdICDgH /z7c6LLLNTPU2ThUrtzItGrjG1Rxm6ZCbcdr+5J4kaMPURCfFZvFa+FYrx oQfbb8w25PuonWAZTNQhNAWGCSMOBWCkI2Fgaf0YW/4qb1+yNiwiHw== Received: from fifthhorseman.net (unknown [38.109.115.130]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by che.mayfirst.org (Postfix) with ESMTPSA id 41C0DF9A5; Fri, 10 Jan 2020 18:16:40 -0500 (EST) Received: by fifthhorseman.net (Postfix, from userid 1000) id 2F0AD202C1; Fri, 10 Jan 2020 18:16:38 -0500 (EST) From: Daniel Kahn Gillmor To: David Bremner , Notmuch Mail Cc: Antoine =?utf-8?Q?Beaupr=C3=A9?= Subject: Re: [PATCH] debian: Add packaging for python3-notmuch2 In-Reply-To: <87a76vkm2d.fsf@fifthhorseman.net> References: <20191223221722.360349-1-dkg@fifthhorseman.net> <87muax626r.fsf@fifthhorseman.net> <87r2083uk5.fsf@tethera.net> <87lfqfkouo.fsf@fifthhorseman.net> <87a76vkm2d.fsf@fifthhorseman.net> Autocrypt: addr=dkg@fifthhorseman.net; prefer-encrypt=mutual; keydata= mDMEXEK/AhYJKwYBBAHaRw8BAQdAr/gSROcn+6m8ijTN0DV9AahoHGafy52RRkhCZVwxhEe0K0Rh bmllbCBLYWhuIEdpbGxtb3IgPGRrZ0BmaWZ0aGhvcnNlbWFuLm5ldD6ImQQTFggAQQIbAQUJA8Jn AAULCQgHAgYVCgkICwIEFgIDAQIeAQIXgBYhBMS8Lds4zOlkhevpwvIGkReQOOXGBQJcQsbzAhkB AAoJEPIGkReQOOXG4fkBAO1joRxqAZY57PjdzGieXLpluk9RkWa3ufkt3YUVEpH/AP9c+pgIxtyW +FwMQRjlqljuj8amdN4zuEqaCy4hhz/1DbgzBFxCv4sWCSsGAQQB2kcPAQEHQERSZxSPmgtdw6nN u7uxY7bzb9TnPrGAOp9kClBLRwGfiPUEGBYIACYWIQTEvC3bOMzpZIXr6cLyBpEXkDjlxgUCXEK/ iwIbAgUJAeEzgACBCRDyBpEXkDjlxnYgBBkWCAAdFiEEyQ5tNiAKG5IqFQnndhgZZSmuX/gFAlxC v4sACgkQdhgZZSmuX/iVWgD/fCU4ONzgy8w8UCHGmrmIZfDvdhg512NIBfx+Mz9ls5kA/Rq97vz4 z48MFuBdCuu0W/fVqVjnY7LN5n+CQJwGC0MIA7QA/RyY7Sz2gFIOcrns0RpoHr+3WI+won3xCD8+ sVXSHZvCAP98HCjDnw/b0lGuCR7coTXKLIM44/LFWgXAdZjm1wjODbg4BFxCv50SCisGAQQBl1UB BQEBB0BG4iXnHX/fs35NWKMWQTQoRI7oiAUt0wJHFFJbomxXbAMBCAeIfgQYFggAJhYhBMS8Lds4 zOlkhevpwvIGkReQOOXGBQJcQr+dAhsMBQkB4TOAAAoJEPIGkReQOOXGe/cBAPlek5d9xzcXUn/D kY6jKmxe26CTws3ZkbK6Aa5Ey/qKAP0VuPQSCRxA7RKfcB/XrEphfUFkraL06Xn/xGwJ+D0hCw== Date: Fri, 10 Jan 2020 18:16:37 -0500 Message-ID: <871rs6lx62.fsf@fifthhorseman.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jan 2020 23:16:46 -0000 --=-=-= Content-Type: text/plain On Fri 2020-01-10 17:01:46 -0500, Daniel Kahn Gillmor wrote: > using diffoscope to compare these objects with the one i built back in > December shows that the December object has a .gnu_debugaltlink section, > but these new objects do not. (so there appears to be a bit more > leftover debugging info in the december objects) Sorry, i got this precisely backward. The difference is that the newer shared objects *have* a .gnu_debugaltlink section, but the one built in december does not. I took one more step at debugging the newly-built modules to try to understand why the non-stripped versions might differ, and noticed that the debugging info in each module itself is different. in particular, in the 3.7 module, the debugging info contains different paths: -./bindings/python-cffi/build/temp.linux-amd64-3.7/notmuch2._capi.c:1272 +./bindings/python-cffi/build/temp.linux-amd64-3.8/notmuch2._capi.c:1272 (notmuch2._capi.c is a generated C file here, iiuc) so maybe the build-id is being generated based on the contents of the debug info, in addition to the contents of the stripped-down data? If that's the case, then what's surprising to me is that i *didn't* see this happening when i built it in december. Very confusing, and i'd appreciate another set of eyeballs on it. all that debugging said and done, i don't think that this weirdness should block us from including the package in debian. If anything, getting it into the debian build infrastructure will expose this weirdness to other people more directly, and might help to iron out some more fundamental issue with either cffi itself, dh-python3's deduplication strategies for shared objects, and/or debian's policies about stripped data and binaries. Shipping the extra .so in a python3-notmuch2 package doesn't appear to be a problem for notmuch itself, because the difference between the .so's shouldn't be relevant for any functional concerns. If we do merge this and get it into debian, then i'll be able to open a more specific bug report with the aforementioned packages. --dkg --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQTJDm02IAobkioVCed2GBllKa5f+AUCXhkF1QAKCRB2GBllKa5f +BWIAP4z/eWSOiwycNBvKygWxrZmZ4qjjsV9lwt31mXzsUpRhwD/bGTc56056vrn DIsX/9YNJH1SAMK2/gys8HZyQT40FQ8= =3O/P -----END PGP SIGNATURE----- --=-=-=--