On Oct 28, 2011, at 19:37, Bruce Vining wrote:
> I have been using Subversion flawlessly (and happily) now for the past 6
> months but performed the latest update via the Web Interface (Collabnet
> Subversion Edge) and now I have hell to pay.
>
> For the past 6 months I have been successfully
For various reasons, I've been working on RPM packaging of 1.7.0 and
now 1.7.1. I'd like to get the old "packages/rpm" structure replaced
with it, and I'm trying to get it into RPMforge. It's built from the
Fedora packaging of subversion-1.6.17, and most of the patches are no
longer needed (because
On Wed, Oct 26, 2011 at 7:23 AM, Neil Bird wrote:
>
> Whilst suffering a subversion server outage, it's made me wonder: we
> currently produce nightly backups of our repos via 'hotcopy' from the
> server's local drive to a network store.
>
> If the server were to die, would I be able to take th
Erwane Breton wrote on Fri, Oct 28, 2011 at 12:31:52 +0200:
> The install of my virtualbox, for Daniel Shahaf, maybe solved the
> problem, in local.
> If it's work with minimal configuration, something goes wrong in my
> apache config.
>
If you find what the problem was, please post back to the t
On Oct 28, 2011, at 5:52 PM, Pietro Moras wrote:
> > more specific questions
>
> My pleasure, dear Geoff,
>Here you have some very Specific Questions.
>
> SQ1] How to get what I presume is a nice Subversion prompt:
>
> $
>
> on one of my standard Windows machines, so to test the wonderf
Dear Pietro,
I think you should start your learning Subversion from learning what a
"command line" is. Subversion manual is no substitute for knowing the OS.
Or alternatively, have someone install a repostory for you and go with a GUI
client, such as TortoiseSVN.
Regards,
Alexey.
On Friday, O
On Fri, Oct 28, 2011 at 3:52 PM, Pietro Moras wrote:
> > more specific questions
>
> My pleasure, dear Geoff,
>Here you have some very Specific Questions.
>
> SQ1] How to get what I presume is a nice Subversion prompt:
>
> $
>
>
There is no prompt, other than terminal. Read the redbook plea
>
more specific questions
My pleasure, dear
Geoff, Here you have some
very Specific Questions.
SQ1] How to get what I
presume is a nice Subversion prompt:
$
on one of my
standard Windows machines, so to test the wonderful Subversion
commands so eloquently described by the mention
On Fri, Oct 28, 2011 at 11:00 AM, Pietro Moras wrote:
> Dear Subversion cognoscenti,
>
> Seriously intentioned to explore what Subversion is all about, armed
> with good will and a good reference book (“Version Control with
> Subversion”, by Ben Collins-Sussman, Brian W. Fitzpatrick, C. Mich
Dear Subversion
cognoscenti,
Seriously
intentioned to explore what Subversion is all about, armed with good
will and a good reference book (“Version Control with Subversion”,
by Ben Collins-Sussman, Brian W. Fitzpatrick, C.
Michael Pilato),
I got immediately lost & stuck at the very fi
On 10/28/2011 2:41 AM, Stefan Sperling wrote:
On Thu, Oct 27, 2011 at 04:19:54PM +0200, Erwane Breton wrote:
The error is always the same
Commit
Commit failed (details follow):
'/svn/site/*!svn/me*' path not found
My repository is https://xyz.coda-cola.net/svn/site/trunk
I've tried svnadmin
Hello,
a new open source tool for reorganizing Subversion repositories
was released. It is optimized to extract parts of a large
repository to form a new smaller one.
It is similar in purpose to svndumpfilter (standard SVN tool)
and Simon Tatham's svndumpfilter2 (*). However it is has less
limit
On Fri, Oct 28, 2011 at 01:20:52PM +0100, Stephen Flowers wrote:
> ---
> Subversion Exception!
> ---
> Subversion encountered a serious problem.
> Please take the time to report this on the Subversion mailing list
> with as much information as possibl
Dear list,
I'm experiencing some weird behaviour of SVN 1.7. The following
sequence of commands fails to respect --depth=empty:
svn co --depth=empty http://foundry.supelec.fr/svn/metapost
svn up --depth=empty metapost/tags
(you can use 'anonymous' as a username if it asks) The first comma
---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much information as possible about what
you were trying to do.
But please first search the mailing list
On Fri, Oct 28, 2011 at 2:00 PM, Andreas Krey wrote:
> That only looks like that because of the way merging is described in the
> book.
Aaah! RTFM, is it?
> In essence, svn sees only two different (and conflicting) changes to
> a block of lines, and leaves it to you to deal with that. (Likewise
On Fri, Oct 28, 2011 at 2:19 PM, Stefan Sperling wrote:
> Does this explanation make sense?
Yes, very much, thank you for taking your time to look into this for
me, I'm sorry to have inconvenienced you, but hopefully someone with
the same problem will find the thread and be enlightened.
--
Flem
On Fri, Oct 28, 2011 at 01:02:05PM +0200, Flemming Frandsen wrote:
> On Fri, Oct 28, 2011 at 12:58 PM, Andreas Krey wrote:
> > You didn't get a clean merge; you got a conflict. When you get a conflict,
> > it is your job to look at what you merged and at the proposed result,
> > and resolve it you
On Fri, 28 Oct 2011 13:02:05 +, Flemming Frandsen wrote:
...
> The problem is that there are many more changes in the conflicted
> block than the diff suggested, iow: svn merge tried to add more lines
> than svn diff said it would.
That only looks like that because of the way merging is descri
Mojca Miklavec writes:
> I'm experiencing some weird behaviour with SVN 1.7. The following
> sequence of commands fails to respect --depth=empty:
> svn co --depth=empty http://foundry.supelec.fr/svn/metapost
> svn up --depth=empty metapost/tags
>
> (you can use 'anonymous' as a username) Th
Dear list,
I'm experiencing some weird behaviour with SVN 1.7. The following
sequence of commands fails to respect --depth=empty:
svn co --depth=empty http://foundry.supelec.fr/svn/metapost
svn up --depth=empty metapost/tags
(you can use 'anonymous' as a username) The first command runs fin
On Fri, Oct 28, 2011 at 12:58 PM, Andreas Krey wrote:
> You didn't get a clean merge; you got a conflict. When you get a conflict,
> it is your job to look at what you merged and at the proposed result,
> and resolve it yourself.
Yes, I have seen conflicts before, that's not what the problem is,
On Fri, 28 Oct 2011 12:49:35 +, Flemming Frandsen wrote:
...
> This is not the only time I've seen the problem manifest, but the
> circumstances where similar, in the other case another developer was
> trying to merge a change from version-1 to version-2, he too got extra
> changes in his merge
On Fri, Oct 28, 2011 at 12:31 PM, Johan Corveleyn wrote:
> Here is something I don't understand. You just did a new checkout to
> someotherpath. The HEAD of your repository is at least 648291. How
> come that someotherpath/stepws.xsd is at revision 610503? That doesn't
> make sense.
I'm sorry, I
Le 28/10/2011 10:51, Daniel Shahaf a écrit :
Erwane, can you provide a minimal server configuration that reproduces
the bug? The svn devs used 1.7 clients against a 1.6.17 svn.apache.org
for a long time without seeing any such errors, so I suspect the issue
is due to your configuration trigger
On Fri, Oct 28, 2011 at 11:55 AM, Flemming Frandsen wrote:
> We're having a major problem with subversion, it seems that for some
> changesets svn merge will do a different change than svn diff would
> suggest.
>
> Here's an example of that the problem looks like:
>
>
> svn diff -c 648291 svn+ssh:
Am 28.10.2011 11:55, schrieb Flemming Frandsen:
We're having a major problem with subversion, it seems that for some
changesets svn merge will do a different change than svn diff would
suggest.
It took me a while of scrolling up and down to find the difference, but
IIUC the problem is A) that
On Fri, Oct 28, 2011 at 11:55:06AM +0200, Flemming Frandsen wrote:
> We're having a major problem with subversion, it seems that for some
> changesets svn merge will do a different change than svn diff would
> suggest.
This does indeed look like a bug in merge.
Is it possible for you to provide th
We're having a major problem with subversion, it seems that for some
changesets svn merge will do a different change than svn diff would
suggest.
Here's an example of that the problem looks like:
svn diff -c 648291 svn+ssh://myserver/somepath/stepws.xsd
Index: stepws.xsd
===
On Thu, Oct 27, 2011 at 04:19:54PM +0200, Erwane Breton wrote:
> The error is always the same
>
> >Commit
> >Commit failed (details follow):
> >'/svn/site/*!svn/me*' path not found
> >
> My repository is https://xyz.coda-cola.net/svn/site/trunk
>
> I've tried svnadmin upgrade, exactly the same.
>
Attila Nagy writes:
> ZFS.
> It it worth to make benchmarks with this WC with 1.6 and 1.7? I so, I
> can try to find the time for it.
There are some reports that a mismatch between SQLite page size and ZFS
block size can cause performance problems and that better performance is
obtained when the
Erwane Breton writes:
> On my client (windows 7 x64 tortoise SVN), i CAN commit with Tortoise
> 1.6.15 on my laptop but i CAN'T commit (or rename or delete) on my
> other computer with tortoise 1.7.1.22161
>
> The error is always the same
>
>> Commit
>> Commit failed (details follow):
>> '/svn/si
Daniel Shahaf wrote on Thu, Oct 27, 2011 at 22:12:46 +0200:
> Does it work with a 1.6 client?
>
dcz, thanks.
Erwane, can you provide a minimal server configuration that reproduces
the bug? The svn devs used 1.7 clients against a 1.6.17 svn.apache.org
for a long time without seeing any such erro
Ulrich Eckhardt wrote on Fri, Oct 28, 2011 at 08:42:30 +0200:
> Am 27.10.2011 23:56, schrieb Big George:
> >What I try to do is to move my Repository and folder D:\Scripts_DB
> >(with all its changes ) from PC1 to PC2.
>
> There are two things involved for moving the repo:
> 1. Moving the repo its
Le jeudi 27 octobre 2011 22:12:46, Daniel Shahaf a écrit :
Does it work with a 1.6 client?
Erwane Breton wrote on Thu, Oct 27, 2011 at 16:19:54 +0200:
i CAN commit with
Tortoise 1.6.15
I guess he can.
35 matches
Mail list logo
