Re: Build error after pull
By: kk4qbn to All on Sat Oct 26 2024 01:41 am

Did a recent pull (10-26) and sbbs will not build, was this taken out or am I missing something??

Compiling ansi_cio.c

Just need to do another git pull I think. Deuce has been working on SyncTERM stuff and committed some code that didn't compile for all targets/tools. That's all.
--
digital man (rob)

Synchronet "Real Fact" #44:
Synchronet added JavaScript suppport with v3.10a (2001)
Norco, CA WX: 65.0øF, 58.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Build error after pull
By: kk4qbn to Digital Man on Sat Oct 26 2024 09:46:54

Just need to do another git pull I think. Deuce has been working on SyncTERM stuff and committed some code that didn't compile for all targets/tools. That's all.

It's good to hang out on #synchronet or maybe #synchronet-devel and you will see git messages like...

[00:32] <git_Deuce> Pipeline for master branch BROKEN by Deuce
[00:32] <git_Deuce> Save and restore the console state for ANSI and Win32Console
[00:32] <git_Deuce> https://gitlab.synchro.net/main/sbbs/-/commit/673210b003fcdee98a98b249a850e797c1e7d615
[00:32] <git_Deuce> 77 failed builds: freebsd-amd64 [uedit], freebsd-amd64 [umonitor], freebsd-amd64 [sbbs],

It looks like you did a git pull after this but before

[01:20] <git_Deuce> Pipeline for master branch FIXED by Deuce
[01:20] <git_Deuce> ANSI mode isn't just for Windows
[01:20] <git_Deuce> https://gitlab.synchro.net/main/sbbs/-/commit/3c234b5f0e0c573aa198e5bf569aff467d04020f

If you don't want to keep an irc window up, you can always run ircii in screen or tmux.

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Build error after pull
By: nelgin to kk4qbn on Sat Oct 26 2024 13:52:43

It's good to hang out on #synchronet or maybe #synchronet-devel and you will see git messages like...

I use to.. seems you choose not to remeber select stuff, whatever the case, I'm not even going there anymore..



[00:32] <git_Deuce>> Pipeline for master branch BROKEN by Deuce Save and
[00:32] <git_Deuce>> restore the console state for ANSI and

Win32Console

These also are posted in dovenet, I saw it updated after the build, it's all good now I only have time to routinely check messages. anymore so dovenet works fine with me.

Thanks
---
Tim (kk4qbn)
+o kk4qbn.synchro.net
þ Synchronet þ KK4QBN BBS - kk4qbn.synchro.net - Chatsworth, GA USA
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Build error after pull
By: kk4qbn to nelgin on Sat Oct 26 2024 17:30:13

I use to.. seems you choose not to remeber select stuff, whatever the case, I'm not even going there anymore..

I remember but I chose to try and help you rather than mentioning it so not sure why you would.

These also are posted in dovenet, I saw it updated after the build, it's all good now I only have time to routinely check messages. anymore so dovenet works fine with me.

Yeah, I forgot they are posted there too.

One last way to quickly check is to have a look at the pipelines in gitlab

https://gitlab.synchro.net/main/sbbs/-/pipelines

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Build error after pull
By: nelgin to kk4qbn on Sat Oct 26 2024 18:42:38

Yeah, I forgot they are posted there too.

One last way to quickly check is to have a look at the pipelines in gitlab

https://gitlab.synchro.net/main/sbbs/-/pipelines

Yeah, I've definatly been looking over gitlab site, most of it is still fairly new to me, when I got back into synchronet last year I automatically from memory tried pulling the code in via CVS, then of course very quicly realized it had moved.

Lots of changes in 3.20, but still was fairly easy to install mainly from repetitive muscle memory.
---
Tim (kk4qbn)
+o kk4qbn.synchro.net
þ Synchronet þ KK4QBN BBS - kk4qbn.synchro.net - Chatsworth, GA USA
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: Build error after pull
By: nelgin to kk4qbn on Sat Oct 26 2024 23:58:15

I am not a big fan of how Synchronet works with git but I have created my own update scripts to mitigate some of the main issues that it was causing me without having to do this git stash crap every time I did changes and whatnot. It's not perfect but it suits my needs. Git itself does provide some useful tools for the developers and I like their bug reporting and it's easy to view the code history.

For my use it really doesnt present any issues really less for me to have to do than what i did with CVS, once the initial pull is done, I do mine kinda a little different though because I keep my working bbs file tree and the source tree seperate, eg

Working:

/sbbs/exec
/sbbs/ctrl
/sbbs/xtrn
...

Source Tree:

/sbbs/repo/src
/sbbs/repo/ctrl
/sbbs/repo/xtrn
...

I have too many of the JS files modified and don't want to accidently screw anything up so just copy JS files that have changed/new etc.. manually I'm sure there are much easier ways to do it, but this is the way I do it. works for me :) and theres really not much I have to put into it.

