From mboxrd@z Thu Jan  1 00:00:00 1970
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
Message-ID: <E487220A-4D4A-4030-BD46-B5D6DF28BBC0@ipfire.org>
In-Reply-To: <4886a0e5-d8d8-1880-ee86-48583a91d4f5@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============4709628055748744849=="
List-Id: <location.lists.ipfire.org>

--===============4709628055748744849==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello,

Oh, that is probably a change that I accidentally committed.

On Debian, the Python modules are residing in a different place (god knows wh=
y) and to test things on my development machine, I occasionally change the pa=
th.

I fixed it here, and you can just grab the patch:

  https://git.ipfire.org/?p=3Dlocation/libloc.git;a=3Dcommitdiff;h=3Dbed4777f=
c99494854335a90c5a6e7fc2e30edf4d

-Michael

> On 30 Sep 2022, at 16:43, Peter M=C3=BCller <peter.mueller(a)ipfire.org> wr=
ote:
>=20
> Hello Michael,
>=20
> trying to update to libloc 0.9.15 in IPFire 2.x, I just noticed that all th=
e Python
> files are now in /usr/lib/python3/dist-packages/location/, not /usr/lib/pyt=
hon3/site-packages/location/,
> where they used to be before.
>=20
> Thanks to that, "location" crashes with a ModuleNotFoundError. Adding
>=20
>> sys.path.append("/usr/lib/python3/dist-packages/")
>=20
> before the location import statements solves this, but is probably not a fi=
x we
> strive for. :-)
>=20
> Am I overlooking something (such as changes to the LFS file)?
>=20
> Thanks, and best regards,
> Peter M=C3=BCller


--===============4709628055748744849==--