git migration scheduled for 11 March 2014

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

git migration scheduled for 11 March 2014

Mark Côté
Hi all, I got IT's go-ahead to perform the bzr-to-git migration of
Bugzilla and related code from bzr.mozilla.org to git.mozilla.org on
Tuesday, 11 March 2014, starting at 17:00 UTC.  At this time, all Bazaar
branches on bzr.mozilla.org will be made read-only (aside from a few
admin accounts), and the migration to git repos on git.mozilla.org will
commence.  It should take around 1.5 hours to migrate everything, after
which point write access will be enabled on the git repos for all users
previously authorized on bzr.mozilla.org.  A script will periodically
mirror changes from git to bzr for all currently supported Bugzilla
branches (4.0, 4.2, and 4.4).  Changes will not be mirrored for any
other branches of Bugzilla nor any other related branches (extensions,
misc, etc.).

We will start mirroring changes to read-only repos on GitHub at some
point (to be determined) after the migration to git.mozilla.org.
git.mozilla.org will remain the repository of record, meaning the only
place to which changes should be committed by developers.  All
mirroring, e.g. to GitHub and bzr.mozilla.org, will be unidirectional.

We've already done one test migration; see http://git.mozilla.org.  It
was successful aside from some missed file deletions, resulting in extra
files on a handful of git repos after the migration.  I manually deleted
the superfluous files after migration, and I also fixed the migration
script to account for this oddity in Bazaar's fast-export output, so it
won't happen during the real migration.

I would like to open up testing to all developers, starting with another
complete, fresh migration, on Tuesday, 18 February 2014, around 17:00
UTC.  To test the git-to-bzr mirroring script, we'll create a new
branch, "migration-test", off of Bugzilla trunk and run the mirroring
script on it after the migration.  We'll leave it running until the real
migration, and I invite anyone with commit access to bzr.mozilla.org to
commit changes to the test-migration branch on git and ensure that they
are mirrored properly to bzr.

The full migration and testing plan, along with other details, is at
https://wiki.mozilla.org/Bugzilla:Migrating_to_git.

Mark
Manager of the bugzilla.mozilla.org development team
_______________________________________________
dev-apps-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>
Reply | Threaded
Open this post in threaded view
|

Re: git migration scheduled for 11 March 2014

Mark Côté
One correction: we will also be mirroring changes to the bugzilla/qa and
bmo/qa branches from git to bzr.

Mark


On 2/16/2014, 12:41 AM, Mark Côté wrote:

> Hi all, I got IT's go-ahead to perform the bzr-to-git migration of
> Bugzilla and related code from bzr.mozilla.org to git.mozilla.org on
> Tuesday, 11 March 2014, starting at 17:00 UTC.  At this time, all Bazaar
> branches on bzr.mozilla.org will be made read-only (aside from a few
> admin accounts), and the migration to git repos on git.mozilla.org will
> commence.  It should take around 1.5 hours to migrate everything, after
> which point write access will be enabled on the git repos for all users
> previously authorized on bzr.mozilla.org.  A script will periodically
> mirror changes from git to bzr for all currently supported Bugzilla
> branches (4.0, 4.2, and 4.4).  Changes will not be mirrored for any
> other branches of Bugzilla nor any other related branches (extensions,
> misc, etc.).
>
> We will start mirroring changes to read-only repos on GitHub at some
> point (to be determined) after the migration to git.mozilla.org.
> git.mozilla.org will remain the repository of record, meaning the only
> place to which changes should be committed by developers.  All
> mirroring, e.g. to GitHub and bzr.mozilla.org, will be unidirectional.
>
> We've already done one test migration; see http://git.mozilla.org.  It
> was successful aside from some missed file deletions, resulting in extra
> files on a handful of git repos after the migration.  I manually deleted
> the superfluous files after migration, and I also fixed the migration
> script to account for this oddity in Bazaar's fast-export output, so it
> won't happen during the real migration.
>
> I would like to open up testing to all developers, starting with another
> complete, fresh migration, on Tuesday, 18 February 2014, around 17:00
> UTC.  To test the git-to-bzr mirroring script, we'll create a new
> branch, "migration-test", off of Bugzilla trunk and run the mirroring
> script on it after the migration.  We'll leave it running until the real
> migration, and I invite anyone with commit access to bzr.mozilla.org to
> commit changes to the test-migration branch on git and ensure that they
> are mirrored properly to bzr.
>
> The full migration and testing plan, along with other details, is at
> https://wiki.mozilla.org/Bugzilla:Migrating_to_git.
>
> Mark
> Manager of the bugzilla.mozilla.org development team
>

