Standing on the shoulders of giants... I got it to build with the
attached control file, after building g-wrap, goffice, libgsf-1 but NOT
dpkg-dev. The gnucash debian changelog makes it clear why the dpkg-dev
version dependency was increased and I don't feel it matters for the
purpose of backports, so I dropped the version number and reverted the
other change.

The resulting gnucash debs (built from edgy source on edgy using prevu)
seem to install fine on dapper and load my data file considerably faster
than the similar version linked from the ubuntuforums thread.

[EMAIL PROTECTED]:~/deb/gnucash-2.0.1$ cd /var/cache/prevu/dapper-debs/
[EMAIL PROTECTED]:/var/cache/prevu/dapper-debs$ ls
gnucash_2.0.1-3ubuntu3~6.06prevu1_i386.deb
gnucash-common_2.0.1-3ubuntu3~6.06prevu1_all.deb
guile-g-wrap_1.9.6-3.1~6.06prevu1_i386.deb
g-wrap_1.9.6-3.1~6.06prevu1_i386.deb
libgoffice-0-3_0.3.0-1ubuntu1~6.06prevu1_i386.deb
libgoffice-0-3-dbg_0.3.0-1ubuntu1~6.06prevu1_i386.deb
libgoffice-0-common_0.3.0-1ubuntu1~6.06prevu1_all.deb
libgoffice-0-dev_0.3.0-1ubuntu1~6.06prevu1_i386.deb
libgoffice-gtk-0-3_0.3.0-1ubuntu1~6.06prevu1_i386.deb
libgoffice-gtk-0-3-dbg_0.3.0-1ubuntu1~6.06prevu1_i386.deb
libgsf-1-114_1.14.1-2ubuntu1.1~6.06prevu1_i386.deb
libgsf-1-114-dbg_1.14.1-2ubuntu1.1~6.06prevu1_i386.deb
libgsf-1-common_1.14.1-2ubuntu1.1~6.06prevu1_all.deb
libgsf-1-dev_1.14.1-2ubuntu1.1~6.06prevu1_i386.deb
libgsf-bin_1.14.1-2ubuntu1.1~6.06prevu1_i386.deb
libgsf-gnome-1-114_1.14.1-2ubuntu1.1~6.06prevu1_i386.deb
libgsf-gnome-1-114-dbg_1.14.1-2ubuntu1.1~6.06prevu1_i386.deb
libgsf-gnome-1-dev_1.14.1-2ubuntu1.1~6.06prevu1_i386.deb
libgwrap-runtime0_1.9.6-3.1~6.06prevu1_i386.deb
libgwrap-runtime0-dev_1.9.6-3.1~6.06prevu1_i386.deb


** Attachment added: "gnucash debian/control file which worked for me"
   http://librarian.launchpad.net/5392882/control

-- 
GnuCash 2.0.0 
https://launchpad.net/bugs/52486

-- 
ubuntu-backports mailing list
[email protected]
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-backports

Reply via email to