Displaying 20 results from an estimated 10000 matches similar to: "can't extract diffs from llvm svn any more"
2009 Aug 10
3
[LLVMdev] svn down?
I've been getting this on svn update all day:
svn: REPORT request failed on '/svn/llvm-project/!svn/vcc/default'
svn: REPORT of '/svn/llvm-project/!svn/vcc/default': 403 Forbidden
(http://llvm.org)
Is this related to the server problems that have been going on for a while?
-Dave
2011 Apr 22
3
[LLVMdev] svn server permissions for top-level svn update
Hi,
My svn working copy mirrors the layout of the whole svn repository,
from llvm-project downwards, so I have:
~/svn/llvm-project/
~/svn/llvm-project/llvm/
~/svn/llvm-project/llvm/trunk/ # lots of stuff in here
~/svn/llvm-project/cfe/
~/svn/llvm-project/cfe/trunk/ # and lots of stuff in here
(and likewise for test-suite, llvm-gcc-4.2 and dragonegg)
This is nice because I can do "svn
2009 Aug 10
0
[LLVMdev] svn down?
On Aug 10, 2009, at 2:59 PM, David Greene wrote:
> I've been getting this on svn update all day:
>
> svn: REPORT request failed on '/svn/llvm-project/!svn/vcc/default'
> svn: REPORT of '/svn/llvm-project/!svn/vcc/default': 403 Forbidden
> (http://llvm.org)
>
> Is this related to the server problems that have been going on for a
> while?
>
svn is
2009 Aug 11
1
[LLVMdev] svn down?
On Monday 10 August 2009 17:42, Tanya Lattner wrote:
> On Aug 10, 2009, at 2:59 PM, David Greene wrote:
> > I've been getting this on svn update all day:
> >
> > svn: REPORT request failed on '/svn/llvm-project/!svn/vcc/default'
> > svn: REPORT of '/svn/llvm-project/!svn/vcc/default': 403 Forbidden
> > (http://llvm.org)
> >
> > Is
2007 Jul 25
0
[LLVMdev] svn issues
Hi David,
On Wed, 2007-07-25 at 10:38 -0500, David A. Greene wrote:
> I'm getting a lot of errors from svn like this:
>
> svn: REPORT request failed on '/svn/llvm-project/!svn/vcc/default'
> svn: REPORT of '/svn/llvm-project/!svn/vcc/default': Could not read response
> body: Secure connection truncated (https://llvm.org)
What is
2007 Jul 25
3
[LLVMdev] svn issues
On Wednesday 25 July 2007 11:06, Reid Spencer wrote:
> Hi David,
>
> On Wed, 2007-07-25 at 10:38 -0500, David A. Greene wrote:
> > I'm getting a lot of errors from svn like this:
> >
> > svn: REPORT request failed on '/svn/llvm-project/!svn/vcc/default'
> > svn: REPORT of '/svn/llvm-project/!svn/vcc/default': Could not read
> > response
2007 Jul 25
3
[LLVMdev] svn issues
I'm getting a lot of errors from svn like this:
svn: REPORT request failed on '/svn/llvm-project/!svn/vcc/default'
svn: REPORT of '/svn/llvm-project/!svn/vcc/default': Could not read response
body: Secure connection truncated (https://llvm.org)
I've now been checking out llvm-gcc for two days.
Is there a problem with the server? I don't have this issue with other
2007 Jul 25
0
[LLVMdev] svn issues
On Wednesday 25 July 2007 11:45, David Greene wrote:
> On Wednesday 25 July 2007 11:06, Reid Spencer wrote:
> > Hi David,
> >
> > On Wed, 2007-07-25 at 10:38 -0500, David A. Greene wrote:
> > > I'm getting a lot of errors from svn like this:
> > >
> > > svn: REPORT request failed on '/svn/llvm-project/!svn/vcc/default'
> > > svn:
2017 Jun 25
2
IMPORTANT: LLVM.org server move complete (SVN impact please read)
Adding +Eric Liu <ioeric at google.com> who helps with Phabricator....
On Sun, Jun 25, 2017 at 3:15 PM Davide Italiano via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> On Sun, Jun 25, 2017 at 12:32 PM, Anton Korobeynikov
> <anton at korobeynikov.info> wrote:
> > Thanks, fixed.
> >
>
> Also, FWIW, phabricator commit mails are broken. Example:
>
>
2006 Aug 16
1
Re: 400 Bad Request error from svn
It's nice to see that the OS where CentOS gets its sources from also
experiments the same error!
I have been very busy lately so I haven't had the time to deal with the
problem, probably later this week or early next week. As soon as I find
something Ill let you know. Hopefully you'll do the same if you come
across the solution first.
PS. Forwarding this message to the mailing
2011 Jul 08
0
[LLVMdev] type-system-rewrite branch near landing
>> ~/svn/llvm-project/llvm/branches$ svn up
>> svn: Server sent unexpected return value (403 Forbidden) in response
>> to REPORT request for '/svn/llvm-project/!svn/vcc/default'
>
> I think that explicitly returns Forbidden just to avoid the strain on
> the server; if you have any write access, you should have write access
> to everything.
Off topic, but
2010 Mar 30
3
[LLVMdev] Need help fixing 2.7 release blockers
On Tuesday 30 March 2010 17:45:16 David Greene wrote:
> On Tuesday 30 March 2010 16:09:03 Tanya Lattner wrote:
> > Please take a look at all release blockers:
> > http://llvm.org/bugs/show_bug.cgi?id=6586
>
> 5893 is not release-critical according to Doug.
>
> 6640 appears to be a test system problem with a patch available (one of the
> ones you're working on?)
2010 Apr 01
7
Press release: Virtual Communication Clouds :: New feature in Asterisk 1.8
FOR IMMEDIATE RELEASE
Puerto Escondido, Mexico, April 1st, 2010:
Digium launches Asterisk VCC (TM) - a new virtual communication platform
for enterprises, the public sector and the home.
===========================================================
Asterisk 1.8 will contain a stunning new technology for all Asterisk users world-
wide - virtual communication clouds or VCC (TM). With this
2014 May 12
2
[LLVMdev] phabricator says "this commit is still importing"
On Mon, May 12, 2014 at 9:34 AM, Manuel Klimek <klimek at google.com> wrote:
> It seems that we cannot execute svn commands against llvm-project any more:
> $ svn diff -r 208457:208458 'http://llvm.org/svn/llvm-project'
> svn: access to '/svn/llvm-project/!svn/vcc/default' forbidden
>
> Tanja, any idea what changed?
>
(Tanya, sorry for messing up the name,
2011 Jul 07
7
[LLVMdev] type-system-rewrite branch near landing
On Thu, Jul 7, 2011 at 12:55 AM, Jay Foad <jay.foad at gmail.com> wrote:
>> 1. Clang - Jay, do you have a patch for this?
>
> Yes. It's good enough to build most of LLVM+Clang, except for a couple
> of files. But I'm running out of time and expertise to be able to fix
> the remaining bits. Some specific concerns:
>
> 1. Many Objective-C(++) tests fail, because
2014 May 19
2
[LLVMdev] phabricator says "this commit is still importing"
On Mon, May 19, 2014 at 1:48 PM, Alex Bradbury <asb at asbradbury.org> wrote:
> On 12 May 2014 08:35, Manuel Klimek <klimek at google.com> wrote:
> > On Mon, May 12, 2014 at 9:34 AM, Manuel Klimek <klimek at google.com>
> wrote:
> >>
> >> It seems that we cannot execute svn commands against llvm-project any
> >> more:
> >> $ svn
2010 Mar 27
4
[LLVMdev] [repository] Make LLVM repository Git-clonable
Hi,
As a Linux package maintainer I tend to follow LLVM mostly towards the
end of each release cycle; nevertheless, I sometimes need to keep
track of multiple LLVM branches at the same time.
It would be great if I could use Git's SVN to clone the repository
once, and then have the full version history available locally in a
compact format. As a bonus, this will reduce the load on the server
2007 Jul 12
2
[LLVMdev] Installing clang
Really happy to hear llvm has the brand-new front-end.
But, unfortunately, I failed to install it.
When I 'svn co http://llvm.org/svn/llvm-project/cfe/trunk clang' in llvm/tools folder, I got this message..
svn: REPORT request failed on '/svn/llvm-project/!svn/vcc/default'
svn: REPORT of '/svn/llvm-project/!svn/vcc/default': 400 Bad Request (http://llvm.org)
Am I missing
2011 Jul 07
0
[LLVMdev] type-system-rewrite branch near landing
> 1. Clang - Jay, do you have a patch for this?
Yes. It's good enough to build most of LLVM+Clang, except for a couple
of files. But I'm running out of time and expertise to be able to fix
the remaining bits. Some specific concerns:
1. Many Objective-C(++) tests fail, because they use implicitly
defined structs for various ObjC runtime data structures; the
ASTConsumer
2017 Jun 25
2
IMPORTANT: LLVM.org server move complete (SVN impact please read)
Thanks, fixed.
On Sun, Jun 25, 2017 at 10:28 PM, Davide Italiano via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> On Sat, Jun 24, 2017 at 4:02 PM, Tanya Lattner via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> LLVMers,
>>
>> We have completed the move to the new server for LLVM.org. One casualty of
>> this move was that svn.llvm.org was NOT enabled