[hardy] G-C-U FTBFS and Possible Merge
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-chemistry-utils (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Here is the scenario/problem:
MOM wants us to merge with debian 0.8.4. The problem is G-C-U 0.8.4 will FTBFS against libgoffice-0.5.1 or newer (our only version in hardy.) G-C-U devs have released 0.9 (development) but this will still not build against 0.5.1 or newer. Why?
G-C-U changelog portion:
-------
2007-09-28 Jean Brefort <email address hidden>
* configure.in: added goffice/math directory.
* goffice/
* goffice/
* goffice/
* goffice/goffice.c: ditto.
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* goffice/
* plugins/
* plugins/
* plugins/
* plugins/
* plugins/
* plugins/
* plugins/
* plugins/
* plugins/
* plugins/
* plugins/
* plugins/
* plugins/
* plugins/
* plugins/
* plugins/
* plugins/
* plugins/
* plugins/
* plugins/
* plugins/
-------
So at this point G-C-U will FTBFS using the current version (0.6.3) or the upstream debian version. Debian has been bypassing this issue so far by sticking with libgoffice-0.4. I have not verified but I expect that the current binary will not run properly in hardy (if at all). I found this problem while attempting to create a merge candidate (0.8.4-3ubuntu1). Here is what MUST be done:
(1) Fix G-C-U so it will build from source and run in hardy.
How?
1) I recommend someone notifies G-C-U devs to this problem and have them fix their code to build against libgoffice >= 0.5.1.
2) Pending the results of (1) if G-C-U devs release a new version we can directly import this into ubuntu because debian will likely stick with libgoffice 0.4 for a while. Otherwise we will need to heavily patch the 0.8.4 source from debian to build against our current (and only) libgoffice which is 0.5.1.
Or we can remove G-C-U from the hardy repositories.
G-C-U should be built against libgoffice 0.4 . Debian has it and we should sync it for Hardy. Then we can merge G-C-U 0.8.4
G-C-U 0.9.x are unstable development releases and we should *not* put them into hardy, especially as it is an LTS release.