On Nov 4, 2013, at 01:35, Stefan Sperling wrote:
> This seems be a bug in the diff code with handling of moves inside copies.
> I've filed http://subversion.tigris.org/issues/show_bug.cgi?id=
You sure that’s the ticket number? It’s usually at least 6 figures.
http://www.youtube.com/watch?v=
On Mon, Nov 04, 2013 at 02:03:04AM -0600, Ryan Schmidt wrote:
>
> On Nov 4, 2013, at 01:35, Stefan Sperling wrote:
>
> > This seems be a bug in the diff code with handling of moves inside copies.
> > I've filed http://subversion.tigris.org/issues/show_bug.cgi?id=
>
> You sure that’s the tick
Hello,
When using the update command with subversion 1.8, one can set the
sticky depth with the --set-depth option.
When changing from emtpy to infinity, all the files that were not
retrieved yet are retrieved immediately.
While this is fine in most cases, I am in a situation where I'd like to
On Mon, Nov 04, 2013 at 11:16:12AM +0100, OBones wrote:
> Hello,
>
> When using the update command with subversion 1.8, one can set the sticky
> depth with the --set-depth option.
> When changing from emtpy to infinity, all the files that were not retrieved
> yet are retrieved immediately.
> While
When booting in Ubuntu 13.04 through a USB key, I was able to mount
the encrypted home folder in read only, and then dump, load, and
verify outside of the encrypted home in 13.04 (but still on btrfs).
Moreover, when I returned to 13.10, I was able to "svn verify" the
repository outside of the encry
Hello,
0. I've updated to Ubuntu 13.10 recently. I'm using btrfs since about
August.
1. Very recently, my repository (~90gb) started giving an error when I
update my checked out copy:
svn: E160004: Corrupt node-revision '3-2320.0-1861.r2320/7091583216'
svn: E160004: Found malformed header
'g?\229
Good evening!
I don't think it's btrfs.
-- I'm using btrfs since August, but the problem came up only
recently, after installing Ubuntu 13.10.
-- I loaded the repository in an ext4 partition from a dump made
before using btrfs, with the same result.
-- I booted Ubuntu 13.04 through a USB key, and
Sorry I just made a mistake. When I copied the repository inside the
ubuntu home encryption with Ubuntu 13.10, I started having the same
problems as before...
On Sun, Nov 3, 2013 at 12:27 PM, Vincent Quenneville-Belair
wrote:
> When booting in Ubuntu 13.04 through a USB key, I was able to mount
On Sun, Nov 3, 2013 at 3:35 PM, Branko Čibej wrote:
> On 03.11.2013 20:29, Nico Kadel-Garcia wrote:
>
> I'm going to give you my Red Hat/Fedora classic advice.
>
> Work From The RPM
>
>
> That's not really helpful. People have legitimate reasons to build from
> source, and you definitely won
Brane,
Thanks for your response.
I agree with your statements. Did I miss dependencies on the Subversion web
site?
I'm using RPMs from Fedora for both architectures (i686 and x86_64) so the
complaint is about their distribution I guess. I'm pursuing this avenue with
the "user-help" mailing li
On 04.11.2013 21:09, George R Goffe wrote:
> Brane,
>
> Thanks for your response.
>
> I agree with your statements. Did I miss dependencies on the Subversion web
> site?
If you had the necessary dependencies for Fedora 16, you shouldn't need
any new ones for Fedora 19.
One thing that comes to mi
For the record, the problem was the following. Fixed.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1243636
On Sun, Nov 3, 2013 at 12:30 PM, Vincent Quenneville-Belair
wrote:
> Sorry I just made a mistake. When I copied the repository inside the
> ubuntu home encryption with Ubuntu 13.10,
12 matches
Mail list logo
