Bug 911999

Summary:	dev-lang/python-3.11.4: bootstrap-prefix.sh stage3 fails (on Ubuntu)
Product:	Gentoo/Alt	Reporter:	APN-Pucky <alexander>
Component:	Prefix Support	Assignee:	Gentoo Prefix <prefix>
Status:	RESOLVED FIXED
Severity:	normal	CC:	alexander
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
See Also:	https://bugs.gentoo.org/show_bug.cgi?id=913856
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:	912222
Bug Blocks:
Attachments:	full_stage3_STABLE_generic_ubuntu1804_20230810073411.log.xz build_stage3_STABLE_generic_ubuntu1804_20230810073411.log.xz full_stage3_STABLE_generic_ubuntu2204_20230813073926.log.xz build_stage3_STABLE_generic_ubuntu2204_20230813073926.log.xz

Description APN-Pucky 2023-08-10 09:17:12 UTC

System:
Vagrant 2.3.7
generic_ubuntu1804 STABLE prefix
Linux ubuntu1804.localdomain 4.15.0-208-generic #220-Ubuntu SMP Mon Mar 20 14:27:01 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Steps to reproduce the bug:
Run the bootstrap-prefix.sh in mode STABLE (default STABLE) for stage3 (lower ones before)

Error message:
somewhere failed :(  Details might be found in the build log:
  /home/vagrant/gentoo-prefix/var/tmp/portage/dev-lang/python-3.11.4/temp/build.log
I have no clue, really.  Please find friendly folks in #gentoo-prefix on
irc.gentoo.org, gentoo-alt@lists.gentoo.org mailing list, or file a bug
at bugs.gentoo.org under Gentoo/Alt, Prefix Support.  This is most
inconvenient, and it crushed my ego.  Sorry, I give up.
Should you want to give it a try, there is /home/vagrant/gentoo-prefix/stage3.log

  CHOST:     x86_64-pc-linux-gnu
  IDENT:     x86_64-rap-linux-ubuntu18.04

Extra info:
https://github.com/APN-Pucky/gentoo-prefix-tester/actions/runs/5817654998

Comment 1 APN-Pucky 2023-08-10 09:17:12 UTC

Created attachment 867538 [details]
full_stage3_STABLE_generic_ubuntu1804_20230810073411.log.xz

Comment 2 APN-Pucky 2023-08-10 09:17:12 UTC

Created attachment 867539 [details]
build_stage3_STABLE_generic_ubuntu1804_20230810073411.log.xz

Comment 3 APN-Pucky 2023-08-11 14:14:38 UTC

> * QA Notice: the following files use invalid (possible non-prefixed) shebangs:
> *   /home/vagrant/gentoo-prefix/etc/init.d/pydoc-3.11:/sbin/openrc-run (script pydoc-3.11 installed in PATH but interpreter /sbin/openrc-run not found)
> * ERROR: dev-lang/python-3.11.4::gentoo failed:
> *   Aborting due to QA concerns: invalid shebangs found


I guess it is this file https://github.com/gentoo/gentoo/blob/a0945dd6b183a559d92dc46fc0b85d949fef59d7/dev-lang/python/files/pydoc.init#L1

Comment 4 APN-Pucky 2023-08-11 14:16:32 UTC

...which is also in the prefix repo https://github.com/gentoo/prefix/blob/395b646f1154d1c1c625387d8decb3a1b8bed254/dev-lang/python/files/pydoc.init#L1

Comment 5 APN-Pucky 2023-08-13 09:21:58 UTC

System:
Vagrant 2.3.7
generic_ubuntu2204 STABLE prefix
Linux ubuntu2204.localdomain 5.15.0-69-generic #76-Ubuntu SMP Fri Mar 17 17:19:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

Steps to reproduce the bug:
Run the bootstrap-prefix.sh in mode STABLE (default STABLE) for stage3 (lower ones before)

Error message:
somewhere failed :(  Details might be found in the build log:
  /home/vagrant/gentoo-prefix/var/tmp/portage/dev-lang/python-3.11.4/temp/build.log
I have no clue, really.  Please find friendly folks in #gentoo-prefix on
irc.gentoo.org, gentoo-alt@lists.gentoo.org mailing list, or file a bug
at bugs.gentoo.org under Gentoo/Alt, Prefix Support.  This is most
inconvenient, and it crushed my ego.  Sorry, I give up.
Should you want to give it a try, there is /home/vagrant/gentoo-prefix/stage3.log

  CHOST:     x86_64-pc-linux-gnu
  IDENT:     x86_64-rap-linux-ubuntu22.04

Extra info:
https://github.com/APN-Pucky/gentoo-prefix-tester/actions/runs/5845759959

Comment 6 APN-Pucky 2023-08-13 09:21:59 UTC

Created attachment 867777 [details]
full_stage3_STABLE_generic_ubuntu2204_20230813073926.log.xz

Comment 7 APN-Pucky 2023-08-13 09:22:00 UTC

Created attachment 867778 [details]
build_stage3_STABLE_generic_ubuntu2204_20230813073926.log.xz

Comment 8 Sam James archtester

2023-08-13 09:23:37 UTC

This is fixed in ~arch, it just needs newer Portage to be stabled first.

Comment 9 Fabian Groffen gentoo-dev

2023-09-23 11:21:18 UTC

I just fixed this in bootstrap-prefix.sh, please try.  Thanks!