-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14.09.2010 01:07, Troy A. Griffitts wrote:
We plan to release soon, but didn't know there was an urgent need.
There are things unreleasable in head right now which need to be removed
if we release 1.6.2 sooner rather than later.
Why not branch?
Jaak Ristioja risti...@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
Hi Karl,
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 1.5.1.1. A bugfix release. That should have
been the answer to the problems at hand, not a patch.
mg
Am 14.09.10 11:58,
On Tue, Sep 14, 2010 at 12:58, Karl Kleinpaste k...@kleinpaste.org wrote:
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
Am Mon, 13 Sep 2010 23:07:32 +0100
schrieb Troy A. Griffitts scr...@crosswire.org:
We plan to release soon, but didn't know there was an urgent need.
There are things unreleasable in head right now which need to be
removed if we release 1.6.2 sooner rather than later.
I was under the
Am 14.09.2010 um 11:19 schrieb Martin Gruner:
Hi Karl,
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 1.5.1.1. A bugfix release. That should have
been the answer to the
Understood going forward.
There were a few factors which made this a slightly non-standard
situation. First, this wasn't exactly a bug fix. It was a workaround
for a bug in a version of libcurl. I was hoping libcurl would be
patched. And no, I personally didn't report the issue to the
On Tue, Sep 14, 2010 at 12:43 PM, Troy A. Griffitts
scr...@crosswire.org wrote:
Understood going forward.
There were a few factors which made this a slightly non-standard situation.
First, this wasn't exactly a bug fix. It was a workaround for a bug in a
version of libcurl. I was hoping
I know for sure that Fedora (a few F11+ i think) Debian (squeeze+) and
Ubuntu (well Karmic+ if you consider PPA or Lucid+ from main archive)
are all patched.
This is way to small for a bugfix release (I'd rather see more
personally). This issue was not present a the time sword 1.6.1 was
released,
Thanks for the email link Greg. Yeah, the submitted changes in
question from project A were filter updates, and we do specifically
state in that email that filter updates are allowed in a stable branch.
It was kindof an odd situation. The updates merely added css classes to
a few of the
On 14 September 2010 19:46, Troy A. Griffitts scr...@crosswire.org wrote:
Thanks for the email link Greg. Yeah, the submitted changes in question
from project A were filter updates, and we do specifically state in that
email that filter updates are allowed in a stable branch. It was kindof
On Tue, Sep 14, 2010 at 1:46 PM, Troy A. Griffitts scr...@crosswire.org wrote:
Thanks for the email link Greg. Yeah, the submitted changes in question
from project A were filter updates, and we do specifically state in that
email that filter updates are allowed in a stable branch. It was
On Wed, Sep 15, 2010 at 10:55 AM, Greg Hellings greg.helli...@gmail.comwrote:
IMO, it would be the other way. If people see a CMake system they
will probably think it's exactly like the autotools, which is not easy
to guarantee. I would think CMake should be held off for a feature
update
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello!
Please release a bugfix version of Sword ASAP! The current version 1.6.1
crashes with all recent versions of curl, while curl versions older than
7.20.0 are being removed from distributions. So this is very urgent. For
the bug, see:
We plan to release soon, but didn't know there was an urgent need.
There are things unreleasable in head right now which need to be removed
if we release 1.6.2 sooner rather than later.
I was under the impression all distros already had our patch in their
distribution. What distros release
15 matches
Mail list logo
