[sword-devel] Sword 1.6.2 NOW!
mg.pub at gmx.net
Tue Sep 14 03:19:32 MST 2010
branching is not a pain for this kind of purpose. Just branch off the
repository state of 1.5.1 (I guess there is a tag available), apply the
one-liner, and release a 18.104.22.168. A bugfix release. That should have
been the answer to the problems at hand, not a patch.
Am 14.09.10 11:58, schrieb Karl Kleinpaste:
> Jaak Ristioja <Ristioja at gmail.com> writes:
>> Why not branch?
> Because branching is a whole new world of pain, for something as
> straightforward as a workaround patch for a curl library bug. It's a
> one-line patch, for pity's sake.
>> Since there has probably been no announcement from Sword that distros
>> should patch,
> Um... Procession from false assumption. Anyone who's involved enough
> to be doing distribution of Sword software ought to be involved enough
> to be seeing discussion about such things as the curl bug and its patch
> When the bug was encountered, there was rather a lot of activity about
> it. Anyone who didn't see it...just wasn't watching.
>> If I remember correctly, an OpenSUSE user was the last to report the
>> bug to BibleTime, so maybe OpenSUSE still has it unpatched.
> No. Brian Dumont <bdumont at ameritech.net> is on top of that, and has
> informed me in the past that appropriate updates were available as of
> Aug 05.
> Whether updated builds get to the field properly is a whole different
> question -- e.g. we have the annoying nightmare that a Xiphos display
> workaround release for an xulrunner bug, fixed in May, hasn't gotten
> back to Ubuntu repositories, though it's available elsewhere just fine
> (via CrossWire's Ubuntu PPA for Sword builds).
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel