Path: csiph.com!news.neodome.net!news.samoylyk.net!gothmog.csi.it!bofh.it!news.nic.it!robomod From: Rene Engelhard Newsgroups: linux.debian.maint.python Subject: Re: hashlib and sha384 Date: Sun, 31 May 2026 13:30:01 +0200 Message-ID: References: X-Original-To: Andrey Rakhmatullin , debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Sun May 31 11:27:42 2026 Old-Return-Path: X-Amavis-Spam-Status: No, score=-106.455 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, BODY_8BITS=1.5, DKIMWL_WL_HIGH=-0.445, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, LDO_WHITELIST=-5, RCVD_IN_DNSWL_MED=-2.3, SUBENDNUM=2, USER_IN_DKIM_WELCOMELIST=-0.01, USER_IN_DKIM_WHITELIST=-100] autolearn=ham autolearn_force=no MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-GB Organization: Debian Project Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Debian-User: rene X-Mailing-List: archive/latest/23796 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/fb19f303-14f0-4610-a2d9-cd297de9ebdd@debian.org Approved: robomod@news.nic.it Lines: 56 Sender: robomod@news.nic.it X-Original-Date: Sun, 31 May 2026 13:27:22 +0200 X-Original-Message-ID: X-Original-References: <2fed898a-280d-4f88-b6f8-c2bbbdb53e83@debian.org> Xref: csiph.com linux.debian.maint.python:17512 Hi, Am 31.05.26 um 11:30 schrieb Andrey Rakhmatullin: > On Sun, May 31, 2026 at 11:07:08AM +0200, Rene Engelhard wrote: >>>>  File "/usr/lib/python3/dist-packages/hypothesis/internal/conjecture/utils.py", line 35, in calc_label_from_name >>>>    hashed = hashlib.sha384(name.encode()).digest() >>>>             ~~~~~~~~~~~~~~^^^^^^^^^^^^^^^ >>>> _hashlib.UnsupportedDigestmodError: unsupported hash type sha384 >>>> >>>> happens. (for both 3.13 and 3.14) >>>> >>>> From what I read in https://docs.python.org/3/library/hashlib.html sha384 should have been supported in python anyways and >>>> xmlsec1s build has >>>> checking for SHA384 support... yes >>>> (if it even matters, python3s _hashlib doesn't use xmlsec..) >>> >>> Considering that sha384(b'').digest() works for me in sid Python you may want to describe your environment better. E.g. do you have anything from experimental installed (like the aforementioned openssl 4)? Is it a clean chroot? > > 1: >> all kinds of build-depends of LO (and other packages) as in my standard systemd-nspawn "working sid machine". >> >> (and yes, xmlsec1 from experimental, since that is the point of this test.,.. No, no openssl 4 yet.) > > 2: >> Indeed it works in a clean deboostrap unstable + apt build-dep python-xmlsec + add experimental  to s.l. + apt -t experimental libxmlsec1-dev chroot... > > Are the only differences between 1 and 2 that 1 has some more build-deps installed? That's weird. It is. But I can reproduce it with the following: - debootstrap clean unstable, add deb-src (and mount /proc) - apt build-dep python-xmlsec works - add experimental  to s.l. + apt -t experimental libxmlsec1-dev works (with the mentioned patch) - apt build-dep libreoffice still works - apt build-dep apache-arrow [1] -> boom Regards, Rene [1] http://people.debian.org/~rene/apache-arrow-apt-build-dep.log