[sword-devel] Module upload: JapDenmo

DM Smith dmsmith at crosswire.org
Sat Jan 5 18:22:17 MST 2019


Peter and I spent some time on this today. More to do. Let me know if the vlsJoNT is visible now.

BTW, the extraneous emails regarding a new module were part of testing fixes.

DM

> On Jan 5, 2019, at 9:43 AM, DM Smith <dmsmith at crosswire.org> wrote:
> 
> I appreciate your eagerness and your service.
> 
> I can work with specifics fairly quickly. That vlsJoNT doesn’t work is helpful and I can look to see what’s where on the guest and host, but that still leaves me sleuthing for the specifics. I don’t know the text type to know what category to look under (though I can guess that NT means that it is a Bible) and I don’t know the language as it would appear in a front-end. Then I don’t know what front-end can see it and which cannot. (There are three different mechanisms: SWORD, PocketSword and JSword and each has a different issues that needs to be diagnosed.) When I have little time and hardly any specifics, I don’t try as it might be more than I have.
> 
> Can you be more specific?
> 
> I’m looking for a simple solution (e..g. sync more often) or a solvable problem (we also need to sync xyz, but didn’t) and have limited time.
> 
> In Him,
> 	DM
> 
>> On Jan 5, 2019, at 9:23 AM, David Haslam <dfhdfh at protonmail.com> wrote:
>> 
>> 2 days delay or less I could live with.
>> 
>> But it's more than that since module vlsJoNT was announced and it's still unobtainable via the module manager UI in most front-ends.
>> Likewise for most if not all module releases since sometime in May 2018.
>> Hence the sighing "When, oh, when...?"
>> 
>> My interest is in providing speedy feedback on any technical issues I can detect in new/updated modules.
>> e.g. If I can report any obvious faults in the .conf file, then the modules team can speedily fix them before there are too many complaints from end users.
>> 
>> I should hope that there are others in this mailing list that would like to provide a similar service.
>> 
>> Announcing module releases that users cannot install is akin to the inverse of "crying wolf".
>> 
>> Best regards,
>> 
>> David
>> 
>> Sent with ProtonMail Secure Email.
>> 
>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>> On Saturday, 5 January 2019 14:07, DM Smith <dmsmith at crosswire.org> wrote:
>> 
>>> I’m very encourage that there’s lots of interest in the module making process. If I can help maintain that momentum, I will.
>>> 
>>> I’ve privately asked Peter, in response to his lament about the problem, for specific things he wants fixed. I have not heard back from him. It is now early morning for me on the weekend and I’m able to help. At least for a few hours.
>>> 
>>> There has always been a lag of a day from when a module is “published” to when it is available to all of SWORD, PocketSword and JSword.
>>> 
>>> I got your email less than 2 hours after announcement. Wait 2 days for it to be fully published.
>>> 
>>> There are several parts to this:
>>> The email is published the moment that the module is put in mods.d and module.
>>> Daily mods.d.tar.gz is rebuilt with the listing of mods.d.
>>> The module is zipped when a user requests the download via the website’s listing of modules.
>>> The indexes for PocketSword and AndBible are built on a daily basis.
>>> The module sizes are updated into the conf daily.
>>> The host and guest repositories are synchronized daily.
>>> Front end users only know of the module when they refresh their module listing.
>>> 
>>> Note, the day lag has always been hit by JSword and noticed every now and then, but we’ve lived with it as long as JSword has been around. It only uses the compressed files.
>>> 
>>> I think your question really is, “When is 'status quo' going to be achieved?” The answer is “Not today, tomorrow or this week.” So, thus my question back to Peter, "What can we do in the meantime?”
>>> 
>>> I also, don’t like where we were before we had a split server and would like to solve that as well. But it’s not going to happen soon, either.
>>> 
>>> DM
>>> 
>>>> On Jan 5, 2019, at 7:11 AM, David Haslam dfhdfh at protonmail.com wrote:
>>>> I downloaded JapDenmo (via Xiphos) and still got the old 2008 module.
>>>> When, oh when, is the server sync issue going to be fixed????
>>>> Best regards,
>>>> David
>>>> Sent with ProtonMail Secure Email.
>>>> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>>>> On Saturday, 5 January 2019 11:08, refdoc at crosswire.org wrote:
>>>> 
>>>>> Dear All,
>>>>> This is to announce that we have just now uploaded JapDenmo.
>>>>> This is is an updated version of JapDenmo.
>>>>> Many thanks to Cyrille for the hard work.
>>>>> yours
>>>>> The Module Team
>>>>> P.S.: This email is sent automatically on upload of a new/updated module
>>>>> sword-devel mailing list: sword-devel at crosswire.org
>>>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>>>> Instructions to unsubscribe/change your settings at above page
>>>> 
>>>> sword-devel mailing list: sword-devel at crosswire.org
>>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>>> Instructions to unsubscribe/change your settings at above page
>>> 
>>> sword-devel mailing list: sword-devel at crosswire.org
>>> http://www.crosswire.org/mailman/listinfo/sword-devel
>>> Instructions to unsubscribe/change your settings at above page
>> 
>> 
>> 
>> _______________________________________________
>> sword-devel mailing list: sword-devel at crosswire.org
>> http://www.crosswire.org/mailman/listinfo/sword-devel
>> Instructions to unsubscribe/change your settings at above page
> 
> 
> _______________________________________________
> sword-devel mailing list: sword-devel at crosswire.org
> http://www.crosswire.org/mailman/listinfo/sword-devel
> Instructions to unsubscribe/change your settings at above page




More information about the sword-devel mailing list