_______________________________________________
dev-apps-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=$MSGRCPT>
Reply | Threaded
Open this post in threaded view
|

Re: git migration scheduled for 11 March 2014

Mark Côté
There were a few complications getting the mirroring script up today; we
need a few bits of infrastructure tweaked.  I'll announce when it's
running, hopefully by next week some time.

Mark


On 2/17/2014, 9:33 AM, Mark Côté wrote:

> One correction: we will also be mirroring changes to the bugzilla/qa and
> bmo/qa branches from git to bzr.
>
> Mark
>
>
> On 2/16/2014, 12:41 AM, Mark Côté wrote:
>> Hi all, I got IT's go-ahead to perform the bzr-to-git migration of
>> Bugzilla and related code from bzr.mozilla.org to git.mozilla.org on
>> Tuesday, 11 March 2014, starting at 17:00 UTC.  At this time, all Bazaar
>> branches on bzr.mozilla.org will be made read-only (aside from a few
>> admin accounts), and the migration to git repos on git.mozilla.org will
>> commence.  It should take around 1.5 hours to migrate everything, after
>> which point write access will be enabled on the git repos for all users
>> previously authorized on bzr.mozilla.org.  A script will periodically
>> mirror changes from git to bzr for all currently supported Bugzilla
>> branches (4.0, 4.2, and 4.4).  Changes will not be mirrored for any
>> other branches of Bugzilla nor any other related branches (extensions,
>> misc, etc.).
>>
>> We will start mirroring changes to read-only repos on GitHub at some
>> point (to be determined) after the migration to git.mozilla.org.
>> git.mozilla.org will remain the repository of record, meaning the only
>> place to which changes should be committed by developers.  All
>> mirroring, e.g. to GitHub and bzr.mozilla.org, will be unidirectional.
>>
>> We've already done one test migration; see http://git.mozilla.org.  It
>> was successful aside from some missed file deletions, resulting in extra
>> files on a handful of git repos after the migration.  I manually deleted
>> the superfluous files after migration, and I also fixed the migration
>> script to account for this oddity in Bazaar's fast-export output, so it
>> won't happen during the real migration.
>>
>> I would like to open up testing to all developers, starting with another
>> complete, fresh migration, on Tuesday, 18 February 2014, around 17:00
>> UTC.  To test the git-to-bzr mirroring script, we'll create a new
>> branch, "migration-test", off of Bugzilla trunk and run the mirroring
>> script on it after the migration.  We'll leave it running until the real
>> migration, and I invite anyone with commit access to bzr.mozilla.org to
>> commit changes to the test-migration branch on git and ensure that they
>> are mirrored properly to bzr.
>>
>> The full migration and testing plan, along with other details, is at
>> https://wiki.mozilla.org/Bugzilla:Migrating_to_git.
>>
>> Mark
>> Manager of the bugzilla.mozilla.org development team
>>
>

_______________________________________________
dev-apps-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=$MSGRCPT>
Reply | Threaded
Open this post in threaded view
|

Re: git migration scheduled for 11 March 2014

Brian Wisti
Thanks for the update. Looking forward to it!


Kind Regards,
Brian Wisti
http://randomgeekery.org


On Tue, Feb 18, 2014 at 8:47 PM, Mark Côté <[hidden email]> wrote:

