[Pkg-crosswire-devel] newer SWORD packages (SWORD 1.6.1 status?)

[Jonathan Marsden]

Matthew Talbert wrote:

> My libsword package I built myself. Basically I svn'ed up, copied the
> debian directory from the PPA source package, modified it so that it
> would patch correctly (several patches are no longer needed), and
> built it. This way I can still install Bibletime from the PPA without
> having to build it myself. Theoretically, so long as sword doesn't
> break ABI, this should work (I think). 

Agreed.

> Anyway, it no longer does :(  Although, the problem could be a real
> problem, but I don't have much way of knowing.

One fairly easy way to check would be: install the official libsword8
package, see if the problem goes away, install your homebrew libsword8
package, retest :)

If the bug only occurs in your svn-based packaged libsword8, then either
you introduced the issue in your packaging process, or changes in SWORD
svn after the 1.6.0 release did.  To determine which, you can package
earlier and earlier svn revisions, until the issue disappears... either
you'll get all the way back to 1.6.0 timeframe, or else you'll know
exactly where the bug was introduced in svn.

Or, you could persuade Troy to release SWORD 1.6.1 -- and then *I* get
to do the packaging and testing work, instead of you :)

> On a completely separate topic, it would be great to get the source
> in the bzr repo updated to latest svn (or do you only update it at 
> release? I'm not sure how that works).

When there is a new SWORD tarball released for us to package, we'll
update bzr to use it.  We probably won't update bzr before that, unless
there is a clear need for a new Debian/Ubuntu package of SWORD and there
is no sign of a new official SWORD tarball, and we decide to "just go
for it" and package up something from SWORD svn out of necessity... but
I *hope* that's pretty unlikely to become necessary :)

A status update from Troy on the proposed SWORD 1.6.1 release would be
useful as part of this discussion :)

Jonathan