On Fri, Aug 7, 2020 at 2:22 PM Bo Berglund wrote:
>
> Thanks!
> I did this:
> sudo apt install gnome-keyring
>
> and now when I used svn up again it did show a password dialog where I
> could select to save the password too.
> And no more error messages!
> Thanks again!
Glad to help! Thanks for
On Fri, 7 Aug 2020 10:34:44 -0400, Nathan Hartman
wrote:
>On Fri, Aug 7, 2020 at 8:58 AM Bo Berglund wrote:
>
>> ** Message: 14:45:45.612: Remote error from secret service:
>> org.freedesktop.DBus.Error.ServiceUnknown: The name
>> org.freedesktop.secrets was not provided by any .service files
>
On Fri, Aug 7, 2020 at 8:58 AM Bo Berglund wrote:
> ** Message: 14:45:45.612: Remote error from secret service:
> org.freedesktop.DBus.Error.ServiceUnknown: The name
> org.freedesktop.secrets was not provided by any .service files
I think it is trying to cache/lookup your password in gnome-keyr
I am programming on a Raspberry Pi3B with the latest Pi-OS Linux.
I have installed subversion via apt two days ago and got version
1.10.4 (r1850624).
When I want to update a project on this machine I get the following
output, which makes no sense to me (I have obfuscated the svn server
name)
Hi,
I've recently been unable to update one of the folders in my SVN and I've found
a couple people having a similar issue but no resolution has been found. Does
anyone know what is going on? I recently made a change to the SVN by making a
symlink have a special status so I'm thinking that this
The update problem has been solved.
The solution was to upgrade the server to a recent version.
Now, it works like a charm.
-Wabe.
> From: philip.mar...@wandisco.com
> To: wabekoelm...@hotmail.com
> CC: users@subversion.apache.org
> Subject: Re: Error when updating
> Date: Thu
Thanks, Philip.
Looking forward to it. Now it takes me quite some extra time to work with SVN.
-Wabe
> From: philip.mar...@wandisco.com
> To: wabekoelm...@hotmail.com
> CC: users@subversion.apache.org
> Subject: Re: Error when updating
> Date: Thu, 3 Nov 2011 16:09:58 +
>
Wabe W writes:
> So, we just have to update the server and see if the problem is solved?
It's issue 4048, it may get fixed in a 1.7.x release:
http://subversion.tigris.org/issues/show_bug.cgi?id=4048
--
Philip
> >> I assume you are using some sort of server. Which version of Subversion
> >> is the server running?
>
> > It is 1.0.8 (2004)
>
> That's old (very old) and unsupported.
I will tell my professor :-)
> The client should still work but
> I haven't built or used 1.0.x for years.
So, we j
Wabe W writes:
>> I assume you are using some sort of server. Which version of Subversion
>> is the server running?
> It is 1.0.8 (2004)
That's old (very old) and unsupported. The client should still work but
I haven't built or used 1.0.x for years.
>>Is it a googlecode server? Are you us
I got word from the person that runs the server.
He replied the following:
> Which Subversion protocol are you using (http:, https:, svn:, file:)?
http://
> I assume you are using some sort of server.
Which version of
> Subversion is the server running?
subversion 1.0.8-2.2 (r11084) on a
> The error you report is:
>
>
> 'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\libsvn_wc\wc_db.c'
> line 11039: assertion failed (base_status == svn_wc__db_status_incomplete)
>
> That happens inside the function end_directory_update, which is called
> from close_edi
Philip Martin writes:
> I'm surprised it happens when the update makes changes to the working
> copy, I can't see how close_edit is called in that case.
Oops! I meant to say I can't see how end_directory_update is called.
--
Philip
Wabe W writes:
>> This is reproducible? You checkout some revision R1 and update to R2
>> and see the error?
>>
>> Can you describe the changes between R1 and R2?
>
> I just did a checkout of the latest revision of the repository. So, if
> I click update the chances are large that there is no n
> Date: Thu, 27 Oct 2011 12:56:11 +0200
> From: s...@elego.de
> To: wabekoelm...@hotmail.com
> CC: users@subversion.apache.org
> Subject: Re: Error when updating
>
> On Thu, Oct 27, 2011 at 10:20:36AM +, Wabe W wrote:
> > From: Philip Martin
> > >Can yo
ing problem. Also, because I tried
5 different repositories with all the same problem.
--Wabe
> From: philip.mar...@wandisco.com
> To: wabekoelm...@hotmail.com
> CC: users@subversion.apache.org
> Subject: Re: Error when updating
> Date: Thu, 27 Oct 2011 12:14:55 +0100
>
> Wabe
Wabe W writes:
> I also tried a checkout of a(n existing) repository to a different
> location. I get the same error message when I try to update.
This is reproducible? You checkout some revision R1 and update to R2
and see the error?
Can you describe the changes between R1 and R2?
Is there a
On Thu, Oct 27, 2011 at 10:20:36AM +, Wabe W wrote:
> From: Philip Martin
> >Can you reproduce the problem with a local test repository?
>
> I tried to reproduce the problem by making a local test repository.
> However, there's no problem anymore. It works perfectly fine.
Are path-based access
From: Philip Martin
Date: Tue, 25 Oct 2011 18:00:07 +0100
>People are replying to utwente.nl address in your Reply-To header.
Thanks for pointing this out. I don't use this hotmail address a lot and
totally forgot the address in the reply-to (which stopped working about 5 years
ago...)
Wabe W writes:
> First, please bear with my ignorance here. I only just figured out
> that I don't get a reply to my e-mail in my inbox. I'm apparently
> supposed to visit this page...
People are replying to utwente.nl address in your Reply-To header.
> Anyway, thank you for replying. To return
First, please bear with my ignorance here. I only just figured out that I don't
get a reply to my e-mail in my inbox. I'm apparently supposed to visit this
page...
Anyway, thank you for replying. To return to the problem:
>Does the problem occur with an upgraded working copy or with
>a new ch
On Tue, Oct 25, 2011 at 11:29:59AM +, Wabe W wrote:
>
> Hello,
>
> After the update to SVN 1.7.1 the error that I reported in the e-mail below
> persists.
> So, I still have the same problem and am hoping there is fix for it.
>
Does the problem occur with an upgraded working copy or with
a
ay, October 25, 2011 1:30 PM
To: users@subversion.apache.org
Subject: FW: Error when updating
Hello,
After the update to SVN 1.7.1 the error that I reported in the e-mail below
persists.
So, I still have the same problem and am hoping there is fix for it.
Awaiting your reply,
Wabe Koelma
Hello,
After the update to SVN 1.7.1 the error that I reported in the e-mail below
persists.
So, I still have the same problem and am hoping there is fix for it.
Awaiting your reply,
Wabe Koelmans.
From: wabekoelm...@hotmail.com
To: users@subversion.apache.org
Subject: Error when updating
Hello,
When I click SVN update I get an error message (see below).
When I first commit something (doens't matter what), I can update only the same
folder after the commit. For all other folders the update still doesn't work.
Once I get the error message it will pop up for all SVN folders. Until
25 matches
Mail list logo
