public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Problem building python3-flit_scm for use with borgbackup
Date: Tue, 09 May 2023 08:42:14 +0100	[thread overview]
Message-ID: <D8F6FA93-B877-41AB-8CC0-09BD7EA1389C@ipfire.org> (raw)
In-Reply-To: <c80bf5fb-6292-21e5-2197-df6312ecdb3f@ipfire.org>

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

Okay, this sounds like good news.

I wish there wouldn’t be such massive chaos with every other language’s build system.

-Michael

> On 5 May 2023, at 16:34, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> Hi Michael,
> 
> On 04/05/2023 16:51, Michael Tremer wrote:
>> Hello Adolf,
>> Another day with another interesting problem that you are bringing us :)
> 
> I do seem to be able to find things that don't work as expected don't I.
>> Did you try to run “python3 -m build” in the source directory of exceptiongroup and flit-scm?
>> That inspiration is coming from here:
>>   https://github.com/archlinux/svntogit-community/blob/packages/python-exceptiongroup/trunk/PKGBUILD
> 
> The day before yesterday I thought to myself maybe I should look what Arch Linux does but never followed through on it. Thanks very much for the suggestion. I will give it a go and see how it goes. I will also compare it with the python3-flit module we have because that looks to use the pypproject.toml file, although there are several environment variables defined that I am not sure how to specify for my case but will see how things go.
>> I am not sure whether we have the build and installer module.
> We do have build but not installer. The python3-flit module seems to work without using installer, just build so will see how things go to start with only using build before looking at adding installer in as well.
> 
> Regards,
> Adolf.
> 
>> Best,
>> -Michael
>>> On 1 May 2023, at 17:52, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>> 
>>> Hi All,
>>> 
>>> I have figured out why the fuse mount stopped working with borgbackup in Core Update 173. (Bug#13076)
>>> 
>>> 
>>> python3-trio was updated when python was updated to 3.10.8 and python3-trio is required by python3-pyfuse3. However the python3-trio update also added a new dependency - python3-exceptiongroup which then requires python3-flit_scm for the build of python3-exceptiongroup.
>>> 
>>> 
>>> Both python3-exceptiongroup and python3-flit_scm use pyproject.toml, however python3-pyproject2setuppy fails with trying to build python3-flit_scm as it does not understand the backend definition in the pyproject.toml file.
>>> 
>>> The error message is :-
>>> 
>>>     File "/usr/lib/python3.10/site-packages/pyproject2setuppy/__main__.py", line 50, in main
>>>     raise NotImplementedError(
>>>     NotImplementedError: Build backend flit_scm:buildapi unknown
>>> 
>>> 
>>> pyproject2setuppy is now marked as DEFUNCT due to the number of special cases in the pyproject.toml file that needed lots of work each time to update pyproject2setuppy to work again.
>>> 
>>> 
>>> Does anyone have any idea how I should build flit_scm and exceptiongroup without using pyproject2setuppy.
>>> 
>>> I have done some searching but could not find anything that I could either understand or that did not require internet access to download all required dependencies.
>>> 
>>> 
>>> Regards,
>>> 
>>> Adolf.
>>> 
> 
> -- 
> Sent from my laptop



  reply	other threads:[~2023-05-09  7:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-01 16:52 Adolf Belka
2023-05-04 14:51 ` Michael Tremer
2023-05-05 15:34   ` Adolf Belka
2023-05-09  7:42     ` Michael Tremer [this message]
2023-05-09 15:30       ` Adolf Belka

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=D8F6FA93-B877-41AB-8CC0-09BD7EA1389C@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@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