From: Michael Tremer <michael.tremer@ipfire.org>
To: location@lists.ipfire.org
Subject: Re: Python location files moved from site-packages to dist-packages
Date: Sat, 01 Oct 2022 12:57:22 +0100 [thread overview]
Message-ID: <E487220A-4D4A-4030-BD46-B5D6DF28BBC0@ipfire.org> (raw)
In-Reply-To: <4886a0e5-d8d8-1880-ee86-48583a91d4f5@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]
Hello,
Oh, that is probably a change that I accidentally committed.
On Debian, the Python modules are residing in a different place (god knows why) and to test things on my development machine, I occasionally change the path.
I fixed it here, and you can just grab the patch:
https://git.ipfire.org/?p=location/libloc.git;a=commitdiff;h=bed4777fc99494854335a90c5a6e7fc2e30edf4d
-Michael
> On 30 Sep 2022, at 16:43, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Hello Michael,
>
> trying to update to libloc 0.9.15 in IPFire 2.x, I just noticed that all the Python
> files are now in /usr/lib/python3/dist-packages/location/, not /usr/lib/python3/site-packages/location/,
> where they used to be before.
>
> Thanks to that, "location" crashes with a ModuleNotFoundError. Adding
>
>> sys.path.append("/usr/lib/python3/dist-packages/")
>
> before the location import statements solves this, but is probably not a fix we
> strive for. :-)
>
> Am I overlooking something (such as changes to the LFS file)?
>
> Thanks, and best regards,
> Peter Müller
next parent reply other threads:[~2022-10-01 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4886a0e5-d8d8-1880-ee86-48583a91d4f5@ipfire.org>
2022-10-01 11:57 ` Michael Tremer [this message]
2022-10-02 9:14 ` Peter Müller
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=E487220A-4D4A-4030-BD46-B5D6DF28BBC0@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=location@lists.ipfire.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