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: Python v3.11 Update broke other programs?
Date: Mon, 14 Nov 2022 05:07:11 +0100	[thread overview]
Message-ID: <20221114040711.3cUZ22sVe-ogS_ridCkAiAyrva-ZS0YdHu5t3YU3bS8@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: 1326 bytes --]

New comment by prashant-hm on void-packages repository

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

Comment:
@sgn 

This seems to be specific to my local setup. 
I am guessing the python3.11 links to libraries (libtorrent) were all messed up on my machine. I am saying so because I tried the following,

`$ python -c "import libtorrent; print(libtorrent.version)"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
SystemError: initialization of libtorrent raised unreported exception`

Anyways, I uninstalled the deluge package first, "xbps-remove deluge deluge-gtk".

Then I compiled Deluge from its Git repo source code. Build and installed it. This seems to have fixed all the library linkages. And Deluge started to work.

However, since I wanted the Void repo version of Deluge (just for the convenience of updates), I uninstalled Deluge.
For people unfamiliar with uninstall process, you can do `sudo updatedb; locate deluge` to figure the locations and remove it. Please refer to Deluge git page for uninstallation instructions.

Then I did usual install using "xbps-install deluge deluge-gtk". It has started working.

It will be interesting to see how things work out in the next package update.

Thanks! We can close this issue now.

  parent reply	other threads:[~2022-11-14  4:07 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 [this message]
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

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=20221114040711.3cUZ22sVe-ogS_ridCkAiAyrva-ZS0YdHu5t3YU3bS8@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).