Re: svn dump failure with bad revison

[Thorsten Schöning]

Guten Tag Stefan Lock,
am Freitag, 21. Oktober 2011 um 18:04 schrieben Sie:

> * Dumped revision 8233.
> svnadmin: File not found: revision 8234, path

Does the revision file 8234 exist and is not 0 kb in size or stuff
like that?

Mit freundlichen Grüßen,

Thorsten Schöning

-- 
Thorsten Schöning   E-Mail:thorsten.schoen...@am-soft.de
AM-SoFT IT-Systeme  http://www.AM-SoFT.de/

Telefon.030-2 1001-310
Fax...05151-  9468- 88
Mobil..0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hanover HRB 207 694 - Geschäftsführer: Andreas Muchow

Re: Apache Subversion 1.7.1 Released

[Nico Kadel-Garcia]

On Sat, Oct 22, 2011 at 10:12 PM, Hyrum Wright  wrote:
> I'm happy to announce the release of Apache Subversion 1.7.1.  This
> release addresses a number of user-reported issues in the 1.7.0
> release.

Great. I notice a couple of points.

* The "packages/rpm/rhel-*" bundles need a thorough rewrite and should
not be used as is. I'm in the midst of writing some such tools for
RPMforge, and will be happy to submit them. A lot of the patches
previously needed have been been already incorporated, which helps.
The new structure, like others from RPMforge, auto-configs options for
different OS releases. David Sommerset's old work there was good, but
it had some traps.

* The compatiblity of Subverson 1.7 with older style working copies
without auto-updating them is much appreciated. I had one hell of a
time geting buyin to get people up to 1.6 with that auto-update
feature.making the upgrade irreversible, and people using shared home
directories across older and newer systems with different Subversion
clients.

* Is serf *preferred* over neon now? serf isn't in any of the
repositories for RHEL 5. It is in Fedora, and can probably be safely
backported. But I'm concerned for it being unstable or unsupported in
the long term, especially in older operating systems. I've got a
chance to add it or not for RPMforge as it stands.

Re: info subversion

[Nico Kadel-Garcia]

On Mon, Oct 10, 2011 at 12:28 PM, filomena ciola
 wrote:
> Hello,
> Please I need your help for a little question:
> I need to erase all the old revisions, if it' s possible, how can I do for
> make this automatically? if this isn't possible, can I put a pw so only
> authorized personell can see old revision?
> Thank you for your interesting
> With best regards
>
>
> Mimma Ciola

If they can see the file, in Subversion, they can see all the old
relevant revisions from that repository. They may not be able to see
*other* files if you have access to them blocked in Apache or svnserve
managed access.

It's also vaguely feasible that if you used svn+ssh based access, the
relevant "svn" user could be made not a member of the appropriate
groups to see that old revision at all.  But this would get *nasty*,
very quickly, It would be like replacing the command "rm" with
something that moves files aside. It would work until it broke,
*badly*.

Re: info subversion

[Ludovic Lambert]

Hi Filomena,

Restricting access on a revision basis is not possible.
You can remove old versions or part of your repo by using the dumpfilter
command.
1. Dump your current repo
2. Use dumpfilter to filter unwanted elements
3. Reload filtered dump into a new repo.
Doc: http://svnbook.red-bean.com/en/1.7/svn.ref.svndumpfilter.html
Exemple 1 - Removing old revisions:
http://robmayhew.com/delete-parts-of-subversion-history/
Exemple 2 - Removing a directory:
http://www.lesnikowski.com/blog/index.php/how-to-permanently-remove-svn-folder/

Cheers,
Ludovic

2011/10/23 Nico Kadel-Garcia 

