Hi, Mark & Al
I've tried to catch up the latest progress of armv8 bootstrap project. However, it seems that there is problem when fetching the rootfs' git repository. The latest HEAD that I can fetch is still at 3e7ab1be, which is commited on Dec 31 2012. Everytime I was trying to update, the git turns out the following error:
error: Unable to find bdb05d63675b92a8376f651e58e501f375342c11 under http://fedorapeople.org/groups/armv8/rootfs.git Cannot obtain needed commit bdb05d63675b92a8376f651e58e501f375342c11 while processing commit 06add7ca8ae78621a8b6c279d575b1ed52ed7c31. error: Fetch failed.
Are there any other ways to fetch the repository to participate in the current stage-3?
Cheers,
Baozi
On Mon, 2013-01-28 at 19:38 +0800, Chen Baozi wrote:
Hi, Mark & Al
I've tried to catch up the latest progress of armv8 bootstrap project. However, it seems that there is problem when fetching the rootfs' git repository. The latest HEAD that I can fetch is still at 3e7ab1be, which is commited on Dec 31 2012. Everytime I was trying to update, the git turns out the following error:
error: Unable to find bdb05d63675b92a8376f651e58e501f375342c11 under http://fedorapeople.org/groups/armv8/rootfs.git Cannot obtain needed commit bdb05d63675b92a8376f651e58e501f375342c11 while processing commit 06add7ca8ae78621a8b6c279d575b1ed52ed7c31. error: Fetch failed.
Are there any other ways to fetch the repository to participate in the current stage-3?
I'm trying a clean checkout now and will let you know how it goes.
--Mark
On Mon, 2013-01-28 at 11:42 -0500, Mark Salter wrote:
On Mon, 2013-01-28 at 19:38 +0800, Chen Baozi wrote:
Hi, Mark & Al
I've tried to catch up the latest progress of armv8 bootstrap project. However, it seems that there is problem when fetching the rootfs' git repository. The latest HEAD that I can fetch is still at 3e7ab1be, which is commited on Dec 31 2012. Everytime I was trying to update, the git turns out the following error:
error: Unable to find bdb05d63675b92a8376f651e58e501f375342c11 under http://fedorapeople.org/groups/armv8/rootfs.git Cannot obtain needed commit bdb05d63675b92a8376f651e58e501f375342c11 while processing commit 06add7ca8ae78621a8b6c279d575b1ed52ed7c31. error: Fetch failed.
Are there any other ways to fetch the repository to participate in the current stage-3?
I'm trying a clean checkout now and will let you know how it goes.
Well, it worked for me. Not sure what happened with your checkout. FWIW, bdb05d63675b92a8376f65 is a commit on msalter-stage2 branch which I cherry picked from commit 92813f26e2f7298da7e277cf on the master branch.
--Mark
Thanks, Mark. I've switched to another machine which has better network connection. And It finally works, :) I guess something I've checkout before was corrupt due to both my poor network connection and big size of the rootfs.
BTW, seems it is not up-to-date? I mean there is no /stage3 under the rootfs.
Cheers,
Baozi
On Mon, Jan 28, 2013 at 11:54:08AM -0500, Mark Salter wrote:
On Mon, 2013-01-28 at 11:42 -0500, Mark Salter wrote:
On Mon, 2013-01-28 at 19:38 +0800, Chen Baozi wrote:
Hi, Mark & Al
I've tried to catch up the latest progress of armv8 bootstrap project. However, it seems that there is problem when fetching the rootfs' git repository. The latest HEAD that I can fetch is still at 3e7ab1be, which is commited on Dec 31 2012. Everytime I was trying to update, the git turns out the following error:
error: Unable to find bdb05d63675b92a8376f651e58e501f375342c11 under http://fedorapeople.org/groups/armv8/rootfs.git Cannot obtain needed commit bdb05d63675b92a8376f651e58e501f375342c11 while processing commit 06add7ca8ae78621a8b6c279d575b1ed52ed7c31. error: Fetch failed.
Are there any other ways to fetch the repository to participate in the current stage-3?
I'm trying a clean checkout now and will let you know how it goes.
Well, it worked for me. Not sure what happened with your checkout. FWIW, bdb05d63675b92a8376f65 is a commit on msalter-stage2 branch which I cherry picked from commit 92813f26e2f7298da7e277cf on the master branch.
--Mark
On Tue, 2013-01-29 at 09:05 +0800, Chen Baozi wrote:
Thanks, Mark. I've switched to another machine which has better network connection. And It finally works, :) I guess something I've checkout before was corrupt due to both my poor network connection and big size of the rootfs.
BTW, seems it is not up-to-date? I mean there is no /stage3 under the rootfs.
Hmm. I looked closer at the tree I checked out and it too had a head at commit 3e7ab1bee31082a0 from Al on Dec 31. I'm at a loss to explain what is going wrong. I have a local tree that appears to be up to date with the repo on fedoraproject.org but the log shows 18 commits which aren't in the tree I cloned from fedoraproject.org repo earlier today. I'll try and see if I can sort it all out tomorrow.
--Mark
On Tue, Jan 29, 2013 at 12:52:24AM -0500, Mark Salter wrote:
On Tue, 2013-01-29 at 09:05 +0800, Chen Baozi wrote:
Thanks, Mark. I've switched to another machine which has better network connection. And It finally works, :) I guess something I've checkout before was corrupt due to both my poor network connection and big size of the rootfs.
BTW, seems it is not up-to-date? I mean there is no /stage3 under the rootfs.
Hmm. I looked closer at the tree I checked out and it too had a head at commit 3e7ab1bee31082a0 from Al on Dec 31. I'm at a loss to explain what
It is the same with my local git tree.
is going wrong. I have a local tree that appears to be up to date with the repo on fedoraproject.org but the log shows 18 commits which aren't in the tree I cloned from fedoraproject.org repo earlier today. I'll try and see if I can sort it all out tomorrow.
Thanks a lot.
Baozi
--Mark
On Tue, 2013-01-29 at 14:12 +0800, Chen Baozi wrote:
On Tue, Jan 29, 2013 at 12:52:24AM -0500, Mark Salter wrote:
On Tue, 2013-01-29 at 09:05 +0800, Chen Baozi wrote:
Thanks, Mark. I've switched to another machine which has better network connection. And It finally works, :) I guess something I've checkout before was corrupt due to both my poor network connection and big size of the rootfs.
BTW, seems it is not up-to-date? I mean there is no /stage3 under the rootfs.
Hmm. I looked closer at the tree I checked out and it too had a head at commit 3e7ab1bee31082a0 from Al on Dec 31. I'm at a loss to explain what
It is the same with my local git tree.
is going wrong. I have a local tree that appears to be up to date with the repo on fedoraproject.org but the log shows 18 commits which aren't in the tree I cloned from fedoraproject.org repo earlier today. I'll try and see if I can sort it all out tomorrow.
Thanks a lot.
Baozi
Al, this may be something for you to look at. If I clone the repo using http, I get 3e7ab1bee31082a as the lastest commit. If I use ssh+git, I get everything correctly.
--Mark
On 01/29/2013 11:09 AM, Mark Salter wrote:
On Tue, 2013-01-29 at 14:12 +0800, Chen Baozi wrote:
On Tue, Jan 29, 2013 at 12:52:24AM -0500, Mark Salter wrote:
On Tue, 2013-01-29 at 09:05 +0800, Chen Baozi wrote:
Thanks, Mark. I've switched to another machine which has better network connection. And It finally works, :) I guess something I've checkout before was corrupt due to both my poor network connection and big size of the rootfs.
BTW, seems it is not up-to-date? I mean there is no /stage3 under the rootfs.
Hmm. I looked closer at the tree I checked out and it too had a head at commit 3e7ab1bee31082a0 from Al on Dec 31. I'm at a loss to explain what
It is the same with my local git tree.
is going wrong. I have a local tree that appears to be up to date with the repo on fedoraproject.org but the log shows 18 commits which aren't in the tree I cloned from fedoraproject.org repo earlier today. I'll try and see if I can sort it all out tomorrow.
Thanks a lot.
Baozi
Al, this may be something for you to look at. If I clone the repo using http, I get 3e7ab1bee31082a as the lastest commit. If I use ssh+git, I get everything correctly.
--Mark
The only thing I can think of right now is that 'git update-server-info' may not be getting run on updates to the repo for some reason. I've run it by hand to see if this changes the behavior -- let me know if you now get the most recent commit. If not, I'll have to poke the infrastructure folks. The short term workaround is to use ssh+git, as you indicated.
Infrastructure and I have been struggling with the underlying problem that http and git and SELinux are in a bit of a disagreement on how access should work -- and it's http that's been losing out so far.
On Tue, 2013-01-29 at 11:23 -0700, Al Stone wrote:
On 01/29/2013 11:09 AM, Mark Salter wrote:
On Tue, 2013-01-29 at 14:12 +0800, Chen Baozi wrote:
On Tue, Jan 29, 2013 at 12:52:24AM -0500, Mark Salter wrote:
On Tue, 2013-01-29 at 09:05 +0800, Chen Baozi wrote:
Thanks, Mark. I've switched to another machine which has better network connection. And It finally works, :) I guess something I've checkout before was corrupt due to both my poor network connection and big size of the rootfs.
BTW, seems it is not up-to-date? I mean there is no /stage3 under the rootfs.
Hmm. I looked closer at the tree I checked out and it too had a head at commit 3e7ab1bee31082a0 from Al on Dec 31. I'm at a loss to explain what
It is the same with my local git tree.
is going wrong. I have a local tree that appears to be up to date with the repo on fedoraproject.org but the log shows 18 commits which aren't in the tree I cloned from fedoraproject.org repo earlier today. I'll try and see if I can sort it all out tomorrow.
Thanks a lot.
Baozi
Al, this may be something for you to look at. If I clone the repo using http, I get 3e7ab1bee31082a as the lastest commit. If I use ssh+git, I get everything correctly.
--Mark
The only thing I can think of right now is that 'git update-server-info' may not be getting run on updates to the repo for some reason. I've run it by hand to see if this changes the behavior -- let me know if you now get the most recent commit. If not, I'll have to poke the infrastructure folks. The short term workaround is to use ssh+git, as you indicated.
Infrastructure and I have been struggling with the underlying problem that http and git and SELinux are in a bit of a disagreement on how access should work -- and it's http that's been losing out so far.
Yay. A clone using http did get the latest bits.
On 01/29/2013 03:10 PM, Mark Salter wrote:
On Tue, 2013-01-29 at 11:23 -0700, Al Stone wrote:
On 01/29/2013 11:09 AM, Mark Salter wrote:
On Tue, 2013-01-29 at 14:12 +0800, Chen Baozi wrote:
On Tue, Jan 29, 2013 at 12:52:24AM -0500, Mark Salter wrote:
On Tue, 2013-01-29 at 09:05 +0800, Chen Baozi wrote:
Thanks, Mark. I've switched to another machine which has better network connection. And It finally works, :) I guess something I've checkout before was corrupt due to both my poor network connection and big size of the rootfs.
BTW, seems it is not up-to-date? I mean there is no /stage3 under the rootfs.
Hmm. I looked closer at the tree I checked out and it too had a head at commit 3e7ab1bee31082a0 from Al on Dec 31. I'm at a loss to explain what
It is the same with my local git tree.
is going wrong. I have a local tree that appears to be up to date with the repo on fedoraproject.org but the log shows 18 commits which aren't in the tree I cloned from fedoraproject.org repo earlier today. I'll try and see if I can sort it all out tomorrow.
Thanks a lot.
Baozi
Al, this may be something for you to look at. If I clone the repo using http, I get 3e7ab1bee31082a as the lastest commit. If I use ssh+git, I get everything correctly.
--Mark
The only thing I can think of right now is that 'git update-server-info' may not be getting run on updates to the repo for some reason. I've run it by hand to see if this changes the behavior -- let me know if you now get the most recent commit. If not, I'll have to poke the infrastructure folks. The short term workaround is to use ssh+git, as you indicated.
Infrastructure and I have been struggling with the underlying problem that http and git and SELinux are in a bit of a disagreement on how access should work -- and it's http that's been losing out so far.
Yay. A clone using http did get the latest bits.
Well, we now know the workaround; do the commit, then ssh into fp.o and run git update-server-info in the repo. Ugly, but it works.
I'm not sure this is fixable, but I'll poke the infrastructure folks and see what we can do.
On Tue, Jan 29, 2013 at 03:24:47PM -0700, Al Stone wrote:
On 01/29/2013 03:10 PM, Mark Salter wrote:
On Tue, 2013-01-29 at 11:23 -0700, Al Stone wrote:
On 01/29/2013 11:09 AM, Mark Salter wrote:
On Tue, 2013-01-29 at 14:12 +0800, Chen Baozi wrote:
On Tue, Jan 29, 2013 at 12:52:24AM -0500, Mark Salter wrote:
On Tue, 2013-01-29 at 09:05 +0800, Chen Baozi wrote: >Thanks, Mark. I've switched to another machine which has better network >connection. And It finally works, :) I guess something I've checkout before >was corrupt due to both my poor network connection and big size of the >rootfs. > >BTW, seems it is not up-to-date? I mean there is no /stage3 under the rootfs.
Hmm. I looked closer at the tree I checked out and it too had a head at commit 3e7ab1bee31082a0 from Al on Dec 31. I'm at a loss to explain what
It is the same with my local git tree.
is going wrong. I have a local tree that appears to be up to date with the repo on fedoraproject.org but the log shows 18 commits which aren't in the tree I cloned from fedoraproject.org repo earlier today. I'll try and see if I can sort it all out tomorrow.
Thanks a lot.
Baozi
Al, this may be something for you to look at. If I clone the repo using http, I get 3e7ab1bee31082a as the lastest commit. If I use ssh+git, I get everything correctly.
--Mark
The only thing I can think of right now is that 'git update-server-info' may not be getting run on updates to the repo for some reason. I've run it by hand to see if this changes the behavior -- let me know if you now get the most recent commit. If not, I'll have to poke the infrastructure folks. The short term workaround is to use ssh+git, as you indicated.
Infrastructure and I have been struggling with the underlying problem that http and git and SELinux are in a bit of a disagreement on how access should work -- and it's http that's been losing out so far.
Yay. A clone using http did get the latest bits.
Well, we now know the workaround; do the commit, then ssh into fp.o and run git update-server-info in the repo. Ugly, but it works.
I'm not sure this is fixable, but I'll poke the infrastructure folks and see what we can do.
Thanks Al & Mark!
I used my fedorapeople account to clone using ssh. But it seems http is still not work, :( Anyway, there is a way for me fetch the latest change.
The new problem is when I ran ./stage3 script it shows the following error report:
script2makefile:34: /stage3/stage3.mk/texinfo.mk: No such file or directory
Building intltool
intltool: src RPM not found make: *** [done/intltool] Error 1
I guess not all the src RPM to be built in stage3 is included in the "/SRPMS"? Is there any TODO list of stage3 src RPM including the location to get them? Thus, I may help part of building progress. Thanks.
Cheers,
Baozi
On Wed, 2013-01-30 at 16:57 +0800, Chen Baozi wrote:
Thanks Al & Mark!
I used my fedorapeople account to clone using ssh. But it seems http is still not work, :( Anyway, there is a way for me fetch the latest change.
The new problem is when I ran ./stage3 script it shows the following error report:
script2makefile:34: /stage3/stage3.mk/texinfo.mk: No such file or directory
I see this too for new packages I add and it appears harmless. The stage3.mk files get created automatically.
Building intltool
intltool: src RPM not found make: *** [done/intltool] Error 1
This was my mistake. Delete stage3/stage3.d/intltool. It shouldn't have been left in there.
--Mark
On Tue, Jan 29, 2013 at 03:24:47PM -0700, Al Stone wrote:
Well, we now know the workaround; do the commit, then ssh into fp.o and run git update-server-info in the repo. Ugly, but it works.
I'm not sure this is fixable, but I'll poke the infrastructure folks and see what we can do.
Hi Al,
I don't know if you've forgotten to do that, or I'm seeing some other problem.
$ git clone http://fedorapeople.org/groups/armv8/rootfs.git Cloning into 'rootfs'...
After over 5 minutes, nothing seems to have happened.
Cheers,
On 01/31/2013 05:15 PM, Steve McIntyre wrote:
On Tue, Jan 29, 2013 at 03:24:47PM -0700, Al Stone wrote:
Well, we now know the workaround; do the commit, then ssh into fp.o and run git update-server-info in the repo. Ugly, but it works.
I'm not sure this is fixable, but I'll poke the infrastructure folks and see what we can do.
Hi Al,
I don't know if you've forgotten to do that, or I'm seeing some other problem.
$ git clone http://fedorapeople.org/groups/armv8/rootfs.git Cloning into 'rootfs'...
After over 5 minutes, nothing seems to have happened.
Howdy, Steve.
I've filed a ticket with our IT folks and we'll see what happens. I'm seeing the same behavior and it worked up until recently.
Sorry about that; hopefully it can be fixed quickly.
On Thu, 2013-01-31 at 17:33 -0700, Al Stone wrote:
On 01/31/2013 05:15 PM, Steve McIntyre wrote:
On Tue, Jan 29, 2013 at 03:24:47PM -0700, Al Stone wrote:
Well, we now know the workaround; do the commit, then ssh into fp.o and run git update-server-info in the repo. Ugly, but it works.
I'm not sure this is fixable, but I'll poke the infrastructure folks and see what we can do.
Hi Al,
I don't know if you've forgotten to do that, or I'm seeing some other problem.
$ git clone http://fedorapeople.org/groups/armv8/rootfs.git Cloning into 'rootfs'...
After over 5 minutes, nothing seems to have happened.
Howdy, Steve.
I've filed a ticket with our IT folks and we'll see what happens. I'm seeing the same behavior and it worked up until recently.
Sorry about that; hopefully it can be fixed quickly.
I've seen it too and found that it does eventually finish. Just takes a long time. The tree has grown to ~8GiB at this point.
--Mark
On Thu, Jan 31, 2013 at 09:55:01PM -0500, Mark Salter wrote:
On Thu, 2013-01-31 at 17:33 -0700, Al Stone wrote:
On 01/31/2013 05:15 PM, Steve McIntyre wrote:
On Tue, Jan 29, 2013 at 03:24:47PM -0700, Al Stone wrote:
Well, we now know the workaround; do the commit, then ssh into fp.o and run git update-server-info in the repo. Ugly, but it works.
I'm not sure this is fixable, but I'll poke the infrastructure folks and see what we can do.
Hi Al,
I don't know if you've forgotten to do that, or I'm seeing some other problem.
$ git clone http://fedorapeople.org/groups/armv8/rootfs.git Cloning into 'rootfs'...
After over 5 minutes, nothing seems to have happened.
Howdy, Steve.
I've filed a ticket with our IT folks and we'll see what happens. I'm seeing the same behavior and it worked up until recently.
Sorry about that; hopefully it can be fixed quickly.
I've seen it too and found that it does eventually finish. Just takes a long time. The tree has grown to ~8GiB at this point.
Ah, yes. OK. I'm used to git being a *little* more verbose when it clones remote repos. Trying again and using strace, I can see it's grabbing large pack files and du is showing data turning up.
Sorry for the false report.
Cheers,
-
Al Stone -
Chen Baozi -
Jon Masters -
Mark Salter -
Steve McIntyre