07:07:59 <antiplatonick> @search irc.irchighway.net
10:22:32 <njsg> *clrh
13:15:05 <Sompi> Now Yle is even more broken on Seamonkey: https://yle.fi/a/74-20113278
13:15:15 <Sompi> Every article just turns into a blank page when you scroll down enough
13:58:42 <tomman> Sompi: yay, the new Chromeisms are in~!
13:59:05 <tomman> who needs server-side frameworks anyway? The Client is the server™
17:23:42 <njsg> I remember when Yle actually had full articles in their RSS feeds... gentler times.
17:26:25 <njsg> tomman: "The Client is the Server™" sounds like a good slogan for an X11 project
17:27:08 <njsg> but also a misnomer of sorts, given that the client isn't the server, it just gets confusing when people expect the server to be the remote part
22:34:08 <oneforall2> not compiling https://pastebin.com/bgWw4MXB
22:40:40 <nsITobin> ./mach create-mach-environment
22:40:57 <nsITobin> it might have some errors too depending on python version but it should complete
22:41:17 <nsITobin> oneforall2:
22:41:28 <nsITobin> what distro?
22:42:03 <nsITobin> are you also sure you have enough space on tmp building mozilla code takes a lot of disk space
22:44:56 <oneforall2> willcheckmy space(chroot) have built a lot over the past 4 days :)
22:49:02 <oneforall2> mope not space
22:49:37 <nsITobin> well do ./mach create-mach-environment
22:51:53 <oneforall2> 200G free
22:55:49 <oneforall2> ./mach build
22:56:30 <oneforall2> so  like this ./mach create-mach-environment build?
22:56:36 <nsITobin> no
22:56:49 <nsITobin> just ./mach create-mach-environment
22:57:11 <nsITobin> i assume you HAVE built before
22:57:11 <oneforall2> or ./mach create-mach-environment  then ./mach build
22:57:23 <nsITobin> no just the command first
22:57:32 <nsITobin> ./mach create-mach-environment
22:58:16 <oneforall2> oh yeah the way it is never failed till adding export MACH_USE_SYSTEM_PYTHON="1"  and first try it failed too..
22:58:37 <nsITobin> i have to use that flag
22:59:20 <nsITobin> what was the output from mach doing that
22:59:44 <nsITobin> oneforall2
23:04:18 <oneforall2> app_data_dir=/root/.local/share/virtualenv)  maybe I delete that and then try again
23:05:46 <nsITobin> please
23:06:00 <nsITobin> whatt is the output of ./mach create-mach-environment
23:06:22 <oneforall2> https://pastebin.com/PyH4MvVL
23:06:55 <nsITobin> I need the full output
23:07:26 <nsITobin> and what distro is this for
23:07:40 <oneforall2> my own based of of slackware
23:07:53 <oneforall2> 20yrs now
23:08:28 <nsITobin> use python 3.7 or 3.9
23:08:32 <nsITobin> in fact
23:09:28 <nsITobin> also you may want to just clear ~/{.rustup,.cargo,.mozbuild} and rebootstrap esr115
23:09:28 <oneforall2> https://pastebin.com/yP1CvxDj
23:10:38 <nsITobin> ./mach clobber && ./mach configure now
23:10:41 <nsITobin> oneforall2:
23:11:29 <nsITobin> also try not using a script when trying to figure out build issues
23:11:33 <nsITobin> its not very helpful
23:11:59 <oneforall2> hmm never though of those others mozbuild  and I don't use rustup
23:12:37 <nsITobin> what version of rust?
23:14:27 <oneforall2> 1.81.0
23:14:36 <nsITobin> that may be too new
23:14:43 <nsITobin> I been using 1.76
23:14:52 <oneforall2> ff thbird compiled ..
23:15:30 <nsITobin> k
23:18:49 <nsITobin> So here is what I been doing is clone 115 and run ./mach bootstrap --application-choice=browser then rustup default 1.76 then clone seamonkey repos do mozconfig setting use system python .. then I run ./mach create-mach-environment.. check for deps with ./mach configure that aren't supplied by modern mozilla bootstrap .. then ./mach build
23:19:44 <nsITobin> Now I have discovered which deps SM actually needs and am collecting the artifacts so they can just be dumpped in to ~/.mozbuild and go.. so we aren't at least directly dependant on mozilla infrastructure as a service
23:21:36 <nsITobin> rust and clang .. its best you use the artifact versions and rustup .. Because SeaMonkey != Firefox and Thunderbird and you are gonna literally need to switch pieces around to build modern mozilla AND seamonkey
23:21:48 <nsITobin> oneforall2: alright?
23:24:39 <oneforall2> https://pastebin.com/6CWbcYxY  all 3 of the mach from the src build
23:27:25 <nsITobin> I dunno maybe you don't have all the depenancies
23:28:22 <nsITobin> oneforall2: basically unless you follow the instructions I am giving you I would have to run your distro to figure it out
23:28:47 <nsITobin> cause I have no idea what your environment is and build environments are NOT what they used to be
23:28:54 <nsITobin> it has caused me issues all year long
23:30:24 <nsITobin> in fact this has caused me so many issues I have literally re-aligned everything to el8 just so I can more easily build seamonkey
23:32:40 <nsITobin> what I know is these are based on the instructions given to me this year to build and contribute to seamonkey and after a lot of trial and error and jiggering of the order of operations and some diving into what exactly its doing I do understand it more but I don't know why you can't build..
23:34:41 <nsITobin> oneforall2: do you have python 3.11 setuptools?
23:35:24 <nsITobin> can you just altinstall 3.9 and use that .. it works fine on here
23:39:33 <oneforall2> setuptools-75.1.0
23:39:51 <oneforall2> haven't had 3.9 far a long time :)
23:39:58 <oneforall2> far/for
23:40:14 <nsITobin> well we are in custom territory
23:45:27 <oneforall2> eamonkey-2.53.18.2 last compile Apr 17 23:59:29 UTC 2024 just checking date on the python I used
23:46:29 <oneforall2> 3.11.9
23:46:45 <oneforall2> just tried that and same fail
23:47:18 <nsITobin> clear ~/.mozbuild
23:47:26 <nsITobin> but you may have to re-bootstrap
23:47:42 <nsITobin> from 115
23:47:47 <oneforall2> yeah unzippedit fresh to tmp and ran the 3 commands and same eror
23:48:07 <oneforall2> errors*
23:48:53 <nsITobin> how did you set it up to build in the first place
23:49:48 <oneforall2> well from my build script same as slackwares .. then I tried unzipping it freash no patchs etc
23:50:10 <oneforall2> well  slight dif but his failed too :)
23:50:32 <nsITobin> I thought you were building manually
23:50:44 <nsITobin> I can't help with distro specific technology past say MAYBE rpm
23:50:58 <nsITobin> and I am still pretty new to rpm
23:51:01 <oneforall2> only for this testing .. but no build scripts to make the packages
23:51:40 <oneforall2> -no
23:53:14 <oneforall2> hmm going to try seamonkey-2.53.18.2
23:53:38 <nsITobin> your mozbuild state path and virtualenv may be corrupt
23:53:59 <nsITobin> but again I dunno what slack's requirements are or how your system was prepped
23:58:34 <oneforall2> well damn 2.53.18.2  is compiling against python3-3.11.10