Re: GitHub migration complete

[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 is it to 
> require that of them when the general consensus usually is that "users 
> shouldn't have to ".
> 
>> Feel free to ask on the -dev list, that's what it's for.
> 
> Well, sure. At least I cannot f*** anything up permanently since I don't have 
> commit access, and I'm not so sure how inclined I still am to try to get that 
> after the move to git (a matter of trust in myself).

You can also subscribe to the git users mailing list, as there are plenty of 
people who will answer "how do I do X" questions there.

git-us...@googlegroups.com

> 
> R.
> ___
> macports-users mailing list
> macports-users@lists.macosforge.org
> https://lists.macosforge.org/mailman/listinfo/macports-users

---
Entertaining minecraft videos
http://YouTube.com/keybounce

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: GitHub migration complete

[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 
shouldn't have to ".

> Feel free to ask on the -dev list, that's what it's for.

Well, sure. At least I cannot f*** anything up permanently since I don't have 
commit access, and I'm not so sure how inclined I still am to try to get that 
after the move to git (a matter of trust in myself).

R.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: GitHub migration complete

[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 least for some things?

Because people are supposed to use Trac. We do not want multiple bug trackers.


> I must admit that while I like git's simpler features I have a very hard time
> getting my head around the more advanced stuff and associated not-always-that-
> intuitive-to-me terminology (or getting its details into my head). Working 
> with
> branches, rebasing, etc., I'd like to think it becomes second nature when you 
> do
> it everyday, but that won't be the case for many if not most MacPorts users
> (including me).

It's something we all have to deal with. Presumably, we will all learn over 
time.


> [lament]
> Personally I have to look many things up every time, provided I even remember 
> or
> know of their existence (or I simply forget steps and then find myself with a
> commit I don't know how or cannot back out of).
> [/lament]

Feel free to ask on the -dev list, that's what it's for.

-- 
Clemens Lang
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: GitHub migration complete

[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 that while I like git's simpler features I have a very hard time 
getting my head around the more advanced stuff and associated not-always-that-
intuitive-to-me terminology (or getting its details into my head). Working with 
branches, rebasing, etc., I'd like to think it becomes second nature when you 
do 
it everyday, but that won't be the case for many if not most MacPorts users 
(including me). 

[lament]
Personally I have to look many things up every time, provided I even remember 
or 
know of their existence (or I simply forget steps and then find myself with a 
commit I don't know how or cannot back out of).
[/lament]

R.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: GitHub migration complete

[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 (including developers and maintainers) that clones the git 
>>> repository. Most users will use the rsync server, on which we do generate 
>>> portindexes for each macOS version.
>> 
>> Of course, but note how I used the word collective, which was supposed to 
>> include the idea that portindex has to be run each time by every user. :)
>> 
> 
> I would actually believe the number of affected users should be between
> very small and zero.

Pretty much.

In any case, between the capabilities of Git itself and the facilities GitHub 
provides, I do not believe it is possible to do what you suggest.

vq
Sent from my iPhone
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: GitHub migration complete

[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 each macOS version.

Of course, but note how I used the word collective, which was supposed to 
include the idea that portindex has to be run each time by every user. :)

R.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: GitHub migration complete

[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 PortIndex files to be generated on the server and served with the actual 
> repo 
> contents? That would probably give a very significant reduction in the 
> resources 
> spent collectively to regenerate those files...

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 each macOS version.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: GitHub migration complete

[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 but indeed port versions could be 
specific to OS version or platform even if no other specific information is 
stored.
Sorry for the noise.

Pity though, the first-run portindex of a fresh git clone just took about 5 
quarters of an hour on one of my machines (a good 5s/port).



That is a one time operation. hardly worth worrying about.


Additionally, git does not preserve timestamps from the repository on
checkout, so you might actually end up re-generating the index locally
anyway.


I think that wouldn't (or shouldn't) happen as the timestamp would be newer. 
And of course the auto-regeneration could be deactivated if the server always 
serves an up-to-date index.

R.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users


___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: GitHub migration complete

[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 OS version or platform even if no other specific information is 
stored.
Sorry for the noise.

Pity though, the first-run portindex of a fresh git clone just took about 5 
quarters of an hour on one of my machines (a good 5s/port).

>Additionally, git does not preserve timestamps from the repository on
>checkout, so you might actually end up re-generating the index locally
>anyway.

I think that wouldn't (or shouldn't) happen as the timestamp would be newer. 
And of course the auto-regeneration could be deactivated if the server always 
serves an up-to-date index.

R.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: GitHub migration complete

[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 would probably give a very
significant reduction in the resources spent collectively to
regenerate those files...


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
PortIndex could only generate all of them into different files.

Additionally, git does not preserve timestamps from the repository on
checkout, so you might actually end up re-generating the index locally
anyway.


After the initial checkout, when the first time generation of the index 
does take a short while, subsequent updates are from my perspective fast 
enough that this is not something to worry about. (I personally actually 
prefer to be generating it myself anyway).


Chris
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: GitHub migration complete

[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 reduction in the resources spent collectively to
> regenerate those files...

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
PortIndex could only generate all of them into different files.

Additionally, git does not preserve timestamps from the repository on
checkout, so you might actually end up re-generating the index locally
anyway.

-- 
Clemens
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: GitHub migration complete

[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 probably give a very significant reduction in the 
resources 
spent collectively to regenerate those files...

R.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: GitHub migration complete

[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
the final repositories, and a naïve "git pull" will try to produce
a merge commit. This is not desirable.

You should instead press the proverbial reset button. Assuming you made
a straightforward clone and only checked out a local master branch:

$ git fetch
$ git reset --hard origin/master
$ git gc --aggressive

This fetches the new history, forces your local master branch to match
ours, and garbage-collects the old objects.

vq
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

Re: GitHub migration complete

[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.

___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users

GitHub migration complete

[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 should now have commit access to the GitHub
repositories. If you are a MacPorts developer and have not yet joined
the MacPorts GitHub organization, please follow instructions in the FAQ
linked below.

If you have further questions, please refer to this new FAQ page:
https://trac.macports.org/wiki/FAQ/GitHubMigration

If your question is not yet answered, ask on the mailing lists so it can
be added.

We have tested the changes thoroughly, but in a system this complex
there might still be undiscovered problems. If you notice any, please do
not hesitate to ask on the mailing lists or file a ticket in Trac
against the "server/hosting" component.


On behalf of the MacPorts migration team,
Lawrence Velázquez
Rainer Müller
Ryan Schmidt
Clemens Lang
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users