Github messages for voidlinux
 help / color / mirror / Atom feed
From: prashant-hm <prashant-hm@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Python v3.11 Update broke other programs?
Date: Tue, 15 Nov 2022 17:05:23 +0100	[thread overview]
Message-ID: <20221115160523.2aT3I2RLj_kyfZ-kdtSP-SXTRWdDLYpY1BARFIovNTw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40463@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 907 bytes --]

Closed issue by prashant-hm on void-packages repository

https://github.com/void-linux/void-packages/issues/40463

Description:
I think the recent update of Python v3.11 has broken a few programs.
For instance, Deluge.

Below is the output that I get now. This was not the case a few weeks back. I understand there is an annual update for Python is happening (5-7 days back). The [waterfall](https://build.voidlinux.org/waterfall) seems to be showing the x86_64 build complete.

I raised this issue on Reddit, where one more user also faced breakage of some other issue. (https://www.reddit.com/r/voidlinux/comments/yrzpee/python_311_update_has_it_broken_some_programs/). I have another program "castero" which started giving error due to python.

![image](https://user-images.githubusercontent.com/563296/201291108-a1486bfa-f7a0-4357-9daa-7814d4d2325d.png)

Any help will be highly appreciated!


      parent reply	other threads:[~2022-11-15 16:05 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  8:14 [ISSUE] " prashant-hm
2022-11-11  8:27 ` sgn
2022-11-11  9:18 ` prashant-hm
2022-11-11  9:29 ` sgn
2022-11-11  9:39 ` prashant-hm
2022-11-11 10:31 ` sgn
2022-11-11 10:32 ` sgn
2022-11-11 19:57 ` simplyTedel
2022-11-11 23:39 ` mtroberts
2022-11-12  0:03 ` paper42
2022-11-12  0:28 ` mtroberts
2022-11-12 11:30 ` prashant-hm
2022-11-12 13:09 ` fanyx
2022-11-12 13:10 ` paper42
2022-11-12 17:22 ` simplyTedel
2022-11-12 21:05 ` paper42
2022-11-13 12:37 ` sgn
2022-11-13 12:54 ` prashant-hm
2022-11-13 13:02 ` sgn
2022-11-13 14:30 ` sgn
2022-11-14  2:31 ` prashant-hm
2022-11-14  2:33 ` prashant-hm
2022-11-14  3:09 ` sgn
2022-11-14  3:10 ` sgn
2022-11-14  4:07 ` prashant-hm
2022-11-14  4:11 ` sgn
2022-11-14  4:24 ` prashant-hm
2022-11-14  4:25 ` prashant-hm
2022-11-14  4:39 ` sgn
2022-11-14  4:51 ` [ISSUE] [CLOSED] " sgn
2022-11-15 16:05 ` prashant-hm [this message]

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=20221115160523.2aT3I2RLj_kyfZ-kdtSP-SXTRWdDLYpY1BARFIovNTw@z \
    --to=prashant-hm@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).