From: "Ivan A. Melnikov" <iv@altlinux.org>
To: ALT Linux Team development discussions <devel@lists.altlinux.org>
Subject: [devel] python3 FTBFS
Date: Thu, 24 Aug 2023 16:29:27 +0400
Message-ID: <7rv72y7lwkh63hst2sixglqudz5aq6t4w2pbj4qhq53szsla4v@jfadtzherk4v> (raw)
In-Reply-To: <ZOcHzP+RheEJ2h7c@cello>
On Thu, Aug 24, 2023 at 10:33:32AM +0300, Arseny Maslennikov wrote:
> python3 grenka imz vitty george glebfm darktemplar
А тут всё любопытно.
Во-первых, новый autoconf делает симлинки вместо копирования,
а cp -rl симлинки разименоввывает перет тем как делать
хардлинки. Эту проблему можно преодолеть несколькими способами,
я предлагаю так:
https://git.altlinux.org/people/iv/packages/?p=python3.git;a=commitdiff;h=441eeaf575d7c8d9e977cc4b658d53e5278b364e
Во-вторых, когда эта проблема преодолена, вылезает следующая:
при поиске зависимостей python3 использует свежесобранный
интерпретатор из %buildroot, поэтому системный
%python3_sitelibdir_noarch к нему в sys.path не попадает.
Раньше это никому не мешало, но после недавнего выделения
py3dephell из rpm-build-python3 начало активно мешать:
https://git.altlinux.org/tasks/327851/logs/events.1.1.log
[x86_64] from py3dephell.py3prov import generate_provides
[x86_64] ModuleNotFoundError: No module named 'py3dephell'
[x86_64] find-provides: ERROR: /usr/lib/rpm/python3.prov failed
[x86_64] error: /bin/sh failed
Эту проблему можно преодолеть несколькими способами, и мне
кажется это стоит сделать на стороне rpm-build-python3.
Ради эксперимента я сделал так:
https://git.altlinux.org/people/iv/packages/?p=rpm-build-python3.git;a=commitdiff;h=d6559329c572b1850a961ac28454a09be0f2979e
хотя наверное можно подумать и сделать аккуратнее.
В третих, когда и эта проблема преодолена, мы упираемся
в текущие проблемы c curses.
https://git.altlinux.org/tasks/327851/logs/events.2.1.log
Тут я просто надеюсь, что эти проблемы куда-нибудь
утекут.
Всем спасибо за внимание, было весело.
--
wbr,
iv m.
next prev parent reply other threads:[~2023-08-24 12:29 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 11:35 [devel] forthcoming p11: a call for requests and action Arseny Maslennikov
2023-06-22 11:52 ` Yuri Sedunov
2023-08-28 16:17 ` Yuri Sedunov
2023-09-25 10:34 ` Yuri Sedunov
2023-11-21 9:29 ` Yuri Sedunov
2023-06-25 11:14 ` Anton Farygin
2023-06-28 12:55 ` Dmitry V. Levin
2023-06-28 16:22 ` Andrey Savchenko
2023-06-28 17:35 ` Gleb Fotengauer-Malinovskiy
2023-06-30 16:00 ` Mikhail Efremov
2023-07-04 13:19 ` [devel] procps-ng-4.0 Arseny Maslennikov
2023-07-04 13:09 ` [devel] [p11-release-mgmt] usrmerge Arseny Maslennikov
2023-07-04 13:11 ` [devel] [p11-release-mgmt] usrmerge action proposal Arseny Maslennikov
2023-11-21 21:41 ` [devel] [p11-release-mgmt] usrmerge Sergey Y. Afonin
2023-11-21 22:13 ` Arseny Maslennikov
2023-07-07 19:27 ` [devel] forthcoming p11: a call for requests and action Alexey Shabalin
2023-07-08 6:56 ` Alexey V. Vissarionov
2023-07-08 11:52 ` Denis Medvedev
2023-07-08 12:17 ` Dmitry V. Levin
2023-08-16 17:48 ` [devel] forthcoming p11: FTBFS summary Arseny Maslennikov
2023-08-16 18:09 ` Arseny Maslennikov
2023-08-16 18:20 ` Anton Zhukharev
2023-08-24 7:33 ` Arseny Maslennikov
2023-08-24 8:06 ` Arseny Maslennikov
2023-08-24 9:47 ` [devel] I: possible double ncurses abi Arseny Maslennikov
2023-08-28 9:42 ` [devel] possible double ncurses abi: call for approvals Arseny Maslennikov
2023-08-28 10:45 ` Dmitry V. Levin
2023-08-28 11:30 ` Dmitry V. Levin
2023-08-28 20:40 ` Arseny Maslennikov
2023-08-29 6:56 ` Dmitry V. Levin
2023-08-24 8:15 ` [devel] forthcoming p11: FTBFS summary Gleb Fotengauer-Malinovskiy
2023-08-24 8:16 ` Gleb Fotengauer-Malinovskiy
2023-08-24 12:29 ` Ivan A. Melnikov [this message]
2023-09-03 14:54 ` [devel] python3 FTBFS Daniel
2023-09-04 7:52 ` Ivan A. Melnikov
2023-08-31 9:50 ` [devel] forthcoming p11: FTBFS summary Arseny Maslennikov
2023-08-31 9:59 ` Dmitry V. Levin
2023-08-31 12:01 ` Anton Farygin
2023-09-07 9:44 ` [devel] forthcoming p11: FTBFS summary available at gitery Arseny Maslennikov
2023-09-07 9:56 ` Yuri Sedunov
2023-09-07 10:15 ` Arseny Maslennikov
2023-09-07 10:31 ` Aleksey Novodvorsky
2023-09-07 11:25 ` Arseny Maslennikov
2023-09-07 10:44 ` Aleksey Novodvorsky
2023-09-07 11:07 ` Arseny Maslennikov
2023-09-07 11:18 ` Sergey V Turchin
2023-09-07 10:49 ` Sergey V Turchin
2023-09-07 10:56 ` Arseny Maslennikov
2023-09-07 10:58 ` Sergey V Turchin
2023-10-18 8:20 ` [devel] I: forthcoming p11: FTBFS summary, more announcements Arseny Maslennikov
2023-10-31 15:45 ` [devel] forthcoming p11: FTBFS summary Arseny Maslennikov
2023-10-31 15:49 ` Arseny Maslennikov
2023-11-01 9:02 ` Sergey Bolshakov
2023-11-01 9:26 ` Arseny Maslennikov
2023-10-31 16:03 ` Aleksey Novodvorsky
2023-11-01 4:06 ` Andrey Cherepanov
2023-11-01 5:51 ` Ivan A. Melnikov
2024-02-04 21:25 ` [devel] [p11-release-mgmt] closing in, hopefully Arseny Maslennikov
2024-02-04 23:34 ` Grigory Ustinov
2024-02-05 1:39 ` Aleksey Novodvorsky
2024-02-05 5:51 ` Anton Farygin
2024-02-05 6:13 ` Andrey Savchenko
2024-02-05 8:01 ` Роман Алифанов
2024-02-05 23:13 ` Alexey V. Vissarionov
2024-04-26 17:11 ` [devel] forthcoming p11: пора чинить пакеты Arseny Maslennikov
2024-04-27 10:09 ` alexei
2024-04-27 10:35 ` [devel] " Sergey V Turchin
2024-04-27 14:12 ` [devel] " Anton Farygin
2024-04-30 3:42 ` Alexey V. Vissarionov
2024-04-30 6:24 ` Anton Farygin
2024-04-28 10:36 ` [devel] forthcoming p11: пора чинить пакеты: jq -> обновление valgrind Anton Farygin
2024-04-28 11:28 ` Anton Farygin
2024-04-30 18:02 ` [devel] forthcoming p11: пора чинить пакеты Arseny Maslennikov
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=7rv72y7lwkh63hst2sixglqudz5aq6t4w2pbj4qhq53szsla4v@jfadtzherk4v \
--to=iv@altlinux.org \
--cc=devel@lists.altlinux.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
ALT Linux Team development discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://lore.altlinux.org/devel/0 devel/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 devel devel/ http://lore.altlinux.org/devel \
devel@altlinux.org devel@altlinux.ru devel@lists.altlinux.org devel@lists.altlinux.ru devel@linux.iplabs.ru mandrake-russian@linuxteam.iplabs.ru sisyphus@linuxteam.iplabs.ru
public-inbox-index devel
Example config snippet for mirrors.
Newsgroup available over NNTP:
nntp://lore.altlinux.org/org.altlinux.lists.devel
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git