similar to: llvm.org svn issue?

On 20 Aug 2013, at 10:35, Benjamin Kramer <benny.kra at gmail.com> wrote: > Seems to be a known bug in SVN 1.8.0, can you try upgrading to 1.8.1 or downgrading to 1.7? Downgrading to 1.7.x means that I can't access my local repo, since there is no svn downgrade. Upgrading to 1.8.1 gives: svn: E175002: Unable to connect to a repository at URL 'https://theraven at

Hi I'm trying to change a commit message that became malformed when pushing to trunk svn propedit svn:log --revprop -r 243434 > svn: E175002: DAV request failed; it's possible that the repository's > pre-revprop-change hook either failed or is non-existent > svn: E175002: Repository has not been enabled to accept revision > propchanges; > ask the administrator to

On Tue, Jul 28, 2015 at 10:42 AM, Martell Malone <martellmalone at gmail.com> wrote: > Hi > > I'm trying to change a commit message that became malformed when pushing > to trunk > > svn propedit svn:log --revprop -r 243434 >> svn: E175002: DAV request failed; it's possible that the repository's >> pre-revprop-change hook either failed or is

> Makes sense to me. If you built with and without LDFLAGS enabled > should probably just commit it - or do you need someone to commit for > you? I can commit it. I was just not sure if this was an intentional difference. I am running a bootstrap without a LDFLAGS. Will commit if it pass. > -eric > _______________________________________________ > LLVM Developers mailing list

Hi, When I try to use LLVM svn (with svn 1.8.0), I'm currently seeing this: svn: E175004: The PROPFIND response did not include the requested properties Does anyone else have this problem? David

On 20.08.2013, at 11:16, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: > Hi, > > When I try to use LLVM svn (with svn 1.8.0), I'm currently seeing this: > > svn: E175004: The PROPFIND response did not include the requested properties > > Does anyone else have this problem? Seems to be a known bug in SVN 1.8.0, can you try upgrading to 1.8.1 or

Hi, I noticed that recently our bots have been failing more than usual on SVN connection problems: Updating '.': svn: E175002: Unable to connect to a repository at URL 'http://llvm.org/svn/llvm-project/lnt/trunk' svn: E175002: Server sent unexpected return value (502 Bad Gateway) in response to OPTIONS request for 'http://llvm.org/svn/llvm-project/lnt/trunk' Is there

I'm just getting started changing the emitted code. Suppose I want to just add one new instruction to the function prologue at the top. Where would I do this? Does it depend on the backend? I'm targeting RISCV64. Gry

Hi, Is the svn archive supposed to be http and https, or just https now? http access was working a few days ago (last week?) but now it results in: svn: E175002: Unable to connect to a repository at URL ' http://svn.xiph.org/trunk/Tremor' svn: E175002: OPTIONS of 'http://svn.xiph.org/trunk/Tremor': Could not read status line: connection was closed by server (http://svn.xiph.org)

> I can commit it. I was just not sure if this was an intentional > difference. I am running a bootstrap without a LDFLAGS. Will commit if > it pass. The bootstrap was OK, but I am getting the following error trying to commit: svn: Commit failed (details follow): svn: MKACTIVITY of '/svn/llvm-project/!svn/act/05b8ac29-8fd9-4f8e-9c3c-d39e89ade19f': 400 Bad Request

Thanks for all the feedback guys So rather than speculating about what could and might not break. I am going to test all these different scenarios by creating my own svn server, svn mirror and git mirror etc I'll get back to you all with details on what breaks and what doesn't soon with changing the commit msgs Many Thanks Martell On Wed, Jul 29, 2015 at 7:01 AM, Sean Silva

Hi, there is no firewall, all DCs are in the same subnet. here ist the output of a test, you can see, the CNAME guid entries in the _msdcs can be resolved on any DC: (DC1 and DC2 are the first and second DCs, SAMBA3 was added at last. ldbsearch -H /srv/samba/private/sam.ldb '(invocationId=*)' --cross-ncs objectguid # record 1 dn: CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-

Heinz, I had exactly the same problem, and used ldbedit to apply the fix. Thanks for digging into this! Now I'm interested in the root cause as well ... Uli Am 16.01.2018 um 16:48 schrieb Heinz Hölzl via samba: > no, it seems to work!!! > > > i did a ldapmodify on DC2: > > ldapmodify -x -h dc2 -D cn=administrator,cn=users,dc=test,dc=net -W -f > serverReference.ldif

On Jun 19, 2008, at 4:04 PM, Rafael Espindola wrote: > The bootstrap was OK, but I am getting the following error trying to > commit: > > svn: Commit failed (details follow): > svn: MKACTIVITY of > '/svn/llvm-project/!svn/act/05b8ac29-8fd9-4f8e-9c3c-d39e89ade19f': 400 > Bad Request (http://llvm.org) > > Any idea what could be wrong? Nope, not really... but

Hi, i have the same problem on samba 4.7.3 and 4.7.4. I start with 2 DCs and the sync works fine. After the join of a third DC mostly i get the WERR_DS_DRA_ACCESS_DENIED. I tested it for 10 times. in my case i have: DC1 (with any FSMO Roles) DC2 new join as DC: DC3 After the join, the sync from DC2 to DC3 fails. samba-tool drs replicate dc2 dc1 dc=gvcc,dc=net : OK samba-tool drs replicate

no, it seems to work!!! i did a ldapmodify on DC2: ldapmodify -x -h dc2 -D cn=administrator,cn=users,dc=test,dc=net -W -f serverReference.ldif serverReference.ldif: dn: CN=SAMBA3,CN=Servers,CN=Default-First- SiteName,CN=Sites,CN=Configuration,DC=test,DC=net changetype: modify add: serverReference serverReference: CN=SAMBA3,OU=Domain Controllers,DC=test,DC=net - now the question: Why the

on DC2 in the log i found: ./source4/dsdb/common/util.c:4807: Failed to find account dn (serverReference) for CN=SAMBA3,CN=Servers,CN=Default-First-Site- Name,CN=Sites,CN=Configuration,DC=test,DC=net, parent of DSA with objectGUID c01a335e-1794-4997-9c7e-553be77fba04, sid S-1-5-21- 1608159440-4144762864-1017073214-18962 ../source4/rpc_server/drsuapi/updaterefs.c:374: Refusing DsReplicaUpdateRefs

Hi Heinz and Johannes, > I had exactly the same problem, and used ldbedit to apply the fix. > Thanks for digging into this! > > Now I'm interested in the root cause as well ... I just had a client calling with a replication issue due to the exact same error. The domain was initially build on 4.7.1, upgraded to 4.7.3, and it was also missing the serverReference attribute on one

Same error here... root at samba01:~# samba-tool ldapcmp ldap://samba01 ldap://samba02 -Uadministrator --filter=CN,DC,member CONFIGURATION Password for [LAURENZ\administrator]: * Comparing [CONFIGURATION] context... * Objects to be compared: 1631 Comparing: 'CN=SAMBA03,CN=Servers,CN=Harz,CN=Sites,CN=Configuration,DC=local,DC=laurenz,DC=ws' [ldap://samba01]