# Trouble committing after import of repository from 1.6.0

**URL:** <https://community.cloudogu.com/t/trouble-committing-after-import-of-repository-from-1-6-0/1105>\
**Category:** SCM-Manager Bug Reports\
**Created:** [March 17, 2023, 8:44am UTC](https://community.cloudogu.com/t/trouble-committing-after-import-of-repository-from-1-6-0/1105 "2023-03-17T08:44:17Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![kulturserver](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/kulturserver/32/1470_2.png) [@kulturserver](https://community.cloudogu.com/u/kulturserver)\
**Post date:** [March 17, 2023, 8:44am UTC](https://community.cloudogu.com/t/trouble-committing-after-import-of-repository-from-1-6-0/1105/1 "2023-03-17T08:44:17Z")

</div>

Hi, we’re currently trying to move all our repositories from scm manager 1.6.0 to 2.42.2 - Importing the dump works, as does the checkout. But when we try to commit a change in the repository, we receive the error E155011 mentioning the file is out of date. What might be the problem and is there a solution? Any help would be appreciated, thanks!

Here are our steps in detail (original language was german, hope I translated it back correctly)

-getting a dump of the repos from scm-Manager 1.60 via svnadmin:  
svnadmin dump /var/repos-global/reponame \> reponame.dump

- Import in SCM.Manager 2.42.2 via webinterface:
- import repository
- import without meta data or compression

-Checkout via svn checkout url/repo/svn/reponame works

when committing:  
user@host:~/test/reponame$ svn commit  
Send dev/config.php

svn: E155011: Transfer failed (details follow)  
svn: E155011: File »/home/user/test/reponame/dev/config.php« is out of date  
svn: E160013: »/repo/svn/reponame/!svn/ver/97/dev/config.php« path not found

---

<div class="post-metadata">

**Author:** ![eheimbuch](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/eheimbuch/32/18_2.png) [@eheimbuch](https://community.cloudogu.com/u/eheimbuch)\
**Post date:** [March 20, 2023, 7:27am UTC](https://community.cloudogu.com/t/trouble-committing-after-import-of-repository-from-1-6-0/1105/2 "2023-03-20T07:27:26Z")

</div>

Hey, you perhaps tried this already but did `svn update` help? Also are your sure that your url is right? Can you access this file via curl `/repo/svn/reponame/!svn/ver/97/dev/config.php`?

Just to mention it. There are several SVN compatibility issues depending which version you used before. You can change that in your global Subversion settings.

 ![Screenshot from 2023-03-20 08-11-26](https://europe1.discourse-cdn.com/flex013/uploads/cloudogu2/original/2X/8/83396d3929ad562190bed090c40675237ce7901a.png)

---

<div class="post-metadata">

**Author:** ![kulturserver](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/kulturserver/32/1470_2.png) [@kulturserver](https://community.cloudogu.com/u/kulturserver)\
**Post date:** [March 23, 2023, 3:08pm UTC](https://community.cloudogu.com/t/trouble-committing-after-import-of-repository-from-1-6-0/1105/3 "2023-03-23T15:08:47Z")

</div>

Thanks a lot for the reply - we’ve had some other trouble unfortunately and were just now able to check your suggestions.  
Yes, we tried svn update and it unfortunately didn’t help. We can’t access the file via curl, there’s also a 404 not found reply.

We’ve checked the subversion compatibility - on both servers we work with version 1.6. and format 4, so this doesn’t help either…are there any more suggestions? Thanks again!

---

<div class="post-metadata">

**Author:** ![kulturserver](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/kulturserver/32/1470_2.png) [@kulturserver](https://community.cloudogu.com/u/kulturserver)\
**Post date:** [April 24, 2023, 2:06pm UTC](https://community.cloudogu.com/t/trouble-committing-after-import-of-repository-from-1-6-0/1105/4 "2023-04-24T14:06:56Z")

</div>

Still couldn’t find a solution, unfortunately…any other suggestions? Thanks in advance!

---

<div class="post-metadata">

**Author:** ![kulturserver](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/kulturserver/32/1470_2.png) [@kulturserver](https://community.cloudogu.com/u/kulturserver)\
**Post date:** [July 30, 2024, 10:01am UTC](https://community.cloudogu.com/t/trouble-committing-after-import-of-repository-from-1-6-0/1105/5 "2024-07-30T10:01:37Z")

</div>

Because we couldn’t find an alternative in the meantime, maybe someone may have a solution now? Any help would be appreciated, thanks!

---

<div class="post-metadata">

**Author:** ![tanh](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/tanh/32/1738_2.png) [@tanh](https://community.cloudogu.com/u/tanh)\
**Post date:** [August 8, 2024, 12:19am UTC](https://community.cloudogu.com/t/trouble-committing-after-import-of-repository-from-1-6-0/1105/6 "2024-08-08T00:19:17Z")

</div>

> [@kulturserver](#):
>
> subversion compatibility - on both servers we work with version 1.6. and format 4, so this doesn

Hi @kulturserver, have you tried using `svnadmin load /path/to/scm-home/repositories/id/data < oldrepo.dump`. It’s a more direct method of importing a SVN dump.

---

<div class="post-metadata">

**Author:** ![kulturserver](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/kulturserver/32/1470_2.png) [@kulturserver](https://community.cloudogu.com/u/kulturserver)\
**Post date:** [August 12, 2024, 10:10am UTC](https://community.cloudogu.com/t/trouble-committing-after-import-of-repository-from-1-6-0/1105/7 "2024-08-12T10:10:58Z")

</div>

Thanks, yes, we tried that already!

---

<div class="post-metadata">

**Author:** ![tanh](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/tanh/32/1738_2.png) [@tanh](https://community.cloudogu.com/u/tanh)\
**Post date:** [August 21, 2024, 10:09pm UTC](https://community.cloudogu.com/t/trouble-committing-after-import-of-repository-from-1-6-0/1105/8 "2024-08-21T22:09:00Z")

</div>

> [@kulturserver](#):
>
> /config.php« is out of date

hello @kulturserver, this might suggest that the error is with the SVN repo itself. I found this through a quick googling session. I hope that it might help.

> <https://stackoverflow.com/questions/87950/how-do-you-overcome-the-svn-out-of-date-error>

---

<div class="post-metadata">

**Author:** ![kulturserver](https://dub1.discourse-cdn.com/flex013/user_avatar/community.cloudogu.com/kulturserver/32/1470_2.png) [@kulturserver](https://community.cloudogu.com/u/kulturserver)\
**Post date:** [August 27, 2024, 7:38am UTC](https://community.cloudogu.com/t/trouble-committing-after-import-of-repository-from-1-6-0/1105/9 "2024-08-27T07:38:51Z")

</div>

Thanks for the reply, but that doesn’t help either unfortunately - we’ve checked the repositories multiple times and they are up to date and otherwise absolutely ok, too.  
What we’ve done:

- set up a test repo admin
- exported the repo via svnadmin dump admin \> admin.dump
- imported the repo via svnadmin load /var/lib/scm/repositories/id/data \< admin.dump
- everything worked fine:
- the data is in the repo
- svn checkout works
- adding files works and they can be committed
- but when we try to change a file e.g. by adding lines, we get the following message: (translated from german)

svn: E155011: Transfer failed (Details follow):  
svn: E155011: File «/home/user/svn/admin/dev/info.php is out of date  
svn: E160013: «/scm/repo/svn/admin/!svn/ver/637/dev/info.php« path not found  
svn: E155011: Your log message in a temporary file:  
svn: E155011: «/home/user/svn/admin/svn-commit.tmp«