Peter isn't who I was thinking would benefit from keeping a professional
level of communication in the list. The other members might enjoy the list
more. The need to adjust things is obviousThe need to tell everyone on the
list about a missing entry which causes nobody trouble is well... possibly
a
Michael,
I'm sure Peter is quite happy for me to report even minor feedback
observations in this mailing list.
It's not as if this aspect of the module release script had not functioned
somewhat erratically on previous occasions, is it?
He and I do have private conversations as well, you know!
An
Hooray Peter for the Hard work.
Can we fix the negative comments script to only feedback to those who need
the info?
On Fri, Jun 16, 2017 at 12:55 PM, David Haslam
wrote:
> Please review how the module release script generates this line in the
> announcement message.
>
> "Many thanks to *The* f
They're in CrossWire Main, mostly under Bibles.
For details of all repos, see https://crosswire.org/wiki/Module_Repositories
Most front-end apps access each repo by name.
If I recall aright, And Bible is the exception, in that modules from all the
repos are presented in one list.
For many front-
On 06/17/2017 06:27 AM, David Haslam wrote:
> If *Bela* has "just" been updated, why doesn't it appear under Updates in
> the Xiphos module manager?
Someone probably just forgot update the version stamp. Presence in
Xiphos' mod.mgr updates depends on a simple comparison.
_
On Sat, Jun 17, 2017 at 03:55:02AM -0700, David Haslam wrote:
> tausug.conf has these minor issues:
>
> Duplicate keys.
>
> Scope=NTOnly
> ...
> Scope=Mat-Rev
>
>
> This is missing: (required for Versification=NRSV)
>
> MinimumVersion=1.6.0
>
> This key has no language name:
> LCSH=Bible..N.T
tausug.conf has these minor issues:
Duplicate keys.
Scope=NTOnly
...
Scope=Mat-Rev
This is missing: (required for Versification=NRSV)
MinimumVersion=1.6.0
This key has no language name:
LCSH=Bible..N.T.
Best regards,
David
--
View this message in context:
http://sword-dev.350566.n4.n
I'm confused!
If *Bela* has "just" been updated, why doesn't it appear under Updates in
the Xiphos module manager?
And yes - I know about Refresh...
The latest module is still version 1.5 - yet version 1.5 was released with
SwordVersionDate=2012-07-12.
Best regards,
David
--
View this me