> There were a few complications getting the mirroring script up today; we
> need a few bits of infrastructure tweaked.  I'll announce when it's
> running, hopefully by next week some time.
>
> Mark
>
>
> On 2/17/2014, 9:33 AM, Mark Côté wrote:
>> One correction: we will also be mirroring changes to the bugzilla/qa and
>> bmo/qa branches from git to bzr.
>>
>> Mark
>>
>>
>> On 2/16/2014, 12:41 AM, Mark Côté wrote:
>>> Hi all, I got IT's go-ahead to perform the bzr-to-git migration of
>>> Bugzilla and related code from bzr.mozilla.org to git.mozilla.org on
>>> Tuesday, 11 March 2014, starting at 17:00 UTC.  At this time, all Bazaar
>>> branches on bzr.mozilla.org will be made read-only (aside from a few
>>> admin accounts), and the migration to git repos on git.mozilla.org will
>>> commence.  It should take around 1.5 hours to migrate everything, after
>>> which point write access will be enabled on the git repos for all users
>>> previously authorized on bzr.mozilla.org.  A script will periodically
>>> mirror changes from git to bzr for all currently supported Bugzilla
>>> branches (4.0, 4.2, and 4.4).  Changes will not be mirrored for any
>>> other branches of Bugzilla nor any other related branches (extensions,
>>> misc, etc.).
>>>
>>> We will start mirroring changes to read-only repos on GitHub at some
>>> point (to be determined) after the migration to git.mozilla.org.
>>> git.mozilla.org will remain the repository of record, meaning the only
>>> place to which changes should be committed by developers.  All
>>> mirroring, e.g. to GitHub and bzr.mozilla.org, will be unidirectional.
>>>
>>> We've already done one test migration; see http://git.mozilla.org.  It
>>> was successful aside from some missed file deletions, resulting in extra
>>> files on a handful of git repos after the migration.  I manually deleted
>>> the superfluous files after migration, and I also fixed the migration
>>> script to account for this oddity in Bazaar's fast-export output, so it
>>> won't happen during the real migration.
>>>
>>> I would like to open up testing to all developers, starting with another
>>> complete, fresh migration, on Tuesday, 18 February 2014, around 17:00
>>> UTC.  To test the git-to-bzr mirroring script, we'll create a new
>>> branch, "migration-test", off of Bugzilla trunk and run the mirroring
>>> script on it after the migration.  We'll leave it running until the real
>>> migration, and I invite anyone with commit access to bzr.mozilla.org to
>>> commit changes to the test-migration branch on git and ensure that they
>>> are mirrored properly to bzr.
>>>
>>> The full migration and testing plan, along with other details, is at
>>> https://wiki.mozilla.org/Bugzilla:Migrating_to_git.
>>>
>>> Mark
>>> Manager of the bugzilla.mozilla.org development team
>>>
>>
>
> _______________________________________________
> dev-apps-bugzilla mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-apps-bugzilla
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>
Reply | Threaded
Open this post in threaded view
|

Re: git migration scheduled for 11 March 2014

Cédric Corazza
In reply to this post by Mark Côté
Hi Mark,

I'm a Bugzilla localizer. I used to follow templates modifications for
every active branch on http://bzr.mozilla.org/bugzilla subscribing to
atom feed for each branch and having English separate repositories for
each branch to run tests (t/).
I don't know git (yet), but consulting the link you gave
https://git.mozilla.org, I'm neither able to see where the code for the
different branches resides nor how to get warned about modification on
templates.
Is there a mozilla wiki page or some other documentation you can lead me
to to get similar behaviour with git?
Thanks

Cédric
_______________________________________________
dev-apps-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=$MSGRCPT>
Reply | Threaded
Open this post in threaded view
|

Re: git migration scheduled for 11 March 2014

Stephanie Daugherty
to answer the first part, https://git.mozilla.org/?p=bugzilla/bugzilla.git;a=summary then look down to see "heads"

Each of these are either branches or tags.

You can switch easily between branches on the same repository with git checkout - the workflows are very similar to bzr but you'll notice branching (and jumps between branches) will probably be much faster since git was designed around making branching as fast as possible to support topic branches.

There are some great (and short!) video tutorials at http://git-scm.com/ also that should help you understand things and get up to speed quickly.




On Fri, Feb 21, 2014 at 4:56 PM, Cédric Corazza <[hidden email]> wrote:
Hi Mark,

I'm a Bugzilla localizer. I used to follow templates modifications for every active branch on http://bzr.mozilla.org/bugzilla subscribing to atom feed for each branch and having English separate repositories for each branch to run tests (t/).
I don't know git (yet), but consulting the link you gave https://git.mozilla.org, I'm neither able to see where the code for the different branches resides nor how to get warned about modification on templates.
Is there a mozilla wiki page or some other documentation you can lead me to to get similar behaviour with git?
Thanks

Cédric

_______________________________________________
dev-apps-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>

Reply | Threaded
Open this post in threaded view
|

Re: git migration scheduled for 11 March 2014

Cédric Corazza
In reply to this post by Cédric Corazza
Le 21/02/2014 23:25, Stephanie Daugherty a écrit :

