Arch Linux

Yew

Member

Registered: 2023-02-07

Posts: 9

Error building seamonkey init_py3

The first error is:

ERROR: The executable seamonkey/src/seamonkey-2.53.15/obj-x86_64-pc-linux-gnu/_virtualenvs/init_py3/bin/python3 is not functioning
ERROR: It thinks sys.prefix is '/usr' ...   [etc]

The last error is:

Exception: Failed to create virtualenv:

src/seamonkey-2.53.15/obj-x86_64-pc-linux-gnu/_virtualenvs/init_py3 (virtualenv.py retcode: 100)
0:19.14 *** Fix above errors and then restart with\
0:19.14                "./mach build"
0:19.14 make: *** [client.mk:114: configure] Error 1
==> ERROR: A failure occurred in build().
    Aborting...

loqs

Member

Registered: 2014-03-06

Posts: 18,101

Re: Error building seamonkey init_py3

https://github.com/BioMike/gentoo-seamo … port.patch

Yew

Member

Registered: 2023-02-07

Posts: 9

Re: Error building seamonkey init_py3

Thanks, I got a bit further...

loqs

Member

Registered: 2014-03-06

Posts: 18,101

Re: Error building seamonkey init_py3

Thanks, I got a bit further...

It built for me in a clean chroot after applying the linked patch,  without any other changes.  If it is not building for you please post an updated build failure in code tags.

screenfox

Member

Registered: 2023-05-13

Posts: 49

Re: Error building seamonkey init_py3

(Edit 2) So i found the -e parameter for makepkg, and this way i can apply the patch and have it used. But this is not a reproducible build - ok for playing around a bit, but not ok for replacing firefox with seamonkey for day-to-day usage. Can we do something about this? I'm not experienced with the infrastructure here.

(Edit) Ok, so i noticed i can apply the patch from src/seamonkey<version>/, but if i makepkg, it just unpacks the source tarball again. Same problem as before. 

I am wondering why this is a patch and does not get checked in to the repo?

So i tried 'git apply 1018_seamonkey_2.53.15-PY3.11_support.patch' in the repository root and got

Fehler: dom/base/usecounters.py: Datei oder Verzeichnis nicht gefunden
Fehler: python/mozbuild/mozbuild/action/process_define_files.py: Datei oder Verzeichnis nicht gefunden
Fehler: python/mozbuild/mozbuild/backend/base.py: Datei oder Verzeichnis nicht gefunden
Fehler: python/mozbuild/mozbuild/virtualenv.py: Datei oder Verzeichnis nicht gefunden
Fehler: python/mozbuild/mozpack/files.py: Datei oder Verzeichnis nicht gefunden
Fehler: third_party/python/virtualenv/virtualenv.py: Datei oder Verzeichnis nicht gefunden

(This says "Error: [...]: File or directory not found")

Do i have to navigate to some subfolder or give another parameter to git apply?

Last edited by screenfox (2023-06-02 10:40:01)

loqs

Member

Registered: 2014-03-06

Posts: 18,101

Re: Error building seamonkey init_py3

(Edit 2) So i found the -e parameter for makepkg, and this way i can apply the patch and have it used. But this is not a reproducible build - ok for playing around a bit, but not ok for replacing firefox with seamonkey for day-to-day usage. Can we do something about this? I'm not experienced with the infrastructure here.

See https://bbs.archlinux.org/viewtopic.php … 6#p2102796 for a PKGBUILD which applies the patch produced by  giannis-arch.  See also Patching_packages#Applying_patches.

I am wondering why this is a patch and does not get checked in to the repo?

Only the current maintainer can do that.

Yew

Member

Registered: 2023-02-07

Posts: 9

Re: Error building seamonkey init_py3

Thanks, I got a bit further...

It built for me in a clean chroot after applying the linked patch,  without any other changes.  If it is not building for you please post an updated build failure in code tags.

I waited two months and then updated the system, and that seemed to solve whatever problem I was having. Now it has been compiling for two days and nights. I think maybe it is not viable if I have to do this for every new version.

The update to the system failed because of some keys to python-markdown, mercurial, among others. I removed these packages, upgraded, then re-installed them, which may have solved some problems, hard to say for sure.