I will volunteer to take the lead on maintaining things on GitHub. I think we
are exceedingly close to being fine there anyway – Chris, what issues do you
see that would need dealing with?
I see the required activity as something like this:
* ensure all the people who should have push access are on GH and are in
the PDLPorters organisation
* ensure all SF issues are present as GH issues
* announce say a week in advance we will be switching the repo location
* CODE FREEZE as releases are going to be happening
* at the same time, dev-release new version with the updated: repo
location, bugtracker location
* after that week, proper-release that version
* quick final check that GH and SF repos are in sync
* turn off Christian’s script – no more error emails!
Can anyone see things I missed or got wrong there?
Ed
From: Christian Walde<mailto:walde.christ...@gmail.com>
Sent: Tuesday, March 06, 2018 5:56 PM
To: pdl-devel@lists.sourceforge.net<mailto:pdl-devel@lists.sourceforge.net> ;
Chris Marshall<mailto:devel.chm...@gmail.com>
Subject: Re: [Pdl-devel] unstable SF git servers and github mirroring
I'm happy to hear that. I'll keep things running for however long you need,
just please let me know when i can shut the scripts down. :)
--
With regards,
Christian Walde
On Sun, 04 Mar 2018 20:53:01 +0100, Chris Marshall <devel.chm...@gmail.com>
wrote:
Christian and all-
I'm fine with moving development and issues
to github if someone wants to take the lead
to maintain things on github.
We should do a quick release to point at
the new locations and maybe include a few
fixes in the hopper. I'm not sure that
all the sf.net bugs are on github at
the moment.
In the meantime, I/we can update the sf.net
information to mention/refer to github instead...
--Chris
On 3/4/2018 10:21, Ed . wrote:
Can someone help me understand what the benefit of staying on Sourceforge at
all is? The only thing we’re using there is the mailing list and we can still
use that. As far as I know all the issues got copied over by Zaki.
I suggest this:
* everybody switch to push to GH only
* make a release with metadata pointing at GH for repo location and bugtracker
* turn off the mirroring and save poor Christian from wasting any further hours
of his life
* continue to enjoy the CI
Chris?
From: Derek Lamb<mailto:de...@boulder.swri.edu>
Sent: Sunday, March 04, 2018 6:03 AM
To: Christian Walde<mailto:walde.christ...@gmail.com>
Cc: pdl-devel<mailto:pdl-devel@lists.sourceforge.net>
Subject: Re: [Pdl-devel] unstable SF git servers and github mirroring
Hi Christian,
If the developers implemented the instructions to push to both SourceForge and
GitHub at the same time described here
(https://sourceforge.net/p/forge/documentation/GitHub%20Importer/#source-code),
would that permit you to shut down your cron scripts and save yourself from the
burden of error emails?
Derek
On Mar 1, 2018, at 12:00 PM, Christian Walde
<walde.christ...@gmail.com<mailto:walde.christ...@gmail.com>> wrote:
For those who aren't aware, or for those whose mind it has slipped:
I run on one of my servers a bunch of very simplicistic cron scripts that
mirror the SourceForge git repositories to github.
Particularly:
pdl.git
pdl-book.git
pdl-fftw.git
pdl-graphics-plplot.git
pdl-io-hdf5.git
pdl-linearalgebra.git
The command used for each is a simple:
[alias]
update-mirror = !git fetch -q origin && git push -q github
My cron looks like this:
MAILTO=walde.christ...@gmail.com<mailto:MAILTO=walde.christ...@gmail.com>
0-59/5 * * * * cd /root/pdl_repo_mirrors/pdl.git && git update-mirror
1-59/5 * * * * cd /root/pdl_repo_mirrors/pdl-linearalgebra.git && git
update-mirror
2-59/5 * * * * cd /root/pdl_repo_mirrors/pdl-book.git && git update-mirror
3-59/5 * * * * cd /root/pdl_repo_mirrors/pdl-graphics-plplot.git && git
update-mirror
4-59/5 * * * * cd /root/pdl_repo_mirrors/pdl-io-hdf5.git && git update-mirror
0-59/5 * * * * cd /root/pdl_repo_mirrors/pdl-fftw.git && git update-mirror
In recent times the SF git servers have become incredibly more flaky, to the
point that on saturday the mirroring between SF and GH sent me a whopping 229
error messages about being unable to reach sf. Over the past two weeks the low
tide was 20 messages per day.
The error messages i get are variations on this theme:
fatal: unable to connect to git.code.sf.net: git.code.sf.net[0: 216.105.38.16]:
errno=Connection timed out
fatal: read error: Connection reset by peer
fatal: remote error: access denied or repository not exported:
/p/pdl/pdl-linearalgebra
fatal: Could not read from remote repository. Please make sure you have the
correct access rights and the repository exists.
etc.
At this point i can make no guarantee that i'll be capable of recognizing when
an actual error happens, particularly since the unreliability of sf servers
results in me getting many varying types of error messages.
Also, it's a gigantic pain in the neck to skim and delete those messages every
day.
In lieu of an actual migration to github, if anyone here would like to offer an
email address i can configure as a target for these things instead, please do
let me know.
--
With regards,
Christian Walde
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
pdl-devel mailing list
pdl-devel@lists.sourceforge.net<mailto:pdl-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/pdl-devel
________________________________
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
________________________________
_______________________________________________
pdl-devel mailing list
pdl-devel@lists.sourceforge.net<mailto:pdl-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/pdl-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
pdl-devel mailing list
pdl-devel@lists.sourceforge.net<mailto:pdl-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/pdl-devel
________________________________
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
________________________________
_______________________________________________
pdl-devel mailing list
pdl-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pdl-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
pdl-devel mailing list
pdl-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pdl-devel