> to answer the first part,
> https://git.mozilla.org/?p=bugzilla/bugzilla.git;a=summary then look down
> to see "heads"
>
> Each of these are either branches or tags.
>
> You can switch easily between branches on the same repository with git
> checkout - the workflows are very similar to bzr but you'll notice
> branching (and jumps between branches) will probably be much faster since
> git was designed around making branching as fast as possible to support
> topic branches.
>
> There are some great (and short!) video tutorials at
> http://git-scm.com/also that should help you understand things and get
> up to speed quickly.

Thanks Stephanie,
I will look into this tomorrow.

Cédric

_______________________________________________
dev-apps-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=$MSGRCPT>
Reply | Threaded
Open this post in threaded view
|

Re: git migration scheduled for 11 March 2014

Mark Côté
In reply to this post by Cédric Corazza
Also, if you go to the "log" link beside the branch names under "heads"
and then scroll to the bottom, there are Atom and RSS links.  When we
start mirroring to github, you'll be able to subscribe there as well.

Mark


On 2/21/2014, 5:25 PM, Stephanie Daugherty wrote:

> to answer the first part,
> https://git.mozilla.org/?p=bugzilla/bugzilla.git;a=summary then look down
> to see "heads"
>
> Each of these are either branches or tags.
>
> You can switch easily between branches on the same repository with git
> checkout - the workflows are very similar to bzr but you'll notice
> branching (and jumps between branches) will probably be much faster since
> git was designed around making branching as fast as possible to support
> topic branches.
>
> There are some great (and short!) video tutorials at
> http://git-scm.com/also that should help you understand things and get
> up to speed quickly.
>
>
>
>
> On Fri, Feb 21, 2014 at 4:56 PM, Cédric Corazza <[hidden email]>wrote:
>
>> Hi Mark,
>>
>> I'm a Bugzilla localizer. I used to follow templates modifications for
>> every active branch on http://bzr.mozilla.org/bugzilla subscribing to
>> atom feed for each branch and having English separate repositories for each
>> branch to run tests (t/).
>> I don't know git (yet), but consulting the link you gave
>> https://git.mozilla.org, I'm neither able to see where the code for the
>> different branches resides nor how to get warned about modification on
>> templates.
>> Is there a mozilla wiki page or some other documentation you can lead me
>> to to get similar behaviour with git?
>> Thanks
>>
>> Cédric
>>
>> _______________________________________________
>> dev-apps-bugzilla mailing list
>> [hidden email]
>> https://lists.mozilla.org/listinfo/dev-apps-bugzilla
>> -
>> To view or change your list settings, click here:
>> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps-bugzilla@...>
>>

_______________________________________________
dev-apps-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=$MSGRCPT>
Reply | Threaded
Open this post in threaded view
|

Re: git migration scheduled for 11 March 2014

Mark Côté
In reply to this post by Mark Côté
The mirroring script is now running every 5 minutes on the new
migration_test Bugzilla branch.

See
http://git.mozilla.org/?p=bugzilla/bugzilla.git;a=shortlog;h=refs/heads/migration_test
for the log of changes to this branch in git.  Within 5 minutes, any
changes should be visible on bzr at
http://bzr.mozilla.org/bugzilla/migration_test/changes.  Note that each
bzr commit will also have a change to the .gitrev file, which keeps
track of which git commits have already been mirrored over.

Anyone with commit access to Bugzilla on bzr.mozilla.org should have
commit access to the Bugzilla git repo; I invite you to make some
changes to the migration_test branch and ensure that they appear
correctly in bzr.

My last task is updating the wiki pages concerning the submission of
patches to Bugzilla.  The migration date of 11 March 2014 is still in place.

Mark


On 2014-02-18, 11:47 PM, Mark Côté wrote:

