still, logbot_cc seems to be down

it just loads nothing, no response from a server

???

could be my provider blocks port 8080 since yesterday

without the :8080 i get at least a response (NS_ERROR_CONNECTION_REFUSED)

so i'll use the tmpbot log for now

McI: I think WG9s is aware of the issue for logbot_cc

Down for me too. bucs one still works logbot.buc.me/seamonkey/20220306

IanN_Away I think this ia hardys not WG9s

frg_Away: ah right, I get confused easily

thanks

that's the one i use now

Mclbut I am working on geting a logbot server working with a valid SSL cert and with better support, but got sidetraked when Ihad a hardware issue on the server I was planning to use for this purpose.

:-)

ok

McI: ended up buying a real server class system instead of trying to use a high end desktop system. I now realize the big difference between a normal desktop and a gaming desktop is in the video card and that makes little difference in a server so was wasting money on something I did not need.

WG9s I think you bought a workstation :)

so still only a single server, but with more disk capcity and 2 cpus each with its own independent memory so if memor shile I order parts. issues or a CPU failure I can run it on just one.

well it comes in 2 flavors R7910 which they sell as a rack mounted server and T7910 which they sell as a workstation, but it turns out other than the form factor they are really identical.

WG9s yeah but they label it as a workstation too : dell.com/en-us/work/shop/cty/pdp/spd/precision-r7910-workstation :)

Doesn't matter. It is an basically dual use. Probably missing IPMI and a KVM.

frg_Away I did not call it a server but said it was server class. From what I remember from before I retired you can not call a tower system a server becuase conputer centers will not allow you to insatll anything that is rack mountable. as for lack of a kvm i have an external kvm and no real use for and IPMI.

frg_Away: i don;t have the actual specs on the R model but if it is sold as a server i would expect it to have redundant power supplies which is what the T version seems to lack

if it had those I would plug one into the wall with a surge u pressor and the other into my ups

WG9s yes and different mobo. More ram too I think. Just the same platform only.

butI am adding more ram

I believe it is the same motherboard if different I would expect a different model number not just the R T diffence

Nope totally different layout: ebay.com/itm/114464821817?

Status meeting in 20 minutes - wiki.mozilla.org/SeaMonkey/StatusMeetings/2022-03-06

hi IanN frg njsg checking in for meeting

hi .*

hi WG9s

Hi all

Greetings All!

hi WaltS48

Hi WaltS48

Status meeting in 8 minutes - wiki.mozilla.org/SeaMonkey/StatusMeetings/2022-03-06

Status meeting in 3 minutes - wiki.mozilla.org/SeaMonkey/StatusMeetings/2022-03-06

Status meeting time - wiki.mozilla.org/SeaMonkey/StatusMeetings/2022-03-06

hi rsx11m

Hi rsx11m

Who's taking minutes?

me

thanks

hi IanN frg

Nominees for Friends of the Fish Tank?

I nominate Myckel Habets the new gentoo maintainer

seconded

any others?

Action Items

nothing new from me

hi rsx11m

hi WG9s

Status of the SeaMonkey Infrastructure

Thanks to IanN we now have heptapod repos: foss.heptapod.net/seamonkey

The l10n-release repo is basically a clone of the gitlab repo. Plans to sync it are in the works

The other two are the base for our development work. They need the 2.53 patch queues which I originally started here: gitlab.com/frg/seamonkey-253-patches

cloning then applying patches is quicker for those doing dev work

Check gitlab.com/frg/seamonkey-253-patches/-/blob/master/readme-first.txt

rsx11m: yes, work well together

8-)

The website is basically gitlab code so unfortunately needs the polyfill add-on from JustOff or another browser.

Status of the SeaMonkey Source Tree

Any suite code goes into comm-central too but htis is basically and endless uphill battle kepping up with the "enhancements" and changes Mozilla and MZLA does.

All building. Ripping out NPAPI code from 2.53 to get rid of gtk2.

or you cpuld use the zip file on my build page wg9s.com/comm-253 which also has a link to the readme-first.txt file which has the d etailed build instructions.

I think WG9s mentioned latest rust required an updated library

was it that it depends on newer glibc++ symbols?

or stdlibc++?

yes do not try to build with 1.59.0 or later if you want to maintin backwards compatibility.

i wonder if it was delibrate or accidental

so I am building with 1.58 .1

seems to be using getrandom which if you build on a system with the getrandom from glib 2.25 or later requires glib 2.25 to run.

Other than for CentOS 7 not really need the comatibility I think. ubuntu 14.x and 16..x support could go if it is just me.

^compatibility

if y ou are building for your own use, not an issue, but I am building soemthing a guarantee will run on CentOS 7

slo an issue for me

WG9s Trying it on CentOS 7 to see what goes.

my linux builds have the same requirements for glabc version as the official builds.

well sinc e that does not have glabc 2.25 it would be hard for the build to require it.

mighgt require backproting a later patch to the libstdc stuff in the mozilla code

I do not have this issue with the comm-central builds so that is likely the case

so has to do with the stuff mozilla builds if you enable libstdcxx-compat

WG9s A non clobber build with 1.59 still works with CentOS 7. Trying a clobber

Release Train

i am sure it will iot is building with fedora27 that said glibc 2.25 is required

Nothing new in source from me.

to run the resultant build

2.53.11 was released on 2nd March

yepp, as reported

thanks for everyone's work on getting it out of the door

Reminds me to correct the release date on the downloads page as reported yesterday.

so i need to look at changes to /home/wag/mozilla/seamonkey/mozilla/build/unix/stdc++compat that have not yet been backported

