public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Info on problems with python3-setuptools for IPFire-3.x
Date: Thu, 21 Sep 2023 20:25:02 +0200	[thread overview]
Message-ID: <19f48063-6aa3-4f8a-9bfa-62e24a79d030@ipfire.org> (raw)

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

Hi All,

The IPFire-3.x version of python3-setuptools is quite old so I thought I 
would have a go at updating it but had a few problems on the way.

Running the existing version for 65.6.3 results in

Building python3-setuptools-65.6.3-1.ipfire3.src...
python3-setuptools-65.6.3-1.ipfire3.src does not support being built on 
x86_64
OSError: [Errno 0] Error

Removing the line from the build section that has arches = noarch stops 
that error occurring. Most of the other python3 .nm files don't have 
that arches line present.

Trying to then run version 68.2.2 resulted in the error
Could not add 'setuptools-68.2.2.tar.gz' to package: Success

Testing out the download url I found that it works with version 65.6.3 
but not with 68.2.2. Looking at the download from PyPI I found that 
other parts of the download url are changed for different versions of 
the same package.

The download url for 65.6.3 and for 68.2.2 are shown below for comparison

https://files.pythonhosted.org/packages/b6/21/cb9a8d0b2c8597c83fce8e9c02884bce3d4951e41e807fc35791c6b23d9a/setuptools-65.6.3.tar.gz
https://files.pythonhosted.org/packages/ef/cc/93f7213b2ab5ed383f98ce8020e632ef256b406b8569606c3f160ed8e1c9/setuptools-68.2.2.tar.gz

The above means that each time the version number is changed the 
download url will also need to be manually edited for all downloads from 
PyPI.

After changing the download url then the package downloaded and was 
successfully built.

Regards,

Adolf.



-- 

Sent from my laptop


             reply	other threads:[~2023-09-21 18:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21 18:25 Adolf Belka [this message]
2023-09-28  9:46 ` Michael Tremer

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=19f48063-6aa3-4f8a-9bfa-62e24a79d030@ipfire.org \
    --to=adolf.belka@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