From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: location@lists.ipfire.org Subject: Re: Python location files moved from site-packages to dist-packages Date: Sun, 02 Oct 2022 09:14:52 +0000 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============6478642423500568542==" List-Id: --===============6478642423500568542== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello Michael, thanks for your reply. > Hello, >=20 > Oh, that is probably a change that I accidentally committed. >=20 > 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. >=20 > I fixed it here, and you can just grab the patch: >=20 > https://git.ipfire.org/?p=3Dlocation/libloc.git;a=3Dcommitdiff;h=3Dbed477= 7fc99494854335a90c5a6e7fc2e30edf4d Ah, I see. Incorporated the patch, and running development. If successful, I'll submit an update patch for libloc in IPFire 2.x to the development mailing list in due course. All the best, Peter M=C3=BCller >=20 > -Michael >=20 >> On 30 Sep 2022, at 16:43, Peter M=C3=BCller w= rote: >> >> Hello Michael, >> >> trying to update to libloc 0.9.15 in IPFire 2.x, I just noticed that all t= he Python >> files are now in /usr/lib/python3/dist-packages/location/, not /usr/lib/py= thon3/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 f= ix we >> strive for. :-) >> >> Am I overlooking something (such as changes to the LFS file)? >> >> Thanks, and best regards, >> Peter M=C3=BCller >=20 --===============6478642423500568542==--