[chromium-dev] gcl commit throwing SVN server error
When I try to commit my change, I am getting following error there - any ideas what might be causing this? >gcl commit my_change Presubmit checks took 1.7s to calculate. Loaded authentication cookies from C:\Users\zelidrag/.codereview_upload_cookies svn: Commit failed (details follow): svn: Server sent unexpected return value (500 Internal Server Error) in response to MKACTIVITY request for '/svn/!svn/act/aa57d512-f59f-9147-897e-0c6aef5f25fc' -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
Re: [chromium-dev] gcl commit throwing SVN server error
How do I know if the repo is read-only? This is how my .gclient looks like
solutions = [
{ "name": "src",
"url" : "http://src.chromium.org/svn/trunk/src";,
"custom_deps" : {
# To use the trunk of a component instead of what's in DEPS:
#"component": "https://svnserver/component/trunk/";,
# To exclude a component from your working copy:
#"data/really_large_component": None,
},
"safesync_url": "http://chromium-status.appspot.com/lkgr";
},
]
On Thu, Dec 3, 2009 at 3:48 PM, Dan Kegel wrote:
> Sounds like you're trying to commit to the read-only repo?
>
> On Thu, Dec 3, 2009 at 3:31 PM, Zelidrag Hornung
> wrote:
> > When I try to commit my change, I am getting following error there - any
> > ideas what might be causing this?
> >>gcl commit my_change
> > Presubmit checks took 1.7s to calculate.
> > Loaded authentication cookies from
> > C:\Users\zelidrag/.codereview_upload_cookies
> > svn: Commit failed (details follow):
> > svn: Server sent unexpected return value (500 Internal Server Error) in
> > response to MKACTIVITY request for
> > '/svn/!svn/act/aa57d512-f59f-9147-897e-0c6aef5f25fc'
> >
> > --
> > Chromium Developers mailing list: chromium-dev@googlegroups.com
> > View archives, change email options, or unsubscribe:
> > http://groups.google.com/group/chromium-dev
>
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
Re: [chromium-dev] gcl commit throwing SVN server error
The core of the problem is that my account somehow had two sets of
credentials for SVN access. It's been fixed now.
Thanks!
On Fri, Dec 4, 2009 at 11:54 AM, Nicolas Sylvain wrote:
>
>
> On Thu, Dec 3, 2009 at 4:03 PM, Dan Kegel wrote:
>
>> If you're a committer, you should have recieved instructions on how
>> to set up your client (it will have an svn rather than an http url)
>> when you got your commit password.
>>
>
> Or for new people to the team, your mentor should guide you through the
> process.
>
> Nicolas
>
>
>>
>> On Thu, Dec 3, 2009 at 3:51 PM, Zelidrag Hornung
>> wrote:
>> > How do I know if the repo is read-only? This is how my .gclient looks
>> like
>> > solutions = [
>> > { "name": "src",
>> > "url" : "http://src.chromium.org/svn/trunk/src";,
>> > "custom_deps" : {
>> > # To use the trunk of a component instead of what's in DEPS:
>> > #"component": "https://svnserver/component/trunk/";,
>> > # To exclude a component from your working copy:
>> > #"data/really_large_component": None,
>> > },
>> > "safesync_url": "http://chromium-status.appspot.com/lkgr";
>> > },
>> > ]
>> >
>> >
>> > On Thu, Dec 3, 2009 at 3:48 PM, Dan Kegel wrote:
>> >>
>> >> Sounds like you're trying to commit to the read-only repo?
>> >>
>> >> On Thu, Dec 3, 2009 at 3:31 PM, Zelidrag Hornung <
>> zelid...@chromium.org>
>> >> wrote:
>> >> > When I try to commit my change, I am getting following error there -
>> any
>> >> > ideas what might be causing this?
>> >> >>gcl commit my_change
>> >> > Presubmit checks took 1.7s to calculate.
>> >> > Loaded authentication cookies from
>> >> > C:\Users\zelidrag/.codereview_upload_cookies
>> >> > svn: Commit failed (details follow):
>> >> > svn: Server sent unexpected return value (500 Internal Server Error)
>> in
>> >> > response to MKACTIVITY request for
>> >> > '/svn/!svn/act/aa57d512-f59f-9147-897e-0c6aef5f25fc'
>> >> >
>> >> > --
>> >> > Chromium Developers mailing list: chromium-dev@googlegroups.com
>> >> > View archives, change email options, or unsubscribe:
>> >> > http://groups.google.com/group/chromium-dev
>> >
>> >
>>
>> --
>> Chromium Developers mailing list: chromium-dev@googlegroups.com
>> View archives, change email options, or unsubscribe:
>>http://groups.google.com/group/chromium-dev
>>
>
>
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
[chromium-dev] unable to check out with git
Does anyone know why following git clone command fails on me today? > git clone git://git.chromium.org/chromium.git src Initialized empty Git repository in /usr/local/google/home/zelidrag/chrome/src/.git/ git.chromium.org[0: 74.125.54.202]: errno=Connection timed out fatal: unable to connect a socket (Connection timed out) -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
[chromium-dev] Portage build errors
Is anyone else seeing these errors while running new_build_pkgs.sh? !!! Please attach the following file when seeking support: !!! /usr/i686-pc-linux-gnu/tmp/portage/x11-drivers/xf86-video-intel-2.8.1-r1/work/xf86-video-intel-2.8.1/config.log * * ERROR: x11-drivers/xf86-video-intel-2.8.1-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3174: Called x-modular_src_compile * environment, line 3958: Called x-modular_src_configure * environment, line 3967: Called econf '--prefix=/usr' '--datadir=/usr/share' '--enable-dri' * ebuild.sh, line 534: Called die * The specific snippet of code: * die "econf failed" * The die message: * econf failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/usr/i686-pc-linux-gnu/tmp/portage/x11-drivers/xf86-video-intel-2.8.1-r1/temp/build.log'. * The ebuild environment file is located at '/usr/i686-pc-linux-gnu/tmp/portage/x11-drivers/xf86-video-intel-2.8.1-r1/temp/environment'. * This ebuild is from an overlay named 'chromiumos': '/home/zelidrag/trunk/src/third_party/chromiumos-overlay/' * * Messages for package x11-drivers/xf86-video-intel-2.8.1-r1 merged to /usr/i686-pc-linux-gnu/: * * ERROR: x11-drivers/xf86-video-intel-2.8.1-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3174: Called x-modular_src_compile * environment, line 3958: Called x-modular_src_configure * environment, line 3967: Called econf '--prefix=/usr' '--datadir=/usr/share' '--enable-dri' * ebuild.sh, line 534: Called die * The specific snippet of code: * die "econf failed" * The die message: * econf failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/usr/i686-pc-linux-gnu/tmp/portage/x11-drivers/xf86-video-intel-2.8.1-r1/temp/build.log'. * The ebuild environment file is located at '/usr/i686-pc-linux-gnu/tmp/portage/x11-drivers/xf86-video-intel-2.8.1-r1/temp/environment'. * This ebuild is from an overlay named 'chromiumos': '/home/zelidrag/trunk/src/third_party/chromiumos-overlay/' -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
[chromium-dev] LONG_BIT not #defined correctly for 32bit target on 64bit host machine
While compiling come changes in Chrome project for ChromeOS - as 32bit target on a 64bit host machine - I am running into a compile error due to a wrong value being set for LONG_BIT define. For some reasons, regardless of my 32bit target build architecture, this value is set as if I am compiling for 64bit target what causes a preprocessor #error. Does anyone know where and how LONG_BIT gets defined within chromium builds? Simple grepping didn't it up anywhere for me. -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
[chromium-dev] Re: LONG_BIT not #defined correctly for 32bit target on 64bit host machine
I think I found what is causing this - there is a problem how python is configured for chromeos chroot, working on a fix... On Wed, Feb 24, 2010 at 11:41 AM, Zelidrag Hornung wrote: > While compiling come changes in Chrome project for ChromeOS - as 32bit > target on a 64bit host machine - I am running into a compile error due to a > wrong value being set for LONG_BIT define. For some reasons, regardless of > my 32bit target build architecture, this value is set as if I am compiling > for 64bit target what causes a preprocessor #error. > > Does anyone know where and how LONG_BIT gets defined within chromium > builds? Simple grepping didn't it up anywhere for me. > > -- Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev
