[UNMETDEPS] gnomesword has unmet dependencies

It should probably depend on libsword6.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Furthermore there is a build dependency problem.

The build of gnomesword depends on libsword-dev (>=1.5.8-7) and
libsword-dev (<< 1.5.8.90-1) but 1.5.9-0ubuntu3 is available in Edgy.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFLZzi4L7OnT0GlBoRArAhAJ4hvracdBg4vIq2avaZ6LHvS1qZbwCglJ0X
8w2a7DtQLKsm/qmGNpYEkLI=
=/71T
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Seems that it was not as easy as I though..

gnomesword does not compile with libsword6-dev..
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFL3254L7OnT0GlBoRAvx5AKCK7hYT37v18J/2Rwe6A6z4YSyJdQCdGj2g
JXqcg3OY42N1vD3/uSUS558=
=Vbei
-----END PGP SIGNATURE-----

I mean libsword-dev 1.5.9-0ubuntu3

Submitted to gnomesword bts here :http://sourceforge.net/tracker/index.php?func=detail&aid=1576964&group_id=5528&atid=105528

The solution is to add --enable-sword_svn to ./configure. This has been fixed in the svn a developer told me. There is a new problem but I hope that I can fix it.

I will prepare updated packages if everything is working fine.

The comment on the gnomesword bts says the same, without the mention of the second problem.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I know.. Sorry for that.

ajmitch now fixes the problem because I was not able to fix it. It is:

g++: @LUCENE_LIBS@: No such file or directory

and as far as I understand it is caused by m4 not being able to detect
lucene.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFML1+4L7OnT0GlBoRAvgKAJ4l3Y7873jOMXvDWa8fscZei6IrYgCeNR4H
4tvgxZ9dLb0kC6jaeCO+PEU=
=Fla6
-----END PGP SIGNATURE-----

@LUCENE_LIBS@: No such file or directory

Gnomesword relies on pkg-config for setting up config files.
However, the pkg-config metadata file (/usr/lib/pkgconfig/sword.pc) of sword 1.5.9 is actually broken.
Replacing @LUCENE_LIBS@ by -lclucene in this file allows Gnonesword to be built against libsword 1.5.9

Hi!

Andrew, any progress on this bug?
A lot of people wait for it in edgy-updates :)

gnomesword 2.1.9-1 is now in feisty, build against libsword6.

Please, open a backport task.

-> Considering libsword-dev (>=1.5.9-2)
      Tried versions: 1.5.9-0ubuntu3
   -> Does not satisfy version, not trying
E: Could not satisfy build-dependency.

It doesn't build in prevu, so I think it won't be backported, sorry.

I'm sorry, I do not agree.

 I've built debs of GnomeSword svn on a stock Ubuntu 6.10 with libsword-dev modified as above since november.Moreover, I'm using it everyday.

There is nothing wrong with GnomeSword.

 libsword-dev in Edgy is buggy. Daniel Glassey had provided a fix in November for Debian.

why a fix to a broken package (aka libsword-dev) takes so long to enter Edgy?

dissapointed that this has taken so long on a top of a line distro.....

honestly, this bug should not take that long to fix....

gnomesword is in universe, which is being community maintained.

Afaik, backporting means to take a package from the developing version and to build it on a stable version, so, building a .deb from scratch and put it to Edgy would not work (Edgy is frozen).

A first step is to try to get sword backported to Edgy. When the Feisty gnomesword builds on Edgy then, a backport *should* be possible.

I'm kind of a noob to building stuff for the ubuntu repository, but why don't you just take the debian package of libsword5, like suggested on http://www.ubuntuforums.org/showthread.php?t=285641? It would make it installable, which is an lot better than waiting for feisty...