> There were a few complications getting the mirroring script up today; we
> need a few bits of infrastructure tweaked.  I'll announce when it's
> running, hopefully by next week some time.
>
> Mark
>
>
> On 2/17/2014, 9:33 AM, Mark Côté wrote:
>> One correction: we will also be mirroring changes to the bugzilla/qa and
>> bmo/qa branches from git to bzr.
>>
>> Mark
>>
>>
>> On 2/16/2014, 12:41 AM, Mark Côté wrote:
>>> Hi all, I got IT's go-ahead to perform the bzr-to-git migration of
>>> Bugzilla and related code from bzr.mozilla.org to git.mozilla.org on
>>> Tuesday, 11 March 2014, starting at 17:00 UTC.  At this time, all Bazaar
>>> branches on bzr.mozilla.org will be made read-only (aside from a few
>>> admin accounts), and the migration to git repos on git.mozilla.org will
>>> commence.  It should take around 1.5 hours to migrate everything, after
>>> which point write access will be enabled on the git repos for all users
>>> previously authorized on bzr.mozilla.org.  A script will periodically
>>> mirror changes from git to bzr for all currently supported Bugzilla
>>> branches (4.0, 4.2, and 4.4).  Changes will not be mirrored for any
>>> other branches of Bugzilla nor any other related branches (extensions,
>>> misc, etc.).
>>>
>>> We will start mirroring changes to read-only repos on GitHub at some
>>> point (to be determined) after the migration to git.mozilla.org.
>>> git.mozilla.org will remain the repository of record, meaning the only
>>> place to which changes should be committed by developers.  All
>>> mirroring, e.g. to GitHub and bzr.mozilla.org, will be unidirectional.
>>>
>>> We've already done one test migration; see http://git.mozilla.org.  It
>>> was successful aside from some missed file deletions, resulting in extra
>>> files on a handful of git repos after the migration.  I manually deleted
>>> the superfluous files after migration, and I also fixed the migration
>>> script to account for this oddity in Bazaar's fast-export output, so it
>>> won't happen during the real migration.
>>>
>>> I would like to open up testing to all developers, starting with another
>>> complete, fresh migration, on Tuesday, 18 February 2014, around 17:00
>>> UTC.  To test the git-to-bzr mirroring script, we'll create a new
>>> branch, "migration-test", off of Bugzilla trunk and run the mirroring
>>> script on it after the migration.  We'll leave it running until the real
>>> migration, and I invite anyone with commit access to bzr.mozilla.org to
>>> commit changes to the test-migration branch on git and ensure that they
>>> are mirrored properly to bzr.
>>>
>>> The full migration and testing plan, along with other details, is at
>>> https://wiki.mozilla.org/Bugzilla:Migrating_to_git.
>>>
>>> Mark
>>> Manager of the bugzilla.mozilla.org development team
>>>
>>
>

_______________________________________________
dev-apps-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=$MSGRCPT>
Reply | Threaded
Open this post in threaded view
|

Re: git migration scheduled for 11 March 2014

Gervase Markham
On 27/02/14 18:11, Mark Côté wrote:
> Anyone with commit access to Bugzilla on bzr.mozilla.org should have
> commit access to the Bugzilla git repo; I invite you to make some
> changes to the migration_test branch and ensure that they appear
> correctly in bzr.

gerv@hare:/tmp$ cd /usr/src/
gerv@hare:/usr/src$ git clone http://git.mozilla.org/bugzilla/bugzilla
bugzilla-git
Cloning into 'bugzilla-git'...
...
gerv@hare:/usr/src$ cd bugzilla-git/
gerv@hare:/usr/src/bugzilla-git$ e robots.txt
<edit>
gerv@hare:/usr/src/bugzilla-git$ git add robots.txt
gerv@hare:/usr/src/bugzilla-git$ git commit robots.txt
[master 64e8f7c] Test commit.
 1 file changed, 2 insertions(+)
gerv@hare:/usr/src/bugzilla-git$ git push
fatal: http://git.mozilla.org/bugzilla/bugzilla/info/refs not valid: is
this a git repository?
gerv@hare:/usr/src/bugzilla-git$


