Summary: | app-office/gnucash-2.2.2 fails to build | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Reinhard Kreim <reini> |
Component: | Current packages | Assignee: | Torsten Veller (RETIRED) <tove> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ed, gnome-office+disabled, halcy0n, jsled, systemdesignworks |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | goffice-0.6.patch |
Description
Reinhard Kreim
2008-01-01 18:16:16 UTC
Dup of Bug#202862. no, this bug looks like gnucash just doesn't check for a libgoffice-0.6.pc This is the kind of problems to be expected with versionned .pc file. (In reply to comment #2) > no, this bug looks like gnucash just doesn't check for a libgoffice-0.6.pc > This is the kind of problems to be expected with versionned .pc file. Well, there's no assurance that gnucash can even build (let alone run) against goffice-0.6. At the time the check was updated to include 0.5.1, 0.6 didn't exist, yet. (Presumably it's versioned because there is incompatability that requires a version bump, so code changes might be required to get it to build against 0.6...) Regardless, making the gnucash ebuild be more specific about which versions of goffice are supported is correct; I thought that's what Bug#202862 was, but looking at it more closely, I guess I was mistaken. :/ Sorry for the noise. no problem. I'll let tove fix this though since he probably knows gnucash better. Some problem here. I masked >=x11-libs/goffice-0.6 and everyting worked. Maybe ebuild should block >=x11-libs/goffice-0.6. symbolic linking in '/usr/lib/pkgconfig' with "# ln -s libgoffice-0.6.pc libgoffice-0.5.pc" does the job: emerges smooth, runs smooth! (In reply to comment #6) > symbolic linking in '/usr/lib/pkgconfig' with > "# ln -s libgoffice-0.6.pc libgoffice-0.5.pc" > does the job: emerges smooth, runs smooth! While an interesting datapoint, I hope you know this is a horrible idea… Same problem here. Created attachment 140144 [details, diff]
goffice-0.6.patch
Patch.
(In reply to comment #9) > Created an attachment (id=140144) [edit] > goffice-0.6.patch > > Patch. > With your patch it compiles fine :) (In reply to comment #3) > (In reply to comment #2) > > no, this bug looks like gnucash just doesn't check for a libgoffice-0.6.pc > > This is the kind of problems to be expected with versionned .pc file. > > Well, there's no assurance that gnucash can even build (let alone run) against > goffice-0.6. At the time the check was updated to include 0.5.1, 0.6 didn't > exist, yet. (Presumably it's versioned because there is incompatability that > requires a version bump, so code changes might be required to get it to build > against 0.6...) Well, it builds and runs. A quick check didn't show any differences in the functions gnucash uses. Speak up if i miss anything. I'll commit a patched version later. I just did a portage/system update today (2008-01-06) which installed x11-libs/goffice-0.6.1 in a new slot. I then ran: emerge --ask --verbose --depclean It reported x11-libs/goffice-0.2.1 as uneeded and I unmerged it. Now gnu-cash doesn't run. Error message is: "gnucash-bin: error while loading shared libraries: libgoffice-1.so.2: cannot open shared object file: No such file or directory" Is this related to the problem under discussion here? Should I manually re-emerge goffice-0.2.1? (In reply to comment #12) > I just did a portage/system update today (2008-01-06) which installed > x11-libs/goffice-0.6.1 in a new slot. I then ran: [snip] > Is this related to the problem under discussion here? Should I manually > re-emerge goffice-0.2.1? This is unrelated to this bug, just use revdep-rebuild. (In reply to comment #9) > Created an attachment (id=140144) [edit] > goffice-0.6.patch > > Patch. Upstream's version on 2.2 branch for upcoming 2.2.3: http://svn.gnucash.org/trac/changeset/16829 Thanks! (In reply to comment #13) > (In reply to comment #12) > > I just did a portage/system update today (2008-01-06) which installed > > x11-libs/goffice-0.6.1 in a new slot. I then ran: > [snip] > > Is this related to the problem under discussion here? Should I manually > > re-emerge goffice-0.2.1? > > This is unrelated to this bug, just use revdep-rebuild. I did run "revdep-rebuild -X -- -av". Yesterday, here is the order I run my update: emerge --sync emerge --ask --verbose --update --newuse --deep --tree world revdep-rebuild -X -- -av dispatch-conf emerge --ask --verbose --depclean After I posted, I did a one-shot emerge of goffice-0.2.1 and gnu-cash works again. But something is still wrong in portage because if I run: revdep-rebuild -X -- -av emerge --ask --verbose --depclean It still wants to remove 0.2.1: >>> These are the packages that would be unmerged: x11-libs/goffice selected: 0.2.1 protected: none omitted: 0.6.1 If I remove it again, will it cause gnu-cash not to work again? (In reply to comment #15) > revdep-rebuild -X -- -av > emerge --ask --verbose --depclean > > It still wants to remove 0.2.1: > > >>> These are the packages that would be unmerged: > > x11-libs/goffice > selected: 0.2.1 > protected: none > omitted: 0.6.1 > > If I remove it again, will it cause gnu-cash not to work again? > Remove the old version of goffice, then run revdep-rebuild. (In reply to comment #16) > Remove the old version of goffice, then run revdep-rebuild. Something is still broken. I ran emerge --ask --verbose --depclean and let it remove goffice-0.2.1. Then I ran: revdep-rebuild -X -- -av and it wanted to re-emerge gnucash with the following command: emerge --oneshot --ask --verbose =app-office/gnucash-2.2.2 This failed with: checking for libgoffice-0.5 >= 0.5.1... no checking for libgoffice-0.4 >= 0.4.0... no checking for libgoffice-0.3 >= 0.3.0... no checking for libgoffice-1 >= 0.0.4... no configure: error: Cannot find libgoffice. Any other suggestions? I am thinking I will re-install goffice-0.2.1 and try to remove it again later when gnucash-2.2.3 is released. -2.2.2-r1 is in tree and fixes the goffice-0.6 problems. Wait an hour, sync, and install -2.2.2-r1 and be happy. If you can wait longer, you'll probably get -2.2.3. |