Re: FreeBSD Port: prosody-0.8.2
> I'll see what I can find out. According to the (generally > lua-knowledgable) prosody folks these libraries might even be merged in the > future.. > For now I'll see if I can use the 0.9.1 patch (and bump it maybe?) so that > I can prosody as my test application. > Sorry for replying to myself. I fixed a minor issue in the luasec patch and formatted it to apply more easily. Plus, I created a patch for prosody and sent a follow-up to ports/182075. I'd be glad to get some feedback, especially from you, David. Would be awesome to get this in somehow. Regards, Ben luasec-update Description: Binary data ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: prosody-0.8.2
On Thu, Feb 6, 2014 at 9:05 PM, David Thiel wrote: > On 02/06, Benjamin Podszun wrote: > > Maybe I can help with that - since I plan to migrate/relocate and > > that's a core part of what I need here (which is why I'm diving into > > ports about 30min after my first FreeBSD installation in years). So - > > one tester, ready to help out. ;-) > > Thanks! > Depending on your progress: Attached the diff that bumps luasec as far as I can tell (builds, installs - but I haven't actually _used_ the package). Note: There might be atrocities in that diff. How can I know.. ;-) > > Luasocket: Well, can you explain what you mean? Are you talking about > > luasec including luasocket (and again, in a prerelease 3.x version)? If > you > > could tell me a bit more I'd be happy to invest some time/give it a go. > > Ugh, I forgot about this part of the mess. So, Prosody says that > Luasocket 2 is "required", but the new Luasec includes luasocket 3. Do > we update the Luasocket port to 3, hosted on its new GitHub repo? Does > this mean that the updated Luasec and luasocket ports would actually > conflict with each other? If you know or can find those answers, that'd > be useful. > > I'll see what I can find out. According to the (generally lua-knowledgable) prosody folks these libraries might even be merged in the future.. For now I'll see if I can use the 0.9.1 patch (and bump it maybe?) so that I can prosody as my test application. On a different note: Is this back and forth okay on this list or .. too much spam? :) Ben luasec-update Description: Binary data ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: prosody-0.8.2
On 02/06, Benjamin Podszun wrote: > Maybe I can help with that - since I plan to migrate/relocate and > that's a core part of what I need here (which is why I'm diving into > ports about 30min after my first FreeBSD installation in years). So - > one tester, ready to help out. ;-) Thanks! > Luasocket: Well, can you explain what you mean? Are you talking about > luasec including luasocket (and again, in a prerelease 3.x version)? If you > could tell me a bit more I'd be happy to invest some time/give it a go. Ugh, I forgot about this part of the mess. So, Prosody says that Luasocket 2 is "required", but the new Luasec includes luasocket 3. Do we update the Luasocket port to 3, hosted on its new GitHub repo? Does this mean that the updated Luasec and luasocket ports would actually conflict with each other? If you know or can find those answers, that'd be useful. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: prosody-0.8.2
On Thu, Feb 6, 2014 at 7:55 PM, David Thiel wrote: > On 02/06, Benjamin Podszun wrote: > > > If you can try to coordinate with the luasec and luasocket maintainers > ? > > > > Actually I think that's a non-issue (now). The comment from lx/the > > maintainer of prosody claims that s2s is broken (no idea, haven't tried > the > > patch just yet) and wonders if we'd need the forked lua dependencies. > > Looking at the prosody project page [1] even THEY don't realize that the > > situation has changed and they still point to [2] as a 'fork just to get > a > > release out'. The luasec bug [3] was closed just a week ago - in other > > words: luasec proper, the official version, got a new release out and the > > fork should be irrelevant now. A quick chat with the prosody developers > > seems to confirm that. > > Well, that's good, at least. Thanks for investigating. > > > That said: The luasec changes _shouldn't_ break s2s (merely disable some > > features, such as PFS for TLS for example). > > I agree! However, I was not able to successfully debug the issue with > the Prosody developers. Things may well have changed now, I just want to > get things fully in compliance with what the Prosody developers are > using, as a test cycle of all of Prosody's functionality is quite > time-consuming. > Maybe I can help with that - since I plan to migrate/relocate and that's a core part of what I need here (which is why I'm diving into ports about 30min after my first FreeBSD installation in years). So - one tester, ready to help out. ;-) The prosody people updated their website to deprecate their luasec fork when I asked them about the new 0.5 release - so their website is now stating 'Use 0.5 if you can, we have a fork that you can use if you have no 0.5 package available just yet'. > > So .. this probably now needs a bump for lua51-luasec (which lists no > > individual maintainer, points to po...@freebsd.org only) from 0.4 to > 0.5. > > How would I approach that? Looking at the port myself and giving it a > try? > > Attaching that to a bug of sorts (similar to the prosody one)? > > Tell you what -- I'll try to tackle LuaSec. If you can take a look at > the Luasocket situation and perhaps bring that up with the maintainer, > that'd certainly be useful. > So, I have a building luasec 0.5 here. Sortof. It fails in make package or anything _after_ make build, failing in 'install'. Obviously I'm not sure if this is just a hge hack or roughly usable.. Luasocket: Well, can you explain what you mean? Are you talking about luasec including luasocket (and again, in a prerelease 3.x version)? If you could tell me a bit more I'd be happy to invest some time/give it a go. Thanks, Ben ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: prosody-0.8.2
On 02/06, Benjamin Podszun wrote: > > If you can try to coordinate with the luasec and luasocket maintainers ? > > Actually I think that's a non-issue (now). The comment from lx/the > maintainer of prosody claims that s2s is broken (no idea, haven't tried the > patch just yet) and wonders if we'd need the forked lua dependencies. > Looking at the prosody project page [1] even THEY don't realize that the > situation has changed and they still point to [2] as a 'fork just to get a > release out'. The luasec bug [3] was closed just a week ago - in other > words: luasec proper, the official version, got a new release out and the > fork should be irrelevant now. A quick chat with the prosody developers > seems to confirm that. Well, that's good, at least. Thanks for investigating. > That said: The luasec changes _shouldn't_ break s2s (merely disable some > features, such as PFS for TLS for example). I agree! However, I was not able to successfully debug the issue with the Prosody developers. Things may well have changed now, I just want to get things fully in compliance with what the Prosody developers are using, as a test cycle of all of Prosody's functionality is quite time-consuming. > So .. this probably now needs a bump for lua51-luasec (which lists no > individual maintainer, points to po...@freebsd.org only) from 0.4 to 0.5. > How would I approach that? Looking at the port myself and giving it a try? > Attaching that to a bug of sorts (similar to the prosody one)? Tell you what -- I'll try to tackle LuaSec. If you can take a look at the Luasocket situation and perhaps bring that up with the maintainer, that'd certainly be useful. Thanks, David ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: prosody-0.8.2
Hi! > > > Starting from 20.08.2013 prosody is on 0.9, 0.9.2 was released in > > > January 2014. > > > > Have a look at > > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/182075 > > > > there is an update to 0.9.1 as a patch and one open question > > someone has to solve. > Thanks for the link. I .. didn't know better to search there first. Sorry > about that. No problem, I learned to rely on http://www.freebsd.org/cgi/query-pr-summary.cgi?query only recently, as well 8-} > So I guess I want that bug to be resolved, with a bump to 0.9.2 > ideally :) Yes, probably. > > > Is there any chance to see an update to this port? Are you still > > > interested in this project or is the port currently abandoned? > > > Can I help with anything to bump this to a more current (ideally: THE > > > current) version? > > > > If you can try to coordinate with the luasec and luasocket maintainers ? > > Actually I think that's a non-issue (now). The comment from lx/the > maintainer of prosody claims that s2s is broken (no idea, haven't tried the > patch just yet) and wonders if we'd need the forked lua dependencies. > Looking at the prosody project page [1] even THEY don't realize that the > situation has changed and they still point to [2] as a 'fork just to get a > release out'. The luasec bug [3] was closed just a week ago - in other > words: luasec proper, the official version, got a new release out and the > fork should be irrelevant now. A quick chat with the prosody developers > seems to confirm that. > > That said: The luasec changes _shouldn't_ break s2s (merely disable some > features, such as PFS for TLS for example). Well, PFS for TLS in post-Snowden-time seems like a must-have feature, but who am I to judge 8-} > So .. this probably now needs a bump for lua51-luasec (which lists no > individual maintainer, points to po...@freebsd.org only) from 0.4 to 0.5. Sounds plausible, yes. > How would I approach that? > Looking at the port myself and giving it a try? Yes, but this needs some serious investigation to try. I just had a look, and there's no distfile, you need to get it from github, etc. I normally copy the port to some work dir, and start fixing the issues that come up. Here's the script to copy the dir to ~/myp/ --- #!/usr/local/bin/bash if [ X$1 = 'X' ] then echo "usage: $0 " exit 1 fi if [ ! -d /usr/ports/$1 ] then echo "$0: error: invalid directory '/usr/ports/$1'" exit 1 fi cd ~/myp && rm -rf $1 cd /usr/ports && tar cf - $1 | ( cd ~/myp; tar xf -) --- If I achive a workable port, I generate a diff and submit it using send-pr. Here's the script to generate the diff: --- #!/usr/local/bin/bash if [ X$1 = 'X' ] then echo "usage: $0 " exit 1 fi if [ ! -d /usr/ports/$1 ] then echo "$0: error: invalid directory '/usr/ports/$1'" exit 1 fi if [ -d /usr/ports/$1/work ] then rm -rf /usr/ports/$1/work fi if [ -d ~/myp/$1/work ] then rm -rf ~/myp/$1/work fi cd /usr/ports diff -r -u -N $1 ~/myp/$1 --- > Attaching that to a bug of sorts (similar to the prosody one)? Yes, somewhat like this. I would suggest to first experiment with smaller ports that need attention 8-} It's a steep learning curve. Check the queue for open PRs: http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports Find one with a patch, copy the port, apply the patch and try it. Submit an update to the bug-report that you have tested it and that it works. etc. It's a useful way to learn many things about software. -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: prosody-0.8.2
Hi. On Thu, Feb 6, 2014 at 4:06 PM, Kurt Jaeger wrote: > Hi! > > > Starting from 20.08.2013 prosody is on 0.9, 0.9.2 was released in > > January 2014. > > Have a look at > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/182075 > > there is an update to 0.9.1 as a patch and one open question > someone has to solve. > Thanks for the link. I .. didn't know better to search there first. Sorry about that. So I guess I want that bug to be resolved, with a bump to 0.9.2 ideally :) > > Is there any chance to see an update to this port? Are you still > > interested in this project or is the port currently abandoned? > > Can I help with anything to bump this to a more current (ideally: THE > > current) version? > > If you can try to coordinate with the luasec and luasocket maintainers ? Actually I think that's a non-issue (now). The comment from lx/the maintainer of prosody claims that s2s is broken (no idea, haven't tried the patch just yet) and wonders if we'd need the forked lua dependencies. Looking at the prosody project page [1] even THEY don't realize that the situation has changed and they still point to [2] as a 'fork just to get a release out'. The luasec bug [3] was closed just a week ago - in other words: luasec proper, the official version, got a new release out and the fork should be irrelevant now. A quick chat with the prosody developers seems to confirm that. That said: The luasec changes _shouldn't_ break s2s (merely disable some features, such as PFS for TLS for example). So .. this probably now needs a bump for lua51-luasec (which lists no individual maintainer, points to po...@freebsd.org only) from 0.4 to 0.5. How would I approach that? Looking at the port myself and giving it a try? Attaching that to a bug of sorts (similar to the prosody one)? Thanks a lot/regards, Ben 1: https://prosody.im/doc/depends#luasec 2: https://prosody.im/doc/depends/luasec/prosody 3: https://github.com/brunoos/luasec/issues/3 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD Port: prosody-0.8.2
Hi! > Starting from 20.08.2013 prosody is on 0.9, 0.9.2 was released in > January 2014. Have a look at http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/182075 there is an update to 0.9.1 as a patch and one open question someone has to solve. > Is there any chance to see an update to this port? Are you still > interested in this project or is the port currently abandoned? > Can I help with anything to bump this to a more current (ideally: THE > current) version? If you can try to coordinate with the luasec and luasocket maintainers ? -- p...@opsec.eu+49 171 3101372 6 years to go ! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD Port: prosody-0.8.2
Hey there. Totally new to FreeBSD here, trying to migrate a piece of my infrastructure from .. Linux. One thing I'm relying on is prosody, you seem to maintain that port. 0.8.2 was released around the 20.06.2011. Starting from 20.08.2013 prosody is on 0.9, 0.9.2 was released in January 2014. Is there any chance to see an update to this port? Are you still interested in this project or is the port currently abandoned? Can I help with anything to bump this to a more current (ideally: THE current) version? Thanks a lot, Ben ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
