Re: GitHub migration complete

2016-11-03 Thread Michael
On 2016-11-03, at 4:44 AM, René J.V. Bertin wrote: > On Thursday November 03 2016 11:35:43 Clemens Lang wrote: > >> It's something we all have to deal with. Presumably, we will all learn over >> time. > > Presumably. Question is, who has to learn what, and how reasonable

Re: GitHub migration complete

2016-11-03 Thread René J . V . Bertin
On Thursday November 03 2016 11:35:43 Clemens Lang wrote: > It's something we all have to deal with. Presumably, we will all learn over > time. Presumably. Question is, who has to learn what, and how reasonable is it to require that of them when the general consensus usually is that "users

Re: GitHub migration complete

2016-11-03 Thread Clemens Lang
Hi, - On 3 Nov, 2016, at 10:57, René J.V. Bertin rjvber...@gmail.com wrote: > last time I checked, github's issue tracker wasn't available for the ports > repo. > I presume that's on purpose, but why? Even if "we already have a bug tracker", > why would it make life harder and not easier at

Re: GitHub migration complete

2016-11-03 Thread René J . V . Bertin
A question that came up due to another ticket: last time I checked, github's issue tracker wasn't available for the ports repo. I presume that's on purpose, but why? Even if "we already have a bug tracker", why would it make life harder and not easier at least for some things? I must admit

Re: GitHub migration complete

2016-10-31 Thread Lawrence Velázquez
> On Oct 31, 2016, at 12:16 PM, Thibaut Paumard wrote: > >> Le 31/10/2016 à 17:01, René J.V. Bertin a écrit : >>> On Monday October 31 2016 10:00:05 Ryan Schmidt wrote: >>> >>> This issue only affects the very small percentage of the MacPorts user >>> population

Re: GitHub migration complete

2016-10-31 Thread René J . V . Bertin
On Monday October 31 2016 10:00:05 Ryan Schmidt wrote: > This issue only affects the very small percentage of the MacPorts user > population (including developers and maintainers) that clones the git > repository. Most users will use the rsync server, on which we do generate > portindexes for

Re: GitHub migration complete

2016-10-31 Thread Ryan Schmidt
> On Oct 31, 2016, at 4:18 AM, René J. V. Bertin wrote: > > Clemens Lang wrote: > >> If your question is not yet answered, ask on the mailing lists so it can >> be added. > > I may have overlooked this, but does github have any provisions that would > allow > the

Re: GitHub migration complete

2016-10-31 Thread Chris Jones
On 31/10/16 10:41, René J.V. Bertin wrote: On Monday October 31 2016 10:49:55 Clemens Lang wrote: Hi, Just as with Subversion, the answer is no. Remember that the PortIndex is specific to the macOS version you are running, so a server-generated Ah, of course. I didn't actually know this

Re: GitHub migration complete

2016-10-31 Thread René J . V . Bertin
On Monday October 31 2016 10:49:55 Clemens Lang wrote: Hi, >Just as with Subversion, the answer is no. Remember that the PortIndex >is specific to the macOS version you are running, so a server-generated Ah, of course. I didn't actually know this but indeed port versions could be specific to

Re: GitHub migration complete

2016-10-31 Thread Chris Jones
On 31/10/16 09:49, Clemens Lang wrote: Hi, On Mon, Oct 31, 2016 at 10:18:42AM +0100, René J. V. Bertin wrote: I may have overlooked this, but does github have any provisions that would allow the PortIndex files to be generated on the server and served with the actual repo contents? That

Re: GitHub migration complete

2016-10-31 Thread Clemens Lang
Hi, On Mon, Oct 31, 2016 at 10:18:42AM +0100, René J. V. Bertin wrote: > I may have overlooked this, but does github have any provisions that > would allow the PortIndex files to be generated on the server and > served with the actual repo contents? That would probably give a very > significant

Re: GitHub migration complete

2016-10-31 Thread René J . V . Bertin
Clemens Lang wrote: > If your question is not yet answered, ask on the mailing lists so it can > be added. I may have overlooked this, but does github have any provisions that would allow the PortIndex files to be generated on the server and served with the actual repo contents? That would

Re: GitHub migration complete

2016-10-30 Thread Lawrence Velázquez
> On Oct 30, 2016, at 9:54 PM, Clemens Lang wrote: > > Our Subversion repository has been split into several repositories on > GitHub. Please note that Ryan ran the svn2git conversion several times this weekend, so any clones made previously will have nothing in common with

Re: GitHub migration complete

2016-10-30 Thread Ryan Schmidt
> On Oct 30, 2016, at 10:28 PM, Carlo Tambuatco wrote: > > Is that mailto link macports-users@lists.macosforge.org in the signature > still valid…? Yes, our previous mailing lists have not moved yet. And even when they do, the old addresses will remain valid.

GitHub migration complete

2016-10-30 Thread Clemens Lang
Good day MacPorts developers and users, We are pleased to announce that MacPorts has moved to GitHub. Our Subversion repository has been split into several repositories on GitHub . The buildbot, email notifications, and Trac are now triggered by changes made on GitHub. MacPorts developers