:-( What's gone wrong here?

Gerv

_______________________________________________
dev-apps-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=$MSGRCPT>
Reply | Threaded
Open this post in threaded view
|

Re: git migration scheduled for 11 March 2014

Denis Roy

On 02/28/2014 06:28 AM, Gervase Markham wrote:

> On 27/02/14 18:11, Mark Côté wrote:
>> Anyone with commit access to Bugzilla on bzr.mozilla.org should have
>> commit access to the Bugzilla git repo; I invite you to make some
>> changes to the migration_test branch and ensure that they appear
>> correctly in bzr.
> gerv@hare:/tmp$ cd /usr/src/
> gerv@hare:/usr/src$ git clone http://git.mozilla.org/bugzilla/bugzilla
> bugzilla-git
> Cloning into 'bugzilla-git'...
> ...
> gerv@hare:/usr/src$ cd bugzilla-git/
> gerv@hare:/usr/src/bugzilla-git$ e robots.txt
> <edit>
> gerv@hare:/usr/src/bugzilla-git$ git add robots.txt
> gerv@hare:/usr/src/bugzilla-git$ git commit robots.txt
> [master 64e8f7c] Test commit.
>   1 file changed, 2 insertions(+)
> gerv@hare:/usr/src/bugzilla-git$ git push
> fatal: http://git.mozilla.org/bugzilla/bugzilla/info/refs not valid: is
> this a git repository?
> gerv@hare:/usr/src/bugzilla-git$
>
>
> :-( What's gone wrong here?

You seem to be cloning anonymously.  Try using your committer ID and
https (or ssh).

Denis
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>
Reply | Threaded
Open this post in threaded view
|

Re: git migration scheduled for 11 March 2014

Gervase Markham
In reply to this post by Gervase Markham
On 28/02/14 13:27, Denis Roy wrote:
> You seem to be cloning anonymously.  Try using your committer ID and
> https (or ssh).

If I am cloning anonymously and I am in fact being denied permission to
write, then:

"fatal: http://git.mozilla.org/bugzilla/bugzilla/info/refs not valid: is
this a git repository?"

is a pretty sucky error message to tell me so!


Neither

gerv@hare:/usr/src$ git clone
ssh://[hidden email]@git.mozilla.org/bugzilla/bugzilla bugzilla-git2

nor

gerv@hare:/usr/src$ git clone
ssh://[hidden email]@git.mozilla.org/bugzilla/bugzilla bugzilla-git2

work - both give permission denied. mcote: when you say you have ensured
that the same people have access permissions, how have you done that? Am
I [hidden email] or [hidden email]? Is it using my standard Mozilla
LDAP public key?

Gerv


_______________________________________________
dev-apps-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>
Reply | Threaded
Open this post in threaded view
|

Re: git migration scheduled for 11 March 2014

Mark Côté
On 2014-02-28, 8:49 AM, Gervase Markham wrote:

> On 28/02/14 13:27, Denis Roy wrote:
>> You seem to be cloning anonymously.  Try using your committer ID and
>> https (or ssh).
>
> If I am cloning anonymously and I am in fact being denied permission to
> write, then:
>
> "fatal: http://git.mozilla.org/bugzilla/bugzilla/info/refs not valid: is
> this a git repository?"
>
> is a pretty sucky error message to tell me so!
>
>
> Neither
>
> gerv@hare:/usr/src$ git clone
> ssh://[hidden email]@git.mozilla.org/bugzilla/bugzilla bugzilla-git2
>
> nor
>
> gerv@hare:/usr/src$ git clone
> ssh://[hidden email]@git.mozilla.org/bugzilla/bugzilla bugzilla-git2
>
> work - both give permission denied. mcote: when you say you have ensured
> that the same people have access permissions, how have you done that? Am
> I [hidden email] or [hidden email]? Is it using my standard Mozilla
> LDAP public key?
>
> Gerv
>
>

If you go to the summary on git.mozilla.org, i.e.
http://git.mozilla.org/?p=bugzilla/bugzilla.git;a=commit;h=71eecc5cad02839e0206f46c6d0b0f77c5555081

you'll see that the URL is
ssh://[hidden email]/bugzilla/bugzilla.git

This is a bit weird, I know, but it's pretty typical for git.  GitHub
ssh URLs are similar (though with just "git@" instead of the overly long
"gitolite3").

Your LDAP key will work with this login.

Mark

_______________________________________________
dev-apps-bugzilla mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-apps-bugzilla
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>
Reply | Threaded
Open this post in threaded view
|

Re: git migration scheduled for 11 March 2014

Dave Miller
Yeah, the thing to get used to here is that all access to the git server
is done as a single user, everyone uses the same user.  It identifies
who you are by which ssh key you authenticate with. (This also means if
you have more than one account, you need more than one SSH key -
something I've run into on github already for role accounts)

Mark Côté wrote:
> you'll see that the URL is
> ssh://[hidden email]/bugzilla/bugzilla.git
>
> This is a bit weird, I know, but it's pretty typical for git.  GitHub
> ssh URLs are similar (though with just "git@" instead of the overly long
> "gitolite3").
>
> Your LDAP key will work with this login.

--
Dave Miller http://www.justdave.net/
IT Infrastructure Engineer, Mozilla http://www.mozilla.org/
Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/

-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists+s6506n84121h51@...>