From: alandiwix <alandiwix@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] hplip: incompatibility with python3.10
Date: Fri, 22 Oct 2021 16:02:34 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33700@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
New issue by alandiwix on void-packages repository
https://github.com/void-linux/void-packages/issues/33700
Description:
See https://bugs.launchpad.net/hplip/+bug/1933973
There are several issues in hplip codebase, the one I encounter personally is:
```
Scanning...
Exception in thread Thread-1:
Traceback (most recent call last):
File "/usr/lib/python3.10/threading.py", line 1009, in _bootstrap_inner
self.run()
File "/usr/share/hplip/scan/sane.py", line 548, in run
st, t = self.dev.readScan(readbuffer)
SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats
Reading data: [\
```
The error
```
SystemError: PY_SSIZE_T_CLEAN macro must be defined for '#' formats
```
is common among those. Some other distributions managed to solve that, Fedora's patch for example:
https://launchpadlibrarian.net/546031954/hplip-pyssizet_clean.patch
Is it possible to do the same in Void?
next reply other threads:[~2021-10-22 14:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-22 14:02 alandiwix [this message]
2021-10-24 16:04 ` ericonr
2021-10-24 20:44 ` biopsin
2021-10-25 14:17 ` biopsin
2021-10-25 14:38 ` misterupkeep
2021-10-25 14:40 ` biopsin
2021-10-25 14:41 ` biopsin
2021-10-26 13:18 ` biopsin
2021-10-26 13:54 ` biopsin
2021-10-26 14:13 ` biopsin
2021-10-27 5:41 ` biopsin
2021-10-27 5:41 ` biopsin
2021-11-03 9:28 ` alandiwix
2021-11-03 9:30 ` alandiwix
2021-12-08 1:36 ` ahesford
2021-12-08 1:36 ` [ISSUE] [CLOSED] " ahesford
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33700@inbox.vuxu.org \
--to=alandiwix@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).