> On Mon, Oct 10, 2011 at 12:28 PM, filomena ciola
>  wrote:
> > Hello,
> > Please I need your help for a little question:
> > I need to erase all the old revisions, if it' s possible, how can I do
> for
> > make this automatically? if this isn't possible, can I put a pw so only
> > authorized personell can see old revision?
> > Thank you for your interesting
> > With best regards
> >
> >
> > Mimma Ciola
>
> If they can see the file, in Subversion, they can see all the old
> relevant revisions from that repository. They may not be able to see
> *other* files if you have access to them blocked in Apache or svnserve
> managed access.
>
> It's also vaguely feasible that if you used svn+ssh based access, the
> relevant "svn" user could be made not a member of the appropriate
> groups to see that old revision at all.  But this would get *nasty*,
> very quickly, It would be like replacing the command "rm" with
> something that moves files aside. It would work until it broke,
> *badly*.
>

Subversion Exception!

[Frank [Aerapay]]

---

Subversion Exception!

---

Subversion encountered a serious problem.

Please take the time to report this on the Subversion mailing list

(users@subversion.apache.org)

with as much information as possible about what

you were trying to do.

But please first search the mailing list archives for the error message

to avoid reporting the same problem repeatedly.

You can find the mailing list archives at

http://subversion.apache.org/mailing-lists.html

 

Subversion reported the following

(you can copy the content of this dialog

to the clipboard using Ctrl-C):

 

In file

'D:\Development\SVN\Releases\TortoiseSVN-1.7.0\ext\subversion\subversion\lib
svn_wc\workqueue.c'

line 672: assertion failed (checksum != NULL)

---

OK   

---

 

I look forward to hearing from you.

 

Kind Regards,

 

 

Frank

 

---

Frank Georgoulas 

Managing Director

Aerapay

  aerapay.com

 

PH: +61 (0) 448 900 510

  LinkedIn 

  Skype

 

Re: Subversion Exception!

[Ryan Schmidt]

On Oct 23, 2011, at 18:59, Frank [Aerapay] wrote:

> ---
> Subversion Exception!
> ---
> 
> Subversion encountered a serious problem.
> Please take the time to report this on the Subversion mailing list
> (users@subversion.apache.org)
> with as much information as possible about what
> you were trying to do.

^^^

> But please first search the mailing list archives for the error message
> to avoid reporting the same problem repeatedly.

^^^

> You can find the mailing list archives at
> http://subversion.apache.org/mailing-lists.html

Re: SVN to Base Clearcase

[sureshkumar nandakumar]

Team,

Can anyone, please guide me on this..


We are struggling more than one year to find a good solution for merge the
SVN branch source to Clearcase branch along with all the versions.

We really appreciate, if you advice to get it done this scenario.



 Please advice and give us solution….


On Wed, Oct 19, 2011 at 12:31 PM, sureshkumar nandakumar <
suresh1256...@gmail.com> wrote:

> Hi,
>
> I need your help to sync my svn branch source with Base clearcase
> branch.
>
> *SVN Details:*
> We have installed latest svn version in red hat Linux & it is
> accessing via Tortoise client.
>
> *Base Clearcase Details:*
> We have one more Version control tool. That is base clearcase which
> was installed in AIX server.
>
> We have two different teams. One team is working with SVN and another
> team is working with IBM BASE Clearcase.
> If any changes will happen in SVN branch, the same source needs to
> sync with Base Clearcase.
>
> Currently we are taking SVN branch source manually using svn export
> command and moving in to Clearcase branch.
> This is not right way for maintaining full Version history.
>
> If we follow the same way, we can able to find only svn branch latest
> files in Clearcase branch.
> It would be great help if you suggest to me for merging svn branch
> source with clearcase branch with full versions.
>
>
> For example: if a.java file is having 10versions in svn branch, i need
> all 10 versions to be sync with Clearcase branch. please assist me,
> how i can do this from svn to Clearcase.
>
> We are struggling more than one year.
> i have tried Clearsvn tool. but it is not compatible for AIX & Linux
> servers
>
> Apart from that Is that any way to sync SVN branch to Clearcase branch
> with full version history.
>