08:17:01 <hardys> frg_Away: with latest build from Bill SM crashes instantly. Build 20230709110001 is ok
08:17:45 <frg_Away> hardys I know. Just backed out the offending patches. Next one will be good again. Should be ready in 2-3h if I am right.
08:18:28 <hardys> frg_Away: thanks and have a nice week
08:23:19 <hardys> frg_Away: btw it would be fine if Bill could provide the DE betas in the future for testing (I have read in the logs he will stop providing them :( )
08:25:11 <frg_Away> hardys I think that is a misunderstanding. One full installer needs to be done anyway to test the build system so de it is. For the others language packs.
08:25:59 <hardys> ah, okay then :)
10:11:33 <WG9s> To make it clear, I am going to continue to do the same builds I do now.  What is potentially changing is that may be no more 32-bit official releases.  So what will be absent is any languages other than en-US and de 32-bit builds, alternatives are use en-US builds with the supplied langpacks or do a full build yourself.
13:32:36 <MattATobin> offensive patches eh?
13:50:23 <NO1> bad rebase
13:51:26 <NO1> btw Bug 1389510 seems to be not breaking obvious things so goes in today for further testing.
15:22:37 <CaptainTobin> old content is fun
15:22:38 <CaptainTobin> The main goal of the project is to keep a suite which is similar from a user's perspective to Mozilla 1.7.x. We are not aiming to tie Firefox and Thunderbird together in some way, or make SeaMonkey drastically more similar to FF & TB.
15:22:46 <CaptainTobin> We plan to move to toolkit/ for the sake of code maintenance - we don't want to end up with another Firefox and Thunderbird. The suite should continue to look and feel similar to how it always has. One of the major concerns here is random changes to toolkit that have occurred in the past; moving to toolkit is contingent on the Mozilla Foundation committing to a more stable set of widgets.
15:24:04 <CaptainTobin> well the mozilla foundation did commit to that
15:24:12 <CaptainTobin> but then the mozilla corperation bypassed it
15:24:17 <CaptainTobin> and thus here we are
15:25:47 <CaptainTobin> giving I am gonna be working with the same code it is good to have a handle on what was actually done
17:16:38 <YoY> Hello
17:20:27 <YoY> i have my seamonkey that crashes when i run it
17:21:11 <YoY> i run it in netbsd
17:24:35 <no1> YoY did you compile it yourself?
17:25:17 <YoY> no but i tried to do it with no success it took too long
17:26:02 <no1> YoY we don't provide netbsd versions. You should ask whoever provided it.
17:26:32 <YoY> how come ?
17:27:22 <no1> not enough houres in the day to support every system under the sun.
17:27:24 <YoY> it is just available in the package
17:28:18 <no1> We only provode Linux macOS and Windows versions.
17:28:31 <YoY> ok
17:28:38 <YoY> so what should i do ?
17:28:55 <YoY> ask in netbsd irc i guess ?
17:29:01 <therube> look, Chrome is pulling a Mozilla, heh.
17:29:11 <no1> ask in a freebsd support group or the person who provided it.
17:29:23 <MattATobin> therube: clarify
17:29:26 <YoY> ok
17:29:46 <YoY> @nol thanks
17:29:47 <therube> they're rounding the corners & making it "pretty" (& they call that "development")
17:30:13 <MattATobin> YoY: You should always check with the source of the binary or whatnot before the name on the sticker
17:30:33 <MattATobin> therube: they are trying to design retrograde us
17:31:07 <MattATobin> and walk back some crap because they aren;t sure they will win right now
17:31:09 <therube> YoY: will the SeaMonkey releases run on netbsd? & if so, do they too crash?
17:32:01 <YoY> yes it runs normaly
17:32:13 <YoY> but not on my system it crashes
17:32:22 <MattATobin> i find it interesting that i can run fedora core 8 with kde 3.5 and seamonkey 1.1 and with trinity and my new xpfe intrest focus i will be able to again
17:32:23 <no1> If I buy a table I probably want rounded corner. I can live without them on a monitor.
17:32:43 <MattATobin> google's rounded corners are too extreme imo
17:33:02 <MattATobin> like a curve i used for all of 2 months in 2009 before making it like 4px again
17:33:44 <MattATobin> my new pixel phone which I am totally gonna use as way to help the linux on cell phone cause SO i can load in evolved kde35 and xpfe code into
17:34:04 <MattATobin> i also disabled the cutout screen shit and just pretend there ain't no screen there
17:34:07 <no1> They are ok as borders in Windows 7 but very small there. But seems lately everything needs to have excessive round corners. Next hype is probably triangles :)
17:34:24 <MattATobin> yeah 2-6px is a decent range
17:34:31 <MattATobin> which also includes the traditional mac corners
17:34:57 <no1> macOS degraded a lot after 10.14.
17:35:21 <MattATobin> MacOS X Degraded a lot after 10.4
17:35:26 <MattATobin> ... fixed that for you ;)
17:35:50 <no1> I liked 10.14 :) Still running 10.15 on the Intel mac mini
17:36:07 <MattATobin> 2006-2008 was the height of software, design, service, and utility
17:37:45 <MattATobin> i keep telling people and now i can read more code i am even MORE convinced but unlike previously i am not really angry but optimistic about it that i can not JUST build it not just update it to build with today's compilers but evolve it in new ways.. NO ONE can say they ever gave new life to xpfe technology or xpinstall technology or used the mozilla application framework like this
17:53:15 <njsg> Chrome has corners left to round!?
17:54:34 <no1> I wonder what happened? Lost 4% in a month: https://gs.statcounter.com/browser-market-share/desktop/worldwide?desktop-browser-ww-monthly-202201-202307
17:56:18 <tomman> that site won't fully load here because over half of its JS URLs are blacklisted by my DNS blocklists :P
17:56:54 <njsg> 0710|18:28:37 < therube> YoY: will the SeaMonkey releases run on netbsd? <-- SeaMonkey code yes, but there are no official binaries for *BSD, there are certainly at least a couple people trying to compile, as compilation failures sometimes pop up in the newsgroup
17:57:31 <YoY> ok
17:58:42 <njsg> (now of course there can be a problem in SeaMonkey code, it's just better to first check with whoever compiled the binaries, and also to check how to get information about the crash, say a backtrace.
17:58:52 <njsg> Is there any output?)
17:59:11 <YoY> yes if you want
18:01:04 <no1> tomman https://ibb.co/k02W2NF
18:01:28 <no1> Cut a but too much. Green is chrome
18:01:46 <tomman> so... less Chrome because Apple sold new toys this month?
18:08:23 <no1> tomman all but Chrome are up. Even Fx added 0.7%
18:08:56 <no1> May was all time low with 5.3% on desktop.
18:13:38 <YoY> here is the paste : https://controlc.com/8070b138
18:17:33 <no1> Just shows a segfault and nothing else, The first errors are "normal"
18:20:26 <YoY> normal ?
18:20:33 <YoY> how do i fix it ?
18:29:01 <YoY> see you tomorrow bye
18:29:05 <YoY> i got to go
20:04:58 <njsg> "core dumped" so there might be a file around to generate a stack trace from even if it's not running with a debugger attached? hopefully who made the build can point how to generate a backtrace
20:06:03 <njsg> "normal" as in present when everything works fine, the only one I don't usually see myself is the gvfs one I think?