3.20 has come a long way to help sysops get up and running quickly from when I and a lot of other sysops started. There was no binkit integration, tickit lacked some features, there was no automatic setting up of fido and FTN networks with the init script or installation of doors and dosemu was hit and miss. That said, there is still quite a learning curve and it's not just plug and play, you have to understand all the terminology that goes with it, and can be daunting task for many new sysops.

That said, again, there have been a bunch of new boards popup since I started so there's people still out there interested in grinding at it. I don't want it to sound like people have it easier these days...which I guess they do in a way, no need to find separate mailers and tossers and get them working with the bbs, but the need for knowledge is still there because you need to know how they work together and interact with the bbs...sorry, I'm rambling...

I've always thought for the most part that putting a BBS up should'nt be too "Plug N' Play" or easy. There should be a degree of difficulty there that the sysop should go through. I might be alone in that thought, But I really would'nt want to see what a bbs scene would look like if ANYONE could install the software and have it runing very quickly and easily.. we still enjoy a certain degree of, well I wouldnt say privacy, but were able to set ourselves apart a bit from the intenet and social media as a whole.

Rambling can be good.
---
Tim (kk4qbn)
+o kk4qbn.synchro.net
þ Synchronet þ KK4QBN BBS - kk4qbn.synchro.net - Chatsworth, GA USA
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

On Sun, Oct 27 05:23:30 -0500, you wrote:

Working:

/sbbs/exec
/sbbs/ctrl
/sbbs/xtrn
...

Source Tree:

/sbbs/repo/src
/sbbs/repo/ctrl
/sbbs/repo/xtrn
...

I have too many of the JS files modified and don't want to accidently
screw anything up so just copy JS files that have changed/new etc.. manually I'm sure there are much easier ways to do it, but this is the
way I do it. works for me :) and theres really not much I have to put
into it.

I don't think you're doing anything different that most others here. I think the above setup is pretty standard. At least that's how it is here, as well. The initial 'clone' of git sets it up this way, for the exact purpose that you're not overwriting what you already have going on.

Any of your modified .JS files should be copied to your /sbbs/mods directory, where they won't be overwritten by git in any case, but will be read by Synchronet before the one located in /sbbs/exec. Once you have that setup, you can safely copy everything from /sbbs/repo/exec to /sbbs/exec after you pull updates from git, rather than tracking what was modified and copying them one at a time, manually.

The modified .js files in /sbbs/mods will need to be updated/diff'd/merged manually, though. But this is the proper way to separate them so whatever changes you've made don't get overwritten and you can continue to update Synchronet from git without accidentally screwing anything up.

Sometimes, if my changes to a .js are minimal (a couple/few lines), and the repo changes to the same .js are more substantial than what I've done, I'll just rename my current script, copy the newly updated one to my mods directory, and then copy/paste my changes into the new one. Otherwise, if the repo changes are minimal, I'll just see what the changes (diffs) were on github and add/remove those modifications to the script I'm already using.

Regards,
Nick

... Take my advice, I don't use it anyway.
--- Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:128.0) Gecko/20100101 Thunderb
* Origin: The Pharcyde ~ telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Re: Build error after pull
By: kk4qbn to nelgin on Sun Oct 27 2024 01:23:30

For my use it really doesnt present any issues really less for me to have to do than what i did with CVS, once the initial pull is done, I do mine kinda a little different though because I keep my working bbs file tree and the source tree seperate, eg

Working:

/sbbs/exec
/sbbs/ctrl
/sbbs/xtrn

I have too many of the JS files modified and don't want to accidently screw anything up so just copy JS files that have changed/new etc.. manually I'm sure there are much easier ways to do it, but this is the way I do it. works for me :) and theres really not much I have to put into it.

If you modify any files in /sbbs/exec then you can put them in /sbbs/mods and it'll use that version instead.

I have a similar setup except my script will copy files to /exec /exec/load /xtrn /sbbs/webv4 and text.dat then notify me of other changed files in /sbbs/text /sbbs/ctrl and /sbbs/data.

I've always thought for the most part that putting a BBS up should'nt be too "Plug N' Play" or easy. There should be a degree of difficulty there that the sysop should go through. I might be alone in that thought, But I really would'nt want to see what a bbs scene would look like if ANYONE could install the software and have it runing very quickly and easily.. we still enjoy a certain degree of, well I wouldnt say privacy, but were able to set ourselves apart a bit from the intenet and social media as a whole.

I think some other sysops see it like that. I once said that every BBS is different and someone replied, "Unless it's a Synchronet BBS"...and it's sort of true. I log into so many Synchronet boards and they have the default many or many default characterists, mine included. That's when I decided to was time to customize my board.

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)