From hilel14 at gmail.com Sat Feb 1 06:26:53 2014 From: hilel14 at gmail.com (hilel14 at gmail.com) Date: Fri, 31 Jan 2014 22:26:53 -0800 (PST) Subject: Bi-directional text support In-Reply-To: References: Message-ID: <8c5cd6af-306c-44a1-9f36-9fdae827fe80@googlegroups.com> I added this entry: https://wiki.mozilla.org/Bugzilla:L10n:Localization_Teams#All_Bi-directional_languages to the list of localization teams. Thank you both, Liz and Gervase, for your help. Hilel Yits?aki _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gerv at mozilla.org Tue Feb 4 13:44:46 2014 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 04 Feb 2014 13:44:46 +0000 Subject: How to document our minimum module versions In-Reply-To: References: Message-ID: On 31/01/14 18:58, Fr?d?ric Buclin wrote: > No need. Requirements are already listed in the release notes: > > http://www.bugzilla.org/releases/4.4.2/release-notes.html#v44_req_perl In which case, we will proceed with the plan of not having this info in the reST documentation itself. Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From lpsolit at gmail.com Tue Feb 4 17:22:10 2014 From: lpsolit at gmail.com (=?UTF-8?B?RnLDqWTDqXJpYyBCdWNsaW4=?=) Date: Tue, 04 Feb 2014 18:22:10 +0100 Subject: How to document our minimum module versions In-Reply-To: References: Message-ID: <52F121C2.9040803@gmail.com> Le 04. 02. 14 14:44, Gervase Markham a ?crit : > In which case, we will proceed with the plan of not having this info in > the reST documentation itself. This is totally fine. Simply add a link pointing to the release notes on bugzilla.org. LpSolit From mcote at mozilla.com Sun Feb 16 05:41:32 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Sun, 16 Feb 2014 00:41:32 -0500 Subject: git migration scheduled for 11 March 2014 Message-ID: <53004F8C.3060700@mozilla.com> 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 dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mcote at mozilla.com Mon Feb 17 14:33:45 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Mon, 17 Feb 2014 09:33:45 -0500 Subject: git migration scheduled for 11 March 2014 In-Reply-To: <53004F8C.3060700@mozilla.com> References: <53004F8C.3060700@mozilla.com> Message-ID: 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 dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mcote at mozilla.com Wed Feb 19 04:47:58 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Tue, 18 Feb 2014 23:47:58 -0500 Subject: git migration scheduled for 11 March 2014 In-Reply-To: References: <53004F8C.3060700@mozilla.com> Message-ID: 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 dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From brian.wisti at gmail.com Wed Feb 19 05:12:27 2014 From: brian.wisti at gmail.com (Brian Wisti) Date: Tue, 18 Feb 2014 21:12:27 -0800 Subject: git migration scheduled for 11 March 2014 In-Reply-To: References: <53004F8C.3060700@mozilla.com> Message-ID: 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? 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 > dev-apps-bugzilla at lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-apps-bugzilla > - > To view or change your list settings, click here: > From cedric.corazza at gmail.com Fri Feb 21 21:56:37 2014 From: cedric.corazza at gmail.com (=?UTF-8?B?Q8OpZHJpYyBDb3Jhenph?=) Date: Fri, 21 Feb 2014 22:56:37 +0100 Subject: git migration scheduled for 11 March 2014 In-Reply-To: <53004F8C.3060700@mozilla.com> References: <53004F8C.3060700@mozilla.com> Message-ID: 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 dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From sdaugherty at gmail.com Fri Feb 21 22:25:00 2014 From: sdaugherty at gmail.com (Stephanie Daugherty) Date: Fri, 21 Feb 2014 17:25:00 -0500 Subject: git migration scheduled for 11 March 2014 In-Reply-To: References: <53004F8C.3060700@mozilla.com> Message-ID: 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 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 > dev-apps-bugzilla at lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-apps-bugzilla > - > To view or change your list settings, click here: > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cedric.corazza at gmail.com Fri Feb 21 22:30:31 2014 From: cedric.corazza at gmail.com (=?UTF-8?B?Q8OpZHJpYyBDb3Jhenph?=) Date: Fri, 21 Feb 2014 23:30:31 +0100 Subject: git migration scheduled for 11 March 2014 In-Reply-To: References: <53004F8C.3060700@mozilla.com> Message-ID: 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 dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mcote at mozilla.com Mon Feb 24 18:48:45 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Mon, 24 Feb 2014 13:48:45 -0500 Subject: git migration scheduled for 11 March 2014 In-Reply-To: References: <53004F8C.3060700@mozilla.com> Message-ID: <8-OdnYFug8eTCZbOnZ2dnUVZ_smdnZ2d@mozilla.org> 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 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 >> dev-apps-bugzilla at lists.mozilla.org >> https://lists.mozilla.org/listinfo/dev-apps-bugzilla >> - >> To view or change your list settings, click here: >> >> _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mcote at mozilla.com Thu Feb 27 18:11:55 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Thu, 27 Feb 2014 13:11:55 -0500 Subject: git migration scheduled for 11 March 2014 In-Reply-To: References: <53004F8C.3060700@mozilla.com> Message-ID: 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 dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gerv at mozilla.org Fri Feb 28 11:28:40 2014 From: gerv at mozilla.org (Gervase Markham) Date: Fri, 28 Feb 2014 11:28:40 +0000 Subject: git migration scheduled for 11 March 2014 In-Reply-To: References: <53004F8C.3060700@mozilla.com> Message-ID: 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 at hare:/tmp$ cd /usr/src/ gerv at hare:/usr/src$ git clone http://git.mozilla.org/bugzilla/bugzilla bugzilla-git Cloning into 'bugzilla-git'... ... gerv at hare:/usr/src$ cd bugzilla-git/ gerv at hare:/usr/src/bugzilla-git$ e robots.txt gerv at hare:/usr/src/bugzilla-git$ git add robots.txt gerv at hare:/usr/src/bugzilla-git$ git commit robots.txt [master 64e8f7c] Test commit. 1 file changed, 2 insertions(+) gerv at hare:/usr/src/bugzilla-git$ git push fatal: http://git.mozilla.org/bugzilla/bugzilla/info/refs not valid: is this a git repository? gerv at hare:/usr/src/bugzilla-git$ :-( What's gone wrong here? Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From denis.roy at eclipse.org Fri Feb 28 13:27:37 2014 From: denis.roy at eclipse.org (Denis Roy) Date: Fri, 28 Feb 2014 08:27:37 -0500 Subject: git migration scheduled for 11 March 2014 In-Reply-To: References: <53004F8C.3060700@mozilla.com> Message-ID: <53108EC9.5040808@eclipse.org> 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 at hare:/tmp$ cd /usr/src/ > gerv at hare:/usr/src$ git clone http://git.mozilla.org/bugzilla/bugzilla > bugzilla-git > Cloning into 'bugzilla-git'... > ... > gerv at hare:/usr/src$ cd bugzilla-git/ > gerv at hare:/usr/src/bugzilla-git$ e robots.txt > > gerv at hare:/usr/src/bugzilla-git$ git add robots.txt > gerv at hare:/usr/src/bugzilla-git$ git commit robots.txt > [master 64e8f7c] Test commit. > 1 file changed, 2 insertions(+) > gerv at hare:/usr/src/bugzilla-git$ git push > fatal: http://git.mozilla.org/bugzilla/bugzilla/info/refs not valid: is > this a git repository? > gerv at 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 From gerv at mozilla.org Fri Feb 28 13:49:48 2014 From: gerv at mozilla.org (Gervase Markham) Date: Fri, 28 Feb 2014 13:49:48 +0000 Subject: git migration scheduled for 11 March 2014 In-Reply-To: References: <53004F8C.3060700@mozilla.com> Message-ID: 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 at hare:/usr/src$ git clone ssh://gerv at mozilla.org@git.mozilla.org/bugzilla/bugzilla bugzilla-git2 nor gerv at hare:/usr/src$ git clone ssh://gerv at gerv.net@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 gerv at mozilla.org or gerv at gerv.net? Is it using my standard Mozilla LDAP public key? Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mcote at mozilla.com Fri Feb 28 16:02:26 2014 From: mcote at mozilla.com (=?UTF-8?B?TWFyayBDw7R0w6k=?=) Date: Fri, 28 Feb 2014 11:02:26 -0500 Subject: git migration scheduled for 11 March 2014 In-Reply-To: References: <53004F8C.3060700@mozilla.com> Message-ID: 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 at hare:/usr/src$ git clone > ssh://gerv at mozilla.org@git.mozilla.org/bugzilla/bugzilla bugzilla-git2 > > nor > > gerv at hare:/usr/src$ git clone > ssh://gerv at gerv.net@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 gerv at mozilla.org or gerv at gerv.net? 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://gitolite3 at git.mozilla.org/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 dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From justdave at bugzilla.org Fri Feb 28 21:52:50 2014 From: justdave at bugzilla.org (Dave Miller) Date: Fri, 28 Feb 2014 16:52:50 -0500 Subject: git migration scheduled for 11 March 2014 In-Reply-To: References: <53004F8C.3060700@mozilla.com> Message-ID: <53110532.3070206@bugzilla.org> 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://gitolite3 at git.mozilla.org/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/