12:08:00 Can't figure out why my mouse scroll wheel is not working right. Any clues? 12:08:01 https://ibb.co/5h6pdGnk 12:08:37 I bet it is a SeaMonkey bug! 12:18:14 get an optical mouse, it'll solve all your problems - oh, wait... 12:18:38 well, maybe it just needs a bit of WD40? 12:20:17 what preconditions are needed to activate Seamonkey autoupdate? 12:22:22 I suppose write permissions on the install directory, enabling the auto-update setting and the platform and installed version being a combination that the update server offers an update to 12:22:29 (but I might be missing something) 12:24:52 It's also possible if the install is customized somehow (e.g. because it's offered from a distro via a package manager) that the auto-update setting is locked or overriden on startup (was this "channel preferences"?) 12:26:39 * njsg bbl 12:27:46 pref "auto.update.channel" was set to default, I got message no update available, I changed to release and got message 500 server error 12:38:58 is it possible to generate a log file to see whats going on in the background when I click the check for updates ? 12:39:22 ewong is probabyl tinkering with the 2.53.21b1 update. Give it a day or two. Update should not be triggered if you are on a release version. 12:43:02 njsg wd40 is only good for mecanical parts up to a point. Cleaned it with isopropyl 100% and an onld toothbrush. Blaregg. It was so much dirt. 13:06:34 WD40 eats plastics, from what I know 13:06:40 so don't - use good ol' IPA 13:07:09 downloaded and tested right now sm2.53.19 official release, Update to version 2.53.20 is working there, What options are needed in mozconfig to enable autoupdate? I used --enable-updater, did I forget something? 13:07:17 then some grease suitable for plastics - 3-in-1 can do in a pinch 13:10:27 slk64_14107: while i understand why you are asking but building yourself with enabled updater seems counterproductive.. if you can update to a binary release why are you building? 13:11:42 tomman IPA also dislikes some plastics like petg. 13:12:30 hot water hot enough to sanitize plastic also instantly melts some plastics like those in 2l bottles .. it shrinks.. and never recovers 13:12:42 update channel needs to be release or beta 13:13:25 i don't remember 2lt bottles in the 90s having that issue.. in fact when I was a kid we'd reuse them for water and would have to clean them and hot soapy water did the trick.. try that today and you will have a collapsed shrunkin useless bottle with a 10th of its volume left useable 13:13:59 only a 10th left useable* 13:14:24 nsITobin in thsi case the pcb needed cleaning too. No water here unless destilled. The salt minerals in it will eat the parts over time otherwise. 13:17:32 yes I'm building sm from source and an update is actually not needed. But I would like to know the reason why an update fails ;-) 13:18:23 slk64_14107: for raisins :P 13:18:29 --enable-updsate-channel 13:18:37 --enable-update-channel 13:19:05 are the channels not defined in confvars or are those still left set to mozilla infra values and you control it via release mozconfig? 13:20:26 yes via mozconfig 13:20:43 frg_Away: in the long run.. it is easier to just tie branding to update channels and then just control enabling or disabling the updater 13:22:17 of course seamonkey would then need some more branding to match said channels :P 13:22:46 need some nightly and unofficial branding first 13:23:35 i like depthcharge and brineshrimp respectively for that if not going SeaMonkey $channel brandwise 13:26:33 seamonkey nightly tho branding could be done with a logo mod.. simply have the sky in the logo be dark with stars.. and there you go 13:27:33 make the seamonkey its self given an orange tint dark blue night sky with stars and darker water.. 13:29:44 wish i knew how to do vector bs.. suppose if i were to do it i'd have to seperate the layers and recomposite them in my raster image program.. 13:30:26 ... cause apperently when I think modern design i think 70s film effects i guess 13:30:47 Status meeting starts in 30 minutes - https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2025-04-27 13:35:24 thank you very much, bye 13:36:03 frg_Away: tomman: yeah, I think I'd go with alcohol too, perhaps also some washing for what's fully removable 13:41:50 Status meeting starts in 19 minutes - https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2025-04-27 13:45:48 still need to work out some means for effectively the SeaMonkey association to assimilate all BinOC infra and constructs should I fall off the internet. 13:51:36 likely just end up writing down several key accounts and passwords putting it in a password'd archive and then putting it on a dedicated free cloud drive then give frg and IanN one the drive account password and the other the archive password.. 13:52:31 best to not vanish and work on offical infra with ewong :) 13:52:38 Status meeting starts in 8 minutes - https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2025-04-27 13:54:34 i have no plans to vanish.. would be extremely anti-climatic at any rate.. 13:58:50 Status meeting starts in 2 minutes - https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2025-04-27 13:59:36 hi . 13:59:38 hi .* 13:59:42 howdy * 14:00:05 rsx11m hi 14:00:22 Status meeting time - https://wiki.mozilla.org/SeaMonkey/StatusMeetings/2025-04-27 14:00:32 hi rsx11m, frg and njsg 14:00:56 hi again IanN 14:01:03 Who's taking minutes? 14:01:12 me 14:02:21 thanks 14:02:31 Nominees for Friends of the Fish Tank? 14:03:26 I nominate frg for his masocistic work on l10n 14:04:18 ye 14:05:11 seconded 14:05:17 thanks 14:05:41 Action Items 14:05:43 Depending on the language it is easy thanks to Total Commanders sync feature. 14:06:05 frg: still takes time 14:06:07 bau 14:06:50 Status of the SeaMonkey Infrastructure 14:06:53 yeah some 15 minutes and some a few hours so far. But one time only. 14:07:05 hello world~ 14:07:10 hiya tomman 14:07:33 Updated the Windows builder for the 2.53.21 beta but only VS2019 and git thg. 14:07:40 Hi tomman 14:07:55 the old windows and linux servers were finally decommissioned 14:08:17 i need to make good on my clone bundle syncing scheme so at least one doesn't have to fool with mozilla until you have the bulk of it already.. i am thinking a script to get various bundles and realign their upstream source upon checkout and pull latest 14:08:50 hg bundle* 14:09:52 nsITobin I think the xref has not picked up the 2.53.21b1 change. 14:10:39 likely a permissions issue i didn't resolve when i last manually sync'd.. i keep having that .. i will kick it here in a few 14:10:47 frg: did you add your usual tag? 14:11:16 IanN: if i manually pull as root and then apache tries to do it it will fail 14:11:26 "apache" 14:11:45 IanN unless I goofed yes. 14:12:16 Status of the SeaMonkey Source Tree 14:12:45 https://gitlab.com/seamonkey-project/seamonkey-2.53-mozilla/-/commit/79ddc5346601393e2d0c9013e733193da370b861 14:13:46 Mozilla chnaes to gitlab as the master source. I think the days of the suite comonent might be numberd now unless I am mistaken. 14:13:52 ^github 14:14:38 Release Train 14:15:01 2.53 is now at 2.53.22b1 pre. Didn't have much time for my wip branch becuase of real life, l10n and beta building. 14:15:02 SM2.53.21b1 is due out this week, please test very well 14:15:47 Planned to be the last x86 release and should be very very stable. cZ has a nickman problem which will be fixed for the final but nothing else I think. 14:16:31 seamonkey-2.53/source: Changing branch to 2_53_21_beta_01... 14:17:10 thanks nsITobin 14:17:28 it was a permissions issue 14:17:35 Extensions Tracking 14:17:38 IanN fixed an outstand issue with find and I a Composer issue with links and images. 14:18:10 we try our best 14:18:20 IanNN I looked at the jetpack breakage discussed last time but no clue currently. 14:20:07 2.Next, Feature List, Planning & Roundtable 14:20:29 how are we doing with the latest JS stuff these days? 14:20:43 dynamic imports and static class members have become pretty much mandatory for.. well, everything 14:21:00 these are the two missing features that bite the most these days 14:21:14 bau. A bit down becuase of the lack of progress wrt web compatibility but can't be helped. Still not giving up. 14:21:26 the world has reached a point where some of these open wifi WLAN APs which require at least clicking somewhere now will leave people out because of JS features 14:21:36 not that I tried with SM directly, but I guess SM would have the same fate there 14:24:27 AOB 14:25:25 tomman Again like a broken record mostly working in my wip branch but needed to take out optional chaning and new regexp for rebasing. 14:27:44 aob bau 14:27:52 thanks for your time today, next meeting in 3 weeks time on 18th May 14:28:02 cu * 14:28:05 (even though it says 4 weeks) 14:28:12 :-/ 14:28:14 same bat channel, same bat time 14:28:21 IanN oh can't make it on the 18th 14:28:43 oh, maybe it does need to be 4 weeks then... 14:29:00 an appointment with a MISTER P. N. GUIN PERHAPS.. frg 14:29:14 11 and 25 are fine by me 14:29:19 IanN: corrected 14:29:25 worse :) 14:30:25 eh, ok - when then? 14:30:53 confidential personal issue 14:31:22 that's ok, shall we keep 18 anyway or reschedule? 14:31:32 i think we're going for 25th 14:32:28 as far as it's weekends, I don't think I have anything scheduled, at least for May 14:32:59 25th is Memorial Day weekend here, but other than BBQ no plans 14:33:25 calendars are difficult... 8-) 14:34:57 so, once a month then 14:35:25 Now we just need to trim all months to have exactly 28 days 14:35:49 njsg: and all have the trimmings at the end of the year? 14:36:37 IanN: or every few years. I mean, we're already doing February 29 14:36:46 shall we adopt a moon calendar? 14:37:34 Too palemoonish :) 14:37:41 quantum central is gonna take longer to index .. i think the hg repo is abusted.. 14:37:57 might have to swap it out for the git version 14:38:44 okay, so next meeting in 4 weeks, thanks again for your time today 14:38:58 ok, so I'll make it 25th in four weeks... 14:39:47 we could always have a short meeting next sunday to hope the Force writes some code :-P 14:40:09 (but yes, see you all on the 25th!) 14:42:12 i know frg doesn't hardly touch the historical trees but do you use them at all IanN or can I slim the cross reference maintaince and store down to just active code and a couple older trees 14:43:18 nsITobin I usually use 2.53 only and when I need history pick the file in thg or searchfox from a later tree. SO for me they can be trimmed. 14:43:41 nsITobin: I mainly use 2.53 14:44:05 With the move to git searxchfox will become useless when hg is gone later but for now it is still ok. 14:44:24 was thinking just have central, seamonkey 2.53, seamonkey 2.49, and historical seamonkey 1.1 and 2.0 14:46:43 2.21 is also a favorite mining tree for me personally but not sure what would be left of value that wouldn't also be in 2.49 at the very least but also likely in 2.53 14:47:10 I think suite didn't change much till about 2.3x. 14:47:25 Then mozilla started the change frenzy. 14:47:36 cu here as away 14:49:47 well the code is here I grabbed my old hg to git conversion tree and overlayed my current bastardization on top.. unfortently Moonchild holds the only surviving copy of the full history repo with all my changes.. 14:49:53 https://gitlab.com/thereisonlyxul/seamonkey/cross-reference 14:50:23 I know where it is but it isn't public 14:52:07 frg_Away: you think searchfox will be killed and mozilla will only use github searching? 14:52:59 nsITobin It will stay but just look at the git log function currently active. It is crap for history. 14:53:16 git blame? 14:53:24 isn't that eq to annotations? 14:53:46 not as nice 14:53:48 but 14:54:39 git log in searchfox. Just links to github 14:54:42 i find searchfox subopimal cause there is no way to seemingly switch branches or get back to the main index of trees plus the searchbar confuses me 14:54:47 oh 14:55:15 It is not good but it is not as worse as native github 14:57:11 well i have some skills i developed from traversing gecko-dev that helps but it is only a virtue i forced my self to do it for so long it has become like instinct.. if i try and explain HOW to accomplish it.. it will be tedious and annoying and I doubt i can translate it back very well .. but there are WAYS to use github's blame and commit history to get into those hard to find nooks and cranies .. like alt history streams not addressed by any direct 14:57:11 branch or tag pointer 14:59:06 of course how mozilla has handled their repos has added a bunch of issues that will plauge a git conversion for years to come.. i warned them about it.. we will see if they listened 15:00:58 central has been switched I think or will be soon. 15:02:26 i dunno but mozilla isn't anything remotely like the mozilla we knew .. or maybe it is and that is a worse thought