Bug 443754
| Summary: | Gramps 3.0 is out | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jack Deslippe <jdeslip> | ||||||||
| Component: | gramps | Assignee: | Jeffrey C. Ollie <jeff> | ||||||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | low | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 9 | CC: | berrange, bigjoe1008, loganjerry, mark | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | All | ||||||||||
| OS: | Linux | ||||||||||
| URL: | http://www.gramps-project.org/wiki/index.php?title=Main_Page | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2008-12-09 11:37:29 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Jack Deslippe
2008-04-23 05:17:25 UTC
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Because version 3 requires an upgrade to the DB and such would this have to get pushed to F10? Created attachment 313362 [details]
Spec file for gramps 3.0.1
I have attached a quick rework of the spec file for 2.2.10 to build 3.0.1. I have not tested this in a mock environment so there may be some new dependencies. It built just fine on Fedora 9 (64bit).
Still no updated package even in rawhide... Perhaps the packager has dropped gramps? Can I get the rpm you built Joseph? I've been working on an updated package for rawhide, however given that I haven't had a running rawhide system for a while it's been difficult to test a new package - the dependencies have changed in rawhide so it's taken a while to get a package to build. I'm taking the plunge and upgrading my laptop to rawhide this weekend so I should be able to do some testing next week. As I think I've said elsewhere I do not have any plans to update F9 or earlier to gramps 3.x. Any ETA on getting a 3.0.x release into Fedora ? The upstream project publishes source RPMS for Fedora, so perhaps they'd be interested in maintaining the official Fedora packages directly ? FWIW, the upstream package installs without trouble on Fedora 9, and the database format upgrade worked automatically & flawlessly first time it was run. Created attachment 324316 [details]
Patch against the current spec file to upgrade to 3.0.3
I've updated the package from CVS with the required changes to update the package from 2.2.10 to 3.0.3. The package builds and installs for both F9 and F10 and is working properly on both.
I'm also attaching the patch to handle the BerklyDB change in the python shipping with F10 referenced in the spec file changes.
Created attachment 324317 [details]
Patch to handle the different BerklyDB versions between F9 and F10
This patch is needed to run version 3.0.3 on both F9 and F10. The next version of GRAMPS should include these changes (hopefully) and it won't be required after that.
gramps-3.0.3-0.fc10 has been submitted as an update for Fedora 10. http://admin.fedoraproject.org/updates/gramps-3.0.3-0.fc10 gramps-3.0.3-0.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gramps'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/f10/FEDORA-2008-10255 gramps-3.0.3-0.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report. |