Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#37024 - [gramps] conflicts with pyxml

Attached to Project: Community Packages
Opened by Patrick Smits (PS0) - Sunday, 22 September 2013, 11:17 GMT
Last edited by Sergej Pupykin (sergej) - Monday, 30 September 2013, 09:44 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
If pyxml is installed, gramps will fail to create reports.
See http://bugs.gramps-project.org/view.php?id=6947 for details.

I solved this by removing pyxml. So, pyxml should be added to the conflicts list in the PKGBUILD.

Additional info:
gramps version 2:4.0.1-3
This task depends upon

Closed by  Sergej Pupykin (sergej)
Monday, 30 September 2013, 09:44 GMT
Reason for closing:  Fixed
Additional comments about closing:  python3 is used now
Comment by Munzir Taha (munzirtaha) - Monday, 30 September 2013, 05:37 GMT
Adding pyxml to the conflicts list would not allow users to install other packages like gcompris. A better solution is to modify the build gramps against python3. This resolved the issue for me. I even wonder why it's kept to python2 though gramps 4 supports and recommends python 3 now.

Loading...