91.7 will be out this week. Seeing a few bugs which might apply. TB is doing a 91.6.2 which does not convern is it seems. Fixing a fix whichas needed for the Firefox Downloads nonimprovements experience...

^which was needed

need to start thinking about 2.53.12b1 release

grump my typing today. Meant which does not concern us.

more coffee?

IanN not so fast typing and hitting enter would be best.

I think I said this once before but would be nice if w e could at some point make the source on heptapod be the source for an official SeaMonkey release andn make the gitlab queue be applied on that. Just Sayin!

WG9s clang 7 clobber build with rust 1.59 still woring when done under CentOS 7.

what i expected it is i can no longer do builds under fedora27 that will work on CentOS 7.

WG9s will not happen That would imply a stable patch queues and I don't see this one becoming stable any time soon. So would ned branches as in gitlab.

I can work on this. it b uilds fine with latest rust is just a backwards compatability issue so will not impact most users

as long as we do our official builds under CentOS 7 then we can use latest rust for those.

WG9s CentOS 7 is becoming ancient. I suspect most users are running something else now. And don't see use making a big bang in the enterprise area.

Extensions Tracking

Nothing new from me. NPAPI rip out should not affect still working extensions.

final CentOS 7.9 release was November 2020

but I recall there was a big change between CentOS 7 and 8 and so some people are still stuck on 7. lLso CentOS is now an official Red Hat thing and fedora is the latest and scariest and CentOS is like Red Hat Enterprise Linux next.

rsx11m still getting sec updates and even rust. Longer life cycle than 8 which is why so man people are happy with IBM :)

no updates on our favourite extensions

As opposed to being RHEL Stable with just a different support model and OS name string.

frg: ah, ok until 2024-06-30

rsx11m Set up a vm with Rocky 8 but blahh.. Sdding kde is a bear and didn't even find a way to run a root shell easy from the desktop. For my backup server I stay with openSUSE for sure.

^Adding kde

2.Next, Feature List, Planning and Roundtable

current RHEL developement cycle is RHEL is latest stable supported by Red Hat version recommended for Enterprise servers; Current stable CentOS which is RHEL next version.; current fedora whch will be next Centoos version; fedora rawhide, which some days ill not even boot!

rsx11m: i was trying to do that.

Doing daily planning and robbing Peter to pay Paul. Too many open SeaMonkey construction sites. Help wanted :)

why i am still running 1.58.1 until i figure out why my comm-central builds do not have the same dependency

Got my new job for sure now and will start in May.

congrats!

Means less SeaMonkey work but can't be helped. Sorry.

oh but i guess could just be change in if Firefox still can run on Cent OS 7

it is fine, just sort out cloning 1st

IanNso what is the cloning issue?

WG9s don't think central Firefox still runs. 91 may. glibc requirements got updated some time ago.

WG9s cloning us :)

frg: but then I would have expected my change in requirements would have not applied.

May1st is actually a holiday so 2nd

well I have this tar file you can get from my site but it differes from what your readme-first.txt file says

requires a different file structure

my tar file req uires a comm-253 with a mizilla under that and a comm under comm-253/mozilla

WG9s if you find any errors feel free to fix. Might be wrong.

while (frg) fork();

no just saying my tar file avoids having to clone from heptapod but is based on the way i have my directories structured that I did becuase when things moved from comm on top to mozilla on tip this avoided a lot of ancillary changs to my build system.

WG9s My mozilla dir is named comm-release56 with a comm under it.

went from a comm-253 that had the comm repostitory which had mozilla rep as a subdir and was aloso where l10n base was and where objdirs were.

relic from the good old times.

was easier to leave that direcory the objdirs were and where l 10n base was and make a mozilla u nder that and also a mozilla /comm under that.

time for AOB I think

but that is not how you do your builds so not how your instructions work

nothing from me. Trying to get some real web compatibility fixes in but slow go.

but i can probably build a new tar file that works with the isntructions rather than keepeiong this thing that was only so I could switch form comm on top to mozilla on tip with minimum changes

I'm out walking 40 miles on 19th, hope to be awake for meeting on 20th

WG9s yes I do. Just a name. No need to name it mozilla. But happy if you change it to be the same as you tar. less confusion.

the i nstructions are fine just not useful with my tar file. I can replace the tar file that one that works with your instructions

IanN unless there is a storm...

no my tar file creates a n extra layer so comm-253 under that mozilla and under that comm your instructions are for comm-253 with comm under

WG9s jupp

but i avoide clones at all costs becuase they seem to not alwahys work expecially under windows so start withn a tar file that can do an hg pull and hgupdate on to get up to date

okay, thanks for your time today

next meeting is in 2 weeks time, same bat channel, same bat UTC time

WG9s yes and heptapod is also a bit resource strained I think and if closes can be avaoided that are probably thankful.

... thus an hour later on the clock in North America and possibly elsewhere

(unless anybody got rid of DST already)

EU is still observing but it changes in the 27th, I think

I don't think anyone has recently

yes, EU is two weeks after us

will highlight in the invitations

maybe they had DST with different rules back then and that's what the stonehenge was for

I'm sure they observed DST 8-)

I hope this ends one year but I suspect will be 6 feet under then if ever.

Was a miracle already then they agreed an sanctions to stop Adolf Putin.

oh well, totally different story ...

yeahhh

and doubt we will see a happy ending soon unless some of the Russian GB vacationers visit the Kremlin.

anyway, have to go now

see you in two weeks!

bye

thanks McI

:-)

nice, user menu finally works again~