I just pulled the latest pike version from git. It clearly has been a while, since I've actively participated. I apologise for my extended leave, it was due to some real-life issues that got in the way of things. That is not to say that I didn't stop using Pike or Roxen; quite the opposite, I just didn't have time to keep up on the mailinglists. I got snippets of updates through Marc though, so I wasn't completely ignorant.
Anyway, the good news is: I'm back. I just glanced through the mailinglist archives (in my mailbox) and it is quite a bundle to skip through (not started on that yet). I first checked the state of the pgsql module. I see some minor updates/fixes. I have one small and one very important fix waiting here which should get in ASAP (which I have been hunting down for the past three years, but did not, until about 2 weeks ago, result in a SEGV; which finally made it possible to zoom in on it; which, in effect, was the final nudge that I needed to get back on track with the mailinglist here).
Hmmm, I just glanced through http://pike.ida.liu.se/development/git/rw-git.xml Is it supposed to be automatic that when you "git commit" it will push it into the main repo? Do I still have access? If not, can I be reinstated?
Maybe the questions below went under in the noise. So let's reiterate them:
Stephen R. van den Berg wrote:
Hmmm, I just glanced through http://pike.ida.liu.se/development/git/rw-git.xml Is it supposed to be automatic that when you "git commit" it will push it into the main repo? Do I still have access? If not, can I be reinstated?
I just pulled the latest pike version from git. It clearly has been a while, since I've actively participated.
Hi, long time, no see!
I apologise for my extended leave, it was due to some real-life issues that got in the way of things. That is not to say that I didn't stop using Pike or Roxen; quite the opposite, I just didn't have time to keep up on the mailinglists. I got snippets of updates through Marc though, so I wasn't completely ignorant.
Anyway, the good news is: I'm back. I just glanced through the mailinglist archives (in my mailbox) and it is quite a bundle to skip through (not started on that yet). I first checked the state of the pgsql module. I see some minor updates/fixes. I have one small and one very important fix waiting here which should get in ASAP (which I have been hunting down for the past three years, but did not, until about 2 weeks ago, result in a SEGV; which finally made it possible to zoom in on it; which, in effect, was the final nudge that I needed to get back on track with the mailinglist here).
Sounds good.
Hmmm, I just glanced through http://pike.ida.liu.se/development/git/rw-git.xml Is it supposed to be automatic that when you "git commit" it will push it into the main repo?
No, you still need to do a git push. The commit hook just performs the same checks that the receive hook will do locally, so that you won't need to go back and fix any problems at push-time.
Do I still have access? If not, can I be reinstated?
It looks like you still have access:
$ ssh-keygen -l -f srbx 2048 f1:45:72:d6:c5:cd:f4:30:92:35:fe:b0:32:d9:f3:e8 srbx
/grubba
Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote:
Hmmm, I just glanced through http://pike.ida.liu.se/development/git/rw-git.xml Is it supposed to be automatic that when you "git commit" it will push it into the main repo?
Do I still have access? If not, can I be reinstated?
It looks like you still have access:
$ ssh-keygen -l -f srbx 2048 f1:45:72:d6:c5:cd:f4:30:92:35:fe:b0:32:d9:f3:e8 srbx
Hmmm, after some digging here, I come to the conclusion that I regenerated keys somewhere, possibly due to this key having been a weak key because of some algorithm flaw back then.
This is my new/current public key: 3072 82:c1:0e:ee:69:b5:3e:35:2b:b4:ac:59:ee:a1:1a:d7
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAYEAtnEYG8DzVDM3hyGbIxb2BBBKxpC41KQtKDdirmEjxPFu6H2GUA9m54/5kTTiS9aJ1NKUr5Cd8K66+TWE3yiXYUtWW0Y+czRm45p3GuMrwSDis730DkkOgzVdm+8GtRmKloirMaUw/Ppbmv1ewx90owKzzf58Su1KCliYlx8wY84IaQCBr9yNqf1XSeD/S5xlaCL1Y4m00sV7lGd7mAWlJ4JXmSS+QGoWbpNGdv9m3oxI1oYIrM963npSHcN+vTnsoYU5KHP/ddrC3e4EAiS+e7K8tSGwCzi9W4eLK2T+5Hl0nAHVwDn1LHX7VgxHc2MgDH5k8trh3BccUGDkelRSZVib3Y7sDHjv02nJsOcZMDI9/O2mh+vVoLkvCA75V45ULjGIdqbEgxAzskptgC7FwD3BvDPiPUz6TE974AovkADFbzoVz+qc3oA4GMtFydAJtjfWnnie6rgKOeLLBsFLl7jkkLzhEywNk2e7X17wywdFIu29Z8fiFyQMkZ+/SFP3 srb@aristoteles.cuci.nl
Hmmm, after some digging here, I come to the conclusion that I regenerated keys somewhere, possibly due to this key having been a weak key because of some algorithm flaw back then.
This is my new/current public key: 3072 82:c1:0e:ee:69:b5:3e:35:2b:b4:ac:59:ee:a1:1a:d7
Added.
/grubba
Henrik Grubbstr?m (Lysator) @ Pike (-) developers forum wrote:
Hmmm, after some digging here, I come to the conclusion that I regenerated keys somewhere, possibly due to this key having been a weak key because of some algorithm flaw back then.
This is my new/current public key: 3072 82:c1:0e:ee:69:b5:3e:35:2b:b4:ac:59:ee:a1:1a:d7
Added.
Thanks, works.
I notice that Pikefarm currently is offline? Which one of the myriad of make targets runs the testsuites just like Pikefarm used to?
Which one of the myriad of make targets runs the testsuites just like Pikefarm used to?
make valgrind_verify TESTARGS="-a -T -F"
You can see exactly the steps that Pikefarm takes by looking in bin/xenofarm.sh. There is also a "make xenofarm" target.
Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum wrote:
Which one of the myriad of make targets runs the testsuites just like Pikefarm used to?
make valgrind_verify TESTARGS="-a -T -F"
You can see exactly the steps that Pikefarm takes by looking in bin/xenofarm.sh. There is also a "make xenofarm" target.
Ok. make verbose_verify was enough to expose a problem, not in my patches, but in the tests; the socket tests hang, possibly due to too low constraints in the vserver I'm testing it in. I've fixed part of these problems last time, seems like they still are not robust enough. I'll revisit the network code and socket tests some time next week.
pike-devel@lists.lysator.liu.se