First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 122877
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Paul de Vrieze <pauldv@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Tom Hosiawa <tomek32@gmail.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 122877 depends on: Show dependency tree
Bug 122877 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2006-02-14 22:09 0000
After upgrading to db-4.2.52_p2-r1, subversion repositories need to be
recovered.

# svnlook youngest /srv/svn/pub/portage/
svnlook: Berkeley DB error for filesystem /srv/svn/pub/portage/db while opening
environment:
Invalid argument
svnlook: bdb: Program version 4.2 doesn't match environment version

I noticed this when I saw the error in websvn. Maybe a note should be made in
the db ebuild reminding users to recover all their repositories "svn recover
repo" and checks permission on repository after upgrading.

------- Comment #1 From Paul de Vrieze 2006-02-15 03:32:47 0000 -------
I'll create a check for it sometime. The problem is that this requires some
magic on the actually installed binaries as it's not that easy to just record
the used db version. It should be in the subversion ebuild though. In general
db is mainly a cause of lots of suffering.

In any case there might be merrits on using fsfs as your repository format. In
general it has a lot less problems.

------- Comment #2 From Arfrever Frehtes Taifersar Arahesis 2007-09-03 23:21:18 0000 -------
It is fixed in subversion-1.5_pre26438 in Eaedificāta Repository.
http://www.ffta.host.sk/Eaedificata/index.html

------- Comment #3 From Benedikt Böhm 2007-09-08 14:20:18 0000 -------
fixed in 1.4.4-r4

First Last Prev Next    No search results available      Search page      Enter new bug