Hi Nikolay,
It's been a while, but as I recall the process is.
1. Because all upgrades were from the last version, you'll need to get from 4.7.1 to 4.7.5.
https://wiki.lyrasis.org/display/FF/Releases
I would pay special attention to warning on the 4.7.3 notes in
case they apply to you.
2. Once you are at 4.7.5, you need to use the fcrepo-import-export tooling to make an export of your Fedora 4 repository on disk.
https://github.com/fcrepo-exts/fcrepo-import-export
3. Then you run the fcrepo-upgrade-utils to convert the on-disk representation to that of a Fedora 5 repository.
https://github.com/fcrepo-exts/fcrepo-upgrade-utils
4. Lastly you use the fcrepo-import-export tool from above to import your on-disk representation into a new Fedora 5.
Because of issues the Fedora project moved away from using the Modeshape JCR repository. Because of this I would recommend storing your export just in-case any issues arise so you have a backup of some of your data.
cheers,
jared
--
You received this message because you are subscribed to the Google Groups "Fedora Tech" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fedora-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fedora-tech/37f1e9a2-4fae-4bdc-92fd-86778059de46n%40googlegroups.com.
-- jwh...@gmail.com
To view this discussion on the web visit https://groups.google.com/d/msgid/fedora-tech/2388fe2d-dbbc-4c4d-a7ae-2a807779ddb1n%40googlegroups.com.
however, this may well have a knock on effect of breaking filesystem access
---
Dan Field
Developer, Fedora Program
LYRASIS
Hi Nikolay,
For the first error you can add the
"-Dfcrepo.properties.management=relaxed" Java system property to
allow you to update certain system managed properties.
More information here (https://wiki.lyrasis.org/display/FEDORA5x/How+to+allow+user-updates+to+certain+server+managed+triples)
For the second issue...I'm less sure.
Do the "parent" objects exist with their own *.ttl files in the
export on disk? It's been a while but if they don't then I believe
they are just pairtree resources and might be treated differently
in Fedora 5 from Fedora 4.
cheers,
jared
To view this discussion on the web visit https://groups.google.com/d/msgid/fedora-tech/dc47988d-645e-4094-a082-23d8ef2c118en%40googlegroups.com.
-- jwh...@gmail.com
Hi Nikolay,
Glad to hear it is working for you and yes, I would recommend the latest version (6.5.0).
cheers,
jared
To view this discussion on the web visit https://groups.google.com/d/msgid/fedora-tech/0775b933-ac48-4c54-99f2-e65c135538e6n%40googlegroups.com.
-- jwh...@gmail.com
Hi Nikolay,
The issue seems to be this
> Found non-empty schema(s) `fcrepo` but no schema history
table. Use baseline() or set baselineOnMigrate to true to
initialize the schema history table.
We use FlywayDB to manage our database changes and it defines a
schema history table to track what updates have or have not been
applied.
It looks like Fedora has been pointed at a database but that database was not created by Fedora 6 or perhaps it didn't start up correctly.
If this is the database from a previous version of Fedora, then I would recommend setting up a new database (i.e. fcrepo-6) and point to it.
If this is a new database specifically for Fedora 6, I would suggest dropping all the tables and trying again.
cheers,
jared
--
You received this message because you are subscribed to the Google Groups "Fedora Tech" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fedora-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fedora-tech/8878e37f-665e-48a9-b5ed-68f776eb0848n%40googlegroups.com.
-- jwh...@gmail.com
Hi Nikolay,
What happens if you attempt to view the resource at http://localhost:9030/fcrepo/rest/objects with a web browser or via cURL?
cheers,
jared
To view this discussion on the web visit https://groups.google.com/d/msgid/fedora-tech/c4bd798b-d4ae-4cf7-9768-ade0fda728f1n%40googlegroups.com.
-- jwh...@gmail.com
I don’t have anything helpful to add for this one, but as a future Fedora 4 to 6 migrator, I’d love to hear more about this. Being able to validate the migration process would be really useful.
David Cook
Senior Software Engineer
Prosentient Systems
Suite 7.03
6a Glen St
Milsons Point NSW 2061
Australia
Office: 02 9212 0899
Online: 02 8005 0595
From: fedor...@googlegroups.com <fedor...@googlegroups.com> On Behalf Of Nikolay Gannev
Sent: Wednesday, 19 June 2024 5:53 AM
To: Fedora Tech <fedor...@googlegroups.com>
Subject: Re: [fedora-tech] Upgrade Fedora
Hi all,
To view this discussion on the web visit https://groups.google.com/d/msgid/fedora-tech/262bd9f1-8262-4e58-89ca-bc73d1967313n%40googlegroups.com.
Hi,
There is not currently a Fedora 4 to 6 validator. One of the main issues is that 4 does not have a consistent on disk presentation to iterate over like both 3 and 6 do.
If there was enough interest and involvement it could be possible to look at refactoring the https://github.com/fcrepo4-labs/fcrepo-import-export-verify to validate an export against a 6 OCFL root and vice-versa. I'm not sure that is as strong of a test as you would have to be confident the export was correct.
Alternatively it would need to act against the Fedora 4.* HTTP
endpoint.
cheers,
jared
You received this message because you are subscribed to a topic in the Google Groups "Fedora Tech" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/fedora-tech/yaYqPbMmPRw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to fedora-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fedora-tech/019b01dac1d5%24d72434c0%24856c9e40%24%40prosentient.com.au.
-- jwh...@gmail.com